** Attachment added: "Output of networkd-test.py"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759255/+files/networkd-test.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Attachment added: "Journal of systemd while running the test"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759257/+files/systemd.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Attachment added: "Log of the DNS resolving dnsmasq while running the test"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759256/+files/dnsmasq-vpn.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 2054716 ***
https://bugs.launchpad.net/bugs/2054716
Public bug reported:
Errors were encountered while processing:
polkitd
colord
update-manager
pkexec
gamemode-daemon
fprintd
gnome-initial-setup
gdm3
packagekit
update-notifier
modemmanager
Sounds like some interaction issue between the system, systemd, and
dnsmasq somehow. As this fails on and off since a very long time. When I
test with the older dnsmasq and getting a success the time spent on the
test seems overly long. Like there is something not quite right even
then.
** Also
Public bug reported:
Investigations done in 22.04/Jammy but may be affecting other series,
too.
The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to
2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue
reported in bug #1957086. Sounds like both have interaction
I was going over the ADT results for the complete linux suite:
https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/amd64/l/linux/20231002_144159_55314@/log.gz (6.5.0-7.7)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
9017s 12:26:37 DEBUG| [stdout] # PASS: neigh get
9018s 12:26:38 DEBUG| [stdout] # PASS: bridge_parent_id
9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto"
is a garbage.
9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or
Public bug reported:
This might be apparmor, the test case, kernel or anything in between:
7720s running attach_disconnected
7720s Fatal Error (unix_fd_server): Unable to run test sub-executable
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
--
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/2031352
Title:
Nouveau driver crash - Ubuntu 22.04.3
@juergh, we tested your kernel on one of our notebooks where the problem
occurred. Shut down and reboot hasn't shown this behaviour, yet.
Looks promising!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
A few of my colleagues are also affected with 6.2.
This is really a bad situation.
As workaround we stepped back to linux-oem-22.04c (6.1) which works
without problems.
[1.545289] VGA switcheroo: detected Optimus DSM method \_SB_.PC00.PEG1.PEGP
handle
[1.545290] nouveau: detected PR
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1837227
Title:
systemd mount units fail
Oh, sorry, I missed that. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2025650
Title:
package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
Public bug reported:
On every boot, multiple times
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
NonfreeKernelModules:
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
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/2016908
Title:
udev fails to make prctl()
Thanks to Massimiliano's lead. I was able to workaround this bug by
replacing /usr/bin/omshell with a freshly compiled version from source.
Note that I've only been using my custom version for about 20 minutes,
so YMMV.
I really dislike replacing packages with homemade utilities, as it's a
pain
> Could somebody confirm if this issue is still happening with omshell
v4.4.3 from the Ubuntu Kinetic package?
Unfortunately, the package requires a new version of libc. It's not a
simple upgrade.
```
# apt list --upgradable
Listing... Done
isc-dhcp-server/kinetic 4.4.3-2ubuntu4 amd64
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: apparmor (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Lunar)
Importance:
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Verified Oracle image build by building Jammy image using livecd-rootfs
from source (https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.765.13). I checked that fwupd was still installed (required for
Oracle bare-metal), and the modemmanager and udisk2 are not installed.
I won't change the
I can replicate this on my Dell XPS13 9380 (no encryption). Occurs as well with
Ubuntu 20.04 LTS, but not with 18.04 LTS, so not sure if it is related to the
same reason?
-> Disabling Secure Boot and SGX did not resolve the issue
--
You received this bug notification because you are a member
To me it looks like the boot-and-services sub-tests got a lot less
reliable on armhf in Focal. The previous systemd version had a higher
chance of passing those. There always was root-unittests which required
multiple attempts. But now from about 10 attempts there was one which
had root-unittests
Public bug reported:
This is a scripted bug report about ADT failures while running systemd
tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Testing failed on:
armhf:
> Could this be a related issue, when deployment to aks fails, due to a
connection refused when pulling images from azure container
registry(ImagePullBackOff).
I you look closer at the message accompanying the ImagePullBackOff, you should
see something like:
dial tcp: lookup
With the revert, the network-manager ADT tests work again.
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/n/network-manager/20220505_053118_fb2db@/log.gz
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1971418
Title:
mmy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notif
This seems to be related to: "rfkill: make new event layout opt-in" in
the -28 kernel. When I revert that a local reproduction run starts to
work again. However I never got the same error pattern as in the ADT
logs (those seem to get random data back from trying to read the MAC
address). So a
Public bug reported:
This is a scripted bug report about ADT failures while running network-
manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by
the dep8 tests of the tested source or the kernel has yet to be
determined.
Testing failed on:
amd64:
Turns out that is a SUT which does not get freshly provisioned and had
proposed enabled. And there is a newer lxc in proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
>From ADT testing: https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/arm64/s/systemd/20220310_155736_6a08c@/log.gz
This was previously failing the storage subtest.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug
@jdstran The fix of Debian doesn't help. I use fail2ban too. But if
fail2ban.service is disabled and masked then the issue still happens.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Running "/usr/bin/sleep 10 && /usr/sbin/ufw enable" via cron works for
me
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1726856
Title:
ufw does not start automatically at
Im using Ubuntu 20.04 by the way.
To make clear what I meant: I think the dependencies aren't defined
right such that some services are starting to early.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
I have the same issue on an computer with NVME. Maybe the boot is too
fast? The fix and all workarounds (cron) haven't helped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Public bug reported:
The debian package for the features2d module (libopencv-features2d4.2
4.2.0+dfsg-5) on Ubuntu 20.04 has a dependency on the highgui module which is
only a debug dependency and should not be a dependency of the release binary.
This dependency indirectly adds dependencies on
Looks like the reinstall with the system helpers did the trick. The
package now installed and seems to work as intended.
I did some cleaning and I don't have any package problems hanging around
any more. So I would think it is a solved problem now.
Thank you for the support.
Den 2021-06-23 kl.
Just as a heads up: The upstream stable update 5.11.20 for hirsute un-reverts
- "s390/cio: remove pm support from ccw bus driver"
and adds
- "s390/cio: remove invalid condition on IO_SCH_UNREG"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: linux (Ubuntu Hirsute)
Status: Triaged => Fix Committed
--
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/1925211
Title:
Hot-unplug of disks leaves
apt-get -y install alsa-tools
cat > /lib/firmware/hda-jack-retask.fw << 'EOFFW'
[codec]
0x10ec0235 0x17aa3826 0
[pincfg]
0x17 0x90170111
[verb]
0x01 0x0716 0x04
0x01 0x0717 0x04
0x01 0x0715 0x04
EOFFW
cat > /etc/modprobe.d/hda-jack-retask.conf << 'EOFCONF'
options snd-hda-intel power_save=0
Thanks Christian, I think we would for now mark this up as known issue
in lxc. There is a bit of a mystery on our side as it seems right now as
if this failed for couple of our releases and never appears to have been
investigated/asked.
--
You received this bug notification because you are a
Public bug reported:
We seem to get failed dep8 testing on lxc in Groovy for a while. What we
are interested in is knowing whether this is known problems in the
testing or something that waits on kernel fixes (who would be driving
those if this is the case).
Testing failed on:
amd64:
Same problem:
- Kernel: 5.8.0-41-generic
- OS: Ubuntu 20.04.02 LTS
- Headset: Sennheiser MB Pro 2
I can switch to HSP but even audio output won't work at all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
Updating the proposed change. This addresses the following:
- Only run from the trigger stage when called from dpkg
- Pass the same environmental flag as update-initramfs does
(in theory there never should be need to generate an initrd)
- Handle special case of installkernel called multiple
** Description changed:
[Availability]
libbpf | 0.1.0-1 | groovy/universe | source
libbpf | 0.3-2 | hirsute/universe | source
[Rationale]
Libbpf is (or is about to become) a dependency for building iproute2 which
already is in main. Using BPF is becoming more wide-spread. The
** Description changed:
[Availability]
libbpf | 0.1.0-1 | groovy/universe | source
libbpf | 0.3-2 | hirsute/universe | source
[Rationale]
Libbpf is (or is about to become) a dependency for building iproute2 which
already is in main. Using BPF is becoming more wide-spread. The
** Description changed:
[Availability]
libbpf | 0.1.0-1 | groovy/universe | source
libbpf | 0.3-2 | hirsute/universe | source
[Rationale]
Libbpf is (or is about to become) a dependency for building iproute2 which
already is in main. Using BPF is becoming more wide-spread. The
** Description changed:
- [MIR] libbpf (dependency of iproute2)
+ [Availability]
+ libbpf | 0.1.0-1 | groovy/universe | source
+ libbpf | 0.3-2 | hirsute/universe | source
+
+ [Rationale]
+ Libbpf is (or is about to become) a dependency for building iproute2 which
already is in main. Using
01 00 00 48 8b 76 10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c
c2 84 c9 0f 84 c7 02 00 00 <49> 83 39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed
01 49 8d 74 1d
Looking forward for a fix.
Thank you.
Stefan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
m
** Changed in: linux-base (Ubuntu)
Status: New => In Progress
** Changed in: linux-base (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Could someone try to put the attached script into /etc/kernel/postinst.d
and let me know whether that make installkernel work? Thanks.
** Attachment added: "Copy to /etc/kernel/postinst.d/xx-update-initrd-links"
Thanks for fixing this!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1576454
Title:
Superfluous Xsession.d script: 60x11-common_localhost
Status in xorg package in
Attached a patch against https://salsa.debian.org/xorg-
team/xorg/-/tree/ubuntu; not sure if this is the right repo, but it does
have the offending change/file.
** Patch added:
"0001-Revert-Seems-when-this-was-renamed-it-fell-out-of-gi.patch"
... or maybe not, since I don't see the file in the Debian git repo
(from the Vcs-Git field in from debian/control from the Ubuntu source):
https://salsa.debian.org/xorg-team/xorg/-/tree/debian-
unstable/debian/local/Xsession.d
--
You received this bug notification because you are a member of
I think both files come from Debian. I did an 'apt-get source
x11-common' and I see that debian/x11-common.install installs stuff from
debian/local/Xsession.d. I see both files there:
stefan@spuiu-vm:~/src/ubuntu/xorg-7.7+19ubuntu14$ grep -rn xhost
debian/local/Xsession.d/
debian/local
scripts who end up calling xhost like this,
with slightly different tweaks:
stefan@spuiu-vm:~$ grep -rn xhost /etc/X11/Xsession.d/
/etc/X11/Xsession.d/35x11-common_xhost-local:3:# If xhost (from
x11-xserver-utils) is installed, use it to give access
/etc/X11/Xsession.d/35x11-common_xhost-local:5
Public bug reported:
My laptop detected this problem, so i reported it
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgpgme11:amd64 1.13.1-7ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18
Uname: Linux 5.3.0-64-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.9
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200918_144021_ce0b3@/log.gz
The failed test is: FAIL: lxc-tests: lxc-test-device-add-remove (0s)
---
Adding
Public bug reported:
Using network printers with samba authentication on Ubuntu 20.04 the
authentication dialog is shown only a very short time and closes
unexpectedly. But authentication works with noninteractive
authentication using specifying username and password as part of the
samba address.
The ADT failures related to lubreswan and ubuntu-fan were resolved by
re-try. The systemd test fails somewhere in the upstream test but does
not give any hints about which part of that section was considered a
failure. The amd64 re-try has now succeeded and from the timing it feels
like the
Test build of proposed change at:
https://launchpad.net/~smb/+archive/ubuntu/bionic
** Merge proposal linked:
https://code.launchpad.net/~smb/ubuntu/+source/iproute2/+git/iproute2/+merge/387837
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Description changed:
+ [SRU Justification]
+
+ Impact: The tc command does not show the correct values for tcp_flags
+ (and ip_tos) on filter rules. This might break other scripts parsing
+ that output but at least confuses users.
+
+ Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr
Oh, so the upstream patch had the test case all the time and I just
blanked it, looking at the content there and visible comments in this
bug report only. :/ Thanks for the pointer. That should be all needed
and I can go on with the SRU process.
** Changed in: iproute2 (Ubuntu Bionic)
Sorry this seems to have gotten list in translation. I already got the
one patch fixed up. What I need is some generic instructions to check
the result. Can one just use any pair of NICs or do they have to be
special?
--
You received this bug notification because you are a member of Ubuntu
Touch
I would like to verify any changes before moving ahead with SRU. But the
given instructions are incomplete or at least not generically usable.
Could the instructions be updated with steps that can be performed in a
generic VM.
--
You received this bug notification because you are a member of
I believe the mention pre-req patch is actually wrong (or not quite the
patch we would be looking for). Instead
commit 6e8634eb13f30c58d1e28d975d99509680e1abc3
Author: Roman Mashak
Date: Thu Mar 29 18:12:35 2018 -0400
tc: add oneline mode
Add initial support for oneline mode in
** Changed in: iproute2 (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: iproute2 (Ubuntu Bionic)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Public bug reported:
The version 2.9.1 (packaged for Ubuntu 20.04) suffers from a bug that
prevents the playback of AAC with Parametric Stereo (PS). The related
change has been reverted in 2.9.2 to fix this:
https://github.com/knik0/faad2/pull/51
So it would be great if this patch could be
Big thanks guys!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1659534
Title:
userdel doesn't supports extrausers
Status in Snappy:
Fix Released
Status in shadow
It's the same on Ubuntu 18.04.
$ LANG=C apt-cache policy software-properties-gtk
software-properties-gtk:
Installed: 0.96.24.32.12
Candidate: 0.96.24.32.12
Version table:
*** 0.96.24.32.12 500
500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500
Public bug reported:
~$ sudo apt upgrade
[sudo] password for stepan:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
google-chrome-stable kmod libkmod2 libvirt0 linux-firmware
Please have a look at the upstream bug:
https://github.com/lathiat/avahi/issues/117
** Bug watch added: github.com/lathiat/avahi/issues #117
https://github.com/lathiat/avahi/issues/117
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I can confirm that there seems to be a regression in the alsa audio
driver. I was trying this soundcard directly with alsa and get
distoreted audio and rumble in *some* apps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Confirmed to be fixed. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1862169
Title:
rhythmbox crashed with SIGSEGV in build_flavored_key()
Status in
I tried it, however, no sound from my subwoofer.
During a sound check, just a very faint swoosh can be heared.
Nevertheless - nice try! Thank you!
regards,
HSS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
Public bug reported:
What I expected to happen:
When exiting from virtual terminal I expected to get back to gnome session with
working keyboard and mouse.
What happened instead:
When exiting from virtual terminal I was switched automatically back to
(locked) gnome session and keyboard and
In the appendix, an image of the screen in which the PC's crotch hangs.
I hope, this might be helpfull.
Thank you
On 16.11.19 22:48, Sebastien Bacher wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we cannot work on this bug because
Public bug reported:
only to start via secured mode
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
Uname: Linux 3.13.0-92-generic i686
.tmp.unity_support_test.1:
ApportVersion: 2.20.9-0ubuntu7.9
It's mainly about new features, so this isn't urgent.
In general I think there should be some kind of process that makes
sure certain packages are kept in sync with the kernel version.
It's not as strict as with the linux-tools packages, but some kind
of coordination with the kernel team would
Public bug reported:
As eoan will ship a 5.3 kernel it needs iproute v5.3.0.
There are important updates, e.g. to the 'rdma' command
which are needed in order to activate certain kernel features.
** Affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
--
You received
Public bug reported:
While restarting systemd-jounald, the following error message occurs:
systemd-journald[28007]: Assertion 'f' failed at ../src/journal/journal-
file.c:143, function journal_file_close(). Aborting.
release: Ubuntu 16.04.5 LTS
systemd version: 229-4ubuntu21.22
This issue is
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Stefan Bader (smb)
--
You received this bug notification be
** Description changed:
+ [SRU Justification]
+
+ == Impact ==
+ The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
+ side of the implementation.
+
+ == Fix ==
+ Backported a patch
I'm on ubuntu 18.10 and I get random drops but if I disconnect and
reconnect from the UI, it works. This isn't happening on my laptop which
runs 18.04 also on cable connection.
-network
description: Ethernet interface
product: I211 Gigabit Network Connection
** Changed in: iproute2 (Ubuntu)
Status: New => Invalid
** Changed in: iproute2 (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: iproute2 (Ubuntu Xenial)
Status: New => In Progress
** Changed in: iproute2 (Ubuntu Xenial)
Assignee: (unassigned) =>
Public bug reported:
If you position the mouse corsor on the edge of Dock and scroll, you can
switch the workspace, which behaves equivalent to the scrolling on the
"Show Applications" button in the corner.
I've reproduced it on other Ubuntu 18 installations of friends (all 3 I
tested, at least
** No longer affects: alsa-lib (Ubuntu Cosmic)
** Also affects: alsa-lib (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Cosmic)
Importance: Undecided
@Stéphane, isn't that the way Britney works? There will always be one
package from proposed which is triggering ADT and the rest is non-
proposed. Or was there more than one?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
In it's current version (systemd-229-4ubuntu21.9) it seems to be made
worse.
Files in /var/run/ will get `Too many levels of symbolic links` files in
/run/ will still get `fchownat() of /run/... failed: Invalid argument`
root@sandres-test-systemd:/usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug
** Changed in: snappy
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1659534
Title:
userdel doesn't supports extrausers
Status in Snappy:
Any updates on this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1659534
Title:
userdel doesn't supports extrausers
Status in Snappy:
New
Status in shadow package in
Public bug reported:
This is just a minor mistake, but still worth correcting, I think.
In the man page for tar_1.29b-2_amd64 and also tar_1.30+dfsg-2_amd64,
the first command demonstrating the option styles is
tar cfv a.tar /etc
which creates the archive a.tar. In the text, however, it is
** Summary changed:
- mistake in the man page
+ Inconsistency in the man page regarding created archive file
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1796900
Title:
I have the same issue on a normal (non-desktop) Ubuntu 18.04 running
XMonad with Gnome and using the gnome-shell.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1553466
Title:
I did prepare some slightly modified proposal for this and will try to
get things progressing tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1786574
Title:
remove
I did prepare some slightly modified proposal for this and will try to
get things progressing tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1786574
Title:
remove
** No longer affects: linux (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** No longer affects: systemd
Fix proposal submitted upstream: https://marc.info/?l=linux-
netdev=153546645305223=2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1789431
Title:
ip rule show has
1 - 100 of 450 matches
Mail list logo
