gnome-shell crashed with SIGSEGV in poll() from poll() from g_poll() from g_main_context_poll()

Bug #1300980 reported by Romano Giannetti
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNOME Shell
New
Critical
gnome-shell (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Testing the Ubuntu Gnome beta 2 in a VirtualBox VM.

Every time I restart/start the VM, the first login will fail (after gdm greeter I have a black screen with the crash report window).

Killing X (either with ctrl-alt-bcksp if enabled, or with sudo restart gdm from a VT) and logging in again do work reliably, and allowed me to file this bug report.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic i686
ApportVersion: 2.14-0ubuntu1
Architecture: i386
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Apr 1 13:38:29 2014
Disassembly: $4 = 0
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2014-04-01 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta i386 (20140326.1)
ProcCmdline: gnome-shell --mode=gdm
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
Registers: $9 = 0x4 <error: Cannot access memory at address 0x4>
SegvAnalysis: Failure: invalid literal for int() with base 16: '='
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:

ThreadStacktrace: No symbol "__nih_abort_msg" in current context.
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 poll () at ../sysdeps/unix/syscall-template.S:81
 poll (__timeout=14, __nfds=12, __fds=0xab0bb08) at /usr/include/i386-linux-gnu/bits/poll2.h:46
 g_poll (fds=fds@entry=0xab0bb08, nfds=nfds@entry=12, timeout=timeout@entry=14) at /build/buildd/glib2.0-2.40.0/./glib/gpoll.c:124
 g_main_context_poll (priority=2147483647, n_fds=12, fds=0xab0bb08, timeout=14, context=0x9b6eb98) at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:4028
 g_main_context_iterate (context=0x9b6eb98, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:3729

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: gnome-shell crash with SIGSEGV on the first login after boot; ok after restarting gdm.

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Grayson Peddie (e-admin-f) wrote :

I'm using amd64 version of Ubuntu GNOME 14.04. I don't know if SegvAnalysis is the same as mine and I tried to report it but apport tells me that I have obsolete packages which I don't think it has something to do with GNOME Shell. Either way, filing a bug report will probably be marked as duplicate to yours.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

The exact fault position is unfortunately really not significant, given that to reach an usable interface you have to kill the xserver and the shell with it...

Trying now to update (big bunch of them, April 3 2014 now) and to report back. I hope that some UbuntuGnome developer is listening here, I will try to help and can test thing (in my VM) if requested.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

I updated the system now (2014-04-04 9:00 MST DST) and it seems fixed --- I could login at the first attempt. Kudos!

Grayson, could you check if this solved the problem to you too?

Revision history for this message
Grayson Peddie (e-admin-f) wrote :

I think what I have forgotten to mention is that the crash seems to be random, so I may have to remove "it affects me" even though the bug report appears to be very similar to mine, but apport stopped me from reporting the bug since it told me I have packages that need to be upgraded, so maybe I might get another random SIGSEGV (signal 11) maybe another time in the future; it didn't happen during login, so, my bad for not reading your comment above the apport-generated report. But if mine occurred similar to your apport-generated report, then I will probably mark it as "it affects me."

Revision history for this message
CarbonPepper (carbonpepper) wrote :

I'm also testing Ubuntu 14.04 64 bit on a VM.

I'm getting this exact bug and it's not random, it's repeatable for me.
It's present on the 3.10 from the Ubuntu repos and the 3.12 from ppa:gnome3-team/gnome3

I have not seen it happen on 32 bit installs.

Changed in gnome-shell:
importance: Unknown → Critical
status: Unknown → New
summary: - gnome-shell crash with SIGSEGV on the first login after boot; ok after
- restarting gdm.
+ gnome-shell crashed with SIGSEGV in poll() from poll() from g_poll()
+ from g_main_context_poll()
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017

https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

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

Ubuntu 14.04 reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm

Changed in gnome-shell (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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