Description of problem: Fresh Alpha3 installation with KDE, no old settings inherited, no automatic login, updates as of today noon. When I boot the system kdm does not succeed, the system falls back to a text login on tty1. When I login and do 'startx' the KDE environment comes up nicely. Reason is probably a problem with kdm (log entries as shown on tty12): ----------------------------------------------- > kdm_config: Multiple occurences of key 'AllowShutdown' in section [X-:*-Core] of /usr/share/config/kdm/kdmrc > kdm_config: Invalid boolean value '' at /usr/share/config/kdm/kdmrc:495 ***** this line is repreated 3 times with different line numbers of kdmrc **** > kdm: : IO Error in XOpenDisplay(:0) > kdm: Display :0 cannot be opened > kdm: Unable to fire up local display :0; disabling ------------------------------------------------- When I boot the system in safe mode (single user mode) the same happens - the system does not boot into RL1 but ends up in a normal text login prompt where I can login as user. Don't know if this is related: Shutdown is not working, it hangs somewhere in the early stage of shutdown until I press the power button or cut the power cable. See also https://forums.mageia.org/en/viewtopic.php?f=15&t=1784
I do not know which package could be involved, so I left this empty.
CC: (none) => molch.b
*** Bug 4266 has been marked as a duplicate of this bug. ***
CC: (none) => herbert
CC: (none) => marja11Hardware: i586 => All
You should attach X & kdm log
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
(In reply to comment #2) > *** Bug 4266 has been marked as a duplicate of this bug. *** fine with that, just note that I am using Gnome/GDM and the system seems to lock up hard, so no kdm or even Xorg logs in this case. also note that I didn't try to recreate the issue (yet)
Sorry, too late. After this bug stayed with me during all updates and there was no reaction to the bug report within 2 weeks I decided on Feb 5 to install something else.
Oops, I was too fast! When I still had that Cauldron installation with the described bug I switched to automatic login without any change. Later I deinstalled kdm and installed gdm but without change in behavior. As I wrote in the beginning, X is running fine except for those continuous jumps to tty1. I looked at X error log but there was nothing in there which could have told something related.
Created attachment 1514 [details] Xorg.0.log.old @ Herbert AFAIK all users who had the hard freeze with mga2a3, had the problem starting the display manager after reinstalling + updating, and many had a problem with booting stopping without hard freeze (magic keys worked to continue booting) in between If after installing mga2a3 with updates again you still have that hard freeze instead of our problems, then I agree your bug is different and bug 4266 should be reopened, and of course too if this bug is assigned to kdm. @ Thierry It doesn't happen all the time, that the display manager doesn't start, but it happened last time I started this Mga2a3 machine, so I'll attach the files you asked for
Created attachment 1515 [details] kdm.log
removing the NEEDINFO keyword, because all requested information has been provided
Keywords: NEEDINFO => (none)
You had a segfault at least once. You should: - enable "debug core release" medium, - install gdb glibc-devel x11-server
CC: (none) => mageiaSummary: After Alpha 3 the system does not boot into the GUI and not into RL1 (safe mode) => a3: DM service doesn't start ("Xf86CloseConsole: VT_ACTIVATE failed: Input/output error")Source RPM: (none) => x11-server
Colin: maybe some bad interaction between systemd, plymouth and x11-server? It looks like such error happened on FC & Ubuntu in the past.
(In reply to comment #10) > You had a segfault at least once. > You should: > - enable "debug core release" medium, > - install gdb glibc-devel x11-server @ Thierry did that and rebooted a few times until it happened again. I did not try to do startx from within gdb, because this problem only occurs when booting the machine which file(s) do you want?
So we won't be able to use gdb :-(
I suspect that this one was fixed in systemd 40 by this commit. http://cgit.freedesktop.org/systemd/systemd/commit/?id=9c07474c6fa296195dcdc734d77792dff95f5c35 Has the problem shown up recently?
(In reply to comment #14) > I suspect that this one was fixed in systemd 40 by this commit. > > http://cgit.freedesktop.org/systemd/systemd/commit/?id=9c07474c6fa296195dcdc734d77792dff95f5c35 > > Has the problem shown up recently? I think it showed up a lot less often, or maybe even not at all for a while, because I remember I was surprised it happened again (one of) the last time(s) I used cauldron (somewhere around last weekend). I'm not using cauldron atm, I got fed up with bug 4557 After i18n freeze I'll check my cauldrons again (only two cauldrons, now) Setting NEEDINFO keyword to remind me to give feedback
Keywords: (none) => NEEDINFO
(In reply to comment #14) > I suspect that this one was fixed in systemd 40 by this commit. > > http://cgit.freedesktop.org/systemd/systemd/commit/?id=9c07474c6fa296195dcdc734d77792dff95f5c35 > > Has the problem shown up recently? That one time I did see it, was probably on an old cauldron that hadn't been updated for a long time, just before installing Mageia 1 over it. I have booted my remaining 2 cauldrons around 10 times each, and they don't have the issue any more. Closing as fixed :)
Keywords: NEEDINFO => (none)Status: NEW => RESOLVEDResolution: (none) => FIXED
I have what seems to be the same issue with a fresh Mageia 2 install from live CD. On system boot, DM starts but kdm does not display the login menu. Only the mouse cursor is displayed. Ctrl-Alt-Fn does not display console. I have to kill xorg with Ctrl-Alt-Backspace. Note :automatic login is disabled.
Status: RESOLVED => REOPENEDCC: (none) => d.strickerResolution: FIXED => (none)
Created attachment 2413 [details] Xorg.0.log.old
Created attachment 2414 [details] kdm.log
Attachment 2413 mime type: application/octet-stream => text/plain
Attachment 2414 mime type: text/x-log => text/plain
Version: Cauldron => 2Summary: a3: DM service doesn't start ("Xf86CloseConsole: VT_ACTIVATE failed: Input/output error") => DM service doesn't start ("Xf86CloseConsole: VT_ACTIVATE failed: Input/output error")
That's a different issue. VirtualBox doesn't compile with x11-server-1.12 whereas it is supposed to.
Oops, wrong ticket
The issue seems to happen systematically when autologin is enabled. I disabled it as well as xguest user after install, but it got enabled again. Don't know exactly why, maybe after trying gnome and reverting to KDE ? Anyway, I did not reproduce the issue after disabling autologin.
Source RPM: x11-server => x11-server,autologin
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: REOPENED => RESOLVEDResolution: (none) => OLD