Bug 333871

Summary:	Mouse Cursor Theme not working in Firefox
Product:	[Applications] systemsettings	Reporter:	Akhilan <akhilkrishnans>
Component:	kcm_cursortheme	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	nate, unassigned-bugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Akhilan 2014-04-25 12:57:14 UTC

Mouse Cursor Theme not working inside Firefox. But works well outside the page. My System also has Gnome. Instead KDE Cursor, Gnome's one is loading. It works well for a while. But not now. I've deleted the .kde files in the home. But no Hope. also updated 'update-alternatives --config x-cursor-theme'. again the same. 

Reproducible: Always

Steps to Reproduce:
1. Open Firefox
2. Get the mouse pointer into the Workspace
3.
Actual Results:  
Gnome's Black Cursor theme is showing

Expected Results:  
KDE Cursor themes have to show

Comment 1 Akhilan 2014-04-25 13:19:35 UTC

Bug in Mozilla Bugzilla : https://bugzilla.mozilla.org/show_bug.cgi?id=1001393

Comment 2 Andrew Crouthamel 2018-11-11 04:26:44 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-11-21 04:29:10 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Nate Graham 2020-01-11 19:24:11 UTC

Per https://bugzilla.mozilla.org/show_bug.cgi?id=1001393, it looks like this wound up being traced to a GTK issue that I gather has since been fixed, since I can't reproduce the issue.