[Pkg-utopia-maintainers] Bug#853239: avahi: Please provide python3-avahi

Am 14.05.2018 um 13:58 schrieb W. Martin Borgert: > I need python3-avahi for gajim. Would you accept a patch? I'd be happy if someone provides a (tested) patch. Even more awesome would be a merge request via salsa (no changes to debian/changelog please, use a gbp dch conforming commit message).

[Pkg-utopia-maintainers] Bug#898394: assign to GNOME Network Manager package

[always CC the package maintainer when reassigning] On Sun, 13 May 2018 15:58:01 +0200 Geert Stappers wrote: > Control: reassign -1 network-manager-gnome > > Hello, > > Bug was report against package "general". > Package 'network-manager-gnome' seems a better fit. Most

[Pkg-utopia-maintainers] Bug#899350: Bug#899350: network-manager-gnome: drops wireless connection sometimes, messes up connection display

Control: tags -1 moreinfo Am 24.05.2018 um 07:26 schrieb Thomas Korimort: > Where can i find the log files of network-manager? Otherwise, i would be > happy, if you would cite mesages from my whole email and not incomplete > excerpts from it. You claimed it's a network-manager problem, so it

[Pkg-utopia-maintainers] Bug#900924: Bug#900924: Bug#900924: [network-manager-gnome] segfault after upgrade to 1.8.12-1

Control: forcemerge 900869 -1 Am 07.06.2018 um 13:36 schrieb Shin Ice: > Hi, > > On Wed, Jun 06, 2018 at 09:43:12PM +0200, Michael Biebl wrote: >> >> Please test 1.8.12-2 and report back. It was uploaded a couple of >> minutes ago and should hit the mirrors soon. >

Re: [Pkg-utopia-maintainers] Bug#895261: RFS: dbus-broker/13-2 [ITP] -- Linux D-Bus Message Broker

Am 29.05.2018 um 19:30 schrieb Daniele Nicolodi: > What would it take to have user services managed in a similar way as > system services? Should I look into implementing that in > init-system-helpers or should a new dh helper be created? It would need changes to both init-system-helpers and

[Pkg-utopia-maintainers] Bug#900924: Bug#900924: [network-manager-gnome] segfault after upgrade to 1.8.12-1

Am 06.06.2018 um 20:54 schrieb Shin Ice: > Package: network-manager-gnome > Version: 1.8.12-1 > Severity: grave > > --- Please enter the report below this line. --- > > Hi, > > after upgrading network-manager-gnome and libnma0 to 1.8.12-1 I receive > a segfault every time I open the menu to

[Pkg-utopia-maintainers] Bug#902644: upower: Upower breaks power saving settings after upgrade to 0.99.8-1

On Sat, 30 Jun 2018 10:58:11 +0100 Alessandro Ghedini wrote: > On Thu, Jun 28, 2018 at 09:55:01PM -0300, Adilson dos Santos Dantas wrote: > > Package: upower > > Version: 0.99.8-1 > > Severity: important > > > > Dear Maintainer, > > > > After upgrading upower to 0.99.8-1, my KDE power saving

[Pkg-utopia-maintainers] Bug#902884: Bug#902884: upowerd fails to start

Control: forcemerge 902411 -1 Am 02.07.2018 um 22:45 schrieb Eric Valette: > Package: upower > Version: 0.99.8-1 > Severity: grave > Justification: renders package unusable > > I had no upowerd daemon running on all my boxes: > > Jul 02 20:52:00 htpc1 systemd[1]: Starting Daemon for power

[Pkg-utopia-maintainers] Bug#902884: Bug#902884: upowerd fails to start

Am 03.07.2018 um 14:14 schrieb Eric Valette: > On Tue, 3 Jul 2018 07:34:32 +0200 Michael Biebl wrote: > >> Duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902411 > > True but both bugs are closed and I'm having 5 computers that exhibit > the problem and proba

[Pkg-utopia-maintainers] Bug#905171: Bug#905171: Subject: network-manager: Network-manager will not connect to known wifi networks "no secrets provided"

Control: tags -1 moreinfo Am 01.08.2018 um 08:57 schrieb Jon Westgate: > Package: network-manager > Version: 1.12.2-1 > Severity: important > > Dear Maintainer, > > Since upgrading from NM version 1.10.x I've noticed that it is getting > increasingly hard to connect to wifi networks. > With

[Pkg-utopia-maintainers] Bug#905389: File conflict with cockpit-ws

Package: firewalld, cockpit-ws Severity: normal While upgrading firewalld to 0.6.0, I noticed that there is a file conflict with cockpit-ws: Unpacking firewalld (0.6.0-1) ... dpkg: error processing archive /home/michael/debian/build-area/firewalld_0.6.0-1_all.deb (--unpack): trying to

[Pkg-utopia-maintainers] Bug#905389: Bug#905389: File conflict with cockpit-ws

Am 04.08.2018 um 00:44 schrieb Michael Biebl: > Package: firewalld, cockpit-ws > Severity: normal > > While upgrading firewalld to 0.6.0, I noticed that there is a file I haven't uploaded 0.6.0-1 to the archive yet, fwiw. > conflict with cockpit-ws: > > Unpacking firewalld

[Pkg-utopia-maintainers] Bug#906965: Bug#906965: network-manager: tests will fail (FTBFS) with GLib 2.57 because it makes g_debug() a fatal error

