[Desktop-packages] [Bug 1815121] Re: Nautilus chashes on login
That's gnome-software and coming from GNOME, you should report that upstream to them -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815121 Title: Nautilus chashes on login Status in nautilus package in Ubuntu: Invalid Bug description: Nautilus crashes when logging in. I see the desktop wallpaper for a second and then it returns to the login screen. I found this in /var/log/apport.log: ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: called for pid 9470, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: executable: /usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service") ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: gdbus call error: Error connecting: Error receiving data: Connection reset by peer ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: debug: session gdbus call: ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: wrote report /var/crash/_usr_bin_nautilus.1000.crash And this in /var/log/syslog (with lots of other similar messages at 21:17:53): Feb 4 21:17:53 zen org.gnome.Shell.desktop[2532]: #7 0x559d466223f0 i /home/ahlberg/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:375 (0x7f4d28080d58 @ 962) Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4951c850), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4b214460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4bb86460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:59 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen kernel: [169739.521202] rfkill: input handler enabled Feb 4 21:18:00 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen gsd-print-notif[2639]: Source ID 2 was not found when attempting to remove it Feb 4 21:18:01 zen systemd[1]: Stopping Thunderbolt system service... Feb 4 21:18:01 zen systemd[1]: Stopped target Bluetooth. Feb 4 21:18:01 zen systemd[1]: Stopping User Manager for UID 1000... Feb 4 21:18:01 zen systemd[1]: Stopping Save/Restore Sound Card State... Feb 4 21:18:01 zen systemd[1]: Stopping Daemon for generating UUIDs... Feb 4 21:18:01 zen kernel: [169739.643650] nautilus[9470]: segfault at 380 ip 7f773432cfb4 sp 7ffc86dcf5b0 error 4 in libgtk-3.so.0.2200.30[7f7734191000+6f1000] I'm running Ubuntu 18.04.1 1:3.26.4-0~ubuntu18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 7 20:21:46 2019 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
[Desktop-packages] [Bug 1815121] Re: Nautilus chashes on login
It was installed through Ubuntu Software. Search for workspace-grid and you should find it there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815121 Title: Nautilus chashes on login Status in nautilus package in Ubuntu: Invalid Bug description: Nautilus crashes when logging in. I see the desktop wallpaper for a second and then it returns to the login screen. I found this in /var/log/apport.log: ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: called for pid 9470, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: executable: /usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service") ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: gdbus call error: Error connecting: Error receiving data: Connection reset by peer ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: debug: session gdbus call: ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: wrote report /var/crash/_usr_bin_nautilus.1000.crash And this in /var/log/syslog (with lots of other similar messages at 21:17:53): Feb 4 21:17:53 zen org.gnome.Shell.desktop[2532]: #7 0x559d466223f0 i /home/ahlberg/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:375 (0x7f4d28080d58 @ 962) Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4951c850), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4b214460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4bb86460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:59 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen kernel: [169739.521202] rfkill: input handler enabled Feb 4 21:18:00 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen gsd-print-notif[2639]: Source ID 2 was not found when attempting to remove it Feb 4 21:18:01 zen systemd[1]: Stopping Thunderbolt system service... Feb 4 21:18:01 zen systemd[1]: Stopped target Bluetooth. Feb 4 21:18:01 zen systemd[1]: Stopping User Manager for UID 1000... Feb 4 21:18:01 zen systemd[1]: Stopping Save/Restore Sound Card State... Feb 4 21:18:01 zen systemd[1]: Stopping Daemon for generating UUIDs... Feb 4 21:18:01 zen kernel: [169739.643650] nautilus[9470]: segfault at 380 ip 7f773432cfb4 sp 7ffc86dcf5b0 error 4 in libgtk-3.so.0.2200.30[7f7734191000+6f1000] I'm running Ubuntu 18.04.1 1:3.26.4-0~ubuntu18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 7 20:21:46 2019 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
[Desktop-packages] [Bug 1815121] Re: Nautilus chashes on login
Ubuntu installs extensions in /usr/share, .local is an user thing so that was probably installed by you through gnome-software/GNOME or manually? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815121 Title: Nautilus chashes on login Status in nautilus package in Ubuntu: Invalid Bug description: Nautilus crashes when logging in. I see the desktop wallpaper for a second and then it returns to the login screen. I found this in /var/log/apport.log: ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: called for pid 9470, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: executable: /usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service") ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: gdbus call error: Error connecting: Error receiving data: Connection reset by peer ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: debug: session gdbus call: ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: wrote report /var/crash/_usr_bin_nautilus.1000.crash And this in /var/log/syslog (with lots of other similar messages at 21:17:53): Feb 4 21:17:53 zen org.gnome.Shell.desktop[2532]: #7 0x559d466223f0 i /home/ahlberg/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:375 (0x7f4d28080d58 @ 962) Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4951c850), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4b214460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4bb86460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:59 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen kernel: [169739.521202] rfkill: input handler enabled Feb 4 21:18:00 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen gsd-print-notif[2639]: Source ID 2 was not found when attempting to remove it Feb 4 21:18:01 zen systemd[1]: Stopping Thunderbolt system service... Feb 4 21:18:01 zen systemd[1]: Stopped target Bluetooth. Feb 4 21:18:01 zen systemd[1]: Stopping User Manager for UID 1000... Feb 4 21:18:01 zen systemd[1]: Stopping Save/Restore Sound Card State... Feb 4 21:18:01 zen systemd[1]: Stopping Daemon for generating UUIDs... Feb 4 21:18:01 zen kernel: [169739.643650] nautilus[9470]: segfault at 380 ip 7f773432cfb4 sp 7ffc86dcf5b0 error 4 in libgtk-3.so.0.2200.30[7f7734191000+6f1000] I'm running Ubuntu 18.04.1 1:3.26.4-0~ubuntu18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 7 20:21:46 2019 EcryptfsInUse: Yes GsettingsChanges:
[Desktop-packages] [Bug 1815121] Re: Nautilus chashes on login
I removed the workspace-grid directory and now it works fine. Thanks for the insights! I then reinstalled workspace-grid via software center and it still works. There are some differences between the old and the new directory so it appears to be a newer release. It seems that the extension was installed once and then not maintained by software update. The fault seems to be not in gnome or the extension but in the way extensions are handled by Ubuntu. They should be kept up to date or disabled when function cannot be guaranteed. Should I report another issue for this somewhere or is it by design? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815121 Title: Nautilus chashes on login Status in nautilus package in Ubuntu: Invalid Bug description: Nautilus crashes when logging in. I see the desktop wallpaper for a second and then it returns to the login screen. I found this in /var/log/apport.log: ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: called for pid 9470, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: executable: /usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service") ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: gdbus call error: Error connecting: Error receiving data: Connection reset by peer ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: debug: session gdbus call: ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: wrote report /var/crash/_usr_bin_nautilus.1000.crash And this in /var/log/syslog (with lots of other similar messages at 21:17:53): Feb 4 21:17:53 zen org.gnome.Shell.desktop[2532]: #7 0x559d466223f0 i /home/ahlberg/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:375 (0x7f4d28080d58 @ 962) Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4951c850), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4b214460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4bb86460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:59 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen kernel: [169739.521202] rfkill: input handler enabled Feb 4 21:18:00 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen gsd-print-notif[2639]: Source ID 2 was not found when attempting to remove it Feb 4 21:18:01 zen systemd[1]: Stopping Thunderbolt system service... Feb 4 21:18:01 zen systemd[1]: Stopped target Bluetooth. Feb 4 21:18:01 zen systemd[1]: Stopping User Manager for UID 1000... Feb 4 21:18:01 zen systemd[1]: Stopping Save/Restore Sound Card State... Feb 4 21:18:01 zen systemd[1]: Stopping Daemon for generating UUIDs... Feb 4 21:18:01 zen kernel: [169739.643650] nautilus[9470]: segfault at 380 ip 7f773432cfb4 sp 7ffc86dcf5b0 error 4 in
[Desktop-packages] [Bug 1815121] Re: Nautilus chashes on login
The nautilus segfault is likely another issue than the session closing, the log errors in ~/.local/share/gnome-shell/extensions/workspace- g...@mathematical.coffee.gmail.com ... does it work better if you move that directory away (or delete it)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815121 Title: Nautilus chashes on login Status in nautilus package in Ubuntu: Invalid Bug description: Nautilus crashes when logging in. I see the desktop wallpaper for a second and then it returns to the login screen. I found this in /var/log/apport.log: ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: called for pid 9470, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: executable: /usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service") ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: gdbus call error: Error connecting: Error receiving data: Connection reset by peer ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: debug: session gdbus call: ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: wrote report /var/crash/_usr_bin_nautilus.1000.crash And this in /var/log/syslog (with lots of other similar messages at 21:17:53): Feb 4 21:17:53 zen org.gnome.Shell.desktop[2532]: #7 0x559d466223f0 i /home/ahlberg/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:375 (0x7f4d28080d58 @ 962) Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4951c850), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4b214460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4bb86460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:59 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen kernel: [169739.521202] rfkill: input handler enabled Feb 4 21:18:00 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen gsd-print-notif[2639]: Source ID 2 was not found when attempting to remove it Feb 4 21:18:01 zen systemd[1]: Stopping Thunderbolt system service... Feb 4 21:18:01 zen systemd[1]: Stopped target Bluetooth. Feb 4 21:18:01 zen systemd[1]: Stopping User Manager for UID 1000... Feb 4 21:18:01 zen systemd[1]: Stopping Save/Restore Sound Card State... Feb 4 21:18:01 zen systemd[1]: Stopping Daemon for generating UUIDs... Feb 4 21:18:01 zen kernel: [169739.643650] nautilus[9470]: segfault at 380 ip 7f773432cfb4 sp 7ffc86dcf5b0 error 4 in libgtk-3.so.0.2200.30[7f7734191000+6f1000] I'm running Ubuntu 18.04.1 1:3.26.4-0~ubuntu18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop:
[Desktop-packages] [Bug 1815121] Re: Nautilus chashes on login
Here's a link to the nautilus dump: https://errors.ubuntu.com/oops/1aa7b5fc-2b0c-11e9-8fa5-fa163e6cac46 I'm currently running a Unity desktop without seeing any crashes as I cannot log in to the default Gnome desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815121 Title: Nautilus chashes on login Status in nautilus package in Ubuntu: Invalid Bug description: Nautilus crashes when logging in. I see the desktop wallpaper for a second and then it returns to the login screen. I found this in /var/log/apport.log: ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: called for pid 9470, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: executable: /usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service") ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: gdbus call error: Error connecting: Error receiving data: Connection reset by peer ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: debug: session gdbus call: ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: wrote report /var/crash/_usr_bin_nautilus.1000.crash And this in /var/log/syslog (with lots of other similar messages at 21:17:53): Feb 4 21:17:53 zen org.gnome.Shell.desktop[2532]: #7 0x559d466223f0 i /home/ahlberg/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:375 (0x7f4d28080d58 @ 962) Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4951c850), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4b214460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4bb86460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:59 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen kernel: [169739.521202] rfkill: input handler enabled Feb 4 21:18:00 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen gsd-print-notif[2639]: Source ID 2 was not found when attempting to remove it Feb 4 21:18:01 zen systemd[1]: Stopping Thunderbolt system service... Feb 4 21:18:01 zen systemd[1]: Stopped target Bluetooth. Feb 4 21:18:01 zen systemd[1]: Stopping User Manager for UID 1000... Feb 4 21:18:01 zen systemd[1]: Stopping Save/Restore Sound Card State... Feb 4 21:18:01 zen systemd[1]: Stopping Daemon for generating UUIDs... Feb 4 21:18:01 zen kernel: [169739.643650] nautilus[9470]: segfault at 380 ip 7f773432cfb4 sp 7ffc86dcf5b0 error 4 in libgtk-3.so.0.2200.30[7f7734191000+6f1000] I'm running Ubuntu 18.04.1 1:3.26.4-0~ubuntu18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb
[Desktop-packages] [Bug 1815121] Re: Nautilus chashes on login
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815121 Title: Nautilus chashes on login Status in nautilus package in Ubuntu: Invalid Bug description: Nautilus crashes when logging in. I see the desktop wallpaper for a second and then it returns to the login screen. I found this in /var/log/apport.log: ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: called for pid 9470, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 11030) Mon Feb 4 21:18:02 2019: executable: /usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service") ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: gdbus call error: Error connecting: Error receiving data: Connection reset by peer ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: debug: session gdbus call: ERROR: apport (pid 11030) Mon Feb 4 21:18:06 2019: wrote report /var/crash/_usr_bin_nautilus.1000.crash And this in /var/log/syslog (with lots of other similar messages at 21:17:53): Feb 4 21:17:53 zen org.gnome.Shell.desktop[2532]: #7 0x559d466223f0 i /home/ahlberg/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:375 (0x7f4d28080d58 @ 962) Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4951c850), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4b214460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d4a35db40), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:53 zen gnome-shell[2532]: Object St.Bin (0x559d4bb86460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Feb 4 21:17:53 zen gnome-shell[2532]: message repeated 2 times: [ Object Shell.GenericContainer (0x559d48fe8430), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs] Feb 4 21:17:59 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen kernel: [169739.521202] rfkill: input handler enabled Feb 4 21:18:00 zen org.gnome.Shell.desktop[2532]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Feb 4 21:18:01 zen gsd-print-notif[2639]: Source ID 2 was not found when attempting to remove it Feb 4 21:18:01 zen systemd[1]: Stopping Thunderbolt system service... Feb 4 21:18:01 zen systemd[1]: Stopped target
