Image 01
profile-image

unknownSpirit

unknown spirit , Austria
Plasma 4 Extensions
test
BusyTasks

Plasma 4 Extensions 84 comments

Score 78.7%
Sep 11 2013
"BTW, have you considered adding a field for MEM usage as well? Sometimes it's nice to spot a memleak before it goes out of control ;)"
I did not plan such a feature, but I'll think about it. Memory usage usually is not that quick changing and therefore does not instantly affect your system. I may add that feature later as optional, but it would mean just another daemon.

"It'd be nice if there was some noob-friendly help to the settings."
I am really surprised about that because they are not really complicated. What's the problem?
If more people don't understand them I'll add an entry to the knowledge base. - Aug 04 2011
"Hmmm, would it be possible to use some inotify or similar system to track this information?"
I think it would.
As the files are updated periodically it would even be enough to just output content regularly. This is actually already the case for iotop's file. - Aug 04 2011
"Sounds brilliant and just what I'd want (instead of having an 'htop' open in Konsole all the time)! :D"
Depending on how much information you actually wanna see, top or htop in konsole may be a bit oversized. You imagine I wrote this plasmoid because I was not happy with the existing system monitors. - Aug 04 2011
Hi H00K

"...what I wonder though is does it have any impact on resources, tailing top and iotop all the time? "
This is an interesting question that I've already asked myself. There are two daemons running, writing to 2 files (see knowledge base), which are the source for the plasmoid. I've implemented the daemon mode because starting and stopping the tops periodically is really slow and cpu intensive.
We've to consider cpu as well as IO activity. Top is a highly configurable and mature program that I've set to log only minimum information, that is, what is actually displayed by the plasmoid. On my CPU (Intel Dualcore) the top daemon averagely needs 0.2% when active, so it's really insignificant. Every 3 seconds, it writes about 1 K/s to a file. I've not noticed an impact on plasma-desktop yet.
With iotop, it's a bit more difficult though.
Unfortunately it's not that adjustable and thus logs more information than actually used. This means more effort for the plasmoid to gain data, process and reformat it. On my system the iotop daemon uses about 1.5% cpu, and consumes a bit more IO activity.
For the plasmoid itself, it's not easy to guess its actual effect on the system as it is fully integrated in plasma-desktop's statistics.
I dare to say, however, that I did not recognise significant resource consumption.

"I'm talking about having it running all the time on a laptop, where I'd primarily like to have as little as CPU wakeups as possible."
HTOP consumes about 2% cpu here, so I guess it is in the same league as my daemons.

Kind regards, - Aug 04 2011
For the time being the plasmoid is finished.
Unfortunately I do not have any bug reports even though there are many negative votes. I've no problem with bad votes, but by JUST voting bad the program won't improve. It's simply a sign of not having understood the importance of sufficient feedback for the development of a valuable program.
It's clearly a statement, and it's not in my favour, but that way it's not in yours either. - Aug 01 2011
Your wish is implemented.
Kind regards - Jul 27 2011
Thanks.
I doubt I am able to realise that wish, but I'll give it a try at least. - Jul 23 2011
Of course you have to restore your top settings on your own. However, the plasmoid won't destroy them any more. - Jul 22 2011
Please try current version, rate and comment.
I have implemented your suggestions.
Kind regards, - Jul 22 2011
Thank you for your remarks.

"But it breaks top, showing the most CPU-intensive process only."
There are several problems with top:
You cannot point top to a specific configuration file. That means I have to either replace it before the start of the plasmoid and then restore the old one, or simply ignore the problem.
I tried to implement the first solution, but I failed. I'll think about it again, I may succeed.

"But it's quite small there, the process name does not fit and has to be guessed."
I gotta admit that although I suggested this use in the description I did not try it myself (I use it standalone on a part of the desktop that is always in foreground). You are right, I hope I can fix this issue. - Jul 21 2011
Mountoid

Plasma 4 Extensions 77 comments

Score 74.0%
Dec 24 2010
I tried version 0.33 and I've still got this problem. Do I really have to edit fstab to get those entries? - Jul 15 2011
...but it does not show my other harddisk partitions. Dolphin does.
I'd like to try an older version to see if it's related to my outdated KDE. - Jul 15 2011
tail

