Bug#1076102: xfce4-screenshooter unable to copy to clipboard after a while

[Terrance Hendrik]

Package: xfce4-screenshooter
Version: 1.10.5-1


Running xfce desktop for a long while, by guessing, 1day or longer, with or
without suspend/wakeup.

Launch xfce4-screenshooter, capture whatever region, at whatever dalay,
then select `Copy to the clipboard`, click OK. Clipboard has no image. but
/tmp/ has a newly created `Screenshot__.png`

Bug#1071157: www.debian.org: securing debian manual: broken links

[Hendrik Jaeger]

Package: www.debian.org
Severity: minor
X-Debbugs-Cc: debian-b...@henk.geekmail.org

Dear Maintainer,

   * What led up to the situation?

Collecting information on SysRq.
Followed by trying to find information how to report issues with the 
documentation.

   * What was the outcome of this action?

For both tasks: stumble over broken links.

   * What outcome did you expect instead?

Working links.


https://www.debian.org/doc/manuals/securing-debian-manual/restrict-sysrq.en.html
 has the following text:
»For more information, read security chapter in the Remote Serial Console 
HOWTO, Kernel SysRQ documentation. and the Magic_SysRq_key wikipedia entry.«
The link to the »Kernel SysRQ documentation« is broken and leads to
https://kernel.org/doc/Documentation/sysrq.txt
correct link would probably be
https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html

https://www.debian.org/doc/manuals/securing-debian-manual/changelog.en.html has 
the following text:
»You can download or view the latest version of the Securing Debian Manual from 
the Debian Documentation Project.«
The link to »Debian Documentation Project« leads to
https://www.debian.org/doc/manuals/securing-debian-howto/ which shows »Page not 
found« and should maybe instead lead to
https://www.debian.org/doc/ddp.

It looks like there are possibly more broken links, among other to 
alioth.debian.org.
So generally it might be a good idea to regularly run a broken link checker 
over all docs.

Thanks!

Bug#1070744: /usr/bin/puppet: puts non-regeneratable data in /var/cache

[Hendrik Jaeger]

Package: puppet-agent
Version: 7.23.0-1
Severity: minor
File: /usr/bin/puppet
X-Debbugs-Cc: debian-b...@henk.geekmail.org

Dear Maintainer,

   * What led up to the situation?

I was trying to build an exclude list for my backups and went through the 
content of my filesystems.

   * What was the outcome of this action?

I noticed that there are reports of puppet runs in /var/cache/puppet/reports.

   * What outcome did you expect instead?

I did expect all data in /var/cache and its subdirectories to be regeneratable 
and not contain any information one might want to backup.
According to the FHS in 
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s05.
> /var/cache is intended for cached data from applications. Such data is 
> locally generated as a result of time-consuming I/O or calculation. The 
> application must be able to regenerate or restore the data.

This is not the case for reports:
Puppet can not regenerate the report for a specific run.
Also "cache" usually refers to data that will be reused which is not the case 
for these reports.
/var/log seems a better fit for those.

In my concrete case, it seems suboptimal that these reports are in a directory 
that I would like to exclude from backups because it should not contain 
anything worth backing up anyway as all data in there is supposed to be 
regeneratable and these reports clearly are not.
Under the "Rationale" this use case is even mentioned explicitly:
> The existence of a separate directory for cached data allows system 
> administrators to set different disk and backup policies from other 
> directories in /var.

The argument has been made on IRC that usually reports are not stored locally 
anyway, but it seemed implied that the server would also store the reports in a 
directory named "cache", but outside the FHS in 
/opt/puppetlabs/puppet/cache/reports in the case of a non-debian installation. 
I have no puppetserver installation with debian on hand, so I don’t know how 
the debian package would behave.

Another argument has been made that the reports are stored in puppetdb and the 
reports are thus only stored temporarily as files on a disk. IMHO that still 
wouldn’t make them "cache" data. "temporary" data maybe, so in that case they 
should probably go to /var/tmp or /tmp.
Or, as https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s14.html mentions:
> /var/spool contains data which is awaiting some kind of later processing. 
> Data in /var/spool represents work to be done in the future (by a program, 
> user, or administrator); often data is deleted after it has been processed.

Both of these arguments are kind of OK for a certain set of circumstances but 
not everybody is running a puppetdb or even a puppetserver. I am running puppet 
standalone, i.e. with `puppet apply`, so the reports will not be transferred to 
the server and will not be consumed into/by puppetdb.

In any case, treating reports as "cached" data seems quite clearly wrong.
In the case of standalone puppet (i.e. `puppet apply`) IMHO they are "logs" and 
should go to /var/log.
In the case of a puppet-agent (i.e. a puppet client/agent connecting to a 
puppet server _without_ a puppetdb), they should probably not be saved on the 
client at all but if so, they are also "logs" IMHO and should be treated like 
mentioned above. On the server, they should also be treated like "logs" but not 
necessarily go to /var/log like machine-local log data. I don’t think I have a 
concrete sensible suggestion for this case. Maybe /var/lib.
In the case of a puppetserver with a puppetdb, they should probably not be 
saved as files at all on the server. Unless they are sent directly to the 
puppetdb from the puppedserver, but consumed later, they are probably "spool" 
data.


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-20-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages puppet-agent depends on:
ii  adduser3.134
ii  debconf [debconf-2.0]  1.5.82
ii  facter 4.3.0-2
ii  hiera  3.10.0-1
ii  init-system-helpers1.65.2
ii  ruby   1:3.1
ii  ruby-augeas1:0.5.0+gem-1
ii  ruby-concurrent1.1.6+dfsg-5
ii  ruby-deep-merge1.1.1-2
ii  ruby-semantic-puppet   1.0.4-1
ii  ruby-shadow2.5.1-1
ii  ruby-sorted-set1.0.3-3

Versions of packages puppet-agent recommends:
pn  augeas-tools   
ii  debconf-utils  1.5.82
ii  lsb-release12.0-1
pn  ruby-selinux   

Versions of packages puppet-agent suggests:
pn  hiera-eyaml
pn  puppet-module-puppetlabs-augeas-core   

Bug#1031619: neofetch seems unmaintained, replace with hyfetch, now it is offical

[Hendrik Lehmbruch]

Package: neofetch
Version: 7.1.0-4
Followup-For: Bug #1031619
X-Debbugs-Cc: hlehmbr...@gmx.net

Dear Maintainer,

I can confirm that!

https://github.com/dylanaraps/neofetch

The github reprository is read only, so the development of neofetch is dead!


-- System Information:
Debian Release: trixie/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.0-rc5-siduction-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

neofetch depends on no packages.

Versions of packages neofetch recommends:
ii  caca-utils   0.99.beta20-4+b1
ii  chafa1.14.0-1.1+b1
ii  imagemagick  8:6.9.12.98+dfsg1-5.2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.12.98+dfsg1-5.2
ii  jp2a 1.2.0-1
ii  libsixel-bin 1.10.3-3+b1
ii  pciutils 1:3.12.0-1
ii  w3m-img  0.5.3+git20230121-2+b3

neofetch suggests no packages.

-- no debconf information

Bug#1068408: Kicad bundle broken

[Terrance Hendrik]

Package: kicad
Version: 7.0.11+dfsg-1

I am using Debian testing/trixie, the Kicad bundle has multiple issues.

1. kicad-footprints kicad-packages3d kicad-symbols kicad-templates (7.x)
are all missing. I also checked stable sources.
```
# apt install kicad-footprints=
Completing package version
6.0.11-1  -- http://deb.debian.org/debian stable/main amd64 Packages
8.0.1-1   -- http://deb.debian.org/debian testing/main amd64 Packages
```
2. I also have "unstable" source for apt, when upgrading, kicad-footprints
kicad-packages3d kicad-symbols kicad-templates got upgraded to 8.0, which
Kicad 7.0 does not compatible with.

Kicad and its footprints packages3d symbols templates

3. kicad-libraries should not Depends kicad-footprints (>= 7.0.0~),
kicad-symbols (>= 7.0.0~), kicad-templates (>= 7.0.0~)，rather >= 7.0.0
<8.0.0


Kicad can only access libraries with same or lower major version.

Bug#1068020: Background process seemingly paused

[Terrance Hendrik]

Package: linux-image-amd64
Version: 6.6.15-2

Debian testing/trixie, kernel 6.6.15-2 (2024-02-04)
xfce

Case 1:

Start a command that runs for a long time, say `ffmpeg`. switch to other
programs, i.e. web browser or other terminal windows, and keep using the
computer. After a while, ffmpeg cpu usage drops to 0%, switch back to
ffmpeg's terminal window, it will go back to running.

Case 2:

start ffmpeg, leave the computer untouched, then screensaver runs, then the
display turns off. No suspend, no hibernate, no shutdown. after a while,
wake up display, unlock session, ffmpeg is using 0% CPU. switch back to its
terminal window, it resumes.


I am not sure which package is causing this. This happened long before
6.6.15 kernels.

Bug#1051432: Info received ()

[Terrance Hendrik]

I fixed this, after months of research.

This is not an issue of bluez.

hidp/uhid really IS the problem. I don't know what makes a Linux decide to
load `uhid` or `hidp`, my "good" and "bad" Linux SSD are dd'ed from same
source, and they even have same partition uuid.

long story short, blacklist hidp and force load uhid kernel module, all
mice work happily now!

echo "blacklist hidp" | sudo tee /etc/modprobe.d/blacklist-hidp.conf
echo -e  "# Fix BLE mouse issue\nuhid" | sudo tee /etc/modules-load.d/uhid.conf
cp --update=none /etc/bluetooth/input.conf{,backup}
sudo sed -ie "s:.*UserspaceHID=.*:UserspaceHID=true:" /etc/bluetooth/input.conf

then reboot.

On Fri, Jan 26, 2024 at 12:52 PM Terrance Hendrik <
terrance.hend...@gmail.com> wrote:

> Update 2024-01-26
>
> 1. It has nothing to do with GUI. In text mode the issue is the same.
>
> 2. it has nothing to do with DKMS, removing it changes nothing.
>
> 3. I swapped SSD between 2 computers, the issue goes with the SSD. So it's
> not a hardware issue
>
> 4. I `apt purge` bluez and blueman, removed /etc/bluetooth, then reinstall
> them, the issue persists.
>
> 5. I compared files in /etc/udev/rules.d and /lib/modules on both
> computer, they are identical.
> only difference is modules.dep*, modules.symbols* and extra dkms modules.
>
> 6. other info
>
> on the working OS, connecting a logitech mouse has 2 syslog messages
> ```
> ... blueman-manager[7228]: blueman-manager 18.32.55 WARNING
>  ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels,
> probably a LE device.
> ... kernel: input: MX Anywhere 3 Mouse as
> /devices/virtual/misc/uhid/0005:046D:B025.000D/input/input37
> ... kernel: hid-generic 0005:046D:B025.000D: input,hidraw5: BLUETOOTH HID
> v0.14 Mouse [MX Anywhere 3] on 
> ```
>
> on the NOT working OS, connecting a logitech mouse has 2 syslog messages
> ```
> ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
> profile accept failed for F6:8C:E4:DD:B8:6B
> ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
> profile accept failed for F6:8C:E4:DD:B8:6B
> ```
>
> 7. Final Question:
> What else can affect the behavior between bluez and the kernel??
>
>
> On Fri, Nov 17, 2023 at 8:36 AM Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> Thank you for the additional information you have supplied regarding
>> this Bug report.
>>
>> This is an automatically generated reply to let you know your message
>> has been received.
>>
>> Your message is being forwarded to the package maintainers and other
>> interested parties for their attention; they will reply in due course.
>>
>> Your message has been sent to the package maintainer(s):
>>  Debian Bluetooth Maintainers 
>>
>> If you wish to submit further information on this problem, please
>> send it to 1051...@bugs.debian.org.
>>
>> Please do not send mail to ow...@bugs.debian.org unless you wish
>> to report a problem with the Bug-tracking system.
>>
>> --
>> 1051432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051432
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>

Bug#1051432: Info received ()

[Terrance Hendrik]

Update 2024-01-26

1. It has nothing to do with GUI. In text mode the issue is the same.

2. it has nothing to do with DKMS, removing it changes nothing.

3. I swapped SSD between 2 computers, the issue goes with the SSD. So it's
not a hardware issue

4. I `apt purge` bluez and blueman, removed /etc/bluetooth, then reinstall
them, the issue persists.

5. I compared files in /etc/udev/rules.d and /lib/modules on both computer,
they are identical.
only difference is modules.dep*, modules.symbols* and extra dkms modules.

6. other info

on the working OS, connecting a logitech mouse has 2 syslog messages
```
... blueman-manager[7228]: blueman-manager 18.32.55 WARNING
 ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels,
probably a LE device.
... kernel: input: MX Anywhere 3 Mouse as
/devices/virtual/misc/uhid/0005:046D:B025.000D/input/input37
... kernel: hid-generic 0005:046D:B025.000D: input,hidraw5: BLUETOOTH HID
v0.14 Mouse [MX Anywhere 3] on 
```

on the NOT working OS, connecting a logitech mouse has 2 syslog messages
```
... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
profile accept failed for F6:8C:E4:DD:B8:6B
... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
profile accept failed for F6:8C:E4:DD:B8:6B
```

7. Final Question:
What else can affect the behavior between bluez and the kernel??


On Fri, Nov 17, 2023 at 8:36 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Bluetooth Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 1051...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1051432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051432
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1058657: python3-apt: undefined symbol: PyAptWarning, breaks nala

[Hendrik Lehmbruch]

Package: python3-apt
Version: 2.7.2
Followup-For: Bug #1058657
X-Debbugs-Cc: hlehmbr...@gmx.net

Dear Maintainer,

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

   * What led up to the situation?

Running nala upgrade

   * What was the outcome of this action?

--- snipp ---

Traceback (most recent call last):
File "/usr/bin/nala", line 5, in 
 from nala.__main__ import main
File "/usr/lib/python3/dist-packages/nala/__main__.py", line 31, in 
 import nala.fetch as _fetch  # pylint: disable=unused-import
 ^^^
File "/usr/lib/python3/dist-packages/nala/fetch.py", line 60, in 
 from nala.downloader import print_error
File "/usr/lib/python3/dist-packages/nala/downloader.py", line 70, in 
 from nala.error import ExitCode, FileDownloadError
File "/usr/lib/python3/dist-packages/nala/error.py", line 38, in 
 from nala.debfile import NalaBaseDep, NalaDebPackage, NalaDep
File "/usr/lib/python3/dist-packages/nala/debfile.py", line 32, in 
 from apt.debfile import DebPackage
File "/usr/lib/python3/dist-packages/apt/debfile.py", line 28, in 
 import apt_inst ImportError: /usr/lib/python3/dist-
packages/apt_inst.cpython-311-x86_64-linux-gnu.so: undefined symbol:
PyAptWarning

- snapp ---

apt policy nala
nala:
  Installed: 0.14.0
  Candidate: 0.14.0


-- System Information:
Debian Release: trixie/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.7-1-siduction-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-apt depends on:
ii  distro-info-data   0.60
ii  libapt-pkg6.0  2.7.7
ii  libc6  2.37-13
ii  libgcc-s1  13.2.0-8
ii  libstdc++6 13.2.0-8
ii  python-apt-common  2.7.2
ii  python33.11.6-1

Versions of packages python3-apt recommends:
ii  iso-codes4.15.0-1
ii  lsb-release  12.0-2

Versions of packages python3-apt suggests:
ii  apt 2.7.7
pn  python-apt-doc  

-- no debconf information

Bug#1051432:

[Terrance Hendrik]

seems more like an issue with kernel/gui than bluez.

checked my modprobe.d blacklists, most are  system default.

```
blacklist ath_pci
blacklist evbug
blacklist usbmouse
blacklist usbkbd
blacklist eepro100
blacklist de4x5
blacklist eth1394
blacklist snd_intel8x0m
blacklist snd_aw2
blacklist prism54
blacklist bcm43xx
blacklist garmin_gps
blacklist asus_acpi
blacklist snd_pcsp
blacklist pcspkr
blacklist amd76x_edac
blacklist ohci1394
blacklist sbp2
blacklist dv1394
blacklist raw1394
blacklist video1394
blacklist aty128fb
blacklist atyfb
blacklist radeonfb
blacklist cirrusfb
blacklist cyber2000fb
blacklist cyblafb
blacklist gx1fb
blacklist hgafb
blacklist i810fb
blacklist intelfb
blacklist kyrofb
blacklist lxfb
blacklist matroxfb_base
blacklist neofb
blacklist nvidiafb
blacklist pm2fb
blacklist rivafb
blacklist s1d13xxxfb
blacklist savagefb
blacklist sisfb
blacklist sstfb
blacklist tdfxfb
blacklist tridentfb
blacklist vfb
blacklist viafb
blacklist vt8623fb
blacklist udlfb
blacklist intel_hid
blacklist sparse_keymap
blacklist nfc
blacklist pn533
blacklist pn533_usb
blacklist nouveau
blacklist hackrf
```

Is it possible something's wrong with DKMS? the other 3 computers have no
DKMS.

Bug#1051432: further info

[Terrance Hendrik]

Thank you, Iwanmatsu san!

But no luck,still logs

```
Nov 14 21:44:49  blueman-manager[10028]: blueman-manager 21.44.49
WARNING  ManagerDeviceList:396 _monitor_power_levels: Failed to get power
levels, probably a LE device.
Nov 14 21:44:49  bluetoothd[9996]: src/service.c:service_accept()
input-hog profile accept failed for 
Nov 14 21:44:51  bluetoothd[9996]: src/service.c:service_accept()
input-hog profile accept failed for 
```
I uncommented those lines and restarted bluetooth.service.

Also tried adding `--experimental` to service execstart, only gets worse.

Strangely, other 3 computers running almost the same kernel 6.3-6.5 and
bluez 5.6x - 5.70, logi mice work perfectly fine.

On Mon, Oct 23, 2023 at 11:10 PM Nobuhiro Iwamatsu 
wrote:

> Hi,
>
> 2023年9月8日(金) 6:57 Terrance Hendrik :
> >
> > bluetoothctl
> >
> > [MX Anywhere 3]# info
> > Device E5:9F:06:B5:08:8D (random)
> > Name: MX Anywhere 3
> > Alias: MX Anywhere 3
> > Appearance: 0x03c2 (962)
> > Icon: input-mouse
> > Paired: yes
> > Bonded: yes
> > Trusted: yes
> > Blocked: no
> > Connected: yes
> > WakeAllowed: no
> > LegacyPairing: no
> > UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
> > UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
> > UUID: Device Information(180a--1000-8000-00805f9b34fb)
> > UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
> > UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
> > UUID: Vendor specific   (0001--1000-8000-011f246d)
> > Modalias: usb:v046DpB025d0014
> > Battery Percentage: 0x4b (75)
>
> Could you please set ClassicBondedOnly=true and LEAutoSecurity=true in
> /etc/bluetooth/input.conf and check?
>
> ```
> [General]
> ClassicBondedOnly = true
> LEAutoSecurity = true
> ```
>
> Best regards,
>   Nobuhiro
>
>
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org / kernel.org}
>GPG ID: 32247FBB40AD1FA6
>

