1 |
On Sunday 20 April 2008, Philip Webb wrote: |
2 |
> 080419 Volker Armin Hemmann & Mick discussed: |
3 |
> M> a box running vanilla KDE is taking an awful long time |
4 |
> M> to exit the KDE session when I shutdown. |
5 |
> VAH> lsof & grep can tell you which files are accessed. |
6 |
> VAH> Maybe it takes a looong time writing to kdm.log |
7 |
> VAH> something that sometimes make my shutdowns extremely slow. |
8 |
> M> How do you mean I need to run lsof? |
9 |
> VAH> Ctrl+Alt+F1 to switch to a console quickly while KDE is shutting down |
10 |
> VAH> and run it from there as root. lsof shows the open files. In my case, |
11 |
> VAH> when shutting down hangs for ages it is always accessing kdm.log. |
12 |
> VAH> But your problem might me be something completly different. |
13 |
> VAH> Are you saving sessions? |
14 |
> |
15 |
> I've had the same problem for some time. |
16 |
> There was 1 version of KDE (perhaps 3.5.6/7) which didn't do it, |
17 |
> but then it started again (now 3.5.9). It saves 11 apps on 10 |
18 |
> desktops, but that shouldn't be taking so long on a fast machine: |
19 |
> after all, it compiles Kdelibs in 17 min ! |
20 |
> In my case, it isn't kdm.log , as I don't have Kdm installed |
21 |
> (I use 'startx' from a raw command-line after booting). |
22 |
> |
23 |
> One way to find out more would be to file a bug with KDE, |
24 |
> but I'ld rather not waste their time, if anyone has further advice. |
25 |
|
26 |
Back on this machine today. I checked that I am not saving any KDE sessions. |
27 |
I ran lsof on the console and saw that it was accessing kdm and some X server |
28 |
files (as expected). Not clever enough to play tunes with lsof - any |
29 |
particular strings that I should run? |
30 |
|
31 |
PS. I also remember that older KDE versions would shut down immediately, but |
32 |
the last couple of versions take their time. |
33 |
PPS. On my laptop I don't experience this delay, however, I am running xdm |
34 |
with Fluxbox and manually run startkde in the very rare occasions that I want |
35 |
to try something within KDE. So the delay could have something to do with |
36 |
kdm? |
37 |
-- |
38 |
Regards, |
39 |
Mick |