Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 982225 - latest update causes desktop layout to fail after rebooting
Summary: latest update causes desktop layout to fail after rebooting
Alias: None
Product: Fedora
Classification: Fedora
Component: rhino
Version: 18
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Alexander Kurtakov
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-07-08 12:20 UTC by Richard S. Hendershot
Modified: 2018-04-11 12:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-07-08 12:44:36 UTC

Attachments (Terms of Use)

Description Richard S. Hendershot 2013-07-08 12:20:48 UTC
Description of problem:  rhino (rhino-1.7R3-8.fc18.noarch) update causes layout of desktop to fail.  Downgrading to 7R3-6 corrects the problem.  

Version-Release number of selected component (if applicable):  7R3-8

How reproducible:  always

Steps to Reproduce:
1.  allow nautilus to layout desktop so that files/folders are visible
2.  upgrade to 7R3-8
3.  reboot, login

Actual results:  positions of desktop items are scattered about, somewhat randomly

Expected results:  desktop should not be affected

Additional info:  Also have nemo installed, but nautilus -n is the handler

Comment 1 Alexander Kurtakov 2013-07-08 12:24:27 UTC
Richard, there is no way I can see rhino interacting with desktop layout. There must be something else going on.

Comment 2 Richard S. Hendershot 2013-07-08 12:44:36 UTC
of the packages upgraded the other day, regressing rhino seemed to fix it.  I may not have rebooted though and now cannot get the same behavior.  Please close this with my apologies.

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