[SRU] xchat crashes frequently on quit

Bug #57951 reported by Alexandre Vassalotti on 2006-08-28
188
Affects Status Importance Assigned to Milestone
xchat (Ubuntu)
Medium
Unassigned
Declined for Edgy by Scott Kitterman
Edgy
Medium
Unassigned

Bug Description

Steps to reproduce:
1. start xchat
2. connect to a server
3. chat a little bit
4. close xchat

It seems the bug isn't easily reproducible. But, it does occur frequently.

Darryl Clarke (dclarke) wrote :

I just experienced this same thing.

I just closed it using the [x], and it popped up a crash dialog.

Only one time so far though, I can't reproduce it step for step.

Darryl Clarke (dclarke) wrote :
Changed in xchat:
status: Unconfirmed → Confirmed
description: updated
description: updated
vrde (vrde) wrote :

I've got the same problem. Until now only one time after using the window [x].

Johnny Jelinek IV (johnnyjiv) wrote :

popup notifier said to upload this :D

Steve Garton (sheepeatingtaz) wrote :

Again, the bug reporting pop-up asked me to upload this

Crash report from me

bert_3262c (casema) wrote :

The crash-report dialog comes up(apport?) when you close x-chat from the tray. maybe apport "thinks" there is a crash when you close the program from the tray. don't think there really is a crash but who knows I might be wrong ;)

bert_3262c (casema) wrote :

to add to my last comment: i am not under the impression that x-chat crashes when you use the quit button in the application, only when closing from the tray, but I can't really reproduce so not to sure :)

Andrew Clunis (orospakr) wrote :

This has been happening consistently when I log out of Edgy with xchat still running, although I don't there's any difference when closing Xchat manually.

Zizou (machavez) wrote :

Yeah it really happens frequently... (Reporting bugs from Venezuela XD)

9johnny (s.j.) wrote :

I occurs frequently, and I think more frequently when closing from systray. I is a bit of a random bug, it doesn't always happen.

Hans L (thehans) wrote :

It's happening to me too.

Joel Calado (joelcalado) wrote :

Another crash report here

Marc Rene Schädler (suaefar) wrote :

Yet another crash report.

Randakar (randakar) wrote :

Another crash output report..

I just found out that the bug is triggered if you close XChat with the "Close Window" button without using /quit before.

DarkMageZ (darkmagez) wrote :

I used to beable to replicate this bug. but since I rebuilt it without the striping of debugging symbols... i can't seem to replicate it anymore. maybe it just needs to be rebuilt against current edgy? or maybe the stripping process is doing some damage? meh.

I discovered that /quit has no effect on the bug.

DarkMageZ (darkmagez) wrote :

ignore my above comment. here is a good crash log.

this is using a slightly modified version of the xchat from edgy. the difference is that i've removed the stripping of debugging stuff. it was built using pbuilder.

amx109 (amx109) wrote :

yet another crash report

Mike Stukalov (xska) wrote :

another crash

graymer (graymer) wrote : same here

yup, me too

crash here too, but i'm not adding a report ;)

i get this frequently when closing xchat through the window manager.

Michael Davis (kiwistardesign) wrote :

I have just encounted this problem as well.

I had just finished my chat and then disconnected from the server and then closed xchat down and then low and behold it says that xchat crashed.

For what ever reason I did everything as pernormal???

Jacob Godserv (fun2program8) wrote :

I think you guys need another crash report, don't you? :P

Pasting it just for the record - I don't really care if everyone ignores this.

Mike Basinger (mike.basinger) wrote :

Same here

russofris (russofris) wrote :

Same. Chatted in ##c for a bit, closed via "X" in the upper right, and boom.

Arun (arunmarjun) wrote :

This crash happened when i was closing it too.

Fabio Marzocca (thesaltydog) wrote :

Same thing to me. Crash on closing.

Tabrez Iqbal (tabrez) wrote :

crashed on quit. doesn't happen always, but 6 out of 10 times.

The bug seems to be fixed in the current CVS version of XChat. Anyone could also confirm this?

DarkMageZ (darkmagez) wrote :

cvs is fairly bleeding edge. tho i can almost confirm that this doesn't happen in 2.6.8

