Control: reassign -1 doublecmd-gtk

[again, please CC the bug report on replies]

Am 29.05.20 um 00:05 schrieb Сергей Фёдоров:
> Installed the udisks2 package version 2.8.4-2
> Mounted all 4 disks via doublecmd. All disks were mounted normally.
> Rebooted Debian 10.4.
> Installed the udisks2 package version 2.9.0-1. Mounted all 4 disks via 
> doublecmd.
> When attempting to mount disk "H", the message" Transition to /media/u1/H 
> failed "is displayed and device" H "is being mounted" H1 "in the"/media/u1/H1 
> " directory. And so for all disks. Accordingly,
> D1 with the message "Transition to the /media/u1/D directory failed".
> E-D1 with the message "Transition to the /media/u1/E-D directory failed".
> S11 with the message "Transition to the /media/u1/S1 directory failed".
> And, for some reason, S2, not S21 with the message "Transition to the 
> directory /media/u1/S failed".
> Rebooted Debian 10.4.
> And so around the circle 3 more times.
> Installed the udisks2 package version 2.8.4-2
> Mounted all 4 disks via doublecmd. All disks were mounted normally.
> Rebooted Debian 10.4.
> Installed the udisks2 package version 2.9.0-1. Mounted all 4 disks via 
> doublecmd.
> When attempting to mount the "S1" partition, the message "Transition to the 
> /media/u1/H directory failed" is displayed, and the "S1" device is mounted 
> "S11 "in the"/media/u1/S11 " directory. All other disks are mounted normally.
> Rebooted Debian 10.4.
> Mounted all 4 disks via doublecmd. All disks were mounted normally. And it's 
> been working fine ever since.
> Question — what happened?
> Answer: I don't know!

Let's reassign this to doublecmd, this apparently is the program
triggering this error message.

Dear doublecmd maintainer, please reassign back, if this turns out to be
a genuine udisks problem.

Michael

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to