** Changed in: qt
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
To manage
** Changed in: qt
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
To manage
** Changed in: qt
Status: New = Confirmed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
To manage
** Changed in: unity-2d
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in
** Changed in: unity-2d
Milestone: 3.10 = 3.8.8
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
To
@Eliah: no worry, it's correct. Just think to close the Qt upstream bug
report once fixed upstream manually please :)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
@Didier Roche: Will do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
To manage notifications about this bug go to:
Marking Invalid in libqt-declarative in Arch Linux, since Andrea
Scarpino has deleted the comment on the upstream Qt bug tracker that had
confirmed it for Arch Linux (and searching https://bugs.archlinux.org
doesn't reveal a report separately confirming it).
** Changed in: libqt-declarative (Arch
** Changed in: gcc-4.6 (Ubuntu Oneiric)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in
** Branch linked: lp:~kubuntu-packagers/qt/ubuntu
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
--
This bug was fixed in the package qt4-x11 - 4:4.7.3-1ubuntu2
---
qt4-x11 (4:4.7.3-1ubuntu2) oneiric; urgency=low
[ Chase Douglas ]
* Fix touch end event handling, LP: #785433
- Updated kubuntu_28_xi2.1.patch with the fix
[ Didier Roche ]
* debian/rules:
- use
** Branch linked: lp:ubuntu/qt4-x11
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
--
kubuntu-bugs mailing
Added libqt-declarative in Arch Linux, as it was confirmed there by
Andrea Scarpino
(http://bugreports.qt.nokia.com/browse/QTBUG-19736?page=com.atlassian.jira.plugin.system.issuetabpanels
:comment-tabpanelfocusedCommentId=156025#comment-156025). Added Qt
(also without a link, since Launchpad
so, just some catchup in this bug:
- tried with a newer gcc 4.6, still segfaulting
- tried with a -f-no-omit-frame-pointer, still segfaulting
wigglytext.qml example from qt4-demos segfault as well with Qt compiled
with this version of gcc. See attached backtrace.
** Attachment added:
please lets rebuild qt4-x11 using a tightened b-d on g++-4.6 (=
4.6.0-11ubuntu2) first, then scan for warnings like the ones that the
upstream report points to.
** Package changed: gcc-defaults (Ubuntu Oneiric) = gcc-4.6 (Ubuntu Oneiric)
--
You received this bug notification because you are a
@Cristian: there is generally no more point to install debug symbols if
not relevant past frame 30/40, here is frame 56, hence not installing
the symbols file from there.
@Eliah: thanks for the stacktrace, continuing debugging this issue, I
rebuilt qt with gcc 4.5 in oneiric instead of 4.6, and
** Package changed: unity-2d (Ubuntu Oneiric) = qt4-x11 (Ubuntu
Oneiric)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in
** Also affects: gcc-defaults (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gcc-defaults (Ubuntu Oneiric)
Status: New = Confirmed
** Changed in: gcc-defaults (Ubuntu Oneiric)
Importance: Undecided = Critical
--
You received this bug notification because you are
took in touch with the Qt guys:
http://bugreports.qt.nokia.com/browse/QTBUG-19736 (launchpad doesn't
recognize the url as a bug tracker link)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
Using the information about missing symbols furnished by Didier Roche's
trace, I just installed all the relevant debug symbol packages and ran
unity-2d-places from the Terminal. In this way, I created duplicate bug
793044, which contains a considerably more complete stack trace (for all
threads),
Not full backtrace in manual_retrace
#56 0x08051c50 in DashAdaptor::qt_metacall(QMetaObject::Call, int, void**) ()
No symbol table info available.
#57 0x00a79788 in ?? () from /usr/lib/libQtDBus.so.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In case it's useful, my duplicate bug 792238 contains additional
description of how the UI appears to behave both before and after the
crash occurs (e.g., after the crash, clicking the home button
ineffectually toggles it between the pressed and unpressed states,
without any menu coming up).
--
** Changed in: unity-2d (Ubuntu)
Importance: Undecided = Critical
** Also affects: unity-2d (Ubuntu Oneiric)
Importance: Critical
Status: Confirmed
** Changed in: unity-2d (Ubuntu Oneiric)
Assignee: (unassigned) = Canonical Desktop Experience Team
(canonical-dx-team)
--
You
Manual retrace, with love
** Attachment added: Retrace of the crash with debugging symbols
https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/791213/+attachment/2150586/+files/manual_retrace
** Visibility changed to: Public
--
You received this bug notification because you are a
** Also affects: unity-2d
Importance: Undecided
Status: New
** Changed in: unity-2d
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
Confirmed by duplicate.
** Changed in: unity-2d
Status: New = Confirmed
** Changed in: unity-2d
Milestone: None = 3.10
** Changed in: unity-2d (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
--
ubuntu-bugs mailing list
27 matches
Mail list logo
