linux-signed-amd64_5.0.1+1~exp1_source.changes uploaded successfully to
localhost
along with the files:
linux-signed-amd64_5.0.1+1~exp1.dsc
linux-signed-amd64_5.0.1+1~exp1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
binary:linux-image-5.0.0-trunk-amd64 is NEW.
binary:linux-image-5.0.0-trunk-cloud-amd64 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so ple
linux-signed-arm64_5.0.1+1~exp1_source.changes uploaded successfully to
localhost
along with the files:
linux-signed-arm64_5.0.1+1~exp1.dsc
linux-signed-arm64_5.0.1+1~exp1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
binary:linux-image-5.0.0-trunk-arm64 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Packages are routinely processed t
linux-signed-i386_5.0.1+1~exp1_source.changes uploaded successfully to localhost
along with the files:
linux-signed-i386_5.0.1+1~exp1.dsc
linux-signed-i386_5.0.1+1~exp1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
The corresponding patch has been merged in the 4.19 branch
and is released as 4.19.29.
commit b4d965a37d89cd8611984ea16c85903d01ac967a
Author: Ronnie Sahlberg
AuthorDate: Wed Oct 24 11:50:33 2018 +1000
Commit: Greg Kroah-Hartman
CommitDate: Wed Mar 13 14:02:40 2019 -0700
cifs: allow
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 12 Mar 2019 23:15:21 +
Source: linux-signed-arm64
Binary: kernel-image-5.0.0-trunk-arm64-di nic-modules-5.0.0-trunk-arm64-di
nic-wireless-modules-5.0.0-trunk-arm64-di
nic-shared-modules-5.0.0-trunk-arm64-di
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 12 Mar 2019 23:15:21 +
Source: linux-signed-amd64
Binary: kernel-image-5.0.0-trunk-amd64-di nic-modules-5.0.0-trunk-amd64-di
nic-wireless-modules-5.0.0-trunk-amd64-di
nic-shared-modules-5.0.0-trunk-amd64-di
binary:linux-image-5.0.0-trunk-686 is NEW.
binary:linux-image-5.0.0-trunk-686-pae is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be
Processing control commands:
> reassign 921004 firmware-amd-graphics 20190114-1
Bug #921004 [xserver-xorg-video-amdgpu] amdgpu: The CS has been cancelled
because the context is lost.
Bug reassigned from package 'xserver-xorg-video-amdgpu' to
'firmware-amd-graphics'.
Ignoring request to alter fou
Processing control commands:
> reassign 921004 firmware-amd-graphics 20190114-1
Bug #921004 [firmware-amd-graphics] AMD Radeon RX 580: no GL display, "amdgpu:
The CS has been cancelled because the context is lost"
Bug #921114 [firmware-amd-graphics] AMD Radeon RX 580: no GL display, "amdgpu:
The
Control: reassign 921004 firmware-amd-graphics 20190114-1
Control: reassign 921145 firmware-amd-graphics 20190114-1
Control: forcemerge 921114 921004 921145
Control: retitle 921114 AMD Radeon RX 580: no GL display, "amdgpu: The CS has
been cancelled because the context is lost"
Control: tags 92111
Processing control commands:
> reassign 921004 firmware-amd-graphics 20190114-1
Bug #921004 [firmware-amd-graphics] AMD Radeon RX 580: no GL display, "amdgpu:
The CS has been cancelled because the context is lost"
Bug #921114 [firmware-amd-graphics] AMD Radeon RX 580: no GL display, "amdgpu:
The
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 12 Mar 2019 23:15:21 +
Source: linux-signed-i386
Binary: kernel-image-5.0.0-trunk-686-di nic-modules-5.0.0-trunk-686-di
nic-wireless-modules-5.0.0-trunk-686-di nic-shared-modules-5.0.0-trunk-686-di
serial-mo
Package: src:linux
Version: 4.19.28-1
Severity: important
With this new kernel, I get the following error 487 times!
PKCS#7 signature not signed with a trusted key
cventin:~> journalctl -b | grep -c 'PKCS#7 signature not signed with a trusted
key'
487
There were no such errors with previous
Package: src:linux
Version: 4.19.28-1
Severity: minor
Dear Maintainer,
upgrading to the new kernel gave me the kernel warning 'PKCS#7 signature not
signed with a trusted key'.
I did a bit of research and it's probably a problem with the nvidia card
(driver 410.104-1).
The message didn't appear wi
Processing control commands:
> severity -1 important
Bug #921114 [firmware-amd-graphics] AMD Radeon RX 580: no GL display, "amdgpu:
The CS has been cancelled because the context is lost"
Bug #921004 [firmware-amd-graphics] AMD Radeon RX 580: no GL display, "amdgpu:
The CS has been cancelled beca
Control: severity -1 important
On Thu, 14 Mar 2019 at 09:07:02 +, Simon McVittie wrote:
> On Fri, 01 Feb 2019 at 18:16:41 +0100, Jean-Dominique Frattini wrote:
> > since the latest update of xserver-xorg-video-amdgpu and
> > firmware-amd-graphics [in buster], most GL applications do not displa
Package: src:linux
Version: 4.19.28-1
Severity: normal
With this kernel version (but not with the last 4.19.0-3) journalctl shows
many of these messages:
PKCS#7 signature not signed with a trusted key
A lot of such messages can also be seen on the early booting phase.
Also I noticed that, below,
Processing control commands:
> forcemerge 924545 924549 924553
Bug #924545 [src:linux] linux-image-4.19.0-4-amd64: many errors "PKCS#7
signature not signed with a trusted key"
Bug #924549 [src:linux] linux-image-4.19.0-4-amd64: 'PKCS#7 signature not
signed with a trusted key', probably nvidia
Bu
Processing control commands:
> forcemerge 924545 924549 924553
Bug #924545 [src:linux] linux-image-4.19.0-4-amd64: many errors "PKCS#7
signature not signed with a trusted key"
Bug #924549 [src:linux] linux-image-4.19.0-4-amd64: 'PKCS#7 signature not
signed with a trusted key', probably nvidia
Bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: forcemerge 924545 924549 924553
On Thu, 2019-03-14 at 11:03 +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 4.19.28-1
> Severity: important
>
> With this new kernel, I get the following error 487 times!
>
> PKCS#7 signatur
Processing control commands:
> forcemerge 924545 924549 924553
Bug #924545 [src:linux] linux-image-4.19.0-4-amd64: many errors "PKCS#7
signature not signed with a trusted key"
Bug #924553 [src:linux] linux-image-4.19.0-4-amd64: PKCS#7 signature not signed
with a trusted key
Severity set to 'impo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
In jessie backports there is currently a 4.9 kernel
(4.9.110-3+debu5~deb8u1) which is based on stretch 4.9.110-3+deb9u2. Since
stretch now has 4.9.144-3.1 are there any plans to make a
4.9.144-3.1~deb8u1 for jessie?
I have a piece of hard
When I run my work laptop (latest Thinkpad Carbon X1) with the kernel from
Testing it fails to resume from suspend about 30% of the time. When I use the
kernel from Stable (with Testing userspace) it runs correctly.
Do you have any ideas for how I could track this down? It fails when it's not
>
> In jessie backports there is currently a 4.9 kernel
> (4.9.110-3+debu5~deb8u1) which is based on stretch 4.9.110-3+deb9u2. Since
> stretch now has 4.9.144-3.1 are there any plans to make a
> 4.9.144-3.1~deb8u1 for jessie?
>
> I have a piece of hardware that requires the newer kernel but will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In jessie backports there is currently a 4.9 kernel
(4.9.110-3+debu5~deb8u1) which is based on stretch 4.9.110-3+deb9u2.
Since stretch now has 4.9.144-3.1 are there any plans to make a
4.9.144-3.1~deb8u1 for jessie?
This kernel is maintained t
Package: src:linux
Version: 4.19.28-1
Severity: normal
Dear Maintainer,
After today's upgrade to 4.19.28 (package linux-image-4.19.0-4-amd64), the
above mentioned is spammed dozens of times at boot.
Other than that, I see no other issue, not even a single delay of the boot
process.
Installing th
On Thu, 2019-03-14 at 04:35 +, Russell Coker wrote:
> Is there an archive of all the kernels that have been uploaded to Unstable
> that I could do a binary search on and find out which version had the change
> that broke things for me?
snapshots.d.o should have everything, including the ones
I cannot confirm this bug with an AMD Radeon RX 570 4gb. There are no
problems with firmware-nonfree/20190114-1 and launching opengl games.
The problem seems to be more hardware specific or is caused by something
else.
Axel
Processing commands for cont...@bugs.debian.org:
> fixed 916797 5.0.1-1~exp1
Bug #916797 [src:linux] linux-image-4.19.0-1-amd64-unsigned: 4.19 + amdgpu +
144 hz = screen corruption / flickering
Marked as fixed in versions linux/5.0.1-1~exp1.
> thanks
Stopping processing here.
Please contact me i
I'm going to close the bug. It only affects kernel 4.19. The newer
Kernels like 4.20 or 5.0 are not affected and it seems that the fix
won't be backported to 4.19.
Processing commands for cont...@bugs.debian.org:
> close 916797
Bug #916797 [src:linux] linux-image-4.19.0-1-amd64-unsigned: 4.19 + amdgpu +
144 hz = screen corruption / flickering
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916797: https:/
Package: nfs-common
Severity: important
Version: 1:1.3.4-2.4
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: debian-edu
Dear maintainers,
we are trying to fix a race condition between autofs(-ldap), the NFSv4
client service stack and the network-online.tar
Hey Ben, Salvatore.
Thanks for cherry-picking the bug for unstable.
AFAIU stretch and jessie[-backports] should be affected as well.
Shouldn't it go there, too?
At least at the upstream mailing list it was said[0] the the bug was
introduced around October 2008, which should be roughly kernel 2.6
Hi Christoph,
On Thu, Mar 14, 2019 at 08:06:52PM +0100, Christoph Anton Mitterer wrote:
> Hey Ben, Salvatore.
>
> Thanks for cherry-picking the bug for unstable.
>
> AFAIU stretch and jessie[-backports] should be affected as well.
> Shouldn't it go there, too?
Yes it needs to be adressed there
On Friday, 15 March 2019 1:44:58 AM AEDT Ian Campbell wrote:
> On Thu, 2019-03-14 at 04:35 +, Russell Coker wrote:
> > Is there an archive of all the kernels that have been uploaded to Unstable
> > that I could do a binary search on and find out which version had the
> > change that broke thing
37 matches
Mail list logo