Bug#1055149: rng-utils-debian: logcheck rules do not use high-precision timeformat

[Hendrik Jaeger]

Package: rng-utils-debian
Version: rng-tools-debian
Severity: minor
X-Debbugs-Cc: debian-b...@henk.geekmail.org

Dear Maintainer,

I started seeing a lot of log messages from `rngd` in my logcheck reports.
Checking on where that service comes from and whether I have configured 
anything about it, I noticed that it comes with a logcheck file in
/etc/logcheck/ignore.d.server/rng-tools-debian

That’s very nice! But the file is not up-to-date with the recent development of 
logs using high-precision timestamps as described in
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#rsyslog-timestamp-change-affects-logcheck

The release notes also link to the solution.

Thank you!

Best regards

henk


-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Bug#1052348: gcc-arm-none-eabi 15:12.3 breaks related latest packages

[Terrance Hendrik]

Package: gcc-arm-none-eabi
Version: 15:12.3.rel1-1

upgrade it will remove latest libstdc++-arm-none-eabi-dev
libstdc++-arm-none-eabi-newlib

Bug#1052217: linux-image-6.5.0-1-amd64: Notebook display black after waking up from suspend

[Hendrik Iseke]

Package: src:linux
Version: 6.5.3-1
Severity: important
X-Debbugs-Cc: h...@tavira-net.de

Dear Maintainer,

After upgrading the linux kernel to version 6.5.3, the display of my
Lenove T15 notebook will remain black after waking up from suspend.
The external display connected to the HDMI port works as usual.
Restarting the xserver or wayland session does not help, nor does
switching to tty. The only way to get the display back to work is
rebooting.

The problem does not occur, when using the the latest linux-image-6.4.
If I can provide you with more information, please let me know.

Cheers,
Hendrik

-- Package-specific info:
** Version:
Linux version 6.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 
13.2.0-4) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC 
Debian 6.5.3-1 (2023-09-13)

** Command line:
BOOT_IMAGE=/vmlinuz-6.5.0-1-amd64 root=/dev/mapper/floripa--vg-root ro quiet 
splash

** Not tainted

** Kernel log:
[ 1241.631837] (NULL device *): firmware: direct-loading firmware 
nvidia/tu117/acr/ucode_ahesasc.bin
[ 1241.631985] (NULL device *): firmware: direct-loading firmware 
nvidia/tu117/gr/sw_bundle_init.bin
[ 1241.632052] (NULL device *): firmware: direct-loading firmware 
nvidia/tu117/acr/ucode_asb.bin
[ 1241.634964] Freezing user space processes
[ 1241.658798] Freezing user space processes completed (elapsed 0.023 seconds)
[ 1241.658805] OOM killer disabled.
[ 1241.658806] Freezing remaining freezable tasks
[ 1241.660095] Freezing remaining freezable tasks completed (elapsed 0.001 
seconds)
[ 1241.660158] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1241.972901] e1000e: EEE TX LPI TIMER: 0011
[ 1243.447035] ACPI: EC: interrupt blocked
[ 1243.588572] ACPI: PM: Preparing to enter system sleep state S3
[ 1243.598092] ACPI: EC: event blocked
[ 1243.598096] ACPI: EC: EC stopped
[ 1243.598097] ACPI: PM: Saving platform NVS memory
[ 1243.598471] Disabling non-boot CPUs ...
[ 1243.600589] smpboot: CPU 1 is now offline
[ 1243.604671] smpboot: CPU 2 is now offline
[ 1243.608362] smpboot: CPU 3 is now offline
[ 1243.611878] smpboot: CPU 4 is now offline
[ 1243.615622] smpboot: CPU 5 is now offline
[ 1243.619468] smpboot: CPU 6 is now offline
[ 1243.622393] smpboot: CPU 7 is now offline
[ 1243.624234] smpboot: CPU 8 is now offline
[ 1243.625855] smpboot: CPU 9 is now offline
[ 1243.627804] smpboot: CPU 10 is now offline
[ 1243.629650] smpboot: CPU 11 is now offline
[ 1243.631935] ACPI: PM: Low-level resume complete
[ 1243.631975] ACPI: EC: EC started
[ 1243.631976] ACPI: PM: Restoring platform NVS memory
[ 1243.633076] Enabling non-boot CPUs ...
[ 1243.633096] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 1243.633676] CPU1 is up
[ 1243.633689] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 1243.634251] CPU2 is up
[ 1243.634262] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 1243.634818] CPU3 is up
[ 1243.634828] smpboot: Booting Node 0 Processor 4 APIC 0x8
[ 1243.635396] CPU4 is up
[ 1243.635406] smpboot: Booting Node 0 Processor 5 APIC 0xa
[ 1243.635989] CPU5 is up
[ 1243.635999] smpboot: Booting Node 0 Processor 6 APIC 0x1
[ 1243.636705] CPU6 is up
[ 1243.636718] smpboot: Booting Node 0 Processor 7 APIC 0x3
[ 1243.637306] CPU7 is up
[ 1243.637316] smpboot: Booting Node 0 Processor 8 APIC 0x5
[ 1243.637926] CPU8 is up
[ 1243.637938] smpboot: Booting Node 0 Processor 9 APIC 0x7
[ 1243.638546] CPU9 is up
[ 1243.638556] smpboot: Booting Node 0 Processor 10 APIC 0x9
[ 1243.639174] CPU10 is up
[ 1243.639185] smpboot: Booting Node 0 Processor 11 APIC 0xb
[ 1243.639815] CPU11 is up
[ 1243.644290] ACPI: PM: Waking up from system sleep state S3
[ 1243.732264] ACPI: EC: interrupt unblocked
[ 1245.033343] ACPI: EC: event unblocked
[ 1245.038725] i915 :00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in 
DSI mode with an ungated DDI clock, gate it
[ 1245.038742] i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is 
disabled/in DSI mode with an ungated DDI clock, gate it
[ 1245.038757] i915 :00:02.0: [drm] [ENCODER:118:DDI C/PHY C] is 
disabled/in DSI mode with an ungated DDI clock, gate it
[ 1245.038774] i915 :00:02.0: [drm] [ENCODER:128:DDI D/PHY D] is 
disabled/in DSI mode with an ungated DDI clock, gate it
[ 1245.046762] nvme nvme1: 12/0/0 default/read/poll queues
[ 1245.051769] nvme nvme0: Shutdown timeout set to 8 seconds
[ 1245.064477] nvme nvme0: 12/0/0 default/read/poll queues
[ 1245.349683] usb 1-10: reset full-speed USB device number 6 using xhci_hcd
[ 1245.637665] usb 1-8: reset high-speed USB device number 4 using xhci_hcd
[ 1245.794767] psmouse serio1: synaptics: queried max coordinates: x [..5678], 
y [..4694]
[ 1245.823080] psmouse serio1: synaptics: queried min coordinates: x [1266..], 
y [1162..]
[ 1245.928959] pci_bus :06: Allocating resources
[ 1245.928974] OOM killer enabled.
[ 1245.928975] Restarting tasks ... 
[ 1245.928976] pci_bus :2c: Allocating resources
[ 1245.929015] pcieport :00:1c.7: PCI bridge

Bug#1051432: further info

[Terrance Hendrik]

bluetoothctl

[MX Anywhere 3]# info
Device E5:9F:06:B5:08:8D (random)
Name: MX Anywhere 3
Alias: MX Anywhere 3
Appearance: 0x03c2 (962)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: no
LegacyPairing: no
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information(180a--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
UUID: Vendor specific   (0001--1000-8000-011f246d)
Modalias: usb:v046DpB025d0014
Battery Percentage: 0x4b (75)

Bug#1051432: bluez 5.6.9 Some bluetooth mouse not working, problem persists

[Terrance Hendrik]

Package: bluez

Version: 5.6.9-1

Not sure if this issue is about bluez or other packages or modules

System info:

```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux trixie/sid
Release:n/a
Codename:   trixie

$ uname -a
Linux  6.4.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.13-1
(2023-08-31) x86_64 GNU/Linux

```

journalctl -f, after connected


```
Sep 08 04:57:06  blueman-manager[11378]: blueman-manager
04.57.06 WARNING  ManagerDeviceList:396 _monitor_power_levels: Failed
to get power levels, probably a LE device.
Sep 08 04:57:06  bluetoothd[1053]:
src/service.c:service_accept() input-hog profile accept failed for

Sep 08 04:57:06  bluetoothd[1053]:
src/service.c:service_accept() input-hog profile accept failed for

```

Bluetooth adapter: 8087:0026 Intel Corp. AX201 Bluetooth


Mouse is Logitech MX Anywhere 3, and MX Master 3. connected to Bluetooth.

Bug#1049456: update

[Terrance Hendrik]

after upgrading bluez bundle to
```
Package: bluez

Version: 5.69-1
...
```

now **MX Anywhere 3** disconnect immediately then reconnected for dozens of
times every several seconds.

While other mice (e.g.UGreen MU002 ) working fine.

Bug#1040636: Kernel bug

[Hendrik Jaeger]

Hi

Regarding the kernel bug:
I found the following bug about this:
https://bugs.archlinux.org/task/78908
which led me to:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master=3e70489721b6c870252c9082c496703677240f53

Talking to people about it indicated that this bug is fixed in linux 6.1.43.

It might be better to reassign this to the linux kernel package.
Since this pretty much breaks a security relevant component in some scenarios 
and nftables is the default, I think severity should be raised to important.
And it would be nice to get an updated kernel without this issue into stable.

Cheers

henk


pgp9jw65qI30d.pgp
Description: OpenPGP digital signature

Bug#1049456: bluez 5.6.8 Some bluetooth mouse not working

[Terrance Hendrik]

Package: bluez
Version: 5.6.8-2
System info:

```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux trixie/sid
Release:n/a
Codename:   trixie
```

journalctl -f, after connected


```
Aug 16 10:00:43  bluetoothd[1022]:
src/service.c:service_accept() input-hog profile accept failed for

Aug 16 10:00:45  bluetoothd[1022]:
src/service.c:service_accept() input-hog profile accept failed for

```

Bluetooth adapter: 8087:0026 Intel Corp. AX201 Bluetooth


Mouse is Logitech MX Anywhere 3, and MX Master 3. connected to Bluetooth.

Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic

[Terrance Hendrik]

;__this_module)
  | ~^~~
  |  |
  |  struct module *
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:1535:35:
note: in expansion of macro ‘THIS_MODULE’
 1535 | xtrx_class = class_create(THIS_MODULE, CLASS_NAME);
  |   ^~~
In file included from
/usr/src/linux-headers-6.4.0-1-common/include/linux/device.h:31,
 from
/usr/src/linux-headers-6.4.0-1-common/include/linux/pci.h:37,
 from
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:25:
/usr/src/linux-headers-6.4.0-1-common/include/linux/device/class.h:230:54:
note: expected ‘const char *’ but argument is of type ‘struct module *’
  230 | struct class * __must_check class_create(const char *name);
  |  ^~~~
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:1535:22:
error: too many arguments to function ‘class_create’
 1535 | xtrx_class = class_create(THIS_MODULE, CLASS_NAME);
  |  ^~~~
/usr/src/linux-headers-6.4.0-1-common/include/linux/device/class.h:230:29:
note: declared here
  230 | struct class * __must_check class_create(const char *name);
  | ^~~~
