New user registration is currently disabled due to spam abuse / Регистрация новых пользователей в настоящее время приостановлена из-за злоупотреблений спаммерами

X Window System error, bug in the program

Report bugs here

X Window System error, bug in the program

Postby gunnvorwagner » Thu Jun 27, 2013 10:01 pm

hi there,

i cannot start goldendict. Xubuntu 13.04 64 bits, goldendict git pulled. After executing the command on a terminal I get:

Code: Select all
Load done
getResource: gdlookup://localhost?blank=1
scheme: gdlookup
host: localhost
getResource: gdlookup://localhost?blank=1
scheme: gdlookup
host: localhost
getResource: gdlookup://localhost?word=Welcome!&group=4294967295
scheme: gdlookup
host: localhost
In-place finish.
The program 'goldendict' 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 522 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.)


Tips are very welcomed
gunnvorwagner
 
Posts: 15
Joined: Mon May 27, 2013 3:53 pm

Re: X Window System error, bug in the program

Postby Tvangeste » Fri Jun 28, 2013 6:36 am

I'm also using Xubuntu 13.04 x64, but with no problems so far. Do you see a crash or what?

So, you're using the latest bits from Github repository?

What git describe prints for you?

Can you try also run GoldenDict under GDB?

1. gdb ./goldendict
2. Type run
3. Type bt after the crash
Tvangeste
 
Posts: 893
Joined: Thu Jun 02, 2011 11:42 am

Re: X Window System error, bug in the program

Postby gunnvorwagner » Fri Jun 28, 2013 1:35 pm

Tvangeste wrote:I'm also using Xubuntu 13.04 x64, but with no problems so far. Do you see a crash or what?


I do see what I pasted. Starting Goldendict via the icon doesnt do anything.

So, you're using the latest bits from Github repository?

What git describe prints for you?


1.5.0-RC-50-g05fa3f3

Can you try also run GoldenDict under GDB?

1. gdb ./goldendict
2. Type run
3. Type bt after the crash


Short answer: no

Terminal output:

Code: Select all
gdb ./goldendict
GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/dexter/Compiled/goldendict/goldendict...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/dexter/Compiled/goldendict/goldendict
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdbd2e700 (LWP 9097)]
[New Thread 0x7fffdaeb0700 (LWP 9098)]
[New Thread 0x7fff7f69d700 (LWP 9101)]
[Thread 0x7fff7f69d700 (LWP 9101) exited]
Load done
[New Thread 0x7fff7f69d700 (LWP 9113)]
getResource: gdlookup://localhost?blank=1
scheme: gdlookup
host: localhost
getResource: gdlookup://localhost?blank=1
scheme: gdlookup
host: localhost
getResource: gdlookup://localhost?word=Welcome!&group=4294967295
scheme: gdlookup
host: localhost
In-place finish.
[New Thread 0x7fff7db92700 (LWP 9114)]
The program 'goldendict' 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 522 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.)
[Thread 0x7fff7db92700 (LWP 9114) exited]
[Thread 0x7fff7f69d700 (LWP 9113) exited]
[Thread 0x7fffdaeb0700 (LWP 9098) exited]
[Thread 0x7fffdbd2e700 (LWP 9097) exited]
[Inferior 1 (process 9087) exited with code 01]
(gdb) bt
No stack.
(gdb)
gunnvorwagner
 
Posts: 15
Joined: Mon May 27, 2013 3:53 pm

Re: X Window System error, bug in the program

Postby Tvangeste » Fri Jun 28, 2013 1:46 pm

Weird. I do see a warning on my machine, but it doesn't affect GoldenDict and it works just fine:

Code: Select all
X Error: BadAccess (attempt to access private resource denied) 10
  Major opcode: 33 (X_GrabKey)
  Resource id:  0x138


Please try to add one more step to your debugging session and see if it produces additional info:

Code: Select all
1. gdb ./goldendict
2. break gdk_x_error
3. run
4. bt
Tvangeste
 
Posts: 893
Joined: Thu Jun 02, 2011 11:42 am

Re: X Window System error, bug in the program

Postby gunnvorwagner » Fri Jun 28, 2013 1:59 pm

Same result, slightly different output:

