[Bug 33149] crash when using mouse gestures
Guillermo GutiƩrrez Herrera
capitanterrex at yahoo.es
Tue Feb 28 14:00:51 UTC 2006
Public bug reported:
https://launchpad.net/malone/bugs/33149
Affects: gaim (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
Description:
sometimes, when using mouse gestures plugin to closing or moving tabs,
gaim crashed unexpectly when, after that, i simple click the
conversation window :s
gdb --args gaim -d throws the following output:
~~~~~~~~~~~~~~~
(no debugging symbols found)
(no debugging symbols found)
(14:55:48) irc: Got a PRIVMSG on #gentemsn.com, which does not exist
(14:55:49) irc: Got a PART on #gentemsn.com, which doesn't exist -- probably clo sed
(14:55:50) GLib-GObject: gsignal.c:1739: instance `0x654900' has no handler with id `486'
(14:55:50) GLib-GObject: gsignal.c:1739: instance `0x654900' has no handler with id `487'
(14:55:50) nautilus: don't save blist online. No change
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(14:55:52) accounts: Writing accounts to disk.
(14:55:52) GLib-GObject: gsignal.c:1739: instance `0x654900' has no handler with id `4901'
(14:55:52) GLib-GObject: gsignal.c:1739: instance `0x654900' has no handler with id `4902'
The program 'gaim' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1300205 error_code 3 request_code 10 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.)
Program exited with code 01.
(gdb) bt
No stack.
(gdb)
~~~~~~~~~~~~~~~
I'm using dapper amd64 and xdmcp.
More information about the desktop-bugs
mailing list