cc1: some warnings being treated as errors
make[1]: ***
[/usr/src/linux-headers-6.4.0-1-common/scripts/Makefile.build:257:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.o] Error 1
make: *** [/usr/src/linux-headers-6.4.0-1-common/Makefile:2051:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.4.0-1-amd64'
```

2 dkms modules failed to built,
xtrx/0.0.1+git20190320.5ae3a3e-3.3
tp_smapi/0.43

quick & dirty fix xtrx
1535 xtrx_class = class_create(THIS_MODULE, CLASS_NAME);
1535 xtrx_class = class_create(/*THIS_MODULE*/, CLASS_NAME);

too many errors from tp-smapi-dkms, and I dont't remember using it , so
`apt purge tp-smapi-dkms`

now /boot/initrd.img-6.4.0-1-amd64 can be built


On Wed, Jul 26, 2023 at 11:14 PM Ben Hutchings  wrote:

> Control: reassign -1 src:linux 6.4.4-1
> Control: tag -1 moreinfo
>
> On Wed, 2023-07-26 at 10:59 +0800, Terrance Hendrik wrote:
> > Package: linux-image-6.4.0-1-amd64
> > Version: 6.4.4-1
> > system info:
> >
> > ```
> > $ lsb_release -a
> > No LSB modules are available.
> > Distributor ID: Debian
> > Description:Debian GNU/Linux trixie/sid
> > Release:n/a
> > Codename:   trixie
> > $ lscpu
> > Architecture:x86_64
> >   CPU op-mode(s):32-bit, 64-bit
> >   Address sizes: 39 bits physical, 48 bits virtual
> >   Byte Order:Little Endian
> > CPU(s):  20
> >   On-line CPU(s) list:   0-19
> > Vendor ID:   GenuineIntel
> >   Model name:12th Gen Intel(R) Core(TM) i7-12700H
> > ...
> > ```
> >
> > Root FS is **btrfs**
> >
> >
> > Boot log (photo OCR, unable to save log, might have some errors)
> [...]
> > [0.704503] List of all partitions:
> >
> > [0.705638] No filesystem could mount root, tried:
> [...]
>
> It seems that your boot loader tried to boot this kernel without an
> initramfs.
>
> - Which boot loader are you using?
> - Does /boot/initrd.img-6.4.0-1-amd64 exist?
> - Does "dpkg --configure -a" do anything or show any errors?
>
> Ben.
>
> --
> Ben Hutchings
> Every program is either trivial or else contains at least one bug
>
>

Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic

[Terrance Hendrik]

Package: linux-image-6.4.0-1-amd64
Version: 6.4.4-1
system info:

```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux trixie/sid
Release:n/a
Codename:   trixie
$ lscpu
Architecture:x86_64
  CPU op-mode(s):32-bit, 64-bit
  Address sizes: 39 bits physical, 48 bits virtual
  Byte Order:Little Endian
CPU(s):  20
  On-line CPU(s) list:   0-19
Vendor ID:   GenuineIntel
  Model name:12th Gen Intel(R) Core(TM) i7-12700H
...
```

Root FS is **btrfs**


Boot log (photo OCR, unable to save log, might have some errors)

```

[0.625362] Key type .fscrypt registered

[0.625379] Key type fscrypt-provisioning registered

[9.626122] Key type encrypted registered

[0.626142] AppArmor: AppArmor shal policy hashing enabled

[0.626493] integrity: Loading X.509 certificate: UEFI:b

[0.626527] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA
2011: 13adb43096d82709cBcd54f316ed522988a1bd4'

[0.626571] integrity: Loading X.509 certificate: UEF1: db

[0.626602] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA
2011: a92902398e16c4977Bcd90 f99e4f9ae17c55af53'

[0.627200] ima: Allocated hash algorithm: sha256

[0.646056] ima: No architecture policies found[

[0.647855] evm: Initialising EVM extended attributes:

[0.649888] evm: security. selinux

[0.651351] evm: security. SMACK64 (disabled)

[0.652752] evm: security. SMACK64EXEC (disabled)

[0.653931] evm: security. SMACK64TRANSMUTE (disabled)

[0.655031] evm: security. SMACK64MMAP (disabled)

[0.656067] evm: security. apparmor

[0.657873] evm: security. ima

[0.658026] evm: security.capability

[0.658966] evm: HMAC attrs: Bx1

[0.703120] clk: Disabling unused clocks

[0.704503] List of all partitions:

[0.705638] No filesystem could mount root, tried:

[8.705639]

[0.707504] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)

[0.708458] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 6.4.0-1-amd64 #1
Debian 6.4.4-1

[8.709396] Harduare name: MECHREVO WUJIE16 Pro/WUJIE16 Pro. BIOS Q3ANWJ.16
12/09/2022

[0.710369] Call Trace:

[0.711305] 

[0.712215] dump_stack_1v1+0×47/0×60

[0.713148] panic+0x17f/0×330

[0.714067] mount_block_root+0×21f/0x2b@

[0.714981] prepare_namespace+Oxf0/0×170

[8.715888] kernel_init_freeable+Bx417/8×470

[0.716782] ?__pfx_kernel_init+B×10/B×10

[0.717637] kernel_init+Bxla/Bx1cl

[0.718583] ret_from_fork+Bx29/0×50

[0.719387] 

[0.720391] Kernel Offset: Bx3700 from Ox8100 (relocation
range: Bx8000-0xbfff)

[0.721331]---[ end Kernel panic - not syncing: FS: Unable to mount root fs
on unknown-black(0,0) ]--

```

Thanks!

Bug#1041590: nvidia-installer-cleanup install fail

[Terrance Hendrik]

YES!

I did
```
unset DEBIAN_PRIORITY
unset DEBIAN_FRONTEND
```
Then a ncurse window popped up and the install finished.

Thanks!!


On Sat, Jul 22, 2023 at 3:49 AM Andreas Beckmann  wrote:

> On 21/07/2023 06.41, Terrance Hendrik wrote:
> > Unpacking nvidia-installer-cleanup (20220217+3) ...
> > Setting up nvidia-installer-cleanup (20220217+3) ...
> > dpkg: error processing package nvidia-installer-cleanup (--configure):
> >   installed nvidia-installer-cleanup package post-installation script
> > subprocess returned error exit status 30
>
> This sounds like debconf couldn't display a question.
>
> Did you customize the debconf priority on this system? Or do you use
> something like DEBIAN_FRONTEND=noninteractive ?
>
> Have you ever had the nvidia driver installed from the .run installer on
> this machine?
>
> Andreas
>

Bug#1041590: nvidia-installer-cleanup install fail

[Terrance Hendrik]

Package: nvidia-installer-cleanup
Version: 20220217+3
system info
```
$ uname-a
Linux  6.3.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.3.11-1
(2023-07-01) x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux trixie/sid
Release:n/a
Codename:   trixie
```

steps to represent

```
# apt install nvidia-installer-cleanup
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  nvidia-installer-cleanup
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/13.3 kB of archives.
After this operation, 48.1 kB of additional disk space will be used.
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package nvidia-installer-cleanup.
(Reading database ... 421224 files and directories currently installed.)
Preparing to unpack .../nvidia-installer-cleanup_20220217+3_amd64.deb ...
Unpacking nvidia-installer-cleanup (20220217+3) ...
Setting up nvidia-installer-cleanup (20220217+3) ...
dpkg: error processing package nvidia-installer-cleanup (--configure):
 installed nvidia-installer-cleanup package post-installation script
subprocess returned error exit status 30
Errors were encountered while processing:
 nvidia-installer-cleanup
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

perl trace log in the attachment.

Thanks!

Bug#1036899: logiops: logid does not work for MX Master 3

[Hendrik Tews]

Hi,

On 2023-06-05 10:22:35, Chow Loong Jin  wrote:

> Could you check if 0.3.1-1 (in unstable) or 0.3.2-1 (in experimental) is
> working for you?

thanks for following up. Both 0.3.1-2 from unstable and 0.3.2-1 from
experimental work. (Unexpected to me, because I reproduced the problem
with the newest upstream version.)

Version 0.3.1-1 is the version from testing, this version does not
work.

Hendrik

Bug#1036899: logiops: logid does not work for MX Master 3

[Hendrik Tews]

Package: logiops
Version: 0.3.1-1
Severity: important
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

after upgrading to logiops version 0.3.1-1 the logid daemon does not
seem to do anything any more. For my configuration the symptom is that
the thumb button is no longer mapped to button 2. The problem seems to
be also present in the current upstream version (v0.3.2), see upstream
issue 387 (https://github.com/PixlOne/logiops/issues/387).

For now I downgraded to 0.2.3-1+b1, which is still working fine.

Best regards,

Hendrik


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages logiops depends on:
ii  libc6   2.36-9
ii  libconfig++9v5  1.5-0.4
ii  libevdev2   1.13.0+dfsg-1
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-02.74.6-2
ii  libstdc++6  12.2.0-14
ii  libudev1252.6-1

logiops recommends no packages.

logiops suggests no packages.

-- Configuration Files:
/etc/logid.cfg changed:
devices: ({
  name: "Wireless Mouse MX Master 3";
  # A lower threshold number makes the wheel switch to free-spin mode
  # quicker when scrolling fast.
  smartshift: {
on: false;
threshold: 3;
  };
  hiresscroll: {
hires: true;
invert: false;
target: false;
  };
  # Higher numbers make the mouse more sensitive (cursor moves faster),
  # 4000 max for MX Master 3.
  dpi: 1000;
  buttons: (
# Make thumb button 2.
{ cid: 0xc3;
  action = {
type: "Keypress";
keys: ["BTN_MIDDLE"];
  };
},
# top button
{ cid: 0xc4;
  action = {
type = "ToggleSmartshift";
  };
}
  );
});


-- no debconf information

Bug#1034871: podman: "sudo podman system reset" can delete current working directory

[Jan Hendrik Farr]

Package: podman
Version: 4.3.1+ds1-6+b2
Severity: normal
Tags: newcomer
X-Debbugs-Cc: deb...@jfarr.cc

Dear Maintainer,

if /etc/containers/storage.conf does not include the runRoot variable, then
running "sudo podman system reset" will delete the current working directory.
This is already fixed in upstream, I hope this can be backported and included
in Debian 12.

upstream issue: https://github.com/containers/podman/issues/18349
upstream fix: https://github.com/containers/storage/pull/1510


Including this fix in Debian 12 has a really low chance of affecting other
packages, but if this fix is not included there will inevitably be more people
like me that accidentally remove their home directory.


With kind regards
Jan



-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.2.11 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages podman depends on:
ii  conmon   2.1.6+ds1-1
ii  crun 1.8.1-1+b1
ii  golang-github-containers-common  0.50.1+ds1-4
ii  libc62.36-9
ii  libdevmapper1.02.1   2:1.02.185-2
ii  libgpgme11   1.18.0-3+b1
ii  libseccomp2  2.5.4-1+b3
ii  libsubid41:4.13+dfsg1-1+b1
ii  runc 1.1.5+ds1-1+b1

Versions of packages podman recommends:
ii  buildah1.28.2+ds1-1+b2
ii  catatonit  0.1.7-1+b1
ii  dbus-user-session  1.14.6-1
ii  fuse-overlayfs 1.10-1
ii  slirp4netns1.2.0-1
ii  tini   0.19.0-1
ii  uidmap 1:4.13+dfsg1-1+b1

Versions of packages podman suggests:
pn  containers-storage  
pn  docker-compose  
ii  iptables1.8.9-2

-- no debconf information

Bug#902866: flameshot: Will not run, exits with error "Could not connect to display"

[Hendrik Jäger]

Hi Prescott

> It's been a while but luckily I've kept all my config changes in a git repo!

Thank you for your quick response and being able to dig this up!

> >How do you select to start bspwm: via a menu in your DM, after logging into 
> >your DM, from your ~/.xsession, ~/.xinitrc, etc.?  

> So I start bspwm by running `startx` at boot and had `exec bspwm` as the WM 
> launch command

This might be the crucial point: I’m guessing you are using ~/.xinitrc?
If you can reproduce the issue with ~/.xinitrc, could you test whether it also 
occurs when you use ~/.xsession instead (i.e. remove ~/.xinitrc!)?
AFAICT /etc/X11/Xsession.d/95dbus_update-activation-env sets up dbus correctly 
but everything in /etc/X11/Xsession* is only active if startx runs 
/etc/X11/xinit/xinitrc and it will not if ~/.xinitrc exists.

Thank you

henk

On Fri, 24 Feb 2023 11:25:16 -0600
Prescott HM  wrote:

> >I’m thinking your (dbus) environment is not initialized correctly when
> >starting your X-session. How do you start it?
> >Do you use some Display Manager, like xdm, gdm, etc.?
> >How do you select to start bspwm: via a menu in your DM, after logging into
> >your DM, from your ~/.xsession, ~/.xinitrc, etc.?  
> 
> It's been a while but luckily I've kept all my config changes in a git repo!
> 
> So I start bspwm by running `startx` at boot and had `exec bspwm` as the WM
> launch command, but had gotten it fixed by correctly starting it with `exec
> dbus- run-session -- bspwm`.
> 
> I think the biggest issue was as someone new to trying out lauching a 
> graphical
> session without a display manager, there really wasn't any indication of
> what exactly is needed to manually start that's taken for granted. It finally
> clicked when I started using other programs that require a D-Bus environment,
> and trying out Void Linux on some machines had me going through their docs
> where it's clearly stated that a session bus may be required for some 
> software.

Bug#902866: flameshot: Will not run, exits with error "Could not connect to display"

[Hendrik Jäger]

Hi Prescott

Do you still have this issue?

> I just realized the issue, although it doesn't seem to be related to 
> flameshot directly. The program runs as a D-BUS service, and for some reason 
> the DISPLAY environment variable isn't being set.

This sounds like this bug needs to be reassigned to some other package.
I’m thinking your (dbus) environment is not initialized correctly when starting 
your X-session. How do you start it?
Do you use some Display Manager, like xdm, gdm, etc.?
How do you select to start bspwm: via a menu in your DM, after logging into 
your DM, from your ~/.xsession, ~/.xinitrc, etc.?

Please report back so proper steps can be taken.

Cheers

henk

On Mon, 20 Aug 2018 14:59:39 + Prescott Hidalgo-Monroy 
 wrote:
> Hi,
> 
> I just realized the issue, although it doesn't seem to be related to 
> flameshot directly. The program runs as a D-BUS service, and for some reason 
> the DISPLAY environment variable isn't being set. The issue is resolved by 
> running
> 
> dbus-update-activation-environment DISPLAY XAUTHORITY
> 
> I had to do the same with systemd and implement a DISPLAY set in my startup 
> script in order for dunst to work as a non-root user. These issues didn't 
> come up under Stretch, so I'm not sure what changed when upgrading to Testing.
> 
> 
> Regards,
> Prescott Hidalgo-Monroy
> 
> ‐‐‐ Original Message ‐‐‐
> On July 3, 2018 9:05 PM, Boyuan Yang <073p...@gmail.com> wrote:
> 
> > Control: tag -1 + help
> > 
> 
> > 在 2018年7月4日星期三 CST 上午12:41:49，Prescott Hidalgo-Monroy 写道：
> > 
> 
> > > Just tried with the bspwm version in the Buster repos, still have the same
> > > issue and error messages.
> > > Regards,
> > > Prescott HM
> > 
> 
> > Hi,
> > 
> 
> > Unfortunately I couldn't reproduce your problem on all major DEs and some 
> > WMs.
> > I am not able to test bspwm at this moment. I'd suggest that you report this
> > problem to upstream http://github.com/lupoDharkael/flameshot meanwhile.
> > 
> 
> > ---
> > 
> 
> > Regards,
> > Boyuan Yang
> > 
> 
> > > ‐‐‐ Original Message ‐‐‐
> > > On July 2, 2018 12:18 PM, Prescott Hidalgo-Monroy  > 
> 
> > monroy.com> wrote:
> > 
> 
> > > > Using git upstream bspwm v0.9.5-5-g229b6fd, and it's all local use.
> > > > I might try the bspwm version from the repos as well, it's on v0.9.5-1.
> > > > Regards,
> > > > Prescott
> > > > ‐‐‐ Original Message ‐‐‐
> > > > On July 2, 2018 10:10 AM, Boyuan Yang 073p...@gmail.com wrote:
> > > > 
> 
> > > > > Control: severity -1 important
> > > > > Control: tag -1 + moreinfo
> > > > > 在 2018年7月2日星期一 CST 下午10:33:29，Prescott 写道：

Bug#774232: recommend using a wired connexion

[Hendrik Boom]

On Sun, Jan 29, 2023 at 09:39:41PM -0500, Antoine Beaupré wrote:
> On 2019-03-18 21:03:14, Paul Gevers wrote:
> > Hi Antoine,
> >
> > On 16-03-2019 15:46, Antoine Beaupré wrote:
> >> On 2019-03-16 15:18:27, Paul Gevers wrote:
> >>> On Mon, 05 Jan 2015 15:59:51 -0500 Antoine =?utf-8?Q?Beaupr=C3=A9?=
> >>>  wrote:
> >>>> On 2015-01-05 15:52:23, Andrei POPESCU wrote:
> >>>>> There might however be an issue with remote upgrades over wireless 
> >>>>> connections handled by Network Manager as it still reinitializes the 
> >>>>> connection on service restart, so doing a remote upgrade over wireless 
> >>>>> could under specific circumstances lead to problems.
> >>>>
> >>>> That. Exactly. :) I would be terrified of doing a remote upgrade over
> >>>> wifi, and that's probably because I know a little more what I am doing
> >>>> than the average Debian user - so I think it makes sense to warn against
> >>>> that particular foot-shooting device.
> >>>
> >>> I expect this is still an issue, but I wonder how hypothetical this is.
> >>> Is there any evidence that this is a real issue? I would update remotely
> >>> over WiFi myself, but ...
> >>>
> >>> So, if we want to share our worries, how to phrase this? Does the
> >>> following make sense?
> >>> """
> >>> Upgrading systems remotely that are connected via WiFi managed by
> >>> Network Manager isn't recommended. Network Manager re-initializes the
> >>> connection on service restart which could lead to problems under certain
> >>> circumstances.
> >>> """
> >> 
> >> The thing is am I do not believe the Debian package restarts network
> >> manager automatically. I have needrestart here for stuff like that, and
> >> even *that* blocks that automated restart by default...
> >
> > So you changed you mind since you filed the bug? Or am I
> > misunderstanding you now?
> 
> So I'm not sure anymore. It's been a *long* time now, and I am not sure
> exactly why I filed that bug... I wish I had been more explicit on the
> "why" back then and an actual failure mode I experienced. I'm pretty
> sure there *was* something, but I can't trace it right now.
> 
> Now that we're working on bookworm, I think I agree that we should move
> on.

I suspect the connection manager does get restarted on upgrade. 

I'm on Devuan chimaera, so things may be different for me.

But whenever I do an upgrade, I start by overriding the entry in rexolv.conf 
that the connection manager put there ao that I get a regular DNS location (I 
usually choose 8.8.8.8 because I can remember it.)

(why do I do that?  Because long long ago the connection manager seems to have 
memorized a particular one of Devuan's mirrors and now it always gives me that 
one and it happens to be broken).  I will get it even if it is no longer i the 
list of Devuan mirrors..

But 8.8.8.8 gets me a new one, and that one works.

The entire upgrade than works cleanly, but afterward, if I look at resolv.conf, 
it has again been overwritten by the connection manager,

So I conclude that it has been restarted.

So I conclude that the upgrade does indeed restart the connection manager.

No problem on my laptop.  But I imagine it could cause problems on a remote 
device it I were to lose contact.

-- hendrik

> 
> I still think that people should use a wired connexion for upgrades, but
> I am not feeling so strongly about this that it should be part of the
> upgrade procedure. In fact, I believe I have myself done upgrades over
> wifi without too much problems recently.
> 
> I don't actually buy the "wifi firmware goes away" theory anymore, and
> if network manager restarts, who cares? You already have the packages
> downloaded at this point and the worse that could happen there is that
> you lose your network, which is something a reboot (which you need to do
> anyways) would do as well.
> 
> So yeah, let's move on, and thanks for nursing all those bugs all those
> years. :)
> 
> a.
> -- 
> La propriété est un piège: ce que nous croyons posséder nous possède.
> - Alphonse Karr
> 

Bug#1029273: linux-image-6.1.0-1-amd64: screen on usb-c dock works only once

[Hendrik Tews]

Package: src:linux
Version: 6.1.4-1
Severity: important
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

