update-notifier crashed with SIGSEGV in XGrabServer()

Bug #317745 reported by 787B
102
This bug affects 7 people
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: update-notifier

I don't know if this is a dupe of a similar bug that had a SIGSEGV in a different call. This crash happened on two boots. on a Compaq Evo N400c.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/update-notifier
Package: update-notifier 0.75.6
ProcCmdline: update-notifier --sm-config-prefix /update-notifier-IzWyWz/ --sm-client-id 117f000101000119638720700000050540004 --screen 0
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: update-notifier
Stacktrace:
 #0 0xb721e216 in XGrabServer () from /usr/lib/libX11.so.6
 #1 0x0804cb72 in ?? ()
 #2 0x0804c533 in ?? ()
 #3 0xb7303775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #4 0x0804c071 in ?? ()
StacktraceTop:
 XGrabServer () from /usr/lib/libX11.so.6
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: update-notifier crashed with SIGSEGV in XGrabServer()
Uname: Linux 2.6.28-4-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash

Related branches

Revision history for this message
787B (787b) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:up_get_clipboard () at clipboard.c:53
main (argc=7, argv=0xbffd2c44) at update-notifier.c:452

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in update-notifier:
importance: Undecided → Medium
Revision history for this message
787B (787b) wrote :

With the update released on January 19 or 20, update-notifier starts on login and doesn't crash. Nice work!

Changed in update-notifier:
status: New → Fix Released
Revision history for this message
Arnaud Faucher (arnaud-faucher) wrote :

This bug happens again on Karmic (see LP: #397981 for traces).

Changed in update-notifier (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Arnaud Faucher (arnaud-faucher) wrote :

This bug happens when the program checks if it is not already running. This is done through a X clipboard hack, which fails for some reason (GDK_DISPLAY() returns NULL at line 53 of src/clipboard.c).

Why not use libunique for this purpose ?

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-notifier - 0.86

---------------
update-notifier (0.86) karmic; urgency=low

  [ Sebastien Bacher ]
  * debian/rules:
    - build using --as-needed to reduce the depends

  [ Dustin Kirkland ]
  * debian/update-notifier-common.dirs: update-notifier-common
    needs /etc/update-motd.d, rather than /etc/update-motd.d/hourly;
    causes this directory to *not* be removed on update-motd package
    removal/upgrade

  [ Michael Vogt ]
  * src/update-notifier.c:
    - if display can not be opened, show a propper error message
      and do not crash (LP: #317745)
  * src/apt_check.py:
    - count security updates correctly even when they are "shadowed"
      by a regular update (LP: #394958)
    - fix typo (thanks to Hew McLachlan)
  * data/update-motd-updates-available, debian/99update-notifier:
    - move updates available from /var/run to /var/lib/update-notifier
      to make it persistent over reboots
  * src/update-notifier.c:
    - make the timeout for no-activity from apt bigger (LP: #274001)
  * data/update-notifier.desktop.in:
    - better description for the auto startup (LP: #146918)
  * src/update-notifier.c:
    - use GAppInfo/GAppLaunchContext to provide startup notification
      support (LP: #46258)

 -- Michael Vogt <email address hidden> Tue, 14 Jul 2009 16:50:46 +0200

Changed in update-notifier (Ubuntu):
status: Confirmed → Fix Released
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.