I can confirm this error and the workarounds.
The workaround to correct cniVersion in ~/.config/cni/net.d/*.conflist is
working for me but it isnn't very intuitive for others.
The universe package containernetworking-plugins corrects this too but thats
not easy maintable for a production system
@mark You need to enable the proposed archive to get the packages I
mentioned. See https://wiki.ubuntu.com/Testing/EnableProposed. I highly
recommend using the "selective" approach.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Installing the packages below seems to work for me (on Ubuntu 22.04.4,
X11, nvidia-550.78). No terminal lag is observed.
mutter=42.9-0ubuntu8
mutter-common=42.9-0ubuntu8
libmutter-10-0=42.9-0ubuntu8
gir1.2-mutter-10=42.9-0ubuntu8
--
You received this bug notification because you are a member of
I had to downgrade the mutter packages on Ubuntu 22.04.4 today as the
lag returned after the latest update. Did almost the same as Deku King
although opted to deprioritize the 42.9-0ubuntu7.1 packages instead of
locking the older ones.
Package: gir1.2-mutter-10
Pin: version 42.9-0ubuntu7.1
Workaround: https://askubuntu.com/a/1427981
** Bug watch added: gitlab.com/sane-project/frontend/xsane/-/issues #50
https://gitlab.com/sane-project/frontend/xsane/-/issues/50
** Also affects: xsane via
https://gitlab.com/sane-project/frontend/xsane/-/issues/50
Importance: Unknown
I can also confirm the lag is gone on my 22.04 laptop using X11 with
nvidia-driver-550 when using the PPA packages.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059847
Title:
Input lag
I can confirm the lag is gone on my 23.10 system using X11 with nvidia-
driver-550 when using the PPA packages.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059847
Title:
Input lag or
** Package changed: network-manager-applet (Ubuntu) => network-manager
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973289
Title:
Qualcomm Snapdragon X55 5G does not turn on
To manage
This is a bug on certified hardware
https://ubuntu.com/certified/202102-28710
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973289
Title:
Qualcomm Snapdragon X55 5G does not turn on
To manage
Probably the NetworkManager package - not the applet
** Tags added: network wwan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973289
Title:
Qualcomm Snapdragon X55 5G does not turn on
To
Public bug reported:
The system tries to configure the device, but never manages to turn on
the hardware. I have to do it by hand by using
sudo qmicli -p -d /dev/wwan0mbim0 --device-open-auto --dms-foxconn-set-
fcc-authentication=0
I also have a case here on ask ubuntu:
Hello,
Thanks for the help! :)
Are these cifs patches present in 5.13.0.27? I got similar issues with
5.4.0.97 and 5.13.0.27, and moving to previous releases fixed the issues
in both cases! :)
Cheers!
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
FWIW, I ran into this issue on when booting the latest available kernel
(after an update) on a Debian VM running on a Debian host. Only booting
the latest kernel triggered the issue.
The key was the "Device out of space" message that lead me to this
bug/message.
As vt100 found, and christiank
** Attachment added: "powertop-5.13.0+.html"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5515994/+files/powertop-5.13.0+.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Kai-Heng,
I have tried kernel 5.13.0+ from #73.
Power consumption is the same and NVMe has ASPM L1 enabled both before and
after suspend/resume. I have been running the kernel for a few hours now and
also done some suspend/resume and it seems to work fine.
I have attached dmesg and powertop
Just a follow-up to anyone else is using this hardware.
I have been using kernel 5.11.0-17-generic and "echo 0 | sudo tee
/sys/bus/pci/devices/\:58\:00.0/d3cold_allowed" just after boot. Now I have
uptime 4 days 23 hours with many suspend/resumes and power consumption is
remaining as it is
** Attachment added: "lspci-5.13.0-051300rc2.after.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5499184/+files/lspci-5.13.0-051300rc2.after.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Koba, I have attached output from "sudo lspci -vvv" before and after
suspend/resume for kernel 5.13.0-051300rc2-generic.
** Attachment added: "lspci-5.13.0-051300rc2.before.txt"
@Koba
I tried kernel 5.13.0-051300rc2-generic. After boot d3cold_allowed was "1",
ASPM L1 enabled for nvme (and bluetooth did not work). After suspend/resume
ASPM L1 was disabled for nvme. Power consumption higher. dmesg is attached.
** Attachment added: "dmesg-koba-5.13.0.rc2.txt"
@Koba,
I have tested kernel 5.10.0-1025lpv1912057i.
After boot cat /sys/bus/pci/devices/\:58\:00.0/d3cold_allowed showed "0".
After suspend/resume power consumption is the same as before and ASPM L1 is
enabled for NVMe. I have attached dmesg.
My full name is Henrik Juul Hansen
@Koba,
Sorry, but I do not know what "test-by signature" is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912057
Title:
Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
To
@Koba,
I have tried kernel 5.10.0-1025lpv1912057h. After boot cat
/sys/bus/pci/devices/\:58\:00.0/d3cold_allowed showed "0".
After suspend/resume power consumption is the same and ASPM L1 is enabled for
NVMe. I have attached dmesg. I will test the kernel for a longer time period
and see if
@Koba,
I have tried kernel 5.10.0-1025lpv1912057g. After boot cat
/sys/bus/pci/devices/\:58\:00.0/d3cold_allowed showed "0".
After suspend/resume the power consumption is higher. ASPM is disabled for
Nvme. I have attached dmesg.
** Attachment added: "dmesg-koba-5.10.0-1025lpv1912057g.txt"
@Koba,
Thanks for your help.
I have tried the kernel from #55.
sudo cat /sys/bus/pci/devices/\:58\:00.0/d3cold_allowed showed "0".
The suspend & resume did end up in a freeze. I have attached dmesg (journalctl
-k -b -1 on next boot).
Just as a note I saw the power consumption during suspend
** Attachment added: "powertop-5.10.0-1025-oem.before.html"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5495699/+files/powertop-5.10.0-1025-oem.before.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "powertop-5.10.0-1025-oem.after.html"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5495700/+files/powertop-5.10.0-1025-oem.after.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Koba,
Here is the dmesg from kernel(5.10.0-1025lpv1912057e).
For the official 5.10-oem-1025 it seems like disabling d3cold for nvme fixes
the issue. ASPM L1 Enabled for nvme and power consumption after suspend/resume
is as before. I have attached output from powertop.
** Attachment added:
Hi Koba,
This time the laptop did not resume at all. It did boot first and seemed to
function normally but I did not test and quite fast after 30-60sec suspended
it. Do you want a dmesg just after boot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Koba, I have tried kernel from #45 (5.10.0-1025lpv1912057d). After
suspend, it fails when resuming. The laptop wakes up and I am able to
log in, but then it freezes. So no dmesg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Koba
I can only see the buildinfo file in the last folder.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912057
Title:
Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
To
@Koba
No problem. I will do.
I have tested kernel in #43 (5.10.0-1025lpv1912057c) and attached dmesg. This
kernel does not fix the issue. ASPM is Disabled for NVMe and higher power
consumption after suspend/resume.
** Attachment added: "dmesg-koba-5.10.0-1025lpv1912057c.txt"
@Koba
I have tested kernel in #41 (5.10.0-1025lpv1912057b) and attached dmesg. This
kernel does not fix the issue. ASPM is Disabled for NVMe and higher power
consumption after suspend/resume.
** Attachment added: "dmesg-koba-5.10.0-1025lpv1912057b.txt"
@Koba
I have tested the kernel from #39. It fixes the issue. I have attached dmesg.
(Installing the headers failed).
** Attachment added: "dmesg.koba.5.10.0.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5494936/+files/dmesg.koba.5.10.0.txt
--
You received
@koba
Using kernel from #31 - the power consumption is the same before and after
suspend/resume and ASPM L1 is enabled for the NVMe after resume. Yes the issue
is gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi again,
I have reopened this issue. It is not fixed in mainline 5.11.0, 5.11.7
or 5.11.10.
I think I was using your kernel and mixed up the version numbers when I sent
the message in #34. Since last I have updated BIOS version from V304->V306. For
the last month I have been using the laptop
** Changed in: linux (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912057
Title:
Power consumption higher after suspend - Ubuntu 20.10 on Asus
** Project changed: sound-juicer => gvfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/627008
Title:
Cannot read cd: sound-juicer and gvfs problem (workaround included)
To manage notifications
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #127
https://gitlab.gnome.org/GNOME/gvfs/-/issues/127
** Changed in: sound-juicer
Importance: Medium => Unknown
** Changed in: sound-juicer
Status: Confirmed => Unknown
** Changed in: sound-juicer
Remote watch: GNOME Bug
Public bug reported:
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software from a Launchpad
The issue is resolved in latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11/amd64/
I will change the status as resolved.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
After using the kernel from #31 for 3 days and having many
suspend/resumes the system has resumed with ASPM L1 enabled and same
power as before suspend every time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Good news!
Before suspend/resume:
Powertop: around 1.5W - pc2,3,7,8,10
ASPM L1 enabled for all controllers
After suspend/resume:
Powertop: around 1.5W - pc2,3,7,8,10
ASPM L1 enabled for all controllers
Fn-keys and touchpad working.
Dmesg is attached.
** Attachment added: "dmesg.5.11.0-7"
I tried the ~khfeng/lp1912057-bridge-d0-2.
Before suspend/resume:
Powertop: around 1.4W - pc2,3,7,8,10
ASPM L1 enabled for all controllers
After suspend/resume:
Powertop: around 4.6W - pc2,3
ASPM Disabled for NVMe
Attached dmesg after "echo 'file drivers/pci/* +p' >
Before suspend/resume:
Powertop: around 1.4W - pc2,3,7,8,10
ASPM L1 enabled for all controllers
After suspend/resume:
Powertop: around 4.6W - pc2,3
ASPM Disabled for NVMe
Fn-keys and touchpad working.
** Attachment added: "dmesg.5.11.0-6"
I did a similar test as you asked in comment #20.
Before suspend/resume:
Powertop: around 1.5W - pc2,3,7,8,10
ASPM L1 enabled for all controllers
After suspend/resume:
Powertop: around 4.8W - pc2,3
ASPM Disabled for NVMe
Fn-keys and touchpad working.
** Attachment added: "dmesg.5.10.0-2011"
** Attachment added: "dmesg.rc4+"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5457093/+files/dmesg.rc4+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912057
Title:
I have not used dynamic_debug before - hope I did it right.
As regular user: "sudo -i"
Then as root: "echo 'file drivers/pci/* +p' >
/sys/kernel/debug/dynamic_debug/control"
followed by "dmesg > dmesg.rc4".
** Attachment added: "dmesg.rc4"
Thanks for the new kernel. I have tried it.
Before suspend/resume:
Power consumption around 2.4 W
Idle stats: pc2-pc3-pc6 is reached
ASPM L1 enabled for NVMe
After suspend/resume:
Power consumption around 4.9 W
Idle stats: pc2-pc3 is reached
ASPM Disabled for NVMe
and keys & touchpad is
** Attachment added: "rc4.html"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5456383/+files/rc4.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912057
Title:
I have tested the rc4+ kernel (two reboots with similar results).
I will try to summarize the results:
Rc4+: ASPM L1 enabled both before and after suspend/resume!
Rc4+ before suspend/resume:
Power consumption around 4.3 W
Idle stats: pc2-pc3 is reached
ASPM L1 enabled for NVMe (and all others)
Output of "sudo acpidump > acpidump" is attached.
"cat /sys/bus/pci/devices/:00:1d.0/firmware_node/path" - outputs
"\_SB_.PCI0.RP09"
** Attachment added: "acpidump"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5456217/+files/acpidump
--
You received this bug
Thanks a lot for the help!
I have tried kernel 5.11-rc4.
It does not solve the issue. I have tried 2 test/reboots.
Power consumption seems better with new kernel just after boot - around 1.5W
but after suspend/resume it is around 4.6W witch is much the same. The ASPM
state is like with the old
I have done the following - turned off pc. At boot pressed "e" added -
pci.dyndbg log_buf_len=16M - to the parameteres after VT-handoff. Logged
in, suspend/resumed and added output of "sudo dmesg".
** Attachment added: "dmesg"
** Attachment added: "lspci_after.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5456034/+files/lspci_after.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912057
** Attachment added: "lspci_before.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5456033/+files/lspci_before.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have run the command and attached the output. I did it both just after
boot and after suspend/resume - same result both times, so I have
attached just one output "active".
I have been poking around to see any differences in drivers/system state
between after boot and after suspend/resume. I
** Attachment added: "Powertop after suspend"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5453727/+files/after.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After boot the idle power consumption is around 2.3 W but after suspend it is
4.7 W.
The measurement is 5-10 min after boot/resume - looking at "top" to see system
was idle.
This is consistent - I have tried more that 10 times.
BIOS is updated to latest version.
I have
The command below gets the controller working again for me.
echo -n ":0a:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind
sleep 5
echo -n ":0a:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have a similar issue with my Logitech Brio. Used with Google Meet I
can usually get through one meeting after which the webcam hangs and the
camera light stays on, even through a reboot. A combination of
unplugging, rebooting and replugging seems to be necessary to recover
it.
The webcam has
> I have same problem.
What architecture? (you can run "uname -m")
What version of Ubuntu? (you can run "lsb_release -a")
What version of apache2?
> Did you solve this?
Yes, by downgrading to 2.4.18-2ubuntu3.17.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
These are the binary packages from the apache2 source package I have
installed:
apache2
apache2-bin
apache2-data
apache2-utils
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs,
My ppc machine is running Xenial. I realize that ppc isn't supported,
and Xenial is on its last legs, so if ppc is the only platform where
this SRU fails then I can figure out a way to live with it. But I
thought I'd report it anyway in case it's not only failing on ppc.
--
You received this bug
apache2 2.4.18-2ubuntu3.18 fails to start on my ppc machine (4.4.0-197
-powerpc-smp #229-Ubuntu):
Nov 28 14:42:31 macmini systemd[1]: Starting LSB: Apache2 web server...
Nov 28 14:42:31 macmini apache2[1284]: * Starting Apache httpd web server
apache2
Nov 28 14:43:03 macmini apache2[1284]:
** Bug watch added: Debian Bug tracker #216923
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216923
** Changed in: ddclient (Debian)
Status: New => Unknown
** Changed in: ddclient (Debian)
Remote watch: Debian Bug tracker #285007 => Debian Bug tracker #216923
** Summary changed:
I am assuming this has been fixed upstream. If not, please reopen.
** Changed in: ddclient (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267448
Closing stale bug report as invalid.
** Changed in: ddclient (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/483936
Title:
ddclient dpkg-configure with "select
Unable to reproduce in ddclient 3.9.1-5, so I am assuming it has been
fixed. If not, please reopen.
** Changed in: ddclient (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
systemd unit file is in version 3.9.1-5.
** Changed in: ddclient (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630661
Title:
provide systemd
Unable to reproduce. If you can reproduce the problem, please reopen and
provide instructions.
** Changed in: ddclient (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unable to reproduce. Possibly fixed in a newer version of the ddclient
package.
** Changed in: ddclient (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235506
Closing stale bug report as invalid.
ddclient 3.9.1-7 (not yet released) will have many debconf improvements.
Please wait for that version to be released. If the debconf questions in
that version are still insufficient, please reopen.
** Changed in: debconf (Ubuntu)
Status: New => Invalid
Likely fixed in a newer version of the ddclient package. Please reopen
if that is not the case.
** Changed in: ddclient (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ddclient (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/700423
Title:
package ddclient 3.8.0-4ubuntu1.1 failed to install/upgrade:
subprocess
Likely fixed in newer versions of the ddclient package.
** Changed in: ddclient (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755482
Title:
package
Closing stale bug report as invalid.
** Changed in: ddclient (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1081171
Title:
package ddclient 3.8.1-1ubuntu1
*** This bug is a duplicate of bug 1662314 ***
https://bugs.launchpad.net/bugs/1662314
** This bug has been marked a duplicate of bug 1662314
ddclient installations breaks dhclient hooks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Bug watch added: Debian Bug tracker #807707
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807707
** Also affects: ddclient (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807707
Importance: Unknown
Status: Unknown
** Changed in: ddclient (Ubuntu)
The logs do not contain enough information, and this bug report is
really old with no recent activity, so I am closing it as invalid.
** Changed in: ddclient (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The logs do not contain enough information, and this bug report is
really old with no recent activity, so I am closing it as invalid.
** Changed in: ddclient (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The logs do not contain enough information, and this is a really ancient
bug report with no recent activity, so I am closing as invalid.
** Changed in: ddclient (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fixed in ddclient 3.8.1-1.1.
** Bug watch added: Debian Bug tracker #652298
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652298
** Also affects: ddclient (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652298
Importance: Unknown
Status: Unknown
** Changed in:
** Changed in: ddclient (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092966
Title:
Freedns support removed from ddclient
To manage notifications
** Changed in: ddclient (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704159
Title:
a bug in dhcp exit hook script of ddclient
To manage
** Changed in: ddclient (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800150
Title:
ddclient 3.8.3 incompatible with current CloudFlare API,
(Closes: #832395, #832396)
+ * debian/control: Set `Rules-Requires-Root: no`
+
+ -- Richard Hansen Tue, 28 Jul 2020 01:46:01
+ -0400
ddclient (3.9.1-4) unstable; urgency=medium
* Delete superseded debian/salsa-ci.yml file.
-- Richard Hansen Wed, 22 Jul 2020 16:26:52
-0400
.
- -- Richard Hansen Wed, 22 Jul 2020 16:26:52
+ -- Richard Hansen Wed, 22 Jul 2020 16:26:52
-0400
ddclient (3.9.1-3) unstable; urgency=medium
- * Use dh_systemd_{enable,start} instead of dh_installsystemd
- * Upgrade to debhelper-compat 12
+ * Use dh_systemd_{enable,start
> This renders the configuration script useless
Omitting the line continuation backslashes causes the 'server=' and
'protocol=' lines to set defaults that apply to subsequent hostnames, so
it should still work. If it is still not working for you, please paste a
detailed log.
** Changed in:
.
---
ddclient (3.9.1-4) unstable; urgency=medium
* Delete superseded debian/salsa-ci.yml file.
-- Richard Hansen Wed, 22 Jul 2020 16:26:52
-0400
ddclient (3.9.1-3) unstable; urgency=medium
* Use dh_systemd_{enable,start} instead of dh_installsystemd
* Upgrade to debhelper-compat 12
** Changed in: ddclient (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446565
Title:
enhance manpage of ddclient with explanation of options
To manage
*** This bug is a duplicate of bug 1446565 ***
https://bugs.launchpad.net/bugs/1446565
** This bug has been marked a duplicate of bug 1446565
enhance manpage of ddclient with explanation of options
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: Debian Bug tracker #682904
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682904
** Also affects: ddclient (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682904
Importance: Unknown
Status: Unknown
** Bug watch added: ddclient bugs on GitHub
*** This bug is a duplicate of bug 1800150 ***
https://bugs.launchpad.net/bugs/1800150
** This bug has been marked a duplicate of bug 1800150
ddclient 3.8.3 incompatible with current CloudFlare API, please update to
3.9.0
--
You received this bug notification because you are a member of
** Bug watch added: Debian Bug tracker #913308
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913308
** Also affects: ddclient (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913308
Importance: Unknown
Status: Unknown
--
You received this bug notification
://launchpad.net/~ddclient/+archive/ubuntu/ppa
** Changed in: ddclient (Ubuntu)
Assignee: (unassigned) => Richard Hansen (rhansen)
** Changed in: ddclient (Ubuntu)
Status: New => In Progress
** Bug watch added: Debian Bug tracker #950246
https://bugs.debian.org/cgi-bin/bugrepo
(Ubuntu)
Assignee: (unassigned) => Richard Hansen (rhansen)
** Changed in: ddclient (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800150
Title:
dd
Gosh. I'd happily forgotten about that video. I was so young and so
mumbly. :D
I'm not sure I understand. If you're not uploading to groovy, how are
you collecting test results?
Also, I don't know what sort of test facilities or processes you have
available, so I don't know how time consuming or
To clarify, I meant: Is there any particular reason to not just upload
this fix *to Groovy* now? I know an SRU needs validation first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/691590
Title:
A non-root process that uses qemu:///system to run virtual machines
(which is required for most network configurations) will lose access to
its disk images for good as soon as the domain is started.
First it'll be changed to libvirt-qemu:kvm and once the domain is
terminated it will be set to
It's exceptionally frustrating.
It's been a while since it was solved upstream such that when a domain
is terminated, the image ownership gets restored to what it was when the
domain was launched. However, the way it tracks the original ownership
is by storing it in xattr's of the image... but
1 - 100 of 3638 matches
Mail list logo
