Summary:
3.2.0-4-amd64 (Wheezy): Brightness controls work, get a popup indicator
showing the brightness should be changing, dmesg says ACPI fails to
switch the brightness.
3.6-trunk: Brightness controls work, get a popup indicator showing the
brightness should be changing, dmesg says ACPI f
Processing control commands:
> tag -1 patch
Bug #602966 [linux-2.6] linux-source-2.6.36: Oops while unmouning an USB key
with FAT filesystem
Added tag(s) patch.
--
602966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with probl
Processing commands for cont...@bugs.debian.org:
> tags 602966 + fixed-upstream
Bug #602966 [linux-2.6] linux-source-2.6.36: Oops while unmouning an USB key
with FAT filesystem
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
602966: h
Processing control commands:
> tag -1 moreinfo
Bug #701148 [src:linux] linux-image-3.7-trunk-amd64: Regression - brightness
controls do not work.
Added tag(s) moreinfo.
--
701148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701148
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Control: tag -1 moreinfo
On Fri, 2013-02-22 at 11:31 +0800, David M Smith wrote:
> Package: src:linux
> Version: 3.7.8-1~experimental.1
> Severity: important
>
>
> If I boot the linux-image-3.6-trunk-amd64, the brightness controls work just
> fine.
>
> Whenever I boot the linux-image-3.7-trunk-
Package: src:linux
Version: 3.7.8-1~experimental.1
Severity: important
If I boot the linux-image-3.6-trunk-amd64, the brightness controls work just
fine.
Whenever I boot the linux-image-3.7-trunk-amd64 my Fn+F4 and Fn+F5 brightness
controls on my laptop do not work.
According to xev, the events
On Thu, Feb 21, 2013 at 02:21:56PM -0500, David Magda wrote:
> On 2013-02-21 14:10, Ben Hutchings wrote:
> >The squeeze kernel is unfortunately missing support for a lot of
> >current hardware (notably graphics but also some networking chips) so
> >many people are running later kernel versions. I
On 2013-02-21 14:10, Ben Hutchings wrote:
The squeeze kernel is unfortunately missing support for a lot of
current hardware (notably graphics but also some networking chips) so
many people are running later kernel versions. I would love to fix
some of these but I have my hands full and I can rar
On Thu, Feb 21, 2013 at 11:39:04AM -0700, Troy Heber wrote:
> On 02/21/13 09:22, David Magda wrote:
>
> > >>If it is the "crash", can we either get:
> > >>(a) the patch added to squeeze package, and/or
> > >>(b) wheezy crash backported.
> >
> > Any news on whether (a) or (b) will be done? Or is t
On 02/21/13 09:22, David Magda wrote:
> >>If it is the "crash", can we either get:
> >>(a) the patch added to squeeze package, and/or
> >>(b) wheezy crash backported.
>
> Any news on whether (a) or (b) will be done? Or is there a (c) that
> hasn't been considered perhaps?
I haven't tried to push
#
# bts-link upstream status pull for source package src:linux
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #697029 (http://bugs.debian.org/697029)
# Bug title: linux-image-3.2.0-4-amd64: i915
#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #602966 (http://bugs.debian.org/602966)
# Bug title: linux-source-2.6.36: Oops while
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package linux-2.6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian
On 2013-02-12 09:07, David Magda wrote:
In /usr/share/doc/kdump-tools/README.Debian the following text appears:
4. Debug Kernel
You *should* have a debug kernel in order for makedumpfile to process
the vmcore file. Without a debug kernel, the transfer process is
reduced to using
On 2013-01-31 00:17, Ben Hutchings wrote:
On Wed, 2013-01-30 at 14:50 -0500, David Magda wrote:
The upstream bug report is at:
https://www.redhat.com/archives/crash-utility/2011-June/thread.html#0
http://people.redhat.com/anderson/crash_patches/5.1.5-to-5.1.6.patch
If it is the "crash",
while my BIOS/UEFI reports a battery charge capacity of 92% for my
notebook-
battery, upower still reports a charge capacity of 100% (AFAIK
upower gets this
information from the kernel - I believe this to be a kernel ACPI
bug).
The kernel driver doesn't do anything very interesting so it's
ac
Package: src:linux
Version: 3.7.3-1~experimental.1
Followup-For: Bug #700333
Dear Maintainer,
* What led up to the situation?
Trying to do pm-hibernate with/without uswsusp installed. A black
unresponsive screen, with no way to interrupt except forced turn
off. This happens with th
18 matches
Mail list logo
