Bug 1100170 - KDE desktop forgets settings between boots and shows empty desktop
Summary: KDE desktop forgets settings between boots and shows empty desktop
Keywords:
Status: CLOSED DUPLICATE of bug 1051692
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-workspace
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-22 07:24 UTC by Peter Andreasen
Modified: 2014-05-22 09:22 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-22 09:20:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1051692 0 unspecified CLOSED KDE Desktop fails to load desktop icons if desktop effects enabled. 2021-02-22 00:41:40 UTC

Description Peter Andreasen 2014-05-22 07:24:31 UTC
Description of problem:
KDE Desktop fails to load icons

Version-Release number of selected component (if applicable):
4.12.5

How reproducible:
Not every time but very often

Steps to Reproduce:
1. Select folder view in desktop settings, and use custom background (slideshow)
2. Log out or reboot
3.

Actual results:
The desktop is empty and shows default background. Something that looks like a  slider occurs on the side of the desktop under the "peanut" icon but it does not do anythng. Selecting another desktop layout (such as standard layout) and back again restores the desktop.

Expected results:
Expected to keep desktop settings between sessions.

Additional info:
My setup uses two monitors and an Nvidia card, but not the proprietary drivers.
This problem is reported as bug 1051692 which was closed as an nvidia proprietary driver problem.

Comment 1 Kevin Kofler 2014-05-22 09:20:43 UTC

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

Comment 2 Kevin Kofler 2014-05-22 09:22:21 UTC
I reopened the original bug for you.


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