xchat-gnome crashed with SIGSEGV in servlist_connect()

[Ted Gould]

Binary package hint: xchat-gnome

So, everyone tells me I should be using a "real" IRC client. I fire up XChat, configure it, and on the next start this is what it does. Make me giggle :)

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/xchat-gnome
NonfreeKernelModules: ath_hal nvidia
Package: xchat-gnome 1:0.18-3ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: xchat-gnome
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: xchat-gnome
StacktraceTop:
 servlist_connect ()
 servlist_auto_connect ()
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
Title: xchat-gnome crashed with SIGSEGV in servlist_connect()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt scanner video

[Apport retracing service (apport)]

StacktraceTop:servlist_auto_connect (sess=0x0) at servlist.c:634
xchat_auto_connect (userdata=0x0) at xchat.c:687
g_idle_dispatch (source=0x8f83990, callback=0, user_data=0x0)
IA__g_main_context_dispatch (context=0x8a1cad8) at /build/buildd/glib2.0-2.17.6/glib/gmain.c:2072
g_main_context_iterate (context=0x8a1cad8, block=1, dispatch=1, self=0x89ee628)

[Sebastien Bacher (seb128)]

the issue is similar to bug #95000

[Pedro Villavicencio (pedro)]

I've opened a new bug upstream about it here: http://bugzilla.gnome.org/show_bug.cgi?id=548907 ; since the other one was closed more than a year ago, thanks you.

[rotsee (leo-wallentin)]

To me it happenes already from the very first attempt to start the program. I'm able to se the program window for a few seconds, but can not interact with it.

[Pedro Villavicencio (pedro)]

 is this still reproducible with xchat-gnome 0.26.1-0ubuntu1 ? latest dup is on 0.26.0

[Pedro Villavicencio (pedro)]

Ted any news about this? may you tell us if it's reproducible with the latest version or not?

[mrnaan (toxicnaan)]

I've upgraded my system!! I'm on 9.04 now, so I'll let you know if it comes
back!!!!!

:-)

On Mon, Jun 15, 2009 at 8:28 PM, Pedro Villavicencio <email address hidden>wrote:

> Ted any news about this? may you tell us if it's reproducible with the
> latest version or not?
>
> --
> xchat-gnome crashed with SIGSEGV in servlist_connect()
> https://bugs.launchpad.net/bugs/259112
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in GNOME frontend to the popular xchat IRC client: Incomplete
> Status in “xchat-gnome” source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: xchat-gnome
>
>
> So, everyone tells me I should be using a "real" IRC client. I fire up
> XChat, configure it, and on the next start this is what it does. Make me
> giggle :)
>
> ProblemType: Crash
> Architecture: i386
> CrashCounter: 1
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/xchat-gnome
> NonfreeKernelModules: ath_hal nvidia
> Package: xchat-gnome 1:0.18-3ubuntu1
> ProcAttrCurrent: unconfined
> ProcCmdline: xchat-gnome
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> Signal: 11
> SourcePackage: xchat-gnome
> StacktraceTop:
> servlist_connect ()
> servlist_auto_connect ()
> ?? ()
> ?? () from /usr/lib/libglib-2.0.so.0
> g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
> Title: xchat-gnome crashed with SIGSEGV in servlist_connect()
> Uname: Linux 2.6.26-5-generic i686
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd
> lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt scanner video
>

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.