When I log out of the connexion console I am not taken back to kdm. At the KDM windows, I select connexion console and I've got a bash console. I do my things and then I log out. Normally, after 10 to 40 seconds, I must be taken back to kdm and this is not the case. Best regards, YC
can you attach /var/log/Xorg.0.log or /var/log/Xorg.0.log.old and ~./.xsession-errors or ~./.xsession-errors.old ? Which console do you use ?
Created attachment 807 [details] the logs file I also added kdm.log. I use a eeepc with mageia 1 32 bits. YC
At the KDM window, I click on the button on the right (the one who looks like an On/Off button) and then on "connexion console Alt+N". The Xorg is shut off and I've got some informations and then a bash console. YC
Can you reproduce with gdm ? please also attach (after " I select connexion console and I've got a bash console." ) ~.xsession-errors and ~.xsession-errors.old
@ Yann I the problem still there in fully updated Mageia 1? @ Manuel Were the xsession-errors logs Yann had provided together with the kdm.log, not good, or do you prefer to get the logs as seperate txt files instead of zipped toghether with kdm.log? I don't fully understand the report, btw, I can't log out now to log in the way Yann does.
Keywords: (none) => NEEDINFOCC: (none) => balcaen.john, marja11Source RPM: ?? => kdebase4-workspace
and now cc'ing Manuel because of the question I asked him
CC: (none) => manuel
Oops, sorry Manuel, I now see he did attach the log files, but not the error files :[ @ Yann Please attach those files if the problem still exists
I attach the xsession-errors file. I removed the file before switching to console connection. I logged in a console connection. Waited a little bit, logged out and waited for 5 minutes. Then I restart my laptop.
Created attachment 1293 [details] the xsession error file
Attachment 1293 mime type: application/octet-stream => text/plain
Thanks, Yann I can reproduce the issue here in Mageia 1 When in the KDM login screen, I choose console login, I first get a message: "......... Graphical mode is automatically resumed 10 seconds after the last console session ends or after 40 seconds if no-one logs in in the first place." But this doesn't happen, nor when I log in and log out, nor when I don't login at all. Assigning to maintainer. @ mikala Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. And of course assign back if the culprit isn't a package you maintain :)
Assignee: bugsquad => balcaen.john
Just in case could you attach your kdmrc ? ( /usr/share/config/kdm/kdmrc )
Created attachment 1294 [details] marja's kdmrc /usr/share/config/kdm/kdmrc John asked for
CC: manuel => (none)
Good news : i can reproduce... Bad news : i don't know how to fix it. I also tested (just in case) under fedora & i can reproduce either. The various fix that i found over google does not help (for example fixing the tty list cf https://bugzilla.redhat.com/show_bug.cgi?id=542138 ). I'll try to dig a little more but i'll guess i end up to disable it for know like it's done under freebsd.
Hardware: i586 => All
(In reply to comment #13) > Good news : i can reproduce... Isn't that the first time you can reproduce a bug I could reproduce ;) > Bad news : i don't know how to fix it. > I also tested (just in case) under fedora & i can reproduce either. > The various fix that i found over google does not help (for example fixing the > tty list cf https://bugzilla.redhat.com/show_bug.cgi?id=542138 ). > I'll try to dig a little more but i'll guess i end up to disable it for know > like it's done under freebsd. Disable what, exactly?
the console login functionnality. If it does not work as expected & that i can fix it, than it's better to disable it.
Then you'll probably disable it in cauldron, too, (there, when you choose to login to a console, you have to change to tty2 after that because tty1 is occupied) I don't mind as long as, with all the changes there, it'll always be possible to login to runlevel 1 or 3 while booting as easily as currently in "1"
Of course.
Keywords: NEEDINFO => (none)
3-monthly ping
Under mageia 1, the problem is still active. Being able to connect via the console (without kde or gnome being launched) is a must have for me. I work with an eeepc and compilation of some tools via console is the only way I found to compiles these tools. Otherwise, gcc hangs while compiling some complexe code or at link time. YC
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 1'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 1 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. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX
I found the bug report 5908. For me both bugs report are duplicate. *** This bug has been marked as a duplicate of bug 5908 ***
Resolution: WONTFIX => DUPLICATE