Bug 287131 - apper crash when installing sax3
Summary: apper crash when installing sax3
Status: RESOLVED DUPLICATE of bug 286801
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-21 07:10 UTC by kiwilinux
Modified: 2011-11-21 10:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kiwilinux 2011-11-21 07:10:46 UTC
Application: apper-sentinel (0.7.0)
KDE Platform Version: 4.7.2 (4.7.2) "release 5"
Qt Version: 4.7.4
Operating System: Linux 3.1.0-1.2-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

when installing sax3 from /repositories/x11:/sax/opensuse_12.1/x86_64 apper will crash with error KDEInit could not launch '/usr/bin/apper'. This is repeatable with all packages that I have tried to download and open via firefox.

-- Backtrace:
Application: Apper (apper-sentinel), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fb5fe3009f4 in QAbstractButton::isChecked (this=0x7783e0) at widgets/qabstractbutton.cpp:772
#7  0x00007fb5fef33f75 in Requirements::~Requirements (this=0x99deb0, __in_chrg=<optimized out>) at /usr/src/debug/apper-0.7.0/libapper/Requirements.cpp:153
#8  0x00007fb5fef33fe9 in Requirements::~Requirements (this=0x99deb0, __in_chrg=<optimized out>) at /usr/src/debug/apper-0.7.0/libapper/Requirements.cpp:157
#9  0x00007fb5ff90b178 in QObject::event (this=0x99deb0, e=<optimized out>) at kernel/qobject.cpp:1209
#10 0x00007fb5fdf9dcfb in QWidget::event (this=0x99deb0, event=0x74e200) at kernel/qwidget.cpp:8754
#11 0x00007fb5fdf4dbe4 in notify_helper (e=0x74e200, receiver=0x99deb0, this=0x67baa0) at kernel/qapplication.cpp:4481
#12 QApplicationPrivate::notify_helper (this=0x67baa0, receiver=0x99deb0, e=0x74e200) at kernel/qapplication.cpp:4453
#13 0x00007fb5fdf52a71 in QApplication::notify (this=0x7fffa732fbd0, receiver=0x99deb0, e=0x74e200) at kernel/qapplication.cpp:4360
#14 0x00007fb600acbe36 in KApplication::notify (this=0x7fffa732fbd0, receiver=0x99deb0, event=0x74e200) at /usr/src/debug/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311
#15 0x00007fb5ff8f481c in QCoreApplication::notifyInternal (this=0x7fffa732fbd0, receiver=0x99deb0, event=0x74e200) at kernel/qcoreapplication.cpp:787
#16 0x00007fb5ff8f7bf8 in sendEvent (event=0x74e200, receiver=0x99deb0) at kernel/qcoreapplication.h:215
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x64c150) at kernel/qcoreapplication.cpp:1428
#18 0x00007fb5ff91f0b3 in sendPostedEvents () at kernel/qcoreapplication.h:220
#19 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:277
#20 0x00007fb5f96f358d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fb5f96f3d88 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fb5f96f3f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fb5ff91f50f in QEventDispatcherGlib::processEvents (this=0x64b930, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#24 0x00007fb5fdff0f2e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007fb5ff8f3a22 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007fb5ff8f3c1f in QEventLoop::exec (this=0x7fffa732fb60, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007fb5ff8f7de7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#28 0x000000000041035d in main (argc=1, argv=0x7fffa732feb8) at /usr/src/debug/apper-0.7.0/Sentinel/main.cpp:54

Possible duplicates by query: bug 286980, bug 286969, bug 286868, bug 286853.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-11-21 10:27:16 UTC

*** This bug has been marked as a duplicate of bug 286801 ***