Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Some applications freezing up

1 view
Skip to first unread message

Daniel Dalton

unread,
Dec 22, 2012, 3:40:01 AM12/22/12
to
Hello,

When I launch some applications from within gnome 3 mainly rhythmbox and
gmpc the following occurs:
* The fan goes to pull speed.
* The desktop is locked up for about a minute
* After about a minute the fan slows back down and the desktop is no
longer frozen allowing me to use these programs.

Does anyone have some ideas why this might be occurring and how to fix
it?

Basically I can't use rhythmbox or gmpc unless I'm happy to wait a
minute first for the desktop to become unfrozen.

I'm also using debian wheezy.

Thanks in advance.

Dan


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012122208...@gwsc.vic.edu.au

Chris Bannister

unread,
Dec 22, 2012, 4:30:01 AM12/22/12
to
On Sat, Dec 22, 2012 at 07:36:18PM +1100, Daniel Dalton wrote:
> Hello,
>
> When I launch some applications from within gnome 3 mainly rhythmbox and
> gmpc the following occurs:
> * The fan goes to pull speed.
> * The desktop is locked up for about a minute
> * After about a minute the fan slows back down and the desktop is no
> longer frozen allowing me to use these programs.
>
> Does anyone have some ideas why this might be occurring and how to fix
> it?

Without knowing the hardware specs, I can only guess that the
DE/software you are using is wanting more resources than the laptop� can
handle. You could try using a DE/software which is lighter e.g LXDE,
XFCE or even just a WM and start you software from an Xterm when needed.

� Guessing it's a laptop because of audible fan speed changes

--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20121222090626.GC3507@tal

berenge...@neutralite.org

unread,
Dec 22, 2012, 6:30:02 AM12/22/12
to
> You could try using a DE/software which is lighter e.g LXDE,
> XFCE or even just a WM and start you software from an Xterm when
> needed.

In short: he can stop to use a bloated desktop environment? ;)
To be honest, I can not say you're wrong, but I guess the OP does not
really want to try a new DE, he might had enough difficulties to be
accustomed to gnome 3 :D

Ok, end of troll for now, constructive reply is taking place:

Some tools will allows you to have better clue about what exactly in
your hardware is not powerful enough, look at any resources monitors you
want, which gave you some history. (I am using xosview, as example, but
there are plenty in aptitude)
The interest is that you will know how to fight the problem: if the
problem is related to high ram consumption, try to locate processes
which are eating it, if you discover that the GPU is never quiet, find
the software(s) you do not need which are running in background.

It seems your problem is related to strong GPU use (there is cooler on
hard disk, as far as I know), so I think you could simply try to look at
$top (in a terminal) when you are doing nothing, to detect the bloatware
which thinks it is alone on your computer.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2c0ae124f5e9eb6e...@neutralite.org

Daniel Dalton

unread,
Dec 22, 2012, 6:50:01 AM12/22/12
to
On Sat, Dec 22, 2012 at 12:27:40PM +0100, berenge...@neutralite.org wrote:
> >You could try using a DE/software which is lighter e.g LXDE,
> >XFCE or even just a WM and start you software from an Xterm when
> >needed.
>
> In short: he can stop to use a bloated desktop environment? ;)
> To be honest, I can not say you're wrong, but I guess the OP does
> not really want to try a new DE, he might had enough difficulties to
> be accustomed to gnome 3 :D

Ok, first of all I'm blind and it seems to be the most accessible option
at this time.
Lxde and xfce4 are gtk based and are alternatives, but I'm reasonably
happy with gnome tbh.

> Some tools will allows you to have better clue about what exactly in
> your hardware is not powerful enough, look at any resources monitors
> you want, which gave you some history. (I am using xosview, as
> example, but there are plenty in aptitude)

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?

