Alberto Mardegan schreef op 21-4-2015 om 17:24:
> On 04/17/2015 11:48 AM, Allan Sandfeld Jensen wrote:
>> If we go with the QImageReader level, it could be an QImageIOHandler::Option,
>> and possibly be set different between JPEG and TIFF by default. The real
>> problem is what we decide the defaul
On Wednesday 22 April 2015 02:14:47 Kevin Kofler wrote:
> > CVE-2015-1860 GIF vulnerability
>
> Qt 3 appears to be VULNERABLE to this issue. I backported the fix from Qt 4:
> http://pkgs.fedoraproject.org/cgit/qt3.git/plain/qt-x11-free-3.3.8b-CVE-201
> 5-1860.patch
>
> Please note that Qt 3 is NO
Hi,
for those who still care about Qt 3, I looked into these vulnerabilities:
> CVE-2015-1858 BMP vulnerability
To the best of my knowledge, Qt 3 is NOT vulnerable to this issue, for the
following reason:
The security fix from Qt 4 changes the relevant code sequence in the BMP/DIB
reader from "p
On Tuesday 21 April 2015 22:32:51 René J.V. Bertin wrote:
> On Tuesday April 21 2015 21:23:13 Florian Bruhin wrote:
>
> Hi Florian,
>
> > I'm sure enough people here will be more than happy to help you with
> > that, but it'd be useful to know what exactly went wrong.
>
> It looked as if commits
On Tuesday April 21 2015 21:23:13 Florian Bruhin wrote:
Hi
> I'm sure enough people here will be more than happy to help you with
In the meantime, this site was more than happy to accept my patch - no gitting
or committing required :)
https://git.reviewboard.kde.org/r/123458/
R.
___
On Tuesday April 21 2015 21:23:13 Florian Bruhin wrote:
Hi Florian,
> I'm sure enough people here will be more than happy to help you with
> that, but it'd be useful to know what exactly went wrong.
It looked as if commits are no longer accepted, and that's after I configured
https upload becau
Hi René,
* René J.V. Bertin [2015-04-21 21:19:43 +0200]:
> On Tuesday April 21 2015 10:07:49 Thiago Macieira wrote:
>
> > Either they've been putting up with it or they've never noticed. Either
> > way,
> > that makes the bug not critical for a patch release.
>
> Possibly.
>
> I've just trie
On Tuesday April 21 2015 10:07:49 Thiago Macieira wrote:
> Either they've been putting up with it or they've never noticed. Either way,
> that makes the bug not critical for a patch release.
Possibly.
I've just tried to create a code review for the Qt 4.8 version of my patch.
Damn system refus
On Tuesday 21 April 2015 17:51:13 René J.V. Bertin wrote:
> > That's not the point.
>
> That *was* not my point. Which was: who knows how many users have been
> working around it, or putting up with it, as I used to do.
Either they've been putting up with it or they've never noticed. Either way,
On Tuesday April 21 2015 16:38:57 Olivier Goffart wrote:
> That's not the point.
That *was* not my point. Which was: who knows how many users have been working
around it, or putting up with it, as I used to do.
> As I said, i don't know the specific details of this patch, but the problem
> is
On 04/17/2015 11:48 AM, Allan Sandfeld Jensen wrote:
> If we go with the QImageReader level, it could be an QImageIOHandler::Option,
> and possibly be set different between JPEG and TIFF by default. The real
> problem is what we decide the default for JPEG should be now.
IMHO, QImageReader default
On Tuesday 21. April 2015 15:26:36 René J.V. Bertin wrote:
> On Tuesday April 21 2015 14:37:49 Olivier Goffart wrote:
> > If people have been living in the 80s for that long, they can wait until
> > the next minor release.
>
> If I decided to pick up on this it's because I had had enough of it tha
Perhaps worth mentioning that QPushButtons don't render on Android:
https://bugreports.qt.io/browse/QTBUG-45714
On 21/04/2015 15:20, Massimo Callegari wrote:
>>> Hi all!
>>> Downmerge from '5.4' to '5.4.2' is now done & all changes targeted to
>>> Qt5.4.2 release must be done
>>> in '5.4.2' br
>> Hi all!
>> Downmerge from '5.4' to '5.4.2' is now done & all changes targeted to
>> Qt5.4.2 release must be done
>> in '5.4.2' branch. From now on '5.4' is for possible Qt5.4.3 release.>> If
>> there is some open changes in '5.4' which should be in Qt5.4.2 please sent
>> re-targeting reques
On Tuesday April 21 2015 14:37:49 Olivier Goffart wrote:
> If people have been living in the 80s for that long, they can wait until the
> next minor release.
If I decided to pick up on this it's because I had had enough of it that about
none of the Medium/Semibold fonts I use in my GUIs were st
Hello,
I tried to add some code for opengl vbo creation inside my qt plugin.
I initialize vbo buffer inside the plugin and after it my program crash in
rendering vbo method on one glBindBuffer call.
this function is called when plugin start and after it my application crash on
a rendering meth
On Tuesday 21. April 2015 10:33:50 René J.V. Bertin wrote:
> On Tuesday April 21 2015 06:32:47 Heikkinen Jani wrote:
> >If you aren't fixing critical bug you should use '5.5' branch for that.
> >'5.4' is for possible 5.4.3 and not for any nice-to-have fixes, sorry.
> This is actually more than just
Hi,
I know I should ask this on the QC ML (but I'd prefer not to sign up for just
an occasional question like this):
Is there a (good) reason why DocumentManagerPrivate::linkWatcher() forces the
use of a polling watcher?
Mainly asking because I just noticed that this approach can lead to signi
Thanks!
FYI, 5.4.2 branch also seems to suffer from the same for qdbus when
compiling for Android,
in addition to 5.4 already mentioned in comments.
Added a comment to that effect.
Harri
On 20/04/2015 09:39, A. Klitzing wrote:
Hi there!
corresponding bug report: https://bugreports.qt.io/b
On Tuesday April 21 2015 06:32:47 Heikkinen Jani wrote:
>If you aren't fixing critical bug you should use '5.5' branch for that. '5.4'
>is for possible 5.4.3 and not for any nice-to-have fixes, sorry.
This is actually more than just a nice-to-have fix. It affects anyone doing any
kind of seriou
On 20/04/2015 20:17, Thiago Macieira wrote:
> On Monday 20 April 2015 20:09:49 Harri Pasanen wrote:
>> Does 5.4 have everything 5.4.2 has?
>>
>> Is there on-line some graphical view of the branches?
> Yes but not always. The 5.4 branch will eventually have the full 5.4.2
> release, but until it clo
21 matches
Mail list logo
