Image 01
profile-image

Zephyr1988

George Panta Athens, Greece
Icon Tasks

Plasma 4 Extensions by CraigD 642 comments

Hello CraigD,

Excellent Job on the plasmoid, it is excellent and bug-free, a great overall improvement to the default plasma taskmanager pasmoid.

I read the plasma devel mailing list today and found a discussion that involved plasma-icontasks and merging it with the default libtaskamanager/taskmanager plasmoid.

Below are links to the emails I mention by Martin Graesslin and Aaron Seigo:

http://mail.kde.org/pipermail/plasma-devel/2011-September/017055.html
http://mail.kde.org/pipermail/plasma-devel/2011-September/017055.html

I thought you might be interested in this.

Either way, I will most definitely keep using your plasmoid. :D

Keep up the good work and thank you very much for this :) - Sep 26 2011
Titlebar menu

Various KDE 1.-4. Improvements by johnnybravo 29 comments

This is an excellent effect, great work and thank you!!

For the next versions could you consider this idea?

http://forum.kde.org/brainstorm.php#idea91172_page1

When the qt-appmenu patch goes upstream in Qt, hopefully 4.8, it could be merged upstream! - Feb 17 2011
oxygen-transparent

QtCurve by HugoPereira 546 comments

Great! Thanks Hugo!

The dolphin and other crashes are most probably only triggered by the patched Qt that Kubuntu has, so if you use another distro it is quite logical to not come across it. (I use ArchLinux with the patched Qt)

Also Aurelien Gateau commented on my bug report half an hour ago with a patch for kdelibs with a QWidget -> QObject patch for the KModifierKeyInfo that was showing in all those other traces.

Finally, since I found a similar bug report on bugs.kde.org I will post it there once I test it so I think this is bug closed from all sides.

Thanks once again! - Feb 10 2011
oxygen-transparent

QtCurve by HugoPereira 546 comments

Great! Thanks Hugo!

The dolphin and other crashes are most probably only triggered by the patched Qt that Kubuntu has, so if you use another distro it is quite logical to not come across it. (I use ArchLinux with the patched Qt)

Also Aurelien Gateau commented on my bug report half an hour ago with a patch for kdelibs with a QWidget -> QObject patch for the KModifierKeyInfo that was showing in all those other traces.

Finally, since I found a similar bug report on bugs.kde.org I will post it there once I test it so I think this is bug closed from all sides.

Thanks once again! - Feb 10 2011
oxygen-transparent

QtCurve by HugoPereira 546 comments

Hello Hugo,

I have found a solution to this problem with the raster engine and the crashes on close, after looking a bit at the bespin code.

Apparently the Qt patch I mentioned earlier was triggering the crashes in the raster engine.

Anyway here it is, thanks for your input on this :)

http://paste.kde.org/4488/ - Feb 10 2011
oxygen-transparent

QtCurve by HugoPereira 546 comments

Hello Hugo (and sorry for annoying you!)

After some more testing I have discovered a bug in the kde bugtracker [1] which is strikingly similar to the trace I got above.

The reporter there uses QtCurve Style [2] and mentions that the bug is solved after QtCurve update to 1.8.4. Its changelog is:

1.8.4
-----
1. Fix saving of custom alpha values.
2. Fix crash upon exit - due to double free

I can say that QtCurve with ARGB transparency ON works fine here when oxygen-transparent presents the same crashes.

Maybe the developer of QtCurve could provide some insight?

Thank you very much for your time!

[1] https://bugs.kde.org/show_bug.cgi?id=264923
[2] http://kde-look.org/content/show.php/QtCurve+(KDE4,+KDE3,+&+Gtk2+Theme)?content=40492 - Feb 06 2011
oxygen-transparent

QtCurve by HugoPereira 546 comments

I think this bug report in Qt is related to these crashes. Are any changes to oxygen transparent needed?

http://bugreports.qt.nokia.com/browse/QTBUG-16974 - Feb 01 2011
oxygen-transparent

QtCurve by HugoPereira 546 comments

Hello Hugo. I have tried to get a better trace and I hope that it helps. I can reproduce it with KDE 4.6 and latest oxygen-transparent.

I believe it might be related to the Qt appmenu patch by Aurelien Gateau and the interaction with the style. Anyway:


Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f65a05c9760 (LWP 13957))]

Thread 2 (Thread 0x7f658b93e700 (LWP 13971)):
#0 0x00007f659fef46d3 in select () from /lib/libc.so.6
#1 0x00007f659c17ff8c in QProcessManager::run (this=0x7f659c4df8c0) at io/qprocess_unix.cpp:245
#2 0x00007f659c0aaeb7 in QThreadPrivate::start (arg=0x7f659c4df8c0) at thread/qthread_unix.cpp:285
#3 0x00007f659922acb0 in start_thread () from /lib/libpthread.so.0
#4 0x00007f659fefaaed in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f65a05c9760 (LWP 13957)):
[KCrash Handler]
#6 0x00007f659cd8c31e in QRasterWindowSurface::~QRasterWindowSurface (this=0xffc1c0, __in_chrg=<value optimized out>) at painting/qwindowsurface_raster.cpp:104
#7 0x00007f659cd8c3e9 in QRasterWindowSurface::~QRasterWindowSurface (this=0xffc1c0, __in_chrg=<value optimized out>) at painting/qwindowsurface_raster.cpp:108
#8 0x00007f659cda99b2 in QWidgetBackingStore::~QWidgetBackingStore (this=0x1063db0, __in_chrg=<value optimized out>) at painting/qbackingstore.cpp:883
#9 0x00007f659cbc23e9 in QWidgetBackingStoreTracker::destroy (this=0xfecf50) at kernel/qwidget.cpp:205
#10 0x00007f659cbc2545 in QWidgetPrivate::deleteExtra (this=0xa78320) at kernel/qwidget.cpp:1750
#11 0x00007f659cbc278c in QWidgetPrivate::~QWidgetPrivate (this=0xa78320, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:318
#12 0x00007f659cbc2a99 in QWidgetPrivate::~QWidgetPrivate (this=0xa78320, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:323
#13 0x00007f659c1bb1d3 in cleanup (this=0xa6df30, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
#14 ~QScopedPointer (this=0xa6df30, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100
#15 QObject::~QObject (this=0xa6df30, __in_chrg=<value optimized out>) at kernel/qobject.cpp:817
#16 0x00007f659cbc51b3 in QWidget::~QWidget (this=0xa6df30, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1477
#17 0x00007f659da543e9 in KModifierKeyInfoProvider::~KModifierKeyInfoProvider (this=0xa6df30, __in_chrg=<value optimized out>) at /home/george/debuggingpkgs/kdelibs/src/kdelibs-4.6.0/kdeui/util/kmodifierkeyinfoprovider_x11.cpp:145
#18 0x00007f659da54409 in KModifierKeyInfoProvider::~KModifierKeyInfoProvider (this=0xa6df30, __in_chrg=<value optimized out>) at /home/george/debuggingpkgs/kdelibs/src/kdelibs-4.6.0/kdeui/util/kmodifierkeyinfoprovider_x11.cpp:152
#19 0x00007f659d994a61 in KModifierKeyInfo::~KModifierKeyInfo (this=0xa7d860, __in_chrg=<value optimized out>) at /home/george/debuggingpkgs/kdelibs/src/kdelibs-4.6.0/kdeui/util/kmodifierkeyinfo.cpp:38
#20 0x00007f659d994a79 in KModifierKeyInfo::~KModifierKeyInfo (this=0xa7d860, __in_chrg=<value optimized out>) at /home/george/debuggingpkgs/kdelibs/src/kdelibs-4.6.0/kdeui/util/kmodifierkeyinfo.cpp:39
#21 0x00007f659fe5c261 in ?? () from /lib/libc.so.6
#22 0x00007f659fe5c2b5 in exit () from /lib/libc.so.6
#23 0x00007f659fe45dd4 in __libc_start_main () from /lib/libc.so.6
#24 0x00000000004005c9 in _start () - Jan 31 2011
oxygen-transparent