Eric Raehn (kaiki) wrote :

Xchat on edgy version 2.6.6-0ubuntu3 also frequently crashes on exit

André Cruz (andrefcruz) wrote :

Me tto.

Could someone tries to reproduce the bug by launching Xchat from the command line?

Eduard Grebe (eduardgrebe) wrote :

I'm experiencing this frequently on edgy ppc.

LuisMendes (luismendes) wrote :

I've managed to get the error, running xchat from command line. I think the output is not very helpful, but here it goes:

$ xchat
Segmentation fault (core dumped)

Same thing, closing xchat, don't really see it crashing, but at the next boot I got the crash message.

I suspect the fact that xchat is not entirely closed when I logoff the machine.

Jad Madi (jad) wrote :
Download full text (26.5 KiB)

ProblemType: Crash
CoreDump:
Date: Tue Nov 28 22:56:12 2006
Dependencies:
 libgcc1 1:4.1.1-13ubuntu5
 lsb-base 3.1-10ubuntu4
 libreadline5 5.1-7build1
 libslang2 2.0.6-2
 libtiff4 3.8.2-6
 libncursesw5 5.5-2ubuntu1
 whiptail 0.52.2-5.1ubuntu1
 libtext-charwidth-perl 0.04-4
 libxrender1 1:0.9.1-0ubuntu1
 fontconfig 2.3.2-7ubuntu2
 libssl0.9.8 0.9.8b-2ubuntu2
 liblocale-gettext-perl 1.05-1
 libxau6 1:1.0.1-1
 libxext6 2:1.0.1-1ubuntu1
 libxfixes3 1:4.0.1-0ubuntu1
 python 2.4.3-11ubuntu3
 libjpeg62 6b-13
 libdbus-glib-1-2 0.71-1ubuntu1
 libacl1 2.2.39-1ubuntu2
 liblzo1 1.08-3
 libncurses5 5.5-2ubuntu1
 readline-common 5.1-7build1
 libgtk2.0-0 2.10.6-0ubuntu1
 libgpg-error0 1.2-1
 libidl0 0.8.6-1ubuntu1
 tcl8.4 8.4.12-1.1
 python2.4-minimal 2.4.4~c1-0ubuntu1
 libpopt0 1.10-2
 gcc-4.1-base 4.1.1-13ubuntu5
 psmisc 22.2-1
 libxcursor1 1.1.7-0ubuntu1
 libperl5.8 5.8.8-6
 launchpad-integration 0.1.4.3
 libfontconfig1 2.3.2-7ubuntu2
 libglib2.0-0 2.12.4-0ubuntu1
 libpng12-0 1.2.8rel-5.1ubuntu0.1
 defoma 0.11.10
 libtext-wrapi18n-perl 0.06-5
 ttf-dejavu 2.7-2
 sed 4.1.5-1
 libcupsys2 1.2.4-2ubuntu3
 xchat-common 2.6.6-0ubuntu3
 mktemp 1.5-2
 libxrandr2 2:1.1.1-0ubuntu1
 libselinux1 1.30-1ubuntu1
 libmagic1 4.17-2ubuntu1
 python2.4 2.4.4~c1-0ubuntu1
 libattr1 2.4.32-1ubuntu1
 libsexy2 0.1.10-0ubuntu2
 mime-support 3.36-1
 libbz2-1.0 1.0.3-3
 liborbit2 1:2.14.3-0ubuntu2
 python-minimal 2.4.3-11ubuntu3
 libenchant1c2a 1.2.3-0ubuntu2
 fontconfig-config 2.3.2-7ubuntu2
 libgnutls13 1.4.0-3ubuntu1
 debconf 1.5.2ubuntu2
 libxinerama1 2:1.0.1-4build1
 libdbus-1-3 0.93-0ubuntu3
 ucf 2.0012
 libpango1.0-common 1.14.5-0ubuntu1
 libgtk2.0-bin 2.10.6-0ubuntu1
 libnewt0.52 0.52.2-5.1ubuntu1
 lsb-release 3.1-10ubuntu4
 libgcrypt11 1.2.2-2
 debconf-i18n 1.5.2ubuntu2
 perl 5.8.8-6
 tzdata 2006m-1ubuntu1
 libxi6 2:1.0.1-0ubuntu1
 libcairo2 1.2.4-1ubuntu2
 x11-common 1:7.1.1ubuntu6
 libsepol1 1.12-1
 debianutils 2.16.2
 locales 2.3.22
 mcpp 2.6.1-0ubuntu2
 gconf2-common 2.16.0-0ubuntu1
 belocs-locales-bin 2.4-1ubuntu6
 libtasn1-3 0.3.5-1
 libxdmcp6 1:1.0.1-1
 libx11-data 2:1.0.3-0ubuntu4
 liblaunchpad-integration0 0.1.4.3
 libatk1.0-0 1.12.3-0ubuntu1
 file 4.17-2ubuntu1
 libxml2 2.6.26.dfsg-2ubuntu4
 libfreetype6 2.2.1-5
 libtext-iconv-perl 1.4-3
 libaspell15 0.60.4-4
 libice6 2:1.0.1-1ubuntu1
 libopencdk8 0.5.8-1
 libsm6 2:1.0.1-1ubuntu1
 perl-modules 5.8.8-6
 dpkg 1.13.22ubuntu7
 coreutils 5.96-5ubuntu4
 libgdbm3 1.8.3-3
 libstdc++6 4.1.1-13ubuntu5
 libgtk2.0-common 2.10.6-0ubuntu1
 libx11-6 2:1.0.3-0ubuntu4
 ncurses-bin 5.5-2ubuntu1
 libgconf2-4 2.16.0-0ubuntu1
 zlib1g 1:1.2.3-13ubuntu2
 libc6 2.4-1ubuntu12
 libxft2 2.1.10-1ubuntu1
 gconf2 2.16.0-0ubuntu1
 perl-base 5.8.8-6
 libdb4.4 4.4.20-6ubuntu1
 libpango1.0-0 1.14.5-0ubuntu1
 libexpat1 1.95.8-3.2
