> Getting all the debuginfos: debuginfo-install kdebase-workspace
> (no debugging symbols found)
> Using host libthread_db library "/lib/libthread_db.so.1".
> (no debugging symbols found)
> (no debugging symbols found)


A backtrace with the above lines is useless, please install the debuginfo 
packages provided by your distro in order to provide useful backtraces 
including debugging symbols.

I installed the following debug packages:

yum list | grep installed | grep debuginfo
extragear-plasma-debuginfo.i386          4.0.0-1.fc8            installed       
kdebase-debuginfo.i386                   6:4.0.1-3.fc8.1        installed       
kdebase-runtime-debuginfo.i386           4.0.1-1.fc8.1          installed       
kdebase-workspace-debuginfo.i386         4.0.1-6.fc8            installed       
kdelibs-debuginfo.i386                   6:4.0.1-4.fc8.1        installed    


I do not know if I should have installed more packages as you were not exactly clear what debug packages to install to uncover details for this specific crash. 


This is the output of the KDE backtrace with debugging symbols loaded (it does not give me the "no debugging symbols" warning):

Using host libthread_db library "/lib/libthread_db.so.1".
Getting all the debuginfos: debuginfo-install kdebase-workspace
[Thread debugging using libthread_db enabled]
[New Thread -1208678672 (LWP 5198)]
[New Thread 107096976 (LWP 5216)]
[New Thread 80051088 (LWP 5199)]
[KCrash handler]
#6  0x008caee7 in XVisualIDFromVisual () from /usr/lib/libX11.so.6
#7  0x023bb9d3 in QWidget::create () from /usr/lib/libQtGui.so.4
#8  0x005bc8e0 in KX11EmbedContainer::prepareFor (this=0x88a2fe8, w=44040195)
    at /usr/src/debug/kdebase-workspace-4.0.1/plasma/applets/systemtray/systemtraycontainer.cpp:86
#9  0x005bccde in SystemTrayContainer (this=0x88a2fe8, clientId=44040195, 
    parent=0x935ed78)
    at /usr/src/debug/kdebase-workspace-4.0.1/plasma/applets/systemtray/systemtraycontainer.cpp:39
#10 0x005bd505 in SystemTrayWidget::x11Event (this=0x935ed78, 
    event=0xbfaaa718)
    at /usr/src/debug/kdebase-workspace-4.0.1/plasma/applets/systemtray/systemtraywidget.cpp:91
#11 0x023ce970 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#12 0x023f3fb4 in ?? () from /usr/lib/libQtGui.so.4
#13 0x07ec91ac in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#14 0x07ecc5ef in ?? () from /lib/libglib-2.0.so.0
#15 0x07eccb55 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#16 0x00aa3d48 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#17 0x023f3d65 in ?? () from /usr/lib/libQtGui.so.4
#18 0x00a81d31 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#19 0x00a81e3c in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#20 0x00a841ea in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#21 0x02379e87 in QApplication::exec () from /usr/lib/libQtGui.so.4
#22 0x002a4026 in kdemain (argc=1, argv=0xbfaaab54)
    at /usr/src/debug/kdebase-workspace-4.0.1/plasma/plasma/main.cpp:54
#23 0x08048792 in main (argc=)
    at /usr/src/debug/kdebase-workspace-4.0.1/i386-redhat-linux-gnu/plasma/plasma/plasma-qgv_dummy.cpp:3
#24 0x00e07390 in __libc_start_main () from /lib/libc.so.6
#25 0x080486b1 in _start ()
#0  0x00110410 in __kernel_vsyscall ()

Hi,

I did post a new backtrace regarding that problem on my KDE4 installation on
Fedora 8 x86 (32 bits) in the bug report, was this more useful to you ?

Regards,

Goffredo Marocchi


On 21 Feb 2008 18:31:39 -0000, S. Burmeister <sven.burmeister@gmx.net>
wrote:

> ------- You are receiving this


mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=158177
>
>
>
>
> ------- Additional Comments From sven.burmeister gmx net  2008-02-21 19:31
> -------
> > Getting all the debuginfos: debuginfo-install kdebase-workspace
> > (no debugging symbols found)
> > Using host libthread_db library "/lib/libthread_db.so.1".
> > (no debugging symbols found)
> > (no debugging symbols found)
>
>
> A backtrace with the above lines is useless, please install the debuginfo
> packages provided by your distro in order to provide useful backtraces
> including debugging symbols.
>

Hi,<br><br>I did post a new backtrace regarding that problem on my KDE4 installation on Fedora 8 x86 (32 bits) in the bug report, was this more useful to you ?<br><br>Regards,<br><br>Goffredo Marocchi<br><br><br><div class="gmail_quote">
On 21 Feb 2008 18:31:39 -0000, S. Burmeister &lt;<a href="mailto:sven.burmeister@gmx.net">sven.burmeister@gmx.net</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&nbsp;</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">mail because: -------<br>
You reported the bug, or are watching the reporter.<br>
<br>
<a href="http://bugs.kde.org/show_bug.cgi?id=158177" target="_blank">http://bugs.kde.org/show_bug.cgi?id=158177</a><br>
<br>
<br>
<br>
<br>
------- Additional Comments From sven.burmeister gmx net &nbsp;2008-02-21 19:31 -------<br>
&gt; Getting all the debuginfos: debuginfo-install kdebase-workspace<br>
&gt; (no debugging symbols found)<br>
&gt; Using host libthread_db library &quot;/lib/libthread_db.so.1&quot;.<br>
&gt; (no debugging symbols found)<br>
&gt; (no debugging symbols found)<br>
<br>
<br>
A backtrace with the above lines is useless, please install the debuginfo<br>
packages provided by your distro in order to provide useful backtraces<br>
including debugging symbols.<br>
</blockquote></div><br>

Hi Goffredo,

does this still happen for you with KDE 4.0.2?

probably related are;
* bug #158991
* bug #158526
* bug #158251
* bug #158215

Hi Sebastian,

as soon as the KDE 4.0.2 packages are out for Fedora 8 (from the KDE SIG)
I'll post an update to the bug.

Best Regards,
Goffredo

On 10 Mar 2008 00:23:54 -0000, Sebastian Sauer <mail@dipe.org> wrote:

[bugs.kde.org quoted mail]
Hi Sebastian,<br><br>as soon as the KDE 4.0.2 packages are out for Fedora 8 (from the KDE SIG) I&#39;ll post an update to the bug.<br><br>Best Regards,<br>Goffredo<br><div class="gmail_quote"><br>On 10 Mar 2008 00:23:54 -0000, Sebastian Sauer &lt;<a href="mailto:mail@dipe.org">mail@dipe.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=158177" target="_blank">http://bugs.kde.org/show_bug.cgi?id=158177</a><br>
<br>
<br>
<br>
<br>
</div>------- Additional Comments From mail dipe org &nbsp;2008-03-10 01:23 -------<br>
Hi Goffredo,<br>
<br>
does this still happen for you with KDE 4.0.2?<br>
<br>
probably related are;<br>
* bug #158991<br>
* bug #158526<br>
* bug #158251<br>
* bug #158215<br>
</blockquote></div><br>

*** This bug has been marked as a duplicate of 159167 ***

Created attachment 29859 [details]
plasma crash report

Comment on attachment 29859 [details]
plasma crash report

Plasma crashes in the following reproductible situation:
I login to my kubuntu intrepid ibex desktop with lastest nvidia propietary driver and Compiz running.
I see just a single virtual desktop in the downside panel bar even when the system is set to four virtual desktops both in compiz settings and in desktop system settings. When I hit Ctrl+arrow_pad_right in order to switch to the second virtual desktop, plasma crashes and raised the error report attached.
Please give a solution.
Thank you

"Please give a solution. "

don't use compiz or install a newer kde build.