Bug 196555 - Mouse cursor theme reverts to default
Summary: Mouse cursor theme reverts to default
Status: RESOLVED DUPLICATE of bug 269939
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.2.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-15 02:45 UTC by Ben Knowles
Modified: 2011-07-22 10:11 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Knowles 2009-06-15 02:45:23 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Any time the mouse cursor theme is changed from its kde4 default to "kdeclassic" it reverts back to the default, usually within a few minutes.
Comment 1 Fergal Mullally 2011-01-24 07:01:59 UTC
I can repeatedly reproduce this bug:
In system settings -> Keyboard and Mouse -> Mouse -> Cursor theme

Set mouse theme to e.g KDE Classic
Log out and log back in again.
Mouse theme immediately reverts to Oxygen White
Comment 2 Markus Kohler 2011-05-21 01:44:25 UTC
I have the very same problem. However, I cannot fully reproduce it and believe it is more random. There were times when I logged out and logged in again and the  mouse theme remained and at other times (most times) it reverted. 

What I discovered though: if the cursor theme reverted, it did not fully revert!! I love to use redclass. If it reverts it reverts to some kind of handhelds theme (same red cursors just very tiny). Some kind of... because I realized that the theme actually switches depending on the Window. On some Windows it was a redclass cursor and in other windows or above the desktop it was handhelds theme.

Hope this helps. If you want me to run further tests please don't hesitate to email me.

ps. I am on kde 4.5.5
Comment 3 José Manuel Santamaría Lema 2011-07-22 10:11:12 UTC

*** This bug has been marked as a duplicate of bug 269939 ***