Arch Linux

anne-nl

Member

Registered: 2017-05-06

Posts: 7

Gnome: Are multiple sessions not supported anymore?

I upgraded my Arch Linux last Saturday and I did not encounter any problems.

I usually have 2 sessions open (work account and home account) and switch between them with Ctrl-Alt-F2, Ctrl-Alt-F3. In the past I have used this extensively on Ubuntu, Linux Mint and Debian. There it worked flawlessly. On Arch however, sometimes the session would crash upon switching. It was an inconvenience that I could live with.

But since the last update, I can't switch sessions at all. It crashes each and every time. I did not change any system configuration, did not install any extensions in Gnome. It just keeps crashing.

Also, I noticed that in the status menu, when I click my user name, there appears a small submenu showing 2 options: 'Logout', 'Account Setting'. There used to be a third option before the upgrade: 'Switch user'. This option is now gone.

Is this a case of removed functionality? Maybe I was the only one in the World using it ? Or is it an instability in Gnome caused by the latest update?

Last edited by anne-nl (2018-05-30 07:10:02)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: Gnome: Are multiple sessions not supported anymore?

Read your journal and establish why it is crashing.

Moving to NC...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

anne-nl

Member

Registered: 2017-05-06

Posts: 7

Re: Gnome: Are multiple sessions not supported anymore?

Ah, the thing I omitted from my initial post:  I could not find anything in the journal that says why it is crashing.

sudo journalctl -xe shows:

Lots of entries like:
gnome-shell[1075]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed

or this:
gnome-shell[8542]: Object Meta.WindowActor (0x55589e10abf0), has been already finalized. Impossible to get any property from it.
org.gnome.Shell.desktop[8542]: == Stack trace for context 0x555899de8050 ==
org.gnome.Shell.desktop[8542]: #0 0x7fff33fb93d0 b   resource:///org/gnome/shell/ui/tweener.js:73 (0x7fd32c4c7cd0 @ 9)
org.gnome.Shell.desktop[8542]: #1 0x7fff33fb9470 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7fd32c4c7f78 @ 36)
org.gnome.Shell.desktop[8542]: #2 0x7fff33fb9c80 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7fd32c4c7de0 @ 52)
org.gnome.Shell.desktop[8542]: #3 0x7fff33fba3a0 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fd32c4d2918 @ 54)
org.gnome.Shell.desktop[8542]: #4 0x7fff33fba4f0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fd32c4d29a0 @ 1626)
org.gnome.Shell.desktop[8542]: #5 0x7fff33fba5a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fd32c4d2a28 @ 100)
org.gnome.Shell.desktop[8542]: #6 0x7fff33fba630 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fd32c4d2ab0 @ 10)
org.gnome.Shell.desktop[8542]: #7 0x7fff33fba6b0 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd32c4cff78 @ 386)
org.gnome.Shell.desktop[8542]: #8 0x7fff33fba760 b   resource:///org/gnome/shell/ui/tweener.js:207 (0x7fd32c4cf5e8 @ 159)
org.gnome.Shell.desktop[8542]: #9 0x7fff33fba7c0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd32c4b5de0 @ 71)
org.gnome.Shell.desktop[8542]: #10 0x7fff33fba860 b   resource:///org/gnome/shell/ui/tweener.js:182 (0x7fd32c4cf560 @ 15)

But these happen all the time, also during normal operation. I could not find any critical error.

Last edited by anne-nl (2018-05-30 08:15:00)