Bug#963176: Additional information.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

>Based on the trace, one of the places wine finds kernelbase.dll on your system 
>is Z:\\usr\\home\\root\\kernelbase.dll. Could this be an out of date version 
>of the dll?

There is no ".wine" directory, so there is no outdated version (or any version) 
of the DLL.
I set the base home directory to "/usr/home" so root's $HOME is 
"/usr/home/root".

>It's not a great idea to run wine as root.

I thought it was a permission problem so I used the root account. It turns out 
that it does not matter.
I used a new account and the problem is the same.
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJe9WDgAAoJEIJMNe5OCOiSTP4H/iwYmkrMgICx+TB/vRrm
XeeOBKb9Lf0RC4CPY7821BKf8AaLlrqXa6qx+XbfAtWExJgK0FPV9wB/w/DN
nrckNy5/s+Ij8CPQ/em3F/3VvfjIAgdTwJ3lNONZRmzNIgepkROwYkXOtm5Q
nvWNP88V5cgZN4XKhtckDlFCH+nXOifTFy65kQ81tSKxYrcNKEr+cqtiS7KS
r0bpGRWGCyENtib2n4IPNSJtZabwKwFKJIUiLiBNx8VZGXvC5C4Z20vmxV/x
YPgVB97AzFDveEa00/amKhTotgQSH66HlSRh2/8aldA/fIoofmG/kwLRzgdR
SzMr2Gp2U+0onbq14My8uwc=
=JIgT
-END PGP SIGNATURE-


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc.sig
Description: PGP signature

Bug#963176: Unable to run any programs due to kernelbase.dll failed to initialize.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: wine-development
Version: 5.5-5
Severity: grave

The current version of wine-development cannot launch any Windows programs, 
including built-in ones like "winecfg" and "wineconsole".

pthfdr:/u/h/pthfdr>wine-development --version
wine-5.5 (Debian 5.5-5)
pthfdr:/u/h/pthfdr>winecfg-development
000b:err:module:LdrInitializeThunk "kernelbase.dll" failed to initialize, 
aborting
000b:err:module:LdrInitializeThunk Initializing dlls for 
L"C:\\windows\\system32\\wineboot.exe" failed, status c005
0009:err:module:LdrInitializeThunk "kernelbase.dll" failed to initialize, 
aborting
0009:err:module:LdrInitializeThunk Initializing dlls for 
L"C:\\windows\\system32\\winecfg.exe" failed, status c005

This issue is similar to #953137, but it seems that someone introduces a 
regression again between 5.2 and 5.5.
(I set LANG to C.UTF8 so there are no NLS problems. If I use EN-US.UTF8 the 
problem is the same as #953137.)
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJe7XrrAAoJEIJMNe5OCOiStKEH/1tjA5An5tHywfWCtB1i
F0nOWBwxD11o5LkL3iuecd1oURLOEhI+VwfqwRtxSbg5HEePoyHrsXB6f0bP
z2UwobXkAW5sgS7WJILYzz3bD1BjzZEhbrLTZ6xh7mK0tazUDhMXRfAlzfQb
ClrKkKs5CWVGBV4VZfIRWoET82e30qOSDmp5IH2UI6+jJzMiAjBvWx0UNLyK
gqFXUYFyXmAeEZt0I+sIWAgDJMPcNp841wdt2mEKifx2SB5TrtvSHiWthVL/
5Pb0LgAoizLny9aWjjwyimW16zx6tY8ilaFtDJwAhkK0puxMacnFxgtSmubM
KhEIp5jNmUEIYCpWfe7aUN4=
=BIgZ
-END PGP SIGNATURE-


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc.sig
Description: PGP signature

Bug#939748: Regarding Antonio Ospite's suggestion.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I do not think that it can be fixed in a per-font basis.
The problem with fonts is that most people download them from the internet or 
(in case of bitmap fonts) make them manually.
I personally use a modified version of the default Fixed font using "gbdfed".
Also, once you convert the font to OTB format, it is impossible to manually 
edit (with simple tools like "gbdfed"; tools like FontForge seems to always 
mess things up).
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJewfwZAAoJEIJMNe5OCOiSunYH/jXEKmQdaDewNH+BZtVk
8kfbZgaDaR/F32QkwCgP/7BdBKLu4G0UmUvsyEgp4x0FEkUzRCAkaX+kyke1
IZ6T29SoXq35YTUiQYSNMIputEFamsqVZnFHUQdUTP/Ae8/AP+nSte83fgIb
EoXbcCbjsRHmWJZzzL3JyRJ2QGjYYQ6iStYbRzFPPQ/ZRYbVNAHi1QatQqip
SeNtWU7MF+koXxPoSgokUzdCVq6vgbL0JsgFdX3srxSzrgzEaG8+KwLgN5AH
3hR0x5R4e46duxiLSRA/Bqavj6xGlglgd1ghHCdyXaIak6uTeCWSeQV/65X/
5oVTSHJzlTmuBLquDO7ZI/Y=
=C1tZ
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xD213AC78.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc.sig
Description: PGP signature

Bug#939748: Additional information.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Here is the report regarding the spacing problem:
https://gitlab.gnome.org/GNOME/pango/-/issues/471

The original issue in "libpango" on the GNOME GitLab is locked so they refuse 
to listen to anything regarding that deprecation.
Seriously, can you just keep that package at 1.42 (or add a "legacy" package)? 
It breaks too many use cases.
I can hold that package from upgrading, but eventually, some packages may 
require the new version (just like "chromium" and GTK2).
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJewfkAAAoJEIJMNe5OCOiSKRQIALUGX1+XJdLPCrISqW9W
j+VeHvIH895Xn5idg1kh90xFgbHtXYoUxsDnCHoQFu8iHfu1g/nUyFoNzrpr
VB1r5y+hyIiD/vec/jg1IojLDJVLqALnAwNQVyrCgK28qFy7Okm1hAZP8Xmr
XVXJuA/+sVdUv76REFZYh0H8zA/IMj9/A0RVl6DYmnPzg458KnIz/Iei2uUB
wafp2YTWEgtZUd3KZZ/NphApzCN/aZT2RiJxWougaOpQ61oxEg7cVMSu7qLl
PyvApXViIU0Txx4WQaRmc6GhSDiKf+YfMaAJv5bvGcSZUDn9XxR5lL21sw24
YRzxN8HumssHsItD7Frddhg=
=5ZWi
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xD213AC78.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc.sig
Description: PGP signature

Bug#960473: Add an deb-alternative entry for hicolor-icon-theme.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: hicolor-icon-theme
Version: 0.17-2
Severity: wishlist

Some people (like me) prefer to use the default X cursors over the "improved" 
adwaita ones, so you should leave a choice there.
You should add these lines to postinst:

update-alternatives --install /usr/share/icons/default/index.theme \
x-cursor-theme /usr/share/icons/hicolor/index.theme 10

And add a prerm:

#! /bin/sh
set -e
case "$1" in
  remove|deconfigure|failed-upgrade)
update-alternatives --remove x-cursor-theme \
/usr/share/icons/hicolor/index.theme
  ;;
esac
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJeu3CcAAoJEIJMNe5OCOiS3dsH/0CXUzTlMha2qYcTdxHy
1o61y++xKIuEuZfhU/I1eOw2Ei5EziHFNpP1+PrYoZxNeN4titBcb22bSLM+
/OanHMezYUOydQABCuzFKuvEs/Rvkgkg1/Y7fcOBoen+3bE9P8d0je+5NEBJ
ym0yHGEXJxmvgyP77MOzF57kd/SRphR3aE11RfnS0ocXwaiL1ZRxwU+gefEr
i90o2CRu9nOiCU6igYqVIpOf5TmI+KmT7HB+NfV/EVym1pEB084Ahlq3K/EX
kjUxrk3BdqtTEkChnhSumsA4oqKUucDLY1Vvi80TPfPqYaVIQ+N+bddGIGRF
WJ03GcHnhr4NQWs3jzDPheU=
=YzfM
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xD213AC78.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc.sig
Description: PGP signature

Bug#960409: Not a bug after all.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

It turns out that in the new version I have to use backslashes instead of 
forward slashes in the kernel command line.
e. g. "initrd=\EFI\EFISTUB\INITRD.IMG" instead of 
"initrd=/EFI/EFISTUB/INITRD.IMG"
Forward slashes work in the previous version, but not on this one.

Please close this bug. I apologize for the inconvenience.
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJeu2A0AAoJEIJMNe5OCOiSmsQH/RlX9uhHpemGPrF5ddb2
oumtdc2ns+lkmIINnq09JQN8V28dYE5UJEdyRu4EflefytptbujPhX9g6yMo
oOC7XE/7eQJQAonnEC8R369iTL+hEJT1e6RgZ/fMnNUUSsPlMNlPizoIT1cj
NlEetGwnhJg63Lty916PLyoh3LJUiirok6U9X3flHjFk5P9qvsOI6yw1dCMr
9Qg+nyTuOfC/U+1QZx/8j6Vysmp/BiTexyPz/lgEljtEQ1HwCdJ4t4oxomOg
nstVucDqq7wFCPYP3lbbieXZZJw0LKmzQ9We2B63wF71NGdltE9wJjnnbSx1
JFy7rixafjM/kTkWfPIfqfk=
=tQ8P
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xD213AC78.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc.sig
Description: PGP signature

Bug#960409: The EFI stub does not work.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: linux-image-5.7.0-rc5-amd64-unsigned
Version: 5.7~rc5-1~exp1

That kernel has dropped to the experimental repo a few hours ago, so I 
installed it, regenerated the initrd, and copied them to the ESP, and added an 
entry for it.
When booting the kernel, the screen blinked for a moment and booted the next 
entry, which basically means that the EFI stub in the new kernel does not work.
The previous version, 5.6.0-1, still boots fine.
The motherboard is an ASRock B450M Pro4 on the latest firmware if that matters. 
Linux is the only OS installed and Safe Boot is disabled.
I cannot provide any log files since the UEFI itself does not provide any.
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJeuoV5AAoJEIJMNe5OCOiSC3cH/jDhurswbIxKeF4n2q2q
VivhbqThi/PBftaf8ESTZEyFY67tEDDU1wvq+z0Josbl4nwUBjo6kfF2l/m6
3d9zamEiJ434MdBtkgNRhVZZbr/FP5DoKbZGF9HQUsBTrE1mX8LPmIaErT1R
8Kegklm/Ruc3janU/Bct/+sF75/99abFcCwO3VDtBfEmt0D00WHZDAqjnE9Z
GITXYXwElK9f/rIY+u21icBS37ioeCVX4QpVBwtmR7RMqgkJOuXD96yoIb/A
lftDc2uWjPiZ85EgbQj6ioFPadQKxZt9CoMLNO2E+OIK0wnusgHv07hUzs97
LVBy6Fjx0Ex0ct3bsE6YE0w=
=j4Lp
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xD213AC78.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc.sig
Description: PGP signature

Bug#939748: Additional information.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The problem with the OTB format is that there are spacing issues. Also if you 
do so, the same font would appear twice.
A possible solution is to keep the old version of Pango (libpango-legacy) in 
another package, and provide an alternative in dependencies (Depends: 
libpango-1.0-0 | libpango-legacy).
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJekblVAAoJEIJMNe5OCOiSQ8UH/A5CRfK1s5bC3/VOjugj
AO3+287q58xDxOYUBno2AyEAFlNXFVyNGzDqwrKdZEcpLkqpLRu3s7NAt6V0
qhcAT5ZUp643ShFhj1junDsQ+OAdHqER98XsgUrQLYBLh084yXj3rZtbU9HF
1ZiJt7ePUX+JmZkXJ7e/szjvhnA7lcHUSAor8fDu8jPldkMu81ka5bQpGEtC
O3mXHyFaGFpU9ZVDrWfV4EMh4wrEIrKJqEwV3NKNtkpuU4ltT04kMClB4CP2
rxdoMjwtno774FgrFXcc59rcIdxqF1cYCD7VIj+9OW4EeOn3zf+pSmcdwvck
uRqSUWHTk8tPYBR3/aCMzD8=
=4ujE
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xD213AC78.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xD213AC78.asc.sig
Description: PGP signature

Bug#947871: Move non-relevant programs away from "e2fsprogs".

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: e2fsprogs
Version: 1.45.4-1
Severity: wishlist

Some people do not use EXT for various reasons and have set up the OS to use 
another FS like JFS, XFS or BTRFS.
Since they do not use EXT, there is no reason to install relevant utilities.

My suggestion:
1. Do not make "e2fsprogs" a required package;
2. Move the following files to new packages, since they are not limited to EXT:
"/usr/bin/lsattr"
"/usr/bin/chattr"
"/usr/sbin/filefrag"
"/sbin/badblocks"
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsFcBAEBCAAGBQJeDF7WAAoJEKtW6mkgNPIbhuYP/j30wl3h5llftPWICXE7
ZF41pUhEQnecXQQqv1oG5A7glCB4TepONWUn014ZP/A82LwcuWRPVUdCh4no
d61UDESP525m0C+yXAbmpQCIvzIkc2F1bQ41foSy3jssv2ZCtz2nhoMCsGWx
cL9UMXCdOGRVTMhe1AjclDY7PIR7T3+sSaV8SB5CWvXMUf1ebNYvEjxwO5eG
CeRF/yHxbz41V9seY0v0STUgxI/9GcsZaOEwZBvTLzfUlN5jO+Eh5PSQDE5b
ylSwoksFFNKlsyYGAJC9jYIMxVVVCaRESVmgoRAmvyGBcJx1WgIJ0+ubo2OV
GFLel5NtoESpsJ45FiPqgYt2fgduNi13ayl4QjZKoakUSC4rLWvKmOukXO8c
/wPati+NvnmwHefHF2MKFRsCjbiLVkjz2YBcv8nNmm3ePX8coPfYS/mQKypb
1bx1np5Z+WJJvGirLV/fAxDGccH9DdKdRPO/RIZz4zJ/gQHyF+ypn618o0hz
K7R/fFK1d7XdljjhnaBoadHrvX9W+cGdTGVHkH50qEdaAuvNZgx8BEQnPXHm
DQQ6G+d4CruIO0DIZP/yL3C6SAWHJJE8U3XM2RBYoz19UPzrcJKkRfNbmnwl
3Tzso1SDRVV98Hojbjh3NObjHR+6RaAEp+ArC29ohyRUqhH0a+ouQ6YqV6kC
wUsy
=0aO9
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0x71E3123C.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0x71E3123C.asc.sig
Description: PGP signature

