Crash with X System Error

Bug #254235 reported by reachingtotheinfinite
66
This bug affects 6 people
Affects Status Importance Assigned to Milestone
cheese (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: cheese

Basic data:
Ubuntu version: Ubuntu 8.04 Hardy Heron
Cheese version: 2.22.3-0ubuntu1

I was trying to open my webcam when suddenly it closed automatically on the load (when the foot appears and the fingers are moving). It didn't show any image of the webcams, but the webcam seem to be active and working when it load because the led appeared on. But the camera is recognized because some hours ago from the application of updates it worked correctly (I think). So, I think the problem is originated by some update. This is what I obtain when I start the application from the console:

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

This probably reflects a bug in the program.

The error was 'BadValue (integer parameter out of range for operation)'.

  (Details: serial 51 error_code 2 request_code 140 minor_code 19)

  (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 camera is built-in model on my laptop, the laptop model is an Asus X53S. That's waht obtain when I type lspci:

spci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc M76 [Radeon Mobility HD 2600 Series]
02:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0)
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
04:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02)
08:00.0 Memory controller: Intel Corporation Turbo Memory Controll

Revision history for this message
Pierre Slamich (pierre-slamich) wrote :

Hi,
Can you try running this command and paste the output here ?
cheese --sync

Revision history for this message
Daniel Wit Preuss (danpre) wrote :

I can confirm the bug with:

Dell XPS m1300
Ubuntu 8.10 (intrepid)
2.24.0 (Ubuntu 2008-10-07)
2.6.27-7-generic (#1 SMP Fri Oct 10 03:55:24 UTC 2008)

Cheese version: 2.24.0-0ubuntu1

It doesn't show any image of the webcams, but the webcam seem to be active and working when it load because the led appears on.

Skype and vlc using the same device are working properly.

When trying to close chees, it stops responding.

cheese --sync
doesn't give any outut

Revision history for this message
nicobrainless (nicoseb) wrote :

Same here...
It's been two month that cheese isn't working for me with Intrepid

Futjitsu Amilo Pi 2530
Ubuntu 8.10 (intrepid)
Cheese 2.24.1
2.6.27-7-generic

I saw on those two links that the bug is suppose to have been fixed upstream
https://bugs.launchpad.net/ubuntu/+source/luvcview/+bug/246089
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/207437

Sure did not work for me...

The webcam works fine with Skype and amsn and like Daniel,
cheese --sync
doesn't give any output

Revision history for this message
Andres Mujica (andres.mujica) wrote :

Nico, this bug is still affecting you? Can you test with Interpid fully updated?

Thanks a lot

Changed in cheese:
status: New → Incomplete
Revision history for this message
Daniel Wit Preuss (danpre) wrote :

I can confirm:
cheese is still affected with this bug.

Full updated Interpid
Cheese version: 2.24.1

Revision history for this message
nicobrainless (nicoseb) wrote :

Hi Andres,

I changed my laptop about a month ago...
MSI PR210 customized

I still had trouble with cheese, not the X error anymore but resolution problem... You actually just made me check and that one is gone too now

Everything is working fine for me now; however I am running on Jaunty fully updated...
cheese version: 2.24.1-0ubuntu2

Thank you,

Revision history for this message
Andres Mujica (andres.mujica) wrote :

Daniel, would it be possible for you to attach the output from

cheese -vv

Thanks

Revision history for this message
Andres Mujica (andres.mujica) wrote :

by the way, thanks Nico for your input, so it seems this would be solved in Jaunty. Let's find what's te problem in intrepid.

Daniel, would it be possible for you to attach the output as separate attachments from

cheese -vv
lspci -vvnn (Nico please add this if you can)
/var/log/Xorg.0.log (Nico please add this if you can)
/etc/X11/xorg.conf (Nico please add this if you can)

Thanks

Please be sure to attach those as separate attachments.

Thanks a lot

Revision history for this message
Daniel Wit Preuss (danpre) wrote :

Andres,

Revision history for this message
Daniel Wit Preuss (danpre) wrote :
Revision history for this message
Daniel Wit Preuss (danpre) wrote :
Revision history for this message
Daniel Wit Preuss (danpre) wrote :
Revision history for this message
Andres Mujica (andres.mujica) wrote :

Nico, if you can add the logs asked would be great, just to compare both of them

thanks!

Revision history for this message
nicobrainless (nicoseb) wrote :

Sorry I was gone during the holidays...
here they are

Revision history for this message
nicobrainless (nicoseb) wrote :
Revision history for this message
nicobrainless (nicoseb) wrote :
Revision history for this message
Andres Mujica (andres.mujica) wrote :

Marking this as confirmed

Changed in cheese:
status: Incomplete → Confirmed
Revision history for this message
Andres Mujica (andres.mujica) wrote :

Sorry i was missing and important part,

Daniel it would be possible for you to give a baktrace from the error?
Please check https://wiki.ubuntu.com/Backtrace and follow the procedure to obtain the backtrace as described.

Thanks a lot for your invaluable help

Changed in cheese:
status: Confirmed → Incomplete
Revision history for this message
Jordan Bradley (jordan-w-bradley) wrote :
Download full text (11.9 KiB)

Hello

I'm getting a similar error:

The program 'cheese' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 61 error_code 11 request_code 140 minor_code 19)
  (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.)

