colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed.

StacktraceTop:
 __assert_fail_base (fmt=0x7fcda3d688b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fcd926f9fb0 "s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", file=file@entry=0x7fcd926f9ee8 "simple-watch.c", line=line@entry=454, function=function@entry=0x7fcd926fa140 "avahi_simple_poll_prepare") at assert.c:92
 __GI___assert_fail (assertion=0x7fcd926f9fb0 "s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", file=0x7fcd926f9ee8 "simple-watch.c", line=454, function=0x7fcd926fa140 "avahi_simple_poll_prepare") at assert.c:101
 avahi_simple_poll_prepare () from /tmp/apport_sandbox_6pKceT/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
 avahi_simple_poll_iterate () from /tmp/apport_sandbox_6pKceT/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
 kodak_network_discovery (host=0x0) at kodakaio.c:2339

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

I got this after upgrade to vivid

Fresh install a couple of days ago. This error appeared after a "cold boot" after the machine was off and after updates were installed. Nothing more to add.

Singtoh

seems an issue with libsane-kodakaio.so.1

Got this in 15.04. Also at times get the avahi disabled .local warning if they may be related.

15.04 confirm

15.04 confirm, only after first boot.

Does this affect anyone on 15.10?

yes, it does.

@lah Same here.

Is this ever going to be fixed? I'm on 15.04. Annoying to see this every time I log in.

I have same proglem in Ubuntu Gnome 15.04.

I'm having the same problem, I'd be more than happy to help but I don't know where to start if anyone could point me to the right direction that would be great.

Thanks

Any sane developers following this? It's very annoying to see the crash notification on every boot.

Ditto on Ville Ranki's question. Not an Earth-shattering problem, but annoying nonetheless.

After update today sep 27 2015 I start to have the same problem, I have this problem on 3 ubuntu version from 2011. May be somebody try to remove this useless program from default installation? please! please!, 4 years you cant fix it, may be simple remove it and stop this hard sex with colord sane ) Thx developers this program! may be this gays start to working on ms windows? - linux is not right OS for this gays )

15.04 steel active bug!

15.10 latest daily.
still bores me every time computers starts, ouch!
pls fix it somehow, cause I can deal only with html

I've had this for what seems like ages now. The apport dialog has an "Ignore future problems of this type" which works but is apparently reset by system updates, which is pretty frequently. :-(

15.04 on every boot appears.

I have experienced this bug as long as I can remember, years anyway. My hardware has changed completely during that time, but the bug stays :-)

I haven't let send the automatic bug report often, because I have thought that sending too many of them annoys the developers. Would it be better to send them all, or perhaps one every week or couple so that the developers know that the bug still exists ?

I'm using 15.10 now, and currently the crash happens at every boot.

The same bug on Ubuntu 15.10
I send data about this bug
I think It could be because of the f.lux. It not works on Ubuntu 15.10 and i changed code to force it work
f.lux make screen not so bright
maybe it could help u guys

After upgrading to 15.10 I get this error every day when I start up.

I don't really use scanner, so I decided to simply remove buggy packages:

sudo apt-get remove sane-utils
sudo apt-get remove colord

Thank you Taras for the instructions! Finally got rid of this crash after 1 year.

In Ubutnu Software center I remove the installed "Simple Scan" application
then removed the packages

 sudo apt-get remove sane-utils
 sudo apt-get remove colord
 sudo apt-get autoremove

Problem gone, finally no crashes any more!

Had the same problem, and decided to go with Taras suggestion. Works like a charm, no more crashes. Thanks!

Still happens on Ubuntu 16.04.

Same issue here on Ubuntu 15.10 64-bit, and also the Avahi disabled .local warning mentioned in reply #10. Hope this gets resolved soon...

As share above, on Ubuntu 15.10 I got the crash every day, that is very annoying

The bug is still present on 16.04 beta build 1.

Same bug on 16.04 daily build 20160406.
Log file attached in /var/crash/

