Bug 193498

Summary:	signal 11 sigsevv error on boot
Product:	[Applications] konqueror	Reporter:	Abe Ezekowitz <aezekowitz>
Component:	nspluginscan	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED INTENTIONAL
Severity:	crash	CC:	andresbajotierra, estellnb, kollix
Priority:	NOR
Version:	3.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Abe Ezekowitz 2009-05-21 14:25:10 UTC

Version:            (using KDE 4.2.85)
OS:                Linux
Installed from:    Ubuntu Packages

here is the output from the backtrace. I was simply booting the computer.

(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 Thread 0xb69d7700 (LWP 4088)]
(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)
[KCrash handler]
#6  0xb77ae896 in memcpy () from /lib/tls/i686/cmov/libc.so.6
#7  0x086abe70 in ?? ()
#8  0xb7340e4e in QString::fromUtf8 () from /usr/lib/libqt-mt.so.3
#9  0xb7662092 in KLocale::translate_priv ()
   from /opt/kde3/lib/libkdecore.so.4
#10 0xb76638c4 in KLocale::translate () from /opt/kde3/lib/libkdecore.so.4
#11 0xb7625b46 in i18n () from /opt/kde3/lib/libkdecore.so.4
#12 0x0804bcb1 in tryCheck ()
#13 0x0804d7ba in scanDirectory ()
#14 0x0804ee56 in main ()

Comment 1 Dario Andres 2009-05-22 03:56:15 UTC

What application crashed? The backtrace is from a KDE3 application.
Can you reproduce the crash at will?
Thanks

Comment 2 Dario Andres 2009-05-22 16:26:12 UTC

Marking a NEEDSINFO/INVALID

Comment 3 Abe Ezekowitz 2009-05-22 16:47:16 UTC

There is no indication of what application actually crashes. I am using kde 3 under Jaunty Jackalope. This began a few days ago after an update to kde 4.3 Beta 1

Comment 4 Dario Andres 2009-05-22 16:51:09 UTC

The crash handler dialog should said which application crashed. I'm also guessing you have some KDE3 applications installed.

Comment 5 Abe Ezekowitz 2009-05-22 16:58:35 UTC

nspluginscan is what crashed, according to what it said. I do have a lot of kde 3 apps because I am using KDE 3 in Jaunty.

Comment 6 Dario Andres 2009-05-22 17:18:32 UTC

Oh, so you are using KDE3.
The confusion started on the first line "Version:            (using KDE 4.2.85)
"

Reassigning to nspluginscan

Comment 7 Martin Koller 2009-06-01 14:15:24 UTC

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.

Comment 8 Dario Andres 2009-08-29 14:15:38 UTC

*** Bug 205575 has been marked as a duplicate of this bug. ***