I just installed wmnetload again and it seems to work for me now. I
haven't tested it extensively, but when I reported the bug (3 years
ago) it wouldn't start at all. I have to say that I pretty much lost
interest the moment it didn't work, but figured filing the bug might
be useful.
Now that I think about it, the server is entirely different now, so
perhaps this isn't too surprising. Still wmnetload 1.3-1.1 but now
basically all lenny, Linux turing 2.6.26-1-amd64 #1 SMP Fri Mar 13
17:46:45 UTC 2009 x86_64 GNU/Linux.
Scott
2009/4/9 Rogério Brito <rbr...@ime.usp.br>:
> Hi.
>
> On May 27 2008, Alexandre Lymberopoulos wrote:
>> The program causes a segmentation fault when X starts and the device
>> to be monitored is not up. When the monitored device is up wmnetload
>> seems to work perfectly.
>
> I'm also seeing the segfaults, but I can't pinpoint when they happen
> precisely. I have many interfaces and sometimes they are working,
> sometimes not and wmnetload seems to work ok.
>
> What I *do* see, though, is that it, suddenly dies "out of the blue",
> when I'm using my system. My configuration is:
>
> * sid, up to date (everyday);
> * fluxbox;
> * amd64, with 2 cores and bleeding-edge kernels from kernel.org.
>
> Can we have any response to this thread? The bug has been filed for
> quite some time, without *any* action being taken.
>
>
> Thanks, Rogério Brito.
>
> --
> Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
> http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
> Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
>
>
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
