** Also affects: network-manager (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux
How to get the fix installed via apt?. any link..?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1794629
Title:
CVE-2018-15473 - User enumeration vulnerability
Status
I tried the same while blacklisting nouveau driver in grub:
$ cat /proc/cmdline
BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet
splash modprobe.blacklist=nouveau ---
This time, I have "acpi_video0" in /sys/class/backlight, but the result
is the same. The screen is
Do you encounter audio stuttering in any other apps?
** Package changed: alsa-driver (Ubuntu) => quodlibet (Ubuntu)
** Changed in: quodlibet (Ubuntu)
Status: New => Incomplete
** Summary changed:
- [wma codec problem, playback] Playback problem
+ Audio sometimes stutters in Quod Libet
If the problem is the kernel version then please try to find the closest
two versions where one works and the other does not, from this list:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
Derek, are you saying kernel 4.18 (or earlier) does not have the bug?
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
I think we should work on releasing the gnome-bluetooth fix for bug
1773897 before assessing whether or not this is a different issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Please run these commands:
1. apport-collect 1821904
2. dpkg -l > allpackages.txt
and then attach the file 'allpackages.txt' to this bug.
** Tags added: disco
** Package changed: gnome-shell (Ubuntu) => pulseaudio (Ubuntu)
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
Xubuntu daily images are still missing the fix for bug 1819943. So
please wait until a newer image is available which includes that fix
before retesting.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
You have been subscribed to a public bug:
On Disco, Gnome Shell always starts muted.
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: disco
--
Gnome Shell always started muted on Disco
https://bugs.launchpad.net/bugs/1821904
You received this bug
I added apport for the python2 -> python3 bug.
Thanks
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
stranger and stranger .. if you install kernel 5.0.0-8.9 at the first
boot into any new install partition before changing any thing else .. it
does not fix the issue .. once you return sda1 to being grub master ..
neither sda7 nor sda6 will keep lightdm running ..both briefly flash
lightdm login
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1821609
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
okay still bug present in xubuntu-disco-amd64-desktop-beta.. still uses
kernel 5.0.0-7
updating from proposed with kernel 5.0.0-8.9 it works properly
i.e. any linux os partion can be used to install grub and another partion with
linux can be
selected and boot normally
e.g. beta install is
** This bug is no longer a duplicate of bug 1819943
intel video driver not installed by default in ubuntu 19.04 (Disco) [needed
for graphics support on Intel Core 2 Duo systems]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Apologies my first run of apport was mainline 5.0. I immediately
rebooted and use a standard default kernel for 18.04. I deleted both
mainlines since they didn't solve my issue anyway.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1821936
Title:
ALC274 unsupported
Status in
** Changed in: lxd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1813622
Title:
systemd-resolved, systemd-networkd and
Verified 239-7ubuntu10.11 on Cosmic:
test@test-Standard-PC-i440FX-PIIX-1996:~$ systemd-detect-virt --container
none
test@test-Standard-PC-i440FX-PIIX-1996:~$ echo $?
1
test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l systemd | cat
Desired=Unknown/Install/Remove/Purge/Hold
|
Verified 239-7ubuntu10.11 on Cosmic:
...
ubuntu@DESKTOP-V4DDKSS:~$ dpkg -l systemd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Public bug reported:
The song Waterloo of ABBA plays correct with
Windows Media Audio 9.1, VBR Quality 50, 44 kHz, stereo 1-pass VBR, but it
stutters badly with
Windows Media Audio 9.2, VBR Quality 50, 44 kHz, stereo 1-pass VBR
I use Quod Libet as audio payer.
The song plays for one second,
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1821822
Title:
Temporary failure in name resolution in Python 3.7.2
Status in
So, I'm reassigning this bug to qt5webkit, thank you Gianfranco for
investigating the issue. That was very obscure!
I'll take care of closing this bug once somebody merges in the new
qt5webkit version (which may be for disco+1)
** Package changed: sigil (Ubuntu) => qtwebkit-opensource-src
I just did the qt5webkit merge for disco, lets close directly.
Of course I don't plan to SRU for bionic or cosmic or whatever, because it is
just a cosmetic error
(I mean, the PNG bad files should have been around since the begin, just later
libpng versions are becoming pickier about them)
**
Verified 229-4ubuntu21.19 on Xenial:
# systemd-detect-virt --container
wsl
...
root@x-uu-upgrade:~# systemd-detect-virt
lxc
oot@x-uu-upgrade:~# dpkg -l systemd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/
You have been subscribed to a public bug:
When sigil is started, it prints the following warning twice to stderr:
Warning: libpng warning: iCCP: known incorrect sRGB profile
This may be symptomatic of a deeper issue.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: sigil 0.9.9+dfsg-1
Verified 237-3ubuntu10.17 on Bionic:
...
[K]0;ubuntu@DESKTOP-V4DDKSS:
~[01;32mubuntu@DESKTOP-V4DDKSS[00m:[01;34m~[00m$ systemd-detect-virt
--container
wsl
...
...
root@bb-ua:~# dpkg -l systemd | cat
Desired=Unknown/Install/Remove/Purge/Hold
|
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Critical
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1821936
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1821936
Title:
ALC274 unsupported
Status
Cleaning up by marking fixed.
** Changed in: software-properties
Status: New => Fix Released
--
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/1307170
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1821939
Title:
package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.8
ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Mar 27
Public bug reported:
I find this to be an issue with current LTS 18.04's latest 4.19 kernel.
I tested this on mainline 4.20 and 5.0 kernels as well.
No audio because ALC274 not properly loaded for use, so no audio output.
A related card had a similar bug, which was fixed, and may be of use in
I have also this pb. It seems gpg cannot handle more than
/etc/apt/trusted.gpg (one keyring) + 39 keyrings in
/etc/apt/trusted.gpg.d/ : https://lists.gnupg.org/pipermail/gnupg-
users/2013-December/048571.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Jamie said that he'd pull in the postinst snippet and include that
change in an upload that he's already preparing.
** Changed in: apparmor (Ubuntu)
Status: New => In Progress
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received
** Attachment added: "HCI trace captured by btmon"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1821929/+attachment/5249821/+files/hcitrace.snoop
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
I recently bought not expensive wireless mouse with bluetooth support:
https://www.aliexpress.com/item/Wireless-Mouse-Bluetooth-Mouse-Silent-Computer-Mouse-PC-Mause-Wireless-Rechargeable-Ergonomic-Optical-USB-Mice-2/32879862474.html?spm=a2g0s.12269583.0.0.36ab310dUGrVZS
I
It looks like the change mentioned in the above comment came from
Debian. Here's the commit:
https://salsa.debian.org/apparmor-
team/apparmor/commit/dc14f24b2c2943c29d0368f913020f1307d8f1d3
They obviously don't have so they
opted to remove that logic from the postinst. I think we should have
If it's intermittent at least what evidence points to fwupd? Is it the
last thing seen in a log somewhere?
Ideally please leave verbose logging turned on in fwipd systemd unit and
leave it enabled. When this repros again we can see the logs.
--
You received this bug notification because you are
This seems intermittent for me. I admit I don't reboot often but I've
been unable to reproduce it, even with leaving fwupd enabled.
--
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)
Status: Incomplete => 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/1818204
Title:
Qualcomm Atheros QCA9377
This failure was noticed by the kernel team as it makes the kernel
autopkgtests to fail while running QRT's test-apparmor.py.
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I see this change in the debdiff from the last apparmor upload to what's
currently in proposed:
diff -Nru apparmor-2.12/debian/apparmor-profiles.postinst
apparmor-2.13.2/debian/apparmor-profiles.postinst
--- apparmor-2.12/debian/apparmor-profiles.postinst 2018-03-22
20:19:58.0 +
Public bug reported:
The apparmor-profiles binary package from apparmor 2.13.2-9ubuntu2 in
disco-proposed is not handling the chromium-browser profile and
abstraction correctly. It installs the profile but not the abstraction
which makes profile loading fail.
$ sudo apt install
*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943
addional clarification .. if sda6 (recovery booted or chrooted)
installed grub then sda6 boots with some brief flashing normally. if
sda7 or sda1 (recovery booted or chrooted or a normal boot for sda1)
@Brian
Now the disco fix is in both cosmic and bionic queues.
please accept them :)
I checked if wl-asneeded was removed from rules, if the patch was added, and
also the upgrade path for versioning was correct for bionic->cosmic->disco
please double check! I also fixed the description
**
*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943
this effected only the more recent installs
you have miss understood the details in the initial report .. the system
would boot normally as long as the grub used (installed) was from the
install partition
libunistring backport patch to cosmic from Disco:
diff -Nru libunistring-0.9.10/debian/changelog
libunistring-0.9.10/debian/changelog
--- libunistring-0.9.10/debian/changelog2018-07-23 16:46:28.0
+0200
+++ libunistring-0.9.10/debian/changelog2019-03-27 12:21:30.0
Ok Brian, so lets backport the fix from 19.04 and fix also 18.10
** Also affects: libidn (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: libunistring (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: libunistring (Ubuntu Cosmic)
*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943
** Summary changed:
- lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870
--
You
@Till
I do not see it crashing:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432#note_475636
--
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/1810316
Public bug reported:
Device: Dell Precision 7530
In the BIOS, the Switchable Graphics option is deactived, which means only the
nVidia GPU is used.
When booting 19.04 beta live USB, the screen becomes very dark and
brightness cannot be adjusted. (The same issue happens with 18.04.2)
There is
** Attachment added: "journalctl -b"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821867/+attachment/5249682/+files/journalctl-b.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
systemd-networkd.service is not active after reboot:
systemctl status systemd-networkd.service
systemd-networkd.service - Network Service ¬m
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled-runtime
¬m
Active: inactive (dead) ¬m
Docs:
@Ricardo: Yes, that was my intent with the original report. I didn't
even know about the other issue when I submitted this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
You have been subscribed to a public bug:
After doing a default disco installation on s390x using the beta ISO image aka
daily from March 26th and the post-install reboot the system restarts aka
reipls (in z/VM in this case) but the interface is not brought up.
Hence no remote connections are
Hi Mathieu, I don't think Cosmic or Disco systemd are affected. They are
both >= v239, and Cosmic behaved fine when verifying
https://bugs.launchpad.net/netplan/+bug/1776228.
It would just be a shame having the LTS release remain broken with DHCP
configurations, that used to work before.
--
You
Please backport this two MR:
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/13
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/14
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
Public bug reported:
After doing a default disco installation on s390x using the beta ISO image aka
daily from March 26th and the post-install reboot the system restarts aka
reipls (in z/VM in this case) but the interface is not brought up.
Hence no remote connections are possible.
The ip cmd
After looking a bit more into this, it seems the issue in
https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html is
maybe not a real security concern, since rbash was wrongly configured.
Having . in PATH is not good with rbash and that makes the whole thing
flawed. So, we could say
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Summary changed:
- Need to add Intel CML related pci-id's to the oem-kernel
+ Need to add Intel CML related pci-id's
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects:
** Description changed:
- I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac
- Wireless Network Adapter (rev 31).
+ === SRU Justification ===
+ [Impact]
+ Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked
+
+ [Fix]
+ The platform in question doesn't have hardware RF switch, so
66 matches
Mail list logo
