Description of problem:
The issue occurred after upgrading from Fedora 21 to 22. Gnome Shell on X session will crash on the session. Note that problem does not affect Gnome on Wayland
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Either upgrade from Fedora 21 to 22. Pratically upgrade Gnome Shell
X session will crash with a Oh No Something went wrong message.
Session is succesfully logged
Workaround is to backup or delete the old .config/dconf/user and relog the X session again.
It would be really useful to see a stacktrace for the shell crash.
It'd also be useful to have a copy of the offending .config file(s), I guess?
did you do fedup ? or yum update ? was it the f21 gnome-shell that crashed or the f22 shell that crashed ?
can you attach the output of journalctl -b -a ?
(In reply to Matthias Clasen from comment #1)
> It would be really useful to see a stacktrace for the shell crash.
I am unable to reproduce the bug in question but that user had that problem:
(In reply to Adam Williamson from comment #2)
> It'd also be useful to have a copy of the offending .config file(s), I guess?
The offending file was .config/dconf/userxxx. I will attach them shortly
(In reply to Ray Strode [halfline] from comment #3)
> did you do fedup ? or yum update ? was it the f21 gnome-shell that crashed
> or the f22 shell that crashed ?
Both methods. It was f22 shell that crashed on X session. Gnome on Wayland was fine.
Created attachment 1025638 [details]
old user file 8175NX from .config/dconf
Created attachment 1025639 [details]
old user file XQ7N2W from .config/dconf
Haven't been able to reproduce yet - so far tried a clean f21 install, update, and then upgrade, and also copying ~/.config/dconf from my production laptop (which is f21) to a VM and upgrading it. May try some more tomorrow, but I'm on vacation officially, so might need someone else to do it.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.