-- Package-specific info:
** Version:
Linux version 6.1.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39.90.20221231) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-1-amd64 root=/dev/mapper/cert2--vg-root1 ro quiet

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[  134.076872] usb 7-1.1: Manufacturer: Realtek
[  134.076874] usb 7-1.1: SerialNumber: 30101
[  134.225874] usb 7-1.3: new SuperSpeed Plus Gen 2x1 USB device number 8 using 
xhci_hcd
[  134.250618] usb 7-1.3: New USB device found, idVendor=17ef, idProduct=a393, 
bcdDevice= d.23
[  134.250630] usb 7-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[  134.250634] usb 7-1.3: Product: USB3.1 Hub
[  134.250637] usb 7-1.3: Manufacturer: VIA Labs, Inc.
[  134.280923] hub 7-1.3:1.0: USB hub found
[  134.281211] hub 7-1.3:1.0: 4 ports detected
[  134.286267] [drm] DP Alt mode state on HPD: 1
[  134.344854] usb 7-1.1: reset SuperSpeed USB device number 7 using xhci_hcd
[  134.379153] r8152 7-1.1:1.0 (unnamed net_device) (uninitialized): Invalid 
header when reading pass-thru MAC addr
[  134.379247] r8152 7-1.1:1.0: firmware: direct-loading firmware 
rtl_nic/rtl8153b-2.fw
[  134.391120] [drm] DM_MST: starting TM on aconnector: 15f96e41 [id: 
94]
[  134.396619] r8152 7-1.1:1.0: load rtl8153b-2 v1 10/23/19 successfully
[  134.429215] r8152 7-1.1:1.0 eth0: v1.12.13
[  134.658821] [drm] Downstream port present 1, type 0
[  134.820305] usb 6-1.3.3: new high-speed USB device number 12 using xhci_hcd
[  134.884639] r8169 :02:00.0 enp2s0f0: Link is Down
[  134.987820] usb 6-1.3.3: New USB device found, idVendor=17ef, 
idProduct=a395, bcdDevice=60.90
[  134.987828] usb 6-1.3.3: New USB device strings: Mfr=10, Product=11, 
SerialNumber=0
[  134.987831] usb 6-1.3.3: Product: USB2.0 Hub
[  134.987834] usb 6-1.3.3: Manufacturer: Lenovo
[  135.048952] hub 6-1.3.3:1.0: USB hub found
[  135.049262] hub 6-1.3.3:1.0: 4 ports detected
[  135.063149] r8152 7-1.1:1.0 enxf4a80d209805: renamed from eth0
[  135.140301] r8169 :05:00.0 enp5s0: Link is Down
[  135.340541] usb 6-1.3.3.1: new full-speed USB device number 13 using xhci_hcd
[  135.468641] usb 6-1.3.3.1: New USB device found, idVendor=17ef, 
idProduct=a38f, bcdDevice= 0.00
[  135.468653] usb 6-1.3.3.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  135.468657] usb 6-1.3.3.1: Product: 40AS
[  135.468659] usb 6-1.3.3.1: Manufacturer: Cypress Semiconductor
[  135.468662] usb 6-1.3.3.1: SerialNumber: 1S40ASZKW2Y1ZW
[  135.540345] hid-generic 0003:17EF:A38F.0006: hiddev1,hidraw3: USB HID v1.11 
Device [Cypress Semiconductor 40AS] on usb-:07:00.4-1.3.3.1/input1
[  135.620675] usb 6-1.3.3.2: new full-speed USB device number 14 using xhci_hcd
[  135.930244] usb 6-1.3.3.2: New USB device found, idVendor=17ef, 
idProduct=a396, bcdDevice= 0.14
[  135.930258] usb 6-1.3.3.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  135.930262] usb 6-1.3.3.2: Product: ThinkPad USB-C Dock Gen2 USB Audio
[  135.930265] usb 6-1.3.3.2: Manufacturer: Lenovo
[  135.930268] usb 6-1.3.3.2: SerialNumber: 
[  136.146506] input: Lenovo ThinkPad USB-C Dock Gen2 USB Audio as 
/devices/pci:00/:00:08.1/:07:00.4/usb6/6-1/6-1.3/6-1.3.3/6-1.3.3.2/6-1.3.3.2:1.3/0003:17EF:A396.0007/input/input34
[  136.204901] hid-generic 0003:17EF:A396.0007: input,hidraw4: USB HID v1.11 
Device [Lenovo ThinkPad USB-C Dock Gen2 USB Audio] on 
usb-:07:00.4-1.3.3.2/input3
[  136.512476] usb 6-1.2: new high-speed USB device number 15 using xhci_hcd
[  136.664411] usb 6-1.2: New USB device found, idVendor=18d1, idProduct=4ee1, 
bcdDevice= 4.40
[  136.664423] usb 6-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  136.664426] usb 6-1.2: Product: Pixel 3a
[  136.664429] usb 6-1.2: Manufacturer: Google
[  136.664431] usb 6-1.2: SerialNumber: 9B1AY1GLXS
[  137.339778] IPv6: ADDRCONF(NETDEV_CHANGE): enxf4a80d209805: link becomes 
ready
[  137.340023] r8152 7-1.1:1.0 enxf4a80d209805: carrier on
[  144.634720] audit: type=1400 audit(1674224479.785:57): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2465 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  144.637641] audit: type=1400 audit(1674224479.785:58): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2465 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  144.655736] audit: type=1400 audit(1674224

Bug#1028381: kwrite depends on kate, but shouldn't

[Hendrik Lehmbruch]

Package: kwrite
Version: 4:22.12.1-1
Severity: normal

Dear Maintainer,

Is there a reason why kwrite depends on kate? While kate did not depends on
kwrite, both depends on ktexteditor-katepart, but ktexeditor-katepart did  not
depend on both.

It should be possible to install kwrite without installing kate (or remove kate
without removing kwrite), and if i understand this right -> https://kate-
editor.org/post/2022/2022-03-31-kate-ate-kwrite/ <- it should work.

So why kwrite depends on kate?

Would it be possible to demote kate to a suggestion?

Greetings

Hendrik Lehmbruch


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.4-1-siduction-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kwrite depends on:
ii  kate  4:22.12.1-1
ii  ktexteditor-katepart  5.101.0-2
ii  libc6 2.36-8
ii  libkf5coreaddons5 5.101.0-1
ii  libkf5dbusaddons5 5.101.0-1
ii  libkf5i18n5   5.101.0-1+b1
ii  libqt5core5a  5.15.7+dfsg-2
ii  libqt5gui55.15.7+dfsg-2
ii  libqt5widgets55.15.7+dfsg-2
ii  libstdc++612.2.0-14

kwrite recommends no packages.

kwrite suggests no packages.

-- no debconf information

Bug#1000627: apache2: missing dependency setting

[Hendrik Jäger]

Control: tags -1 upstream

Hi

On Fri, 3 Jun 2022 23:53:50 +0200 Michael Biebl  wrote:
> I'd like to refer to https://systemd.io/NETWORK_ONLINE/ as well.
> Especially to "Should network-online.target be used?" which suggest 
> better and more robust options then using network-online.target

AFAICT there is an upstream bugreport for implementing IP_FREEBIND:
https://bz.apache.org/bugzilla/show_bug.cgi?id=58725
This seems to have already been implemented, at least in 2.5/trunk:
https://httpd.apache.org/docs/trunk/mod/mpm_common.html#listen

Since this bug only occurs when the user specifies an IP address to listen on, 
our default config is not affected AFAIU.
So the easiest way to fix this bug is to wait and maybe add a comment before 
the default 'Listen' directives to add the freebind option when changing the 
'Listen' to a specific IP address.
This can only be done once we package a release containing that option, though.

In the meantime the only workaround seems to be to wait for the 
network-online.target but since this is not necessary for the stock config, I 
don’t really want to do that.

Bug#1004275: php upgrade apache2: After upgrade php install apache2 and i have intalled lighttpd

[Hendrik Jäger]

Control: tags -1 moreinfo
Control: reassign php

Hi

Thank you for your report.

On Mon, 24 Jan 2022 01:33:24 +0100  wrote:
> After apt update & upgrade a new php update appear but the upgrade also 
> installed apache2.

Can you provide a log of your commands and outputs?
Which php package(s) were updated from which version to which version?

> I am running lighttpd server and apache2 it's not neccesary on my system.

Makes sense. Which version of lighthttpd is installed?

I’m reassigning this package to php, exclusively, because I don’t think any 
change in the apache2 package(s) can fix the issue.

Cheers

henk

Bug#745605: please retest

[Hendrik Jäger]

Control: tags -1 -fixed-upstream

It seems this bugreport was tagged 'fixed-upstream' automatically after the 
upstream bug was closed automatically due to age or inactivity.

AFAICT the bug is not fixed, the change proposed in [1] / [2] does not seem to 
be applied, see [3].

Someone would need to retest this (as described in upstream’s bugtracker’s 
closing comment), report back, and depending on result either close this bug or 
reopen upstream’s bug; or alternatively provide a minimal example how to 
reproduce it for someone else to test.

Thanks!

[1]: https://bz.apache.org/bugzilla/show_bug.cgi?id=35049#c1
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745605#55
[3]: 
https://svn.apache.org/viewvc/httpd/httpd/trunk/server/protocol.c?view=markup#l80

Bug#714083: default-ssl.conf should also be prefixed with 000- to be sure to be first ssl virtualhost

[Hendrik Jäger]

Control: retitle -1 default-ssl.conf should also be prefixed with 000- to be 
sure to be first ssl virtualhost
Control: severity -1 normal
Control: tags -1 help

Increased severity because this does easily cause problems, unexpected 
behaviour, confusion, and support requests when an ssl vhost is put in a config 
with a filename that is sorted before 'default-ssl.conf', e.g. 
'custom-vhost.conf' or 'a-vhost.conf'.

There is already a pull request [1] that was already merged but then reverted 
because changing this config file’s name is not trivial and I had not thought 
of how to do this migration on productive systems.
Concrete questions are:
* how to deal with this on all variations of systems
** unchanged, not activated (will dpkg/ucf/whatever-handles-these-config-files 
do the right thing? I guess the old file will be removed and the new file 
placed, but how to be certain?)
** changed, not activated (what do we do? move the existing file? remove it, 
install the new?)
** unchanged, activated (similar to first variant, but how to deal with the 
symlink in sites-enabled/?)
** changed, activated (do we even do anything in this case or just assume that 
it’s working as intended and leave the admin to it?)

Concrete suggestions, patches, references to relevant docs, merge requests, 
etc. welcome!

Cheers

henk

Bug#1006921: apache2: security.conf can be improved

[Hendrik Jaeger]

Hi

I took your suggestions and prepared some merge requests.

On Tue, 08 Mar 2022 03:10:00 -0600 Daniel Lewart  wrote:
> The attached patch improves security.conf (last updated Jun 24, 2015)
> in the following ways:
>   * Change Subversion example to git and improve it

I have changed the subversion example and added the same for git.
https://salsa.debian.org/apache-team/apache2/-/merge_requests/29

>   * Change obsolete X-Frame-Options to Content-Security-Policy

https://salsa.debian.org/apache-team/apache2/-/merge_requests/30
I removed the link to the docs here and …

>   * Add reference URLs to comments

… also here.
IMHO these references should not be part of the config files because keeping 
them up to date will cause these files to change on production systems which is 
unnecessary noise.
People can search the Web for these directives and mechanisms or refer to the 
official Apache HTTPd manual if they need to look something up.

>   * Change indentation from spaces to tabs

Also a merge request:
https://salsa.debian.org/apache-team/apache2/-/merge_requests/32

Related: uncommenting that example:
https://salsa.debian.org/apache-team/apache2/-/merge_requests/33

I’m not really involved in packaging, just currently trying to improve the 
apache packaging (because I have other things to do but love Productive 
Procrastination), so I can’t promise that any of this will be merged …

Thanks for your inputs, nevertheless!

henk

Bug#1023810: acct: Initscript complains about non-existant /var/lock/subsys/

[Hendrik Jaeger]

Package: acct
Version: 6.6.4-4
Severity: normal
X-Debbugs-Cc: debian-b...@henk.geekmail.org

Dear Maintainer,

   * What led up to the situation?

A mail from Anacron containing:
/etc/cron.daily/acct:
touch: cannot touch '/var/lock/subsys/acct': No such file or directory

Running the initscript manually gives the same error.

(Accounting needs to be enabled in /etc/default/acct or the error will
not occur)

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

/var/lock/subsys/ does not exist on my sysvinit-based systems:
# namei -l '/var/lock/subsys/acct'
f: /var/lock/subsys/acct
drwxr-xr-x root root /
drwxr-xr-x root root var
lrwxrwxrwx root root lock -> /run/lock
drwxr-xr-x root root   /
drwxr-xr-x root root   run
drwxrwxrwt root root   lock
 subsys - No such file or directory

AFAIU this directory is created on systemd-based systems but does not
seem to get created on sysvinit-based systems.
Since it’s on a tmpfs, creating it manually would not help permanently:
# df -h /var/lock/
Filesystem  Size  Used Avail Use% Mounted on
tmpfs   5.0M 0  5.0M   0% /run/lock


I don’t know where this directory is supposed to be coming from on
sysvinit-based systems.
Maybe the acct initscript should check whether it exists and create it
if needed?

Thanks

Hendrik


-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-15-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages acct depends on:
ii  init-system-helpers  1.60
ii  libc62.31-13+deb11u3
ii  lsb-base 11.1.0

acct recommends no packages.

acct suggests no packages.

-- no debconf information

Bug#1010156: logiops: systemd incompatibility - mouse mapping does not work

[Hendrik Tews]

Package: logiops
Version: 0.2.2-2
Severity: normal
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

thanks a lot for packaging this driver!

Unfortunately, the packaged version is incompatible with the
version of systemd currently shipped in testing, see
https://github.com/PixlOne/logiops/commit/911e91eeebf72417d081e2b0f7e3d4c6db83c37b

For me, the symptom is that button remapping of my MX Master 3
mouse does not work, while the invert hiresscroll feature did
work.

The upstream version from github works fine for me.

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

Kernel: Linux 5.16.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages logiops depends on:
ii  libc6   2.33-7
ii  libconfig++9v5  1.5-0.4
ii  libevdev2   1.12.1+dfsg-1
ii  libgcc-s1   12-20220319-1
ii  libstdc++6  12-20220319-1
ii  libudev1250.4-1

logiops recommends no packages.

logiops suggests no packages.

-- Configuration Files:
/etc/logid.cfg changed:
devices: ({
  name: "Wireless Mouse MX Master 3";
  # A lower threshold number makes the wheel switch to free-spin mode
  # quicker when scrolling fast.
  smartshift: {
on: false;
threshold: 3;
  };
  hiresscroll: {
hires: true;
invert: false;
target: false;
  };
  # Higher numbers make the mouse more sensitive (cursor moves faster),
  # 4000 max for MX Master 3.
  dpi: 1000;
  buttons: (
# Make thumb button 2.
{ cid: 0xc3;
  action = {
type: "Keypress";
keys: ["BTN_MIDDLE"];
  };
},
# top button
{ cid: 0xc4;
  action = {
type = "ToggleSmartshift";
  };
}
  );
});


-- no debconf information

Bye,

Hendrik

Bug#998824: firefox hangs randomly

[Hendrik Lehmbruch]

Package: firefox
Version: 94.0-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
So I played around with soundcloud, no problems at all ,as long as the
addblocker is disabled ;)

FF hangs when I follow a link, and it doesn't load!
If the link loads fast, there is no problem, strange, very strange.
When I restart FF the problem with that link is gone.
Maybe they were too fast to enable that egl feature.
So at the most time of using FF there are no problems, maybe it is an addon
like uBlock or something similar causing it!?

I can reproduce it, open many links till it starts to get slow and slower to
open a link because it needs more and more bandwidth, by stressing the
connection. (started FF in the --safe-mode)


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


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.1-1-siduction-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox depends on:
ii  debianutils  5.5-1
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libc62.32-4
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-3
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi8  3.4.2-3
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.11.0+dfsg-1
ii  libgcc-s111.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.1-1
ii  libgtk-3-0   3.24.30-3
ii  libnspr4 2:4.32-1
ii  libnss3  2:3.72-1
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libstdc++6   11.2.0-10
ii  libvpx7  1.11.0-2
ii  libx11-6 2:1.7.2-2+b1
ii  libx11-xcb1  2:1.7.2-2+b1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:5.0.3-2
ii  libxrandr2   2:1.5.2-1
ii  procps   2:3.3.17-5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages firefox recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.4.1-1+b1

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-6.1
ii  fonts-stix [otf-stix]  1.1.1-4.1
ii  libcanberra0   0.30-8
ii  libgssapi-krb5-2   1.18.3-7
ii  pulseaudio 15.0+dfsg1-2

-- no debconf information

Bug#992555: probably same on Dell Inspiron 3580

[Hendrik Buchner]

> Hi,
> 
> both: after upgrade from Buster and after clean install laptop does
> not wake up when opening lid. Simply freezes, only power off helps.
> 
> When I boot Bullseye with 4.19 kernel it works.
> 
> Regards,
> Piotr A. Dybczyński
> -- 
> /**
>   dr Piotr A. Dybczyński 
>  homepage: https://www.dybczynski.pl/Piotr e-mail:
> pi...@dybczynski.pl
> PAD***/
> 
> 
Hi,

I found out, that disabling Intels VT-d in the BIOS let the suspend and
resume work again with kernel 5.10.
Can you please check and confirm this on your laptop?

Bug#992555: 5.14 also affected

[Hendrik Buchner]

I've installed 5.14 from bullseye backports and it's also affected. It
seems that something has changed from 4.x to 5.x-Series.

Bug#997943: systemd: Persistent attribute of timer is ignored

[Hendrik Buchner]

> This appears to be inconsistent imho.
>
> Somehow I think systemd could be more clever here and scale down
> RandomizedDelaySec= on boot depending on how far in the past the
> timestamp of the stampfile is.
> Say the last activation of the service was 12 hours ago, then scale
> down RandomizedDelaySec=12h by dividing it by 12, so it would become
> RandomizedDelaySec=1h. The further in the past, the shorter the delay
> would become and the more likely that the timer fires eventually.
>
> And for consistencies sake, a (scaled) RandomizedDelaySec=1 should
> also be reapplied on resume.
>

That's right, if systemd would be capable of this behaviour, it would be
very helpfull to not end up in a never updated system for example (like
it might happen to my systems).

Bug#997943: systemd: Persistent attribute of timer is ignored

[Hendrik Buchner]

Hello Michael and Julian,

that explains why the behaviour of "RandomizedDelaySec" together with
"Persistent" is different between buster and bullseye. If that's the
intended behaviour, my systems seems to work like they should and it's
no bug.
So for me I will change the delay from 12h to maybe 5min. I think that
will fit better to my use case.
Thanks a lot for your research and explanation of the timers.

Regards

Hendrik

Bug#997943: systemd: Persistent attribute of timer is ignored

[Hendrik Buchner]

>Is this issue only reproducible with apt-daily.timer and
>apt-daily-upgrade.timer works correctly?

I think so, but I will observe it for the next days.

>Does this issue happen reproducibly? Say "systemctl status
>apt-daily.timer" shows that the timer is about to elapse in 5 hours. If
>you shut down the system before that and start it after that,
>apt-daily.service is not run with 100% certainty?

Yes, that's correct.

>Can you mark in the log, when you upgraded your system

I think it was at 15. August, one day after bullseye was released.

>at what times you shutdown/started the system and where exactly you
>expected the timer to fire

That's different, but it's easy to see when you compare both logs. As
you can see the last execution of "apt-daily" was "Okt 24 19:34:45".
In the log of "apt-daily-upgrade" you see that the system was running
at "Okt 25 16:08:30" and "Okt 26 21:10:30" and "Okt 27 15:45:00".
So with the options of "apt-daily.timer" (OnCalendar=*-*-* 6,18:00
RandomizedDelaySec=12h) it should have been executed since then because
there were missed timers.
For normal the computer is not running for only 1 minute so that
the timespan is too short for execution (apt-daily-upgrade had also
enough time for execution).

Bug#997943: systemd: Persistent attribute of timer is ignored

[Hendrik Buchner]

I've attached the output of "journalctl -u apt-daily.service" and as
you can see, it has not been running as often as
"apt-daily-upgrade.service"
-- Journal begins at Sun 2021-08-15 08:33:03 CEST, ends at Wed 2021-10-27 
16:11:14 CEST. --
Aug 15 08:57:42 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Aug 15 08:57:42 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Aug 15 08:57:42 HendrikDesktop systemd[1]: Started Daily apt download 
activities.
-- Boot 8bcc8b56436d47d8816dd4989a2e91ea --
Aug 16 11:02:41 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Aug 16 11:02:52 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Aug 16 11:02:52 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Aug 16 11:02:52 HendrikDesktop systemd[1]: apt-daily.service: Consumed 5.892s 
CPU time.
-- Boot eac17eef52814025972b053869dc43fe --
Aug 25 12:51:20 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Aug 25 12:51:34 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Aug 25 12:51:34 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Aug 25 12:51:34 HendrikDesktop systemd[1]: apt-daily.service: Consumed 5.831s 
CPU time.
-- Boot f2f96db9cb3e42d7a5a785f1276beb4d --
Aug 27 17:46:53 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Aug 27 17:47:06 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Aug 27 17:47:06 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Aug 27 17:47:06 HendrikDesktop systemd[1]: apt-daily.service: Consumed 5.907s 
CPU time.
-- Boot b1f151c44fa642abbac067531fba592d --
Aug 28 14:18:20 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Aug 28 14:18:30 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Aug 28 14:18:30 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Aug 28 14:18:30 HendrikDesktop systemd[1]: apt-daily.service: Consumed 6.072s 
CPU time.
-- Boot d2e1da510d2041528f8d5459cac991c7 --
Aug 29 11:42:58 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Aug 29 11:43:04 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Aug 29 11:43:04 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Aug 29 11:43:04 HendrikDesktop systemd[1]: apt-daily.service: Consumed 5.818s 
CPU time.
Aug 29 19:59:06 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Aug 29 19:59:13 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Aug 29 19:59:13 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
-- Boot f617d9b40dac4ce8b512433965fc48cb --
Aug 30 16:04:07 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Aug 30 16:04:13 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Aug 30 16:04:13 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Aug 30 16:04:13 HendrikDesktop systemd[1]: apt-daily.service: Consumed 5.707s 
CPU time.
Aug 30 22:35:47 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Aug 30 22:35:48 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Aug 30 22:35:48 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
-- Boot fd98891fe1ee43388cddc29af892d542 --
Sep 05 17:21:07 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Sep 05 17:21:15 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Sep 05 17:21:15 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Sep 05 17:21:15 HendrikDesktop systemd[1]: apt-daily.service: Consumed 7.087s 
CPU time.
-- Boot 6829dbf0502e41e5b400f311f16ad026 --
Sep 12 22:14:00 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Sep 12 22:14:26 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Sep 12 22:14:26 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Sep 12 22:14:26 HendrikDesktop systemd[1]: apt-daily.service: Consumed 12.531s 
CPU time.
-- Boot 72a07b4cb11f43d28c19c6204ecb3e1f --
Sep 13 09:28:10 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Sep 13 09:28:17 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Sep 13 09:28:17 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Sep 13 09:28:17 HendrikDesktop systemd[1]: apt-daily.service: Consumed 6.145s 
CPU time.
-- Boot 32f6c3239cf648ed9e08c4a2f6968768 --
Sep 14 12:25:52 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Sep 14 12:25:58 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Sep 14 12:25:58 HendrikDesktop systemd[1]: Finished Daily apt download 
activities.
Sep 14 12:25:58 HendrikDesktop systemd[1]: apt-daily.service: Consumed 5.959s 
CPU time.
-- Boot 9c111d1a11e94b85a74216639f21a6ea --
Sep 16 20:04:32 HendrikDesktop systemd[1]: Starting Daily apt download 
activities...
Sep 16 20:04:38 HendrikDesktop systemd[1]: apt-daily.service: Succeeded.
Sep 16 20:04:38 HendrikDesktop systemd[1]: Finished Daily apt 

