Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#16238 - [kdebase-workspace] Disk usage Plasmoid not working
Attached to Project:
Arch Linux
Opened by andi (turing) - Thursday, 17 September 2009, 16:28 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 28 November 2009, 21:14 GMT
Opened by andi (turing) - Thursday, 17 September 2009, 16:28 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 28 November 2009, 21:14 GMT
|
DetailsDescription:
In KDE 4.2 it worked well, but since 4.3 it does not show any partitions. I have the problem on my desktop and laptop system. I'm using x86_64 and hoped that the problem will disappear on 4.3.1 but it did not. I found a thread about it: http://forums.freebsd.org/showthread.php?p=37338 and the same thing works here. Using "export LC_ALL=C" and restarting plasma-desktop => the plasmoid works fine. But with my standard de_DE.utf8 it doesn't. I don't have any experience in automated patching, but the attached file should help you. It has to be applied to the src/kdebase-workspace-4.3.1/plasma/applets/system-monitor/hdd.cpp file. Additional info: * package version(s) 4.3.1-1 * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Saturday, 28 November 2009, 21:14 GMT
Reason for closing: Upstream
Additional comments about closing: please report upstream
Saturday, 28 November 2009, 21:14 GMT
Reason for closing: Upstream
Additional comments about closing: please report upstream
Comment by Pierre Schmitz (Pierre) -
Thursday, 17 September 2009, 16:51 GMT
You should report this upstream then. The patch looks more like a workaround than a fix; but I did not check the context.
hdd.patch