linux_3.16.36-1+deb8u2~bpo70+1_multi.changes ACCEPTED into wheezy-backports->backports-policy

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Oct 2016 19:33:42 +0100 Source: linux Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 linux-support-3.16.0-0.bpo.4 linux-libc-dev linux-headers-3.16.0-0.bpo.4-all

Processing of linux_3.16.36-1+deb8u2~bpo70+1_multi.changes

linux_3.16.36-1+deb8u2~bpo70+1_multi.changes uploaded successfully to localhost along with the files: linux_3.16.36-1+deb8u2~bpo70+1.dsc linux_3.16.36-1+deb8u2~bpo70+1.debian.tar.xz linux-support-3.16.0-0.bpo.4_3.16.36-1+deb8u2~bpo70+1_all.deb

linux_4.7.8-1~bpo8+1_multi.changes ACCEPTED into jessie-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Oct 2016 19:47:42 +0100 Source: linux Binary: linux-source-4.7 linux-support-4.7.0-0.bpo.1 linux-doc-4.7 linux-manual-4.7 linux-kbuild-4.7 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.7

Processing of linux_4.7.8-1~bpo8+1_multi.changes

linux_4.7.8-1~bpo8+1_multi.changes uploaded successfully to localhost along with the files: linux_4.7.8-1~bpo8+1.dsc linux_4.7.8-1~bpo8+1.debian.tar.xz linux-support-4.7.0-0.bpo.1_4.7.8-1~bpo8+1_all.deb lockdep_4.7.8-1~bpo8+1_all.deb linux-doc-4.7_4.7.8-1~bpo8+1_all.deb

linux_3.16.36-1+deb8u2_multi.changes ACCEPTED into proposed-updates->stable-new

Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Oct 2016 06:27:03 +0200 Source: linux Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all

Processing of linux_3.16.36-1+deb8u2_multi.changes

linux_3.16.36-1+deb8u2_multi.changes uploaded successfully to localhost along with the files: linux_3.16.36-1+deb8u2.dsc linux_3.16.36-1+deb8u2.debian.tar.xz linux-support-3.16.0-4_3.16.36-1+deb8u2_all.deb linux-doc-3.16_3.16.36-1+deb8u2_all.deb linux-manual-3.16_3.16.36-1+deb8u2_all.deb

Bug#841240: similar issue on 4.9-rc1

Lemme add: there's a similar, more serious issue on 4.9-rc1. x32 processes fail not just on preadv but on apparently any startup of something linked with glibc (although at least _exit() and write() do work). I haven't yet had the tuits to bisect or debug what's the cause. -- A MAP07 (Dead

Processed: Re: Bug#841289: [drm/i915] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [2507], reason: Engine(s) hung, action: reset

Processing control commands: > forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=98332 Bug #841289 [src:linux] [drm/i915] GPU HANG: ecode 9:0:0xfffe, in Xorg [2507], reason: Engine(s) hung, action: reset Set Bug forwarded-to-address to

Bug#841289: [drm/i915] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [2507], reason: Engine(s) hung, action: reset

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=98332 Am 19.10.2016 um 14:35 schrieb Ben Hutchings: > On Wed, 2016-10-19 at 13:53 +0200, Jonas Meurer wrote: >> Package: src:linux >> Version: 4.7.6-1 >> Severity: grave >> Justification: renders package unusable >> >> Hello, >>

linux_4.7.8-1_allonly.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Oct 2016 17:56:57 +0200 Source: linux Binary: linux-source-4.7 linux-support-4.7.0-1 linux-doc-4.7 linux-manual-4.7 linux-kbuild-4.7 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.7 libusbip-dev

linux_4.7.6-1~bpo8+1_amd64.changes ACCEPTED into jessie-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Oct 2016 11:41:53 +0200 Source: linux Binary: linux-source-4.7 linux-support-4.7.0-0.bpo.1 linux-doc-4.7 linux-manual-4.7 linux-kbuild-4.7 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.7

Bug#841357: linux-source-4.7: 'make allnoconfig' generates an allyesconfig

Package: linux-source-4.7 Severity: normal Dear Maintainer, we are using the kernel source packages to generate minimized configurations for particular use cases. As our tools only give us a partial configuration, we need to expand our precomputed set of options to a full kernel config. We do

Processing of linux_4.7.6-1~bpo8+1_amd64.changes

linux_4.7.6-1~bpo8+1_amd64.changes uploaded successfully to localhost along with the files: linux_4.7.6-1~bpo8+1.dsc linux_4.7.6-1~bpo8+1.debian.tar.xz linux-support-4.7.0-0.bpo.1_4.7.6-1~bpo8+1_all.deb lockdep_4.7.6-1~bpo8+1_all.deb linux-doc-4.7_4.7.6-1~bpo8+1_all.deb

Processed: bug 841275 is forwarded to linux-in...@vger.kernel.org

