root@pswsl01:~# software-properties-gtk &
[1] 18337
root@pswsl01:~#
root@pswsl01:~#
root@pswsl01:~# Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 173, in
activate_name_owner
return self.get_name_owner(bus_name)
^^^
And by the way, I just tested the old setup with your full
recommendation, adding the BEFORE= statement and it finally stopped the
I/O errors. I can now take the time to transition properly.
Thank you!
Pedro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "systemd-analyze dot graph"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1924494/+attachment/5492912/+files/USRgraph.svg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Attachment added: "Services, hook, and journal after adding AFTER= and
REQUIRES="
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1924494/+attachment/5492904/+files/buglog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Christian
I set this up back when without properly researching systemd.mount,
particularly the automatic dependencies. I make half of the changes you
recommended (Requires=virt-guest-shutdown.target; After=virt-guest-
shutdown.target) and it made no change, the I/O errors still showed up.
I'm att
Hi Christian,
Thanks for your attention. I replicated the issue and here is the
journal log for today.
Regards
Pedro Serrano
On Wed, 2021-04-21 at 11:08 +, Christian Ehrhardt wrote:
> Hi Pedro,
>
> > Wouldn't it be beneficial for all guests to be shutdown before
Sure can. I'm away but should have access to that laptop tomorrow
afternoon.
Would it matter if I re-created the conditions and sent you that
journal?
On Apr 21, 2021, 07:21, at 07:21, "Christian Ehrhardt "
<1924...@bugs.launchpad.net> wrote:
>Hi Pedro,
>
>> Wouldn't it be beneficial for all g
Public bug reported:
Last night I started a reboot without manually shutting down a qemu/kvm
guest first. After X went down a bunch of I/O errors associated with a
network block device that contains a NTFS filesystem showed up on the
console. I noticed that the umount.target had been reached b
Same result:
echo "dummy" >> /etc/modules
echo "options dummy numdummies=4" >> /etc/modprobe.d/dummy-options.conf
Reboot...
lsmod|grep dummy ; SHOWS THE dummy MODULE LOADED.
no dummy devices are created.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
And the error messages pertinent to the issue with the VLAN are:
=
may 01 11:34:31 ps01lnx systemd[1]: Started Network Service.
may 01 11:34:31 ps01lnx systemd[1]: systemd-networkd.service: Failed to send
unit change signal for systemd-networkd.ser
Nope, it is still a problem in "systemd 231-9ubuntu4 amd64". Actually,
it seems like multiple features documented in the Ubuntu Manpages for
systemd.network are not functioning. Below are some error messages
(journalctl -a -u systemd-networkd), followed by the configuration
files.
ERROR MESSAGES
Public bug reported:
just doing an apt-get update &&apt-get dist-upgrade on ubuntu 15.04
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: menu 2.1.47ubuntu1
Uname: Linux 3.19.0-031900-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
Date: Tue Mar
Public bug reported:
** (update-manager:7750): WARNING **: Couldn't connect to accessibility
bus: Failed to connect to socket /tmp/dbus-GxEtj3txBA: Connection
refused
Always happens when using update-manager.. System originally installed from
Trusty media, upgraded to Utopic. Happened in bot
13 matches
Mail list logo
