After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 506706 - crash in XChat-GNOME IRC Chat: y do not
crash in XChat-GNOME IRC Chat: y do not
Status: RESOLVED DUPLICATE of bug 487503
Product: xchat-gnome
Classification: Other
Component: general
0.18
Other All
: High critical
: ---
Assigned To: xchat-gnome maintainers
xchat-gnome maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-01 15:57 UTC by ilmare
Modified: 2008-03-23 23:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ilmare 2008-01-01 15:57:13 UTC
What were you doing when the application crashed?
y do not


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 49065984 vsize: 49065984 resident: 22118400 share: 18616320 rss: 22118400 rss_rlim: 4294967295
CPU usage: start_time: 1199202489 rtime: 35 utime: 31 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/xchat-gnome'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208256800 (LWP 4359)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208256800 (LWP 4359))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 pevent_make_pntevts
  • #8 load_text_events
  • #9 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
  Resource id:  0x2e00003
XChat CRITICAL *** default event text failed to build!
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x3200003
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x2e000d7
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x2e0011e
XChat CRITICAL *** default event text failed to build!
--------------------------------------------------
Comment 1 Marc-Andre Lureau 2008-03-23 23:55:50 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 487503 ***