Thanks for the hint, this is indeed a ZFS bug.
Reported to upstream at https://github.com/openzfs/zfs/pull/15344/
2023-09-25 0:38 GMT+08:00, Ben Hutchings :
> Control: reassign -1 src:zfs-linux
>
> On Fri, 2023-09-22 at 16:13 +, WHR wrote:
>> Package: src:linux
>> Version: 6.5.3-1
>>
This 'fix' unnecessarily broke the dependency of my VIM 7.4 packages, which
aren't affected by this bug.
> Now I'm confused. Your attached file is virtually identical to
> magic/Magic/zfs in the file(1) sources, and is present since 5.11
> which is in wheezy.
ZFS stream (dump) format is not ZFS on-disk format.
Control: tags 1024639 + patch
$ truncate --size 1GiB /tmp/test-hfs+
$ mkfs.hfsplus /tmp/test-hfs+
Initialized /tmp/test-hfs+ as a 1024 MB HFS Plus volume
$ file --magic-file magic/Magdir/ /tmp/test-hfs+
/tmp/test-hfs+: Apple HFS Plus version 4 data (mounted) last mounted
by: '10.0', created: Sun
Not all non-unicode text streams can be reliably detected, as they could be
ambiguous to eachother.
And the attached file is actually in UTF-8, not Big5, confirmed by file(1)
as well as manual reading:
$ file 111D2012841-01.txt
111D2012841-01.txt: Unicode text, UTF-8 text
Further debugging shows this wasn't the root cause, instead the X BadShmSeg
error is happening inside libGLX.so.0 function glXSwapBuffers, which is
called from src/video/x11/SDL_x11opengl.c, function X11_GL_SwapWindow. As
such I guess the bug may actually be in GLX.
2022-11-11 19:37 GMT+08:00, 王昊
--- src/video/x11/SDL_x11framebuffer.c.orig2022-01-08 10:29:52.0 +0800
+++ src/video/x11/SDL_x11framebuffer.c2022-11-11 19:27:12.527050231 +0800
@@ -42,6 +42,10 @@
static SDL_bool have_mitshm(Display *dpy)
{
+const char *no_shm = SDL_getenv("SDL_VIDEO_X11_NO_SHM");
+if(no_shm &&
Forward the missing messages.
-- Forwarded message --
From: 王昊然
Date: Fri, 21 Oct 2022 14:09:33 +0800
Subject: Re: Bug#1022049: libnettle8: Illegal instruction on IBM POWER7
To: Maamoun TK
Cc: Niels Möller
I can confirm this patch worked on my system.
2022-10-20 21:02 GMT+08
Yes, I has already confirmed the fix in my last email. But it isn't
automatically being CCed to Debian BTS for some reason.
> -- Forwarded message --
> From: 王昊然
> Date: Fri, 21 Oct 2022 14:09:33 +0800
> Subject: Re: Bug#1022049: libnettle8: Illegal instruction o
Hello.
I have just installed a new Linux image with CONFIG_VSX=y, however nettle is
still triggering illegal instruction there.
2022-10-20 2:14 GMT+08:00, Niels Möller :
> 王昊然 writes:
>
>>> int main() {
>>> unsigned long int hwcap = getauxval(AT_HWCAP);
>&g
-- Forwarded message --
From: 王昊然
Date: Thu, 20 Oct 2022 00:33:18 +0800
Subject: Re: Bug#1022049: libnettle8: Illegal instruction on IBM POWER7
To: Niels Möller
2022-10-20 0:18 GMT+08:00, 王昊然 :
>> The ppc specification says "vmrgow is treated as a Vector
>> ins
-- Forwarded message --
From: 王昊然
Date: Thu, 20 Oct 2022 00:18:35 +0800
Subject: Re: Bug#1022049: libnettle8: Illegal instruction on IBM POWER7
To: Niels Möller
> The ppc specification says "vmrgow is treated as a Vector
> instruction in terms of resource availabil
Also reproducible with gdb 8.2.1-2+b3 on buster ppc64el.
I think it is better to use '/proc//comm' instead; it shows
correct script name instead of interpreter name, and didn't have the
issues of 'cmdline'.
While adding 'enable-bracketed-paste off' into inputrc appears fixed
this issue, no idea why it didn't fully work with bashrc only.
2021-01-14 20:59 GMT+08:00, 王昊然 :
> I just found another issue with this new BASH/Readline bug/feature.
> Even with 'bind "set enable-bracketed-paste off&
I just found another issue with this new BASH/Readline bug/feature.
Even with 'bind "set enable-bracketed-paste off"', BASH 5.1 still
behaving differently from previous versions: if pasted text contains
new lines, BASH 5.1 would still buffering the pasted text, rather than
evaluating the pasted
I also found this feature causes confusing in some terminals. However
disabling bracketed paste for BASH worked good enough for me: just
adding 'bind "set enable-bracketed-paste off"' into /etc/bash.bashrc.
Using ARP is wrong, as it is not supported by IP over InfiniBand.
Thanks for conform; I has just tested latest bullseye version and it
worked correctly this time.
Is there some serious problems on fixing this for buster? I think just
restoring the behavior as in stretch should be enough to fix this bug.
2020-05-17 14:55 GMT+08:00, Christoph Biedl :
> Control:
I found a workaround for this issue.
I has put followings into '/etc/profile':
if [ "${LANG%%.*}" = zh_CN ]; then
# Workaround for bug 939445
export LANG="zh_TW${LANG#zh_CN}"
[ -z "$LANGUAGE" ] && export LANGUAGE=zh_CN:zh_TW:en_US:en_GB
fi
This changes LANG from zh_CN to zh_TW so
Thanks, it works, I think this report could be closed now.
2019-07-26 4:08 GMT-07:00, Michael Biebl :
> Am 26.07.19 um 11:21 schrieb 王昊然:
>> OK, now I understands that was a feature, but how should I tell
>> systemd to disable this feature so I can get a normal terminal output
nderstand
> these escape sequences or something mangling them.
>
> Ansgar
>
> [1] https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda
>
> On Fri, 2019-07-26 at 01:53 -0700, 王昊然 wrote:
>> The terminal emulator I used was xfce4-terminal 0.8.3 that is from
The terminal emulator I used was xfce4-terminal 0.8.3 that is from
Debian stretch; the target system reached via ssh(1) in this terminal.
In addition, the same issue can also be seen with Terminator 1.90,
MATE Terminal 1.16.3 and libvte 2.90.
2019-07-25 23:51 GMT-07:00, Michael Biebl :
> Control:
This makes sence, this explained why the didn't happen in dtterm(1) and tmux(1).
2019-07-26 0:55 GMT-07:00, Thomas Dickey :
> On Fri, Jul 26, 2019 at 01:53:21PM +0800, WHR wrote:
>> Package: libncurses6
>> Version: 6.1+20181013-2
>> Severity: important
>> Tags: a11y
>>
>> Hello.
>> Most TUI
Also reproduce with Konsole 16.12.0, PuTTY 0.67, MATE Terminal 1.16.3
and Terminator 1.90.
I think this issue may be in libncurses6 or libtinfo6, because it is
affecting many other programs, not only nload(1).
Please see bug #933053.
I submitted this patch because on CentOS 7, the usage 'service
status -l' works;
and I found it doesn't work on Debian, without a warning.
I agree the service(8) command is a compatibility wrapper for many
different init systems,
so those systemctl specific options cannot be used with other init
27 matches
Mail list logo
