Bug 1374125 - Bluetooth mouse not working on GDM login screen.
Summary: Bluetooth mouse not working on GDM login screen.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bluez
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: gopal krishna tiwari
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-08 03:04 UTC by Kurt Bechstein
Modified: 2020-06-16 12:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-27 16:03:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Kurt Bechstein 2016-09-08 03:04:46 UTC
Description of problem:
Running RHEL 7.2 Workstation my bluetooth mouse does not work at the GDM login screen.  Once I log into Gnome Desktop mouse will start working.  However, occasionally I need to cycle the radio switch on the laptop to get bluetooth working after logging in.  This is a Dell latitude E7440 laptop.  I was previously running Fedora 24 and this was not an issue, but decided to move to RHEL for stability.  

I'm not sure if this is necessarily a gdm issue or a kernel issue.  I will provide whatever information/logs I can to help narrow it down.

Version-Release number of selected component (if applicable):
gdm-3.14.2-12.el7.x86_64

How reproducible:
Every time the system starts up.

Steps to Reproduce:
1.Boot up the system
2.Once the GDM greeter is up try and use the bluetooth mouse and it doesn't work.
3.

Actual results:


Expected results:
The mouse works.

Additional info:

Comment 2 Ray Strode [halfline] 2020-02-19 21:03:44 UTC
gdm is definitely the wrong component.

So I think to use a bluetooth mouse, the mouse needs to be paired.  There's no way to pair from the login screen, as far as I know.  I think the pairing process is stored per-system not per-user, though, via bluez, so if the device is working from the user session I think it should work from the login screen.

Anyway, there's a giant hole in my knowledge here, so I'm moving to bluez and cc'ing hadess who knows a ton on this topic.

Comment 3 gopal krishna tiwari 2020-02-20 07:02:36 UTC
(In reply to Ray Strode [halfline] from comment #2)
> gdm is definitely the wrong component.
> 
> So I think to use a bluetooth mouse, the mouse needs to be paired.  There's
> no way to pair from the login screen, as far as I know.  I think the pairing
> process is stored per-system not per-user, though, via bluez, so if the
> device is working from the user session I think it should work from the
> login screen.
> 
> Anyway, there's a giant hole in my knowledge here, so I'm moving to bluez
> and cc'ing hadess who knows a ton on this topic.

Have we checked with latest of RHEL-7 ? 

Gopal..

Comment 4 Ray Strode [halfline] 2020-02-20 14:28:01 UTC
Kurt, sorry for the long turn around on your report. have you had an opportunity to try this on newer RHEL releases in the time since this report was originally filed?

Comment 5 Kurt Bechstein 2020-02-20 15:07:02 UTC
Ray, it's been so long that I almost forgot about this one being out there.  I assume it has been addressed, but I will give it a test to validate that for sure and then we can get this closed out.  I will report back soon.

Comment 6 Ray Strode [halfline] 2020-02-20 15:28:24 UTC
Thanks, much appreciated!

Comment 7 Kurt Bechstein 2020-02-27 15:47:28 UTC
I can no longer reproduce this issue on the latest version of RHEL 7 so I would say this one is good to close out.  Thank you.

Comment 8 gopal krishna tiwari 2020-02-27 16:03:00 UTC
(In reply to Kurt Bechstein from comment #7)
> I can no longer reproduce this issue on the latest version of RHEL 7 so I
> would say this one is good to close out.  Thank you.

Closing this out.


Note You need to log in before you can comment on or make changes to this bug.