Description of problem: xsane --sync Gtk-Message: Failed to load module "canberra-gtk-module" Xlib: extension "RANDR" missing on display ":0". The program 'xsane' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 51810 error_code 8 request_code 157 minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Version-Release number of selected component (if applicable): How reproducible: Start xsane with --sync as instructed after first crash Steps to Reproduce: 1.run xsane (with -sync for reasonable error message) 2.crashes 3.file bug report System is updated as of ~10 minutes ago, clean reboot, had same issue before updates and new kernel etc, just updated in case it was already fixed.
xsane-0.998-2.mga2
CC: (none) => hhielscher
Hi, thanks for reporting this bug. Assigned to the package maintainer.
Keywords: (none) => TriagedCC: (none) => stormiAssignee: bugsquad => supp
This still seems to be valid in Mageia 3.
Version: 2 => 3Whiteboard: (none) => MGA2TOO
xsane doesn't crash here, must be either related to driver/hardware issues, or maybe to a missing dependency
Just had an opportunity to do a fresh reinstall after my /home and / drive started having (recoverable) thermal errors. xsane and xsane-gimp still crash reliably as described. May have something to do with the HP Photosmart C4780 all in one? (or the outdated hplip in MGA3) he scanner works fine using the (cmd line) hp utility or simple scan.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD