On Sun, Oct 6, 2019 at 11:12 AM Michael Biebl wrote:
> I'm still getting the fail-whale for the GNOME Classic session.
> Tried with a fresh user account, just to be sure.
>
> Should this bug report be reopened or should I file a new one?
Please file a new bug.
smcv and I are thinking that
I'm still getting the fail-whale for the GNOME Classic session.
Tried with a fresh user account, just to be sure.
Should this bug report be reopened or should I file a new one?
signature.asc
Description: OpenPGP digital signature
Control: reassign 940468 gnome-session
Control: forcemerge 940468 -1
Hi,
On Thu, Oct 03, 2019 at 02:16:32PM +0200, Michael Ott wrote:
> Hi!
>
> I have the same problem. And I already create a bug report here
> #940468
>
> But I found out that it is a problem with mutter.
> Using mutter
Hi!
I have the same problem. And I already create a bug report here
#940468
But I found out that it is a problem with mutter.
Using mutter 3.34.0-1 it works
CU
Michael
On 2019-10-03 19:55, Andreas Henriksson wrote:
So Gnome 3.34 is currently unusable.
FWIW I have a hard time agreeing with this conclusion.
One solution would be to simply drop support for "System X11 Default"
which we're currently patching in. I'd say using it is not recommended
and it only
More tests: the failure occurs when logging in with "System X11 Default"
or "Gnome Classic" selected from the gdm3 login screen.
Log-in via the plain "Gnome" option does successfully start a
gnome-session. Extensions from 3.30 cause it to freeze, but that's a
separate issue (it works if
Package: gnome-session
Version: 3.34.0-2
Severity: grave
Justification: renders package unusable
With the Gnome upgrade from 3.30 to 3.34, a Gnome session now fails to
start.
gdm3 runs fine, the login screen is shown and I can proceed with
logging in. But instead of logging in and starting a
7 matches
Mail list logo