QtCurve by HugoPereira 546 comments

Hello Hugo,

I also had no problem when using KDE 4.5.
After upgrading to KDE 4.6 betas and RC1, I get these crashes.

I just tested with Bespin (latest svn and ARGB transparency on) and I can reproduce the crash when closing KMix with similar trace.

With QtCurve with transparency enabled I do not get any crash. The QtCurve kde4 package however is compiled on KDE 4.5 and Qt 4.7.1 if that matters.

I will try to get a better trace by recompiling Qt and kdelibs with Debug symbols enabled. - Dec 29 2010
oxygen-transparent

QtCurve by HugoPereira 546 comments

Hi Hugo and thanks for this theme! It's great!

I use KDE 4.6 Beta2, oxygen-transparent-svn rev. 1204527 and Qt 4.7.1 with Raster graphicssystem on ArchLinux 64-bit.

I get crashes after closing some programs, reproducable every time. Especially with dolphin, systemsettings, kmix and on logout/shutdown with ksmserver.

I believe you can easily reproduce by running e.g.

dolphin -graphicsystem raster

and then closing the application.

My distro does not provide debug packages so my trace is incomplete but I hope it helps:


Application: System Settings (systemsettings), signal: Segmentation fault
[Current thread is 1 (Thread 0x7ffc0eb3a760 (LWP 7415))]

Thread 2 (Thread 0x7ffbec501710 (LWP 7443)):
#0 0x00007ffc0c0932d3 in select () from /lib/libc.so.6
#1 0x00007ffc0c76ccfc in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007ffc0c6a453e in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007ffbf61fea33 in ?? () from /usr/lib/libGL.so.1
#4 0x00007ffc0a1c5cb0 in start_thread () from /lib/libpthread.so.0
#5 0x00007ffc0c0999dd in clone () from /lib/libc.so.6
#6 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ffc0eb3a760 (LWP 7415)):
[KCrash Handler]
#6 0x00007ffc0d5b29e9 in QRasterWindowSurface::~QRasterWindowSurface() () from /usr/lib/libQtGui.so.4
#7 0x00007ffc0d5b2a69 in QRasterWindowSurface::~QRasterWindowSurface() () from /usr/lib/libQtGui.so.4
#8 0x00007ffc0d5cce61 in ?? () from /usr/lib/libQtGui.so.4
#9 0x00007ffc0d40b299 in ?? () from /usr/lib/libQtGui.so.4
#10 0x00007ffc0d40b3e8 in QWidgetPrivate::deleteExtra() () from /usr/lib/libQtGui.so.4
#11 0x00007ffc0d40b62c in QWidgetPrivate::~QWidgetPrivate() () from /usr/lib/libQtGui.so.4
#12 0x00007ffc0d40b939 in QWidgetPrivate::~QWidgetPrivate() () from /usr/lib/libQtGui.so.4
#13 0x00007ffc0c7a3723 in QObject::~QObject() () from /usr/lib/libQtCore.so.4
#14 0x00007ffc0d40d9e6 in QWidget::~QWidget() () from /usr/lib/libQtGui.so.4
#15 0x00007ffc0d40dc09 in QWidget::~QWidget() () from /usr/lib/libQtGui.so.4
#16 0x00007ffc0d9793a5 in ?? () from /usr/lib/libQtGui.so.4
#17 0x00007ffc0c000181 in ?? () from /lib/libc.so.6
#18 0x00007ffc0c0001d5 in exit () from /lib/libc.so.6
#19 0x00007ffc0bfe9c54 in __libc_start_main () from /lib/libc.so.6
#20 0x000000000040a7d9 in _start () - Dec 10 2010