On Wed, Feb 19, 2020 at 06:26:56PM +0200, Konstantin Ritt wrote:
> Should we ever try to work around issues caused by broken CPUs?
Yes.
Because "CPU is broken" one way or the other is rather the common
case. Declining to work as best as reasonably feasible in this
situation might as well end up
On Wednesday, 19 February 2020 08:26:56 PST Konstantin Ritt wrote:
> Should we ever try to work around issues caused by broken CPUs? Maybe we
> should warn the user instead (with big red banner) and decline to install
> anything at all?
That was the thinking on the first task. We thought it was a
> > > Judging from the screenshots, it's the latest and greatest version
> > > of the Qt installer (qt-opensource-windows-x86-5.14.1.exe) [1]
> >
> > Okay, but what version of Qt is the Qt Installer using? Installer
> > team, can you check?
> >
>
> Looking into the binary I've found:
>
> "Build d
> >
> > Judging from the screenshots, it's the latest and greatest version of
> > the Qt installer (qt-opensource-windows-x86-5.14.1.exe) [1]
>
> Okay, but what version of Qt is the Qt Installer using? Installer team, can
> you
> check?
>
Looking into the binary I've found:
"Build date: Jan 8
On woensdag 19 februari 2020 00:51:12 CET Thiago Macieira wrote:
> Also https://bugreports.qt.io/browse/QTBUG-70606, which is when I reported
> the
> problem to AMD, but we did not introduce a workaround since we didn't know it
> was this widespread.
We for sure encountered it very, very often
Just for clarity: systemd has worked around this issue back in 2019 IIRC ,
once the issue has been widely reported and confirmed. Did that allow the
user to boot his linux? Yes, the user is now able to boot into his shiny
and fast (yet insecure and highly vulnerable) operation system. Months
later,
Should we ever try to work around issues caused by broken CPUs? Maybe we
should warn the user instead (with big red banner) and decline to install
anything at all?
> (or buy Intel)
Or let's maybe also try to work around Meltdown and Spectre on i, just for
symmetry? ;)
Regards,
Konstantin
ср,
On Tuesday, 18 February 2020 05:36:56 PST Sze Howe Koh wrote:
> > Christian Kandeler (18 February 2020 12:59) replied
> >
> > > Probably the same as https://bugreports.qt.io/browse/QTBUG-77375.
Also https://bugreports.qt.io/browse/QTBUG-70606, which is when I reported the
problem to AMD, but we
On Tue, 18 Feb 2020 at 20:57, Edward Welbourne wrote:
>
> On Tue, 18 Feb 2020 19:35:53 +0800
> Sze Howe Koh wrote:
> >> See
> >> https://forum.qt.io/topic/111473/maintenance-tool-error-cannot-open-file-for-writing-no-error/
>
> I note that the code quoted is using rand(); the code in QTemporary
On Tue, 18 Feb 2020 19:35:53 +0800
Sze Howe Koh wrote:
>> See
>> https://forum.qt.io/topic/111473/maintenance-tool-error-cannot-open-file-for-writing-no-error/
I note that the code quoted is using rand(); the code in QTemporary file
switched to using QRandomGenerator at 5.10.0; that's what now p
On Tue, 18 Feb 2020 19:35:53 +0800
Sze Howe Koh wrote:
> See
> https://forum.qt.io/topic/111473/maintenance-tool-error-cannot-open-file-for-writing-no-error/
Probably the same as https://bugreports.qt.io/browse/QTBUG-77375.
> Is this worth a post on the Qt Blog? I foresee many frustrated and
>
See
https://forum.qt.io/topic/111473/maintenance-tool-error-cannot-open-file-for-writing-no-error/
In summary, a bad BIOS prevents QTemporaryFile from generating
different filenames each run. The Qt Installer encounters name
conflicts and produces a cryptic error message:
Cannot open file ""
12 matches
Mail list logo