Bug#997943: systemd: Persistent attribute of timer is ignored

[Hendrik Buchner]

Hello Michael,

my system isn't running on battery because it's a Desktop-PC and not a
laptop. I've observed this behaviour now on 3 of my computers (2
Desktop-PCs and 1 laptop).

Attached you can find the output of your "journalctl", but on this
system I haven't already changed the timer. If you need the output from
a system which has already a modified timer please contact me.

Regards

Hendrik

On Wed, 27 Oct 2021 15:05:02 +0200
Michael Biebl  wrote:

> Control: tags -1 + unreproducible moreinfo
>
> Hello,
>
> unfortunately, I can not confirm the issue (thus marking the bug
> report accordingly).
>
> Persistent timers are correctly "remembered" when shutdown/rebooted.
>
> Have you seen that apt-daily-upgrade.service has
> ConditionACPower=true
>
> Maybe your system is not updated because it ran on battery when the
> timer fired?
>
>
> Can you send me the "journalctl -u apt-daily-upgrade.service"
> log after the dist upgrade until you locally modified the timer.
>
> Regards,
> Michael
-- Journal begins at Sun 2021-08-15 08:33:03 CEST, ends at Wed 2021-10-27 
15:45:46 CEST. --
Aug 15 08:33:10 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Aug 15 08:33:15 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 15 08:33:15 HendrikDesktop systemd[1]: Started Daily apt upgrade and clean 
activities.
-- Boot f0005b8e1ce7461a81bac6cf42abfa2d --
Aug 16 10:14:39 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Aug 16 10:14:41 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 16 10:14:41 HendrikDesktop systemd[1]: Finished Daily apt upgrade and clean 
activities.
Aug 16 10:14:41 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Consumed 
2.456s CPU time.
-- Boot b3a1c412838d450aa1e3fbb0f1f05710 --
Aug 24 22:35:33 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Aug 24 22:35:33 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 24 22:35:33 HendrikDesktop systemd[1]: Finished Daily apt upgrade and clean 
activities.
-- Boot eac17eef52814025972b053869dc43fe --
Aug 25 11:23:24 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Aug 25 11:23:27 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 25 11:23:27 HendrikDesktop systemd[1]: Finished Daily apt upgrade and clean 
activities.
Aug 25 11:23:27 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Consumed 
3.110s CPU time.
-- Boot f2f96db9cb3e42d7a5a785f1276beb4d --
Aug 27 11:13:53 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Aug 27 11:13:56 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 27 11:13:56 HendrikDesktop systemd[1]: Finished Daily apt upgrade and clean 
activities.
Aug 27 11:13:56 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Consumed 
3.071s CPU time.
-- Boot b1f151c44fa642abbac067531fba592d --
Aug 28 13:15:33 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Aug 28 13:15:36 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 28 13:15:36 HendrikDesktop systemd[1]: Finished Daily apt upgrade and clean 
activities.
Aug 28 13:15:36 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Consumed 
3.157s CPU time.
-- Boot d2e1da510d2041528f8d5459cac991c7 --
Aug 29 11:15:31 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Aug 29 11:15:34 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 29 11:15:34 HendrikDesktop systemd[1]: Finished Daily apt upgrade and clean 
activities.
Aug 29 11:15:34 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Consumed 
3.143s CPU time.
-- Boot f617d9b40dac4ce8b512433965fc48cb --
Aug 30 13:41:16 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Aug 30 13:41:20 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 30 13:41:20 HendrikDesktop systemd[1]: Finished Daily apt upgrade and clean 
activities.
Aug 30 13:41:20 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Consumed 
3.163s CPU time.
-- Boot c6eaaf590b0742358327072575d70e3b --
Sep 01 14:39:53 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Sep 01 14:39:56 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Sep 01 14:39:56 HendrikDesktop systemd[1]: Finished Daily apt upgrade and clean 
activities.
Sep 01 14:39:56 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Consumed 
3.034s CPU time.
-- Boot 2f18728d597147b19066035e836c3ec7 --
Sep 02 19:31:24 HendrikDesktop systemd[1]: Starting Daily apt upgrade and clean 
activities...
Sep 02 19:31:28 HendrikDesktop systemd[1]: apt-daily-upgrade.service: Succeeded.
Sep 02 19:31:28 HendrikDesktop systemd[1]: Finished Daily apt upgrade and clean 
activities.
Sep 02 19:31:28 HendrikDesktop systemd[1]: a

Bug#992555: 5.10.0-9 still affected

[Hendrik Buchner]

I've done the upgrade from 11.0 to 11.1. The new kernel 5.10.0-9 is
still affected and the oldstable 4.19 still does the job.

Bug#994692: RFA: gogglesmm -- Goggles Music Manager

[hendrik . rittich]

Package: wnpp
Severity: normal

Gogglesmm is a fast and light weight music player and music collection
browser. I have packaged Gogglesmm years ago and I have not been using it for
quite some time. Hence, I would like to find someone actually using the
package who is willing to adopt it.

The current website is

  https://gogglesmm.dev/

and the sources are located at

  https://github.com/gogglesmm/gogglesmm/ .

The Debian package got stuck on version 0.12.7, since back then it required a
newer version of libfox than was available in Debian at that time. This
might have changed and the situation should be re-evaluated.

The package should probably be ported to a recent version of devscripts. The
only open bug report is concerned with packaging a recent version:

- #739268 gogglesmm: new version available 0.13.0

I might be hard to reach these days, so feel free to adopt the package without
asking for my approval.

H.

Bug#993819: release-notes: Please document the removal of wicd

[Hendrik Boom]

On Thu, Sep 09, 2021 at 09:35:05PM +0200, Paul Gevers wrote:
> Hi Hendrik,
> 
> On 09-09-2021 21:27, Hendrik Boom wrote:
> > Here is the text I have included in the current draft upgrade 
> > instructions for Devuan:
> > 
> > Warning:  `wicd` will no longer be available after the upgrade, so if 
> > you use it to connect to the internet through wifi, you will be cut 
> > off.  To prevent this, you should change to a connection manager that 
> > *will* still be available, such as `connman`.  If you want a convnient 
> > graphical interface, without which making connections can be difficult, 
> > you should install `connman-gtk`.  You should do this *before* you 
> > start the upgrade, or you will have trouble reconnecting if things go 
> > wrong.
> 
> Isn't NetworkManager the default graphical manager nowadays? Or is there
> a link with systemd such that you wouldn't mention it for Devuan? No
> judgement intended, just wanting to have the facts straight.

When I installed devuan a few releases ago it gave me connman.  So I
knew it worked.  And I tested it on chimaera.

network-manager is also available on Devuan, so I guess, there's no 
systemd issue.  But I am loathe to recommend something I hadn't tested 
on chimaera.

-- hendrik

> 
> Paul
> 
> 

Bug#993819: release-notes: Please document the removal of wicd

[Hendrik Boom]

On Tue, Sep 07, 2021 at 06:54:05AM +0200, Joost van Baal-Ilić wrote:
> Hi,
> 
> On Mon, Sep 06, 2021 at 05:23:45PM -0400, Hendrik Boom wrote:
> > On Mon, Sep 06, 2021 at 10:01:10PM +0100, Roger Lynn wrote:
> > > Package: release-notes
> > > Severity: important
> > > 
> > > Please document the removal of wicd in Bullseye. This seems particularly
> > > dangerous if the upgrade is being done over a network connection being 
> > > managed
> > > by wicd as it seems likely that the connection will be lost when wicd is
> > > removed (due to dependency problems). It would also be helpful if 
> > > alternatives
> > > could be suggested.
> > 
> > I already did that in the draft upgrade instructions for Devuan, as 
> > something to be done before anything else. 
> > 
> > SHould I send a copy of the paragraph to this list?
> 
> Yes, that would be helpful, and please do Cc 993...@bugs.debian.org .

Here is the text I have included in the current draft upgrade 
instructions for Devuan:

Warning:  `wicd` will no longer be available after the upgrade, so if 
you use it to connect to the internet through wifi, you will be cut 
off.  To prevent this, you should change to a connection manager that 
*will* still be available, such as `connman`.  If you want a convnient 
graphical interface, without which making connections can be difficult, 
you should install `connman-gtk`.  You should do this *before* you 
start the upgrade, or you will have trouble reconnecting if things go 
wrong.

-- hendrik





> 
> Thanks, Bye,
> 
> Joost
> 

Bug#990782: inkscape: /usr/share/inkscape/fonts does not exist

[Hendrik Tews]

Mattia Rizzolo  writes:

> That said, I'll ask upstream what they think about toning down
> the lines at DEBUG level, so they don't show up by default.

Thanks,

Hendrik

Bug#990782: inkscape: /usr/share/inkscape/fonts does not exist

[Hendrik Tews]

Package: inkscape
Version: 1.0.2-4
Severity: normal
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

each time I start inkscape, it complains

   ** (org.inkscape.Inkscape:44746): WARNING **: 11:29:57.779: Fonts dir 
'/usr/share/inkscape/fonts' does not exist and will be ignored.

   ** (org.inkscape.Inkscape:44746): WARNING **: 11:29:57.779: Fonts dir 
'/home/tews/.config/inkscape/fonts' does not exist and will be ignored.

It is possible to get rid of these warnings by just creating
these directories. But if inkscape expects these directories, the
package or inkscape should create them, shouldn't they?

Thanks,

Hendrik


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

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

Versions of packages inkscape depends on:
ii  libatkmm-1.6-1v5   2.28.0-3
ii  libc6  2.31-12
ii  libcairo2  1.16.0-5
ii  libcairomm-1.0-1v5 1.12.2-4
ii  libcdr-0.1-1   0.1.6-2
ii  libdbus-glib-1-2   0.110-6
ii  libdouble-conversion3  3.1.5-6.1
ii  libfontconfig1 2.13.1-4.2
ii  libfreetype6   2.10.4+dfsg-1
ii  libgc1 1:8.0.4-3
ii  libgcc-s1  10.2.1-6
ii  libgdk-pixbuf-2.0-02.42.2+dfsg-1
ii  libgdl-3-5 3.34.0-1
ii  libglib2.0-0   2.66.8-1
ii  libglibmm-2.4-1v5  2.64.2-2
ii  libgomp1   10.2.1-6
ii  libgsl25   2.6+dfsg-2
ii  libgtk-3-0 3.24.24-4
ii  libgtkmm-3.0-1v5   3.24.2-2
ii  libgtkspell3-3-0   3.0.10-1
ii  libharfbuzz0b  2.7.4-1
ii  libjpeg62-turbo1:2.0.6-4
ii  liblcms2-2 2.12~rc1-2
ii  libmagick++-6.q16-88:6.9.11.60+dfsg-1.3
ii  libpango-1.0-0 1.46.2-3
ii  libpangocairo-1.0-01.46.2-3
ii  libpangoft2-1.0-0  1.46.2-3
ii  libpangomm-1.4-1v5 2.42.1-1
ii  libpng16-161.6.37-3
ii  libpoppler-glib8   20.09.0-3.1
ii  libpoppler102  20.09.0-3.1
ii  libpotrace01.16-2
ii  librevenge-0.0-0   0.0.4-6+b1
ii  librsvg2-common2.50.3+dfsg-1
ii  libsigc++-2.0-0v5  2.10.4-2
ii  libsoup2.4-1   2.72.0-2
ii  libstdc++6 10.2.1-6
ii  libvisio-0.1-1 0.1.7-1+b1
ii  libwpg-0.3-3   0.3.3-1
ii  libx11-6   2:1.7.1-1
ii  libxml22.9.10+dfsg-6.7
ii  libxslt1.1 1.1.34-4
ii  python33.9.2-3
ii  zlib1g 1:1.2.11.dfsg-2

Versions of packages inkscape recommends:
ii  aspell   0.60.8-2
ii  fig2dev  1:3.2.8-3+b1
ii  imagemagick  8:6.9.11.60+dfsg-1.3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3
ii  libimage-magick-perl 8:6.9.11.60+dfsg-1.3
ii  libwmf-bin   0.2.8.4-17
ii  python3-lxml 4.6.3-1
ii  python3-numpy1:1.19.5-1
ii  python3-scour0.38.2-1

Versions of packages inkscape suggests:
pn  dia   
pn  inkscape-tutorials
pn  libsvg-perl   
pn  libxml-xql-perl   
pn  pstoedit  
pn  python3-uniconvertor  
ii  ruby  1:2.7+2

-- no debconf information

Bug#919242: fails to start with apparmor enabled

[Hendrik Jaeger]

Hi

I run into a similar problem running quassel-core with the provided
init-script as a system service.
Excerpts from the audit.log are attached.

The problem is first that the ssl keyfile in /etc/ssl/private/ can not
be read. After adding this line to
/etc/apparmor.d/local/usr.bin.quasselcore
a number of other files are becoming the issue.
Also the process cannot be handled by the init-script anymore because
it’s not allowed to receive signals, it seems.
I added the following lines the local apparmor profile before giving up:
/usr/bin/quasselcore {
  #include 

  /etc/ssl/private/quassel.example.org.key r,
  /lib/i386-linux-gnu/libdl-2.28.so rm,
  /lib/i386-linux-gnu/libz.so.1.2.11 rm,
  signal (receive),
}

I then decided to just disable the apparmor profile.

This profile is provided by the apparmor package, so I’m adding onto
this package.

As it seems to make the package unusable (or maybe just with sysvinit?)
this is IMHO not wishlist but at least serious.

Is this possibly related to and fixed by #940482?

Thanks!

Hendrik
type=AVC msg=audit(1619561765.074:5182): apparmor="DENIED" operation="open" profile="/usr/bin/quasselcore" name="/etc/ssl/private/quassel.example.org.key" pid=1006 comm="quasselcore" requested_mask="r" denied_mask="r" fsuid=103 ouid=0
type=AVC msg=audit(1619561787.225:5188): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/bin/quasselcore" pid= comm="apparmor_parser"
type=AVC msg=audit(1619561792.697:5191): apparmor="DENIED" operation="signal" profile="/usr/bin/quasselcore" pid=1149 comm="start-stop-daem" requested_mask="receive" denied_mask="receive" signal=term peer="unconfined"
type=AVC msg=audit(1619561792.729:5192): apparmor="DENIED" operation="signal" profile="/usr/bin/quasselcore" pid=1173 comm="start-stop-daem" requested_mask="receive" denied_mask="receive" signal=exists peer="unconfined"
type=AVC msg=audit(1619561863.707:5203): apparmor="DENIED" operation="signal" profile="/usr/bin/quasselcore" pid=1419 comm="start-stop-daem" requested_mask="receive" denied_mask="receive" signal=term peer="unconfined"
type=AVC msg=audit(1619561863.735:5204): apparmor="DENIED" operation="signal" profile="/usr/bin/quasselcore" pid=1444 comm="start-stop-daem" requested_mask="receive" denied_mask="receive" signal=exists peer="unconfined"
type=AVC msg=audit(1619561878.338:5206): apparmor="DENIED" operation="signal" profile="/usr/bin/quasselcore" pid=17822 comm="zsh" requested_mask="receive" denied_mask="receive" signal=term peer="unconfined"
type=AVC msg=audit(1619561889.466:5207): apparmor="DENIED" operation="signal" profile="/usr/bin/quasselcore" pid=1574 comm="start-stop-daem" requested_mask="receive" denied_mask="receive" signal=term peer="unconfined"
type=AVC msg=audit(1619561899.978:5209): apparmor="DENIED" operation="signal" profile="/usr/bin/quasselcore" pid=17822 comm="zsh" requested_mask="receive" denied_mask="receive" signal=term peer="unconfined"
type=AVC msg=audit(1619561979.279:5216): apparmor="DENIED" operation="signal" profile="/usr/bin/quasselcore" pid=17822 comm="zsh" requested_mask="receive" denied_mask="receive" signal=term peer="unconfined"
type=AVC msg=audit(1619562153.658:5235): apparmor="DENIED" operation="signal" profile="/usr/bin/quasselcore" pid=2364 comm="start-stop-daem" requested_mask="receive" denied_mask="receive" signal=term peer="unconfined"
type=AVC msg=audit(1619562190.033:5241): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/bin/quasselcore" pid=2568 comm="apparmor_parser"
type=AVC msg=audit(1619562193.076:5245): apparmor="DENIED" operation="mknod" profile="/usr/bin/quasselcore" name="/var/lib/quassel/quassel-storage.sqlite-journal" pid=1006 comm="quasselcore" requested_mask="c" denied_mask="c" fsuid=103 ouid=103
type=AVC msg=audit(1619562193.116:5246): apparmor="DENIED" operation="mknod" profile="/usr/bin/quasselcore" name="/var/lib/quassel/quassel-storage.sqlite-journal" pid=1006 comm="QThread" requested_mask="c" denied_mask="c" fsuid=103 ouid=103
type=AVC m

Bug#982059: psmisc: isn't insallable

[Hendrik Lehmbruch]

Package: psmisc
Version: 23.3-1
Followup-For: Bug #982059

Dear Maintainer,

I can confirm this!

Preparing to unpack .../psmisc_23.4-1_amd64.deb ...
Unpacking psmisc (23.4-1) over (23.3-1) ...
dpkg: error processing archive /var/cache/apt/archives/psmisc_23.4-1_amd64.deb
(--unpack):
 trying to overwrite '/usr/share/man/de/man1/fuser.1.gz', which is also in
package manpages-de 4.2.0-1
Errors were encountered while processing:
 /var/cache/apt/archives/psmisc_23.4-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)




-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.13-towo.1-siduction-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages psmisc depends on:
ii  libc62.31-9
ii  libselinux1  3.1-2+b2
ii  libtinfo66.2+20201114-2

psmisc recommends no packages.

psmisc suggests no packages.

-- no debconf information

Bug#973907: sddm 0.19.0-1 doesnt remeber last session

[Hendrik Lehmbruch]

Package: sddm
Version: 0.19.0-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
upgrading sddm

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
reboot and login, now 3 times

   * What was the outcome of this action?
in my case i thought that plasma would pop up, but fluxbox appears

   * What outcome did you expect instead?
