Your message dated Fri, 24 Jun 2016 18:29:45 +0200 with message-id <[email protected]> and subject line Re: Bug#815168: log has caused the Debian Bug report #815168, regarding apparmor-profiles-extra: Pidgin not able to connect to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 815168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815168 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: apparmor-profiles-extra Version: 1.6 Severity: important Dear Maintainer, enabling AppArmor with the Pidgin profile from apparmor-profiles-extra version 1.6 on Debian testing disables Pidgin from successfully connecting to servers ("dnsquery: Error resolving XXX.XX ... Unable to find alternative connection methods ... Connection error" or with manual nslookup: "connection: Connection error on 0xXXXXXXXX (reason: 0 description: host unknown)"). I'm unsure whether this is connected to some recent software update to i.e. network-manager. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.3.0-1-686-pae Init: systemd (via /run/systemd/system) Versions of packages apparmor-profiles-extra depends on: ii apparmor 2.10-3 apparmor-profiles-extra recommends no packages. apparmor-profiles-extra suggests no packages. -- no debconf information ---- Sent using GuerrillaMail.com Block or report abuse: https://www.guerrillamail.com/abuse/?a=UlR2CAQUY7YAjx369HsdexXJA8WC1Q%3D%3D
--- End Message ---
--- Begin Message ---intrigeri wrote (09 May 2016 18:52:38 GMT) : > Thank you. I believe this problem was actually in > /etc/apparmor.d/abstractions/nameservice, and has been fixed when we > uploaded apparmor 2.10-4 a while ago. Can you please try and confirm? Closing as a duplicate of #813835.
--- End Message ---