Running top shows many running processes (that's normal?).
The top few are things I use eg. brltty cpufreq etc. so looks pretty
reasonable.

Thanks,
Dan


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012122211...@gwsc.vic.edu.au

berenge...@neutralite.org

unread,
Dec 22, 2012, 7:10:02 AM12/22/12
to
> 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...

> 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.

> The top few are things I use eg. brltty cpufreq etc. so looks pretty
> reasonable.
>
> Thanks,
> Dan

And when you start one of your freezing softwares, and still look at
top, does it takes bit amount of RAM/CPU?
I'm not experienced enough with gnome, but maybe they are really heavy
to load. But it sounds strange anyway to simply run a software is able
to freeze a computer with a ssd, 4G of ram etc...
Btw, seeing other people's stuff make me thing mine is sooo outdated :D
(but it runs well so I do not mind)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/d5046ac0f85b76c3...@neutralite.org

Andrei POPESCU

unread,
Dec 22, 2012, 7:30:01 AM12/22/12
to
On Sb, 22 dec 12, 19:36:18, Daniel Dalton wrote:
> Hello,
>
> When I launch some applications from within gnome 3 mainly rhythmbox and
> gmpc the following occurs:
> * The fan goes to pull speed.
> * The desktop is locked up for about a minute
> * After about a minute the fan slows back down and the desktop is no
> longer frozen allowing me to use these programs.

I get similar symptoms when mutt encounters a new GPG key in a
mailinglist and gpg rebuilds the trustdb, completely hogging one core. I
can tell because I have a CPU monitor in the panel.

My suggestion would be to find some application that can write a log
with sufficient granularity to see which part of your system is hogged
(but my money is on the CPU). This could also be a home made script ;)

You might need to 'nice' the monitor application/script so that it will
be able to do its work while the hog is locking up your system.

Good hunting,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
signature.asc

Daniel Dalton

unread,
Dec 22, 2012, 8:00:01 AM12/22/12
to
On Sat, Dec 22, 2012 at 12:59:53PM +0100, berenge...@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

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

(rhythmbox:8210): GLib-GObject-CRITICAL **: g_value_set_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012122212...@gwsc.vic.edu.au

Lisi Reisz

unread,
Dec 22, 2012, 8:20:01 AM12/22/12
to
On Saturday 22 December 2012 11:44:41 Daniel Dalton wrote:
> Ok, first of all I'm blind and it seems to be the most accessible option
> at this time.

That's really interesting. Could you elaborate on why?

Thanks,
Lisi


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/201212221313.4...@gmail.com

berenge...@neutralite.org

unread,
Dec 22, 2012, 8:50:01 AM12/22/12
to
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-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/692e4ec80d97710a...@neutralite.org

Andrei POPESCU

unread,
Dec 22, 2012, 1:20:02 PM12/22/12
to
On Sb, 22 dec 12, 14:43:26, berenge...@neutralite.org wrote:
>
> 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.

Maybe it's doing some database indexing or so. For simple listening mpd
runs fine on the Raspberry Pi (with AAC streams) and even on a router
with 240Mhz MIPS CPU (but only with MP3 streams).

Kind regards,
signature.asc

berenge...@neutralite.org

unread,
Dec 22, 2012, 2:50:01 PM12/22/12
to
Le 22.12.2012 19:09, Andrei POPESCU a écrit :
> On Sb, 22 dec 12, 14:43:26, berenge...@neutralite.org wrote:
>>
>> 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.
>
> Maybe it's doing some database indexing or so. For simple listening
> mpd
> runs fine on the Raspberry Pi (with AAC streams) and even on a router
> with 240Mhz MIPS CPU (but only with MP3 streams).
>
> Kind regards,
> Andrei

Maybe, but I think mpd do such things when you explicitly ask it to
update the database. However, I've clue about that. I did not
investigate more, because it is not the bigger performance problem on my
computer, so... And yes, anyway it works well on a very old computer of
mine when there it have not too many tasks to do :) that's why I use it
since many months now, and just forgot vlc (which became more and more
dirty and heavy in my opinion. I think it just disgusted me at max near
v0.95, when random misteriously stopped to be random, which can not be a
bug, but a will, because random is so easy to implement in C/C++...)
which I was using before.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/cd36d5f0e041df9d...@neutralite.org