i would like to see a plasma-session (last-session) with out choosing it after
every reboot/logout and not the first in the line (fluxbox in my case)



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.6-towo.1-siduction-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sddm depends on:
ii  adduser 3.118
ii  debconf [debconf-2.0]   1.5.74
ii  libc6   2.31-4
ii  libgcc-s1   10.2.0-16
ii  libpam0g1.3.1-5
ii  libqt5core5a5.15.1+dfsg-2
ii  libqt5dbus5 5.15.1+dfsg-2
ii  libqt5gui5  5.15.1+dfsg-2
ii  libqt5network5  5.15.1+dfsg-2
ii  libqt5qml5  5.15.1+dfsg-3
ii  libqt5quick55.15.1+dfsg-3
ii  libstdc++6  10.2.0-16
ii  libsystemd0 246.6-2
ii  libxcb-xkb1 1.14-2
ii  libxcb1 1.14-2
ii  qml-module-qtquick2 5.15.1+dfsg-3
ii  x11-common  1:7.7+21
ii  xauth   1:1.0.10-1
ii  xserver-xorg [xserver]  1:7.7+21

Versions of packages sddm recommends:
ii  haveged1.9.8-4
ii  libpam-systemd 246.6-2
ii  sddm-theme-2001 [sddm-theme]   1.1
ii  sddm-theme-debian-elarun [sddm-theme]  0.19.0-1
ii  sddm-theme-patience [sddm-theme]   2018.3.0-1

Versions of packages sddm suggests:
ii  libpam-kwallet5   5.20.2-1~np1
pn  qtvirtualkeyboard-plugin  

-- debconf information:
  sddm/daemon_name: /usr/bin/sddm
* shared/default-x-display-manager: sddm

Bug#973303: fonts-noto: file conflict between fonts-noto-unhinted and fonts-noto-mono

[Hendrik Lehmbruch]

Package: fonts-noto-unhinted
Version: 20201027-1
Severity: normal

Dear Maintainer,

a full-upgrade on debian sid/unstable ends up like. see below

apt full-upgrade

- snip --
Unpacking fonts-noto-unhinted (20201027-2) over (20201027-1) ...
dpkg: error processing archive /var/cache/apt/archives/fonts-noto-
unhinted_20201027-2_all.deb (--unpack):
 trying to overwrite '/usr/share/fonts/truetype/noto/NotoMono-Bold.ttf', which
is also in package fonts-noto-mono 20201027-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
- snap ---

greetings
Hendrik Lehmbruch



-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
it  fontconfig 2.13.1-4.2amd64generic font configuration 
library - support binaries
ii  libfreetype6:amd64 2.10.2+dfsg-4 amd64FreeType 2 font engine, 
shared library files
ii  libxft2:amd64  2.3.2-2   amd64FreeType-based font drawing 
library for X

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.16-towo.1-siduction-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#969036: linux-image-5.7.0-2-amd64: system does not power off

[Hendrik Tews]

Package: src:linux
Version: 5.7.10-1
Severity: important
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

when booting this Linux version with a testing/bullseye
installation, the laptop does not power off on shutdown
(systemctl poweroff) anymore. When booting

  4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux

with buster (from a different partition) it does correctly power
off. Some web resources recommend adding "acpi=force" to
GRUB_CMDLINE_LINUX_DEFAULT. This does not help. I would
appreciate any hints or possible workarounds.

Thanks,

Hendrik Tews


