Ubuntu
xsane package

The program 'xsane' received an X Window System error.

Bug #446373 reported by Pete Graner on 2009-10-08

This bug affects 16 people

Affects		Status	Importance	Assigned to	Milestone
	xsane (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Binary package hint: xsane

When trying to scan a document, I will get the scanning devices box, then the device selection window will pop up. When I select the proper scanner and click Ok, I get the following error in the term, the xsane windows will pop up for a split second then disappear.

pgraner@desktop:~$ xsane
WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect

(xsane:20293): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

(xsane:20293): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
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 20082 error_code 8 request_code 151 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.)

ProblemType: Bug
Architecture: amd64
Date: Thu Oct 8 10:30:56 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: xsane 0.996-2ubuntu1
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
SourcePackage: xsane
Uname: Linux 2.6.31-12-generic x86_64

Tags:

Revision history for this message

Pete Graner (pgraner) wrote on 2009-10-08:

Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (5.4 KiB, text/plain; charset="utf-8")

summary:

- 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 38901 error_code 8
- request_code 151 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.)
+ The program 'xsane' received an X Window System error.

Revision history for this message

Rick Spencer (rick-rickspencer3) wrote on 2009-10-08:

I have no scanner attached atm. I get the same gtk warnings, but then xsane comes up as normal.

Changed in xsane (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Bernd Schubert (aakef) wrote on 2009-10-27:

I get the same and the preview window doesn't work. Usually I could 'fix' the preview issue by deleting $HOME/.gtk*, but no there are already now .gtk* files and I run into it again :(

Revision history for this message

Justin Mazzola Paluska (jmp-mit) wrote on 2009-11-02:

xsane --sync run in gdb Edit (20.1 KiB, text/plain)

I'm running into the same problem and I ran "xsane --sync" in gdb and got a backtrace on the X error (see the attached xsane.gdb). Unfortunately, there don't seem to be any dbg packages for xsane in the repository, so I don't have useful symbols. Is there an easy way to get symbols?

Revision history for this message

Catscrash (catscrash) wrote on 2009-11-04:

same here, everytime i want to scan something...
it starts scanning and just after it got finished xsane crashes

64bit here too.

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2009-11-04:

Thank you for the backtrace. However, it is missing some important symbols. Could you please try again with libx11-6-dbg installed, and also obtain the backtrace with "bt full" rather than "bt".

Thanks

Changed in xsane (Ubuntu):
status:	New → Incomplete

Revision history for this message

Justin Mazzola Paluska (jmp-mit) wrote on 2009-11-04: Re: [Bug 446373] Re: The program 'xsane' received an X Window System error.

xsane-symbols-full.gdb Edit (41.5 KiB, text/plain; name="xsane-symbols-full.gdb")

Here you go.

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2009-11-04:

Thats better - thanks. So, it's XRenderChangePicture which triggers this error

Revision history for this message

Florian Quèze (florian-instantbird) wrote on 2009-11-18:

valgrind log Edit (5.5 KiB, text/plain)

I have the same problem on a 32bit machine since I upgraded to karmic.

I noticed when running xsane with valgrind that some uninitialized values are used just before the X errors.
I tried to download the source code and compile it with --enable-debug so that I can get a valgrind log with correct backstacks.
I'm attaching the log of the errors I got.

Revision history for this message

Oliver Steenbuck (ubuntu-hexren) wrote on 2009-12-07:

#10

Bug does not happen for me anymore. Guess one of the last X11 or Kernel upgrades fixed that.

Thanks :)

Revision history for this message

Justin Mazzola Paluska (jmp-mit) wrote on 2009-12-15:

#11

I still have the same problems.

Revision history for this message

Onewing (williammitc) wrote on 2009-12-29:

#12

I have the same bug, xsane preview windows closes. It started with install of Karmic on my amd64 system. Laptop x86 performs fine. As a workaround, I installed gimp2.0-quiteinsane. Clunky, but I now have the preview function when scanning via the gimp.

Revision history for this message

Jaime (jaime-parada) wrote on 2010-01-06:

#13

I have the same problem on a 64bit machine since I upgraded to karmic.

Revision history for this message

Captain Chaos (launchpad-chaos) wrote on 2010-01-13:

#14

Same problem here. Karmic 64-bit. xsane 0.996-2ubuntu1.1 starts and shows the scanner selection dialog. I select a network scanner and xsane crashes with the above message. Strange thing is, it doesn't always happen. Earlier in the same session xsane would start normally, and would crash only when I try to acquire a preview.

