Le 22.12.2012 13:51, Daniel Dalton a écrit :
On Sat, Dec 22, 2012 at 12:59:53PM +0100,
berenger.mo...@neutralite.org wrote:
>Hmm, I really hope it is not h/w problem:
>Intel core I5 2.4 Ghz 4 gb ram 128 gb ssd.
>
>Do you still think it's a h/w problem?
I do not know, it depends on how many stuff you have loaded at the
same time. But... well, to be honest, seeing your computer, I do not
really think it could be that...
I don't really have anything running asside from some basic daemons
and
it is the only gui application running.
>Running top shows many running processes (that's normal?).
Yes, even on my configuration, which aim to be very lightweight, top
gave me many things, I guess most are kernel relative.
Yeah, so it does look like rhythmbox could possibly be hogging cpu.
from a quick look.
I did some research and found:
* if I run rhythmbox from the terminal here are the errors I see.
(below
my name)
* I thought it could be "libglib2.0-0" causing some problems as it is
a
dependency of gmpc and rhythmbox.
However, I have no solution at this stage rather than saying it is
likely some bug?
output below my name.
Cheers,
Dan
It is a bug problem, but not related to Glib-GObject.
Gtk libs do plenty of assertions, which are here to help users
(developers which uses the lib) to solve problems.
Assertions are the clue of programming error in the "client" software,
here, the source of those problems is probably rhytmbox.
Anyway, it might not be the cause of your hangs.
Sounds like you are using mpd to play music. I have noticed that
sometimes it uses more CPU than it really needs (restart it usually fix
the problem so...) so it could be an mpd problem.
If you really think it might be the client (gmpc) try mpc, the
command-line client, ncmpcpp (a ncurse client), or ario (a gtk client).
If you encounter the same problem with all of them, it is not the
client, so probably the server.
If you only have the problem with some of them, then you will have to
find a better, at least, less bugged, client.
One other thing that might cause the problem, is visualization, try to
disable it, maybe it is the cause of the slow down.
My opinion is that I now prefer mpc and ncmpcpp as clients, because
they are really lightweight, and do everything I need: mpc allows me to
create "desktop-wide" shortcuts while ncmpcpp allows me to have a
real-time interface.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/692e4ec80d97710a8afb23110d1b3...@neutralite.org
