Maybe someone more familiar with udev can help.
** Package changed: udisks2 (Ubuntu) => udev (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1456338
Title:
USB floppy drive
"udevadm monitor" (runned as root) output is in the attached file. I
have stopped sddm before.
** Attachment added: "udevadm_output.txt"
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1456338/+attachment/5161168/+files/udevadm_output.txt
--
You received this bug notification because
Ok, so it is something that udev is doing. Run sudo udevadm monitor,
then plug in the drive, and see what it outputs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1456338
Title:
I stopped sddm, udisks, udev:
sudo systemctl stop sddm
sudo systemctl stop udisks2.service
sudo systemctl stop systemd-udevd.service
sudo systemctl stop systemd-udevd-control.socket
sudo systemctl stop systemd-udevd-kernel.socket
After connecting the floppy drive, it did not run (seemed not to be
That does indicate that the problem is not in udisks. Try stopping udev
as well before plugging in the drive.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1456338
Title:
USB
> Ahh, ok.. try disabling udisks to see if that is the cause:
> systemctl stop udisks2.service
The wrong behaviour remained. Also when I booted in rescue mode (root shell),
then resumed normal boot, stopped udisks2 and connected the device.
Is it possible that the problem is in systemd?
Now I
Ahh, ok.. try disabling udisks to see if that is the cause:
systemctl stop udisks2.service
Then connect the drive.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1456338
Title:
USB
> Does it also do the same if you plug it in and then boot the system normally?
Yes. When a splash screen "kubuntu" is shown the drive starts "running forever".
> But if you boot in rescue mode, then plug in the drive, it works normally
> even after you resume the normal boot?
No. I have tried
Let me see if I have this right. If you boot the system normally and
plug in the drive, it starts running forever. Does it also do the same
if you plug it in and then boot the system normally? But if you boot in
rescue mode, then plug in the drive, it works normally even after you
resume the
I have installed Ubuntu 18.04 (after removal "/bin", "/usr" and some
other directories on the root FS). The bug remains. If I boot into
rescue mode ("Drop to root shell prompt") and connect the USB floppy
drive without disk, it works normally. If I boot into rescue mode,
select resuming normal
What if you boot into rescue mode?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1456338
Title:
USB floppy drive is running without floppy
Status in udisks2 package in Ubuntu:
I have attached the output of "udisksctl dump" and "udisksctl monitor"
(launched as usual user, not root, before stopping udisks).
I have stopped udisks using "sudo systemctl stop udisks2". The wrong behaviour
has remained (floppy drive has runned without floppy disk).
** Attachment added:
** Attachment added: "udisksctl_monitor.txt"
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1456338/+attachment/5071621/+files/udisksctl_monitor.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
What if you only shut down udidks? Can you post the output of udisksctl
dump?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1456338
Title:
USB floppy drive is running without
The same problem in Ubuntu 17.10 (updated from previuos version). I
tried to stop some systemd services, remove kernel modules, kill some
processes and unmount some filesystems. There are output of lsmod, ps,
mount (executed after stopping, removing modules and so on) below. The
problem was not
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
16 matches
Mail list logo
