Opened 17 years ago
Last modified 15 years ago
#2081 closed bug
Change in mount status not picked up — at Version 2
| Reported by: | andreasf | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | System/Kernel | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description (last modified by )
DriveSetup does not notice (any more?) that a drive has been mounted or unmounted externally, i.e. through Tracker.
A rescan does not help, nor does changing the selection. Restarting DriveSetup has it picked up correctly.
Change History (2)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
| Component: | Applications/DriveSetup → System/Kernel |
|---|---|
| Description: | modified (diff) |
| Owner: | changed from to |
DriveSetup is already doing everything correctly, and this did work at one time. This appears to be a bug in the kernel side notifications.
Note:
See TracTickets
for help on using tickets.
Volumes mounted e.g. via Tracker while DriveSetup is running are now (in hrev31644) picked up when doing a rescan. DriveSetup would benefit from keeping a BVolumeRoster around, listening to mounts/unmounts and perhaps simply doing a rescan for such events (or something more specific).