Hi,
After the update to FF 56.0 was done, I created a new profile and
added my previous addons.
Now, the FF opens in half screen width everytime I start it. From what
I remember, the previous size when closing FF is the next size when
openening FF - now it seems to be a somehow hardcoded value.
You might try reinstalling it (possibly downloading it again, some bit patterns
tend to damage so as to preserve the checksums, seen it, took 4 downloads to
get a good one before, despite everything looking good, and the same issue 3
times!).
There's a possibility you confused it copying thin
On 10/02 09:08, mad.scientist.at.la...@tutanota.com wrote:
> You might try reinstalling it (possibly downloading it again, some bit
> patterns tend to damage so as to preserve the checksums, seen it, took 4
> downloads to get a good one before, despite everything looking good, and the
> same iss
Am Montag, 2. Oktober 2017, 10:22:37 CEST schrieb tu...@posteo.de:
> Hi,
>
> After the update to FF 56.0 was done, I created a new profile and
> added my previous addons.
>
> Now, the FF opens in half screen width everytime I start it. From what
> I remember, the previous size when closing FF is
On 10/02 10:31, Marc Joliet wrote:
> Am Montag, 2. Oktober 2017, 10:22:37 CEST schrieb tu...@posteo.de:
> > Hi,
> >
> > After the update to FF 56.0 was done, I created a new profile and
> > added my previous addons.
> >
> > Now, the FF opens in half screen width everytime I start it. From what
>
Ok, so just got the notice that Linode is discontinuing their support
for Xen, and forcing everyone to migrate their VMs to KVM.
Of course this comes at the worst possible time for me, when I'm out of
the country, and won't be back before the deadline (the 9th).
I have a week, so am trying to do
> On 2 Oct 2017, at 18:30, Tanstaafl wrote:
>
> One thing I do seem to recall is there was somewhere that I had to
> define Xen as the virtualization environment being used, but I can't
> remember where I did that. Was that in the kernel config? If so, their
> tool should (hopefully) handle that
On 10/2/2017, 2:39:51 PM, Stroller wrote:
>
>> On 2 Oct 2017, at 18:30, Tanstaafl wrote:
>>
>> One thing I do seem to recall is there was somewhere that I had to
>> define Xen as the virtualization environment being used, but I can't
>> remember where I did that. Was that in the kernel config? I
On 10/2/2017, 4:03:37 PM, Tanstaafl wrote:
> On 10/2/2017, 2:39:51 PM, Stroller wrote:
>>
>>> On 2 Oct 2017, at 18:30, Tanstaafl wrote:
>>>
>>> One thing I do seem to recall is there was somewhere that I had to
>>> define Xen as the virtualization environment being used, but I can't
>>> remember
Hello friends!
On Mon, Oct 2, 2017 at 3:03 PM, Tanstaafl wrote:
> On 10/2/2017, 2:39:51 PM, Stroller wrote:
>>
>>> On 2 Oct 2017, at 18:30, Tanstaafl wrote:
>>>
>>> One thing I do seem to recall is there was somewhere that I had to
>>> define Xen as the virtualization environment being used, bu
hi
On 10/02/2017 08:30 PM, Tanstaafl wrote:
> One thing I do seem to recall is there was somewhere that I had to
> define Xen as the virtualization environment being used, but I can't
> remember where I did that. Was that in the kernel config? If so, their
> tool should (hopefully) handle that cha
11 matches
Mail list logo