Bug#945920: Chromium randomly crashes in the latest version.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: chromium
Version: 79.0.3945.56-1
Severity: important

After updating to the latest version, Chromium randomly crashes after a while.
There are no error messages. It happens randomly and just abruptly quits.
There is no "dmesg" messages generated.
I used a temporary profile and it will still happen.

Stack trace:

Received signal 11 SEGV_MAPERR 
#0 0x5653d1480469 
#1 0x5653d13c9a76 
#2 0x5653d147ec63 
#3 0x5653d14803e6 
#4 0x7ffa7263b510 
#5 0x5653d27ed107 
#6 0x5653d0ffd850 
#7 0x5653d0ff5922 
#8 0x5653d1424b35 
#9 0x5653d143403b 
#10 0x5653d14359bc 
#11 0x5653d13e649a 
#12 0x7ffa7171bf3d g_main_context_dispatch
#13 0x7ffa7171c1c0 
#14 0x7ffa7171c24f g_main_context_iteration
#15 0x5653d13e67a0 
#16 0x5653d1435c79 
#17 0x5653d1411cca 
#18 0x5653d0f17cb7 
#19 0x5653cf23d046 
#20 0x5653cf23d1f5 
#21 0x5653cf213477 
#22 0x5653d0e9fba1 
#23 0x5653d0e9fdd8 
#24 0x5653d0ea0147 
#25 0x5653d0ed62a2 
#26 0x5653d0e9db66 
#27 0x5653ce3cc425 ChromeMain
#28 0x7ffa6bae __libc_start_main
#29 0x5653ce3cc26a _start
  r8: 5653dc28af00  r9: 0001 r10: 5653da8dd010 r11: 
7ffa6bc7ec40
 r12: 7ffcf239ae50 r13: 7ffcf239ae30 r14: 7ffcf239ae50 r15: 
5653dc3ae940
  di:   si: 7ffcf239ae30  bp: 7ffcf239adf0  bx: 

  dx: 7ffcf239ae50  ax: 7ff9dc002810  cx: 5653dc45bb20  sp: 
7ffcf239adb0
  ip: 5653d27ed107 efl: 00010202 cgf: 002b0033 erf: 
0004
 trp: 000e msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJd4ySwAAoJENi1YDlFXXQfDFEH/1VzTV+JyJ7ody7FMorh
dSJ+l60HtPNxDrxRCgGydNzJzJHu47FPHqgiwetNeXgNJGEULiyr/XPk0JLQ
6bliAMCjdFJvIth0hBsINPRZK+Oh5f+gUiF1M1CDikwL7CGxc34zeCODscJ2
kTakc5ikZdFMlHg6UnizY+qX0VyETUGEtZb0FwoGUC9UOrJWJTUBHQnK6Umv
jweGFoypgZWyqp9UOsgLeAfWf3OEWMKYOGH1TtasjS7WSIbvd+OncxAYiC9+
0AY7e/TxRqD/h7GxK0DO5CLCWkG6ulvsHyG5hCohYetboluZehXy30aq4REF
tkc6gKGNto1EoWMdcvb1A2A=
=j/ZR
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#945256: Do not make `gcc` depend on one paticular version.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: gcc
Version: 4:9.2.1-3.1
Severity: wishlist

It seems that the GCC-related packages (`cpp`, `g++`, etc.) have hard 
dependencies to one particular version of said programs, so when a new version 
of GCC is released and a package depends on `gcc` or `cpp`, I have to install 
multiple versions of GCC or CPP.

I think that a better idea is to:
1. Make GCC-related packages virtual packages, and make various versions of 
`gcc` like `gcc-8` and `gcc-9` provide the `gcc` package name.
2. Use the debian-alternatives system for the GCC-related binaries, so if a 
program only needs to use a compiler, it would use the latest version (or 
user-specifies version with `update-alternatives`), and if a program needs a 
particular version, it would directly use `gcc-8` or `gcc-9`.
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJd11OtAAoJENi1YDlFXXQfk6IIAJQpYVtuOm0WaRGKRytF
r6C1+L+bU3FwIFs1PWxeZTlyeP5Z64CChl6EscU4j+JQgKZKE84tWCysnGgB
5986TmDHh6aD3Z3x8l4XiL/Ukz3kWhnvATvIBKAbQGHSDKhhNvs+7cUtQbrc
42W0JsQeSlMfgITPkMFV8VHZ17FA45+U4YA/hexzMk3TPGLgXVGcvRb1JYqX
O1UlV9h/OPce17v+YdOXSNPXY8Ob0DSrc7R7Sus/9YuMnE3rlouVowAy0G09
z8JfldBAHqp2CZKYvBkQQ+tAg3Otj0sgpQNlLgMlrWeI1oDqjKGWPc+qjbE8
dfYkWXrQAr2xIKCPVqSxcLA=
=vGb5
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#944224: Keep "dmesg" logging after boot.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: initscripts
Version: 2.96-1
Severity: wishlist

Currently, the "bootlogd" script only records the "dmesg" messages during boot, 
and exits afterwards.
However, most system issues happen after boot.
So when such issue happens, nothing is logged, so it is hard to find the cause.
I think that it is wise to keep `dmesg` running after booting.
To be precise, change line 35 of "/etc/init.d/bootlogs"
from "dmesg -s 524288 > /var/log/dmesg"
to "nohup dmesg -Hwx > /var/log/dmesg".
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJdwpx3AAoJENi1YDlFXXQfSkEIAKMgrTXx66UQWUP65+Lt
460SljjDd0gMlKh57fUQuQJdEU4kjrthdefu2tD5nYHXzrKlRbKJ9mgq1tcX
sFvR/MIt0huffSESzwOkOTt+tfWLT3ZfTlE9I332WjJjuXF9bdn84XRRGobS
XASbnwRPbtHMLOv5w/6ABWD8MPO24QwxYBSiCAPiG1NhUb/amZWSz3tRVUMF
LJEggQdd4veyF5NROM6mauHISgj6N3vRyPiLs+j9qAYSB03oCi1wC0CJ+Bo+
eXywW8SdpP/e6tbwARIAdae61v5sJNSKYFxtrh9uXCcIYU0+YowqOUDhYZ7K
YzStKv3R5g1y/RCcmZPOirM=
=pOyO
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#939748: Additional information.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

It is sad to see this. It is the same reason that I refuse to use GTK3.

I hope that you can contact upstream to preserve bitmaps. Or at least compile a 
separate package with bitmap support.
The problem is that most TrueType fonts are rendered poorly unless you have a 
high-DPI/"retina" display, which most people do not have.
Also, remember that embedded devices usually have low-resolution screens (like 
128*128 or 64*64).
If you enable antialiasing you get blurry texts. If you disable antialiasing 
you get out-of-shape texts.
Bitmap fonts have no such problems because they are pixel-perfect and does not 
require antialiasing if a fixed font size is specified (which in most cases is).
Last but not least, bitmap fonts are easy to edit, unlike TrueType fonts.
Also, not everyone uses a DE like GNOME. I (and many people) use WMs like i3 
and TWM because they use fewer resources and has fewer distractions.
If I use a minimal WM and I use the terminal all day long, obviously I want the 
UI font to be the same as the terminal font.
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJddYolAAoJENi1YDlFXXQf9nMIAIiZ8obxAUt4faKEnwEp
zmHmAY1bydH/yWRzxqZ5WGu1BiWkna0tPL2dIuPA0dp2W1rPMR5YnrkbaKca
c1H17Y9XeayOhs1GObEEihmORJiEuYwfhFS5LLT9emRS/fd0NfwtrRZU1+iY
ytZaO8RU11larzPPzLCHDnGoGGf61q61/+dDA7vDbYVVQ4tlunkQd/pFdqEm
Ye4TbW7En3I4tm/n6unv3sIjCbMbTJn62ECs0KbmaI33u3iXYB8Xq5pBVKbU
cSJqCOQb3JEKONt2TZKY8v8Ohuclf2ri6ZAQjV1zzHQ9Tx9NcVNhJK8a40jI
Dx135xocUWvsunBnYiA+/Io=
=SHFu
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#939748: Newest version breaks rendering of bitmap fonts in GTK applications.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: pango1.0
Version: 1.44.6-1
Severity: important

The newest version in the experimental repo, 1.44.6-1, breaks the displaying of 
XLFD bitmap fonts in GTK applications.
If you set the UI font to a bitmap font (Fixed) in /etc/gtk2/gtkrc, all 
characters are replaced by empty glyphs.
I do not have GTK3 installed (since I dislike the direction GTK is taking), but 
it should affect GTK3 as well.
Downgrading the packages "libpangoft2-1.0-0", "libpangocairo-1.0-0" and 
"libpango-1.0-0" from 1.44.6-1 to 1.42.6-7 fixes the problem.
See attached screenshots for the issue.

PS: Before you say "nobody is using bitmap fonts", you should consider that not 
everybody has a high-definition screen or want to see blurry text.
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJddOP1AAoJENi1YDlFXXQfzh4H/Ax28fn3LDpSxDCoNGaq
vbl+Fq7UPt+gszhXlC8z6j6YO2tFnC5aHS7iZ+Maw7KkXg7QbcQEUFqll1dI
91fd28sLusNQufCbW4vKdQckpBRivetl4QNkOGm9J4Fftm6vN/HcEKWNxBHp
YcQ33xY21Pl7OrS+bZaWLYSZgqn9ITdb9iq9WwfiK2K1laN1txNIPgXibu9i
bpOe6MgysTCbVj4aBO2/rIZMY+VJOAbyyP0XwPkqiMqTk56jLx/nawtUd1hB
rB33HBSFOPlfZMfmedLaBKEshrTchDGQ8f6dodnC9QheNaLh1Ac/If+iylZT
z4gTwPrx9uB8x39ltw7CJ3Y=
=SO62
-END PGP SIGNATURE-



before-update.png.sig
Description: PGP signature


after-update.png.sig
Description: PGP signature


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#929754: Restoration failures due to PID increment rates.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: criu
Version: 3.11-2
Severity: important

How to reproduce:
1. Dump a process with many threads.
2. Reboot.
3. When trying to restore, it fails with "Pid $PID do not match expected $PID".

