Bug 155711 - Plasma Randomly Crashing When Idle
Summary: Plasma Randomly Crashing When Idle
Status: RESOLVED WORKSFORME
Alias: None
Product: knewsticker
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Frerich Raabe
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-14 02:37 UTC by Jay LaCroix
Modified: 2009-01-01 01:41 UTC (History)
1 user (show)

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


Attachments
Crash report (4.62 KB, text/plain)
2008-02-15 00:42 UTC, Alexey Chernov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jay LaCroix 2008-01-14 02:37:09 UTC
Version:            (using KDE KDE 4.0.0)
Installed from:    Ubuntu Packages
OS:                Linux

I am not sure why or what triggers this. Sometimes I just leave my KDE4 session idle to watch TV for a while, and I come back a few hours later and a crash message is on my screen. I do not have desktop effects turned on.

Here is the backtrace:
---
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(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 47568695868032 (LWP 8779)]
[New Thread 1090541904 (LWP 8822)]
[New Thread 1082149200 (LWP 8780)]
(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)
(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)
(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)
(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)
(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)
(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)
(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)
(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)
(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)
(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)
(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)
[KCrash handler]
#4  0x00002b436ae86134 in QString::realloc () from /usr/lib/libQtCore.so.4
#5  0x00002b436ae86325 in QString::realloc () from /usr/lib/libQtCore.so.4
#6  0x00002b436ae70198 in ?? () from /usr/lib/libQtCore.so.4
#7  0x00002b436ae86a0e in QString::replace () from /usr/lib/libQtCore.so.4
#8  0x00002b436cbde723 in ?? () from /usr/lib/libQtGui.so.4
#9  0x00002b436cbde851 in QGraphicsSimpleTextItem::setText ()
   from /usr/lib/libQtGui.so.4
#10 0x00002aaaab8131a2 in ?? ()
   from /usr/lib/kde4/lib/kde4/plasma_applet_knewsticker.so
#11 0x00002aaaab8139d2 in ?? ()
   from /usr/lib/kde4/lib/kde4/plasma_applet_knewsticker.so
#12 0x00002aaaab813af5 in ?? ()
   from /usr/lib/kde4/lib/kde4/plasma_applet_knewsticker.so
#13 0x00002b436af08770 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#14 0x00002b436af08bbb in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#15 0x00002b436af2bc38 in QTimeLine::finished () from /usr/lib/libQtCore.so.4
#16 0x00002b436ae91061 in ?? () from /usr/lib/libQtCore.so.4
#17 0x00002b436ae910e5 in QTimeLine::timerEvent ()
   from /usr/lib/libQtCore.so.4
#18 0x00002b436af09330 in QObject::event () from /usr/lib/libQtCore.so.4
#19 0x00002b436c6c6d51 in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#20 0x00002b436c6c7070 in QApplication::notify () from /usr/lib/libQtGui.so.4
#21 0x00002b436b9d5fa1 in KApplication::notify ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#22 0x00002b436aef7846 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#23 0x00002b436aefaa6d in ?? () from /usr/lib/libQtCore.so.4
#24 0x00002b436af22743 in ?? () from /usr/lib/libQtCore.so.4
#25 0x00002b436af1f60f in ?? () from /usr/lib/libQtCore.so.4
#26 0x00002b436ee7afd3 in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#27 0x00002b436ee7e2dd in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x00002b436ee7e80e in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#29 0x00002b436af1ef69 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#30 0x00002b436c757e07 in ?? () from /usr/lib/libQtGui.so.4
#31 0x00002b436aef4b31 in QEventLoop::processEvents ()
   from /usr/lib/libQtCore.so.4
#32 0x00002b436aef4c86 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#33 0x00002b436aef7ffc in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#34 0x00002b436c6c6928 in QApplication::exec () from /usr/lib/libQtGui.so.4
#35 0x00002b436a4b8f3b in kdemain ()
   from /usr/lib/kde4/lib/libkdeinit4_plasma.so
