USB Memory Sticks don't show up in Ubuntu 9.10.

Bug #452318 reported by John Wheelwright
12
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

When I plug in any USB memory stick into the USb port the PC dosn't seem to open them and no Icon appears either,no error messages.
As far as I know i have installed the relevant software packages.
This is the new Ubuntu 9.10 beta version which I think is amazing and i hope everything will be sorted out for the final release in two weeks time.
Just to memtion that I also cannot view DVD movies (Disks)and i have the LIbdvdXXXX4 installed but other media Dvd;s seem to be okay.

Thanks.

Regards.

ProblemType: Bug
Architecture: i386
CheckboxSubmission: 81697cc94b47c47d895b7862c454934f
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
Date: Thu Oct 15 17:07:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.28.0-0ubuntu6
ProcEnviron:
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
John Wheelwright (jbwheelwright) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for the report, could you attach the output of : dmesg &> dmesg.txt and devkit-disks --dump &> devkit.txt to the report? thanks. and yes you need to plug the memory first.

Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
John Wheelwright (jbwheelwright) wrote :
Download full text (49.3 KiB)

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.31-14-generic (buildd@vernadsky) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #47-Ubuntu SMP Thu Oct 15 02:08:08 UTC 2009 (Ubuntu 2.6.31-14.47-generic)
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009bc00 (usable)
[ 0.000000] BIOS-e820: 000000000009bc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000b5ea8000 (usable)
[ 0.000000] BIOS-e820: 00000000b5ea8000 - 00000000b5ed0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000b5ed0000 - 00000000b5ee1000 (reserved)
[ 0.000000] BIOS-e820: 00000000b5ee1000 - 00000000b5ee2000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000b5ee2000 - 00000000b5f0a000 (reserved)
[ 0.000000] BIOS-e820: 00000000b5f0a000 - 00000000b5f0b000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000b5f0b000 - 00000000b5f0c000 (reserved)
[ 0.000000] BIOS-e820: 00000000b5f0c000 - 00000000b5f17000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000b5f17000 - 00000000b5f1d000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000b5f1d000 - 00000000b5f39000 (reserved)
[ 0.000000] BIOS-e820: 00000000b5f39000 - 00000000b6000000 (usable)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffa00000 - 00000000ffc00000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
[ 0.000000] DMI 2.4 present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0xb6000 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-D3FFF write-protect
[ 0.000000] D4000-E7FFF write-through
[ 0.000000] E8000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 base 080000000 mask FC0000000 write-back
[ 0.000000] 2 base 0B8000000 mask FF8000000 uncachable
[ 0.000000] 3 base 0B6000000 mask FFE000000 uncachable
[ 0.000000] 4 base 100000000 mask FC0000000 write-back
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820 update range: 00000000b6000000 - 0000000100000000 (usable) ==> (reserved)
[ 0.000000] Scanning 0 areas for low memory corruption...

Revision history for this message
John Wheelwright (jbwheelwright) wrote : Re: [Bug 452318] Re: USB Memory Sticks don't show up in Ubuntu 9.10.

Hi Pedro.

I have added some things but I'm not 100% sure if that will help as I'm new to Linux and still learning about it.

Regards.

--- On Thu, 15/10/09, Pedro Villavicencio <email address hidden> wrote:

> From: Pedro Villavicencio <<email address hidden>
> Subject: [Bug 452318] Re: USB Memory Sticks don't show up in Ubuntu 9.10.
> To: <email address hidden>
> Date: Thursday, 15 October, 2009, 8:18 PM
> thanks for the report, could you
> attach the output of : dmesg &>
> dmesg.txt and devkit-disks --dump &> devkit.txt to
> the report? thanks.
> and yes you need to plug the memory first.
>
> ** Changed in: nautilus (Ubuntu)
>    Importance: Undecided => Low
>
> ** Changed in: nautilus (Ubuntu)
>        Status: New =>
> Incomplete
>
> ** Changed in: nautilus (Ubuntu)
>      Assignee: (unassigned) =>
> Ubuntu Desktop Bugs (desktop-bugs)
>
> --
> USB Memory Sticks don't show up in Ubuntu 9.10.
> https://bugs.launchpad.net/bugs/452318
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>
> Status in “nautilus” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: nautilus
>
> When I plug in any USB memory stick into the USb port
> the PC dosn't seem to open them and no Icon appears
> either,no error messages.
> As far as I know i have installed the relevant software
> packages.
> This is the new Ubuntu 9.10 beta version which I think is
> amazing and i hope everything will be sorted out for the
> final release in two weeks time.
> Just to memtion that I also cannot view DVD movies
> (Disks)and i have the LIbdvdXXXX4 installed but other media
> Dvd;s seem to be okay.
>
> Thanks.
>
> Regards.
>
> ProblemType: Bug
> Architecture: i386
> CheckboxSubmission: 81697cc94b47c47d895b7862c454934f
> CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
> Date: Thu Oct 15 17:07:01 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/nautilus
> Package: nautilus 1:2.28.0-0ubuntu6
> ProcEnviron:
> LANG=en_IE.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
> SourcePackage: nautilus
> Uname: Linux 2.6.31-14-generic i686
>