On 8/22/18 20:46, Simon McVittie wrote: > Source: network-manager > Version: 1.12.0-4 > Severity: important > Tags: patch fixed-upstream > > While upgrading GLib to 2.57.x in a Debian derivative, I found that > NetworkManager will FTBFS with a test failure when that version is used, > for

[Pkg-utopia-maintainers] Bug#903996: Bug#903996: network-manager-config-connectivity-debian fills up logs

Am 18.07.2018 um 22:40 schrieb Mark van Rossum: > Thanks. > Another work-around is to comment out the uri in the config file. > I have noticed any negative side-effects so far. Well, if you do that, you can just as well uninstall the network-manager-config-connectivity-debian package. It's an

[Pkg-utopia-maintainers] Bug#903996: Bug#903996: network-manager-config-connectivity-debian fills up logs

Am 18.07.2018 um 00:32 schrieb Mark van Rossum: > Package: network-manager-config-connectivity-debian > Version: 1.12.0-5 > Severity: important > > > Dear Maintainer, > > Since the update to network-manager-config-connectivity-debian:amd64 > 1.12.0-4, and when I am connected via Wifi >

[Pkg-utopia-maintainers] Bug#903996: Bug#903996: network-manager-config-connectivity-debian fills up logs

Am 18.07.2018 um 20:05 schrieb Mark van Rossum: > Thank for looking into this. > > >> So it is this exact same error message over and over again? > Yes. Ok. >> How many of those messages do you get (per minute)? > About 8000 per minute. > So, while I can't reproduce this particular issue,

[Pkg-utopia-maintainers] Bug#907747: Bug#907747: network-manager manages interface managed by /etc/network/interfaces

On 9/1/18 23:58, Arian Sanusi wrote: > I have these interfaces: > "bridge": a bridge without any ports connected on start, LXCs connect here. > It's configured in /etc/network/interfaces, and I expect NM not to touch it > "mlan0": wifi, not in interfaces, expected to be handled by NM > "lo": for

[Pkg-utopia-maintainers] Bug#907747: Bug#907747: network-manager manages interface managed by /etc/network/interfaces

On 9/2/18 00:43, Michael Biebl wrote: > On 9/1/18 23:58, Arian Sanusi wrote: >> I have these interfaces: >> "bridge": a bridge without any ports connected on start, LXCs connect here. >> It's configured in /etc/network/interfaces, and I expect NM n

[Pkg-utopia-maintainers] Bug#908340: Bug#908340: pre-up/pre-down actions supported

Am 08.09.18 um 19:05 schrieb Laurent Bigonville: > Package: network-manager > Version: 1.12.2-3 > Severity: normal > File: /etc/NetworkManager/dispatcher.d/01-ifupdown > > Hi, > > In the /etc/NetworkManager/dispatcher.d/01-ifupdown file there is a > comment that states that the pre-up is not

[Pkg-utopia-maintainers] Bug#907747: Bug#907747: network-manager manages interface managed by /etc/network/interfaces

On Mon, 3 Sep 2018 12:54:30 +0200 Arian Sanusi wrote: > to put my paint point first, maybe it was not clear: at boot NM does not > connect at boot to a WiFi. Instead I have to click the applet, wait multiple > seconds for a scan to finish and then have to choose the wifi manually. NM > says

[Pkg-utopia-maintainers] Bug#908088: Bug#908088: network-manager-gnome: nm-applet icon corrupt after upgrade to GTK 3.24

On 9/7/18 01:33, Michael Biebl wrote: > On 9/7/18 01:15, Ben Caradoc-Davies wrote: >> Another reboot, and a different set of corruption. A mostly black >> background with a few pixels of grey and black garbage at the top left. >> Screenshot attached. > > I can't r

[Pkg-utopia-maintainers] Bug#753464: firewalld: Upon startup, no rules are setup

On Wed, 02 Jul 2014 09:02:23 +0200 Vincent Bernat wrote: > Package: firewalld > Version: 0.3.10-1 > Severity: important > > Hi! > > Upon startup, firewalld is running but nor rules are setup. > > firewalld.service - firewalld - dynamic firewall daemon >Loaded: loaded

Re: [Pkg-utopia-maintainers] Bug#895261: RFS: dbus-broker/13-2 [ITP] -- Linux D-Bus Message Broker

Hi Daniele Am 09.07.2018 um 01:45 schrieb Daniele Nicolodi: > my attempt to implement user service management in init-system-helpers > and debhelper unfortunately stalled by lack of review of the > init-system-helper patches. Before I loose all interest, how do prefer > to solve the issue of

[Pkg-utopia-maintainers] Bug#903109: Bug#903109: network-manager-openvpn: "Cannot specify device when activating VPN" when connect to any VPN

Am 06.07.2018 um 12:50 schrieb Chris Lamb: > dev=tun > dev-type=tun Hm, my VPN profile only has dev=tun If I add dev-type=tun it fails for me as well. I'll raise this upstream. For the time being I would suggest you remove "dev-type=tun" from your connection profile. Regards, Michael --

[Pkg-utopia-maintainers] Bug#903109: Bug#903109: Bug#903109: network-manager-openvpn: "Cannot specify device when activating VPN" when connect to any VPN

Am 06.07.2018 um 13:34 schrieb Chris Lamb: > Dear Michael > >> Hm, my VPN profile only has >> dev=tun >> >> If I add dev-type=tun it fails for me as well. > > Thank you for the suggestion. Unfortunately this still fails for me — indeed > combinations of disabled, enabled-with-name and

