Em seg 09 jun 2014, às 18:28:20, Thiago Macieira escreveu:
> Em seg 09 jun 2014, às 12:06:10, Jacob Kroon escreveu:
> > Hi,
> >
> > I'm testing Qt 5.2.1 on a Wandboard using Yocto. If I build Qt5 without
> > udev support,
> >
> > I get 3 or 4 of these kernel warnings when I start my application:
Em seg 09 jun 2014, às 12:06:10, Jacob Kroon escreveu:
> Hi,
>
> I'm testing Qt 5.2.1 on a Wandboard using Yocto. If I build Qt5 without
> udev support,
> I get 3 or 4 of these kernel warnings when I start my application:
>
> idr_remove called for id=xxx which is not allocated.
> CPU: 0 P
Hi,
Gerrit (https://codereview.qt-project.org/) will be unavailable while we deploy
a new version.
The upgrade takes the current v2.2.1 based version to v2.7 based. Most of our
customized features stay: staging system for CI, one page review and deferred
changes. The topic review feature, very
Hi,
I'm testing Qt 5.2.1 on a Wandboard using Yocto. If I build Qt5 without
udev support,
I get 3 or 4 of these kernel warnings when I start my application:
idr_remove called for id=xxx which is not allocated.
CPU: 0 PID: 538 Comm: xxx Not tainted xxx
[<80013c7c>] (unwind_backtrace+0x
Hi there,
this quote originated from "Request for a sandbox area: Replicant", but
I did not want to hijack this discussion for something different.
On 05/31/2014 01:33 AM, Thiago Macieira wrote:
> One of the goals for QtDBus is to replace the need to have libdbus-1
> installed. We discussed this
I suspect one of these three changes in qtbase:
>Revert "Fixed duplicate QMoveEvent generated for each QWidget::move call"
> Fix selection by dragging after double click in QWidgetTextControl.
> QPlatformClipboard::emitChanged(): Do not emit signals when closing down.
Do those ring a bell for an
