when returning from sleep, nautilus opens removable media

Bug #496956 reported by Oded Arbel
38
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Nautilus
New
Low
nautilus (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Use case as follows:
1. I have inserted an SD card to my laptop's reader.
2. Nautilus opens up a file browser to that SD card.
3. I close the window.
4. I suspend the laptop.
5. I resume the laptop

Nautilus opens up a file browser to the SD card again. I believe this is wrong - Nautilus should only open a window for a removable media only when it is first inserted.

ProblemType: Bug
Architecture: amd64
Date: Tue Dec 15 15:04:25 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.28.1-0ubuntu3
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-11-generic x86_64

Revision history for this message
Oded Arbel (oded-geek) wrote :
Changed in nautilus (Ubuntu):
importance: Undecided → Low
Revision history for this message
malev (marcosvanetta) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Could you tell me if the persist after you update you're system?
I tried your bug on my laptop and I didn't have the problem.
Regards
malev

Changed in nautilus (Ubuntu):
status: New → Incomplete
Revision history for this message
Oded Arbel (oded-geek) wrote :
Download full text (11.4 KiB)

This is 100% reproducible on my laptop running a fully updated Ubuntu 9.10. I'm using a thinkpad X61s with an internal SD card reader. The thinkpad also has a docking station with a DVD writer, and if I resume when the docking station is connected and there is a disc in the DVD drive, I also get the "What would you like to do with the disc you just inserted" dialog in addition to the SD card being opened.

I'm going to upgrade my laptop to Lucid for Alpha 3, but as it features the same GNOME version (no 2.30, right?) then I don't assume it will behave differently.

Here is my kernel syslog from waking up - I don't see anything interesting there except the last line about the cdrom. I think the SD reader is connected internally through USB, so that might be related.
---8<---
Feb 11 10:53:51 sepiroth kernel: [50198.109171] Initializing CPU#1
Feb 11 10:53:51 sepiroth kernel: [50198.109171] Calibrating delay using timer specific routine.. 2792.96 BogoMIPS (lpj=13964806)
Feb 11 10:53:51 sepiroth kernel: [50198.109171] CPU: L1 I cache: 32K, L1 D cache: 32K
Feb 11 10:53:51 sepiroth kernel: [50198.109171] CPU: L2 cache: 4096K
Feb 11 10:53:51 sepiroth kernel: [50198.109171] CPU 1/0x1 -> Node 0
Feb 11 10:53:51 sepiroth kernel: [50198.109171] CPU: Physical Processor ID: 0
Feb 11 10:53:51 sepiroth kernel: [50198.109171] CPU: Processor Core ID: 1
Feb 11 10:53:51 sepiroth kernel: [50198.270816] CPU1: Intel(R) Core(TM)2 Duo CPU L7300 @ 1.40GHz stepping 0a
Feb 11 10:53:51 sepiroth kernel: [50198.270881] CPU0 attaching NULL sched-domain.
Feb 11 10:53:51 sepiroth kernel: [50198.272529] Switched to high resolution mode on CPU 1
Feb 11 10:53:51 sepiroth kernel: [50198.310034] CPU0 attaching sched-domain:
Feb 11 10:53:51 sepiroth kernel: [50198.310038] domain 0: span 0-1 level MC
Feb 11 10:53:51 sepiroth kernel: [50198.310041] groups: 0 1
Feb 11 10:53:51 sepiroth kernel: [50198.310048] CPU1 attaching sched-domain:
Feb 11 10:53:51 sepiroth kernel: [50198.310050] domain 0: span 0-1 level MC
Feb 11 10:53:51 sepiroth kernel: [50198.310054] groups: 1 0
Feb 11 10:53:51 sepiroth kernel: [50198.312529] CPU1 is up
Feb 11 10:53:51 sepiroth kernel: [50198.312533] ACPI: Waking up from system sleep state S3
Feb 11 10:53:51 sepiroth kernel: [50201.640200] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Feb 11 10:53:51 sepiroth kernel: [50201.640235] pci 0000:00:02.1: restoring config space at offset 0x1 (was 0x900000, writing 0x900007)
Feb 11 10:53:51 sepiroth kernel: [50201.640417] uhci_hcd 0000:00:1a.0: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 11 10:53:51 sepiroth kernel: [50202.060087] uhci_hcd 0000:00:1a.1: power state changed by ACPI to D0
Feb 11 10:53:51 sepiroth kernel: [50202.060153] uhci_hcd 0000:00:1a.1: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 11 10:53:51 sepiroth kernel: [50202.060246] ehci_hcd 0000:00:1a.7: restoring config space at offset 0x1 (was 0x2900106, writing 0x2900102)
Feb 11 10:53:51 sepiroth kernel: [50202.060281] ehci_hcd 0000:00:1a.7: PME# disabled
Feb 11 10:53:51 sepiroth kernel: [50202.060377] HDA Intel 0000:00:1b.0: restoring co...

malev (marcosvanetta)
Changed in nautilus (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

I found the regarding upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=579123, so linking it here.

Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: Confirmed → Triaged
Changed in nautilus:
status: Unknown → New
Changed in nautilus:
importance: Unknown → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you still see that issue in newer versions?

Changed in nautilus (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

Bug report did not expire due to bug watch
Upstream report has seen no activity
Tested ok with 2 removable devices and Ubuntu 18.04
Last report was over 10 years ago
No reply to comment #5
As multiple users affected issue must have been fixed

Changed in nautilus (Ubuntu):
status: Incomplete → Fix Released
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.