No or wrong icons for filesystems

Bug #404593 reported by Alan Pope ๐Ÿบ๐Ÿง๐Ÿฑ ๐Ÿฆ„
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
human-icon-theme (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: nautilus

I have a few disks in my machine, when I boot to ubuntu on one disk I can see icons for the partitions on the other disks, but the icons are 'wrong'. I can mount them and the icons on the desktop are also wrong. I would expect a disk icon (like the one in the screenshot for the drobo)..

In the screenshot note the 15G and 183G filesystems have wrong icons, but the drobo one is right.

In another screenshot (which I only noticed as I attempted to upload the first to this bug report) showing the file/open dialog, you can see _no_ icon next to the 15G and 183G filesystems.

ProblemType: Bug
Architecture: amd64
Date: Sat Jul 25 17:31:43 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: nautilus 1:2.27.4-0ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.22-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-4-generic x86_64

Revision history for this message
Alan Pope ๐Ÿบ๐Ÿง๐Ÿฑ ๐Ÿฆ„ (popey) wrote :
Revision history for this message
Alan Pope ๐Ÿบ๐Ÿง๐Ÿฑ ๐Ÿฆ„ (popey) wrote :

screenshot showing file/open dialog..

summary: - No or wrong icons for unmounted filesystem
+ No or wrong icons for filesystems
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for your bug report. As this seems to occur in Nautilus, GTK file chooser and gnome-panel, I'm re-assigning it to GLib for now. Do you remember when this stopped working? Does the same happen for other icon themes?

affects: nautilus (Ubuntu) → glib2.0 (Ubuntu)
Changed in glib2.0 (Ubuntu):
importance: Undecided → Low
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Alan,

Would you also mind please posting the output of "gvfs-mount -l -i"

Thanks

Changed in glib2.0 (Ubuntu):
status: New → Incomplete
Revision history for this message
Alan Pope ๐Ÿบ๐Ÿง๐Ÿฑ ๐Ÿฆ„ (popey) wrote :

I have the following kernels installed, and will try all of them:-

ii linux-image-2.6.28-13-generic 2.6.28-13.45 Linux kernel image for version 2.6.28 on x86/x86_64
ii linux-image-2.6.31-2-generic 2.6.31-2.17 Linux kernel image for version 2.6.31 on x86/x86_64
ii linux-image-2.6.31-3-generic 2.6.31-3.19 Linux kernel image for version 2.6.31 on x86/x86_64
ii linux-image-2.6.31-4-generic 2.6.31-4.22 Linux kernel image for version 2.6.31 on x86/x86_64

alan@wopr64:~$ gvfs-mount -l -i
Volume(0): cdrom0
  Type: GUnixVolume
  ids:
   unix-device: '/dev/scd0'
  themed icons: [drive-optical] [drive]
  can_mount=1
  can_eject=1
  should_automount=1
Volume(1): floppy0
  Type: GUnixVolume
  ids:
   unix-device: '/dev/fd0'
  themed icons: [drive-removable-media] [drive-removable] [drive]
  can_mount=1
  can_eject=0
  should_automount=1
Mount(0): drobo -> file:///media/drobo
  Type: GUnixMount
  themed icons: [drive-harddisk] [drive]
  can_unmount=1
  can_eject=0
  is_shadowed=0

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thanks - that's interesting, as there doesn't seem to be any GDrive's for the filesystems that are displayed with no icons. Would you mind also posting the output of "devkit-disks --dump"?

Thanks

Revision history for this message
Alan Pope ๐Ÿบ๐Ÿง๐Ÿฑ ๐Ÿฆ„ (popey) wrote :

Just so you know, that was taken with the filesystems _not_ mounted. I just mounted the filesystems and this is the result:-

alan@wopr64:~$ gvfs-mount -l -i
Volume(0): cdrom0
  Type: GUnixVolume
  ids:
   unix-device: '/dev/scd0'
  themed icons: [drive-optical] [drive]
  can_mount=1
  can_eject=1
  should_automount=1
Volume(1): floppy0
  Type: GUnixVolume
  ids:
   unix-device: '/dev/fd0'
  themed icons: [drive-removable-media] [drive-removable] [drive]
  can_mount=1
  can_eject=0
  should_automount=1
Mount(0): 6092a582-cc4c-4fda-9e84-ac4ba865376a -> file:///media/6092a582-cc4c-4fda-9e84-ac4ba865376a
  Type: GUnixMount
  themed icons: [drive-harddisk] [drive]
  can_unmount=1
  can_eject=0
  is_shadowed=0
Mount(1): a355b4b6-6b9a-4cba-bf8a-dd1aa8a4f272 -> file:///media/a355b4b6-6b9a-4cba-bf8a-dd1aa8a4f272
  Type: GUnixMount
  themed icons: [drive-harddisk] [drive]
  can_unmount=1
  can_eject=0
  is_shadowed=0
Mount(2): drobo -> file:///media/drobo
  Type: GUnixMount
  themed icons: [drive-harddisk] [drive]
  can_unmount=1
  can_eject=0
  is_shadowed=0

Attached is the result of devkit-disks --dump

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thanks. I wonder if this is something unique to your RAID setup? I will try and set one up tomorrow and recreate this to understand where the issue is. Re-assigning to gvfs for now.

affects: glib2.0 (Ubuntu) → gvfs (Ubuntu)
Revision history for this message
Alan Pope ๐Ÿบ๐Ÿง๐Ÿฑ ๐Ÿฆ„ (popey) wrote :

Ok, I replicated this on a completely separate system by crafting a RAID1 array on an SD card :)

