"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
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
> 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 hav
> 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 to
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 boot
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: "udis
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
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 sol
I have tried to log file access using fatrace during the USB floppy
drive connection.
** Attachment added: "Fatrace output during connection the drive"
https://bugs.launchpad.net/ubuntu/+bug/1456338/+attachment/4399839/+files/fatrace.txt
--
You received this bug notification because you are
Public bug reported:
When I connect USB floppy drive (Gembird) without floppy under Ubuntu, the
drive engine seems to be running (the floppy drive LED is on and the drive is
sounding). The same behaviour takes place if I connect the drive with a floppy
and then remove the floppy. It seems that
Motherboard: ASUS P5LD2-SE.
CPU: Intel Core 2.
Kernel: Linux 3.11.0-13-generic from Ubuntu 13.10.
"standby" is ACPI S1 state.
If I am not mistaken, pm-utils use "standby" only if "mem" (S3 ACPI) state is
not available. It cannot be configured to use "standby" instead of "mem" using
configuration
Public bug reported:
The state (for /sys/power/state) is hardcoded in systemd-shim. My computer
doesn't go into the "mem" state under Ubuntu so I want to use "standby". If I
am not mistaken some software in Ubuntu uses systemd interface to suspend the
system. "pm-suspend" doesn't allow to selec
12 matches
Mail list logo
