--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2055776
Title:
After updating ubuntu, the network to which the subnet address is
assigned does not become active in KVM.
Something in a recent dnsmasq update broke KVM. I hit the same and found
a workaround that gets me rolling again wtih KVM guests at least
here's a quick shell summary:
bladernr@galactica:~$ sudo virsh net-start default
error: Failed to start network default
error: internal error: Child
Questions/Comments:
What does "remotely" mean here? The bug report speaks of using the laptop
keyboard, not remote access; and a remote connection would mean just passing
a data stream - the local keymap setting has no effect on the keys sent by a
remote connection.
localectl is not how we
>If direct access to Launchpad is blocked how was a bug report filed in
the first place?
Clicking the "Report a Bug" link on any project's page in LP. This is
done from a machine outside of the airgapped or restricted access lab
where the hardware sits.
Also, I should point out (which I
Public bug reported:
We very often tell our hardware partners to "file a bug" when they
encounter issues. This requires them to run apport-collect to gather
and submit logs for the bug.
However, very often, the hardware that has the problem is in a lab that
has tight security restrictions and
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows "systemd-udevd[2837]:
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows "systemd-udevd[2837]: nvme0n1:
Can this be reproduced in EFI mode, or is it only when in Legacy Mode?
ALso, what is the mount command you are using? Just basic like "mount
/dev/device /mountpoint"? Or is there a different mount command you are
using that is failing?
--
You received this bug notification because you are a
Please verify this is no longer an issue in Focal or Hirsute based on
Graham's comment #3 above.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: lvm2 (Ubuntu Focal)
Status: Confirmed => Incomplete
** Changed in: lvm2 (Ubuntu Hirsute)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1933359
Title:
[Ubuntu 21.10][Broadcom] mpi3mr driver submission request
Mariusz,
> The following patches should fix the issue (not verified yet):
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81
Were those patches verified to fix
Can this please be targeted for 21.10?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid array
Status in lvm2 package in
** Also affects: lvm2 (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon
** Changed in: lvm2 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid array
Just spun up a Focal LXD container and this is still an issue in
containers:
bladernr@focal-builder:~/development/kernels-ubuntu/focal$ sudo vim
/etc/apt/sources.list
sudo: setrlimit(RLIMIT_CORE): Operation not permitted
** Also affects: sudo (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
I fired up a LXD container using ubuntu-daily:f on my machine and every
time I issue a comment inside the container using sudo, I get this
error:
sudo: setrlimit(RLIMIT_CORE): Operation not permitted
I did some digging online and found this was reported against Fedora last
** Tags removed: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1089389
Title:
juju bootstrap fail behind a proxy when a gpg key must be
Public bug reported:
According to --help:
-m, --massive-debug Print a lot of debug information to the command
line
Now, perhaps my understanding of the words "massive" and "debug" are
flawed, but the output I get while trying to debug failure to add a PPA
is neither massive, nor really
Also, yes, I get that this is a nit-pick and that there's a history
there, this is more a wishlist thing because it's a usability issue.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
-h is a fairly common shortcut for --help.
reboot, however, reboots the machine when one issues the command:
reboot -h
Now looking at the man page, there is an entry for --halt and --help,
but NOTHING for -h at all.
reboot should return the same as --help when -h is
Public bug reported:
fwupd is the closest we have to a standard mechanism currently for doing
in-band firmware updates in a vendor agnostic way. As long as the
vendors provide firmware blobs in an appropriately formatted package,
fwupd (or fwupdate) can install those firmware blobs from within
@Steve, I don't disagree, and I've already merged a patch to fix that
issue in the cert suite.
For context, what happens isn't a test case, but a resource that
enumerates the binaries in the system so that the suite can validate
requirements for executing the tests.
e.g., it enumerates a list
Public bug reported:
add-apt-repository says to hit ctrl-c to cancel adding a PPA. Then it
tracebacks when you do:
ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next
This PPA holds new upstream development releases, usually development
releases. Currently, it is holding the 2.2 series.
This also affects Xenial. Plugging a keyboard directly into a system
running Ubuntu Server 16.04.2 with the 4.8 kernel (and 4.10) fails to
illuminate the Caps Lock light on any USB keyboards tried, but the
actual function of the key works.
--
You received this bug notification because you are a
Note that the udev package seems to be looking for /sys/class/net/eth*
On my z/KVM instance, eth* do not exist, rather the dev is enc*:
ubuntu@s1lp9g003:~$ ls /sys/class/net/
enc4 lo
Likewise, on z/VM, the device is also enc*:
ubuntu@hwe0008:~$ ls /sys/class/net
enc600 lo
Interestingly
Public bug reported:
I'm attempting to install some cert tools on a z/KVM instance of Zesty.
This is failing because udev exits with an error during installation.
The apt logs show this:
Setting up udev (232-21ubuntu3) ...
addgroup: The group `input' already exists as a system group. Exiting.
Looks to me like I have the same version you do, and Python3 IS compiled
in.
bladernr@galactica:~$ vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28)
Included patches: 1-1689
Modified by pkg-vim-maintain...@lists.alioth.debian.org
Compiled by
Gonna set this to invalid. After the third or fourth reboot, NM started
loading on it's own and I no longer needed to manually do so. I don't
know why, but I'm unable to recreate the original fail state now :(
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Invalid
--
You
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650573/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "PciNetwork.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650580/+files/PciNetwork.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "nmcli-con.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650584/+files/nmcli-con.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650570/+files/IpAddr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "NetDevice.wlp3s0.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650578/+files/NetDevice.wlp3s0.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
apport information
** Attachment added: "NetDevice.tun0.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650575/+files/NetDevice.tun0.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650583/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "NetDevice.lo.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650574/+files/NetDevice.lo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650581/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "NetDevice.virbr0-nic.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650577/+files/NetDevice.virbr0-nic.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650582/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650572/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650569/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "NetworkManager.conf.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650579/+files/NetworkManager.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager
apport information
** Attachment added: "nmcli-dev.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650585/+files/nmcli-dev.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "NetDevice.virbr0.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650576/+files/NetDevice.virbr0.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
apport information
** Attachment added: "IpRoute.txt"
https://bugs.launchpad.net/bugs/1576364/+attachment/4650571/+files/IpRoute.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
Running Xenial on a Macbook Air. This was running Wily and was upgraded
to Xenial using do-release-upgrade. Network Manager works, and can
manage NICs, WiFI and VPNs that I have configured, however, the
Public bug reported:
Running Xenial on a Macbook Air. This was running Wily and was upgraded
to Xenial using do-release-upgrade. Network Manager works, and can
manage NICs, WiFI and VPNs that I have configured, however, the service
no longer starts on boot like it did under Wily and like it
et viola, it's working.
Still, no idea where that second, edited version came from :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1547585
Title:
Pulseaudio stopped
H... ok. I didn't realize there was a second pulseaudio config.
I have no idea how it got there, nor where it came from, and I do not
recall ever setting it, but sure enough:
### Make some devices default
#set-default-sink output
set-default-source 2
set-source-mute 2 0
So this is likely
On Tue, Mar 1, 2016 at 8:10 AM, David Henningsson
<1547...@bugs.launchpad.net> wrote:
> You haven't changed any configuration files (e g such as
> /etc/pulse/default.pa ) so they now reference a hard-coded "source #2",
> have you?
I have only changed the autospawn line in /etc/pulse/client.conf:
** Summary changed:
- Pulseaudio stopped working but sound still comes out LOUDLY
+ Pulseaudio stopped working but sound still works at the low level (can be
controlled with alsamixer)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Syslog is flooded with this series of messages
Feb 19 11:42:07 galactica pulseaudio[22209]: [pulseaudio] main.c: Source 2 does
not exist.
Feb 19 11:42:07 galactica pulseaudio[22209]: [pulseaudio] main.c: No sink found
by this name or index.
Feb 19 11:42:07 galactica pulseaudio[22209]:
This may be related to bug #1547589
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1547585
Title:
Pulseaudio stopped working but sound still comes out LOUDLY
Status
I AM able to control sound levels with alsamixer directly, FWIW.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1547585
Title:
Pulseaudio stopped working but sound
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Critical
** Changed in: pulseaudio (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Public bug reported:
After updating packages, I rebooted the system to load the new libc. ON
reboot I discovered after login that I was unable to connect any
configured VPNs because NetworkManager showed no VPNs.
I eventually figured out that clicking "Enable Networking" to disable
and
Public bug reported:
Not sure if it was an update or what that broke, but I suddenly have no
ability to control sound.
Sound settings no longer show any output devices and syslog is flooded
with pulseaudio messages.
Haven't tried a reboot, that's next.
ProblemType: Bug
DistroRelease: Ubuntu
Public bug reported:
rtkit is flooding syslog with the following:
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for
user '1000', denying request.
Feb 19 11:42:07
Rebooted system and still no audio devices, but I am listening to a
video play RIGHT NOW, despite the fact that pulseaudio thinks I have no
audio devices now.
This was working until I did a dist-upgrade earlier (maybe yesterday or
today).
--
You received this bug notification because you are a
Public bug reported:
Whenever I run ubuntu-bug on this newly installed and updated Xenial
destktop system, I get the following PyGIWarning messages dumped to
console:
bladernr@critical-maas:~$ ubuntu-bug apport
sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use
Thanks for that explanation Pitti! THat makes sense now that I've read
the thread.
I wouldn't suggest making changes here for the sake of convenience, I
also admit that I am a special corner case in this matter.
Would it be a safe assumption that if I can decipher how to write a udev
rule for
More checking... on Trusty, the file is generated by
/lib/udev/write_net_rules:
bladernr@sulaco:~$ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
And checking
Public bug reported:
Fresh install of Xenial on an intel NUC with 1 onboard GigE and one USB
GigE NIC.
I was setting up networking for MAAS and discovered that the device
names were ridiculous:
bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr
eno1 Link encap:Ethernet HWaddr
Hrmm... frustratingly, it's been changed automatically at boot somehow:
[5.389985] e1000e :00:19.0 eno1: renamed from eth0
[8.689549] asix 2-1.5:1.0 enx8cae4cff4099: renamed from eth0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
Attempting to upgrade a fully updated 14.04.3 system to Xenial using the
do-release-upgrade tool.
The upgrade proceeds until it attempts to install fontconfig. This
fails and causes a cascading set of failures for 160+ more packages
resulting in a system that boots, and has
Hi,
Not sure this is still an issue, Stephane informed me that those tests
are not meant to be run stand alone and could fail in spectacular ways
when run outside of autopkgtest.
if this is not the case, let me know and when I'm home next week,
I'll dig into this further... otherwise, you can
Public bug reported:
I have VPNs configured in Network Manager, one of which is a default
work VPN. That VPN is configured to connect whenever the network
connection is active on my desktop, thus every time I reboot, the
connection for eth0 is active and the VPN connects automatically.
I've
Public bug reported:
on a default 15.10 installation, I have installed lxc-tests and am
running through them individually.
lxc-test-checkpoint-restore fails to run because the package criu is not
installed
ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
/usr/bin/lxc-test-checkpoint-restore:
Public bug reported:
Ran the ste lxc-test-checkpoint-restore and that failed, but there is no
explanation in the output as to why it failed. All the output I was
able to create says it created the container fine, but then just failed
for some reason:
I: Configuring libsemanage1:amd64...
I:
Public bug reported:
I ran lxc-test-checkpoint-restore and it failed. So I decided to try
one additional attempt to verify the failure. However now I am unable
to re-run the test because apparently the container already exists
(previous test did not clean up after itself), however, lxc list
Public bug reported:
I'm investigating lxc-tests and have very little idea what they actually
do. I had hoped to read a man page, or even just pass --help to them to
get some idea of what each is actually doing.
For example, lxc-test-apparmor, I know it does something with apparmor,
but no idea
Thanks for the pointers... I think this is not an apport bug after all,
but one in xdg?
I have Google Chrome set as the default browser. When I launch via xdg-
open:
xdg-open http://bugs.launchpad.net
It returns the line "Created new window in existing browser session."
ANd it opens a new
Accidentally added the Ubuntu apport package... apparently xdg-utils
doesn't track bugs here... now what?
** Also affects: apport
Importance: Undecided
Status: New
** No longer affects: apport (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
When you want to update just a specific package, you can do the
following:
apt-get install $PACKAGE
and if $PACKAGE is installed, apt will update it to the latest available
version in the repos.
If you want to update an entire system, you can do:
upgrade to upgrade all
Can someone please close this bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/401823
Title:
Gdk-WARNING **: XID collision, trouble ahead
Status in Chromium Browser:
Daniel, can you please hand this off?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1134069
Title:
[HP Envy 4 Sleekbook] external audio jacks are reversed
Status in
77 matches
Mail list logo
