Update: so far the patched version hasn't crashed on my system. No
guarantees but it looks like it's working
On Sep 20, 2017 1:24 AM, "Ben Gladstone" wrote:
> Oh whoops reading fail, I missed that part. Thanks!
>
> On Sep 20, 2017 1:22 AM, "Roman Mamedov"
Oh whoops reading fail, I missed that part. Thanks!
On Sep 20, 2017 1:22 AM, "Roman Mamedov" wrote:
> On Wed, 20 Sep 2017 01:16:08 -0700
> Ben Gladstone wrote:
>
> > I'm just waiting to see if it crashes in the next week or so. Have you
> tried
> > that p
gt; On Wed, 20 Sep 2017 00:49:06 -0700
> Ben Gladstone wrote:
>
> > I unfortunately haven't been able to identify a pattern, but every
> couple of days mhddfs
> > crashes, giving me the message "The transport endpoint is not
> connected." when I try to access
Package: mhddfs
Version: 0.1.39+nmu1+b1
Severity: important
Tags: patch
Dear Maintainer,
I unfortunately haven't been able to identify a pattern, but every couple of
days mhddfs
crashes, giving me the message "The transport endpoint is not connected." when
I try to access
anything mounted by mh
ode to know what exactly is wrong, but I think I found where to
look!
On Thu, Jun 15, 2017 at 1:16 AM, Ben Gladstone
wrote:
> Ah you're right! I hadn't tried it via the setup menu but it's behaving
> the same way for me that it is for you. Definitely has something to do with
&g
Ah you're right! I hadn't tried it via the setup menu but it's behaving the
same way for me that it is for you. Definitely has something to do with F5.
Thanks, I'm curious to see what it turns out to be
On Jun 15, 2017 1:11 AM, "Daniel Lange" wrote:
> A
modes=2 2 2 1 1 1 1 \n", 693) = 693
This doesn't tell us much we didn't already know, except that it proves
that it actually is htop modifying the file like that and not some other
program. The big question is still: why?
This is a super goofy issue and isn't really making sens
I agree it's really strange and it doesn't make sense to me either why it
would be doing that. I thought maybe it had something to do with my F5 key,
maybe if there was another keybinding I forgot about. But nope, it has the
same behavior when I use the mouse to click on tree mode too. I'll play
ar
Whoops forgot to hit reply-all, resending:
Alright I just tried that and I'm still seeing the strange behavior. I
deleted htoprc and opened htop, then quit. I've attached the htoprc file it
created as "htoprc.start"
Then, I reopened htop and added a "CPU 1" meter, then quit htop. I've
attached th
Package: htop
Version: 2.0.2-1~bpo8+1
Severity: normal
Dear Maintainer,
I noticed this bug upon upgrading from htop in Debian stable to htop in Debian
jessie-backports.
In the version in stable, there wasn't a meter for "All CPUs", so I built my
own by adding meters
for CPU1,2,3,4,5,6,7,8 all
10 matches
Mail list logo
