Bug 191216

Summary: kded4 crashed during upgrade
Product: [Unmaintained] kdelibs Reporter: larsoanneli
Component: kdedAssignee: David Faure <faure>
Status: RESOLVED WORKSFORME    
Severity: crash CC: andresbajotierra, larsoanneli, zahl
Priority: NOR    
Version: 4.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description larsoanneli 2009-05-01 10:55:29 UTC 
Version:            (using KDE 4.1.4)
Compiler:          Only precompiled packages used from Ubuntu 8.10 upgrade handler 
OS:                Linux
Installed from:    Ubuntu Packages

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.10
DISTRIB_CODENAME=intrepid
DISTRIB_DESCRIPTION="Ubuntu 8.10"

$ kded4 --version
Qt: 4.4.3
KDE: 4.1.4 (KDE 4.1.4)
KDE Daemon: $Id: kded.cpp 901205 2008-12-24 16:51:16Z dfaure $

$ gnome-about
Version: 2.24.1
Distributor: Ubuntu
Build date: 10/24/2008

I was running standard update manager today by the gnome desktop interface. It was the 1:st time during last 2 days. Update manager still says that upgrade finished successfully, but produced a crashreport. I can't reproduce error because no more update to run than Ubuntu 9.04 to run in update manager. I looked into dpkg.log but didn't see any crashmessages. If of any interest, I can send the 200 lines dpkg.log for today.

Cutout of crashreport follows:

Program: KDE Daemon (kded4), signal SIGSEGV

Thread 1 (Thread 0xb61638d0 (LWP 7466)):
[KCrash Handler]
#6  0xb7e8ea18 in ?? () from /lib/tls/i686/cmov/libc.so.6
#7  0xb7e908c5 in malloc () from /lib/tls/i686/cmov/libc.so.6
#8  0xb743bf5d in qMalloc () from /usr/lib/libQtCore.so.4
#9  0xb748402d in QString::fromLatin1_helper () from /usr/lib/libQtCore.so.4
#10 0xb74d579d in QTextStream::operator<< () from /usr/lib/libQtCore.so.4
#11 0xb7c26c1c in ?? () from /usr/lib/libkio.so.5
#12 0xb7ca5084 in ?? () from /usr/lib/libkio.so.5
#13 0xb7ca4cfd in ?? () from /usr/lib/libkio.so.5
#14 0xb7ca5c5b in ?? () from /usr/lib/libkio.so.5
#15 0xb7ca5e80 in KDirWatch::~KDirWatch () from /usr/lib/libkio.so.5
#16 0xb7f80040 in ?? () from /usr/lib/libkdeinit4_kded4.so
#17 0xb7f822e0 in ?? () from /usr/lib/libkdeinit4_kded4.so
#18 0xb7f82379 in ?? () from /usr/lib/libkdeinit4_kded4.so
#19 0xb7f84ab3 in ?? () from /usr/lib/libkdeinit4_kded4.so
#20 0xb7546a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#21 0xb75477e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0xb75817a7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#23 0xb754d40e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#24 0xb754153f in QObject::event () from /usr/lib/libQtCore.so.4
#25 0xb6ac48ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#26 0xb6acc72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#27 0xb7a00d1d in KApplication::notify () from /usr/lib/libkdeui.so.5
#28 0xb7531e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#29 0xb755fd81 in ?? () from /usr/lib/libQtCore.so.4
#30 0xb755c520 in ?? () from /usr/lib/libQtCore.so.4
#31 0xb64f4718 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb64f7dc3 in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb64f7f81 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb755c478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#35 0xb6b5eea5 in ?? () from /usr/lib/libQtGui.so.4
#36 0xb753052a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#37 0xb75306ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#38 0xb7532da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#39 0xb6ac4767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#40 0xb7f85ec6 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#41 0x080485a2 in _start ()
Comment 1 A. Spehr 2009-05-07 13:32:08 UTC 
We don't need a log file, just a more complete version of this data. Follow the instructions here:
http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports

And then wait till you need more updates or something and see if it crashes. 

I'm tempted to say it is an *ubntu problem, since it involves their update manager, except it seems to be mostly kio calls. You should still look to see if there is anything in the bug reports on their site: bugs.launchpad.net
Comment 2 Dario Andres 2009-10-11 22:07:36 UTC 
Missing backtrace
Comment 3 larsoanneli 2009-10-12 01:23:51 UTC 
Hello Mr Dario.

I am sorry to say that I was not able to replay the crash. At the 10:th 
of may I got the system upgrade from Interpeid to Jaunty. I guess 
something in my system wasn't happy. During the upgrade it spend more 
than 4 hours. A normal clean install from CD goes for 35 min. I do have 
fast broadband as I can download an normal CD in less than 5 minutes. I 
have tried to recreate the crash on virtual systems (both Xen and 
Virtual Box) from the same original 8.10 CD as I installed my old system 
with back in February 2009.
I don't believe on bad hardware as I don't have trouble running the 9.04.

I guess that Mr Spehr assumed correct when saying *ubntu problem as I 
was running their updater.

I assume we can close this case as I don't know where to find the 
requested information and I'm unable to recreate situation.

/Big thanks for the teams effort.
/Lars


Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=191216
>
>
> Dario Andres <andresbajotierra@gmail.com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>                  CC|                            |andresbajotierra@gmail.com
>          Resolution|                            |BACKTRACE
>
>
>
>
> --- Comment #2 from Dario Andres <andresbajotierra gmail com>  2009-10-11 22:07:36 ---
> Missing backtrace
>
>
Comment 4 Dario Andres 2009-10-31 22:57:18 UTC 
Mr Lars:
Thanks for the feedback. it is likely that this could be an Ubuntu issue. In any case, that KDE version is a bit old, and some related crashes were also fixed, and the behaviour was improved.
I'm closing this as WORKSFORME.
Regards

Darío A.