Disassembly:
 (no debugging symbols found)
 Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debu...

Has anyone tried compiling Debian Sid's newer version of xchat yet? Though I
doubt that'd fix anything :D

I tried re-compiling the Debian Sid version and got a dbus error.

DarkMageZ (darkmagez) wrote :

sid = debians unstable branch right?
i've been running debian's 2.6.8 for alittle while now. it fixes the bug.

i'm not sure how Mike compiles his software, but under a clean environment (pbuilder). debian's 2.6.8 compiles fine and fixes this bug without opening up any new bugs that i have seen.

John Dong (jdong) wrote :

debian sid's version does compile cleanly in pbuilder.... though I haven't tried it long enough to make a judgement about whether or not this is fixed yet.

John Dong (jdong) wrote :

I see xchat was merged from Sid and uploaded to Feisty. Perhaps that's the "fix committed" we're looking for?

I'll play with it a bit on Edgy and see how it is, and perhaps a Backports request can be opened for it.

DarkMageZ (darkmagez) wrote :

a backport would not fix it for those who don't have -backports enabled. something needs to be put in -updates for this to be resolved properly for the majority of people.
if people don't have -updates enabled... well we can't help them.

happens more often if you are connected to more than one server then close x-chat with the keyboard Ctrl-Q combination.

Here's one of my crash just happened

kunami (mastah-killa) wrote :

It also crashes here

viyyer (viyyer) wrote :

here too

Enselic (enselic) wrote :

I also got a crash when I closed it, though it appeared to prevent me from opening some widgets, like the shutdown computer button didn't work, and I couldn't open a new terminal.

Please remove me from this mailing list.

--- Enselic <email address hidden> wrote:

> I also got a crash when I closed it, though it appeared to prevent me
> from opening some widgets, like the shutdown computer button didn't
> work, and I couldn't open a new terminal.
>
> ** Attachment added: "crash report"
> http://librarian.launchpad.net/5330393/_usr_bin_xchat.1000.crash
>
> --
> xchat crashes frequently on quit
> https://launchpad.net/bugs/57951
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

John Dong (jdong) wrote :

