Hello Jacob,
I tested the patch from your previous message with putty 0.82-1
(currently available in Debian Unstable and Debian Testing), which I
found to be affected by the same bug as the previous version 0.81-3.
It works :-)
For those interested, these are the commands I used to patch the
Hello,
I found that rebuilding the putty package with compiler optimisation
disabled seems to fix the problem.
These are the command I used to rebuild the package:
sudo apt install packaging-dev
apt source putty
sudo apt build-dep putty
cd putty-0.81
DEBFULLNAME="noname" DEBEMAIL="non...@nona
Hello,
On 18/11/2024 19:59, Colin Watson wrote:
I just ran "sbuild -Ad unstable --chroot-mode unshare putty" and it
built fine. Perhaps pbuilder is doing something odd. sbuild is the
tool used on Debian's build daemons, so I always prefer it. Try that
and see if it behaves better?
(This was
Package: putty
Version: 0.81-3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
I have tried to build the putty_0.81-3 package using pbuilder.
* What exactly did you do (or not do)
Hello,
A bug report has been opened on KDE bug tracking system:
https://bugs.kde.org/show_bug.cgi?id=471979
Hello,
On 30/01/2023 07:21, Cyril Brulebois wrote:
Package: www.debian.org
Severity: important
Hi,
This was mentioned a few days ago on debian-project@ by Gunnar:
https://lists.debian.org/debian-project/2023/01/msg00018.html
but much work has happened since then, with debian-installer comp
Hello Salvatore,
On Tue, 4 Oct 2022 19:39:23 +0200 Computer Enthusiastic
wrote:
Hello Salvatore,
Il giorno mar 20 set 2022 alle ore 12:32 Salvatore Bonaccorso
ha scritto:
>
> Hi,
[..]
> >
> > What could be done to make the patch land in the current Debian Stable
>
Hello,
Can something still be done to let atop make to Debian Bookworm ?
Thanks.
Hello Salvatore,
Il giorno mar 20 set 2022 alle ore 12:32 Salvatore Bonaccorso
ha scritto:
>
> Hi,
[..]
> >
> > What could be done to make the patch land in the current Debian Stable
> > (Bullseye) kernel release ?
>
> It should land in the 5.10.y stable series which we will then pick up
> automa
Hello,
Il giorno mar 20 set 2022 alle ore 09:33 Salvatore Bonaccorso
ha scritto:
>
> close 989705 5.19.6-1
> thanks
What could be done to make the patch land in the current Debian Stable
(Bullseye) kernel release ?
Thanks.
Hello,
An upstream patch has been released [1]
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc5&id=6b04ce966a738ecdd9294c9593e48513c0dc90aa
Hello,
To whom it may interests, I've successful tested the patch (see
previous message [0]) with Debian
kernels version 5.10.0-16-amd64 [1] from bullseye-security and,
5.18.0-0 [2] from bullseye-backports
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989705#64
[1]
http://security.debian
Hello,
I've been successfully used an experimental "work in progress" patch
with the kernel version 5.10.113 since last 25 may (see
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/547#note_1438950)
.
I suspended and hibernated the system (Debian GNU/Linux 11.3 with the
afor
Hello,
Another similar bug report has been opened here [1] for a different computer
model (different CPU, different GPU) with a possible solution [2]. Perhaps you
could test if solution in [2] applies to your computer, too.
Hope that help. Bye.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi
Hello,
This is an update of the reported issue for different kernel versions.
The column 'STATUS" shows if suspend to ram/suspend to disk fails (FAIL) or
succeeds (OK).
The kernel versions linux-image-4.19.0-11-amd64, linux-image-5.10.0-8-amd64 and
linux-image-5.10.0-8-amd64 are from official
15 matches
Mail list logo
