Bug#734173: linux-image-3.12-1-686-pae: After upgrade to 3.12, need to toogle a switch in alsamixer to use the mike

Package: src:linux Version: 3.12.6-2 Severity: minor Dear Maintainer, as stated in the subject and the switch I need to toogle is the one to enable recording from the microphone, named "Microphone Capture". It is always enabled, but after resume I have to switch it off and back on, otherwise the

Bug#677727: [3.2->3.3 regression] mceusb: only every second keypress is recognised

On 10.07.2013 17:31, Moritz Muehlenhoff wrote: reassign 677727 src:linux thanks On Sun, Jul 15, 2012 at 03:25:18PM +0200, Michael Schmitt wrote: Did this issue drop under everybodys radar? :) Does this still occur with 3.9 from unstable or 3.10-rc7 from experimental? I did install 3.10-1-686

Bug#690162: mouse/keyboard stop working after s2ram until hid_logitech reloaded

Am 12.10.2012 12:33, schrieb Michael Schmitt: Hi Jonathan, Am 11.10.2012 02:11, schrieb Jonathan Nieder: Michael Schmitt wrote: Am 11.10.2012 00:23, schrieb Jonathan Nieder: - What was the first non-working kernel? If you have time to bisect through the pre-compiled kernels at

Bug#690162: Acknowledgement (3.5-trunk-686-pae)

Damn it, I forgot the attachments... here they are. regards and greetings Michael [0.694118] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 [0.728176] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1 [0.728243] input:

Bug#690162: 3.5-trunk-686-pae

Package: src:linux Version: 3.5.5-1~experimental.1 Severity: normal Dear maintainers, after resume from s2ram my mouse from a Logitech mouse/keyboard-set does not work anymore. Reloading hid_logitech.ko fixes the mouse again. Keyboard works always. The former version off linux-image-3.5 from

Bug#678215: USB mouse not recognized after resuming from suspend to, RAM

Hi Jonathan, Am 10.10.2012 01:03, schrieb Jonathan Nieder: Michael Schmitt wrote: I have the exact same symptom here with Linux kernel 3.5-trunk from experimental. AFAIR kernel 3.4 did fine, but I will retest that if required. Please file a separate report. If your symptoms turn out to have

Bug#678215: [wheezy] USB mouse not recognized after resuming from suspend to, RAM

Hi folks, I have the exact same symptom here with Linux kernel 3.5-trunk from experimental. AFAIR kernel 3.4 did fine, but I will retest that if required. mschmitt@adrastea:~$ dmesg |egrep -i "hid|logitech|input" [0.694199] input: AT Translated Set 2 keyboard as /devices/platform/i8042/se

Bug#677727: [3.2->3.3 regression] mceusb: only every second keypress is recognised

hings: [Full bug log is at<http://bugs.debian.org/677727>.] On Mon, 2012-06-18 at 15:20 +0200, Michael Schmitt wrote: Hi Ben, mschmitt@ganymed:~$ dmesg |head -3 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.

Bug#677727: linux-image-3.4-trunk-686-pae: lirc / devinput remote control, only avery second keypress is recognised vs. sids 3.2 kernel where everything is ok

Hi Ben, mschmitt@ganymed:~$ dmesg |head -3 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.3.0-rc6-686-pae (Debian 3.3~rc6-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SM

Bug#677727: linux-image-3.4-trunk-686-pae: lirc / devinput remote control, only avery second keypress is recognised vs. sids 3.2 kernel where everything is ok

Am 16.06.2012 18:44, schrieb Ben Hutchings: On Sat, 2012-06-16 at 16:26 +0200, Michael Schmitt wrote: Package: linux-2.6 Version: 3.4.1-1~experimental.1 Severity: normal Dear Maintainers, with the current kernel from experimental only every second keypress is recognized on my ir remote

Bug#677727: linux-image-3.4-trunk-686-pae: lirc / devinput remote control, only avery second keypress is recognised vs. sids 3.2 kernel where everything is ok

Package: linux-2.6 Version: 3.4.1-1~experimental.1 Severity: normal Dear Maintainers, with the current kernel from experimental only every second keypress is recognized on my ir remote control. Reboot to kernel 3.2 from sid, all back to normal. I have no idea how the kernel could be responsible t

Bug#671689: [regression 3.2->3.3.4] sata_sil (on sil 3512) hotplug broken again

Am 18.05.2012 22:32, schrieb Jonathan Nieder: Please test the attached patch, for example following the instructions from [1]. (Found at [2].) Thanks, Jonathan [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official or the corresponding page in the debian-kernel-hand

Bug#671689: [regression 3.2->3.3.4] sata_sil (on sil 3512) hotplug broken again

Hi, sorry that it took so long, but now I have the time to test the hotplugging with a kernel >= 3.3 :) dmesg logs directly pasted here. So first, booted with powered down esata enclosure and now, poweron: [36997.268364] ata5: exception Emask 0x10 SAct 0x0 SErr 0x5 action 0xe frozen [

Bug#671689: [regression 3.2->3.3.4] sata_sil (on sil 3512) hotplug broken again

Hi Jonathan, Am 06.05.2012 08:18, schrieb Jonathan Nieder: Hi Michael, Michael Schmitt wrote: I tend to hotswap sata drives with a frameless-sata-hotswap-enclosure connected to a Silicon Image 3512 controller on a regular basis and have to report... broken again. :) The last 3.2 kernel did

Bug#671689: linux-image-3.3.0-trunk-686-pae: sata_sil (on sil 3512) hotplug broken again

Package: linux-2.6 Version: 3.3.4-1~experimental.1 Severity: normal Dear Maintainer, I tend to hotswap sata drives with a frameless-sata-hotswap-enclosure connected to a Silicon Image 3512 controller on a regular basis and have to report... broken again. :) The last 3.2 kernel did work, the first