Bug#1074363: monitoring-plugins-check-smart: Don't depend on nagios-nrpe-server

[Frederik Himpe]

Source: monitoring-plugins-check-smart
Version: 6.14.1-2
Severity: normal

Dear Maintainer,

check_smart.pl can be ran locally or from an icinga2 agent, without
nagios-nrpe-server, so it should not have a hard dependency on
nagios-nrpe-server.

-- System Information:
Debian Release: 12.5
  APT prefers stable-security
  APT policy: (810, 'stable-security'), (810, 'stable'), (809, 
'proposed-updates'), (710, 'oldstable-security'), (710, 'oldstable'), (709, 
'oldstable-proposed-updates'), (310, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.32-frehi12 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1060222: aide-common: 31_aide_php-fpm defines PHPVERSION 2.2 instead of 8.2

[Frederik Himpe]

On Mon, 2024-01-08 at 22:01 +0100, Marc Haber wrote:
> Control: tag -1 confirmed
> 
> Hi,
> 
> 
> On Sun, Jan 07, 2024 at 09:10:17PM +0100, Frederik Himpe wrote:
> > The config file 31_aide_php-fpm defines PHPVERSION as 2.2 instead
> > of 8.2.
> 
> thanks for spotting this. Pardon the stupid question, all PHP
> packages
> in a Debian version us the same PHP version, right? Maybe it would be
> a
> good idea to deliver PHPVERSION it its own config snippet just in
> case
> that multiple PHP related rules have to refer to the versioN?

That might indeed not be a bad idea.

By the way, I also noticed there is still 31_aide_php7 and its rules
seem to conflict with rules in 31_aide_php-common, so I guess
31_aide_php7 can be dropped.

I'm currently also making some new configuration files for other
services and I am happy to contribute them if you are interested. What
would be the best way to send them? Creating pull requests on Salsa?

-- 
Frederik Himpe 

Bug#1060222: aide-common: 31_aide_php-fpm defines PHPVERSION 2.2 instead of 8.2

[Frederik Himpe]

Package: aide-common
Version: 0.18.6.2.20231120-2
Severity: normal

Dear Maintainer,

The config file 31_aide_php-fpm defines PHPVERSION as 2.2 instead of 8.2.


-- System Information:
Debian Release: 12.4
  APT prefers stable-security
  APT policy: (810, 'stable-security'), (810, 'stable'), (809, 
'proposed-updates'), (710, 'oldstable-security'), (710, 'oldstable'), (709, 
'oldstable-proposed-updates'), (310, 'testing'), (200, 'unstable'), (160, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-16-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aide-common depends on:
ii  aide0.18.6.2.20231120-2
ii  debconf [debconf-2.0]   1.5.82
ii  liblockfile11.17-1+b1
ii  systemd [systemd-sysusers]  252.19-1~deb12u1
ii  ucf 3.0043+nmu1

Versions of packages aide-common recommends:
ii  bsd-mailx [mailx]   8.1.2-0.20220412cvs-1
ii  s-nail  14.9.24-2
ii  systemd-cron [cron-daemon]  2.3.0-1~bpo12+1

aide-common suggests no packages.

-- debconf information excluded

Bug#1049861: unhide: Dependeny on net-tools not required any more

[Frederik]

Package: unhide
Version: 20220611-1
Severity: normal

Dear Maintainer,

The unhide package depends on net-tools because unhide-tcp uses netstat to find
open ports. However, since version 20110113 of unhide, it uses ss by
default on Linux (https://github.com/YJesus/Unhide/blob/master/NEWS)

iproute2, which contains ss, is already a dependeny of unhide, so the
dependency on netstat can be dropped.


-- System Information:
Debian Release: 12.1
  APT prefers stable-security
  APT policy: (810, 'stable-security'), (810, 'stable'), (809, 
'proposed-updates'), (710, 'oldstable-security'), (710, 'oldstable'), (709, 
'oldstable-proposed-updates'), (310, 'testing'), (200, 'unstable'), (160, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages unhide depends on:
ii  iproute2   6.1.0-3
ii  libc6  2.36-9+deb12u1
ii  lsof   4.95.0-1
ii  net-tools  2.10-0.1
ii  procps 2:4.0.2-3
ii  psmisc 23.6-1

unhide recommends no packages.

Versions of packages unhide suggests:
ii  rkhunter  1.4.6-11

-- no debconf information

Bug#1031825: [Pkg-nagios-devel] Bug#1031825: icinga-php-library: Creation of dynamic property is deprecated in PHP 8.2

[Frederik Himpe]

Sebastiaan Couwenberg schreef op 2023-02-23 17:59:


 skip_validation is not a documented resource option:

  
https://icinga.com/docs/icinga-web/latest/doc/04-Resources/#configuration


 You likely have this in /etc/icingaweb2/resources.ini though, can you
confirm that?


Yes:
my icingadb resource has:
skip_validation = "0"

This was set by the icingaweg2 setup: there is an option "Skip 
validation" which ignores any errors if it cannot connect to the 
database. Some screenshots with this option are here: 
https://github.com/Icinga/icingaweb2/issues/4291


Anyway, I temporarily used this option during the setup but I don't need 
this any more so I removed it. The errors are gone now and everything 
works as expected.


--
Frederik Himpe 
Vrije Universiteit Brussel

Bug#1031825: [Pkg-nagios-devel] Bug#1031825: icinga-php-library: Creation of dynamic property is deprecated in PHP 8.2

[Frederik Himpe]

(Sorry for the double post, sending this to the bug report too.)

Sebastiaan Couwenberg schreef op 2023-02-23 17:45:

Control: tags -1 moreinfo

Hi Frederik,

On 2/23/23 17:05, Frederik wrote:
I'm using Debian Bookworm with icinga-php-library 0.10.1-1 and PHP 
8.2. When I log in in icingaweb2, I see three times this message in 
the left sidebar between the search bar in the menu:
Deprecated: Creation of dynamic property 
ipl\Sql\Config::$skip_validation is deprecated in 
/usr/share/icinga-php/ipl/vendor/ipl/sql/src/Config.php on line 32


Are you using icinga2-ido-mysql by chance?

I cannot reproduce the issue with icinga2-ido-pgsql


No, I'm not using any of the icinga2-ido-* packages, I am using icingadb 
with icingadb-web instead.


--
Frederik Himpe 
Vrije Universiteit Brussel

Bug#1031825: icinga-php-library: Creation of dynamic property is deprecated in PHP 8.2

[Frederik]

Package: icinga-php-library
Version: 0.10.1-1
Severity: normal
Tags: upstream

Dear Maintainer,

I'm using Debian Bookworm with icinga-php-library 0.10.1-1 and PHP 8.2. When I 
log in in icingaweb2, I see three times this message in the left sidebar 
between the search bar in the menu:
Deprecated: Creation of dynamic property ipl\Sql\Config::$skip_validation is 
deprecated in /usr/share/icinga-php/ipl/vendor/ipl/sql/src/Config.php on line 32

Upstream report: https://github.com/Icinga/ipl-sql/issues/69

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'stable-security'), (700, 'stable'), 
(650, 'proposed-updates'), (200, 'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages icinga-php-library depends on:
ii  icinga-php-thirdparty0.11.0-2
ii  php-intl 2:8.2+93
ii  php8.2-cgi [php-json]8.2.2-3
ii  php8.2-cli [php-json]8.2.2-3
ii  php8.2-common [php-pdo]  8.2.2-3
ii  php8.2-fpm [php-json]8.2.2-3
ii  php8.2-intl [php-intl]   8.2.2-3

icinga-php-library recommends no packages.

icinga-php-library suggests no packages.

-- no debconf information

Bug#1031260: puppetserver: Needs OpenJDK 17, but does not depend on this version

[Frederik]

Package: puppetserver
Version: 7.9.5-1
Severity: normal

On a system with only OpenJDK 11 installed, the puppetserver service
fails to start with this error:

Feb 14 08:28:38 puppet systemd[1]: Starting puppetserver.service - Puppet 
Server...
Feb 14 08:28:50 puppet java[1942954]: Exception in thread "main" Syntax error 
macroexpanding at 
(puppetlabs/services/request_handler/request_handler_core.clj:1:1).
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.Compiler.load(Compiler.java:7665)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RT.loadResourceScript(RT.java:381)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RT.loadResourceScript(RT.java:372)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RT.load(RT.java:459)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RT.load(RT.java:424)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load$fn__6908.invoke(core.clj:6161)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load.invokeStatic(core.clj:6160)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load.doInvoke(core.clj:6144)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RestFn.invoke(RestFn.java:408)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_one.invokeStatic(core.clj:5933)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_one.invoke(core.clj:5928)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_lib$fn__6850.invoke(core.clj:5975)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_lib.invokeStatic(core.clj:5974)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_lib.doInvoke(core.clj:5953)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RestFn.applyTo(RestFn.java:142)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$apply.invokeStatic(core.clj:669)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_libs.invokeStatic(core.clj:6016)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_libs.doInvoke(core.clj:6000)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RestFn.applyTo(RestFn.java:137)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$apply.invokeStatic(core.clj:669)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$require.invokeStatic(core.clj:6038)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$require.doInvoke(core.clj:6038)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RestFn.invoke(RestFn.java:551)
Feb 14 08:28:50 puppet java[1942954]: at 
puppetlabs.services.request_handler.request_handler_service$eval18108$loading__6789__auto18109.invoke(request_handler_service.clj:1)
Feb 14 08:28:50 puppet java[1942954]: at 
puppetlabs.services.request_handler.request_handler_service$eval18108.invokeStatic(request_handler_service.clj:1)
Feb 14 08:28:50 puppet java[1942954]: at 
puppetlabs.services.request_handler.request_handler_service$eval18108.invoke(request_handler_service.clj:1)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.Compiler.eval(Compiler.java:7194)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.Compiler.eval(Compiler.java:7183)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.Compiler.load(Compiler.java:7653)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RT.loadResourceScript(RT.java:381)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RT.loadResourceScript(RT.java:372)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RT.load(RT.java:459)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RT.load(RT.java:424)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load$fn__6908.invoke(core.clj:6161)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load.invokeStatic(core.clj:6160)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load.doInvoke(core.clj:6144)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RestFn.invoke(RestFn.java:408)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_one.invokeStatic(core.clj:5933)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_one.invoke(core.clj:5928)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_lib$fn__6850.invoke(core.clj:5975)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_lib.invokeStatic(core.clj:5974)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_lib.doInvoke(core.clj:5953)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.lang.RestFn.applyTo(RestFn.java:142)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$apply.invokeStatic(core.clj:669)
Feb 14 08:28:50 puppet java[1942954]: at 
clojure.core$load_libs.invokeStatic(core.clj:6016)
Feb 14 08:28:50 puppet java[1942954]: at 

Bug#1013902: RFS: bosch_career/1.0.1 [ITP] -- Avoid possible misuse of a package ID

[Frederik]

Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: debian-report...@frederikheld.de

Dear Mentors,

I am looking for a sponsor for my package "bosch_career":

* Package name: bosch_career
  Version: 1.0.1
* URL: https://github.com/frederikheld/bosch_career
* License: GNU GPLv3
* VCS: https://github.com/frederikheld/bosch_career

The Source builds the following binary packages:

  bosch_career - Educational package about package security and the question 
what 'being a software company' means.

To access further information about this package, please visit the following 
URL:

  https://github.com/frederikheld/bosch_career/README.md
  
https://github.com/frederikheld/bosch_career/blob/main/bosch_career/__main__.py

Regards,
Frederik

Bug#992000: modsecurity-crs: Needs update to 3.3.2 for CVE-2021-35368

[Frederik Himpe]

Package: modsecurity-crs
Version: 3.3.0-1
Severity: normal

Dear Maintainer,

The version of modsecurity-crs contains a vulnerability and needs to be
updated to 3.3.2 to get the security fix:

https://coreruleset.org/20210630/cve-2021-35368-crs-request-body-bypass/

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (800, 'testing'), (750, 'proposed-updates'), (700, 'stable'), 
(600, 'oldstable'), (200, 'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

modsecurity-crs depends on no packages.

Versions of packages modsecurity-crs recommends:
ii  libapache2-mod-security2  2.9.3-3

Versions of packages modsecurity-crs suggests:
pn  geoip-database-contrib  
pn  lua 
pn  python  
ii  ruby1:2.7+2

-- Configuration Files:
/etc/modsecurity/crs/crs-setup.conf changed [not included]

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/share/modsecurity-crs/rules/REQUEST-903.9002-WORDPRESS-EXCLUSION-RULES.conf
 (from modsecurity-crs package)

Bug#989474: lutris: Needs patch for Python 3.9 compatibility

[Frederik Himpe]

Package: lutris
Version: 0.5.8.3-1
Severity: normal
Tags: patch
X-Debbugs-Cc: frede...@frehi.be

Installation of the game Obduction from GOG failed with this message:
AttributeError("'xml.etree.ElementTree.Element' object has no attribute
'getchildren'")

This is fixed by this patch:
https://github.com/lutris/lutris/pull/3430/commits/8ac18d594c72d40308899e775868d49f2e4d98bd


-- System Information:
Debian Release: 11.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'testing'), (400, 'unstable'), (250, 'stable'), (160, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-6-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lutris depends on:
ii  cabextract   1.9-3
ii  curl 7.74.0-1.2
ii  fluid-soundfont-gs   3.1-5.2
ii  gir1.2-gnomedesktop-3.0  3.38.5-2
ii  gir1.2-gtk-3.0   3.24.24-4
ii  gir1.2-notify-0.70.7.9-3
ii  gir1.2-webkit2-4.0   2.32.1-1
ii  mesa-utils   8.4.0-1+b1
ii  p7zip16.02+dfsg-8
ii  psmisc   23.4-2
ii  python3  3.9.2-3
ii  python3-dbus 1.2.16-5
ii  python3-distro   1.5.0-1
ii  python3-gi   3.38.0-2
ii  python3-lxml 4.6.3-1
ii  python3-magic2:0.4.20-3
ii  python3-pil  8.1.2+dfsg-0.1
ii  python3-requests 2.25.1+dfsg-2
ii  python3-setproctitle 1.2.1-1+b1
ii  python3-yaml 5.3.1-4
ii  unzip6.0-26
ii  x11-xserver-utils7.7+8

Versions of packages lutris recommends:
ii  gvfs-backends1.46.2-1
ii  libwine-development  5.22+repack-1
ii  python3-evdev1.4.0+dfsg-1
ii  winetricks   0.0+20210206-2

Versions of packages lutris suggests:
ii  gamemode  1.6.1-1

-- no debconf information

-- debsums errors found:

Bug#984650: update-initramfs fails when /etc/systemd/network/99-default.link is symlink to /dev/null

[Frederik Lindenaar]

Hi Cyril,

Thank you for the quick reply

As Ben also pointed out, I probably have indeed mixed up /dev/zero and 
/dev/null and had already fixed that by using an empty file. Nevertheless the 
result was pretty odd (the disk filling up rapidly) and very confusing so might 
still be useful to prevent this (if possible).

Why not use a cp -aLt  {} instead to prevent this?

regards,

Frederik


> On 6 Mar 2021, at 16:27, Cyril Brulebois  wrote:
> 
> Hello Frederik,
> 
> It seems there's some confusion around special character devices. Your
> subject mentions /dev/null…
> 
> Frederik Lindenaar  (2021-03-06):
>> When one disables the "Predicatble Network InterfaceNames" 
>> by making /lib/systemd/network/99-default.link a symlink to /dev/zero then
> 
> … but this is about /dev/zero (not the same thing! — see `man 4 null`).
> 
>> update-initramfs will fail as the copy of this symlink will fill-up all space
>> available in /var/tmp and makes it impossible to install any kernel image
>> 
>> the culprit is the following command executed by update-initramfs:
>> 
>>  find /etc/systemd/network -name *.link -execdir cp -pt /var/tmp/ {} +
>> 
>> As it (and should) dereference de symlink, it reads zero bytes from
>> /dev/null until the disk is full.
> 
> … and here you write /dev/null but what you describe happens with
> /dev/zero instead.
> 
>> Changing the symlink to a zero byte file resolved the issue for me but
>> as this approach is one of the recommended approaches to disable
>> predicatble network interface names (see [1]) others may also bump
>> into this.
>> 
>> [1] https://wiki.debian.org/NetworkInterfaceNames#How_to_get_it_back
> 
> This correctly describes a symlink to /dev/null, and not /dev/zero which
> appears to be what you're trying to use.
> 
> Fix your symlink, and you should be good to go?
> 
> 
> Cheers,
> -- 
> Cyril Brulebois (k...@debian.org)<https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant

Bug#984650: update-initramfs fails when /etc/systemd/network/99-default.link is symlink to /dev/null

[Frederik Lindenaar]

Hi Ben,

Thanks for the quick reply. I am not sure how I could have mixed these two up 
but did a quick test with cp just now and the problem indeed looks like mixing 
up /dev/zero and /dev/null (I have no way to check that anymore though).

Nevertheless the result was very confusing (a full disk) so might still be good 
to check somehow

regards,

Frederik

> On 6 Mar 2021, at 16:38, Ben Hutchings  wrote:
> 
> Control: tag -1 moreinfo
> 
> On Sat, 2021-03-06 at 14:57 +0100, Frederik Lindenaar wrote:
>> Package: initramfs-tools
>> Version: 0.133+deb10u1
>> Severity: important
>> 
>> When one disables the "Predicatble Network InterfaceNames" 
>> by making /lib/systemd/network/99-default.link a symlink to /dev/zero then
>> update-initramfs will fail as the copy of this symlink will fill-up all space
>> available in /var/tmp and makes it impossible to install any kernel image
>> 
>> the culprit is the following command executed by update-initramfs:
>> 
>> find /etc/systemd/network -name *.link -execdir cp -pt /var/tmp/ {} +
>> 
>> As it (and should) dereference de symlink, it reads zero bytes from
>> /dev/null until the disk is full.
> [...]
> 
> It looks like you have mixed up /dev/null and /dev/zero (as a Dutch
> learner, I can see how that would happen).  /dev/null is always empty
> and would be copied as an empty file.  This is the correct target for
> symlinks when you want to disable a systemd unit.  /dev/zero is an
> infinite stream of binary zeroes and would result in the behaviour you
> saw.
> 
> Ben.
> 
> 
> -- 
> Ben Hutchings
> Knowledge is power.  France is bacon.

Bug#984650: update-initramfs fails when /etc/systemd/network/99-default.link is symlink to /dev/null

[Frederik Lindenaar]

Package: initramfs-tools
Version: 0.133+deb10u1
Severity: important

When one disables the "Predicatble Network InterfaceNames" 
by making /lib/systemd/network/99-default.link a symlink to /dev/zero then
update-initramfs will fail as the copy of this symlink will fill-up all space
available in /var/tmp and makes it impossible to install any kernel image

the culprit is the following command executed by update-initramfs:

find /etc/systemd/network -name *.link -execdir cp -pt /var/tmp/ {} +

As it (and should) dereference de symlink, it reads zero bytes from /dev/null 
until the disk is full.

Changing the symlink to a zero byte file resolved the issue for me but as this
approach is one of the recommended approaches to disable predicatble network
interface names (see [1]) others may also bump into this.

[1] https://wiki.debian.org/NetworkInterfaceNames#How_to_get_it_back

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 6.9M Mar  6 14:31 /boot/initrd.img-4.19.0-13-amd64
-rw-r--r-- 1 root root 6.9M Mar  6 14:32 /boot/initrd.img-4.19.0-14-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-14-amd64 
root=UUID=8d33b150-7c84-4dd0-8893-06eab0e7b9d7 ro quiet

-- resume
RESUME=UUID=2db37a4d-80dd-46b3-aa4d-ff57862589ba
-- /proc/filesystems
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
vmw_vsock_vmci_transport32768  1
vsock  40960  2 vmw_vsock_vmci_transport
ata_generic16384  0
crct10dif_pclmul   16384  0
crc32_pclmul   16384  0
vmwgfx331776  1
ttm   126976  1 vmwgfx
ghash_clmulni_intel16384  0
vmw_balloon20480  0
drm_kms_helper208896  1 vmwgfx
intel_rapl_perf16384  0
joydev 24576  0
pcspkr 16384  0
drm   495616  4 vmwgfx,drm_kms_helper,ttm
ahci   40960  0
vmxnet369632  0
ata_piix   36864  0
libahci40960  1 ahci
sg 36864  0
libata270336  4 ata_piix,libahci,ahci,ata_generic
vmw_vmci   81920  2 vmw_balloon,vmw_vsock_vmci_transport
i2c_piix4  24576  0
ac 16384  0
button 20480  0
ip_tables  28672  0
x_tables   45056  1 ip_tables
autofs449152  2
ext4  745472  1
crc16  16384  1 ext4
mbcache16384  1 ext4
jbd2  122880  1 ext4
crc32c_generic 16384  0
fscrypto   32768  1 ext4
ecb16384  0
crc32c_intel   24576  2
sd_mod 61440  3
aesni_intel   200704  0
psmouse   172032  0
aes_x86_64 20480  1 aesni_intel
crypto_simd16384  1 aesni_intel
cryptd 28672  3 crypto_simd,ghash_clmulni_intel,aesni_intel
glue_helper16384  1 aesni_intel
evdev  28672  2
serio_raw  16384  0
vmw_pvscsi 28672  2
scsi_mod  249856  4 vmw_pvscsi,sd_mod,libata,sg

-- /etc/initramfs-tools/modules

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=auto
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto
RUNSIZE=10%

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- /sys/block
sda

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:

/usr/share/initramfs-tools/hooks:
dmsetup
fsck
fuse
keymap
klibc-utils
kmod
resume
thermal
udev
zz-busybox


-- System Information:
Debian Release: 10.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-14-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.utf8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.utf8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages initramfs-tools depends on:
ii  initramfs-tools-core  0.133+deb10u1
ii  linux-base4.6

initramfs-tools recommends no packages.

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.8-6

-- no debconf information

Bug#984603: puppet-master-passenger crashes when ruby-scanf is not installed

[Frederik]

Package: puppet-master-passenger
Version: 5.5.22-1
Severity: normal

Dear Maintainer,

I upgraded my system running puppet-master-passenger from Buster to
bullseye. From that moment on, puppet-master-passenger crashed when a
client tries to retriveve its configuration. The follow stacktrace could
be found in the Apache error.log:

App 25308 stderr: [ 2021-03-05 18:58:49.5455 28292/0x56253d9b7cc0(Worker 1) 
utils.rb:87 ]: *** Exception LoadError (cannot load such file -- scanf) 
(process 28292, thread 0x56253d9b7cc0(Worker 1)):
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/functions/scanf.rb:29:in `block in get_binding'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/functions.rb:250:in `class_eval'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/functions.rb:250:in `create_loaded_function'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/functions.rb:191:in `create_function'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/functions/scanf.rb:28:in `get_binding'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/ruby_function_instantiator.rb:22:in
 `eval'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/ruby_function_instantiator.rb:22:in
 `create'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/module_loaders.rb:263:in 
`instantiate'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/module_loaders.rb:237:in `find'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:161:in 
`internal_load'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:42:in `load_typed'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:153:in 
`internal_load'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:42:in `load_typed'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:153:in 
`internal_load'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:42:in `load_typed'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:153:in 
`internal_load'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:42:in `load_typed'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:153:in 
`internal_load'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/base_loader.rb:42:in `load_typed'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/loader/loader.rb:72:in `load'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:302:in 
`call_function'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:964:in 
`call_function_with_block'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:959:in 
`eval_CallMethodExpression'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:90:in `visit_this_1'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:81:in 
`evaluate'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:370:in 
`eval_AssignmentExpression'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:90:in `visit_this_1'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:81:in 
`evaluate'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:660:in `block 
in eval_BlockExpression'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:660:in `each'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:660:in 
`reduce'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:660:in 
`eval_BlockExpression'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:90:in `visit_this_1'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:81:in 
`evaluate'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:177:in `block 
in evaluate_block_with_bindings'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/parser/scope.rb:983:in `with_guarded_scope'
App 25308 stderr:   from 
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:173:in 
`evaluate_block_with_bindings'
App 25308 stderr: 

Bug#982112: apparmor-profiles: aa-genprof error because of usr.lib.dovecot.script-login

[Frederik Himpe]

Package: apparmor-profiles
Version: 2.13.6-7
Severity: normal

aa-genprof on any executable fails with this error:
ERROR: Include file /etc/apparmor.d/local/usr.lib.dovecot.script-login not found

This is because of
#include 
in the file /usr/share/apparmor/extra-profiles/usr.lib.dovecot.script-login

Commenting out this line (as is done by default in the other dovecot
scripts), fixes the problem.

It's basically the same as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928160 but this bug
was probably (re-)introduced in version 2.13.6-1 when the
usr.lib.dovecot.script-login profile was added.


-- System Information:
Debian Release: 10.8
  APT prefers stable
  APT policy: (800, 'stable'), (600, 'oldstable'), (500, 'oldoldstable'), (410, 
'proposed-updates'), (300, 'testing'), (200, 'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-3-amd64 (SMP w/10 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apparmor-profiles depends on:
ii  apparmor  2.13.6-7

apparmor-profiles recommends no packages.

apparmor-profiles suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/share/apparmor/extra-profiles/usr.lib.dovecot.script-login (from 
apparmor-profiles package)

Bug#977301: Spice needs file audio-spice.so in qemu-system-gui

[Frederik Himpe]

I'm experiencing the same problem.

The problem is missing audio-spice.so file. It's in qemu-system-gui, so
installing this fixes the problem.

According to
https://lists.gnu.org/archive/html/qemu-devel/2020-12/msg04335.html

all files *spice*.so and hw-display-qxl.so should be together in the
same package.

Bug#977686: gosa-plugin-mail: Cannot use string offset as an array in class_sieve.inc:331

[Frederik Himpe]

Package: gosa-plugin-mail
Version: 2.7.4+reloaded3-14
Severity: normal

When using gosa on PHP 7.3, this error occurs when creating a user with
an e-mail account in Cyrus IMAP:

 Fatal error: Uncaught Error: Cannot use string offset as an array in 
/usr/share/gosa/plugins/personal/mail/sieve/class_sieve.inc:331 Stack trace: #0 
/usr/share/gosa/plugins/personal/mail/class_mail-methods-cyrus.inc(497): 
sieve->sieve_login() #1 
/usr/share/gosa/plugins/personal/mail/class_mailAccount.inc(957): 
mailMethodCyrus->saveSieveSettings() #2 
/usr/share/gosa/include/class_tabs.inc(360): mailAccount->save() #3 
/usr/share/gosa/plugins/admin/users/tabs_user.inc(148): tabs->save() #4 
/usr/share/gosa/include/class_management.inc(844): usertabs->save() #5 
/usr/share/gosa/plugins/admin/users/class_userManagement.inc(406): 
management->saveChanges() #6 /usr/share/gosa/include/class_management.inc(475): 
userManagement->saveChanges('save', Array, Array) #7 
/usr/share/gosa/include/class_management.inc(183): 
management->handleActions(Array) #8 
/usr/share/gosa/plugins/admin/users/main.inc(44): management->execute() #9 
/usr/share/gosa/html/main.php(407): require('/usr/share/gosa...') #10 {main} 
thrown in /usr/share/gosa/plugins/personal/mail/sieve/class_sieve.inc on line 
331

The attached patch fixes this problem.

-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (800, 'stable'), (600, 'oldstable'), (500, 'oldoldstable'), (410, 
'proposed-updates'), (300, 'testing'), (200, 'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.48 (SMP w/10 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gosa-plugin-mail depends on:
ii  gosa 2.7.4+reloaded3-14
ii  gosa-plugin-systems  2.7.4+reloaded3-14

gosa-plugin-mail recommends no packages.

gosa-plugin-mail suggests no packages.

-- Configuration Files:
/etc/gosa/vacation/vacation_example.txt [Errno 13] Permission denied: 
'/etc/gosa/vacation/vacation_example.txt'

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/share/gosa/plugins/personal/mail/sieve/class_sieve.inc (from 
gosa-plugin-mail package)
--- plugins/personal/mail/sieve/class_sieve.inc.orig2020-09-01 
16:19:36.585529202 +0200
+++ plugins/personal/mail/sieve/class_sieve.inc 2020-12-18 22:21:46.714976257 
+0100
@@ -217,7 +217,7 @@
 $this->tmpfile="";
 $this->fh=0;
 $this->len=0;
-$this->capabilities="";
+$this->capabilities=array();
 $this->loggedin=false;
 $this->error= "";
 $this->error_raw="";

Bug#977350: certbot: Version in Debian Stable gets certificates by R3 issuer which might fail to validate

[Frederik]

Package: certbot
Version: 0.31.0-1
Severity: normal

Yesterday I started getting certificate validation errors on one domain
in the DAVx5 client on Android and in Evolution 3.38 running on Debian
testing. The error here was that the issuer of the certificate is
unknown. I noticed that certbot had renewed the certificate yesterday.

The new certificate is now issued by C=US, O=Let's Encrypt, CN=R3, while
the previous one was issued by C=US, O=Let's Encrypt, CN=Let's Encrypt 
Authority X3
This change is documented here: 
https://community.letsencrypt.org/t/beginning-issuance-from-r3/139018

They mention that some ACME clients might have a problem with this change,
and in that case the new certificate can fail to validate. I updated the
certbot package to 1.10.1 from Testing, and renewed the certificate for
the problematic domain. The certificate validation error went away in
both DAVx5 and Evolution. So it appears that the old certbot version in
Stable is suffering from this problem.

-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'proposed-updates'), (600, 'oldstable'), 
(500, 'oldoldstable'), (500, 'testing'), (200, 'unstable'), (160, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages certbot depends on:
ii  python3  3.7.3-1
ii  python3-certbot  0.31.0-1

certbot recommends no packages.

Versions of packages certbot suggests:
pn  python-certbot-doc  
pn  python3-certbot-apache  
pn  python3-certbot-nginx   

-- Configuration Files:
/etc/cron.d/certbot [Errno 2] No such file or directory: '/etc/cron.d/certbot'

-- no debconf information

Bug#976854: samba: not built with io_uring support

[Frederik Himpe]

Package: samba
Version: 2:4.13.2+dfsg-3
Severity: normal
X-Debbugs-Cc: frede...@frehi.be

The vfs_io_uring module is missing from Debian's samba-vfs-modules package.

https://wiki.samba.org/index.php/Samba_4.12_Features_added/changed#.27io_uring.27_vfs_module




-- Package-specific info:
* /etc/samba/smb.conf present, but not attached
* /var/lib/samba/dhcp.conf not present

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (400, 'unstable'), (250, 'stable'), (160, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages samba depends on:
ii  adduser  3.118
ii  dpkg 1.20.5
ii  init-system-helpers  1.59
ii  libbsd0  0.10.0-1
ii  libc62.31-5
ii  libgnutls30  3.6.15-4
ii  libldb2  2:2.2.0-3+b1
ii  libpam-modules   1.3.1-5
ii  libpam-runtime   1.3.1-5
ii  libpopt0 1.18-2
ii  libpython3.9 3.9.1~rc1-2
ii  libtalloc2   2.3.1-2+b1
ii  libtasn1-6   4.16.0-2
ii  libtdb1  1.4.3-1+b1
ii  libtevent0   0.10.2-1
ii  libwbclient0 2:4.13.2+dfsg-3
ii  lsb-base 11.1.0
ii  procps   2:3.3.16-5
ii  python3  3.9.0-4
ii  python3-dnspython2.0.0-1
ii  python3-samba2:4.13.2+dfsg-3
ii  samba-common 2:4.13.2+dfsg-3
ii  samba-common-bin 2:4.13.2+dfsg-3
ii  samba-libs   2:4.13.2+dfsg-3
ii  tdb-tools1.4.3-1+b1

Versions of packages samba recommends:
pn  attr
ii  logrotate   3.17.0-2
pn  python3-markdown
pn  samba-dsdb-modules  
ii  samba-vfs-modules   2:4.13.2+dfsg-3

Versions of packages samba suggests:
pn  bind9  
pn  bind9utils 
pn  ctdb   
pn  ldb-tools  
pn  ntp | chrony   
pn  smbldap-tools  
pn  ufw
ii  winbind2:4.13.2+dfsg-3

-- no debconf information

Bug#976680: update-apparmor-samba-profile generates invalid file if share path in smb.conf between double quotes

[Frederik Himpe]

Package: samba
Version: 2:4.13.2+dfsg-3
Severity: normal
X-Debbugs-Cc: frede...@frehi.be

I have a share in smb.conf configured like this:
[Classical music]
   comment = Classical music
   path = "/mnt/storage2/Classical music"
   guest ok = no
   browseable = yes
   read only = yes
   valid users = foo
   vfs objects = btrfs

update-apparmor-samba-profile then puts this in the /etc/apparmor.d/samba/smbd-
shares file:

""/mnt/storage2/Classical music"/"   rk,
""/mnt/storage2/Classical music"/**" rwkl,

Which results in this error:
# apparmor_parser -r /etc/apparmor.d/usr.sbin.smbd
AppArmor parser error for /etc/apparmor.d/usr.sbin.smbd in
/etc/apparmor.d/samba/smbd-shares at line 5: Lexer found unexpected character:
'"' (0x22) in state: INITIAL



-- Package-specific info:
* /etc/samba/smb.conf present, but not attached
* /var/lib/samba/dhcp.conf not present

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (400, 'unstable'), (250, 'stable'), (160, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages samba depends on:
ii  adduser  3.118
ii  dpkg 1.20.5
ii  init-system-helpers  1.59
ii  libbsd0  0.10.0-1
ii  libc62.31-5
ii  libgnutls30  3.6.15-4
ii  libldb2  2:2.2.0-3+b1
ii  libpam-modules   1.3.1-5
ii  libpam-runtime   1.3.1-5
ii  libpopt0 1.18-2
ii  libpython3.9 3.9.1~rc1-2
ii  libtalloc2   2.3.1-2+b1
ii  libtasn1-6   4.16.0-2
ii  libtdb1  1.4.3-1+b1
ii  libtevent0   0.10.2-1
ii  libwbclient0 2:4.13.2+dfsg-3
ii  lsb-base 11.1.0
ii  procps   2:3.3.16-5
ii  python3  3.9.0-3
ii  python3-dnspython2.0.0-1
ii  python3-samba2:4.13.2+dfsg-3
ii  samba-common 2:4.13.2+dfsg-3
ii  samba-common-bin 2:4.13.2+dfsg-3
ii  samba-libs   2:4.13.2+dfsg-3
ii  tdb-tools1.4.3-1+b1

Versions of packages samba recommends:
pn  attr
ii  logrotate   3.17.0-2
pn  python3-markdown
pn  samba-dsdb-modules  
ii  samba-vfs-modules   2:4.13.2+dfsg-3

Versions of packages samba suggests:
pn  bind9  
pn  bind9utils 
pn  ctdb   
pn  ldb-tools  
pn  ntp | chrony   
pn  smbldap-tools  
pn  ufw
ii  winbind2:4.13.2+dfsg-3

-- no debconf information

Bug#964194: gitlab: "internal API unreachable" when pushing something to repository

[Frederik Himpe]

Pirate Praveen schreef op 2020-07-05 23:00:


In 2 days and 70+ rebuilds we have gitlab working with ruby 2.7 (just
tested git clone and git push).



Once you confirm, I can push these packages to fasttrack.debian.net


Sorry, I cannot test it any more because in the meantime I migrated to 
the omnibus packages.


Thank you for your work though.

Regards,
--
Frederik Himpe 
Vrije Universiteit Brussel

Bug#964194: gitaly errors

[Frederik Himpe]

Now I see in gitaly journal these errors. At the time I was also making 
a backup, or it might be a user doing some action triggering this. So 
these messages might be completely unrelated to the original problem, or 
not.


jul 03 17:48:06 ai-gitlab gitaly[6050]: time="2020-07-03T17:48:06+02:00" 
level=error msg="error: pack-objects died of signal 9\\nerror: 
pack-objects died\\n" grpc.meta.auth_version=v2 
grpc.meta.client_name=gitlab-web grpc.meta.deadline_type=unknown 
grpc.method=CreateBundle 
grpc.request.deadline="2020-07-03T23:39:09+02:00" 
grpc.request.fullMethod=/gitaly.RepositoryService/CreateBundle 
grpc.request.glProjectPath=group/repo 
grpc.request.glRepository=project-64 
grpc.request.repoPath=group/repo.git grpc.request.repoStorage=default 
grpc.request.topLevelGroup=group grpc.service=gitaly.RepositoryService 
grpc.start_time="2020-07-03T17:39:09+02:00" peer.address=@ pid=6050 
span.kind=server system=grpc
jul 03 17:48:06 ai-gitlab gitaly[6050]: time="2020-07-03T17:48:06+02:00" 
level=error msg="finished streaming call with code Internal" error="rpc 
error: code = Internal desc = CreateBundle: cmd wait failed: exit status 
1" grpc.code=Internal grpc.meta.auth_version=v2 
grpc.meta.client_name=gitlab-web grpc.meta.deadline_type=unknown 
grpc.method=CreateBundle 
grpc.request.deadline="2020-07-03T23:39:09+02:00" 
grpc.request.fullMethod=/gitaly.RepositoryService/CreateBundle 
grpc.request.glProjectPath=group/repo 
grpc.request.glRepository=project-64 
grpc.request.repoPath=group/repo.git grpc.request.repoStorage=default 
grpc.request.topLevelGroup=group grpc.service=gitaly.RepositoryService 
grpc.start_time="2020-07-03T17:39:09+02:00" grpc.time_ms=536612.94 
peer.address=@ pid=6050 span.kind=server system=grpc



--
Frederik Himpe 
Vrije Universiteit Brussel

Bug#964194: gitlab: "internal API unreachable" when pushing something to repository

[Frederik Himpe]

Pirate Praveen schreef op 2020-07-03 17:31:

I can see you already have the latest version. Do you use custom push 
hooks?


Not that I know. I understand these would be defined in 
gitlab-shell.conf or gitaly/config.toml, and I don't see any there.


The repository of the example has 
hooks/{pre-receive,post-receive,update}, all containing this:

#!/bin/sh
echo "The gitlab-shell hooks have been migrated to Gitaly, see 
https://gitlab.com/gitlab-org/gitaly/issues/1226;

exit 1


I see no messages in gitaly journal when I push something.

--
Frederik Himpe 
Vrije Universiteit Brussel

Bug#964194: gitlab: "internal API unreachable" when pushing something to repository

[Frederik Himpe]

Pirate Praveen schreef op 2020-07-03 17:18:


See #964097 for a discussion. We saw this error with git push and
changing that file fixed it. So not sure what is the issue you have.


In that bug it mentions that a stack trace was printed. This is not the 
case on my system. I guess I experience another bug, or either the patch 
hid the stack trace, but introduced another problem which does not cause 
a stack trace.


--
Frederik Himpe 
Vrije Universiteit Brussel

Bug#964194: gitlab: "internal API unreachable" when pushing something to repository

[Frederik Himpe]

Pirate Praveen schreef op 2020-07-03 17:00:


This was fixed in 13.1.2-1+fto10+2.


Where can I find this package? It's not avaible in my Debian Fasttrack 
mirror.




Sorry that was a typo, you have the changes that fixed this error as
you noted below.


Can you check the contents of
/usr/share/gitlab/lib/gitlab/gl_repository/identifier.rb line 52?


id = Integer(segments[1], 10)



Can you try restarting gitlab service?


Already did that many times, including a full reboot. Does not help.

Your message seems to imply that some version before 13.1.2-1+fto10+1 
had this bug, but I went directly from 12.10.3-1+fto10+1 (where I did 
not have this problem) to 13.1.2-1+fto10+1, so in that case I should 
never have had that bug. But I do have it since that upgrade.


--
Frederik Himpe 
Vrije Universiteit Brussel

Bug#964194: gitlab: "internal API unreachable" when pushing something to repository

[Frederik Himpe]

Pirate Praveen schreef op 2020-07-03 16:38:


Since upgrading from 12.10.3-1+fto10+1 to 13.1.2-1+fto10+1, all users
cannot push anything any more to any repository, either via SSH, 
HTTPS,

or by editing and committing a file in the web interface. The error
always comes down to: Internal API unreachable.


This was fixed in 13.1.2-1+fto10+2.


Where can I find this package? It's not avaible in my Debian Fasttrack 
mirror.



Can you check the contents of
/usr/share/gitlab/lib/gitlab/gl_repository/identifier.rb line 52?


id = Integer(segments[1], 10)

Regards,

--
Frederik Himpe 
Vrije Universiteit Brussel

Bug#964194: gitlab: "internal API unreachable" when pushing something to repository

[Frederik Himpe]

Package: gitlab
Version: 13.1.2-1+fto10+1
Severity: important

Dear Maintainer,

Since upgrading from 12.10.3-1+fto10+1 to 13.1.2-1+fto10+1, all users
cannot push anything any more to any repository, either via SSH, HTTPS,
or by editing and committing a file in the web interface. The error
always comes down to: Internal API unreachable.

For example using SSH:
$ git push
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Writing objects: 100% (3/3), 249 bytes | 249.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
remote: GitLab: Failed to authorize your Git request: internal API unreachable
To gitlab.example.com:user/test.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'gitlab.example.com:user/test.git'

I cannot see any error or backtrace in
/var/log/gitlab-shell/gitlab-shell.log or
/var/log/gitlab/producation.log

Cloning the repository works fine though.


gitlab:check says the internal API is available:
# runuser -u gitlab -- sh -c '/usr/bin/bundle exec rake gitlab:check 
RAILS_ENV=production'
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Attention: used pure ruby version of MurmurHash3
DEPRECATION WARNING: ActionDispatch::Http::ParameterFilter is deprecated and 
will be removed from Rails 6.1. Use ActiveSupport::ParameterFilter instead. 
(called from  at 
/usr/lib/ruby/vendor_ruby/grape_logging/util/parameter_filter.rb:2)
/usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized constant 
Gitlab::COM_URL
/usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was 
here
/usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized constant 
Gitlab::STAGING_COM_URL
/usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of 
STAGING_COM_URL was here
/usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized constant 
Gitlab::APP_DIRS_PATTERN
/usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of 
APP_DIRS_PATTERN was here
/usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized constant 
Gitlab::SUBDOMAIN_REGEX
/usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of 
SUBDOMAIN_REGEX was here
/usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized constant 
Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of VERSION was 
here
/usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized constant 
Gitlab::INSTALLATION_TYPE
/usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of 
INSTALLATION_TYPE was here
/usr/share/gitlab/lib/gitlab.rb:44: warning: already initialized constant 
Gitlab::HTTP_PROXY_ENV_VARS
/usr/share/gitlab/lib/gitlab.rb:44: warning: previous definition of 
HTTP_PROXY_ENV_VARS was here
/usr/share/gitlab/config/initializers/2_app.rb:6: warning: already initialized 
constant Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of VERSION was 
here
Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 13.3.0 ? ... OK (13.3.0)
Running /usr/share/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... Server: ldapmain
LDAP authentication... Anonymous. No `bind_dn` or `password` configured
LDAP users with access to your GitLab server (only showing the first 100 
results)
[]
Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
Projects have namespace: ...
[...]
Redis version >= 4.0.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.5.5)
Git version >= 2.22.0 ? ... yes (2.26.2)
Git user has default SSH configuration? ... yes
Active users: ... 171
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... no
  Try fixing it:
  Please migrate all projects to hashed storage
  as legacy storage is deprecated in 13.0 and support will be removed 

Bug#964193: gitlab: 500 Errrors at log in because of missing setting in gitlab.yml

[Frederik Himpe]

Package: gitlab
Version: 13.1.2-1+fto10+1
Severity: normal

I upgraded from 12.10.3-1+fto10+1 to 13.1.2-1+fto10+1 and when trying to
login after that, I got 500 errors.

Error from production log:

Settingslogic::MissingSetting (Missing setting 
'admin_area_protected_paths_enabled' in 'rack_attack' section in 
/etc/gitlab/gitlab.yml):

config/initializers/rack_attack_new.rb:18:in 
`should_use_omnibus_protected_paths?'
config/initializers/rack_attack_new.rb:11:in `protected_paths_enabled?'
config/initializers/rack_attack_new.rb:90:in `block in '
lib/gitlab/middleware/read_only/controller.rb:51:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/same_site_cookies.rb:27:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/middleware/handle_ip_spoof_attack_error.rb:25:in `call'
lib/gitlab/middleware/request_context.rb:23:in `call'
config/initializers/fix_local_cache_middleware.rb:9:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:60:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'


I hadd to add 
admin_area_protected_paths_enabled: true

to gitlab.yml to make it work.

/etc/gitlab/gitlab.yml.example does not contain this option, nor could I
find much information about this specific option documented online. This
should be at least in gitlab.yml.example.


-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'proposed-updates'), (640, 
'buster-backports'), (630, 'buster-fasttrack'), (600, 'oldstable'), (550, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'testing'), (200, 
'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  apache2 [httpd]2.4.38-3+deb10u3
ii  asciidoctor2.0.10-2~bpo10+1
ii  bc 1.07.1-2+b1
ii  bundler1.17.3-3
ii  bzip2  1.0.6-9.2~deb10u1
ii  dbconfig-pgsql 2.0.11+deb10u1
ii  debconf [debconf-2.0]  1.5.71
ii  gitlab-common  13.1.0+dfsg-1~bpo10+1
ii  gitlab-workhorse   8.36.0+debian-1~bpo10+1
ii  libjs-bootstrap4 [node-bootstrap]  4.3.1+dfsg2-1
ii  libjs-popper.js [node-popper.js]   1.14.6+ds2-1
ii  libjs-uglify   2.8.29-6
ii  lsb-base   10.2019051400
ii  node-autosize  4.0.2~dfsg1-3
ii  node-axios 0.17.1+dfsg-2
ii  node-babel-loader  8.1.0-3~bpo10+1
ii  node-babel77.4.5+~cs7.3.8-1~bpo10+1
ii  node-brace-expansion   1.1.8-1
ii  node-cache-loader  4.1.0-1~bpo10+1
ii  node-chart.js  2.7.3+dfsg-5
ii  node-clipboard 2.0.6+ds-1~bpo10+1
ii  node-compression-webpack-plugin3.0.1-1~bpo10+1
ii  node-core-js   3.6.5-1
ii  node-css-loader2.1.1-1~bpo10+1
ii  node-d3-scale  2.2.2-2
ii  node-d3-selection  1.4.0-5
ii  node-dateformat3.0.0-1
ii  node-exports-loader0.7.0-2~bpo10+1
ii  node-fuzzaldrin-plus   0.5.0+dfsg-1
ii  node-glob  7.1.6-1~bpo10+1
ii  node-imports-loader0.8.0-2~bpo10+1
ii  node-jed   1.1.1-1
ii  node-jquery3.5.1+dfsg-4
ii  node-jquery-ujs1.2.2-2
ii  node-js-cookie 2.2.0-2
ii  node-jszip 3.2.2+dfsg-1
ii  node-jszip-utils   0.0.2+dfsg-1
ii  node-lodash4.17.15+dfsg-2
ii  node-marked0.5.1+dfsg-1
ii  node-mousetrap 1.6.1+ds-1
ii  node-prismjs   1.11.0+dfsg-3
ii  node-prosemirror-model 1.9.0-3
ii  node-raven-js  3.22.1+dfsg-2
ii  node-three-orbit-controls  82.1.0-2
ii  node-three-stl-loader  1.0.6-2
ii  node-timeago.js4.0.2-2
ii  node-underscore1.9.1~dfsg-1
ii  node-url-loader

Bug#958445: ruby-attr-encrypted and ruby-acts-as-taggable incompatible with Rails 6

[Frederik Himpe]

I found these ruby gems are still using set_attribute_was, which appears 
to have been removed in rails 6:


vendor_ruby/attr_encrypted/adapters/active_record.rb:
set_attribute_was(attr, __send__(attr)) if value != __send__(attr)
vendor_ruby/acts_as_taggable_on/taggable/core.rb:  
set_attribute_was("#{tag_type}_list", #{tag_type}_list)



ii  ruby-acts-as-taggable-on 6.5.0-2~bpo10+1 all  provides 
advanced tagging for Rails
ii  ruby-attr-encrypted  3.1.0-2~bpo10+1 all  Encrypt and 
decrypt attributes


https://github.com/mbleigh/acts-as-taggable-on/issues/955
https://github.com/rolandoalvarado/acts-as-taggable-on/commit/391650aa48c571687844393e16b5d03c88f93be1

https://github.com/attr-encrypted/attr_encrypted/pull/337
attr_encrypted seems pretty much a dead project...

--
Frederik Himpe 
Vrije Universiteit Brussel

Bug#958445: gitlab: 500 error on two-factor auth page

[Frederik Himpe]

Package: gitlab
Version: 12.9.3+dfsg-1+fto10+1
Severity: normal

Dear Maintainer,

When opening /profile/two_factor_auth to set up 2FA on my account, I get
a 500 internal server error.

Log contains this:

Processing by Profiles::TwoFactorAuthsController#show as HTML
Completed 500 Internal Server Error in 176ms (ActiveRecord: 2.5ms | 
Elasticsearch: 0.0ms | Allocations: 14662)
  
NoMethodError (undefined method `set_attribute_was' for #
Did you mean?  custom_attributes):
  
app/controllers/profiles/two_factor_auths_controller.rb:8:in `show'
app/controllers/application_controller.rb:479:in `set_current_admin'
lib/gitlab/session.rb:11:in `with_session'
app/controllers/application_controller.rb:470:in `set_session_storage'
lib/gitlab/i18n.rb:55:in `with_locale'
lib/gitlab/i18n.rb:61:in `with_user_locale'
app/controllers/application_controller.rb:464:in `set_locale'
lib/gitlab/error_tracking.rb:34:in `with_context'
app/controllers/application_controller.rb:555:in `sentry_context'
lib/gitlab/application_context.rb:46:in `block in use'
lib/gitlab/application_context.rb:46:in `use'
lib/gitlab/application_context.rb:19:in `with_context'
app/controllers/application_controller.rb:455:in `set_current_context'
lib/gitlab/request_profiler/middleware.rb:17:in `call'
lib/gitlab/middleware/go.rb:20:in `call'
lib/gitlab/etag_caching/middleware.rb:13:in `call'
lib/gitlab/middleware/multipart.rb:122:in `call'
lib/gitlab/middleware/read_only/controller.rb:53:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/middleware/request_context.rb:23:in `call'
config/initializers/fix_local_cache_middleware.rb:9:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:49:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'


-- System Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'proposed-updates'), (640, 
'buster-backports'), (630, 'buster-fasttrack'), (600, 'oldstable'), (550, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'testing'), (200, 
'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  apache2 [httpd] 2.4.38-3+deb10u3
ii  asciidoctor 2.0.10-2~bpo10+1
ii  bc  1.07.1-2+b1
ii  bundler 1.17.3-3
ii  bzip2   1.0.6-9.2~deb10u1
ii  dbconfig-pgsql  2.0.11+deb10u1
ii  debconf [debconf-2.0]   1.5.71
ii  gitlab-common   12.9.3+dfsg-1~bpo10+1
ii  gitlab-workhorse8.30+debian-1~bpo10+1
ii  libjs-bootstrap4 [node-bootstrap]   4.3.1+dfsg2-1
ii  libjs-popper.js [node-popper.js]1.14.6+ds2-1
ii  libjs-uglify2.8.29-6
ii  lsb-base10.2019051400
ii  node-autosize   4.0.2~dfsg1-3
ii  node-axios  0.17.1+dfsg-2
ii  node-brace-expansion1.1.8-1
ii  node-chart.js   2.7.3+dfsg-5
ii  node-clipboard  2.0.6+ds-1~bpo10+1
ii  node-core-js3.6.1-3
ii  node-css-loader 1.0.1-1
ii  node-d3-scale   2.2.2-2
ii  node-d3-selection   1.4.0-5
ii  node-dateformat 3.0.0-1
ii  node-exports-loader 0.7.0-2~bpo10+1
ii  node-fuzzaldrin-plus0.5.0+dfsg-1
ii  node-glob   7.1.3-2
ii  node-imports-loader 0.8.0-2~bpo10+1
ii  node-jed1.1.1-1
ii  node-jquery 3.4.0+dfsg-1
ii  node-jquery-ujs 1.2.2-2
ii  node-js-cookie  2.2.0-2
ii  node-jszip  3.2.2+dfsg-1
ii  node-jszip-utils0.0.2+dfsg-1
ii  node-lodash 4.17.15+dfsg-2
ii  node-marked 0.5.1+dfsg-1
ii  node-mousetrap  1.6.1+ds-1
ii  node-prismjs1.11.0+dfsg-3
ii  node-prosemirror-model  1.9.0-3
ii  node-raven-js   3.22.1+dfsg-2
ii  node-three-orbit-controls   82.1.0-2
ii  node-three-stl-loader   1.0.6-2
ii  node-timeago.js 4.0.2-2
ii  node-underscore 1.9.1~dfsg-1
ii  node-url-loader 3.0.0-1~bpo10+1
ii  node-vue-resource   1.5.1+dfsg-5
ii  node-webpack-stats-plugin   

Bug#958442: gitlab: complains about too old json-jwt when running triggers

[Frederik Himpe]

Package: gitlab
Version: 12.9.3+dfsg-1+fto10+1
Severity: normal

Dear Maintainer,

Processing triggers for gitlab (12.9.3+dfsg-1+fto10+1) ...
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Bundler could not find compatible versions for gem "json-jwt":
  In Gemfile:
doorkeeper-openid_connect (>= 1.6.3, ~> 1.6) was resolved to 1.6.3, which 
depends on
  json-jwt (~> 1.6)

rack-oauth2 (>= 1.9.3, ~> 1.9) was resolved to 1.11.0, which depends on
  json-jwt (>= 1.11.0)

Could not find gem 'json-jwt (>= 1.11.0)', which is required by gem 
'doorkeeper-openid_connect (>= 1.6.3, ~> 1.6)', in any of the sources.
#
# Failed to detect gitlab dependencies; if you are in the middle of an #
# upgrade, this is probably fine, there will be another attempt later.  #
#   #
# If you are NOT in the middle of an upgrade, there is probably a real  #
# issue. Please report a bug.   #
#


It appears like a dependency on newer ruby-json-jwt from backports is missing.

-- System Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'proposed-updates'), (640, 
'buster-backports'), (630, 'buster-fasttrack'), (600, 'oldstable'), (550, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'testing'), (200, 
'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  apache2 [httpd] 2.4.38-3+deb10u3
ii  asciidoctor 2.0.10-2~bpo10+1
ii  bc  1.07.1-2+b1
ii  bundler 1.17.3-3
ii  bzip2   1.0.6-9.2~deb10u1
ii  dbconfig-pgsql  2.0.11+deb10u1
ii  debconf [debconf-2.0]   1.5.71
ii  gitlab-common   12.9.3+dfsg-1~bpo10+1
ii  gitlab-workhorse8.30+debian-1~bpo10+1
ii  libjs-bootstrap4 [node-bootstrap]   4.3.1+dfsg2-1
ii  libjs-popper.js [node-popper.js]1.14.6+ds2-1
ii  libjs-uglify2.8.29-6
ii  lsb-base10.2019051400
ii  node-autosize   4.0.2~dfsg1-3
ii  node-axios  0.17.1+dfsg-2
ii  node-brace-expansion1.1.8-1
ii  node-chart.js   2.7.3+dfsg-5
ii  node-clipboard  2.0.6+ds-1~bpo10+1
ii  node-core-js3.6.1-3
ii  node-css-loader 1.0.1-1
ii  node-d3-scale   2.2.2-2
ii  node-d3-selection   1.4.0-5
ii  node-dateformat 3.0.0-1
ii  node-exports-loader 0.7.0-2~bpo10+1
ii  node-fuzzaldrin-plus0.5.0+dfsg-1
ii  node-glob   7.1.3-2
ii  node-imports-loader 0.8.0-2~bpo10+1
ii  node-jed1.1.1-1
ii  node-jquery 3.4.0+dfsg-1
ii  node-jquery-ujs 1.2.2-2
ii  node-js-cookie  2.2.0-2
ii  node-jszip  3.2.2+dfsg-1
ii  node-jszip-utils0.0.2+dfsg-1
ii  node-lodash 4.17.15+dfsg-2
ii  node-marked 0.5.1+dfsg-1
ii  node-mousetrap  1.6.1+ds-1
ii  node-prismjs1.11.0+dfsg-3
ii  node-prosemirror-model  1.9.0-3
ii  node-raven-js   3.22.1+dfsg-2
ii  node-three-orbit-controls   82.1.0-2
ii  node-three-stl-loader   1.0.6-2
ii  node-timeago.js 4.0.2-2
ii  node-underscore 1.9.1~dfsg-1
ii  node-url-loader 3.0.0-1~bpo10+1
ii  node-vue-resource   1.5.1+dfsg-5
ii  node-webpack-stats-plugin   0.2.1-1
ii  node-worker-loader  2.0.0-2~bpo10+1
ii  node-xterm  3.8.1-4
ii  nodejs  10.15.2~dfsg-2
ii  openssh-client  1:7.9p1-10+deb10u2
ii  postfix [mail-transport-agent]  3.4.8-0+10debu1
ii  postgresql-client   

Bug#839702: gitlab: logrotate not working?

[Frederik Himpe]

Package: gitlab
Version: 12.6.4-1
Followup-For: Bug #839702

Dear Maintainer,

The package should include /etc/logrotate.d/gitlab to rotate logs.
However, then the permissions on /var/log/gitlab and
/var/log/gitlab-shell also need to be changed in order to prevent this
security bug: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/4380

Bug#948957: knot-resolver: TLSv1.3 session resumption broken

[Frederik Himpe]

Package: knot-resolver
Version: 3.2.1-3
Severity: normal

Dear Maintainer,

This version of Knot Resolver, which is in both Buster as in Sid, has a bug
in session resumption support with TLSv1.3. This is upstream bug
https://gitlab.labs.nic.cz/knot/knot-resolver/issues/489
which has been fixed in upstream 4.2.0.

This bug can be easily reproduced with TLS_FORWARD to 1.1.1.1 since 2 days
because Cloudflare enabled TLSv1.3 then. You need this in the configuration
file:

policy.add(policy.all(policy.TLS_FORWARD({
 { '1.1.1.1', hostname='cloudflare-dns.com', 
ca_file='/etc/ssl/certs/ca-certificates.crt' },
})))

Then any DNS lookup not yet cached by Knot will fail and these messages are 
logged:

kresd[8129]: [tls_client] TLS handshake with 1.1.1.1#00853 has completed
kresd[8129]: [tls_client] TLS session has not resumed
kresd[8129]: [gnutls] (5) REC[0x55868f25e580]: Preparing Packet Application 
Data(23) with length: 41 and min pad: 0
kresd[8129]: [gnutls] (5) REC[0x55868f25e580]: Sent Packet[1] Application 
Data(23) in epoch 2 and length: 63
kresd[8129]: [gnutls] (3) ASSERT: 
../../lib/buffers.c[_gnutls_io_read_buffered]:589
kresd[8129]: [gnutls] (3) ASSERT: ../../lib/record.c[_gnutls_recv_int]:1775
kresd[8129]: [gnutls] (5) REC[0x55868f25e580]: SSL 3.3 Application Data packet 
received. Epoch 2, length: 445
kresd[8129]: [gnutls] (5) REC[0x55868f25e580]: Expected Packet Application 
Data(23)
kresd[8129]: [gnutls] (5) REC[0x55868f25e580]: Received Packet Application 
Data(23) with length: 445
kresd[8129]: [gnutls] (5) REC[0x55868f25e580]: Decrypted Packet[0] 
Handshake(22) with length: 428
kresd[8129]: [gnutls] (3) ASSERT: ../../lib/buffers.c[get_last_packet]:1168
kresd[8129]: [gnutls] (4) HSK[0x55868f25e580]: NEW SESSION TICKET (4) was 
received. Length 210[424], frag offset 0, frag length: 210, sequence: 0
kresd[8129]: [gnutls] (3) ASSERT: 
../../lib/buffers.c[_gnutls_handshake_io_recv_int]:1429
kresd[8129]: [gnutls] (4) HSK[0x55868f25e580]: parsing session ticket message
kresd[8129]: [gnutls] (3) ASSERT: ../../lib/buffers.c[get_last_packet]:1168
kresd[8129]: [gnutls] (4) HSK[0x55868f25e580]: NEW SESSION TICKET (4) was 
received. Length 210[210], frag offset 0, frag length: 210, sequence: 0
kresd[8129]: [gnutls] (3) ASSERT: 
../../lib/buffers.c[_gnutls_handshake_io_recv_int]:1429
kresd[8129]: [gnutls] (4) HSK[0x55868f25e580]: parsing session ticket message
kresd[8129]: [gnutls] (3) ASSERT: 
../../lib/record.c[_gnutls_recv_in_buffers]:1577
kresd[8129]: [gnutls] (3) ASSERT: ../../lib/record.c[_gnutls_recv_int]:1775
kresd[8129]: [io] => connection to '1.1.1.1#00853': error processing TLS data, 
close

For Buster this patch could be cherry picked: 
https://gitlab.labs.nic.cz/knot/knot-resolver/commit/9d42f93d591e1f581a4287a141f0af4276ebb1fb

See also 
https://community.cloudflare.com/t/dns-over-tls-broken-with-knot-resolver-since-today/142319


-- System Information:
Debian Release: 10.2
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'proposed-updates'), (600, 'oldstable'), 
(550, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'testing'), 
(200, 'unstable'), (160, 'experimental'), (110, 'disco')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages knot-resolver depends on:
ii  adduser  3.118
ii  dns-root-data2019031302
ii  libc62.28-10
ii  libdnssec6   2.7.6-2
ii  libedit2 3.1-20181209-1
ii  libgcc1  1:8.3.0-6
ii  libgnutls30  3.6.7-4
ii  libknot8 2.7.6-2
ii  liblmdb0 0.9.22-1
ii  libluajit-5.1-2  2.1.0~beta3+dfsg-5.1
ii  libstdc++6   8.3.0-6
ii  libsystemd0  241-7~deb10u2
ii  libuv1   1.24.1-1
ii  libzscanner2 2.7.6-2
ii  lua-sec  0.7-1
ii  lua-socket   3.0~rc1+git+ac3201d-4

Versions of packages knot-resolver recommends:
pn  knot-resolver-module-http  
pn  lua-basexx 

knot-resolver suggests no packages.

-- Configuration Files:
/etc/knot-resolver/kresd.conf changed [not included]

-- no debconf information

Bug#948034: roundcube-core: Adapt logroate config for added .log suffix to log files

[Frederik Himpe]

Package: roundcube
Version: 1.4.2+dfsg.1-1
Severity: normal

Dear Maintainer,

The new roundcube version now adds a .log suffix to its log files in
/var/log/roundcube. The logrotate configuration should be adapted
accordingly.

See https://github.com/roundcube/roundcubemail/blob/release-1.4/CHANGELOG :

RELEASE 1.4-beta

- Add .log suffix to all log file names, add option log_file_ext to
  control this (#313)


-- System Information:
Debian Release: 9.11
  APT prefers oldstable
  APT policy: (600, 'oldstable'), (550, 'oldstable-proposed-updates'), (500, 
'oldoldstable'), (420, 'stable'), (410, 'proposed-updates'), (300, 'testing'), 
(200, 'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/10 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages roundcube-core depends on:
ii  dbconfig-common 2.0.8
ii  debconf [debconf-2.0]   1.5.61
ii  dpkg1.18.25
ii  libjs-bootstrap44.4.1+dfsg1-1
ii  libjs-codemirror5.4.0-1
ii  libjs-jquery3.1.1-2+deb9u1
ii  libjs-jquery-minicolors 2.2.6+dfsg-3
ii  libjs-jquery-ui 1.12.1+dfsg-4
ii  libjs-jstimezonedetect  1.0.6-2
ii  libmagic1   1:5.30-1+deb9u3
ii  php 1:7.0+49
ii  php-auth-sasl   1.0.6-3
ii  php-common  1:49
ii  php-mail-mime   1.10.0-2
ii  php-masterminds-html5   2.7.0+dfsg-2
ii  php-net-sieve   1.4.1-1
ii  php-net-smtp1.8.0-1
ii  php-net-socket  1.0.14-2
ii  php-pear1:1.10.1+submodules+notgz-9+deb9u1
ii  php7.0 [php]7.0.33-0+deb9u6
ii  php7.0-cli [php-cli]7.0.33-0+deb9u6
ii  php7.0-intl [php-intl]  7.0.33-0+deb9u6
ii  php7.0-json [php-json]  7.0.33-0+deb9u6
ii  php7.0-mbstring [php-mbstring]  7.0.33-0+deb9u6
ii  roundcube-pgsql 1.4.2+dfsg.1-1
ii  ucf 3.0036

Versions of packages roundcube-core recommends:
ii  apache2 [httpd-cgi] 2.4.25-3+deb9u9
ii  php-pspell  1:7.0+49
ii  php7.0-fpm [php-fpm]7.0.33-0+deb9u6
ii  php7.0-gd [php-gd]  7.0.33-0+deb9u6
ii  php7.0-pspell [php-pspell]  7.0.33-0+deb9u6

Versions of packages roundcube-core suggests:
pn  php-crypt-gpg 
pn  php-mkopinsky-zxcvbn-php  
ii  php-net-ldap3 1.0.4-1
ii  roundcube-plugins 1.4.2+dfsg.1-1

Versions of packages roundcube depends on:
ii  dpkg  1.18.25

-- Configuration Files:
/etc/roundcube/apache.conf changed:
Alias /webmail/program/js/tiny_mce/ /usr/share/tinymce/www/
Alias /webmail /var/lib/roundcube

  Options Indexes MultiViews FollowSymLinks
  AllowOverride None
  Order allow,deny
  allow from all


  Options +FollowSymLinks
  # This is needed to parse /var/lib/roundcube/.htaccess. See its
  # content before setting AllowOverride to None.
  AllowOverride All
  Require all granted


Options -FollowSymLinks
AllowOverride None


Options -FollowSymLinks
AllowOverride None
Require all denied


Options -FollowSymLinks
AllowOverride None
Require all denied



-- debconf information excluded

Bug#948030: roundcube-plugins-extra: Replace unmaintained dkimstatus plugin by authres_status

[Frederik Himpe]

Package: roundcube-plugins-extra
Version: 1.3.8-20190219
Severity: normal

Dear Maintainer,

The dkimstatus plugin is not working and logs these errors:
[03-Jan-2020 12:25:32 Europe/Berlin] PHP Warning:  preg_match() expects 
parameter 2 to be string, array given in 
/usr/share/roundcube/plugins/dkimstatus/dkimstatus.php on line 73
[03-Jan-2020 12:25:32 Europe/Berlin] PHP Warning:  preg_match() expects 
parameter 2 to be string, array given in 
/usr/share/roundcube/plugins/dkimstatus/dkimstatus.php on line 77

Apparently this plugin is unmaintained: https://github.com/jvehent/dkimstatus

The authres_status plugin is partially based on this plugin and appears
to be maintained: 
https://plugins.roundcube.net/packages/roundcube/authres_status

It would be great to have this one in the roundcube-plugins-extra
package.


-- System Information:
Debian Release: 9.11
  APT prefers oldstable
  APT policy: (600, 'oldstable'), (550, 'oldstable-proposed-updates'), (500, 
'oldoldstable'), (420, 'stable'), (410, 'proposed-updates'), (300, 'testing'), 
(200, 'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/10 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages roundcube-plugins-extra depends on:
ii  libjs-jquery-mousewheel  11-3
ii  roundcube-core   1.4.2+dfsg.1-1

roundcube-plugins-extra recommends no packages.

Versions of packages roundcube-plugins-extra suggests:
ii  fail2ban  0.10.2-2~bpo9+1

-- Configuration Files:
/etc/roundcube/plugins/sieverules/config.inc.php changed [not included]

-- no debconf information

Bug#948011: Error message

[Frederik Himpe]

The error logged with too old libjs-bootstrap4 is this:

AH00037: Symbolic link not allowed or link target not accessible: 
/var/lib/roundcube/skins/elastic/deps/bootstrap.bundle.min.js, referer: 
https://example.com/webmail/?_task=mail&_action=compose


-- 
Frederik Himpe 
Vrije Universiteit Brussel

Bug#948011: roundcube-core: Needs dependency on newer libjs-bootstrap4 libjs-popper.js

[Frederik Himpe]

Package: roundcube
Version: 1.4.2+dfsg.1-1
Severity: normal

Dear Maintainer,

I installed roundcube-core 1.4.2 with libjs-bootstrap4:amd64 4.3.1+dfsg2-1
and libjs-popper.js 1.14.6+ds2-1, and noticed that the elastic theme was
not behaving properly: pop-ups were not working (for example the list
did not open when clicking on the priority and "sent folder" comboboxes
on the compose page), and the lay-out looked "garbled" (for example the
text pane on the compose page was not stretched out over the whole width
of the page).

I installed libjs-bootstrap4=4.4.1+dfsg1-1 which also pulled in an upgrade of
libjs-popper.js=1.16.0+ds2-1, and now it's behaving as I expected.


-- System Information:
Debian Release: 9.11
  APT prefers oldstable
  APT policy: (600, 'oldstable'), (550, 'oldstable-proposed-updates'), (500, 
'oldoldstable'), (420, 'stable'), (410, 'proposed-updates'), (300, 'testing'), 
(200, 'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/10 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages roundcube-core depends on:
ii  dbconfig-common 2.0.8
ii  debconf [debconf-2.0]   1.5.61
ii  dpkg1.18.25
ii  libjs-bootstrap44.4.1+dfsg1-1
ii  libjs-codemirror5.4.0-1
ii  libjs-jquery3.1.1-2+deb9u1
ii  libjs-jquery-minicolors 2.2.6+dfsg-3
ii  libjs-jquery-ui 1.12.1+dfsg-4
ii  libjs-jstimezonedetect  1.0.6-2
ii  libmagic1   1:5.30-1+deb9u3
ii  php 1:7.0+49
ii  php-auth-sasl   1.0.6-3
ii  php-common  1:49
ii  php-mail-mime   1.10.0-2
ii  php-masterminds-html5   2.7.0+dfsg-2
ii  php-net-sieve   1.4.1-1
ii  php-net-smtp1.8.0-1
ii  php-net-socket  1.0.14-2
ii  php-pear1:1.10.1+submodules+notgz-9+deb9u1
ii  php7.0 [php]7.0.33-0+deb9u6
ii  php7.0-cli [php-cli]7.0.33-0+deb9u6
ii  php7.0-intl [php-intl]  7.0.33-0+deb9u6
ii  php7.0-json [php-json]  7.0.33-0+deb9u6
ii  php7.0-mbstring [php-mbstring]  7.0.33-0+deb9u6
ii  roundcube-pgsql 1.4.2+dfsg.1-1
ii  ucf 3.0036

Versions of packages roundcube-core recommends:
ii  apache2 [httpd-cgi] 2.4.25-3+deb9u9
ii  php-pspell  1:7.0+49
ii  php7.0-fpm [php-fpm]7.0.33-0+deb9u6
ii  php7.0-gd [php-gd]  7.0.33-0+deb9u6
ii  php7.0-pspell [php-pspell]  7.0.33-0+deb9u6

Versions of packages roundcube-core suggests:
pn  php-crypt-gpg 
pn  php-mkopinsky-zxcvbn-php  
ii  php-net-ldap3 1.0.4-1
ii  roundcube-plugins 1.4.2+dfsg.1-1

Versions of packages roundcube depends on:
ii  dpkg  1.18.25

-- Configuration Files:
/etc/roundcube/apache.conf changed [not included]

-- debconf information excluded

Bug#945224: closed by Michael Biebl (Re: Bug#945224: resolve gateway libnss-myhostname)

[Frederik Vos]

i am sorry, missed that one … see also 
https://github.com/systemd/systemd/commit/5248e7e1f11aba6859de0b28f0dd3778b22842f2

> On 21 Nov 2019, at 14:36, Debian Bug Tracking System  
> wrote:
> 
> This is an automatic notification regarding your Bug report
> which was filed against the libnss-myhostname package:
> 
> #945224: resolve gateway libnss-myhostname
> 
> It has been closed by Michael Biebl .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Michael Biebl 
>  by
> replying to this email.
> 
> 
> -- 
> 945224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945224
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> 
> From: Michael Biebl 
> Subject: Re: Bug#945224: resolve gateway libnss-myhostname
> Date: 21 November 2019 at 14:33:30 CET
> To: Frederik Vos , 945224-d...@bugs.debian.org
> 
> 
> Am 21.11.19 um 14:05 schrieb Frederik Vos:
>> Package: libnss-myhostname
>> Version: 241-7~deb10u2
>> 
>> getent ahosts $(hostname) works as expected,
>> getent ahosts gateway does not
>> 
>> A strace suggest that it is found:
>> 
>> recvfrom(3, "\224\235\204\3\0\1\0\0\0\0\0\0\7gateway\vlocaldomain"..., 2048, 
>> 0,
>> {sa_family=AF_INET, sin_port=htons(53), 
>> sin_addr=inet_addr("192.168.122.2")}, [2
>> 8->16]) = 37
>> 
>> but it is never printed to the standard output
> 
> Please see man nss-myhostname:
> 
>>   •   The hostname "_gateway" is resolved to all current default routing
>>   gateway addresses, ordered by their metric. This assigns a stable
>>   hostname to the current gateway, useful for referencing it
>>   independently of the current network configuration state.
> 
> I.e. use getent ahosts _gateway
> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 
> 
> 
> 
> 
> getent ahosts $(hostname) works as expected,
> getent ahosts gateway does not
> 
> A strace suggest that it is found:
> 
> recvfrom(3, "\224\235\204\3\0\1\0\0\0\0\0\0\7gateway\vlocaldomain"..., =
> 2048, 0,
> {sa_family=3DAF_INET, sin_port=3Dhtons(53), =
> sin_addr=3Dinet_addr("192.168.122.2")}, [2
> 8->16]) =3D 37
> 
> but it is never printed to the standard output
> 
>  Operating System: Debian GNU/Linux 10 (buster)
>Kernel: Linux 4.19.0-6-amd64
>   Architecture: x86-64=
> 
> 

Bug#945224: resolve gateway libnss-myhostname

[Frederik Vos]

Package: libnss-myhostname
Version: 241-7~deb10u2

getent ahosts $(hostname) works as expected,
getent ahosts gateway does not

A strace suggest that it is found:

recvfrom(3, "\224\235\204\3\0\1\0\0\0\0\0\0\7gateway\vlocaldomain"..., 2048, 0,
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.122.2")}, [2
8->16]) = 37

but it is never printed to the standard output

  Operating System: Debian GNU/Linux 10 (buster)
Kernel: Linux 4.19.0-6-amd64
   Architecture: x86-64

Bug#935004: cups-filters: print test page problem solved by upgrading to github version (1.25.1)

[frederik]

You need to change the "deb" line in /etc/apt/sources.list to use the
unstable archive:

 deb http://deb.debian.org/debian/ unstable main contrib non-free

Then 'apt update' followed by 'apt install cups-filters'.

I do not see any benefit in updating the other other packages, but it
should not do any harm.


I think it is not so simple as that on Raspbian, first of all I don't want 
*all* new packages to come from Debian Unstable, so I should have some command 
that specifies this archive is to be used for just one package. Besides, if it 
is true that CUPS doesn't work on Raspbian Buster then that should probably be 
fixed. But again no one else has reported it so maybe it is something on my 
end. FWIW when I ran 'apt update' I got:

W: GPG error: http://deb.debian.org/debian unstable InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138



Also, is there a reason why you think the new version would fix the
problem? Perhaps since my time is limited and no one else has reported
this bug, we should regard it as a potential misconfiguration, or an
issue that may have arisen from my trying to install and then
uninstall the Github cups-filters package as I explained in my
original report.


Testing is best done with the latest version. You have described your
issue well, but we have little to go on. My inability to reproduce it
on unstable would incline me to close the report.


I don't mind if you close the report.


(The avahi-browse output would still be useful my records).



> > What might also prove useful later on is avahi.log from
> >  avahi-browse -art > avahi.log
> > avahi-browse is in the avahi-utils package.


Thanks for reminding me, I'm attaching the output although I'm not sure why you 
need it. The printer is a USB printer, I thought Avahi was network-related 
(like mDNS and stuff?).


A full error log would be useful. It will compress very well with gzip
before being sent as an attachment.



Would you also do (as root)



 cupsfilter -p /etc/cups/ppd/ -m printer/foo -e 
/usr/share/cups/data/default-testpage.pdf > out.dat
2>log



and post log.


Here's the entire error log after running the above cupsfilter command:

$ less /var/log/cups/error_log
E [28/Aug/2019:23:37:42 +] HP_Photosmart_Plus_B210_series: File 
\"/usr/lib/cups/filter/hpcups\" not available: No such file or directory
E [28/Aug/2019:23:37:42 +] [Job 71] Unknown MIME type 
application/vnd.cups-pdf-banner for file 1.

Note that this file does indeed exist:

$ file /usr/lib/cups/filter/hpcups
/usr/lib/cups/filter/hpcups: ELF 32-bit LSB executable, ARM, EABI5 version 1 
(SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 
3.2.0, BuildID[sha1]=ddd2c08496a0a15afb812660a6a0c6c4fe269f0e, stripped

I've been seeing the error about "File \"/usr/lib/cups/filter/hpcups\" not 
available: No such file or directory" at other times as well, but I couldn't reproduce it so I 
didn't submit a bug.

It was interesting to learn about cupsfilter and avahi-browse, thank you.

Taking a step back, it seems that if CUPS is complaining about 'Unsupported format 
"text/plain"' when the test page is a PDF, and when text/plain is supported, and when the 
actual error has to do with \"/usr/lib/cups/filter/hpcups\" not existing, even though it 
does exist  then I think it might be that we should prioritize getting CUPS to have better 
error reporting, rather than what we are doing.

Thanks,

Frederick


cupsfilter.tar.gz
Description: application/gzip
+   eth0 IPv6 HP Photosmart Plus B210 series @ musa Internet Printer
 local
+   eth0 IPv6 Brother DCP-7065DN @ musa Internet Printer
 local
+   eth0 IPv4 HP Photosmart Plus B210 series @ musa Internet Printer
 local
+   eth0 IPv4 Brother DCP-7065DN @ musa Internet Printer
 local
+   eth0 IPv4 Brother DCP-7065DN @ thutmose Internet Printer
 local
+   eth0 IPv4 HP Photosmart Plus B210 series USB @ thutmose Internet Printer
 local
+   eth0 IPv4 P1102_remote @ thutmose   Internet Printer
 local
+   eth0 IPv4 HP Photosmart Plus B210 series @ thutmose Internet Printer
 local
+   eth0 IPv6 HP Photosmart Plus B210 series @ musa Secure Internet 
Printer local
+   eth0 IPv6 Brother DCP-7065DN @ musa Secure Internet 
Printer local
+   eth0 IPv4 HP Photosmart Plus B210 series @ musa Secure Internet 
Printer local
+   eth0 IPv4 Brother DCP-7065DN @ musa Secure Internet 
Printer local
+   eth0 IPv4 Brother DCP-7065DN @ thutmose Secure Internet 
Printer local
+   eth0 IPv4 HP Photosmart Plus B210 series USB @ thutmose Secure Internet 
Printer local
+   eth0 IPv4 P1102_remote @ thutmose   Secure Internet 
Printer local
+   eth0 IPv4 HP Photosmart Plus B210 series @ 

Bug#935816: php-horde-imp: Default installation does not display text email

[Frederik Vanrenterghem]

On Mon, 26 Aug 2019 16:37:15 +0200 Frederik Vanrenterghem <
frederik_debianbugrep...@vanrenterghem.biz> wrote:

> 
> A similar problem is described on 
https://horde.horde.narkive.com/acoQ1HB5/display-problem-with-php7-3
> 

I can confirm applying the small patches mentioned on 
https://github.com/horde/Text_Filter/commit/8d0de407dbb95626bc54eaba078191847be9c574
fixes the issue.

I believe this makes this bug a duplicate of 931255, which is resolved
in the current version of horde in testing and unstable. No backports
package appears available at this stage for the stable release buster.

Bug#935816: php-horde-imp: Default installation does not display text email

[Frederik Vanrenterghem]

Package: php-horde-imp
Version: 6.2.22-1
Severity: normal
Tags: a11y

Dear Maintainer,

A default installation of the Horde webmail package does not display
plaintext emails. Instead, following error is shown in the message
content section:

Cannot display message text.
The message part may contain incorrect character set information preventing 
correct display.

A similar problem is described on 
https://horde.horde.narkive.com/acoQ1HB5/display-problem-with-php7-3

Mail is accessed on a Dovecot localhost instance.

Sample mail content:

Subject: test
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline

dit is een test

The message can be seen by viewing the mail source.

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-5-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php-horde-imp depends on:
ii  php-cli2:7.3+69
ii  php-common 2:69
ii  php-horde  5.2.20+debian0-1
ii  php-horde-auth 2.2.2-3
ii  php-horde-browser  2.0.15-3
ii  php-horde-cache2.5.5-3
ii  php-horde-compress 2.2.1-4
ii  php-horde-core 2.31.6+debian0-1
ii  php-horde-crypt2.7.12-1
ii  php-horde-css-parser   1.0.11-3
ii  php-horde-date 2.4.1-3
ii  php-horde-editor   2.0.5+debian0-2
ii  php-horde-exception2.0.8-4
ii  php-horde-icalendar2.1.8-1
ii  php-horde-image2.5.3-1
ii  php-horde-imap-client  2.29.16-1
ii  php-horde-itip 2.1.2-4
ii  php-horde-listheaders  1.2.5-3
ii  php-horde-logintasks   2.0.7-4
ii  php-horde-mail 2.6.4-3
ii  php-horde-mail-autoconfig  1.0.3-4
ii  php-horde-mime 2.11.0-2
ii  php-horde-mime-viewer  2.2.2-3
ii  php-horde-nls  2.2.1-3
ii  php-horde-notification 2.0.4-5
ii  php-horde-pack 1.0.7-3
ii  php-horde-perms2.1.7-4
ii  php-horde-spellchecker 2.1.3-5
ii  php-horde-stream   1.6.3-5
ii  php-horde-stream-filter2.0.4-5
ii  php-horde-stream-wrapper   2.1.4-2
ii  php-horde-support  2.2.0-3
ii  php-horde-text-filter  2.3.5-3
ii  php-horde-text-flowed  2.0.3-5
ii  php-horde-tree 2.0.5-3
ii  php-horde-url  2.2.6-3
ii  php-horde-util 2.5.8-3
ii  php-horde-vfs  2.4.0-3
ii  php-horde-view 2.0.6-5
ii  php-xml2:7.3+69
ii  php7.3-cli [php-cli]   7.3.4-2
ii  php7.3-json [php-json] 7.3.4-2
ii  php7.3-xml [php-xml]   7.3.4-2

Versions of packages php-horde-imp recommends:
ii  php-horde-history   2.3.6-5
ii  php-horde-http  2.1.7-3
ii  php-horde-service-gravatar  1.0.1-5
pn  php-phpseclib-file-asn1 

php-horde-imp suggests no packages.

-- no debconf information

Bug#935004: cups-filters: print test page problem solved by upgrading to github version (1.25.1)

[frederik]

Sorry for the delay, I just ran 'sudo apt-get update' and 'sudo apt-get remove 
cups-filters' and 'sudo apt-get install cups cups-filters hplip 
printer-driver-gutenprint printer-driver-hpcups' and I saw that it is trying to 
install the same version of cups-filters as I had reported the bug in. Can you 
explain how I should install the version you uploaded to Debian Unstable? I 
don't often use Debian so I am not familiar with this process.

Also, is there a reason why you think the new version would fix the problem? 
Perhaps since my time is limited and no one else has reported this bug, we 
should regard it as a potential misconfiguration, or an issue that may have 
arisen from my trying to install and then uninstall the Github cups-filters 
package as I explained in my original report.

Thanks!

On Sun, Aug 18, 2019 at 05:27:29PM +0200, Didier 'OdyX' Raboud wrote:

Le dimanche, 18 août 2019, 01.13:46 h CEST frede...@ofb.net a écrit :

Package: cups-filters
Version: 1.21.6-5
Severity: normal

(resending due to email problems on Pi)

Dear Maintainer,

I get the following error when trying to print a test page on my inkjet (via
the web interface):

Print Test Page
Print Test Page HP_Photosmart_Plus_B210_series Error

Unable to print test page:

Unsupported format "text/plain".

I will try to attach the PPD.

The software works fine when I install the latest version of cups-filters
from GitHub. Here is something from error log


I have just uploaded 1.25.2 to Debian unstable; could you try this version,
from the Debian repos?

Cheers,
   OdyX

Bug#935004: cups-filters: print test page problem solved by upgrading to github version (1.25.1)

[frederik]

I'm so sorry I will try to get around to that today

On Sat, Aug 24, 2019 at 08:21:21PM +0100, Brian Potkin wrote:

tags 935004 moreinfo
thanks


On Sun 18 Aug 2019 at 17:27:29 +0200, Didier 'OdyX' Raboud wrote:


I have just uploaded 1.25.2 to Debian unstable; could you try this version,
from the Debian repos?


Any news?

Cheers,

Brian.

Bug#935058: torbrowser-launcher: Fails to start because apparmor prevents acces to mutter/xwayland xauth file

[Frederik Himpe]

On Mon, 2019-08-19 at 08:10 +0200, intrigeri wrote:
> torbrowser-launcher fails to start with this apparmor message in
> > kernel log:
> > [  135.043787] audit: type=1400 audit(1566153604.771:58):
> > apparmor="DENIED"
> > operation="open" profile="torbrowser_firefox"
> > name="/run/user/1000/.mutter-
> > Xwaylandauth.B4GI6Z" pid=4793 comm="firefox.real"
> > requested_mask="r"
> > denied_mask="r" fsuid=1000 ouid=1000


> Can you please add the following line to
> /etc/apparmor.d/abstractions/wayland
> 
>   owner /run/user/*/.mutter-Xwaylandauth.* r,
> 
> … then reload the affected profile with:
> 
>   sudo apparmor_parser -r /etc/apparmor.d/torbrowser.Browser.firefox 

Confirmed, this fixes the problem.

Thanks!

-- 
Frederik Himpe 

Bug#935058: torbrowser-launcher: Fails to start because apparmor prevents acces to mutter/xwayland xauth file

[Frederik Himpe]

Package: torbrowser-launcher
Version: 0.3.2-1
Severity: important

torbrowser-launcher fails to start with this apparmor message in kernel log:

[  135.043787] audit: type=1400 audit(1566153604.771:58): apparmor="DENIED"
operation="open" profile="torbrowser_firefox" name="/run/user/1000/.mutter-
Xwaylandauth.B4GI6Z" pid=4793 comm="firefox.real" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=1000

This happens when starting torbrowser-launcher in a GNOME Wayland session with
Mutter 3.33.90-2 from Experimental.



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'oldoldstable'), (500, 'testing'), (400, 'unstable'), (250, 'stable'), (160, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20190110
ii  libdbus-glib-1-2  0.110-4
ii  python3   3.7.3-1
ii  python3-gpg   1.13.0-2
ii  python3-pyqt5 5.12.3+dfsg-1
ii  python3-requests  2.21.0-1
ii  python3-socks 1.6.8+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.4.0.5-2

Versions of packages torbrowser-launcher suggests:
ii  apparmor  2.13.3-4

-- no debconf information

Bug#935004: cups-filters: print test page problem solved by upgrading to github version (1.25.1)

[frederik]

Package: cups-filters
Version: 1.21.6-5
Severity: normal

(resending due to email problems on Pi)

Dear Maintainer,

I get the following error when trying to print a test page on my inkjet (via 
the web interface):

   Print Test Page
   Print Test Page HP_Photosmart_Plus_B210_series Error

   Unable to print test page:

   Unsupported format "text/plain".

I will try to attach the PPD.

The software works fine when I install the latest version of cups-filters from 
GitHub. Here is something from error log

   E [17/Aug/2019:17:32:36 +] HP_Photosmart_Plus_B210_series: File 
\"/usr/lib/cups/filter/hpcups\" not available: No such file or directory
   E [17/Aug/2019:17:32:36 +] [Job 37] Unknown MIME type 
application/vnd.cups-pdf-banner for file 1.
   E [17/Aug/2019:17:34:28 +] [Client 8] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/HP_Photosmart_Plus_B210_series) from localhost.

Note the file /usr/lib/cups/filter/hpcups does indeed exist.

To check the behavior of the Raspbian packages I do this:

   # in github cups-filters directory
   sudo make uninstall
   sudo apt-get remove cups-filters
   # this is the list of packages that got uninstalled in previous step
   sudo apt-get install cups cups-filters hplip printer-driver-gutenprint 
printer-driver-hpcups

Then when I do "sudo make install" (installing the version from GitHub) 
everything works again. I hope I haven't messed up the package file structure by 
alternately installing the Apt version and the GitHub version.

Also note that for building the github repo I tried this:

   sudo apt-get build-dep cups-filters

However this didn't get all the build dependencies, I also had to do this:

   sudo apt-get install mupdf-tools
   sudo apt-get install automake-1.15

I hope this is all helpful and I'm not doing something dumb again.

Thank you for maintaining this package, I was pleasantly surprised that I could 
use my Raspberry Pi as a print server.


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 10 (buster)
Release:10
Codename:   buster
Architecture: armv7l

Kernel: Linux 4.19.58-v7+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups-filters depends on:
ii  bc 1.07.1-2
ii  cups-filters-core-drivers  1.21.6-5
ii  ghostscript9.27~dfsg-2+deb10u1
ii  libc6  2.28-10+rpi1
ii  libcups2   2.2.10-6
ii  libcupsfilters11.21.6-5
ii  libcupsimage2  2.2.10-6
ii  libfontconfig1 2.13.1-2
ii  libfontembed1  1.21.6-5
ii  libgcc11:8.3.0-6+rpi1
ii  libqpdf21  8.4.0-2
ii  libstdc++6 8.3.0-6+rpi1
ii  poppler-utils  0.71.0-5

Versions of packages cups-filters recommends:
ii  colord 1.4.3-4
ii  liblouisutdml-bin  2.7.0-5+b1

Versions of packages cups-filters suggests:
pn  antiword   
pn  docx2txt   
pn  foomatic-db-compressed-ppds | foomatic-db  
ii  imagemagick8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]8:6.9.10.23+dfsg-2.1

-- no debconf information

--===2022940238==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="HP_Photosmart_Plus_B210_series.ppd"

*PPD-Adobe: "4.3"
* PPD file for HP Photosmart Plus b210 Series with CUPS.
* Created by the CUPS PPD Compiler CUPS v2.2.10.
*% (c) 2008 Copyright HP Development Company, LP
*FormatVersion: "4.3"
*FileVersion: "3.18.12"
*LanguageVersion: English
*LanguageEncoding: ISOLatin1
*PCFileName: "hp-photosmart_plus_b210_series.ppd"
*Product: "(HP Photosmart Plus b210 Series)"
*Manufacturer: "HP"
*ModelName: "HP Photosmart Plus b210 Series"
*ShortNickName: "HP Photosmart Plus b210 Series hpijs"
*NickName: "HP Photosmart Plus b210 Series, hpcups 3.18.12"
*PSVersion: "(3010.000) 0"
*LanguageLevel: "3"
*ColorDevice: True
*DefaultColorSpace: RGB
*FileSystem: False
*Throughput: "1"
*LandscapeOrientation: Plus90
*TTRasterizer: Type42
*% Driver-defined attributes...
*RequiresPageRegion All: True
*hpPrinterLanguage: "pcl3gui2"
*HPMechOffset: "70"
*1284DeviceID: "MFG:HP;MDL:photosmart plus b210 series;DES:photosmart plus b210 
series;"
*cupsVersion: 2.2
*cupsModelNumber: 0
*cupsManualCopies: True
*cupsFilter: "application/vnd.cups-raster 0 hpcups"
*cupsLanguages: "en"
*UIConstraints: *ColorModel KGray *OutputMode Photo
*UIConstraints: *OutputMode Photo *ColorModel KGray
*UIConstraints: *ColorModel CMYGray *OutputMode Photo
*UIConstraints: *OutputMode Photo *ColorModel CMYGray
*UIConstraints: *MediaType 

Bug#926771: knot-resolver: Needs to recommend lua-cqueues for automatic detection of changes to RPZ file

[Frederik Himpe]

Package: knot-resolver
Version: 3.2.1-3
Severity: normal

Dear Maintainer,

The package should at least recommend the lua-cqueues package, because that one 
is needed for detecting changes to RPZ files.

https://github.com/CZ-NIC/knot-resolver/blob/master/modules/policy/policy.lua#L430

-- System Information:
Debian Release: 9.8
  APT prefers stable
  APT policy: (600, 'stable'), (550, 'proposed-updates'), (500, 'oldstable'), 
(420, 'testing'), (200, 'unstable'), (160, 'experimental'), (110, 'xenial')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-3-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages knot-resolver depends on:
ii  adduser  3.115
ii  dns-root-data2017072601~deb9u1
ii  libc62.28-8
ii  libdnssec6   2.7.6-2~bpo9+1
ii  libedit2 3.1-20160903-3
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libgnutls30  3.6.6-2
ii  libknot8 2.7.6-2~bpo9+1
ii  liblmdb0 0.9.18-5
ii  libluajit-5.1-2  2.0.4+dfsg-1+b1
ii  libstdc++6   6.3.0-18+deb9u1
ii  libsystemd0  241-1
ii  libuv1   1.18.0-3~bpo9+1
ii  libzscanner2 2.7.6-2~bpo9+1
ii  lua-sec  0.6-3
ii  lua-socket   3.0~rc1+git+ac3201d-3

Versions of packages knot-resolver recommends:
pn  knot-resolver-module-http  
pn  lua-basexx 

knot-resolver suggests no packages.

-- Configuration Files:
/etc/knot-resolver/kresd.conf changed [not included]

-- no debconf information

Bug#501194: info opens browser even when argument is not found

[frederik]

Wow, you are very diligent.

Yes it seems to have been fixed sometime in the past 11 years!

Thanks.

On Mon, Feb 04, 2019 at 05:51:15PM +0100, Hilmar Preuße wrote:


Am 05.10.2008 um 14:23 teilte Frederik Eaton mit:

Hi Frederik,


Package: info
Version: 4.11.dfsg.1-4
Severity: minor

If I am looking for information on 'foo', the program 'man' tells me
right away that it isn't in the manpage database:

$ man foo
No manual entry for foo

However, 'info' forces the user to read through the following output:


With


hille@sid:~ $ info --version
info (GNU texinfo) 6.5

Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.


I see:

hille@sid:~ $ info foo
info: No menu item 'foo' in node '(dir)Top'

I guess we can close the bug. Please confirm.

Hilmar
--
#206401 http://counter.li.org

Bug#920552: procps: Enable regular file and FIFO protection

[Frederik Himpe]

Package: procps
Version: 2:3.3.15-2
Severity: normal

In analogy with bug #889098, procps should by default enabling the regular file
and FIFO protection added in 4.19 by setting:

fs.protected_regular = 1
fs.protected_fifos = 1

This will be done by default in systemd 241, but as Debian does not use
Systemd's sysctl settings, it should be made in procps.

References:
https://github.com/torvalds/linux/commit/30aba6656f
https://github.com/systemd/systemd/commit/2732587540035227fe59e4b64b60127352611b35
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889098



-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (400, 'unstable'), (250, 'stable'), (160, 'experimental'), (100, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages procps depends on:
ii  init-system-helpers  1.56+nmu1
ii  libc62.28-5
ii  libncurses6  6.1+20181013-1
ii  libncursesw6 6.1+20181013-1
ii  libprocps7   2:3.3.15-2
ii  libtinfo66.1+20181013-1
ii  lsb-base 10.2018112800

Versions of packages procps recommends:
ii  psmisc  23.2-1

procps suggests no packages.

-- no debconf information

Bug#912665: (geen onderwerp)

[Frederik Himpe]

FYI, this is where it crashes:

#0  0x7fc0172239c6 in _IO_fgets (buf=0x7ffc9b2b1640 "  
/dev/aivmhost3-vg/ceph-node1-storage:ceph-ff35163d-b03f-4dbf-a6ce-155730069dc0:4194304:-1:8:8:-1:4096:511:0:511:ZNexTV-ylVb-ltMP-T8Zu-ZklU-cN1I-dETf5o\n", 
n=1024, fp=0x1a90030)

at iofgets.c:47

Bug#912665: libc6: dsm_sa_datamgrd crashes in libc6 since update from 2.27-6 to 2.27-8

[Frederik Himpe]

Package: libc6
Version: 2.27-6
Severity: normal

Dear Maintainer,

I upgraded today from libc6 version 2.27-6 to version 2.27-8 in testing. After 
that, the dsm_sa_datamgrd process, part of Dell OpenManage utilities and 
started by the dataeng init script, crashes. Reverting to libc6 2.27-6, fixes 
the problem.

   PID: 1818 (dsm_sa_datamgrd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 11 (SEGV)
 Timestamp: Fri 2018-11-02 15:02:20 CET (1h 55min ago)
  Command Line: /opt/dell/srvadmin/sbin/dsm_sa_datamgrd
Executable: /opt/dell/srvadmin/sbin/dsm_sa_datamgrd
 Control Group: /system.slice/dataeng.service
  Unit: dataeng.service
 Slice: system.slice
   Boot ID: 61c29297067f417b9bce592fd0b72fca
Machine ID: 463207fee8e74cc5a854722afda5b9e2
  Hostname: ai-vmhost3
   Storage: 
/var/lib/systemd/coredump/core.dsm_sa_datamgrd.0.61c29297067f417b9bce592fd0b72fca.1818.1541167340.lz4
   Message: Process 1818 (dsm_sa_datamgrd) of user 0 dumped core.

Stack trace of thread 1818:
#0  0x7f1bffe389c6 _IO_fgets (libc.so.6)
#1  0x7f1bf8048905 _Z21get_disk_of_volume_V2PcPS_iPi 
(libmvraid.so)
#2  0x7f1bf8049485 
_ZN22LinuxSystemDiskScanner10scanOSDiskEv (libmvraid.so)
#3  0x7f1bf8049595 _ZN22LinuxSystemDiskScanner4scanEv 
(libmvraid.so)
#4  0x7f1bf80479e0 OSCheckManagement_init (libmvraid.so)
#5  0x7f1bf804b6b2 inter_MV_API_Initialize (libmvraid.so)
#6  0x7f1bf80342df MV_API_Initialize (libmvraid.so)
#7  0x7f1bf82d4fbc 
_ZN24CMVLibraryInterfaceLayer18getControllerCountEP14IVendorLibrary 
(libdsm_sm_gsmvil.so)
#8  0x7f1bf82a5445 
_ZN3stg22CLibraryManager_Helper24checkControllerExistenceEjP14IVendorLibrary 
(libdsm_sm_gsmvil.so)
#9  0x7f1bf828deba _ZN14CLibraryLoader16createAllLibObjsEv 
(libdsm_sm_gsmvil.so)
#10 0x7f1bf828c1f5 
_ZN15CLibraryManager17initializeLibraryEv (libdsm_sm_gsmvil.so)
#11 0x7f1bf82a31ae _ZN15CCommandHandler10initializeEv 
(libdsm_sm_gsmvil.so)
#12 0x7f1bf82a43c3 _ZN15CCommandHandler9navigatorEjPvPS0_ 
(libdsm_sm_gsmvil.so)
#13 0x7f1bf82864c0 libdsm_sm_gsmvil_entry 
(libdsm_sm_gsmvil.so)
#14 0x7f1bfafabec5 ValInit (libdsm_sm_val.so)
#15 0x7f1bfb1dcb94 StorageInit (libdsm_sm_ral.so)
#16 0x7f1bfb1dfb42 PopulatorDispatch (libdsm_sm_ral.so)
#17 0x7f1bfb1dfcb7 RAL_SMPopulatorDispatch 
(libdsm_sm_ral.so)
#18 0x00412ef9 PopLdrNodeDispatchByPopID 
(dsm_sa_datamgrd)
#19 0x0040ab5d PopDispPopLoad (dsm_sa_datamgrd)
#20 0x00413385 PopStartStopLoadByPopINICfgDLWalk 
(dsm_sa_datamgrd)
#21 0x7f1c001e1171 DLListWalkAtHead (libdcsupt.so.9)
#22 0x004134bd PopStartStopDispatchByPopID 
(dsm_sa_datamgrd)
#23 0x00413560 PopStartStopLoadPopByAliasListAndType 
(dsm_sa_datamgrd)
#24 0x00413781 PopStartStopAllLoad (dsm_sa_datamgrd)
#25 0x004137d9 PopStartStopAttach (dsm_sa_datamgrd)
#26 0x0040cccd DMModAttach (dsm_sa_datamgrd)
#27 0x0040cd9d ModuleSvcAttach (dsm_sa_datamgrd)
#28 0x00417b55 ModuleMain (dsm_sa_datamgrd)
#29 0x7f1bffdecb17 __libc_start_main (libc.so.6)
#30 0x0040a839 _start (dsm_sa_datamgrd)

Stack trace of thread 1823:
#0  0x7f1bffeb7739 __poll (libc.so.6)
#1  0x7f1bf975c00d _ZN20__LSI_STORELIB_IR3__7monitorEPv 
(libstorelibir-3.so)
#2  0x7f1bfff8ef2a start_thread (libpthread.so.0)
#3  0x7f1bffec1edf __clone (libc.so.6)

Stack trace of thread 1827:
#0  0x7f1bffec3cb7 semop (libc.so.6)
#1  0x7f1c001e8d21 WaitForSemaphore (libdcsupt.so.9)
#2  0x7f1c001e9e37 OSEventWait (libdcsupt.so.9)
#3  0x7f1bfaaeae11 _Z16BtmTimerTickTaskPv 
(libdsm_sm_sasvil.so)
#4  0x7f1bfff8ef2a start_thread (libpthread.so.0)
#5  0x7f1bffec1edf __clone (libc.so.6)

Stack trace of thread 1824:
#0  0x7f1bffe8f510 __nanosleep (libc.so.6)
#1  0x7f1bffeba2f4 usleep (libc.so.6)
#2  0x7f1bf975d2b8 _ZN20__LSI_STORELIB_IR3__5SleepEi 
(libstorelibir-3.so)
#3  0x7f1bf976fe62 
_ZN20__LSI_STORELIB_IR3__21monitorEnclosureFaultEPv (libstorelibir-3.so)
#4  0x7f1bfff8ef2a start_thread (libpthread.so.0)

Bug#912575: cups: ipp backend is not able to authenticate using kerberos

[Felix Frederik Zimmermann]

Package: cups
Version: 2.2.1-8+deb9u2
Severity: important

Hi,

in debian stable, the ipp backend is not using the kerberos ticket of the user. 
This bug is reported (https://github.com/apple/cups/issues/5233) and fixed 
upstream 
(https://github.com/apple/cups/commit/c59948f6fb2261653593c7d09ed2c0f673f610e2).
 Please consider applying this patch to the stable branch as it fixes a 
security related bug and would allow users to use kerberos for securing access 
to an remote printer queue.

Thank you
Felix


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups depends on:
ii  cups-client2.2.1-8+deb9u2
ii  cups-common2.2.1-8+deb9u2
ii  cups-core-drivers  2.2.1-8+deb9u2
ii  cups-daemon2.2.1-8+deb9u2
ii  cups-filters   1.11.6-3
ii  cups-ppdc  2.2.1-8+deb9u1
ii  cups-server-common 2.2.1-8+deb9u2
ii  debconf [debconf-2.0]  1.5.61
ii  ghostscript9.20~dfsg-3.2+deb9u2
ii  libavahi-client3   0.6.32-2
ii  libavahi-common3   0.6.32-2
ii  libc-bin   2.24-11+deb9u3
ii  libc6  2.24-11+deb9u3
ii  libcups2   2.2.1-8+deb9u2
ii  libcupscgi12.2.1-8+deb9u2
ii  libcupsimage2  2.2.1-8+deb9u2
ii  libcupsmime1   2.2.1-8+deb9u2
ii  libcupsppdc1   2.2.1-8+deb9u2
ii  libgcc11:6.3.0-18+deb9u1
ii  libstdc++6 6.3.0-18+deb9u1
ii  libusb-1.0-0   2:1.0.21-1
ii  poppler-utils  0.48.0-2+deb9u2
ii  procps 2:3.3.12-3+deb9u1

Versions of packages cups recommends:
pn  avahi-daemon 
pn  colord   
ii  cups-filters [ghostscript-cups]  1.11.6-3
ii  printer-driver-gutenprint5.2.11-1+b2

Versions of packages cups suggests:
pn  cups-bsd   
pn  cups-pdf   
pn  foomatic-db-compressed-ppds | foomatic-db  
ii  hplip  3.16.11+repack0-3
ii  printer-driver-hpcups  3.16.11+repack0-3
pn  smbclient  
ii  udev   232-25+deb9u4

-- debconf information excluded

Bug#911972: greenbone-security-assistant Default-Start contains no runlevels

[Frederik Himpe]

Package: greenbone-security-assistant
Version: 7.0.3+dfsg.1-1
Severity: normal

Dear Maintainer,

Trying to prevent greenbone-security-assistant from starting by default,
fails with this error:

# systemctl disable greenbone-security-assistant
Synchronizing state of greenbone-security-assistant.service with SysV service 
script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable 
greenbone-security-assistant
update-rc.d: error: greenbone-security-assistant Default-Start contains no 
runlevels, aborting.


-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (600, 'stable'), (550, 'proposed-updates'), (500, 'oldstable'), 
(450, 'oldstable-proposed-updates'), (420, 'testing'), (200, 'unstable'), (160, 
'experimental'), (150, 'oldoldstable'), (140, 'oldoldstable-proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages greenbone-security-assistant depends on:
ii  greenbone-security-assistant-common  7.0.3+dfsg.1-1
ii  libc62.27-6
ii  libgcrypt20  1.8.3-1
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.19-1
ii  libmicrohttpd12  0.9.59-1
ii  libopenvas9  9.0.3-1+b1
ii  libxml2  2.9.4+dfsg1-2.2+deb9u2
ii  libxslt1.1   1.1.29-2.1
ii  lsb-base 9.20161125

greenbone-security-assistant recommends no packages.

greenbone-security-assistant suggests no packages.

-- no debconf information

Bug#909191: gitaly: Hard coded outdated version numbers in Gemfile and Gemfile.lock cause problems with newer versions

[Frederik Himpe]

Package: gitaly
Version: 0.96.2+debian-2~bpo9+1
Severity: normal

When creating a project in gitlab, there was an error that it failed to
create the repository via gitlab-shell.

In the gitaly logs, I found that it failed to connect to gitaly-ruby:

Sep 19 14:48:02 ai-gitlab gitaly[17635]: time="2018-09-19T14:48:02+02:00" 
level=info msg="grpc: addrConn.createTransport failed to connect to 
{/tmp/gitaly-ruby260196508/socket.0 0  }. Err :connection error: desc = 
\"transport: Error while dialing dial unix /tmp/gitaly-ruby260196508/socket.0: 
connect: no such file or directory\". Reconnecting..." system=system

GemNotFound: Your bundle is locked to rouge (3.1.1), but that version
could not be found in any of the sources listed in your Gemfile. If you
haven't changed sources, that means the author of rouge (3.1.1) has
removed it. You'll need to update your bundle to a different version of
rouge (3.1.1) that hasn't been removed in order to install
GemNotFound: Your bundle is locked to rugged (0.27.0), but that version
could not be found in any of the sources listed in your Gemfile. If you
haven't changed sources, that means the author of rugged (0.27.0) has
removed it. You'll need to update your bundle to a different version of
rugged (0.27.0) that hasn't been removed in order to install
GemNotFound: Your bundle is locked to sanitize (4.6.5), but that version
could not be found in any of the sources listed in your Gemfile. If you
haven't changed sources, that means the author of sanitize (4.6.5) has
removed it. You'll need to update your bundle to a different version of
sanitize (4.6.5) that hasn't been removed in order to install


I modified /usr/share/gitaly/ruby/Gemfile and
/usr/share/ruby/Gemfile.lock to specify the version numbers of the
newwer versions of the packages installed from backports, and then this
problem was gone.


-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (600, 'stable'), (550, 'proposed-updates'), (500, 'oldstable'), 
(450, 'oldstable-proposed-updates'), (420, 'testing'), (200, 'unstable'), (160, 
'experimental'), (150, 'oldoldstable'), (140, 'oldoldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitaly depends on:
ii  gitlab-common   10.7.7+dfsg-1~bpo9+1
ii  libc6   2.27-6
ii  pipexec 2.5.5-1
ii  procps  2:3.3.12-3+deb9u1
ii  ruby-activesupport  2:4.2.10-1~bpo9+1
ii  ruby-gitaly 0.99.0+dfsg-2~bpo9+1
ii  ruby-github-linguist5.3.3-1~bpo9+1
ii  ruby-github-markup  1.6.3-1~bpo9+1
ii  ruby-gollum-lib 4.2.7.5-3~bpo9+1
ii  ruby-gollum-rugged-adapter  0.4.4.1-2~bpo9+1
ii  ruby-google-protobuf3.6.0~rc2-2~bpo9+1
ii  ruby-grpc   1.11.0+debian-1~bpo9+1
ii  ruby-licensee   8.9.2-1~bpo9+1
ii  ruby-rugged 0.27.4+ds-1~bpo9+1
ii  ruby-sentry-raven   2.7.2-1~bpo9+1

gitaly recommends no packages.

gitaly suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/gitaly/ruby/Gemfile (from gitaly package)

Bug#902552: linux-image-4.17.0-trunk-amd64-unsigned: enable CONFIG_Z3FOLD

[Frederik Himpe]

Package: src:linux
Version: 4.17.2-1~exp1
Severity: normal

Dear Maintainer,

Please enable CONFIG_Z3FOLD. It makes higher compression possible with zswap.

Thank you,



-- Package-specific info:
** Version:
Linux version 4.17.0-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.17.2-1~exp1 (2018-06-19)

** Command line:
BOOT_IMAGE=/vmlinuz-4.17.0-trunk-amd64 root=/dev/mapper/linux-root ro 
resume=/dev/mapper/linux-swap transparent_hugepage=always pcie_aspm=force 
zswap.enabled=1 zswap.compressor=lz4

** Tainted: E (8192)
 * Unsigned module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: SAMSUNG ELECTRONICS CO., LTD.
product_name: N150/N210/N220 
product_version: Not Applicable
chassis_vendor: SAMSUNG ELECTRONICS CO., LTD.
chassis_version: N/A 
bios_vendor: Phoenix Technologies Ltd.
bios_version: 06JI.M053.20100129.JIP
board_vendor: SAMSUNG ELECTRONICS CO., LTD.
board_name: N150/N210/N220 
board_version: Not Applicable

** Loaded modules:
btrfs(E)
zstd_compress(E)
zstd_decompress(E)
xxhash(E)
xor(E)
raid6_pq(E)
ufs(E)
qnx4(E)
hfsplus(E)
hfs(E)
minix(E)
ntfs(E)
vfat(E)
msdos(E)
fat(E)
jfs(E)
xfs(E)
msr(E)
cpuid(E)
fuse(E)
ip6t_REJECT(E)
nf_reject_ipv6(E)
xt_multiport(E)
ip6table_mangle(E)
ip6table_nat(E)
nf_nat_ipv6(E)
nf_conntrack_ipv6(E)
nf_defrag_ipv6(E)
ip6table_raw(E)
nf_log_ipv6(E)
ip6table_filter(E)
ip6_tables(E)
xt_recent(E)
ipt_REJECT(E)
nf_reject_ipv4(E)
xt_comment(E)
xt_conntrack(E)
xt_hashlimit(E)
xt_addrtype(E)
xt_mark(E)
iptable_mangle(E)
iptable_nat(E)
nf_nat_ipv4(E)
nf_conntrack_ipv4(E)
nf_defrag_ipv4(E)
xt_tcpudp(E)
xt_CT(E)
iptable_raw(E)
xt_NFLOG(E)
nfnetlink_log(E)
nf_log_ipv4(E)
nf_log_common(E)
xt_LOG(E)
nf_conntrack_sane(E)
nf_conntrack_netlink(E)
nfnetlink(E)
nf_nat_tftp(E)
nf_nat_snmp_basic(E)
nf_conntrack_snmp(E)
nf_nat_sip(E)
nf_nat_pptp(E)
nf_nat_proto_gre(E)
nf_nat_irc(E)
nf_nat_h323(E)
nf_nat_ftp(E)
nf_nat_amanda(E)
nf_nat(E)
nf_conntrack_tftp(E)
nf_conntrack_sip(E)
nf_conntrack_pptp(E)
nf_conntrack_proto_gre(E)
nf_conntrack_netbios_ns(E)
nf_conntrack_broadcast(E)
nf_conntrack_irc(E)
nf_conntrack_h323(E)
nf_conntrack_ftp(E)
ts_kmp(E)
nf_conntrack_amanda(E)
nf_conntrack(E)
libcrc32c(E)
iptable_filter(E)
ctr(E)
ccm(E)
uvcvideo(E)
videobuf2_vmalloc(E)
videobuf2_memops(E)
videobuf2_v4l2(E)
videobuf2_common(E)
videodev(E)
media(E)
btusb(E)
btrtl(E)
btbcm(E)
btintel(E)
bluetooth(E)
jitterentropy_rng(E)
drbg(E)
ansi_cprng(E)
ecdh_generic(E)
iTCO_wdt(E)
iTCO_vendor_support(E)
coretemp(E)
pcspkr(E)
joydev(E)
evdev(E)
serio_raw(E)
arc4(E)
i915(E)
ath9k(E)
snd_hda_codec_realtek(E)
ath9k_common(E)
ath9k_hw(E)
snd_hda_codec_generic(E)
ath(E)
sg(E)
snd_hda_intel(E)
snd_hda_codec(E)
snd_hda_core(E)
mac80211(E)
drm_kms_helper(E)
lpc_ich(E)
snd_hwdep(E)
cfg80211(E)
snd_pcm(E)
snd_timer(E)
snd(E)
battery(E)
drm(E)
soundcore(E)
button(E)
ac(E)
i2c_algo_bit(E)
shpchp(E)
acpi_cpufreq(E)
samsung_laptop(E)
rfkill(E)
video(E)
zram(E)
zsmalloc(E)
loop(E)
parport_pc(E)
ppdev(E)
lp(E)
parport(E)
ip_tables(E)
x_tables(E)
autofs4(E)
ext4(E)
crc16(E)
mbcache(E)
jbd2(E)
crc32c_generic(E)
fscrypto(E)
ecb(E)
crypto_simd(E)
cryptd(E)
glue_helper(E)
aes_x86_64(E)
dm_mod(E)
sd_mod(E)
ahci(E)
libahci(E)
psmouse(E)
libata(E)
uhci_hcd(E)
i2c_i801(E)
ehci_pci(E)
ehci_hcd(E)
scsi_mod(E)
usbcore(E)
sky2(E)
usb_common(E)
thermal(E)
lz4(E)
lz4_compress(E)

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010]
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA 
controller])
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012]
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller [8086:27d8] (rev 02)
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- 

Bug#901379: gitlab: postinst script should not call psql if database is not managed by dbconfig-common

[Frederik Himpe]

Package: gitlab
Version: 10.7.5+dfsg-2~bpo9+1
Severity: normal

Dear Maintainer,

the gitlab.postinst script fails to enable the pg_trgm extension if
there is no locally running postgresql database:

Setting up gitlab (10.7.5+dfsg-2~bpo9+1) ...
Creating/updating gitlab user account...
Making gitlab owner of /var/lib/gitlab...
Creating runtime directories for gitlab...
Updating file permissions...
Configuring hostname and email...
Configuring nginx with HTTPS...
Configuring gitlab with HTTPS...
Updating gitlab_url in gitlab-shell configuration...
Registering /usr/lib/tmpfiles.d/gitlab.conf via ucf
/etc/systemd/system/gitlab-mailroom.service.d/override.conf already
exist
/etc/systemd/system/gitlab-unicorn.service.d/override.conf already exist
/etc/systemd/system/gitlab-sidekiq.service.d/override.conf already exist
/etc/systemd/system/gitlab-workhorse.service.d/override.conf already
exist
Registering /etc/gitlab-shell/config.yml via ucf
Registering /etc/gitlab/gitlab.yml via ucf
Registering /etc/gitlab/gitlab-debian.conf via ucf
dbconfig-common: writing config to /etc/dbconfig-common/gitlab.conf
dbconfig-common: flushing administrative password
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.5432"?
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned
 error exit status 2

I chose to not manage the postgresql database by dbconfig because I am using
an externally running database. In that case this command should not be run.


-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (600, 'stable'), (550, 'proposed-updates'), (500, 'oldstable'), 
(450, 'oldstable-proposed-updates'), (420, 'testing'), (200, 'unstable'), (160, 
'experimental'), (150, 'oldoldstable'), (140, 'oldoldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  adduser3.115
ii  apache2 [httpd]2.4.25-3+deb9u4
ii  asciidoctor1.5.6.2-2~bpo9+1
ii  bc 1.06.95-9+b3
ii  bundler1.13.6-2
ii  dbconfig-pgsql 2.0.9~bpo9+1
ii  debconf [debconf-2.0]  1.5.61
ii  git1:2.17.1-1~bpo9+1
ii  gitlab-shell   7.1.2+dfsg-2~bpo9+1
ii  gitlab-workhorse   4.2.1+debian-2~bpo9+1
ii  init-system-helpers1.48
ii  lsb-base   9.20161125
ii  nodejs 8.11.1~dfsg-2~bpo9+1
ii  npm1.4.21+ds-2~bpo9+1
ii  openssh-client 1:7.4p1-10+deb9u3
ii  postfix [mail-transport-agent] 3.1.8-0+deb9u1
ii  postgresql-client  9.6+181+deb9u1
ii  postgresql-client-9.6 [postgresql-client]  9.6.7-0+deb9u1
ii  postgresql-contrib 9.6+181+deb9u1
ii  rake   12.3.1-1~bpo9+1
ii  redis-server   5:4.0.9-2~bpo9+1
ii  ruby   1:2.3.3
ii  ruby-ace-rails-ap  4.1.1-1
ii  ruby-acts-as-taggable-on   5.0.0-2~bpo9+1
ii  ruby-addressable   2.5.2-1~bpo9+1
ii  ruby-akismet   2.0.0-1
ii  ruby-allocations   1.0.3-1+b2
ii  ruby-arel  6.0.4-1~bpo9+1
ii  ruby-asana 0.6.0-1~bpo9+1
ii  ruby-asciidoctor-plantuml  0.0.8-1~bpo9+1
ii  ruby-asset-sync2.2.0-2~bpo9+1
ii  ruby-attr-encrypted3.1.0-1~bpo9+1
ii  ruby-babosa1.0.2-2
ii  ruby-base320.3.2-3
ii  ruby-batch-loader  1.2.1-1~bpo9+1
ii  ruby-bcrypt-pbkdf  1.0.0-1~bpo9+1
ii  ruby-bootstrap-form2.7.0-1~bpo9+1
ii  ruby-bootstrap-sass3.3.5.1-5
ii  ruby-browser   2.2.0-2
ii  ruby-carrierwave   1.2.2-1~bpo9+1
ii  ruby-charlock-holmes   0.7.5-1~bpo9+1
ii  ruby-chronic   0.10.2-3
ii  ruby-chronic-duration  0.10.6-1
ii  ruby-commonmarker  0.17.9-1~bpo9+1
ii  ruby-connection-pool 

Bug#901338: gitlab: dependency on postgresql-contrib pulls in postgresql server

[Frederik Himpe]

Package: gitlab
Version: 10.7.5+dfsg-2~bpo9+1
Severity: normal

Dear Maintainer,

gitlab depends on postgresql-client and postgresql-contrib. The latter
pulls in the postgresql server package, and because postgresql itself
already depends on postgresql-client, the explicit dependency on
postgresql-client in gitlab is actually useless.

Personally I already have a postgresql server running on another host,
which I want to use for gitlab, so I would prefer a suggest or recommend
dependency instead of a hard dependency.

-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (600, 'stable'), (550, 'proposed-updates'), (500, 'oldstable'), 
(450, 'oldstable-proposed-updates'), (420, 'testing'), (200, 'unstable'), (160, 
'experimental'), (150, 'oldoldstable'), (140, 'oldoldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  adduser3.115
ii  apache2 [httpd]2.4.25-3+deb9u4
ii  asciidoctor1.5.6.2-2~bpo9+1
ii  bc 1.06.95-9+b3
ii  bundler1.13.6-2
ii  dbconfig-pgsql 2.0.9~bpo9+1
ii  debconf [debconf-2.0]  1.5.61
ii  git1:2.17.1-1~bpo9+1
ii  gitlab-shell   7.1.2+dfsg-2~bpo9+1
ii  gitlab-workhorse   4.2.1+debian-2~bpo9+1
ii  init-system-helpers1.48
ii  lsb-base   9.20161125
ii  nodejs 8.11.1~dfsg-2~bpo9+1
ii  npm1.4.21+ds-2~bpo9+1
ii  openssh-client 1:7.4p1-10+deb9u3
ii  postfix [mail-transport-agent] 3.1.8-0+deb9u1
ii  postgresql-client  9.6+181+deb9u1
ii  postgresql-client-9.6 [postgresql-client]  9.6.7-0+deb9u1
ii  postgresql-contrib 9.6+181+deb9u1
ii  rake   12.3.1-1~bpo9+1
ii  redis-server   5:4.0.9-2~bpo9+1
ii  ruby   1:2.3.3
ii  ruby-ace-rails-ap  4.1.1-1
ii  ruby-acts-as-taggable-on   5.0.0-2~bpo9+1
ii  ruby-addressable   2.5.2-1~bpo9+1
ii  ruby-akismet   2.0.0-1
ii  ruby-allocations   1.0.3-1+b2
ii  ruby-arel  6.0.4-1~bpo9+1
ii  ruby-asana 0.6.0-1~bpo9+1
ii  ruby-asciidoctor-plantuml  0.0.8-1~bpo9+1
ii  ruby-asset-sync2.2.0-2~bpo9+1
ii  ruby-attr-encrypted3.1.0-1~bpo9+1
ii  ruby-babosa1.0.2-2
ii  ruby-base320.3.2-3
ii  ruby-batch-loader  1.2.1-1~bpo9+1
ii  ruby-bcrypt-pbkdf  1.0.0-1~bpo9+1
ii  ruby-bootstrap-form2.7.0-1~bpo9+1
ii  ruby-bootstrap-sass3.3.5.1-5
ii  ruby-browser   2.2.0-2
ii  ruby-carrierwave   1.2.2-1~bpo9+1
ii  ruby-charlock-holmes   0.7.5-1~bpo9+1
ii  ruby-chronic   0.10.2-3
ii  ruby-chronic-duration  0.10.6-1
ii  ruby-commonmarker  0.17.9-1~bpo9+1
ii  ruby-connection-pool   2.2.0-1
ii  ruby-creole0.5.0-2
ii  ruby-d3-rails  3.5.6+dfsg-1
ii  ruby-default-value-for 3.0.1-1
ii  ruby-devise4.4.3-1~bpo9+1
ii  ruby-devise-two-factor 3.0.0-2
ii  ruby-diffy 3.1.0-1~bpo9+1
ii  ruby-doorkeeper4.3.1-1~bpo9+1
ii  ruby-doorkeeper-openid-connect 1.3.0-1~bpo9+1
ii  ruby-dropzonejs-rails  0.7.1-1
ii  ruby-email-reply-trimmer   0.1.6-1~bpo9+1
ii  ruby-escape-utils  1.2.1-1~bpo9+1
ii  ruby-excon 0.60.0-1~bpo9+1
ii  ruby-faraday   0.13.1-2~bpo9+1
ii  ruby-fast-blank1.0.0-1~bpo9+1
ii  ruby-flipper   0.13.0-3~bpo9+1
pn  ruby-flipper-active-record 
pn  ruby-flipper-active-support-cache-store
ii  ruby-fog-aliyun0.2.0-1~bpo9+1
ii  ruby-fog-aws   2.0.1-1~bpo9+1
ii  ruby-fog-core 

Bug#901308: accountsservice: Version 0.6.49 available

[Frederik Himpe]

Package: accountsservice
Version: 0.6.45-1
Severity: wishlist

Dear Maintainer,

accountsservice 0.6.49 is available, fixing some memory leaks and improving
performance in specific situations. It would be nice to have this in Debian.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (300, 
'testing'), (205, 'stable'), (200, 'unstable'), (150, 'oldstable'), (102, 
'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages accountsservice depends on:
ii  dbus   1.12.8-3
ii  init-system-helpers1.51
ii  libaccountsservice00.6.45-1
ii  libc6  2.27-3
ii  libglib2.0-0   2.56.1-2
ii  libpolkit-gobject-1-0  0.105-20

accountsservice recommends no packages.

Versions of packages accountsservice suggests:
ii  gnome-control-center  1:3.28.1-1

-- no debconf information

Bug#898446: Please reconsider enabling the user namespaces by default

[Frederik Himpe]

On Sun, 13 May 2018 00:33:02 +0100 Ben Hutchings <b...@decadent.org.uk>
wrote:
> Control: tag -1 moreinfo
> 
> On Fri, 2018-05-11 at 20:44 +0200, Laurent Bigonville wrote:
> > Source: linux
> > Version: 4.16.5-1
> > Severity: normal
> > 
> > Hi,
> > 
> > Firefox (and probably other applications) are using user namespaces these
> > days to enhance the security.
> 
> Can you provide some information about this?

There is some info here:
https://www.morbo.org/2018/05/linux-sandboxing-improvements-in_10.html


Regards,

-- 
Frederik Himpe <frede...@frehi.be>

Bug#898368: openvas-manager-common: README.Debian mentions commands not existing in sid

[Frederik Himpe]

Package: openvas-manager-common
Version: 7.0.2-4
Severity: normal

Dear Maintainer,

The README.Debian says to execute these commands:
$ sudo openvas-nvt-sync
$ sudo openvas-scapdata-sync
$ sudo openvas-certdata-sync

However, they don't seem to be present any more in Debian Sid.

-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (600, 'stable'), (550, 'proposed-updates'), (500, 'oldstable'), 
(450, 'oldstable-proposed-updates'), (420, 'testing'), (200, 'unstable'), (160, 
'experimental'), (150, 'oldoldstable'), (140, 'oldoldstable-proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openvas-manager-common depends on:
ii  gnutls-bin  3.5.18-1

Versions of packages openvas-manager-common recommends:
ii  openvas-manager  7.0.2-4

Versions of packages openvas-manager-common suggests:
ii  gnupg 2.1.18-8~deb9u1
ii  python2.7.13-2
ii  wget  1.18-5+deb9u2
pn  xsltproc  

-- no debconf information

Bug#886883: RFP: clazy -- Qt oriented code checker based on clang framework

[Frederik Schwarzer]

Package: wnpp
Severity: wishlist

* Package name: clazy
  Version : 1.3
  Upstream Author : Sergio Martins 
* URL : https://github.com/KDE/clazy/
* License : (LGPLv2)
  Programming Lang: (C++)
  Description : Qt oriented code checker based on clang framework

Bug#884638: linux-image-4.9.0-4-amd64: Display cuts to black and back w/ intel gpu/fifo underrun

[frederik]

I can confirm this. For my Lenovo ThinkPad T450s with 2 external 
monitors, it is exactly the same. Drove me nuts for the better part of a 
day until I realized it was due to 4.9.0-4. As such I'm also back to 
running 4.9.0-3 as a workaround.


In my case I would only* get the flickering (ie. the screen/monitor 
goes blank for a sec or two) in the following scenario:


1) move mouse cursor inside of my GNOME Terminal window
2) use the keyboard to type something (anything)

*With the mouse cursor hovering outside of my term window, I was safe 
so to say. Having said this, occasionally a monitor would also flicker 
when moving the mouse cursor from one external monitor to another.


B/R,
Frederik Dannemare

Bug#874054: [Development] Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Frederik Gladhorn]

I'm a bit split here, let's try to find some middle ground :)

I do think that we should always run with accessibility enabled and we don't 
do that for a reason.
One thing to fix for linux accessibility is listening to the change signal on 
for a11y being enabled or not. If I recall correctly listening to property 
changes on dbus is not implemented in Qt since it's impossible to know if 
there are any listeners to these change signals, Thiago knows the details I 
think.

The next thing is to make sure we don't actually send the keyboard and mouse 
events when not needed (pure insanity anyway, we should have a sound 
approach...). For the time being sending all of these events over dbus is the 
only way to make Orca happy and thus the only way to make applications behave 
somewhat acceptable for blind users. Thinking about the code gives me 
nightmares though and I'd support anyone looking at it and making sure we 
don't overdo the sending of events.

And then Allan is right, by setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON you ask 
for it. All the stuff unconditionally. Please don't, why do you need it in the 
first place?
Maybe it's time to sit down and create a somewhat defined way when it should be 
enabled? Right now Qt is trying to emulate Gnome's way, except since we don't 
listen to the change signal, we never dynamically enable/disable a11y. The 
code is there, it's just actually reacting to the notification that's missing.

Cheers,
Frederik



On søndag 3. september 2017 19.13.38 CEST Allan Sandfeld Jensen wrote:
> On Sonntag, 3. September 2017 18:15:15 CEST Samuel Thibault wrote:
> > On the long run, it really should.  Just hiding issues is not the way
> > forward :)
> > 
> > Also, note that if the performance is so bad, it means something *needs*
> > to be fixed, otherwise blind users will get the bad performance, and
> > nobody will be there to fix it, because nobody notices it except blind
> > users, who are left with little hope to fix it by themselves.
> 
> It is not a issue or a bug. The performance impact comes from sending
> everything the mouse hovers over to the accessibility framework (for
> instance to be spoken aloud), when there is not any accessibility tools
> running.
> 
> You are deliberately crippling Qt to always send dbus events even when no
> one is listening.
> 
> Note the performance impact is the same in all applications regardless of
> framework. Running accessibility tools has a substantional performance cost
> on mouse movements, but a mouse rendered or text scrolling at 60 fps is
> completely pointless to blind people, but rather important to everybody
> else.
> 
> 'Allan
> ___
> Development mailing list
> developm...@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

Bug#860879: closed by Holger Levsen <hol...@debian.org> (Bug#860879: fixed in munin 2.999.6-2)

[Frederik Himpe]

Ouch, apparently I made a typo in the title of my bug report: the
package name is libio-string-perl, not libo-string-perl

This leads to this error when upgrading:

 munin : Depends: libo-string-perl but it is not installable

My apologies for the confusion...

-- 
Frederik Himpe <fhi...@ai.vub.ac.be>
Vrije Universiteit Brussel

Bug#860899: [Packaging] Bug#860899: munin-limits: Global symbol "$onfield" requires explicit package name

[Frederik Himpe]

Holger Levsen <hol...@layer-acht.org> schreef op 21 april 2017 16:04:56 CEST:
>On Fri, Apr 21, 2017 at 03:53:54PM +0200, Frederik Himpe wrote:
>> 
>> This error is also mentioned here:
>>
>https://github.com/munin-monitoring/munin/issues/794#issuecomment-295878938
>
>to be clear, you're only seeing the "2." from that github issue, but
>not "1.",
>correct?!

That's correct!
-- 
Frederik Himpe
fhi...@ai.vub.ac.be

Bug#860899: munin-limits: Global symbol "$onfield" requires explicit package name

[Frederik Himpe]

Package: munin
Version: 2.999.6-1
Severity: normal

munin-limits, which is called by the munin cron script, fails with these
errors:

Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 442.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 442.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 443.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 444.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 445.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 448.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 449.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 452.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 458.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 459.
Global symbol "$onfield" requires explicit package name (did you forget
to declare "my $onfield"?) at /usr/share/perl5/Munin/Master/LimitsOld.pm
line 556.
Compilation failed in require at /usr/bin/munin-limits line 31.
BEGIN failed--compilation aborted at /usr/bin/munin-limits line 31.

This error is also mentioned here:
https://github.com/munin-monitoring/munin/issues/794#issuecomment-295878938

-- Package-specific info:
===
 Munin support information
==

This is support information for Munin version 2.999.6


Munin Master


Configuration items from /etc/munin/munin.conf

Directories
---

dbdir  /var/lib/munin
logdir /var/log/munin
rundir /var/run/munin
tmpldir/etc/munin/templates

Processes
-

fork   1
max_cgi_graph_jobs (unset)
max_graph_jobs (unset)
max_processes  16

TLS
---

tlsdisabled
tls_ca_certificate /etc/munin/cacert.pem
tls_certificate/etc/munin/munin.pem
tls_match  (unset)
tls_private_key/etc/munin/munin.pem
tls_verify_certificate (unset)
tls_verify_depth   5

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (600, 'testing'), (550, 'unstable'), (500, 'stable'), (450, 
'proposed-updates'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages munin depends on:
ii  adduser  3.115
ii  cron [cron-daemon]   3.0pl1-128+b1
ii  fonts-dejavu-core2.37-1
ii  init-system-helpers  1.47
ii  libdbd-sqlite3-perl  1.54-1
ii  libfile-copy-recursive-perl  0.38-1
ii  libhtml-template-perl2.95-2
ii  libhtml-template-pro-perl0.9510-1+b4
ii  libhttp-server-simple-perl   0.51-1
ii  libio-socket-inet6-perl  2.72-2
ii  liblist-moreutils-perl   0.416-1+b1
ii  libmunin-master-perl 2.999.6-1
ii  librrds-perl 1.6.0-1+b2
ii  liburi-perl  1.71-1
ii  libxml-dumper-perl   0.81-1.2
ii  lsb-base 9.20161125
ii  munin-common 2.999.6-1
pn  perl:any 
ii  rrdcached1.6.0-1+b2
ii  rrdtool  1.6.0-1+b2

Versions of packages munin recommends:
pn  munin-doc   
pn  munin-node  

Versions of packages munin suggests:
ii  elinks [www-browser]  0.12~pre6-12

Versions of packages munin-common depends on:
pn  perl:any  

-- no debconf information

Bug#860879: [Packaging] Bug#860879: munin-httpd needs libo-string-perl and libhttp-server-simple-cgi-prefork-perl

[Frederik Himpe]

On Fri, 2017-04-21 at 11:05 +, Holger Levsen wrote:
> control: severity -1 serious
> 
> On Fri, Apr 21, 2017 at 11:19:28AM +0200, Frederik Himpe wrote:
> > Munin from experimtal fails to start if
> > libhttp-server-simple-cgi-prefork-perl and libio-string-perl is not
> > installed.
> 
The Munin cron job is also missing libparallel-forkmanager-perl as a
dependency:

Can't locate Parallel/ForkManager.pm in @INC (you may need to install the 
Parallel::ForkManager module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Munin/Master/Update.pm line 154.
BEGIN failed--compilation aborted at /usr/share/perl5/Munin/Master/Update.pm 
line 154.
Compilation failed in require at /usr/bin/munin-update line 12.
BEGIN failed--compilation aborted at /usr/bin/munin-update line 12.

After installing that package, the cron job still fails with a
compilation error, but I'll open a separate bug report for that if I
can find out what's wrong exactly.

-- 
Frederik Himpe <fhi...@ai.vub.ac.be>
Vrije Universiteit Brussel

Bug#860879: munin-httpd needs libo-string-perl and libhttp-server-simple-cgi-prefork-perl

[Frederik Himpe]

Package: munin
Version: 2.999.6-1
Severity: normal

Munin from experimtal fails to start if
libhttp-server-simple-cgi-prefork-perl and libio-string-perl is not
installed.

These are the errors:
Apr 21 10:36:30 artipc10 munin-httpd[6502]: Can't locate
HTTP/Server/Simple/CGI/PreFork.pm in @INC (you may need to install the
HTTP::Server::Simple::CGI::PreFork module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at
/usr/bin/munin-httpd line 35.

Apr 21 11:13:46 artipc10 munin-httpd[1478]: Can't locate IO/String.pm in
@INC (you may need to install the IO::String module) (@INC contains:
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1
/usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24
/usr/share/perl/5.24 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base) at
/usr/share/perl5/Munin/Master/Graph.pm line 663,  line 16.


-- Package-specific info:
===
 Munin support information
==

This is support information for Munin version 2.999.6


Munin Master


Configuration items from /etc/munin/munin.conf

Directories
---

dbdir  /var/lib/munin
logdir /var/log/munin
rundir /var/run/munin
tmpldir/etc/munin/templates

Processes
-

fork   1
max_cgi_graph_jobs (unset)
max_graph_jobs (unset)
max_processes  16

TLS
---

tlsdisabled
tls_ca_certificate /etc/munin/cacert.pem
tls_certificate/etc/munin/munin.pem
tls_match  (unset)
tls_private_key/etc/munin/munin.pem
tls_verify_certificate (unset)
tls_verify_depth   5

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (600, 'testing'), (550, 'unstable'), (500, 'stable'), (450, 
'proposed-updates'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages munin depends on:
ii  adduser  3.115
ii  cron [cron-daemon]   3.0pl1-128+b1
ii  fonts-dejavu-core2.37-1
ii  init-system-helpers  1.47
ii  libdbd-sqlite3-perl  1.54-1
ii  libfile-copy-recursive-perl  0.38-1
ii  libhtml-template-perl2.95-2
ii  libhtml-template-pro-perl0.9510-1+b4
ii  libhttp-server-simple-perl   0.51-1
ii  libio-socket-inet6-perl  2.72-2
ii  liblist-moreutils-perl   0.416-1+b1
ii  libmunin-master-perl 2.999.6-1
ii  librrds-perl 1.6.0-1+b2
ii  liburi-perl  1.71-1
ii  libxml-dumper-perl   0.81-1.2
ii  lsb-base 9.20161125
ii  munin-common 2.999.6-1
pn  perl:any 
ii  rrdcached1.6.0-1+b2
ii  rrdtool  1.6.0-1+b2

Versions of packages munin recommends:
pn  munin-doc   
pn  munin-node  

Versions of packages munin suggests:
ii  elinks [www-browser]  0.12~pre6-12

Versions of packages munin-common depends on:
pn  perl:any  

-- no debconf information

Bug#860261: tt-rss does not work without php-gettext package

[Frederik Himpe]

Package: tt-rss
Version: 17.1+git20170410+dfsg-1
Severity: normal

To fix bug #837508, the php-gettext dependency was removed in tt-rss.
However, without this package being installed, tt-rss.service fails to
start:

apr 13 18:59:10 artipc10 systemd[1]: Started Update the Tiny Tiny RSS 
subscribed syndication feeds.
apr 13 18:59:10 artipc10 update.php[4067]: PHP Warning: 
require_once(lib/gettext/gettext.inc): failed to open stream: No such file or 
directory in /usr/share/tt-rss/www/include/functions.php on line 102
apr 13 18:59:10 artipc10 update.php[4067]: PHP Fatal error: require_once(): 
Failed opening required 'lib/gettext/gettext.inc' 
(include_path='/usr/share/tt-rss/www/include:.:/usr/share/php') in 
/usr/share/tt-rss/www/include/functions.php 

Installing php-gettext, fixes these errors as it contains the files
tt-rss is looking for:

$ dpkg -L php-gettext
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/php-gettext
/usr/share/doc/php-gettext/changelog.Debian.gz
/usr/share/doc/php-gettext/copyright
/usr/share/php
/usr/share/php/php-gettext
/usr/share/php/php-gettext/gettext.inc
/usr/share/php/php-gettext/gettext.php
/usr/share/php/php-gettext/streams.php

php-php-gettext instead has this file in another location:
$ dpkg -L php-php-gettext | grep gettext.inc
/usr/share/php/php-php-gettext/gettext.inc

So maybe tt-rss needs to be patched to look for the new name?

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (600, 'testing'), (550, 'unstable'), (500, 'stable'), (450, 
'proposed-updates'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tt-rss depends on:
ii  dbconfig-common 2.0.8
ii  dbconfig-mysql  2.0.8
ii  debconf [debconf-2.0]   1.5.60
ii  init-system-helpers 1.47
ii  libjs-dojo-core 1.11.0+dfsg-1
ii  libjs-dojo-dijit1.11.0+dfsg-1
ii  libjs-scriptaculous 1.9.0-2
ii  libphp-phpmailer5.2.14+dfsg-2.3
ii  lsb-base9.20161125
ii  php 1:7.0+49
ii  php-mysql   1:7.0+49
ii  php-pgsql   1:7.0+49
ii  php-php-gettext 1.0.12-0.1
ii  php-xml 1:7.0+49
ii  php7.0 [php]7.0.16-3
ii  php7.0-cli [php-cli]7.0.16-3
ii  php7.0-json [php-json]  7.0.16-3
ii  php7.0-mbstring [php-mbstring]  7.0.16-3
ii  php7.0-pgsql [php-pgsql]7.0.16-3
ii  php7.0-xml [php-xml]7.0.16-3
ii  phpqrcode   1.1.4-2

Versions of packages tt-rss recommends:
ii  apache2 [httpd] 2.4.25-3
ii  ca-certificates 20161130
ii  php-curl1:7.0+49
ii  php-gd  1:7.0+49
ii  php-mcrypt  1:7.0+49
ii  php7.0-curl [php-curl]  7.0.16-3
ii  php7.0-gd [php-gd]  7.0.16-3
ii  php7.0-mcrypt [php-mcrypt]  7.0.16-3

Versions of packages tt-rss suggests:
pn  php-apc   
pn  sphinxsearch  

-- Configuration Files:
/etc/default/tt-rss changed [not included]
/etc/tt-rss/apache.conf changed [not included]
/etc/tt-rss/config.php changed [not included]

-- debconf information excluded

Bug#856979: asterisk-opus: No documentation on how to use this

[Frederik Himpe]

Package: asterisk-opus
Version: 13.7+20161113-3
Severity: normal

I had expected to find some documentation in /usr/share/doc/asterisk-opus 
explaining me what I should add to sip.conf to allow usage of the opus codec.

-- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (500, 'stable'), (450, 'proposed-updates'), (300, 'testing'), 
(200, 'unstable'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-042stab120.11 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages asterisk-opus depends on:
ii  asterisk [asterisk-fa819827cbff2ea35341af5458859233]  1:13.14.0~dfsg-1
ii  libc6 2.24-9
ii  libopus0  1.2~alpha2-1
ii  libopusfile0  0.8-1+b1

asterisk-opus recommends no packages.

asterisk-opus suggests no packages.

-- debconf information excluded

Bug#855905: slurmd: Restarting slurmd kills all running jobs

[Frederik Himpe]

Package: slurmd
Version: 16.05.7-1
Severity: important

Dear Maintainer,

When the slurmd is updated and the service is stopped and started, all
running jobs are killed. This is not supposed to happen.

I found this bug:
https://bugs.schedmd.com/show_bug.cgi?id=2095
which leads to this commit fixing this problem when slurmd is running
via systemd:
https://github.com/SchedMD/slurm/commit/508f866ea10e4c359d62d443279198082d587107

Debian's slurmd.service is indeed missing the option
KillMode=process

Maybe Debian should use the upstream slurmd.service.in instead of
maintaining its own slurmd.service?

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (600, 'testing'), (550, 'unstable'), (500, 'stable'), (450, 
'proposed-updates'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages slurmd depends on:
ii  adduser  3.115
ii  init-system-helpers  1.46
ii  libc62.24-8
ii  libhwloc51.11.5-1
ii  libpam0g 1.1.8-3.4
ii  lsb-base 9.20161125
ii  munge0.5.12-1
ii  openssl  1.1.0c-2
ii  openssl-blacklist0.5-3
ii  slurm-wlm-basic-plugins  16.05.7-1
ii  ucf  3.0036
ii  zlib1g   1:1.2.8.dfsg-4

slurmd recommends no packages.

slurmd suggests no packages.

-- no debconf information

Bug#847342: slurm-wlm-torque: qstat does not work until libswitch-perl is installed

[Frederik Himpe]

Package: slurm-wlm-torque
Version: 16.05.6-1
Severity: normal

# qstat
Can't locate Switch.pm in @INC (you may need to install the Switch
module) (@INC contains: /usr/lib/x86_64-linux-gnu/perl/5.24.1 /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at
/usr/bin/qstat line 53,  line 620.
BEGIN failed--compilation aborted at /usr/bin/qstat line 53,  line
620.

I needed to install libswitch-perl to make qstat work.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (600, 'testing'), (550, 'unstable'), (500, 'stable'), (450, 
'proposed-updates'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages slurm-wlm-torque depends on:
ii  libslurm-perl16.05.6-1
ii  libslurmdb-perl  16.05.6-1
pn  perl:any 
ii  slurm-client 16.05.6-1

slurm-wlm-torque recommends no packages.

slurm-wlm-torque suggests no packages.

-- no debconf information

Bug#838462: [Pkg-xfce-devel] Bug#838462: light-locker: X crashes when attaching/removing displays while locked

[Frederik Möllers]

On 23/09/16 09:17, Yves-Alexis Perez wrote:
> If you have an intel card, try to use the modesetting driver instead
> of the xserver-xorg-video-intel one (just removing the package is
> enough, I think).

I tried that, but the error persists. Checking the X log gave some new
information, though:

[   316.532] (II) AIGLX: Suspending AIGLX clients for VT switch
[   331.694] (II) config/udev: Adding input device Logitech USB Laser Mouse 
(/dev/input/mouse2)
[   331.695] (II) No input driver specified, ignoring this device.
[   331.695] (II) This device may have been added with another device file.
[   331.727] (II) config/udev: Adding input device Logitech USB Keyboard 
(/dev/input/event19)
[   331.727] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard 
catchall"
[   331.727] (**) Logitech USB Keyboard: Applying InputClass "libinput keyboard 
catchall"
[   331.727] (II) Using input driver 'libinput' for 'Logitech USB Keyboard'
[   331.727] (**) Logitech USB Keyboard: always reports core events
[   331.727] (**) Option "Device" "/dev/input/event19"
[   331.727] (**) Option "_source" "server/udev"
[   331.728] (II) input device 'Logitech USB Keyboard', /dev/input/event19 is 
tagged by udev as: Keyboard
[   331.728] (II) input device 'Logitech USB Keyboard', /dev/input/event19 is a 
keyboard
[   331.748] (II) libinput: Logitech USB Keyboard: needs a virtual subdevice
[   331.748] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb2/2-3/2-3.4/2-3.4.2/2-3.4.2:1.1/0003:046D:C328.0003/input/input20/event19"
[   331.748] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" 
(type: MOUSE, id 14)
[   331.748] (**) Option "AccelerationScheme" "none"
[   331.749] (**) Logitech USB Keyboard: (accel) selected scheme none/0
[   331.749] (**) Logitech USB Keyboard: (accel) acceleration factor: 2.000
[   331.749] (**) Logitech USB Keyboard: (accel) acceleration threshold: 4
[   331.749] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard 
catchall"
[   331.749] (**) Logitech USB Keyboard: Applying InputClass "libinput keyboard 
catchall"
[   331.749] (II) Using input driver 'libinput' for 'Logitech USB Keyboard'
[   331.749] (**) Logitech USB Keyboard: always reports core events
[   331.749] (**) Option "Device" "/dev/input/event19"
[   331.749] (**) Option "_source" "_driver/libinput"
[   331.749] (II) libinput: Logitech USB Keyboard: is a virtual subdevice
[   331.749] (EE)
[   331.749] (EE) Backtrace:
[   331.749] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x562dd5a8401a]
[   331.749] (EE) 1: /usr/lib/xorg/Xorg (0x562dd58ca000+0x1be389) 
[0x562dd5a88389]
[   331.749] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f874b5a5000+0x33040) 
[0x7f874b5d8040]
[   331.749] (EE) 3: /usr/lib/x86_64-linux-gnu/libinput.so.10 
(libinput_device_config_tap_get_finger_count+0x0) [0x7f8747122440]
[   331.749] (EE) 4: /usr/lib/xorg/modules/input/libinput_drv.so 
(0x7f874737+0x83ae) [0x7f87473783ae]
[   331.749] (EE) 5: /usr/lib/xorg/Xorg (0x562dd58ca000+0xa4202) 
[0x562dd596e202]
[   331.749] (EE) 6: /usr/lib/xorg/modules/input/libinput_drv.so 
(0x7f874737+0x67af) [0x7f87473767af]
[   331.749] (EE) 7: /usr/lib/xorg/Xorg (ProcessWorkQueue+0x21) [0x562dd5922ee1]
[   331.749] (EE) 8: /usr/lib/xorg/Xorg (WaitForSomething+0xac) [0x562dd5a80c3c]
[   331.749] (EE) 9: /usr/lib/xorg/Xorg (0x562dd58ca000+0x53e9e) 
[0x562dd591de9e]
[   331.749] (EE) 10: /usr/lib/xorg/Xorg (0x562dd58ca000+0x58073) 
[0x562dd5922073]
[   331.749] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) 
[0x7f874b5c52b1]
[   331.749] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2a) [0x562dd590bfea]
[   331.749] (EE)
[   331.749] (EE) Segmentation fault at address 0x40
[   331.749] (EE)
Fatal server error:
[   331.749] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   331.749] (EE)
[   331.749] (EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[   331.749] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
[   331.749] (EE)
[   331.749] (EE) Server terminated with error (1). Closing log file.

It seems the error is related to the X input library rather than any
video drivers. I have confirmed that the X server does not crash if I
plug my mouse and keyboard out of my dock.
Sorry for the wrong assignment. Could you reassign the bug to the
xserver-xorg-input-libinput package? Or should I just file a new report
there?

Best,
Frederik

Bug#844414: puppet-agent: Remounts file systems for no reason at every run

[Frederik Himpe]

This bug is fixed upstream with this patch:

https://github.com/puppetlabs/puppet/commit/ac6709f2e76cbb68639bb626b6481b743cd9b56b.patch

Can it be applied to the Debian package?

Thanks,
-- 
Frederik Himpe <fhi...@vub.ac.be>
Vrije Universiteit Brussel

Bug#844414: puppet-agent: Remounts file systems for no reason at every run

[Frederik Himpe]

Package: puppet-agent
Version: 4.8.0-1
Severity: normal

Since I upgraded to Puppet 4.8, every puppet agent run, all mounts defined in 
my puppet configuration, are remounted, even though they are already mounted 
correctly with the right options. This is causing a dependency cascade, making 
different services depending on these mount definitions,restarting for no 
reason.

This is an upstream regression being tracked in 
https://tickets.puppetlabs.com/browse/PUP-6861


-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (500, 'stable'), (450, 'proposed-updates'), (300, 'testing'), 
(200, 'unstable'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/10 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages puppet-agent depends on:
ii  init-system-helpers  1.22
ii  lsb-base 4.1+Debian13+nmu1
ii  puppet   4.8.0-1

puppet-agent recommends no packages.

puppet-agent suggests no packages.

-- no debconf information

Bug#843780: fai-doc: script FAIBASE/10-misc should use symlink for /etc/localtime

[Frederik Himpe]

Package: fai-doc
Version: 5.2
Severity: normal

On Stretch, the FAIBASE/10-misc script fails to copy the correct
zoneinfo file to /etc/localtime, because /etc/localtime is a symlink.

I had to replace
cp -f /usr/share/zoneinfo/${TIMEZONE} $target/etc/localtime
by
ln -sf /usr/share/zoneinfo/${TIMEZONE} $target/etc/localtime

to have the time zone set correctly on the target machine.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (600, 'testing'), (550, 'unstable'), (500, 'stable'), (450, 
'proposed-updates'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#843256: systemd: man systemd-resolved refers to /usr/lib/systemd/resolv.conf instead of /lib/systemd/resolv.conf

[Frederik Himpe]

Package: systemd
Version: 231-9
Severity: normal

man systemd-resolved mentions the file /usr/lib/systemd/resolv.conf , however
this file is installed as /lib/systemd/resolv.conf.



-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (300, 
'testing'), (250, 'stable'), (200, 'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.10.95-5
ii  libaudit1   1:2.6.7-1
ii  libblkid1   2.28.2-1
ii  libc6   2.24-5
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.2-5
ii  libgcrypt20 1.7.3-2
ii  libgpg-error0   1.24-1
ii  libidn111.33-1
ii  libip4tc0   1.6.0-4
ii  libkmod222-1.1
ii  liblzma55.2.2-1.2
ii  libmount1   2.28.2-1
ii  libpam0g1.1.8-3.3
ii  libseccomp2 2.3.1-2
ii  libselinux1 2.6-1
ii  libsystemd0 231-9
ii  mount   2.28.2-1
ii  util-linux  2.28.2-1

Versions of packages systemd recommends:
ii  dbus1.10.12-1
ii  libpam-systemd  231-9

Versions of packages systemd suggests:
ii  policykit-10.105-17
pn  systemd-container  
ii  systemd-ui 3-4

Versions of packages systemd is related to:
ii  udev  231-9

-- no debconf information

Bug#841013: upstream bug report

[Frederik Himpe]

On Tue, 2016-10-25 at 21:46 +0200, Frederik Himpe wrote:
> I'm experiencing the same problem. Someone also reported this
> upstream 
> in this bug report: https://fedorahosted.org/sssd/ticket/3189

Actually this is the same bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840617

-- 
Frederik Himpe <frede...@frehi.be>

Bug#841013: upstream bug report

[Frederik Himpe]

I'm experiencing the same problem. Someone also reported this upstream 
in this bug report: https://fedorahosted.org/sssd/ticket/3189


-- 
Frederik Himpe <frede...@frehi.be>

Bug#838462: light-locker: X crashes when attaching/removing displays while locked

[Frederik Möllers]

Package: light-locker
Version: 1.7.0-3
Severity: important

Dear Maintainer,

ever since my Debian installations swapped xscreensaver for light-locker, my X
server crashes when attaching or removing displays while the desktop is locked.

Reproducing the bug works as follows:
1. Lock the screen using light-locker. I don't know if this affects the
behaviour, but I use XFCE as my desktop manager.
2. Attach or remove an attached display while the screen is locked. I regularly
plug my laptop into its docking station or remove it from there with the lid
closed.
3. Unlock the display by entering username and password in the light-locker
dialog.
4. The X server crashes and a new desktop session is started. All programs
previously running on the old X server are killed. Note: The X server only
crashes when unlocking. As long as the desktop is still locked, you can add or
remove displays as you please. However, once you unlock it and the number of
displays is different than when the display was being locked, X crashes.

A workaround is to only attach or remove displays while the desktop is
unlocked.

I will try to gather more information on where exactly things go wrong, but
maybe other people are affected as well and can add their experience here.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  libc62.23-5
ii  libcairo21.14.6-1+b1
ii  libdbus-1-3  1.10.10-1
ii  libdbus-glib-1-2 0.108-1
ii  libglib2.0-0 2.49.6-1
ii  libgtk-3-0   3.21.5-3
ii  libpango-1.0-0   1.40.2-1
ii  libpangocairo-1.0-0  1.40.2-1
ii  libsystemd0  231-4
ii  libx11-6 2:1.6.3-1
ii  libxext6 2:1.3.3-1
ii  libxss1  1:1.2.2-1
ii  lightdm  1.18.2-2

light-locker recommends no packages.

light-locker suggests no packages.

-- no debconf information

Bug#836611: chromium: crash after upgrade 52.0.2743.116-2 -> 53.0.2785.89-1

[Frederik Himpe]

Could this be triggered by the switch to GCC 6?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68853
https://bugs.chromium.org/p/v8/issues/detail?id=3782

-- 
Frederik Himpe <frede...@frehi.be>

Bug#836164: lynis: CUST-0830 should not fail when needrestart is installed

[Frederik Himpe]

Package: lynis
Version: 2.3.3-1
Severity: normal

CUST-0830 checks whether the checkrestart command from the debian-goodies is 
installed. Instead, I have the needrestart package installed, which serves the 
same purpose. This test should not fail when needrestart is installed.

-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (500, 'stable'), (450, 'proposed-updates'), (300, 'testing'), 
(200, 'unstable'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

lynis depends on no packages.

Versions of packages lynis recommends:
pn  menu  

Versions of packages lynis suggests:
ii  aide  0.16~a2.git20130520-3
pn  apt-listbugs  
ii  debsecan  0.4.17
ii  debsums   2.0.53
pn  dnsutils  
ii  fail2ban  0.8.13-1
pn  samhain   
pn  tripwire  

-- Configuration Files:
/etc/bash_completion.d/lynis f792edcbbdf9f71645e60a619bfde321 [Errno 2] No such 
file or directory: u'/etc/bash_completion.d/lynis 
f792edcbbdf9f71645e60a619bfde321'

-- no debconf information

Bug#833750: fai-server: fai-make-nfsroot fails with E: Unable to locate package dracut-config-generic

[Frederik Himpe]

Package: fai-server
Version: 5.1.2~bpo8+1
Severity: normal

I installed fai from backports on my Debian Jessie system. When running 
fai-make-nfsroot, now it fails with:
E: Unable to locate package dracut-config-generic


-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (500, 'stable'), (450, 'proposed-updates'), (300, 'testing'), 
(200, 'unstable'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fai-server depends on:
ii  debootstrap  1.0.67
ii  fai-client   5.1.2~bpo8+1
ii  xz-utils 5.1.1alpha+20120614-2+b3

Versions of packages fai-server recommends:
ii  isc-dhcp-server   4.3.4-1
pn  libproc-daemon-perl   
ii  nfs-kernel-server 1:1.2.8-9
pn  openbsd-inetd | inet-superserver  
ii  openssh-client1:6.7p1-5+deb8u3
ii  openssh-server1:6.7p1-5+deb8u3
ii  tftpd-hpa 5.2+20150808-1

Versions of packages fai-server suggests:
ii  aptitude0.6.11-1+b1
ii  binutils2.25-5
pn  debmirror   
pn  grub2   
pn  perl-tk 
pn  reprepro
pn  squashfs-tools  
pn  xorriso 

-- Configuration Files:
/etc/fai/apt/sources.list changed [not included]
/etc/fai/live.conf df156bb06ff01ea0578799e1ae5e5261 [Errno 2] No such file or 
directory: u'/etc/fai/live.conf df156bb06ff01ea0578799e1ae5e5261'
/etc/fai/nfsroot.conf changed [not included]

-- no debconf information
Using configuration files from /etc/fai
Creating FAI nfsroot in /srv/fai/nfsroot
Creating base system using debootstrap version 1.0.67
Calling debootstrap --exclude=info,wget --include=aptitude jessie 
/srv/fai/nfsroot http://localhost:3142/http.debian.net/debian
I: Retrieving Release 
I: Retrieving Release.gpg 
I: Checking Release signature
I: Valid Release signature (key id 75DDC3C4A499F1A18CB5F3C8CBF8D6FD518E17E1)
I: Retrieving Packages 
I: Validating Packages 
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Found additional required dependencies: acl adduser dmsetup insserv 
libaudit-common libaudit1 libbz2-1.0 libcap2 libcap2-bin libcryptsetup4 
libdb5.3 libdebconfclient0 libdevmapper1.02.1 libgcrypt20 libgpg-error0 
libkmod2 libncursesw5 libprocps3 libsemanage-common libsemanage1 libslang2 
libsystemd0 libudev1 libustr-1.0-1 procps systemd systemd-sysv udev 
I: Found additional base dependencies: aptitude-common libcwidget3 
libdns-export100 libffi6 libgmp10 libgnutls-deb0-28 libgnutls-openssl27 
libhogweed2 libirs-export91 libisc-export95 libisccfg-export90 libmnl0 
libnetfilter-acct1 libnettle4 libnfnetlink0 libp11-kit0 libsqlite3-0 libtasn1-6 
libxapian22 
I: Checking component main on http://localhost:3142/http.debian.net/debian...
I: Retrieving acl 2.2.52-2
I: Validating acl 2.2.52-2
I: Retrieving libacl1 2.2.52-2
I: Validating libacl1 2.2.52-2
I: Retrieving adduser 3.113+nmu3
I: Validating adduser 3.113+nmu3
I: Retrieving apt 1.0.9.8.3
I: Validating apt 1.0.9.8.3
I: Retrieving apt-utils 1.0.9.8.3
I: Validating apt-utils 1.0.9.8.3
I: Retrieving libapt-inst1.5 1.0.9.8.3
I: Validating libapt-inst1.5 1.0.9.8.3
I: Retrieving libapt-pkg4.12 1.0.9.8.3
I: Validating libapt-pkg4.12 1.0.9.8.3
I: Retrieving aptitude 0.6.11-1+b1
I: Validating aptitude 0.6.11-1+b1
I: Retrieving aptitude-common 0.6.11-1
I: Validating aptitude-common 0.6.11-1
I: Retrieving libattr1 1:2.4.47-2
I: Validating libattr1 1:2.4.47-2
I: Retrieving libaudit-common 1:2.4-1
I: Validating libaudit-common 1:2.4-1
I: Retrieving libaudit1 1:2.4-1+b1
I: Validating libaudit1 1:2.4-1+b1
I: Retrieving base-files 8+deb8u5
I: Validating base-files 8+deb8u5
I: Retrieving base-passwd 3.5.37
I: Validating base-passwd 3.5.37
I: Retrieving bash 4.3-11+b1
I: Validating bash 4.3-11+b1
I: Retrieving libdns-export100 1:9.9.5.dfsg-9+deb8u6
I: Validating libdns-export100 1:9.9.5.dfsg-9+deb8u6
I: Retrieving libirs-export91 1:9.9.5.dfsg-9+deb8u6
I: Validating libirs-export91 1:9.9.5.dfsg-9+deb8u6
I: Retrieving libisc-export95 1:9.9.5.dfsg-9+deb8u6
I: Validating libisc-export95 1:9.9.5.dfsg-9+deb8u6
I: Retrieving libisccfg-export90 1:9.9.5.dfsg-9+deb8u6
I: Validating libisccfg-export90 1:9.9.5.dfsg-9+deb8u6
I: Retrieving libboost-iostreams1.55.0 1.55.0+dfsg-3
I: Validating libboost-iostreams1.55.0 1.55.0+dfsg-3
I: Retrieving bsdmainutils 9.0.6
I: Validating bsdmainutils 9.0.6
I: Retrieving libbz2-1.0 1.0.6-7+b3
I: Validating libbz2-1.0 1.0.6-7+b3
I: Retrieving libdebconfclient0 0.192
I: Validating libdebconfclient0 0.192
I: Retrieving coreutils 8.23-4
I: Validating coreutils 8.23-4
I: Retrieving cpio 2.11+dfsg-4.1+deb8u1
I: Validating cpio 2.11+dfsg-4.1+deb8u1
I: Retrieving cron 3.0pl1-127+deb8u1
I: Validating cron 

Bug#831891: r-cran-dplyr: New upstream release v0.5.0

[Frederik Vanrenterghem]

Package: r-cran-dplyr
Version: 0.4.3-6
Severity: wishlist
Tags: upstream

Dear Maintainer,

Version 0.5.0 of dplyr was released in June 2016 with several breaking changes.

https://github.com/hadley/dplyr/releases

Best regards,
Frederik

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages r-cran-dplyr depends on:
ii  libc6  2.22-9
ii  libgcc11:5.3.1-14
ii  libstdc++6 5.3.1-14
ii  r-base-core [r-api-3]  3.3.1-1
ii  r-cran-assertthat  0.1-1
ii  r-cran-dbi 0.4-1-2
ii  r-cran-lazyeval0.1.10-1
ii  r-cran-magrittr1.5-3
ii  r-cran-r6  2.1.2-3
ii  r-cran-rcpp0.12.5-1

Versions of packages r-cran-dplyr recommends:
ii  r-cran-data.table  1.9.6-1
ii  r-cran-rsqlite 1.0.0-2

Versions of packages r-cran-dplyr suggests:
pn  r-cran-lahman  

-- no debconf information

Bug#823865: phpsysinfo: missing copyright

[Frederik Schueler]

Hi Björn,

all files within the debian folder I am the author of are GPL-2.

Best regards
Frederik

On 12.06.2016 11:25, Bjoern Boschman wrote:
> Hi,
> 
> I did not recieve any reply yet.
> Please reply until 2016-06-25. Otherwise I have to choose a copyright on
> my own.
> See also. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823865
> 
> Cheers
> B
> 
> On Thu, May 26, 2016 at 1:59 PM Bjoern Boschman <bjo...@boschman.de
> <mailto:bjo...@boschman.de>> wrote:
> 
> Hi,
> 
> as the current maintainer of phpsysinfo I'd like to ask you if GPL-2
> is ok for you for all files within debian/ folder.
> 
> Cheers
> B
> 



signature.asc
Description: OpenPGP digital signature

Bug#824881: nemo: SIGSEGV in g_type_check_instance_is_fundamentally_a in glib2.0-2.48.1/./gobject/gtype.c:4034

[Frederik Himpe]

Package: nemo
Version: 3.0.1-1
Severity: normal

While I'm browsing my pictures directory's, containing JPEG and NEF RAW images,
nemo will always crash after some time browsing around. This is a stack trace:

Program received signal SIGSEGV, Segmentation fault.
0x750f480c in g_type_check_instance_is_fundamentally_a
(type_instance=type_instance@entry=0x7fffd4002b60,
fundamental_type=fundamental_type@entry=80) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gtype.c:4034
4034/build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gtype.c: No such file or
directory.
(gdb) thread apply all bt

Thread 26 (Thread 0x7fffe7fff700 (LWP 15058)):
#0  0x74056ae9 in syscall () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x74e3dd4a in g_cond_wait_until (cond=cond@entry=0x894c38,
mutex=mutex@entry=0x894c30, end_time=end_time@entry=1891790839) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gthread-posix.c:1441
#2  0x74dcd999 in g_async_queue_pop_intern_unlocked (queue=0x894c30,
wait=wait@entry=1, end_time=1891790839) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gasyncqueue.c:422
#3  0x74dcdff8 in g_async_queue_timeout_pop_unlocked (queue=, timeout=timeout@entry=50) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gasyncqueue.c:570
#4  0x74e20536 in g_thread_pool_thread_proxy (pool=0x896560) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gthreadpool.c:262
#5  0x74e20536 in g_thread_pool_thread_proxy (data=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gthreadpool.c:296
#6  0x74e1fbc5 in g_thread_proxy (data=0x7fffdc0154f0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gthread.c:780
#7  0x7431d454 in start_thread () at /lib/x86_64-linux-
gnu/libpthread.so.0
#8  0x7405aeed in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7fffe77fe700 (LWP 15036)):
#0  0x74051e5d in poll () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x74df939c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fffd40010c0, timeout=, context=0x93ea80) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x74df939c in g_main_context_iterate
(context=context@entry=0x93ea80, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x74df94ac in g_main_context_iteration (context=0x93ea80,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7fffec03a41d in  () at /usr/lib/x86_64-linux-
gnu/gio/modules/libdconfsettings.so
#5  0x74e1fbc5 in g_thread_proxy (data=0x999800) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gthread.c:780
#6  0x7431d454 in start_thread () at /lib/x86_64-linux-
gnu/libpthread.so.0
#7  0x7405aeed in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7fffeca40700 (LWP 15034)):
#0  0x74051e5d in poll () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x74df939c in g_main_context_iterate (priority=2147483647, n_fds=4,
fds=0x7fffe0004380, timeout=, context=0x895550) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x74df939c in g_main_context_iterate (context=0x895550,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x74df9722 in g_main_loop_run (loop=0x8954e0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4034
#4  0x753f7916 in gdbus_shared_thread_func (user_data=0x895520) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./gio/gdbusprivate.c:246
#5  0x74e1fbc5 in g_thread_proxy (data=0x8324a0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gthread.c:780
#6  0x7431d454 in start_thread () at /lib/x86_64-linux-
gnu/libpthread.so.0
#7  0x7405aeed in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7fffed241700 (LWP 15033)):
#0  0x74051e5d in poll () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x74df939c in g_main_context_iterate (priority=2147483647, n_fds=2,
fds=0x7fffe80008c0, timeout=, context=0x894d40) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x74df939c in g_main_context_iterate
(context=context@entry=0x894d40, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x74df94ac in g_main_context_iteration (context=0x894d40,
may_block=may_block@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x74df94e9 in glib_worker_main (data=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:5672
#5  0x74e1fbc5 in g_thread_proxy (data=0x832450) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gthread.c:780
#6  0x7431d454 in start_thread () at /lib/x86_64-linux-
gnu/libpthread.so.0
#7  0x7405aeed in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x77f2aa40 (LWP 15029)):
#0  0x750f480c in g_type_check_instance_is_fundamentally_a

Bug#823713: libkf5coreaddons5:amd64: random sequences not random

[Frederik Schwarzer]

Package: libkf5coreaddons5
Version: 5.21.0-1
Severity: normal

Dear Maintainer,

please add the patch from
https://bugs.kde.org/show_bug.cgi?id=362161
to have properly seeded random numbers.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to en_US.UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libkf5coreaddons5:amd64 depends on:
ii  libc6  2.22-7
ii  libfam02.7.0-17.1+b1
ii  libgcc11:6.1.1-1
ii  libkf5coreaddons-data  5.21.0-1
ii  libqt5core5a   5.6.0+dfsg-2
ii  libstdc++6 6.1.1-1
ii  shared-mime-info   1.6-1

libkf5coreaddons5:amd64 recommends no packages.

libkf5coreaddons5:amd64 suggests no packages.

-- no debconf information

Bug#821030: requires python-setuptools >= 11.3

[Frederik Himpe]

I was experiencing the same error on Debian jessie with letsencrypt
0.5.0-1:

Traceback (most recent call last):
  File "/usr/bin/letsencrypt", line 9, in 
load_entry_point('letsencrypt==0.5.0', 'console_scripts',
'letsencrypt')()
  File "/usr/lib/python2.7/dist-packages/letsencrypt/main.py", line
692, in main
return config.func(config, plugins)
  File "/usr/lib/python2.7/dist-packages/letsencrypt/main.py", line
504, in obtain_cert
le_client = _init_le_client(config, auth, installer)
  File "/usr/lib/python2.7/dist-packages/letsencrypt/main.py", line
356, in _init_le_client
acc, acme = _determine_account(config)
  File "/usr/lib/python2.7/dist-packages/letsencrypt/main.py", line
320, in _determine_account
accounts = account_storage.find_all()
  File "/usr/lib/python2.7/dist-packages/letsencrypt/account.py", line
160, in find_all
accounts.append(self.load(account_id))
  File "/usr/lib/python2.7/dist-packages/letsencrypt/account.py", line
173, in load
regr = messages.RegistrationResource.json_loads(regr_file.read())
  File "/usr/lib/python2.7/dist-packages/acme/jose/interfaces.py", line
180, in json_loads
return cls.from_json(loads)
  File "/usr/lib/python2.7/dist-packages/acme/jose/json_util.py", line
297, in from_json
return cls(**cls.fields_from_json(jobj))
  File "/usr/lib/python2.7/dist-packages/acme/jose/json_util.py", line
288, in fields_from_json
fields[slot] = field.decode(value)
  File "/usr/lib/python2.7/dist-packages/acme/jose/json_util.py", line
92, in decode
return self.fdec(value)
  File "/usr/lib/python2.7/dist-packages/acme/jose/json_util.py", line
297, in from_json
return cls(**cls.fields_from_json(jobj))
  File "/usr/lib/python2.7/dist-packages/acme/jose/json_util.py", line
288, in fields_from_json
fields[slot] = field.decode(value)
  File "/usr/lib/python2.7/dist-packages/acme/jose/json_util.py", line
92, in decode
return self.fdec(value)
  File "/usr/lib/python2.7/dist-packages/acme/jose/json_util.py", line
489, in from_json
return type_cls(**type_cls.fields_from_json(jobj))
  File "/usr/lib/python2.7/dist-packages/acme/jose/jwk.py", line 226,
in fields_from_json
key = public_numbers.public_key(default_backend())
  File "/usr/lib/python2.7/dist-
packages/cryptography/hazmat/backends/__init__.py", line 35, in
default_backend
_default_backend = MultiBackend(_available_backends())
  File "/usr/lib/python2.7/dist-
packages/cryptography/hazmat/backends/__init__.py", line 22, in
_available_backends
"cryptography.backends"
AttributeError: 'EntryPoint' object has no attribute 'resolve'

This is https://github.com/pyca/cryptography/issues/2838 which states
that python-cryptography requires at least version 11.3 of
python-setuptools 11.3
https://github.com/pyca/cryptography/blob/master/setup.py#L40

I indeed had Jessie's python-setuptools 5.5.1-1. Upgrading this to
18.8-1~bpo8+1 made the error go away.
-- 
Frederik Himpe <fhi...@vub.ac.be>
Vrije Universiteit Brussel

Bug#815897: apache2-utils: Conflicting /usr/sbin/httxt2dbm when upgrading from Squeeze to Jessie

[Frederik Himpe]

Package: apache2-utils
Version: 2.2.16-6+squeeze15
Severity: normal

When upgrading my system from Squeeze to Jessie using apt-get dist-upgrade, I 
get this error:

Preparing to replace apache2-utils 2.2.16-6+squeeze15 (using 
.../apache2-utils_2.4.10-10+deb8u4_amd64.deb) ...
Unpacking replacement apache2-utils ...
dpkg: error processing 
/var/cache/apt/archives/apache2-utils_2.4.10-10+deb8u4_amd64.deb (--unpack):
 trying to overwrite '/usr/sbin/httxt2dbm', which is also in package 
apache2.2-bin 2.2.16-6+squeeze15
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


-- System Information:
Debian Release: 6.0.10
  APT prefers squeeze-lts
  APT policy: (500, 'squeeze-lts'), (500, 'oldoldstable-updates'), (500, 
'oldoldstable'), (300, 'oldstable'), (200, 'stable'), (100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apache2-utils depends on:
pn  libapr1(no description available)
pn  libaprutil1(no description available)
ii  libc6  2.19-18+deb8u3GNU C Library: Shared libraries
ii  libssl0.9.80.9.8o-4squeeze23 SSL shared libraries

apache2-utils recommends no packages.

apache2-utils suggests no packages.

-- no debconf information

Bug#812252: less not any more registered as "pager" alternative

[Frederik Möllers]

Hi,

I've created a patch which moves the update-alternatives commands to the
correct scripts and which also implements the strategy mentiones in
message 5 of bug #694051. Applying it to the source directory should
solve all problems related to these two bugs.

Cheers,
Frederik
diff -urN less-481.old/debian/less.postinst less-481/debian/less.postinst
--- less-481.old/debian/less.postinst	2016-01-11 13:08:57.0 +0100
+++ less-481/debian/less.postinst	2016-01-26 12:04:54.124486691 +0100
@@ -1,12 +1,66 @@
-#!/bin/sh
+#! /bin/sh
+# postinst script for less
+#
+# see: dh_installdeb(1)
+
 set -e
 
-if [ "$1" = 'configure' ]; then
-  for file in lessfile lesspipe lesskey lessecho less; do
-if [ ! -e /usr/bin/$file ]; then
-  ln -s /bin/$file /usr/bin/$file
-fi
-  done
-fi
+# summary of how this script can be called:
+#*  `configure' 
+#*  `abort-upgrade' 
+#* <conflictor's-postinst> `abort-remove' `in-favour' 
+#  
+#* <deconfigured's-postinst> `abort-deconfigure' `in-favour'
+#`removing'
+#   
+# for details, see /usr/doc/packaging-manual/
+#
+# quoting from the policy:
+# Any necessary prompting should almost always be confined to the
+# post-installation script, and should be protected with a conditional
+# so that unnecessary prompting doesn't happen if a package's
+# installation fails and the `postinst' is called with `abort-upgrade',
+# `abort-remove' or `abort-deconfigure'.
+
+case "$1" in
+configure)
+update-alternatives --quiet --install /usr/bin/pager pager \
+	/bin/less 77 --slave /usr/share/man/man1/pager.1.gz \
+	pager.1.gz /usr/share/man/man1/less.1.gz
+
+  # This change needs to get into one stable release.
+  # See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694051
+update-alternatives --quiet --remove pager /usr/bin/less
+
+  # Purge the debconf database we no longer need.
+  if [ -e /usr/share/debconf/confmodule ]; then
+. /usr/share/debconf/confmodule
+db_version 2.0
+db_purge
+  fi
+
+  # install links in /bin
+  for file in lessfile lesspipe lesskey lessecho less; do
+if [ ! -e /usr/bin/$file ]; then
+  ln -s /bin/$file /usr/bin/$file
+fi
+  done
+
+;;
+
+abort-upgrade|abort-remove|abort-deconfigure)
+
+;;
+
+*)
+echo "postinst called with unknown argument \`$1'" >&2
+exit 0
+;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
 
 #DEBHELPER#
+
+exit 0
diff -urN less-481.old/debian/less.postrm less-481/debian/less.postrm
--- less-481.old/debian/less.postrm	2016-01-11 13:08:57.0 +0100
+++ less-481/debian/less.postrm	2016-01-26 12:06:27.928916149 +0100
@@ -9,4 +9,9 @@
   done
 fi
 
+if [ "$1" = 'remove' -o "$1" = 'disappear' ]
+then
+update-alternatives --quiet --remove pager /bin/less
+fi
+
 #DEBHELPER#
diff -urN less-481.old/debian/less.prerm less-481/debian/less.prerm
--- less-481.old/debian/less.prerm	1970-01-01 01:00:00.0 +0100
+++ less-481/debian/less.prerm	2016-01-26 12:01:23.683327144 +0100
@@ -0,0 +1,37 @@
+#! /bin/sh
+# prerm script for less
+#
+# see: dh_installdeb(1)
+
+set -e
+
+# summary of how this script can be called:
+#*  `remove'
+#*  `upgrade' 
+#*  `failed-upgrade' 
+#* <conflictor's-prerm> `remove' `in-favour'  
+#* <deconfigured's-prerm> `deconfigure' `in-favour'
+#`removing'
+#   
+# for details, see /usr/doc/packaging-manual/
+
+case "$1" in
+remove)
+update-alternatives --quiet --remove pager /bin/less
+;;
+upgrade|failed-upgrade|deconfigure)
+;;
+*)
+echo "prerm called with unknown argument \`$1'" >&2
+exit 0
+;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
+
+
diff -urN less-481.old/debian/postinst less-481/debian/postinst
--- less-481.old/debian/postinst	2014-09-08 06:08:25.0 +0200
+++ less-481/debian/postinst	1970-01-01 01:00:00.0 +0100
@@ -1,59 +0,0 @@
-#! /bin/sh
-# postinst script for less
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#*  `configure' 
-#*  `abort-upgrade' 
-#* <conflictor's-postinst> `abort-remove' `in-favour' 
-#  
-#* <deconfigured's-postinst> `abort-deconfigure' `in-favour'
-#`removing'
-#   
-# for details, see /usr/doc/packaging-manual/
-#
-# quoting from the policy:
-# Any necessary prompting should almost always be confined to the
-# post-installation script, and should be protected with a conditional
-# so that unnecessary prompting doesn't happen if 

Bug#809964: [kwalletmanager] Manager from kde 4 and 5 should be co-installable

[Frederik Schwarzer]

Package: kwalletmanager
Version: 4:15.08.3-1
Severity: normal

--- Please enter the report below this line. ---

Hi,

since some applications use the KDE 4 version of kwalletmanager and 
some other applications use the KDE 5 version of kwalletmanager, both 
versions should be co-installable.

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.3.0-1-amd64

Debian Release: stretch/sid
  500 unstableftp2.de.debian.org 
1 experimentalftp2.de.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#808580: bareos-storage-tape: Package tries to chown unexisting /etc/bareos/bareos-sd.d/device-tape-with-autoloader.conf

[Frederik Himpe]

Package: bareos-storage-tape
Version: 14.2.6-2
Severity: normal

Dear Maintainer,

When updating bareos-storage-tape to 14.2.6-2, I got this error:

Setting up bareos-storage-tape (14.2.6-2) ...
chown: cannot access 
‘/etc/bareos/bareos-sd.d/device-tape-with-autoloader.conf’: No such file or 
directory
dpkg: error processing package bareos-storage-tape (--configure):
 subprocess installed post-installation script returned error exit status 1

I removed this configuration file in the past because I don't need it in my set 
up. The script should probably check first whether this file still exists 
before chowning it.


-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable'), (450, 'proposed-updates'), (300, 'testing'), 
(200, 'unstable'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates'), (100, 'squeeze-lts'), (100, 
'oldoldstable-updates'), (100, 'oldoldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bareos-storage-tape depends on:
ii  adduser3.113+nmu3
ii  bareos-common  14.2.6-2
ii  bareos-storage 14.2.6-2
ii  debconf [debconf-2.0]  1.5.56
ii  libc6  2.19-18+deb8u1
ii  libcap21:2.24-8
ii  libgcc11:4.9.2-10
ii  libgnutls-deb0-28  3.3.8-6+deb8u3
ii  liblzo2-2  2.08-1.2
ii  libstdc++6 4.9.2-10
ii  libwrap0   7.6.q-25
ii  lsb-base   4.1+Debian13+nmu1
ii  mtx1.3.12-9
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages bareos-storage-tape recommends:
ii  mt-st  1.1-6

Versions of packages bareos-storage-tape suggests:
pn  scsitools  
pn  sg3-utils  

-- Configuration Files:
/etc/bareos/bareos-sd.d/device-tape-with-autoloader.conf changed [not included]

-- no debconf information

Bug#804212: pulseaudio: Build with soxr support

[Frederik Himpe]

:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1e20"
device.product.name = "7 Series/C210 Series Chipset Family High 
Definition Audio Controller"
device.form_factor = "internal"
device.string = "0"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Formats:
pcm

Source #1
State: SUSPENDED
Name: alsa_input.pci-_00_1b.0.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 6
Mute: yes
Volume: front-left: 33154 /  51% / -17.76 dB,   front-right: 33154 /  
51% / -17.76 dB
balance 0.00
Base Volume: 8739 /  13% / -52.50 dB
Monitor of Sink: n/a
Latency: 0 usec, configured 0 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "92HD81B1X5 Analog"
alsa.id = "92HD81B1X5 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xd473 irq 36"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1e20"
device.product.name = "7 Series/C210 Series Chipset Family High 
Definition Audio Controller"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Intel PantherPoint HDMI"
alsa.components = "HDA:111d7605,103c17c2,00100107 
HDA:80862806,80860101,0010"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Ports:
analog-input-internal-mic: Internal Microphone (priority: 8900)
analog-input-mic: Microphone (priority: 8700, not available)
analog-input-linein: Line In (priority: 8100, not available)
Active Port: analog-input-internal-mic
Formats:
pcm

Source #2
State: SUSPENDED
Name: alsa_output.platform-pcspkr.analog-mono.monitor
Description: Monitor of pcsp Analog Mono
Driver: module-alsa-card.c
Sample Specification: s16le 1ch 37286Hz
Channel Map: mono
Owner Module: 7
Mute: no
Volume: mono: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: alsa_output.platform-pcspkr.analog-mono
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Monitor of pcsp Analog Mono"
device.class = "monitor"
alsa.card = "1"
alsa.card_name = "pcsp"
alsa.long_card_name = "Internal PC-Speaker at port 0x61"
alsa.driver_name = "snd_pcsp"
device.bus_path = "platform-pcspkr"
sysfs.path = "/devices/platform/pcspkr/sound/card1"
device.string = "1"
module-udev-detect.discovered = "1"
device.icon_name = "audio-ca

Bug#781888: [pkg-cinnamon] Bug#781888: cinnamon-session: session does not start

[Frederik Himpe]

I am experiencing this bug on two different systems now.

I have opened an upstream bug:
https://github.com/linuxmint/Cinnamon/issues/4156


-- 
Frederik Himpe frede...@frehi.be


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781888: [pkg-cinnamon] Bug#781888: cinnamon-session: session does not start

[Frederik Himpe]

On 2015-05-16 15:16, Frederik Himpe wrote:

I am experiencing this bug on two different systems now.

I have opened an upstream bug:
https://github.com/linuxmint/Cinnamon/issues/4156


# apt-get install -t experimental gir1.2-meta-muffin-0.0
fixed this problem.

All muffin packages where still the 2.2 version.

So this dependency seems to be missing.

--
Frederik Himpe


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785486: nemo crashes when starting desktop icon with libnemo-extension1 2.2.4-2

[Frederik Himpe]

Package: nemo
Version: 2.4.5-1
Severity: normal

I upgraded to cinnamon 2.4 and nemo from Experimental. When double clicking a
desktop icon in Cinnamon, nemo crashes and all desktop icons disappear.

I found this was caused by libnemo-extension1 which was still at version
2.2.4-2. Upgrading libnemo-extension1 to version 2.4.5-1 from Experimental,
made this crash go away.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (300, 'testing'), (200, 'unstable'), (200, 'stable'), (160, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nemo depends on:
ii  desktop-file-utils 0.22-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  gvfs   1.22.2-1+b1
ii  libatk1.0-02.16.0-2
ii  libc6  2.19-18
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libcinnamon-desktop4   2.4.2-1
ii  libexempi3 2.2.2-2
ii  libexif12  0.6.21-2
ii  libgail-3-03.14.5-1
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libglib2.0-0   2.44.0-2
ii  libglib2.0-data2.44.0-2
ii  libgtk-3-0 3.14.5-1
ii  libnemo-extension1 2.4.5-1
ii  libnotify4 0.7.6-2
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libx11-6   2:1.6.3-1
ii  libxml22.9.1+dfsg1-5
ii  nemo-data  2.4.5-1
ii  shared-mime-info   1.3-1

Versions of packages nemo recommends:
pn  cinnamon-l10nnone
ii  eject2.1.5+deb1+cvs20081104-13.1
ii  gvfs-backends1.22.2-1+b1
ii  librsvg2-common  2.40.5-1
ii  nemo-fileroller  1.8.0-1

Versions of packages nemo suggests:
ii  eog3.14.1-1
ii  evince [pdf-viewer]3.14.1-2
ii  totem  3.14.0-2
ii  vlc [mp3-decoder]  2.2.1-1+b1
ii  vlc-nox [mp3-decoder]  2.2.1-1+b1
ii  xdg-user-dirs  0.15-2

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781888: [pkg-cinnamon] Bug#781888: cinnamon-session: session does not start

[Frederik Himpe]

On Mon, 2015-05-04 at 12:35 +0200, Maximiliano Curia wrote:
 Hi,
 
 On 02/05/15 17:25, Frederik Himpe wrote:
  I'm experiencing exactly the same problem on one of my systems:
 
  ii  libcinnamon-control-center1:amd64 2.2.11-4 amd64utilities to
  configure the Cinnamon desktop
 
 Oh, cinnamon-control-center is missing a version dependency of
 libcinnamon-control-center1, added.
 
  ii  libcinnamon-menu-3-0  2.2.0-3  amd64Cinnamon
  implementation of the freedesktop menu specification
 
 Well, that's not updated, you are probably missing the updated:
 gir1.2-cmenu-3.0
 
 I'm adding those missing dependencies (that would be part of the next
 release). Please let me know it that fixes the issue.

No, it does not help.

I have these versions installed on one system where Cinnamon is starting
successfully:

ii  cinnamon  2.4.8-1  amd64Innovative and 
comfortable desktop
ii  cinnamon-common   2.4.8-1  all  Innovative and 
comfortable desktop (Common data files)
ii  cinnamon-control-center   2.4.2-1  amd64utilities to 
configure the Cinnamon desktop
ii  cinnamon-control-center-data  2.4.2-1  all  configuration 
applets for Cinnamon - data files
ii  cinnamon-core 2.2.4all  Cinnamon 
desktop environment - essential components
ii  cinnamon-desktop-data 2.4.2-1  all  Common files 
for Cinnamon desktop apps
ii  cinnamon-screensaver  2.4.2-1  amd64Cinnamon screen 
saver and locker
ii  cinnamon-session  2.4.3-1  amd64Cinnamon 
Session Manager - Minimal runtime
ii  cinnamon-session-common   2.4.3-1  all  Cinnamon 
Session Manager - common files
ii  cinnamon-settings-daemon  2.4.3-1  amd64daemon handling 
the Cinnamon session settings
ii  cjs   2.4.2-1  amd64Mozilla-based 
javascript bindings for the GNOME platform
ii  gir1.2-cinnamondesktop-3.02.4.2-1  amd64Introspection 
data for CinnamonDesktop
ii  gir1.2-cmenu-3.0  2.2.0-3  amd64GObject 
introspection data for the Cinnamon menu library
ii  libcinnamon-control-center1:amd64 2.4.2-1  amd64utilities to 
configure the Cinnamon desktop
ii  libcinnamon-desktop4:amd642.4.2-1  amd64Cinnamon 
library for loading .desktop files
ii  libcinnamon-menu-3-0  2.2.0-3  amd64Cinnamon 
implementation of the freedesktop menu specification
ii  libcjs0:amd64 2.4.2-1  amd64Mozilla-based 
javascript bindings for the GNOME platform

So it looks like these missing dependencies are unrelated to this problem.



-- 
Frederik Himpe frede...@frehi.be


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#612539: Still a good option when upgrading from wheezy to jessie

[Frederik Vanrenterghem]

Hi,

upgrading from wheezy to jessie I had to look a while to figure out what
the source was of my daily security updates, having forgotten about
debsecan being installed a long while ago. In lieu of this wishlist, maybe
add something like Generated by debsecan to the emails, possibly as a
header if the email format shouldn't change?

Thx,
Frederik Vanrenterghem