#36 0x00002b436a6fcb44 in __libc_start_main () from /lib/libc.so.6
#37 0x0000000000400649 in _start ()
#0  0x00002b436a778c3f in waitpid () from /lib/libc.so.6
Comment 1 Frerich Raabe 2008-01-22 11:34:46 UTC
Which of the two view modes (scrolling view and paging view) are you using?
Comment 2 Jay LaCroix 2008-01-22 14:27:11 UTC
Scrolling view right now.

By the way, how do I make it like I see in the KDE4 screenshots? Like a big
box with a list of links, rather than one scrolling at a time?

On 22 Jan 2008 10:34:46 -0000, Frerich Raabe <raabe@kde.org> wrote:

[bugs.kde.org quoted mail]
Scrolling view right now.<br><br>By the way, how do I make it like I see in the KDE4 screenshots? Like a big box with a list of links, rather than one scrolling at a time?<br><br><div class="gmail_quote">On 22 Jan 2008 10:34:46 -0000, Frerich Raabe &lt;
<a href="mailto:raabe@kde.org">raabe@kde.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">------- You are receiving this mail because: -------
<br>You reported the bug, or are watching the reporter.<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=155711" target="_blank">http://bugs.kde.org/show_bug.cgi?id=155711</a><br><br><br><br><br></div>------- Additional Comments From raabe kde org &nbsp;2008-01-22 11:34 -------
<br>Which of the two view modes (scrolling view and paging view) are you using?<br></blockquote></div><br>
Comment 3 Frerich Raabe 2008-01-22 15:33:44 UTC
For changing the scrolling mode, go to the preferences dialog (right-click onto the news ticker) and change the value of the 'Scrolling mode' combo box. There's a bug in there though which causes the GUI not to be updated correctly sometimes, so try changing the combo box value back and forth to make sure that you have the right mode selected.

Regarding the crash: you can run the news ticker (or any other plasmoid for that matter) in its own window (and its own process) using the 'plasmoidviewer' program. Try running 'plasmoidviewer clock' or 'plasmoidviewer knewsticker' to run the clock (or the news ticker) in its own window. That way you can avoid that your whole desktop crashes just because a single plasmoid has a problem.

Do you have any additional news sources configured for your news ticker, or just the default KDE news? I'll see whether I can reproduce this problem this evening.
Comment 4 Jay LaCroix 2008-01-22 16:30:20 UTC
I added Osnews.com to it, but that was after it started crashing for me. In
my experience it will crash with the default source only.

To reproduce it I think all you'd have to do is add it to your desktop, then
leave the room for a few hours. By the time you come back it might have
crashed.

