Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42547 - upower 0.99.1-2 causes gnome-shell to crash on boot
Attached to Project:
Arch Linux
Opened by Jonas Frei (freijon) - Saturday, 25 October 2014, 10:37 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 October 2014, 15:18 GMT
Opened by Jonas Frei (freijon) - Saturday, 25 October 2014, 10:37 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 October 2014, 15:18 GMT
|
DetailsDescription:
After updating to upower 0.99.1-2, gnome-shell crashes on start, leaving me with the "Oh no, something has gone wrong" screen. journalctl shows the following error: Okt 25 12:12:29 arch gnome-session[1326]: /usr/bin/gnome-shell: error while loading shared libraries: libupower-glib.so.2: cannot open shared object file: No such file or directory Okt 25 12:12:29 arch gnome-session[1326]: gnome-session[1326]: WARNING: App 'gnome-shell.desktop' exited with code 127 Downgrading to upower 0.99.0-3 fixes the problem Steps to reproduce: 1) update to upower 0.99.1-2 2) reboot |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Saturday, 25 October 2014, 14:52 GMT
Your problem is not with gnome-shell as it doesn't link to upower. Is your entire system up to date? Do you have anything from the AUR/ABS?
Comment by Jonas Frei (freijon) -
Saturday, 25 October 2014, 15:04 GMT
I'm aware of that, I'm filing the bug against upower which clearly seems to be the problem.I have "mutter" from ABS.
Comment by Doug Newgard (Scimmia) -
Saturday, 25 October 2014, 15:09 GMT
The problem isn't with upower. It's with whatever you have that links to upower that wasn't rebuilt for the soname bump. You'll notice mutter was rebuilt for this reason: https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/mutter&id=d62f448ccbca9838b23f40302ba84a4d0bfbb1bf . If you didn't rebuild your local copy, that's the problem.
Comment by Jonas Frei (freijon) -
Saturday, 25 October 2014, 15:14 GMT
You are right, I reinstalled "mutter" from the repository and now I can fully update the system without upower causing problems. Guess this bug report is invalid then... Thanks