Opened 11 years ago

Closed 10 years ago

#2081 closed bug (fixed)

Change in mount status not picked up

Reported by: andreasf Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description (last modified by stippi)

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 (3)

comment:1 Changed 10 years ago by jonas.kirilla

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).

comment:2 Changed 10 years ago by stippi

Component: Applications/DriveSetupSystem/Kernel
Description: modified (diff)
Owner: changed from stippi to axeld

DriveSetup is already doing everything correctly, and this did work at one time. This appears to be a bug in the kernel side notifications.

comment:3 Changed 10 years ago by axeld

Resolution: fixed
Status: newclosed

Stippi is dreaming of a working Haiku, it seems; this feature was not implemented until hrev32891 :-)

Note: See TracTickets for help on using tickets.