I uploaded sosreport with
sudo sos report -a --all-logs --case-id=2085520 --upload --batch
I hope you got it
```
Your sosreport has been generated and saved in:
/tmp/sosreport-drakkar-2085520-2024-10-24-fntenns.tar.xz
Size 171.21MiB
Owner root
sha256 384377438b825356eb2ce303
Public bug reported:
>From time to time my headphones loses sound I had to switch the coded to
>another one and back then I got sound back.
The Ubuntu is 24.04.
Also I have problem that switching from Handsfree mode takes very long
(over 10s after closing the source of the call). Then Headset m
I added this option to pipewire.conf and seems work much better right
now
tail -1 /etc/pipewire/pipewire.conf
module-allow-priority = false
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launch
This bug fix for Jammy is critical for our ongoing deployment at the customer
side.
The unique combination of hardware (Intel NICs and AMD platform) causes unusual
long time for the bond to come up after running netplan (7-11s). That is long
enough to cause:
- three way database partition
- time
*** This bug is a duplicate of bug 2072605 ***
https://bugs.launchpad.net/bugs/2072605
I have similar symptom
-- Boot eae21136928345238f36ceb7e6286634 --
Aug 20 09:15:40 drakkar systemd[1]: Starting Bluetooth service...
Aug 20 09:15:40 drakkar bluetoothd[3008]: Bluetooth daemon 5.64
Aug 20 09
So I did tests on Jammy, installed fresh Ubuntu Jammy from ISO on the VM
instance and attached the WiFi device.
Initially it asked me for admin password to change the network settings.
In Jammy the polkit (<0.106) still relies on pkla files to add the proper
privileges, instead of Javascript-cod
I checked again and it seems that dbus-daemon goes zombie
gdm 1927 0.0 0.0 0 0 tty1 Z+ 15:42 0:00
[dbus-daemon]
The keyring seems to be running with the proper options
root@desktop-noble:~# ps aux|grep keyring
I attached sos report
** Attachment added:
"sosreport-desktop-noble-lp-2098016-2025-02-17-zzlaapp.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2098016/+attachment/5858212/+files/sosreport-desktop-noble-lp-2098016-2025-02-17-zzlaapp.tar.xz
--
You received this bug n
Thanks Alesto due to private message, I fixed my previous comment and
added
ExecStart= in override to unset it first
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2
Interesting observation in noble in contrary to jammy, the keyring runs
with two components secrets,pkcs11, instead only secrets
root@desktop-noble:~# ps aux|grep keyrin
gdm 5468 0.0 0.1 314312 9728 ?Ssl 11:12 0:00
/usr/bin/gnome-keyring-daemon --foreground --components=pkcs
After the discussion with Alessandro:
I fixed the ExecStart and now it run with control file
root@desktop-noble:~# ps aux|grep keyring │.service: Deactivated successfully.
gdm 1836 0.0 0.1 314312 9600 ? Ssl 15:39 0:00 /usr/bin/gnome-keyring-daemon
--foreground --
components=secrets --control-dire
That's great, thank you Alessandro!
>https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3646
I wonder if they agree about this change, isn't somewhat overriding the
security?
If the polkit rules are removed, because let's say someone don't like that
will this still throw an error at us
Public bug reported:
This is my VPN connection. I set not to add DNS resolving (ipv6.ignore-
auto-dns: "true") and default route for ipv6 (ipv6.never-default:
"true")
Yet after connection it still set the default route via tun0
These routes I get:
2a00:1398:300:14::/64 dev tun0 proto kernel metr
This seesm to be caused by other device like phone owning the output and
the implementation by Sennheiser is particually deficient in some what
If I list all UUIDs the proper output seems to be there
[MOMENTUM 3]# info 00:1B:66:E9:99:8F
Device 00:1B:66:E9:99:8F (public)
Name: MOMENTUM 3
14 matches
Mail list logo