[Pkg-utopia-maintainers] Bug#903109: Bug#903109: network-manager-openvpn: "Cannot specify device when activating VPN" when connect to any VPN

Hi Chris Am 06.07.2018 um 11:31 schrieb Chris Lamb: > This was working a few days ago but now I'm getting: > > Jul 6 11:27:36 keyboardcat NetworkManager[29379]: > [1530869256.9971] audit: op="connection-activate" > uuid="5993302e-22ee-46e4-8450-661be0cd2a0e" name="UK London" result="fail"

[Pkg-utopia-maintainers] Bug#903109: Bug#903109: network-manager-openvpn: "Cannot specify device when activating VPN" when connect to any VPN

Am 06.07.2018 um 15:50 schrieb Chris Lamb: > Dear Michael, > >> Are you using nm-applet to activate the connection? > > I am indeed... whilst I would usually try create a bare-bones minimal > testcase I assumed that in nm-applet was simply poking the same dbus > (?) endpoints! :) > >> What

[Pkg-utopia-maintainers] Bug#903109: Bug#903109: network-manager-openvpn: "Cannot specify device when activating VPN" when connect to any VPN

Control: forwarded -1 https://github.com/NetworkManager/NetworkManager/pull/159 Control: reassign -1 network-manager Control: found -1 1.11.3-1 Am 06.07.2018 um 16:23 schrieb Michael Biebl: > I poked upstream via IRC about this and they could reproduce it as well, > so the said to have

[Pkg-utopia-maintainers] Bug#903109: Bug#903109: network-manager-openvpn: "Cannot specify device when activating VPN" when connect to any VPN

Am 06.07.2018 um 13:34 schrieb Chris Lamb: > Dear Michael > >> Hm, my VPN profile only has >> dev=tun >> >> If I add dev-type=tun it fails for me as well. > > Thank you for the suggestion. Unfortunately this still fails for me — indeed > combinations of disabled, enabled-with-name and

[Pkg-utopia-maintainers] Bug#896258: Bug#896258: python3-bytesize: bytesize fails to import

Am 20.04.2018 um 22:01 schrieb Helmut Grohne: > Package: python3-bytesize > Version: 1.2-2 > Severity: serious > User: helm...@debian.org > Usertags: python-import > > After installing python3-bytesize importing the module bytesize > into a python interpreter fails with the following error: > >

[Pkg-utopia-maintainers] Bug#896476: Bug#896476: network-manager: NetworkManager fail with undefined symbol in liggobject2 g_varant_dict_ref

Control: tags -1 + moreinfo Am 21.04.2018 um 14:39 schrieb Carlo Marchiori: > Package: network-manager > Version: 1.10.6-3 > Severity: normal > > Dear Maintainer, > > > today my debian buster/sid failes to start properly. > Various services fail to start, apparently for the same reason. >

[Pkg-utopia-maintainers] Bug#880169: Please enable Indicator support and build against Ayatana Indicators

Am 20.04.2018 um 10:59 schrieb Mike Gabriel: > Control: tags -1 fixed-upstream > > Hi Michael, > > On  Mi 18 Apr 2018 19:47:31 CEST, Michael Biebl wrote: > >> Am 17.04.2018 um 16:57 schrieb Mike Gabriel: >>> Forwarded upstream with a patch rebased against m

[Pkg-utopia-maintainers] Bug#896818: Bug#896818: libnma over GI not working

Am 24.04.2018 um 16:32 schrieb Fabio Fantoni: > Package: network-manager-applet > Version: 1.4.4-1 > Severity: important > Tags: stretch > > Trying to use libnma over GI from a python script is not working at all and > can also cause crash of other software using it. > This patch solved it: >

[Pkg-utopia-maintainers] Bug#637748: network-manager-gnome: Persistent warning about local service discovery

Control: tags -1 + moreinfo On Sun, 14 Aug 2011 13:29:04 +0900 Mark Brown wrote: > Package: network-manager-gnome > Version: 0.8.4-2 > Severity: normal > Tags: upstream > > When the network it's connected to is not suitable for the use of local > service discovery Network

[Pkg-utopia-maintainers] Bug#908310: Original DNS kept in resolv.conf when resolved is used

On Sat, 08 Sep 2018 12:04:49 +0200 Laurent Bigonville wrote: > Package: network-manager-vpnc > Version: 1.2.6-1 > Severity: important > > Hi, > > It seems that when the VPN connection is established, the original DNS > servers are kept and the DNS coming from the VPN are added at the top. > >

[Pkg-utopia-maintainers] Bug#895810: network-manager: Network-manager wifi connection disappears after a while by itself (gnome)

On Mon, 16 Apr 2018 11:22:52 +0200 Tomas Ukkonen wrote: > Package: network-manager > Version: 1.10.6-2 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > I'm using Lenovo W510 laptop with Intel® Centrino® Wireless-N

[Pkg-utopia-maintainers] Bug#911621: Bug#911621: network-manager: crash since last apt upgrade

Am 22.10.18 um 19:30 schrieb Nicolas Patrois: > Package: network-manager > Version: 1.14.2-2 > Severity: important > > Dear Maintainer, > > Since the last upgrade with aptitude (network-manager wasn’t upgraded though), > Network manager crashes even with a reinstallation. Can you please install