The problem is that many thing in the OS creates new processes frequently and 
take up the PID desired.
They create new processes every few seconds, and they are too important (or 
simply impossible) to kill.
For example, "systemd-udevd" now frequently ends and spawns child processes 
after an update.
BTRFS also frequently creates kernel threads.
Even worse, CRIU now set the starting point of new PIDs to the restored 
process' PID,
so no matter how many times you try, it will always fail because the next few 
PIDs are quickly taken.
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJc792pAAoJENi1YDlFXXQfpaQH/1X37GkNBHkgw+96EgEm
ACL+WfEOewF8AF/MYfuTEcsl3xlAyB/X7JcrnnizN/tiqYqlZYf1sQaAv3Vz
F58jJEu/gJdIL/DKEqRTyI06F38fPOnpj1IR1dOUx/uWK5vYTuaxxnDcdtFX
3vypvFxm8M/jH9OdO3YAKxjVgWpyKH2jWjKAnUdiydDZEd0QfGW1sUb1dvUk
aPLu8c+kzs545Q5e7mRLFLEyNsWg9isIKH+txKgrzlTOMnLdX/Bcpa4VjkZd
PQ80yPtMDp7WZrqPw2zFOTQ96O4tJQFE4vuWYfabhYBTovjtXH61LTnN3sZd
Um3dKbwAzcXI8u6kmV79OaY=
=6MUI
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#915094: Not limited to EXT4.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Now the problem happens in JFS as well.
It is a kernel bug, and it looks like that it is not fixed in 5.0.
Because of that, I have lost nearly one month of work. How sad.
Here is what "dmesg" said:
-BEGIN OUTPUT-
[287480.751455] sysrq: SysRq : Show Blocked State
[287480.751462]   taskPC stack   pid father
[287480.751496] zpaqD0 33088  1 0x0004
[287480.751500] Call Trace:
[287480.751510]  ? __schedule+0x2d4/0x870
[287480.751515]  ? wake_up_q+0x70/0x70
[287480.751517]  schedule+0x28/0x70
[287480.751521]  io_schedule+0x12/0x40
[287480.751530]  txBeginAnon+0x16c/0x1c0 [jfs]
[287480.751534]  ? wake_up_q+0x70/0x70
[287480.751541]  extAlloc+0x4b/0x460 [jfs]
[287480.751547]  ? extHint+0x7c/0x110 [jfs]
[287480.751552]  jfs_get_block+0xa1/0x2b0 [jfs]
[287480.751557]  ? pagecache_get_page+0xf2/0x2c0
[287480.751561]  nobh_write_begin+0x161/0x4c0
[287480.751567]  jfs_write_begin+0x32/0x70 [jfs]
[287480.751572]  ? jfs_release+0x60/0x60 [jfs]
[287480.751575]  generic_perform_write+0xf4/0x1b0
[287480.751579]  __generic_file_write_iter+0xfe/0x1c0
[287480.751582]  generic_file_write_iter+0xab/0x150
[287480.751585]  new_sync_write+0x112/0x180
[287480.751588]  vfs_write+0xa5/0x1a0
[287480.751590]  ksys_write+0x4f/0xb0
[287480.751594]  do_syscall_64+0x53/0x100
[287480.751598]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[287480.751601] RIP: 0033:0x482c67
[287480.751606] Code: Bad RIP value.
[287480.751607] RSP: 002b:7f3a5b132bd0 EFLAGS: 0293 ORIG_RAX: 
0001
[287480.751609] RAX: ffda RBX: 0003 RCX: 
00482c67
[287480.751610] RDX: f000 RSI: 7fff8a22a55c RDI: 
0003
[287480.751611] RBP: 7fff8a22a55c R08:  R09: 
7fff8a229058
[287480.751612] R10:  R11: 0293 R12: 
f000
[287480.751613] R13: f000 R14: 7fff8a22a55c R15: 
f000
[287480.751626] kworker/u8:1D0 65623  2 0x8000
[287480.751631] Workqueue: writeback wb_workfn (flush-8:32)
[287480.751633] Call Trace:
[287480.751637]  ? __schedule+0x2d4/0x870
[287480.751640]  schedule+0x28/0x70
[287480.751642]  rwsem_down_write_failed+0x17c/0x3a0
[287480.751645]  call_rwsem_down_write_failed+0x13/0x20
[287480.751648]  down_write+0x29/0x40
[287480.751652]  jfs_get_block+0x59/0x2b0 [jfs]
[287480.751657]  __mpage_writepage+0x2b8/0x790
[287480.751661]  ? page_mkclean+0x6e/0xc0
[287480.751663]  ? invalid_page_referenced_vma+0x80/0x80
[287480.751666]  ? clear_page_dirty_for_io+0x230/0x2a0
[287480.751669]  write_cache_pages+0x1aa/0x440
[287480.751671]  ? clean_buffers+0x60/0x60
[287480.751677]  ? jfs_release+0x60/0x60 [jfs]
[287480.751680]  mpage_writepages+0x75/0x100
[287480.751684]  ? jfs_release+0x60/0x60 [jfs]
[287480.751687]  do_writepages+0x41/0xd0
[287480.751692]  ? jfs_commit_inode+0x89/0x100 [jfs]
[287480.751695]  __writeback_single_inode+0x3d/0x350
[287480.751697]  writeback_sb_inodes+0x1e5/0x480
[287480.751701]  __writeback_inodes_wb+0x5d/0xb0
[287480.751703]  wb_writeback+0x25f/0x2f0
[287480.751706]  wb_workfn+0x30d/0x400
[287480.751709]  ? __switch_to+0x8c/0x440
[287480.751714]  process_one_work+0x1a7/0x3b0
[287480.751717]  worker_thread+0x30/0x390
[287480.751720]  ? create_worker+0x1a0/0x1a0
[287480.751722]  kthread+0x112/0x130
[287480.751724]  ? __kthread_parkme+0x70/0x70
[287480.751726]  ret_from_fork+0x1f/0x40
[287480.751732] syncD0 67361  67333 0x
[287480.751734] Call Trace:
[287480.751737]  ? __schedule+0x2d4/0x870
[287480.751741]  ? default_file_splice_write+0x20/0x20
[287480.751743]  schedule+0x28/0x70
[287480.751745]  wb_wait_for_completion+0x5e/0x90
[287480.751749]  ? finish_wait+0x80/0x80
[287480.751751]  sync_inodes_sb+0xd8/0x2c0
[287480.751754]  ? default_file_splice_write+0x20/0x20
[287480.751757]  iterate_supers+0x98/0x100
[287480.751760]  ksys_sync+0x40/0xb0
[287480.751763]  __ia32_sys_sync+0xa/0x10
[287480.751765]  do_syscall_64+0x53/0x100
[287480.751768]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[287480.751769] RIP: 0033:0x7f8cd49bf287
[287480.751772] Code: Bad RIP value.
[287480.751773] RSP: 002b:7ffc3ac18868 EFLAGS: 0202 ORIG_RAX: 
00a2
[287480.751775] RAX: ffda RBX: 7ffc3ac18998 RCX: 
7f8cd49bf287
[287480.751776] RDX: 7f8cd4a8c001 RSI:  RDI: 
7f8cd4a50b3a
[287480.751777] RBP: 0001 R08:  R09: 

[287480.751778] R10: fb34 R11: 0202 R12: 

[287480.751779] R13:  R14:  R15: 

-END OUTPUT-
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJc6naeAAoJENi1YDlFXXQf+XkH/RO/ifsa3vdcOzFrHQYq

Bug#928336: Suggestion: Separate client and server packages.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: shadowsocks-libev
Version: 3.2.5+ds-1

Please separate the package into "shadowsocks-libev-client" which only contains 
"ss-local",
and "shadowsocks-libev-server" which contains the rest of the suite like 
"ss-server" and the system service.
The reason is that most of the ShadowSocks users only need the client to access 
forbidden websites,
and there is no point to run both the client and the server on the same host.
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcysXNAAoJENi1YDlFXXQfe58IALpRBSp91Llji9XbVcuF
UGHWM2lNSrFqaG7Tw+ScV8hxyfJFsqH5MBB83J/39CJvIYU6FlD3xlzDRgY6
XuZbQ0gUimi/CyvLPNGPJSgNkjFMWj2DGbtfQGARN+pg1xQz3iGIu+jkPq/O
5z7F1MtdhXuu5Zuymtmx7ZO4JH4GPTJbtU9MnedotMN1JagHAWQTd7wp94aQ
TdQMOQ3LUoMBYl9TGm49ZYa+nVxm0XW570K6jwUtw1g/4QPJa2IRp09bdBs4
NneIVYMMvW74uUzbOzu4Er16F+SWtam0dwa60zKtS0LqOfu92lXyNfHcHslT
JymkN1I7ksMcnnnMsYvvhlc=
=2I8E
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#923701: Additional information.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I do not think that they are related.
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcxTCxAAoJENi1YDlFXXQfMVwH/3yzqXiLe9kRDzftW3QG
OwkelU+xrx6aljj0iZyJFQVpI+BLWosMo1ZSI5h1Q07LwqKaRtY7ryeYY+Yx
VFCSayQKfGH/sevyr/PpNi34HsrxeBiZAI21UPWl4KlLIwr2hoivoFI/nWoF
gwv7gpKLIYXNfjyNBYgpgQdRdMozOTZkcP8SF30dyfoOaGICacE8XtL/uM0u
Q+eCl2RybCdZ8i5hAH/Yw6FijpfMu5cAYeBjpcjX3hS9UexIH7ZWyF1ExmID
Zbi2D5ImsaqD49EHXAEySMms7h/Z9g5Vm3aNrzT52raIDoVoqYLjwd6UGGOR
nRRMTmI6S+1vkR5HHUrtQHk=
=VyKn
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#923701: Additional information.

[Gong S.]

Sorry for this reply. I am on mobile because my workstation is under repair.

It looks like that the problem happens in the Windows version of Chrome (and 
Chromium) as well.
When I use a classic theme (in Windows 7, this means screen composition is 
disabled), the same problem occurs.
So it means that with the new layout, Chromium now expects a compositor. This 
is a very bad trend.
Not everyone use a DE, and you should not force everyone to use one.

Sent from ProtonMail mobile

publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys

Bug#923701: Problem is not fixed.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The problem is still there in version 73.0.3683.75-1~deb9u1.
It looks like it originates from Chrome's new layout.
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcquZJAAoJENi1YDlFXXQfntYIAJRqkOyl5UvLef88CvSu
gTNATlI4+eBnXW3Y2YB/30Ie+ehmQoZWJyVbcAMmx/MSoxgS6a8Rp9sjCb79
1+EoZ1rsf4c+YbYPxhWi/+9xI1NAKfub7cw9HZKiJNaWDjTGze+KKVYgtIRA
xUoZRLHdd4UuGcHqt2Bu8Hmm5q1VdM9GvkoVZu5mH5U6nnwhFTgXYDX/1Dm9
ezC1mUVeBcZGPXKDzDknBhimtPkypW/IFXm+j63ZPkS6QznbRN6DYrEKiEZs
WjEM9yIAm9MekEloFDNKF4X0MnFms7KAUnlvkCpHogNN4UBp2to8yspfKzPj
ooMwtL+xgmcdbtlyoR5iK9Q=
=AFZ6
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#925951: "zsnes" does not support symlinks.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: zsnes
Version: 1.510+bz2-8+b3

Steps to reproduce:
1. Start ZSNES and save settings.
2. It creates a "$HOME/.zsnes/" folder for the configuration.
3. Symlink that folder to elsewhere, e. g. "$HOME/.config/zsnes/" (the folder 
is already created).
4. Start ZSNES again and found that the settings are not applied.
5. Change settings and save them again. This time it directly put them in 
"$HOME/".

Not related, but I hope you to follow XDG and move your config in a sane folder 
like "$HOME/.config/zsnes/".
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcnbBvAAoJENi1YDlFXXQfWNwH/AxEhkWM8m/IMQT5M7N7
IggXNvccxJywg4lcYk7lR4JSiCSqlHQA0gHApHX4TuSWW1J6mztydArm7PCV
ZGOSQEgWIYuzrcFlPBb2K7LN9G7hShRwo9aaDuy0IvEVc2JVbfEYJgvqWGDZ
nWeUKINc5/VmHZ3eqVcxmTnOtN09kwv+/R9u9itdwlCb8XaJjnvEFbVHhb4k
WX5e1CrwrjiRWPWBfs4zG94QIj/dXZ9V4zS78Mv+eGqCqBvWqo1V5C5TAhMH
O5SiM5E3+PAmOJHRM+iJbXdwxSoAnjhhCm4BuROAvw/yvBTzrhD4fH2sTEcu
ERLXEFLP0lx+Bqu+IFlSRxg=
=C0kg
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#925440: Seriously?!

[Gong S.]

I'm on mobile, so forgive my formatting.

>The file ~/.mkshrc, prepopulated from /etc/skel/.mkshrc, loads /etc/mkshrc if 
>it is non-empty (in Debian and derivatives, as well as several other 
>packagings).
You should not require yet another hidden file in the user's home directory.
My home directory is already messy enough. I clearly do not want it to be even 
more messier.

publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys

Bug#925440: Are you sure?

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

>This was done in 2010 already.
No, you did not. I created "/etc/mkshrc" and it is ignored by "mksh".
If I symlink "~/.mkshrc" to "/etc/mkshrc" it works, but if I removed the 
symlink the file is ignored again.
>...and ASCII is not enough to represent almost all of the languages I speak.
...and I cannot type anything beyond 0x7F easily on a standard US keyboard. In 
a place like this, please use English.
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcmN55AAoJENi1YDlFXXQfzlIH/RzXsYcDSX35eLUr5ZWn
OLoOQ4UE4dC9lBXBdAkoQcRUgJMQ0Dp2EbysPtfhY+dtlR+yGd3SDXIH+boB
OO2pLXuzwtq+WLwqM/heJxOmpho7opONW1A7UNqd6szEGKHRT5AnRS/nlywG
tJYS/7ZHajbRy+kRdMWbZJCXE67skkcrpvnlxLnAh6PHBo/FBlkCrr1clDtp
MJju4Aj3SQkoqrLzmToitz+MNaP0d31ub8n67YDKBC1YDf7EbY5NuT/2wIwp
KclFKdpwqP/ySHfkhJnuyid6QFvxnMbksRdZVv1b+8B4IWCPyI0C/w05180p
eblpEvvdfgZim9tmswUm7kk=
=D7F6
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#925440: Feature request: support global config at "/etc/mkshrc".

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: mksh
Version: 57-1
Severity: wishlist

Can you support a global configuration file in "/etc/mkshrc"? Just like "bash".
The Android version of "mksh" already does this at "/system/etc/mkshrc".
This simplifies configuration.
("/etc/profiles" does not count as it only applies to login shells)
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a terminal.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcmEtzAAoJENi1YDlFXXQf3qEH/R1VP5kC2reKD3IHzGIr
goxxSsgJY9/KH/TdA/XJ8YzQ9GYJzd7tSM7mt16PMjk9DVeRnm+8Z2/qTnT0
O14rKuM5H8UvHTv2o24FuDiIBVOYMF0JCuz1b5aHDYAkdPTDiENsf/WGcXTa
nuLdhc+/pNjKGyzEQQbcgq0wno4D9q0BNo58kgZ2h7WgKqklXZbO83k4B4+R
lN0KWhA9iw7N6v0ZnCwTGOXFuruCCEUWQJZfHV/TkU5f4mwR83M89TEkc4pS
i5uEX6pd/faiS+3W27XdmNJIb/GZPOL7VUtzz3rZIcdUl6wnQU+QvwO15ExK
xbxnUbcpY2vB1btFr5vpGXo=
=8MpC
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#925128: Correction.

[Gong S.]

