Fuckyouuguys
On 04/06/13 20:58, Philippe Coval wrote:
> I just wanted to share that I faced this issue (100% cpu)
> but once upgraded to experimental version of dbus-x11
> it went away...
You had the same symptom, but there are likely to be multiple bugs that
can cause excessive CPU usage; for instance, I'm p
Package: dbus-x11
Followup-For: Bug #630002
I just wanted to share that I faced this issue (100% cpu)
but once upgraded to experimental version of dbus-x11
it went away...
Additional info, I use gnome-3.8.1 from experimental and not KDE as previously
reported
Hope this help
-- System
Am 15.05.2013 18:06, schrieb Simon McVittie:
> On 15/05/13 16:43, Alexander Mansurov wrote:
>> If I run htop, the two most CPU consuming processes are dbus-daemon
>> and udisks.
>
> dbus-daemon transports messages. If it's using a lot of CPU time, it
> is likely to be a bug in whatever process is
On 15/05/13 16:43, Alexander Mansurov wrote:
> If I run htop, the two most CPU consuming processes are dbus-daemon
> and udisks.
dbus-daemon transports messages. If it's using a lot of CPU time, it
is likely to be a bug in whatever process is causing those messages.
According to the clock_gettime
Package: dbus
Version: 1.6.8-1
the command from htop causing the 90%+ CPU load:
/usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
/proc/DBUD-PID/fd has 999 entries.
I have the impression that using icewease or icedove triggers that
behaviour, particularly when opening pdf
Package: dbus
Version: 1.6.8-1
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome
On Tue, 14 Jun 2011 at 15:39:37 +0100, Simon McVittie wrote:
> On Fri, 10 Jun 2011 at 11:53:55 +0400, Alexandr Bravo wrote:
> > After last update of dbus for amd64 testing "dbus-daemon --system" consumes
> > about 40% of CPU, which is not normal I think.
>
> Can you get strace output or a stack tr
On Fri, 10 Jun 2011 at 11:53:55 +0400, Alexandr Bravo wrote:
> After last update of dbus for amd64 testing "dbus-daemon --system" consumes
> about 40% of CPU, which is not normal I think.
Can you get strace output or a stack trace from the faulty dbus-daemon
to see what it's up to, similar to on
<
Package: dbus
Version: 1.4.8-3
Severity: important
After last update of dbus for amd64 testing "dbus-daemon --system" consumes
about 40% of CPU, which is not normal I think.
$ ps ax | grep dbus
837 ?S 0:00 /usr/bin/dbus-daemon --fork --print-pid 5
--print-address 7 --session
840
10 matches
Mail list logo