Qtcurve-->Configure Aqua Apply then Curve Apply causes plasma desktop crash RC2

Qtcurve crashes kwin and a host of other programs when changing presets while using qtcurve.

KDE SC 4.6

I need more people to help out. Please install qtcurve and then try the following steps to confirm if this is on 32-bit and 64-bit.

**My Results with GeForce 8600 GTS
Driver: NVIDIA-Linux-x86_64-270.29.run
**
**Reproducible: Always **

**Steps to Reproduce: **

  1. Select Configure Desktop → Application Appearance
  2. Select Qtcurve -->Configure–> Aqua OK and Apply buttons
  3. Select Qtcurve -->Configure–> Curve OK and Apply buttons
  4. Plasma desktop crashes

Please see Bugzilla link:

https://bugzilla.novell.com/show_bug.cgi?id=675651

Cheers!

Romanator

I have tried, but cannot replicate this.

Three machines. Clean KDE installs of RC2.1 from the x86_64 DVD. Added qtcurve-kde, then followed your recipe. Then installed kernel-desktop-2.6.38-rc6 from Kernek:HEAD and repeated. Still no Plasma crash.

AMD 950e, 8GiB, integrated NVIDIA GeForce 8200
Intel Atom 330, 2GiB, integrated NVIDIA Ion
Intel SU4100, 4GiB, ATI Mobility Radeon HD4330 (this also has switchable Intel graphics, but I cannot get it to work)

There is no non-Free software on any of these installs – I am testing for work, not home use. Have you tried this without the proprietory graphics driver? Perhaps the problem is with NVIDIA rather than openSuSE or KDE?

Could be Nvidia. I’ll uninstall the Nvidia frivers and see what happens.

You probably mean “Agua” and not “Aqua.” But still it totally crashes stuff.

Sorry for the short reply, but my keyboard yielded up the ghost.

After changing to Agua and applying lots of processes crashed. Firefox was not one of them though.

Anyway:

Thank you for replying. I thought I was seeing things. The problem also exists on openSUSE RC2.

You’re right the name is Agua not Aqua.

So, I uninstalled the Nvidia driver, set up Nouveau and I’m still getting about 55 windows pop up.
Various programs from akonadi to kwin to kdeinit to neponuk. And I’m running 64-bit.

I’m going to reinstall again. Any one else out there using an Nvidia card experiencing this bug?

I am not sure this has anything got to do with Agua or QtCurve itself. I have meanwhile experience similar mis-behaviour when switching to other QtCurve configs, or totally different Styles, e.g. Plastique.

I downgraded the NVIDIA drivers from 270.29 (installed the hard way) to NVIDIA 260.19.36 from the repositories. So that now my configuration is as follows:

  • KDE SC 4.6.0

  • openSUSE 11.3; 64-bit

  • QtCurve 1.8.4

  • GPU: NVIDIA GeForce 6100; onboard

  • Drivers: NVIDIA 260.19.36

It is the same story as it was before. Lots of crashes. But now I have collected crash-information, some of which is flagged as “may be useful” and some flagged as “is useful”.

I only have no real idea where to best put this info. :shame:

I have created a Bugzilla report. If you haven’t created an account, create one so that you can add comments and submit files.

One you have created an account, please add your comments to my bug report.

Please see Bugzilla link:

https://bugzilla.novell.com/show_bug.cgi?id=675651

Btw I have checked kde.org and there appears to be a fix coming in 4.6.1.

I have created a Bugzilla report. If you haven’t created an account, create one so that you can add comments and submit files.

One you have created an account, please add your comments to my bug report.

Please see Bugzilla link:

https://bugzilla.novell.com/show_bug.cgi?id=675651

Btw I have checked kde.org and there appears to be a fix coming in 4.6.1.

OK, done. I hope it is not too noobish.

That sound good. :slight_smile:

Thank you for contributing. I welcome anyone out there with an Nvidia graphics card. If you are experiencing crashes with qtcurve presets to add to the Bugzilla report.

Hopefully, we’ll get a fix for this issue with qtcurve crashes when changing qtcurve presets.

Here’s the link:

https://bugzilla.novell.com/show_bug.cgi?id=675651

Cheers!

Romanator

It’s very quiet. Nobody is responding to the Bugzilla report. I know I’m not the only person submitting bug reports. Usually when reports are set to major a user gets a response.

Here’s my crash report:

Application: Plasma Desktop Shell (kdeinit4), signal: Aborted
[Current thread is 1 (Thread 0x7fa438785760 (LWP 5561))]

