gnome-shell freezes randomly

Bug #1725932 reported by Hiruna Wijesinghe
40
This bug affects 9 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

+++UBUNTU RELEASE+++

Description: Ubuntu 17.10
Release: 17.10

+++PACKAGE VERSION+++

gnome-shell:
  Installed: 3.26.1-0ubuntu5
  Candidate: 3.26.1-0ubuntu5
  Version table:
 *** 3.26.1-0ubuntu5 500
        500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     3.26.1-0ubuntu4 500
        500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

First found this bug when I copied some files into /opt/ via root access nautilus. After clicking on another window, Ubuntu froze.

This happened again and possibly recreated by performing root operations and navigating around gnome.

Here is something I found interesting in the /var/log/syslog:

Oct 22 19:03:14 hiruna-ubuntu-XPS kernel: [ 9031.695578] traps: gnome-shell[1813] general protection ip:7f91e14a6de2 sp:7ffd8ed31070 error:0 in libgobject-2.0.so.0.5400.1[7f91e1471000+52000]

This ^ was about the time when it froze the laptop.

Also it should be noted that this keeps repeating over and over:

Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: addSignalMethods is replacing existing [0x564478e7a990 Gjs_ShowAppsIcon.dash-item-container] connect method
Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: addSignalMethods is replacing existing [0x564478e7a990 Gjs_ShowAppsIcon.dash-item-container] disconnect method
Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: addSignalMethods is replacing existing [0x564478e7a990 Gjs_ShowAppsIcon.dash-item-container] emit method
Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 60 times: [ unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.]
Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: [AppIndicatorSupport-DEBUG] Reload detected, destroying old watchdog
Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 568 times: [ unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.]
Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-session[1763]: gnome-session-binary[1763]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-session-binary[1763]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 30 times: [ unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.]
Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Too many open files. dconf will not work properly.

I will attach a syslog below.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 19:18:47 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-05-24 (151 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-19 (2 days ago)

Revision history for this message
Hiruna Wijesinghe (hiruna) wrote :
Revision history for this message
Hiruna Wijesinghe (hiruna) wrote :

Here is a snip of the syslog where the issue occurred.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

We're going to need to analyse the hung gnome-shell process. Please
try to do this:

1. Install openssh-server:
   sudo apt install openssh-server
2. Using a second machine, log into the offending machine via SSH:
   ssh <USERNAME>@<HOSTNAME>
   where <USERNAME> is your username, and <HOSTNAME> is either hostname or the machine's IP address.
3. Reproduce the freeze.
4. From your ssh login, run:
   killall -TRAP -u $USER gnome-shell
5. Look in /var/crash for a newly created file, something like '_usr_bin_gnome-shell.1000.crash'
6. Upload the crash file using this command or similar:
   ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
7. Tell use the new bug ID that was created.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Hiruna Wijesinghe (hiruna) wrote :

Hi Daniel,

Sorry for this late reply, I've been studying for college finals.

I followed your steps and here is the .crash file as requested.

How I was able to recreate the crash multiple times:

1. Login
2. Open terminal, run sudo nautilus
--> I get this error :

Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused

(nautilus:4129): Gtk-WARNING **: cannot open display: :0

3. Run su, login and run nautilus
4. Navigate to /opt/<some app folder>
5. Open a file and close it
6. Copy that file to my non root desktop (/home/hiruna/Desktop in my case)
7. Open the file normally from the non root user
--> Immediate freeze

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks but please do:

6. Upload the crash file using this command or similar:
   ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
7. Tell use the new bug ID that was created.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
tags: added: need-amd64-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Hiruna Wijesinghe (hiruna) wrote :

Hi Daniel,

When I try to report the bug, I get this error :/ (see attachment)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, sorry to hear. Please retry, or try making a whole new .crash file?

Revision history for this message
Hiruna Wijesinghe (hiruna) wrote : Re: [Bug 1725932] Re: gnome-shell freezes randomly
Download full text (4.8 KiB)

I will re-create the crash and try to make/upload a new file by tonight

On Wed, Oct 25, 2017 at 2:52 PM, Daniel van Vugt <
<email address hidden>> wrote:

> OK, sorry to hear. Please retry, or try making a whole new .crash file?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725932
>
> Title:
> gnome-shell freezes randomly
>
> Status in gnome-shell package in Ubuntu:
> Incomplete
>
> Bug description:
> +++UBUNTU RELEASE+++
>
> Description: Ubuntu 17.10
> Release: 17.10
>
> +++PACKAGE VERSION+++
>
> gnome-shell:
> Installed: 3.26.1-0ubuntu5
> Candidate: 3.26.1-0ubuntu5
> Version table:
> *** 3.26.1-0ubuntu5 500
> 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64
> Packages
> 100 /var/lib/dpkg/status
> 3.26.1-0ubuntu4 500
> 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
>
> First found this bug when I copied some files into /opt/ via root
> access nautilus. After clicking on another window, Ubuntu froze.
>
> This happened again and possibly recreated by performing root
> operations and navigating around gnome.
>
> Here is something I found interesting in the /var/log/syslog:
>
> Oct 22 19:03:14 hiruna-ubuntu-XPS kernel: [ 9031.695578] traps: gnome-
> shell[1813] general protection ip:7f91e14a6de2 sp:7ffd8ed31070 error:0
> in libgobject-2.0.so.0.5400.1[7f91e1471000+52000]
>
> This ^ was about the time when it froze the laptop.
>
> Also it should be noted that this keeps repeating over and over:
>
> Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING:
> addSignalMethods is replacing existing [0x564478e7a990
> Gjs_ShowAppsIcon.dash-item-container] connect method
> Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING:
> addSignalMethods is replacing existing [0x564478e7a990
> Gjs_ShowAppsIcon.dash-item-container] disconnect method
> Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING:
> addSignalMethods is replacing existing [0x564478e7a990
> Gjs_ShowAppsIcon.dash-item-container] emit method
> Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create
> file '/run/user/1000/dconf/user': Permission denied. dconf will not work
> properly.
> Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 60
> times: [ unable to create file '/run/user/1000/dconf/user': Permission
> denied. dconf will not work properly.]
> Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]:
> [AppIndicatorSupport-DEBUG] Reload detected, destroying old watchdog
> Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create
> file '/run/user/1000/dconf/user': Permission denied. dconf will not work
> properly.
> Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated
> 568 times: [ unable to create file '/run/user/1000/dconf/user': Permission
> denied. dconf will not work properly.]
> Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-session[1763]:
> gnome-session-binary[1763]: dconf-CRITICAL: unable to create file
> '/run/user/1000/dconf/user': Permission denied. dconf will not work
> p...

