[Pkg-utopia-maintainers] Bug#998073: wireplumber: fails to automatically switch to headphones when connected

Hi, On 2022-10-09 02:48:27 +0200, Vincent Lefevre wrote: > On 2022-10-05 09:45:03 +0200, Dylan Aïssi wrote: > > Control: fixed -1 0.4.12-1 > [...] > > I just uploaded the new wireplumber version with this feature in sid. > > I wait your feedback to close (or not) this b

[Pkg-utopia-maintainers] Bug#1056313: network-manager: breaks networking

Control: found -1 1.44.2-3 Control: retitle -1 network-manager: breaks networking (Permission denied for the new /usr/libexec/nm-dhcp-helper) On 2023-11-20 12:24:36 +0100, Vincent Lefevre wrote: > Package: network-manager > Version: 1.44.2-4 > Severity: grave > Justification: ren

[Pkg-utopia-maintainers] Bug#1056313: network-manager: breaks networking

Package: network-manager Version: 1.44.2-4 Severity: grave Justification: renders package unusable Just after the upgrade of network-manager from 1.44.2-1 to 1.44.2-4, my network is down. In the journalctl logs, I can see [...] Nov 20 12:08:58 cventin NetworkManager[286424]: [1700478538.0092]

[Pkg-utopia-maintainers] Bug#1056313: network-manager: breaks networking

On 2023-11-20 12:24:36 +0100, Vincent Lefevre wrote: > Note: the errors about /usr/libexec/nm-dhcp-helper changed to > > Nov 20 12:17:42 cventin dhclient[295468]: execve > (/usr/libexec/nm-dhcp-helper, ...): No such file or directory > > but the network is workin

[Pkg-utopia-maintainers] Bug#1056313: network-manager: breaks networking

On 2023-11-20 12:42:14 +0100, Vincent Lefevre wrote: > I suspect that nm-dhcp-helper has been added because it is now needed. > But it doesn't work due to the "Permission denied". If I understand correctly, /usr/lib/NetworkManager/nm-dhcp-helper moved to /usr/libexec/nm-dhcp-

[Pkg-utopia-maintainers] Bug#1069636: network-manager: should not depend on the transitional package policykit-1

Package: network-manager Version: 1.46.0-1+b2 Severity: normal network-manager currently has Depends: [...] polkitd | policykit-1 policykit-1 is now a transitional package. network-manager should not depend on it (even in an OR dependency), otherwise apt or aptitude cannot propose its

[Pkg-utopia-maintainers] Bug#1064500: avahi-autoipd: should stop recommending isc-dhcp-client

Package: avahi-autoipd Version: 0.8-13+b1 Severity: wishlist ISC no longer maintains the client part of isc-dhcp. Moreover, isc-dhcp-client no longer works with NetworkManager. avahi-autoipd should use an alternative DHCP client. -- System Information: Debian Release: trixie/sid APT prefers

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

On 2019-05-15 12:50:49 +0200, Michael Biebl wrote: > Which part of /usr/lib/avahi/avahi-daemon-check-dns.sh is taking so long? > Can you add a "set -x" and then manually invoke "ifdown eth0" I get: + PATH=/bin:/usr/bin:/sbin:/usr/sbin + RUNDIR=/var/run/avahi-daemon/ +

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

On 2019-05-16 18:36:09 +0200, Michael Biebl wrote: > Am 16.05.19 um 18:17 schrieb Vincent Lefevre: > > On 2019-05-16 17:52:03 +0200, Michael Biebl wrote: > >> I would suggest the following: If there is a local nameserver but no > >> network connectivity, quer

[Pkg-utopia-maintainers] Bug#876342: Bug#876342: Bug#876342: avahi-daemon: upgrade failed: failed to configure

Control: tags -1 - unreproducible Removing the tag "unreproducible" since the issue is now different and should be more common: PID file not removed when avahi-daemon is stopped. It seems to occur *every time* avahi-daemon is restarted, on two of my machines. The failure in case of reuse of the

[Pkg-utopia-maintainers] Bug#876342: Bug#876342: Bug#876342: avahi-daemon: upgrade failed: failed to configure

