There is no "cursor ghost" that I can see in that image. Try viewing the
screenshot on a different monitor.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Because being an interactive user proves you have some authority to
consume GPU time.
Being a non-interactive user can include compromised daemons for
example.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu
My concern with 0666 is that it means any process can consume the GPU.
And invisibly because they are no longer guaranteed to be a login with
an obvious entitlement to the display.
IMHO the best middleground would be to grant remote/headless logins the
same access as local logins. Keep it at 0660.
You may require either the bluez fix that is in proposed for bug
2092158:
https://launchpad.net/ubuntu/+source/bluez/5.79-2ubuntu1.1
or a future kernel fix being tracked in bug 2113469.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
** Changed in: glib2.0 (Ubuntu Plucky)
Milestone: None => plucky-updates
** Changed in: glib2.0 (Ubuntu)
Milestone: None => ubuntu-25.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.
** Changed in: packagekit (Ubuntu)
Importance: Undecided => Medium
** Changed in: packagekit (Ubuntu Noble)
Importance: Undecided => Medium
** Tags added: desktop-needs-sru
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Tags added: noble
--
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/2104331
Title:
empty warning msg
Status in software-properties package in Ubuntu:
New
B
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.04 (focal) reached end-of-standard-support in May 2025.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it anymor
This bug is closed. I suggest subscribing to bug 2092158 instead, and
you can try the proposed fix for that at:
https://launchpad.net/ubuntu/+source/bluez/5.72-0ubuntu5.3/+build/30919292
Users of kernel 6.14 may also be experiencing bug 2113469.
--
You received this bug notification because you
Public bug reported:
Sync bluez 5.83-1 from Debian, when it's ready.
The only patch Ubuntu is carrying has been upstreamed in 5.83 so we can
return to pure Debian packages.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: questing
--
You received this bug n
Can you give a list of the filesystems you want to block (or allow if
that's shorter)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/2114945
Title:
block less common filesys
Does that mean verification is now complete?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpciaccess in Ubuntu.
https://bugs.launchpad.net/bugs/2111684
Title:
[SRU] Xorg AMD platform A + N config selected wrong primary
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
Mahesh, I think bug 1978905 may be relevant to you. There is a fix in
proposed, in particular libmutter-14-0 version 46.2-1ubuntu0.24.04.9:
https://launchpad.net/ubuntu/+source/mutter/46.2-1ubuntu0.24.04.9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
The patch mentioned in comment #4 doesn't seem to exist anymore. It got
upstreamed in systemd 242 so we're already widely releasing it.
--
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.
Public bug reported:
In Questing we no longer have all-graphical splash screens prior to the
login screen. There is an fsck "clean" message on the console causing
the system to switch to text mode during boot.
This is a regression of bug 1970069 in 25.10, which was fully resolved
in 24.04.
** Af
The new issue has moved to bug 2114116 now.
IIRC, shutdown splash is affected by what happened during startup. That
is whether or not the console had to be taken over to display any
messages during startup, or whether you used text mode switching to any
VTs.
Another issue is speed. If Plymouth do
Ah sorry, #106 was too long so #105 scrolled off the screen.
Given this bug already had an initramfs-tools fix, and this comment
history is so long, I will move to a new bug 2114116.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification
Are you trying to use the audio through HDMI/DP or the regular
speaker/headphone?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2113991
Title:
Crackly audo after updat
** Changed in: bluez (Ubuntu)
Status: New => Invalid
** Summary changed:
- Logitech MX Anywhere and MX Keys need to re-pair after suspend after
upgrading to 25.04
+ Logitech MX Anywhere and MX Keys need to re-pair after suspend after
upgrading to kernel 6.14
--
You received this bug no
Sadly, systemd 257.6-1ubuntu1 didn't fix this. It only fixed bug
2113455.
This bug has returned after being masked for a while by bug 2113455. To
work around this bug 1970069 in Questing I have to use fsck.mode=skip.
So that sounds very much like a systemd issue still.
** Changed in: systemd (Ub
The boot splash is working again after the systemd update, but slightly
regressed so part of bug 1970069 has been reopened for that.
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Invalid
** Changed in: plymouth (Ubuntu)
Milestone: ubuntu-25.10 => None
--
You received this bug
** Changed in: systemd (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/2113455
Title:
Boot splash is missing since ply
** Tags added: xrandr-scaling
** Package changed: xorg (Ubuntu) => mutter (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/2113859
Title:
Wrong font scaling with mult
Can you boot a LiveUSB of Ubuntu 25.04 and the file bug from there?
--
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/2113777
Title:
Intel Meteor Lake only HDMI audio det
These Ubuntu releases are no longer supported. Please open new bugs for
any issues you find.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING is ignored on 24.04 so it can't be
helping... It must be MUTTER_DEBUG_USE_KMS_MODIFIERS=0 helping you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpa
It looks like the Toshiba hard disk might be the bottleneck as the
system log is flooded with UFW (firewall) messages. Try this:
sudo ufw logging off
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification beca
Sounds like bug 2093824, but you already have that fix.
I don't think it makes sense to blame glib when it's just reporting a
descriptor leak. Such a leak is more likely to be the app's fault.
** Also affects: fwupd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug n
These commands might help you figure out what's going on. Try running
them on a fast boot and a slow one and comparing.
systemd-analyze
systemd-analyze blame
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
htt
The "MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING" option only exists in Ubuntu
22.04. It has changed names a couple of times since then, but I doubt
that was actually fixing your issue. More likely it is
MUTTER_DEBUG_USE_KMS_MODIFIERS=0 helping. But since it sounds like
you're on 22.04 then there could b
Please consider upstreaming when ready:
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/62
** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #62
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/62
** Also affects: plymouth via
https://gitlab.freedeskto
** Changed in: systemd (Ubuntu)
Status: Fix Committed => 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 interferin
Those patches need work. If plucky does get "0.17-3ubuntu1" then noble
can't get the same version.
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to li
** Tags removed: focal
--
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/1698083
Title:
Maximize vertically/horizontally doesn't work (in some apps) if
configured via middl
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-25.10
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubun
"Failed to connect to system scope bus via local transport: Connection
refused"
Probably duplicate of bug 207
--
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/2112233
Tit
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/plymouth/+git/plymouth/+merge/485641
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-25.10
** Changed in: plymouth (Ubuntu)
Milestone: None => ubuntu-25.10
** Changed in: plymouth (Ubuntu)
Sta
The attached Xrandr.txt file shows this monitor is detected:
000022f0233101010101
22190103803420782a4ca5a7554da226
105054210800b30095008100d1c0a9c0
81c0a9408180283c80a070b023403020
36000644211a00fd00323c1f
5011000a20202020202000fc0048
502045323431690a202020200
@jchittum: This person isn't even running Pulseaudio. The Alsa info is already
attached
Codec: Realtek ALC889
Maybe they should turn the headphone volume up in alsamixer?
Simple mixer control 'Headphone',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Pl
It looks like Nvidia is your primary GPU so I'm guessing you just need
the fix for bug 1876632, coming soon.
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-570
(Ubuntu)
** Tags added: nvidia suspend-resume
--
You received this bug notification because you are a member of Ubuntu
To
** Summary changed:
- screen corruption
+ [amdgpu] screen corruption
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: amdgpu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
Can you elaborate on what is saying "no detected bios"?
--
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/2111748
Title:
Ubuntu 24.04 not booting after installation no detected
Also how did you report this bug if it's not booting?
** 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 subscribed to xorg in Ubuntu.
https:/
** Summary changed:
- touchpad
+ [Lenovo 14w Gen 2] Touchpad doesn't work
** Package changed: xorg (Ubuntu) => linux-hwe-6.11 (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.ne
** Tags added: fixed-in-mesa-25.0.6 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/2101817
Title:
gnome-shell crashed with SIGSEGV in drisw_init_screen() from
> Secure-boot is enabled and the NVIDIA drivers are installed but not
signed.
I see kernel messages in peoples' logs suggesting that's the case fairly
regularly. Also I get the impression our list of kernel versions for
which Canonical has signed modules is too small. Not just because some
people
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
Reopened for Mesa, following
https://gitlab.freedesktop.org/mesa/mesa/-/issues/12080
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #12080
https://gitlab.freedesktop.org/mesa/mesa/-/issues/12080
** Changed in: mesa
Status: Fix Released => Unknown
** Changed in: mesa
Rem
I'll mark this report 'Incomplete' in case you continue to have issues
(and changing to alsa-driver since you're not running pulseaudio).
If your system continues to function correctly, you do not need to do
anything here, and this report will close in 60 days.
** Package changed: pulseaudio (Ubu
So did that solve the issue entirely? I was thinking it would solve your
issues with headphones, but I didn't think it would help with the
speakers (when headphones aren't plugged in).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Please run the following command on the system in question to gather
information:
apport-collect 2111500
** Package changed: ubuntu => alsa-driver (Ubuntu)
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ub
Failing to open Bluetooth settings and failing to reconnect
automatically sound like different issues. Which one would you like this
bug to be about?
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Nvidia kernel module is not loading (no kernel module in use listed).
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD107GLM [RTX 2000
Ada Generation Laptop GPU]
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
Do you have SecureBoot enabled? If so, did you sign the N
*** This bug is a duplicate of bug 2109992 ***
https://bugs.launchpad.net/bugs/2109992
** This bug has been marked a duplicate of bug 2109992
laptop xorg freeze USB stick memory is 2 GT installation freeze
--
You received this bug notification because you are a member of Ubuntu
Touch see
See also
https://bugs.launchpad.net/ubuntu/+source/qt6-tools/+bug/2084278
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtchooser in Ubuntu.
https://bugs.launchpad.net/bugs/1964763
Title:
QtChooser doesn't support qt6
St
** Package changed: python-apt (Ubuntu) => linux-restricted-signatures-
lowlatency-hwe-6.11 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/2110031
Title:
Recen
Thanks for the bug report. If you experience any more freezes after installing
then please follow:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
If the machine only has 2GB of RAM then that might also explain the
problem. Because I know from experienc
"No provider of glFenceSync found" is from libepoxy, which is used by
GTK and others.
--
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/2047739
Title:
Flutter apps crash with
It looks like the kernel is failing to install the required firmware.
** Package changed: bluez (Ubuntu) => linux (Ubuntu)
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
** Summary changed:
- snap-store crashes with core dumped upon opening [No provider of glFenceSync
found]
+ Flutter apps crash with "No provider of glFenceSync found"
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Bug watch added: github.com/canonical/desktop-security-center/issues #81
https://github.com/canonical/desktop-security-center/issues/81
** Also affects: desktop-security-center via
https://github.com/canonical/desktop-security-center/issues/81
Importance: Unknown
Status: Unknown
Thanks for the bug report. On a fresh restart while the monitor is still
not detected, please run:
sudo apt install drm-info
drm_info > drminfo.txt
grep . /sys/class/drm/*/status > drm-status.txt
lspci -k > lspci-all.txt
journalctl -b0 > journal.txt
and attach the resulting text files h
It sounds like a problem with PSR (panel self refresh). To test that
theory try disabling PSR by adding a kernel parameter:
GRUB_CMDLINE_LINUX="i915.enable_psr=0"
in /etc/default/grub and then run:
sudo update-grub
and reboot.
If the problem isn't solved then check the parameter has been a
** Changed in: totem (Ubuntu Oracular)
Milestone: ubuntu-24.10 => oracular-updates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/2060730
Title:
totem cannot instal
It's all to do with which GPU the port is physically wired to. In most
cases it's the Intel chipset wired to USB-C (and the laptop panel), so
any monitor connected to that shows up as directly connected to the
Intel GPU. In most cases on a dual GPU laptop, the HDMI port is wired to
the discrete (Nv
Interesting to see simpledrm (software rendering) being used for the
integrated GPU there, and yet nvidia-drm is still active for the
discrete GPU. Presumably you ran that command in recovery mode. So I'm
surprised you get a working hybrid GPU configuration from simpledrm but
not from i915.
It sti
It looks like Ubuntu/Debian patches should be proposed to
https://salsa.debian.org/gnome-team/glib instead of Launchpad.
** Tags added: fixed-in-glib-2.85 fixed-upstream
** Changed in: glib2.0 (Ubuntu)
Milestone: None => ubuntu-25.10
--
You received this bug notification because you are a m
** Bug watch added: gitlab.gnome.org/GNOME/dconf/-/issues #76
https://gitlab.gnome.org/GNOME/dconf/-/issues/76
** Also affects: glib via
https://gitlab.gnome.org/GNOME/dconf/-/issues/76
Importance: Unknown
Status: Unknown
** Project changed: glib => dconf
--
You received this bu
Attached is `journalctl -u avahi-daemon --boot -0 > avahi-
journalctl.txt`.
I find lines "Host name conflict, retrying with daniel-desktop3-2" and
"Detected another IPv4 mDNS stack running on this host" strange. They
didn't happen last boot. I left `/etc/systemd/reso
Public bug reported:
After suspending and resuming my desktop, my tablet could not resolve
its hostname over mDNS. `getent hosts daniel-desktop3.local` has no
output. Wireshark on the desktop captured incoming mDNS packets but no
outgoing response. Disconnecting/reconnecting the desktop&#
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2108973
Title:
libglib2.0-dev:i386 dependency issue
Status in glib2.0 package in Ubuntu:
New
Bug de
** Description changed:
After the latest apt mirror update on 2025-04-22 21:35:15 UTC some of
the i386 libglib2 packages broke for our 24.04 LTS systems running
x86_64
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are usi
That's a good catch. I didn't notice that it works correctly with a
24.04 container on a 24.10 host, which is very odd. I've just tested it
myself to ensure consistent behaviour.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Since you have two graphics "cards" (NB2 and pvr) it's possible only one
is really required. And the other will forever log messages about
LLVM... Although "libLLVM-14.so.1: cannot open shared object file" is
fairly definitive - does that file exist at all?
Please note that we no longer support Li
It's been suggested this is fixed in GNOME 48 (Ubuntu 25.04). Can anyone
confirm?
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #841
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/841
** Also affects: gnome-settings-daemon via
https://gitlab.gnome.
** Summary changed:
- gnome-shell crashed with SIGABRT in amdgpu_ctx_set_sw_reset_status() from
amdgpu_cs_submit_ib() from util_queue_thread_func() from impl_thrd_routine()
from start_thread()
+ Crash with SIGABRT in amdgpu_ctx_set_sw_reset_status() from
amdgpu_cs_submit_ib() from util_queue_th
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags added: nvidia x11
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
**
That many busy threads in gnome-shell either means it's using LLVM
(software rendering) or there's a buggy extension.
Please run:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and log in again. If that hasn't fixed it then run:
journalctl -b0 > journal.txt
and attach the resulting tex
** Description changed:
From the host (24.10)
```
$ lxc launch ubuntu:24.04 test-container
Launching test-container
$ lxc shell test-container
root@test-container:~# sudo systemd-creds encrypt --name mysecret - - <<<
"This is my secret"
Whxqht+dQJax1aZeCGLxmiABDB
Public bug reported:
From the host (24.10)
```
$ lxc launch ubuntu:24.04 test-container
Launching test-container
$ lxc shell test-container
root@test-container:~# sudo systemd-creds encrypt --name mysecret - - <<< "This
is my secret"
Whxqht+dQJax1aZeCGLxmiABDBBlMLRMJ/Z7up70ybYAAA
** Changed in: bluez (Ubuntu Plucky)
Status: In Progress => Fix Released
** Changed in: bluez (Ubuntu Plucky)
Milestone: None => ubuntu-25.04
** Changed in: bluez (Ubuntu Oracular)
Status: In Progress => Fix Committed
** Changed in: bluez (Ubuntu Oracular)
Milestone: None =
** Tags added: udeng-6791
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1869655
Title:
Boot splash starts too late to be useful
Status in Plymouth:
New
Status
Thanks for the bug report.
After the problem happens next, please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Tags added: nvidia
--
You received this bug no
You'll need a 6.14 kernel for the speakers:
https://github.com/tiwai/sound/commit/f479ecc5ef15ed8d774968c1a8726a49420f11a0
For headphone, it shows your headphone contol as being off. See if you
can fix it in alsamixer.
Simple mixer control 'Headphone',0
Front Left: Playback 87 [100%] [0.00dB] [
Please run the following command to gather info:
apport-collect 2107274
** Package changed: linux-firmware (Ubuntu) => alsa-driver (Ubuntu)
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I suspect this bug is the reason Jammy is reporting so many more crashes
than the other supported series. So I'm going to say 'desktop-needs-sru'
but Jammy would need a completely different fix to the others because it
uses GTK3.
** Also affects: nautilus (Ubuntu Plucky)
Importance: Low
** Summary changed:
-
/usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_unref:expiry_func:g_timeout_dispatch:g_main_dispatch
+ gnome-shell crashed with SIGSEGV in
g_type_check_instance_is_fundamentally_a() from g_object_unref() from
expiry_func() from g_timeout_dispatch(
I can see errors coming from your kernel graphics driver so that's
probably the culprit. Can you provide a photo or video of the problem?
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Changed in: linux-hwe-6.8 (Ubuntu)
Status: New => Incomplete
** Summary changed:
- blin
*** This bug is a duplicate of bug 2106722 ***
https://bugs.launchpad.net/bugs/2106722
** This bug has been marked a duplicate of bug 2106722
Xorg freeze
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
The main fix required here is tracked in Mutter.
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: mutter (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
** Summary changed:
- software updater crush
+ software updater crash
** Description changed:
- Hello I wanted to update the system as I do every-time I open my laptop But
it can not update , and I receive the message that the updater has crushed.In
the Terminal it gave this :E: Malformed entr
Please show the contents of the problematic file:
/etc/apt/sources.list.d/third-party.sources
** Changed in: software-properties (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to softwa
https://launchpad.net/ubuntu/+source/mesa/25.0.3-1ubuntu2
** Changed in: mesa (Ubuntu)
Status: In Progress => Fix Committed
--
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/bu
Public bug reported:
After switching from lightdm (which sources /etc/profile) to gdm, gdb
stopped offering debuginfod. Workarounds are SSH, TTY, and a manual
`export DEBUGINFOD_URLS="https://debuginfod.ubuntu.com"`.
$ lsb_release -rd
Description:Ubuntu 24.10
Release:24.10
$ apt-cach
That can be done by having the profile.d script instead echo the
variables as a systemd.environment-generator. Alternatively, the
variables can be cached on postinst.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in
Please double check /proc/cmdline to ensure xe.enable_psr=0 is present.
** Also affects: linux-hwe-6.11 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Top of screen (date & time and notificati
You seem to have a very large number of packages from "origin: unknown"
or from PPAs. That means they're not the Ubuntu supported software
packages...
If you don't know how to fix this manually, please reinstall Ubuntu from
scratch before reporting bugs. And be sure to avoid using PPAs or
prerelea
Hi Wl-dustin,
Note that comment #26 has a more general fix (define has_option() in an
Xsession.d file if it's not already defined). There appear to be various
other X session scripts likewise neglecting to define it.
--
You received this bug notification because you are a member of Ubuntu
Touch
Those images show low-level rendering problems which are the kernel and
Mesa's responsibility.
Personally I've only found Lunar Lake to work reliably with Ubuntu 25.04
but that's not even due for release until later this month. Still, you
can try it at https://cdimage.ubuntu.com/daily-live/
** No
1 - 100 of 1385 matches
Mail list logo
