Image 01
profile-image

unknownSpirit

unknown spirit , Austria
Plasma 4 Widgets
OxyLightsSplashScreen

KDE 4 Splashscreens 11 comments

Score 73.1%
Feb 18 2010
Supported resolutions:
I'll start with some praise. The excellent beauty of the smooth colour transition is clearly mind-blowing. However, some resolutions do not only affect the wallpaper but also the animation itself, causing the splash screen to crash.
You've got to manually adjust the ksplashML file. - Dec 24 2013
Icon Tasks

Plasma 4 Widgets 642 comments

Score 88.4%
Nov 10 2011
The plasmoid needs an internal source code update. A software adaptor (e.g. class(es)) may work as well. The developer obviously does not maintain this project any more. - Oct 16 2013
See "Mar 23 2013" - Jun 14 2013
Library links are broken for >KDE4.7
Compare files:
http://api.kde.org/4.7-api/kde-workspace-apidocs/libs/taskmanager/html/taskmanager_8h_source.html
and
http://api.kde.org/4.8-api/kde-workspace-apidocs/libs/taskmanager/html/taskmanager_8h_source.html
This plasmoid needs a revision for new KDE versions. - Mar 23 2013
Here as well, with KDE4.8 - Mar 23 2013
This issue is also present with Glx-Dock and FancyTasks. The only flawless task bar is obviously the standard one. - Sep 01 2011
BusyTasks

Plasma 4 Widgets 84 comments

Score 78.7%
Sep 11 2013
No problem. If you like it, just vote for it.
Kind regards, - Sep 12 2013
The plasmoid was updated. I cannot test it here though as I don't have procps-ng 3.3.8 per default. - Sep 11 2013
After a few annoying bug-workarounds I eventually got KDE 4.11 to run.
First of all, the crash is very likely due to a 64-bit architecture without ia32-libs being installed. See the last point of requirements.
Moreover, there's a bug in procps-ng prior to version 3.3.5 causing the rcfile being used to be locale-dependent. (http://lists.opensuse.org/opensuse-bugs/2012-12/msg01466.html)
So if you have 3.3.1-3.3.4, this plasmoid won't work for you.
Actual procps-ng release seems fine, the name of the configuration file changed, however. So there'll be a small update soon. - Sep 10 2013
Thanks for your feedback
I'm gonna try it with 4.11 myself and see what happens.
Stay tuned, kind regards,
- Aug 31 2013
First of all: Are you sure you need the self-compilation? There are three versions in the plasmoid-package.
Does nethogs start when you display the NET intensive task? - Dec 22 2011
I updated 11.7 once again, with minor changes inherited from the debug release.
So I think the official version eventually supports newer kernels. - Dec 22 2011
Glad it works but I am still pondering about the problem.
Which version works? The debuginfo one?
Kind regards, - Dec 21 2011
This version works with arch and kdesu:
http://www.unet.univie.ac.at/~a0647161/BusyTasks-debuginfo.plasmoid
Honestly, I can't find the mistake.
Kind regards, - Dec 21 2011
I tried it on a system with kdesu now and it does not work here either. (development environment runs with kdesudo)
As soon as I get it to work I'll upload it.
Kind regards, - Dec 21 2011
I tried it on a system with kdesu now and it does not work here either. (development environment runs with kdesudo)
As soon as I get it to work I'll upload it.
Kind regards, - Dec 21 2011
Just to make sure I get it right: nethogs works? - Dec 21 2011
Ok, we're getting closer...
Case one and three are OK (indicates that it should work if you enter the password in plasmoid configuration).
Two is a riddle so far. You should either get an error message or a message prompt.

