[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 193498] signal 11 sigsevv error on boot
From:       Martin Koller <kollix () aon ! at>
Date:       2009-06-01 12:15:29
Message-ID: 20090601121529.2887112131 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=193498


Martin Koller <kollix@aon.at> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |kollix@aon.at
         Resolution|                            |WONTFIX




--- Comment #7 from Martin Koller <kollix aon at>  2009-06-01 14:15:24 ---
I had the same problem but only running KDE3.5.10.
I now found out that nspluginscan is crashing whenever it loads a plugin which
is linked against Qt4. I assume this is due to the fact that then you have 2 Qt
libraries loaded which share some equal symbols and the wrong one is used, e.g.
calling a function from Qt4 but the one from Qt3 was meant to be used.
I had such a plugin installed in my ~/.mozilla/plugins and when I removed this
one, nspluginscan did no longer crash.

You can check which one is the culprit by activating the KDE debugflag 1433 by
running kdebugdialog (assuming you have KDE3 libs built with debug
information).
If you don't have the debug version of the KDE3 libs, then you can check with
ldd <plugin-name>
in the directories where nspluginscan looks for - which you can configure in
konquerors settings/plugins dialog.
Also, in this dialog you can deactivate that the scan is run each time you log
into KDE.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

[prev in list] [next in list] [prev in thread] [next in thread]