Screenshot attached.

alan@hactar:~$ gvfs-mount -l -i
Drive(0): MATSHITA DVD-RAM UJ-842S
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sr0'
  themed icons: [drive-optical] [drive]
  is_media_removable=1
  has_media=0
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=1
  can_start=0
  can_stop=0
  start_stop_type=unknown
Drive(1): RAID device /dev/md0 (clean)
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/md0'
  themed icons: [gdu-raid-array] [gdu-raid] [gdu]
  is_media_removable=0
  has_media=1
  is_media_check_automatic=0
  can_poll_for_media=1
  can_eject=0
  can_start=0
  can_stop=1
  start_stop_type=multidisk
  Volume(0): 2.1 GB Filesystem
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: 'da245e56-eda0-4e84-a297-501d8eb56bbf'
     unix-device: '/dev/md0'
    themed icons: [gdu-raid-array] [gdu-raid] [gdu]
    can_mount=1
    can_eject=0
    should_automount=0
Mount(0): drobo -> file:///media/drobo
  Type: GProxyMount (GProxyVolumeMonitorGdu)
  themed icons: [drive-harddisk] [drive]
  can_unmount=1
  can_eject=0
  is_shadowed=0
alan@hactar:~$

Revision history for this message
Alan Pope ๐Ÿบ๐Ÿง๐Ÿฑ ๐Ÿฆ„ (popey) wrote :

More interesting.. If I mount the filesystem (by clicking on it) as a normal user, it mounts fine. If I have a root nautilus window open (gksudo nautilus) then the filesystem shows up as mounted (correctly) and actually has an icon. The name is duff, but the icon is there... See screenshot.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

The clue is here:

"themed icons: [gdu-raid-array] [gdu-raid] [gdu]"

devicekit-disks uses new icon names for RAID members, and that might be causing your issue. Does the problem go away if you create an icon called "gdu-raid-array", eg by doing something like "ln -s /usr/share/icons/Human/scalable/devices/gnome-dev-harddisk.svg /usr/share/icons/Human/scalable/devices/gdu-raid-member.svg"? (You might need to create the icon in some other sizes for it to show properly in the panel).

If that works, then this is probably an issue with the Human theme (it needs some new icons)

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Re-assigning this one to human-icon-theme - it needs a new icon for this (gdu-raid-array or gdu-raid)

affects: gvfs (Ubuntu) → human-icon-theme (Ubuntu)
Changed in human-icon-theme (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
tad1073 (tad1073) wrote :

I have a similar problem. No desktop icons for mounted partitions, but they show up in places and computer.

:~/Desktop$ uname -a
Linux thomthom 2.6.32-13-generic #18-Ubuntu SMP Wed Feb 10 21:32:38 UTC 2010 x86_64 GNU/Linux

:~/Desktop$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu lucid (development branch)"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.