** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Summary changed:
- [drm] *ERROR* flip_done timed out
+ [amdgpu][drm] *ERROR* flip_done timed out
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Summary changed:
- Screen brightness
+ [Lenovo IdeaPad Z500] Screen brightness
** Summary changed:
- [Lenovo IdeaPad Z500] Screen brightness
+ [Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and I can't
change it
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
Only the kernel can crash that hard, so reassigning there.
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (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/2047388
T
What is the make and model of the machine? It seems to identify itself
as "Default string".
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Changed in: bluez (Ubuntu)
Status: Triaged => In Progress
--
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/2047780
Title:
BlueZ release 5.71
Status in bluez package
** Attachment added: "bluez_5.71.orig.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5735864/+files/bluez_5.71.orig.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Updated source files are attached above. And the source is in:
https://git.launchpad.net/~bluetooth/bluez/log/
--
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/2047780
Title:
** Attachment added: "bluez_5.71-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5735865/+files/bluez_5.71-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Here's the debdiff. We don't usually use them for major updates though
because of the size. 34174 lines in this case is not plausibly
reviewable.
** Patch added: "bluez_5.71-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5736020/+files/bluez_5.71-0u
It's usually Seb sponsoring these, but he's on vacation. To avoid any
future complaints in case he's away again I will also include debdiffs
in future.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://b
The build is failing:
https://launchpad.net/ubuntu/+source/bluez/5.71-0ubuntu1
But I don't know how to reproduce the failure. Certainly it builds on
both noble and mantic, and installs, and works for me. Is this because
Launchpad is using a focal toolchain?
--
You received this bug notification
** Summary changed:
- Screen crashes in a wierd way
+ [amdgpu] Screen crashes in a weird way
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
Turns out it's not as simple as the above comments suggest.
> https://salsa.debian.org/systemd-team/systemd/-/commit/ee83b5721
> https://salsa.debian.org/DebianOnMobile-team/modemmanager/-/commit/367180c3
udev changes are not relevant to the failures in
https://launchpad.net/ubuntu/+source/bluez/
I appreciate everyone is frustrated. BlueZ isn't really staffed, it's
just something I look at once or twice a year. The diff to Debian is
shrinking over the long term, but again that's something I don't look at
very often.
The justification for Ubuntu using a separate process for the past 6 years
It looks like most of you are members of ~bluetooth already via ~ubuntu-
core-dev so feel free to commit directly to
https://git.launchpad.net/~bluetooth/bluez in future.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez i
Thank you for working over the weekend on this. I would have resolved it
myself on the Monday if someone answered the question in comment #11.
Also I've sent a bug report to Debian about their orig tarball not
matching the upstream release tarball. I feel that's a discussion they
need to have with
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Fix Released
** Tags removed: fixed-in-mesa-23.3
** Tags added: fixed-in-mesa-23.3.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.la
** Description changed:
+ [ Workaround ]
+
+ 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
+ 2. Run: systemctl restart bluetooth # or reboot
+
+ [ Original Description ]
+
Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
to connect my PS3 Sixasis controll
Ideally please open a new bug for the merge. This bug should remain Fix
Released because we're already past the point in time when it was
released to Noble.
Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez
** Changed in: bluez (Ubuntu)
Status: I
BTW, having the previous Ubuntu version 5.71-0ubuntu3 on line 415 of the
changelog doesn't feel ideal for people wanting to read the Ubuntu
release history.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
http
> Force pushing my local commits over, sorry not sorry. :)
Yeah it's fine this time. :)
--
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/2047780
Title:
BlueZ release 5.71
St
From what I read of overnight discussions, it is believed that Mesa
23.3.3 has a fix. Looks like some kind of GLX protocol breakage happened
in 23.3.0?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Fix Committed
--
** Summary changed:
- ssh-agent fails to start (has_option: command not found)
+ Xorg scripts fail with "has_option: command not found"
--
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
See also bug 2049016.
--
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/1922414
Title:
Xorg scripts fail with "has_option: command not found"
Status in Light Display Manager:
The version of Mesa installed: 24.0.0.20231114.1-2088~22.04 is not
supported or provided by Ubuntu. We cannot fix any bugs it causes.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of
** Tags added: amdgpu
** Summary changed:
- Video does not output to second monitor
+ [amdgpu] Video does not output to second monitor
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
This appears to be a networking or server problem, so likely isn't a bug
we need to track here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
ver 5.72:
Fix issue with BAP and handling stream IO linking.
Fix issue with BAP and setup of multiple streams per endpoint.
Fix issue with AVDTP and potential incorrect transaction label.
Fix issue with A2DP and handling crash on suspend.
Let me know when it's safe to start work on LP: #2049352 for 5.72 or if
someone else wants to do it.
--
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/2047780
Title:
BlueZ rele
This is being tracked upstream in:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158
** Bug watch added: gitlab.freedesktop.org/wayland/wayland-protocols/-/issues
#158
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158
** Changed in: wayland (Ubuntu)
Xorg itself doesn't paint anything, it will start with a black window.
So it's likely to be a Xubuntu bug. Since it can't be reproduced then
let's leave it Incomplete and it will close automatically after two
months of inactivity.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
** Changed in: bluez (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 to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049352
Title:
Package BlueZ 5.72
** Changed in: mesa (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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2043915
Title:
Booting into live session results in t
** Changed in: bluez (Ubuntu)
Status: Triaged => In Progress
--
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/2049352
Title:
Package BlueZ 5.72 for Noble
Status in blu
Confirmed fix released in https://cdimage.ubuntu.com/daily-
live/20240116/
--
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
** Attachment added: "bluez_5.72.orig.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739877/+files/bluez_5.72.orig.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Patch added: "bluez_5.72-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739879/+files/bluez_5.72-0ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubu
** Attachment added: "bluez_5.72-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739878/+files/bluez_5.72-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Thanks, yes any failure to install now needs a separate bug report.
--
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/ins
Thanks for the bug report. I've watched the attached screencast a few
times and can't see any artifacts in it. This is unsurprising given how
screen recording works. You will probably need to take a video of the
screen externally, like with a phone.
** Summary changed:
- screen artifacts especia
Thanks for the bug report. It appears you no longer have an nvidia
kernel driver for the current kernel version. I'm also not sure if such
a newer kernel can be supported by the old nvidia 390 driver.
This might just be bug 1975650 so please try reinstalling the driver
using the 'Additional Driver
Thanks for the bug report. It looks like the i915 kernel graphics driver
is crashing a lot, which may or may not be related. Please run these
commands in a Terminal:
sudo apt install mesa-utils
glxinfo > glxinfo.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu)
Am I correct in assuming the problem goes away after a reboot?
--
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/2049708
Title:
bluez bluetoothd unable to locate executable
St
5.71-1ubuntu3:
Binary: /usr/libexec/bluetooth/bluetoothd
SystemD: system/bluetooth.service:ExecStart=/usr/libexec/bluetooth/bluetoothd
So that's consistent, but it sounds like you might have encountered an
upgrade bug and your systemd was looking in the old path? I'm guessing
there should be a sy
I can't seem to reproduce any such issue with 2024-01-17 here.
Please log a new bug, although it might be bug 2049617 as mentioned in
https://discourse.ubuntu.com/t/help-with-edubuntu-desktop-
installer/41683
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Perhaps try a recursive grep for '/usr/lib/bluetooth/bluetoothd'
--
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/2049708
Title:
bluez bluetoothd unable to locate executable
** Summary changed:
- display backlight
+ [Acer eMachines D725] Display backlight
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (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.launc
"Input/output error" is probably a USB connection issue, or a flash
drive error. Please try a different drive and/or different USB port.
** Package changed: bluez (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a me
** Summary changed:
- Can't change screen brightness
+ [HP Victus 15-fb0xxx] Can't change screen brightness
** 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
If it's software at all then this would be a kernel bug. But I suspect
the issue is more likely hardware since 1920x1080 @60Hz is pushing the
limits of analog VGA. Anything less than a perfect cable with perfect
connections and I'd expect display glitches like this.
Personally I'd recommend adding
** Package changed: bluez (Ubuntu) => 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/2049958
Title:
package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unabl
** Summary changed:
- brightness
+ [HP EliteBook 8560w] Can't change screen brightness
** 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.
https://bugs
Thanks for the bug report. 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
+ consistently fails to resume from suspend
** Package changed: xorg (Ubuntu) => ubuntu
** Changed
*** This bug is a duplicate of bug 2050954 ***
https://bugs.launchpad.net/bugs/2050954
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 2050954, so it is being marked as such. Please look
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
Please run:
apport-collect 2050040
so we can see more details about the software versions in use.
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
Thanks. Please try this command to see if it stops the problem:
gnome-extensions disable mediacontr...@cliffniff.github.com
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
You received this bug notifi
Please try this command to see if it stops the problem:
gnome-extensions disable mediacontr...@cliffniff.github.com
You should also avoid using 'sudo apt remove --purge' because it will
break the system even more.
--
You received this bug notification because you are a member of Ubuntu
Touch
Please try this command to see if it stops the problem:
gnome-extensions disable mediacontr...@cliffniff.github.com
--
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/20500
If you already had multiple keyboards associated with the machine then
this sounds like bug 108. Please try removing all but one keyboard
from the system.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Summary changed:
** Changed in: pulseaudio (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-15 fixed-upstream
--
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/15
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624
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 1924624, so it is being marked as such. Please look
Thanks for the bug report. It appears there are two problems here:
1. You are using the 'oibaf' PPA which is unsupported and is known to
cause graphics problems. Please uninstall it or at least don't report
bugs while it is installed.
2. There is a recent regression in the Intel kernel driver so
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
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624
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 1924624, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624
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 1924624, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1923347 ***
https://bugs.launchpad.net/bugs/1923347
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 1923347, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624
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 1924624, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624
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 1924624, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624
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 1924624, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624
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 1924624, so it is being marked as such. Please look
Thanks for the bug report. Next time the problem happens please run:
journalctl -b0 > journal.txt
or if you had to reboot then run:
journalctl -b-1 > prevjournal.txt
and attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ [nvidia] System freeze after power saving mod
** Summary changed:
- bluetooth just turning off and on and also disconnecting
+ [QCA9565] bluetooth just turning off and on and also disconnecting
** Package changed: bluez (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
Unfortunately the fix is still only in Mesa version 21.
--
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/1915870
Title:
gnome-shell/gnome-session-check-accelerated-gl-helper cr
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags added: nvidia
** Tags added: dualgpu hybrid
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
** Summary changed:
- Headphones don't work when speakers work
+ [ASUS ROG STRIX Z590-E] Headphones don't work when speakers work
--
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.ne
I wonder if this is bug 1897965 (again)? That's only fixed in 21.04
** Summary changed:
- headphone not correctly detected on 20.10
+ [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
--
You received this bug n
Thanks for the bug report. Your system seems to be experiencing a lot of
kernel crashes in the 'rtl8821ce' driver. Please try uninstalling that
and using the built-in driver (if available).
** Package changed: xorg (Ubuntu) => rtl8821ce (Ubuntu)
** Changed in: rtl8821ce (Ubuntu)
Status: In
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
Thanks for the bug report. It appears there was a kernel update a couple
of days before this bug was opened so I would investigate that first.
Please use the Escape key to access the boot menu and try selecting an
older kernel. Or try a different kernel version from here:
https://kernel.ubuntu.co
Alright, maybe it was bug 1897965 but Fix Released regardless.
** Changed in: pulseaudio (Ubuntu)
Status: New => Fix Released
--
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
^^^ Bug 1925320
--
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/1915870
Title:
gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
SIGSEGV in cso_destroy_cont
If the problem was /sys/module/snd_hda_intel/parameters/power_save then
this should be assigned to the kernel.
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Strange sound when speaker is muted
+ [Dell Vostro 3668] Strange sound when speaker is muted
--
You rec
** Summary changed:
- Display Error (hardware bug: Screen doesnt display on warm boot and turning
on after Suspend)
+ [Avita NS14A2] Screen doesn't display on warm boot and turning on after
Suspend (i915 :00:02.0: [drm] *ERROR* failed to enable link training)
** Package changed: xorg (Ubu
It appears 'amdgpu' is the wrong driver for this system. 'radeon' is the
correct driver. Maybe you had a config file that was forcefully loading
the wrong one?
** Summary changed:
- Incomplete display of text
+ [amdgpu] Incomplete display of text
** Package changed: xorg (Ubuntu) => xserver-xorg
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-460
(Ubuntu)
** Summary changed:
- display broken on logout
+ [nvidia] display broken on logout
** Changed in: nvidia-graphics-drivers-460 (Ubuntu
This sounds like an HDMI connection/signalling problem. Please check to
see if a direct connection (no receiver), and even a new cable, exhibits
the same problem.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Summary changed:
- Screen "disconnects" when updating screen buffer
+ [i
Next time the problem happens, after rebooting please run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
Please also follow these instructions to check for application crashes:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachmen
*** This bug is a duplicate of bug 1926084 ***
https://bugs.launchpad.net/bugs/1926084
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 1926084, so it is being marked as such. Please look
** Summary changed:
- Bluetooth speakers reconnect randomly
+ [hirsute] Bluetooth speakers reconnect randomly
--
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/1926084
Title:
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624
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 1924624, so it is being marked as such. Please look
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 1926770
When reporting bugs in the future please use apport by using 'ubuntu-
bu
** Tags added: regression-release
** Tags added: amdgpu
** Summary changed:
- After suspending, no video signal appears after waking up
+ [amdgpu] After suspending, no video signal appears after waking up
** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)
--
You received
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 1926095, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or
*** This bug is a duplicate of bug 1926062 ***
https://bugs.launchpad.net/bugs/1926062
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 1926062, so it is being marked as such. Please look
Since you say the current kernel for Ubuntu 20.04 does not have the
problem then it is considered Fix Released.
If there is a newer kernel that does still have the bug then you should
report it upstream, not here.
** Summary changed:
- [USB-Audio - Saffire 6 USB, playback] Sound is faster, high-
It sounds like you are getting spurious mouse button (or even keyboard)
events from one of your input devices, which will randomly break drag
operations. This does happen to people occasionally and in every case
(so far) it turns out to be a broken input device.
Please try unplugging all input dev
Thanks for the bug report. Next time the problem happens please reboot
and then run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
Although I notice the attached logs already show your SSD is
experiencing hardware errors. You might need to replace the SSD:
[ 1633.238
Which process is using 100% CPU?
I also wonder if this is related to bug 1924624...
** 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 subscr
Sounds like this is about graphics drivers. This system has an Intel GPU
so there are no additional graphics drivers. There is no bug here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: Incomplete => Invalid
--
You received this bug notification because you a
801 - 900 of 16692 matches
Mail list logo