Please follow the launchpad.net link and unsubscribe yourself from the
bug.
On Sat, 2006-12-09 at 01:38 +0000, B wrote:
> Please remove me from this mailing list.
>
> --- Enselic <email address hidden> wrote:
>
> > I also got a crash when I closed it, though it appeared to prevent me
> > from opening some widgets, like the shutdown computer button didn't
> > work, and I couldn't open a new terminal.
> >
> > ** Attachment added: "crash report"
> > http://librarian.launchpad.net/5330393/_usr_bin_xchat.1000.crash
> >
> > --
> > xchat crashes frequently on quit
> > https://launchpad.net/bugs/57951
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>

After a very long conversation with the core developer of xchat (zed). I've gone along and hopefully fixed this up. Known regressions consist of loss of being able to use links from within firefox to open up irc channels and servers.

Testing packages:
http://mirror.randumb.org/darkmagez/ubu/xchat-common_2.6.6-0ubuntu4~dmzfix4ubuntu_all.deb
http://mirror.randumb.org/darkmagez/ubu/xchat_2.6.6-0ubuntu4~dmzfix4ubuntu_i386.deb

if you don't know how to install these, then you shouldn't be testing them.

have fun, hopefully this is it.

Would it be possible to get the patches you used? Binary packages aren't very useful.

Thanks

DarkMageZ (darkmagez) wrote :

all that was done was disabling dbus in debian/rules plus lots of hacky changes due to xchat-remote another other stuff nolonger being made due to the disabling of dbus. for the diff used for these packages. http://mirror.randumb.org/darkmagez/ubu/xchat_2.6.6-0ubuntu4~dmzfix4ubuntu.diff.gz

DarkMageZ do you know what caused the bug? Is possible to reproduce it
easily, for testing purposes?

I attached the patch against the current Ubuntu version of the
package, for review.

It seems Launchpad doesn't support email attachments. :/ Here the attachment.

DarkMageZ (darkmagez) wrote :

iirc....... edgy's dbus is borked, so for xchat 2.6.8, zed redesigned his implementation to protect against such borkedness. so unless we are going to put 2.6.8 in -updates then unless someone wants to alter edgy's dbus... or wants to pull that huge change back from 2.6.8 then the only viable option is to disable xchat's dbus support.

this is why xchat 2.6.6 works fine in dapper & fiesty, because their dbus is fine.

DarkMageZ (darkmagez) wrote :

and no, i don't have a 100% way to replicate this. but it should have replicated by now or someone should have jumped up and down saying my package doesn't fix it.

Look good to me. The patch fixes the problem.

Subscribing ubuntu-universe-sponsors.

Changed in xchat:
status: Confirmed → In Progress
Michael Bienia (geser) wrote :

Please read and follow https://wiki.ubuntu.com/MOTU/SRU to get an updated xchat into edgy-updates.

Changed in xchat:
importance: Undecided → Medium
Ed Hargin (ed-hargin) wrote :

Xchat crash log. Crash occurs frequently for me - almost 100% of the time when closing Xchat with the "close window" button.

Edgy, with Xchat 2.6.6

Laudeci Oliveira (laudeci) wrote :

i got the same bug here and at home

skippy (skippy) wrote :

Using Ubuntu Edgy Eft on an amd64 system, I get this error fairly regularly when I quit by typing CTRL+Q.

Expect (rui-p-grr) wrote :

the samme thing crash when i close Xchat

R. Pereira Braga (rpereira) wrote :

The same error. I attached the log from bug report program.

anuparp (anuparp-b) wrote :

while I download xchat, It happens crashes

anuparp (anuparp-b) wrote :

while I download xchat, It happens crashes

bigestben (bigestben) wrote :

Same Problem

Ubuntu 6.10

get a crash dialog upon exiting. Doesn't appear to realise that it didn't crash but that i purposefully exited and asks if i want to reopen

Rudy (thundermaniak) wrote :

After using the [x] button, XChat closed and the popup error occured.

Ubuntu 6.10

TobiThu (tober) wrote :

crashed unexpected on quit

ChristianStamm (stammi) wrote :

I don't think you need another crash report so i don't attach one.
This bugs reminds me of a similar one in ekiga.

http://bugzilla.gnome.org/show_bug.cgi?id=359655