Got it on 16.04 LTS final release as well.
Followed earlier instructions to remove colord, so it is really does not bother me, but might spoil the impression of newcomers

I have this bug on final version 16.04 LTS (i386) after cold restart every time!

I have a fresh install for Ubuntu 16.04, updated, and same issue.

After read the peterK (peter-kanderholm) post wrote on 2016-01-08, I couldn't accept it, I do use regular basis a scanner...

Then per the bug reported I did remember the "Color" and "Color Profile Viewer", entered there and almost immediately was recommended to install Gnome Color Manager, accepted.

Then twice reboot no bug, no more crashes.

I do remember this come after I did plug a second monitor to my laptop, could this be a coincidence?

Regards!

I tried installing Gnome Color Manager as well, and while colord no longer seems to crash on every boot, it still sometimes crashes after waking from suspend on the same failed assertion.

I have this bug on final version 16.04 LTS (x64) after every starting !
It occured after upgrading to 16.04 from 15.10. Please give a solution ！ Too annoy ！!

Yep, installing gnome-color-manager helps. Thanks, Sarraceno!

I installed gnome-color-manager. It does not work completely. Error appears periodically on Ubuntu 16.04.1 LTS.

Ubuntu 16.04.1 LTS: colord-sane always crashes. Installed gnome-color-manager today. Let's see what happens next...

Problem stays unsolved.

The problem has disappeared after I have plugged back my scanner (Mustek BearPaw 1200 TA)

End March install 16.04.2. First boot... not all boots... few reboots.

Ubuntu 16.10 has the same bug

This bug was fixed in the package sane-backends - 1.0.25+git20150528-1ubuntu4

---------------
sane-backends (1.0.25+git20150528-1ubuntu4) zesty; urgency=medium

  * debian/patches/kodak_avahi_crash.patch:
    - Fix crash when Avahi fails scanning for Kodak scanners (LP: #1351286)

 -- Robert Ancell <email address hidden> Tue, 04 Apr 2017 11:56:59 +1200

There's a whole bunch of these in the Error Tracker so that'll be a useful data point when verifying the fix. Although, you'd need to dig into the Dependencies to find the sane-backends version.

https://errors.ubuntu.com/bucket/?id=/usr/lib/colord/colord-sane%3Acolord-sane%3A%20simple-watch.c%3A454%3A%20avahi_simple_poll_prepare%3A%20Assertion%20%60s-%3Estate%20%3D%3D%20STATE_INIT%20%7C%7C%20s-%3Estate%20%3D%3D%20STATE_DISPATCHED%20%7C%7C%20s-%3Estate%20%3D%3D%20STATE_FAILURE%27%20failed.

Hello Fred, or anyone else affected,

Accepted sane-backends into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sane-backends/1.0.25+git20150528-1ubuntu2.16.10.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Fred, or anyone else affected,

Accepted sane-backends into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sane-backends/1.0.25+git20150528-1ubuntu2.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Crash reports on errors.ubuntu.com:
https://errors.ubuntu.com/problem/8b9ed48be6c32a738c54fc1fc36cccf2058be60b

I couldn't find any reports with crashes using the updated libsane, but this was just a random selection. I don't know of a method to get all these reports easily and check the libsane dependency?

The small number of 17.04 reports gives me hope this is really fixed...

As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.

Thank you!

Please verify for Xenial.

I have this Problem on ubuntu 16.04 after i am update my ubuntu.

I see someone marked this bug as verified but did not provide any testing summary. Remember that it is required to put at least an overview of what tests have been performed and on which package versions for the SRU team to consider a bug as verified.

Could you please provide the necessary information? We cannot release it otherwise. Thank you.

The fix for this bug has been awaiting testing feedback in the -proposed repository for xenial for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository.

This bug seems to be fixed in Xenial proposed package. My system reported about saned crashes (caused by assertion failure described in this bug) on every boot. Then I installed updated package and I do not observe any sane related crashes anymore.

The version of sane-backends in the proposed pocket of Xenial that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.