-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Apps
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login


Sponsoring


-
- Content .- Fans (4) .- Knowledge Base (3) . 

BusyTasks

   14.3 | 13.0  

Plasmoid Script

Score 67%
BusyTasks
zoom


BusyTasks
zoom


BusyTasks
zoom


Minimum required   PyKDE/PyQt
Downloads:  1527
Submitted:  Jul 21 2011
Updated:  Sep 11 2013

Description:

This plasmoid uses several integrated backends to receive its input. Please read at least section REQUIREMENTS before installation.
Moreover, I'd be very grateful for any kind of feedback.


UPDATE
  • 14.0: Holds the new configuration interface and supports synchronised plasmoid instances on multiple workspaces
    14.1: Timeout for network notification messages.
    14.2: Optional Irix mode, 64-bit support, many optimizations concerning the on-click-function and the panel mode
    14.3: Additional configuration file for procps-ng

  • DOCUMENTATION:
    Isn't everything some kind of process? At least on a computer it is. So let's keep an eye on them.
    This plasmoid initially was a clumsy spin-off from Dmitry Makovey's tail plasmoid, but after I got more and more used to python and the program got more and more complex I cut everything superfluous and eventually separated it from tail.
    This plasmoid uses several programs to get its input. The collected data is neither unique nor new, but the idea to clearly sum it up in one single program is. This task monitor displays up to four different tasks, each with different priority.

    CPU intensive task:
    Name and the percentage of the most CPU intensive task. The underlying top daemon is very efficient and does not really affect CPU, it is piped to shared memory.
    Used backend: http://linux.die.net/man/1/top

    Memory intensive task:
    Name of the most memory intensive task, combined with a measure of size (absolute value or percentage to total available memory).
    The implementation is the same as for the task above.

    IO intensive task:
    The task (or one of its threads) that currently triggers most IO.
    The software package includes an own version of iotop that sends data via shared memory.
    Original version: http://guichaz.free.fr/iotop/

    NET intensive task:
    The task that eats up your bandwidth.
    You will be prompted for an administrator password when starting nethogs.
    Like the one of iotop, this is a modified nethogs daemon that uses IPC.
    Original version: http://nethogs.sourceforge.net

    Additionally, the configurable update interval plays a crucial role in resource consumption. The smaller it is set, the more resources are needed.
    There should be slightly less resource consumption (in terms of IO as well as overall) since release 8.0. Release 10.0 eventually cut out all IO.

    The plasmoid is highly configurable to fit most desktop designs.
    It supports highlighting of processes, either through a simple colour change after a certain limit of per cents or via colour gradient. For the statisticians among you, you can even log output. BusyTasks is only useful if it is always visible (e.g. residing on a panel) If you'd have got to minize windows or show the desktop to have a glance on it you could equally start the system monitor.

    REQUIREMENTS: (and installation instructions)
    The program was tested under several different distributions and is considered stable.(read below). Some of the used daemons may require additional libraries, however.
    For full functionality, you need to meet the following requirements:
  • Installation of top in your command-line interpeter. This usually is the case on UNIX OSs.
  • Proper value of $HOME variable in the shell environment. Verify with "echo $HOME".
  • Python version 2.
    On new systems version 3 may only be installed. Use the bash command "python -V" to check your version, additionally you may verify the installation of python2 by entering "python2 -V". Usually it's easy to get previous releases, they are not interfering
  • The System V IPC module for python.
    If you don't have it yet, visit http://semanchuk.com/philip/sysv_ipc/ for download and install instructions.
    Short manual:
    Download file, go to the related directory and run "sudo python setup.py install". For systems linking python 3 per default, type "sudo python2 setup.py install". If it quits moaning about a python file install the package "python-dev(el)" first. Eventually restart KDE
  • Libraries for iotop and nethogs, whose scripts/binaries are integrated in the plasmoid package. There is a slight chance that one of them does not work due to missing libraries. In this rare case, there are basically two ways to proceed: Either install the standalone versions of iotop and nethogs and benefit from automatic dependency resolution or get the missing files/packages manually. BusyTasks usually reports the problem. (read section "troubleshooting")
  • On 64-bit architectures you need to install the 32-bit libraries

  • TROUBLESHOOTING:
  • Oddly enough, inside a panel configuration was not possible in KDE prior to version 4.8. You had to drag it out, change settings there and redrag it into the panel.
  • If you have a problem with resizing, activate the option "resize manually"
  • On systems with linux kernel 3.1 (or above), iotop must be run in administration mode. Before activation, make sure there's a permissions error with standard rights. Be careful, arbitrarily switching between user and administration mode may cause an IPC permission error!
  • If the iotop daemon does not start, some libraries may be missing. (see plasmoid output) Install them via KPackageKit, pacman, portage, etc.
  • If none of the implemented nethogs daemons run, make sure you have the required libraries (libpcap). If it still doesn't work, download the sources (see links), compile it directly on your system, copy it to the BusyTasks directory and overwrite one of the existing nethogs0* daemons.
  • If the name resolution of VirtualBox virtual machines does not work and you see some weird symbols, close the plasmoid, delete the current bashpipetosharedmemory75* binaries from the contents folder and use the old ones by removing the *.old endings. Additionally, they must be executable.
  • On some systems the superuser frontend does only accept passwords entered in terminals. As a consequence the "use administrative password"-setting does not work, you've to manually enter your password each time. As a workaround, one may handle the daemons in the appropriate system runlevel.
  • If you still don't get it to work, contact me here or via mail. You probably found a bug/compatibility problem.

    BUGS:
    Since release 12.5 the program should be nearly bug free.
    Please report here or via mail (see plasmoid info) if your plasma-desktop crashes (so that I can at least remove the above claim), which usually happens when BusyTasks is removed from the desktop.
    Known severe bugs:
    None

    Bugs occurring too rarely to be easily classified:
    1. Nethogs transfer statistics obviously arbitrarily resets at low transfer rates (further examination/observation necessary)
    2. VirtualBox name resolution does not work in rare cases (i.e. starting Windows XP before Unix, further examination/observation necessary)
    3. The format of the data string provided by nethogs does not always meet the requirements for the plasmoid.

    PERFORMANCE:
    Python may be the wrong language to write such a tool in.
    However, plasma-desktop does not seem to be affected by the plasmoid. On a thirteen years old (!) PIV 1.8GHz the most cpu-intensive plasmoid part is one of its daemons: iotop with 10% cpu load on average, which is quite good for a computer that takes 5-10 min to start up. Given the fact that iotop itself is written in python I even expect some space for improvement using a faster programming language.
    Currently the process of (re)configuration is horribly slow.
    On the one hand, bad code is responsible for the speed inefficiency, on the other hand it is my quest for user-convenience and upwards-compatibility that accounts for this behaviour. As jobs of configuration or organisation are usually done only twice per runtime (at startup and at termination) it's still acceptable.
    I'll probably rewrite the whole program (including the iotop daemon) in C++ sometime (sometime...what a nice euphemism for never ;-)). For the moment reconfiguration performance remains the only real bug.
    Additional note: It seems that there's slightly less CPU utilization since version 12.3 on my system. Could just be a coincidence, though.

    TESTS: Program successfully tested on:
    Kubuntu 9.10, 11.04, 11.10, 12.04 64-bit
    Fedora 15
    OpenSUSE 11.4
    Arch 2011-08-19
    Slackware 13.37
    Gentoo 11.2
    Mint 12
    Sabayon 7

    TRANSLATIONS:
    If you want to contribute to the project, feel free to unpack the plasmoid-package and read the translation instructions in the contents folder.

    Suggestions for further development:
    *Implement colour gradient for the data transmission monitors.

    I strongly recommend all who have installed a previous version to get an update!
    Please comment, rate and criticise.
    In the long run I'll have to create a website for documentation because the installation possibilities and configuration options are quite impressive and this description's already uncomfortably large. Due to a severe lack of time reading tooltips is all I suggest for now.




    Changelog:

    1.0 Initial release
    2.0 Keeping original top configuration, Panel integration
    2.1 Minor ajdustment: support for multiple plasmoids
    3.0 Highlighting a process passing a certain limit with an individual colour.
    4.0 More configuration options (e.g. colour gradient)
    4.1 Click on plasmoid opens a list of tasks ordered according to CPU usage.
    5.0 Optional display of IO intensive task
    5.1 Bugfixes (colour change for IO intensive task, process and rate mismatch)
    5.2 Configuration option for on-click-behaviour, tooltips, whatsthis-tips
    6.0 Code reorganisation, further configuration options, memory intensive task, file history log..
    6.1 Optional horizontal arrangement of the tasks, saving the size
    6.2 Optional font background to avoid unreadable design
    7.0 Code cleanup and reorganisation, disassociation with tail, destructor, bugfixes, more configuration options, NET intensive task, etc.
    7.1 Direct change of network interface supported.
    8.0 Integration of own iotop and nethogs versions, IPC
    9.0 Added icons and a panel mode
    10.0 No tail involvement any more (only IPC), bugfixes
    10.1 No blocking of plasma-desktop on startup with NET intensive task any more.
    10.2 Correct behaviour on systems without user configuration for top.
    10.3 Less resource consumption of nethogs, small fix concerning the configuration dialog
    10.4 Added a logo
    10.5 German and French translations
    10.6 Further fixes of bugs (concerning units and logfile) that occurred during code reorganisation.
    10.7 Bugfixes: kdesu as optional superuser trigger (for nethogs), updated library link for nethogs
    10.8 Implemented several nethogs daemons compiled with different libraries/libary links, debug information
    10.9 Small modification for systems with python version 3.
    11.0 Easy network interface switching and advanced control over nethogs.
    11.1 The last observed unchanged value for a task is displayed for an additional second if the plasmoid is updated once per second.
    11.2 Integration of VirtualBox virtual machine name resolution.
    11.3 Optional display of the processor that the monitored process is assigned to.
    11.4 Improved error handling (at runtime and for plasmoidviewer).
    11.5 Extirpation of crashes, performance optimisations, more configuration options
    11.6 Iotop bug fix assuring that the task with most IO is chosen.
    11.7 Support for newer kernels that deny access to IO statistics for regular users.
    11.8 Improved configuration interface, bug fix concerning password prompt
    11.9 Small changes to handle high update rate in panels.
    12.0 Highlight change in memory amount between update intervals
    12.1 Improved panel layout
    12.2 Fixed VirtualBox name resolution
    12.3 Major update including changes in iotop, nethogs and BusyTasks to enable advanced data collection.
    12.4 Extended reset interval concerning the transfer statistics, separate colouring for sum and transfer rate.
    12.5 Support for gigabyte values
    12.6 Fixed iotop shared memory attachment
    12.7 Bugfix concerning encoding of iotop string
    12.8 Several minor optimisations (iotop, daemon organisation)
    14.0 New internal configuration interface (compatibility upgrade), support for multiple workspaces
    14.1 | 12.9 Timeout for network notification messages.
    14.2 | 13.0 Optional Irix mode, 64-bit support, many optimizations concerning the on-click-function and the panel mode
    14.3 Support for procps-ng (other configuration file)




    LicenseGPL
    (BusyTasks (KDE4.8 or higher))
    (BusyTasks (KDE4.7 or lower))
    (System V IPC for python)
    Source(nethogs for BusyTasks - optional)
    Send to a friend
    Subscribe
    Other  Apps  from unknownSpirit
    Report inappropriate content



    goto page: prev   1  2  3 

    -
    .

     Strange bug

     
     by unknownSpirit on: Aug 5 2011
     
    Score 50%

    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?


    Reply to this

    -
    .

     Re: Strange bug

     
     by unknownSpirit on: Aug 15 2011
     
    Score 50%

    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.


    Reply to this

    -

     BusyTasks can't re-size

     
     by chepioq on: Sep 2 2011
     
    Score 50%

    I test your plasmoid, when I launch it the size is 30x60.

    If i want re-size (60x120), I click on OK button and close the windows setting, but BusyTasks don't grows but is smaller (I think 6x12...).

    I use Fedora with KDE 4.7.


    Reply to this

    -

     Re: BusyTasks can't re-size

     
     by unknownSpirit on: Sep 2 2011
     
    Score 50%

    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.


    Reply to this

    -

     Re: BusyTasks can't re-size

     
     by chepioq on: Sep 2 2011
     
    Score 50%

    I launch BusyTasks on my desktop, stanalone.
    When I install with plasmapkg -i BusyTasks.plasmoid I have an error :

    [dominique@localhost Téléchargements]$ plasmapkg -i BusyTasks.plasmoid
    plasmapkg(6951)/libplasma Plasma::PackageStructurePrivate::createPackageMetadata: No metadata file in the package, expected it at: "/tmp/kde-dominique/plasmapkgS1G4J1//metadata.desktop"
    Installation réussie de /home/dominique/Téléchargements/BusyTasks.plasmoid

    but the plasmoid work.

    with plasmoidviewer I have error :

    [dominique@localhost Téléchargements]$ plasmoidviewer BusyTasks
    Error reading configuration!
    Error reading configuration!
    Error reading configuration!


    I have no problems to re-size fonts or start deamons


    Reply to this

    -

     Re: Re: BusyTasks can't re-size

     
     by unknownSpirit on: Sep 2 2011
     
    Score 50%

    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


    Reply to this

    -

     Re: Re: Re: BusyTasks can't re-size

     
     by chepioq on: Sep 3 2011
     
    Score 50%

    I test your BusyTasks modified, but that don't work.

    Output of plasmoidviewer BusyTasks :

    [dominique@localhost ~]$ plasmoidviewer BusyTasks
    Traceback (most recent call last):
    File "/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py", line 75, in init
    self.pyapplet.init()
    File "/home/dominique/.kde/share/apps/plasma/plasmoids/BusyTasks/contents/code/main.py", line 111, in init
    self.readConfig()
    File "/home/dominique/.kde/share/apps/plasma/plasmoids/BusyTasks/contents/code/main.py", line 147, in readConfig
    self.height=int(self.config('MCPU').readEntry('height'))
    ValueError: invalid literal for int() with base 10: ''
    Exception RuntimeError: 'underlying C/C++ object has been deleted' in <bound method BusyTasks.__del__ of <applet_BusyTasks.main.BusyTasks object at 0x13dcd40>> ignored
    [dominique@localhost ~]$

    This last line

    Exception RuntimeError: 'underlying C/C++ object has been deleted' in <bound method BusyTasks.__del__ of <applet_Busy

    is when I close plasmoidviewer window.


    Reply to this

    -

     Re: Re: Re: Re: BusyTasks can't re-size

     
     by unknownSpirit on: Sep 3 2011
     
    Score 50%

    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


    Reply to this

    -

     Re: Re: Re: Re: Re: BusyTasks can't re-size

     
     by unknownSpirit on: Sep 3 2011
     
    Score 50%

    You've got to resize manually via the plasmoid interface now!


    Reply to this

    -

     Re: Re: Re: Re: Re: Re: BusyTasks can't re-size

     
     by chepioq on: Sep 4 2011
     
    Score 50%

    Thank...
    That work fo me now...
    I can re-size plasmoid.

    I have another request

    I see your plasmoid setting is not internationalized.
    For test, I make that and that work for me, I translate some words and there are in french in setting.

    For that I use a script python, made by mjmccans for gmail.plasmoid ( http://kde-look.org/content/show.php/gmail-plasmoid?content=101229 )

    If you want, send me your email by private message and I send you a BusyTasks with internationalization.

    I think you should contact mjmccans to ask if you can use the script.





    -

     Re: Re: BusyTasks can't re-size

     
     by unknownSpirit on: Sep 4 2011
     
    Score 50%

    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.


    Reply to this

    -

     Re: Re: BusyTasks can't re-size

     
     by unknownSpirit on: Sep 4 2011
     
    Score 50%

    And thanks for your offer to help, I think I'll come back to it later.


    Reply to this

    -

     Last release don't work...

     
     by chepioq on: Sep 8 2011
     
    Score 50%

    Hi...
    I test your last release, with icons, but that don't work for me.
    With plasmoidviewer I have this error :

    [dominique@localhost Téléchargements]$ plasmoidviewer BusyTasks
    Traceback (most recent call last):
    File "/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py", line 47, in init
    PythonAppletScript.importer.register_top_level(self.pluginName, str(self.applet().package().path()))
    UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 17: ordinal not in range(128)
    [dominique@localhost Téléchargements]$


    Reply to this

    -

     Re: Last release don't work...

     
     by unknownSpirit on: Sep 8 2011
     
    Score 50%

    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)?


    Reply to this

    -

     Re: Re: Last release don't work...

     
     by chepioq on: Sep 8 2011
     
    Score 50%

    Yes I am french and I have some accents...


    Reply to this

    -

     Re: Re: Re: Last release don't work...

     
     by unknownSpirit on: Sep 8 2011
     
    Score 50%

    In the plasmoid package path?
    Can you print it here please?


    Reply to this

    -

     Re: Re: Re: Re: Last release don't work...

     
     by chepioq on: Sep 8 2011
     
    Score 50%

    Ok, path is /home/dominique/Téléchargements...
    I change and place it in /home/dominique/Documents but I have other error message :

    [dominique@localhost Documents]$ plasmoidviewer BusyTasks
    Traceback (most recent call last):
    File "/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py", line 59, in init
    self.module = __import__(self.pluginName+'.'+relpath)
    File "/usr/share/kde4/apps/plasma_scriptengine_python/plasma_importer.py", line 107, in load_module
    exec code in mod.__dict__
    File "/home/dominique/.kde/share/apps/plasma/plasmoids/BusyTasks/contents/code/main.py", line 18, in <module>
    import sysv_ipc
    ImportError: No module named sysv_ipc
    [dominique@localhost Documents]$


    Reply to this

    -

     Re: Re: Re: Re: Re: Last release don't work...

     
     by unknownSpirit on: Sep 8 2011
     
    Score 50%

    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!


    Reply to this

    -

     Re: Re: Re: Re: Re: Re: Last release don't work...

     
     by unknownSpirit on: Sep 8 2011
     
    Score 50%

    "since release 9.0"
    Sorry, I was referring to release 8.0.



    -

     Re: Re: Re: Re: Re: Re: Last release don't work...

     
     by chepioq on: Sep 8 2011
     
    Score 50%

    Ok, it's my mistake, I install System V IPC module for python and that work... (I re-installed my Fedora two days ago and I forget install this)

    Sorry...



    -

     Re: Last release don't work...

     
     by unknownSpirit on: Sep 8 2011
     
    Score 50%

    No problem, mistakes do happen.
    I better have such kind of feedback than have nothing but a couple of arbitrarily bad votes.
    Kind regards,


    Reply to this

    -

     Re: Re: Last release don't work...

     
     by chepioq on: Sep 8 2011
     
    Score 50%

    I have one comment.
    I think you don't include the patch for re-size the plasmoid, because I have same issue that in my previous post "BusyTasks can't re-size"...


    Reply to this

    -

     Re: Re: Re: Last release don't work...

     
     by unknownSpirit on: Sep 8 2011
     
    Score 50%

    Even with the "noresizing" version?


    Reply to this

    -

     Re: Re: Re: Last release don't work...

     
     by unknownSpirit on: Sep 9 2011
     
    Score 50%

    Tested the 'BusyTasks - noresizing' version again.
    Please make sure you use this one.
    Should work for you.


    Reply to this

    -

     Re: Re: Re: Re: Last release don't work...

     
     by chepioq on: Sep 9 2011
     
    Score 50%

    Ok...
    That work with Busytasks - noresize
    Thank


    Reply to this

    -

     Problem with BusyTasks and command top in console

     
     by chepioq on: Sep 20 2011
     
    Score 50%

    I have a big problem with your plasmoid.

    When I install and lauch it, the command "top" don't work properly in console.

    And when I remove the plasmoid with plasmapkg -r BusyTasks problem still persist.

    But I saw where is the problem. BusyTasks install in /home/myUser/ a file named ".toprc" , and this file is the problem (this file IS NOT erase when I remove BusyTasks).

    When I delete this file, top in console work well (but this file is recreate when I launch BusyTasks).

    As you will not resolve this problem, I could not use your plasmoid...



    Reply to this

    -

     Re: Problem with BusyTasks and command top in cons

     
     by unknownSpirit on: Sep 20 2011
     
    Score 50%

    "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?


    Reply to this

    -

     Re: Re: Problem with BusyTasks and command top in

     
     by chepioq on: Sep 21 2011
     
    Score 50%

    When I launch top in console, I have no error message but just that:
    [dominique@localhost ~]$ top

    Quote:
    %CPU COMMAND
    1.0 X


    Normally I must have :
    Quote:
    Tasks: 173 total, 2 running, 171 sleeping, 0 stopped, 0 zombie
    Cpu(s): 3.7%us, 3.2%sy, 0.0%ni, 93.2%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
    Mem: 4058756k total, 1646580k used, 2412176k free, 60912k buffers
    Swap: 2047996k total, 0k used, 2047996k free, 609784k cached

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    2052 dominiqu 20 0 800m 73m 22m R 3.0 1.9 2:34.62 npviewer.bin
    1042 root 20 0 155m 49m 23m S 2.3 1.3 5:22.66 X
    2040 dominiqu 20 0 299m 13m 8072 S 2.0 0.3 1:00.13 plugin-containe
    1751 dominiqu 20 0 732m 5676 4320 S 1.7 0.1 0:49.12 conky
    .................................................


    I don't know what is the version of top, and I have no configuration for me.


    Reply to this

    -

     Re: Re: Re: Problem with BusyTasks and command top

     
     by unknownSpirit on: Sep 21 2011
     
    Score 50%

    Hi chepioq
    BusyTasks should not touch your top configuration by any means any more.


    Reply to this

    -
    .

     Re: Re: Re: Re: Problem with BusyTasks and command

     
     by unknownSpirit on: Sep 21 2011
     
    Score 50%

    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,


    Reply to this

    -
    .

     Re: Problem with BusyTasks and command top in cons

     
     by unknownSpirit on: Sep 21 2011
     
    Score 50%

    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!


    Reply to this

    -

     Re: Re: Problem with BusyTasks and command top in

     
     by chepioq on: Sep 21 2011
     
    Score 50%

    The latest version of BusyTasks (10.2) solve the problem,
    Thank...


    Reply to this

    -
    .

     iotop requires root permissions

     
     by rvs82 on: Dec 20 2011
     
    Score 50%

    Hi,

    Nice widget. There's only one problem. I can't get it to use iotop. I think the reason is iotop requires root privileges. This is because of security changes in the Linux kernel (I'm using 3.1.0).

    Is this a known bug and if so, is there a workaround for this? Thanks.


    Reply to this

    -
    .

     Re: iotop requires root permissions

     
     by unknownSpirit on: Dec 20 2011
     
    Score 50%

    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,


    Reply to this

    -

     Re: Re: iotop requires root permissions

     
     by rvs82 on: Dec 20 2011
     
    Score 50%

    Thanks!


    Reply to this

    -
    .

     Re: Re: Re: iotop requires root permissions

     
     by unknownSpirit on: Dec 20 2011
     
    Score 50%

    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,


    Reply to this

    -
    .

     Does not work yet

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    I found a way to test it and discovered that it does not work yet.
    Will upload a fix soon, stay tuned.
    Kind regards,


    Reply to this

    -

     Re: Does not work yet

     
     by rvs82 on: Dec 21 2011
     
    Score 50%

    Thanks, I was just about to post the error message I got :) I tried finding the bug myself, but didn't manage to. I'll await the final update.


    Reply to this

    -
    .

     Re: Re: Does not work yet

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    Another update, another try.
    This time it works here at least.
    Kind regards,



    -
    .

     Re: Re: Does not work yet

     
     by rvs82 on: Dec 21 2011
     
    Score 50%

    I still get the same error message:

    Quote:
    Iotop could not be started.
    Information:
    ^[[?1049h^[[1;24r^[<B^[[m^[[41^[[?7h^[[?1l^[>Traceback (most recent call last):
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks//contents/iotop-0.4.3/iotop.py", line 12, in <module>
    main()
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/ui.py", line 582, in main
    main_loop()
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/ui.py", line 572, in <lambda>
    main_loop = lambda: run_iotop(options)
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/ui.py", line 484, in run_iotop
    return curses.wrapper(run_iotop_window, options)
    File "/usr/lib/python2.7/curses/wrapper.py", line 49, in wrapper
    curses.nocbreak()
    _curses.error: nocbreak() returned ERR


    Also, the script never reaches the point where it asks for my password. I'm running OpenSUSE 12.1 (32-bit).



    -
    .

     Re: iotop requires root permissions

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    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,


    Reply to this

    -

     Re: Re: iotop requires root permissions

     
     by rvs82 on: Dec 21 2011
     
    Score 50%

    I get the following (after turning on iotop in the settings window):

    –Error
    Traceback (most recent call last):
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/code/main.py", line 287, in readConfig
    self.netIFnumber=int(self.config('BusyTasks').readEntry('netIFnumber'))
    ValueError: invalid literal for int() with base 10: ''
    mv: cannot stat `/home/user/.toprc': No such file or directory
    mv: cannot stat `/home/user/.toprcorig': No such file or directory
    Traceback (most recent call last):
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks//contents/iotop-0.4.3/iotop.py", line 12, in <module>
    main()
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/ui.py", line 582, in main
    main_loop()
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/ui.py", line 572, in <lambda>
    main_loop = lambda: run_iotop(options)
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/ui.py", line 482, in run_iotop
    return run_iotop_window(None, options)
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/ui.py", line 476, in run_iotop_window
    process_list = ProcessList(taskstats_connection, options)
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/data.py", line 347, in __init__
    self.update_process_counts()
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/data.py", line 403, in update_process_counts
    stats = self.taskstats_connection.get_single_task_stats(thread)
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/data.py", line 161, in get_single_task_stats
    reply = GeNlMessage.recv(self.connection)
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/genetlink.py", line 50, in recv
    msg = conn.recv()
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/iotop-0.4.3/iotop/netlink.py", line 229, in recv
    raise err
    OSError: Netlink error: Operation not permitted (1)
    Tried attaching memory
    Tried attaching memory
    Tried attaching memory
    Tried attaching memory
    Tried attaching memory
    Tried attaching memory
    Tried attaching memory
    Tried attaching memory
    Tried attaching memory
    –Error
    Traceback (most recent call last):
    File "/home/user/.kde4/share/apps/plasma/plasmoids/BusyTasks/contents/code/main.py", line 645, in paintInterface
    iotext=re.search('.*?\t([0-9.]{,}).([0-9.]{,}).([KM]{,}B/s).([0-9.]{,}).([KM]{,}B/s).([0-9.]{,}).([KM]{,}B/s).(.*)', self.iotopsmemory.read())
    AttributeError: 'int' object has no attribute 'read'

    This basically repeats itself 3 times after which it loops on the last error (AttributeError). I get the error window after the lines with "Tried attaching memory" with the message I showed in the earlier post (also 3 times).

    Hope this helps.


    Reply to this

    -

     Re: Re: Re: iotop requires root permissions

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    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


    Reply to this

    -

     Re: Re: Re: Re: iotop requires root permissions

     
     by rvs82 on: Dec 21 2011
     
    Score 50%

    When I do the first (as normal user) I get the same netlink error as before.
    The 2nd (kdesu) I don't get any errors, nor any output.
    The 3rd (sudo) I get the correct iotop output.


    Reply to this

    -

     Re: Re: Re: Re: Re: iotop requires root permission

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    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?


    Reply to this

    -

     Re: Re: Re: Re: Re: iotop requires root permission

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    Just to make sure I get it right: nethogs works?


    Reply to this

    -

     Re: Re: Re: Re: Re: Re: iotop requires root permis

     
     by rvs82 on: Dec 21 2011
     
    Score 50%

    Nethogs works just fine. Both if I let it ask the password and if I set the password through the settings dialog.

    I use kdesu, but I don't think the problem lies there either. If I set the password in the settings dialog I still get the error. And if I do 'kdesu -c "konsole -e /PATH_TO_IOTOP/iotop.py"' it opens another console where the usual iotop output is shown.



    -

     Re: Re: Re: Re: iotop requires root permissions

     
     by rvs82 on: Dec 21 2011
     
    Score 50%

    Sorry, Python version is 2.7.2


    Reply to this

    -

     Re: Re: Re: Re: Re: iotop requires root permission

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    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,


    Reply to this

    -

     Re: Re: Re: Re: Re: iotop requires root permission

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    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,


    Reply to this

    -
    .

     Re: Re: Re: Re: Re: Re: iotop requires root permis

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    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,



    -

     Re: Re: Re: Re: Re: Re: iotop requires root permis

     
     by rvs82 on: Dec 21 2011
     
    Score 50%

    Works here too. Great job!

    I don't know what you changed, but it works for me.



    -
    .

     Re: Re: iotop requires root permissions

     
     by unknownSpirit on: Dec 21 2011
     
    Score 50%

    Glad it works but I am still pondering about the problem.
    Which version works? The debuginfo one?
    Kind regards,


    Reply to this

    -
    .

     Re: Re: Re: iotop requires root permissions

     
     by unknownSpirit on: Dec 22 2011
     
    Score 50%

    I updated 11.7 once again, with minor changes inherited from the debug release.
    So I think the official version eventually supports newer kernels.


    Reply to this

    -
    .

     Nethogs install breaks on ncurses.h

     
     by brucew on: Dec 22 2011
     
    Score 50%
    brucewbrucew
    Alcohol Justice
    Home
    -
    Bruce Wolfe 1

    Alcohol Justice
    United States of America, San Rafael
    Last visit Apr 4 2013
    0 Friends
    0 Groups

    More info
    Send a message
    Add as friend
    Other contents
    --

    I get this error after installing System V IPC package and before installing busytasks.plasmoid:

    Quote:
    ~/Downloads/KDE/Plasmoids/BusyTasks/BusyTasks-nethogs$ make install
    g++ -g -Wall -Wextra -c process.cpp
    process.cpp:4:21: fatal error: ncurses.h: No such file or directory
    compilation terminated.
    make: *** [process.o] Error 1


    Reply to this

    -
    .

     Re: Nethogs install breaks on ncurses.h

     
     by brucew on: Dec 22 2011
     
    Score 50%
    brucewbrucew
    Alcohol Justice
    Home
    -
    Bruce Wolfe 1

    Alcohol Justice
    United States of America, San Rafael
    Last visit Apr 4 2013
    0 Friends
    0 Groups

    More info
    Send a message
    Add as friend
    Other contents
    --

    Note: ncurses.h is natively installed at:
    /usr/include/ncursesw/ncurses.h


    Reply to this

    -
    .

     Re: Re: Nethogs install breaks on ncurses.h

     
     by unknownSpirit on: Dec 22 2011
     
    Score 50%

    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?


    Reply to this

    goto page: prev   1  2  3 

    Add commentBack






    -
    -
    How do you like Plasma 5?
     The best KDE Desktop ever.
     Definitely a nice improvement.
     Not decided yet. Haven't tried it yet.
     I do not like some of the changes.
     KDE is taking the wrong way.
     I am still sticking with KDE 3.5.
     I have no opinion, but wanted to vote anyway.

    resultmore
     
     
     Who we are
    Contact
    More about us
    Frequently Asked Questions
    Register
    Twitter
    Blog
    Explore
    Apps
    Jobs
    Knowledge
    Events
    People
    Updates on identi.ca
    Updates on Twitter
    Facebook App
    Content RSS   
    Events RSS   

    Participate
    Groups
    Forum
    Add App
    Public API
    About KDE-Apps.org
    Legal Notice
    Spreadshirt Shop
    CafePress Shop
    Advertising
    Sponsor us
    Report Abuse
     

    Copyright 2003-2014 KDE-Apps.org Team  
    All rights reserved. KDE-Apps.org is not liable for any content or goods on this site.
    All contributors are responsible for the lawfulness of their uploads.
    KDE and K Desktop Environment are trademarks of KDE e.V.