*** This bug is a duplicate of bug 1876989 ***
https://bugs.launchpad.net/bugs/1876989
Public bug reported:
20.04.1 Encrypted LVM install, sda4 > LUKSv2 > VG > LVs
cryptsetup creates LUKSv2 containers. GRUB can only understand LUKSv1
and therefore cannot access its root device making the
Public bug reported:
20.04.1, when applying updates, 'full log' is reporting for every
package install:
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such
device)
This should either be corrected (by mounting devpts into the /target/ or
redirecting the error to /dev/null to
Public bug reported:
20.04.1, Custom storage layout
This view does not refresh when underlying changes have occurred,
whether using the "Reset" option, or using 'Back' to move back through
the pages.
Specific scenario is related to "Unable to add a GPT partition with
400+GB free space" bug
Public bug reported:
20.04.1 installer, Custom storage layout
On a device with 400+ GB free space and 4 existing GPT partitions the
option to add a GPT partition is disabled.
Apparently the logic cannot code with dis-contiguous partitions!
root@ubuntu-server:/# gdisk -l /dev/sda
GPT fdisk
May be fixed by upstream commits:
7b7d897e8898 2020-07-24 12:34:42 +0200 N shirley her mmc: sdhci-pci-o2micro:
Add HW tuning for SDR104 mode
cdd2b769789a 2020-07-24 12:30:36 +0200 N shirley her mmc: sdhci-pci-o2micro:
Bug fix for O2 host controller Seabird1
--
You received this bug
Public bug reported:
I've been working with a colleague with an ubuntu-server install in a
Xen virtual machine. The install doesn't use an external
kernel/initrd.img but due to having package ubuntu-server installed also
installs cloud-initramfs-copymods.
The initial report was the system
There are a couple of problems here, for 20.04 LTS.
1) inkscape package declares a Recommends: for python-scour which does
not exist in 20.04 - only python3-scour.
2) /usr/share/inkscape/extensions/scour.inkscape.py depends on python2:
#! /usr/bin/python2
** Summary changed:
- Optimized svg
** Changed in: inkscape (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878453
Title:
20.04: Optimized SVG save fails due to no python-scour package
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1892276/+attachment/5403971/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have run the command as requested and opened a new issue for gnome.
The issue number is #216.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892276
Title:
pdf images stretched on desktop 20.04
apport information
** Tags added: apport-collected
** Description changed:
- I updated all packages from the update branch and in the last week or
- two the pdfs on my desktop are displayed incorrectly and stretched out.
- It appears that I did not have the bug prior to the fix, but have it now
Public bug reported:
I updated all packages from the update branch and in the last week or
two the pdfs on my desktop are displayed incorrectly and stretched out.
It appears that I did not have the bug prior to the fix, but have it now
that I have updated to the new package version.
** Affects:
Is part of the issue here that some (most) initramfs-tools created
images have an uncompressed early CPU microcode firmware prefixed ?
That is stored as ASCII CPIO which is why Con see's that reported by
'file' since that tool checks the magic signatures at start of a file.
binwalk reveals more
I've just hit this similar issue on Xubuntu 20.04. The problem here is
there's a missing "Depends: kde-cli-tools" because the "Full mode"
desktop file tries to call kdesu which isn't installed:
Exec=kdesu nmapsi4
I think that is probably not the way to do it even though it is a using
a QT GUI -
I've worked with upstream AMD and we've fixed the problem in in xf86
-video-amdgpu. As soon as that is available in the upstream repository
I'll prepare a cherry-pick update to 20.04.
I suspect we also need to consider an SRU patch to 18.04 ?
--
You received this bug notification because you
** Also affects: linux via
https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Urgh, should have written "With the help and suggestions of 'brainwash'
and 'bluesabre' on #xubuntu-devel..."
** Summary changed:
- Regression: block staircase display with side-by-side monitors
+ Regression: block staircase display with side-by-side monitors of different
pixel widths
**
With the help and suggestions of Bluesabre on #xubuntu-devel we've
tracked it down to a recent change in xfwm4 where it switched from using
glx to xpresent:
https://git.xfce.org/xfce/xfwm4/commit/?id=23900123ad8418149897a094d1096d6ecb984d3c
which seems to be a bug in the driver as mentioned
** Also affects: xfwm4 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
Regression: block staircase display with side-by-side
Reproducing this:
$ xrandr -d :0.0 --output HDMI-A-0 --left-of eDP
$ xrandr -d :0.0 --output HDMI-A-0 --right-of eDP
No problem with:
$ xrandr -d :0.0 --output HDMI-A-0 --above eDP
$ xrandr -d :0.0 --output HDMI-A-0 --below eDP
The affected and unaffected laptops each have identical kernel log
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357359/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357358/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357357/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357349/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357360/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
Timo: yes, sorry, I think I got a bit confused about packages due to
lack of sleep. I've reported this against xserver-xorg-video-amdgpu for
now although looking at the apt history it wasn't updated.
I'm not too familiar with the Xorg internals so any pointers on
potential culprits would be
Tim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
Regression: block staircase display with side-by-side monitors
To manage notifications about this bug go to:
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357361/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357348/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357355/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357353/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357364/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357363/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357356/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357362/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357354/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357351/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357352/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357346/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided
Status: New
** Tags added: apport-collected focal ubuntu
** Description changed:
Two identical Lenovo E495 laptops with 20.04 installed. The problem
occurred initially on the laptop that
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357350/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357347/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
These are the packages I've tested via a downgrade:
$ apt list --upgradeable
Listing... Done
libxcomposite1/focal 1:0.4.5-1 amd64 [upgradable from: 1:0.4.5-0ubuntu1]
libxcomposite1/focal 1:0.4.5-1 i386 [upgradable from: 1:0.4.5-0ubuntu1]
libxdamage1/focal 1:1.1.5-2 amd64 [upgradable from:
I'm attaching the complete list of packages upgraded on the second
laptop that triggered this bug.
The total list is over 300 packages. I've prefixed the unlikely package
with #. That leaves 77 possibles all related to X server or display
drivers.
** Attachment added: "List of upgraded packages
The packages upgraded on the second laptop that are libx related are:
$ grep 'Upgrade: hunspell' /var/log/apt/history.log | grep -o 'libx[^ ]*'
libxml2-utils:amd64
libxml2:amd64
libxatracker2:amd64
libxcomposite1:amd64
libxcomposite1:i386
libxml2-dev:amd64
libxfixes3:amd64
libxfixes3:i386
Public bug reported:
Two identical Lenovo E495 laptops with 20.04 installed. The problem
occurred initially on the laptop that is having package upgrades applied
regularly.
With dual monitors and the external monitor placed left or right the
display has a blocked staircase effect shown in the
So is this being left broken then? This is a regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866065
Title:
weechat python.so not linked against libpython3 (undefined symbol:
Assignee: (unassigned) => TJ (tj)
** Summary changed:
- CVEs: backport 2.7.1 CVEs to 20.04 weechat-2.6
+ CVE-2020-8955: backport 2.7.1 CVEs to 20.04 weechat-2.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
See also additional patches address CVE-2020-8955 in Bug #1872425
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8955
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866065
Title:
Public bug reported:
Ensure latest CVEs fixed in 2.7.1 are included in 20.04
** Affects: weechat (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Debdiff against 2.6-2ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/weechat/+bug/1866065/+attachment/5353091/+files/lp1866065.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "python3: correctly find and link against libpython3.8"
https://bugs.launchpad.net/ubuntu/+source/weechat/+bug/1866065/+attachment/5353078/+files/lp1866065-python3-linking.patch
** Changed in: weechat (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: we
The problem here is the build isn't linking against libpython3
$ ldd /usr/lib/x86_64-linux-gnu/weechat/plugins/python.so
linux-vdso.so.1 (0x7ffd8eb94000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1ae4b37000)
/lib64/ld-linux-x86-64.so.2 (0x7f1ae4d83000)
Solution:
Create all the mountpoints in the root-fs when doing a manual install.
e.g:
sudo mkdir -p /target/{proc,sys,dev/pts,var,home,boot,usr/local}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reviewing the source it looks to be stalling in
partman/finish.d/apt_clone_save
I added 'set -x' to top of that file in the live system and captured the
following in its syslog. Looks like there's a failure to create the
root-fs directory structure and so there is no mountpoint for the /var/
Public bug reported:
Trying to install the Xubuntu 20200408 amd64 ISO from USB, Try (safe
graphics mode) on Lenovo E495 (AMD Ryzen 7 mobile CPU) - not sure if the
CPU might have something to do with this but probably not.
Nothing obvious in the logs I've checked.
Currently the system has been
Public bug reported:
Working with a new install of 20.04 on RAID-1 mirror using mdadm grub-
install fails on EFI installs with:
# grub-install -v /dev/md0
...
Installing for x86_64-efi platform.
grub-install: warning: efivarfs_get_variable:
Public bug reported:
apt-cache policy python3-twisted
python3-twisted:
Installed: 18.9.0-6ubuntu1
Candidate: 18.9.0-6ubuntu1
Version table:
*** 18.9.0-6ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
Setting up
There are no logs required; this is a feature enhancement request
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859212
Title:
Public bug reported:
Move "pci-hyperv.ko" to the primary kernel image package.
Whilst attempting a 20.04 install into a Microsoft Windows Hyper-V guest
that uses Discrete Device Assignment (DDA a.k.a. PCI pass-through) for
2x NVMe SSDs and Intel i350-T4 quad-port Gigabit Ethernet we found that
There's another angle to this that ought to be considered.
A few months ago in the Lubuntu project, due to a variety of issues with
installer images, I investigated using dm-verity to detect errors:
"Make checksum verification automatic"
https://phab.lubuntu.me/T32
I went further to
19.10, having the same issue. Installed the latest adcli (0.9.0) and
this resolved my issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842951
Title:
adcli join fails
To manage notifications
@Sebastian Oops! I usually add ~tj or ~lpXX but lost that change this time
because whilst fighting with trying to combine the upstream, Debian, and Ubuntu
git repos and use sbuild to test.
It failed in all sorts of confusing ways so I simply made a non-git copy and
ran 'dch -i' immediately
: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
And the GUI editor opened on the connection.
The built package can be found at:
https://launchpad.net/~tj/+archive/ubuntu/bugfixes
** Patch added: "Debdiff containing the patch"
https://bugs.launchpad.net/ubuntu/+source/network-mana
I've built a test package for 18.04 in my PPA if you want to test it:
https://launchpad.net/~tj/+archive/ubuntu/bugfixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752091
Title:
gvfsd-metadata
Just to be clear the device Austin is dealing with is:
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI
Express Card Reader [10ec:5227] (rev 01)
Subsystem: Hewlett-Packard Company RTS5227 PCI Express Card Reader
[103c:804e]
Kernel driver in use:
Austin, thanks for confirming that repository solves the issue for you.
I'll try to make a diff of the original commit to that repository
against the Linux mainline driver at the same date, maybe we can be
lucky and it'll make the required change clear so we can test it in
Ubuntu and then get it
The linked github repository doesn't break out whatever the fix is to
the rtsx_pci driver is. Therefore it is all but impossible to figure out
what was changed.
Another user reported this today with 5.0.0-27-generic where 64GB cards
are readable but 256GB cards are not. It isn't clear if the
Re-marking as Invalid since I finally figured out today the erroneous RR
was not generated by dnssec-signzone but a 3rd party tool that
mistakenly writes the salt-length field too (which shouldn't be present
except in the on-the-wire RDATA).
** Changed in: bind9 (Ubuntu)
Status: Triaged
Public bug reported:
On 18.04 with bind9/bionic-updates,bionic-proposed,now 1:9.11.3+dfsg-
1ubuntu1.9
When the zone file includes:
@ IN CAA "letsencrypt.org"
An error occurs when trying to sign the zone:
$ sudo dnssec-signzone -v 255 -o example.com example.com.hosts
** Description changed:
On 18.04 with bind9/bionic-updates,bionic-proposed,now 1:9.11.3+dfsg-
1ubuntu1.9
+
+ This prevents Certbot Let's Encrypt validation and therefore certificate
+ issuance when the zone is configured to use NSEC3.
+
+ NSEC3 is valuable in preventing DNSSEC NSEC zone
Public bug reported:
On 18.04 with bind9/bionic-updates,bionic-proposed,now 1:9.11.3+dfsg-
1ubuntu1.9
Where a zone file has DNSSEC enabled and an NSEC3PARAM record is added
to the already-signed zone file:
example.com.IN NSEC3PARAM ( 1 0 10 16 0d95646237ae38bc )
an attempt to
There were quite a few changes in the i915 driver related to idle
condition and states. Is it confirmed v4.19 exhibits the issue whilst
v4.18 does not? If so then the candidate commits causing the regression
could be in this list:
$ gitlog --reverse --grep=idle v4.18..v4.19 --
Please ensure the installer media image is not corrupt. In this case
UbiquitySyslog.txt reports:
Aug 11 16:12:44 ubuntu kernel: [ 3438.661203] SQUASHFS error: zlib
decompression failed, data probably corrupt
Aug 11 16:12:44 ubuntu kernel: [ 3438.661208] SQUASHFS error:
squashfs_read_data failed
The reason your "dyndbg=module e1000" does not work is because
dyndbg=... is only processed at boot time and therefore only affects
*built-in* modules. e1000 is a dynamically loaded module not a built-in.
What you need is the module.dyndbg=... form as in:
"e1000.dyndbg=+p"
See especially line
This is correct. The essential thing to understand is the kernel's
command-line uses space as the separator between options so:
option1=1 option2=2 option3=3
option1=1 option2="2" option3="3 or 4"
option1=1 "option2=2" "option3=3 or 4"
are all identical.
What you are seeing in /proc/cmdline is
Could very likely be, or closely related to:
https://bugzilla.kernel.org/show_bug.cgi?id=199349
If the issue is RCU (Read-Copy-Update) or Memory-Management related and
specific to the AMD Turion X2 the most obvious suspect commits between
v4.6.2..v4.6.3 are:
$ gitlog v4.6.2..v4.6.3 -- mm/
Today in IRC we were asked if the ficed package is in the 19.04 ISOs. It
isn't so they will fail to boot on AMD Ryzen 3000 CPUs.
Is there a plan to re-build the 19.04 ISOs? If not there ought to at
least be a prominent addition to the 19.04 release notes.
--
You received this bug notification
This package is imported from Debian and doesn't carry Ubuntu-specific
patches so the best way to get these changes is to report a bug against
it there. If the Debian maintainer adds these options Ubuntu will
inherit it at next import.
https://packages.debian.org/sid/goldendict
--
You received
** Summary changed:
- dm-verity: Invalid number of feature args
+ "dm-verity: Invalid number of feature arg" with FEC due to "#
CONFIG_DM_VERITY_FEC is not set"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
On an 18.04 amd64 system dm-verity reports:
device-mapper: table: 253:20: verity: Invalid number of feature args
device-mapper: ioctl: error adding target to table
when trying to use "veritysetup" to create a previously formatted verity
device that uses
Public bug reported:
On an 18.04 amd64 system dm-verity reports:
device-mapper: table: 253:20: verity: Invalid number of feature args
device-mapper: ioctl: error adding target to table
when trying to use "veritysetup" to create a previously formatted verity
device that uses FEC. Without FEC it
Strongly related bug for 18.04 with an explanation of what is hanging
but referencing plymouth's "splash" which this system doesn't use:
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.15.0-56-lowlatency root=/dev/mapper/VG02-rootfs ro
intremap=no_x2apic_optout no_console_suspend acpi_osi=!
I'm seeing this same issue (hung syscall on VT) from systemd-sleep on a
suspend operation with Xubuntu (and therefore lightdm). I see a similar
stack-trace too. 18.04 with 4.15.0-56-lowlatency.
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1744370
apt list plymouth
Listing... Done
Just re-discovered my own report here whilst trying to solve another
occurrence of the same issue 18 months later.
Now with 18.04 and 4.15.0-56-lowlatency (amd64).
With assistance of grawity in IRC #systemd I found some more information which
might help narrow this down.
$ uname -a
Linux
@ahasenack: 2.4.29-1ubuntu4.8~sslreadrc~ppa3 confirmed working without
processes spinning
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836329
Title:
Regression running ssllabs.com/ssltest causes
ptions: uhelper=udisks2
org.freedesktop.UDisks2.Filesystem:
MountPoints:/media/tj/Xubuntu 19.10 amd64
Size: 0
$ mount | grep media/tj
/dev/sr0 on /media/tj/Xubuntu 19.10 amd64 type iso9660
(ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=100
** Changed in: linux (Ubuntu Disco)
Assignee: TJ (tj) => (unassigned)
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811869
Title:
Alienware m15 takes very long to boot Ubuntu
To man
Request for cherry-pick sent to kernel-team mailing list 27 June 2019.
** Also affects: linux via
https://github.com/lwfinger/rtlwifi_new/issues/401
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Upstream commit:
commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
Author: Larry Finger
Date: Sat Nov 17 20:55:03 2018 -0600
rtlwifi: Fix leak of skb when processing C2H_BT_INFO
With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO"), calling
Using gparted (which requires root access to the block storage devices)
"test" user fails whilst original "lubuntu" user is successful:
# In "lubuntu" user's GUI terminal emulator:
lubuntu@lubuntu:~$ gparted
localuser:root being added to access control list
==
libparted : 3.2
Possibly related to Bug #1821415 "pkexec fails in a non-graphical
environment"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828663
Title:
policykit failures due to internal user id mismatch
To
Lubuntu is suffering what seems to be a related failure although I
tracked that down to what I thought was a different upstream bug report.
In Lubuntu's case the lxqt-policykit-agent suffers a SIGSEGV as a side-
affect (I think) of polkit failing to authorise.
It was originally discovered when,
> Invalid
** Changed in: lxqt-policykit (Ubuntu)
Status: Confirmed => Invalid
** Changed in: policykit-1 (Ubuntu)
Status: New => Confirmed
** Changed in: lubuntu-meta (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a m
** Also affects: policykit-1 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/polkit/polkit/issues #39
https://gitlab.freedesktop.org/polkit/polkit/issues/39
** Also affects: policykit-1 via
Looks like there may be two problems but I'm not familiar enough with
the code bases to figure it out.
1) should a user already a member of "sudo" group even be prompted to
select the user they wish to authenticate as?
2) when they do something goes wrong and there's a SIGSEGV which looks
like
** Also affects: polkit-qt-1 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828663
Title:
lubuntu 19.04 QT interfaces not properly working where
There's a SIGSEGV; gdb bt full attached.
#0 0x7f1d14271201 in g_type_check_instance_is_fundamentally_a
(type_instance=type_instance@entry=0x55b74c6fd010,
fundamental_type=fundamental_type@entry=0x50 [GObject]) at
../../../gobject/gtype.c:4025
node =
#1 0x7f1d14251399 in
** Changed in: lubuntu-meta (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: lubuntu-meta (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
101 - 200 of 2979 matches
Mail list logo
