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. > > ** if gpodder starts them, why doesn't gpodder close them down at exit? > > gPodder does not explicitly start them. All gPodder does that could be > related is load the PyGTK module. I don't think this will start the > daemons mentioned. Can you please try to run gpodder with the > "--verbose" switch and watch your process list to see when these daemons > are started? Yes. Started: # gpodder --verbose and as soon as I start playing a video clip, the: /--------------\ /-------------------\ | Use X settings | | Keep GNOME Settings | \--------------/ \-------------------/ come up again, and my own xsettings are changed. sh: jackd: command not found sh: jackd: command not found show up in the xterm too. > > * gpodder/gconf screws up my xsettings: > > > > ** I have 'xset r rate 300 50' in my ~/.xsessions; 'xset q' shows > > "auto repeat delay: 300, repeat rate: 50" > > ** after quitting from gpodder they look different: > > "auto repeat delay: 500, repeat rate: 30" > > ** similar things happen with "Pointer Control", acceleration and > > threshold are modified > > Can you try to remove the gconf package or stop gconfd-2 from running to > see if these settings are modified by gconf or gPodder? Looks like that if I kill gconfd-2 and restore my own xsettings no questions are asked and no settings changed. > I suspect these may be modified by gnome-settings-daemon, but please > test to see which one is the culprit here. > > > * I see "sh: jackd: command not found" in the xterm window I started > > gpodder from; what is it trying to do? > > Please run gPodder with the "--verbose" switch and post the complete > output here. I killed all of these: gconfd-2, gnome-vfs-daemon and gnome-settings-daemon and restarted: # gpodder --verbose as soon as I start playin a video clip, 'ps' shows the following: /usr/lib/libgconf2-4/gconfd-2 20 /usr/lib/gnome-vfs-2.0/gnome-vfs-daemon /usr/lib/control-center/gnome-settings-daemon and the irritating: /--------------\ /-------------------\ | Use X settings | | Keep GNOME Settings | \--------------/ \-------------------/ too :( I also noticed this in the process table: /usr/bin/dbus-launch --exit-with-session /usr/bin/seahorse-agent --execute sh ~/.xsession It may be that what pushes up gconf (seahorse dependencies show gconf2). It's not obvious to me what starts dbus-launch :( Cheers, -- Cristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
