Bug#996871: wmnet: crashes on launch

2021-10-20 Thread Thomas Groman
Package: wmnet
Version: 1.06-1+b2
Severity: grave
Justification: renders package unusable

Launching wmnet causes it to crash on launch with the following output:
$ wmnet
wmnet: using devstats driver to monitor eth0
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  45 (X_OpenFont)
  Serial number of failed request:  36
  Current serial number in output stream:  39

I expect it to launch an Xwindow and display things. If it requires a specific 
font I expect that to be part of the package's dependencies.


-- System Information:
Debian Release: 11.1
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages wmnet depends on:
ii  libc6 2.31-13+deb11u2
ii  libx11-6  2:1.7.2-1
ii  libxext6  2:1.3.3-1.1
ii  netbase   6.3

wmnet recommends no packages.

Versions of packages wmnet suggests:
pn  wmaker  

-- no debconf information



Bug#996869: mail.debian.org: https://postgrey.schweikert.ch/help/bugs.debian.org.html contact email broken

2021-10-19 Thread Thomas Groman
Package: buxtehude.debian.org
Severity: normal
Tags: a11y

Dear Maintainer,

Upon sending to b...@debian.org I encountered the following message in my log 
files:
"relay="[2607:f8f0:614:1::1274:39] (buxtehude.debian.org)" delay=5s 
result="TempFail" stat="451 Greylisted, see 
http://postgrey.schweikert.ch/help/bugs.debian.org.html;

Upon going to the URL listed it has a friendly webpage Postgrey help with 
information on who to contact for help. The email listed for contact is "[email 
protected]". 
[email protected] is not a valid email address and should anyone attempt to 
email [email protected] mail would not go through and help would not be 
recieved.

I expect the postgrey help contact to be a valid email address that goes to the 
maintainer of the system where the error occured, in this case 
buxtehude.debian.org. Preferably using the mailto: URL schema inside of an 
XHTML anchored hyperlink.


-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 4 (chimaera)
Release:4
Codename:   chimaera
Architecture: x86_64

Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled



Bug#983505: doas: persist option still does not work

2021-10-19 Thread Thomas Groman
I am writing to inform that this bug still persists

Distributor ID: Devuan
Description:Devuan GNU/Linux 4 (chimaera)
Release:4
Codename:   chimaera
Kernel: Linux 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64
GNU/Linux
Package: doas
Version: 6.8.1-2
Priority: optional
Section: admin
Maintainer: Scupake 
Installed-Size: 69.6 kB
Depends: libc6 (>= 2.26), libpam0g (>= 0.99.7.1)
Homepage: https://github.com/Duncaen/OpenDoas
Download-Size: 21.1 kB
APT-Manual-Installed: yes
APT-Sources: http://pkgmaster.devuan.org/merged chimaera/main amd64
Packages


pgplyikUbPRNx.pgp
Description: OpenPGP digital signature


Bug#912860: Don't ship libgtk2-perl in Bullseye

2021-02-13 Thread Thomas Groman
Gtk2 support and gtk2 for Perl shouldn't be removed. Lots of users
depend on it and GTK3 is not a replacement or viable upgrade path from
gtk2. It doesn't do the same things, it uses significantly more
resources, it's incredibly more buggy, and it puts a dependence on
redhatisms. It is also very poorly designed software.


pgp7MgwedDm8v.pgp
Description: OpenPGP digital signature


Bug#969433: linux-image-4.19.0-10-amd64: sluggish and jittery, [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.

2020-09-02 Thread Thomas Groman
Package: src:linux
Version: 4.19.132-1
Severity: normal



-- Package-specific info:
** Version:
Linux version 4.19.0-10-amd64 (debian-ker...@lists.debian.org) (gcc
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-10-amd64 root=/dev/mapper/lappy--vg-root ro
quiet module_blacklist=mei_me

** Not tainted

** Kernel log:
[10932.246340] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10933.861829] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10933.911908] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10933.961969] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10934.012027] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10934.062089] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10934.112167] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10934.162228] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10934.212294] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10934.262352] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10935.845841] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10935.895918] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10935.945979] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10935.996040] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10936.046101] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10936.096164] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10936.146225] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10936.196285] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10936.246343] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10937.861750] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10937.911823] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10937.961876] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10938.011933] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10938.061992] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10938.112065] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10938.162125] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10938.212186] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10938.262244] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10939.845677] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10939.895742] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10939.945794] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10939.995851] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10940.045906] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10940.095972] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10940.146034] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10940.196095] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10940.246152] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10941.861647] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10941.911724] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10941.961784] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10942.011848] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10942.061908] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10942.111982] [drm:fw_domains_get [i915]] *ERROR* render: timed out
waiting for forcewake ack request. [10942.162040] [drm:fw_domains_get
[i915]] *ERROR* render: timed out waiting for forcewake ack request.
[10942.212106] [drm:fw_domains_get 

Bug#921151: unable to connect using TLSv1.2.

2019-02-02 Thread Thomas Groman
Package: mariadb-client
Version: 10.1.37-0+deb9u1
Severity: important



-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 2.0 (ascii)
Release:2.0
Codename:   ascii

Architecture: x86_64

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mariadb-client depends on:
ii  mariadb-client-10.1  10.1.37-0+deb9u1

mariadb-client recommends no packages.

mariadb-client suggests no packages.

-- no debconf information

Mariadb-client is unable to negotiate to TLSv1.2. I have tested this
with server versions: 10.1.37-MariaDB Gentoo Linux mariadb-10.1.37
10.1.34-MariaDB Gentoo Linux mariadb-10.1.34
. It should be noted that only the client version:
Ver 15.1 Distrib 10.1.37-MariaDB, for debian-linux-gnu (x86_64) using
readline 5.2 is unable to connect to the servers listed previously when
TLSv1.2 is enforced. However clients on other operating systems tested:
Ver 15.1 Distrib 10.1.34-MariaDB, for Linux (x86_64) using readline 7.0
Ver 15.1 Distrib 10.1.37-MariaDB, for Linux (x86_64) using readline 7.0
are able to connect just fine. Upon further inspection, looking at
packet traces with WireShark it appears that the Debian client is only
attempting to negotiate a connection with TLSv1.1, which is blacklisted
while the Gentoo clients are able to negotiate at TLSv1.2. The Debian
client fails and prints "ERROR 2026 (HY000): SSL connection error:
unknown error number" to stdout.