Bug 163305 - Plasma crashed when trying to install new theme
Summary: Plasma crashed when trying to install new theme
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: knewstuff (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Jeremy Whiting
URL:
Keywords:
: 163584 163650 164171 164523 164585 164672 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-06-05 21:50 UTC by Shrikant Khare
Modified: 2008-06-29 12:09 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace (13.30 KB, text/plain)
2008-06-07 06:59 UTC, Sebastian Sauer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Shrikant Khare 2008-06-05 21:50:53 UTC
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.2.1 gcc (GCC) 4.2.1 (SUSE Linux 10.3)
OS:                Linux

In the "Desktop Setting", when the "New Theme" button is clicked, GetHotNewStuff gets started and immediately plasma crashed.
Comment 1 Shrikant Khare 2008-06-05 21:51:14 UTC
Application: Plasma Workspace (plasma), signal SIGSEGV
[?1034h(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(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 0x2add93dc9d30 (LWP 4076)]
[New Thread 0x41802950 (LWP 4205)]
[New Thread 0x41001950 (LWP 4086)]
[New Thread 0x40800950 (LWP 4077)]
[KCrash handler]
#4  0x0000000001e96c10 in ?? ()
#5  0x00002add8b6f3752 in ?? () from /usr/lib64/libkdecore.so.5
#6  0x00002add8b6f3662 in KCompositeJobPrivate::~KCompositeJobPrivate ()
   from /usr/lib64/libkdecore.so.5
#7  0x00002add8a5ba2ab in ?? () from /usr/lib64/libkio.so.5
#8  0x00002add8b6f3ecd in KJob::~KJob () from /usr/lib64/libkdecore.so.5
#9  0x00002add8a5a8157 in KIO::FileCopyJob::~FileCopyJob ()
   from /usr/lib64/libkio.so.5
#10 0x00002add8cda2c5d in QObject::event () from /usr/lib64/libQtCore.so.4
#11 0x00002add8fc7cccf in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#12 0x00002add8fc834c5 in QApplication::notify () from /usr/lib64/libQtGui.so.4
#13 0x00002add8ab4fadb in KApplication::notify () from /usr/lib64/libkdeui.so.5
#14 0x00002add8cd95b84 in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#15 0x00002add8cd96e05 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib64/libQtCore.so.4
#16 0x00002add8cdbc100 in QEventDispatcherUNIX::processEvents ()
   from /usr/lib64/libQtCore.so.4
#17 0x00002add8fcf7e46 in QEventDispatcherX11::processEvents ()
   from /usr/lib64/libQtGui.so.4
#18 0x00002add8cd94f45 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#19 0x00002add8cd950b7 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#20 0x00002add95a9ac84 in ?? () from /usr/lib64/libknewstuff2.so.4
#21 0x00002add95a9ae0d in KNS::Engine::downloadDialogModal ()
   from /usr/lib64/libknewstuff2.so.4
#22 0x00002add9580f91e in ?? ()
   from /usr/lib64/kde4/plasma_containment_desktop.so
#23 0x00002add95807e7f in ?? ()
   from /usr/lib64/kde4/plasma_containment_desktop.so
#24 0x00002add8cda53eb in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#25 0x00002add9015dfb7 in QAbstractButton::clicked ()
   from /usr/lib64/libQtGui.so.4
#26 0x00002add8ff3948b in QAbstractButtonPrivate::emitClicked ()
   from /usr/lib64/libQtGui.so.4
#27 0x00002add8ff39b15 in QAbstractButtonPrivate::click ()
   from /usr/lib64/libQtGui.so.4
#28 0x00002add8ff39d11 in QAbstractButton::mouseReleaseEvent ()
   from /usr/lib64/libQtGui.so.4
#29 0x00002add8fcc28e8 in QWidget::event () from /usr/lib64/libQtGui.so.4
#30 0x00002add8ff3a2c0 in QAbstractButton::event ()
   from /usr/lib64/libQtGui.so.4
#31 0x00002add8ffbc448 in QPushButton::event () from /usr/lib64/libQtGui.so.4
#32 0x00002add8fc7cccf in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#33 0x00002add8fc836bb in QApplication::notify () from /usr/lib64/libQtGui.so.4
#34 0x00002add8ab4fadb in KApplication::notify () from /usr/lib64/libkdeui.so.5
#35 0x00002add8cd95b84 in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#36 0x00002add8fc81743 in QApplicationPrivate::sendMouseEvent ()
   from /usr/lib64/libQtGui.so.4
#37 0x00002add8fcd6947 in QETWidget::translateMouseEvent ()
   from /usr/lib64/libQtGui.so.4
#38 0x00002add8fcd5beb in QApplication::x11ProcessEvent ()
   from /usr/lib64/libQtGui.so.4
#39 0x00002add8fcf7dd2 in QEventDispatcherX11::processEvents ()
   from /usr/lib64/libQtGui.so.4
#40 0x00002add8cd94f45 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#41 0x00002add8cd950b7 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#42 0x00002add8cd97071 in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#43 0x00002add89d0fbee in kdemain () from /usr/lib64/libkdeinit4_plasma.so
#44 0x00002add9153eb54 in __libc_start_main () from /lib64/libc.so.6
#45 0x00000000004008d9 in _start ()
#0  0x00002add8d06cacf in waitpid () from /lib64/libpthread.so.0
Comment 2 Anne-Marie Mahfouf 2008-06-06 07:48:56 UTC
What kdelibs revision it it? 
Can you reproduce with download "New Wallpapers..."? Or any other KNS dialog?
Thanks in advance!
Comment 3 Sebastian Sauer 2008-06-07 06:59:34 UTC
Created attachment 25177 [details]
backtrace

The backtrace I catched while trying to reproduce it. It happened with the
systemsettings=>splash screen=>GHNS option and therefore seems to be a GHNS bug
rather then plasma one.
Comment 4 Sebastian Sauer 2008-06-07 07:03:59 UTC
@ Shrikant

But to be sure that it's really the same issue, could you please install the kdelibs debug-packages like explained at 
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and provide a more useful backtrace? Thanks in advance :)

p.s. change product from Plasma to kdelibs cause GHNS is in there?!
Comment 5 Anne-Marie Mahfouf 2008-06-10 08:18:29 UTC
Assigning to kdelibs/KNS
Comment 6 Anne-Marie Mahfouf 2008-06-15 20:30:38 UTC
*** Bug 164171 has been marked as a duplicate of this bug. ***
Comment 7 Anne-Marie Mahfouf 2008-06-15 20:40:17 UTC
Bug 164171 is closer to initial backtrace than Sebastian bt. Shrikant Khare can you provide a better backtrace with installing debug packages please? Thanks! 
Comment 8 Anne-Marie Mahfouf 2008-06-15 20:40:56 UTC
*** Bug 163584 has been marked as a duplicate of this bug. ***
Comment 9 Shrikant Khare 2008-06-16 09:49:17 UTC
I removed the plasma-theme-aya package from YaST Software Management (KDE:/UNSTABLE openSUSE 10.3 repository) and KHNS/plasma stopped crashing since; although it still slows the system down to a crawl with all the simultaneous http requests.

I have since switched to openSUSE 11.0 RC1 and compiled KDE4 from svn trunk. I should now be able to provide better backtraces.

Sorry for not being much help in this case.

Should I mark this bug as RESOLVED?
Comment 10 Shrikant Khare 2008-06-18 12:36:47 UTC
Does not crash anymore......

Look at my previous comment for more info

Thanks
Comment 11 Sebastian Sauer 2008-06-21 21:51:33 UTC
*** Bug 164585 has been marked as a duplicate of this bug. ***
Comment 12 Anne-Marie Mahfouf 2008-06-22 18:00:42 UTC
*** Bug 164672 has been marked as a duplicate of this bug. ***
Comment 13 Sebastian Sauer 2008-06-24 05:12:46 UTC
*** Bug 163650 has been marked as a duplicate of this bug. ***
Comment 14 Sebastian Sauer 2008-06-24 05:14:04 UTC
*** Bug 164523 has been marked as a duplicate of this bug. ***
Comment 15 Diederik van der Boor 2008-06-29 12:06:50 UTC
In KDE 4.1 beta 2 I still get a similar issue.

When opening GHNS in plasma, everything seams to be blocked when the downloading of previews starts. I haven't seen a crash dialog somewhere unfortunately.

What happens afterwards:
- plasma remains blocked
- restarting plasma gives errors, it can't contact KLauncher.
- any app trying to start something (e.g. the bug reporter) blocks for a few seconds until it times out with the same error about klauncher. (are these dbus calls synchronous?)
Comment 16 Diederik van der Boor 2008-06-29 12:09:18 UTC
Additional note, in `top` there aren't any processes hung at 100% or something like it.