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,
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
-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
-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
-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
-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.
-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
-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
-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
-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
-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
-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
-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:
-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
-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.
-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\
-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
-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
-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:
-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,
-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
-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,
-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
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
-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"
-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
-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
-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:
-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
-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.
-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
-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
-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
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
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
-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
-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
-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
-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
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
-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
-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
-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
-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
-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
-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.
-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
-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:
-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,
-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
-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
-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
-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
-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
54 matches
Mail list logo