[Pkg-utopia-maintainers] Bug#911621: Bug#911621: Re : Bug#911621: network-manager: crash since last apt upgrade

Am 23.10.18 um 16:47 schrieb nicolas.patr...@gmail.com: > Le 22/10/2018 17:43:12, Michael Biebl a écrit : > >> Can you please install debug symbols and get a backtrace: >> https://wiki.debian.org/HowToGetABacktrace > > Here you are: Thanks. So it crashes in the ifupdo

[Pkg-utopia-maintainers] Bug#911691: Bug#911691: network-manager: Daemon crashes immediately upon startup

Am 23.10.18 um 16:33 schrieb tamaramaca...@protonmail.com: > Package: network-manager > Version: 1.14.2-2 > Severity: important > > Currently, upon starting with systemd, the network-manager daemon > immediately crashes. This began right after upgrading it to the latest > version. > Can you

[Pkg-utopia-maintainers] Bug#842036: nmcli does not return after bringing up a connection

Control: tags -1 + moreinfo On Tue, 25 Oct 2016 14:48:17 +0200 Marc Haber wrote: > Package: network-manager > Version: 1.4.2-2 > Severity: minor > File: /usr/bin/nmcli > > Hi, > > on my notebook, nmcli does - sometimes - not return to the shell after > bringing up the wireless LAN: > >

[Pkg-utopia-maintainers] Bug#820174: network-manager: fails to start: "Failed at step NAMESPACE"

On Wed, 06 Apr 2016 10:13:07 +0200 Stephen Kitt wrote: > Package: network-manager > Version: 1.1.92-1 > Severity: important > > Dear Maintainer, > > The upgrade from 1.1.91-3 to 1.1.92-1 failed, with > NetworkManager.service unable to start the service. The logs say > > Apr 06 10:07:14

[Pkg-utopia-maintainers] Bug#823921: firewalld: fails to start and so delays system boot

Control: tags -1 + moreinfo On Tue, 10 May 2016 15:08:16 +0200 =?utf-8?q?Uwe_Kleine-K=C3=B6nig?= wrote: > Package: firewalld > Version: 0.4.1.2-1 > Severity: normal > > Hello, > > $ sudo journalctl | grep firewalld > May 10 14:57:04 perseus systemd[1]: Starting firewalld - dynamic

[Pkg-utopia-maintainers] Bug#909574: Bug#909574: firewalld: FirewallBackend=nftables breaks NAT networks in libvirt

Hi Am 10.11.18 um 15:47 schrieb Ralf Jung: > According to https://bugzilla.redhat.com/show_bug.cgi?id=1638342, Fedora > changed > the default for FirewallBackend back until libvirt works with > FirewallBackend=nftables. Might be worth doing that in Debian as well? I was under the impression

[Pkg-utopia-maintainers] Bug#913729: wrong modinfo path if compiled on merged-usr system and executed on unmerged system

Package: firewalld Version: 0.6.3-2 Severity: serious Trying to start firewalld, I get: Nov 14 13:05:04 pluto firewalld[1126]: WARNING: modinfo command is missing, not able to detect conntrack helpers. Nov 14 13:05:04 pluto firewalld[1126]: ERROR: Failed to load nf_conntrack module: Nov 14

[Pkg-utopia-maintainers] Bug#910139: Bash tabcompletion triggers a polkit check (ask for a password)

Control: tags -1 + moreinfo On Wed, 03 Oct 2018 09:57:53 +0200 Laurent Bigonville wrote: > Package: firewalld > Version: 0.6.2-1 > Severity: normal > > Hi, > > When using firewall-cmd in bash (as normal user) and using tab to > complete the list of option, it trigger a polkit check that asks

[Pkg-utopia-maintainers] Bug#913662: Switch default backend to nftables

Package: firewalld Version: 0.6.3-2 Severity: normal Upstream uses nftables as the default backend. There are still integration issues with e.g. docker or libvirt, which still use iptables, and are broken by this change, so the Debian package was patched to revert back to iptables. See [1]. Once

[Pkg-utopia-maintainers] Bug#896818: libnma over GI not working

Hi Fabio On Tue, 24 Apr 2018 16:32:10 +0200 Fabio Fantoni wrote: > Package: network-manager-applet > Version: 1.4.4-1 > Severity: important > Tags: stretch > > Trying to use libnma over GI from a python script is not working at all and > can also cause crash of other software using it. > This

[Pkg-utopia-maintainers] Bug#892998: libnm/client: proxy *_enabled and metered properties to the wrong object make application using it crashing

Hi Fabio On Thu, 15 Mar 2018 12:22:40 +0100 Fabio Fantoni wrote: > Package: network-manager > Version: 1.6.2-3 > Severity: important > Tags: stretch > > Trying Cinnamon next version (with switch to libnm) on Stretch was find that > it crash for this "small" upstream fix missed: > libnm/client:

[Pkg-utopia-maintainers] Bug#910670: Bug#910670: network-manager-openvpn: unable to import valid configuration file

Am 09.10.18 um 16:38 schrieb Bruno BEAUFILS: > Package: network-manager-openvpn > Version: 1.8.6-1 > Severity: important > > Dear Maintainer, > > Current network-manager-openvpn (or network-manager-openvpn-gnome) do not let > one import an .ovpn file which is perfectly valid, aka usable with