Control: retitle -1 PID file not removed when avahi-daemon is stopped, causing a failure when the PID is reused On 2017-09-22 09:49:16 +0200, Vincent Lefevre wrote: > On 2017-09-21 23:33:07 +0200, Michael Biebl wrote: > > Not sure what to do about this bug report then aside fro

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

Control: retitle -1 avahi-daemon: 10-second timeout in /usr/lib/avahi/avahi-daemon-check-dns.sh and other issues (buggy regexp...) Any news? BTW, it seems to be an issue similar to bug 559927 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559927 "/usr/lib/avahi/avahi-daemon-check-dns.sh

[Pkg-utopia-maintainers] Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

Package: avahi-daemon Version: 0.7-4+b1 Severity: normal /etc/network/if-post-down.d/avahi-daemon takes 12 seconds to complete, slowing the shutdown: [...] May 15 10:23:47 zira dhclient[19399]: DHCPRELEASE of 192.168.1.3 on eth0 to 192.168.1.1 port 67 May 15 10:23:47 zira ifdown[19369]:

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

On 2019-05-16 14:15:37 +0200, Michael Biebl wrote: > Looks like you have a local resolver configured in /etc/resolv.conf > (which should be reachable via lo, even if eth0 is down). Yes, /etc/resolv.conf contains nameserver 127.0.0.1 nameserver 192.168.1.1 as I use "unbound". -- Vincent

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

