** Summary changed:
- bose quietcomfort 35 unable to connect after suspend
+ Bluetooth headphones unable to connect after suspend
--
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/bug
Commit 83c6b2a was released already in gnome-shell 3.37.1
--
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/1962346
Title:
Ubuntu reboots instead of powering off if a soft
Ok. So it seems that the bug *exists* in Focal, so now we just need to
verify that the bug is *fixed* by the proposed package.
@angie78 - as you seem to suffer from the bug, can you try to verify
that the proposed packages (from
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/comment
** Attachment added: "Ubuntu dock overlapping a program after resume from
screen blank"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1962638/+attachment/5564720/+files/Screenshot%20from%202022-03-02%2008-42-37.png
** Description changed:
1) The release of Ubuntu you are using
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
- 21.10
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
ubuntu-desktop:
Installed: 1.472
Candidate: 1.472
Version tabl
Public bug reported:
tbb has been superceeded upstream in Debian and in its own development
as onetbb. This was recently sync'd to the archive. See
https://metadata.ftp-
master.debian.org/changelogs//main/o/onetbb/onetbb_2021.5.0-7_changelog
** Affects: tbb (Ubuntu)
Importance: Undecided
** Changed in: upower
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1962276
Title:
Laptop monitor does not turn off/disconnect when
> systemd should drop its setting to defer to the file that we have been
carrying in procps for a very long time.
at some point it would be a better idea to drop the procps files and
adjust the systemd defaults where/if needed. The sysctl configuration
hasn't been applied by procps since upstart;
Public bug reported:
Hi,
just updated from 21.10 to 22.04 and noticed my pulseUI VPN client fails with a
SIGSEGV. The core dump shows the following:
(gdb) backtrace
#0 0x0032 in ()
#1 0x7f7dd2b0c6c1 in () at /lib/x86_64-linux-gnu/libgstapp-1.0.so.0
#2 0x7f7dd13ee958 in _
This bug was fixed in the package gtk+3.0 - 3.24.20-0ubuntu1.1
---
gtk+3.0 (3.24.20-0ubuntu1.1) focal; urgency=medium
* debian/patches/git_rendering_issues.patch:
- cherry pick an upstream fix for opengl display issues when using
software rendering (lp: #1960947)
* debia
The verification of the Stable Release Update for gtk+3.0 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
** Patch added: "initramfs-tools-0.140ubuntu12..0.140ubuntu13.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+attachment/5564513/+files/initramfs-tools-0.140ubuntu12..0.140ubuntu13.debdiff
--
You received this bug notification because you are a member of Ubunt
Fixing the statement from the previous post, the feature had been not working
and was fixed in
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/83c6b2a
So yes, it's a regression and we need to decide on the best way forward
--
You received this bug notification because you are a member of Ub
Upstream seems to disagree with the IP_FREEBIND implementation, as per
https://bugzilla.samba.org/show_bug.cgi?id=13463. The reason behind it
is that the daemon should fail for invalid ip addresses.
Adding After=network-online.target is frowned upon by systemd upstream.
Following up with upstream
Was it a change on the packagekit side this cycle? The shell has been
having the same behaviour of displaying the dialog if offline updates
are enabled for a long time
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit
Upstream issue: https://github.com/libexpat/libexpat/issues/572
** Bug watch added: github.com/libexpat/libexpat/issues #572
https://github.com/libexpat/libexpat/issues/572
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e
** Changed in: bluez
Status: Unknown => Fix Released
--
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/1962542
Title:
bose quietcomfort 35 unable to connect after suspen
** Changed in: bluez
Status: Unknown => Fix Released
--
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/1962563
Title:
bluetoothd crashed with SIGSEGV in __strlen_avx2()
** Also affects: gst-plugins-good1.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gst-plugins-bad1.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gst-plugins-base1.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gst-plugins-
** Description changed:
+ [ Description ]
+
+ We should keep up with GStreamer's bugfix releases in the 1.16 series
+ that 20.04 shipped with.
+
+ [ QA and testing ]
+
+ Play a range of videos in Totem. Play a range of audio tracks in
+ Rhythmbox. Try to stream audio and/or video. Try to instal
I'll leave this open until we have >=5.64 released and are sure the same
crash isn't happening.
** Also affects: bluez via
https://github.com/bluez/bluez/issues/272
Importance: Unknown
Status: Unknown
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received thi
OK the crash is a separate issue.
This is https://github.com/bluez/bluez/issues/284 which is also fixed in
BlueZ 5.64.
** Bug watch added: github.com/bluez/bluez/issues #284
https://github.com/bluez/bluez/issues/284
** Bug watch added: github.com/bluez/bluez/issues #284
https://github.com/
See also bug 1962563.
--
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/1962542
Title:
bose quietcomfort 35 unable to connect after suspend
Status in Bluez Utilities:
Unknow
Actually it sounds like https://github.com/bluez/bluez/issues/272 but
yours isn't crashing(?)
There's mention of QC35 in https://github.com/bluez/bluez/issues/220
too, and that it works after downgrading to BlueZ 5.61.
Both seem to be fixed in upstream master (which will be BlueZ 5.64).
** Chang
If you can find evidence of 'bluetoothd' crashing then it is
https://github.com/bluez/bluez/issues/272 (fixed in BlueZ 5.64).
--
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/196
Looks like https://github.com/bluez/bluez/issues/272 which is fixed in
BlueZ 5.64
** Summary changed:
-
/usr/lib/bluetooth/bluetoothd:11:__strlen_avx2:_dbus_string_init_const:_dbus_check_is_valid_path:_dbus_check_is_valid_path:dbus_message_iter_append_basic
+ bluetoothd crashed with SIGSEGV in _
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
bluez. This problem was most recently seen with package version 5.63-0ubuntu1,
the problem page at
https://errors.ubuntu.com/problem/05251767678452859eebd21c29df5e7c4b67ff66
contains more detail
** Also affects: openssh (Ubuntu Jammy)
Importance: Low
Status: Triaged
** Changed in: openssh (Ubuntu Jammy)
Status: Triaged => Fix Released
** Changed in: openssh (Ubuntu Bionic)
Status: New => Triaged
** Changed in: openssh (Ubuntu Focal)
Status: New => Triaged
Reassigned to the kernel/firmware packages.
We next need to review what the kernel has logged during suspend/resume.
Comment #18 doesn't look like enough info so can you attach the full
log? (journalctl -b0)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
^^^
That's missing two of your radio devices (the Intel Wifi and Bluetooth), if you
compare to comment #17. So it looks like the kernel devices have vanished after
resuming from suspend the first time.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
** Also affects: linux-firmware (
Though on the other hand I don't really want flavours to do offline
upgrades, but I don't think we have a clear-cut policy on that. Either
way, removing the feature inside PackageKit might break some flavours,
so seeing as we are past feature freeze, fixing that in the frontend
would be less invasi
This is *not* a packagekit issue. There are flavours upgrading using
packagekit, not everyone uses update-manager. It's either gnome-shell or
gnome-session or something that should not be reacting to this.
** Package changed: packagekit (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug n
There is no difference in 'rfkill' before/after suspend. In both cases,
the bluetooth line looks like this:
heather@fenrir:~$ rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth tpacpi_bluetooth_sw unblocked unblocked
And the PID of bluetoothd is the same before/after suspend
Public bug reported:
I'm using:
bsci@ip-10-132-42-225:~/test$ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
bsci@ip-10-132-42-225:~/test$ apt-cache policy openssl
openssl:
Installed: 1.1.1f-1ubuntu2.10
Candidate: 1.1.1f-1ubuntu2.10
Version table:
*** 1.1.1f-1ubu
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1962542
Title:
bose quietcomfort
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564360/+files/syslog.txt
--
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
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564358/+files/getfacl.txt
--
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.
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564359/+files/rfkill.txt
--
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
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564355/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564354/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564356/+files/UdevDb.txt
--
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
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564357/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564351/+files/Lsusb-v.txt
--
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.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564350/+files/Lsusb-t.txt
--
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.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564348/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564352/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564349/+files/Lsusb.txt
--
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/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564353/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
h
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564347/+files/Lspci.txt
--
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/b
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564346/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.
apport information
** Description changed:
Bose quietcomfort 35 is a common headset that can no longer connect to a
jammy system after just one suspend. This started at the end of January
but just now really debugging the issue.
+
+ Side note that my bluetooth mouse works fine without prob
Also does the 'rfkill' command show any difference in the radio status
after resume?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Firstly good news that it partially works now. It didn't before
according to bug 1620636.
What is the Bluetooth chip in the laptop (lspci / lsusb)? We probably
need to check to see if it is chip-specific (a kernel bug) or a BlueZ
bug.
Please also check the PID of bluetoothd to see if it's the sam
Still seems low priority. Not many people will care if on some rare
occasion they have to wait for a reboot before powering off.
--
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/
Public bug reported:
Bose quietcomfort 35 is a common headset that can no longer connect to a
jammy system after just one suspend. This started at the end of January
but just now really debugging the issue.
The headset is only trying to connect to the jammy system (no other
bluetooth devices it's
the issue there is that packagekit is proposing offline updates which it
shouldn't do on Ubuntu
** Package changed: gnome-shell (Ubuntu) => packagekit (Ubuntu)
** Changed in: packagekit (Ubuntu)
Importance: Low => High
** Tags added: rls-jj-incoming
--
You received this bug notification bec
You have been subscribed to a public bug:
When I want to turn off a computer, I got a checkbox "Install deferred
updates" (see screenshot, I'm not sure if my back-translation is
correct).
If the checkbox is checked, Ubuntu box reboots instead of powering off.
It is not "rebopot to install updates
57 matches
Mail list logo
