Bug 156851 - Kopete crashes X/compiz-fusion when opening MSN messages
Summary: Kopete crashes X/compiz-fusion when opening MSN messages
Status: RESOLVED NOT A BUG
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-28 17:20 UTC by Kenjiro Tanaka
Modified: 2008-01-29 17:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kenjiro Tanaka 2008-01-28 17:20:48 UTC
Version:            (using KDE 3.5.8)
Installed from:    Slackware Packages
OS:                Linux

This weekend I took some time to install and run compiz-fusion on my Slackware 12.0.

I start it (compiz) with "compiz --replace ccp & kde-window-decorator --replace &". KDE and all the programs run fine. Then I was using kopete (as I always did) and everything was OK till I received a message from a MSN contact. When I clicked the baloon to view the message, X crashed.

I restarted X, logged in my KDE, fired up kopete, everything OK. I can open an ICQ contact chat window or a gtalk (jabber) chat window with no problem. When I open ANY MSN chat window, it crashes again.

Bellow I put some extra information as NVidia driver version, the last lines of /var/log/Xorg.0.log and a "gdb log" of kopete.

gdb log of kopete (ran kopete, waited for it to finish connecting to all the accounts and then tried to open a MSN chat window):
=========
This GDB was configured as "i486-slackware-linux"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/kopete 
(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 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 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 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 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)
[Thread debugging using libthread_db enabled]
[New process 3688]
(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 debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1252349152 (LWP 3688)]

Program exited normally.
(gdb) MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
kopete: Fatal IO error: client killed
libkopete: WARNING: [virtual Kopete::PluginManager::~PluginManager()] Destructing plugin manager without going through the shutdown process! Backtrace is: 
libkopete: 
libkopete: WARNING: [virtual Kopete::PluginManager::~PluginManager()] Deleting stale plugin 'unnamed'
libkopete: WARNING: [virtual Kopete::Protocol::~Protocol()] Deleting protocol with existing accounts! Did the account unloading go wrong?
KCrash: Application 'kopete' crashing...
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
drkonqi: cannot connect to X server :0.0
=========

Xorg.0.log (last lines, because above those everything is OK):
=========
Backtrace:
0: X(xf86SigHandler+0x80) [0x80dbde0]
1: [0xffffe420]

Fatal server error:
Caught signal 11.  Server aborting
=========

NVidia driver version == 169.09


Need more info?

Thanks for your attention
Comment 1 Rex Dieter 2008-01-28 18:21:40 UTC
maybe I'm confused, *compiz* is crashing, and this is kopete's bug, how/why?
Comment 2 Kenjiro Tanaka 2008-01-28 18:36:04 UTC
Well, I THINK it has to do with Kopete because it only happens with Kopete, no other program made X crash. And, it only crashed when I opened a MSN contact window (for reading or sending a message). If I open an ICQ or Jabber (gtalk) contact, nothing happens.
Comment 3 Rex Dieter 2008-01-28 18:50:59 UTC
OK, but I think you'd make more progress taking this to compiz (it shouldn't be crashing, period).
Comment 4 Kenjiro Tanaka 2008-01-28 19:14:44 UTC
well, I've just sent a bug report to the compiz-fusion guys too. Let's see what happens ;)
Comment 5 Urs Wolfer 2008-01-28 22:17:32 UTC
Well, when I have running Kopete from KDE 3 in a KDE 4 session, it crashes KWin (with compositing activated) from time to time when opening MSN messages.
Comment 6 Matt Rogers 2008-01-29 02:06:09 UTC
Unless somebody can prove otherwise, this is not our problem so i'm closing as invalid. If you can, in fact, prove that this is a kopete problem, then please reopen
Comment 7 Kenjiro Tanaka 2008-01-29 17:30:53 UTC
OK, time to put some honor on the table.

It IS NOT Kopete's fault. I checked with Compiz-Fusion guys and they said the problem could be caused by NVidia's driver (I was using 169.09).

So I tried downgrading the driver to version 169.07, but the crash would still happen, the very same way. So I went further and downgraded the driver to version 100.14.19. After that I could use kopete normally withou a single problem in X, compiz, whatever.

So, it is NVidia's fault, not Kopete/KDE nor compiz.

I think the knowledge stays for all other people who might be having the same problems I HAD.

Thanks guys!