[Pkg-utopia-maintainers] Bug#910511: Bug#910511: network-manager-openvpn: openvpn 2.4 in stable supports tls-crypt, but nm-openvpn 1.2.8 in stable doesn't

Am 07.10.18 um 15:55 schrieb Gijs Molenaar: > Package: network-manager-openvpn > Version: 1.2.8-2 > Severity: important > > Dear Maintainer, > > I'm developing a UI wrapper around various platforms for an open VPN service. > Debian 9 is one of our targetted platforms. We have tls-crypt enabled

[Pkg-utopia-maintainers] Bug#910511: Bug#910511: network-manager-openvpn: openvpn 2.4 in stable supports tls-crypt, but nm-openvpn 1.2.8 in stable doesn't

Am 07.10.18 um 16:15 schrieb Michael Biebl: > That said, 1.2.10 could be provided via stretch-backports: > https://backports.debian.org/ Fwiw, if we go the stretch-backports route, then it would probably make sense to use the current version from testing, i.e. 1.8.4-1 -- Why is it th

[Pkg-utopia-maintainers] Bug#910511: Bug#910511: Bug#910511: network-manager-openvpn: openvpn 2.4 in stable supports tls-crypt, but nm-openvpn 1.2.8 in stable doesn't

Am 07.10.18 um 17:30 schrieb Gijs Molenaar: > Hi Michael, > > > Op zo 7 okt. 2018 om 16:36 schreef Michael Biebl <mailto:bi...@debian.org>>: > > Am 07.10.18 um 16:15 schrieb Michael Biebl: > > That said, 1.2.10 could be provided via

[Pkg-utopia-maintainers] Bug#907902: Bug#907902: network-manager-openvpn won't save changes in username or password

On 9/4/18 03:39, Jape Person wrote: > On 09/03/2018 07:22 PM, Michael Biebl wrote: >> On 9/4/18 00:25, Jape Person wrote: >>> The software gives no indication that anything is wrong other than the >>> fact that the "Editing " dialog that >>> come

[Pkg-utopia-maintainers] Bug#907902: Bug#907902: network-manager-openvpn won't save changes in username or password

On 9/4/18 05:34, Michael Biebl wrote: > This is what I'm getting on the console: > > ** Message: 05:28:17.858: Cannot save connection due to error: Invalid > setting VPN: ca: No key set Nvm, seems to be a genuine upstream issue, see https://gitlab.gnome.org/GNOME/network-manager-a

[Pkg-utopia-maintainers] Bug#907902: Bug#907902: network-manager-openvpn won't save changes in username or password

On 9/4/18 00:25, Jape Person wrote: > The software gives no indication that anything is wrong other than the > fact that the "Editing " dialog that > comes up doesn't activate the "Save" button when I change the contents > of the user name or password fields. Can you share such a .ovpn file? --

[Pkg-utopia-maintainers] Bug#907902: Bug#907902: network-manager-openvpn won't save changes in username or password

Control: tags -1 moreinfo unreproducible On 9/3/18 23:14, Jape Person wrote: > Package: network-manager-openvpn > Version: 1.8.4-1 > Severity: important > > Dear Maintainer, > > > To duplicate the issue, use Edit Connections function of network-manager. > > Attempt to edit an imported openvpn

Re: [Pkg-utopia-maintainers] Bug#909356: iwd 0.8 not compatible with NM < 1.14

Am 22.09.18 um 12:41 schrieb Adrian Bunk: > On Sat, Sep 22, 2018 at 11:22:07AM +0200, Andreas Henriksson wrote: >> Package: iwd >> Version: 0.8-1 >> Severity: serious >> >> Filing this bug report to block iwd 0.8 from migrating to testing (yet). >> >> The NetworkManager support for iwd has been

[Pkg-utopia-maintainers] Bug#909657: Bug#909657: firewalld: firewall rules don't work after change to nftables backend

Am 26.09.18 um 14:53 schrieb Pavel Kreuzt: > kernel is 4.18 > In that case, can you please file that issue upstream at https://github.com/firewalld/firewalld/issues and report back with the bug number. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the

[Pkg-utopia-maintainers] Bug#909657: Bug#909657: firewalld: firewall rules don't work after change to nftables backend

Am 26.09.18 um 14:01 schrieb Pavel Kreuzt: > Package: firewalld > Version: 0.6.2-1 > Severity: normal > > Dear Maintainer, > > after upgrade to firewalld 0.6.2, in which backend changed to nftables by > default, a custom script I use to enable multicast when needed stoppped > working. Its

[Pkg-utopia-maintainers] Bug#909657: Bug#909657: firewalld: firewall rules don't work after change to nftables backend

Control: forwarded -1 https://github.com/firewalld/firewalld/issues/399 Am 26.09.18 um 15:49 schrieb Pavel Kreuzt: > Reported upstream as: > > https://github.com/firewalld/firewalld/issues/399 Thank, marking accordingly. Btw, please always CC the bug report email address. Michael -- Why is

[Pkg-utopia-maintainers] Bug#909574: Bug#909574: Bug#909574: firewalld: FirewallBackend=nftables breaks NAT networks in libvirt

Control: forwarded -1 https://github.com/firewalld/firewalld/issues/397 Am 25.09.18 um 16:33 schrieb Tomas Janousek: > Hi, > > On Tue, Sep 25, 2018 at 04:25:25PM +0200, Michael Biebl wrote: >> Could you raise this upstream please at >> https://github.com/firewall

