nautilus crashed with SIGSEGV in gdk_display_get_event()

Bug #1124099 reported by cacula
54
This bug affects 12 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

0. plugged ipad in
1. mounted ipad in virtualbox
2. stoped virtualbox
3. unplugged ipad (was not accessible)
4. plugged ipad in
5. tried to access via nautilus
6. unity freezed
7. openend tty0, loged in and typed: unity --replace
8. went back to unity and apport poped up

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 13 13:57:17 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'931x1027+57+24'"
InstallationDate: Installed on 2013-02-06 (7 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130206)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc30d1bcab0: mov 0x70(%rdi),%rax
 PC (0x7fc30d1bcab0) ok
 source "0x70(%rdi)" (0x00000070) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: nautilus crashed with SIGSEGV in gdk_display_get_event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-02-06T12:51:07.984081

Revision history for this message
cacula (cacula) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed
Download full text (12.5 KiB)

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1 version 1:4.7.2-21ubuntu1 required, but 1:4.7.2-22ubuntu3 is available
libmtp-common version 1.1.5-1 required, but 1.1.5-42-g6e96316-1ubuntu1 is available
mountall version 2.47 required, but 2.48build1 is available
humanity-icon-theme version 0.6.1 required, but 0.6.2 is available
libgusb2 version 0.1.3-5 required, but 0.1.5-0ubuntu1 is available
libudisks2-0 version 2.0.1-1 required, but 2.0.92-0ubuntu2 is available
libk5crypto3 version 1.10.1+dfsg-3 required, but 1.10.1+dfsg-4 is available
libindicator3-7 version 12.10.1-0ubuntu1 required, but 12.10.2daily13.02.25-0ubuntu1 is available
dosfstools version 3.0.13-1ubuntu2 required, but 3.0.14-1ubuntu1 is available
libmtp9 version 1.1.5-1 required, but 1.1.5-42-g6e96316-1ubuntu1 is available
libudev0 version 175-0ubuntu17 required, but 175-0ubuntu19 is available
libxcb-shm0 version 1.8.1-2ubuntu1 required, but 1.8.1-2ubuntu2 is available
libnotify4 version 0.7.5-1build1 required, but 0.7.5-2 is available
libpam-runtime version 1.1.3-7ubuntu4 required, but 1.1.3-8ubuntu2 is available
outdated debug symbol package for libcap2: package version 1:2.22-1.2ubuntu2 dbgsym version 1:2.22-1ubuntu4
libpcre3 version 1:8.31-1ubuntu1 required, but 1:8.31-2 is available
python2.7 version 2.7.3-15ubuntu2 required, but 2.7.3-16ubuntu1 is available
libjack-jackd2-0 version 1.9.8~dfsg.4+20121110git67ac4440-1 required, but 1.9.9.5+20130127git15950eb1-1 is available
nautilus-data version 1:3.6.3-0ubuntu5 required, but 1:3.6.3-0ubuntu9 is available
libdbus-1-3 version 1.6.8-1ubuntu3 required, but 1.6.8-1ubuntu5 is available
ntfs-3g version 1:2012.1.15AR.5-4ubuntu3 required, but 1:2013.1.13-1+0ubuntu2 is available
libcups2 version 1.6.1-1ubuntu1 required, but 1.6.1-2 is available
libisofs6 version 1.2.4-0ubuntu1 required, but 1.2.6-0ubuntu1 is available
tzdata version 2012e-0ubuntu2 required, but 2013b-1ubuntu1 is available
python-gi version 3.7.5.1-0ubuntu1 required, but 3.7.91.1-0ubuntu1 is available
libcolord1 version 0.1.23-0ubuntu3 required, but 0.1.30-0ubuntu3 is available
gvfs-common version 1.15.3-0ubuntu1 required, but 1.15.4-0ubuntu1b1 is available
libapt-pkg4.12 version 0.9.7.7ubuntu1 required, but 0.9.7.7ubuntu3 is available
outdated debug symbol package for libprocps0: package version 1:3.3.3-2ubuntu5 dbgsym version 1:3.3.3-2ubuntu3
libicu48 version 4.8.1.1-10 required, but 4.8.1.1-10ubuntu1 is available
nautilus version 1:3.6.3-0ubuntu5 required, but 1:3.6.3-0ubuntu9 is available
python-xdg version 0.25-1ubuntu1 required, but 0.25-2 is available
libgl1-mesa-glx version 9.0.2-0ubuntu1 required, but 9.0.3-0ubuntu1 is available
liborc-0.4-0 version 1:0.4.16-2 required, but 1:0.4.17-1 is available
libplymouth2 version 0.8.8-0ubuntu5 required, but 0.8.8-0ubuntu6 is available
libgtk2.0-common version 2.24.14-0ubuntu1 required, but 2.24.16-1ubuntu2 is available
libsecret-1-0 version 0.13-0ubuntu1 required, but 0.14-0ubuntu1 ...

tags: removed: need-amd64-retrace
Revision history for this message
Christopher Townsend (townsend) wrote :

Changing this back to confirmed since it appears that a few folks are being affected by this.

Changed in nautilus (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug didn't get activity/new duplicates for some years and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
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.