Package: kate
Version: 4:22.12.3-1
Severity: normal
Dear Maintainer,
Upstream bug https://bugs.kde.org/show_bug.cgi?id=476307 has been reported
resolved by MR https://invent.kde.org/utilities/kate/-/merge_requests/1441
It would be extremely helpful if you were able to pull the patch back to
Package: libtiff
Version: 4.3.0-7
In 4.3.0-7 it looks like you've included a patch based on https://gitlab.com/
libtiff/libtiff/-/commit/9752dae8febab08879fc0159e7d387cff14eb3c3 as a fix for
CVE-2022-1355, but I don't think this is the right patch. You can confirm this
by building the package
In attempting to test out the indicated patch I noticed it's already applied
to linux 4.19.194 (as commit c733cf4abfba34e54e83bcb4ac4733203647e339), so
that's clearly not the fix.
This continues to happen for me maybe 1 in every 5 hibernations (on previously
stated thinkpad x230).
robert.
Package: li1nux
Version: 4.19.0-17
tl;dr: I have a feeling this is https://bugzilla.redhat.com/show_bug.cgi?
id=1656233
After resuming a buster system with linux-4.19.0-17 on a thinkpad x220 the
intel 6205 wifi fails to work, with the below dmesg warnings.
Hopefully this _is_ just the same bug
Package: linux
Version: 4.9.0-16
Hi,
linux-4.9.0-16-amd64 is not a happy kernel.
I don't know whether this is a duplicate of #990423, because I'm also using
iwlwifi, but this is on a thinkpad X220.
I actually received the latter two crashes *during* my upgrade to buster,
which didn't do a
FWIW I'm fairly convinced that the first vulnerable version for CVE-2020-5310
is 6.0.0, which is the first release that included
https://github.com/python-pillow/Pillow/commit/e91b851fdc1c914419543f485bdbaa010790719f
which introduced
the overflow when switching away from the safer TIFFTileSize
Source: tightvnc
Version: 1:1.3.9-9
Just letting you know I've ported fixes for the above CVEs from (the actively
maintained) libvnc for NixOS: https://github.com/NixOS/nixpkgs/pull/73970/
files
robert.
> Alternatively, it could be related to:
> https://www.sqlite.org/src/info/4feb3159c6bc3f7e33959
>
> This was released as a part of 3.27.2 and looks like it has the right
> text as well. What concerns me is that the ticket[0] is almost a week
> before TALOS's timeline for "Vendor patched" plus
Hi,
I can confirm that this is still occurring in wheezy.
Package: kmail
Version: 4:4.4.11.1+l10n-3+b1
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP
Package: src:linux
Version: 3.2.46-1
Severity: normal
Dear Maintainer,
On a Lenovo Ideapad z585, using HDMI output, having already had to blacklist
snf-hda-codec-hdmi to avoid oopses on boot (probably a different issue, will
file separately), when starting plasma-desktop for the first time on
Package: installation-reports
Version: Whatever version's on the currently available 7.1.0 netinst cd image
Severity: important
Tags: d-i
Hi,
When installing on a UEFI system (Lenovo Ideapad Z585), amd64, (installer
booted in UEFI mode, _I think_), installing grub fails with:
Executing
On Sunday 18 August 2013, Steven Chamberlain wrote:
Hi Robert,
If GRUB installed successfully, and you booted it, it would then need to
load the kernel image and initramfs into memory. AFAIK it would be
unable to do that if those are inside of the encrypted LVM. (The wheezy
version of
Hi,
What's the status of this fix?
I'm getting the same behaviour on my Lenovo Ideapad S10-3, however I'm running
on i386 (well, 686-pae).
I'm using squeeze with linux-modules-3.2.0-0.bpo.2-686-pae 3.2.12-1~bpo60+1.
linux-modules-2.6.39-bpo.2-686-pae 2.6.39-3~bpo60+1 works fine but no
On Saturday 27 August 2011, Jonathan Nieder wrote:
I think we are long overdue to take this one upstream. I have a few
questions anyway for before then:
- does hibernation work for you if you try a sid (3.x) kernel?
Would 2.6.39+35.1 (from squeeze-backports) do? It's a lot easier to get
On Saturday 27 August 2011, Jonathan Nieder wrote:
- does hibernation work for you if you try a sid (3.x) kernel?
Would 2.6.39+35.1 (from squeeze-backports) do? It's a lot easier to get
installed ;)
Or is there a specific relevant patch that's gone into 3.*?
Sure, 2.6.39 is fine.
Hi,
I've been having the same problem on a Lenovo ideapad S10-3 in bug #623149
(should probably be marked as a duplicate in fact but I don't like to mess
around with other peoples bug trackers).
As suggested by Frederic, I tried 2.6.32-31 with
On Tuesday 19 April 2011, Frédéric Boiteux wrote:
Hello Robert,
Perhaps you're also affected by the same bug I did with my eeepc
(see #622259). Could you test a 2.6.32-31 kernel with following patch
reverted :
x86-hotplug-use-mwait-to-offline-a-processor-fix-the-legacy-case.patch
It
Package: linux-image-2.6.32-5-686
Version: 2.6.32-31
Severity: important
Hi,
I sure the last thing Ben needs is another netbook hibernation resume failure,
but here we go.
Using a Lenovo ideapad S10-3 (which afaik is a pretty much standard pine trail
netbook), squeeze installed from scratch,
On Sunday 16 January 2011, Cyril Brulebois wrote:
Could you please get a full backtrace?
http://pkg-xorg.alioth.debian.org/xsf-docs/howtos/use-gdb.html
Ah, didn't know about bt full.
(gdb) bt full
#0 0xb74d0042 in __glXDRIscreenProbe (pScreen=0x88cd058) at
../../glx/glxdri2.c:639
Package: linux-image-2.6.32-5-686
Version: 2.6.32-21
Severity: grave
Hi,
Blacklisting the 855GM from KMS in 2.6.32-21 to fix bugs like 582105 seems to
be causing my system to hard lock when X starts up. Magic sysrq key does
nothing, and of course the 855GM being totally blacklisted means
On Saturday 11 September 2010, you wrote:
On 09/11/2010 06:24 PM, Robert Scott wrote:
Blacklisting the 855GM from KMS in 2.6.32-21 to fix bugs like 582105
seems to be causing my system to hard lock when X starts up. Magic
sysrq key does nothing, and of course the 855GM being totally
Hi,
The libpuma-dev package in experimental (0.99+1.0pre3-3) doesn't seem to
include any headers. This makes developing with it pretty difficult.
robert.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Indeed; bluepin is no longer installed.
But python-gtk2 is a suggested package. Which doesn't make any sense anymore.
Unless there's another component of bluez-utils which uses it which I don't
know about.
Very nice.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: bluez-utils
Version: 2.25-1
Subject says it all really. Reasonably freshly installed etch system.
robert.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: realtime-lsm-source
Version: 0.1.1-6
I understand that realtime-lsm is going away, but until a fresh pam turns up
in testing, it is a good enough stopgap and it would be nice for it to at
least still be working. With kernel 2.6.15 it does still work if you build a
custom kernel with
25 matches
Mail list logo