[Pkg-utopia-maintainers] Bug#908116: firewalld: blocks multicast dns resolution for home zone

On Thu, 06 Sep 2018 11:20:41 +0200 Sergio Villar Senin wrote: > Package: firewalld > Version: 0.6.1-2 > Severity: normal > > Dear Maintainer, > >* What led up to the situation? > >Upgrading to sid's 0.6.1-2 > >* What exactly did you do (or not do) that was effective (or >

[Pkg-utopia-maintainers] Bug#914015: Bug#914015: bus-daemon: Activated service 'org.freedesktop.systemd1' failed

Am 18.11.18 um 15:52 schrieb Helge Kreutzmann: > Package: dbus > Version: 1.12.10-1 > Severity: minor > > At the very end of the boot, just after the first user logs in > (usually using sddm / X) I get the following messages in my logs: > Nov 18 07:02:33 samd dbus-daemon[2879]: [session uid=1000

[Pkg-utopia-maintainers] Bug#914015: Bug#914015: Bug#914015: bus-daemon: Activated service 'org.freedesktop.systemd1' failed

Am 18.11.18 um 18:00 schrieb Helge Kreutzmann: > On Sun, Nov 18, 2018 at 04:19:10PM +0100, Michael Biebl wrote: >> Am 18.11.18 um 15:52 schrieb Helge Kreutzmann: >> Do you have dbus-user-session installed? > > No. > > I looked at the description of dbus-user-se

[Pkg-utopia-maintainers] Bug#917633: Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments

Am 29.12.18 um 17:05 schrieb Alf Gaida: > if [ "$1" = "configure" ]; then > # we ship udev rules, so trigger an update > -udevadm trigger --subsystem-match=block --action=change > +udevadm trigger --subsystem-match=block --action=change | true > > fi I guess you meant "||" here.

[Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments

Am 29.12.18 um 16:28 schrieb Alf Gaida: > Package: udisks2 > Version: 2.8.1-3 > Severity: important > > Dear Maintainer, > > tried to install udisks2 in a chroot: > > Setting up udisks2 (2.8.1-3) ... > Failed to scan devices: No such file or directory > dpkg: error processing package udisks2

[Pkg-utopia-maintainers] Bug#917633: Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments

Am 29.12.18 um 18:59 schrieb Alf Gaida: > On 29.12.18 18:54, Michael Biebl wrote: >> I guess you meant "||" here. >> >> That seems like a reasonable change. Do you want to file a MR for that? >> > > Yes - otherwise it would be cool to know the rea

[Pkg-utopia-maintainers] Bug#918353: Bug#918353: upower.service fails to start

Am 05.01.19 um 15:56 schrieb olga906...@web.de: > Dear Maintainer, > > almost all my problems were solved by removing/purging all packages from > unstable (only 47 - one of these have to have caused the problem). > So this issue is fixed now and the bug report can be closed? -- Why is it

[Pkg-utopia-maintainers] Bug#916791: Bug#916791: firewalld: nftables backend not happy with --set-log-denied={unicast, broadcast, multicast}

Hi Sam! Am 18.12.18 um 17:08 schrieb Sam Morris: > > firewalld doesn't seem to be happy with any log setting other than 'all' > and 'off'. > > # firewall-cmd --set-log-denied=unicast > # journalctl -u firewalld -e This sounds a lot like https://github.com/firewalld/firewalld/pull/410 This

Re: [Pkg-utopia-maintainers] Intent to NMU upower to fix longstanding l10n and documention bugs

Hi Helge, hi Ola! Am 19.12.18 um 19:06 schrieb Helge Kreutzmann: > Hello Ola, > I propose to NMU upower to solve the long standing translation bug > 858851 and the request for more documentation (654164). For the latter > adding the output of --help (and maybe a few words?) should solve the >

Re: [Pkg-utopia-maintainers] Bug#863333: Intent to NMU upower to fix longstanding l10n and documention bugs

Am 19.12.18 um 19:55 schrieb Helge Kreutzmann: > Please go ahead and forward it to upstream. I prefer if the author of a patch forwards it to upstream in case upstream has further questions. I don't like to be a bug proxy (and a bottle neck). -- Why is it that all of the instruments seeking

[Pkg-utopia-maintainers] Bug#914959: Bug#914959: network-manager: Unable to use machine account for 802.1x authorization

Hello Am 29.11.18 um 06:29 schrieb kpp: > Package: network-manager > Version: 1.6.2-3+deb9u2 > Severity: normal > > Dear maintainer. > > If a machine is a member of AD domain and security policy assumes 802.1x > authorization it is impossible to use machine's account for authorization. > It is

[Pkg-utopia-maintainers] Moving dbus policy files to /usr/share/dbus-1/system.d

Hi Simon, dbus since 1.9.18 support policy files being installed in /usr/share/dbus-1/system.d/ Atm only very few packages use the "new" location, most prominently systemd. I was wondering if you had any plans of getting packages updated to move their D-Bus policy files from

[Pkg-utopia-maintainers] Bug#914694: Bug#914694: firewall-cmd --reload fails: RULE_REPLACE failed (No such file or directory): rule in chain {INPUT, OUTPUT}

Hi Eric, I recently switched firewalld back to iptables given the feedback in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909574 This seems to have caused a regression. Does this specific problem ring a bell? Regards, Michael Am 26.11.18 um 12:30 schrieb Martin Pitt: > Package: firewalld

[Pkg-utopia-maintainers] Bug#914948: Bug#914948: Might be a kernel bug

You could try with a kernel from stretch-backports Am 30. November 2018 19:56:33 MEZ schrieb EP : >Hello! > >https://bugzilla.redhat.com/show_bug.cgi?id=1579046 > >This bug report and some posts in debianforum.de make me think that it >is an already fixed kernel bug (fixed in newer kernel

[Pkg-utopia-maintainers] Bug#926328: Bug#926328: network-manager-gnome: nm-applet crashes with a coredump when try to create a new WiFi network

Am 03.04.19 um 17:15 schrieb Jiang Jun: > Package: network-manager-gnome > Version: 1.8.20-1 > Severity: normal > > Dear Maintainer, > > I am experiencing a crash every time I try to create a hot-spot WiFi using nm- > applet menu. The steps were: > > 1. Click nm-applet(I am using Xfce4 and

[Pkg-utopia-maintainers] Bug#926504: Bug#926504: No hibernate option in shutdown menu

Am 06.04.19 um 10:10 schrieb Aleksey Midenkov: > Package: policykit-1 > Version: 0.105-4 > > Desktop envs suffer from lack of hibernation option. The workaround for > this is cat > > /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla > > [Re-enable hibernate by default in

[Pkg-utopia-maintainers] Bug#925380: Bug#925380: network-manager-gnome: ifupdown no longer appears in the applet and no longer does not detects hotplug event

Control: tags -1 moreinfo Am 24.03.19 um 01:52 schrieb Jack Underwood: > Package: network-manager-gnome > Version: 1.8.20-1 > Severity: important > > Dear Maintainer, > > Sometime in (late) 2018 the NetworkManager stopped showing ifupdown (eth0) in > the interfaces, iirc > eth0 would only

[Pkg-utopia-maintainers] Bug#743138: Bug#743138: Bug#743138: [Needs upstream 0.9.10 release] Please only enable ifupdown plugin when ifupdown installed

Hi Guus Am 26.02.19 um 22:10 schrieb Guus Sliepen: > On Tue, Feb 26, 2019 at 07:24:27PM +0100, Michael Biebl wrote: > >> On Sun, 10 Feb 2019 11:03:55 +0100 Andrej Shadura >> wrote: >> >>>> this is fixed a while ago. >>>> >>>> Handl

[Pkg-utopia-maintainers] Bug#923244: Bug#923244: policykit-1: Please support elogind backend

Hi Am 25.02.19 um 12:49 schrieb Mark Hindley: > Package: policykit-1 > Version: 0.105-25 > Severity: normal > > Dear Maintainers, > > policykit-1 needs specific support for elogind, an alternative implementation > of > the DBus login1 API for systems not running systemd as pid 1. Without this

[Pkg-utopia-maintainers] Bug#743138: Bug#743138: Bug#743138: Bug#743138: [Needs upstream 0.9.10 release] Please only enable ifupdown plugin when ifupdown installed

Am 27.02.19 um 08:09 schrieb Guus Sliepen: > On Tue, Feb 26, 2019 at 10:37:28PM +0100, Michael Biebl wrote: > >>>> Andrej, I'm fine with dropping ifupdown from the default NM >>>> configuration if the ifupdown package is going to ship such a config >>>&

[Pkg-utopia-maintainers] Bug#923387: Bug#923387: udisks2: Please support new logind virtual packages

Control: tags -1 + moreinfo Am 27.02.19 um 13:26 schrieb Mark Hindley: > Package: udisks2 > Version: 2.1.3-4 > Severity: normal > Tags: patch > > Dear Maintainer, > > Please change udisks2 to use the new default-logind and logind virtual > packages. > This will enable udisks2 to also be used

[Pkg-utopia-maintainers] Bug#923244: Bug#923244: Bug#923244: policykit-1: Please support elogind backend

Hi Am 27.02.19 um 18:12 schrieb Mark Hindley: > Micael, > > Thanks. This is very helpful. > > On Wed, Feb 27, 2019 at 02:00:16PM +0100, Michael Biebl wrote: >> I think, only 3) has a chance to work in Debian (or a slight >> modification of it). > > Would you

Re: [Pkg-utopia-maintainers] Bug#923244: Bug#923244: libelogind ABI compatibility pending

Am 06.03.19 um 10:07 schrieb Mark Hindley: > On Tue, Mar 05, 2019 at 09:11:28PM +0100, Michael Biebl wrote: >>>> This has the potential for some interesting breakage, like the real >>>> systemd being installed and used together with libelogind0. >>>> We

[Pkg-utopia-maintainers] Bug#922554: Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

Control: reassign -1 src:curl Control: found -1 7.64.0-1 Control: tags -1 + patch fixed-upstream Am 05.03.19 um 10:10 schrieb Dominique Dumont: > On Tue, 05 Mar 2019 09:03:53 +0100 Dominique Dumont wrote: >> They probably patched curl with [1] following the resolution if this curl >> bug [2]. I

Re: [Pkg-utopia-maintainers] Bug#923244: Bug#923244: libelogind ABI compatibility pending

Am 05.03.19 um 18:17 schrieb Mark Hindley: > On Tue, Mar 05, 2019 at 05:58:30PM +0100, Michael Biebl wrote: >> Am 05.03.19 um 15:34 schrieb Mark Hindley: >>> >>> reassign -1 elogind >>> retitle -1 Make libelogind0 ABI compatible with libsystemd0 >>> tag

[Pkg-utopia-maintainers] Bug#743138: Bug#743138: [Needs upstream 0.9.10 release] Please only enable ifupdown plugin when ifupdown installed

On Sun, 10 Feb 2019 11:03:55 +0100 Andrej Shadura wrote: > > this is fixed a while ago. > > > > Handling of hostname moved from the settings plugin to NMSettings. > > Also, hostnamed is supported as one of several options. > > > > There were many changes there, so I am not going to hunt down

[Pkg-utopia-maintainers] Bug#916187: network-manager-gnome no longer creates system connections for netdev group

On Mon, 10 Dec 2018 16:29:02 -0500 Dean Serenevy wrote: > Package: network-manager-gnome > Version: 1.8.18-2 > Severity: normal > > Dear Maintainer, > > Hello, it seems that upstream changes have broken part of > Allow-to-create-connections-without-admin-privileges.patch (written to > address

[Pkg-utopia-maintainers] Bug#918081: /usr/bin/nm-applet: Cellular icon overlap in xfce4 notification tray

Control: tags -1 + moreinfo On Thu, 03 Jan 2019 11:10:00 +0700 Minh Duc Vo wrote: > Package: network-manager-gnome > Version: 1.8.18-2 > Severity: minor > File: /usr/bin/nm-applet > Tags: patch > > The icon of nm-applet when mobile broadband connection is used are overlapped > with other icons,

[Pkg-utopia-maintainers] Bug#922916: network-manager: I think it's the same as #922554. No wifi connection is possible.

Control: tags -1 + moreinfo On Thu, 21 Feb 2019 15:37:15 -0500 Steve Newcomb wrote: > Package: network-manager > Version: 1.14.4-4 > Severity: normal > > Dear Maintainer, > > >* What led up to the situation? > Regular maintenance via aptitude (apt update). >* What exactly did you do

[Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

Control: tags -1 + moreinfo Do you have network-manager-config-connectivity-debian installed or connectivity checking enabled otherwise? Is the server reachable for the connectivity check reachable? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed

[Pkg-utopia-maintainers] Bug#915315: network-manager: wifi always on at startup

Control: tags -1 + moreinfo On Sun, 02 Dec 2018 20:59:12 +0300 "ZakharenkoA.D." wrote: > Package: network-manager > Version: 1.14.4-4 > Severity: normal > > Dear Maintainer, > > What led up to the situation, and what did I do: > I tried to make wireless led working on Asus N56vj notebook. The

[Pkg-utopia-maintainers] Bug#924142: Bug#924142: udisks: crashes when i plug in some disk

Am 09.03.19 um 21:54 schrieb treaki: > Source: udisks There is no udisks package in the archive (anymore) > Version: crashes when i plug in some disk If you meant to file it against udisks2, please include the output of reportbug --template udisks2 -- Why is it that all of the instruments

[Pkg-utopia-maintainers] Bug#926866: Bug#926866: network-manager: Typo in help concerning man pages section

Am 11.04.19 um 15:06 schrieb J. A. Corbal: > The last line of the command 'nmcli' says: > > Consult nmcli(1) and nmcli-examples(5) manual pages for complete usage > details. > > But there's no man page 'nmcli-examples (5)'. The actual man section > is 7. It should say: > > Consult

[Pkg-utopia-maintainers] Bug#910124: Bug#910124: network-manager-gnome: option to import/export WiFi config as a QR code

Am 01.06.19 um 21:37 schrieb Salvatore Bonaccorso: > On Fri, May 31, 2019 at 02:57:13PM +0200, Salvatore Bonaccorso wrote: >> Is that the same as src:qr-code-generator as present in unstable, cf. >> https://tracker.debian.org/pkg/qr-code-generator . >> >> Is the network-manager-applet embedded

[Pkg-utopia-maintainers] Bug#910124: network-manager-gnome: option to import/export WiFi config as a QR code

Am 30.05.19 um 04:36 schrieb Paul Wise: > On Wed, 2019-05-29 at 12:57 +0200, Michael Biebl wrote: > >>> This has been implemented in 1.8.22. >> This is apparently implemented as well. > > Thanks for the notice. > >> https://gitlab.gnome.org/GNOME/netw

[Pkg-utopia-maintainers] Bug#910124: network-manager-gnome: option to import/export WiFi config as a QR code

On Wed, 03 Oct 2018 11:38:47 +0800 Paul Wise wrote: > Package: network-manager-gnome > Version: 1.8.18-1 > Severity: wishlist > > I recently discovered that there is a defacto standard for converting > WiFi configs to QR codes and back again. > > https://qifi.org/ >

[Pkg-utopia-maintainers] Bug#910124: network-manager-gnome: option to import/export WiFi config as a QR code

Am 29.05.19 um 12:48 schrieb Michael Biebl: > On Wed, 03 Oct 2018 11:38:47 +0800 Paul Wise wrote: >> Package: network-manager-gnome >> Version: 1.8.18-1 >> Severity: wishlist >> >> I recently discovered that there is a defacto standard for converting >>

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

Am 16.05.19 um 00:27 schrieb Vincent Lefevre: > 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:

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

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 via lo, even if eth0 is down). > > Yes, /etc/resolv.conf contains >

  1   2   3   4   5   >