[Bug 220628] Re: [MASTER] firefox-3.0b5 received an X Window System error: 'BadIDChoice'
BlueT - Matthew Lien
bluet at ubuntu-tw.org
Mon Apr 13 19:32:11 UTC 2009
matthew at Priapus:~/bug-report$ firefox -g --sync &
[1] 13228
matthew at Priapus:~/bug-report$ /home/matthew/bin/backtrace.sh /usr/lib/firefox-3.0.8/firefox -x /tmp/mozargs.o13230
outputting trace to '/tmp/gdb-firefox.txt'
FoxyProxy settingsDir = /home/matthew/.mozilla/firefox/hpelwq2p.default
matthew at Priapus:~/bug-report$
matthew at Priapus:~/bug-report$ Removing DOMNodeRemoved listener
Removing DOMNodeRemoved listener
Removing DOMNodeRemoved listener
!!! [Hook] hook(): title not found
!!! [Hook] hook(): title not found
[FDLProc] canHandle()
[FDLProc] canHandle()
[FDLProc] canHandle()
Removing DOMNodeRemoved listener
Removing DOMNodeRemoved listener
Removing DOMNodeRemoved listener
Removing DOMNodeRemoved listener
Removing DOMNodeRemoved listener
Removing DOMNodeRemoved listener
Removing DOMNodeRemoved listener
Removing DOMNodeRemoved listener
[ConvConfHandler] isPreferred contentType: application/zip
Removing DOMNodeRemoved listener
[FDLProc] canHandle()
Removing DOMNodeRemoved listener
[FDLProc] canHandle()
The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
(Details: serial 40698879 error_code 14 request_code 152 minor_code 4)
(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.)
[1]+ Done firefox -g --sync
** Attachment added: "gdb-firefox.10.txt"
http://launchpadlibrarian.net/25353581/gdb-firefox.10.txt
--
[MASTER] firefox-3.0b5 received an X Window System error: 'BadIDChoice'
https://bugs.launchpad.net/bugs/220628
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to gtk-qt-engine in ubuntu.
More information about the kubuntu-bugs
mailing list