Here is a correction. "defaults-disabled" does not seem to work, so I set it up 
normally and disable it.
--
Please limit your reply to 7-bit ASCII.

dhcpcd5.postinst
Description: Binary data


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#925128: Additional information.

[Gong S.]

Here are the files that need to change.
Firstly, the post-install script.
If "ifupdown" is configured, use it instead.
Secondly, the config file.
Many networks are IPv4-only, especially college networks.
So you should still use "clientid".
--
Please limit your reply to 7-bit ASCII.# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.

Suggestion: IPv6 is still unpopular in China.
Many IPv4-only networks will only use clientid.
Better be safe than sorry.
clientid
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# Most distributions have NTP support.
#option ntp_servers

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private


dhcpcd5.postinst
Description: Binary data


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#925128: "dhcpcd" launches multiple times at startup.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: dhcpcd5
Version: 7.1.0-1

I am using SysV init and "ifupdown" to configure my workstation. 
"network-manager" is not installed because I refuse to lick Lennart's "D".
"isc-dhcp-client" is not installed, so "dhcpcd" is the only thing that handles 
DHCP.
During startup, the network has already configured in "/etc/init.d/networking", 
using "ifupdown".
Since the interface is already configured, "/etc/init.d/dhcpcd" will launch 
"dhcpcd" a second time which fails the sanity test, causing the service to fail.
My suggestion is that if "dhcpcd" is already running, "service dhcpcd start" 
should do nothing and "service dhcpcd stop" should kill all instances of 
"dhcpcd".

Related configuration:
/etc/network/interfaces
---
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
dns-nameservers 1.1.1.1 1.0.0.1

/etc/dhcpcd.conf
---
hostname
ipv4only
clientid
option rapid_commit
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option interface_mtu
require dhcp_server_identifier
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a terminal.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJckc5oAAoJENi1YDlFXXQf78MH/0/MBuOhCvC6U9+LtAHp
7Sl4ngqe+zGkK7LPf269lVplWPjXu/dcjl59c62Mb/dsJxh2qHUFEtd0GBwZ
n6Xr4CguMZ4fiYoiZMOJLzIVieIO1Msa8JbrIVc/xxR0Sur8VwFK3wKJAtNq
Ct02o2rcDAF8+j49IA4TnMs8IOuuKHl8c3QKloq3qESNje+59MtqrqASIGLU
u5RUAWKE2dVyUkwho/0QIfFV6z7c+OgihH4vtqbgyonUwZJG3tjF0UJug336
iThiinsAvCyp5HJfB3b/xP+InE04xUqw9BWZRkcnpJm+HQbSkcIvEUDuSdIo
npNwz0OBm2o1/MqlxItHpaw=
=Agxf
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#924901: Chromium ignores SIGTERM even when respective settings are turned off.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: chromium
Version: 72.0.3626.122-1~deb9u1

Even with "Continue running background apps when Chromium is closed" option 
turned off in settings,
Chromium still runs in the background when I close all tabs, close the entire 
window, or choose "Exit" in the menu.
As seen on the attached screenshot.
Even worse, the residual process does not accept SIGTERM, thus wasting cycles 
and RAM. SIGKILL still works, though.
Maybe this (mis-)feature is good for some users, but if you offer an option 
there and I turned it off, it should respect that.
---
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a terminal.
Thanks for your co-operation.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcj1jHAAoJENi1YDlFXXQfPooH/0SiLMNXFLme6HyGEmOg
RnmP9JX1OEebzIQnhLuvl5CwVhRhw6A967DoSUouqwiSxwe4GfRNfXuQxlTr
Yd7/PC1M9kHbRQeRm7dA0GLSYSdgv4Kf5xQPXHpFxDx2KfhgS5F8vhWkdcnm
yVJGlrV7ZQYCFziyXsirodZlzf/J09qAFgv5dsc18GjRIL/NAh9wztkrP5pl
4BlRa3WXJC+0vmg3PIN6Z1ZTNVgCOVY1ONCLe1vyJ0jS/dq7Drn9d2CwqMpz
LYCUf/fYD/zZHQH1+1n4hcJlpix55rXdiAi8TcnIUJ0KvXJq1aIE2tjnVz2B
BGdM4UNZF5wAAGxgp9D+6xk=
=dp2P
-END PGP SIGNATURE-



2019-03-18-162629_1600x1200_scrot.png.sig
Description: PGP signature


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#908199: Not an issue in "aptitude".

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

It turns out that the problem is that in kernel 4.19-trunk the console 
rendering is broken.
Updating to kernel 4.20 fixes the problem.
Please close this.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcgxfZAAoJENi1YDlFXXQfHIQIAKZ0vZaktX00PXOZwvbZ
vzrlxgJDjvORhAjaRGZO5HW2Q0D6NrgEAYRWeqEFvRN6we41XBe6m09TOp7m
wcQ/r6Ea4tRbCNe4JCCdrYjwovbwg+XExvyB+7rPcVk4uDF3L5nDynOzab48
LOdkuuc7jitIsbWU4fI9sxUTB+bL2C8FnbCNNABwn120kWMCCpzSczn/RHIa
tvp3hvMckDTh+dZWF1+fUiPuwgccjTIrUr+dE8wURdd7S1+iMt7vYY/6Wt3q
4ulKkXYfxA8JzbesQFSzLxcxDjuIKeDuwQ6byR+HpLQd+oHPH0WYZlVkql8W
fW7fyJ/jzfqOmcdrdGGpiiw=
=B2+B
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#923701: Concerns about GTK.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Thanks, but I hope that the new version is still compiled against GTK2 in the 
stable repo.
I have submitted an issue before in #901021, and I am deeply concerned.
GTK3 is not an improvement on GTK2, but a bastardization.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcfS4AAAoJENi1YDlFXXQfp/YH/28VGHMmotxKJ7yVSZK3
Cam6UsBqpv42YN5zXdO2GeCdHLGbc7TB0W/70XO8Z0efbiq2RJMmJdG9lmVY
MhQPDzpywZbUg8nb7oCnMLEMcL2l4M6PI+ZAdiyKz4H7ojYRGg3qMyAw+ZY8
eOdZXK/d/BfxG2Oy5DaFwb2DpXfZ1frBhN53FgBy0bdGJbzV9o8AaSioE46A
ETIIeBiJPdxFaKOzUkfGmcbjcD3JM3BKqB5OGwR9+x4w1hJFEWJkqTMTWswP
jiqPOgFOtJlzKtfGrkHRG6ZXF/TFIVYIVxC1SZQ113yrhsoYyrZ1ExQlU9cY
cPX/6Rui2yehQuxZ63icZSw=
=qwH8
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#923640: "ifupdown" 0.8.35 breaks DHCP and DNS resolving.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: ifupdown
Version: 0.8.35
Severity: important

Since I upgraded "ifupdown" from 0.8.34 to 0.8.35, I cannot get an IP address 
from DHCP at boot.
Also, despite that I can still use "dhclient eth0" to get an IP, every domain 
fails to resolve.
(I can still "ping" an address to get an IP, but anything else ("apt update", 
web browsing etc) will not work).
The network in question is IPv4-only requires me to access a login page.
However, if I booted up System Rescue CD, login and "chroot", there is still no 
resolving inside chroot despite that the host has no problem.
I am not using a network manager because of Poetterware. I am using 
"sysvinit-core" and "sysv-rc".
I have read the changelog and I believe the DHCP problem is caused by the 
suggestion in #906894. No idea about the resolving problem.
___
Related configuration:

[/etc/network/interfaces]
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp

[/etc/resolv.conf (auto generated)]
nameserver 10.20.208.158
nameserver 208.67.222.222
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJce6BEAAoJENi1YDlFXXQfYy8H/ijl94JJTO7CTOLUeHGZ
dI+f1OVQFwTZ4RcSiZ/Piy0G13IetzizND1O1ONmZ2HTJUcguG6KIuWn0hIR
3BskniC+eVTaH0obLRBLkInGL/udVenr69JBXW1Xsbr1sx/squIqIOq9gzUF
jjkH5kKjQ7dABRPcGI31MSWXUjAup5KMGJCvaUedKrQYcDPIs4+/FqmPnClp
9MUZ9BHrgtCOJqpuprV6Pw0nkaWaCNhuInt13gwH0ETH0uEpx54C5U2fQe+i
PqXNsejLk93JhQQ71xMH+McBgipXkUO9bfVz7Y/VGYswUoKEyS9mHl6xQ5st
CfQyWCKsW6Von5KjasQ8NXI=
=ji5v
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#918327: ERROR #80 extracting when an ISO file contains non-english characters.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: wit
Version: 3.01a-2

It looks like that "wit" expects that everything is in English, and crashed 
when dealing with files that contain non-english entries.
===BEGIN OUTPUT===
pthfdr:/r/m/s/W/q>wit copy --fst test.iso Popn\ Music_\[R83EA4].wbfs/
*  wit: Wiimms ISO Tool v3.01a r0 x86_64 - Dirk Clemens - 2018-10-25  *
wit: EXTRACT 1/1 ISO:test.iso -> Popn Music_[R83EA4].wbfs/
!! wit: ERROR #80 [CAN'T CREATE FILE] in CreateFileFST() @ 
src/iso-interface.c#2987
!!  Can't create temp file: Popn 
Music_[R83EA4].wbfs/./files/g3ddemo/3ddemo/CutieLiveHouse/nw4reffect/t@C¼Íeffect_liveŨ袵ܷB
!! wit: ERROR #80 [CAN'T CREATE FILE] in CreateFileFST() @ 
src/iso-interface.c#2987
!!  Can't create temp file: Popn 
Music_[R83EA4].wbfs/./files/g3ddemo/3ddemo/SpecialDJClub/nw4reffect/t@C¼Íeffect_djŨ袵ܷB
!! wit: ERROR #80 [CAN'T CREATE FILE] in CreateFileFST() @ 
src/iso-interface.c#2987
!!  Can't create temp file: Popn 
Music_[R83EA4].wbfs/./files/g3ddemo/3ddemo/SweetsStage/nw4reffect/t@C¼Íeffect_sweetsŨ袵ܷB
!! wit: ERROR #80 [CAN'T CREATE FILE] in ExtractImage() @ src/lib-sf.c#3408
!!  3 files and/or directories not created.
===END OUTPUT===
--
"And in the naked light, I saw ten thousand people, maybe more. People \
talking without speaking, people hearing without listening. People writ\
ing songs that voices never shared, no one dared disturb the sound of s\
ilence." --MA Bo'yong
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcMErkAAoJENi1YDlFXXQfVpkIAJgJJz4Bcv0UiVYsOqq2
V4z7UkwCCFcsRc9ljEY/jaft8WdxIW4I0Zd38C4O3+By4zqZcWLXMjcmgSbG
QSnpNRIR2negr6X0y03klDsyVW9wC9kVXtS5107g8+LfEtVimcryH5G6CGer
jXjHc+ZdAxiWXMgALoAODc/XwVCGqOUPUHAXOEspJLhpjHsXEXCRYtUn9Tgp
tzRQbrfVfJ5ArQ3KbQoX+pP8mbOU8H3VoC2EHvGsc4lTN8ifDTOrlIqVENLM
tB87vjyZV0k+KhgpPjIEcV04uYPCLK4tKNWtpcA3twbKhDQlKOwktjiKHaJ/
GrxpOc49I2Q4ymJh3wnd43k=
=UPdi
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#918006: DVD-RAMs are always displayed as blank with `xorrecord`, even with data written.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: xorriso
Version: 1.5.0-1

It looks like that if I tries to query a DVD-RAM with `xorrecord`, it always 
shows that the disc is blank, despite that there is data on it.
It only happens with DVD-RAMs, other media do not have such problem.
===BEDIN OUTPUT===
pthfdr:/u/h/pthfdr>xorrecord dev=/dev/sr0 -inq
xorriso 1.5.0 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev '/dev/sr0'
Media current: DVD-RAM
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4368m free
Device type: Removable CD-ROM
Vendor_info: 'HL-DT-ST'
Identifikation : 'BD-RE BH40N'
Revision   : 'BD04'
pthfdr:/u/h/pthfdr>pmount /dev/sr0
pthfdr:/u/h/pthfdr>cd /media/sr0
pthfdr:/r/m/sr0>ls -Falis
total 1284
  306   2 dr-xr-xr-x  8 pthfdr users716 2011-02-24   ./
11145   0 drwxr-xr-x  4 root   root 120 01-02 16:06  ../
  310   2 dr-xr-xr-x  4 pthfdr users568 2011-02-24   boot/
  308   2 dr-xr-xr-x  9 pthfdr users724 2011-02-24   DS/
  312   2 dr-xr-xr-x  3 pthfdr users100 2011-02-24   efi/
  314  12 dr-xr-xr-x 13 pthfdr users  11504 2011-02-24   sources/
  321   2 dr-xr-xr-x  4 pthfdr users148 2011-02-24   support/
  323   2 dr-xr-xr-x  3 pthfdr users 92 2011-02-24   upgrade/
 2935 376 -r-xr-xr-x  1 pthfdr users 383562 2011-02-24   bootmgr*
 2936 654 -r-xr-xr-x  1 pthfdr users 667712 2011-02-24   bootmgr.efi*
 2933  16 -r-xr-xr-x  1 pthfdr users  16039 2011-02-24  'Release Notes.htm'*
 2937 106 -r-xr-xr-x  1 pthfdr users 107288 2011-02-24   setup.exe*
 2934 108 -r-xr-xr-x  1 pthfdr users 110440 2011-02-24  'Third Party 
