bamfdaemon crashed with SIGSEGV in gdk_display_get_event()

Bug #862076 reported by Gopal
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bamf (Ubuntu)
New
Undecided
Unassigned

Bug Description

my system went to sleep mode as i didnt connect to the power. when i started the system (back from sleep and not restart). the bamfdaemon crashed. Compiz is also acting wierd. when i press alt+tab, too many programs are shown in compiz screen even though i have only few applications opened.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bamfdaemon 0.2.104-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Thu Sep 29 12:21:37 2011
ExecutablePath: /usr/lib/bamf/bamfdaemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/bamf/bamfdaemon
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_IN:en
 LANG=en_IN
SegvAnalysis:
 Segfault happened at: 0x738dee: mov 0x8(%esi),%ebp
 PC (0x00738dee) ok
 source "0x8(%esi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%ebp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: bamf
StacktraceTop:
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 gdk_display_get_event () from /usr/lib/libgdk-3.so.0
Title: bamfdaemon crashed with SIGSEGV in gdk_display_get_event()
UpgradeStatus: Upgraded to oneiric on 2011-09-29 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Gopal (gopal-mailme) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #814826, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-i386-retrace
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.