It still hasn't been determined if this is confirmed to be a Devuan
issue or not, so Firefox needs to be ruled out.
No it's not supposed to be a solution, it's just information-gathering.
Welcome to software testing; yes, we turn things off then on again.
On Fri, 27 Apr 2018 18:37:22 +0100
I'd agree, but then the profile has to be deleted after and I didn't
want to bother checking to see if manager does that correctly.
On Fri, 27 Apr 2018 20:42:06 +0200
Florian Zieboll wrote:
> It's even more easy: Just start firefox with the "--ProfileManager"
> option and
On Fri, 27 Apr 2018 10:00:50 -0700
spiralofhope wrote:
> The most brute-force test is to create a whole new user profile:
>
> # (exit firefox)
> mv ~/.mozilla ~/.mozilla-backup
> # (launch, re-test)
> # (exit firefox)
> rm -rf ~/.mozilla
> mv
Isn't it more likely that part of Firefox needs to be paged in, and the
local disk is slow? I see this on a few systems, once in a while.
On Fri, Apr 27, 2018 at 10:37 AM, KatolaZ wrote:
> On Fri, Apr 27, 2018 at 10:00:50AM -0700, spiralofhope wrote:
> > The most
On Fri, Apr 27, 2018 at 10:00:50AM -0700, spiralofhope wrote:
> The most brute-force test is to create a whole new user profile:
>
> # (exit firefox)
> mv ~/.mozilla ~/.mozilla-backup
> # (launch, re-test)
> # (exit firefox)
> rm -rf ~/.mozilla
> mv ~/.mozilla-backup ~/.mozilla
>
The most brute-force test is to create a whole new user profile:
# (exit firefox)
mv ~/.mozilla ~/.mozilla-backup
# (launch, re-test)
# (exit firefox)
rm -rf ~/.mozilla
mv ~/.mozilla-backup ~/.mozilla
On Fri, 27 Apr 2018 15:55:36 +0200
Edward Bartolo wrote:
> Hi
On 27/04/2018, Florian Zieboll wrote:
> Am 27. April 2018 15:55:36 MESZ schrieb Edward Bartolo :
>
>> Does anyone know of anything that can tame Firefox not to gobble all
>> my CPU's cycles just to display some letters?
>
>
> I'd have a look at my lng list
Am Freitag 27 April 2018 schrieb Florian Zieboll:
> Am 27. April 2018 15:27:46 MESZ schrieb Stefan Krusche
:
> > It's the default for the default distribution you are using, I think.
> > You can change that in /etc/apt/preference with pinning.
>
> Yeah, thanks - I was
Am 27. April 2018 15:55:36 MESZ schrieb Edward Bartolo :
> Does anyone know of anything that can tame Firefox not to gobble all
> my CPU's cycles just to display some letters?
I'd have a look at my lng list of add-ons^^
lg,
f.
--
[message sent mobile]
Am 27. April 2018 15:13:28 MESZ schrieb KatolaZ :
> it's determined in the repo config, and apt acquires this in formation
> from the Release files. In particular, if the following fields are
> present in the Release file of a suite:
>
> NotAutomatic: yes
>
Hi All,
I am lately noticing that while typing on youtube to post my comments
the types letters take several seconds to become visible. I comment on
some youtube channels dealing with electronics.
I am using ASCII and firefox version 52.7.3.
Does anyone know of anything that can tame Firefox
Am 27. April 2018 15:27:46 MESZ schrieb Stefan Krusche
:
> It's the default for the default distribution you are using, I think.
> You can change that in /etc/apt/preference with pinning.
Yeah, thanks - I was just wondering where this default is defined, if not in
Am Freitag 27 April 2018 schrieb Florian Zieboll:
> obviously I hit "send" too fast, as I couldn't find that configuration
> anywhere under "/etc/apt/". Where is this behavior defined, resp. how
> would I change it? (Just in case...)
It's the default for the default distribution you are using, I
On Fri, Apr 27, 2018 at 02:24:36PM +0200, Florian Zieboll wrote:
> On Fri, 27 Apr 2018 14:13:15 +0200
> Florian Zieboll wrote:
>
> > On Fri, 27 Apr 2018 10:07:02 +0100
> > KatolaZ wrote:
> >
> > >
> > > Pinning should not be needed any more, since the
On 04/27/2018 02:23 AM, Steve Litt wrote:
[snip]
First thing I'd do is test the RAM and the disk. Easy to do, and it
would be real shame to chase your video driver tail for a month when
it was bad RAM. I'm pretty sure bad RAM can cause almost anything: Why
not rule it out early.
[snip]
Thanks
On Fri, 27 Apr 2018 14:13:15 +0200
Florian Zieboll wrote:
> On Fri, 27 Apr 2018 10:07:02 +0100
> KatolaZ wrote:
>
> >
> > Pinning should not be needed any more, since the *-backports suites
> > are at prio 100 by default (it was not like that in the
On Fri, 27 Apr 2018 10:31:43 +0200
Florian Zieboll wrote:
> If you really want to have the "backports" version, in the worst case,
> you'll have to specify the needed version for every package in the
> dependency chain (...)
Hallo Lars,
in the meantime i remembered that
On Fri, 27 Apr 2018 10:07:02 +0100
KatolaZ wrote:
> On Fri, Apr 27, 2018 at 10:31:43AM +0200, Florian Zieboll wrote:
> >
> > On Thu, 26 Apr 2018 21:05:41 +0300
> > Lars Noodén wrote:
> >
> [...]
> >
> > Not sure if you are aware that your
On Fri, Apr 27, 2018 at 10:31:43AM +0200, Florian Zieboll wrote:
>
> On Thu, 26 Apr 2018 21:05:41 +0300
> Lars Noodén wrote:
>
> > # apt-cache show nvidia-driver-bin | head -n 3
> > Package: nvidia-driver-bin
> > Source: nvidia-graphics-drivers
> > Version:
On Thu, 26 Apr 2018 21:05:41 +0300
Lars Noodén wrote:
> # apt-cache show nvidia-driver-bin | head -n 3
> Package: nvidia-driver-bin
> Source: nvidia-graphics-drivers
> Version: 390.48-2~bpo9+1
Not sure if you are aware that your system tries to pull the package
from the
20 matches
Mail list logo