I can't really tell wether those bugs are related. I still hope it is helpful.

Alex Mayorga (alex-mayorga) wrote :

FWIW my crash report.

Zizou (machavez) wrote :

Same thing!

xdg (xdaveg) wrote :

Another crash log

Yatagan (franck-lienard) wrote :
John Dong (jdong) wrote :

Applying the patch seems to have cured this on a test Edgy machine.

In Ubuntu Edgy, XChat crashes frequently when the application is
closed. This has the effect of opening `apport', the bug report tool.
For XChat users, this bug is annoying and gives Ubuntu a lack of
polishing impression.

The bug is caused by the `gconf' feature of XChat. The solution, for
this version of XChat, is to disable `gconf' support completely. This
has the side effect of removing `xchat-remote', the irc:// protocol
handler of Firefox. However, this feature isn't known or used by most
XChat users, according to a small survey in the #ubuntu and
#ubuntu-offtopic done in December 2006. Most users would prefer to get
this bug fixed. Therefore, I think it's safe to disable XChat's
`gconf' support to fix this bug.

The patch disables XChat's `gconf' support and change the Maintainer
to Ubuntu MOTU Developers. The full package of the fixed version can
be found on REVU at: http://revu.tauware.de/details.py?upid=4534

please use 2.6.6-0ubuntu3.1~proposed1 as a version number and edgy-proposed as distribution.

Others than that I'm not too happy about removing features in SRUs, but since you've have researched this thoroughly that most of the users won't mind having this feature removed, I'm not objecting on this one. Maybe you could also make this clear in changelog that the irc://-protocol will be removed?

Thanks,
    Stefan.

StefanPotyra (sistpoty) wrote :

Oh, and please set yourself as assignee fro this bug.

I made the requested changes to the package's version. I also added a notice about the irc:// regression. And uploaded everything to REVU again.

> The patch disables XChat's `gconf' support and change the Maintainer
> to Ubuntu MOTU Developers.

Errata: The patch disables XChat's `dbus' support, not `gconf'.

Changed in xchat:
assignee: nobody → avassalotti
StefanPotyra (sistpoty) wrote :

+1 from me.

Reinhard Tartler (siretart) wrote :

after some clarification on #ubuntu-motu, +1 as well!

StefanPotyra (sistpoty) wrote :

Transferring to ubuntu-universe-sponsors, due to new motu-sru policy.

SerP (serp2002) wrote :

I have that problem too

Emmet Hikory (persia) wrote :

Apologies for the delay in review. I've reset the Status and Assignment to match current Ubuntu-Universe-Sponsors practices, which may attract sponsorship sooner.

Changed in xchat:
assignee: avassalotti → nobody
status: In Progress → Confirmed
Emmet Hikory (persia) wrote :

Fixed with the release of 2.6.8 in feisty.

Changed in xchat:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
status: Confirmed → Fix Released
Daniel Holbach (dholbach) wrote :

What's the state of things here - is the fix in Edgy still desired?

Scott Kitterman (kitterman) wrote :

edgy-proposed should not have the maintainer changed as the Edgy toolchain has not been extensively tested for that.

Personally I'm not convinced that crash on close is truly SRU worthy. After all, the crash (which technically qualifies for an SRU), with the exception of the crash dialogue, gets you where you wanted to go. Is eliminating having to close a crash dialogue box really worth the risk of an SRU?

I still think that a backported fix should be put in edgy-updates because
crashes are bad.

-- Asheesh.

Scott Kitterman (kitterman) wrote :

Yes, crashes are bad, but balance a crash on exit versus the risk associated
with fielding change in a released distribution. I'm certainly not the final
authority, but I don't think it makes sense.

Emmet Hikory (persia) wrote :

I've unsubscribed ubuntu-universe-sponsors based on the previous comment suggesting that an SRU may not be appropriate by a sponsor. Please discuss the suitability of this update further, and resubscribe ubuntu-universe-sponsors if there is consensus that an SRU is appropriate.

Asheesh Laroia (paulproteus) wrote :

I don't feel all that strongly about it; no big deal. (-:

--
Cheops' Law:
  Nothing ever gets built on schedule or within budget.

Changed in xchat:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers