Bug 1806179 - No mouse cursor on AMD Radeon HD graphics in a Wayland session
Summary: No mouse cursor on AMD Radeon HD graphics in a Wayland session
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 32
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-22 16:06 UTC by Bill Gianopoulos
Modified: 2021-05-25 17:18 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:18:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lshw output (30.29 KB, text/plain)
2020-02-22 16:06 UTC, Bill Gianopoulos
no flags Details

Description Bill Gianopoulos 2020-02-22 16:06:27 UTC
Created attachment 1665084 [details]
lshw output

Since fedora rawhide switched from version 32 to version 33 I get an invisible mouse cursor on a Wayland session on a Samsumg model NP305E5A-A05US.

As a workaround I have uncommented this line:

#WaylandEnable=false

in /etc/gdm/custom.conf

Comment 1 Bill Gianopoulos 2020-02-25 16:49:03 UTC
This installation is on a USB drive (and I have 2 of these so not an issue with the installation)  It works fine on my ThinkCenter that has Intel graphics but not on my Samsung HP or ASUS laptop, all of which have AMD graphics.

Comment 2 Bill Gianopoulos 2020-02-25 17:11:24 UTC
lshw identifies the graphics on the failing laptops as:

Samsung
AMD A6-3420M APU with Radeon(tm) HD Graphics
Sumo [Radeon HD 6520G]

HP
AMD A6-4400M APU with Radeon(tm) HD Graphics
Trinity 2 [Radeon HD 7520G]

ASUS
Cape Verde LE [Radeon HD 7730/8730]

Comment 3 Bill Gianopoulos 2020-03-07 15:08:34 UTC
Not sure what happcrashreporterened here I had not run fedora32 on any of these systems since the branching and I now see that this issue exists on the fedora32 branch so either caused by a late just before branching change or something that was uplifted to fedora32 post branching.

Comment 4 Olivier Fourdan 2021-02-12 08:44:39 UTC
Wayland is a set of protocols, the bug described here is not with Wayland but with the implementation - Moving to mutter where this is implemented.

Comment 5 Fedora Program Management 2021-04-29 16:52:31 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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.

Comment 6 Ben Cotton 2021-05-25 17:18:12 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.


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