Re: Options for kdepim using kde 4.7/unstable?
Am Freitag, 16. März 2012 schrieb Dietz Pröpper: > Benjamin Eikel: > > > I suspect something like that, but can't nail it down. The fact, > > > that if I fire up gnome, I see the "expected" consumption, around > > > 15W, and on a freshly created account, kde pulls around 22W > > > idleing around indicates that it's in some way kde related I > > > think. > > > > have you tried "powertop" [1] to get an idea which process might be > > responsible for the power consumption? > > Indeed, I did, which led me to plasma-desktop in the first place. I see > around 300 wakeups/s, 1/3 of them via plasma-desktop. Expected are > around 120-150 on "my" kde workspace. Of course, in "idle" state. Hmmm, I have easily around 500-600 wakeups/second. But I do not even see plasma-desktop in the process list on the Overview tab of powertop. No, no plasma-desktop there at all. But stuff like KWin, Dolphin, Kmail, Akregator, some Konquerors which were preloaded - why are these doing anything anyway? -, sometimes Iceweasel, and various Nepomuk stuff like nepomukindexer, nepomukservicestubs and virtuoso-t, as well as postgres for Akonadi, some interrupt threads (I use threadirqs kernel option) and BTRFS. Still fan isn´t even running most of the time. Sandybrdige CPU is in C7 sleep state in 87% of the time. It idles in about 30-35% of the time and is at 800 MHz in about 60% of the time. Rest is distributed among frequencies with the bulk of 2-8% in turbo mode. The machine is basically doing nothing except for those wakeups. Thus is you have plasma-desktop in the first place, I think this is not normal. Unless you do not run anything else at all in the moment. I think I will try with all user applications closed and look again. I would test with a new user with a bog standard KDE configuration first. If that is better I would disable plasmoids one by one starting with those which I added yourself until I find the culprit. Since these are running in the context of plasma-desktop and I am not even sure whether they run as threads there, I do not know any other approach that would work. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203171147.19444.mar...@lichtvoll.de
Re: Options for kdepim using kde 4.7/unstable?
Am Samstag, 17. März 2012 schrieb Martin Steigerwald: > Thus is you have plasma-desktop in the first place, I think this is > not normal. Unless you do not run anything else at all in the moment. > I think I will try with all user applications closed and look again. So there we go - just two samples with all applications closed, all preloaded konquerors stopped, Akonadi stopped, Nepomuk told to stop indexing (whether it did, is another question): Summary: 355,2 wakeups/second, 0,0 GPU ops/second and 0,0 VFS ops/sec Usage Events/sCategory Description 100,0% Device Audio codec hwC0D0: Conexant 100,0% Device Audio codec hwC0D3: Intel 9,2 ms/s 89,2Processkwin -session 10cec7d36b0001315584005015999_1331979787_317189 12,3 ms/s 67,5Process/usr/bin/X :0 vt7 -br -nolisten tcp -auth /var/run/xauth/A:0-5Zjkna 2,0 ms/s 60,1Process[irq/44-i915] 1,0 ms/s 40,0Timer hrtimer_wakeup 257,1 µs/s 23,5Interrupt [44] i915 2,7 ms/s 14,2Process/usr/bin/konsole -session 10cec7d36b00013279203730100040021_1331979787_178488 79,4 µs/s 7,5Process[ksoftirqd/2] 143,2 µs/s 6,5Process[irq/43-ahci] 7,9 ms/s 2,8Process/usr/bin/plasma-desktop 66,6 µs/s 5,6Process[ksoftirqd/0] 243,3 µs/s 4,6Process[irq/16-mmc0] 400,8 µs/s 3,5Timer tick_sched_timer 39,9 µs/s 2,9Process[ksoftirqd/1] 19,9 µs/s 2,6Process[btrfs-endio-met] 92,2 µs/s 1,9Process[scsi_eh_2] 19,2 µs/s 1,9Interrupt [16] mmc0 16,8 µs/s 1,6Process[ksoftirqd/3] 150,0 µs/s 1,5Process/usr/bin/dirmngr --daemon --sh 361,7 µs/s 1,2Process[btrfs-transacti] 221,6 µs/s 1,2Process/usr/lib/upower/upowerd 40,1 µs/s 1,1Process[irq/9-acpi] 241,0 µs/s 1,0kWork disk_events_workfn 107,8 µs/s 1,1Process/usr/bin/python /usr/bin/hp-systray 124,5 µs/s 1,0kWork cache_reap 291,0 µs/s 0,8Process/usr/bin/dbus-daemon --system 194,3 µs/s 0,8Processkdeinit4: kded4 [kdeinit] 18,7 µs/s 0,7Interrupt [43] SATA controller 580,1 µs/s 0,5Processksysguardd 148,5 µs/s 0,5Process/usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_jd2710.ini +wait 106,5 µs/s 0,5Processudisks-daemon: polling /dev/sr0 16,0 µs/s 0,5kWork e1000_watchdog_task 3,7 µs/s 0,5kWork wq_barrier_func 2,6 µs/s 0,5kWork i915_gem_retire_work_handler 33,7 µs/s 0,5kWork gen6_pm_rps_work Summary: 261,3 wakeups/second, 0,0 GPU ops/second and 0,0 VFS ops/sec Usage Events/sCategory Description 100,0% Device Audio codec hwC0D0: Conexant 100,0% Device Audio codec hwC0D3: Intel 6,7 ms/s 75,1Processkwin -session 10cec7d36b0001315584005015999_1331979787_317189 10,6 ms/s 57,5Process/usr/bin/X :0 vt7 -br -nolisten tcp -auth /var/run/xauth/A:0-5Zjkna 1,3 ms/s 39,4Process[irq/44-i915] 273,0 µs/s 19,5Interrupt [44] i915 0,9 ms/s 16,5Timer hrtimer_wakeup 1,5 ms/s 6,8Process/usr/bin/konsole -session 10cec7d36b00013279203730100040021_1331979787_178488 81,0 µs/s 5,9Process[ksoftirqd/2] 164,2 µs/s 5,2Process[irq/43-ahci] 6,1 ms/s 2,1Process/usr/bin/plasma-desktop 50,1 µs/s 4,1Process[ksoftirqd/1] 21,1 µs/s 2,8Interrupt [43] SATA controller 345,4 µs/s 2,2Timer tick_sched_timer 114,2 µs/s 2,2Process[irq/16-mmc0] 39,0 µs/s 2,1Process[btrfs-endio-met] 91,0 µs/s
Re: Options for kdepim using kde 4.7/unstable?
Martin Steigerwald: > Am Freitag, 16. März 2012 schrieb Dietz Pröpper: > > Benjamin Eikel: > > > > I suspect something like that, but can't nail it down. The fact, > > > > that if I fire up gnome, I see the "expected" consumption, around > > > > 15W, and on a freshly created account, kde pulls around 22W > > > > idleing around indicates that it's in some way kde related I > > > > think. > > > > > > have you tried "powertop" [1] to get an idea which process might be > > > responsible for the power consumption? > > > > Indeed, I did, which led me to plasma-desktop in the first place. I > > see around 300 wakeups/s, 1/3 of them via plasma-desktop. Expected > > are around 120-150 on "my" kde workspace. Of course, in "idle" state. > > Hmmm, I have easily around 500-600 wakeups/second. On an idle system? > But I do not even see > plasma-desktop in the process list on the Overview tab of powertop. I see between 20 and 100 events from plasma-desktop, and around the same from the X sever (nvidia, Quadro FX 880M). CPU-wise, plasma-desktop permanently pulls 1-2% cpu time, and the x server another 3-5%. > Thus is you have plasma-desktop in the first place, I think this is not > normal. Ack. And the behaviour is not that clear that I can rule out other heavy electrons ;-). > Unless you do not run anything else at all in the moment. I > think I will try with all user applications closed and look again. Yes, that will be the next step. Did not really have the time to look into this much deeper. > I would test with a new user with a bog standard KDE configuration > first. That was the first try I gave ;-). And power consumption was basically the same. And, as written, it seems to be something kde related, because neither with a gnome desktop, nor with no X11 running at all I could reproduce the power drain. > If that is better I would disable plasmoids one by one starting > with those which I added yourself until I find the culprit. Since these > are running in the context of plasma-desktop and I am not even sure > whether they run as threads there, I do not know any other approach > that would work. Hopefully I'll have the time to look into that the next days a littl deeper. (You know, knowing that probably s.t. is broken on my side makes diagnosis much easier ;-). regards, Dietz -- To be a bug is a dumb thing, a silly and a bump thing, but to be a bug is something, and You're not a thing at all. signature.asc Description: This is a digitally signed message part.
Re: Okular::Document::openDocument: No plugin for mimetype '"application/epub+zip"'
Am Freitag, 16. März 2012 schrieb shirish शिरीष: > Hi all, Hi, > I was opening an .epub file and got the following statements and error > :- > > okular(25729)/kdecore (KConfigSkeleton) > KCoreConfigSkeleton::writeConfig: okular(25729)/kdecore > (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: > okular(25729)/kdecore (KConfigSkeleton) > KCoreConfigSkeleton::writeConfig: okular(25729)/kdecore > (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: > okular(25729)/okular (app) Okular::Document::openDocument: No plugin > for mimetype '"application/epub+zip"'. > > See the last line, it says no plugin for mimetype > "application/epub+zip" . Don't know what to make head or tail of it. > Okular version is 4:4.7.4-2 and system is up-to-date. The file itself > is good as I was able to open it in other apps. Do you have okular-extra-backends installed? Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203171606.37651.mar...@lichtvoll.de
