name 'Auto-Mute Mode'
value Disabled
You need to enable Auto-Mute in alsamixer.
--
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/2057957
Title:
Headphon
In case anyone is wondering, you won't start to see an improvement until
you have at least:
linux >= 6.8.0-20.20 and
plymouth >= 24.004.60-1ubuntu6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bu
Please rename the video using Latin characters because Launchpad can't
handle other character sets and we're unable to download the video.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a m
Doing this "right" requires kernel patch (attached).
This will work on 2024 model JZR.
A similar version will work on 2023 if you add the right subsystem ids[1] to
the patch.
You can also work around this by creating /etc/modprobe.d/alsa-base.conf
and adding
options snd-hda-intel model=1043:1c
Important context from https://lists.debian.org/debian-security-
announce/2024/msg00057.html :
Andres Freund discovered that the upstream source tarballs for xz-utils,
the XZ-format compression utilities, are compromised and inject
malicious code, at build time, into the resulting liblzma5 l
Yes this bug no longer happens, confirmed on two machines. But there are
other issues with many hundreds of packages being released so please log
new bugs as you find them.
** No longer affects: ubuntu-meta (Ubuntu)
** Package changed: network-manager (Ubuntu) => ubuntu
** Changed in: ubuntu
Thanks for the bug report. Please attach screenshots, photos or a video
of the problem so we can better understand the issue.
** Package changed: ubuntu-meta (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member
Public bug reported:
network-manager gets uninstalled on apt full-upgrade
I've tried two Noble systems this evening and both got their network-
manager packages removed. So wifi is gone.
** Affects: network-manager (Ubuntu)
Importance: High
Status: New
** Affects: ubuntu-meta (Ubu
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1970069
Title:
Annoying boot messages interfering
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
It appears the recurring problem here is:
simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem)
WARNING: CPU: 19 PID: 4751 at drivers/gpu/drm/drm_gem_shmem_helper.c:319
drm_gem_shmem_vmap+0x1a5/0x1e0
** Summary changed:
- Xorg crash
+ Crash
** Package changed: xorg (Ubuntu) =
Please see bug 2056160 for the time being.
--
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/2043915
Title:
Booting into live session results in try/install page white screen
S
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
That commit is not meant to reflect the outcome of discussions that
happened after it (comment #93). It's just an intermediate "UNRELEASED"
commit reflecting intermediate development.
My intent with shared repos like this is to show what is being worked on
before anything is released to the archiv
Thanks. I've reflected those changes in git:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest/
--
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/1970069
** Tags added: fixed-in-mesa-24.1 fixed-upstream
--
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/2054851
Title:
[radeon] gnome-shell and Xorg both crash with SIGSEGV in
rade
That change is in plymouth, but hooks/framebuffer is in initramfs-tools.
If you're suggesting moving the code from plymouth into initramfs-tools
then I kind of understand, but it's not directly related to fixing this
bug.
--
You received this bug notification because you are a member of Ubuntu
To
If you are suggesting moving the logic from plymouth into initramfs-
tools then please start by duplicating the code you'd like moved into
initramfs-tools. That would be efficient since you have commit access to
initramfs-tools, and would mean I only have to deal with plymouth here.
--
You receiv
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228
** Summary changed:
-
/usr/bin/software-properties-gtk:ValueError:/usr/bin/software-properties-gtk@100:__init__:__init__:backup_sourceslist:__init__
+ software-properties-gtk (ValueError) /usr/bin/software
Also tracking in:
https://errors.ubuntu.com/problem/3f3a7a239df521d94b27fbe6096dc4a05f967d35
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
soft
** Summary changed:
-
/usr/share/apport/whoopsie-upload-all:TypeError:/usr/share/apport/whoopsie-upload-all@220:main:collect_info:process_report:add_gdb_info:gdb_command
+ whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload-all@220 →
main → collect_info → process_report → add_gdb_i
If it looks correct in GNOME then please briefly log into GNOME and run:
xrandr --verbose > gnome-xrandr.txt
and attach the resulting text file here.
Also if KDE has any monitor colour profile settings then try toggling
those.
** Summary changed:
- Notebook screen the look is "matte"
+ Note
event this bug 1970069.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
The patch proposed in
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/comments/91
will help here, but since it might not be the last plymouth change
required for this issue, it doesn't mention bug 1869655.
--
You received this bug notification because you are a member of Ubuntu
To
Here's a fix for plymouth/noble.
The source is in:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest
We skipped ubuntu5 because that technically existed in bug 2054769 for
10 days already.
Also note this will cause some temporary initrd bloat while the
initramfs-tools cha
** Changed in: plymouth (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Bump this is also affecting us causing quite a lot of downtime just to
add a vlan interface
--
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/2052137
Title:
bonded link goes
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/462482
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a me
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
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.laun
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
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.laun
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
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.laun
** Description changed:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many machines,
when the user should be seeing only the BIOS logo and/or Plymouth splash
screens.
[ Workaround ]
On most machines you can hide the problem by using these kernel parameter
Seems it's fairly easy to make a working solution in initramfs-tools
alone, but there's a compromise. If I only include tiny/simple
framebuffer drivers in initrd then i915 starts so late that Plymouth
doesn't use it, and bug 2054769 can occur on some machines. If I include
all the current drm drive
Plymouth would still need patching in order to optimize the drm modules
in debian/local/plymouth.hook
** Changed in: plymouth (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syst
s-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Low
** Changed in: initramfs-tools (Ubuntu)
Statu
I think the delay I'm seeing is a feature of Plymouth, not a bug:
"ignoring since we only handle SimpleDRM devices after timeout"
As much as I dislike it perpetuating bug 1869655, this feature does
prevent bug 2054769 from reoccurring.
But this raises the question: is it worth putting i915, am
*** This bug is a duplicate of bug 1961508 ***
https://bugs.launchpad.net/bugs/1961508
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1961508, so it is being marked as such. Please look
Since this bug has expired it would be useful to get a fresh bug report.
Please run:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1761382
Title:
U
Fedora 39:
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
Ubuntu 24.04:
# CONFIG_FB_VESA is not set
# CONFIG_FB_EFI is not set
In the kernel source, DRM_SIMPLEDRM recommends SYSFB_SIMPLEFB if you
want it to work on UEFI and VESA. And we do enable SYSFB_SIMPLEFB whose
help text says:
> you should still keep
If by "yes" in comment #1 you mean the same issue occurs with wired,
then it sounds like there are two separate bugs. Because in comment #2
it sounds like PulseAudio's Bluetooth support was the original problem.
And I know other people have reported the same. It's unfortunate that
Ubuntu 22.04 was
That might explain the strange behaviour I'm seeing where simpledrm
doesn't seem to be usable until a few seconds into the boot (maybe not
till i915drmfb is mentioned in the log?).
/boot/config-6.8.0-11-generic:# CONFIG_FB_EFI is not set
It was removed as part of bug 1965303. But I was hoping sim
** Bug watch added: Debian Bug tracker #1064123
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123
** Also affects: mesa (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Hopefully I'm wrong about the need for all the 'tiny' drivers and
simpledrm is in a class of its own. But I'd like to better understand
what the backend of simpledrm is and how much we can assume that it will
just work(tm).
--
You received this bug notification because you are a member of Ubuntu
Also hooks/plymouth is equally to blame and needs modifying, as
mentioned in comment #49 which I forgot.
Looking at my older 6.6 kernel however I'm reminded that some kernels
may have the drivers we need in the form of tiny drm (which is the
backend for simpledrm??):
/lib/modules/6.6.0-14-gener
> * hooks/framebuffer can be totally removed.
By chance I was testing on a desktop that has the Nvidia driver
installed (though no Nvidia card today, Intel only). Disabling
hooks/framebuffer had relatively little impact. In the end it was
hooks/framebuffer-nvidia that also needed disabling to remo
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
--
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/1970069
Title:
Annoying boot messages interfering
Thanks for the bug report. This is a common problem and is almost always
due to a bad connection or low quality cable. Please try unplugging and
replugging the cable at both ends. If that doesn't solve it then please
try a different cable. For better performance and reliability on a
Lenovo G50-70,
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
This looks like just bad UI design. The option to include the pointer
already exists but it's disabled by default and not obvious because the
button looks exactly like the mouse pointer itself (bottom right of the
dialog). Please select that option in the screen recorder dialog before
starting the
Please check the headphone is in pairing mode, and try pairing something
else like a mouse if you can.
I can see only one other bug with the same Bluetooth chip having similar
issues: bug 1887968
** Summary changed:
- i could not able to connect my bluetooth headphone or for context any
headpho
This suggests the menu is an override-redirect X11 window, so perhaps
appearing on all workspaces is 'correct' and it is a bug in Firefox.
Please also try logging into a Wayland session.
** Package changed: xorg (Ubuntu) => firefox (Ubuntu)
** Changed in: firefox (Ubuntu)
Status: New => I
*** This bug is a duplicate of bug 1961508 ***
https://bugs.launchpad.net/bugs/1961508
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1961508, so it is being marked as such. Please look
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2053228, so it is being marked as such. Please look
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2053228, so it is being marked as such. Please look
** Changed in: initramfs-tools (Ubuntu)
Status: Opinion => New
--
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/1970069
Title:
Annoying boot messages interfering with
I encountered the same kind of corruption on AMD graphics last night.
Using Firefox on Wayland in Ubuntu 24.04.
--
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
Title:
Maybe initramfs-tools does still need changing. plymouth-start.service
seems to run twice, and I get the feeling only the second instance is
actually succeeding in splashing on screen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
You can test if the above suggestion will work for you by adding these
kernel parameters:
loglevel=3 fsck.mode=skip
--
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/1970069
I've analysed a couple of Noble systems today and don't think initramfs-
tools needs improving (although it might not hurt). On both systems,
plymouth-start was within 1 second of simpledrm starting (same
timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences the
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs
Similar, yes. But we can't treat them as the same bug when one was
declared fixed in Firefox in September 2023, and the other declared a
problem in Firefox in February 2024.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mes
Tracked down the cause to the Docker host, which runs on jammy, not
knowing about fchmodat2(). The syscall should normally return ENOTSUP
when called with AT_SYMLINK_NOFOLLOW on Linux, but the Docker seccomp
profile causes it to return EPERM, which confuses tar(1). Closing.
** Changed in: tar (Ubu
Public bug reported:
This concerns tar 1.35+dfsg-3 in Ubuntu noble. This does NOT affect tar
1.34+dfsg-1.2ubuntu1.1 in mantic.
I'm seeing errors like this:
$ tar xvJf /extern/source/chromium_122.0.6261.111.orig.tar.xz --wildcards
chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca
Does the problem occur if Firefox is never opened?
Do you find any files in /var/crash ?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Please open the Additional Drivers app and use it to install an Nvidia
driver. Then reboot and tell us if the problem persists.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Summary changed:
- Xorg freeze
+ Freeze
--
You received this b
This sounds like a per-application bug, but also something we would like
gnome-font-viewer to handle.
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- Choosing font
+ Apps can't handle tens of thousands of fonts installed at once
** Package changed: xorg (Ubunt
This bug is closed. But also please refrain from reporting multiple
different issues at the same time.
The current problem with a blank window is being tracked in:
https://github.com/canonical/ubuntu-desktop-installer/issues/2418
For everything else, please open new bugs.
** Bug watch added: git
Noble is now shipping with SimpleDRM enabled in kernel 6.8, so the next
step is comment #49 (which would also resolve bug 1869655).
--
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/
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2055779
When reporting bugs in the future please use apport by using 'ubuntu-
bu
mesa (24.0.2-1ubuntu1) noble; urgency=medium
* Merge from Debian.
* radeon-fix-gnome-shell-crash.diff: Fix a regression crashing
gnome-shell. (LP: #2054851)
-- Timo Aaltonen Thu, 29 Feb 2024 09:40:21 +0200
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix Committed
** Cha
Also focal (20.04.6) does have the bug now, per comment #23.
** Tags added: focal
--
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/1970069
Title:
Annoying boot messages int
Bug 2016925 suggests the problem went away in Ubuntu 23.10
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Tags added: amdgpu
** Summary changed:
- firefox screen corruption on Athlon 200GE after fresh installation of 22.04.4
+ [amdgpu] Firefox screen corruption on Athlo
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2055351
When reporting bugs in the future please use apport by using 'ubuntu-
This bug is currently hidden behind bug 1970069, but I do remember this
one. And it still happens on a small minority of machines. It would
happen for everyone if we fixed bug 1970069.
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notific
It looks like the above code might not need /dev/console at all. It
should be possible to modify it to use a private pipe for fsck's stdout.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launc
I'm starting to suspect our patch (comment #39) isn't directly to blame
for the systemd issue. Disabling or otherwise breaking systemd-
fsckd.service doesn't stop fsck output from polluting the console and
triggering this bug. Only skipping fsck avoids it. You can skip fsck
using 'fastboot' or 'fsc
Please don't attach crash files to bugs because it's a security risk for
yourself. Instead run:
ubuntu-bug /var/crash/YOURFILE.crash
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
** Attachment removed: "_usr_bin_nautilus.1000.crash"
https
** Changed in: systemd (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: systemd (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a me
** Tags removed: flickerfree
** Tags added: flickerfreeboot
--
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/1914409
Title:
fsck integration is not flicker free
Status in s
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
Thanks for the bug report.
Each time you experience a failed boot followed by a successful boot
please run:
journalctl -b-1 > failedboot.txt
And each time you experience a slow boot please run:
journalctl -b0 > slowboot.txt
and attach the resulting text files here.
** Summary changed:
-
There are lots of amdgpu errors in your system log, so let's start
there.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
http
CurrentDmesg.txt shows the Nvidia kernel driver crashing, which is
probably not helpful. But also...
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 st
** Summary changed:
- gnome-shell crashed with SIGSEGV in radeon_bo_reference()
+ gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
** Tags added: rls-nn-incoming
** Summary changed:
- gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
+ [radeon] gnome-shell
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
** Package changed: xorg (Ubuntu) => gnome-remote-desktop (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/2054859
Title:
VNC connection issues with 22.04
Status in g
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1922047
Title:
Touchpad scrolling is too fast
Status in Mozilla Firefox:
Fix Released
Status in GTK+
*** This bug is a duplicate of bug 2054121 ***
https://bugs.launchpad.net/bugs/2054121
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2054121, so it is being marked as such. Please look
Tracking upstream in:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613
** Information type changed from Private to Public
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in radeon_bo_reference()
** Package changed: gnome-shell (Ubuntu) => mesa (U
*** This bug is a duplicate of bug 2054121 ***
https://bugs.launchpad.net/bugs/2054121
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2054121, so it is being marked as such. Please look
The tracker-extract crash may be bug 1990630 or bug 1962585, because it
looks like both fixes haven't made it into jammy yet. But also this bug
list probably needs some maintenance:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners
The gnome-shell crash is now tracked in bug 2054761.
--
Y
** Tags removed: kinetic lunar
** Tags added: udeng-2004
--
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/1970069
Title:
Annoying boot messages interfering with splash scree
Next time the problem happens please:
1. Reboot.
2. Run:
journalctl -b-1 > prevboot.txt
3. Attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ Xorg freeze: i915 flips and commits are timing out
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
** Changed i
Please use 'ubuntu-bug' to report each crash file so the robots can
analyse and classify them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/2054319
Title:
System ins
Same for Weston 13.0. But since it's Nvidia asking, maybe we can help
some other way?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2053235
Title:
Upgrade libwayland to 1
*** This bug is a duplicate of bug 2037015 ***
https://bugs.launchpad.net/bugs/2037015
If it's just appeared in 22.04.4 then Mesa might be to blame, but this looks
more likely:
https://launchpad.net/ubuntu/+source/webkit2gtk/2.42.5-0ubuntu0.22.04.2
--
You received this bug notification beca
Same issue in Yelp (the Help app) when in Xorg sessions. So I think this
is a webkit2gtk bug that only manifests on Xorg (like our installer/live
sessions).
Also I have removed the series targets because they were getting
cluttered and likely targeting the wrong package anyway.
** Also affects: w
*** This bug is a duplicate of bug 2037015 ***
https://bugs.launchpad.net/bugs/2037015
** This bug has been marked a duplicate of bug 2037015
Screen corruption of slides during install on Raspberry Pi 4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Description changed:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many machines,
when the user should be seeing only the BIOS logo and/or Plymouth splash
screens.
+ [ Workaround ]
+
+ On most machines you can hide the problem by using these kernel parameter
201 - 300 of 1024 matches
Mail list logo