I get the same error if I append --sync to the cheese command. I'm using Ubuntu 32bit 8.10 on an Acer Aspire 5515 laptop.

lspci -vv:

00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge
 Subsystem: Gateway 2000 Device 0184
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
 Latency: 64
 Kernel modules: ati-agp

00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 64
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
 I/O behind bridge: 00009000-00009fff
 Memory behind bridge: f8100000-f82fffff
 Prefetchable memory behind bridge: 00000000f0000000-00000000f7ffffff
 Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
 BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
  PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 Capabilities: <access denied>
 Kernel modules: shpchp

00:06.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 2)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 32 bytes
 Bus: primary=00, secondary=02, subordinate=04, sec-latency=0
 Memory behind bridge: f8300000-f83fffff
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
 BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
  PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 Capabilities: <access denied>
 Kernel driver in use: pcieport-driver
 Kernel modules: shpchp

00:07.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 3)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 32 bytes
 Bus: primary=00, secondary=05, subordinate=07, sec-latency=0
 I/O behind bridge: 0000a000-0000afff
 Memory behind bridge: 88000000-880fffff
 Prefetchable memory behind bridge: 00000000f8000000-00000000f80fffff
 Secondary status: 66MHz- FastB2B- ParErr- ...

Revision history for this message
Andres Mujica (andres.mujica) wrote :

@Jordan, please add the backtrace as asked in the previous comment, it's the only missing part for this bug.

Tahnks

Revision history for this message
Jordan Bradley (jordan-w-bradley) wrote :

Here you go.

Revision history for this message
Andres Mujica (andres.mujica) wrote :

Hi Jordan, thanks for the backtrace, but sadly it didn't get the info needed. So we'd need that you help us with:

1.- installing debugging symbols for cheese
2.- repeating the process, adding at the gdb prompt :
                        break gdk_x_error

For 1. you'll need to add a repo and install the cheese-dbgsym package

Further instructions here:

https://wiki.ubuntu.com/DebuggingProgramCrash

Changed in cheese (Ubuntu):
importance: Undecided → Low
Revision history for this message
Jordan Bradley (jordan-w-bradley) wrote :

Re Andres Mujica:

Where do I run "break gdk_x_error"?

I'm using the instructions at https://wiki.ubuntu.com/Backtrace#Generation but wherever I run "break gdk_x_error" I get:

"Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n])"

Revision history for this message
Timothée Manaud (timothee) wrote :

Hello, since the 9.04 (RC) version, cheese doesn't start properly with a very similar error, on a eeePc 901. It was running fine on the same hardware, version 8.10.
Traces below.

Revision history for this message
Timothée Manaud (timothee) wrote :
Revision history for this message
Timothée Manaud (timothee) wrote :
Revision history for this message
Timothée Manaud (timothee) wrote :
Revision history for this message
Timothée Manaud (timothee) wrote :
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Bug 326328 and bug 335010 are X Error crashes and have stacktraces.

summary: - Cheese crashes in the load
+ Crash with X System Error
Revision history for this message
Timothée Manaud (timothee) wrote :

Cheese version 2.26.0 fixed my problem, many thanks.

Revision history for this message
Jordan Bradley (jordan-w-bradley) wrote :

Cheese version 2.26.0 works for me too.

Revision history for this message
misiu_mp (misiu-mp) wrote :

I herby report this very problem with 2.26.0.
It still sucks. Using ubuntu 9.04.

Revision history for this message
Vish (vish) wrote :

Closing bug report as per multiple comments mentioning that the bug was fixed in cheese 2.26.0.

misiu_mp , if you are still noticing the problem , kindly open a separate bug report

Changed in cheese (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Alessandro Losavio (alo21) wrote :

I opened cheese with my webcam there was a crash and program closed

tags: added: iso-testing
Revision history for this message
tutuca (tutuca) wrote :

I get this backtrace when running from the terminal

Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-alternative-sort-arrows' of type `gboolean' from rc file value "((GString*) 0x84a740)" of type `gboolean'
The program 'cheese' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 77 error_code 8 request_code 132 minor_code 19)
  (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.)

Running 10.04

Revision history for this message
John (jpennefather) wrote :

I was getting this error when I first started cheese (gave up and started using guvcview). Later, when fiddling with dconf I noticed no path was set for the device (web-cam) to be used. I set this string, and it now works fine. I know I am 2 years late to the party but this page is still one of the top google hits for the problem. and it seems a few are still having this problem.

Revision history for this message
John (jpennefather) wrote :

sorry forgot to add v3.4.1 on 12.04

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.