The look of the news ticker I'm referring to is in this screenshot:
http://www.kde.org/announcements/4.0/screenshots/dashboard.jpg
I like that style alot better but I can't figure out how to make the news
ticker look like that. :(

On 22 Jan 2008 14:33:45 -0000, Frerich Raabe <raabe@kde.org> wrote:

[bugs.kde.org quoted mail]
I added <a href="http://Osnews.com">Osnews.com</a> to it, but that was after it started crashing for me. In my experience it will crash with the default source only.<br><br>To reproduce it I think all you&#39;d have to do is add it to your desktop, then leave the room for a few hours. By the time you come back it might have crashed.
<br><br>The look of the news ticker I&#39;m referring to is in this screenshot:<br><a href="http://www.kde.org/announcements/4.0/screenshots/dashboard.jpg">http://www.kde.org/announcements/4.0/screenshots/dashboard.jpg</a>
<br>I like that style alot better but I can&#39;t figure out how to make the news ticker look like that. :(<br><br><div class="gmail_quote">On 22 Jan 2008 14:33:45 -0000, Frerich Raabe &lt;<a href="mailto:raabe@kde.org">raabe@kde.org
</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.
<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=155711" target="_blank">http://bugs.kde.org/show_bug.cgi?id=155711</a><br><br><br><br><br>------- Additional Comments From raabe kde org &nbsp;2008-01-22 15:33 -------<br>For changing the scrolling mode, go to the preferences dialog (right-click onto the news ticker) and change the value of the &#39;Scrolling mode&#39; combo box. There&#39;s a bug in there though which causes the GUI not to be updated correctly sometimes, so try changing the combo box value back and forth to make sure that you have the right mode selected.
<br><br>Regarding the crash: you can run the news ticker (or any other plasmoid for that matter) in its own window (and its own process) using the &#39;plasmoidviewer&#39; program. Try running &#39;plasmoidviewer clock&#39; or &#39;plasmoidviewer knewsticker&#39; to run the clock (or the news ticker) in its own window. That way you can avoid that your whole desktop crashes just because a single plasmoid has a problem.
<br><br>Do you have any additional news sources configured for your news ticker, or just the default KDE news? I&#39;ll see whether I can reproduce this problem this evening.<br></blockquote></div><br>
Comment 5 Frerich Raabe 2008-01-22 16:48:12 UTC
What you see on that screenshot (in the upper right corner) isn't the news ticker. That's some other plasmoid (I think it's called "news" or something like that).
Comment 6 Jay LaCroix 2008-01-22 16:52:00 UTC
Is that available in the default release? I don't have it, and I did install
every package tagged as "4.0.0".

On 22 Jan 2008 15:48:12 -0000, Frerich Raabe <raabe@kde.org> wrote:

[bugs.kde.org quoted mail]
Is that available in the default release? I don&#39;t have it, and I did install every package tagged as &quot;4.0.0&quot;.<br><br><div class="gmail_quote">On 22 Jan 2008 15:48:12 -0000, Frerich Raabe &lt;<a href="mailto:raabe@kde.org">
raabe@kde.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.
<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=155711" target="_blank">http://bugs.kde.org/show_bug.cgi?id=155711</a><br><br><br><br><br>------- Additional Comments From raabe kde org &nbsp;2008-01-22 16:48 -------<br>What you see on that screenshot (in the upper right corner) isn&#39;t the news ticker. That&#39;s some other plasmoid (I think it&#39;s called &quot;news&quot; or something like that).
<br></blockquote></div><br>
Comment 7 Alexey Chernov 2008-02-15 00:40:49 UTC
I have this bug with knewsticker, too. Plasma suddenly crashes. I tried to commit it as plasma bug here: http://bugs.kde.org/show_bug.cgi?id=156207, but it appeared to be knewsticker problem. I've got crash report, I hope it helps.
Comment 8 Alexey Chernov 2008-02-15 00:42:06 UTC
Created attachment 23579 [details]
Crash report
Comment 9 Frerich Raabe 2008-02-15 01:01:26 UTC
Is this with KDE 4.0.1? I fixed a bug in KNewsTicker's "Paging" view (which you're using apparently) for KDE 4.0.1, and the back trace you're posting looks pretty similar to the one I fixed.
Comment 10 Alexey Chernov 2008-02-15 13:25:04 UTC
Yes, I use KDE 4.0.1 with "Paging" view, that's true. I previously used KDE 4.0.0, but I removed it with 'make uninstall' with every package before compiling 4.0.1. Could it be the problem in settings in ~/.kde? I didn't changed it since KDE 4.0.0. I will delete settings to test it and write a result here.
Comment 11 Alexey Chernov 2008-02-15 15:31:01 UTC
Well, removing ~/.kde/share/config/knewstickerrc made no effect. It's still crashing plasma...
Comment 12 Jay LaCroix 2008-04-03 23:40:50 UTC
As of KDE 4.0.3 this still happens to me. 

In an unrelated note, I see alot of people with an RSS news reader, that doesn't scroll, but is intead a rectangle box with the news items as a list. Is there any way to get this in KDE4.0.3 or make it available in whatever the next KDE4 release is?
Comment 13 Dario Andres 2008-12-31 13:51:02 UTC
Can you still reproduce this bug with a recent KDE (4.1.3 / 4.2beta2 / 4.2svn) ? Thanks :)
Comment 14 Jay LaCroix 2009-01-01 00:11:32 UTC
No, I cannot reproduce this bug as of right now.
Comment 15 Dario Andres 2009-01-01 01:41:51 UTC
Closing as WORKSFORME.Please re-open the bug report if you experience the same crash again. Thanks