Arch Linux

kobhian

Member

Registered: 2021-02-07

Posts: 20

[solved] Oh no! Something has gone wrong (gdm/gnome)

Hello,

I've just installed Arch on my new laptop (lenovo thinkpad x1 carbon 8th gen/intel graphics), everything was fine last time I left my computer, just closed my laptop only to come back to this issue:

Once I am greeted by the gdm login window and I enter my login details, I get this error - Oh no! Something has gone wrong! which sends me back to gdm login panel.

- I haven't updated the system, it's a 5/6h old fresh install.
- Last thing I recall changing was a few app icons with alacarte (aur)

here's my xorg.0.log - https://pastebin.com/XrzRFns4

Thanks in advance!

Last edited by kobhian (2021-02-09 01:22:26)

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: [solved] Oh no! Something has gone wrong (gdm/gnome)

Does this happen with both Xorg and Wayland sessions?
Wayland is the default, and therefore the Xorg.0.log probably isn't useful here (and I didn't notice any errors in it anyway).

Please post logs from systemd journal from when you try to log in, as it should contain any possible error output.

kobhian

Member

Registered: 2021-02-07

Posts: 20

Re: [solved] Oh no! Something has gone wrong (gdm/gnome)

Hello ooo,

It happens with both Xorg and Wayland sessions, yes.

Here's the output of my latest session journal - https://pastebin.com/cf84WukX

Thank you!

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: [solved] Oh no! Something has gone wrong (gdm/gnome)

This looks like it might be the fatal error:

Feb 08 22:17:20 archlx gnome-shell[898]: JS ERROR: TypeError: app.app_info.get_icon().names is undefined
                                         _createSubMenu@resource:///org/gnome/shell/ui/status/system.js:89:41
                                         _init@resource:///org/gnome/shell/ui/status/system.js:20:14
                                         _init@resource:///org/gnome/shell/ui/panel.js:743:24
                                         _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1070:25
                                         _updateBox@resource:///org/gnome/shell/ui/panel.js:1081:34
                                         _updatePanel@resource:///org/gnome/shell/ui/panel.js:1027:14
                                         _init@resource:///org/gnome/shell/ui/panel.js:836:14
                                         _initializeUI@resource:///org/gnome/shell/ui/main.js:218:13
                                         start@resource:///org/gnome/shell/ui/main.js:159:5
                                         @<main>:1:47

Based on the error, my guess it that something went wrong when you changed those icons with alacarte. You should probably be able to revert whatever changes you made, by removing the broken .desktop files from $HOME/.local/share/applications.

kobhian

Member

Registered: 2021-02-07

Posts: 20

Re: [solved] Oh no! Something has gone wrong (gdm/gnome)

ooo, spot on.

Thanks so much!

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: [solved] Oh no! Something has gone wrong (gdm/gnome)

It might also be appropriate to report this as an issue to gnome-shell and alacarte.

The gnome-shell really shouldn't fail to start just because there's an broken desktop file somewhere. If you reproduce the broken .desktop files and figure out what was wrong with them (e.g. whether the icon name was wrong, or if the files was malformed in some other way), I'd imagine it shouldn't be too difficult to add a failsafe in gnome-shell to prevent the crash.

In the case of alacarte, I can't tell if the program was misbehaving or if there was some kind of user erro, without seeing the generated files. However, I don't think the application should generate broken desktop files in either scenario. Again, it's best if you can figure out what actually was wrong in the generated files. If you need help with that let me know :)