Bug 1335511
| Summary: | gdm with X: fully reproducible failure: VT_ACTIVATE: Operation not permitted | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alan Jenkins <alan.christopher.jenkins> | 
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | 
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | 
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | ernstp, hdegoede, rstrode, xgl-maint | 
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-20 20:27:40 UTC | Type: | Bug | 
| Regression: | --- | Mount Type: | --- | 
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| 
 
        
          Description
        
        
          Alan Jenkins
        
        
        
        
        
          2016-05-12 11:44:58 UTC
        
       
      
      
      
    Seems like a gdm bug to me, changing component. do you mind filing this on bugzilla.gnome.org ? That was a bit unfair to ask :-P. I said I thought it was a bug in X and Hans didn't mention why not. I see Hans should know about this stuff. I was worrying at this earlier & ran some tests. Can you confirm my surmise please? Then I will have an informed description I can file with GNOME. 1. gdm is running /usr/libexec/Xorg as non-root. 2. Xorg as non-root can _not_ switch VTs. And it's not that it ever uses a logind API to request VT switches. (ala `loginctl activate`) 3. Therefore gdm has taken responsibility for switching to the desired VT. It looks like gdm is failing to do so in this case. Test: $ tty /dev/tty3 $ /usr/libexec/Xorg :1 vt3 [success] $ /usr/libexec/Xorg :1 [failure, misleading error message about tty0 not existing] $ /usr/libexec/Xorg.wrap :1 [success, yay :) Xorg switches to a free VT as is traditional. By brute-force: Xorg is shown running as root. Boo :(] i'm not trying to be unfair, just trying to keep all gdm bugs in one place! if it's an inconvenience for you to file it upstream, I can do it. GDM should be jumping to and forcing VT1 when it first starts. The code is there, there just must be a bug... I have this bug on Ubuntu Gnome FYI. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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 Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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 Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.  |