Bug 299591 - no nautilus on login
Summary: no nautilus on login
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: online-desktop
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-21 01:59 UTC by cje
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-21 16:23:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description cje 2007-09-21 01:59:02 UTC
Description of problem:
nautilus sometimes doesn't start.  clicking on 'More' in the 'Files' section of
bigboard (which fails because my 'Desktop' folder has been renamed to a
different language) causes it (nautilus) to (re)start.

Version-Release number of selected component (if applicable):
online-desktop-0.2.12-2.fc8

How reproducible:
often (most logins)

Steps to Reproduce:
1.select online desktop session
2.log in
3.
  
Actual results:
blank white screen, no icons, right-click does nothing

Expected results:
regular nautilus-driven desktop with background, icons and context-menu.

Additional info:

Comment 1 Colin Walters 2007-09-21 16:23:57 UTC
This change was intentional; the idea was that the online desktop was focused
around the web, not local files.  However, I've reverted this change for now.

I hopefully fixed the Desktop translation issue in a new bigboard package just
uploaded.

Comment 2 cje 2007-09-27 17:02:53 UTC
i half-suspected it was deliberate.  i like the idea - was just a pain losing
the ability to have a desktop background.  if we could restore that
functionality and maybe still have a desktop context menu (and if it worked the
same at every login!) then i'd be all for it.  but i suppose i could just tell
nautilus not to show any desktop icons.  maybe we could just change the nautilus
desktop icon defaults in gconf?

oh, and i've tried the Desktop translation thing and that looks like it's
working just fine now.  :-)


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