Bob Proulx

unread,
Dec 22, 2012, 8:50:02 PM12/22/12
to
Andrei POPESCU wrote:
> Daniel Dalton wrote:
> > When I launch some applications from within gnome 3 mainly rhythmbox and
> > gmpc the following occurs:
> > * The fan goes to pull speed.
> > * The desktop is locked up for about a minute
> > * After about a minute the fan slows back down and the desktop is no
> > longer frozen allowing me to use these programs.
>
> I get similar symptoms when mutt encounters a new GPG key in a
> mailinglist and gpg rebuilds the trustdb, completely hogging one core. I
> can tell because I have a CPU monitor in the panel.

I get similar behavior from the fsync() fiasco. Everyone has been
told they are a bad programmer unless they defeat the filesystem
buffer cache by using fsync() everywhere. This forces a cache flush
to the drive and everything waits while it is doing so. If using
'eatmydata' avoids the behavior then you know that is the problem.

Bob
signature.asc

berenge...@neutralite.org

unread,
Dec 22, 2012, 9:20:01 PM12/22/12
to
> Everyone has been
> told they are a bad programmer unless they defeat the filesystem
> buffer cache by using fsync() everywhere.

Huh?
So, everyone think we should all go back to the ms-dos world, when each
programmer had to know everything about the hardware?

Hum...
Maybe I should leave my hopes to have a correct job in development...
I wonder if producing craps is really the only solution to live from
doing something you like? Seriously, every-time I hear someone winning
about the fact he bought crap, the winner is often complaining about
crap he did not bought for many money.

I'm starting to think I should be mad, to want a world were non-cheap
products are the rule, and are able to be repaired and used for more
than 10 years...
Is there is someone else, who is less that 30 years old, thinking like
me (at least on that point), in western europe? because I'm really
startting to think I'm a mad guy, thinking that past items should not
just be "recycled" but repaired while they can...

sorry, I'm feeling quite bad actually, and I know I should not put that
here... but I'm not in a state were I can really control my thinking.
And to be honest, I would be unable to control it more often...

> This forces a cache flush
> to the drive and everything waits while it is doing so. If using
> 'eatmydata' avoids the behavior then you know that is the problem.
>
> Bob

Oh, so, maybe I'm not the only one to think that we, software
developers, should let kernel programmers do their job, and simply rely
on what they give to us?
Thanks a lot... because I'm so tired to see dumb structures in
softwares, and I'm so young!

I really would like to understand why people think it is a problem to
do softwares able to run on lower hardware... if someone have any clue,
I really want to know it!


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/840f65a194ad2c90...@neutralite.org

John Hasler

unread,
Dec 22, 2012, 9:40:01 PM12/22/12
to
berenger.morel writes:
> I really would like to understand why people think it is a problem to
> do softwares able to run on lower hardware... if someone have any
> clue, I really want to know it!

Because they aren't very good programmers. And that's a problem,
because there is more programming to do than there are good programmers
to do it.
--
John Hasler


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/87a9t5s...@thumper.dhh.gt.org

berenge...@neutralite.org

unread,
Dec 23, 2012, 11:10:02 AM12/23/12
to
Le 23.12.2012 03:37, John Hasler a écrit :
> berenger.morel writes:
>> I really would like to understand why people think it is a problem
>> to
>> do softwares able to run on lower hardware... if someone have any
>> clue, I really want to know it!
>
> Because they aren't very good programmers. And that's a problem,
> because there is more programming to do than there are good
> programmers
> to do it.
> --
> John Hasler

But what I do not understand is why it is starting to become a rule to
avoid performances. Sounds like people think it is a good thing to do
the job of the OS or the WM in a simple application. Now, we are
starting to have HTML interpreters, aka web browsers (just an example),
able to manage windows, load and execute programs, access to webcams...
and mozilla is building OSes...

