Public bug reported:
On Ubuntu 22.04 the package ansible-core 2.12.0-1 can not be installed (ansible
and python3-ansible-runner ware already installed):
ansible-core (2.12.0-1) wird eingerichtet ...
[Errno 2] No such file or directory:
'/usr/lib/python3.10/dist-packages/ansible/module_utils/ansi
Public bug reported:
Hello,
as reported in https://bugs.launchpad.net/ubuntu/+source/intel-
gmmlib/+bug/1966362 for Ubuntu 22.04, libigdgmm12 version 22.1.1+ds1-1
had an ABI-breaking change that brokje vaapi - this was fixed with the
version 22.1.2+ds1-1, but unfortunately it seems that intel-med
Public bug reported:
Dear Maintainer,
the udev rule installed from debian/ir-keytable.udev is not guaranteed to be
run at the
appropriate moment during bootup which can cause the remote not to be
configured according to the settings in /etc/rc_maps.cfg. This seems to occur
more often with newer
Also the shebang should be changed to #!/usr/bin/env python2 since
/usr/bin/python does not exist anymore in
Ubuntu focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816473
Title:
obamenu depen
I encountered a dead symbolic link for libvdpau.so:
$ ls -l /usr/lib/x86_64-linux-gnu/libvdpau_nvidia.so
lrwxrwxrwx 1 root root 31 Feb 22 18:50
/usr/lib/x86_64-linux-gnu/libvdpau_nvidia.so -> vdpau/libvdpau_nvidia.so.390.25
libvdpau_nvidia.so.390.25 is located in the same directory, not in the
s
Public bug reported:
Using the latest autofs package (with libtirpc support) the automount
process crashes when mounting a nfs share (at least when using IPv4).
I am using a file /etc/auto.master.d/net.autofs to be able to mount
arbitrary nfs shares to /net:
/net-hosts -intr,soft --timeout=6
Hello,
both systemd packages in the -proposed repository for xenial (229-4ubuntu12)
and yakkety (231-9ubuntu1) are sending all the DBus signals I need to track
unit state changes, thank you very much for fixing this regression.
--
You received this bug notification because you are a member of U
I have been able to reproduce those missing signals most reliably within
a systemd user session (for the system session it works most of the
time):
Steps to reproduce missing dbus signals with Ubuntu 16.10 Desktop:
Create a ~/.config/systemd/user/terminal.service with this content:
[Unit]
Descri
Public bug reported:
Since the penultimate systemd package update in september (229-4ubuntu8)
systemd does not send the remaining queued DBus signals (e.g.
PropertiesChanged) when a unit's state changes to inactive.
Sending those signals has been working since the release of Ubuntu 16.04
and it i
Would it be possible to include this change to be able to receive all
queued DBus signals from a unit before it is removed?
https://github.com/systemd/systemd/commit/0dd99f86addd1f81e24e89807b6bc4aab57d5793
Tracking unit states using DBus signals has been working initially with
Ubuntu 16.04 but do
https://launchpad.net/~seahawk1986-hotmail/+archive/ubuntu/misc/+packages?field.name_filter=sysinfo&field.status_filter=published&field.series_filter=xenial
- simply download
https://launchpad.net/~seahawk1986-hotmail/+archive/ubuntu/misc/+files/sysinfo_0.7-11~ppa1_all.deb
(this url might change
Please have a look at the attached patch, which fixes the crash (caused
by attempted string operations on a null pointer due to a missing tag in
the gnome-version.xml) for me (although it does not change the crude way
that is used to parse the file /usr/share/gnome/gnome-version.xml).
** Patch add
12 matches
Mail list logo
