xsane crashes openSUSE 12.1 64 bit

Xsane crashed shortly after executing. It works fine on the 32 bit version.

On 2012-03-20 03:06, Parthenolide wrote:
>
> Xsane crashed shortly after executing. It works fine on the 32 bit
> version.

And…? :slight_smile:

Sorry, do you expect something from us? You have to say more.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 20/03/12 02:06, Parthenolide wrote:
>
> Xsane crashed shortly after executing. It works fine on the 32 bit
> version.
>

Works for me on 12.1 64-bit, KDE 4.74.


Graham Davis, Bracknell, Berks.
openSUSE 12.2 M2 (64-bit); KDE 4.8.1; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306

Works great for me on three different HP all-in-one devices. I’m running OpenSUSE 12.1 (x86_64) and KDE 4.7.2 Release 5. No problems, no crashes.

FYI,

Gordon

Works fine here too on 32 and 64 bit, fresh install up to upgrading to kde 4.8.1/openSUSE 12.1
The only occasion xsane failed to load when I fire it and forgot to turn on the scanner.

Yep xsane and skanlite doesn’t have the ability to wake up the off network scanner here
but simple scan does.

Check your xsane log entries in /var/log/messages and see if that tells you anything.

Here is the error message:

Mar 20 08:06:41 linux-fgl7 dbus[1451]: [system] Activating service name=‘org.freedesktop.PackageKit’ (using servicehelper)
Mar 20 08:06:41 linux-fgl7 dbus-daemon[1451]: dbus[1451]: [system] Activating service name=‘org.freedesktop.PackageKit’ (using servicehelper)
Mar 20 08:06:41 linux-fgl7 dbus-daemon[1451]: (packagekitd:22449): PackageKit-Zypp-DEBUG: zypp_backend_initialize
Mar 20 08:06:41 linux-fgl7 dbus[1451]: [system] Successfully activated service ‘org.freedesktop.PackageKit’
Mar 20 08:06:41 linux-fgl7 dbus-daemon[1451]: dbus[1451]: [system] Successfully activated service ‘org.freedesktop.PackageKit’
Mar 20 08:07:01 linux-fgl7 dbus-daemon[1451]: (packagekitd:22449): PackageKit-Zypp-DEBUG: zypp_backend_destroy
Mar 20 08:07:15 linux-fgl7 kernel: [70674.920543] Did not find alt setting 1 for intf 0, config 1
Mar 20 08:07:15 linux-fgl7 kernel: [70674.920786] Did not find alt setting 1 for intf 0, config 1
Mar 20 08:07:18 linux-fgl7 xsane: io/hpmud/hpmud.c 341: device_cleanup: device uri=hp:/usb/Officejet_4500_G510n-z?serial=CN05VH808J05HR
Mar 20 08:07:18 linux-fgl7 xsane: io/hpmud/hpmud.c 353: device_cleanup: close device dd=1…
Mar 20 08:07:18 linux-fgl7 xsane: io/hpmud/hpmud.c 355: device_cleanup: done closing device dd=1

Here is the error message:

Mar 20 08:06:41 linux-fgl7 dbus[1451]: [system] Activating service name=‘org.freedesktop.PackageKit’ (using servicehelper)
Mar 20 08:06:41 linux-fgl7 dbus-daemon[1451]: dbus[1451]: [system] Activating service name=‘org.freedesktop.PackageKit’ (using servicehelper)
Mar 20 08:06:41 linux-fgl7 dbus-daemon[1451]: (packagekitd:22449): PackageKit-Zypp-DEBUG: zypp_backend_initialize
Mar 20 08:06:41 linux-fgl7 dbus[1451]: [system] Successfully activated service ‘org.freedesktop.PackageKit’
Mar 20 08:06:41 linux-fgl7 dbus-daemon[1451]: dbus[1451]: [system] Successfully activated service ‘org.freedesktop.PackageKit’
Mar 20 08:07:01 linux-fgl7 dbus-daemon[1451]: (packagekitd:22449): PackageKit-Zypp-DEBUG: zypp_backend_destroy
Mar 20 08:07:15 linux-fgl7 kernel: [70674.920543] Did not find alt setting 1 for intf 0, config 1
Mar 20 08:07:15 linux-fgl7 kernel: [70674.920786] Did not find alt setting 1 for intf 0, config 1
Mar 20 08:07:18 linux-fgl7 xsane: io/hpmud/hpmud.c 341: device_cleanup: device uri=hp:/usb/Officejet_4500_G510n-z?serial=CN05VH808J05HR
Mar 20 08:07:18 linux-fgl7 xsane: io/hpmud/hpmud.c 353: device_cleanup: close device dd=1…
Mar 20 08:07:18 linux-fgl7 xsane: io/hpmud/hpmud.c 355: device_cleanup: done closing device dd=1

Only the last three entries are xsane log entries and they don’t tell me anything. You may want to try reinstalling the printer/scanner drivers with YaST2 or CUPS. Alternatively, you could try uninstalling/reinstalling xsane. Otherwise, I’m not sure what to recommend.

Do you know the history to this? I wonder whether you have any underlying library (package) conflicts causing this. Have a look at your configured repos. Perhaps worth checking with

zypper ve

for any anomalies.