| Summary: | kdm login switches to a text console tty1 by itself. Can't switch manually to any text console. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Curtis Hildebrand <curtis_mageia> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | anssi.hannula, balcaen.john, dmorganec, manuel.mageia |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kdebase4-workspace-4.7.97-1.mga2.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: |
lspcidrake -v
kdm.log file |
||
|
Description
Curtis Hildebrand
2012-01-15 07:38:52 CET
Created attachment 1362 [details]
lspcidrake -v
Forgot to add that I'm getting numerous lines of this in the messages log: Jan 14 20:23:02 localhost systemd[1]: getty@tty1.service holdoff time over, scheduling restart. Jan 14 20:23:05 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id Jan 14 20:37:36 localhost systemd[1]: getty@tty1.service holdoff time over, scheduling restart. Jan 14 20:37:38 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id Jan 14 21:17:38 localhost systemd[1]: getty@tty1.service holdoff time over, scheduling restart. Jan 14 21:17:42 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id Hi thanks for reporting this bug. Anssi, dmorgan KMS issue related to the driver, or more one with the recent update ? CC:
(none) =>
anssi.hannula, dmorganec, manuel Some more info: Running 'systemctl stop getty@tty1.service' stops the screen switches to tty1. (and keeps me sane) When I shutdown the computer, the DM stops and the screen goes to a tty console with EVERYTHING I have typed on the keyboard. Then it finishes shutting down. Created attachment 1378 [details]
kdm.log file
I think this is related to KDM. I switched to logging in with GDM and I don't see the problem. I can switch to tty1-6 consoles and the DM session is started on tty7.
]# grep kdm /var/log/messages
Jan 16 01:17:31 localhost kdm[4450]: Cannot execute 'grub-set-default': not in $PATH.
Jan 17 11:32:43 localhost kdm[4612]: X server for display :0 terminated unexpectedly
Jan 17 11:32:43 localhost kdm: :0[5833]: Fatal X server IO error: Interrupted system call
Jan 17 11:36:45 localhost kdm[4612]: Cannot execute 'grub-set-default': not in $PATH.
Jan 17 11:46:12 localhost kdm[4781]: X server for display :0 terminated unexpectedly
Jan 17 11:46:12 localhost kdm: :0[5909]: Fatal X server IO error: Interrupted system call
Jan 17 12:24:35 localhost kdm[4781]: Cannot execute 'grub-set-default': not in $PATH.
Jan 17 12:25:20 localhost kdm: :0[27588]: Fatal X server IO error: Interrupted system call
Curtis Hildebrand
2012-01-17 21:42:02 CET
Summary:
dm switches to a text console tty1 by itself. Can't switch manually to any text console. =>
kdm login switches to a text console tty1 by itself. Can't switch manually to any text console. i'm not sure that kdm is at fault here because kdm just notice that X server is probably crashing : Fatal X server IO error: Interrupted system call/ Also something is strange here because X should be started on tty1 according to last change done by coling in plymouth/systemd. CC:
(none) =>
balcaen.john |