| Summary: | [QT] fotowall segfaults with "Painter not active" | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Qing He <qing.he> |
| Component: | meta-yocto | Assignee: | Kai Kang <kai.kang> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, jiajun.xu, ke.yu, kevin.tian, liang.li2, liangliang.wang, poky.bs.watcher, poky.watcher, richard.purdie, sgw, Xiaofeng.yan, yi.zhao |
| Version: | 1.0 | ||
| Target Milestone: | 1.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | will be fixed by Aug24/2011 | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 280 | ||
|
Description
Qing He
2010-09-21 00:57:32 UTC
the below error message:
QNativeImage: Unable to attach to shared memory segment.
is caused by a likely invalid rect size, QNativeImage is a recent addition in Qt, it used shm to map the image, the call trace shows something like:
#0 XShmCreateImage()
#1 QNativeImage(this=0x8e5a60, width=6418448, height=432...)
#2 QRasterWindowSurface::prepareBuffer(...)
...
the width parameter is too high and causing problems, considering the depth, this needs to shmget about 11G address space, which fails shmget and returns EINVAL.
Still don't know where this weird parameter comes from
copied the fotowall binary of targets to my dev machine (x86_64), it runs without crashes, so it's likely not the problem of the app. copied Qt libraries in my dev machine into the target (libQtGui, libQtCore, libQtXml, libQtSvg, libQtNetwork), with some necessary dependencies (libasound, libpcre.so.3), fotowall also crashes, so it's probably not the problem of Qt as well. Googling around shows some other unrelated cases that report "painter not active", (e.g. https://bugs.kde.org/show_bug.cgi?id=189059), no root cause can be found, but some suspected "probably a graphics driver issue", but Xorg.0.log doesn't show anything about it. I tried also to replace vmware driver to vesa, but it was not successful (X can't boot up) Has anyone tried running 64bit X and Qt on real hardware or with drivers other than vmware? Suggesting to lower the importance and delay to 1.0. Severity: 1. fotowall is a test application for QT, the issue shown in this bug hasn't been observed in other applications so far. 2. the bug only happens on x86_64 (and possibly with only vmware_drv.so) Also suggesting to test several other QT apps to see whether this issue only happens to fotowall or is more widespread. The bug is complex and has risk to be fixed within 0.9 M4 1. It's difficult if not impossible to trace the origin from crash point due to the event driven nature of QT 2. The root cause doesn't necessarily lie in QT 3. In order to report it to upstream , we may need to reproduce it outside poky (In reply to comment #2) > copied the fotowall binary of targets to my dev machine (x86_64), it runs > without crashes, so it's likely not the problem of the app. > copied Qt libraries in my dev machine into the target (libQtGui, libQtCore, > libQtXml, libQtSvg, libQtNetwork), with some necessary dependencies (libasound, > libpcre.so.3), fotowall also crashes, so it's probably not the problem of Qt as > well. > Googling around shows some other unrelated cases that report "painter not > active", (e.g. https://bugs.kde.org/show_bug.cgi?id=189059), no root cause can > be found, but some suspected "probably a graphics driver issue", but Xorg.0.log > doesn't show anything about it. I tried also to replace vmware driver to vesa, > but it was not successful (X can't boot up) > Has anyone tried running 64bit X and Qt on real hardware or with drivers other > than vmware? Qing, could you post the last question to the yocto list as only limited people are monitoring bugzilla? For disabling vmware driver, I think you also need some option tweak in qemu side, e.g. using stdvga... (In reply to comment #3) > Suggesting to lower the importance and delay to 1.0. > Severity: > 1. fotowall is a test application for QT, the issue shown in this bug hasn't > been observed in other applications so far. > 2. the bug only happens on x86_64 (and possibly with only vmware_drv.so) > Also suggesting to test several other QT apps to see whether this issue only > happens to fotowall or is more widespread. Have you tried other QT apps? Ke may better answer this question since he chose those QT demo apps... > The bug is complex and has risk to be fixed within 0.9 M4 > 1. It's difficult if not impossible to trace the origin from crash point due to > the event driven nature of QT > 2. The root cause doesn't necessarily lie in QT > 3. In order to report it to upstream , we may need to reproduce it outside poky (In reply to comment #4) > For disabling vmware driver, I think you also need some option tweak in qemu > side, e.g. using stdvga... Yes, I tried "-vga std" and removing the parameter (defaults to -vga cirrus), it still showed nothing (but in graphical mode though) Can we test some other QT apps at least? (In reply to comment #7) > Can we test some other QT apps at least? we can try qmmp, qtdemo. |