| 1 |
On 2/6/09, Sebastian Günther <samson@××××××××××××××××.de> wrote: |
| 2 |
> Some application does not capture ctrl+c, which is normaly the interupt |
| 3 |
> shortcut in bash. So it surely is passed down to bash which intrupts |
| 4 |
> startx, since it is the active job. |
| 5 |
> |
| 6 |
> I bet it won't happen with any Xsession started from any *dm. |
| 7 |
|
| 8 |
Thanks for the tip. I tried adding xdm to default runlevel and |
| 9 |
rebooted. Logging in from the kde(?) graphical login screen and |
| 10 |
pressing ctrl+c in korganizer then resulted in screen flickering via |
| 11 |
text mode back into the kde(?) login screen. So the same seems to |
| 12 |
happen there. Well, actually a bit worse: no user can login after that |
| 13 |
any more, later login attempts will flicker straight back into the |
| 14 |
login screen. |
| 15 |
|
| 16 |
> If it's possible then please test this, anyway you should pinpoint down, |
| 17 |
> where else it is possible to kill your Xsession, so that you can file a |
| 18 |
> bugreport to the right people. |
| 19 |
|
| 20 |
Will do. Deep inside I was hoping that it would be just some |
| 21 |
configuration issue I had missed. I'm currently browsing through all |
| 22 |
the "ctrl+something" bugs in bugs.kde.org and will either find |
| 23 |
something or squeeze a dump with debug info for a new one. |
| 24 |
|
| 25 |
-- |
| 26 |
Arttu V. |
Archives