#3 audacious crashes when I enable the plugin

[Götz Waschk]

This is with audacious svn r4207 and plugins svn r1629 (post rc2) on Mandriva Cooker i586 with itouch-control 0.1.1. When I enable the plugin I get this crash:

The program 'audacious' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
(Details: serial 7 error_code 10 request_code 33 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.)

[William Pitcock]

Logged In: YES
user_id=1734291
Originator: NO

This problem is because iTouch control uses a second connection to the X server. This is incorrect. Instead, iTouch control should use GDK/Xlib normally.

[paskov]

Logged In: YES
user_id=1002559
Originator: NO

What do you mean by normally? I

Currently when plugin is initialized, it opens connection to the X server default display, sets a timer and starts to listen for events! If there is some other way of getting the default display.

From my research I have discovered that the crash (sometimes at leas on my machine) is in the itouchctrl_timeout_func () called by g_timeout_add (100, itouchctrl_timeout_func, NULL).

the itouchctrl_timeout_func ():

static gint itouchctrl_timeout_func (gpointer data)
{
long mask = KeyPressMask;
XEvent event;

while (XCheckMaskEvent(xdisplay, mask, &event))
{
itouchctrl_handle_keyevent (event.xkey.keycode);
}

return TRUE;
}
=====================================

Any suggestion, what exactly is wrong?

[Anonymous]

Logged In: YES
user_id=1071047
Originator: NO

i just compiled 0.1.1 and i'm having the same issue. funny thing is, i already reported this, but it got closed later on, without any comment saying why. i assumed it was fixed in the codebase as of then, but apparently it just got closed for no reason.

[Nobody/Anonymous]

Logged In: NO

Hello again,

I mean that you should use GDK and not Xlib, and additionally not connect your own client to the XServer. This is why the crash is occuring. X11 dislikes having multiple connections from the same client process, and Xlib (and thus GTK) is dependant on not having multiple connections in the state.

It is possible to grab the root window using audacious's primary X11 connection.

- nenolod

[Nobody/Anonymous]

Logged In: NO

Just a note: Having the exact same problem on Ubunty Feisty Fawn

[Nobody/Anonymous]

Logged In: NO

I have the same problem. Audacious 1.3.2 compiled from source, on Ubunty Edgy

[Anonymous]

Logged In: YES
user_id=1071047
Originator: NO

Any updates on this? I haven't been able to use this plugin for a while now...

[Nobody/Anonymous]

Logged In: NO

A fix is available in Global Hotkey Plugin, which is a fork/rewrite of iTouch Control. See the Audacious plugins site for more info.

[Anonymous]

Logged In: YES
user_id=1071047
Originator: NO

Cool, thanks. I already found the plugin last week though, but its nice to have it posted here for everyone else that runs into this problem.