Thread 3 (Thread 0x7fa414c66700 (LWP 5566)):
#0  0x00007fa435e8e8fe in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x00007fa435e27f2e in _L_lock_9927 () from /lib64/libc.so.6
#2  0x00007fa435e262d1 in free () from /lib64/libc.so.6
#3  0x00007fa432ce5e08 in ?? () from /lib64/libglib-2.0.so.0
#4  0x00007fa437469dc8 in QEventDispatcherGlib::~QEventDispatcherGlib() () from /usr/lib64/libQtCore.so.4
#5  0x00007fa437469e29 in QEventDispatcherGlib::~QEventDispatcherGlib() () from /usr/lib64/libQtCore.so.4
#6  0x00007fa437354da4 in ?? () from /usr/lib64/libQtCore.so.4
#7  0x00007fa437355a66 in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007fa4370c6a3f in start_thread () from /lib64/libpthread.so.0
#9  0x00007fa435e8167d in clone () from /lib64/libc.so.6
#10 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fa40ffff700 (LWP 5568)):
#0  0x00007fa435e78503 in poll () from /lib64/libc.so.6
#1  0x00007fa432cea114 in ?? () from /lib64/libglib-2.0.so.0
#2  0x00007fa432cea650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007fa437469976 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007fa43743e052 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007fa43743e265 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007fa4373531e4 in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007fa43741f968 in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007fa437355a5e in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007fa4370c6a3f in start_thread () from /lib64/libpthread.so.0
#10 0x00007fa435e8167d in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa438785760 (LWP 5561)):
[KCrash Handler]
#6  0x00007fa435de0ab5 in raise () from /lib64/libc.so.6
#7  0x00007fa435de1fb6 in abort () from /lib64/libc.so.6
#8  0x00007fa435e1bdd3 in __libc_message () from /lib64/libc.so.6
#9  0x00007fa435e213b6 in malloc_printerr () from /lib64/libc.so.6
#10 0x00007fa435e262dc in free () from /lib64/libc.so.6
#11 0x00007fa4250ee92b in QtCurve::Style::freeColors (this=0x719180) at /usr/src/debug/QtCurve-KDE4-1.8.4/style/qtcurve.cpp:1407
#12 0x00007fa4250f0d3c in QtCurve::Style::init (this=0x719180, initial=false) at /usr/src/debug/QtCurve-KDE4-1.8.4/style/qtcurve.cpp:1017
#13 0x00007fa4250f28f7 in QtCurve::Style::kdeGlobalSettingsChange (this=0x719180, type=<value optimized out>) at /usr/src/debug/QtCurve-KDE4-1.8.4/style/qtcurve.cpp:13648
#14 0x00007fa425141e24 in QtCurve::Style::qt_metacall (this=0x719180, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x7fffd7fbec10) at /usr/src/debug/QtCurve-KDE4-1.8.4/build/style/moc_qtcurve.cxx:106
#15 0x00007fa434293b68 in ?? () from /usr/lib64/libQtDBus.so.4
#16 0x00007fa43429ec1f in ?? () from /usr/lib64/libQtDBus.so.4
#17 0x00007fa437452a6a in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x00007fa4365edd14 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00007fa4365f622a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00007fa4380e29e6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x00007fa43743ebfc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x00007fa4374423f5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#23 0x00007fa437469783 in ?? () from /usr/lib64/libQtCore.so.4
#24 0x00007fa432ce9bd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#25 0x00007fa432cea3b0 in ?? () from /lib64/libglib-2.0.so.0
#26 0x00007fa432cea650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#27 0x00007fa43746991f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007fa436692d8e in ?? () from /usr/lib64/libQtGui.so.4
#29 0x00007fa43743e052 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x00007fa43743e265 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x00007fa4374426ab in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x00007fa426228da8 in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so
#33 0x00000000004075e9 in _start ()

If they can’t fix this major crash when changing QtCurve presets. I think the best thing to do is to remove the file(s) until this is resolved.

Any thoughts?

Romanator

I gave added a bug report upstream with kde.org. This applies to Nvidia cards only.

https://bugs.kde.org/show_bug.cgi?id=267636

Hopefully, I’ll get some confirmation with them.

Btw If you just stick withe the QtCurve preset Agua, you won’t experience a crash. But if you switch…>:(

Since I’m getting 55 different kcrashes at once. How can I set up a trace the next time it crashes so all information can be written to a single text file.

Any thoughts?

Romanator

This problem is not unique to Nvidia cards. I duplicated your crash(es) almost exactly on an i5-430m with Intel GMA HD graphics.

Confirm that the first switch (to Aqua) seems OK. The second switch starts a crash-and-burn (task after task) until the final swan song.

Just when I was dreaming of an Arrandale with switchable (Intel GMA + Nvidia) graphics!

I just got confirmation that the problem is not with the Nvidia cards (I’m running 64-bit) but the QtCurve style.

Refer to the bug report I submitted with kde:

https://bugs.kde.org/show_bug.cgi?id=267636

[LEFT][FONT=Bitstream Vera Sans]------- Comment #3 From Aaron J Seigo 2011-03-05 06:08:47 -------since all of those apps are crashing, that should be a hint that the bug is in the QtCurve style.[/LEFT]
[/FONT]

[LEFT][FONT=Bitstream Vera Sans]------- Comment #4 From Craig Drummond 2011-03-05 14:23:19 -------Totally agree - this is a bug in QtCurve. Versions < 1.8.4 had a bug where (for certain configurations) memory was beeing free’d twice. Sorry.[/LEFT]
[/FONT]
Hopefully, this will be fixed upstream and then passed on to our KDE openSUSE Team.

It’s official! This has been marked as “RESOLVED UPSTREAM” by the kde team.

Cheers!

Romanator

Thanks a lot, Romanator.

You are welcome. It sure pays to get involved.

Always try to submit bugs upstream with https://bugs.kde.org

and downstream with https://bugzilla.novell.com/index.cgi

Remember to have fun!

Romanator