notify-osd (alsdorf) crashed with signal 5 in main()

Bug #331150 reported by Daniel Holbach on 2009-02-18
68
This bug affects 8 people
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)
Medium
Mirco Müller

Bug Description

Binary package hint: alsdorf

No idea what happened - just rebooted and logged into the session - first start of alsdorf.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/alsdorf/alsdorf
Package: alsdorf 0.8-0ubuntu1
ProcCmdline: /usr/lib/alsdorf/alsdorf
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=de_DE.UTF-8
Signal: 5
SourcePackage: alsdorf
Stacktrace:
 #0 0xb78a6b0f in g_logv () from /usr/lib/libglib-2.0.so.0
 #1 0xb78a6e96 in g_log () from /usr/lib/libglib-2.0.so.0
 #2 0x0805ad1c in main ()
StacktraceTop: main ()
ThreadStacktrace:
 .
 Thread 1 (process 28392):
 #0 0xb78a6b0f in g_logv () from /usr/lib/libglib-2.0.so.0
 #1 0xb78a6e96 in g_log () from /usr/lib/libglib-2.0.so.0
 #2 0x0805ad1c in main ()
Title: alsdorf crashed with signal 5 in main()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Daniel Holbach (dholbach) wrote :

StacktraceTop:main (argc=) at main.c:69

Changed in alsdorf:
importance: Undecided → Medium

this is an assertion crash here:

        connection = dbus_create_service_instance (DBUS_NAME);
        if (connection == NULL)
        {
                g_error ("Could not register instance");
        }

usually meaning that there is another instance already running. We could exit cleanly here, or wait a while retrying to RequestName before giving up.

Changed in alsdorf:
status: New → Triaged
Alexander Sack (asac) wrote :

resassigning alsdorf bugs.

Alexander Sack (asac) on 2009-02-19
Changed in notify-osd:
assignee: nobody → macslow
David Barth (dbarth) on 2009-03-14
Changed in notify-osd:
assignee: nobody → macslow
importance: Undecided → Medium
status: New → Triaged
Pedro Villavicencio (pedro) wrote :

just got the same while using pidgin.

Do not use the alsdorf code anymore. The latest version of the code is
in the public notify-osd version. If an automatic upgrade did not
triggered the change, then please manually remove 'alsdorf' and install
'notify-osd' instead. Thanks

David Barth (dbarth) wrote :

Pushing that to high

Changed in notify-osd:
importance: Medium → High
Mirco Müller (macslow) on 2009-03-18
Changed in notify-osd (Ubuntu):
status: Triaged → Fix Committed
Changed in notify-osd:
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package notify-osd - 0.9.6-0ubuntu1

---------------
notify-osd (0.9.6-0ubuntu1) jaunty; urgency=low

  * New upstream release 0.9.6:
    - Detect screensaver inhibition for do-not-disturb mode.
    - Add compatibility checks to ease transition period for applications to
      pick up the capability and hint name changes. (LP: #343553)
    - Correctly exit if registering on DBus failed. (LP: #331150)
    - Fix filtering of HTML.
    - Basic accessibility support.

 -- Martin Pitt <email address hidden> Thu, 19 Mar 2009 13:39:13 +0100

Changed in notify-osd:
status: Fix Committed → Fix Released
David Barth (dbarth) on 2009-04-06
Changed in notify-osd:
status: Fix Committed → Fix Released
no longer affects: notify-osd
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers