Bug#961745: [Pkg-pascal-devel] Bug#961745: [Pkg-utopia-maintainers] Bug#961745: udisks2 2.9.0-1 problems
Based on your suggestion, I wrote to the doublecmd developer and they solved this problem. Thanks.
Bug#961745: [Pkg-pascal-devel] Bug#961745: [Pkg-utopia-maintainers] Bug#961745: udisks2 2.9.0-1 problems
Control: tags -1 + fixed-upstream Hi! Thanks for forwarding this bug, On Fri, 29 May 2020 at 02:00, Michael Biebl wrote: > Apparently doublecmd calls udisksctl mount -b > I'm not really speaking Pascal: Maybe it is parsing the output of that > command (which is brittle). > I notice the difference between 2.8.x and 2.9.x > > 2.8.x: > udisksctl mount -b /dev/sdb2 > Mounted /dev/sdb2 at /media/michael/Test. > > 2.9.x: > udisksctl mount -b /dev/sdb2 > Mounted /dev/sdb2 at /media/michael/Test > > (note the missing '.') > > Maybe doublecmd get's confused by that. It is fixed upstream [1]. Regards Graham [1] https://sourceforge.net/p/doublecmd/code/9425/
Bug#961745: [Pkg-utopia-maintainers] Bug#961745: udisks2 2.9.0-1 problems
May be. I will write to him. Thanks. 29.05.2020, 02:57, "Michael Biebl" : > Apparently doublecmd calls udisksctl mount -b > I'm not really speaking Pascal: Maybe it is parsing the output of that > command (which is brittle). > I notice the difference between 2.8.x and 2.9.x > > 2.8.x: > udisksctl mount -b /dev/sdb2 > Mounted /dev/sdb2 at /media/michael/Test. > > 2.9.x: > udisksctl mount -b /dev/sdb2 > Mounted /dev/sdb2 at /media/michael/Test > > (note the missing '.') > > Maybe doublecmd get's confused by that.
Bug#961745: [Pkg-utopia-maintainers] Bug#961745: udisks2 2.9.0-1 problems
Apparently doublecmd calls udisksctl mount -b I'm not really speaking Pascal: Maybe it is parsing the output of that command (which is brittle). I notice the difference between 2.8.x and 2.9.x 2.8.x: udisksctl mount -b /dev/sdb2 Mounted /dev/sdb2 at /media/michael/Test. 2.9.x: udisksctl mount -b /dev/sdb2 Mounted /dev/sdb2 at /media/michael/Test (note the missing '.') Maybe doublecmd get's confused by that. signature.asc Description: OpenPGP digital signature
Bug#961745: [Pkg-utopia-maintainers] Bug#961745: udisks2 2.9.0-1 problems
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 signature.asc Description: OpenPGP digital signature
Bug#961745: [Pkg-utopia-maintainers] Bug#961745: udisks2 2.9.0-1 problems
[Please always CC the bug report on replies] Am 28.05.20 um 19:37 schrieb Сергей Фёдоров: > /etc/fstab : > > # /etc/fstab: static file system information. > # > # Use 'blkid' to print the universally unique identifier for a > # device; this may be used with UUID= as a more robust way to name devices > # that works even if disks are added and removed. See fstab(5). > # > # > # / was on /dev/sda5 during installation > UUID=5dede9d6-ff78-4669-8e74-cc035749b9ba / ext4 > errors=remount-ro 0 1 > # /boot was on /dev/sda1 during installation > UUID=bf20f503-0791-4f37-b907-80468173eb57 /boot ext4defaults > 0 2 > # /home was on /dev/sda10 during installation > UUID=0f21095a-b02c-4d69-b1f9-1f0cacb783ee /home ext4defaults > 0 2 > # /tmp was on /dev/sda7 during installation > UUID=c5e3a2fb-ddf6-433a-b39d-cab7175bbe0e /tmpext4defaults > 0 2 > # /usr was on /dev/sda9 during installation > UUID=ee0b9fca-2326-4b2d-b6b5-bc0541eaf0f2 /usrext4defaults > 0 2 > # /var was on /dev/sda8 during installation > UUID=50a8bdc3-886f-4115-8066-f994ca45d743 /varext4defaults > 0 2 > # swap was on /dev/sda6 during installation > UUID=92183ea7-4dc3-43a0-8346-b4ec643d6956 noneswapsw > 0 0 > /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 > > : lsblk -f > NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% > MOUNTPOINT > sda > ├─sda1 > │ext4 1.0 bf20f503-0791-4f37-b907-80468173eb578,4G 2% > /boot > ├─sda2 > │ > ├─sda3 > │ext4 1.0 DebRepo2 > │ b507efaf-6d1f-4173-9804-6f7d0d4f5a31 406,8G60% > /mnt/repo/ > ├─sda5 > │ext4 1.0 5dede9d6-ff78-4669-8e74-cc035749b9ba 15,4G10% / > ├─sda6 > │swap 1 92183ea7-4dc3-43a0-8346-b4ec643d6956 > [SWAP] > ├─sda7 > │ext4 1.0 c5e3a2fb-ddf6-433a-b39d-cab7175bbe0e 86,4G 0% > /tmp > ├─sda8 > │ext4 1.0 50a8bdc3-886f-4115-8066-f994ca45d743 85,6G 1% > /var > ├─sda9 > │ext4 1.0 ee0b9fca-2326-4b2d-b6b5-bc0541eaf0f2 286,9G 5% > /usr > └─sda10 > ext4 1.0 0f21095a-b02c-4d69-b1f9-1f0cacb783ee 58,7G14% > /home > sdb > ├─sdb1 > │ext4 1.0 s1319ffa1e-d977-4248-8df1-d33acf965314 296,9G62% > /media/u1/ > └─sdb2 > ext4 1.0 s26548b874-6a70-436f-beb7-8ab4612b55a5 > sdc > └─sdc1 > ext4 1.0 D f8f76019-e459-4f5c-b4d0-b2ed4bcbed90 > sdd > └─sdd1 > ext4 1.0 E-G ffbe6520-1584-44a0-adcc-d951c09b24e1 > sde > └─sde1 > ext4 1.0 H bc0046f3-e5c2-4e3e-9359-7a9d3b088833 > sr0 Those error messages you see, where are they coming from? Your desktop environment? Which one do you use? Can you attach a screenshot? Do you get any error messages in the journal? signature.asc Description: OpenPGP digital signature
Bug#961745: [Pkg-utopia-maintainers] Bug#961745: udisks2 2.9.0-1 problems
Control: tags -1 + moreinfo Please attach your /etc/fstab and the output of lsblk -f signature.asc Description: OpenPGP digital signature
Bug#961745: udisks2 2.9.0-1 problems
Package: udisks2 Version: 2.9.0-1 Severity: normal -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages udisks2 depends on: ii dbus 1.12.16-2 ii libacl12.2.53-8 ii libatasmart4 0.19-5 ii libblockdev-fs22.24-1 ii libblockdev-loop2 2.24-1 ii libblockdev-part2 2.24-1 ii libblockdev-swap2 2.24-1 ii libblockdev-utils2 2.24-1 ii libblockdev2 2.24-1 ii libc6 2.30-8 ii libglib2.0-0 2.64.2-1 ii libgudev-1.0-0 233-1 ii libmount1 2.35.2-2 ii libpam-systemd 245.5-3 ii libpolkit-agent-1-00.105-26 ii libpolkit-gobject-1-0 0.105-26 ii libsystemd0245.5-3 ii libudisks2-0 2.9.0-1 ii libuuid1 2.35.2-2 ii parted 3.3-4 ii udev 245.5-3 Versions of packages udisks2 recommends: ii dosfstools 4.1-2 ii e2fsprogs1.45.6-1 ii eject2.35.2-2 ii exfat-utils 1.3.0-1 ii libblockdev-crypto2 2.24-1 ii ntfs-3g 1:2017.3.23AR.3-3 ii policykit-1 0.105-26 Versions of packages udisks2 suggests: pn btrfs-progs pn f2fs-tools pn libblockdev-mdraid2 pn mdadm pn nilfs-tools pn reiserfsprogs pn udftools pn udisks2-bcache pn udisks2-btrfs pn udisks2-lvm2 pn udisks2-zram pn xfsprogs -- no debconf information The udisks2 package version 2.8.4-2 worked fine. Updated to version 2.9.0-1 package In addition to the boot disk, there are 4 disks labeled "D", "H", "E-D" and a disk with two partitions labeled "S1"and " S2". The boot disk is mounted automatically and normally. 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". Returned to udisks2 version 2.8.4-2.
