Page 1 of 1

[SOLVED] Problems switching Cinnamon->Mate

Posted: Sun Dec 09, 2018 9:08 pm
by Kudalufi
I have finally grown fed up with Cinnamon and am trying to switch to mate. I stopped my desktop, logged into a pty and used apt-get to install mint-meta-mate. After a reboot, Mate correctly appeared in the list of window managers for LightDM. Attempting to log into it, though, causes the screen to go blank and for the LightDM login screen to reappear.

I have read about problems with panels for people doing what I have done, which requires rebuilding them. But I have not heard of issues even logging in. Is there a trick? Do I need to remove Cinammon before this will work?

I'm not even really sure what logs to peruse. Syslog was not really helpful to me, but I can attach it if it would be useful to anyone else.

Re: Problems switching Cinnamon->Mate

Posted: Mon Dec 10, 2018 3:15 pm
by deepakdeshp
Best and easiest would be to backup your data and make a fresh install.

Re: Problems switching Cinnamon->Mate

Posted: Mon Dec 10, 2018 3:40 pm
by gm10
Kudalufi wrote:
Sun Dec 09, 2018 9:08 pm
I have read about problems with panels for people doing what I have done, which requires rebuilding them. But I have not heard of issues even logging in. Is there a trick? Do I need to remove Cinammon before this will work?
No, I'm not sure why that happened. Can you still log in when selecting Cinnamon? If not then the issue is unrelated, in which case log in via a virtual terminal and

Code: Select all

rm .ICEauthority  .Xauthority
Another classic is

Code: Select all

sudo chown $USER:$USER ~
One of those usually does it. Unless your disk is full, which is another common cause:

Code: Select all

df / /home

Re: Problems switching Cinnamon->Mate

Posted: Mon Dec 10, 2018 9:58 pm
by Kudalufi
Yes, I can still log in with Cinnamon with no trouble.

I created a new user, one that had never logged into Cinnamon, just in case that was an issue, and it still couldn't log in. Here is the syslog output from that attempt.

Notable are systemd failing repeatedly, and:
Dec 9 20:35:16 GlitchV2 mate-session[5369]: GLib-GIO-ERROR: Settings schema 'org.gnome.Vino' does not contain a key named 'enabled'#012aborting...

Even though systemd is logged first as failing, I'm wondering if the error for Vino is actually occurring first and logged after as it comes from a different process.

The installation is a luks/dm-crypt encrypted system that is a dual-boot with Windows. The tutorials for this are mostly outdated and painful to implement, so I'd really rather not have to reinstall if possible.

Code: Select all

Dec  9 20:35:13 GlitchV2 systemd[1]: Started User Manager for UID 1001.
Dec  9 20:35:15 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] AppArmor D-Bus mediation is enabled
Dec  9 20:35:15 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1001 pid=5678 comm="dbus-update-activation-environment --verbose --sys" label="unconfined")
Dec  9 20:35:15 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Dec  9 20:35:15 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=1001 pid=5690 comm="dbus-update-activation-environment --verbose --sys" label="unconfined")
Dec  9 20:35:15 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Dec  9 20:35:15 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=1001 pid=5696 comm="dbus-update-activation-environment --verbose --sys" label="unconfined")
Dec  9 20:35:15 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='org.a11y.Bus' requested by ':1.3' (uid=1001 pid=5369 comm="mate-session " label="unconfined")
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Successfully activated service 'org.a11y.Bus'
Dec  9 20:35:16 GlitchV2 org.a11y.Bus[5676]: dbus-daemon[5779]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1001 pid=5369 comm="mate-session " label="unconfined")
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='org.freedesktop.systemd1' requested by ':1.6' (uid=1001 pid=5369 comm="mate-session " label="unconfined")
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Dec  9 20:35:16 GlitchV2 org.a11y.Bus[5676]: dbus-daemon[5779]: Successfully activated service 'org.a11y.atspi.Registry'
Dec  9 20:35:16 GlitchV2 org.a11y.Bus[5676]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=1001 pid=5369 comm="mate-session " label="unconfined")
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=1001 pid=5369 comm="mate-session " label="unconfined")
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='ca.desrt.dconf' requested by ':1.7' (uid=1001 pid=5369 comm="mate-session " label="unconfined")
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Successfully activated service 'ca.desrt.dconf'
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=1001 pid=5369 comm="mate-session " label="unconfined")
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=1001 pid=5369 comm="mate-session " label="unconfined")
Dec  9 20:35:16 GlitchV2 dbus-daemon[5676]: [session uid=1001 pid=5674] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Dec  9 20:35:16 GlitchV2 mate-session[5369]: GLib-GIO-ERROR: Settings schema 'org.gnome.Vino' does not contain a key named 'enabled'#012aborting...
Dec  9 20:35:16 GlitchV2 mate-session[5369]: ******************* START ********************************
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 0: mate-session(+0x1b9d5) [0x561b649b19d5]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 1: mate-session(+0x1bba7) [0x561b649b1ba7]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 2: /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7f6a51881f20]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 3: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x51e11) [0x7f6a51f09e11]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 4: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x27b) [0x7f6a51f0b15b]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 5: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x8f) [0x7f6a51f0b2af]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 6: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x10e159) [0x7f6a529a4159]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 7: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x10e78c) [0x7f6a529a478c]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 8: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_get_value+0x5f) [0x7f6a529a82af]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 9: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_get_boolean+0xb) [0x7f6a529a93ab]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 10: mate-session(+0xd927) [0x561b649a3927]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 11: mate-session(+0xea49) [0x561b649a4a49]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 12: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1557e) [0x7f6a521e357e]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 13: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_valist+0x3d0) [0x7f6a521e55c0]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 14: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new+0x99) [0x7f6a521e5939]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 15: mate-session(+0xf06f) [0x561b649a506f]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 16: mate-session(+0x24e51) [0x561b649bae51]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 17: mate-session(+0x250bd) [0x561b649bb0bd]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 18: mate-session(+0xc2f6) [0x561b649a22f6]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 19: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f6a51864b97]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: Frame 20: mate-session(+0xc5ca) [0x561b649a25ca]
Dec  9 20:35:16 GlitchV2 mate-session[5369]: ******************* END **********************************
Dec  9 20:35:16 GlitchV2 at-spi-bus-laun[5774]: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Dec  9 20:35:16 GlitchV2 org.a11y.Bus[5676]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Dec  9 20:35:16 GlitchV2 org.a11y.Bus[5676]:       after 21 requests (21 known processed) with 0 events remaining.

Re: Problems switching Cinnamon->Mate

Posted: Tue Dec 11, 2018 4:11 am
by gm10
Hmm ok, so I guess you've got a corrupt schema for that package, although it's interesting it would crash your session. Are you relying on the Vino VNC server? Otherwise please do

Code: Select all

apt purge --autoremove vino
and then try logging in with MATE again.

Re: Problems switching Cinnamon->Mate

Posted: Tue Dec 18, 2018 12:03 am
by Kudalufi
What a simple solution. I had just assumed that it was required for Vino to be in the chain because Gnome. I have no need of a VNC server, so gone it is and Mate now loads up beautifully. I had been pulling my hair out, since the only reference to this that I could see was here, and there was no resolution.

Perhaps this is a vestigial leftover from an older upgrade.