Arch Linux

foggybrain

Member

Registered: 2008-07-29

Posts: 86

X Window Errors [SOLVED]

Using up to date Arch 64 KDE4 with nvidia 8400 graphics card.

After system upgrade yesterday I now have discovered three applications that will not start anymore, error messages below.

checkgmail-svn

The program 'checkgmail' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 159 error_code 8 request_code 2 minor_code 0)
  (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.)

me-tv

Me TV 1.3.4
16/11/10 00:11:11: Device: 'DiBcom 7000PC' (DVB-T) at "/dev/dvb/adapter0/frontend0"
16/11/10 00:11:13: Frontend::tune_to(505833330)
16/11/10 00:11:13: Waiting for signal lock ...
16/11/10 00:11:13: Got signal lock
me-tv-player (xine): Setting deinterlacer state to true
me-tv-player (xine): Setting audio stream to 0
me-tv-player (xine): Setting subtitle stream to -1
me-tv-player (xine): Setting mute state to false
me-tv-player (xine): Setting volume to 100
** (process:7162): DEBUG: Failed to call Inhibit method

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  132 (XVideo)
  Minor opcode of failed request:  19 ()
  Serial number of failed request:  134
  Current serial number in output stream:  135

amule-upnp

Initialising aMule 2.2.6 using wxGTK2 v2.8.11
Checking if there is an instance already running...
No other instances are running.
ListenSocket: Ok.
The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 2842 error_code 8 request_code 2 minor_code 0)
  (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.)

What the hell has happend to X ?????

Please help, or at least let me know I'm not the only one with this/these problems

Thanks, Tim

Last edited by foggybrain (2010-11-16 11:17:24)

1LordAnubis

Member

Registered: 2008-10-10

Posts: 253

Website

Re: X Window Errors [SOLVED]

add Sonata to the list

---

Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw

rabid_works

Member

Registered: 2010-08-15

Posts: 45

Re: X Window Errors [SOLVED]

I've got the same issue with firestarter. I have some other weird behaviour with lxpanel/xfce-panel and applications not being able to dock in their respective status bars. X is just acting weirdly in general. I tried downgrading all x related updates that I -Syu'd this morning, but that hasn't done anything. Everything was running fine until I updated earlier.

Here's my pacman.log from this morning:

upgraded alsa-utils (1.0.23-2 -> 1.0.23-3)
[2010-11-16 03:21] upgraded coreutils (8.6-1 -> 8.7-1)
[2010-11-16 03:21] upgraded glib2 (2.26.0-2 -> 2.26.1-1)
[2010-11-16 03:21] upgraded inputproto (2.0-1 -> 2.0.1-1)
[2010-11-16 03:21] installed libgnome-data (2.32.0-3)
[2010-11-16 03:21] upgraded libgnome (2.32.0-1 -> 2.32.0-3)
[2010-11-16 03:21] upgraded libgphoto2 (2.4.10-1 -> 2.4.10.1-1)
[2010-11-16 03:21] upgraded libxi (1.3.2-1 -> 1.4.0-1)
[2010-11-16 03:21] upgraded man-pages (3.30-1 -> 3.31-1)
[2010-11-16 03:21] upgraded perl-xml-parser (2.36-7 -> 2.40-1)
[2010-11-16 03:21] upgraded pyxml (0.8.4-7 -> 0.8.4-8)
[2010-11-16 03:21] upgraded qtcurve-gtk2 (1.7.0-1 -> 1.7.1-1)
[2010-11-16 03:21] upgraded qtcurve-kde4 (1.7.0-1 -> 1.7.1-1)
[2010-11-16 03:22] upgraded transmission-gtk (2.11-1 -> 2.12-1)
[2010-11-16 03:22] upgraded tzdata (2010n-1 -> 2010o-1)
[2010-11-16 03:22] upgraded vlc (1.1.4.1-2 -> 1.1.5-1)
[2010-11-16 03:22] upgraded xorg-xgamma (1.0.3-1 -> 1.0.4-1)
[2010-11-16 03:22] upgraded xorg-xinput (1.5.2-1 -> 1.5.3-1)
[2010-11-16 03:22] upgraded xorg-xkill (1.0.2-1 -> 1.0.3-1)
[2010-11-16 03:22] upgraded xorg-xrandr (1.3.3-1 -> 1.3.4-1)
[2010-11-16 03:22] upgraded xorg-xrdb (1.0.6-1 -> 1.0.7-1)
[2010-11-16 03:22] upgraded xorg-xrefresh (1.0.3-1 -> 1.0.4-1)
[2010-11-16 03:22] upgraded xorg-xset (1.2.0-1 -> 1.2.1-1)
[2010-11-16 03:22] upgraded xorg-xsetroot (1.0.3-1 -> 1.1.0-1)
[2010-11-16 03:22] upgraded xorg-xwd (1.0.3-1 -> 1.0.4-1)
[2010-11-16 03:22] upgraded xorg-xwud (1.0.2-1 -> 1.0.3-1)
[2010-11-16 03:22] upgraded xproto (7.0.18-1 -> 7.0.19-1)

I'm using the nvidia-173xx driver from [extra] and Pekwm and XFCE (both show the same behaviour). If anyone has any ideas on what's the cause of the issue, I'm also keen to sort this out.

Cheers.

[EDIT] actually, just had another look at the pacman.log and realised it was qtcurve-gtk2 and qtcurve-kde4 that were the culprits. Just downgraded them and everything is fine again. Firestarter works again as well.

Last edited by rabid_works (2010-11-16 04:25:35)

foggybrain

Member

Registered: 2008-07-29

Posts: 86

Re: X Window Errors [SOLVED]

Thank-you, thank-you, thank-you rabid_works

warning: qtcurve-gtk2: ignoring package upgrade (1.6.4-1 => 1.7.1-1)
warning: qtcurve-kde3: ignoring package upgrade (1.6.2-1 => 1.7.1-1)
warning: qtcurve-kde4: ignoring package upgrade (1.6.4-1 => 1.7.1-1)

all apps work fine now, I'll will report bug(s)

[EDIT]

https://bugs.archlinux.org/task/21713

Last edited by foggybrain (2010-11-16 19:37:53)

darose

Member

Registered: 2004-04-13

Posts: 161

Re: X Window Errors [SOLVED]

Please post the bug #'s here.  I'm also having problems with qtcurve today.  (XFCE panel applets are flickering / not docking in panel.)

skunktrader

Member

From: Brisbane, Australia

Registered: 2010-02-14

Posts: 1,667

Re: X Window Errors [SOLVED]

I'm also having problems with qtcurve today.  (XFCE panel applets are flickering / not docking in panel.)

As a workaround, try editing ~/.config/qtcurve/stylerc and add gtk to the list of apps in noMenuBgndOpacityApps

noMenuBgndOpacityApps=inkscape,gtk,totem,sonata

Last edited by skunktrader (2010-11-16 15:10:23)

kst-

Member

Registered: 2009-07-06

Posts: 2

Re: X Window Errors [SOLVED]

same here with gmusicbrowser, downgrading qtcurve-gtk2 and qtcurve-kde4 to 1.6.4 works for the moment

skunktrader

Member

From: Brisbane, Australia

Registered: 2010-02-14

Posts: 1,667

Re: X Window Errors [SOLVED]

qtcurve 1.7.2 is in the repos and should fix these problems