Bug#984956: Me too

[sixerjman]

I am hit by this bug also. Going to try and learn SLURM in the meantime. Is
there
any progress? Thank you for your work on this excellent package.

Bug#970752: Works OK now with current version of open-vm-tools

[sixerjman]

sctl status vmtoolsd ? vmtoolsd.service - Service for virtual machines
hosted on VMware Loaded: loaded (/usr/lib/systemd/system/vmtoolsd.service;
enabled; vendor preset: enabled) Active: active (running) since Tue
2020-10-20 13:47:58 EDT; 4min 49s ago

open-vm-tools version: 2:11.1.5-1

OK to close.

Bug#970752: system-detect-virt with Debian under VirtualBox

[sixerjman]

$ systemd-detect-virt
oracle

Bug#970752: systemd-detect-virt

[sixerjman]

Results of 'systemd-detect-virt' detect 'vmware' correctly in both
VirtualBox and VMplayer:

$ systemd-detect-virt
vmware

Bug#970752: Subject: open-vm-tools: ConditionVirtualization=vmware was not met

[sixerjman]

Package: open-vm-tools Version: open-vm-tools service (vmtoolsd) fails to
start Severity: normal Dear Maintainer,

* What led up to the situation? Tried to start vmtoolsd

* What exactly did you do (or not do) that was effective (or ineffective)?
n/a

* What was the outcome of this action? Condition not met, start failed

* What outcome did you expect instead? vmtoolsd starts

The following condition caused the failure:

ConditionVirtualization=vmware was not met

After commenting it out vmtoolsd started successfully. For what it's worth,
the same condition fails in VMware vmplayer.

-- System Information: Debian Release: bullseye/sid APT prefers testing APT
policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64)
Kernel: Linux 5.8.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags:
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8,
LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8),
LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via
/run/systemd/system) LSM: AppArmor: enabled

Bug#668613: Bug still exists

[sixerjman]

I have the same situation with two Broadcom adapters, one is Ethernet and
the other is wireless.
The postinst script sees the Ethernet adapter first, finds no matching
firmware and defaults
to downloading latest firmware (now 1:019-6) which does not work with older
B43 adapters.
See open bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964140

Bug#939262: Bug still exists in Version 20200721-1

[sixerjman]

It just hit me again.

Bug#964140: Correction - workaround does not work

[sixerjman]

b43-fwcutter still insists on installing the latest firmware (666 - sign of
the devil HA).
This package and b43-fwcutter are hopelessly broken on my previously
working system.
The last good version was 1:09-5, but that .deb is not available in any
repository. Please help.

Bug#968452: sysstat: Invalid system activity file on i686

[sixerjman]

Package: sysstat
Version: 12.3.3-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?
Execute 'sar'
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Deleted old system activity files (/var/log/sysstat/saXX) and restarting
sysstat
   * What was the outcome of this action?
Invalid system activity file: saXX
   * What outcome did you expect instead?