Plasma 4 Extensions 19 comments

Score 82.4%
Apr 28 2011
"after "> file" to reset it will no longer refresh in the current session and should be cleared too"
Depends on what you write to the file.
On my system (ubuntu with old kde) it works.
If you remove the file the plasmoid will stop. However, it won't continue if your observed data is restored. That's a bit annoying. - Jul 15 2011
Fancy Tasks

Plasma 4 Extensions 570 comments

by Emdek
Score 84.4%
Jun 10 2012
Sorry:
"ITS integration in plasma" - Jul 01 2011
Hi Jose Filipe,
With Daisy it's similar to Fancy Tasks: it's integration in plasma results in a take-over of all its benefits and limitations.
On my system (ubuntu), plasma-deskop's panels are slow.
I really do not why, but they are just not suitable for fluent (!) animation and quick response, especially with a high working load.
In contrast to the other two docks, Cairo-Dock is lightning fast and it is constantly fast.
I do not know what's the case with AWN, I have not tried it and I guess I won't do it as there's simply no need. Although Cairo-Dock certainly can't replace the whole desktop interface yet it satisfies my needs. - Jul 01 2011
Due to advanced slowness, proportionally increasing with CPU-utilisation, I decided to look for an alternative dock.
The latest release of Cairo dock (glx-dock) eventually fixed a bug that deterred me from using it. Cairo's seperate implementation has ambivalent consequences: on the one hand it is independent from plasma's bugs (speed, mess of plasmoids' positions...), on the other one it cannot interfere with it (yet).
Regards, - Jun 30 2011
I eventually realized what you mean: drkonqi's output

Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5762700 (LWP 2235))]

