Hi Roland,
thanks for the report! I'm gonna look into it asap.

Sandro

On 9/9/07, Roland Rosenfeld <[EMAIL PROTECTED]> wrote:
> Package: xsysinfo
> Version: 1.7-6
> Version: 1.7-5
> Severity: normal
> Tag: lenny, sid
>
> After upgrading from etch to lenny (including a Kernel upgrade from
> 2.6.18 to 2.6.21) xsysinfo stopped working on my system but outputs
> only a message:
>
> $ xsysinfo
> get_total_procs: Success
>
> As a workaround I added the option -noload which lets me start the
> program, but suppresses the Load: gauge.
>
> Downgrading xsysinfo to 1.7-5 from etch doesn't change the broken
> behavior.
>
> -- System Information:
> Debian Release: lenny/sid
>   APT prefers testing
>   APT policy: (600, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 2.6.21-2-amd64 (SMP w/1 CPU core)
> Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/bash
>
> Versions of packages xsysinfo depends on:
> ii  libc6                       2.6.1-1      GNU C Library: Shared libraries
> ii  libice6                     2:1.0.4-1    X11 Inter-Client Exchange library
> ii  libsm6                      2:1.0.3-1+b1 X11 Session Management library
> ii  libx11-6                    2:1.0.3-7    X11 client-side library
> ii  libxaw7                     2:1.0.4-1    X11 Athena Widget library
> ii  libxext6                    1:1.0.3-2    X11 miscellaneous extension 
> librar
> ii  libxmu6                     1:1.0.3-1    X11 miscellaneous utility library
> ii  libxpm4                     1:3.5.7-1    X11 pixmap library
> ii  libxt6                      1:1.0.5-3    X11 toolkit intrinsics library
>
> xsysinfo recommends no packages.
>
> -- no debconf information
>
> Tschoeeee
>
>         Roland
>
> --
>  * [EMAIL PROTECTED] * http://www.spinnaker.de/ *
>
>
>


-- 
Sandro Tosi (aka Morpheus, matrixhasu)
My (little) site: http://matrixhasu.altervista.org/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to