Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Unable to lock when using KDM instead of GDM
Version-Release number of selected component (if applicable):
gnome-shell-3.8.4-22.el7.x86_64
How reproducible:
always
Steps to Reproduce:
Try: Ctrl+L or Super+L
Actual results:
nothing happens, no lockscreen
Expected results:
locked screen
Additional info:
Regression, this works in RHEL 6.x
I'd like to see opinion from Product Management, they could see this problem from bigger picture.
This is clearly integration issue and regression since RHEL 6.x and also from previous Gnome 3.x releases.
From user point of view and quality assurance, I'd like to see polished user experience and I don't see any reason for breaking previously working functionality/combination/workflow.
I'd rather question why kdm is included in the release. That came as a surprise to me at some point - it was certainly not in the desktop team plans for RHEL7 to support multiple display managers, and feature development has been done under the assumption that gdm would be the display manager.
I'm a bit surprised as well... kdm probably shouldn't be included in RHEL at all, it's basically dead upstream with several candidates to eventually replace it in the near future (sddm, lightdm)
And for the record, the whole KDE stack is fully ported to use the systemd/logind services, so running the KDE session under gdm should pose no problems at all.
(In reply to Lukáš Tinkl from comment #6)
> And for the record, the whole KDE stack is fully ported to use the
> systemd/logind services, so running the KDE session under gdm should pose no
> problems at all.
This is integration problem in Gnome session when using KDM as login manager.
(In reply to Martin Holec from comment #7)
> (In reply to Lukáš Tinkl from comment #6)
> > And for the record, the whole KDE stack is fully ported to use the
> > systemd/logind services, so running the KDE session under gdm should pose no
> > problems at all.
>
> This is integration problem in Gnome session when using KDM as login manager.
I know, I'm merely pointing out that getting rid of kdm should be no problem at all if we decide so