Attribution Notices.rtf'*
pthfdr:/r/m/sr0>df -h
Filesystem  Size  Used Avail Use% Mounted on
tmpfs28G   32M   28G   1% /run
/dev/block/8:0  239G   20G  219G   9% /
/dev/sdc7.3T  3.8T  3.6T  52% /run/mount/sdc
/dev/sr03.4G  3.4G 0 100% /run/mount/sr0
===END OUTPUT===
--
"And in the naked light, I saw ten thousand people, maybe more. People \
talking without speaking, people hearing without listening. People writ\
ing songs that voices never shared, no one dared disturb the sound of s\
ilence." --MA Bo'yong
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcLHavAAoJENi1YDlFXXQfBm8IAKoZonA6Qf4qpuVNUmq3
dEq3LVVjSTEFm8sgmH3v+oLcBgK9rR9zGC3mSXztxVAyN0Mez9/2touGLGzv
+V/Ahbw9uhFsjbKClm5odZFU8EjTr4/ywTR7wEEuoYOJDepTDkMsxot6+avG
2op5UZs+VLTejIYeVUQplsKNM5UTftsNX/Mwve7UUQVrJrshfDGnU1vfWA/n
1vMeSAhoLe6p4YA4IdaDKCQJxgQUB+j/0MRBfU7x30957kTU3diAsTVpo1Ob
vMAdRb+PFKMpwL05Nt6X7hmBo5Gg0aVLurskJlyLW1zDtYN+faNb/kTrjDz8
slxUBHhsBxhHalUyUkHMi+Q=
=9WtE
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#901289: Additional information.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Original submitter here.
The problem is that do we really need "logsave"? It is a binary program.
I think that you can store the "fsck" logs in "/dev/kmsg" so the output\
 is stored in the "dmesg" logs. It is a system event, after all.
--
"And in the naked light, I saw ten thousand people, maybe more. People \
talking without speaking, people hearing without listening. People writ\
ing songs that voices never shared, no one dared disturb the sound of s\
ilence." --MA Bo'yong
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcJPWRAAoJENi1YDlFXXQf6XUH/RwumHhRE7qaY9vJuO2r
kJvwjBDXsxlkLFpCp2iRrUT2WgsXDu4sIEaa76KF9KbkwC9oAwjSLiJB5GB3
MYCHlx3slyD+Ilyn9kQZDzJmOfkb2k33UT/GsxHEE+vDTXO5G60Q0NWl4xPX
dnv1cUpwr0W/4l0y61zq5REVzSLtkn0DLh3aMjS7sE4pnqZlW8pZvdNBTX/k
pqidMKFTuTah0KBqZmrJkYIldZdjgojexJu9lbN4cs4/9Rpk3vdssEQY22P4
4j6YKmvSLSf0m2Bk+fCkC92GiABQSMTmK+S8t+7Qe9iVwEZ8fsbYdZvWj6u/
/TCOi1ASSI49J+fkTDt+C34=
=MDHm
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#917272: Kernel module failed to load on 4.19 kernel.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: firmware-amd-graphics
Version: 20180825+dfsg-1

For some reason, from 4.19.0 onward, the kernel refuses to load the AMD 
modules. The screen defaults to 80*25 text mode and "startx" does not work.
Here is what I have tried:
linux-image-4.19.0-trunk-amd64-unsigned/now 4.19.5-1~exp1 amd64: WORKS
linux-image-4.19.0-1-amd64-unsigned/unstable 4.19.12-1 amd64: DOES NOT WORK
linux-image-4.20.0-trunk-amd64-unsigned/experimental 4.20-1~exp1 amd64: DOES 
NOT WORK ("dmesg" log attached)
It does not look like the kernel itself is the problem (as 4.19-trunk works but 
4.19 does not), so the problem is the firmware.
--
"And in the naked light, I saw ten thousand people, maybe more. People \
talking without speaking, people hearing without listening. People writ\
ing songs that voices never shared, no one dared disturb the sound of s\
ilence." --MA Bo'yong
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcIg5HAAoJENi1YDlFXXQfqRAH/3NGXqLXLCWWOEAkRkHn
RXCYbILbBYqY9G1PTadc4ycce828Z9uwRytKkQ3C7rvulIjcYA6SD5Zv7Yl6
g9yhb0+ZW6gedIV86bGvQpwgY2NWyvDtm1FL+GUrEcrNMT9qJD1W4uQ2s+P9
YZCdEWcvBaj/mYuqLzHG9yA/2Kfv7BFjULbhq3+PDfBKiOGZdG3ufHd6NEP5
m7QN/PXV2F6K6BPQ/uGragb0/QHFUE6pyeCynh4rbDixMwe5Fb2mfRcDNTDg
J8GUH8J0CkLaqADVZK6zzrDiAy+MqlVK3zTSx3EBK6bDc8S9CNOgvXt34XRh
KwceEhcEsZpqKguUw3qlsQg=
=cy56
-END PGP SIGNATURE-



dmesg.0
Description: Binary data


dmesg.0.sig
Description: PGP signature


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#917139: Additional information.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

>You want to say, that "pmount" and "udisks" are fine with /media point\
ing to nowhere?
"/mnt" and "/media" are for manual mounts (by using "pmount $DEVICE", "\
udisksctl mount -b $DEVICE" or using GUI buttons to do the same thing) \
with USB disks, NTFS volumes from Windows and such. System volumes are \
mounted through "/etc/fstab".

