From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Iww01-0007Ea-Q5 for garchives@archives.gentoo.org; Tue, 27 Nov 2007 08:40:58 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lAR8d5IG000483; Tue, 27 Nov 2007 08:39:05 GMT Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id lAR8d4VG000478 for ; Tue, 27 Nov 2007 08:39:04 GMT Received: by ug-out-1314.google.com with SMTP id j3so1212083ugf for ; Tue, 27 Nov 2007 00:39:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=YIdMKQZJ7f8W+ARmqlFoUIalNQ0eibbXA+yW423ofW4=; b=oEKlY5wyv8roCIo3SOk88s7I2msQyvXGrbB1/udaD7tY8b/QORr6Nuusi1XQG9ZDVncFF2DySEb00mk6hluGrZ0/7VP0yxNoi3KrlsN4qbXX9+RFCJozqvteBp/9337f865HKWcvIoiowj/18W0fWn+WLAuZLLtEsjLPNpBIlNU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=XiVJKA6o7OVWqpo6ARHf8OxZSuP0hAl6xNOhFcJ3xLEoX6Hlx8p8phy5dxgSraqMTaQa10IWNyOCSOePnR5trRx3pf823it20kYRrwGeqfjyLV/kC4lhPcvUIu418moeIp3ZrstE+Ntoz1QEC2qyfHjt6GJ1AulrcubH5pzN/HM= Received: by 10.82.156.12 with SMTP id d12mr9862842bue.1196152743720; Tue, 27 Nov 2007 00:39:03 -0800 (PST) Received: by 10.82.141.15 with HTTP; Tue, 27 Nov 2007 00:39:03 -0800 (PST) Message-ID: Date: Tue, 27 Nov 2007 09:39:03 +0100 From: Beso To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] firefox vs firefox-bin restored on kde session In-Reply-To: <474B3E3E.9080004@nagafix.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1071_15008424.1196152743683" References: <47434E8B.1050608@nagafix.co.uk> <47447E8E.7030401@nagafix.co.uk> <474B3E3E.9080004@nagafix.co.uk> X-Archives-Salt: 99baa6a4-d682-4e23-b1c1-14086c08e78a X-Archives-Hash: fbc6dcfba282d07ac08b1472ca61db8d ------=_Part_1071_15008424.1196152743683 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 2007/11/26, Antoine Martin : > > Beso wrote: > > hmmm.... maybe you didn't understood.... > > when you shutdown, restart or whatever kde its last session will > continue to > > load as it was before restart. > Well, maybe you misunderstood my question: the session does not resume > as it was but with the wrong version of firefox. this is due to a wrong shutdown... the only way of this to happen is a forced kill of kde. there's no other way for it to happen. anyway for what i know of kde sessions you just need to remove everything in: /var/tmp/kdecache- /tmp/ksocket- and have these directories writable (but if you login they should already be writable). just in case do a ls -l on them and see if they are at least drwxr--r-- 2 users (this means that the directory is owned by the user, of group users which has full permissions, while the group members have read permission and the other users not in the users group have read permissions). this is the minimum required permissions for kde to run. if they're are lower (for the specific user) kde won't work. > the problem is that when you do a > > restart/shutdown ecc from the kde session the next time the session > which > > will load will be the last one to load, but when you do force a restart > then > > the last session would be the one before the forced restart. > That's not the problem here. as i've said before, it's quite impossible for kde to restart a wrong session on restart if it wasn't killed. > now, if this is not your case for firefox autostart there are 2 ways: > > 1. the firefoxstarter app > > 2. a link in your /home/foo/.kde/Autostart/ directory. > > for what i know there aren't other methods of autostarting something > > something on kde. > > if you want your firefox to load after login then place a symlink to > firefox > > in the autostart directory. > > you could also use the firefoxstarter, but it has the problem that you > have > > to exit it when flash breaks with nspluginwrapper. > I don't want to add an autostart (as shown above, that's easy), just > find where the session applications are saved so I can zap the wrong > copy of firefox from it (and script this step if necessary). > > Antoine hmmm, maybe you've added the autostart item in the Autostart. verify it and remove if necessary. look in the directory specified above. -- dott. ing. beso ------=_Part_1071_15008424.1196152743683 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

2007/11/26, Antoine Martin <antoine@nagafix.co.uk>:
Beso wrote:
> hmmm.... maybe you didn't understood....
> when you shutdown, restart or whatever kde its last session will continue to
> load as it was before restart.
Well, maybe you misunderstood my question: the session does not resume
as it was but with the wrong version of firefox.

this is due to a wrong shutdown... the only way of this to happen is a forced kill of kde. there's no other way for it to happen.
anyway for what i know of kde sessions you just need to remove everything in:

/var/tmp/kdecache-<user>
/tmp/ksocket-<user>

and have these directories writable (but if you login they should already be writable). just in case do a ls -l on them and see if they are at least drwxr--r--  2 <user> users (this means that the directory is owned by the user, of group users which has full permissions, while the group members have read permission and the other users not in the users group have read permissions). this is the minimum required permissions for kde to run. if they're are lower (for the specific user) kde won't work.

> the problem is that when you do a
> restart/shutdown ecc from the kde session the next time the session which
> will load will be the last one to load, but when you do force a restart then
> the last session would be the one before the forced restart.
That's not the problem here.

as i've said before, it's quite impossible for kde to restart a wrong session on restart if it wasn't killed.

> now, if this is not your case for firefox autostart there are 2 ways:
> 1. the firefoxstarter app
> 2. a link in your /home/foo/.kde/Autostart/ directory.
> for what i know there aren't other methods of autostarting something
> something on kde.
> if you want your firefox to load after login then place a symlink to firefox
> in the autostart directory.
> you could also use the firefoxstarter, but it has the problem that you have
> to exit it when flash breaks with nspluginwrapper.
I don't want to add an autostart (as shown above, that's easy), just
find where the session applications are saved so I can zap the wrong
copy of firefox from it (and script this step if necessary).

Antoine

hmmm, maybe you've added the autostart item in the Autostart. verify it and remove if necessary. look in the directory specified above.

--
dott. ing. beso ------=_Part_1071_15008424.1196152743683-- -- gentoo-amd64@gentoo.org mailing list