Closed Bug 636008 Opened 9 years ago Closed 9 years ago

[Maemo6] Fennec crashes on startup, with Xlib error.

Categories

(Core Graveyard :: Widget: Qt, defect)

ARM
Maemo
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: romaxa, Assigned: romaxa)

Details

Attachments

(2 files)

Attempt to run fennec on Maemo6 (HW acceleration disable) finished with crash.

./fennec -url http://ya.ru
Not loading meegotouch-qt-style for meegotouch app.
void MInputContext::connectToDBus() 
MInputContext: void GlibDBusIMServerProxy::connectToDBus() 
MInputContext: in virtual QString MInputContext::identifierName() 
Your program has been terminated because it entered a critical section
in Xlib simultaneously from more than one thread. To avoid this, you
should call XInitThreads before doing any other Xlib calls.
Aborted (core dumped)

4  0x3d6771d8 in abort () at abort.c:88
#5  0x3e02dcc0 in xmutex_lock_checked (lock=<value optimized out>) at ../../src/locking.c:129
#6  0x3e02dd44 in _XLockDisplay (dpy=0x3fc77000) at ../../src/locking.c:490
#7  0x3e03ef60 in XSynchronize (dpy=0x3fc77000, onoff=1031327744) at ../../src/Synchro.c:47
#8  0x3ade0430 in X11Error (display=0x3fc77000, event=0x3fa5c750)
    at toolkit/xre/nsX11ErrorHandler.cpp:136
#9  0x3e0460a8 in _XError (dpy=0x3fc77000, rep=0x409c3460) at ../../src/XlibInt.c:1577
#10 0x3e043d10 in handle_error (dpy=0x3fc77000, err=0x409c3460, in_XReply=6) at ../../src/xcb_io.c:167
#11 0x3e043d48 in handle_response (dpy=0x3fc77000, response=0xa1d, in_XReply=6) at ../../src/xcb_io.c:321
#12 0x3e0443e4 in _XReply (dpy=0x3fc77000, rep=<value optimized out>, extra=<value optimized out>, discard=<value optimized out>)
    at ../../src/xcb_io.c:626
#13 0x3e03eeac in XSync (dpy=0x3fc77000, discard=0) at ../../src/Sync.c:44
#14 0x3e03f00c in _XSyncFunction (dpy=0x0) at ../../src/Synchro.c:35
#15 0x3e0316e8 in XSetWindowBackgroundPixmap (dpy=0x3fc77000, w=0, pixmap=0) at ../../src/PmapBgnd.c:45
#16 0x3ba521bc in nsWindow::createQWidget (this=0x41241100, parent=<value optimized out>, aInitData=<value optimized out>)
---Type <return> to continue, or q <return> to quit---
    at widget/src/qt/nsWindow.cpp:2610
#17 0x3ba52380 in nsWindow::Create (this=0x41241100, aParent=0x0, aNativeParent=0x0, aRect=..., aHandleEventFunction=
    0x3b8b2a50 <nsWebShellWindow::HandleEvent(nsGUIEvent*)>, aContext=0x0, aAppShell=0x404fb978, aToolkit=0x0, aInitData=0xaefb7364)
    at widget/src/qt/nsWindow.cpp:2177
#18 0x3b8b1d70 in nsWebShellWindow::Initialize (this=0x41342200, aParent=0x0, aOpener=<value optimized out>, aShell=<value optimized out>, aUrl=
    0x0, aInitialWidth=1, aInitialHeight=1, aIsHiddenWindow=0, widgetInitData=...)
    at xpfe/appshell/src/nsWebShellWindow.cpp:219
Attachment #514321 - Flags: review?(mozilla)
Attached file Full backtrace
Assignee: nobody → romaxa
Comment on attachment 514321 [details] [diff] [review]
Patch (make Xlib code less sensitive to Qt/X behaviour changes )

makes sense
Attachment #514321 - Flags: review?(mozilla) → review+
http://hg.mozilla.org/mozilla-central/rev/3c68f42b4682
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.