Package: linux-image-2.6.23-1-686
Version: 2.6.23-2
Severity: normal
On my Thinkpad X20, frequently after booting my usb mouse responds in a
very sluggish and jumpy manner, making it basically unuseable. At the
same time, the stick mouse (which I hate using) works normally.
This has been going o
On Thu, 24 Jan 2008, Lennart Sorensen wrote:
> Any way to tell the bug system to move a message to another bug? Or to
> delete it so I can send it to the right bug?
you have to repost to the other one.
but be warned oops or bugs with tainted kernels don't get love here
unless they are reproduced
Your message dated Thu, 24 Jan 2008 21:58:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#457992: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#440807: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#455892: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#454797: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#420245: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426124: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426124: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#455566: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#458899: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#433204: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#456416: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#454776: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#458142: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#458312: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 24 Jan 2008 21:58:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#457562: fixed in linux-2.6 2.6.24~rc8-1~experimental.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Accepted:
linux-2.6_2.6.24~rc8-1~experimental.1.diff.gz
to pool/main/l/linux-2.6/linux-2.6_2.6.24~rc8-1~experimental.1.diff.gz
linux-2.6_2.6.24~rc8-1~experimental.1.dsc
to pool/main/l/linux-2.6/linux-2.6_2.6.24~rc8-1~experimental.1.dsc
linux-2.6_2.6.24~rc8.orig.tar.gz
to pool/main/l/linux-2.
Package: linux-image-2.6.23-1-686
Version: 2.6.23-2
Severity: important
For several months (I think ever since I switched from 2.6.17 to
2.6.18 -- prior to that it was rock solid), I've been getting fairly
regular Oops in ext3_clear_inode, after which the entire system
becomes wedged (ping works,
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.12
> severity 462229 important
Bug#462229: sata - sata_nv - sata link fails on heavy load
Severity set to `important' from `critical'
> reassign 462229 linux-2.6
Bug#462229: sata - sata_
On Thu, Jan 24, 2008 at 04:08:23PM +0100, maximilian attems wrote:
> On Thu, Jan 24, 2008 at 09:43:03AM -0500, Lennart Sorensen wrote:
> > There is no reason what so ever to say it is a driver bug.
> >
>
> no idea what bug you are reffering to but your message seems
> in no way to correlate with
On Thu, Jan 24, 2008 at 09:43:03AM -0500, Lennart Sorensen wrote:
> There is no reason what so ever to say it is a driver bug.
>
no idea what bug you are reffering to but your message seems
in no way to correlate with 461182 that still misses quite some
output in order to be useful.
--
To UN
There is no reason what so ever to say it is a driver bug.
kwin crashes with the nvidia driver. kwin should not crash no matter
what garbage the driver may return to it. It can detect that it got bad
data back and give an error, but a crash is simply sloppy coding and
hence a bug in kwin. There
I got the same type of error on a sunblade 150 :
kernel: Kernel unaligned access at TPC[10201e60] tcp_packet+0x5fc/0xcb4
[ip_conntrack]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
24 matches
Mail list logo
