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 495715 - crash in XChat-GNOME IRC Chat: first run
crash in XChat-GNOME IRC Chat: first run
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: 2007-11-10 21:35 UTC by rrrr.sssss
Modified: 2007-12-08 04:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description rrrr.sssss 2007-11-10 21:35:50 UTC 
What were you doing when the application crashed?
first run


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 323670016 vsize: 323670016 resident: 16605184 share: 11542528 rss: 16605184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194737597 rtime: 48 utime: 40 stime: 8 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912511237616 (LWP 4663)]
(no debugging symbols found)
0x0000003522e0d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 176888

Thread 1 (Thread 46912511237616 (LWP 4663))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 strcmp
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 pevent_make_pntevts
  • #6 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (4035 sec old) ---------------------
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x5000001 non valido per 0x5000013 (Virtual TI).
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2007-12-08 04:30:26 UTC 
Thanks for the 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.


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