-- Package-specific info:
** Version:
Linux version 5.7.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-16), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.10-1 (2020-07-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.7.0-2-amd64 root=/dev/mapper/cert--vg-root2 ro quiet

** Not tainted

** Kernel log:
[   10.797787] RAPL PMU: hw unit of domain package 2^-14 Joules
[   10.797788] RAPL PMU: hw unit of domain dram 2^-14 Joules
[   10.797788] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[   10.797788] RAPL PMU: hw unit of domain psys 2^-14 Joules
[   10.891923] Adding 9764860k swap on /dev/mapper/cert--vg-swap.  Priority:-2 
extents:1 across:9764860k SSFS
[   10.910993] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: 
(null)
[   10.917548] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b541)
[   10.929418] uvcvideo: Failed to initialize entity for entity 6
[   10.929419] uvcvideo: Failed to register entities (-22).
[   10.929798] input: Integrated Camera: Integrated C as 
/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input15
[   10.929852] usbcore: registered new interface driver uvcvideo
[   10.929853] USB Video Class driver (1.1.1)
[   10.938600] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   10.940624] Bluetooth: Core ver 2.22
[   10.940632] NET: Registered protocol family 31
[   10.940632] Bluetooth: HCI device and connection manager initialized
[   10.940635] Bluetooth: HCI socket layer initialized
[   10.940636] Bluetooth: L2CAP socket layer initialized
[   10.940638] Bluetooth: SCO socket layer initialized
[   10.943316] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: 
(null)
[   10.993647] usbcore: registered new interface driver btusb
[   11.003472] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC293: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   11.003474] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   11.003475] snd_hda_codec_realtek hdaudioC0D0:hp_outs=2 
(0x16/0x15/0x0/0x0/0x0)
[   11.003476] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   11.003477] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   11.003478] snd_hda_codec_realtek hdaudioC0D0:  Dock Mic=0x19
[   11.003479] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a
[   11.003479] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   11.008969] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   11.015593] Bluetooth: hci0: Device revision is 5
[   11.015594] Bluetooth: hci0: Secure boot is enabled
[   11.015595] Bluetooth: hci0: OTP lock is enabled
[   11.015595] Bluetooth: hci0: API lock is enabled
[   11.015596] Bluetooth: hci0: Debug lock is disabled
[   11.015596] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.016877] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 
8260, REV=0x208
[   11.024646] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-11-5.sfi
[   11.024649] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   11.027556] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
[   11.027728] iwlwifi :03:00.0: Allocated 0x0040 bytes for firmware 
monitor.
[   11.063278] audit: type=1400 audit(1598439368.339:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=567 comm="apparmor_parser"
[   11.063347] audit: type=1400 audit(1598439368.339:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=564 comm="apparmor_parser"
[   11.071470] audit: type=1400 audit(1598439368.347:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=571 
comm="apparmor_parser"
[   11.073447] audit: type=1400 audit(1598439368.351:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" 
pid=572 comm="apparmor_parser"
[   11.081619] audit: type=1400 audit(1598439368.359:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/m

Bug#961265: [homeserver] /usr/bin/docker: logs are flooded with systemd[1]: run-docker-runtime\x2drunc....mount: Succeeded.

[Hendrik Friedel]

Package: docker-ce-cli
Version: 5:19.03.8~3-0~debian-buster
Severity: normal
File: /usr/bin/docker
Tags: upstream

Dear Maintainer,

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

My logs are spammed by docker:
May 21 23:46:20 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.cryHiX.mount:
 Succeeded.
May 21 23:46:51 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.dU5ZsQ.mount:
 Succeeded.
May 21 23:47:52 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.uFcPMJ.mount:
 Succeeded.
May 21 23:48:22 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.M9hxSJ.mount:
 Succeeded.
May 21 23:48:52 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.Sz55uO.mount:
 Succeeded.
May 21 23:49:23 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.hVo3dH.mount:
 Succeeded.
May 21 23:49:53 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.R41jcK.mount:
 Succeeded.
May 21 23:50:33 homeserver systemd[1]: smartmontools.service: Got notification 
message from PID 810941, but reception only permitted for main PID which is 
currently not known
May 21 23:50:34 homeserver smartd[810941]: Device: 
/dev/disk/by-id/ata-KINGSTON_SMS200S3120G_50026B72690068A9 [SAT], SMART Usage 
Attribute: 189 Airflow_Temperature_Cel changed from 29 to 28
May 21 23:50:34 homeserver smartd[810941]: Device: 
/dev/disk/by-id/ata-KINGSTON_SMS200S3120G_50026B72690068A9 [SAT], SMART Usage 
Attribute: 194 Temperature_Celsius changed from 29 to 28
May 21 23:50:49 homeserver systemd[1]: smartmontools.service: Got notification 
message from PID 810941, but reception only permitted for main PID which is 
currently not known
May 21 23:51:24 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.uMw8YD.mount:
 Succeeded.
May 21 23:51:34 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-d9d74a027540fd2b5213c597e29f8096a180c9b642e14fa8e60fc1d5416dc704-runc.2m2TEJ.mount:
 Succeeded.
May 21 23:53:26 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.QMCRyz.mount:
 Succeeded.
May 21 23:54:26 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.rkJbbA.mount:
 Succeeded.
May 21 23:54:57 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.B2ZnEu.mount:
 Succeeded.
May 21 23:55:58 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.LTdzym.mount:
 Succeeded.
May 21 23:55:58 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.b4MwVo.mount:
 Succeeded.
May 21 23:56:58 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.m9M3yx.mount:
 Succeeded.
May 21 23:57:29 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.prbwqo.mount:
 Succeeded.
May 21 23:58:30 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.z2Bcck.mount:
 Succeeded.
May 21 23:59:30 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.RoaNNp.mount:
 Succeeded.


https://github.com/docker/for-linux/issues/679


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


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

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

Versions of packages docker-ce-cli depends on:
ii  libc6  2.28-10

docker-ce-cli recommends no packages.

docker-ce-cli suggests no packages.

-- no debconf information

Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"

[Hendrik Boom]

On Sun, May 03, 2020 at 09:34:34AM +0200, Niels Thykier wrote:
> Paul Gevers:
> > Dear Benedikt, all,
> > 
> > On 16-04-2020 10:44, Benedikt Tuchen wrote:
> >> While doing an upgrade from Stretch to Buster on a Laptop with XFS
> >> Filesystem in use. After the upgrade the laptop doesn't boot into
> >> the system because of the removed "barrier|nobarrier" mount option
> >> for XFS in version 4.19.
> >>
> >> I think this issue should be mentioned in the "5. Issues to be aware
> >> of for buster" part of the release-notes in Buster.
> > 
> > What is exactly the problem? Does everybody with XFS run into this
> > issue? Do you have a solution for the problem that we can mention? Or,
> > phrased differently, what should the user do if they have an XFS
> > filesystem and want to upgrade to buster?
> > 
> > Paul
> > 
> 
> They would have to remove the "barrier" or "nobarrier" keyword if they
> use either in their fstab (or in scripts that passes that mount option
> explicitly).
> 
> If I try to mount an XFS file system with "barrier" (or "nobarrier"), I
> get cryptic errors like this:
> """
> mount: : wrong fs type, bad option, bad superblock on ,
> missing codepage or helper program, or other error.
> """
> 
> (using mount -o ...,barrier - I don't remember if the fstab message is
> better)

Would that refer to the write battier on the hard drive?  Isn't that 
essential to the safe operation of XFS?

-- hendrik

Bug#941544: NMU upload

[Hendrik Tews]

Gard Spreemann  writes:

> If I don't hear back from anyone within three days, my AM will upload
> this NMU in DELAYED/7.

Thanks for working on this. As far as I am concerned, please
upload directly without delay.

Hendrik

Bug#919504: [kmail] blank page on print preview

[Hendrik Lehmbruch]

Package: kmail
Version: 4:18.08.3-1
Followup-For: Bug #919504

Dear Maintainer,

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

   * What led up to the situation?
Well, i tried to print an eMail
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
open the printdialog and the printpreview
   * What was the outcome of this action?
the preview shows empty page and the printer prints an empty page.
html-mails ¡and! text-mails.
¡No chance to print any mail, evry print would/is empty!
   * What outcome did you expect instead?
 A well printed page.

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

I can confirm that on to uptodate buster/sid installations 


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.20.9-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kmail depends on:
ii  akonadi-server   4:18.08.3-4
ii  kdepim-runtime   4:18.08.3-1
ii  kio  5.54.1-1
ii  libc62.28-7
ii  libgcc1  1:8.2.0-21
ii  libgpgmepp6  1.12.0-6
ii  libkf5akonadiagentbase5  4:18.08.3-4
ii  libkf5akonadicontact54:18.08.3-1
ii  libkf5akonadicore5abi2   4:18.08.3-4
ii  libkf5akonadimime5   4:18.08.3-1
ii  libkf5akonadisearch-bin  4:18.08.3-1
ii  libkf5akonadisearch-plugins  4:18.08.3-1
ii  libkf5akonadisearchdebug54:18.08.3-1
ii  libkf5akonadisearchpim5  4:18.08.3-1
ii  libkf5akonadiwidgets5abi14:18.08.3-4
ii  libkf5bookmarks5 5.54.0-1
ii  libkf5calendarcore5abi2  4:18.08.3-1
ii  libkf5calendarutils5 4:18.08.3-2
ii  libkf5codecs55.54.0-1
ii  libkf5completion55.54.0-1
ii  libkf5configcore55.54.0-1
ii  libkf5configgui5 5.54.0-1
ii  libkf5configwidgets5 5.54.0-1
ii  libkf5contacts5  4:18.08.3-1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5dbusaddons55.54.0-1
ii  libkf5followupreminder5  4:18.08.3-2
ii  libkf5grantleetheme-plugins  18.08.3-1
ii  libkf5gravatar5abi2  4:18.08.3-1
ii  libkf5guiaddons5 5.54.0-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5iconthemes55.54.0-1
ii  libkf5identitymanagement518.08.3-2
ii  libkf5itemmodels55.54.0-1
ii  libkf5itemviews5 5.54.0-1
ii  libkf5jobwidgets55.54.0-1
ii  libkf5kcmutils5  5.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5kiofilewidgets55.54.1-1
ii  libkf5kiowidgets55.54.1-1
ii  libkf5kontactinterface5  18.08.3-1
ii  libkf5ksieveui5  4:18.08.3-2
ii  libkf5libkdepim-plugins  4:18.08.3-2
ii  libkf5libkdepim5 4:18.08.3-2
ii  libkf5libkdepimakonadi5  4:18.08.3-2
ii  libkf5libkleo5   4:18.08.3-2
ii  libkf5mailcommon5abi24:18.08.3-2
ii  libkf5mailtransport5 18.08.3-2
ii  libkf5mailtransportakonadi5  18.08.3-2
ii  libkf5messagecomposer5abi1   4:18.08.3-1
ii  libkf5messagecore5abi1   4:18.08.3-1
ii  libkf5messagelist5abi1   4:18.08.3-1
ii  libkf5messageviewer5abi1 4:18.08.3-1
ii  libkf5mime5abi1  18.08.3-1
ii  libkf5mimetreeparser5abi14:18.08.3-1
ii  libkf5notifications5 5.54.0-1
ii  libkf5notifyconfig5  5.54.0-1
ii  libkf5parts5 5.54.0-1
ii  libkf5pimcommon5abi2 4:18.08.3-2
ii  libkf5pimcommonakonadi5abi1  4:18.08.3-2
ii  libkf5pimtextedit5abi2   18.08.3-1
ii  libkf5sendlater5 4:18.08.3-2
ii  libkf5service-bin5.54.0-1
ii  libkf5service5   5.54.0-1
ii  libkf5sonnetui5  5.54.0-1
ii  libkf5templateparser54:18.08.3-1
ii  libkf5textwidgets5   5.54.0-1
ii  libkf5tnef5  4:18.08.3-1
ii  libkf5wallet-bin 5.54.0-1
ii  libkf5wallet55.54.0-1
ii  libkf5webengineviewer5abi1   4:18.08.3-1
ii  libkf5widgetsaddons5 5.54.0-1
ii  libkf5windowsystem5  5.54.0-1
ii  libkf5xmlgui55.54.0-1
ii  libqgpgme7   1.12.0-6
ii  libqt5core5a 5.11.3+dfsg-5
ii  libqt5dbus5  5.11.3+dfsg-5
ii  libqt5gui5   5.11.3+dfsg-5
ii  libqt5network5   5.11.3+dfsg-5
ii  libqt5widgets5   5.11.3+dfsg-5
ii  libqt5xml5   5.11.3+dfsg-5
ii  libstdc++6   8.2.0-21

Versions of packages kmail recommends:
ii  accountwizard   4:18.08.3-1
ii  gnupg 

Bug#919813: recognising devuan

[Hendrik Boom]

So the remaining problem is that the Debian Buster os-prober did not 
recognise Devuan ascii.

-- hendrik

Bug#919813: comparison with earlier release

[Hendrik Boom]

Just for comparison, on Devuan ascii (stretch wirhout systend), I get:

root@midwinter:/home/hendrik# os-prober
File descriptor 8 (socket:[13898]) leaked on lvs invocation. Parent PID 2831: 
/bin/sh
File descriptor 9 (socket:[13899]) leaked on lvs invocation. Parent PID 2831: 
/bin/sh
File descriptor 10 (socket:[16454]) leaked on lvs invocation. Parent PID 2831: 
/bin/sh
File descriptor 11 (socket:[16455]) leaked on lvs invocation. Parent PID 2831: 
/bin/sh
File descriptor 18 (socket:[13991]) leaked on lvs invocation. Parent PID 2831: 
/bin/sh
/dev/sda6:Debian GNU/Linux buster/sid:Debian:linux
root@midwinter:/home/hendrik# 

Here it also does not recognise the OS it runs on, but it *does* recognise
Debian.

Could the problem be that it is does not recognise
  (a) its own OS, nor
  (b) any OS those root partition in on an LVM volume, even if its /boot
  is on a primary partition?

-- hendrik

Bug#919813: os-prober fails to find any os's at all.

[Hendrik Boom]

Package: os-prober
Version: 1.77

os-prober fails to find any os's at all after a new Debian buster install,
not even the installed and running DEbian buster.

The install was done using the net-install CD on a USB stick on 2019 01 18,
downloaded immediately before the installation.

root@buster:/home/guest# os-prober
root@buster:/home/guest# 

This was run the day after installation.

The machine actually has two Linux systems installed:

* the newly installed Debian buster.
  * /boot on /dev/sda2, and / on /dev/sda6.
  * Installed yesterday.
* An older Devuan ascii.
  * /boot on /dev/sda1, and other partitions in an LVM on /dev/sda3
  * Installed a few months ago.

Both are now bootable from the grub2 boot menu installed by using the 
debian installer to install buster yesterday.  Presumably the installer 
used os-prober succesfully, but the os-prober I installed 
today using aptitude does not work.

Could they be different versions?

I'm not aware of anything unusual about the enviromnent.  It'a a Purism 
laptop.

-- hendrik

Bug#762829: Now misclassified as Java

[Hendrik Boom]

The example Pascal program in the original bug report is now 
misclassified as Java source.  This is on a new buster install as of 
2019 01 19.

guest@buster:~$ file Downloads/emil23m.pas 
Downloads/emil23m.pas: Java source, ASCII text
guest@buster:~$ file --version
file-5.35
magic file from /etc/magic:/usr/share/misc/magic
guest@buster:~$ 

-- hendrik

Bug#857050: Regression for stable users

[Hendrik Naumann]

Dear Debian Firefox Maintainers

Since Firefox  60.2.0esr-1 is shipped to all users of stable now, this 
issue causes a serious regression to the usability of firefox in stable.


I would be very pleased if you could fix this issue.

Thanks

Hendrik Naumann

Bug#906853: ITP: tbsync -- [Thunderbird Add-On] Sync contacts, tasks and calendars to thunderbird. Currently supporting Exchange ActiveSync (EAS) and sabre/dav (CalDAV & CardDAV)

[Hendrik Sattler]

Am 1. September 2018 09:38:50 MESZ schrieb Carsten Schoenert 
:
>Hello Hednrik,
>
>On Tue, Aug 21, 2018 at 09:45:19PM +0200, Hendrik Sattler wrote:
>...
>> >Synchronize Exchange ActiveSync accounts (contacts, tasks and
>> >calendars) to Thunderbird, supports Office 365, Outlook.com,
>> >Freenet, Strato, Hotmail, Kopano and other EAS compatible servers.
>> 
>> While this is a long list, none of these are free software. Maybe you
>> can add compatible free software servers? (Horde?)
>
>if you know some FOSS based server TbSync that is also working with
>this
>AddOnn I'd say it's absolutely no problem to add them to the list too.

I rather meant in the context of Debian. What tbsync-compatible servers are 
packaged in Debian?

The only one I know of is Horde with the ActiveSync plugin and Sogo.

More can be found at least at 
https://github.com/jobisoft/TbSync/wiki/What-is-TbSync%3F

How does tbsync compare to xul-ext-sogo-connector?

>The list of possible use cases here is mostly longer than for the
>proprietary products. So far I know the main intention behind TbSync
>(and other connectors) was to add the possibility to let Thunderbird
>and
>the Lightning AddOn also use some proprietary backends that are
>unfortunately really common in bigger 'professional' environments.

So it is compatible with Microsoft Exchange Server. Always? Or only in some 
specific setup? If you know, why not mention it? Debian users in companies 
might appreciate that information. But you are right: a readme file or the wiki 
mentioned above might suffice :-)

And yes, I really appreciate that you package this!

HS

Bug#906853: ITP: tbsync -- [Thunderbird Add-On] Sync contacts, tasks and calendars to thunderbird. Currently supporting Exchange ActiveSync (EAS) and sabre/dav (CalDAV & CardDAV)

[Hendrik Sattler]

Am 21. August 2018 19:12:06 MESZ schrieb Mechtilde :
>Package: wnpp
>Severity: wishlist
>Owner: Mechtilde 
>
>* Package name: tbsync
>  Version : 0.7.12
>  Upstream Author : Name john.biel...@gmx.de
>* URL : https://github.com/jobisoft/TbSync
>* License : GPL v3
>  Programming Lang: Javascript
>Description : [Thunderbird Add-On] Sync contacts, tasks and
>calendars to
>thunderbird. Currently supporting Exchange ActiveSync (EAS) and
>sabre/dav
>(CalDAV & CardDAV)
>
>Synchronize Exchange ActiveSync accounts (contacts, tasks and
>calendars) to Thunderbird, supports Office 365, Outlook.com,
>Freenet, Strato, Hotmail, Kopano and other EAS compatible servers.

While this is a long list, none of these are free software. Maybe you can add 
compatible free software servers? (Horde?)
Also "EAS compatible" is very unspecific, it usually refers to a minimum and 
maximum supported version.

>This package helps to connect to calender and contacts which are
>provided by a
>server named above.
>
>It has a similar functionality to calendar-exchange-provider which
>doesn't work
>any more with thunderbird >=60
>
>I use it myself. I will do the package as I did it with
>calendar-exchange-
>provider.

Bug#904386: sshguard: Version 2.2.0 available

[Hendrik VIsage]

Package: sshguard
Version: 1.7.1-1
Severity: minor

Dear Maintainer,

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

The latest version released is 2.2.0, while Debian stretch only have 1.7.x, 
ditto for buster & sid.
Seems thhat the requests for the maintainer to relinquish control to another 
also have been falling on deaf ears

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


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

Kernel: Linux 4.15.17-3-pve (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL 
set to C), LANGUAGE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set 
to C)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages sshguard depends on:
ii  init-system-helpers  1.48
ii  iptables 1.6.0+snapshot20161117-6
ii  libc62.24-11+deb9u3
ii  lsb-base 9.20161125

sshguard recommends no packages.

sshguard suggests no packages.

-- Configuration Files:
/etc/sshguard/whitelist changed [not included]

-- no debconf information

Bug#869114: status of the topkg package

[Hendrik Tews]

Andy Li <a...@onthewings.net> writes:

> What is the status of the topkg package?

I worked on it last September, see
https://lists.debian.org/debian-ocaml-maint/2017/09/msg00015.html
and https://salsa.debian.org/ocaml-team/ocaml-topkg . I have not
looked into it since then.

Hendrik

Bug#884285: Backport fix from 4.14

[Hendrik SACHSE]

Please backport
https://github.com/torvalds/linux/commit/9d11b06638f6aa30d099090e6b8a540c558295ac#diff-d45f6c5dfa1088acc4fb00e7636dbba7
from 4.14 to 4.9, this bug makes my setup almost unusable with Debian Stretch

Regards
Hendrik Sachse


Der Inhalt dieser E-Mail ist für den Absender rechtlich nicht verbindlich.
Informieren Sie uns bitte, wenn Sie diese E-Mail fälschlicherweise erhalten 
haben (Fax: +49-7551-891-4001). Bitte löschen Sie in diesem Fall die Nachricht. 
Jede Form der weiteren Benutzung ist untersagt.


The content of this e-mail is not legally binding upon the sender.
If this e-mail was transmitted to you by error, then please inform us 
accordingly (Fax: +49-7551-891-4001). In such case you are requested to erase 
the message. Any use of such e-mail message is strictly prohibited.

Bug#893319: Crash when displaying Unicode 'ALARM CLOCK' (U+23F0) character

[Hendrik Tews]

Another observation: emacs24-x (24.5+1-11+deb9u1) inside Debian
testing does crash on the alarm clock, while the same binary
inside Debian stable (9 - stretch) has no problem with the alarm
clock.

Hendrik

Bug#893319: Crash when displaying Unicode 'ALARM CLOCK' (U+23F0) character

[Hendrik Tews]

The error message pasted by Gaudenz hints at gtk, but gtk can
show the alarm clock (I tried the hello world example from the
tutorial) and emacs25-lucid does also crash, albeit with a
shorter message:

X protocol error: BadLength (poly request too large or internal Xlib 
length error) on protocol request 139

Hendrik

Bug#893319: Crash when displaying Unicode 'ALARM CLOCK' (U+23F0) character

[Hendrik Tews]

I wrote:

 > Gnus is completely unusable for me - emacs dies when I open
 > the first message.

For me the culprit was a spam message containing the ALARM CLOCK
sign in the subject. Gnus therefore crashed emacs when it tried
to display the summary line for that message.

I got around the problem by temporarily deleting ``%s'' (that is,
the subject) from gnus-summary-line-format. Then, carefully
avoiding to show the message, I was able to delete that message
from within the summary buffer.

Hendrik

Bug#893319: Crash when displaying Unicode 'ALARM CLOCK' (U+23F0) character

[Hendrik Tews]

severity 893319 important
thanks

Hi,

I see the same behavior, both with emacs24 and emacs25. And emacs
dies with the same error message in many different circumstances.
Gnus is completely unusable for me - emacs dies when I open the
first message. Raising to important for this reason.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, arm64

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 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

Versions of packages emacs25 depends on:
ii  emacs25-bin-common 25.2+1-6+b1
ii  libacl12.2.52-3+b1
ii  libasound2 1.1.3-5
ii  libatk1.0-02.28.1-1
ii  libc6  2.27-2
ii  libcairo-gobject2  1.15.10-1
ii  libcairo2  1.15.10-1
ii  libdbus-1-31.12.6-2
ii  libfontconfig1 2.12.6-0.1
ii  libfreetype6   2.8.1-2
ii  libgdk-pixbuf2.0-0 2.36.11-1
ii  libgif75.1.4-2
ii  libglib2.0-0   2.54.3-2
ii  libgnutls303.5.18-1
ii  libgomp1   8-20180312-2
ii  libgpm21.20.7-5
ii  libgtk-3-0 3.22.28-1
ii  libice62:1.0.9-2
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libm17n-0  1.7.0-3+b2
ii  libmagickcore-6.q16-5  8:6.9.9.34+dfsg-3+b1
ii  libmagickwand-6.q16-5  8:6.9.9.34+dfsg-3+b1
ii  libotf00.9.13-3+b1
ii  libpango-1.0-0 1.40.14-1
ii  libpangocairo-1.0-01.40.14-1
ii  libpng16-161.6.34-1
ii  librsvg2-2 2.40.20-2
ii  libselinux12.7-2+b1
ii  libsm6 2:1.2.2-1+b3
ii  libtiff5   4.0.9-4
ii  libtinfo5  6.1-1
ii  libx11-6   2:1.6.4-3
ii  libx11-xcb12:1.6.4-3
ii  libxcb11.13-1
ii  libxfixes3 1:5.0.3-1
ii  libxft22.3.2-1+b2
ii  libxinerama1   2:1.1.3-1+b3
ii  libxml22.9.4+dfsg1-6.1
ii  libxpm41:3.5.12-1
ii  libxrandr2 2:1.5.1-1
ii  libxrender11:0.9.10-1
ii  zlib1g 1:1.2.8.dfsg-5

emacs25 recommends no packages.

Versions of packages emacs25 suggests:
ii  emacs25-common-non-dfsg  25.2+1-1

-- no debconf information

Hendrik

Bug#885525: (no subject)

[Jan-Hendrik Peters]

I had the same issue and 1.8.10-2 does the job for me too.

Thanks!

Bug#884454: systemd: systemd udev rule is not executed when removing - only when adding

[Hendrik Tews]

Package: systemd
Version: 235-3
Severity: important

Dear Maintainer,

on my system, systemd_wants udev rules get only executed when I
add devices, not when I remove them.

I have two udev rules

ENV{PRODUCT}=="3/46d/101a/111", TAG+="systemd", ENV{SYSTEMD_WANTS}="aaa"
ENV{PRODUCT}=="3/46d/101a/111", RUN+="/bin/bash -c '/bin/date 
+%%Y-%%m-%%d-%%H:%%M:%%S-RUN >> /tmp/log'"

The product ID belongs to my mouse. The aaa.service contains

[Unit]
Description=AAA

[Service]
Type=simple
ExecStart=/bin/bash -c "/bin/date '+%%Y-%%m-%%d %%H:%%M:%%S AAA' >> 
/tmp/log"

When I unplug the mouse, I only see

2017-12-15-11:40:54-RUN

in /tmp/log. When I plug the mouse, I see

2017-12-15-11:41:22-RUN
2017-12-15 11:41:22 AAA

as expected.

When removing the mouse, the only line in the syslog related to
aaa.service is

Dec 15 11:40:54 cert systemd[1]: aaa.service: Collecting.


I report the problem here for SYSTEMD_WANTS, the same happens for
SYSTEMD_USER_WANTS. I would like to use the latter to run some
command in my X session when the mouse is added and removed.

Thanks for your attention,

Hendrik


-- Package-specific info:

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 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)

Versions of packages systemd depends on:
ii  adduser 3.116
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.1-4
ii  libaudit1   1:2.8.1-2
ii  libblkid1   2.30.2-0.1
ii  libc6   2.25-3
ii  libcap2 1:2.25-1.2
ii  libcryptsetup4  2:1.7.5-1
ii  libgcrypt20 1.8.1-4
ii  libgpg-error0   1.27-5
ii  libidn111.33-2
ii  libip4tc0   1.6.1-2+b1
ii  libkmod224-1
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.3
ii  libmount1   2.30.2-0.1
ii  libpam0g1.1.8-3.6
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.7-2
ii  libsystemd0 235-3
ii  mount   2.30.2-0.1
ii  procps  2:3.3.12-3
ii  util-linux  2.30.2-0.1

Versions of packages systemd recommends:
ii  dbus1.12.2-1
ii  libpam-systemd  235-3

Versions of packages systemd suggests:
ii  policykit-10.105-18
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 235-3

-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandleLidSwitch=ignore

/etc/systemd/system.conf changed:
[Manager]
LogLevel=debug


-- no debconf information

Bug#884285: linux-image-4.9.0-4-rt-amd64: TP-link UE300 causes system hang

[hendrik . sachse]

Package: src:linux
Version: 4.9.65-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?
usage of TP-link UE300 USB to ethernet adapter
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
plug in UE300 into USB port
   * What was the outcome of this action?
kernel messages and eventual system freeze

Dec  8 18:49:43 LxTE04 kernel: [16790.642451] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 18:51:49 LxTE04 kernel: [16917.298453] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 18:53:55 LxTE04 kernel: [17043.314451] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 19:01:18 LxTE04 kernel: [17486.322451] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 19:03:24 LxTE04 kernel: [17612.274451] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 19:04:27 LxTE04 kernel: [17675.314452] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped

   * What outcome did you expect instead?
normal operation

refer to https://patchwork.kernel.org/patch/10022309/


-- Package-specific info:
** Version:
Linux version 4.9.0-4-rt-amd64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP PREEMPT RT Debian 
4.9.65-3 (2017-12-03)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-4-rt-amd64 root=/dev/mapper/LxTE04-root ro quiet

** Not tainted

** Kernel log:
[78559.428637] usb 1-1: new high-speed USB device number 5 using xhci_hcd
[78559.569963] usb 1-1: New USB device found, idVendor=2357, 
idProduct=0601
[78559.569970] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
[78559.569973] usb 1-1: Product: USB 10/100/1000 LAN
[78559.569976] usb 1-1: Manufacturer: TP-LINK
[78559.569979] usb 1-1: SerialNumber: 0100
[78559.582728] cdc_ether 1-1:2.0 eth0: register 'cdc_ether' at 
usb-:00:14.0-1, CDC Ethernet Device, 18:a6:f7:1d:4d:d3
[78559.582766] usbcore: registered new interface driver cdc_ether
[78559.596244] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[78559.596360] cdc_ether 1-1:2.0 eth0: kevent 12 may have been dropped
[78559.611081] cdc_ether 1-1:2.0 eth0: kevent 12 may have been dropped

** Model information
sys_vendor: Shuttle Inc.
product_name: DS67U
product_version: V1.0
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 1.01
board_vendor: Shuttle Inc.
board_name: FS67U
board_version: 1.0

** Loaded modules:
cdc_ether
usbnet
mii
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_codec_generic
intel_rapl
intel_powerclamp
coretemp
kvm_intel
kvm
irqbypass
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
arc4
intel_cstate
intel_uncore
intel_rapl_perf
rtsx_usb_ms
serio_raw
pcspkr
evdev
memstick
snd_soc_skl
snd_soc_skl_ipc
snd_soc_sst_ipc
snd_soc_sst_dsp
snd_hda_ext_core
snd_soc_sst_match
snd_soc_core
snd_compress
iTCO_wdt
iTCO_vendor_support
rtl8821ae
btcoexist
rtl_pci
btusb
btrtl
rtlwifi
snd_hda_intel
sg
snd_hda_codec
mac80211
snd_hda_core
snd_hwdep
cfg80211
snd_pcm
i915
snd_timer
snd
mei_me
soundcore
drm_kms_helper
shpchp
mei
drm
hci_uart
btbcm
btqca
btintel
bluetooth
battery
rfkill
video
intel_lpss_acpi
intel_lpss
acpi_pad
acpi_als
kfifo_buf
button
industrialio
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
crc32c_generic
fscrypto
ecb
mbcache
dm_mod
rtsx_usb_sdmmc
mmc_core
rtsx_usb
mfd_core
sd_mod
hid_generic
usbhid
crc32c_intel
aesni_intel
aes_x86_64
glue_helper
lrw
gf128mul
ablk_helper
cryptd
psmouse
ahci
libahci
igb
i2c_algo_bit
i2c_i801
e1000e
dca
i2c_smbus
ptp
libata
pps_core
scsi_mod
xhci_pci
xhci_hcd
usbcore
usb_common
fan
thermal
i2c_hid
hid

** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: AFDX1A:  mtu 1500 qdisc mq 
state DOWN group default qlen 1000
link/ether 80:ee:73:bd:b3:a2 brd ff:ff:ff:ff:ff:ff
inet 10.10.1.1/16 brd 10.10.255.255 scope global AFDX1A
   valid_lft forever preferred_lft forever
3: AFDX1B:  mtu 1500 qdisc 
pfifo_fast state UP group default qlen 1000
link/ether 80:ee:73:bd:b3:a3 brd ff:ff:ff:ff:ff:ff
inet 10.10.1.2/16 brd 10.10.255.255 scope global AFDX1B
   valid_lft forever preferred_lft forever
inet6 fe80::82ee:73ff:febd:b3a3/64 scope link 
   valid_lft forever preferred_lft forever
4: wlp1s0:  mtu 1500 qdisc mq state DOWN group 
default 

Bug#681661: rfkill doesn't switch off Intel 2100

[Hendrik Buchner]

Hi Ben,

now (5 years later :) ) I'm using Debian stretch with kernel 4.9.51-1. 
Everything is working fine with this kernel.


Hendrik

Am 17.11.2017 um 19:15 schrieb Ben Hutchings:

Control: reassign -1 src:linux 3.2.21-3
Control: tag -1 - unreproducible
Control: tag -1 moreinfo

On Tue, 20 Nov 2012 19:55:53 + Darren Salt <devs...@moreofthesa.me.uk> 
wrote:

tag 681661 unreproducible
thanks

rfkill uses a kernel interface; the kernel rfkill core hands this off to
whichever driver registered that particular kill switch. So this is likely to
be a driver issue or, possibly, a BIOS or hardware issue.

Beyond that, I couldn't say...

Indeed, this sounds like a kernel bug.  Which kernel version are you
running now (use "uname -v" to find this) and is the bug still present?

Ben.

Bug#880449: unison: Uncaught exception Failure("input_value: bad bigarray kind")

[Hendrik Tews]

Vincent Lefevre <vinc...@vinc17.net> writes:

> Alternatively, wouldn't it be possible to rename the current unison
> package and make it co-installable with the one from stretch?

Possible maybe, but it wouldn't help. Both packages would be
compiled with the only OCaml compiler available in the current
Debian version, hence both unison's would be incompatible with
the one in stretch.

One side condition that you have to keep in mind is that there
are a lot of architectures and the OCaml team does source
uploads, which get compiled using the current Debian version.

As Stéphane pointed out already: Please discuss with the upstream
authors or submit patches there. Alternatively you could set up
inofficial repository version, where you provide unision packages
compiled with different OCaml versions.

Hendrik

Bug#876533: hol-light FTBFS with OCaml 4.05.0

[Hendrik Tews]

> Hi Hendrik, any progress on this? I notice in the ocaml transition tracker:

I really spend more than 4 weeks in discussions with upstream
about license and copyright clarifications. Now it is finished. I
uploaded a new hol-light version to DOM git yesterday. Please
review and upload.

If you think I fulfill the conditions for directly uploading
hol-light, I would appreciate, if somebody could execute

dcut dm --uid "Hendrik Tews" --allow hol-light

Bye,

Hendrik

Bug#878968: libglvnd0-nvidia: undefined symbol: _glapi_tls_Current makes system unusable

[Hendrik Tews]

> Please attach the full report by running
>
> reportbug --template nvidia-driver

I am not sure this helps, but here you go. This is the result
that ``reportbug --template nvidia-driver'' saved in /tmp:

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Hendrik Tews <hend...@askra.de>
To: Debian Bug Tracking System <sub...@bugs.debian.org>
Subject: nvidia-driver: none

Package: nvidia-driver
Severity: wishlist

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Bug#878968: libglvnd0-nvidia: undefined symbol: _glapi_tls_Current makes system unusable

[Hendrik Tews]

Package: libglvnd0-nvidia
Version: 375.82-5
Severity: critical

Dear Maintainer,

after updating some packages this morning, X11 did not come up
any more and the system was completely unusable. Apparently gdm
was restarting continuously, making it impossible to enter
anything in a terminal window. I needed to boot in recovery mode
to get access again.

The syslog contains

/usr/lib/gdm3/gdm-x-session[2703]: (EE) Failed to load 
/usr/lib/xorg/modules/extensions/libglx.so: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current

and I get the same undefined symbol error when I try startx.

After installing libglvnd0 (and purging libglvnd0-nvidia)
everything is fine again. In contrast to what is reported in
https://lists.debian.org/debian-kde/2017/10/msg00028.html, the
problem appears again, when I reinstall libglvnd0-nvidia.

Bye,

Hendrik


-- Package-specific info:
uname -a:
Linux cert 4.13.0-1-amd64 #1 SMP Debian 4.13.4-1 (2017-10-01) x86_64 GNU/Linux

/proc/version:
Linux version 4.13.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
6.4.0 20170920 (Debian 6.4.0-7)) #1 SMP Debian 4.13.4-1 (2017-10-01)

