bsdisks issueshttps://foss.heptapod.net/bsdutils/bsdisks/-/issues2024-02-16T06:28:26Zhttps://foss.heptapod.net/bsdutils/bsdisks/-/issues/21Failed to mount - Not authorized2024-02-16T06:28:26ZDamjan JovanovicFailed to mount - Not authorizedOn FreeBSD 14.0, with both bsdisks 0.34 and 0.35, when in any file manager I click a plugged in USB drive to mount it, I get an error dialog with:
```
Error
Failed to mount "16 GB Volume".
Not authorized.
+-----+
|Close|
+-----+
```
An...On FreeBSD 14.0, with both bsdisks 0.34 and 0.35, when in any file manager I click a plugged in USB drive to mount it, I get an error dialog with:
```
Error
Failed to mount "16 GB Volume".
Not authorized.
+-----+
|Close|
+-----+
```
Any ideas?https://foss.heptapod.net/bsdutils/bsdisks/-/issues/20unknown error with camcontrol2024-01-15T13:18:24ZDmitry Lukhtionovunknown error with camcontrolI am launching bsdisks and see in log:
```
Dec 19 15:19:53 m18 bsdisks[1510]: Created drive "nda0"
Dec 19 15:19:53 m18 bsdisks[1510]: Created block "nda0"
Dec 19 15:19:53 m18 bsdisks[1510]: Created drive "ada0"
Dec 19 15:19:53 m18 bsd...I am launching bsdisks and see in log:
```
Dec 19 15:19:53 m18 bsdisks[1510]: Created drive "nda0"
Dec 19 15:19:53 m18 bsdisks[1510]: Created block "nda0"
Dec 19 15:19:53 m18 bsdisks[1510]: Created drive "ada0"
Dec 19 15:19:53 m18 bsdisks[1510]: Created block "ada0"
Dec 19 15:19:53 m18 bsdisks[1510]: Created block "nda0p2"
Dec 19 15:19:53 m18 bsdisks[1510]: Created block "nda0p3"
Dec 19 15:19:53 m18 bsdisks[1510]: Created block "nda0p1"
Dec 19 15:19:53 m18 bsdisks[1510]: camcontrol failed
Dec 19 15:19:53 m18 bsdisks[1510]: "Registering /org/freedesktop/UDisks2/drives/nda0"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished GEOM probe on "nda0"
Dec 19 15:19:53 m18 bsdisks[1510]: "Registering /org/freedesktop/UDisks2/drives/ada0"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished GEOM probe on "ada0"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished FS probe on "nda0"
Dec 19 15:19:53 m18 bsdisks[1510]: "Registering /org/freedesktop/UDisks2/block_devices/nda0"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished GEOM probe on "nda0p2"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished FS probe on "nda0p2"
Dec 19 15:19:53 m18 bsdisks[1510]: "Registering /org/freedesktop/UDisks2/block_devices/nda0p2"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished GEOM probe on "nda0p3"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished FS probe on "nda0p3"
Dec 19 15:19:53 m18 bsdisks[1510]: "Registering /org/freedesktop/UDisks2/block_devices/nda0p3"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished GEOM probe on "nda0p1"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished FS probe on "nda0p1"
Dec 19 15:19:53 m18 bsdisks[1510]: "Registering /org/freedesktop/UDisks2/block_devices/nda0p1"
Dec 19 15:19:53 m18 bsdisks[1510]: Finished FS probe on "ada0"
Dec 19 15:19:53 m18 bsdisks[1510]: "Registering /org/freedesktop/UDisks2/block_devices/ada0"
```
Can you add more verbose information to `camcontrol failed` message ?https://foss.heptapod.net/bsdutils/bsdisks/-/issues/18The CD-drive seems to be only checked once.2023-01-27T19:19:12ZAlexander VereekenThe CD-drive seems to be only checked once.Hello,
i want to report that the CD-drive seems to be only checked once after booting.
So
- if you drive was empty on boot and you put a disc in then it will not show as a mount option.
- If a disc got detected on boot then mount op...Hello,
i want to report that the CD-drive seems to be only checked once after booting.
So
- if you drive was empty on boot and you put a disc in then it will not show as a mount option.
- If a disc got detected on boot then mount option will stay forever (Disc name stays the same etc..) until you reboot.
Thank you in advance!
Log when opening an empty drive and put in an DVD:
```
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 04 01" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 04 01" CDB="00 00 00 00 00 00 "
!system=DEVFS subsystem=CDEV type=MEDIACHANGE cdev=cd0
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 06 28 00" CDB="00 00 00 00 00 00 "
!system=GEOM subsystem=DEV type=MEDIACHANGE cdev=cd0
!system=DEVFS subsystem=CDEV type=CREATE cdev=iso9660/NARCOS_S3_D1
!system=GEOM subsystem=DEV type=CREATE cdev=iso9660/NARCOS_S3_D1
```
Log of replacing an DVD in the CD-drive:
```
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 04 01" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=DEVFS subsystem=CDEV type=DESTROY cdev=iso9660/NARCOS_S3_D1
!system=GEOM subsystem=DEV type=DESTROY cdev=iso9660/NARCOS_S3_D1
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 3a 02" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 04 01" CDB="00 00 00 00 00 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="71 02 04 01" CDB="00 00 00 00 00 00 "
!system=DEVFS subsystem=CDEV type=MEDIACHANGE cdev=cd0
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 06 28 00" CDB="00 00 00 00 00 00 "
!system=GEOM subsystem=DEV type=MEDIACHANGE cdev=cd0
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=GEOM subsystem=DEV type=SIZECHANGE cdev=cd0
!system=GEOM subsystem=DEV type=SIZECHANGE cdev=cd0
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=CAM subsystem=periph type=error device=cd0 serial="KMSK42F2536" cam_status="0xcc" scsi_status=2 scsi_sense="70 05 6f 03" CDB="28 00 00 3a 44 fd 00 00 04 00 "
!system=DEVFS subsystem=CDEV type=CREATE cdev=iso9660/NARCOS_S3_D2
!system=GEOM subsystem=DEV type=CREATE cdev=iso9660/NARCOS_S3_D2
!system=GEOM subsystem=DEV type=SIZECHANGE cdev=cd0
!system=GEOM subsystem=DEV type=SIZECHANGE cdev=cd0
!system=GEOM subsystem=DEV type=SIZECHANGE cdev=iso9660/NARCOS_S3_D2
!system=GEOM subsystem=DEV type=SIZECHANGE cdev=iso9660/NARCOS_S3_D2
!system=GEOM subsystem=DEV type=SIZECHANGE cdev=iso9660/NARCOS_S3_D2
!system=GEOM subsystem=DEV type=SIZECHANGE cdev=iso9660/NARCOS_S3_D2
```https://foss.heptapod.net/bsdutils/bsdisks/-/issues/16Crash after mobile data dongle disconnects2021-10-03T07:37:26ZDamjan JovanovicCrash after mobile data dongle disconnectsbsdisks 0.26 crashed a few days ago, apparently when my mobile data dongle disconnected (presumably with its ISO9660 filesystem containing the Windows driver, not mounted AFAIK):
```
Oct 1 18:14:28 pc kernel: ugen0.5: <HUAWEI HUAWEI> at...bsdisks 0.26 crashed a few days ago, apparently when my mobile data dongle disconnected (presumably with its ISO9660 filesystem containing the Windows driver, not mounted AFAIK):
```
Oct 1 18:14:28 pc kernel: ugen0.5: <HUAWEI HUAWEI> at usbus0
Oct 1 18:14:28 pc kernel: umass2 on uhub2
Oct 1 18:14:28 pc kernel: umass2: <Mass Storage> on usbus0
Oct 1 18:14:28 pc kernel: umass2: SCSI over Bulk-Only; quirks = 0x0000
Oct 1 18:14:28 pc kernel: umass2:8:2: Attached to scbus8
Oct 1 18:14:28 pc kernel: cd1 at umass-sim2 bus 2 scbus8 target 0 lun 0
Oct 1 18:14:28 pc kernel: cd1: <Linux File-CD Gadget 0310> Removable CD-ROM SCSI-2 device
Oct 1 18:14:28 pc kernel: cd1: 40.000MB/s transfers
Oct 1 18:14:28 pc kernel: cd1: 5MB (11716 512 byte sectors)
Oct 1 18:14:28 pc kernel: cd1: quirks=0x10<10_BYTE_ONLY>
Oct 1 18:14:28 pc kernel: ugen0.5: <HUAWEI HUAWEI> at usbus0 (disconnected)
Oct 1 18:14:28 pc kernel: umass2: at uhub2, port 12, addr 24 (disconnected)
Oct 1 18:14:28 pc kernel: cd1 at umass-sim2 bus 2 scbus8 target 0 lun 0
Oct 1 18:14:28 pc kernel: cd1: <Linux File-CD Gadget 0310> detached
Oct 1 18:14:28 pc kernel: (cd1:umass-sim2:2:0:0): Periph destroyed
Oct 1 18:14:28 pc kernel: umass2: detached
Oct 1 18:14:29 pc kernel: pid 2602 (bsdisks), jid 0, uid 0: exited on signal 11 (core dumped)
Oct 1 18:14:30 pc devd[877]: notify_clients: send() failed; dropping unresponsive client
```
The core file isn't very helpful:
```
Core was generated by `/usr/local/bin/bsdisks --no-debug --syslog-output'.
Program terminated with signal SIGSEGV, Segmentation fault.
Address not mapped to object.
#0 0x00000000002432ed in ?? ()
[Current thread is 1 (LWP 101791)]
(gdb) bt
#0 0x00000000002432ed in ?? ()
#1 0x0000000000229290 in ?? ()
#2 0x000000080086683d in QObject::event(QEvent*) () from /usr/local/lib/qt5/libQt5Core.so.5
#3 0x000000080083bd7d in QCoreApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/local/lib/qt5/libQt5Core.so.5
#4 0x000000080083b980 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/local/lib/qt5/libQt5Core.so.5
#5 0x000000080083c9f9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/local/lib/qt5/libQt5Core.so.5
#6 0x00000008008948b8 in ?? () from /usr/local/lib/qt5/libQt5Core.so.5
#7 0x00000008016f612e in g_main_context_invoke_full () from /usr/local/lib/libglib-2.0.so.0
#8 0x00000008016f64d4 in ?? () from /usr/local/lib/libglib-2.0.so.0
#9 0x00000008016f6596 in ?? () from /usr/local/lib/libglib-2.0.so.0
#10 0x00000008008942f0 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/local/lib/qt5/libQt5Core.so.5
#11 0x0000000800837f17 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/local/lib/qt5/libQt5Core.so.5
#12 0x000000080083c01e in QCoreApplication::exec() () from /usr/local/lib/qt5/libQt5Core.so.5
#13 0x0000000000225e22 in ?? ()
#14 0x000000000021af50 in ?? ()
#15 0x000000000021ae50 in ?? ()
#16 0x0000000000000000 in ?? ()
```https://foss.heptapod.net/bsdutils/bsdisks/-/issues/15org.freedesktop.UDisks2.Block.IdType names filesystems differently from Linux2021-07-27T10:02:35ZDamjan Jovanovicorg.freedesktop.UDisks2.Block.IdType names filesystems differently from LinuxIn Wine, the drive type emulated to Windows apps is determined by checking the filesystem type. This check, in its `dlls/mountmgr.sys/dbus.c`, works by checking if org.freedesktop.UDisks2.Block.IdType is "iso9660" or "udf". FreeBSD uses ...In Wine, the drive type emulated to Windows apps is determined by checking the filesystem type. This check, in its `dlls/mountmgr.sys/dbus.c`, works by checking if org.freedesktop.UDisks2.Block.IdType is "iso9660" or "udf". FreeBSD uses "udf" too and will work, but our ISO9660 filesystem is called "cd9660" instead, and won't match.
It's easy to add "cd9660" to Wine, but what should we generally do here? Use Linux's filesystem names, or patch apps to check for ours too?https://foss.heptapod.net/bsdutils/bsdisks/-/issues/13100% CPU usage in gvfs-udisks2-volume-monitor2021-03-25T16:33:33ZDamjan Jovanovic100% CPU usage in gvfs-udisks2-volume-monitorIn both version 0.24 and 0.25, when unmounting a drive:
```
last pid: 3212; load averages: 0.81, 0.31, 0.12 up 0+00:01:53 16:48:17
PID THR PRI NICE SIZE RES STATE C TIM...In both version 0.24 and 0.25, when unmounting a drive:
```
last pid: 3212; load averages: 0.81, 0.31, 0.12 up 0+00:01:53 16:48:17
PID THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
2823 5 103 0 67M 15M CPU7 7 0:54 99.09% gvfs-udisks2-volume
```https://foss.heptapod.net/bsdutils/bsdisks/-/issues/1Honor /etc/fstab in Filesystem.Mount2020-02-10T14:16:16ZGleb PopovHonor /etc/fstab in Filesystem.MountDocumentation for http://storaged.org/doc/udisks2-api/latest/gdbus-org.freedesktop.UDisks2.Filesystem.html#gdbus-method-org-freedesktop-UDisks2-Filesystem.Mount says:
> The directory the filesystem will be mounted in is determined by ...Documentation for http://storaged.org/doc/udisks2-api/latest/gdbus-org.freedesktop.UDisks2.Filesystem.html#gdbus-method-org-freedesktop-UDisks2-Filesystem.Mount says:
> The directory the filesystem will be mounted in is determined by looking at data related to the device or filesystem (such the filesystem UUID and label) and will be created automatically except if the device the filesystem resides on is referenced in the /etc/fstab file
> If the device in question is referenced in the /etc/fstab file, the mount command is called directly (as root) and the given options or filesystem type given in options are ignored.