Processing commands for cont...@bugs.debian.org: > forwarded 841275 linux-in...@vger.kernel.org Bug #841275 [src:linux] linux: Logitech Unifying Receiver shows devices that aren't connected Set Bug forwarded-to-address to 'linux-in...@vger.kernel.org'. > thanks Stopping processing here. Please

Bug#841275: linux: Logitech Unifying Receiver shows devices that aren't connected

On Wed, 19 Oct 2016 02:42:40 -0600 Trent Gamblin wrote: > Source: linux > Severity: normal >  > Dear Maintainer, >  > I have a PC with a mouse connected by a Logitech Unifying Receiver, and > an Android TV box with a keyboard connected by a separate Unifying > Receiver.  The

Bug#841275: linux: Logitech Unifying Receiver shows devices that aren't connected

Control: severity -1 wishlist Control: tag -1 - moreinfo Control: tag -1 upstream On Wed, 2016-10-19 at 08:43 -0600, Trent Gamblin wrote: > It seems pretty likely to me that there is some identifying information  > that the driver can look at to determine if the device is connected or  > not. On

Processed: Re: Bug#841275: linux: Logitech Unifying Receiver shows devices that aren't connected

Processing control commands: > severity -1 wishlist Bug #841275 [src:linux] linux: Logitech Unifying Receiver shows devices that aren't connected Severity set to 'wishlist' from 'normal' > tag -1 - moreinfo Bug #841275 [src:linux] linux: Logitech Unifying Receiver shows devices that aren't

Bug#841275: linux: Logitech Unifying Receiver shows devices that aren't connected

On Wed, 2016-10-19 at 07:55 -0600, Trent Gamblin wrote: > The fact that the device isn't connected to the PC should make it  > obvious that it shouldn't show up in the list of connected devices. [...] The kernel can't possibly detect a device that is not, in some sense, connected to the PC.  The

Bug#841275: linux: Logitech Unifying Receiver shows devices that aren't connected

The fact that the device isn't connected to the PC should make it obvious that it shouldn't show up in the list of connected devices. Perhaps the bug is not in the kernel but in the applet, though, if it had enough information to filter those devices. On 19/10/16 06:33 AM, Ben Hutchings

Processed: tagging 841289

Processing commands for cont...@bugs.debian.org: > tags 841289 + upstream moreinfo Bug #841289 [src:linux] [drm/i915] GPU HANG: ecode 9:0:0xfffe, in Xorg [2507], reason: Engine(s) hung, action: reset Added tag(s) upstream and moreinfo. > thanks Stopping processing here. Please contact me if

Bug#841289: [drm/i915] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [2507], reason: Engine(s) hung, action: reset

On Wed, 2016-10-19 at 13:53 +0200, Jonas Meurer wrote: > Package: src:linux > Version: 4.7.6-1 > Severity: grave > Justification: renders package unusable > > Hello, > > recently, something on my system related to drm/i915 broke. Since no > xserver/drm packages have been upgraded, I strongly

Processed: severity of 841289 is important

Processing commands for cont...@bugs.debian.org: > severity 841289 important Bug #841289 [src:linux] [drm/i915] GPU HANG: ecode 9:0:0xfffe, in Xorg [2507], reason: Engine(s) hung, action: reset Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if

Bug#841275: linux: Logitech Unifying Receiver shows devices that aren't connected

Control: tag -1 moreinfo On Wed, 2016-10-19 at 02:42 -0600, Trent Gamblin wrote: > Source: linux > Severity: normal > > Dear Maintainer, > > I have a PC with a mouse connected by a Logitech Unifying Receiver, > and > an Android TV box with a keyboard connected by a separate Unifying > Receiver. 

Processed: Re: Bug#841275: linux: Logitech Unifying Receiver shows devices that aren't connected

Processing control commands: > tag -1 moreinfo Bug #841275 [src:linux] linux: Logitech Unifying Receiver shows devices that aren't connected Added tag(s) moreinfo. -- 841275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841275 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#841289: [drm/i915] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [2507], reason: Engine(s) hung, action: reset

Package: src:linux Version: 4.7.6-1 Severity: grave Justification: renders package unusable Hello, recently, something on my system related to drm/i915 broke. Since no xserver/drm packages have been upgraded, I strongly suspect the latest linux kernel upgrade to be the culprit. Since several

Quick Query

Hi, I'm writing to you having come across dug.net.pl whilst doing some research on gaming. It got me thinking, and I was wondering if you might like me to write a well-informed and researched guide to speeding up your PC on no budget for you? As a gamer myself, I have tweaked my PC a lot over

Bug#841275: linux: Logitech Unifying Receiver shows devices that aren't connected

Source: linux Severity: normal Dear Maintainer, I have a PC with a mouse connected by a Logitech Unifying Receiver, and an Android TV box with a keyboard connected by a separate Unifying Receiver. The keyboard shows up on the Linux box with a message in dmesg: [3.120080] usb 5-2.1: new