This appears to be in the same family as bug 1943406. But rather than
being driver-specific it looks like mutter is trying to delete an
invalid texture, which will crash differently for each driver.
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in
Thanks for the bug report. Please edit /etc/default/grub and change:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0"
and then run:
sudo update-grub
and reboot.
Does that fix the problem?
** Package changed: xorg (Ubuntu) =>
** Description changed:
- [Why SRU?]
+ [Impact]
The fixes for this bug (including the fixes for LP:#1944906) need to be
backported to hirsute, focal and bionic) to be able to re-enable the
"repo-snapshot-stamp" feature for image builds. That feature is important to
get consistent image
Tracking in
https://errors.ubuntu.com/problem/d20095c0f9516f2d25a5e5b9194fdb87eec5ba8b
** Tags added: vmware vmwgfx
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from
mm_buffer_destroy() from pb_destroy()
** Package
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
*** This bug is a duplicate of bug 1933771 ***
https://bugs.launchpad.net/bugs/1933771
** This bug is no longer a duplicate of bug 1926084
[hirsute] [Intel AX200 Bluetooth] Bluetooth speakers reconnect randomly
** This bug has been marked a duplicate of bug 1933771
Bluetooth headset
*** This bug is a duplicate of bug 1933771 ***
https://bugs.launchpad.net/bugs/1933771
Yes I was thinking that but didn't have any evidence of it yet. Let's
group this with bug 1933771 for now.
** This bug has been marked a duplicate of bug 1933771
Bluetooth headset random disconnects
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
*** This bug is a duplicate of bug 1945235 ***
https://bugs.launchpad.net/bugs/1945235
** This bug has been marked a duplicate of bug 1945235
pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from
transport_put() from hfp_rfcomm_handle()
--
You received this bug
*** This bug is a duplicate of bug 1945235 ***
https://bugs.launchpad.net/bugs/1945235
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
pulseaudio. This problem was most recently seen with package version
1:15.0+dfsg1-1ubuntu2, the problem
** Summary changed:
- delayed display update / konsole artifacts
+ KDE delayed display update / konsole artifacts
** Package changed: xorg (Ubuntu) => kwin (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
Most likely cause of this problem is this bug in linux-firmware
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
System is Mint 20.2, with the relevant packages taken from Ubuntu Focal.
This is the output of `systemd-resolv --status vpn0`:
Link 7 (vpn0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Tracking in
https://errors.ubuntu.com/problem/3f255341dbcb4f57cf88d6fc2bed25ae18a760fe
** Summary changed:
- pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put()
+ pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from
transport_put() from hfp_rfcomm_handle()
**
huh, focal-updates has a much newer mesa which has that commit..
--
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/1776499
Title:
Crash in libegl-mesa0 due to out of bound
Public bug reported:
I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake
GT2 [HD Graphics 520] and I am having flickering graphics.
The problem sometimes happens showing grey flickering boxes 5-6 times in
a minute, and sometimes it does not happen for 2-3 minutes. Overall, it
** Description changed:
+ [Why SRU?]
+ The fixes for this bug (including the fixes for LP:#1944906) need to be
backported to hirsute, focal and bionic) to be able to re-enable the
"repo-snapshot-stamp" feature for image builds. That feature is important to
get consistent image builds (means
I confirm the bug on our environment with Ubuntu 20.04 and isc-dhcp-server
4.4.1.
Omshell randomly goes on segfault:
[Tue Sep 28 11:05:22 2021] omshell[4604]: segfault at 0 ip 55623cdd06dc sp
7ffd5a2c7c78 error 4 in omshell[55623cd97000+45000]
--
You received this bug notification
Public bug reported:
I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake
GT2 [HD Graphics 520] and I am having flickering graphics.
The problem sometimes happens showing grey flickering boxes 5-6 times in
a minute, and sometimes it does not happen for 2-3 minutes. Overall, it
Thanks for the bug report.
You seem to be using the 'oibaf' PPA which is unsupported and often
causes bugs like this. Please remove it using 'ppa-purge', reboot, and
then open new bugs for any issues you still have.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
** Changed in: livecd-rootfs (Ubuntu Hirsute)
Assignee: (unassigned) => Thomas Bechtold (toabctl)
** Changed in: livecd-rootfs (Ubuntu Focal)
Assignee: (unassigned) => Thomas Bechtold (toabctl)
** Changed in: livecd-rootfs (Ubuntu Bionic)
Assignee: (unassigned) => Thomas Bechtold
Tracking upstream in https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/issues/134 although I found it by
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/563 which
better matches this bug.
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu)
** Bug watch added:
Update: Lennart's AF_SOCKET solution was added to systemd v248 in:
commit e2c2f868b28f1445e061bf7eb475b0c49efe3ac2
Author: Lennart Poettering
Date: Wed Nov 4 17:24:53 2020 +0100
cryptsetup: port cryptsetup's main key file logic over to
read_full_file_full()
Previously, we'd load
This really should not be marked Invalid since it represents a very real
regression on recommended and documented functionality that many
installs using LUKS rely upon. Workarounds of varying security quality
abound as a result instead of a single, well designed and integrated
solution.
Indeed,
This issue is still happened using focal-update.
I checked below changelog for libegl-mesa0 package:
- https://packages.ubuntu.com/focal/libegl-mesa0
- https://packages.ubuntu.com/focal-updates/libegl-mesa0
And found the change is only existed in focal, but not in focal-update:
mesa
Public bug reported:
The test of bolt fails with the new version due to a crash:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz
...
Trace/breakpoint trap (core dumped)
The bolt test really uses umockdev, d/t/control has
** Changed in: systemd (Ubuntu Impish)
Status: Fix Released => Won't Fix
--
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/1938259
Title:
Add ACCEL_LOCATION=base
** Also affects: iptables (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: lxd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: iptables (Ubuntu
It works:
# witness the original bug while running `sudo -i` in another session:
sdeziel@xeon:~$ tail -f /var/log/auth.log | grep pam
Sep 28 16:56:52 xeon sudo: pam_unix(sudo:auth): Couldn't open /etc/securetty:
No such file or directory
Sep 28 16:56:53 xeon sudo: pam_unix(sudo:session): session
This could be a problem in pulseaudio native backend, provoked by
numerous reconnections between bluez and headset.
If verbose log from pulseaudio daemon can be collected for this crash, I
think it is worth to file an issue in pulseaudio tracker here
Public bug reported:
i open a second bug report because i have already freeze problem after the
installation of nvidia drivers and reboot.
Freeze become generally when i am using firefox and visioning a video with
youtube.
I specify that since the last bug report, i re install ubuntu with
it's not going to be ready for impish
** Changed in: software-properties (Ubuntu Impish)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
@robert-ancell: IIRC you had some code for this already? Or am I
misremembering it?
** Changed in: software-properties (Ubuntu Focal)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
>From my perspective, this is a bugfix, not a new feature, since it's
required to maintain compatibility with current .deb packages as shipped
in the corresponding Ubuntu release.
** Changed in: python-debian (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because
** Merge proposal linked:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/python-debian/+git/python-debian/+merge/407413
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
I tried it, but it didn't work. It goes back to A2DP by itself
Em seg., 27 de set. de 2021 às 23:30, Hui Wang <1944...@bugs.launchpad.net>
escreveu:
> If so, please select hsp/hfp from configuration, the A2DP only has
> output.
>
> --
> You received this bug notification because you are
Thanks Christian -- Indeed I noticed that, and set
https://gitlab.freedesktop.org/bolt/bolt/-/merge_requests/246 the day
after to fix this. Unfortunately I didn't get a reaction yet, and
Christian also didn't respond on IRC yet. I'll do some more prodding.
** Changed in: bolt (Ubuntu)
Since Debian is also affected I filed it there as well:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248
** Bug watch added: Debian Bug tracker #995248
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248
** Also affects: umockdev (Debian) via
> I am in contact with Christian now, and hope to sort this out soon.
Sorry -- I meant Christian Kellner, bolt's upstream, not you :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
The bug is assigned and targetted to focal, it's import for the LTS but
we don't believe it should be a release issue for impish
** Tags removed: rls-ii-incoming
** Tags added: rls-ii-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: pulseaudio (Ubuntu)
Status: In Progress => Fix Released
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Changed in: software-properties (Ubuntu Hirsute)
Status: New => Won't Fix
** Changed in: software-properties (Ubuntu Bionic)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: software-properties (Ubuntu Xenial)
Assignee: (unassigned) => Robert Ancell
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/409304
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Christian, as I write above I believe this really needs to be fixed in
bolt's tests. The umockdev change was a bug fix which bolt's tests
(incorrectly) worked around. So I hope you don't mind that I flipped the
affected package around? I am in contact with Christian now, and hope to
sort this out
** Changed in: bolt (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1945321
Title:
umockdev 0.16.3-1 breaks autopkgtest of
Looking at the changelog this looks suspicious:
- Immediately create "bus" and "class" directories in /sys to fix udev
enumerator (thanks David Lechner)
That change is at
https://github.com/martinpitt/umockdev/commit/5e829601434610ef510bda12571291509a3a51d2
And that explains it,
Hello Seth, or anyone else affected,
Accepted pam into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pam/1.3.1-5ubuntu4.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: libcamera (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1931958
Title:
Worked for me on my daily workstation:
⏚ [sarnold:~/trees] 100 $ sudo apt install -tfocal-proposed libpam0g
libpam-runtime libpam-modules-bin libpam-modules
Reading package lists... Done
Building dependency tree
Reading state information... Done
Recommended packages:
update-motd
The
I had a WIP branch done as part of the ESM work. That's now been
rescheduled to April 2022, and the Livepatch migration will be done as
part of that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
** Also affects: graphite2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to graphite2 in Ubuntu.
*This* bug was never present in the release pocket. It was resolved
before libffi left -proposed.
As a user, you should not be installing updates from the -proposed
pocket of the development release.
You should file a new bug report for the issue you're experiencing.
--
You received this bug
** 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/1945376
Title:
Touch pad stopped working
Status in xorg package in Ubuntu:
New
** Also affects: alsa-ucm-conf (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Focal)
** No longer affects: linux (Ubuntu Hirsute)
** No longer affects: linux (Ubuntu Impish)
** No longer affects: pulseaudio (Ubuntu Focal)
** No longer affects:
6 years later, I'm encountering the same issue in Ubuntu 18.04.
sudo apt install libfreetype6-dev:i386
[...]
The following packages have unmet dependencies:
libfreetype6-dev:i386 : Depends: libc6-dev:i386 but it is not going to be
installed or
libc-dev:i386
** Also affects: pulseaudio (Ubuntu Impish)
Importance: Medium
Status: Fix Released
** Also affects: linux (Ubuntu Impish)
Importance: Medium
Status: Fix Released
** Also affects: alsa-ucm-conf (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this
hey, can I upgrade or not? Last time I updated, I broke my system and
had to reinstall, and now someone has already tested if you can upgrade
without breaking the system? This bug has been affecting me for a long
time and it's been bothering me .. No matter that I change the update
settings to
You have been subscribed to a public bug:
The touchpad on my Asus ZenBook flip always stops working after I close
the laptop! I have to restart the computer to make working again.
Appreciate your support.
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
If so, usually it is the issue on bluetooth host controller side. Either
the kernel's driver issue or the bluetooth firmware's issue.
Please upload the log of '$usb-devices'.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for software-properties (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: software-properties (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for indicator-power (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: indicator-power (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for avahi (Ubuntu) because there has been no activity for 60
days.]
** Changed in: avahi (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
All autopkgtests for the newly accepted pam (1.3.1-5ubuntu4.3) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
kopanocore/8.7.0-7ubuntu1 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding
Hello Timo, or anyone else affected,
Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.3~20.04.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
[Expired for Ubuntu MATE because there has been no activity for 60
days.]
** Changed in: ubuntu-mate
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Summary changed:
- Touch pad stopped working
+ [Asus ZenBook Flip UX363EA] Touchpad stops working after closing the laptop
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
[Expired for gtk+2.0 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gtk+2.0 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
The most likely cause of this problem is environmental such as:
* Other Bluetooth devices in the same area, like mice; or
* 2.4GHz wifi networks interfering with Bluetooth. Try using 5GHz
networks, or wired networking instead.
** Summary changed:
- [hirsute] Bluetooth speakers reconnect
If it works in Ubuntu 20.04.3 as you say, and only fails in MATE, then
we probably shouldn't assign this to the common package where it's
working already.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
** Summary changed:
- Problem with bluetooth keyboard: not usable
+ Problem with
75 matches
Mail list logo
