bamfdaemon crashed with SIGSEGV in sn_xcb_display_new()

Bug #836866 reported by pello on 2011-08-29
64
This bug affects 12 people
Affects Status Importance Assigned to Milestone
BAMF
Critical
Unassigned
Unity
Invalid
Critical
Unassigned
bamf (Ubuntu)
Medium
Unassigned
notify-osd (Ubuntu)
Undecided
Unassigned
startup-notification (Ubuntu)
Undecided
Unassigned

Bug Description

crash at the system start.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bamfdaemon 0.2.96-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic-pae 3.0.3
Uname: Linux 3.0.0-9-generic-pae i686
Architecture: i386
Date: Sun Aug 28 23:13:43 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/bamf/bamfdaemon
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/bamf/bamfdaemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=fr_FR:fr:en_GB:en
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6ae554c <sn_xcb_display_new+380>: mov 0x8(%eax),%edx
 PC (0xb6ae554c) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: bamf
StacktraceTop:
 sn_xcb_display_new () from /usr/lib/libstartup-notification-1.so.0
 sn_display_new () from /usr/lib/libstartup-notification-1.so.0
 wnck_screen_get () from /usr/lib/libwnck-3.so.0
 wnck_screen_get_default () from /usr/lib/libwnck-3.so.0
 bamf_legacy_screen_get_default ()
Title: bamfdaemon crashed with SIGSEGV in sn_xcb_display_new()
UpgradeStatus: Upgraded to oneiric on 2011-08-28 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

pello (fropert) wrote :

StacktraceTop:
 sn_xcb_display_new () from /tmp/tmpqH2elf/usr/lib/libstartup-notification-1.so.0
 sn_display_new () from /tmp/tmpqH2elf/usr/lib/libstartup-notification-1.so.0
 wnck_screen_construct (number=0, screen=<optimized out>, display=0x9dce248) at screen.c:591
 wnck_screen_get (index=0) at screen.c:648
 wnck_screen_get_default () at screen.c:685

Changed in bamf (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Neil J. Patel (njpatel) on 2011-09-13
visibility: private → public
Changed in bamf:
assignee: nobody → Neil J. Patel (njpatel)
importance: Undecided → Critical
status: New → Fix Committed
Changed in unity:
assignee: nobody → Neil J. Patel (njpatel)
importance: Undecided → Critical
milestone: none → 4.16.0
status: New → Fix Committed
assignee: Neil J. Patel (njpatel) → nobody
status: Fix Committed → New
Changed in bamf:
assignee: Neil J. Patel (njpatel) → nobody
status: Fix Committed → New
Neil J. Patel (njpatel) wrote :

This patch should protect against NULL values being returned by xcb_intern_atom_reply. It won't stop the cause of that, but should stop the crash.

Changed in bamf (Ubuntu):
status: New → Confirmed
Neil J. Patel (njpatel) on 2011-09-13
Changed in bamf:
status: New → Invalid
Changed in notify-osd:
status: New → Invalid
Changed in unity:
status: New → Invalid
Changed in bamf (Ubuntu):
status: Confirmed → Invalid

The attachment "fix_836866.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Launchpad Janitor (janitor) wrote :

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

Changed in startup-notification (Ubuntu):
status: New → Confirmed
affects: notify-osd → notify-osd (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers