Version: (using KDE KDE 3.3.0) Installed from: SuSE RPMs Compiler: gcc 3.3 OS: Linux When starting KDE, a window pops up indicating that kicker crashes. If I them try running kicker manualy in a xterm, kicker again crashes. Here is what the 'backtrace' displays Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1097704384 (LWP 5068)] [KCrash handler] #7 0x408de016 in KCmdLineArgs::isSet () from /opt/kde3/lib/libkdecore.so.4 #8 0x41ab0734 in MapWidget::load () from /opt/kde3/lib/kde3/ww_panelapplet.so #9 0x41ab7a43 in typeinfo name for ClockDialog () from /opt/kde3/lib/kde3/ww_panelapplet.so
sorry, the stacktrace is pretty useless as you seem to miss any kind of debug symbols and it works fine here.
I have no doubt that it works flawlessly at YOUR computer, but what I want to know is why it does not work on MY computer. What is it exactly that you need to be able to determine why it crashes on my system? I only sent what that error reporting utility (in KDE) gave me. jly -----Original Message----- From: owner@bugs.kde.org [mailto:owner@bugs.kde.org]On Behalf Of Stephan Kulow Sent: Saturday, September 04, 2004 1:09 AM To: Yanez, Juan Subject: [Bug 88802] Kicker crashes when starting KDE ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. http://bugs.kde.org/show_bug.cgi?id=88802 coolo kde org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID ------- Additional Comments From coolo kde org 2004-09-04 10:08 ------- sorry, the stacktrace is pretty useless as you seem to miss any kind of debug symbols and it works fine here.
The backtrace seems to point to kworldwatch, so reassigning and reopening in case the kworldwatch developer can do something about it.
fixed in cvs
*** Bug 92025 has been marked as a duplicate of this bug. ***