I took the liberty of changing the status to New, since the requested information has been provided, I hope that's alright.

Changed in xsane (Ubuntu):
status:	Incomplete → New

Revision history for this message

Captain Chaos (launchpad-chaos) wrote on 2010-01-15:

#15

According to this email: http://lists.alioth.debian.org/pipermail/sane-devel/2009-December/025644.html by Julien Blache, the maintainer of libsane for Debian, this is due to a known bug in the proprietary Nvidia driver.

Can anyone confirm or deny this? I am using the proprietary Nvidia driver, and I can't stop using it as I have two cards with three monitors attached.

Is anyone getting this error message who is not using the proprietary Nvidia drivers?

Revision history for this message

nicolas gapaillard (nicolas-gapaillard) wrote on 2010-01-25:

#16

I have the same problem with ati drivers...

Revision history for this message

Simen Gaure (simen) wrote on 2010-02-07:

#17

I have the same problem. karmic, nvidia-drivers, dual head. However, it goes away if I switch off xinerama in xorg.conf.

Revision history for this message

ghostwriter78 (ghostwriter78) wrote on 2010-04-08:

#18

Still persists in 9.10 (with latest updates) on HP printer/scanner.

A few weeks before it was working, now i added a second monitor to the same nvidia card and enabled xinerama.
Please check why this issue happens it should have nothing to do with my second display!

Reinstalling XSANE does not help!

Revision history for this message

Captain Chaos (launchpad-chaos) wrote on 2010-07-27:

#19

Still happening in Lucid with xsane-0.996.

@nicolas gapaillard: do you have Xinerama enabled?

Since it's still happening with the latest proprietary NVidia driver, and according to nicolas, also with ATi drivers, it seems likely that this really is a bug in xsane itself (like the error message already states). Especially since no other software, including scanner utilities, crashes with that error on my system.

Changed in xsane (Ubuntu):
status:	New → Confirmed

Revision history for this message

James (jamessteward) wrote on 2010-11-17:

#20

On Karmic with nvidia dual head I get this problem.

xsane runs properly however (without crashing on startup) if I run it as root, as in sudo xsane and ignore the warning.

JS.

Revision history for this message

Blake W (blake-weyman) wrote on 2010-12-04:

#21

I can confirm this occurs in Lucid amd64, Xorg 1.8.2, with radeon module version 6.13.99. Running as root works.

Revision history for this message

Ivan Kharlamov (the-paper-men) wrote on 2011-02-21:

#22

xsane_gdb Edit (8.9 KiB, text/plain)

Xsane fails to start on my up to date Lucid x86_64. I run latest proprietary Nvidia driver and two video cards with three displays connected. Every other program runs fine.

Here's my gdb output.

Pete Graner (pgraner) on 2011-03-11

Changed in xsane (Ubuntu):
status:	Confirmed → Fix Released

Revision history for this message

Pacho Ramos (pacho) wrote on 2011-07-12:

#23

What patch did fix this problem? Thanks a lot

Revision history for this message

Torsten Landschoff (torsten) wrote on 2011-11-29:

#24

This seems to be related to https://bugs.launchpad.net/pcb/+bug/699251
I don't think it is fixed, it is only hard to reproduce.
We just ran into this with an in-house application that has no relation to xsane. Basically, whenever a throbber is displayed, we get a crash.

This happens only on one machine which is distinct by
* Using the proprietary nvidia driver
* Having XINERAMA enabled (as opposed to the nividia-specific dual-screen support)
* Has one screen with the usual orientation and the other rotated by 90°

I believe this to be a bug in the Xrender support somewhere (libXrender, Server module, nvidia driver?)
It also does only happen sometimes and may be related to reparenting the throbber on another wizard page in our case.

Revision history for this message

Torsten Landschoff (torsten) wrote on 2011-11-29:

#25

The BadMatch error is returned from the render extension somewhere in this code block:

http://cgit.freedesktop.org/xorg/xserver/tree/render/picture.c?id=b2015a2c01711646bb7ae23d684abee0cd55d4d0#n1096

One reason would be that the mask pixmap is from another screen (no idea) or has the wrong depth (unlikely):

http://cgit.freedesktop.org/xorg/xserver/tree/render/picture.c?id=b2015a2c01711646bb7ae23d684abee0cd55d4d0#n1136

The other possibility is that *ps->ChangePictureClip() generates the BadMatch, but I have no idea where that call goes:

http://cgit.freedesktop.org/xorg/xserver/tree/render/picture.c?id=b2015a2c01711646bb7ae23d684abee0cd55d4d0#n1148