Bug#477622: [Pkg-xfce-devel] Bug#477622: xfce4-xfapplet: xfapplet process does not die when X server is killed
On Wed, Apr 23, 2008 at 10:51 PM, Yves-Alexis Perez [EMAIL PROTECTED] wrote: If you kill the panel, do you reproduce this? Actually, I can't reproduce it by anything other than pressing Ctrl + Alt + Del. I tried killing xfce4-panel both with TERM and KILL signals, and xfce4-xfapplet dies as it should. Then I tried killing the X server itself (launched by gdm) both with TERM and KILL signals, and again xfce4-xfapplet dies. It's only when X server is killed by that special key sequence (I don't know enough about X to know what the difference is between that and sending KILL signal to the X server process) that xfapplet survives. Thanks, Andrzej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#470599: [Pkg-xfce-devel] Bug#470599: Bug#470599: /etc/xdg/xfce4/xinitrc ignores Xsession.options in handling ssh-agent
On Thu, Mar 13, 2008 at 12:13 AM, Yves-Alexis Perez [EMAIL PROTECTED] wrote: Well, it kills ssh-agent only if it has run it. And it kills the one it ran, using SSH_AGENT_PID. So if you run keychain after that, it shouldn't kill its ssh-agent. If it does, there's a bug in ssh-agent. I see that I was mistaken about what ssh-agent -k actually does (and it's probably improbable for a program to export a new SSH_AGENT_PID into the shell process running xfce4's xinitrc). But the main problem is, keychain won't run another ssh-agent process if it finds one already running. This is its sole purpose---enable use of the same ssh-agent across logins---so that can't be fixed (unless there's an easy way to distinguish xfce4-launched ssh-agent processes from ssh-agent process from a previous session). And what I really consider as bug isn't the fact that xfce4 runs ssh-agent---it's the fact that to disable it, one has to dig into xfce4-specific xinitrc, if one knows to look there at all (I didn't and it took me a while before I decided grepping the entire /etc for ssh-agent would be faster). I thought in Debian this can really be considered a bug, given that Xsession.options can be expected to exist and options set there ought to be respected, but perhaps the XFCE4 developers can gauge better whether the same can be expected on other distributions as well and xfce4's own xinitrc should check for a central options file for common configurables. That is, if they can spare time for a minor issue like this (probably affecting ... only keychain users). Thanks, Andrzej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#470599: [Pkg-xfce-devel] Bug#470599: /etc/xdg/xfce4/xinitrc ignores Xsession.options in handling ssh-agent
On Wed, Mar 12, 2008 at 3:21 AM, Yves-Alexis Perez [EMAIL PROTECTED] wrote: Here, the running ssh-agent is by Xsession stuff, not by xfce's xinitrc (the line is like ssh-agent gpgagent --daemon ... dbus-launch --exit-with-session startxfce4). I should have clarified. I already edited Xsession.options to comment out use-ssh-agent, but even then, ssh-agent kept getting mysteriously killed, until I found xfce4's xinitrc that has its own ssh-agent-related lines, which does its own thing with ssh-agent, if ssh-agent isn't run with the common Xsession script. And that's what I considered a bug---xfce4's xinitrc is not working with the rest of the X: if the user wants ssh-agent launched with X and has use-ssh-agent defined, then xfce4's xinitrc is not doing anything useful in that regard, and if the user does not want ssh-agent launched with X (i.e. use-ssh-agent is not defined in Xsession.options), xfce4 launches ssh-agent anyway and kills it on exit. Regards, Andrzej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#470599: [Pkg-xfce-devel] Bug#470599: Bug#470599: /etc/xdg/xfce4/xinitrc ignores Xsession.options in handling ssh-agent
On Wed, Mar 12, 2008 at 9:47 AM, Yves-Alexis Perez [EMAIL PROTECTED] wrote: Well, that is for people not using Xsession.d but still using startxfce4. startxfce4 is the upstream way to run Xfce, wich is what user may expect to have when it uses Xfce on whatever distro. If you don't want this behavior, you're free to edit it. But this is still a sane default, imho. Well, even in that scenario, I don't see how this would be a sane default: this configuration launches ssh-agent for the vast majority who do not use ssh-agent or don't even know that ssh-agent is installed on their machine, and it kills ssh-agent prematurely on those who rely on it so much that they want to be able to access it across login sessions, by using something like keychain (this default configuration accomplishes this in two ways: (1) when ssh-agent is launched before keychain had a chance to run, it suppresses keychain from launching its own ssh-agent (since that is the sole purpose of the script), (2) because the particular ssh-agent is not identified and tracked, even if I were to run a separate ssh-agent on the side, xfce4 will kill it on logout with ssh-agent -k). But, since it sounds like this is something coming from the upstream, not the Debian package, I'll try taking it to the upstream and see what they'll say. Perhaps they'll see the value in cooperating with the remainder of X server setup and not introducing/keeping odd, hard-to-track behaviors into/in xfce4's default setup (after all, it's always easier for the user to run a program that they want but is not running than it is for them to track down what keeps killing the program that they don't want killed). Regards, Andrzej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