Read more...

Revision history for this message
Hiruna Wijesinghe (hiruna) wrote :

I will re-create the crash and try to make/upload a new file by tonight

Revision history for this message
Hiruna Wijesinghe (hiruna) wrote :

Hi again,

I removed the old crash file and re-created and trapped the crash. It's not corrupted anymore. however, I just tried to report the bug 3 times but I keep getting 502 error. :/ (see attachment)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Ugg. Sorry about that. I don't fully understand the Ubuntu policy on that myself, but it did change over night:

  https://launchpad.net/ubuntu/+source/apport/2.20.7-0ubuntu3.1

You might have some luck by downgrading your apport packages to the previous version first:

  https://launchpad.net/ubuntu/+source/apport/2.20.7-0ubuntu3/+build/13569366

Again, sorry about that. I need to get in contact with the relevant Canonical staff and ask what the rationale for periodically disabling crash reports is...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Hiruna Wijesinghe (hiruna) wrote :
Download full text (5.1 KiB)

Hi Daniel,

After downgrading apport to the version you specified, I was able to submit
a new bug 1727603 :

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727603

I was notified that this report contains private information and it was
automatically selected as private. I changed the visibility to public after
going through the .txt files. Please let me know if I should change the bug
visibility back to private.

Thanks

On Thu, Oct 26, 2017 at 2:22 PM, Daniel van Vugt <
<email address hidden>> wrote:

> Please try this:
>
> https://wiki.ubuntu.com/Apport#Why_is_apport_disabled_by_default.3F
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725932
>
> Title:
> gnome-shell freezes randomly
>
> Status in gnome-shell package in Ubuntu:
> Incomplete
>
> Bug description:
> +++UBUNTU RELEASE+++
>
> Description: Ubuntu 17.10
> Release: 17.10
>
> +++PACKAGE VERSION+++
>
> gnome-shell:
> Installed: 3.26.1-0ubuntu5
> Candidate: 3.26.1-0ubuntu5
> Version table:
> *** 3.26.1-0ubuntu5 500
> 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64
> Packages
> 100 /var/lib/dpkg/status
> 3.26.1-0ubuntu4 500
> 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
>
> First found this bug when I copied some files into /opt/ via root
> access nautilus. After clicking on another window, Ubuntu froze.
>
> This happened again and possibly recreated by performing root
> operations and navigating around gnome.
>
> Here is something I found interesting in the /var/log/syslog:
>
> Oct 22 19:03:14 hiruna-ubuntu-XPS kernel: [ 9031.695578] traps: gnome-
> shell[1813] general protection ip:7f91e14a6de2 sp:7ffd8ed31070 error:0
> in libgobject-2.0.so.0.5400.1[7f91e1471000+52000]
>
> This ^ was about the time when it froze the laptop.
>
> Also it should be noted that this keeps repeating over and over:
>
> Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING:
> addSignalMethods is replacing existing [0x564478e7a990
> Gjs_ShowAppsIcon.dash-item-container] connect method
> Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING:
> addSignalMethods is replacing existing [0x564478e7a990
> Gjs_ShowAppsIcon.dash-item-container] disconnect method
> Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING:
> addSignalMethods is replacing existing [0x564478e7a990
> Gjs_ShowAppsIcon.dash-item-container] emit method
> Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create
> file '/run/user/1000/dconf/user': Permission denied. dconf will not work
> properly.
> Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 60
> times: [ unable to create file '/run/user/1000/dconf/user': Permission
> denied. dconf will not work properly.]
> Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]:
> [AppIndicatorSupport-DEBUG] Reload detected, destroying old watchdog
> Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create
> file '/run/user/1000/dconf/user': Permission denied. dconf will not work
> properly.
> Oct...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.