What graphical superuser frontend do you use? kdesu or kdesudo? - Dec 21 2011
It's a bit strange, or to state it differently, I do not see what I expected to do :-/
The plasmoid tries to start iotop with standard rights, and fails, as expected (OSError: Netlink error: Operation not permitted (1))
Afterwards, you should get a prompt, which, however, is not the case (and I cannot see a related error either) As a consequence, shared memory is not attached and painting is error-prone.
What python version do you have?
Can you start the iotop daemon manually by entering the direct path in a terminal?
For example via
/home/YOURDIRECTORY/.kde4/share/apps/plasma/plasmoids/BusyTasks//contents/iotop-0.4.3/iotop.py
or
kdesudo -c "python /home/YOURDIRECTORY/.kde4/share/apps/plasma/plasmoids/BusyTasks//contents/iotop-0.4.3/iotop.py"
or
sudo python /home/YOURDIRECTORY/.kde4/share/apps/plasma/plasmoids/BusyTasks//contents/iotop-0.4.3/iotop.py - Dec 21 2011
Unfortunately the error code is not really useful as I get it here too when starting iotop without command line options.
Could you run it in plasmoidviewer and give me the output?
Kind regards, - Dec 21 2011
Another update, another try.
This time it works here at least.
Kind regards, - Dec 21 2011
I found a way to test it and discovered that it does not work yet.
Will upload a fix soon, stay tuned.
Kind regards, - Dec 20 2011
Should work now for the new kernel too.
Please consider the fact that I can't test it as I don't have a system with such a kernel yet.
You should have regular glances at a system monitor of your choice to control if all daemons start and stop correctly!
Kind regards, - Dec 20 2011
Hi
I guess you are right, it's due to a linux kernel update concerning tasks' permissions.
http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.1
I hope I'll be able to upload a fix in a few hours' time.
Kind regards, - Dec 20 2011
That is, it does not touch the old file .toprc that the previous version left, either.
A short manual to restore your settings:

–Remove BusyTasks from your desktop.
–Remove the file .toprc in your home-directory if it is NOT your own one (e.g. you see something in top that you have not seen before the installation).
–Install the new version.
Kind regards, - Sep 21 2011
Hi chepioq
BusyTasks should not touch your top configuration by any means any more. - Sep 21 2011
I think I found the reason, it's quite a small bug but with big consequences.
Thank you for pointing it out!
I'll upload a fix tomorrow, stay tuned.

Once again a global call for feedback:
As I already mentioned earlier in the comment section, feedback is important!
Although I keep testing the program extensively I cannot find all mistakes.
Please tell me if there's something wrong! - Sep 20 2011
"As you will not resolve this problem, I could not use your plasmoid..."
I can only solve the problems I know about.
Unfortunately people here are not very communicative.

