Your message dated Tue, 4 Aug 2009 09:35:35 +0530
with message-id <[email protected]>
and subject line Re: Bug#527130: starting with kernel 2.6.29, xosview uses 50%
cpu continuously
has caused the Debian Bug report #527130,
regarding starting with kernel 2.6.29, xosview uses 50% cpu continuously
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
527130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527130
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xosview
Version: 1.8.2-10
Severity: important
Starting with kernel 2.6.29, xosview uses 50% cpu of one core of the
system, continuously. It does not exhibit this problem with 2.6.28 or
any previous kernel version.
-- System Information:
Debian Release: 4.0
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.29.2-andy
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages xosview depends on:
ii libc6 2.3.6.ds1-13etch8 GNU C Library: Shared libraries
ii libgcc1 1:4.1.1-21 GCC support library
ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3
ii libx11-6 2:1.0.3-7 X11 client-side library
xosview recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.8.3+debian-14
On Tue, Aug 4, 2009 at 2:46 AM, Andrew Sharp<[email protected]> wrote:
>> Can you please check this bug (#527130) with latest kernel? xosview is
>> working fine with my AMD64 system.
>
> Just built and tested 2.6.30.4 and it's working, hooray. Let's just
> assume that Lenny xosview is also working and declare victory.
Thanks for testing. I am closing this bug since its solved with newer kernel
> Thanks for pinging me with followups ~:^)
:)
--
Cheers,
Kartik Mistry | 0xD1028C8D | IRC: kart_
Debian GNU/Linux Developer
Blogs: {ftbfs, kartikm}.wordpress.com
--- End Message ---
