[lucid] gdm-session-worker segfault

Bug #552606 reported by Sergey K
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gdm

gdm-session-worker segfault if i'm plug/unplug any usb device like usb bluetooth dongle, usb flash drive, ...

dmesg:
[ 359.916395] usb-storage: device found at 15
[ 359.916398] usb-storage: waiting for device to settle before scanning
[ 364.924472] usb-storage: device scan complete
[ 364.925420] scsi 7:0:0:0: Direct-Access HTS42128 0H9AT00 A70G PQ: 0 ANSI: 2 CCS
[ 364.927798] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 364.938501] gdm-session-wor[3197]: segfault at 11 ip 00000011 sp bfc39f8c error 4 in libdbus-glib-1.so.2.1.0[110000+1c000]
[ 364.975549] sd 7:0:0:0: [sdc] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
[ 364.978725] sd 7:0:0:0: [sdc] Write Protect is off
[ 364.978730] sd 7:0:0:0: [sdc] Mode Sense: 00 38 00 00
[ 364.978733] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 364.985548] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 364.985555] sdc: sdc1
[ 365.019026] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 365.019103] sd 7:0:0:0: [sdc] Attached SCSI disk
[ 386.504389] usb 1-4.3: new full speed USB device using ehci_hcd and address 16
[ 386.619793] usb 1-4.3: configuration #1 chosen from 1 choice
[ 386.643303] gdm-session-wor[3440]: segfault at 11 ip 00000011 sp bf8d809c error 4
[ 526.956972] gdm-session-wor[3712]: segfault at 11 ip 00000011 sp bff17d7c error 4 in librt-2.11.1.so[110000+7000]

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gdm 2.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
Date: Wed Mar 31 19:19:46 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
SourcePackage: gdm

Revision history for this message
Sergey K (koblin) wrote :
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gdm (Ubuntu):
status: New → 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.