*** This bug is a duplicate of bug 1550779 ***
https://bugs.launchpad.net/bugs/1550779
** Summary changed:
- Xorg freeze
+ After I turn on the machine in the morning (probably from S3 sleep), it just
blinks the displays for a few moments, than it turns to black for seconds and
this is an
Public bug reported:
Hello there!
I have an HP 840 G5, with an external docking station (HP USB-C Dock G4). All
the input and output devices are connected to this docking station"
- display on Displayport (x2)
- ethernet
- keyboard
- mouse
After I turn on the machine in the morning (probably
It should be removed from all types eventually, this was a distro wide
change no an ISO specific change.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Re-new this bug for requesting above confirmation.
--
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/1844763
Title:
file /etc/network/interfaces is missing in
Hi Joshua,
Thanks for your reply.
Could you please confirm if all Ubuntu types uses Netplan from 19.10, I
noticed from 17.10 to 19.04, Desktop type has ifupdown, Server and Live
Server are using Netplan.
Thanks,
Pengpeng
** Changed in: network-manager (Ubuntu)
Status: Invalid => New
--
This looks like one or two bugs. And at least the first one is a kernel
bug so reassigning there...
https://launchpadlibrarian.net/446679771/gpf-amdpu
** Tags added: amdgpu
** Summary changed:
- Screen Glitching & Kernal Panic
+ [amdgpu] Screen Glitching & Kernel Panic
** Package changed:
Public bug reported:
I've recently updated to Eoan, but it seems like some nasty bugs came
with it, particularly from the amdgpu package.
It started with visual glitches but it would occasionally freeze the
screen with whatever playing in the background and require me to hard-
shutdown to
That *might* be a different bug. This bug is specifically about:
error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-
gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
If v5.4-rc3 doesn't work too, please upload a alsa-info.txt based on
v5.4-rc3.
thx.
--
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/1848070
Title:
[System Product
could you please test with latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc3/
--
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/1848070
A fix has landed in lxd, I refer you to the following comment:
https://github.com/lxc/lxd/issues/4656#issuecomment-541266681
Please check if this addresses the issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
https://github.com/mvo5/unattended-upgrades/pull/228
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => Low
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => In Progress
--
** Description changed:
+ [impact]
+
+ due to recent change to run armhf tests in nested lxd container,
+ autopkgtest for systemd on disco fails consistently.
+
+ [test case]
+
+ see test results, linked in original description below.
+
+ [regression potential]
+
+ very low, autopkgtest fix
sordna, regarding your specific problem, please file a bug against apport via a
terminal:
ubuntu-bug apport
In this new report, please copy/paste the reproduction steps, and result
as per terminal command.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Interactive use of python shouldn't invoke apport! On my 19.04 system
typing "foo" on the python3 interpreter ends up in this huge ugly mess
for no reason:
$ python3
Python 3.7.3 (default, Oct 7 2019, 12:56:13)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more
** Description changed:
+ [impact]
+
+ upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal
upload, because it added a check to verify the Content-Length header, but the
upload may use Transfer-Encoding of 'chunked' which does
+ not specify Content-Length.
+
+ [test
Reuploaded without the bug number reference now
--
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/1556439
Title:
pulseaudio crashed with SIGABRT in
Steve Langasek wrote:
> The root failure is:
> objcopy -O binary usr/klibc/syscalls/typesize.o
> usr/klibc/syscalls/typesize.bin
> mkdir -p usr/include/klibc/; perl /tmp/klibc-2.0.6/usr/klibc/syscalls.pl -2
> usr/klibc/syscalls/SYSCALLS.i
> /tmp/klibc-2.0.6/usr/klibc/arch/x86_64/sysstub.ph
> Based on
> https://salsa.debian.org/systemd-team/systemd/merge_requests/56#note_113429,
> is https://salsa.debian.org/systemd-team/systemd/merge_requests/55 suitable
> for the
> SRU workaround?
Have you actually tested this using an affected system? I'm concerned
that changing to use by-path
yeah ok just checked, that totally fixes it, have asked the systemd
maintainer if that patch can be included in the next update
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
*** This bug is a duplicate of bug 1775219 ***
https://bugs.launchpad.net/bugs/1775219
** This bug has been marked a duplicate of bug 1775219
incorrectly reports package as unsupported if apt cache is empty
--
You received this bug notification because you are a member of Ubuntu
Touch
It is a fresh installation and I didn’t run apt update.
I wanted to check if I can update it from Ubuntu Software (I had problems in
terminal), then I run into a problem there, and wanted to report it.
> On 14 Oct 2019, at 18:45, Brian Murray wrote:
>
> If this is a fresh install of Ubuntu
-- Forwarded message --
From: Adam Conrad
Message-ID:
<157106879908.15546.2658970073129703906.mal...@soybean.canonical.com>
2.0.7-1 fails to build in the same way on Ubuntu 19.10. I'm assuming
it's either glibc 2.30 (Debian is at 2.29) or linux 5.3 (Debian is at
5.2), with
@ddstreet
Based on https://salsa.debian.org/systemd-
team/systemd/merge_requests/56#note_113429, is https://salsa.debian.org
/systemd-team/systemd/merge_requests/55 suitable for the SRU workaround?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
After a while (after rebooting my computer), my sound output gets
distorted. When listening to music containing voice, it sounds like
voice is removed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu
Attaching my alsa-base.conf
** Attachment added: "Alsa config"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1848070/+attachment/5297125/+files/alsa-base.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
If this is a fresh install of Ubuntu have you run 'apt update'? If it is
not a fresh install what is the output of "apt-cache policy gnome-
software"?
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: evolution-data-server
Thank you for your bug report, it looks like a local corruption/download
error rather than a package bug though
** Changed in: evolution-data-server (Ubuntu)
Importance: Undecided => Low
** Changed in: evolution-data-server (Ubuntu)
Status: New => Invalid
--
You received this bug
s/D-Bus session/logind session/
--
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/1847896
Title:
Unable to shutdown or restart from log-in screen
Status in gnome-shell
** Package changed: ubuntu => apport (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1848063
Title:
Ubuntu Software in not considered as
It's the most reported 19.10 issue on e.u.c at the moment
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
You have been subscribed to a public bug:
I'm trying to report a bug about "Ubutnu Software", using ubuntu-bug.
When I click on it, the dialog "Problem in gnome-software" with content "The
problem cannot be reported: This is not an official Ubuntu package. Please
remove any third party package
I haven't tested this, but since seb128 pasted the relevant messages in
IRC.
I bet you that it's because polkit isn't considering the D-Bus session
of the greeter to be 'active', because it's not finding it.
If someone would like to test build a systemd with this commit included:
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu8, the problem page at
https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae
contains more
This bug was fixed in the package systemd - 242-7ubuntu3
---
systemd (242-7ubuntu3) eoan; urgency=medium
* Fix using domain set by DHCP as search domain (LP: #1846509)
File:
debian/patches/network-do-not-use-ordered_set_printf-for-DOMAINS-or-ROUT.patch
2.0.7-1 fails to build in the same way on Ubuntu 19.10. I'm assuming
it's either glibc 2.30 (Debian is at 2.29) or linux 5.3 (Debian is at
5.2), with the latter being more likely.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Same for me on Bionic.
Linux 4.15.0-65-generic x86_64
vainfo
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva error:
@Seb128,
Sorry to bother you again, but I've noticed some (at least for me) unexpected
fallout from this bug.
Using Xubuntu Eoan with 20.4-2ubuntu2 from proposed.
When connecting to my Wi-Fi network (which is set to WPA2/WPA3 mixed
mode) using NM-Applet (the GUI not NMTUI) it will show the
Thanks for the details, it doesn't seem a release blocker/target at this
point but might be a good update to get in a SRU. It would be nice if
the kernel team would look after things that should be upodated when a
kernel update land indeed
--
You received this bug notification because you are a
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
*** This bug is a duplicate of bug 1847815 ***
https://bugs.launchpad.net/bugs/1847815
** This bug has been marked a duplicate of bug 1847815
storage autopkgtest is flaky
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
# pkgs that are (for some reason) not safe to install
blacklist = get_blacklist()
logging.info(_("Initial blacklist : %s"),
" ".join(blacklist))
# install only these packages regardless of other upgrades available
whitelist =
Thank you for your bug report. Is there anything buggy/not working when
using the current 5.2 version on a 5.3 kernel? Or is that just that it's
not able to make use of some new kernel features?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
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
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Triaged
--
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/1847570
Title:
PulseAudio automatically switches
I'm using a Ubuntu 16.04.6 LTS version.
The xprop output is:
XdndAware(ATOM) = BITMAP
_NET_WM_ICON_GEOMETRY(CARDINAL) = 1925, 737, 54, 54
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_DESKTOP(CARDINAL) = 0
_NET_WM_STATE(ATOM) =
sudo ln -s source_linux.py /usr/share/apport/package-hooks/source_linux-oem.py
sudo ln -s source_linux.py
/usr/share/apport/package-hooks/source_linux-oem-osp1.py
Above commands would fix this issue. Judging from all other
source_linux* symlinks are created by apport package itself (via
to use 'xprop' just type that command on a command line (you need
'x11-utils' installed) and click on the dialog you want the info from
and it's going to print the info on the command line
what session/desktop are you using?
--
You received this bug notification because you are a member of
** Description changed:
- (To be filled with details)
+ When `apport-bug linux` was executed on systems with linux-oem, linux-
+ oem-osp1 kernels, many details are not included as generic linux kernel
+ does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing.
--
You received this bug
What do you see during the freeze? Is it a black screen or something
else?
Does the machine even boot kernel 5.3 successfully?
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Public bug reported:
Xorg freeze at boot on Intel Corporation HD Graphics 530 with
linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan
Ermine (development branch).
If i boot with linux-image-5.0.0-31-generic the Xorg works well.
ProblemType: Bug
DistroRelease: Ubuntu
Graham, you could be hit by a different bug. (In my case it was fubared
NFS mount from fstab – turns out NFS mounts should be removed from fstab
before upgrades) You are interested in solving "pam_nologin should allow
sudoers to log in" – it is bug #1847902
--
You received this bug notification
** Summary changed:
- oem kernel packages treat differently from generic kernel ones
+ oem kernel packages treated differently from generic kernel ones
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** Also affects: apport
Importance: Undecided
Status: New
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority
** No longer affects: apport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Yes I have a verified Google address, which is that I enter in the
gnome-control-center-app
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1847597
Title:
Public bug reported:
(To be filled with details)
** Affects: oem-priority
Importance: Undecided
Status: New
** Affects: apport (Ubuntu)
Importance: Undecided
Assignee: You-Sheng Yang (vicamo)
Status: New
** Tags: oem-priority
--
You received this bug
I've had this issue since 2017 all the time. As you can see in the
comments, Kai suggested that this is an hardware issue. He developed a
workaround for the kernel that I tested, however it made the general
output volume significantly lower, see #96, which is the reason this fix
was never shipped.
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/rsyslog/+git/rsyslog/+merge/374072
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/rsyslog/+git/rsyslog/+merge/374073
--
You received this bug notification because you are a member
I prepped the two MPs for the SRU as this isn't the biggest impact fix,
but OTOH patch-on-a-platter and also easy to review for code/impact.
** Changed in: rsyslog (Ubuntu Disco)
Importance: Undecided => Low
** Changed in: rsyslog (Ubuntu Bionic)
Importance: Undecided => Low
**
** Description changed:
+ [Impact]
+
+ * rsyslog ships with a (Default disable) apparmor profile.
+ * Security sensitive users are in general encouraged to enable such
+profiles but unfortunately due to slightly new behavior of the program
+the profile prevents its usage.
+ * Allow
@seb128
>From a functional point of view, it is working now.
I'm able to connect to my AP with WPA3-SAE/WPA3-Personal using
1.20.4-2ubuntu2 from proposed.
Although I'm unable to comment on the gnome-shell part of this bug since
i'm using XFCE.
Thanks for helping out.
--
You received this
63 matches
Mail list logo