Bug 86812 - konqueror crashed on startup
Summary: konqueror crashed on startup
Status: RESOLVED DUPLICATE of bug 68528
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-09 00:36 UTC by Christian Spitzlay
Modified: 2004-08-10 08:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Spitzlay 2004-08-09 00:36:54 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc-Version 3.3.4 (Debian 1:3.3.4-3) 
OS:                Linux

Konqi just crashed on me when I clicked the kicker icon. 
(I'm not sure if I clicked the webbrowsing profile or the file manager profile
because the icons are next to each other.  Anyway, the file manager profile 
loads my home dir, and the webbrowsing profile starts up empty, so there's 
no special start page.)

The crash is not reproducible.

Here's the trace: 

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1099180608 (LWP 5607)]
[KCrash handler]
#3  0x40fb421c in QString (this=0xbfffe510, s=@0x14) at tools/qstring.cpp:1393
#4  0x4077973f in KIconEffect::fingerprint ()
   from /home/kdedev/devel/kde/lib/libkdecore.so.4
#5  0x40785d96 in KIconLoader::loadIcon ()
   from /home/kdedev/devel/kde/lib/libkdecore.so.4
#6  0x40788fff in KIconFactory::createPixmap ()
   from /home/kdedev/devel/kde/lib/libkdecore.so.4
#7  0x40c02b28 in QIconSetPrivate::icon (this=0x8a082e0, iconSet=0xbfffe980, 
    size=Small, mode=Disabled, state=Off) at kernel/qiconset.cpp:195
#8  0x40c0329c in QIconSet::pixmap (this=0xbfffe980, size=Small, 
    mode=Disabled, state=Off) at kernel/qiconset.cpp:520
#9  0x4055a253 in KToolBarButton::drawButton ()
   from /home/kdedev/devel/kde/lib/libkdeui.so.4
#10 0x40cd2248 in QButton::paintEvent (this=0x89fb168)
    at widgets/qbutton.cpp:887
#11 0x40c75fd9 in QWidget::event (this=0x89fb168, e=0xbfffed90)
    at kernel/qwidget.cpp:4774
#12 0x40bda5dd in QApplication::internalNotify (this=0xbffff5c0, 
    receiver=0x89fb168, e=0xbfffed90) at kernel/qapplication.cpp:2620
#13 0x40bda273 in QApplication::notify (this=0xbffff5c0, receiver=0x89fb168, 
    e=0xbfffed90) at kernel/qapplication.cpp:2508
#14 0x40714723 in KApplication::notify ()
   from /home/kdedev/devel/kde/lib/libkdecore.so.4
#15 0x40b70140 in QApplication::sendSpontaneousEvent (receiver=0x89fb168, 
    event=0xbfffed90) at qapplication.h:494
#16 0x40b6b571 in QETWidget::translatePaintEvent (this=0x89fb168, 
    event=0xbffff150) at kernel/qapplication_x11.cpp:5603
#17 0x40b66e58 in QApplication::x11ProcessEvent (this=0xbffff5c0, 
    event=0xbffff150) at kernel/qapplication_x11.cpp:3456
#18 0x40b813f7 in QEventLoop::processEvents (this=0x812c638, flags=4)
    at kernel/qeventloop_x11.cpp:192
#19 0x40beeb69 in QEventLoop::enterLoop (this=0x812c638)
    at kernel/qeventloop.cpp:198
#20 0x40beea82 in QEventLoop::exec (this=0x812c638)
    at kernel/qeventloop.cpp:145
#21 0x40bda749 in QApplication::exec (this=0xbffff5c0)
    at kernel/qapplication.cpp:2743
#22 0x41b4c79c in kdemain ()
   from /home/kdedev/devel/kde/lib/libkdeinit_konqueror.so
#23 0x41ae5976 in kdeinitmain ()
   from /home/kdedev/devel/kde/lib/kde3/konqueror.so
#24 0x0804cc76 in launch ()
#25 0x0804e16b in handle_launcher_request ()
#26 0x0804e68e in handle_requests ()
#27 0x0804f70d in main ()
Comment 1 Christian Spitzlay 2004-08-09 00:49:49 UTC
Forgot to mention it:  

The version is KDE_3_3_BRANCH from 2004-08-07. 
Comment 2 George Staikos 2004-08-09 01:01:04 UTC
Does anyone actually understand this crash yet?  It's very persistent.

*** This bug has been marked as a duplicate of 68528 ***
Comment 3 Stephan Kulow 2004-08-09 10:50:18 UTC
Did you a clean build and restarted KDE before you did that?
Comment 4 Christian Spitzlay 2004-08-10 08:04:58 UTC
I had removed the complete install dir before starting the build, 
and the compilation script did a "make clean" in each of the CVS modules as part of the process.  

I was not compiling KDE itself at the time but had just finished compiling and installing a Qt application (prokyon3).   As far as I can tell the whole machine had been rebooted after the KDE build (and before the crash).  

One strange thing I noticed about the self-built version: I have the regular Debian unstable KDE 3.2.3 packages installed alongside, and there are two control center modules in my build that don't work (Audio CD and Mixer).  The error message suggests a problem with an old version of the modules or a failed update from a prior version (In the explanation to the message that says: "The library kcm_audio.la could not be found in your PATH").  

Taking into account that the build was clean this seems to indicate a misconfiguration that causes the kcm_audio.la (which only exists in the Debian packages) to be found by my own KDE build.   Do I interpret this correctly? Maybe that is related?