1 |
On Sunday 03 June 2007 19:36, Kevin O'Gorman wrote: |
2 |
> On 6/3/07, Dale <dalek@××××××××××.net> wrote: |
3 |
> > deface wrote: |
4 |
> > > ' /etc/init.d/xdm restart ' |
5 |
> > > This would restart your login manager, assuming your running one. |
6 |
> > > (gdm/kdm/xdm/slim) |
7 |
> > > |
8 |
> > > I would recommend on finding out the root of your X locking up, rather |
9 |
> > > than actually trying to band-aid it. |
10 |
> > > |
11 |
> > > deface |
12 |
> > > |
13 |
> > > On Jun 3, 2007, at 8:22 PM, Dale wrote: |
14 |
> > >> Or, you can do a /etc/init.d/xdm restart . Either should work. |
15 |
> > >> |
16 |
> > >> On another note, you may want to find out why it is locking up. This |
17 |
> > >> should not be happening. Are you sure it is locked up or could it be |
18 |
> > >> that what you are doing is just using all the CPU processes and it is |
19 |
> > >> to busy to respond? |
20 |
> > >> |
21 |
> > >> Maybe some serious guru will come in with a plan. |
22 |
> > >> |
23 |
> > >> Dale |
24 |
> > >> |
25 |
> > >> :-) :-) :-) |
26 |
> > >> |
27 |
> > >> -- |
28 |
> > >> www.myspace.com/-remove-me-dalek1967 |
29 |
> > >> |
30 |
> > >> Copy n paste then remove the -remove-me- part. |
31 |
> > |
32 |
> > If he does that, it will restart X. I have also seen where a few others |
33 |
> > made the suggestion too. This has always worked for me at least. |
34 |
> > |
35 |
> > Dale |
36 |
> > |
37 |
> > :-) :-) :-) |
38 |
> > |
39 |
> > -- |
40 |
> > www.myspace.com/-remove-me-dalek1967 |
41 |
> > |
42 |
> > Copy n paste then remove the -remove-me- part. |
43 |
> > |
44 |
> > -- |
45 |
> |
46 |
> Thanks for all the ideas. I'll keep them handy for the next time (it |
47 |
> usually happens |
48 |
> about once or twice a month). |
49 |
> |
50 |
> In the meanwhile, a couple of notes: |
51 |
> 1) Yes, it's REALLY locked up. But there's always enough CPU left |
52 |
> for a non-X login from another machine. It has to be another machine |
53 |
> because I can't even switch to a console terminal. |
54 |
> 2) I have no clue how to find out what's causing the lockup. I'd |
55 |
> love to, because I usually lose a bunch of work in the crash. |
56 |
> 3) I don't see anything labeled "SysReq" on my keyboard, but it's |
57 |
> associated with the PrintScreen key on my wife's box. Can I hope |
58 |
> alt-printscreen-K will work? (I personally wonder about it since |
59 |
> _nothing_ else on the keyboard works, but maybe the kernel can see |
60 |
> it). |
61 |
> |
62 |
> Again, thanks. I'll say more when it happens again. |
63 |
> |
64 |
> -- |
65 |
> Kevin O'Gorman, PhD |
66 |
1) alt-printscreen-k should work |
67 |
2) try 'killall X' via ssh and if that doesnt restart and bring the display |
68 |
back also do "killall kdm" |
69 |
3) can you share a copy of you xorg.conf? |
70 |
-- |
71 |
Guillermo A. Amaral, CSE |
72 |
# Free & Open Source Advocate |
73 |
& nick: guillermoamaral |
74 |
@ blog: http://blog.guillermoamaral.com/ |
75 |
@ site: http://www.guillermoamaral.com/ |
76 |
$ irc: guillermoamaral@freenode |
77 |
% gpg: http://downloads.guillermoamaral.com/public.asc |