Valid report from sar

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 5.7.0-2-686-pae (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sysstat depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  libc6  2.31-3
ii  libsensors51:3.6.0-2
ii  lsb-base   11.1.0
ii  ucf3.0043
ii  xz-utils   5.2.4-1+b1

Versions of packages sysstat recommends:
ii  cron [cron-daemon]  3.0pl1-136

Versions of packages sysstat suggests:
pn  isag  

-- debconf information:
  sysstat/enable: true
  sysstat/remove_files: true

Bug#965960: AMD64 version is clean

[sixerjman]

This bug only seems to happen on x86 (i686, et. al.) 32-bit architecture.
AMD64 does not
exhibit this behavior.

Bug#964140: V1:19-6 loads wrong firmware when >1 Broadcom network adapter present

[sixerjman]

Package: firmware-b43-installer
Version: 1:019-6
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?
Upgrading to latest version from testing (1:019-6)
The .postinst script derives the vendor : product ID for Broadcom adapters
on this line:

pci=`lspci -n -d 14e4: | grep -o "14e4:[1234567890abcdef]\+" || true

The machine in question has an Ethernet adapter from Broadcom, so
the above test results in the two vendor IDs being reported with
the ethernet adapter listed first:


lspci -n -d 14e4: | grep -o "14e4:[1234567890abcdef]\+"
14e4:4401   <=== Ethernet adapter
14e4:4320

As a result the B43 wireless adapter is not found resulting in
the latest (broken for this adapter) firmware being downloaded
and installed.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Patch firmware-b43-installer.postinst to force classic firmware

--- firmware-b43-installer.postinst~ 2020-06-26 09:20:22.090176695 -0400
+++ firmware-b43-installer.postinst 2020-06-26 09:22:51.900010353 -0400
@@ -215,6 +215,7 @@
 fi

 # Fix for #960270
+latest=
 classic=1

 make_download_vars

   * What was the outcome of this action?
Classic firmware downloaded and installed

   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.6.0-2-686-pae (SMP w/2 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), LANGUAGE=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)
LSM: AppArmor: enabled

Versions of packages firmware-b43-installer depends on:
ii  b43-fwcutter  1:019-4
ii  bzip2 1.0.8-3
ii  wget  1.20.3-1+b1

firmware-b43-installer recommends no packages.

firmware-b43-installer suggests no packages.

-- no debconf information

Bug#960279: To pin version to 1:019-4

[sixerjman]

apt-mark hold b43-fwcutter
apt-mark hold firmware-b43-installer

Bug#960279: b43-fwcutter: Version 1:019-5 breaks b43

[sixerjman]

Package: b43-fwcutter
Version: 1:019-5
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?
Upgrade to lastest version in testing
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Downgraded to stable version 1:019-4
   * What was the outcome of this action?
Receive / Transmit rate dropped from 54 mbps to 1 mbps
   * What outcome did you expect instead?
~48-54 mbps Recieve / Transmit rate

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 5.6.0-1-686-pae (SMP w/2 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), LANGUAGE=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)
LSM: AppArmor: enabled

Versions of packages b43-fwcutter depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  libc6  2.30-4

b43-fwcutter recommends no packages.

b43-fwcutter suggests no packages.

-- debconf information:
  b43-fwcutter/install-unconditional: trueContent-Type: text/plain;
charset="us-ascii"

Bug#953104: Fedora updates has bugix release of HPLIP

[sixerjman]

===
  hplip-3.20.2-1.fc31
===
  Update ID: FEDORA-2020-c243f9765f
   Type: bugfix
Updated: 2020-03-06 15:58:07
Description: 3.20.2
   Severity: None

Bug#953104: Upstream issue link?

[sixerjman]

Has a problem been opened with HPLIP upstream? If so is there a link to the
issue page?

Bug#953104: How to downgrade to 3.19

[sixerjman]

Thank you Addison. I also found this set of instructions for downgrading:

https://www.linuxuprising.com/2019/02/how-to-downgrade-packages-to-specific.html

Bug#953104: How to downgrade to HPLIP version 3.19?

[sixerjman]

I was able to downgrade on my Fedora machine with the dnf command, but
downgrade option(s) don't seem to be available with apt(-get). What is the
procedure to downgrade on Debian systems? I am tracking testing/unstable,
but see 3.18 is available in stable.

Bug#942563: Workaround for older chips

[sixerjman]

This workaround from the Debian iwlwifi wiki seems to have fixed the
problem on my WiFi 5100 Link adapter:

Troubleshooting

Slow WiFi problems when using Bluetooth

Some devices like the 6235 do include a Bluetooth device in the same card,
which may lead into radio conflict. Newer devices (7200 and up) try to
solve them intelligently, but it is not the case of older ones.

If your WiFi is slow when using Bluetooth, try adding the following to
/etc/modprobe.d/iwlwifi.conf and reboot:

   -

   options iwlwifi bt_coex_active=0 swcrypto=1 11n_disable=8


https://wiki.debian.org/iwlwifi

Bug#942563: Any progress on getting a fix for this?

[sixerjman]

This is a record of all the restarts for the last ~24 hours:

Feb 23 08:24:49 debiant kernel: [260162.902256] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 23 10:00:37 debiant kernel: [265911.64] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 23 11:52:27 debiant kernel: [272621.545283] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 23 17:20:56 debiant kernel: [292329.572778] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 23 18:21:08 debiant kernel: [295942.240028] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 23 19:02:22 debiant kernel: [298416.101106] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 23 19:23:29 debiant kernel: [299682.797195] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 23 19:30:00 debiant kernel: [300074.260841] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 23 19:40:08 debiant kernel: [300681.853074] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 24 06:16:21 debiant kernel: [301294.103572] Restarting tasks ... done.
Feb 24 07:57:08 debiant kernel: [307340.793350] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 24 08:12:55 debiant kernel: [308288.569309] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 24 08:15:08 debiant kernel: [308421.082506] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.
Feb 24 08:22:09 debiant kernel: [308842.138632] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x200.

I believe this is also the cause of constant crashes in the inetd service
running on this machine.

Bug#948257: Is there a fix coming down the pike?

[sixerjman]

Can we expect a fix soon in whatever package causes the console spam? It's
a rude awakening to get hit by these messages first thing in the morning
when doing maintenance.

Bug#864079: Thank you for the update

[sixerjman]

Thanks for continuing to stay on top of this. I realize it is kind of
complicated with the split out
of the BackupPC software into 3 clients with shifting dependencies, but
next to the operating
system and attendant major subsystems (i.e. networking), the backup
software is the most important subsystem
IMO. As upstream BackupPC continues to release bug fix / enhancement
updates, it is a priority to
continue to track it closely. Again, thank you for your work and attention
to this matter.

Bug#864079: Status of this bug?

[sixerjman]

I would like to know if anybody is working on this. There has been a recent
update of
perl-base from 5.28 to 5.30 which necessitated rebuilding the backuppc and
backuppc-xs
(now libbackuppc-xs-perl) packages. The most recent backuppc version is now
4.3.1
and each time a new release of any of packages comes out it necessitates
rebuilding
the packages per

https://github.com/backuppc/backuppc/wiki/Build-Your-Own-Packages.

Now today on testing yet another perl-base upgrade from 5.30.0-8 to
5.30.0-9 has come
along, and I just got done with the a somewhat stressful rebuild for
5.30.0-8.

For what it's worth, the rsync-bpc on my server is version 3.0.9.12 which
has worked
with v4.2, v4.3 and v4.3.1 of backuppc. This bug is listed as a packaging
blocker
for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873075 but it seems
like
it could be packaged up so progress can be made on packaging backuppc-v4
proper.

Bug#909260: Retry coming

[sixerjman]

I will be retrying the 'make deb-pkg' build with kernel version 5 source in
the
next few days. I will report back later.

Bug#909260: Utilities used

[sixerjman]

Using gcc and binutils

Bug#935915: The problem went away

[sixerjman]

The last 4 or 5 days have seen a return to LAN speed transfers. I have no
idea why
it appeared or why it went away. There have been lots of WLAN errors as
reported
by my router. That may not have been the root cause but it certainly
wouldn't help.
Also, the Intel WiFi modem on one of the clients has been taking firmware,
so
that may have been a contributing factor.  Falls in 'The bug one that got
away'
category I guess. OK to close.

Bug#885958: Variant of this error still occurring

[sixerjman]

Aug  6 09:00:07 debiant kernel: [876895.326060] iwlwifi :04:00.0:
Microcode SW error detected.  Restarting 0x9200.
Aug  6 09:00:07 debiant kernel: [876895.326070] iwlwifi :04:00.0:
Loaded firmware version: 8.83.5.1 build 33692
Aug  6 09:00:07 debiant kernel: [876895.326199] iwlwifi :04:00.0: Start
IWL Error Log Dump:
Aug  6 09:00:07 debiant kernel: [876895.326202] iwlwifi :04:00.0:
Status: 0x004C, count: 5
Aug  6 09:00:07 debiant kernel: [876895.326205] iwlwifi :04:00.0:
0x0005 | SYSASSERT
Aug  6 09:00:07 debiant kernel: [876895.326208] iwlwifi :04:00.0:
0x24EC | uPc
Aug  6 09:00:07 debiant kernel: [876895.326210] iwlwifi :04:00.0:
0x24C8 | branchlink1
Aug  6 09:00:07 debiant kernel: [876895.326213] iwlwifi :04:00.0:
0x24C8 | branchlink2
Aug  6 09:00:07 debiant kernel: [876895.326215] iwlwifi :04:00.0:
0x0916 | interruptlink1
Aug  6 09:00:07 debiant kernel: [876895.326218] iwlwifi :04:00.0:
0x | interruptlink2
Aug  6 09:00:07 debiant kernel: [876895.326220] iwlwifi :04:00.0:
0x00FF | data1
Aug  6 09:00:07 debiant kernel: [876895.326223] iwlwifi :04:00.0:
0x0489 | data2
Aug  6 09:00:07 debiant kernel: [876895.326225] iwlwifi :04:00.0:
0x0489 | line
Aug  6 09:00:07 debiant kernel: [876895.326228] iwlwifi :04:00.0:
0x41C0497E | beacon time
Aug  6 09:00:07 debiant kernel: [876895.326230] iwlwifi :04:00.0:
0x05DC7682 | tsf low
Aug  6 09:00:07 debiant kernel: [876895.326233] iwlwifi :04:00.0:
0x0152 | tsf hi
Aug  6 09:00:07 debiant kernel: [876895.326235] iwlwifi :04:00.0:
0x | time gp1
Aug  6 09:00:07 debiant kernel: [876895.326238] iwlwifi :04:00.0:
0xEF49090D | time gp2
Aug  6 09:00:07 debiant kernel: [876895.326240] iwlwifi :04:00.0:
0x | time gp3
Aug  6 09:00:07 debiant kernel: [876895.326243] iwlwifi :04:00.0:
0x00010853 | uCode version
Aug  6 09:00:07 debiant kernel: [876895.326245] iwlwifi :04:00.0:
0x0054 | hw version
Aug  6 09:00:07 debiant kernel: [876895.326248] iwlwifi :04:00.0:
0x00488704 | board version
Aug  6 09:00:07 debiant kernel: [876895.326250] iwlwifi :04:00.0:
0x0249001C | hcmd
Aug  6 09:00:07 debiant kernel: [876895.326253] iwlwifi :04:00.0:
0xAFF73000 | isr0
Aug  6 09:00:07 debiant kernel: [876895.326255] iwlwifi :04:00.0:
0x110BE000 | isr1
Aug  6 09:00:07 debiant kernel: [876895.326258] iwlwifi :04:00.0:
0x001A | isr2
Aug  6 09:00:07 debiant kernel: [876895.326260] iwlwifi :04:00.0:
0x044310C3 | isr3
Aug  6 09:00:07 debiant kernel: [876895.326263] iwlwifi :04:00.0:
0x10800112 | isr4
Aug  6 09:00:07 debiant kernel: [876895.326265] iwlwifi :04:00.0:
0x6226 | isr_pref
Aug  6 09:00:07 debiant kernel: [876895.326268] iwlwifi :04:00.0:
0x00D4 | wait_event
Aug  6 09:00:07 debiant kernel: [876895.326270] iwlwifi :04:00.0:
0x0040 | l2p_control
Aug  6 09:00:07 debiant kernel: [876895.326273] iwlwifi :04:00.0:
0x0007 | l2p_duration
Aug  6 09:00:07 debiant kernel: [876895.326276] iwlwifi :04:00.0:
0x | l2p_mhvalid
Aug  6 09:00:07 debiant kernel: [876895.326278] iwlwifi :04:00.0:
0x0005 | l2p_addr_match
Aug  6 09:00:07 debiant kernel: [876895.326281] iwlwifi :04:00.0:
0x02121704 | lmpm_pmg_sel
Aug  6 09:00:07 debiant kernel: [876895.326283] iwlwifi :04:00.0:
0x1FE4C8C8 | timestamp
Aug  6 09:00:07 debiant kernel: [876895.326286] iwlwifi :04:00.0:
0x0100 | flow_handler
Aug  6 09:00:07 debiant kernel: [876895.326372] iwlwifi :04:00.0: Start
IWL Event Log Dump: display last 20 entries
Aug  6 09:00:07 debiant kernel: [876895.326404] iwlwifi :04:00.0:
EVT_LOGT:4013537338:0x0113:0106
Aug  6 09:00:07 debiant kernel: [876895.326435] iwlwifi :04:00.0:
EVT_LOGT:4013537340:0x:0302
Aug  6 09:00:07 debiant kernel: [876895.326467] iwlwifi :04:00.0:
EVT_LOGT:4013537366:0x0440:0323
Aug  6 09:00:07 debiant kernel: [876895.326482] iwlwifi :04:00.0:
EVT_LOGT:4013537370:0x:0355
Aug  6 09:00:07 debiant kernel: [876895.326515] iwlwifi :04:00.0:
EVT_LOGT:4013537371:0x0480:0367
Aug  6 09:00:07 debiant kernel: [876895.326546] iwlwifi :04:00.0:
EVT_LOGT:4013539198:0x0113:0106
Aug  6 09:00:07 debiant kernel: [876895.326578] iwlwifi :04:00.0:
EVT_LOGT:4013539200:0x:0302
Aug  6 09:00:07 debiant kernel: [876895.326610] iwlwifi :04:00.0:
EVT_LOGT:4013539223:0x:0355
Aug  6 09:00:07 debiant kernel: [876895.326625] iwlwifi :04:00.0:
EVT_LOGT:4013539294:0x0113:0106
Aug  6 09:00:07 debiant kernel: [876895.326657] iwlwifi :04:00.0:
EVT_LOGT:4013539296:0x:0302
Aug  6 09:00:07 debiant kernel: [876895.326689] iwlwifi :04:00.0:
EVT_LOGT:4013539322:0x0440:0323
Aug  6 09:00:07 debiant kernel: [876895.326721] iwlwifi :04:00.0:
EVT_LOGT:4013539326:0x:0355
Aug  6 09:00:07 debiant kernel: [876895.326752] iwlwifi :04:00.0:
EVT_LOGT:4013539327:0x0480:0367
Aug  6 

Bug#892102: epoll_wait.c no such file or directory?

[sixerjman]

I generated a core dump with gdb on the running instance of inetd. Here is
the backtrace:

#0  0x7f910f0997b7 in epoll_wait (epfd=3, events=0x55df220e8ad0,
maxevents=32, timeout=2497)
at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
30 ../sysdeps/unix/sysv/linux/epoll_wait.c: No such file or directory.
(gdb) bt full
#0  0x7f910f0997b7 in epoll_wait (epfd=3, events=0x55df220e8ad0,
maxevents=32, timeout=2497)
at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
resultvar = 18446744073709551612
sc_ret = 
#1  0x7f910f235408 in ?? () from
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
No symbol table info available.
#2  0x7f910f22b329 in event_base_loop () from
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
No symbol table info available.
#3  0x55df219e8a12 in ?? ()
No symbol table info available.
#4  0x7f910efc409b in __libc_start_main (main=0x55df219e8680, argc=1,
argv=0x7ffd231f48a8, init=, fini=,
rtld_fini=, stack_end=0x7ffd231f4898) at
../csu/libc-start.c:308
self = 
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0,
-2537960699707725357, 94416830106576, 140725192706208, 0, 0,
-8609933386768389677,
-8621291608355968557}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x7ffd231f48b8, 0x7f910f4d1190}, data = {prev = 0x0,
  cleanup = 0x0, canceltype = 589252792}}}
not_first_call = 
#5  0x55df219e8bfa in ?? ()
No symbol table info available.

Bug#935915: Same problem reported on ubuntu

[sixerjman]

https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1034392

The original bug was reported in 2012 but recent comments are from 2018 and
2019:

Steve Dodd (anarchetic)  wrote on
2018-07-07: #17


I am seeing this on a box running 14.04 (acng 0.7.26-1ubuntu0.1) - nothing
leapt out when I strace'd, I will try again and save to file. I am also not
sure that strace-ing didn't "unstick" the acng process, which would be very
odd ..

I will also try backporting a more recent acng and see if problem still
exists,
Andres Jalinton (andresj551)  wrote on
2019-01-24: #18


   - logfile2
   

Edit
   

(234.2
   KiB, text/plain)

I'm running an Ubuntu 14.04 and Ubuntu 16.04.5 serving the DEB cache with
apt-cacher-ng.

The download of files to the older (and tested in other distros debian
based) is very slow (10 to 50 kbps)

Attached are the strace files.

Bug#935915: CPU load, kernel IP filters not a factor

[sixerjman]

CPU load - Not a factor, utilization is almost always less than 30% when
tests are run. Nothing is running in the GUI,
of the acng server, not even a browser.  The out of tree module is the
'netatop' module which works inside atop
and it hardly uses any cycles. The module is loaded and the netatop daemon
is running all the time, and CPU utilization
hasn't budged past 5% all day.

Kernel IP filters - None are running as far as I can tell, i.e. no firewall
is running.

Things were going well until a few weeks ago IIRC, but since it slowed to a
crawl I had to revert the few clients I have
to direct downloads. Using the same mirror as the acng server, the 'apt
update / upgrade' cycle elapsed time
immediated reverted back to the order of seconds from order of minutes.
the order of seconds from the order of minutes immediately.

The apt-cacher-err.log shows the debug trace of an 'apt-get update' from a
client. Note the
elapsed time is a tad over 3 minutes. From the same client an 'apt-get
update' took about 9 seconds:

time sudo apt-get update

<* 27 gets *>

real 0m9.601s
user 0m10.649s
sys 0m1.819s

Bug#892102: Need a core dump

[sixerjman]

The inetd daemon runs as a systemd service, but lately I've been getting
the following message when it crashes with SIGABRT:

systemd-coredump[15585]: Resource limits disable core dumping for process
13098 (inetd).

How can the system be configured to allow a core dump to be taken? I have
core dumps
configured to 'unlimited' in '/etc/security/limits.conf', so I don't
understand why systemd-coredump
refuses to actually do it's job and take a core dump which can be analyzed
later.

Another question is how to the debugging symbols for libevent. There used
to be a package
'libevent-dbg' which provided the debug symbols but it is not available in
the testing ('bullseye')
or unstable distributions.

Bug#935915: apt-cacher-ng: Extremely low transfer rate on LAN

[sixerjman]

Package: apt-cacher-ng
Version: 3.2-2
Severity: important

Dear Maintainer,

   * What led up to the situation?
Very low transfer speed for clients on LAN
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
apt update / apt upgrade
   * What was the outcome of this action?
Approximately 1/10 transfer rate for packages which had been previously
downloaded to the server (same architecture AMD64)
   * What outcome did you expect instead?
LAN speed equivalent to speed from direct download from same Debian mirror

Attached is a compressed 'apt-cacher-ng.err' log of the apt update






-- Package-specific info:

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

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.73
ii  dpkg   1.19.7
ii  libbz2-1.0 1.0.6-9.2
ii  libc6  2.28-10
ii  libgcc11:9.2.1-4
ii  liblzma5   5.2.4-1+b1
ii  libssl1.1  1.1.1c-1
ii  libstdc++6 9.2.1-4
ii  libsystemd0242-4
ii  libwrap0   7.6.q-28
ii  lsb-base   11.1.0
ii  zlib1g 1:1.2.11.dfsg-1+b1

apt-cacher-ng recommends no packages.

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.7-4+b1
pn  doc-base  
ii  libfuse2  2.9.9-1

-- Configuration Files:
/etc/apt-cacher-ng/acng.conf changed:
CacheDir: /var/cache/apt-cacher-ng
LogDir: /var/log/apt-cacher-ng
SupportDir: /usr/lib/apt-cacher-ng
Remap-debrep: file:deb_mirror*.gz /debian ; file:backends_debian # Debian
Archives
Remap-uburep: file:ubuntu_mirrors /ubuntu ; file:backends_ubuntu # Ubuntu
Archives
Remap-cygwin: file:cygwin_mirrors /cygwin # ; file:backends_cygwin #
incomplete, please create this file or specify preferred mirrors here
Remap-sfnet:  file:sfnet_mirrors # ; file:backends_sfnet # incomplete,
please create this file or specify preferred mirrors here
Remap-alxrep: file:archlx_mirrors /archlinux # ; file:backend_archlx # Arch
Linux
Remap-fedora: file:fedora_mirrors # Fedora Linux
Remap-epel:   file:epel_mirrors # Fedora EPEL
Remap-slrep:  file:sl_mirrors # Scientific Linux
Remap-gentoo: file:gentoo_mirrors.gz /gentoo ; file:backends_gentoo #
Gentoo Archives
Remap-secdeb: security.debian.org ; security.debian.org
deb.debian.org/debian-security
ReportPage: acng-report.html
ExThreshold: 4
Debug:3
LocalDirs: acng-doc /usr/share/doc/apt-cacher-ng
PassThroughPattern: ^repo\.nordvpn\.com:443$

/etc/apt-cacher-ng/security.conf [Errno 13] Permission denied:
'/etc/apt-cacher-ng/security.conf'


apt-cacher-ng.err.gz
Description: application/gzip

Bug#892102: Valgrind options needed

[sixerjman]

The default 'memcheck' only shows the same stack trace as 'coredumpctl'.
Which
valgrind tool(s) and options should I use?

Bug#892102: Running systemd inetd service under valgrind now

[sixerjman]

sctl cat inetd
# /etc/systemd/system/inetd.service
[Unit]
Description=Internet superserver
Documentation=man:inetd(8)
After=network-online.target
Wants=network-online.target
ConditionPathExists=/etc/inetd.conf

[Service]
Type=notify
ExecStart=/usr/bin/valgrind /usr/sbin/inetd
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure
WatchdogSec=5
KillMode=process

[Install]
WantedBy=multi-user.target

Bug#892102: Possible correlation with cron job(s) run on the hour

[sixerjman]

Looking at the times it seems more likely that hourly cron jobs (logcheck,
sysstat, backup jobs
via backuppc) are causing system stress. Investigating devising a trap via
valgrind or some
other mechanism because the system load is different throughout the day so
I can't really
say which hour the event will occur for sure.

Bug#892102: Watchdog timeout expiring

[sixerjman]

I'll give it a whirl in a likely scenario (i.e. resume from suspend).

On Sun, Aug 4, 2019 at 5:02 PM Marco d'Itri  wrote:

> On Aug 04, Bálint Réczey  wrote:
>
> > This seems to be an issue in inetd's watchdog handling. What do you
> think?
> I suspect that the watchdog is being triggered because at that point the
> internal state of libevent is broken.
>
> It is implemented here, and there is not much that could go wrong unless
> you can spot any misuse on libevent on my part:
>
>
> https://salsa.debian.org/md/openbsd-inetd/blob/master/debian/patches/sd_daemon#L38
>
> sixerjman: can you still reproduce this bug? If you can then please try
> running inetd in valgrind.
>
> --
> ciao,
> Marco
>

Bug#892102: Watchdog timeout expiring

[sixerjman]

Hmmm, it looks like inetd watchdog timer is expiration (systemd or inet's?)
is the root cause:

-- Logs begin at Sat 2019-07-06 06:34:04 EDT, end at Sun 2019-08-04
07:55:01 EDT. --
Jul 23 08:37:26 debiant systemd[1]: Starting Internet superserver...
Jul 23 08:37:27 debiant systemd[1]: Started Internet superserver.
Jul 23 19:00:05 debiant systemd[1]: inetd.service: Watchdog timeout (limit
5s)!
Jul 23 19:00:05 debiant systemd[1]: inetd.service: Killing process 1628
(inetd) with signal SIGABRT.
Jul 23 19:00:07 debiant systemd-coredump[3087]: Process 1628 (inetd) of
user 0 dumped core.
Jul 23 19:00:07 debiant systemd[1]: inetd.service: Main process exited,
code=dumped, status=6/ABRT
Jul 23 19:00:07 debiant systemd[1]: inetd.service: Failed with result
'watchdog'.
Jul 23 19:00:08 debiant systemd[1]: inetd.service: Service RestartSec=100ms
expired, scheduling restart.
Jul 23 19:00:08 debiant systemd[1]: inetd.service: Scheduled restart job,
restart counter is at 1.
Jul 23 19:00:08 debiant systemd[1]: Stopped Internet superserver.
Jul 23 19:00:08 debiant systemd[1]: Starting Internet superserver...
Jul 23 19:00:08 debiant systemd[1]: Started Internet superserver.
Jul 24 19:19:23 debiant inetd[3105]: could not getpeername
Jul 24 19:19:23 debiant inetd[3105]: could not getpeername
Jul 24 19:19:23 debiant inetd[3105]: could not getpeername
Jul 24 20:00:07 debiant systemd[1]: inetd.service: Watchdog timeout (limit
5s)!
Jul 24 20:00:07 debiant systemd[1]: inetd.service: Killing process 3105
(inetd) with signal SIGABRT.
Jul 24 20:00:08 debiant systemd-coredump[8689]: Process 3105 (inetd) of
user 0 dumped core.
Jul 24 20:00:08 debiant systemd[1]: inetd.service: Main process exited,
code=dumped, status=6/ABRT
Jul 24 20:00:08 debiant systemd[1]: inetd.service: Failed with result
'watchdog'.
Jul 24 20:00:08 debiant systemd[1]: inetd.service: Service RestartSec=100ms
expired, scheduling restart.
Jul 24 20:00:08 debiant systemd[1]: inetd.service: Scheduled restart job,
restart counter is at 2.
Jul 24 20:00:08 debiant systemd[1]: Stopped Internet superserver.
Jul 24 20:00:08 debiant systemd[1]: Starting Internet superserver...
Jul 24 20:00:08 debiant systemd[1]: Started Internet superserver.
Jul 27 18:00:05 debiant systemd[1]: inetd.service: Watchdog timeout (limit
5s)!
Jul 27 18:00:05 debiant systemd[1]: inetd.service: Killing process 8701
(inetd) with signal SIGABRT.
Jul 27 18:00:08 debiant systemd-coredump[5111]: Process 8701 (inetd) of
user 0 dumped core.
Jul 27 18:00:08 debiant systemd[1]: inetd.service: Main process exited,
code=dumped, status=6/ABRT
Jul 27 18:00:08 debiant systemd[1]: inetd.service: Failed with result
'watchdog'.
Jul 27 18:00:08 debiant systemd[1]: inetd.service: Service RestartSec=100ms
expired, scheduling restart.
Jul 27 18:00:08 debiant systemd[1]: inetd.service: Scheduled restart job,
restart counter is at 3.
Jul 27 18:00:08 debiant systemd[1]: Stopped Internet superserver.
Jul 27 18:00:08 debiant systemd[1]: Starting Internet superserver...
Jul 27 18:00:08 debiant systemd[1]: Started Internet superserver.
Jul 27 20:00:07 debiant systemd[1]: inetd.service: Watchdog timeout (limit
5s)!
Jul 27 20:00:07 debiant systemd[1]: inetd.service: Killing process 5129
(inetd) with signal SIGABRT.
Jul 27 20:00:08 debiant systemd-coredump[17389]: Process 5129 (inetd) of
user 0 dumped core.
Jul 27 20:00:08 debiant systemd[1]: inetd.service: Main process exited,
code=dumped, status=6/ABRT
Jul 27 20:00:08 debiant systemd[1]: inetd.service: Failed with result
'watchdog'.
Jul 27 20:00:08 debiant systemd[1]: inetd.service: Service RestartSec=100ms
expired, scheduling restart.
Jul 27 20:00:08 debiant systemd[1]: inetd.service: Scheduled restart job,
restart counter is at 4.
Jul 27 20:00:08 debiant systemd[1]: Stopped Internet superserver.
Jul 27 20:00:08 debiant systemd[1]: Starting Internet superserver...
Jul 27 20:00:09 debiant systemd[1]: Started Internet superserver.
Jul 28 08:00:06 debiant systemd[1]: inetd.service: Watchdog timeout (limit
5s)!
Jul 28 08:00:06 debiant systemd[1]: inetd.service: Killing process 17405
(inetd) with signal SIGABRT.
Jul 28 08:00:08 debiant systemd-coredump[1974]: Process 17405 (inetd) of
user 0 dumped core.
Jul 28 08:00:08 debiant systemd[1]: inetd.service: Main process exited,
code=dumped, status=6/ABRT
Jul 28 08:00:08 debiant systemd[1]: inetd.service: Failed with result
'watchdog'.
Jul 28 08:00:08 debiant systemd[1]: inetd.service: Service RestartSec=100ms
expired, scheduling restart.
Jul 28 08:00:08 debiant systemd[1]: inetd.service: Scheduled restart job,
restart counter is at 5.
Jul 28 08:00:08 debiant systemd[1]: Stopped Internet superserver.
Jul 28 08:00:08 debiant systemd[1]: Starting Internet superserver...
Jul 28 08:00:08 debiant systemd[1]: Started Internet superserver.
Jul 28 16:00:07 debiant systemd[1]: inetd.service: Watchdog timeout (limit
5s)!
Jul 28 16:00:07 debiant systemd[1]: inetd.service: Killing process 1983
(inetd) with signal SIGABRT.
Jul 28 16:00:09 debiant 

Bug#892102: Reproduction

[sixerjman]

Sorry, I can find no correlation of the segfaults to any specific events
other than
maybe sleep / resume cycles. This morning I just resumed from sleep and
inetd
was fine.

Bug#892102: inetd coredumpctl info

[sixerjman]

   PID: 21014 (inetd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 6 (ABRT)
 Timestamp: Tue 2019-07-09 08:00:05 EDT (3 weeks 1 days ago)
  Command Line: /usr/sbin/inetd
Executable: /usr/sbin/inetd
 Control Group: /system.slice/inetd.service
  Unit: inetd.service
 Slice: system.slice
   Boot ID: acccaeafcbe0474ea3eea5fb4708e76f
Machine ID: 891bd6059e0d4cecae7b4ea3aac6b9fc
  Hostname: debiant
   Storage: none
   Message: Process 21014 (inetd) of user 0 dumped core.

   PID: 28590 (inetd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 6 (ABRT)
 Timestamp: Sun 2019-07-14 08:00:01 EDT (2 weeks 3 days ago)
  Command Line: /usr/sbin/inetd
Executable: /usr/sbin/inetd
 Control Group: /system.slice/inetd.service
  Unit: inetd.service
 Slice: system.slice
   Boot ID: acccaeafcbe0474ea3eea5fb4708e76f
Machine ID: 891bd6059e0d4cecae7b4ea3aac6b9fc
  Hostname: debiant
   Storage:
/var/lib/systemd/coredump/core.inetd.0.acccaeafcbe0474ea3eea5fb4708e76f.28590.156310560100.lz4
(inaccessible)
   Message: Process 28590 (inetd) of user 0 dumped core.

Stack trace of thread 28590:
#0  0x7fb71bea17b7 epoll_wait (libc.so.6)
#1  0x7fb71c037408 n/a (libevent-2.1.so.6)
#2  0x7fb71c02d329 event_base_loop (libevent-2.1.so.6)
#3  0x558fe556fa12 n/a (inetd)
#4  0x7fb71bdcc09b __libc_start_main (libc.so.6)
#5  0x558fe556fbfa n/a (inetd)

   PID: 29173 (inetd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 6 (ABRT)
 Timestamp: Sun 2019-07-14 18:00:08 EDT (2 weeks 2 days ago)
  Command Line: /usr/sbin/inetd
Executable: /usr/sbin/inetd
 Control Group: /system.slice/inetd.service
  Unit: inetd.service
 Slice: system.slice
   Boot ID: acccaeafcbe0474ea3eea5fb4708e76f
Machine ID: 891bd6059e0d4cecae7b4ea3aac6b9fc
  Hostname: debiant
   Storage:
/var/lib/systemd/coredump/core.inetd.0.acccaeafcbe0474ea3eea5fb4708e76f.29173.156314160800.lz4
(inaccessible)
   Message: Process 29173 (inetd) of user 0 dumped core.

Stack trace of thread 29173:
#0  0x7f833daa57b7 epoll_wait (libc.so.6)
#1  0x7f833dc3b408 n/a (libevent-2.1.so.6)
#2  0x7f833dc31329 event_base_loop (libevent-2.1.so.6)
#3  0x55ae6a128a12 n/a (inetd)
#4  0x7f833d9d009b __libc_start_main (libc.so.6)
#5  0x55ae6a128bfa n/a (inetd)

   PID: 1520 (inetd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 6 (ABRT)
 Timestamp: Mon 2019-07-15 08:00:05 EDT (2 weeks 2 days ago)
  Command Line: /usr/sbin/inetd
Executable: /usr/sbin/inetd
 Control Group: /system.slice/inetd.service
  Unit: inetd.service
 Slice: system.slice
   Boot ID: d6b821853be945a18e789f97bcc9110a
Machine ID: 891bd6059e0d4cecae7b4ea3aac6b9fc
  Hostname: debiant
   Storage: none
   Message: Process 1520 (inetd) of user 0 dumped core.

   PID: 7636 (inetd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 6 (ABRT)
 Timestamp: Mon 2019-07-15 17:00:07 EDT (2 weeks 1 days ago)
  Command Line: /usr/sbin/inetd
Executable: /usr/sbin/inetd
 Control Group: /system.slice/inetd.service
  Unit: inetd.service
 Slice: system.slice
   Boot ID: d6b821853be945a18e789f97bcc9110a
Machine ID: 891bd6059e0d4cecae7b4ea3aac6b9fc
  Hostname: debiant
   Storage: none
   Message: Process 7636 (inetd) of user 0 dumped core.

   PID: 25004 (inetd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 6 (ABRT)
 Timestamp: Mon 2019-07-15 19:00:01 EDT (2 weeks 1 days ago)
  Command Line: /usr/sbin/inetd
Executable: /usr/sbin/inetd
 Control Group: /system.slice/inetd.service
  Unit: inetd.service
 Slice: system.slice
   Boot ID: d6b821853be945a18e789f97bcc9110a
Machine ID: 891bd6059e0d4cecae7b4ea3aac6b9fc
  Hostname: debiant
   Storage: none
   Message: Process 25004 (inetd) of user 0 dumped core.

   PID: 3482 (inetd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 6 (ABRT)
 Timestamp: Tue 2019-07-16 12:00:07 EDT (2 weeks 1 days ago)
  Command Line: /usr/sbin/inetd
Executable: /usr/sbin/inetd
 Control Group: /system.slice/inetd.service
  Unit: inetd.service
 Slice: system.slice
   Boot ID: d6b821853be945a18e789f97bcc9110a
Machine ID: 891bd6059e0d4cecae7b4ea3aac6b9fc
  Hostname: debiant
   Storage: none
   Message: Process 3482 (inetd) of user 0 dumped core.

   PID: 6536 (inetd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 6 (ABRT)
 Timestamp: Wed 2019-07-17 10:00:07 EDT (2 weeks 0 

Bug#933202: Additional information

[sixerjman]

kernel: [155898.814801] xfdesktop[7896]: segfault at 10 ip b7052d52 sp
bfb1a070 error 4 in
+libglib-2.0.so.0.5800.3[b700+82000]

Bug#933202: xfdesktop4: SEGV in g_slice_alloc

[sixerjman]

Package: xfdesktop4
Version: 4.12.4-2
Severity: normal

coredumpctl info output:

Storage:
/var/lib/systemd/coredump/core.xfdesktop.1000.78062c2cbcad4f70a20e427190921195.7896.156423115200.lz4
   Message: Process 7896 (xfdesktop) of user 1000 dumped core.

Stack trace of thread 7896:
#0  0xb7052d52 g_slice_alloc (libglib-2.0.so.0)
#1  0xb703056b g_list_prepend (libglib-2.0.so.0)
#2  0xb7d752a0 n/a (libwnck-1.so.22)
#3  0xb7d762f6 n/a (libwnck-1.so.22)
#4  0xb7034e65 g_main_context_dispatch
(libglib-2.0.so.0)
#5  0xb7035269 n/a (libglib-2.0.so.0)
#6  0xb7035609 g_main_loop_run (libglib-2.0.so.0)
#7  0xb7918675 gtk_main (libgtk-x11-2.0.so.0)
#8  0x00447847 n/a (xfdesktop)
#9  0x00447d2e n/a (xfdesktop)
#10 0xb70315bf n/a (libglib-2.0.so.0)
#11 0xb703200a n/a (libglib-2.0.so.0)
#12 0xb7034eee g_main_context_dispatch
(libglib-2.0.so.0)
#13 0xb7035269 n/a (libglib-2.0.so.0)
#14 0xb7035314 g_main_context_iteration
(libglib-2.0.so.0)
#15 0xb72d88c3 g_application_run (libgio-2.0.so.0)
#16 0x00448e02 xfdesktop_application_run (xfdesktop)
#17 0x0043bffb main (xfdesktop)
#18 0xb6e03b41 __libc_start_main (libc.so.6)
#19 0x0043c047 _start (xfdesktop)

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?
 Happens sporadically

* What exactly did you do (or not do) that was effective (or
 ineffective)?
  Nothing, xfdesktop recovers, restarts

* What was the outcome of this action?
N/A

* What outcome did you expect instead?
No crash with accompanying output

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-5-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_US.UTF-8), LANGUAGE=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)
LSM: AppArmor: enabled

Versions of packages xfdesktop4 depends on:
ii  exo-utils0.12.6-1
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libdbus-1-3  1.12.16-1
ii  libdbus-glib-1-2 0.110-4
ii  libexo-1-0   0.12.6-1
ii  libgarcon-1-00.6.3-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-3
ii  libgtk2.0-0  2.24.32-3
ii  libnotify4   0.7.7-4
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libwnck222.30.7-6
ii  libx11-6 2:1.6.7-1
ii  libxfce4ui-1-0   4.12.1-3
ii  libxfce4util74.12.1-3
ii  libxfconf-0-24.12.1-1
ii  xfdesktop4-data  4.12.4-2

Versions of packages xfdesktop4 recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.16-1
ii  dbus-x11 [dbus-session-bus]   1.12.16-1
ii  librsvg2-common   2.44.10-2.1
pn  tumbler   
ii  xdg-user-dirs 0.17-2

Versions of packages xfdesktop4 suggests:
pn  menu  

-- no debconf information

Bug#928821: Section 3.1 'An overview of the boot strap process' should reference UEFI

[sixerjman]

Package: debian-reference
Source: debian-reference
Severity: wishlist
Tags: upstream

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?
Reading Section 3.1 'Bootstrap Process'

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
N/A

   * What was the outcome of this action?
No information on the bootstrap process for modern UEFI enabled
machines

   * What outcome did you expect instead?
Short segment about the bootstrap process on UEFI machines

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.19.0-4-amd64 (SMP w/2 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), LANGUAGE=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)
LSM: AppArmor: enabled

Bug#925200: missing warning for wrong path

[sixerjman]

Thanks, I'll take a look.

On Thu, Mar 21, 2019 at 10:11 AM Osamu Aoki  wrote:

> control: retitle -1 check doc-base-file-references-wrong-path
> control: tags -1 + patch
>
> Excuse me, lintian warning was correct.
>
> But after checking this bug of mine, I came up with a possible
> improvement for the lintian check.  I made a proof-of-concept patch
> here.
>
> Package: lintian
> Version: 2.11.0
> Severity: normal
>
> Requested action for /usr/share/lintian/checks/menus.pm:
> 
>
>* add sanity check for the file path to be usr/share/doc/*
>  or /usr/share/info/*.
>  --> /usr/share/lintian/checks/menus.pm before line 353
>  add file path matching rule and produce error message as
>  needed.
>
> Attached a proof of concept patch:
>
> Note:
> I didn't run perltidy since that changed many other parts.
>
> I still didn't figure out how the test suite within lintian works.
> This code is tested by installing it to the target pat manually ;-)
>
> Osamu
>
> PS: I at least see that libreoffice-help-en-us should fail this new
> test.  It shouldn't list /usr/share/libreoffice/help/media/* which is
> outside of /usr/share/doc/*.  Instead, it should create symlink using
> dh_link:
>   /usr/share/doc//help -> /usr/share/libreoffice/help
> Then use this new path for doc-base.
>
> PS sixerjman: I think your concern is addressed with lintian now.
>

Bug#924686: debian-reference

[sixerjman]

Source: debian-reference
Version: 7.5.2
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?
   Trying to access debian-reference from dwww
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Click on DR link under the 'Debian' section of dwww
   * What was the outcome of this action?
   dwww denied access to directory /usr/share
   * What outcome did you expect instead?
   DR HTML index

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores)
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)
LSM: AppArmor: enabled

Bug#803342: I switched to dwww

[sixerjman]

No problems experieced with dwww's cron daily or weekly jobs.

Bug#864079: I am onboard the team to help package BackupPC V4

[sixerjman]

I have been tracking and using the upstream version of BackupPC V4 for
awhile and would
like to help out as a set of eyes and testing. I am currently using V4.2.1
but will be upgrading
to V4.3.0 this weekend. Thanks for all your efforts with this marvelous
software backup suite!

Bug#921024: Apache and apache-htcacheclean services fail to start after this update

[sixerjman]

straces on the way

Bug#912749: Correlation with upgrade

[sixerjman]

Seems to occur on the first tmpfiles clean run after upgrade. Version
0.8.8.3 (March 2018) changelog
has this:

- speech-dispatcher.tmpfile: Add /var/run links in systemd case.

Bug#912749: These warnings occur with annoying regularity

[sixerjman]

Even after performing the prescribed fix, after a few days or weeks the
warning are back.

Bug#914495: Fixed in linux-image-4.19

[sixerjman]

Just installed it from testing distribution and no black screen, modeset
worked fine.

Bug#873075: Version 4.3.0 Release notes

[sixerjman]

https://github.com/backuppc/backuppc/releases/tag/4.3.0

Bug#873075: Fedora just released V4.3.0-1

[sixerjman]

Many enhancements and bug fixes included:

http://backuppc.github.io/backuppc/index.html

Bug#914495: Bug appearing on Intel GM965

[sixerjman]

I incorrectly stated there was no problem on one of my Debian machines with
video adapter

Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller
(primary) (rev 0c).

There is black screen and lightdm failed to start after this:

BUG: unable to handle kernel NULL pointer dereference at 0004
[Tue Dec  4 12:30:21 2018] *pdpt = 36555001 *pde = 
[Tue Dec  4 12:30:21 2018] Oops:  [#1] SMP
[Tue Dec  4 12:30:21 2018] CPU: 0 PID: 316 Comm: systemd-udevd Not tainted
4.18.0-3-686-pae #1 Debian 4.18.20-2
[Tue Dec  4 12:30:21 2018] Hardware name: Dell Inc. Inspiron 1520
 /0KY767, BIOS A03 08/16/2007
[Tue Dec  4 12:30:21 2018] EIP: gen4_render_ring_flush+0x52/0x100 [i915]

Bug#914495: More evidence that the gen4 adapter commit is at fault

[sixerjman]

I have 3 Debian machines in the lab, and two booted 4.18.3 fine. One has a
Radeon GPU, the other is an Intel GM965. The one that gave me the black
screen at boot is:

lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller (rev 07)

Bug#914495: nomodeset enabled boot

[sixerjman]

But the graphics mode is low res (1280x768). Also, 'nomodeset' is no longer
documented in the kernel parameters doc (
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt).

Bug#822323: I had to enable cgi(d) module to get this working

[sixerjman]

sudo a2enmod cgi
Your MPM seems to be threaded. Selecting cgid instead of cgi.
Enabling module cgid.
To activate the new configuration, you need to run:
  systemctl restart apache2

Bug#873075: backuppc-xs must be rebuilt after perl-base upgrade from 5.26 ---> 5.28

[sixerjman]

Recent testing updates installed perl-base 5.28 which breaks the unofficial
backuppc-xs.deb
on https://github.com/backuppc/backuppc/wiki/Build-Your-Own-Packages. The
solution
is to uninstall backuppc-xs, install the perl updates, then build a new
backuppc-xs.deb
using the instructions on the page.

Bug#882504: I get 'network unreachable failures' after resume from suspend

[sixerjman]

Using apt-cacher-ng, after resume I see:

Oct 05 04:30:58 debiant apt.systemd.daily[21976]: Reading package lists...
Oct 05 04:30:58 debiant apt.systemd.daily[21976]: W: Failed to fetch
http://localhost:3142/debian.csail.mit.edu/debian/dists/testing/InRelease
Oct 05 04:30:58 debiant apt.systemd.daily[21976]: W: Failed to fetch
http://localhost:3142/debian.csail.mit.edu/debian/dists/unstable/InReleas
Oct 05 04:30:58 debiant apt.systemd.daily[21976]: W: Failed to fetch
http://localhost:3142/security.debian.org/dists/testing/updates/InRelease
Oct 05 04:30:58 debiant apt.systemd.daily[21976]: W: Failed to fetch
http://deb-multimedia.org/dists/testing/InRelease  Temporary failure reso
Oct 05 04:30:58 debiant apt.systemd.daily[21976]: W: Some index files
failed to download. They have been ignored, or old ones used instead.

The only service I have enabled is NetworkManager, and looking at the code
it seems like the '--timeout' parameter passed to nm-online should read
'--timeout=30' instead of the two strings in apt-helper.cc:

{"NetworkManager.service", "nm-online", "-q", "--timeout", "30", nullptr},

nm-online failures would not be seen because of the "-" prefix in the
'ExecStartPre' service statement.

Testing with customized service specifying a longer timeout (i.e. 60
seconds), and without the quiet parm.

Bug#909841: Workaround was to delete failing directory

[sixerjman]

After moving '/usr/local/share/fonts' to a backup location fc-cache ran
successfully. The local font directory (which contained only the .uuid) was
not recreated.

Bug#909841: fc-cache failure preventing dpkg configuration of libreoffice updates

[sixerjman]

Ran into this problem when the aptitude upgrade was interrupted yesterday.
Trying 'dpkg --configure -a' resulted in the following:

dpkg: dependency problems prevent configuration of libreoffice-core:
 libreoffice-core depends on fontconfig; however:
  Package fontconfig is not configured yet.

dpkg: error processing package libreoffice-core (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-calc:
 libreoffice-calc depends on libreoffice-core (= 1:6.1.2-1); however:
  Package libreoffice-core is not configured yet.

dpkg: error processing package libreoffice-calc (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-gtk2:
 libreoffice-gtk2 depends on libreoffice-core (= 1:6.1.2-1); however:
  Package libreoffice-core is not configured yet.

...etc. for all libreoffice products.  fc-cache produced
'/var/log/fontconfig.log' which is attached.
/usr/share/fonts: caching, new cache contents: 0 fonts, 9 dirs
/usr/share/fonts/X11: caching, new cache contents: 0 fonts, 6 dirs
/usr/share/fonts/X11/100dpi: caching, new cache contents: 358 fonts, 0 dirs
/usr/share/fonts/X11/75dpi: caching, new cache contents: 358 fonts, 0 dirs
/usr/share/fonts/X11/Type1: caching, new cache contents: 8 fonts, 0 dirs
/usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/X11/encodings/large: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/X11/misc: caching, new cache contents: 89 fonts, 0 dirs
/usr/share/fonts/X11/util: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cMap: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap: caching, new cache contents: 0 fonts, 5 dirs
/usr/share/fonts/cmap/adobe-cns1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-gb1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-japan1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-japan2: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-korea1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/eot: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/eot/font-awesome: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/opentype: caching, new cache contents: 0 fonts, 2 dirs
/usr/share/fonts/opentype/font-awesome: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/opentype/linux-libertine: caching, new cache contents: 13 fonts, 0 dirs
/usr/share/fonts/svg: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/svg/font-awesome: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/truetype: caching, new cache contents: 0 fonts, 12 dirs
/usr/share/fonts/truetype/crosextra: caching, new cache contents: 8 fonts, 0 dirs
/usr/share/fonts/truetype/dejavu: caching, new cache contents: 22 fonts, 0 dirs
/usr/share/fonts/truetype/droid: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/font-awesome: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/freefont: caching, new cache contents: 12 fonts, 0 dirs
/usr/share/fonts/truetype/gentium: caching, new cache contents: 4 fonts, 0 dirs
/usr/share/fonts/truetype/gentium-basic: caching, new cache contents: 8 fonts, 0 dirs
/usr/share/fonts/truetype/lato: caching, new cache contents: 18 fonts, 0 dirs
/usr/share/fonts/truetype/liberation: caching, new cache contents: 16 fonts, 0 dirs
/usr/share/fonts/truetype/noto: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/openoffice: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/roboto: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/truetype/roboto/slab: caching, new cache contents: 4 fonts, 0 dirs
/usr/share/fonts/type1: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/type1/gsfonts: caching, new cache contents: 35 fonts, 0 dirs
/usr/share/fonts/woff: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/woff/font-awesome: caching, new cache contents: 1 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts: skipping, no such directory
/usr/local/share/fonts: /usr/local/share/fonts: failed to write cache
caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/X11: skipping, looped directory detected
/usr/share/fonts/cMap: skipping, looped directory detected
/usr/share/fonts/cmap: skipping, looped directory detected
/usr/share/fonts/eot: skipping, looped directory detected
/usr/share/fonts/opentype: skipping, looped directory detected
/usr/share/fonts/svg: skipping, looped directory detected
/usr/share/fonts/truetype: skipping, looped directory detected
/usr/share/fonts/type1: skipping, looped directory detected
/usr/share/fonts/woff: skipping, looped directory detected
/usr/share/fonts/X11/100dpi: skipping, looped directory detected
/usr/share/fonts/X11/75dpi: skipping, looped directory detected

Bug#909260: make deb-pkg output shows fixdep compile / link failure occurs in objtool

[sixerjman]

There are two fixdep.c files, one in basic scripts and the other in tools.
I exported gcc option '-fPIC' in an attempt to get past the linker error,
and it was in effect for the basic script, but was not passed to the tools
script. The follow output is from a log of the build process:

grep fixdep make-kernel.log
  gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes
-Wstrict-prototypes -O2 -fomit-frame-pointer -std=gnu89-fPIC   -o
scripts/basic/fixdep scripts/basic/fixdep.c
... (build proceeds)
make -C /usr/src/linux-source-4.18/tools/build CFLAGS= LDFLAGS=
/usr/src/linux-source-4.18/tools/objtool/fixdep
  HOSTCC   /usr/src/linux-source-4.18/tools/objtool/fixdep.o
  HOSTLD   /usr/src/linux-source-4.18/tools/objtool/fixdep-in.o
  LINK /usr/src/linux-source-4.18/tools/objtool/fixdep
/usr/bin/ld: /usr/src/linux-source-4.18/tools/objtool/fixdep-in.o:
relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making
a PIE object; recompile with -fPIC
make[6]: *** [Makefile:46: /usr/src/linux-source-4.18/tools/objtool/fixdep]
Error 1
make[5]: *** [/usr/src/linux-source-4.18/tools/build/Makefile.include:4:
fixdep] Error 2

Bug#831764: I am on V3.14.0-3 and experiencing this

[sixerjman]

The rsyslog configuration I have has messages, kern and ssh log. I see the
active file(s) as messages | kern | ssh log.1 and all have 'delaycompress'
in the /etc/logrotate.d/ snippet:

/var/log/ssh.log /var/log/messages /var/log/kern.log {
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
invoke-rc.d rsyslog rotate > /dev/null
endscript
}

Bug#873075: Debian packages for V4.2.1 and friends (rsync-bpc / backuppc-xs) available

[sixerjman]

.deb files are available here:

https://github.com/backuppc/backuppc/wiki/Build-Your-Own-Packages

Bug#903217: Problem went away

[sixerjman]

After pool size registered as non-zero I have graphs.

Bug#903217: Still no graphs

[sixerjman]

Even after applying the above mentioned patch. The fact that the pool size
shows at 0 bytes on the status page (pool size is several gigabytes)
probably
has some bearing.

Bug#881632: Try latest version

[sixerjman]

'Stack smashing detected' crashes fixed in last version:

x11vnc (0.9.13-6) unstable; urgency=medium

  * Add two buffer overflow fixes from upstream. Closes: #851496, #859213.
This is a temporary measure, new upstream should be package instead.

 -- Nikita Yushchenko   Mon, 07 May 2018 23:13:43 +0300

Bug#857498: This is fixed in latest version

[sixerjman]

x11vnc (0.9.13-6) unstable; urgency=medium

  * Add two buffer overflow fixes from upstream. Closes: #851496, #859213.
This is a temporary measure, new upstream should be package instead.

 -- Nikita Yushchenko   Mon, 07 May 2018 23:13:43 +0300

Bug#873075: +1 on the packaging suggestion

[sixerjman]

I am moving my backup server from Fedora (currently V4.2.1 with package
rsync-bpc V3.0.9.12) to Debian.