vino

Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Daedalus79

vino

Post by Daedalus79 »

Good Day all,

New to the forum, and i will probably not post that much but i thought i may provide valueable information for other users :

So after ages i rebooted my old MSI CX720 laptop to Linux as my wife has been using this laptop with windows until recently when she got a new laptop.

Obviously i want the best and latest software so i updated Mint. I came from 18.something and went on to 19.0 when i thought i was up-to-date. I fiddled around a bit, noticed there was a MATE option which i did not have so i got it installed and played around with it. Then i noticed (While on MATE) that there was a 19.1 update available which i instantly ran.

After reboot I tried logging into MATE again just to see the screen flicker once or twice to return to the login screen. surprised i tried it again with the same result.

Tried CInnamon and that was no problem. Tried updating again > rebooted a couple of times while removing and installing mint-mate-meta but MATE would return to the login screen so that left me with Cinnamon. not that bad, but when things are broken i want to fix stuff.

browsing google for CLI troubleshooting i stumbled on a forum thread somewhere where it was encouraged to do :

Code: Select all

cat /var/log/syslog | grep fail
cat /var/log/syslog | grep mate
The fail gave me way to much options so i tried MATE as that was troublesome the output of that was a lot of text but this got my attention:

Code: Select all

Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: GLib-GIO-ERROR: Settings schema 'org.gnome.Vino' does not contain a key named 'enabled'#012aborting...
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: ******************* START ********************************
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 0: mate-session(+0x1b9d5) [0x5600afb679d5]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 1: mate-session(+0x1bba7) [0x5600afb67ba7]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 2: /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fcf46ff3f20]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 3: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x51e11) [0x7fcf4767be11]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 4: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x27b) [0x7fcf4767d15b]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 5: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x8f) [0x7fcf4767d2af]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 6: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x10e159) [0x7fcf48116159]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 7: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x10e78c) [0x7fcf4811678c]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 8: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_get_value+0x5f) [0x7fcf4811a2af]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 9: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_get_boolean+0xb) [0x7fcf4811b3ab]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 10: mate-session(+0xd927) [0x5600afb59927]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 11: mate-session(+0xea49) [0x5600afb5aa49]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 12: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1557e) [0x7fcf4795557e]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 13: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_valist+0x3d0) [0x7fcf479575c0]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 14: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new+0x99) [0x7fcf47957939]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 15: mate-session(+0xf06f) [0x5600afb5b06f]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 16: mate-session(+0x24e51) [0x5600afb70e51]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 17: mate-session(+0x250bd) [0x5600afb710bd]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 18: mate-session(+0xc2f6) [0x5600afb582f6]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 19: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fcf46fd6b97]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: Frame 20: mate-session(+0xc5ca) [0x5600afb585ca]
Jan 16 21:40:17 DietLinuxMint19 mate-session[1487]: ******************* END **********************************
Googling Glib-GIO-error lead to other stuff but in general i got the idea that VINO may be a dealbreaker here.
VINO turns out to be a remote desktop viewer from VNC or something like that.

So i tried locating org.gnome.Vino which gave me some results :

Code: Select all

locate org.gnome.Vino
cat /usr/share/glib-2.0/schemas/org.gnome.Vino.enums.xml 
cat /usr/share/glib-2.0/schemas/org.gnome.Vino.gschema.xml 
doing CAT on both xml files lead to nothing. (although i think the actual fault lies within /usr/share/glib-2.0/schemas/org.gnome.Vino.gschema.xml

Locating Vino even more :

Code: Select all

Diet@DietLinuxMint19 ~ $ locate vino
/etc/xdg/autostart/vino-server.desktop
/usr/bin/vino-passwd
/usr/bin/vino-preferences
/usr/lib/vino
/usr/share/vino
/usr/share/app-install/desktop/vino:vino-preferences.desktop
/usr/share/applications/vino-preferences.desktop
/usr/share/applications/vino-server.desktop
/usr/share/doc/vino
/usr/share/locale-langpack/en@shaw/LC_MESSAGES/vino.mo
/usr/share/locale-langpack/en_AU/LC_MESSAGES/vino.mo
/usr/share/locale-langpack/en_CA/LC_MESSAGES/vino.mo
/usr/share/locale-langpack/en_GB/LC_MESSAGES/vino.mo
/usr/share/locale-langpack/nl/LC_MESSAGES/vino.mo
/var/lib/dpkg/info/vino.conffiles
/var/lib/dpkg/info/vino.list
/var/lib/dpkg/info/vino.md5sums
So I

Code: Select all

cat /etc/xdg/autostart/vino-server.desktop
Where is saw that MATE uses vino as well. :

Code: Select all

Diet@DietLinuxMint19 ~ $ cat /etc/xdg/autostart/vino-server.desktop 
[Desktop Entry]
Name=Desktop Sharing
Comment=GNOME Desktop Sharing Server
Keywords=vnc;share;remote;
NoDisplay=true
Exec=/usr/lib/vino/vino-server --sm-disable
Icon=preferences-desktop-remote-desktop
OnlyShowIn=GNOME;LXDE;Unity;MATE;XFCE;
Terminal=false
Type=Application
AutostartCondition=GSettings org.gnome.Vino enabled
X-GNOME-Autostart-Phase=Applications
X-GNOME-AutoRestart=true
X-GNOME-UsesNotifications=true
X-Ubuntu-Gettext-Domain=vino
But cinnamon is not mentioned here so i figured that was the reason why Cinnamon worked, and MATE did not.

using vim I removed MATE from the red line, just to notice after reboot MATE has returned. and obviously a flickering login screen.

Then i figured I had never used vino (hell, i even had never heard of the program) so i decided to remove Vino.

After :

Code: Select all

sudo apt-get autoremove vino
and a reboot i was able to login to MATE again.

Although autoremove removed a lot of programs i still think that vino may not have been to happy on my installation.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Locked

Return to “MATE”