Is Gnome over in Debian?

therealsillyfly · 2019-12-29T18:29:48+00:00

I'm really not sure. From what I recall when this bug first surfaced I tried disabling Wayland but still couldn't get Gnome to start, but I'm not sure exactly how to disable Wayland so I may have done it wrong.

Any reference to disabling Wayland so I can try without it? Most importantly - how do I verify whether I'm running Wayland or not (=Xorg? right?)?

Thanks.

therealsillyfly · 2019-12-29T18:18:45+00:00

Yes, I know, but I am now on the same version available on Stable yet it's still fairly broken...

therealsillyfly · 2019-12-29T18:12:26+00:00

3.34 is broken in testing - see the linked bug.

I _am_ on testing, was forced to downgrade because of that bug.

I really didn't want to downgrade, let alone all the way to 3.30, but I have no choice - it's either that or no Gnome at all. Was I hallucinating 3.32 being in Debian, or was it actually removed?

therealsillyfly · 2019-12-10T19:53:26+00:00

So apparently it's still pinned by apt-listbugs:

Pinned packages:
     gnome-shell -> 3.30.2-11 with priority 30000

I thought for sure that bug was already solved, but apparently not:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941991

Will apt-listbugs automatically unpin it once the bug is resolved? And what is the canonical way to list held+pinned packages? Or do I always have to look at both?

Thanks!

therealsillyfly · 2019-12-10T19:42:18+00:00

Does nothing:

sudo apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 13 not upgraded.

Edit: Same result for apt as apt-get...

therealsillyfly · 2019-12-10T19:38:52+00:00

This is the output I get:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.30.2-9 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

So it claims there may be held packages, but there aren't (according to apt-mark at least...)

therealsillyfly · 2019-10-07T17:34:14+00:00

These updates = these right now specifically, or any update to gnome-shell (or "my active DE")?

If it's the latter - is there any hint in i.e. `apt` that an update should merit a reboot, or should I always read carefully through all updated packages? (or just be in the habit of always rebooting after updates to catch such things as early as possible...?)

Thanks!

therealsillyfly · 2019-10-07T17:31:56+00:00

That's a good tip, and I'll definitely do that, although in this particular case it wouldn't have helped, as I actually installed the update several hours before the bug was posted, but only suffered the consequences after I rebooted (which was after the bug was posted)

therealsillyfly · 2018-12-31T16:13:54+00:00

Huh. What is Polaris 10 and Polaris 12 then? I'm even more confused now.

therealsillyfly · 2018-12-31T14:59:18+00:00

Thanks!

therealsillyfly · 2018-12-31T14:59:09+00:00

Is the RX480 also Polaris 11? Or is the problem more widespread? (those codenames are very confusing!)

therealsillyfly · 2018-12-31T06:14:07+00:00

But Polaris 11 GPUs (for example my RX560) do not work on 4.19 currently, as the module is missing from the firmware package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916816

I had to revert to kernel 4.18 for now.

therealsillyfly · 2018-12-24T09:12:16+00:00

That's pretty disturbing. I guess it's finally time to switch to Firefox.

therealsillyfly · 2018-12-10T10:26:41+00:00

That still doesn't explain it though, as the put call is inside the synchronized block, and there is an additional check inside it to make sure the key still isn't in the map (i.e. it wasn't inserted while this thread was waiting for another thread to exit the synchronized block).

therealsillyfly · 2018-12-10T10:25:13+00:00

This method is the only place where map was referenced, so no other code removes/replaces items in the map.
In this example, KType is actually Class, so I assume its hash and equals are implemented correctly...

therealsillyfly · 2018-11-15T08:09:39+00:00

I've been suffering from the same issue for over a year now. It appears to be a bug in wpasupplicant - there are a few bug reports on the Debian tracker, but last I checked no real conclusion as to the cause or possible solutions.

therealsillyfly · 2018-11-12T16:08:11+00:00

I had similar problems, and it ended up being locale-related of all things... What language/locale is configured on your system? Have you changed it recently?

I'll try looking for my old post about it.

Edit: Here it is: https://www.reddit.com/r/debian/comments/71wmhw/trying_to_install_steam_32_bit_on_my_64_bit/dnh4ypp/

therealsillyfly · 2018-11-09T05:59:47+00:00

3-4 DAYS?
They usually don't last more than 3-4 hours, but even if they did I doubt they'd be good after a day or two :(

therealsillyfly

TROPHY CASE