After kernel + x.org updates this week, firefox is now displaying
properly using xserver-xorg on the Athlon 200GE.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2055351
Similar hardware:
R7 240 graphics card (previous generation graphics cores) on Athlon
200GE: everything works fine on X11
Plugged SSD from Athlon install into 5600G (Vega 6 graphics instead of
Vega 3): everything works fine on X11.
So it seems to be something weird about Vega 3 graphics in
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753661/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753659/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753658/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753660/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753652/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753653/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753657/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753644/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753646/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753655/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753654/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753651/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753650/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753648/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753647/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753649/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753645/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753642/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753643/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
It is similar but not identical.
I just updated Snap, Firefox, and Chromium, and, currently, Firefox with
hardware acceleration works fine using wayland, but not X11. Firefox
without hardware acceleration works on either.
I am attaching a screenshot of unaccelerated Firefox beside (corrupted)
Verified that the package was called xorg and not X11
** Package changed: ubuntu => xorg (Ubuntu)
--
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/2055351
Title:
firefox
Public bug reported:
I've been debugging PostgreSQL REL_14_STABLE branch authentication code
starting the postgres postmaster, running psql and then connecting to a
new process using `sudo gdb -p `. After a long day of it, I met
this segmentation fault. This message says, that it is definitely a
We may as well close this issue, I don't have that laptop any more, I
don't work for Canonical any more and the boot speed regressions seem to
have fallen off the CTO's "must do priority radar" otherwise this kind
of regression would have had more engineering time devoted to it.
--
You received
** Changed in: systemd (Ubuntu)
Status: Invalid => Confirmed
--
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:
Ubuntu 22.04.3 LTS stuck on
Thanks JJ, much appreciated :-)
--
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/2024599
Title:
linux-image-5.15.0-1032-realtime locks up under scheduler test load
Status
And also occurs in Ubuntu Mantic with 6.3.0-7-generic
--
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/2024599
Title:
linux-image-5.15.0-1032-realtime locks up under
5.15.0.75 works fine, no problem, 5.19.0-45 kernel crashes, so issue
introduced between 5.15 and 5.19
** Also affects: apparmor (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: apparmor
And with 5.19.0-45-generic:
sudo ./stress-ng --apparmor 1 --klog-check
[sudo] password for cking:
stress-ng: info: [1179] defaulting to a 86400 second (1 day, 0.00 secs) run
per stressor
stress-ng: info: [1179] dispatching hogs: 1 apparmor
stress-ng: info: [1180] klog-check: kernel cmdline:
On 6.2.0-21-generic I also get:
sudo ./stress-ng --apparmor 1 --klog-check
stress-ng: error: [1083] klog-check: alert: [66.442338] 'BUG: kernel NULL
pointer dereference, address: 0030'
stress-ng: error: [1083] klog-check: alert: [66.442538] '#PF: supervisor read
access in kernel
Public bug reported:
Just saw the bug notification, not sure how it happened.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4.4
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
ApportVersion:
Why won't fix? It occurs on other releases too.
--
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/1992979
Title:
kinetic ppc64le reporting Failed to send WATCHDOG=1
s/pull/687
Cheers,
Ian.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
New
Status in atr
Still exists in Ubuntu 22.04 with NVidia driver 390.157 DP works HDMI
shows as connected, but no output to monitor. HDMI cable works with Mac
Monterey but DP does not.
Nouveau driver works with both ports but the external display speed is
very slow and choppy even if I add PiP and use both
systemd error is being emitted from dispatch_notify_event() in
src/journal/journald-server.c, which is called from
server_connect_notify(). This function contains a large hunk of comment
block describing a potential race condition. I wonder if this is some
kind of race condition that only occurs
This looks related:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754328
--
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/1992979
Title:
kinetic ppc64le
Public bug reported:
For more information, please see
https://github.com/notroj/neon/issues/102.
The 22.04 built package of neon lacks GSSAPI support, whereas previous
versions (e.g. 18.04) had this support built-in. This appears to be due
to a recent-ish change in the build logic for neon,
I can't install Kinetic server from the LiveCD because of this issue.
It's just broken.
** Also affects: systemd (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Lunar)
Importance: Critical
Status: Incomplete
--
You received this bug
Using power9 arch, attached is the xml config
ubuntu22.10-kinetic-ppc64le
e410f72a-6555-4b47-bb18-8bb61eb52de2
http://libosinfo.org/xmlns/libvirt/domain/1.0;>
http://ubuntu.com/ubuntu/22.04"/>
8388608
8388608
1
hvm
POWER9
destroy
restart
Getting the same issue on the kinetic server daily image during the
install phase, see attached
** Attachment added: "issue during install"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+attachment/5624145/+files/Screenshot%20from%202022-10-14%2018-01-37.png
--
You received
Public bug reported:
Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU, single
CPU, 1GB memory, rebooted, can NO longer login. Stuck in systems boot
phase.
Attached is an image of the hang
** Affects: systemd (Ubuntu)
Importance: Critical
Status: New
** Attachment
** Description changed:
rsync 3.2.3 has a broken "--update" option.See the examples below.
The "--update" option incorrectly makes rsync say a file is newer than itself.
Remove the "--update" option, and rsync correctly says the file is "uptodate".
The right output should of course be
I'm not familiar with your SRU process, debdiff, dput, the "General
Requirements" document, the "security policy document", or your upload
process, and I'm not into learning about all that and filling out your
special form and making your special upload when there is no guarantee
that Ubuntu will
I knew nothing about your SRU process until now; the man page for
`ubuntu-bug` makes no mention of it. Who fills out the SRU Bug Template
and makes the fix actually happen? Is there anything more I need to do
here?
--
You received this bug notification because you are a member of Ubuntu
Touch
The problem was marked as Confirmed by Paride back on March 17.
Then today it gets marked Invalid.
Then later today it gets marked Confirmed again.
I don't understand your process.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Your incorrect statement "seems the issue does not actually exist" is
wrong. I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release. I gave you the link to the upstream bug that Wayne
fixed over two years ago. This two-year-old bug does exist and it
exists in your
Your incorrect statement "seems the issue does not actually exist" is
wrong. I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release. You were also given the link to the upstream bug
that Wayne fixed over two years ago. This two-year-old bug does exist
and it exists
Hey Ubuntu - I see now that this bug was reported and fixed at source in
September 2020, over two years ago. The real bug is: "Why didn't Ubuntu
apply the fix to the supported Ubuntu releases?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
The laptop is logged in and running Wayland: /usr/bin/Xwayland :0
My desktop is running X11: /usr/lib/xorg/Xorg -nolisten tcp :0
When I SSH into the laptop from the desktop, my DISPLAY is set to
"localhost:10".
When I start an xterm in the SSH session (running xterm on the laptop),
the xterm
Public bug reported:
I'm running Ubuntu 20.04 on my desktop. I SSH into my laptop running
22.04:
desktop$ ssh laptop
laptop$ sudo -sE
laptop#
If I now run most any X11 client applications (e.g. xload, xterm)
using this laptop SSH command line, they correctly open windows on my
Public bug reported:
The system was running in the background, and then I saw - maybe 12
hours later that it had crashed - but it appears that all the programs I
was running were till running!
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-48-generic
WPA2 Enterprise PEAP wifi working great with solution
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/76.
Thanks for the great work Sebastien!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1958267
Title:
wpa can't connect to servers using TLS 1.1 or older
Status in wpa package in Ubuntu:
Fix Released
Status in
Solution
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/22
didn't worked for me. Installing this
https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 didn't worked
for me as well. Downgraded following instructions from
** Changed in: snapd
Assignee: Ian Johnson (anonymouse67) => (unassigned)
--
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/1902748
Title:
ubuntu-seed / ubuntu-b
I am not arguing about the behaviour, which is correct and apparently hasn't
changed.
I'm complaining about the unannounced change in message from "is uptodate" to
"is newer".
Three problems:
1. The message "is newer" is an unannounced change from all previous
versions of rsync that say "is
Public bug reported:
rsync 3.2.3 has a broken "--update" option.See the examples below.
The "--update" option incorrectly makes rsync say a file is newer than itself.
Remove the "--update" option, and rsync correctly says the file is "uptodate".
The right output should of course be "is
So indeed your system is still using upstart, in order to use snapd you
will need to switch your system over to use systemd instead. Likely one
of the upgrade scripts from 10.04 to 16.04 did not transition from
upstart to systemd the way a fresh install of 16.04 would default to.
** Changed in:
What is the output of these commands:
ps -o cmd fp 1
sudo ls -lah /proc/1/exe
cat /proc/cmdline
--
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/1961418
Title:
snap
Public bug reported:
The rsyslog program mis-handles the "startswith_i" comparison when applied
to $programname. Details follow:
Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
files):
if ( $programname startswith 'foo' ) then {
/var/log/idallen-cron.log
Public bug reported:
While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade
failed
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13
ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22
Uname: Linux 5.11.0-1023-raspi
@slyon could you make available the core18 snap you built with this
systemd ?
--
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/1949089
Title:
systemd randomly fails to
** Changed in: linux-azure (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unassigned)
--
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/1822118
Title:
Kernel Pa
Dan, note that although we set the SNAP_REEXEC environment variable in
that integration test, that environment variable is actually not obeyed
when it comes to the mksquashfs command which is called here:
Also I'm not sure I agree with jdstrand's apparmor profile which
includes:
/run/snapd.socket rw,
which I don't think we want to grant to any PDF file opened with evince?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
As seb128 found, the issue is also affecting the debian package of snapd
since when we call mksquashfs, we actually have code which specifically
calls mksquashfs from the "system" snap which is either the snapd snap
or the core snap, this is presumably to ensure that a consistent
mksquashfs is
Any update on this? Having issues with sound working for some time,
than suddenly stopping with a buzzing sound. Will attempt to modify
patch for most recent kernel, but my understanding is the kernel should
already be patched. Works fine on galliumos, but not with any other
distro or most
Ah Miguel, thanks for realizing my error, I should have probably just
said something like
sudo snap install snapd --edge; sudo snap refresh snapd --edge
which will ensure that it's always installed and gets refreshed.
--
You received this bug notification because you are a member of Ubuntu
@iogui, hmm it could be that our fix isn't working, can you show the
output of these commands:
snap version
snap list
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-pt-base in
Ubuntu.
@iogui could you try again? snapd on the edge channel may not have
finished building by the time you tried, but I see that there was an
update pushed out this morning.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
to make sure the message no longer appears
snap refresh snapd --stable
# to go back to tracking stable, as edge sometimes can have unstable changes on
it
```
Thanks,
Ian
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: snapd (Ubuntu)
Importa
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
initramfs-tools:
Installed: 0.136ubuntu6.6
Candidate: 0.136ubuntu6.6
Version table:
*** 0.136ubuntu6.6 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
500
This systemd bug can be problematic for snapd as well, leading to the
sort of situation in https://bugs.launchpad.net/snapd/+bug/1928806,
where running snap commands frequently leads to many many many leftover
scopes like this
** Also affects: snapd
Importance: Undecided
Status: New
--
Public bug reported:
package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 1
ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-25-generic 5.11.0-25.27
Thanks Dimitri!
--
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/1931725
Title:
initramfs-tools: use zstd as the default compression method
Status in
Public bug reported:
Turns out that loading is always the slow part in loading initramfs into
memory and decompressing it since decompression is always the final
10-20% or so of the task. It therefore makes sense to use a good
compressor that shrinks the initramfs as much as possible with little
bionic/linux-oracle-5.4: 5.4.0-1044.47~18.04.1
--
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/1884024
Title:
lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
bionic/linux-gke-5.4: 5.4.0-1043.45~18.04.1
--
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/1884024
Title:
lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Status
Public bug reported:
Automatic upgrade failed
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-0 2.48.2-0ubuntu4.8
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
bionic/linux-azure 5.4.0-1047.49~18.04.1 sru-20210412
** Tags added: sru-20210412
--
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/1884024
Title:
lxc-test-device-add-remove
FWIW I know what the snapd issue is, the issue is that snapd does not
and will not work in a nested LXD container, we need to add code to make
snapd.seeded.service die/exit gracefully in this situation.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
** Tags added: sru-20210222
--
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/1884024
Title:
lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Status in
I tested this out with focal -proposed and don't see any issues. Looks
OK to me.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in
Is there any timeline on when this will be considered for SRU'ing back
to focal so it is usable in i.e. UC20?
--
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/1878969
Title:
Public bug reported:
This happened a little while back and it other than not being able to
boot into the new kernel, it hasn't been a problem (at least for the old
5.4.0-58) It exits on the plymouth hook
Ubuntu 20.04.1 LTS
initramfs-tools 0.136ubuntu6.3
I expected the update-initramfs to
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki)
--
You received this bug
Public bug reported:
Shouldn't these give the same results in dash, i.e. "/root"?
They give the same output in bash.
$ dash
$ var=~root
$ echo "$var"
/root
$ export var=~root
$ echo "$var"
~root
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: dash 0.5.10.2-6
ProcVersionSignature: Ubuntu
Public bug reported:
http://archive.ubuntu.com/ubuntu/pool/main/p/python-apt/python-apt-
common_2.1.3ubuntu1.1_all.deb lacks `Suite: groovy` in `Ubuntu.info`,
which is present in http://archive.ubuntu.com/ubuntu/pool/main/p/python-
apt/python-apt-common_2.1.3ubuntu1_all.deb.
I assume this is
** Tags added: uc20
--
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/1902748
Title:
ubuntu-seed / ubuntu-boot partition detection could be improved
Status in snapd:
** Changed in: snapd
Status: New => Confirmed
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
For me, as far I remember, to fix the issue on my local machine, I have to
remove python and reinstalled it.It seems that after upgrading ubuntu18 to
ubuntu focal, some python 2 footprints still remains, I am not sure if it
was the cause of issue but after removing python and purging both python2
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1895144
Title:
ubuntu-server CET gap analysis
Status in
Public bug reported:
the version of busybox in the initramfs of uc20, which derives from
ubuntu 20.04, does not have the less module/applet built into it, so
there is no less command available in the initramfs on uc20.
This is unfortunate as sometimes when debugging problems in the
initramfs it
Public bug reported:
systemd is pegged at 100% after booting Groovy Desktop.
Seems like an apport-report.service issue:
Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service:
This is a useful workaround, the fundamental issue is a coreutils issue
with dd. I wonder if the coreutils maintainers can figure out why dd has
an executable stack.
** Also affects: coreutils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: coreutils (Ubuntu)
Importance:
** Changed in: linux (Ubuntu Xenial)
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/1891224
Title:
[Hyper-V] VSS and File
Fix sent to mailing list for review: https://lists.ubuntu.com/archives
/kernel-team/2020-August/112820.html
--
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/1885730
Title:
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
@xnox,
one can detect the machine type from the DMI data (iff it is available
and reliable).
e.g. on my laptop:
sudo dmidecode -s "chassis-type"
Notebook
on my desktop server:
sudo dmidecode -s "chassis-type"
There are quite a few chassis-type, see
1 - 100 of 395 matches
Mail list logo
