| 1 |
2007/11/26, Antoine Martin <antoine@××××××××××.uk>: |
| 2 |
> |
| 3 |
> Beso wrote: |
| 4 |
> > hmmm.... maybe you didn't understood.... |
| 5 |
> > when you shutdown, restart or whatever kde its last session will |
| 6 |
> continue to |
| 7 |
> > load as it was before restart. |
| 8 |
> Well, maybe you misunderstood my question: the session does not resume |
| 9 |
> as it was but with the wrong version of firefox. |
| 10 |
|
| 11 |
|
| 12 |
this is due to a wrong shutdown... the only way of this to happen is a |
| 13 |
forced kill of kde. there's no other way for it to happen. |
| 14 |
anyway for what i know of kde sessions you just need to remove everything |
| 15 |
in: |
| 16 |
|
| 17 |
/var/tmp/kdecache-<user> |
| 18 |
/tmp/ksocket-<user> |
| 19 |
|
| 20 |
and have these directories writable (but if you login they should already be |
| 21 |
writable). just in case do a ls -l on them and see if they are at least |
| 22 |
drwxr--r-- 2 <user> users (this means that the directory is owned by the |
| 23 |
user, of group users which has full permissions, while the group members |
| 24 |
have read permission and the other users not in the users group have read |
| 25 |
permissions). this is the minimum required permissions for kde to run. if |
| 26 |
they're are lower (for the specific user) kde won't work. |
| 27 |
|
| 28 |
> the problem is that when you do a |
| 29 |
> > restart/shutdown ecc from the kde session the next time the session |
| 30 |
> which |
| 31 |
> > will load will be the last one to load, but when you do force a restart |
| 32 |
> then |
| 33 |
> > the last session would be the one before the forced restart. |
| 34 |
> That's not the problem here. |
| 35 |
|
| 36 |
|
| 37 |
as i've said before, it's quite impossible for kde to restart a wrong |
| 38 |
session on restart if it wasn't killed. |
| 39 |
|
| 40 |
> now, if this is not your case for firefox autostart there are 2 ways: |
| 41 |
> > 1. the firefoxstarter app |
| 42 |
> > 2. a link in your /home/foo/.kde/Autostart/ directory. |
| 43 |
> > for what i know there aren't other methods of autostarting something |
| 44 |
> > something on kde. |
| 45 |
> > if you want your firefox to load after login then place a symlink to |
| 46 |
> firefox |
| 47 |
> > in the autostart directory. |
| 48 |
> > you could also use the firefoxstarter, but it has the problem that you |
| 49 |
> have |
| 50 |
> > to exit it when flash breaks with nspluginwrapper. |
| 51 |
> I don't want to add an autostart (as shown above, that's easy), just |
| 52 |
> find where the session applications are saved so I can zap the wrong |
| 53 |
> copy of firefox from it (and script this step if necessary). |
| 54 |
> |
| 55 |
> Antoine |
| 56 |
|
| 57 |
|
| 58 |
hmmm, maybe you've added the autostart item in the Autostart. verify it and |
| 59 |
remove if necessary. look in the directory specified above. |
| 60 |
|
| 61 |
-- |
| 62 |
dott. ing. beso |
Archives