Bug#810904: libmutter: Cannot start gnome-session as I got "Oh no something has gone wrong" libmutter ERROR 4
juan herrera
juanjo19m89 at gmail.com
Wed Jan 13 15:39:08 UTC 2016
Package: libmutter0e
Version: 3.14.4-1~deb8u1
Severity: important
File: libmutter
Dear Maintainer, thanks for your help on this thread!
* What led up to the situation?
Unexpected system behaviour, I was not expecting the system to failed, as this system is a stable Debian version system.
* What exactly did you do (or not do) that was effective (or
ineffective)?
A couple of days before having this error, I updated the system, These are the results of the update from apt log
Start-Date: 2016-01-07 20:39:42
Upgrade: python-samba:amd64 (4.1.17+dfsg-2, 4.1.17+dfsg-2+deb8u1), samba-common-bin:amd64 (4.1.17+dfsg-2, 4.1.17+dfsg-2+deb8u1), libldb1:amd64 (1.1.17-2, 1.1.17-2+deb8u1), samba-libs:amd64 (4.1.17+dfsg-2, 4.1.17+dfsg-2+deb8u1), git-man:amd64 (2.1.4-2.1, 2.1.4-2.1+deb8u1), git:amd64 (2.1.4-2.1, 2.1.4-2.1+deb8u1), smbclient:amd64 (4.1.17+dfsg-2, 4.1.17+dfsg-2+deb8u1), libwbclient0:amd64 (4.1.17+dfsg-2, 4.1.17+dfsg-2+deb8u1), linux-libc-dev:amd64 (3.16.7-ckt20-1+deb8u1, 3.16.7-ckt20-1+deb8u2), python-ldb:amd64 (1.1.17-2, 1.1.17-2+deb8u1), samba-common:amd64 (4.1.17+dfsg-2, 4.1.17+dfsg-2+deb8u1), libsmbclient:amd64 (4.1.17+dfsg-2, 4.1.17+dfsg-2+deb8u1)
End-Date: 2016-01-07 20:40:18
Start-Date: 2016-01-11 20:12:33
Commandline: apt-get install pkgconf
Install: pkgconf:amd64 (0.9.7-1)
End-Date: 2016-01-11 20:12:37
Start-Date: 2016-01-11 20:30:12
Commandline: /usr/sbin/synaptic
Install: libsodium-dbg:amd64 (1.0.0-1), libsodium-dev:amd64 (1.0.0-1), libsodium13:amd64 (1.0.0-1, automatic)
End-Date: 2016-01-11 20:30:13
The next morning the "Oh no something has gone wrong" message appears, I had the NVIDIA-Linux-x86_64-346.72.run so I thought I need it to update it, so I did to the NVIDIA-Linux-x86_64-352.63.run, but issues still remains
* What was the outcome of this action?
I cannot use my both monitors (Display Port and VGA), only one (VGA) when disconnecting the display port cable if connected I can only use the virtual terminals
I still have the same error:
[ 54.697265] gnome-shell[1531]: segfault at 0 ip 00007f7877fbadb2 sp 00007ffeb03168c0 error 4 in libmutter.so.0.0.0[7f7877f6d000+103000]
[ 54.878411] gnome-shell[1552]: segfault at 0 ip 00007ff52cfeddb2 sp 00007ffe196c92c0 error 4 in libmutter.so.0.0.0[7ff52cfa0000+103000]
I think this is because of:
Jan 12 21:19:49 k9 gnome-session[2477]: gnome-session[2477]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
Jan 12 21:19:49 k9 gnome-session[2477]: (gnome-shell:2487): mutter-WARNING **: Could not stat /dev/dri/card0: No such file or directory
Jan 12 21:19:49 k9 gnome-session[2477]: (gnome-shell:2487): Clutter-CRITICAL **: Unable to initialize Clutter: Failed to connected to any renderer due to constraints
Jan 12 21:19:49 k9 gnome-session[2477]: (gnome-shell:2487): mutter-ERROR **: Unable to initialize Clutter.
Jan 12 21:19:49 k9 gnome-session[2477]: gnome-session[2477]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 5
Jan 12 21:19:49 k9 kernel: [ 3088.137358] gnome-shell[2487] trap int3 ip:7f6e2c826d30 sp:7ffca4885ba0 error:0
I also found this in syslog
Jan 13 08:44:53 k9 gnome-session[1346]: (tracker-miner-fs:1597): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
Jan 13 08:44:53 k9 gnome-session[1346]: (tracker-miner-fs:1597): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
Jan 13 08:44:53 k9 gnome-session[1346]: (tracker-miner-fs:1597): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
Jan 13 08:44:53 k9 gnome-session[1346]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
Jan 13 08:44:53 k9 gnome-session[1346]: Received signal:15->'Terminated'
Jan 13 08:44:53 k9 org.gnome.evolution.dataserver.Sources3[1394]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
Jan 13 08:44:53 k9 gnome-session[1346]: (nm-applet:1582): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
* What outcome did you expect instead?
I was expecting to resolve the issue, updating the NVIDIA driver
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libmutter0e depends on:
ii gsettings-desktop-schemas 3.14.1-1
ii libc6 2.19-18+deb8u1
ii libcairo2 1.14.0-2.1
ii libcanberra-gtk3-0 0.30-2.1
ii libcanberra0 0.30-2.1
ii libclutter-1.0-0 1.20.0-1
ii libcogl20 1.18.2-3
ii libdrm2 2.4.58-2
ii libgbm1 10.3.2-1+deb8u1
ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u4
ii libgirepository-1.0-1 1.42.0-2.2
ii libglib2.0-0 2.42.1-1
ii libgnome-desktop-3-10 3.14.1-1
ii libgtk-3-0 3.14.5-1+deb8u1
ii libice6 2:1.0.9-1+b1
ii libinput5 0.6.0+dfsg-2
ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3
ii libsm6 2:1.2.2-1+b1
ii libstartup-notification0 0.12-4
ii libsystemd0 215-17+deb8u2
ii libupower-glib3 0.99.1-3.2
ii libwayland-client0 1.6.0-2
ii libwayland-server0 1.6.0-2
ii libx11-6 2:1.6.2-3
ii libx11-xcb1 2:1.6.2-3
ii libxcb-randr0 1.10-3+b1
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1+b1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.1-2+b2
ii libxi6 2:1.7.4-1+b2
ii libxinerama1 2:1.1.3-1+b1
ii libxkbcommon-x11-0 0.4.3-2
ii libxkbcommon0 0.4.3-2
ii libxkbfile1 1:1.0.8-1
ii libxrandr2 2:1.4.2-1+b1
ii mutter-common 3.14.4-1~deb8u1
libmutter0e recommends no packages.
libmutter0e suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list