Revision history for this message
John Wheelwright (jbwheelwright) wrote :
Download full text (5.3 KiB)

more info.

administrator@administrator-laptop:~$ dmesg | grep -i usb
[ 0.246728] usbcore: registered new interface driver usbfs
[ 0.246728] usbcore: registered new interface driver hub
[ 0.246728] usbcore: registered new device driver usb
[ 0.933898] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.933974] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
[ 0.952017] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 0.952097] usb usb1: configuration #1 chosen from 1 choice
[ 0.952126] hub 1-0:1.0: USB hub found
[ 0.952246] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[ 0.968018] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 0.968077] usb usb2: configuration #1 chosen from 1 choice
[ 0.968103] hub 2-0:1.0: USB hub found
[ 0.968172] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.968188] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.968253] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[ 0.968367] usb usb3: configuration #1 chosen from 1 choice
[ 0.968393] hub 3-0:1.0: USB hub found
[ 0.968495] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[ 0.968617] usb usb4: configuration #1 chosen from 1 choice
[ 0.968643] hub 4-0:1.0: USB hub found
[ 0.968737] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
[ 0.968840] usb usb5: configuration #1 chosen from 1 choice
[ 0.968866] hub 5-0:1.0: USB hub found
[ 0.968962] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
[ 0.969065] usb usb6: configuration #1 chosen from 1 choice
[ 0.969091] hub 6-0:1.0: USB hub found
[ 0.969188] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
[ 0.969291] usb usb7: configuration #1 chosen from 1 choice
[ 0.969317] hub 7-0:1.0: USB hub found
[ 0.969417] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
[ 0.969529] usb usb8: configuration #1 chosen from 1 choice
[ 0.969557] hub 8-0:1.0: USB hub found
[ 1.304049] usb 1-2: new high speed USB device using ehci_hcd and address 2
[ 1.439159] usb 1-2: configuration #1 chosen from 1 choice
[ 1.883545] usb 7-1: new low speed USB device using uhci_hcd and address 2
[ 2.053337] usb 7-1: configuration #1 chosen from 1 choice
[ 2.100712] usbcore: registered new interface driver hiddev
[ 2.113475] input: USB Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/input/input5
[ 2.113558] generic-usb 0003:04B3:310C.0001: input,hidraw0: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.1-1/input0
[ 2.113571] usbcore: registered new interface driver usbhid
[ 2.113573] usbhid: v2.6:USB HID core driver
[ 8.993715] input: UVC Camera (05ca:18b3) as /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/input/input8
[ 8.993760] usbcore: registered new interface driver uvcvideo
[ 8.993763] USB Video Class driver (v0.1.0)
[ 73.292105] usb 2-1: new high speed USB device using ehci_hcd and address 3
[ 73.434465] usb 2-1: configuration #1 chosen from 1 choice
[ 73.500992] Initializing USB Mas...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

did you add the devicekit-disks binary instead of the log?

Revision history for this message
John Wheelwright (jbwheelwright) wrote :
Download full text (5.5 KiB)

I hope this helps,I'm new to Linux and I can't find a file called devicekit-disks.log???