I'm not a good programmer (or at least, I do not think to be good
enough to claim such thing), but I know that I am not able to build an
OS (well, I must admit that is might because I tried in my first years
of programming ^^).
I do not understand why people are taking what is obviously the wrong
way to do things: reimplementing features which are already given by
other softwares, in applications which are not specialized in those
features.
The most obvious example is window management, I think. Most softwares
nowadays implement window management features, like tabbed and MDI
interfaces (and we can see consequences: memory leaks, crash which makes
you loose all your work, strange behaviors, ...)
And the post from which I replied was speaking about people who just
think they can manage disk access better than the kernel!

Is not it non-sense? Being a good programmer or not is not the problem
here, even a newbie could understand that multiplying features in a
software makes it harder to maintain and memory hungry... no?


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/fb08b87cc8157213...@neutralite.org

Daniel Dalton

unread,
Dec 25, 2012, 10:00:02 PM12/25/12
to
On Sat, Dec 22, 2012 at 02:43:26PM +0100, berenge...@neutralite.org wrote:
> It is a bug problem, but not related to Glib-GObject.

yeah
> 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).

Yes... I always use mpc and it works with no problem.

Also control mpd from within emacs through emms is just fine also.

> 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.

Ok so it looks like mpd is not the problem.

The common problems are occurring with rhythmbox and gmpc.

So it is hard to know what is the problem, maybe a commonly used library
between the two (rhythmbox and gmpc)?

Cheers,
Dan


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012122602...@gwsc.vic.edu.au

berenge...@neutralite.org

unread,
Dec 26, 2012, 8:20:02 AM12/26/12
to
> Yes... I always use mpc and it works with no problem.
>
> Also control mpd from within emacs through emms is just fine also.

huhu... sometimes I think that emacs is a really a full OS :D

>> 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.
>
> Ok so it looks like mpd is not the problem.
>
> The common problems are occurring with rhythmbox and gmpc.
>
> So it is hard to know what is the problem, maybe a commonly used
> library
> between the two (rhythmbox and gmpc)?

I have no idea since I do not even know them.
Maybe those softwares are using their own database?

But I just took an eye to rythmbox's dependencies... that's ugly to
bind a software to so many libs, introducing a bug is really easy...
well, not my problem, since I do not intend to use such kind of
softwares.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/9f82b1449d164892...@neutralite.org

Daniel Dalton

unread,
Dec 26, 2012, 9:10:02 PM12/26/12
to
On Wed, Dec 26, 2012 at 02:14:35PM +0100, berenge...@neutralite.org wrote:
> Maybe those softwares are using their own database?

Rhythmbox yes, gmpc, would use mpd though?
> well, not my problem, since I do not intend to use such kind of
> softwares.

I can avoid rhythmbox, but it'd be nice to have at least one of the gui
apps working.

Anyway looks like it is going to be tricky to debug so I suppose command
line is better for now.

Cheers,
Dan


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012122702...@gwsc.vic.edu.au

berenge...@neutralite.org

unread,
Dec 26, 2012, 9:30:01 PM12/26/12
to


Le 27.12.2012 03:05, Daniel Dalton a écrit :
> On Wed, Dec 26, 2012 at 02:14:35PM +0100,
> berenge...@neutralite.org wrote:
>> Maybe those softwares are using their own database?
>
> Rhythmbox yes, gmpc, would use mpd though?
>> well, not my problem, since I do not intend to use such kind of
>> softwares.
>
> I can avoid rhythmbox, but it'd be nice to have at least one of the
> gui
> apps working.
>
> Anyway looks like it is going to be tricky to debug so I suppose
> command
> line is better for now.
>
> Cheers,
> Dan

Hum... thinking about it, using valgrind might give you some hints
about where is the problem.

About gmpc to not build it's own db, I've seen sqlite3 in it's
dependencies. I guess it is using it to store informations mpd does not
manage.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/3bc122b5c0d6c5c4...@neutralite.org
0 new messages