Hi Julien,
On Wed, Jul 17, 2019 at 06:31:15AM +0200, Julien Aubin wrote:
> Hi,
>
> Sadly the bug is still there for Buster. Could you re-open it please ?
That should actually not be done. The Debian BTS has the version
tracking in place, so for 4.19.37-5 it is still marked as unfixed even
if
Hi,
Sadly the bug is still there for Buster. Could you re-open it please ?
Le mar. 16 juil. 2019 à 23:09, Debian Bug Tracking System
a écrit :
>
> This is an automatic notification regarding your Bug report
> which was filed against the src:linux package:
>
> #930904:
Processing commands for cont...@bugs.debian.org:
> reassign 931584 src:linux
Bug #931584 [steam] Steam failed to connect to servers - Buster
Bug #931588 [steam] Steam failed to connect to servers - Buster
Bug reassigned from package 'steam' to 'src:linux'.
Bug reassigned from package 'steam' to
Package: linux-image-amd64
Version: 4.19+105
Followup-For: Bug #932250
adding file with segfault data
-- System Information:
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE,
Package: linux-image-amd64
Version: 4.19+105
Severity: important
Hi.
Im currently running debian buster kernel and i experienced some segfaults.
Segfaults are random, which prevents me from pinpointing the trigger.
First i tried disabling overcommit on memory, the behavior stoped.
Today it
Processing commands for cont...@bugs.debian.org:
> severity 932162 important
Bug #932162 [src:linux] linux-image-4.19.0-5-amd64: Blank screen after startup.
Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument"
Severity set to 'important' from 'critical'
> thanks
Stopping
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 29 Jun 2019 09:29:10 +0200
Binary: linux-doc-4.9 linux-headers-4.9.0-10-common
linux-headers-4.9.0-10-common-rt linux-manual-4.9 linux-source-4.9
linux-support-4.9.0-10
Source: linux
Architecture: all source
Your message dated Tue, 16 Jul 2019 21:07:58 +
with message-id
and subject line Bug#866122: fixed in linux 4.9.184-1
has caused the Debian Bug report #866122,
regarding FP register corruption on ppc64el with lock elision
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 16 Jul 2019 21:07:58 +
with message-id
and subject line Bug#866122: fixed in linux 4.9.184-1
has caused the Debian Bug report #866122,
regarding FP register corruption on ppc64el with lock elision
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 16 Jul 2019 21:07:58 +
with message-id
and subject line Bug#930904: fixed in linux 4.9.184-1
has caused the Debian Bug report #930904,
regarding linux-image-4.19.0-5-amd64: Latest kernel upgrades on unstable break
Steam (link to fix included)
to be marked as done.
git clone
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
cd linux-firmware
mkdir /lib/firmware/mediatek/
cp mediatek/mt7610u.bin /lib/firmware/mediatek/
rmmod mt76x0
modprobe mt76x0
Adapter is working.
Installed gdm3 and set it as default.
Everything works and I can reach the Xfce desktop.
Issue seems related to LightDM.
Em ter, 16 de jul de 2019 09:21, Henry J. Douglas
escreveu:
> Booted with nomodeset i915.modeset=0 and here are the results.
>
> No display either. LightDM doesn't start,
Processing control commands:
> tag -1 + pending
Bug #929968 [src:linux] linux: Missing C_CAN module
Added tag(s) pending.
--
929968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 + pending
Hello,
I merged your PR and added a changelog entry for it.
Best regards
Uwe
signature.asc
Description: PGP signature
Booted with nomodeset i915.modeset=0 and here are the results.
No display either. LightDM doesn't start, Xorg doesn't start.
[30.131]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[30.131] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[30.131] Current Operating
On Tue, 16 Jul 2019 00:15:44 +0100
Ben Hutchings wrote:
> I suspect that this bug is a duplicate of bug #928510, for which the
> fix missed the buster release (but we can fix it in a point release).
> If you run "update-initramfs -u" and reboot, does that fix the
> problem?
Ah, that does
16 matches
Mail list logo