"When I install and lauch it, the command "top" don't work properly in console."
What do you mean?
Does it quit with error or does it display something?
What top version do you use?
Do you have your own top configuration? - Sep 20 2011
Tested the 'BusyTasks - noresizing' version again.
Please make sure you use this one.
Should work for you. - Sep 08 2011
Even with the "noresizing" version? - Sep 08 2011
No problem, mistakes do happen.
I better have such kind of feedback than have nothing but a couple of arbitrarily bad votes.
Kind regards, - Sep 08 2011
"since release 9.0"
Sorry, I was referring to release 8.0. - Sep 08 2011
Ok, now we eventually caught the real problem. (The package path problem only occurred for plasmoidviewer):
You don't have the System V IPC module for python installed, which is necessary since release 9.0. See description for download link and installation!
- Sep 08 2011
In the plasmoid package path?
Can you print it here please? - Sep 08 2011
Hi chepioq, thanks for your feedback.
If I get things right, this is an encode problem of your package path string. Obviously a function does not support unicode characters. This accounts for the directory where you ran plasmoidviewer, but may not be true for your plasmoid package directory.
Does it have language specific symbols too (like french accents, for example)? - Sep 08 2011
And thanks for your offer to help, I think I'll come back to it later. - Sep 04 2011
Glad it works now.
The plasmoid is not finished yet, I currently work on the next release with icons. Having least priority language support is still a nice feature that may be included when everything else is done. - Sep 04 2011
You've got to resize manually via the plasmoid interface now! - Sep 03 2011
I must admit I got ahead of myself, the target goal of this version might have been missed.
If resizing really is your only problem with the plasmoid (what I can't imagine though), this version should work:
http://www.unet.univie.ac.at/~a0647161/BusyTasksmodified.plasmoid - Sep 03 2011
This is partly what I expected. The plasmoid size is saved in the configuration, which obviously is not read correctly.
This is a modified version without error handling. Please run it with plasmoidviewer and report output.
http://www.unet.univie.ac.at/~a0647161/BusyTasksmodified.plasmoid - Sep 02 2011
Thank you very much for you feedback. As I run a pretty old KDE (version 4.3) I already expected compatibility problems with actual releases.
I am motivated to solve this, though.
If you are using it in a panel:
The first reason I can think of is a panel bug that I have here too: inside a panel, the plasmoid cannot be configured. The solution is quite simple: drag it to the desktop, configure it there and then redrag it to the panel.
If you are using it standalone:
Please tell me if the size problem is the only one (e.g. does the font size change, do the daemons start, etc.)
Last but not least, run it with plasmoidviewer and print the output here.

You may wonder why the plasmoid saves its size independently from plasma. Well, this is related to a plasma bug that keeps size only for a single session. My approach is just a workaround.
If the new KDE does not have this problem any more, I will remove this option. - Sep 02 2011
In the current version only the top daemons write to files. As they work very economically a switch to IPC won't be necessary. - Aug 31 2011
I still do not know the cause for this problem.
Nonetheless, for all interested, I wanna state that there will be a major update (first stable release) tomorrow with workarounds and bug fixes. - Aug 15 2011
On my computer the initial plasmoid-specific top configuration of the daemon is broken in rare cases. Example given: after a restart of plasma-desktop the plasmoid shows a line of my own top configuration.
As there are no complaints about bugs (I can't really believe there are none) I post an explicit request for feedback: did you encounter that bug too? - Aug 05 2011
Ok I'll add some tooltips. - Aug 04 2011
MOUNTAINRIVER V (Bavaria, DE)

Mountains 6 comments

by jfest
Score 50.0%
Mar 25 2012
Just tick the option to hide wallpapers then. - Mar 26 2012
I guess you mean "mountainriver" - Mar 25 2012
Luna 2

Plasma 4 Widgets 31 comments

by glad
Score 70.0%
Jul 06 2011
If the moon in Luna2 is supposed to be completely invisible on the new moon, then these remarks truly are a thoroughly embarrassing and, unfortunately, everlasting exposure of my ignorance.
Can someone confirm my assumption please - Sep 27 2011
The original luna works.
Updating to last version, rebuilding and reinstalling did not work. - Sep 27 2011
Interestingly I noticed today that this plasmoid does not work any more on my Kubuntu 9.10.
Plasma does not report errors, the plasmoid is shown but the moon is not drawn.
Plasmoidviewer claims the following:
Couldn't find node 0. Skipping rendering.
QPixmap::scaled: Pixmap is a null pixmap

Anyone having an idea? - Sep 27 2011
Crystal

Various KDE 1.-4. Styles
by dralgebra

Score 75.8%
Mar 19 2013
Fancy Tasks

Plasma 4 Widgets
by Emdek

Score 84.4%
May 27 2011
Py-Cashew

Plasma 4 Widgets
by BenoitMonin

Score 84.7%
9   Oct 16 2013
luckyBackup

System Software
by luckyb

Score 83.1%
9   Jan 31 2012
tail

Plasma 4 Widgets
by dmakovey

Score 82.4%
9   Jul 15 2011
Luna 2

Plasma 4 Widgets
by glad

Score 70.0%
9   Jul 12 2011
Fancy Tasks

Plasma 4 Widgets
by Emdek

Score 84.4%
9   May 27 2011