/.
/var
/var/lib
/var/lib/DeviceKit-disks
/usr
/usr/share
/usr/share/doc
/usr/share/doc/devicekit-disks
/usr/share/doc/devicekit-disks/README
/usr/share/doc/devicekit-disks/AUTHORS
/usr/share/doc/devicekit-disks/copyright
/usr/share/doc/devicekit-disks/NEWS.gz
/usr/share/doc/devicekit-disks/changelog.Debian.gz
/usr/share/dbus-1
/usr/share/dbus-1/interfaces
/usr/share/dbus-1/interfaces/org.freedesktop.DeviceKit.Disks.xml
/usr/share/dbus-1/interfaces/org.freedesktop.DeviceKit.Disks.Device.xml
/usr/share/dbus-1/system-services
/usr/share/dbus-1/system-services/org.freedesktop.DeviceKit.Disks.service
/usr/share/polkit-1
/usr/share/polkit-1/actions
/usr/share/polkit-1/actions/org.freedesktop.devicekit.disks.policy
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/devkit-disks.1.gz
/usr/share/man/man7
/usr/share/man/man7/DeviceKit-disks.7.gz
/usr/share/man/man8
/usr/share/man/man8/devkit-disks-daemon.8.gz
/usr/share/pkgconfig
/usr/share/pkgconfig/DeviceKit-disks.pc
/usr/share/apport
/usr/share/apport/package-hooks
/usr/share/apport/package-hooks/devicekit-disks.py
/usr/bin
/usr/bin/devkit-disks
/usr/lib
/usr/lib/devicekit-disks
/usr/lib/devicekit-disks/devkit-disks-daemon
/usr/lib/devicekit-disks/devkit-disks-helper-mkfs
/usr/lib/devicekit-disks/devkit-disks-helper-delete-partition
/usr/lib/devicekit-disks/devkit-disks-helper-create-partition
/usr/lib/devicekit-disks/devkit-disks-helper-modify-partition
/usr/lib/devicekit-disks/devkit-disks-helper-create-partition-table
/usr/lib/devicekit-disks/devkit-disks-helper-change-filesystem-label
/usr/lib/devicekit-disks/devkit-disks-helper-linux-md-remove-component
/usr/lib/devicekit-disks/devkit-disks-helper-fstab-mounter
/usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect
/usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-selftest
/usr/lib/devicekit-disks/devkit-disks-helper-drive-detach
/usr/lib/devicekit-disks/devkit-disks-helper-drive-poll
/usr/lib/devicekit-disks/devkit-disks-helper-linux-md-check
/usr/lib/devicekit-disks/devkit-disks-helper-change-luks-password
/usr/lib/polkit-1
/usr/lib/polkit-1/extensions
/usr/lib/polkit-1/extensions/libdevkit-disks-action-lookup.so
/etc
/etc/dbus-1
/etc/dbus-1/system.d
/etc/dbus-1/system.d/org.freedesktop.DeviceKit.Disks.conf
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/95-devkit-disks.rules
/lib/udev/devkit-disks-part-id
/lib/udev/devkit-disks-dm-export
/lib/udev/devkit-disks-probe-ata-smart
/sbin
/sbin/umount.devkit

701786dffc2077cbe2ff7aff9709f27f usr/share/doc/devicekit-disks/README
42e6e23c5e17b009dba1619b5c3c7634 usr/share/doc/devicekit-disks/AUTHORS
9069f5e7f326e8a3b1accf4422f7fcd4 usr/share/doc/devicekit-disks/copyright
7c509f89d3242a0cc0821f47e82a0368 usr/share/doc/devicekit-disks/NEWS.gz
bb0dfee484d6c272f174d9c53b68ef96 usr/share/doc/devicekit-disks/changelog.Debian.gz
567c818bc48d0e3aa22454da0659192f usr/share/dbus-1/interfaces/org.freedesktop.DeviceKit.Disks.xml
4599adcf634eb47d134baeb46859de6a usr/share/dbus-1/interfaces/org.freedesktop.DeviceKit.Disks.Device.xml
6211fd8e5aaa6d18e7c4040d2c3dd4e3 usr/share/dbus-1/system-servi...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

when running "devkit-disks --dump &> devkit.txt" a file is written where you run the command?

Revision history for this message
John Wheelwright (jbwheelwright) wrote :
Download full text (46.9 KiB)

   detection by polling: 0
    detection inhibitable: 0
    detection inhibited: 0
  is read only: 0
  is mounted: 0
  mount paths:
  mounted by uid: 0
  presentation hide: 0
  presentation nopolicy: 0
  presentation name:
  presentation icon:
  size: 20974431744
  block size: 512
  job underway: no
  usage: filesystem
  type: ntfs
  version:
  uuid: A0584A87584A5C62
  label: New Volume
  partition:
    part of: /org/freedesktop/DeviceKit/Disks/devices/sda
    scheme: mbr
    number: 10
    type: 0x07
    flags:
    offset: 272626937856
    size: 20974431744
    label:
    uuid:

========================================================================
Showing information for /org/freedesktop/DeviceKit/Disks/devices/sda11
  native-path: /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda11
  device: 8:11
  device-file: /dev/sda11
    by-id: /dev/disk/by-id/ata-TOSHIBA_MK3252GSX_58T2P0YWT-part11
    by-id: /dev/disk/by-id/scsi-SATA_TOSHIBA_MK3252G_58T2P0YWT-part11
    by-id: /dev/disk/by-uuid/3763005d-c5f5-47a3-a879-b7cde07dd2b7
    by-path: /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part11
  detected at: Fri 16 Oct 2009 11:41:47 IST
  system internal: 1
  removable: 0
  has media: 1 (detected at Fri 16 Oct 2009 11:41:47 IST)
    detects change: 0
    detection by polling: 0
    detection inhibitable: 0
    detection inhibited: 0
  is read only: 0
  is mounted: 1
  mount paths: /
  mounted by uid: 0
  presentation hide: 0
  presentation nopolicy: 0
  presentation name:
  presentation icon:
  size: 26468918784
  block size: 512
  job underway: no
  usage: filesystem
  type: ext4
  version: 1.0
  uuid: 3763005d-c5f5-47a3-a879-b7cde07dd2b7
  label:
  partition:
    part of: /org/freedesktop/DeviceKit/Disks/devices/sda
    scheme: mbr
    number: 11
    type: 0x83
    flags:
    offset: 293601401856
    size: 26468918784
    label:
    uuid:

========================================================================
Showing information for /org/freedesktop/DeviceKit/Disks/devices/sda2
  native-path: /sys/devices/pci...

Revision history for this message
John Wheelwright (jbwheelwright) wrote :

What I just noticed was, if I leave the Memory stick plugged in and restart my laptop and log back in the USB will show up as in screenshot,But if I unplug it and plug it back in whilst logged on it dosn't work.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you have any formated partition on the key?

Revision history for this message
John Wheelwright (jbwheelwright) wrote :

I have 2 keys with NTFS 8GB and one with 8GB FAT32,strange thing was that i run some updates a few minutes ago then i just tried the keys and they all came up??????,then i rebooted and tried them again and it didn't work so that is really strange???????

I was using Ubuntu jaunty 9.04 before and everything worked so the keys are fine in that respect.

Thanks.

Revision history for this message
John Wheelwright (jbwheelwright) wrote :

I have a Hard drive that has 8 partitions
7 of them are NTFS which mount fine so i don't understand why the NTFS keys don't mount.
1 of them is formated with ext4 which is used for the Ubuntu installation.

Revision history for this message
John Wheelwright (jbwheelwright) wrote :

I just did the following and it seemed to work for me.

"I removed /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi according to this bug report: https://bugs.launchpad.net/ubuntu/+s...al/+bug/450160

    *

          After restarting HAL I had, however, still the same problem.

    * I then proceeded with this bug report: https://bugs.launchpad.net/ubuntu/+s...er/+bug/429257

          I simply wanted to see what the udevadm monitor command said when inserting the devices, and strangely enough the device was auto mounted as it should. Since invoking that command it seems my problem went away. After a reboot, everything still works.

So, the solution lies either in the update or the other two points above, maybe in conjunction. Can it be that udevadm created some needed files when invoked?""

Revision history for this message
Tadeu Bastos (tmcb) wrote :

Here in my computer the same symptoms of the description are happening. The ''uname -a" output is

Linux hostname 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

Killing all udev process instances with a "sudo pkill udev" worked for me, since a new process is created after that. Maybe it's something on the startup, I'll try to go further on that.

Revision history for this message
Elmar Roberg (roberg) wrote :

I am also new to Linux/ Ubuntu.
First time it seemed to be related to not knowing that i need to unmount, and when the CD would not eject on pressing the physical eject button, I used a pin to force it to open the tray.

However, this time, I used the eject in "places" in Nautilus after creating CD's.

Now I cannot see the USB stick nor the CD (but I can play the contents). There is also no icon for either on the desktop.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue in lucid?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

Revision history for this message
Sebastien Bacher (seb128) wrote :

there has been no such issue reported in years, assuming it doesn't exist in the current version of the code and closing

Changed in nautilus (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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