This has been fixed in Precise (if not earlier): libsane depends on libsane-common, which now provides html/sane-mfgs.html.
jani@saegusa:~$ dlocate sane-mfgs.html
libsane-common: /usr/share/doc/libsane/html/sane-mfgs.html
jani@saegusa:~$ LC_ALL=C apt-cache depends libsane | grep libsane
libsane
Depends: libsane-common
libsane-common:i386
Suggests: libsane-extras
Replaces: libsane-extras
Replaces: libsane-extras:i386
Replaces: libsane:i386
Breaks: libsane:i386
This also concerns libsane 1.0.22-7ubuntu1 here. I don’t think this is Bug #904853, as I’ve not installed these packages manually, although I can’t vouch if –force-acrchitecture is used automatically by some upgrades.
Confirming this in up-to-date Precise.
The two dialogs are very, very inconsistent: the dialog icon they use (DIALOG_QUESTION in one, the DIALOG_ERROR in the other), the dialog window title (”Application problem” vs. none), the dialog title and explanation style (brief vs. verbose), the ignore option missing from one… It’s almost as if the engineers behind the two dialogs have intentionally tried to make them as different from one another as possible. (No offence intended, I just think it’s funny although it is a genuine accessibility problem as well.) Also, one dialog seems to be minimizable whereas the other is not — though this doesn’t appear in Blair’s screenshot; it may be something introduced in Precise which the system my screenshot is from is running.
Can also be triggered by closing the dialog with mouse using the (x) button.
I tested this in a VM I upgraded from 10.04 all the way up to 11.10, and up until Natty the unlocking dialog still used the correct login@hostname under my full name. In Oneiric, and in Precise which I’m running on the host, it says Linux@Linux instead.
I’ll attach screenshots of the unlocking dialog in 11.04 and 11.10 below.
Hi Marcel. You’re absolutely right: it’s the .bashrc alias that caused this. Such a simple yet elusive solution, my compliments for catching it! :)
Here’s the steps I can currently reproduce this with on my system:
0. Have Gdebi associated with .debs
1. Download http://launchpadlibrarian.net/89242455/linux-generic_3.2.0.8.8_i386.deb in Chromium
2. Click the downloaded file in Chromium’s downloads bar to open it in Gdebi
This results in Gdebi launching and the crash triggering. If I then close Gdebi, it triggers the same crash again (apport points me to this report in both instances).
(I have yet to install the upgrades from this weekend. If any of those change this, I’ll report back.)
Happens at least daily. Nothing I do in particular to pinpoint as the trigger. Now that the crash has occurred, the lens doesn’t seem to work (clicking the files it shows does nothing). I’ll try it again on another session prior to the SIGSEGV happening.
This is a terse report, I know, but I’ll provide any additional info anyone might care to ask for if needed.
Jason: As with Davide, it was indicator-power that was missing here. The greeter log didn’t show that though, it claimed libdatetime.so was missing even though indicator-datetime is in fact installed.