Code: Select all
gdb ./goldendict
GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/dexter/Compiled/goldendict/goldendict...(no debugging symbols found)...done.
(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error) pending.
(gdb) run
Starting program: /home/dexter/Compiled/goldendict/goldendict
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdbd2e700 (LWP 10580)]
[New Thread 0x7fffdaeb0700 (LWP 10581)]
[New Thread 0x7fff7f69d700 (LWP 10584)]
[Thread 0x7fff7f69d700 (LWP 10584) exited]
Load done
[New Thread 0x7fff7f69d700 (LWP 10596)]
getResource: gdlookup://localhost?blank=1
scheme: gdlookup
host: localhost
getResource: gdlookup://localhost?blank=1
scheme: gdlookup
host: localhost
getResource: gdlookup://localhost?word=Welcome!&group=4294967295
scheme: gdlookup
host: localhost
In-place finish.
[New Thread 0x7fff7db92700 (LWP 10597)]
The program 'goldendict' 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 548 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.)
[Thread 0x7fffdbd2e700 (LWP 10580) exited]
[Thread 0x7fff7f69d700 (LWP 10596) exited]
[Thread 0x7fffdaeb0700 (LWP 10581) exited]
[Thread 0x7ffff7fa17c0 (LWP 10556) exited]
[Inferior 1 (process 10556) exited with code 01]
(gdb) bt
No stack.
(gdb)
gunnvorwagner
 
Posts: 15
Joined: Mon May 27, 2013 3:53 pm

Re: X Window System error, bug in the program

Postby Tvangeste » Fri Jun 28, 2013 2:36 pm

Thanks for your efforts.

I've filed a bug in our issue tracker: https://github.com/goldendict/goldendict/issues/359

If only I could reproduce the problem somehow!

Meahwhile, you could try to comment a couple of lines in hotkeywrapper.cc file, like this:

Code: Select all
  if ( result.second )
  {
//    XGrabKey( QX11Info::display(), keyCode, modifiers, QX11Info::appRootWindow(),
//              True, GrabModeAsync, GrabModeAsync );
  }


That should unblock you and you should be able to start GoldenDict, albeit global hotkeys (Ctrl+F11+F11 and Ctrl+C+C) might not work. Let me know once you've tried that, is the crash gone or not.
Tvangeste
 
Posts: 893
Joined: Thu Jun 02, 2011 11:42 am

Re: X Window System error, bug in the program

Postby gunnvorwagner » Fri Jun 28, 2013 5:33 pm

Tvangeste wrote:
Code: Select all
  if ( result.second )
  {
//    XGrabKey( QX11Info::display(), keyCode, modifiers, QX11Info::appRootWindow(),
//              True, GrabModeAsync, GrabModeAsync );
  }



quoting those lines doesnt make any difference
gunnvorwagner
 
Posts: 15
Joined: Mon May 27, 2013 3:53 pm

Re: X Window System error, bug in the program

Postby Tvangeste » Fri Jun 28, 2013 5:59 pm

Whoa, that's totally unexpected. I'm out of ideas for the moment. Let's wait for Abs62, maybe he has some fresh ones. :)

So, do you have any custom stuff on your system or anything atypical in your setup that worth mentioning? I'm surprised that we're seeing completely different behaviors on about the same systems. What Window Manager do you use, by the way?
Tvangeste
 
Posts: 893
Joined: Thu Jun 02, 2011 11:42 am

Re: X Window System error, bug in the program

Postby gunnvorwagner » Fri Jun 28, 2013 6:21 pm

Tvangeste wrote:So, do you have any custom stuff on your system or anything atypical in your setup that worth mentioning? I'm surprised that we're seeing completely different behaviors on about the same systems. What Window Manager do you use, by the way?


I usually start goldendict the following way:

Code: Select all
goldendict -style plastique


this is due to: viewtopic.php?f=6&t=2261

I didnt make a fresh install of xubuntu 13.04. I upgraded from 12.10. Other than that I cannot think of any other unusual setup

Window manager: x11
gunnvorwagner
 
Posts: 15
Joined: Mon May 27, 2013 3:53 pm

Re: X Window System error, bug in the program

Postby Tvangeste » Fri Jun 28, 2013 8:08 pm

OK, one more thing to try.

Make sure no goldendict is running, then open the ~/.goldendict/conifg file in any text editor and change 1 to 0 in two places:

Code: Select all
<enableMainWindowHotkey>1</enableMainWindowHotkey>
... snip ....
<enableClipboardHotkey>1</enableClipboardHotkey>

to
Code: Select all
<enableMainWindowHotkey>0</enableMainWindowHotkey>
... snip ...
<enableClipboardHotkey>0</enableClipboardHotkey>


Is your GoldenDict still crashing after such change?
Tvangeste
 
Posts: 893
Joined: Thu Jun 02, 2011 11:42 am

Next

Return to Bugs

Who is online

Users browsing this forum: No registered users and 15 guests