Your message dated Tue, 5 Jun 2007 13:44:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#302424: About your bug 302424 "ksysguardd doesn't start
automatically" in Debian BTS
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 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ksysguardd
Version: 4:3.4.0-0pre2
Severity: normal
Tags: experimental
When I start the ksysguard panel applet, it can't connect to ksysguardd,
because ksysguardd isn't running. I have to start it manually.
In KDE 3.3, I don't remember ever having to start ksysguardd myself, or
wonder whether it had started or how to start it. I just ran ksysguard,
and it worked. Apparently ksysguardd was already running, or maybe
ksysguard started it.
I could write a script to start ksysguardd at boot, if that's what's needed.
But shouldn't it arrange to start itself without my intervention?
Thanks,
Andrew.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages ksysguardd depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libsensors3 1:2.9.0-18 library to read temperature/voltag
-- no debconf information
--- End Message ---
--- Begin Message ---
thanks,
Closing this bug.
regards
Olivier
2007/5/25, Andrew Schulman <[EMAIL PROTECTED]>:
> So please
> respond to this mail and tell us if:
>
> - you are still experiencing this bug (adding in what version)
> - the bug was already fixed (if known, in which version),
> - or if you have extra information on how reproduce this bug.
As I reported on October 6, I solved this problem by resetting my ksysguard
config. I can't speak to Chris Moore's comment, but as far as I'm
concerned, the bug is done and should be closed.
Thanks,
Andrew.
--- End Message ---
