Incomplete: Waiting for the bug to reoccur... It sounds to me like a
kernel or hardware problem though, in which the device itself is
believed to have disappeared, and so would the dialog.
** Tags added: mantic
** Package changed: bluez (Ubuntu) => ubuntu
** Changed in: ubuntu
Status:
Please check that this isn't being caused by local extensions. You can
remove them by running:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. If the problem persists after that then please
run:
gnome-extensions list --enabled > extensions.txt
and attach the
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
It looks like the 'modesetting' Xorg driver is at fault, if we trust the
log message suggesting /dev/dri/card0 exists. Please run:
sudo apt install drm-info
sudo drm_info > drminfo.txt
and then attach the resulting text file here.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags added: amdgpu
** Tags added: flicker suspend-resume
** Summary changed:
- After screen turns off and you turn it back on, weird corruption
+ [amdgpu] After screen turns off and you turn it back on, weird corruption
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received
Patches sent (to multiple places per get_maintainer.pl):
https://lkml.org/lkml/2024/2/2/373
https://lkml.org/lkml/2024/2/2/375
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The blanking from GRUB_TIMEOUT>0 will be made much worse by
CONFIG_FB_EFI=n because usually in Ubuntu it's the efifb that restores
the logo after Grub has wiped it. I think not having CONFIG_FB_EFI at
the same time as using GRUB_TIMEOUT>0 explains your previous "really
long time of a black
GRUB_TIMEOUT > 0 also causes the vendor logo to be replaced by a black
screen, but that seems to be Grub's fault. Default Ubuntu won't have
that problem since it ships GRUB_TIMEOUT=0. And if you want a nonzero
timeout without the blackness then GRUB_TERMINAL=console is a
workaround.
--
You
This bug has been closed for over 14 years so if you have any current
issues then please open new bugs for each of them.
--
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/241000
I think that's a different bug. I believe it's when plymouthd is
starting and is the handover (mode set?) from efifb to DRM. It doesn't
happen at all if you add "nomodeset" (please try that).
"Really long time" might be subjective though? How long?
VT switches (or more accurately virtual console
Here's a no-compromises patch set. No bugs, no delays, it just does the
right thing.
If I haven't changed my mind again on Friday then it will be sent
upstream.
** Patch added: "lp1970069-patchset-20240201a.patch"
> You could detect both parameters to avoid that corner case.
Sure one can check for "splash nomodeset" to avoid the confusion in most
cases, but that wouldn't fix it for "splash $DRIVER.modeset=0" or less
common architectures which might have no primary framebuffer. I guess we
can tell people
BTW bug 2050743 is making the situation worse on noble. It will be fixed
shortly.
--
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
A new attempt at a kernel patch. While this is pleasingly simple and
reliable in my own testing, it has a bug when "splash" is used at the
same time as there being no primary framebuffer (like with "nomodeset").
I'm not sure if that's a realistic concern and am reluctant to go back
to delays to
Hmm, no plymouthd isn't starting quite early enough in Noble:
2.799s - plymouthd starts
4.080s - first show-splash attempt (rejected because DRM hasn't started yet)
5.290s - found /dev/dri/card0
5.364s - showing splash screen
What this means is that any attempt to fix the bug in plymouthd itself
Yes I learned that recently thanks. I'm building it on a noble desktop
(no proposed). Just apt-get source plymouth
--
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/2051765
Ah it's because the new systemd (which will fix this) is stuck in
proposed. To work around it you need to manually revert:
https://launchpadlibrarian.net/709437063/plymouth_23.360.11-0ubuntu1_23.360.11-0ubuntu2.diff.gz
** Changed in: plymouth (Ubuntu)
Status: New => In Progress
** Also
I'm not sure we even need Plymouth installed in initrd because the
device_timeout experiment mentioned in comment #18 suggests plymouthd
was starting early enough already. It's not the root filesystem that
takes too long to appear, but the i915/amdgpu drivers to fully
initialize. Also all this
Thanks for the bug report. It appears the graphics driver and Xorg are
working correctly here. And certainly I would not expect all modern
games to maintain 60 FPS on the integrated GPU of an Intel i3-1115G4.
As for the blurry HDMI output, the Samsung un32t4300 is limited to
1366x768 so a little
> I belive /usr/share/initrams-tools/hooks/plymouth can be modified to stop
> including any
> drm modules and /usr/share/initramfs-tools/framebuffer can be totally dropped.
Dropping the DRM modules would also allow us to use a near-zero
device_timeout in Plymouth now. It would then render to
** Package changed: xorg (Ubuntu) => xorg-server (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/2051694
Title:
Regression: Kubuntu 22.04 LTS overrides
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
--
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 screen
Status in linux package in Ubuntu:
In Progress
Thanks. So it still sounds like SimpleDRM is in Ubuntu's future (bug
1965303). But in case that doesn't happen in time for Noble, or if we
simply want a solution that backports to jammy, then I will still focus
on plymouth/kernel changes only.
--
You received this bug notification because you
"splash" is more appropriate than "quiet" (unfortunately) because we
would delay framebuffer takeover to the same event (primary DRM startup)
as Plymouth does.
I would also like to know why our Plymouth doesn't render on SimpleDRM
even when it's available (tested in bug 1965303). I don't really
It looks like the installation might have succeeded and just requires a
reboot. The error was:
Failed to start bluetooth.service: Unit bluetooth.service failed to load
properly, please adjust/correct and reload service manager: File exists
** Summary changed:
- package bluez 5.68-0ubuntu1.1
I now expect the kernel patch would change before it gets proposed to
dri-devel. In particular the primary delay doesn't need to be
configurable (or even finite?), and the secondary delay probably doesn't
need to be more than zero. But the feature would still be gated on the
"splash" kernel
** Changed in: plymouth (Ubuntu)
Status: Invalid => Confirmed
--
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 am also the author of the Plymouth feature that parses and renders the
fsck progress. What I think isn't being communicated here is that it's
currently useless on startup. Because Plymouth doesn't start rendering
until well after the fsck has already happened. See also bug 1869655.
--
You
You can use the 'fastboot' kernel parameter to bypass the systemd-fsckd
issue. So overall most systems can work around the bug in full using
kernel parameters:
quiet splash loglevel=2 fastboot
After that I've only encountered one weird laptop that refused to stay
silent (even with loglevel=0).
The userspace part of this bug is coming from our systemd patch:
debian/fsckd-daemon-for-inter-fsckd-communication.patch
In particular where systemd-fsckd.service says:
StandardOutput=journal+console
Is the patch still required at all, or can it be reordered to wait for
Plymouth to splash
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: 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
Looks like systemd failed and started timing out for multiple things
before this happened. So there's nothing bluez can do about that.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Please check to see if the kernel is getting the button events:
sudo apt install evtest
sudo evtest
** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu)
** Changed in: linux-raspi (Ubuntu)
Status: New => Incomplete
** Package changed: linux-raspi (Ubuntu) => linux (Ubuntu)
**
> Display resolution stuck at 800x600 after using nomodeset in grub.
> But my Dell monitor has 1600x900 resolution.
This is correct behaviour. "nomodeset" means to disable the graphics
driver and to disable high resolution support.
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
**
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
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
It looks like there are Bluetooth packet problems at the kernel level
(if not hardware), so reassigning there.
** Summary changed:
- blutooth
+ [BCM43142] Bluetooth headset disconnects
** Package changed: bluez (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because
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
is still very relevant
** Attachment added: "full .xsession-errors"
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/2047457/+attachment/5742804/+files/xsession-errors.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Thank you Mr. Eickmeyer for your fix in 23.04.
> notice how the askubuntu question was closed? That's because it was
offtopic/for an unsupported release
AskUbuntu closes questions as off-topic *because* they want those
questions to be *posted here* instead. It says "Bug reports and problems
Marked as confirmed as the real reporter is the asker on AskUbuntu, and
after my investigation, I confirm that this bug is reasonable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
Public bug reported:
This bug was migrated from https://askubuntu.com/q/1501240/1004020 .
A nearly identical bug is
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
default-settings`. Please add an analogous
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:
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.
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
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
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
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
*** 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
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
**
Hi georgiag, thank you for your command suggestion. Yes, it does fix my
issue.
I had a bunch of tabs open for months and finally closed them. After updating
Firefox and not restarting today, it seems that the postinst autoloaded the
AppArmor profile despite apparmor.service being disabled, so I
*** This bug is a duplicate of bug 2018439 ***
https://bugs.launchpad.net/bugs/2018439
There is a more official solution at
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2018439/comments/14
.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
*** This bug is a duplicate of bug 2018439 ***
https://bugs.launchpad.net/bugs/2018439
** This bug has been marked a duplicate of bug 2018439
Apparmor crashes GPU acceleration
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** 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.
** 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:
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
** 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
"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
** 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.
Public bug reported:
I am seeing this on Ubuntu noble with polkitd 123-3.
After debootstrap'ing a minimal system, I run
# apt-get install linux-generic
which pulls in polkitd as a dependency. In the output, I see the
following:
Setting up polkitd (123-3) ...
Creating group
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
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
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
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
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)
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
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
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
** 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
** 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
** 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.
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
** 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
** 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
** 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
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
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)
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
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.
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
** 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,
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
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:
** 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.
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
--
> 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
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.
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:
** 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
** 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.
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
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 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
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
** 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
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
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.
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"
** 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
201 - 300 of 18149 matches
Mail list logo
