Bug 86035

Summary: Crash when opening Konqueror with webshortcut
Product: [Applications] konqueror Reporter: Bram Schoenmakers <me>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Bram Schoenmakers 2004-07-26 20:40:56 UTC
Version:            (using KDE KDE 3.2.92)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2 
OS:                Linux

When I run Konqueror from the "Run command" dialog with a webshortcut, Konqueror crashes immediately. Without webshortcut, it works fine. Looking at the backtrace, I cannot decide it's a Konqueror problem or a kdelibs problem.

BT:

#5  <signal handler called>
#6  0x407d1edc in KIconLoader::loadIcon(QString const&, KIcon::Group, int, int, QString*, bool) const (this=0x8571120, _name=@0x17, group=Toolbar, size=22,
    state=2, path_store=0x0, canReturnNull=false)
    at /home/kde-devel/SRC/kdelibs/kdecore/kiconloader.cpp:554
#7  0x407d6a3d in KIconFactory::createPixmap(QIconSet const&, QIconSet::Size, QIconSet::Mode, QIconSet::State) (this=0x8648da8, mode_P=23)
    at /home/kde-devel/SRC/kdelibs/kdecore/kiconloader.cpp:1181
#8  0x40bebc26 in QIconSetPrivate::icon(QIconSet const*, QIconSet::Size, QIconSet::Mode, QIconSet::State) () from /usr/lib/qt/lib/libqt-mt.so.3
#9  0x40bec5a7 in QIconSet::pixmap(QIconSet::Size, QIconSet::Mode, QIconSet::State) const () from /usr/lib/qt/lib/libqt-mt.so.3
#10 0x405986d3 in KToolBarButton::drawButton(QPainter*) (this=0x8648ac8,
    _painter=0x8810418) at /usr/lib/qt/include/qwidget.h:731
#11 0x40cc6e96 in QButton::paintEvent(QPaintEvent*) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#12 0x40c634e0 in QWidget::event(QEvent*) () from /usr/lib/qt/lib/libqt-mt.so.3
#13 0x40bc22f5 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#14 0x40bc1965 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#15 0x40760406 in KApplication::notify(QObject*, QEvent*) (this=0xbffff550,
    receiver=0x8648ac8, event=0xbfffed10)
    at /home/kde-devel/SRC/kdelibs/kdecore/kapplication.cpp:495
#16 0x40b53224 in QETWidget::translatePaintEvent(_XEvent const*) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#17 0x40b4e737 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#18 0x40b6639f in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#19 0x40bd6446 in QEventLoop::enterLoop() () from /usr/lib/qt/lib/libqt-mt.so.3
#20 0x40bd62e8 in QEventLoop::exec() () from /usr/lib/qt/lib/libqt-mt.so.3
#21 0x40bc2571 in QApplication::exec() () from /usr/lib/qt/lib/libqt-mt.so.3
#22 0x41e1fe40 in kdemain (argc=23, argv=0x17)
    at /home/kde-devel/SRC/kdebase/konqueror/konq_main.cc:204
#23 0x40933956 in kdeinitmain (argc=23, argv=0x17) at konqueror_dummy.cc:2
#24 0x0804d175 in launch (argc=4, _name=0x810076c "konqueror",
    args=0x81007bb "/home/bram", cwd=0x81007bb "/home/bram", envc=29,
    envs=0x0, reset_env=true, tty=0x0, avoid_loops=false,
    startup_id_str=0x17 <Address 0x17 out of bounds>)
    at /home/kde-devel/SRC/kdelibs/kinit/kinit.cpp:599
#25 0x0804e243 in handle_launcher_request (sock=4)
    at /home/kde-devel/SRC/kdelibs/kinit/kinit.cpp:1163
#26 0x0804e8db in handle_requests (waitForPid=0)
    at /home/kde-devel/SRC/kdelibs/kinit/kinit.cpp:1354
#27 0x0804f9f2 in main (argc=3, argv=0xbffffc24, envp=0x17)
    at /home/kde-devel/SRC/kdelibs/kinit/kinit.cpp:1817
Comment 1 Stephan Kulow 2004-07-26 20:54:25 UTC
in any kind reproducible? Because if not: welcome to the world of heisenbugs. 
Did you restart your kdeinit after some make install?

*** This bug has been marked as a duplicate of 68528 ***
Comment 2 Bram Schoenmakers 2004-07-26 22:26:20 UTC
The compile-conditions were not perfect. I did a 'make install' from a running KDE 3.2.3 environment (to another prefix). I forgot to set the $KDEDIR to the installation prefix, it might have messed things up.