>some other filesystems, mounted under /run, that should be ignored in \
`umountfs'?
None except "/run/shm" and "/run/lock". Most other programs do not use \
mount points under "/run". There are still some programs doing this, li\
ke "fstransform".
I think that there is another solution: Checking whether there are bloc\
k devices mounting in "/run". If it is a "tmpfs", it is safe to ignore;\
 if it is a block device, it is not safe to do so.
--
"And in the naked light, I saw ten thousand people, maybe more. People \
talking without speaking, people hearing without listening. People writ\
ing songs that voices never shared, no one dared disturb the sound of s\
ilence." --MA Bo'yong
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcIb9lAAoJENi1YDlFXXQfWTAH/3cnUT+h/y8WBsqL1RJR
YkAPIr+45qF+cL3hwuRQQ6DjS3T367ydGCRRQC3FkXNeld7R8M5NfR++JKUM
O0ruRGPyesyFtlLkkcc7K0GWue9EAw6DftILUHGL/UBv+aqsG02KYBsx8g3h
a90CSXhbpTaWOVHiSu2+8I5p91+GsuyW1BNerfV2//0i06KG/I6P6RqoORZn
zqOTI0cOTB/z1CueWQGwFvQaoNHCG6MUGCzJ2YJOLcFozlEj+gf8lvIZ0kXF
90UH7MliYdt59Ol1IMJdn+/XNqHXdTUgDQhGBGNYVCcl5GaOd2M8hRNEv47J
kbiCYke9ro4++eJNDgcUmLQ=
=vHSf
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#917139: Do not ignore unmounting of "/run/mount" and "/run/media" in "/etc/init.d/umountfs"

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: initscripts
Version: 2.93-1

In "/etc/init.d/umountfs" line 28, everything under "/run/*" is not unmounted 
when shutting down or rebooting the system, and this includes "/run/mount" and 
"/run/media".
Also it is not uncommon to symlink "/media" and "/mnt" to said locations as it 
does not leave automatically created folders after a reboot.
So if you mount disks as a normal user using "pmount" or "udisks", they are not 
unmounted, resulting in data loss.
I suggest you that you should only ignore "/run/lock" and "/run/shm" (if exist, 
as specified in "/etc/default/tmpfs").
--
"And in the naked light, I saw ten thousand people, maybe m\
ore. People talking without speaking, people hearing withou\
t listening. People writing songs that voices never shared,\
no one dared disturb the sound of silence."
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcHzqrAAoJENi1YDlFXXQfdgcH/01UoNuzuAwlVfPYq8Jc
qrhT0cKZQBd+jJhFwRkDRBBP35ks/UG6wrkHiqDdk/qUF0GJfpBeYlm6P8lx
n1Xxsh9KnhJ5b5X/ojsL6dzOvd5BYgXpaTeryd5sX/OOkUCTDM55M+wWQY/6
N22T9w1icOdQJD5O0GulxiT1ljPWVnQj41wlue+Oa9d6mp7tfmqgj8+bZoyQ
NxkflalH0QulY+Sq+LUE3KS/6PQD3CwHCDNYQXyZ1UZDJ78b/vOotF14j/3E
AIhSHKBMUm5SGEgbVQtpD17X6TDQMOPXzq7iAa5L8HHkshN2X9CbQvVpMlVS
O5y3gGCs51o7RqiyUKXi/kY=
=Tk6/
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#915094: Additional information.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

>Is this true even if you reboot?
The problem does not happen at boot. It happens randomly after you have 4-5 
days of uptime, especially with long, CPU-heavy processes already running (like 
ZPAQ compression).
I still do not know the exact cause, but it happens only with new processes, as 
soon as it starts. Existing processes are not affected.
>What if you force an fsck check on the file system?
I have not tested it, but I do not want to take the risk of checking a running 
system.
I reformatted the FS without that feature, and it does not seem to happen after 
a week. Maybe the problem is within the EXTFS driver?
--
"And in the naked light, I saw ten thousand people, maybe m\
ore. People talking without speaking, people hearing withou\
t listening. People writing songs that voices never shared,\
no one dared disturb the sound of silence."
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJcEQIWCRDYtWA5RV10HwAAR3sH/1qqatN9KerwnfLm82zr
mcZJdDdInoFoyPcUIE7uFiInmT6e5k+nVo5pxVY9+2FamLFpVE3MoChUon0z
JHywMUeC8rvmZMnHq1JH0Z9RSdRvv430w/OdcqDBa71Bm4XQMn3eVMQcTLCo
1m8E8PvO++4ZB1YC1h0FzCnp92qeLoG1nUu1CYf7Gcdx1rDeOVytnpcJV9tO
hkN7Stlf9QMxjthql/fkRTe34D0VO4kiE6yMQJzW7RLiwfa0siM13yTEk+OS
vQsl2UXj8Q80a/MrAlk/uV9mCWEShufwZyk78tY98t+PMwiow8MXTPdbEWE5
Xso0RgTFTUyzB4d2BoawKgY=
=EGHR
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#915945: Feature request: determine the filesystem using "file" instead of trying one by one.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: pmount
Version: 0.9.99-alpha-1
Severity: wishlist

You can determine the type of filesystems by probing the superblock using "file 
-s". For example:
===BEGIN OUTPUT===
pthfdr:/u/h/pthfdr>file -s /dev/sd*
/dev/sda:  DOS/MBR boot sector, LInux i386 boot LOader
/dev/sdb:  DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 
"Invalid partition table" at offset 0x17b "Error loading operating system" at 
offset 0x19a "Missing operating system", disk signature 0x512bd3a9; partition 1 
: ID=0x7, active, start-CHS (0x0,32,33), end-CHS (0x11,80,63), startsector 1, 
234441647 sectors
/dev/sdb1: DOS/MBR boot sector, code offset 0x52+2, OEM-ID "NTFS", 
sectors/cluster 8, Media descriptor 0xf8, sectors/track 63, heads 255, hidden 
sectors 1, dos < 4.0 BootSector (0x80), FAT (1Y bit by descriptor); NTFS, 
sectors/track 63, sectors 234441646, $MFT start cluster 786432, $MFTMirror 
start cluster 2, bytes/RecordSegment 2^(-1*246), clusters/index block 1, serial 
number 0a05667ac566781c0; containsMicrosoft Windows XP/VISTA bootloader BOOTMGR
/dev/sdc:  Linux rev 1.0 ext4 filesystem data, 
UUID=afb8ef7a-29bc-42fa-8d6b-970f5d91f45a, volume name "ARCHIVE" (needs journal 
recovery) (extents) (large files) (huge files)
/dev/sdd:  empty
/dev/sde:  empty
/dev/sdf:  empty
/dev/sdg:  DOS/MBR boot sector, code offset 0x58+2, OEM-ID "mkfs.fat", 
sectors/cluster 128, reserved sectors 2, FAT  1, sectors/track 32, heads 64, 
sectors 62333952 (volumes > 32 MB), FAT (32 bit), sectors/FAT 3805, serial 
number 0x779542a7, label: "SDUT   "
===END OUTPUT===
This command works with normal users, so you do not need to try to guess which 
FS the disk in question is using.
--
"And in the naked light, I saw ten thousand people, maybe m\
ore. People talking without speaking, people hearing withou\
t listening. People writing songs that voices never shared,\
no one dared disturb the sound of silence."
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJcC0qyCRDYtWA5RV10HwAAqvAIAKFJueQias6Qj1iKo4p5
zw50NTiFxcvNsFvsV2DMZadCF4PfoRWqgyXbTpPC+Z0nHppRkaE7y3As4opY
JwLshvKZDZuzB1kU6ms/UApfT96CTuXLo4CcjXi5Rj+Ry6Npw3Bgs+oK0fZf
Z9yWUIUW4Tqd9OGTCK89trfcUeX+6icpNn6fQYo0+UzRj1v444pp5YqjfpJb
1zBb1Mvc9sK+qbmR8l7h9VoVKoR2MsCSNYCqtduVVQYRWp2izJ4TsRxaBYLz
7tIs488jGKHNyXdgfI+7ez8JRYqyJ8O0I01oy4XlRSPHWjLBM+2dPf8Gz7Qc
7fBqZ+hSVpdHep4gvpG9zmE=
=2UiG
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#915094: Additional information.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

>Can you tell what version of the kernel you are using?
4.19.0-trunk-amd64. I guess that I am not getting any semblance of support with 
an experimental kernel.
However, when I upgrade from 4.19.0-rc7 to 4.19.0-trunk, the problem is still 
there, so it does not look like a kernel problem.
>How/when did you enable this feature?
Just me poking around options in the man page. I assume that I can save some 
space with small files.
>It looks like you were trying to upgrade some packages when you ran into this 
>issue.
It happened to random processes. It happened to "mandb", "perl" and "chromium" 
most frequently. Sometimes it happens to very basic processes like "ls" or "rm" 
(happened once when I try to remove Chromium's cache folder).
Also, if a process is stuck, the processes will be stuck again if I invoke that 
program again.
--
"And in the naked light, I saw ten thousand people, maybe m\
ore. People talking without speaking, people hearing withou\
t listening. People writing songs that voices never shared,\
no one dared disturb the sound of silence."
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJcAdSQCRDYtWA5RV10HwAAi6QH/0wsTVCyYWSHzeegbkiz
pKLva43dlXwvd62AbB2CYyzSdytUacGyvk4LOSvAg9FtD0PsK1eayTJ3cQgV
VyIUc7zCLgWA9HXm36HiUoi8hTlkeqa+8Vy/AG0X4pTVIaZPLPyGiUu3yQyM
PCyfGTv9so26v244RQ+FJNQVYdOtE6ajM//570HXHTmb4/GykmHMGIk1iwIH
YDQa+4FlZFNPDo+Gi3Az2IKj+hDYQyZ+spJTs53GWuwu3W02lH3bno2HXYNJ
ciP+jo+l/PIj+8zqIUL4ddUOrBWglj+fJGAVN3YVxs+iKz3VD+IFOFv29eHw
t1NgJ3BV02yAjQNWWo+eOdQ=
=HkKt
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#915094: Processes stuck in "D" state with inline_data feature enabled.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: e2fsprogs
Version: 1.44.4-2

>From time to time, some processes get stuck and I cannot kill them. Even 
>SIGKILL does not work. The only way is to reboot (which I usually cannot 
>afford because I have ZPAQ compression processes that last days).
When I view them in "htop", they are in "D" state, with the wait channel being 
"call_rwsem_down_read_failed".
Like this: https://i.ibb.co/Ry86CJ2/2018-11-28-110558-1600x1200-scrot.png
It happens randomly, and "dmesg" does not show anything unusual, no hardware 
problems, no NFS involved.
I tried to trace the problem with SysRq+W:
===BEGIN OUTPUT===
[40732.001687] sysrq: SysRq : Show Blocked State
[40732.001691]   taskPC stack   pid father
[40732.001751] dpkg-preconfigu D0 19836  1 0x0004
[40732.001753] Call Trace:
[40732.001760]  ? __schedule+0x2a2/0x870
[40732.001761]  schedule+0x28/0x80
[40732.001763]  rwsem_down_read_failed+0x10f/0x180
[40732.001765]  call_rwsem_down_read_failed+0x14/0x30
[40732.001767]  down_read+0x1c/0x30
[40732.001783]  ext4_find_inline_entry+0x4c/0x160 [ext4]
[40732.001794]  ext4_find_entry+0x47f/0x540 [ext4]
[40732.001798]  ? d_alloc_parallel+0x99/0x4a0
[40732.001806]  ext4_lookup+0x6f/0x200 [ext4]
[40732.001809]  __lookup_slow+0x97/0x150
[40732.001810]  lookup_slow+0x35/0x50
[40732.001811]  walk_component+0x1bf/0x4a0
[40732.001813]  path_lookupat.isra.48+0x6d/0x220
[40732.001815]  filename_lookup.part.62+0xa0/0x170
[40732.001817]  ? __check_object_size+0xa3/0x181
[40732.001819]  ? strncpy_from_user+0x4a/0x170
[40732.001821]  vfs_statx+0x73/0xe0
[40732.001822]  __do_sys_newstat+0x39/0x70
[40732.001824]  ? handle_mm_fault+0xda/0x200
[40732.001826]  ? __do_page_fault+0x26c/0x4f0
[40732.001828]  do_syscall_64+0x53/0x100
[40732.001830]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[40732.001831] RIP: 0033:0x7fa7bb720dd5
[40732.001834] Code: Bad RIP value.
[40732.001834] RSP: 002b:7ffd327671a8 EFLAGS: 0246 ORIG_RAX: 
0004
[40732.001836] RAX: ffda RBX: 558e2745e260 RCX: 7fa7bb720dd5
[40732.001836] RDX: 558e2745e478 RSI: 558e2745e478 RDI: 558e277a3430
[40732.001836] RBP: 558e278a4ae0 R08:  R09: 0033
[40732.001837] R10:  R11: 0246 R12: 
[40732.001837] R13: 558e266f1198 R14: 558e277a3430 R15: 558e276ae340
===END OUTPUT===
I am no programmer, but since it shows "ext4" and "inline", I think there is a 
problem with EXT4, especially with its "inline_data" feature.
This is my current configuration using "tune2fs -l":
===BEGIN OUTPUT===
tune2fs 1.44.4 (18-Aug-2018)
Filesystem volume name:   DEBIAN
Last mounted on:  /root
Filesystem UUID:  c5971091-77d2-40fe-9095-54bb0ff96a2c
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr dir_index sparse_super2 
needs_recovery extent flex_bg inline_data large_file uninit_bg
Filesystem flags: signed_directory_hash
Default mount options:discard
Filesystem state: clean
Errors behavior:  Remount read-only
Filesystem OS type:   Linux
Inode count:  228960
Block count:  117220824
Reserved block count: 0
Free blocks:  102491793
Free inodes:  107444
First block:  1
Block size:   1024
Fragment size:1024
Blocks per group: 8192
Fragments per group:  8192
Inodes per group: 16
Inode blocks per group:   4
Flex block group size:16
Filesystem created:   Wed Oct 17 19:58:28 2018
Last mount time:  Fri Nov 30 08:32:36 2018
Last write time:  Fri Nov 30 08:32:36 2018
Mount count:  9
Maximum mount count:  -1
Last checked: Wed Nov 28 17:01:44 2018
Check interval:   0 ()
Lifetime writes:  437 GB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 32
Desired extra isize:  32
Journal inode:8
First orphan inode:   168961
Default directory hash:   tea
Directory Hash Seed:  a4bd0a95-469a-48ff-8d9e-c1a3e4674ec8
Journal backup:   inode blocks
===END OUTPUT===
--
"And in the naked light, I saw ten thousand people, maybe m\
ore. People talking without speaking, people hearing withou\
t listening. People writing songs that voices never shared,\
no one dared disturb the sound of silence."

-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJcASmeCRDYtWA5RV10HwAAte4H/ixkZtYgCuWCfyCg9Mdf
VDKnvNSxCjsSZ23fA1BxEuf2DkBHCyvHMw9qIAugO0jlkePeWLwJdR15jF93
Tbf9o5fT8+BHtnyEfXi2uK1BnOAOlIsR21SHc/r4qgXQLBd0AftCWbfxHNIP
2t+2mRzhj2TjUjT9vjg9NlnOVU2HkdmaCOrSYwfbb1WmP/oeLybFd/pstU46
CuWS8twRwIBxZUw/UzhXHP5YT+F4gCO+rIzhvzziiJwhpI+G8Y18/bcWBw6l

Bug#913540: "crypto: stream: repeat IV detected" after upgrading to newest version.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: shadowsocks-libev
Version: 3.2.1+ds-1

After upgrading to the latest version, any connection attempts through the 
proxy would be closed with:
 2018-11-12 09:46:44 ERROR: invalid password or cipher
 2018-11-12 09:46:45 ERROR: crypto: stream: repeat IV detected
despite the passwords are correct.
If I downgrade to the previous version (3.2.0+ds-5) it works as normal.
Config files "/etc/shadowsocks-libev/config.json:
{
"server":[REDACTED],
"server_port":[REDACTED],
"local_port":1080,
"password":[REDACTED],
"timeout":4,
"method":"aes-256-cfb"
}
*END OF MESSAGE
Please reply to this e-mail with UTF8-encoded plain text.
You are as malicious as any other spammer if you send HTML e-mails.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJb6N2zCRDYtWA5RV10HwAA/yQH/3dQpbCxPuPvP3QFj6qe
WryeRhjdtWzLZAj4Yw5KmHbC8yNQbUnXJAn5YvCO6CR5PPNQVCTwwspph/9G
J4mAcMqVFaVHK4GQgXip145B+xl4DMqVhDRn04Z29C7qorlcLXf7q5Aifqbk
GexIA6H5B/SoJgn7zYRRFe99QpbrLauEbYKoInE91B+nyq+LmQKbcstxFcjv
eVr2ZvfPqGy3PqSrOeqhWUrWGS/6MrpIab3mwXAxsL0jwn/fu5bO5xpo2s8z
YhFH2BgSOcLYd9fkN38OGbKYPC7F90FDWrVOWIxEOvcNk4CMUr4YQSPTl0az
70/1dM/e7XtJmZ0JAkQtgxs=
=lBqy
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#912824: [Pkg-alsa-devel] Bug#912824: Distorted sound with some headphones.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

No, the connection is not loose.
It looks like that this issue only happens on "Apple" earphones (as well as the 
"Apple mode" on some earphones). There is a button on the earphone, and if I 
hold down the button, there is no problem playing. But I cannot hold it forever.
The distortion problem is Linux-exclusive. I do not know the course. All music 
files have this problem but not very noticable. It becomes noticable with 
speech. Holding the button solves the problem.
The "wrong channel" problem exists in Windows too, but not in devices such as 
an Android phone or a Nintendo 3DS. Again, holding the button down solves the 
problem.
Maybe it is related to this: 
https://mashtips.com/apple-headphone-on-android-or-windows/
Apple has its own implementation of TRRS and I guess the button disables the 
mic and other "special features".
So it is a hardware problem after all. But I hope you to provide some sort of 
software workaround.
---END OF MESSAGE---
Please reply to this e-mail with UTF8-encoded plain text.
You are as malicious as any other spammer if you send HTML e-mails.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJb3uvxCRDYtWA5RV10HwAAvpMIAIJ3ZecALDRou1EvfETp
iPdap8DWTfJfjPso9OAEcTQom8H8uTxsFTGSV6VN5LV3Z0gQ2nrk5XkowyCT
h8do4ISHR2pcMvnsSh6XTw31smIaH57sL4jIcha/Mw6lLtBJCedfL1P5vm8q
Iszr0M++crl5b2ATFg2VsMRebIQvzlEBtS2P5XYyTwajd8PrA4ZiEgAGE6lH
W37DjALf6NfQzJL58RNdfiWIhW0WDr3zV0mX7ca7bzJ9ymc7gURvlkx90hnk
K7v6EgPl/WK5GyXOkXQg87HT1XyUhddp9K5cYXdMUx3u/ir3heZMtNpjarIi
g1i28TPN2DTzAmQ1Dxiu19I=
=awp7
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#912824: [Pkg-alsa-devel] Bug#912824: Distorted sound with some headphones.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

No, I am not talking about clipping. The problem happens regardless of volume.
If I run "speaker-test -c2", both speakers have sound output at the same time 
(which should not happen).
The "constantly swapping" does not always happen-it happens at random, and only 
on some of my audio files. I do not know what caused it.
Some observations when I adjust the volume in "alsamixer" and run "speaker-test 
-c2" (it seems that the swapping problem does not happen):
L=0, R>0: Both have constant sound on "Front Left", Both have no sound on 
"Front Right". (No, this is not a typo)
L>0, R=0: Both have no sound on "Front Left", Both have constant sound on 
"Front Right".
L>0, R>0, L>R: Both have constant weak sound on "Front Left", Both have 
constant strong sound on "Front Right".
---END OF MESSAGE---
Please reply to this e-mail with UTF8-encoded plain text.
You are as malicious as any other spammer if you send HTML e-mails.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJb3sgaCRDYtWA5RV10HwAAWpUIAKrzd1zNwmkdl680zuXb
OtTIpBrIIoNUSzenkVVJcRFf+uWXCH4yZ/4rDwGBbDOAOfseaI8eoYzhgeHE
hCfddLldkk1SFl4ojBKvnRAy4nAg06NJdtM6yWIHpwICx7pf2ojzvnIdxR9S
ffWl1AqsqtvUdK9qRxiWhQdgfYLOskp7KyWsRXdR265EMDzV5NlchAoJdYfH
6IWEazg9GnnW3l+V8NNJl6m3JM/y0+0g32vFt0t3sO1DahGl4+hcfWfkwKwE
BD0faaoOG6dajgHUwMr25B8JyJ5v6m7q8YRy49gQIhXa0XJ+3pnrKWgN0uHo
huNQuepxAb5X2tS2kA5DJuo=
=XrvL
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#912824: Distorted sound with some headphones.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: alsa-utils
Version: 1.1.7-1

With some headphones and earphones, the sound output is distorted, e.g. the 
left and right channels are swapping constantly, this issue is especially 
serious with human speech.
I used a Sony MDR-AS800AP earphone directly inserted to the sound card's audio 
output, the sound is distorted. However, if I hold the button on the earphone 
the output is normal but at a higher volume.
I can confirm that the earphone and the sound card have no problem because it 
plays normally on an Android smartphone or on dual-booted Windows. The problem 
is certainly in ALSA.
I also tested with other earphones, some of them have similar problems. Some 
earphones have an "Android/Apple" switch, and the distortion happens when the 
switch is set to "Apple".
I am using ALSA directly without PulseAudio or other Poetterware.
The configuration can be found in the attachment.
---END OF MESSAGE---
Please reply to this e-mail with UTF8-encoded plain text.
You are as malicious as any other spammer if you send HTML e-mails.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJb3obdCRDYtWA5RV10HwAAtL4H/0ce5qAoOs+omS4MpRGE
f+e66Gcxrug9558YBATVdB4RoF82VnaWMQPjrh2xh6OffTZoal3OuFa4S2cO
0QLsiv5Hc1qBIvJ26R49nMdsKD2jUP+cFBXKKloUHTDosy1KEGyQUWcPJ7HP
25nDnh50uhOrz5B+TAI3K9WFnXCvDpplLmR17idf4UoVYjDn6nS1eH2b7Tl0
BStP2lr4Le8lvdhySuwmcS5h9X6faKG9VKindMQDNskktYCYvgbedVk9V+RT
9xf3ynfBTILeYwaMNwba23uD3Ji2djBPvxlAGB+gla075epBfh7O014z8DjW
WsM6jsIDPY26C56lM1VSC0M=
=aME2
-END PGP SIGNATURE-



alsa-info.txt.m3tnKxZsxA
Description: Binary data


alsa-info.txt.m3tnKxZsxA.sig
Description: PGP signature


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#912308: "-o" mount options in "tune2fs" is not being honoured by the OS.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: e2fsprogs
Version: 1.44.4-2

The mount options set in "e2fsprogs" are not being used by the OS, regardless 
whether there are corresponding entries in "/etc/fstab".
Here is my example:
===BEGIN OUTPUT===
root@AVENTHEIM:/u/h/root>tune2fs -l /dev/sda
tune2fs 1.44.4 (18-Aug-2018)
Filesystem volume name:   DEBIAN
Last mounted on:  /root
Filesystem UUID:  c5971091-77d2-40fe-9095-54bb0ff96a2c
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr dir_index sparse_super2 
needs_recovery extent flex_bg inline_data large_file uninit_bg
Filesystem flags: signed_directory_hash
Default mount options:discard
Filesystem state: clean
Errors behavior:  Remount read-only
Filesystem OS type:   Linux
Inode count:  228960
Block count:  117220824
Reserved block count: 0
Free blocks:  107372244
Free inodes:  130667
First block:  1
Block size:   1024
Fragment size:1024
Blocks per group: 8192
Fragments per group:  8192
Inodes per group: 16
Inode blocks per group:   4
Flex block group size:16
Filesystem created:   Wed Oct 17 19:58:28 2018
Last mount time:  Tue Oct 30 08:04:00 2018
Last write time:  Tue Oct 30 08:04:00 2018
Mount count:  3
Maximum mount count:  -1
Last checked: Mon Oct 29 08:13:17 2018
Check interval:   0 ()
Lifetime writes:  267 GB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 32
Desired extra isize:  32
Journal inode:8
First orphan inode:   163356
Default directory hash:   legacy
Directory Hash Seed:  a4bd0a95-469a-48ff-8d9e-c1a3e4674ec8
Journal backup:   inode blocks
root@AVENTHEIM:/u/h/root>mount |grep /dev/sda
/dev/sda on / type ext4 (rw,relatime,lazytime)
root@AVENTHEIM:/u/h/root>cat /etc/fstab
/dev/block/8:0 / ext4 lazytime 0 1
===END OUTPUT===
Note that "discard" is not in the mount parameters despite that I have set it 
in "tune2fs".
(It is an SSD and it supports TRIM. And yes, I do not partition it.)
Another example:
===BEGIN OUTPUT===
root@AVENTHEIM:/u/h/root>tune2fs -l /dev/sdc
tune2fs 1.44.4 (18-Aug-2018)
Filesystem volume name:   USERDATA
Last mounted on:  /run/mount/sdc
Filesystem UUID:  afb8ef7a-29bc-42fa-8d6b-970f5d91f45a
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal dir_index sparse_super2 needs_recovery 
extent flex_bg large_file uninit_bg
Filesystem flags: signed_directory_hash
Default mount options:bsdgroups uid16
Filesystem state: clean
Errors behavior:  Remount read-only
Filesystem OS type:   Linux
Inode count:  1907744
Block count:  1953506646
Reserved block count: 0
Free blocks:  1768323885
Free inodes:  1905162
First block:  0
Block size:   4096
Fragment size:4096
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 32
Inode blocks per group:   1
Flex block group size:16
Filesystem created:   Wed Oct 17 21:07:45 2018
Last mount time:  Tue Oct 30 08:04:37 2018
Last write time:  Tue Oct 30 08:04:37 2018
Mount count:  3
Maximum mount count:  -1
Last checked: Mon Oct 29 08:13:35 2018
Check interval:   0 ()
Lifetime writes:  1551 GB
Reserved blocks uid:  65534 (user nobody)
Reserved blocks gid:  65534 (group nogroup)
First inode:  11
Inode size:   128
Journal inode:8
Default directory hash:   legacy
Directory Hash Seed:  b99b9c29-ee43-423e-b4bd-0321c1f7d12a
Journal backup:   inode blocks
root@AVENTHEIM:/u/h/root>mount |grep /dev/sdc
/dev/sdc on /run/mount/sdc type ext4 
(rw,nosuid,nodev,relatime,resuid=65534,resgid=65534,user)
===END OUTPUT===
Again, the default options are not being honoured. I mounted it using "pmount 
-e" but it should not affect options like "bsdgroups" and "uid16". Also, it is 
not in "/etc/fstab".
--
Please reply to this e-mail with UTF8-encoded plain text.
You are as malicious as any other spammer if you send HTML e-mails.

-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJb19LBCRDYtWA5RV10HwAAhccIALRLrZ/EglI5VSThTNSP
yGnd/95GV5gOMEFhTW1kcKp1zReC06Ja6IFzBWQrMZsksl9dpseFEZqUjvcn
J+/h5lGLNPTjO7D4Aujqpyh+qxKq9UIfSnBAeSDaojT9i8nl5vGHfs/rRWhf
adML2703nJQjuNgLP/SThuQJQqAOk3vXCLhlp7whA1zH57h5yIO99QuUMRKT
T2P04ZhhIf/2ljJng0DJ73nPtW0gunIJcmoHLUEjMIQv7SigEzVg1TZt8qQm
In08fCK289CG6Dde1lNRQjqqcC+Kj3Og1KtXCC08ekBsuoSedrvvztqyrHKv
eZF1VFoqeci3uKq0K0fW22k=
=uB8a
-END PGP SIGNATURE-

Bug#910846: User error.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Using "glamor" instead of "EXA" works. However, the manpage says "EXA (for 
pre-TAHITI GPUs) and glamor (for R300 or higher)". TURKS GPUs are pre-TAHITI 
ones.
I cannot test the patch for you. I have said, I am no developer, and I do not 
want to mess up my OS by recompiling an important package.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJbxLbBCRDYtWA5RV10HwAACdAH/2yVrvePAd0gZ6G0ADyT
41e9Mg54bqW7L00fIzZCcWpCHW5Ux4EUeg2OzbJGxfM/z4ItT/0KqQ1A0lPk
ky/zGQffQzyn1uxg419ktO/vgeg4XVt/uXjc657NISkFh6NeOG+81zEaEo2r
zVQqAPmzGvrBmPPE0/VdJhyzQ4F3tUNxHGVOu47S9X2QNeu5Matu8U4q0s6U
SgrlTu35a1W0gQSIHlFBETuVSKJv9iGqU15vVTRplZq7TejL/eVy5HinrFjM
i2BovG0F5VQUGyb/PO3M8Eh/9l5R7SCo1Asd15A0Bt1oUSL7TUPCf2H/tDEm
XyKDAAd1DexafdQ9H03bgHI=
=KSv9
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#910846: User error.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Sorry, I have found the problem. If I remove this line from 
"/etc/X11/xorg.conf", X would not crash:
Option "DRI" "3"
So it is my fault. Sorry.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJbxH1vCRDYtWA5RV10HwAAX08H/29y/7iN69E57QmCJrjy
RU1nHqfOxgggoi7be9N+9i8zbiQzhyFN4FnWpasWkJr8yGibYwNLKyXmtTw+
qtNToX2WE3mYJ+8v4/nnEUQCVWcvjbJ2vwI2IbBNbOomZo1H6b8CJ50RvkGm
lazo024twWAx/ZjCysztfaT8EzUke2+eWEAEJoSZf7xKitCr8I27mTcUIlZx
Z2hhSB48GGR3LJ+OHE7nFmZqP/GpLXeuVVYQSfeHQp2WKs5sDsPpXLcjEpFD
BojmrHH4Cqx6MTv+3ZG3Zkzj7ka1u+lMhIze+6wSThWRRijJB2k2FO7aNRnx
fIR2P6am19I8Ck/cVMCSd/8=
=/ahJ
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#910846: Here is the result.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Here is the output of GDB.
I am no developer, thus I do not know whether this is what you want.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJbxHuOCRDYtWA5RV10HwAAh3oH/Avj5UFSkRC9/ycaJQY8
Ib64nAdpzHcDhSQnR2wV2/ui4QNCpp+Vlh9Qd+AVKUhlBQiknePZQOqJovEU
r+r7FVN3NfNooKililvDMJIFD3YY54DfACdvqySbQmggyuuyi4FYUStfCULD
eseUYWwTS5vmSS/2Lyma8JFTqIx2DgcCPThmwYypM08bv7wX52PiPPiWBp2W
zcD4G098izvz2AMy5DkVwD8aRNXUVuJTRUkmGuTpQ8nio1ruv8nK7+s8JlXK
m+ZicUlR3MujdYsHvktLjdbuOh4mBsbYyCH39Sr5JuHpQA6/t5Auq/Y+B3/n
XKkGfY4tcZ+rMwVLgEgTsOQ=
=WL0I
-END PGP SIGNATURE-

GNU gdb (Debian 8.1.90-1+b1) 8.1.90
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/xorg/Xorg...Reading symbols from /usr/lib/debug/.build-id/92/cbd96948ba614f538b64667017f2b323ab4386.debug...done.
done.
[?1h=(gdb) attach 2784
(gdb) attach 2784
(gdb) attach 2784
[?1l>Attaching to program: /usr/lib/xorg/Xorg, process 2784
[New LWP 2785]
[New LWP 2790]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fb3b6f91207 in epoll_wait () from /lib/x86_64-linux-gnu/libc.so.6
[?1h=[?1l>[?1h=(gdb) cont
[?1l>Continuing.

Thread 1 "Xorg" received signal SIGSEGV, Segmentation fault.
0x7fb3b5c0b592 in radeon_dri3_fd_from_pixmap (screen=, pixmap=0x555d942d75b0, stride=0x7ffd70bcd570, size=0x7ffd70bcd568)
   from /usr/lib/xorg/modules/drivers/radeon_drv.so
[?1h=[?1l>[?1h=(gdb) 
(gdb) 
(gdb) backtrace full
[?1l>#0  0x7fb3b5c0b592 in radeon_dri3_fd_from_pixmap (screen=, pixmap=0x555d942d75b0, stride=0x7ffd70bcd570, 
size=0x7ffd70bcd568) from /usr/lib/xorg/modules/drivers/radeon_drv.so
bo = 
fd = 32765
scrn = 
info = 
screen = 
fd = 
scrn = 
info = 
size = 0x7ffd70bcd568
stride = 0x7ffd70bcd570
pixmap = 0x555d942d75b0
bo = 
bo = 
fd = 
scrn = 
info = 
#1  0x555d9277865d in dri3_fd_from_pixmap (pixmap=, stride=stride@entry=0x7ffd70bcd570, size=size@entry=0x7ffd70bcd568)
at ../../../../dri3/dri3_screen.c:134
screen = 
ds = 
info = 
strides = {0, 0, 2, 0}
offsets = {39, 0, 12583657, 2}
modifier = 93860376544726
fds = {-1808960080, 21853, -1808925696, 21853}
num_fds = 
#2  0x555d92777a2b in proc_dri3_buffer_from_pixmap (client=0x555d942dfc00) at ../../../../dri3/dri3_request.c:261
stuff = 
rep = {type = 1 '\001', nfd = 1 '\001', sequenceNumber = 9379, length = 0, size = 0, width = 16, height = 16, stride = 0, 
  depth = 24 '\030', bpp = 32 ' ', pad20 = 0, pad24 = 0, pad28 = 0}
rc = 0
fd = 
pixmap = 0x555d942d75b0
#3  0x555d9264a91e in Dispatch () at ../../../../dix/dispatch.c:478
result = 
client = 0x555d942dfc00
start_tick = 660
#4  0x555d9264e8c6 in dix_main (argc=8, argv=0x7ffd70bcd758, envp=) at ../../../../dix/main.c:276
i = 
alwaysCheckForInput = {0, 1}
#5  0x7fb3b6ebbb17 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#6  0x555d9263867a in _start () at ../../../../dri3/dri3_request.c:724
No symbol table info available.
[?1h=(gdb) [?1l>quit
[?1h=A debugging session is active.

	Inferior 1 [process 2784] will be detached.

Quit anyway? (y or n) y
[?1l>Detaching from program: /usr/lib/xorg/Xorg, process 2784
[Inferior 1 (process 2784) detached]


xorg_gdb.log.sig
Description: PGP signature


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#910846: No packages.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

There is no "xserver-xorg-video-radeon-dbgsym" or "xserver-xorg-core-dbgsym" in 
the repo.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJbwsu/CRDYtWA5RV10HwAAlBoH/31H3xlegMCUp4lFdulZ
cGqNjqkA4nljr2x4Jmrr00RzxWiLUcd7P96wogePu15NSHj5qEzLTiiWlIoX
0AFJO+zaoua02QiqS9TEZz8wET11f4J/3KhqvyX00QWCXk06CQP9N7aGtL15
SCJ7x0p2B1U/6F0LVdUBcPnOAv/WB0c1SkcYJSPHZII1dCIUelHVz4lakwAA
jerubxK0qIOS1YZTNHQiLAhlLhFuhY0NPbvD4+QnEKDFm/HgJ424mBHaZ7t+
KqdZ4olbLWrYFpEkDjbs2cdSywWWA3tKYCZwZc/2u8atllg4MDNgsf7UfQNd
ZbDZp+Nzu9Hlgf0soqsg+Ww=
=00U5
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#910846: X server "Segmentation fault at address 0x0" when using about:support in Firefox-based browsers.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: xserver-xorg-video-radeon
Version: 1:18.1.0-1

I am using a standalone AMD HD 7670. "firmware-amd-graphics" is installed and 
loaded during boot.
It seems that whenever I tries to query information about hardware 
acceleration, X segfaults.
"dmesg" does not show any error or warning after segfault.
Sometimes other programs or games trigger it as well, with the same problem 
described in the file Xorg.0.log.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJbwCXBCRDYtWA5RV10HwAAuiQIAJQ2jdMOx42C2e3u6tMl
gWPQH1duJcPbXwk/SgD6mQBZPFP2+q/nxStgqAEtrihj78DrgefD9tnyt4tu
Z/PAp0g5quf6ds4Apwo4RCXbsxq1aQRe0ATRHidj2h959k6Qi9InH7skxcCO
AYn0GFRNGEtLXiqs3BE5Je8oQ+t5lI71s1DtmzCLtaQo/OKwNQl+T29UO01d
fz4Y9VppJdQLZYP71cPW3MRbW0o+dv7FcURoiU/28GF28941APtDX+M1rDQ/
o4UrKYR1I4Ea4ejroYSOQGZyKCc7c3Ao0z5rTAFTkLnNncp4pfJnHwCK20GO
8KMH6svPEBKMjfxINfI635g=
=SqQz
-END PGP SIGNATURE-

[   303.139] 
X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
[   303.139] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[   303.139] Current Operating System: Linux AVENTHEIM 4.19.0-rc7-amd64 #1 SMP Debian 4.19~rc7-1~exp1 (2018-10-07) x86_64
[   303.139] Kernel command line: auto BOOT_IMAGE=vmlinuz rw root=800 scsi_mod.use_blk_mq=0 elevator=deadline net.ifnames=0 biosdevname=0 pti=off radeon.dpm=1 quiet video=vesafb:ywrap,mtrr:3
[   303.139] Build Date: 10 October 2018  04:23:15PM
[   303.139] xorg-server 2:1.20.1-5 (https://www.debian.org/support) 
[   303.139] Current version of pixman: 0.34.0
[   303.139] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   303.139] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   303.139] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 12 08:03:49 2018
[   303.141] (==) Using config file: "/etc/X11/xorg.conf"
[   303.141] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   303.142] (==) No Layout section.  Using the first Screen section.
[   303.142] (==) No screen section available. Using defaults.
[   303.142] (**) |-->Screen "Default Screen Section" (0)
[   303.142] (**) |   |-->Monitor ""
[   303.143] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[   303.143] (**) |   |-->Device "Card0"
[   303.143] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   303.143] (==) Automatically adding devices
[   303.143] (==) Automatically enabling devices
[   303.143] (==) Automatically adding GPU devices
[   303.143] (==) Max clients allowed: 256, resource mask: 0x1f
[   303.143] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (**) FontPath set to:
	/usr/share/fonts/X11,
	built-ins,
	built-ins
[   303.143] (**) ModulePath set to "/usr/lib/xorg/modules"
[   303.144] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   303.144] (II) Loader magic: 0x5627644f5e20
[   303.144] (II) Module ABI versions:
[   303.144] 	X.Org ANSI C Emulation: 0.4
[   303.144] 	X.Org Video Driver: 24.0
[   303.144] 	X.Org XInput driver : 24.1
[   303.144] 	X.Org Server Extension : 10.0
[   303.144] (++) using VT number 1

[   303.145] (EE) systemd-logind: failed to get session: The name org.freedesktop.login1 was not provided by any .service files
[   303.145] (II) xfree86: Adding drm device (/dev/dri/card0)
[   303.148] (--) PCI:*(1@0:0:0) 1002:675b:174b:7670 rev 0, Mem @ 0xe000/268435456, 0xf7e2/131072, I/O @ 0xe000/256, BIOS @ 0x/131072
[   303.148] (II) LoadModule: "glx"
[   303.149] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   303.161] (II) Module glx: vendor="X.Org Foundation"
[   303.161] 	compiled for 1.20.1, module version = 1.0.0
[   303.161] 	ABI class: X.Org Server Extension, version 10.0
[   303.161] (II) LoadModule: "radeon"
[   303.161] (II) Loading 

Bug#910492: Formatting suggestions.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: htop
Version: 2.2.0-1+b1
Severity: wishlist

Firstly, the UID field only use 4 digits, while in UNIX UIDs can be 0-65535. If 
I have a UID greater than  the list gets misaligned like which shown in the 
screenshot. You should reserve 5 digits for that field.
Secondly, you should use the old format for IO rates (Disk R/W), like other 
fields (just a number, no "B/s").
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJbucCQCRDYtWA5RV10HwAALfQIALuDve0ncFa+TYBzuFWh
OM3oDBnmUBWtM/BsyJXR//b0jiW+T9GyXaKJHwngj8jMVeLkZGxBVrfmODE2
EgWE9ArG4pxsavCJ36/09DQrY4Bnk+mbVA0g1ShvBs62yrgreFF0l/coEpjf
0PUpZ19qiBOhHw6C3lg9RPb7klIG4tA5apaO5Xg2zf4DUcmLiwzSp6oPyHqN
SM7NsykiAANqC1DVfgmzaX0ePB2dFuFOUO1AlOVc5xzIR/GGeIVjMM3hbpUH
y3WO00xvrTytWc1ZEprA9t3I7nQdfTy0SoqyOoNiNki0/j0I1704zzOlBN/9
Apsig73eJvNzarZ5mDLjbhM=
=stqb
-END PGP SIGNATURE-



2018-10-07-160444_1600x1200_scrot.png.sig
Description: PGP signature


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#903692: `fsck.fat` assumes that the FS is aligned.

[Gong S.]

Package: dosfstools
Version: 4.1-2

Firstly create an FAT FS with alignment. Obviously 62 sectors are wasted:

root:/u/h/root> mkfs.fat -D 0x00 -f 1 -F 32 -h 0 -I -m /dev/null -M 0xF0 -n 
TEST -R 2 -s 64 -vv /dev/sdg
mkfs.fat 4.1 (2017-01-24)
attribute "partition" not found
Boot jump code is eb 58
Using 2 reserved sectors
Trying with 64 sectors/cluster:
FAT12: #clu=967090, fatlen=2880, maxclu=4080, limit=4080
FAT12: too much clusters
FAT16: #clu=967075, fatlen=3840, maxclu=65520, limit=65520
FAT16: too much clusters
FAT16: would be misdetected as FAT12
FAT32: #clu=967016, fatlen=7616, maxclu=974848, limit=268435440
Using sector 6 as backup boot sector (0 = none)
/dev/sdg has 64 heads and 32 sectors per track,
hidden sectors 0x;
logical sector size is 512,
using 0xf0 media descriptor, with 61896704 sectors;
drive number 0x00;
filesystem has 1 32-bit FAT and 64 sectors per cluster.
FAT size is 7616 sectors, and provides 967016 clusters.
There are 64 reserved sectors.
Volume ID is fce1837e, volume label TEST   .

Then check it. There is no problem:

root:/u/h/root> fsck.fat -vV /dev/sdg
fsck.fat 4.1 (2017-01-24)
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkfs.fat"
Media byte 0xf0 (5.25" or 3.5" HD floppy)
   512 bytes per logical sector
 32768 bytes per cluster
64 reserved sectors
First FAT starts at byte 32768 (sector 64)
 1 FATs, 32 bit entries
   3899392 bytes per FAT (= 7616 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 3932160 (sector 7680)
967016 data clusters (31687180288 bytes)
32 sectors/track, 64 heads
 0 hidden sectors
  61896704 sectors total
Starting check/repair pass.
Checking for unused clusters.
Checking free cluster summary.
Starting verification pass.
Checking for unused clusters.
/dev/sdg: 1 files, 1/967016 clusters

Now create the FAT FS without alignment (-a option):

root:/u/h/root> mkfs.fat -a -D 0x00 -f 1 -F 32 -h 0 -I -m /dev/null -M 0xF0 -n 
TEST -R 2 -s 64 -vv /dev/sdg
mkfs.fat 4.1 (2017-01-24)
attribute "partition" not found
Boot jump code is eb 58
Using 2 reserved sectors
Trying with 64 sectors/cluster:
FAT12: #clu=967091, fatlen=2834, maxclu=4080, limit=4080
FAT12: too much clusters
FAT16: #clu=967076, fatlen=3778, maxclu=65520, limit=65520
FAT16: too much clusters
FAT16: would be misdetected as FAT12
FAT32: #clu=967017, fatlen=7555, maxclu=967040, limit=268435440
Using sector 1 as backup boot sector (0 = none)
/dev/sdg has 64 heads and 32 sectors per track,
hidden sectors 0x;
logical sector size is 512,
using 0xf0 media descriptor, with 61896704 sectors;
drive number 0x00;
filesystem has 1 32-bit FAT and 64 sectors per cluster.
FAT size is 7555 sectors, and provides 967017 clusters.
There are 2 reserved sectors.
Volume ID is fe0451d2, volume label TEST   .

Checking the newly-created filesystem:

root:/u/h/root> fsck.fat -vV /dev/sdg
fsck.fat 4.1 (2017-01-24)
Checking we can access the last sector of the filesystem
FSINFO sector has bad magic number(s):
  Offset 0: 0x6d9058eb != expected 0x41615252
  Offset 484: 0x != expected 0x61417272
1) Correct
2) Don't correct (FSINFO invalid then)
? 1
Boot sector contents:
System ID "mkfs.fat"
Media byte 0xf0 (5.25" or 3.5" HD floppy)
   512 bytes per logical sector
 32768 bytes per cluster
 2 reserved sectors
First FAT starts at byte 1024 (sector 2)
 1 FATs, 32 bit entries
   3868160 bytes per FAT (= 7555 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 3869184 (sector 7557)
967017 data clusters (31687213056 bytes)
32 sectors/track, 64 heads
 0 hidden sectors
  61896704 sectors total
Starting check/repair pass.
Checking for unused clusters.
Checking free cluster summary.
Free cluster summary uninitialized (should be 967016)
1) Set it
2) Leave it uninitialized
? 1
Starting verification pass.
Checking for unused clusters.
Perform changes ? (y/n) y
/dev/sdg: 1 files, 1/967017 clusters

Now check the FS again. The same error occurs no matter how many times I 
checked it:

root:/u/h/root> fsck.fat -vV /dev/sdg
fsck.fat 4.1 (2017-01-24)
Checking we can access the last sector of the filesystem
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  0:eb/52, 1:58/52, 2:90/61, 3:6d/41, 4:6b/00, 5:66/00, 6:73/00, 7:2e/00
  , 8:66/00, 9:61/00, 10:74/00, 12:02/00, 13:40/00, 14:02/00, 16:01/00
  , 21:f0/00, 24:20/00, 26:40/00, 33:78/00, 34:b0/00, 35:03/00, 36:83/00
  , 37:1d/00, 44:02/00, 48:01/00, 50:01/00, 66:29/00, 67:99/00, 68:04/00
  , 69:0b/00, 70:08/00, 71:54/00, 72:45/00, 73:53/00, 74:54/00, 75:20/00
  , 76:20/00, 77:20/00, 78:20/00, 79:20/00, 80:20/00, 81:20/00, 82:46/00
  , 83:41/00, 84:54/00, 85:33/00, 86:32/00, 87:20/00, 88:20/00, 89:20/00
  , 90:0e/00, 91:1f/00, 92:be/00, 93:77/00, 94:7c/00, 95:ac/00, 96:22/00
  , 97:c0/00, 98:74/00, 99:0b/00, 100:56/00, 

Bug#902741: Use `p7zip` for archive operations, if possible.

[Gong S.]

Package: mc
Version: 3:4.8.21-1

Currently, `mc` uses standalone utilities like `unzip` to process ZIP files.
However, the package `p7zip` and `p7zip-full` is capable to process such 
formats as well.
You can see which format `p7zip` can handle using `7za i`, and for 
`p7zip-full`, `7z i`.
So, here is my suggestion:
1. Drop the `unzip` recommendation and `arj`, `bzip2`, `genisoimage`, `zip` 
suggestions;
2. Add `p7zip` or `p7zip-full` to suggestions;
3. Use `7za` and `7z` instead of standalone utilities like `unzip` in 
`/etc/mc/mc.ext`.


PGP AB77ABA4-E9D228C9-647BD377-D8B56039-455D741F
Please reply to this e-mail with UTF8-encoded plain text.
You are as malicious as any other spammer if you send HTML e-mails.