Thread 2 (Thread 0xa62ffb70 (LWP 2245)):
#0 0xb7795430 in __kernel_vsyscall ()
#1 0xb5ebae15 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:122
#2 0xb607f9ad in __pthread_cond_wait (cond=0x90d6138, mutex=0x90d6120) at forward.c:139
#3 0xb7595e67 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4 0xb5dcc922 in ?? () from /usr/lib/libQtNetwork.so.4
#5 0xb7594e32 in ?? () from /usr/lib/libQtCore.so.4
#6 0xb5eb680e in start_thread (arg=0xa62ffb70) at pthread_create.c:300
#7 0xb6072a0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb5762700 (LWP 2235)):
[KCrash Handler]
#6 QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:711
#7 FancyTasks::Job::title (this=0x0) at /home/user/Programme/fancytasks-1.0.0/applet/FancyTasksJob.cpp:227
#8 0xa727f964 in FancyTasks::Icon::title (this=0x93b5238) at /home/user/Programme/fancytasks-1.0.0/applet/FancyTasksIcon.cpp:1853
#9 0xa7283535 in FancyTasks::Icon::paint (this=0x93b5238, painter=0xbfd87ef8, option=0x93432d0, widget=0x92d4b28) at /home/user/Programme/fancytasks-1.0.0/applet/FancyTasksIcon.cpp:405
#10 0xb692697a in ?? () from /usr/lib/libQtGui.so.4
#11 0xb6931de1 in ?? () from /usr/lib/libQtGui.so.4
#12 0xb69341f4 in QGraphicsScene::drawItems(QPainter*, int, QGraphicsItem**, QStyleOptionGraphicsItem const*, QWidget*) () from /usr/lib/libQtGui.so.4
#13 0xb6941ebc in QGraphicsView::drawItems(QPainter*, int, QGraphicsItem**, QStyleOptionGraphicsItem const*) () from /usr/lib/libQtGui.so.4
#14 0xb694ebde in QGraphicsView::paintEvent(QPaintEvent*) () from /usr/lib/libQtGui.so.4
#15 0xb42c4dac in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#16 0xb6353dd4 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#17 0xb6703633 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
#18 0xb67a2494 in QAbstractScrollArea::viewportEvent(QEvent*) () from /usr/lib/libQtGui.so.4
#19 0xb694c51f in QGraphicsView::viewportEvent(QEvent*) () from /usr/lib/libQtGui.so.4
#20 0xb67a4a95 in ?? () from /usr/lib/libQtGui.so.4
#21 0xb768483a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#22 0xb62fef2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#23 0xb63065ca in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#24 0xb6d4ebfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#25 0xb76856cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#26 0xb635be25 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4
#27 0xb635c64d in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
from /usr/lib/libQtGui.so.4
#28 0xb635ba16 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4
#29 0xb64ea2f8 in ?? () from /usr/lib/libQtGui.so.4
#30 0xb634d116 in QWidgetPrivate::syncBackingStore() () from /usr/lib/libQtGui.so.4
#31 0xb6354215 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#32 0xb6703633 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
#33 0xb67a2faa in QAbstractScrollArea::event(QEvent*) () from /usr/lib/libQtGui.so.4
#34 0xb694c406 in QGraphicsView::event(QEvent*) () from /usr/lib/libQtGui.so.4
#35 0xb42c6523 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#36 0xb62fef54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#37 0xb63065ca in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#38 0xb6d4ebfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#39 0xb76856cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#40 0xb76862b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#41 0xb768647d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#42 0xb76b03ff in ?? () from /usr/lib/libQtCore.so.4
#43 0xb5f02e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#44 0xb5f06730 in ?? () from /lib/libglib-2.0.so.0
#45 0xb5f06863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#46 0xb76b002c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#47 0xb639fbe5 in ?? () from /usr/lib/libQtGui.so.4
#48 0xb7683c79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#49 0xb76840ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#50 0xb768653f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#51 0xb62fedd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#52 0xb42bb80d in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#53 0x0804dde1 in _start ()
- Jun 21 2011
It is 1.0, the latest version for KDE 4.3. (the one you linked to in the description).
I don't know what you mean by backtrace. My log shows significant close errors before segmentation fault, only occurring with the jobs section activated. - Jun 21 2011
Bad news.
Unfortunately, I've recognized bugs.
Two things are bothering me:
Since installation, three plasma-widgets get weird after some time (that is: they are still working, but incorrectly)
Restarting plasma-desktop temporarily solves the problem, meaning I've to restart it about ten times a day if I want to have functional widgets.
I am not sure yet if the installation is just a coincidence and the whole plasma configuration is corrupt or it's really related to Fancy Tasks, but I'll find out as soon as I've more time to play with the environment.
One thing is for sure: the jobs section is not working for me either.
Each time a job completes, whole desktop crashes and restarts. I've made a log and hope it helps you to find the bug: http://tinyurl.com/67eav3n (first half may be irrelevant)
I hope you still support my old version.
Regards, - Jun 08 2011
...on this masterpiece. There are no bugs on my old KDE (4.3).
I've got a wish though: more panel backgrounds. - May 28 2011
Daisy

Plasma 4 Extensions 574 comments

Score 81.9%
Jul 14 2012
I guess the project is closed.
Good work, but I prefer more action on mouse-over (see panel "fancy tasks" http://kde-apps.org/content/show.php?content=99737). - May 28 2011
sabaaland

Wallpaper Other 7 comments

by gcwds
Score 50.0%
Apr 23 2010
Can someone look for his pacifier, please?
I am not used to childcare. - Apr 23 2010
Very simple CPU temperature

Plasma 4 Extensions 3 comments

Score 67.1%
Mar 07 2010
Simple but useful. The design is a bit outdated, but it is formatable via HTML.

lm-sensors needs to be installed! - Apr 20 2010
Crystal

Various KDE 1.-4. Styles
by dralgebra

Score 75.8%
Mar 19 2013
Fancy Tasks

Plasma 4 Extensions
by Emdek

Score 84.4%
May 27 2011
Py-Cashew

Plasma 4 Extensions
by BenoitMonin

Score 84.7%
9   Oct 16 2013
luckyBackup

System Software
by luckyb

Score 83.1%
9   Jan 31 2012
tail

Plasma 4 Extensions
by dmakovey

Score 82.4%
9   Jul 15 2011
Luna 2

Plasma 4 Extensions
by glad

Score 70.0%
9   Jul 12 2011
Fancy Tasks

Plasma 4 Extensions
by Emdek

Score 84.4%
9   May 27 2011