On 2019-05-16 14:41:44 +0200, Michael Biebl wrote: > Am 16.05.19 um 14:22 schrieb Vincent Lefevre: > > On 2019-05-16 14:15:37 +0200, Michael Biebl wrote: > >> Looks like you have a local resolver configured in /etc/resolv.conf > >> (which should be reachable v

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

On 2019-05-16 15:59:09 +0200, Vincent Lefevre wrote: > On 2019-05-16 14:41:44 +0200, Michael Biebl wrote: > > Am 16.05.19 um 14:22 schrieb Vincent Lefevre: > > > On 2019-05-16 14:15:37 +0200, Michael Biebl wrote: > > >> Looks like you have a local resolver

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

On 2019-05-16 16:09:04 +0200, Vincent Lefevre wrote: > On 2019-05-16 15:59:09 +0200, Vincent Lefevre wrote: > > On 2019-05-16 14:41:44 +0200, Michael Biebl wrote: > > > Am 16.05.19 um 14:22 schrieb Vincent Lefevre: > > > > On 2019-05-16 14:15:37 +0200, Michael Biebl

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

On 2019-05-16 16:25:01 +0200, Michael Biebl wrote: > What happens, if you only list your local 127.0.0.1 in /etc/resolv.conf? See my other mail, i.e. no problems. FYI, I use 192.168.1.1 just as a fallback. > Well, the assumption that /usr/lib/avahi/avahi-daemon-check-dns.sh makes > is, that if a

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

On 2019-05-16 16:54:26 +0200, Michael Biebl wrote: > I'm happy to review a tested patch, which considers your specific use case. Would one of the following behaviors be OK? 1. If there is no default route, then assume that we can't reach any nameservers (there's potentially a local nameserver,

[Pkg-utopia-maintainers] Bug#929010: Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

On 2019-05-16 17:52:03 +0200, Michael Biebl wrote: > I would suggest the following: If there is a local nameserver but no > network connectivity, query the local nameserver only. OK, I can do that. Indeed, the default behavior of "host" is to try every server in /etc/resolv.conf until it

[Pkg-utopia-maintainers] Bug#933930: Fwd: Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

On 2019-08-12 09:40:43 +0200, Beniamino Galvani wrote: > On Fri, Aug 09, 2019 at 05:03:34PM +0200, Vincent Lefevre wrote: > > On 2019-08-09 16:05:11 +0200, Beniamino Galvani wrote: > > > in the traces I see that there are 3 servers and one of them > > > advertises a subn

[Pkg-utopia-maintainers] Bug#933930: network-manager: Ethernet connection no longer works

Package: network-manager Version: 1.19.90-2 Severity: grave Justification: renders package unusable After upgrading to 1.19.90-2 and rebooting my machine, I completely lost Ethernet connection. cventin:~> journalctl -b -2 -g network -- Logs begin at Tue 2016-04-19 07:35:01 CEST, end at Mon

[Pkg-utopia-maintainers] Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

On 2019-08-06 22:24:49 +0200, Michael Biebl wrote: > Ok, so the current state of affairs is: > > dhcp=dhclient works always > dhcp=internal (the default) fails (sometimes) > > ? That's right. Here are more complete logs for dhcp=internal, first those corresponding to a success, then those

[Pkg-utopia-maintainers] Bug#933930: Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

On 2019-08-07 12:57:37 +0200, Michael Biebl wrote: > mbiebl_, Unclear what is not working. Could you ask for > level=TRACE logs? See > https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28 > , preferably without ratelimiting from journal (see

[Pkg-utopia-maintainers] Bug#933930: network-manager: Ethernet connection no longer works

On 2019-08-05 11:32:59 +0200, Vincent Lefevre wrote: > On 2019-08-05 11:20:24 +0200, Vincent Lefevre wrote: > > Downgrading to 1.14.6-2 solved the issue. As a comparison with this working > > version: 1.18.0-3 is also working. cventin:~> journalctl -b -g network -- Logs begin

[Pkg-utopia-maintainers] Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

On 2019-08-06 10:38:19 +0200, Michael Biebl wrote: > Can you try and switch to dhclient instead of the internal one. > > $ cat /etc/NetworkManager/conf.d/dhcp.conf > [main] > dhcp=dhclient I upgraded to 1.19.90-2 again, and I did that, and rebooted, and it worked. Then, to be sure, I removed

[Pkg-utopia-maintainers] Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

On 2019-08-06 15:27:19 +0200, Vincent Lefevre wrote: > Now, I'll try to see if I can reproduce the failure with dhcp.conf. I tried a dozen of times, but I couldn't. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net

[Pkg-utopia-maintainers] Bug#933930: Fwd: Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

On 2019-08-08 13:37:04 +0200, Michael Biebl wrote: > Bringing Vincent into the loop here. > > Vincent, can you gather the information Beniamino is asking for? > > Am 08.08.19 um 09:51 schrieb Beniamino Galvani: > > Would it be possible to capture a dump of DHCP packets for a success > > and for

[Pkg-utopia-maintainers] Bug#933930: Fwd: Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

On 2019-08-09 09:42:10 +0200, Beniamino Galvani wrote: > On Thu, Aug 08, 2019 at 06:07:41PM +0200, Vincent Lefevre wrote: > > On 2019-08-08 13:37:04 +0200, Michael Biebl wrote: > > > Bringing Vincent into the loop here. > > > > > > Vincent, can you gather

[Pkg-utopia-maintainers] Bug#933930: Fwd: Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

On 2019-08-09 16:05:11 +0200, Beniamino Galvani wrote: > in the traces I see that there are 3 servers and one of them > advertises a subnet different from other two. This setup makes the > behavior non-deterministic because clients can get an address either > in the 10.0.1.0/24 or in the

[Pkg-utopia-maintainers] Bug#966618: network-manager: with dhcp=dhclient, dhclient hooks are not run

Package: network-manager Version: 1.26.0-1 Severity: normal I have configured NetworkManager with [main] dhcp=dhclient in particular to use the dhclient hooks, but they are not run. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500,

[Pkg-utopia-maintainers] Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

Package: policykit-1 Version: 0.105-27 Severity: grave Justification: renders package unusable policykit-1 cannot be installed: [...] Setting up policykit-1 (0.105-27) ... chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such file or directory dpkg: error processing package

[Pkg-utopia-maintainers] Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

Note: The bug is not present in 0.105-26, thus this is a different bug from 965164 (or the metadata have been messed up in bug 965164, which is ignored by apt-listbugs when upgrading from 0.105-26). -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

[Pkg-utopia-maintainers] Bug#965193: Bug#965193: Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

On 2020-07-17 16:47:33 +0200, Michael Biebl wrote: > Am 17.07.20 um 16:29 schrieb Michael Biebl: > > Am 17.07.20 um 15:29 schrieb Vincent Lefevre: > >> Note: The bug is not present in 0.105-26, thus this is a different > >> bug from 965164 (or the metadata have b

[Pkg-utopia-maintainers] Bug#978935: Bug#978935: network-manager: disconnect on upgrade

On 2020-12-31 20:22:56 +0100, Michael Biebl wrote: > Am 31.12.20 um 18:37 schrieb Vincent Lefevre: > > During the upgrade, network-manager disconnected, so that I completely > > lost the network connection. Fortunately, I was in front of my machine, > > but this means that

[Pkg-utopia-maintainers] Bug#978935: Bug#978935: network-manager: disconnect on upgrade

On 2021-01-01 12:58:48 +0100, Michael Biebl wrote: > Am 01.01.21 um 01:19 schrieb Vincent Lefevre: > > The name of the active connection could be stored in a file, so that > > a reexec'ed daemon could pick the information. By active connection, > > I mean the last connecti

[Pkg-utopia-maintainers] Bug#978935: Bug#978935: network-manager: disconnect on upgrade

On 2021-01-01 15:12:06 +0100, Michael Biebl wrote: > Am 01.01.21 um 14:55 schrieb Vincent Lefevre: > > On 2021-01-01 12:58:48 +0100, Michael Biebl wrote: > > > Am 01.01.21 um 01:19 schrieb Vincent Lefevre: > > > > The name of the active connection

[Pkg-utopia-maintainers] Bug#978935: network-manager: disconnect on upgrade

Package: network-manager Version: 1.28.0-1+b1 Severity: serious During the upgrade, network-manager disconnected, so that I completely lost the network connection. Fortunately, I was in front of my machine, but this means that a remote upgrade can make the machine unavailable! In the journalctl

[Pkg-utopia-maintainers] Bug#999363: Shouldn't replace pulseaudio by pipewire by default

On 2021-11-10 15:40:21 +0100, Sebastien Bacher wrote: > The pipewire 0.3.39-3 updated replaced pipewire-media-service Recommends by > wireplumber, or wireplumber Recommends pipewire-pulse which makes it take > over pulseaudio as the default sound service. We got several report of > people

[Pkg-utopia-maintainers] Bug#997862: wireplumber: Bluetooth is not supported, breaking audio of existing systems

On 2021-10-26 12:00:34 +0200, Dylan Aïssi wrote: > Wireplumber needs the libspa-0.2-bluetooth package to support > bluetooth. I guess it was missing from your system. > libspa-0.2-bluetooth is only a plugin, wireplumber can work without > it. This is why it is not a dependency. OK, but then, this

[Pkg-utopia-maintainers] Bug#998073: pipewire-pulse: fails to automatically switch to headphones when connected

Package: pipewire-pulse Version: 0.3.39-3 Severity: important I use bluetooth speakers by default. When I connect my bluetooth headphones, I want the system to automatically switch from the speakers to the headphones. This is how it behaved before the upgrade and the replacement of

[Pkg-utopia-maintainers] Bug#997862: wireplumber: Bluetooth is not supported, breaking audio of existing systems

On 2021-10-26 10:26:17 +0200, Vincent Lefevre wrote: > After the upgrade of my system, which lead to wireplumber > installation, Bluetooth audio is no longer working. > > In the journalctl logs, I can see: > > Oct 26 10:18:29 zira wireplumber[1701]: SPA handle 'api.bluez5.e

[Pkg-utopia-maintainers] Bug#997862: wireplumber: Bluetooth is not supported, breaking audio of existing systems

Package: wireplumber Version: 0.4.4-1 Severity: grave Justification: renders package unusable After the upgrade of my system, which lead to wireplumber installation, Bluetooth audio is no longer working. In the journalctl logs, I can see: Oct 26 10:18:29 zira wireplumber[1701]: SPA handle

[Pkg-utopia-maintainers] Bug#997859: pipewire-bin should no longer recommend pipewire-media-session as it prevents the upgrade

Package: pipewire-bin Version: 0.3.39-2 Severity: serious pipewire-bin still has: Recommends: wireplumber | pipewire-media-session, rtkit However, in the changelog: * Don't build the pipewire-media-session binary package anymore, media-session has moved to a separate module to

[Pkg-utopia-maintainers] Bug#989493: udisks2: Warning in journal about "Failed to load the 'mdraid' libblockdev plugin"

Control: found -1 2.9.4-1 On 2021-06-05 10:43:03 +0200, Tia wrote: > On each startup udisksd gives a warning to journal about missing module > > udisksd[789]: failed to load module mdraid: libbd_mdraid.so.2: cannot open > shared object file: No such file or directory > udisksd[789]: Failed to

[Pkg-utopia-maintainers] Bug#922630: avahi-daemon high cpu usage

Control: found -1 0.8-5 On 2019-02-18 16:10:35 +, David Miguel Susano Pinto wrote: > avahi-dameon shows a very high cpu usage and I found no useful > messages on the logs. Same issue. The htop utility shows: PID USER PRI NI VIRT RES SHR S CPU%▽MEM% TIME+ Command 634

[Pkg-utopia-maintainers] Bug#922630: avahi-daemon high cpu usage

On 2022-03-03 16:12:57 +0100, Vincent Lefevre wrote: > On 2019-02-18 16:10:35 +, David Miguel Susano Pinto wrote: > > avahi-dameon shows a very high cpu usage and I found no useful > > messages on the logs. > > Same issue. The htop utility shows: > > PID US

[Pkg-utopia-maintainers] Bug#1054650: dbus: makes the machine extremely slow, freezes on shutdown

Package: dbus Version: 1.14.10-2 Severity: critical Justification: breaks the whole system dbus 1.14.10-2 makes the machine extremely slow (this affects the boot, login, the su command, and package installation at least), and it freezes on shutdown. This is reproducible (I've tested on 2

[Pkg-utopia-maintainers] Bug#1018880: under ssh X11 forwarding, apps like nautilus that use xdg-desktop-portal start with 25s delay

On 2023-08-15 11:45:59 -0400, Jim McCann wrote: > Some additional information: this bug also triggers for me without > X11 forwarding. > > I don't run a desktop environment or graphical login (login in text > mode and then `startx` with fluxbox launched from .xinitrc); but I > still have

Re: [Pkg-utopia-maintainers] Bug#1011035: vlc: breaks pulseaudio

On 2022-05-16 00:18:31 +0200, Sebastian Ramacher wrote: > vlc doesn't. vlc is a meta package. There is a question to the pipewire > maintainers whether pipewire should depend or recommend > libspa-0.2-bluetooth to have a smoother transition from pulseaudio to > pipewire. Hence, reassigning there.

[Pkg-utopia-maintainers] Bug#1011130: libpipewire-0.3-0: should not recommend pipewire

Package: libpipewire-0.3-0 Version: 0.3.51-1 Severity: critical Justification: breaks unrelated software Several packages depend on libpipewire-0.3-0 in order to have pipewire *support* (but they don't need pipewire: the user may want to use pulseaudio). However, libpipewire-0.3-0 currently has

[Pkg-utopia-maintainers] Bug#1011130: libpipewire-0.3-0: should not recommend pipewire

On 2022-05-30 13:49:57 +0200, IOhannes m zmölnig wrote: > 3. i understand sebastinas' annoyance if they feel somebody is on a crusade > against pipewire (but i haven't followed any of the discussion except > for this bug-report on the thread on debian-devel@ to acknowledge > whether there is an

[Pkg-utopia-maintainers] Bug#998073: wireplumber: fails to automatically switch to headphones when connected

Control: reassign -1 wireplumber 0.4.4-1 Control: retitle -1 wireplumber: fails to automatically switch to headphones when connected Control: tags -1 upstream Control: forwarded -1 https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/267 On 2021-10-29 18:23:03 +0200, Vincent Lefevre

[Pkg-utopia-maintainers] Bug#922630: dupe of 993051?

On 2022-06-06 11:51:17 +0200, Mathieu ROY wrote: > This bug is very likely the same as 993051 that you fixed yesterday. I agree. With the absence of additional information (and a vague bug title), these bugs should be regarded as being the same. Before the upgrade to 0.8-6 (i.e. containing the

[Pkg-utopia-maintainers] Bug#1018880: dbus-user-session: GNOME applications such as evince and nautilus start with a 25-second delay via ssh

Package: dbus-user-session Version: 1.12.20-2 Severity: important (not sure about the right package) I first noticed that when I connect by ssh, evince is very slow to start. A "strace -f -ttt evince" shows a 15-second timeout followed by a 10-second timeout, thus a 25-second delay, before the

[Pkg-utopia-maintainers] Bug#1018880: dbus-user-session: GNOME applications such as evince and nautilus start with a 25-second delay via ssh

On 2022-09-07 09:19:26 +0100, Simon McVittie wrote: > On Thu, 01 Sep 2022 at 12:22:28 +0200, Vincent Lefevre wrote: > > I first noticed that when I connect by ssh, evince is very slow to > > start. A "strace -f -ttt evince" shows a 15-second timeout followed > > by

[Pkg-utopia-maintainers] Bug#998073: wireplumber: fails to automatically switch to headphones when connected

Hi, On 2022-09-27 10:51:55 +0200, Samuel Thibault wrote: > Dylan Aïssi, le mar. 27 sept. 2022 10:29:15 +0200, a ecrit: > > Is this issue still reproducible with latest wireplumber 0.4.11-5 > > available in sid? I should be able to try tonight (I need to reinstall packages). > On my system, for

[Pkg-utopia-maintainers] Bug#1023004: network-manager: does not attempt reconnect after a temporary wifi failure

Package: network-manager Version: 1.40.2-1 Severity: normal In case of temporary wifi failure, network-manager doesn't try to reconnect. Here are the logs: Oct 29 00:58:06 zira wpa_supplicant[851]: wlp61s0: CTRL-EVENT-BEACON-LOSS Oct 29 00:58:09 zira wpa_supplicant[851]: wlp61s0:

[Pkg-utopia-maintainers] Bug#1023004: Bug#1023004: network-manager: does not attempt reconnect after a temporary wifi failure

On 2022-10-29 10:17:09 +0200, Michael Biebl wrote: > Am 29.10.22 um 01:26 schrieb Vincent Lefevre: > > Package: network-manager > > Version: 1.40.2-1 > > Severity: normal > > > > In case of temporary wifi failure, network-manager doesn't try to > > reconnect

[Pkg-utopia-maintainers] Bug#1023004: Bug#1023004: Bug#1023004: network-manager: does not attempt reconnect after a temporary wifi failure

Control: forwarded -1 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/628 Control: retitle -1 network-manager: does not attempt to reconnect after a temporary wifi failure in case of link timed out Clarified the title. NetworkManager attempts to reconnect after a

[Pkg-utopia-maintainers] Bug#1018880: dbus-user-session: GNOME applications such as evince and nautilus start with a 25-second delay via ssh

On 2022-09-07 11:50:53 +0100, Simon McVittie wrote: > Part of the root cause here is that xdg-desktop-portal-gtk is a systemd > user-service that cannot work without either an X11 or Wayland display > (its purpose is to show prompts when a sandboxed application wants to > do something that needs

[Pkg-utopia-maintainers] Bug#998073: wireplumber: fails to automatically switch to headphones when connected

Control: found -1 0.4.12-1 On 2022-10-05 09:45:03 +0200, Dylan Aïssi wrote: > Control: fixed -1 0.4.12-1 [...] > I just uploaded the new wireplumber version with this feature in sid. > I wait your feedback to close (or not) this bug. It is not fixed (same issue as previously), and worse, it

[Pkg-utopia-maintainers] Bug#998073: wireplumber: fails to automatically switch to headphones when connected

Control: found -1 0.4.11-5 On 2022-09-27 10:29:15 +0200, Dylan Aïssi wrote: > Le lun. 30 mai 2022 à 16:57, Vincent Lefevre a écrit : > > > > On 2021-10-29 18:23:03 +0200, Vincent Lefevre wrote: > > > I use bluetooth speakers by default. When I connect my bluetooth

[Pkg-utopia-maintainers] Bug#1071919: xdg-document-portal.service: timeout during shutdown

Package: xdg-desktop-portal Version: 1.18.4-1 Severity: normal I logged out, so that I was back to the lightdm display manager. I did a restart, but it took a long time due to a timeout for xdg-document-portal.service. This was the first time I got this issue. I've attached the journalctl

[Pkg-utopia-maintainers] Bug#1071919: xdg-document-portal.service: timeout during shutdown

On 2024-05-25 23:26:43 +0200, Vincent Lefevre wrote: > I logged out, so that I was back to the lightdm display manager. > I did a restart, but it took a long time due to a timeout for > xdg-document-portal.service. This was the first time I got this > issue. I don't know whether thi