Fedora Account System
Red Hat Associate
Red Hat Customer
abrt 1.0.6 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/firefox-3.5.6/firefox component: firefox executable: /usr/lib/firefox-3.5.6/firefox kernel: 2.6.31.12-174.2.3.fc12.i686.PAE package: firefox-3.5.6-1.fc12 rating: 4 reason: Process was terminated by signal 6 (Aborted) release: Fedora release 12 (Constantine)
Created attachment 390524 [details] File: backtrace
#7 0x00be9486 in IA__g_warn_message (domain=<value optimized out>, file=<value optimized out>, line=<value optimized out>, func=<value optimized out>, warnexpr=<value optimized out>) at gmessages.c:608 s = 0xa9e7cc00 "The program 'firefox' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'XI_BadDevice (invalid Device parameter)'.\n (Details: serial 1686568 error_code 145"... lstr = "\353Qi\000\005\000\000\000\360\341\346\277e\343\232\000\000\212v\251\000\000\000\000\001\000\000\000\005\000\000" #8 0x00be94b7 in IA__g_warn_message (domain=<value optimized out>, file=<value optimized out>, line=<value optimized out>, func=<value optimized out>, warnexpr=<value optimized out>) at gmessages.c:606 s = <value optimized out> lstr = "\315<)*\240Pi\000\004\226U\000[\216\276\000 \035t\000(\274\031\000L\342\346\277\b\342\346\277" #9 0x006f0313 in gdk_x_error (display=<value optimized out>, error=<value optimized out>) at gdkmain-x11.c:466 buf = "XI_BadDevice (invalid Device parameter)", '\000' <repeats 24 times> msg = <value optimized out> #10 0x009ee946 in bonobo_x_error_handler (display=<value optimized out>, error=<value optimized out>) at bonobo-ui-main.c:61 No locals. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Thank you for taking the time to submit this bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 538207 ***