Plasma Desktop Keeps Crashing

[Xplorer4x4]

I clean installed Kubuntu 13.10, dual booted with windows 7. In GRUB 2 I now have 3 choices, core 3.5.0 - 25, 26, 27.

25 runs fine. With 26 and 27 it is as if the GUI is incompatible in some respect.
The display breaks down, images persist, and it quickly becomes unusable and switch off is the only resort.

Like I said before, what do you mean "core?" When you say "core" do you mean the Kernel?

[Xplorer4x4]

Maybe this provides some useful info.

Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1f493ee780 (LWP 2585))]

Thread 4 (Thread 0x7f1f29b56700 (LWP 2790)):
#0  0x00007f1f3cfc2d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f1f42911cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f1f42911d09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f1f3cfbee9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#4  0x00007f1f48ccecbd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f1f1eb26700 (LWP 2797)):
#0  0x00007f1f3c8bfc9e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f1f3c8bfea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f1f458bac46 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x00007f1f4588b2ef in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007f1f4588b578 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007f1f4578cb40 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007f1f4586b9df in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007f1f4578fb1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007f1f3cfbee9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#9  0x00007f1f48ccecbd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#10 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f1f1dc90700 (LWP 2802)):
#0  0x00007f1f48cc3303 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f1f3c8bfd84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f1f3c8bfea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f1f458bac46 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007f1f4588b2ef in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007f1f4588b578 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007f1f4578cb40 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007f1f4586b9df in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007f1f4578fb1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007f1f3cfbee9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007f1f48ccecbd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f1f493ee780 (LWP 2585)):
[KCrash Handler]
#5  0x00007f1f48d29f2d in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x00007f1f457ad9b9 in QListData::remove(int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007f1f4749de32 in ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#8  0x00007f1f458a1f8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007f1f475e2e6f in ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#10 0x00007f1f474b4d6c in ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#11 0x00007f1f475e34a1 in ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#12 0x00007f1f458a1f8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007f1f475d78ff in QListModelInterface::itemsRemoved(int, int) () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#14 0x00007f1f4742037f in QDeclarativeListModel::remove(int) () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#15 0x00007f1f475d64cb in ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#16 0x00007f1f475d65cf in QDeclarativeListModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#17 0x00007f1f47581018 in ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#18 0x00007f1f47582c86 in ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#19 0x00007f1f475835bb in ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
#20 0x00007f1f429880b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#21 0x00007f1f428841d0 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#22 0x00007f1f428612c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#23 0x00007f1f0ec176a8 in ?? ()
#24 0x0000000000000000 in ?? ()

[LCWyche]

I suppose I do mean kernel. I forgot to mention that both Win7 and Kubuntu 12.10 are 64bit.

[Xplorer4x4]

Seems this is QT related, not kernel related:
https://bugs.kde.org/show_bug.cgi?id=311871

[Xplorer4x4]

You need to review the sources.list file and any .list file in /etc/apt/sources.d/ and ensure that they all reference quantal as the release. If you find any other release referenced, you need to correct them to quantal. This could be the cause of your issues.

I looked in to this, it turns out steam does not offer a quantal specific repo and falls back to precise.I also had a PPA that seems to have gotten a URL change. I did update that PPA and left steam intact for now and it seems to be working fine. I don't think the precise vs quantal is an issue, atleast in this case. Rather the broken URL(which I noticed for awhile but thought they simply did not have a quantal build available yet).

Thanks everyone for the help. Looks like myself and others will be waiting on a fix from the QT devs.

[dmeyer]

I looked in to this, it turns out steam does not offer a quantal specific repo and falls back to precise.I also had a PPA that seems to have gotten a URL change. I did update that PPA and left steam intact for now and it seems to be working fine. I don't think the precise vs quantal is an issue, atleast in this case. Rather the broken URL(which I noticed for awhile but thought they simply did not have a quantal build available yet).

Thanks everyone for the help. Looks like myself and others will be waiting on a fix from the QT devs.

Mixing packages although usually discouraged, tends not to break your system as long as they aren't core packages.

[Xplorer4x4]

That's about what I expected, but thanks for the confirmation and thanks for trying to help trouble shoot this.

[LCWyche]

Thank you Xplorer4x4. Many of these bugs reports do resemble my problem. Guess I'll just have to wait for for a fix. Thanks again.