You are not logged in.
Hi all
I have arch installed in vmware. I've used pacman to install xfce and can use it fine as root but cannot start it with a non-root account. I get the following error message
/etc/xdg/xfce4/xinitrc: line 77: 4578 Aborted $xfcesm
SSH_AGENT_PID not set, cannot kill agent
Is there a fix for this?
Jeremy
Offline
I've never had openssh installed but try
export SSH_AGENT_PID=`pidof sshd`
then start your xfce session.
If that doesn't work.
Start sshd by running '/etc/rc.d/sshd start' then start xfce
or
Run 'pacman -Rns openssh' to remove openssh then start xfce.
Last edited by hussam (2007-07-20 14:46:13)
Offline
I'll give that a go. I still find it strange that this problem only occurs with a non-root account. Why does that happen?
Offline
If this is the same problem that is discussed at this link: http://bbs.archlinux.org/viewtopic.php?id=33151
you could try changing all permissions in /tmp to 1777. Worked for me.
Offline
I have had this problem too (on two archlinux installs, mind me). It brought me on the verge of changing distros.
I needed a complete reinstall (one on each machine) to get rid of it. I suspect pacman, since it somehow mysteriously started after the 3.5.0-1 to 3.5.0-2 upgrade... A reinstall of all packages (as was advised) did not help in any way, nor did 'changing' /tmp permissions (which, by the way, were fine).
This is my story, for what it's worth
. Git pacman is supposed to fix it (someone mentioned it is a libalpm problem).
Last edited by B (2007-07-20 22:38:57)
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
I have had this problem too (on two archlinux installs, mind me). It brought me on the verge of changing distros.
I needed a complete reinstall (one on each machine) to get rid of it. I suspect pacman, since it somehow mysteriously started after the 3.5.0-1 to 3.5.0-2 upgrade... A reinstall of all packages (as was advised) did not help in any way, nor did 'changing' /tmp permissions (which, by the way, were fine).
This is my story, for what it's worth
. Git pacman is supposed to fix it (someone mentioned it is a libalpm problem).
So is your problem still unresolved?
Offline
sorry but im not so savvy with linux. with reference to http://bugs.archlinux.org/task/7194 what do i do with the filesystem install scrip or the snip of code available on the page?
jeremy
Offline
B wrote:I have had this problem too (on two archlinux installs, mind me). It brought me on the verge of changing distros.
I needed a complete reinstall (one on each machine) to get rid of it. I suspect pacman, since it somehow mysteriously started after the 3.5.0-1 to 3.5.0-2 upgrade... A reinstall of all packages (as was advised) did not help in any way, nor did 'changing' /tmp permissions (which, by the way, were fine).
This is my story, for what it's worth
. Git pacman is supposed to fix it (someone mentioned it is a libalpm problem).
So is your problem still unresolved?
As I said: I had to do a reinstall to 'fix' the problem. I built git pacman but it was unable to sync with the repo's.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
sorry but im not so savvy with linux. with reference to http://bugs.archlinux.org/task/7194 what do i do with the filesystem install scrip or the snip of code available on the page?
jeremy
That bug fix is implemented in pacman 3.5.0-2 , users should not need to change anything.
The easiest way to solve it (specially since you're using a VM) is probably to do a new FTP-installation.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline