Comment # 17 on bug 968727 from
(In reply to Franck Bui from comment #16)
> (In reply to patrick shanahan from comment #9)
> > (In reply to Dr. Werner Fink from comment #6)
> > > (In reply to Franck Bui from comment #5)
> > > 
> > > This could be, yes.
> > > 
> > > @ Patrick -- more informations is required on your report.
> > > 
> > > Please can you provide some more informations about your moount points and
> > > the devices used for those.  What type of devices do you use and are those
> > > devices part of a special target?
> > 
> > runlevel 5
> > plug in external usb drive
> > mount using device notifier
> 
> Could you tell us more about the last step ?

"device notifier" is applet on task bar

> Do you know which exact compement is doing the mount ?

no

> Again tell us which DE you're using.

plasma5

> 
> > 
> > change to runlevel 3
> > mount is not there
> > 
> > /run/media/<user>/<drive-mount-point>
> > 
> > 
> > manually mount /mnt/<drive-mount-point>
> > change to runlevel 5
> > mount is not there
> 
> This case is strange because mount units are not stopped when isolating a
> target...
> 
> Perhaps the mount point has been moved to
> /run/media/<user>/<drive-mount-point> ?

that is the normal mount point when device notifier is utilized.  grepping for
the device, "mount |grep sdb2" provides no output at *any* mount point.


You are receiving this mail because: