Hello, Cristian!

Cristian Ionescu-Idbohrn wrote:
> Hi Thomas,
> 
> On Mon, 3 Dec 2007, Thomas Perl wrote:
> 
>> Cristian Ionescu-Idbohrn wrote:
>>> Package: gpodder
>>> Version: 0.10.2-2
>>> Severity: normal
>>>
>>> I run gpodder under window maker (not gnome).
>>>
>>> * at startup, I am asked if I want to keep my xsettings (or something
>>>   similar); it doesn't seem to matter what I annswer to that; settings are
>>>   changed regardless
>> Can you give the exact message and (while the message is open) the
>> output of "ps ax"?
> 
> Here it is:
> 
> ,----
> | The X system keyboard settings differ from your current GNOME keyboard
> | settings.
> |
> | Expected was model "pc105", layout "se" and no options, but the the
> | following settings were found: model "pc105", layout "se" and option "ctrl
> | ctrl:nocaps".
> |
> | Which set would you like to use?
> |
> |  /--------------\   /-------------------\
> | | Use X settings | | Keep GNOME Settings |
> |  \--------------/   \-------------------/
> `----
> 
> It comes up when I start playing a video clip I just downloaded.
> 
>> gPodder does not display these settings, so this
>> might be related to gnome-settings-daemon or similiar.
> 
> Yes.  I notice now that:
> 
>   /usr/lib/libgconf2-4/gconfd-2 11
> 
> is already started when X comes up.  I didn't yet figure out where it's
> started from, but it's there long before I start gpodder.
> 
> After I start gpodder I notice these processes:
> 
>   totem 
> file://.../gpodder-downloads/ed7f77e59b16f43a28ad0eacf09f09a1/2055dbe4e2f5d9e6ee06a96c6134ecb7.mp4
>   /usr/lib/gnome-vfs-2.0/gnome-vfs-daemon
>   /usr/lib/control-center/gnome-settings-daemon
> 
> are active.  Could be either gconfd-2 or gpodder itself that start those.
> 
>>> * after exiting gpodder, I see some processes which were not there before
>>>   I started gpodder: /usr/lib/gnome-vfs-2.0/gnome-vfs-daemon,
>>>   /usr/lib/control-center/gnome-settings-daemon and
>>>   /usr/lib/libgconf2-4/gconfd-2
>>>
>>>   ** does gpodder require these daemons?
>> Neither gnomevfs nor gconf is used. Maybe they get invoked by GTK/PyGTK?
> 
> Could be.  Killed gnome-vfs-daemon and gnome-settings-daemon now.

The culprit is totem, then. Totem is a "fully GNOME-ified" app. These
changes and processes only start when you watch a video, right?

You might try to install xine or gmplayer and set xine/gmplayer as your
preferred media player in gPodder's preferences. This way, when you
click on "play" to play a video or audio file, xine/gmplayer get
launched instead of totem, so no GNOME-ified app gets started :)

Does using gmplayer or xine fix your problem?

Thomas



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to