Mailinglist Archive: opensuse (3566 mails)
| < Previous | Next > |
Re: [opensuse] KDE OR X HANGS
- From: Siegfried Wolkenstein <rough_rough@xxxxxx>
- Date: Mon, 30 Apr 2007 15:41:34 +0200
- Message-id: <200704301541.34536.rough_rough@xxxxxx>
Hello,
I haven't mixed SUSE kde with stock kde...
killing won't work... kill -9 <proc number> doesn't work... in fact it is
impossible to kill any of the X processes...
Yesterday I updated every rpm-package I have installed... Just now It happend
once again. This time it was kopete, which caused the trouble (at least I
think so): I was sending a message over the icqprotocol and suddenly the the
window turned pale and freezed. Then the keyboard got stuck and I did a
ctrl-alt-backspace, since all the other keys got barred.
The ctrl-alt-backspace let the X disappear (but the process was still running)
but after that it didn't restart. Then the usual: changing runlevels, kill -9
and some other useless stuff. Eventually a reset did the "trick".. grrrr!
How can kopete upset the kernel in such a way, that one can no more kill any X
processes? The keyboard got freezed and I had to do a restart (which didn't
work -> reset on the mainboard)
For now I will try to install a new kdenetwork3-InstantMessenger package (I
already have kdenetwork3-InstantMessenger-3.5.5-41.2). Probably SuSE 10.3
will provide a new one - including kopete 0.12.4....
Any suggestions? New Kernel (the one shipping with opensuse10.3)?
It's got to be a kernel problem!?? What might encourage the system to no more
react to kill signals? Tasklet/Softirq problem?
After all I have a standard openSUSE 10.2 system here on my Athlon X2, it
might be possible, that other folks get irritated by the same problem (I am
just wondering whether I did something naughty here with my OS. Actually I am
certain not to have done anything special)!
Is there a big difference between stack kopete and
kdenetwork3-instantmessenger?
PS: Thank you for the message M Harris!
On Monday 30 April 2007 05:13, M Harris wrote:
> On Sunday 29 April 2007 09:56, Siegfried Wolkenstein wrote:
> > sometimes kde or x just hangs.... I can not even kill any kde programme
> > after it happens. I am able to kill X by doing a "ctrl-alt-backspace",
> > but after that, X doesn't restart - even if I change the runlevel from 5
> > to 3 and then to 5 again. After reinitialising runlevel 5, X simply won't
> > start...
>
> This is very unusual. toggling between runlevel 3 & 5 normally fixes
> things that go crash in the X night.
>
> > If I try to restart the machine it hangs while trying to kill any
> > programme started in the X-Shells...
>
> You will need to find the process number that has everything tied up...
> killing them thoughtfully one by one (from the bottom) is one way to handle
> this... a little experience will tell you which to try first... but
> obviously anything having to do with X, kde, or anything that may touch the
> video in any obscure way (gaming, etc). If the normal kill doesn't get it
> then a hard kill will be required (use with caution):
> kill -9 <proc number> as root.
>
> Have you mixed and matched SUSE kde with stock kde?
>
>
>
>
>
> --
> Kind regards,
>
> M Harris <><
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
I haven't mixed SUSE kde with stock kde...
killing won't work... kill -9 <proc number> doesn't work... in fact it is
impossible to kill any of the X processes...
Yesterday I updated every rpm-package I have installed... Just now It happend
once again. This time it was kopete, which caused the trouble (at least I
think so): I was sending a message over the icqprotocol and suddenly the the
window turned pale and freezed. Then the keyboard got stuck and I did a
ctrl-alt-backspace, since all the other keys got barred.
The ctrl-alt-backspace let the X disappear (but the process was still running)
but after that it didn't restart. Then the usual: changing runlevels, kill -9
and some other useless stuff. Eventually a reset did the "trick".. grrrr!
How can kopete upset the kernel in such a way, that one can no more kill any X
processes? The keyboard got freezed and I had to do a restart (which didn't
work -> reset on the mainboard)
For now I will try to install a new kdenetwork3-InstantMessenger package (I
already have kdenetwork3-InstantMessenger-3.5.5-41.2). Probably SuSE 10.3
will provide a new one - including kopete 0.12.4....
Any suggestions? New Kernel (the one shipping with opensuse10.3)?
It's got to be a kernel problem!?? What might encourage the system to no more
react to kill signals? Tasklet/Softirq problem?
After all I have a standard openSUSE 10.2 system here on my Athlon X2, it
might be possible, that other folks get irritated by the same problem (I am
just wondering whether I did something naughty here with my OS. Actually I am
certain not to have done anything special)!
Is there a big difference between stack kopete and
kdenetwork3-instantmessenger?
PS: Thank you for the message M Harris!
On Monday 30 April 2007 05:13, M Harris wrote:
> On Sunday 29 April 2007 09:56, Siegfried Wolkenstein wrote:
> > sometimes kde or x just hangs.... I can not even kill any kde programme
> > after it happens. I am able to kill X by doing a "ctrl-alt-backspace",
> > but after that, X doesn't restart - even if I change the runlevel from 5
> > to 3 and then to 5 again. After reinitialising runlevel 5, X simply won't
> > start...
>
> This is very unusual. toggling between runlevel 3 & 5 normally fixes
> things that go crash in the X night.
>
> > If I try to restart the machine it hangs while trying to kill any
> > programme started in the X-Shells...
>
> You will need to find the process number that has everything tied up...
> killing them thoughtfully one by one (from the bottom) is one way to handle
> this... a little experience will tell you which to try first... but
> obviously anything having to do with X, kde, or anything that may touch the
> video in any obscure way (gaming, etc). If the normal kill doesn't get it
> then a hard kill will be required (use with caution):
> kill -9 <proc number> as root.
>
> Have you mixed and matched SUSE kde with stock kde?
>
>
>
>
>
> --
> Kind regards,
>
> M Harris <><
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |