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 549084 - xchat-gnome crashes with segfault when setting to away
xchat-gnome crashes with segfault when setting to away
Status: RESOLVED FIXED
Product: xchat-gnome
Classification: Other
Component: general
0.18
Other Linux
: Normal major
: ---
Assigned To: xchat-gnome maintainers
xchat-gnome maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-23 03:57 UTC by Oxmosys
Modified: 2008-08-31 15:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Backtrace (47.37 KB, text/plain)
2008-08-23 04:00 UTC, Oxmosys
  Details
valgrind (420.45 KB, text/plain)
2008-08-23 04:01 UTC, Oxmosys
  Details
Patch between 0.18 and svn 2630 proposed for ubuntu. (2.99 KB, patch)
2008-08-26 23:25 UTC, Philip Wyett
none Details | Review

Description Oxmosys 2008-08-23 03:57:44 UTC
If you set yourself away when you are already connected to a server and inside a channel, xchat-gnome crashes with segmentation fault.

Steps to reproduce :

1. Open xchat-gnome.
2. Connect to a server and go into a channel.
3. Click on your nickname on the bottom of the window.
4. Check the case to set yourself away.
5. Click apply.
Comment 1 Oxmosys 2008-08-23 04:00:26 UTC
Created attachment 117253 [details]
Backtrace
Comment 2 Oxmosys 2008-08-23 04:01:00 UTC
Created attachment 117254 [details]
valgrind
Comment 3 Philip Wyett 2008-08-26 23:22:45 UTC
This bug is fixed in the xchat-gnome svn trunk. I have taken current code to create a patch for Ubuntu it is corrects the crash issue.
Comment 4 Philip Wyett 2008-08-26 23:25:15 UTC
Created attachment 117429 [details] [review]
Patch between 0.18 and svn 2630 proposed for ubuntu.

For reference I am attaching the diff/patch I have created and used to correct the issue under Ubuntu.
Comment 5 Oxmosys 2008-08-27 16:29:12 UTC
According to Philip Wyett, this bug is already fixed in the more recent svc sources, so this bug should probably be closed.
Comment 6 Christian Persch 2008-08-31 15:21:01 UTC
Closing obsolete as per comment 5.