Summary: | [gnome-overlay] gnome-base/gdm-3.5.9 tries to reuse console already in use | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Covici <covici> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | NeedPatch |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 436384 | ||
Attachments: | emerge --info |
Description
John Covici
2012-09-15 17:02:07 UTC
Created attachment 323908 [details]
emerge --info
If you are using gdm with USE=-systemd, then in /etc/conf.d/xdm, make sure to set DISPLAYMANAGER="gdm" and CHECKVT="11" (or whatever other console is guaranteed to not be used for anything). Then /etc/init.d/xdm should in theory use that console when launching gdm. Also, gdm-3.5.9 is long obsolete. Please update to 3.5.91-r2. This is still present in gdm 3.6.0-r1 Then we probably need a gentoo-specific patch for gdm to read the value of CHECKVT from /etc/conf.d/xdm at runtime. Something like the following logic: if using systemd, do the automagic systemd thing. else try parsing /etc/conf.d/xdm for the initial vt. else fall back to GDM_INITIAL_VT for the initial vt. This report does not contain any update wrt. verifications suggested by Alexandre. Please update the report with them. (In reply to comment #6) > This report does not contain any update wrt. verifications suggested by > Alexandre. Please update the report with them. Unless someone wrote and committed the patch that I described in comment #5, the problem is still present in our gdm-3.6.x. In earlier versions of gdm, they did not check /etc/conf.d/xdm, but actually checked to see if the console was in use -- I have 11 text consoles already running and I don't want gdm to try to use console 7 because its logged in or has login running. Maybe you could check /etc/inittab, or check the processes. so changing CHECKVT to 11/12 does not fix the issue ? Please note that upstream does not care about this part of the code, really, it never worked properly in the 3.* series and will probably never will as upstream now relies on systemd to handle this. No matter how many patches we tried... (In reply to comment #9) > so changing CHECKVT to 11/12 does not fix the issue ? > Please note that upstream does not care about this part of the code, really, > it never worked properly in the 3.* series and will probably never will as > upstream now relies on systemd to handle this. No matter how many patches we > tried... What is checkvt? Is it some config option and if so, where does it go? this no longer occurs in 3.8 |