lspci 'VGA compatible controller [0300]':
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:191b] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Lenovo HD Graphics 530 [17aa:5056]
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

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Oct 17 21:58 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Oct 17 21:58 /dev/dri/renderD128

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Oct 17 21:58 pci-:00:02.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Oct 17 21:58 pci-:00:02.0-render -> ../renderD128
video:x:44:tews

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root 15 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libEGL.so.1 -> libEGL.so.1.0.0
-rw-r--r-- 1 root root  76344 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libEGL.so.1.0.0
lrwxrwxrwx 1 root root 14 Sep 28 22:04 /usr/lib/x86_64-linux-gnu/libGL.so.1 
-> libGL.so.1.0.0
-rw-r--r-- 1 root root 567624 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libGL.so.1.0.0
lrwxrwxrwx 1 root root 18 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2 -> libGLESv2.so.2.0.0
-rw-r--r-- 1 root root  55616 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2.0.0
-rw-r--r-- 1 root root 29 Jul  7 07:31 
/usr/lib/xorg/modules/extensions/libglx.so
-rw-r--r-- 1 root root   5883 Oct 17 09:07 /var/log/Xorg.0.log

/etc/modprobe.d:
total 24
drwxr-xr-x   2 root root  4096 Sep 18 13:14 .
drwxr-xr-x 162 root root 12288 Oct 17 21:55 ..
-rw-r--r--   1 root root   154 Nov 30  2016 amd64-microcode-blacklist.conf
-rw-r--r--   1 root root   154 Nov  9  2016 intel-microcode-blacklist.conf


/etc/modules-load.d:
-rw-r--r-- 1 root root  195 Mar  1  2017 /etc/modules

/etc/modules-load.d/:
total 20
drwxr-xr-x   2 root root  4096 Oct 17 08:42 .
drwxr-xr-x 162 root root 12288 Oct 17 21:55 ..
-rw-r--r--   1 root root   119 Jan 19  2017 cups-filters.conf
lrwxrwxrwx   1 root root10 Oct 11 00:46 modules.conf -> ../modules


Files from nvidia-installer:

Config and logfiles:

<<<<<<<<<< /home/tews/.local/share/xorg/Xorg.0.log >>>>>>>>>>
[32.985] 
X.Org X Server 1.19.3
Release Date: 2017-03-15
[32.991] X Protocol Version 11, Revision 0
[32.992] Build Operating System: Linux 4.9.0-3-amd64 x86_64 Debian
[32.994] Current Operating System: Linux cert 4.13.0-1-amd64 #1 SMP Debian 
4.13.4-1 (2017-10-01) x86_64
[32.994] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-1-amd64 
root=/dev/mapper/cert--vg-root1 ro single
[32.998] Build Date: 07 July 2017  06:22:09AM
[33.000] xorg-server 2:1.19.3-2 (https://www.debian.org/support) 
[33.001] Current version of pixman: 0.34.0
[33.005]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[33.005] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[33.012] (==) Log file: "/home/tews/.local/share/xorg/Xorg.0.log", Time: 
Tue Oct 17 21:58:39 2017
[33.019] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[33.024] (==) No Layout section.  Using the first Screen section.
[33.024] (==) No screen section available. Using defaults.
[33.024] (**) |-->Screen "Default Screen Section" (0)
[33.024] (**) |   |-->Monitor ""
[33.024] (==) No monitor specified for screen "Default Screen Section"

Bug#878615: hol-light: installs .pc/ files into a binary package

[Hendrik Tews]

Thanks for the note! I'll take care of it in the next version.

Hendrik

Bug#876533: hol-light FTBFS with OCaml 4.05.0

[Hendrik Tews]

Upstream does indeed fix this problem. However, it also contains
a few files with unclear license and copyright, currently
preventing to package it. I am trying to solve these license and
copyright issues with upstream.

Hendrik

Bug#876537: otags FTBFS with OCaml 4.05.0

[Hendrik Tews]

Yesterday, I prepared a new otags package that builds fine with
4.05, see
https://lists.debian.org/debian-ocaml-maint/2017/09/msg00079.html
and
https://anonscm.debian.org/gitweb/?p=pkg-ocaml-maint/packages/otags.git .
The only thing that is missing now is somebody who sponsors an
upload.

Hendrik

Bug#876533: hol-light FTBFS with OCaml 4.05.0

[Hendrik Tews]

I have a look at it, hopefully a new upstream version will fix
the problem.

Hendrik

Bug#686754: why 686754 is not a bug

[Hendrik Boom]

I hit this bug, read the previous messages, and wondered why it had 
not been fixed in so long.  I resolved to fix it myself, and spent 
some time reading the code.

But then I was diverted to other tasks, and when I returned to the bug 
a week later, it suddenly dawned on me why it was not a bug.

When grub-install uses its varous tools to survey the disk and make 
proper boot stanzas, it tries as much as possible to figure out how 
the other OS's want to be booted and place that information in its 
boot stanzas.

And the copied OS plainly states how it wants to be booted in its  
copied boot stanzas -- namely, exactly like the originally uncopied 
OS, so in the newly created boot stanza, that's exactly what it gets 
-- a copy of the copy of the original stanza.

So that's what we get.  And to fix it we have to make sure that the 
copied system is altered to refer to itself, just as its /etc/fstab is 
altered to refer to itself.

-- hendrik

Bug#869114: ITP: ocaml-libtopkg -- packager for distributing OCaml software

[Hendrik Tews]

Hi,

with great help from the upstream author, the cyclic build
dependency has been solved now. However, I still only intend to
package the topkg packaging library and not the topkg-care tool,
because the latter has a number of build dependencies that are
not (yet) available in Debian.

I intend to name the source package ocaml-topkg with binary
packages libtopkg-ocaml and libtopkg-ocaml-dev, if needed.

Regards,

Hendrik

Bug#873375: linux-image-4.9.0-3-amd64: snd_hda_intel sometimes crashes

[Hendrik Buchner]

Package: src:linux
Version: 4.9.30-2+deb9u3
Severity: normal

Dear Maintainer,

sometimes on my system the "snd_hda_intel" kernelmodule crashes. The result is
that the module is still present but there's no sound. After removing the
module with "rmmod -f snd_hda_intel" and loading it again with "modprobe
snd_hda_intel" everything works fine again. Sometimes this happens after a new
boot, but mostly it happens after suspend (s2r). My system is a Lenovo
ThinkCentre M58P SFF with Intel Q45 Chipset. Before on Debian 8.0 Jessie
everything worked fine.



-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 
root=UUID=bc77dc37-6d9f-48eb-a6b0-a24245589caf ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

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

** Model information
sys_vendor: LENOVO
product_name: 6234BB6
product_version: ThinkCentre M58p
chassis_vendor: LENOVO
chassis_version: NONE
bios_vendor: LENOVO
bios_version: 5CKT76AUS
board_vendor: LENOVO
board_name: LENOVO
board_version: NONE

** Loaded modules:
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
snd_hda_codec_analog
snd_hda_codec_generic
hid_generic
joydev
iTCO_wdt
iTCO_vendor_support
evdev
kvm_intel
kvm
irqbypass
serio_raw
sg
snd_hda_intel
lpc_ich
mfd_core
i915
snd_hda_codec
snd_hda_core
snd_hwdep
snd_pcm
snd_timer
snd
mei_me
soundcore
mei
drm_kms_helper
drm
i2c_algo_bit
video
wmi
button
acpi_cpufreq
coretemp
sunrpc
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
crc32c_generic
fscrypto
ecb
glue_helper
lrw
gf128mul
ablk_helper
cryptd
aes_x86_64
mbcache
hid_lenovo
usbhid
hid
sr_mod
cdrom
sd_mod
psmouse
ahci
i2c_i801
libahci
i2c_smbus
floppy
uhci_hcd
ehci_pci
ehci_hcd
e1000e
ptp
pps_core
usbcore
usb_common
ata_generic
libata
scsi_mod

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller 
[8086:2e10] (rev 03)
Subsystem: Lenovo 4 Series Chipset DRAM Controller [17aa:3048]
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 4 Series Chipset 
Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA 
controller])
Subsystem: Lenovo ThinkCentre M6258 [17aa:3048]
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 4 Series Chipset 
Integrated Graphics Controller [8086:2e13] (rev 03)
Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller 
[17aa:3048]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:03.0 Communication controller [0780]: Intel Corporation 4 Series Chipset 
HECI Controller [8086:2e14] (rev 03)
Subsystem: Lenovo 4 Series Chipset HECI Controller [17aa:3048]
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: mei_me
Kernel modules: mei_me

00:03.2 IDE interface [0101]: Intel Corporation 4 Series Chipset PT IDER 
Controller [8086:2e16] (rev 03) (prog-if 85 [Master SecO PriO])
Subsystem: Lenovo 4 Series Chipset PT IDER Controller [17aa:3048]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: ata_generic

00:03.3 Serial controller [0700]: Intel Corporation 4 Series Chipset Serial KT 
Controller [8086:2e17] (rev 03) (prog-if 02 [16550])
Subsystem: Lenovo 4 Series Chipset Serial KT Controller [17aa:3048]
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: serial

00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM-3 Gigabit Network 
Connection [8086:10de] (rev 02)
Subsystem: Lenovo 82567LM-3 Gigabit Network Connection [17aa:3048]
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: e1000e

Bug#869821: xournal: Please package newest version 0.4.8.2016 which fixes several bugs

[Hendrik Langer]

Package: xournal
Version: 1:0.4.8-1+b1
Severity: normal

Dear Maintainer,

recently upstream released a bugfix-release: 0.4.8.2016
the current packaged version is now 3 years old and contains several annoying
minor bugs which were fixed in 2016.

Upstream bugreport:https://sourceforge.net/p/xournal/bugs/182/
Commit(Changes):
https://sourceforge.net/p/xournal/code/ci/25b6ffc05f1a68728b69b5c122abc68d660df940/

Please package the new version. Thanks!



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

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

Versions of packages xournal depends on:
ii  ghostscript-x9.21~dfsg-1
ii  libart-2.0-2 2.3.21-2
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-12
ii  libcairo21.14.10-1
ii  libfontconfig1   2.12.3-0.2
ii  libfreetype6 2.8-0.2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.52.3-1
ii  libgnomecanvas2-02.30.3-3
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.6-1
ii  libpangocairo-1.0-0  1.40.6-1
ii  libpangoft2-1.0-01.40.6-1
ii  libpoppler-glib8 0.48.0-2
ii  libx11-6 2:1.6.4-3
ii  zlib1g   1:1.2.8.dfsg-5

xournal recommends no packages.

xournal suggests no packages.

-- no debconf information

Bug#869114: ITP: ocaml-libtopkg -- packager for distributing OCaml software

[Hendrik Tews]

Package: wnpp
Owner: Hendrik Tews <hend...@askra.de>
Severity: wishlist

* Package name: ocaml-libtopkg
  Version : 0.9.0
  Upstream Author : Daniel Bünzli
* URL or Web page : http://erratique.ch/software/topkg
* License : ISC
  Programming Lang: OCaml
  Description : packager for distributing OCaml software

Topkg is a packager for distributing OCaml software. It provides
an API to describe the files a package installs in a given build
configuration and to specify information about the package's
distribution creation and publication procedures.

Topkg is needed as build dependency for new upstream versions of
existing OCaml packages, for instance cmdliner. The topkg
upstream sources do also contain topkg-care, a command line tool
that helps with various aspects of a package's life cycle.
However, topkg-care has various build dependencies, among them
cmdliner. Therefore, the ocaml-libtopkg source package won't
build topkg-care. If we need topkg-care in Debian, it should go
into a separate source package with identical upstream tar ball.

Regards,

Hendrik

Bug#868606: hol-light FTBFS: Error: This expression has type (MLast.loc * string Ploc.vala) Ploc.vala but an expression was expected of type MLast.loc * 'a

[Hendrik Tews]

> Some recent change in unstable make hol-light FTBFS:

I blame the new camlp5 version for this. I have to see if
upstream supports camlp5 version 7 already.

Hendrik

Bug#774553: exim4: Do not scan outgoing mail for spam

[Hendrik Tews]

Hi,

could you please include this patch or something similar? I also
followed the suggestion in the Debian exim config files and, as a
result, produced non-conform messages that were discarded by some
other servers.

Note that the Debian exim wiki contains the same wrong advice.

Thanks,

Hendrik

Bug#543548: coq-doc-pdf: bookmarks and links for table of contents

[Hendrik Tews]

found 543548 coq-doc/8.4pl4-2
forwarded 543548 https://coq.inria.fr/bugs/show_bug.cgi?id=5636
thanks

Hi,

as others have noticed, the reference manual contains the
bookmarks and the links for some while already. However, the FAQ,
the Tutorial and the RecTutorial do not.

Hendrik

Bug#821812: icedove: High CPU usage with IMAP+SSL and iceowl+SSL-Caldav

[Hendrik Buchner]

Hi Carsten,

meanwhile I'm using a newer version of Thunderbird, I've updated Debian 
from Jessie to Stretch and I'm using newer, more powerful hardware. So 
there is still a high CPU-usage while starting up Thunderbird, but it's 
about 10-15 seconds and not for a minute.
I can test starting Thunderbird from a command line when I'm back at my 
Office-PC.


Hendrik

Am 20.05.2017 um 10:00 schrieb Carsten Schoenert:

Hello Hendrik,

On Tue, Apr 19, 2016 at 03:59:56PM +0200, Hendrik Buchner wrote:

Package: icedove
Version: 38.7.0-1~deb8u1
Severity: important

Dear Maintainer,

I've connected an IMAP-account with SSL (Port 993) and the calendar (iceowl)
with a SSL-caldav-calendar from the company. When I start icedove one core of
my CPU (i7-620m) is at 100% for about one minute. In this time icedove is
almost unusable. When I disable iceowl everything runs fine, on the other hand,
when only iceowl is using the calendar and no email-account is configured
everything is fine too. I only found an older bugreport for the same problem
but it seems to be fixed, maybe it's a similiar issue.

https://bugzilla.redhat.com/show_bug.cgi?id=488066

Unfortunaly I'm only allowed to use connections with SSL so I can't test if
this is also happening without any encryption.

we usaly don't prefer not encrypted transport security so with enabled
TLS traffic all needs to work the same as without.

I can't reproduce such a behavior here, ist this issue still alive on
your side?
If so maybe you want to start thunderbird from the comman line to see
some moer output.

Regards
Carsten

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Hendrik Tews]

> Note that this only applies on boot. Resume does not work.

What do you mean with "Resume does not work"? I usually wake up
my laptop from suspend or hibernate in the morning, then
apt.systemd.daily runs before the network comes up. Now and then
I reboot the system later, but then the time stamps prevent
apt.system.daily from doing anything.

> You could look at 
>
>  /var/lib/systemd/deb-systemd-helper-enabled/network-online.target.wants/
>  /{usr/,}lib/systemd/system/network-online.target.wants/ 
>  /etc/systemd/system/network-online.target.wants

I have the first and the last and they both contain files
networking.service and NetworkManager-wait-online.service and I
use NetworkManager.

Thanks,

Hendrik

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Hendrik Tews]

Julian,

thanks a lot for you quick answer.

> Check that your network-online target actually ensures that the
> network is up. (the service might want to depend on that as

I have no idea how to check this. Could you point me to a
relevant HowTo?

Thanks,

Hendrik

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Hendrik Tews]

Package: apt
Version: 1.4.1
Severity: normal

Dear Maintainer,

I configured

APT::Periodic::Enable "1";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";

but apt almost never downloads anything automatically. The reason
is that systemd runs apt.systemd.daily before the network comes
up.

Bye,

Hendrik

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.9\.0-2-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Periodic "";
APT::Periodic::Enable "1";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::Verbose "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/app-info -a 
-e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi";
APT::Architectures "";
APT::Architectures:: &qu

Bug#860375: wmaker: Cannot start multiple terminal instances

[Hendrik Weimer]

Package: wmaker
Version: 0.95.7-8

After updating the wmaker package from 0.95.2-1, I can no longer start
multiple xterms from the same appicon on the dock. I'm using the
configuration described in the Window Maker FAQ at
<https://windowmaker.org/FAQ.php#104>. Other terminal emulators have the
same issue. As a workaround, I can select "Launch" from the title bar of
the xterm window to start another terminal instance.

Hendrik