#7 would suggest it's a kernel bug, so maybe test drm-tip to see if it
helps
--
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/1918855
Title:
Xorg xserver got signal 6 to abort
Public bug reported:
tcpdump has a sync from debian 4.99.0-2 that is currently blocked in
hirsute-proposed due to a regression in the apparmor adt tests. The
reason for this failure is that 'compile-policy' testcase is failing;
this test ensures that various apparmor policies included in packages
** Changed in: oem-priority
Assignee: (unassigned) => Andy Chi (andch)
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Version of mesa on oibaf ppa
21.2~git2104200600.4a384f~oibaf~h
(note)
--
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/1918855
Title:
Xorg xserver got signal 6 to abort
Public bug reported:
==36966==ERROR: AddressSanitizer: stack-overflow on address 0x7ffc5b883fe8 (pc
0x7f07be5f21a4 bp 0x7ffc5b884860 sp 0x7ffc5b883ff0 T0)
#0 0x7f07be5f21a3 in __interceptor_strlen
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x701a3)
#1 0x6a3f4a in demangle_type
Public bug reported:
==32900==ERROR: AddressSanitizer: stack-overflow on address 0x7ffe20ebff88 (pc
0x7faa529f75cf bp 0x7ffe20ec0800 sp 0x7ffe20ebff90 T0)
#0 0x7faa529f75ce in __asan_memcpy
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x8c5ce)
#1 0x6a660a in str_buf_append
OK, thanks, let me ask for help from realtek side to explain the #9.
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/1925057
Title:
[82A1, Realtek ALC287,
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.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490780/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490778/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490783/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490777/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490781/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490773/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490772/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490784/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490782/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490779/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490776/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490775/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490774/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490767/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490771/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490770/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490769/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490768/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490766/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1925055/+attachment/5490765/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hello Dan,
Thank you very much for your comments!
I played with graphics card settings and found out that when I use only
Intel graphics everything works well and I can boot without stuck.
I performed the following steps.
1. Originally I used NVidia graphics via NVidia driver.
2. First I
I am testing 21.04. I stated the system randomly crashed but am unsure
how to diagnose it and was asking for guidance so that I can share the
relevant logs and you can fix it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I attach the screencast with Ubuntu 20.04 LTS VM about CapsLock issue
for illustration.
** Attachment added: "Screecast with Ubuntu 20.04 LTS VM about CapsLock issue"
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1925141/+attachment/5490764/+files/capslock-focal-vm.gif
--
You received
> So if only run below commands, does the audio become good or not?
Yes, I confirm that the following lines are enough to make audio good:
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x08
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x4ab7
--
You received this bug notification
** Description changed:
Rsync has an astonishing and dangerous bug:
The dry run feature (-n / --dry-run) fails to report file deletions when
--remove-source-files is used. This is quite serious. People use --dry-
run to see if an outcome will work as expected before a live run. When
Public bug reported:
Rsync has an astonishing and dangerous bug:
The dry run feature (-n / --dry-run) fails to report file deletions when
--remove-source-files is used. This is quite serious. People use --dry-
run to see if an outcome will work as expected before a live run. When
the simulated
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 1925055
and then change the status of the bug to 'Confirmed'.
If, due to the
Thanks for the investigation, Dan. I tested the Linux package from your
PPA on a s390x machine and can confirm that it does solve the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The errors seems to be coming from gnome-shell-extension-appindicator
there, do you still get the issue using
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/35-1 ?
** Package changed: glib2.0 (Ubuntu) => gnome-shell-extension-
appindicator (Ubuntu)
--
You received this
@juliank Yes, python-apt works with just touched /usr/bin/zstd :
>>> apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
True
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
> But after I install some drivers (NVidia
you appear to have 2 separate graphics cards:
[4.893710] nvidia :30:00.0: enabling device (0006 -> 0007)
[6.034799] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device
my guess would be you're having problems with the kernel choosing
** Also affects: console-setup (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1925141
Title:
There is no
It looks like something happened to dbus, but it's hard to tell what, if
anything.
Was this upgrading from 246.6-1ubuntu1.2 to 246.6-1ubuntu1.3, or some
other versions?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
I have not tested hirsute in a clean container; but touch /usr/bin/zstd
makes it work, so the compressor lookup is broken.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
There seems to be a bug in bionic's apt.
root@bb:/home/jak/Projects# python3 -c 'import apt_inst, apt_pkg;
apt_pkg.init();
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2_zstd1_all.deb").control.extractdata("control")'
Traceback (most recent call last):
File "", line 1, in
LookupError:
Public bug reported:
==34504==ERROR: AddressSanitizer: stack-overflow on address 0x7ffee6038f48 (pc
0x006a3331 bp 0x7ffee6039060 sp 0x7ffee6038f20 T0)
#0 0x6a3330 in demangle_path rust-demangle.c:664
#1 0x6a3bd1 in demangle_path rust-demangle.c:774
#2 0x6a3bd1 in demangle_path
I don't understand what python-apt does here, it inherits zstd support
from apt.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages
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/1925344
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Debootstrap fix is merged in Debian:
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
** Also affects: appstream-glib (Ubuntu)
Importance: Undecided
Status: New
** Also affects: aptly (Ubuntu)
Importance: Undecided
Status: New
** Also affects: boinc
This is a very irritating thing, and should be easy to solve. The fix is just
changing initial focus!
Hard to understand this has been open for 12 years now.
There's even a risk of data loss by unintentionally overwriting a file
when one types, *as it works just fine on all other OS*, the
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1916485
in case anyone wants to test with the patched kernel
--
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/1916485
It seems the s390x failure on bionic is fixed by the patch(es) for bug
1895132. I'm not 100% sure why it is returning the normal ENOSYS for
invalid syscalls except while running under systemd-nspawn, but it might
be due to the different syscall entry path taken when _TIF_TRACE is set,
and that
Public bug reported:
After installation, the first boot works as expected - the system boots
into a graphical shell login screen. However all subsequent reboots end
up with a black screen with a blinking cursor in the top-left corner of
the screen. To get to the login screen, one has to switch to
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ Hot removal of disks under kvm on s390 does not result in the kernel
+ removing the block device, which can lead to hung tasks and other
+ issues.
+
+ [Test Plan]
+
+ See steps to reproduce the bug in the original description below.
The condition for css_sch_device_unregister(sch) also caught my eye,
calling it unconditionally is probably closer to right because it was
called in the !cdev case before, and in the attached patch it would no
longer be called in this case. However I think in the short term the
revert is the
** Package changed: ubuntu => bluez (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1925318
Title:
bluetooth just turning off and on and also disconnecting
Status
You have been subscribed to a public bug:
bluetooth just turning off and on and also disconnecting.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion:
I'm commenting to let other people know and be aware that this issue
persists on Ubuntu 20.04 with lightdm 1.30.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1806961
Thank you for help and answer.
Regards
J
--
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/1924597
Title:
package openssh-server 1:8.3p1-1ubuntu0.1 failed to
Public bug reported:
looks like the boot partition is full
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.11
ProcVersionSignature: Ubuntu 5.6.0-1054.58-oem 5.6.19
Uname: Linux 5.6.0-1054-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
Interestingly, faccessat2() does correctly return ENOSYS when using a
simple chroot instead of systemd-nspawn:
ubuntu@test-s390x:~/h$ sudo systemd-nspawn
Spawning container h on /home/ubuntu/h.
Press ^] three times within 1s to kill container.
root@h:~# test -x /bin/bash || echo "fail"
fail
Public bug reported:
PLACEHOLDER
migrate to building libclc from llvm?
** Affects: directx-headers (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: libdrm (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: llvm-toolchain-12 (Ubuntu)
** Also affects: libdrm (Ubuntu Hirsute)
Importance: Wishlist
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1923880
Title:
FFE: libdrm 2.4.105
Thanks, it seems the issue is happening without plymouth then so it's
probably the wrong component. I'm unsure what's the right place but I'm
going to reassign to systemd which is probably closer from being right
** Package changed: plymouth (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd
You have been subscribed to a public bug:
Hello,
I faced the following problem.
After the fresh installation of Ubuntu, everything works well. But after I
install some drivers (NVidia or VirtualBox) that require key enrolling I stuck
on boot. See below detailed description.
Normal behavior:
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Hot-unplug of disks leaves broken block devices around in Hirsute on
s390x
Status in
** Tags added: architecture-s39064 bugnameltc-192463 severity-high
targetmilestone-inin2104
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Hot-unplug of
I was wondering if I could trigger the same issue on an lpar as it would
raise the severity IMHO. I have no claim on completeness of these tests
in regard to all that could happen. I tried what I considered low
hanging fruits in regard to this cross check.
Pre-condition each time
- a dasd
I can reproduce this issue on hirsute.
Information below is the mesa version.
libegl-mesa0:amd64 21.0.1-2
libgbm1:amd64 21.0.1-2
libgl1-mesa-dri:amd64 21.0.1-2
libglapi-mesa:amd64 21.0.1-2
libglx-mesa0:amd64 21.0.1-2
libxatracker2:amd64 21.0.1-2
mesa-vulkan-drivers:amd64
Yes, !resuming always evaluates to true because obviously the hot-unplug
test was not done in any system PM operations.
I am also unsure whether cdev can be NULL in that context so I left it
there. Other functions have similar cdev check too. I think IBM devs
will have more insights on this.
--
68 matches
Mail list logo
