colord assert failure: colord: browser.c:701: avahi_service_browser_free: Assertion `*_head == _item' failed.

Bug #831867 reported by Patrick McEvoy
This bug affects 136 people
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
Fix Released
High
Chris Halse Rogers
Oneiric
Fix Released
High
Chris Halse Rogers

Bug Description

Crashes after login in gnome-shell on oneiric

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: colord 0.1.11-1
ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
AssertionMessage: colord: browser.c:701: avahi_service_browser_free: Assertion `*_head == _item' failed.
Date: Tue Aug 23 10:23:05 2011
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord
ProcEnviron:

Signal: 6
SourcePackage: colord
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 avahi_service_browser_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 ?? () from /usr/lib/sane/libsane-net.so.1
Title: colord assert failure: colord: browser.c:701: avahi_service_browser_free: Assertion `*_head == _item' failed.
UpgradeStatus: Upgraded to oneiric on 2011-08-10 (13 days ago)
UserGroups:

Revision history for this message
Patrick McEvoy (patrickmcevoy) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___assert_fail (assertion=0x7f85c691378c "*_head == _item", file=<optimized out>, line=701, function=<optimized out>) at assert.c:81
 avahi_service_browser_free () from /tmp/tmp2HrKOY/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 net_avahi_callback (c=0x2623740, state=<optimized out>, userdata=<optimized out>) at net.c:854
 ?? () from /tmp/tmp2HrKOY/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 ?? () from /tmp/tmp2HrKOY/usr/lib/x86_64-linux-gnu/libavahi-client.so.3

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in colord (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in colord (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
visibility: private → public
Changed in colord (Ubuntu Oneiric):
importance: Medium → High
tags: added: rls-mgr-o-tracking
Revision history for this message
Michael Tinsay (tinsami1) wrote :

I ran into this problem when I disabled avahi-daemon. I reenabled avahi-daemon and rebooted, it seemed to not happen again. "apt-cache show colord" doesn't state that it depends on avahi-daemon, directly that is; I haven't walked through the dependencies.

Revision history for this message
Extender (msveshnikov) wrote :

Seems that bug is visible only when avahi daemon is disabled. It disabled for me in default install since my ISP has .local domain.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

If it's Avahi, indeed the .local domain problem is bug #327362. Colord should really cope with it though, since the bug #327362 affects millions of potential Ubuntu users at minimum (based on the couple of operators known).

Changed in colord (Ubuntu Oneiric):
assignee: nobody → Chris Halse Rogers (raof)
Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

Where to look if I have avahi disabled and how to detect if my network has .local domain?

A week ago I was connecting to a hotel WiFI network and got notification about avahi daemon being disabled because of that .local domain. While I never saw this happening on the network I'm on now, is it possible that avahi was disabled persistently?

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

Oh and I forgot to note that almost at the same time as this crash I had another one: https://bugs.launchpad.net/ubuntu/+source/oneconf/+bug/851603

Could these two be caused by a general connectivity problem?

Revision history for this message
Alessandro Losavio (alo21) wrote :

I have the same problem in Ubuntu 11.10 amd64

Changed in colord (Ubuntu Oneiric):
status: Confirmed → In Progress
Revision history for this message
Chris Halse Rogers (raof) wrote :

Ok. After a little yak shaving I think this is actually a sane-backends problem - it seems to be freeing an avahi_client before the avahi_browser that depends on it.

I can't seem to easily reproduce this bug, though. I'll come back to it in the morning and try the patch.

affects: colord (Ubuntu Oneiric) → sane-backends (Ubuntu Oneiric)
tags: removed: bugpattern-needed
tags: added: bugpattern-written
Changed in sane-backends (Ubuntu Oneiric):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sane-backends - 1.0.22-2ubuntu2

---------------
sane-backends (1.0.22-2ubuntu2) oneiric; urgency=low

  * debian/patches/fix_avahi_error_paths.patch:
    - Fix free order of avahi_client and avahi_browser in failure path.
      Fixes assert when avahi is unavailable (LP: #831867)
 -- Christopher James Halse Rogers <email address hidden> Wed, 21 Sep 2011 16:39:32 +1000

Changed in sane-backends (Ubuntu Oneiric):
status: Fix Committed → 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.