Bug 260993 - Dolphin crashed out of nothing
Summary: Dolphin crashed out of nothing
Status: RESOLVED UPSTREAM
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-22 19:41 UTC by maninred
Modified: 2011-01-29 15:09 UTC (History)
2 users (show)

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 maninred 2010-12-22 19:41:21 UTC
Application: dolphin (1.5)
KDE Platform Version: 4.5.4 (KDE 4.5.4) "release 9"
Qt Version: 4.7.1
Operating System: Linux 2.6.34.7-0.5-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Well,
Dolphin crashed out of nothing.
Sorry, but there is not even more to say.
I´ve istalled all debuginfo packages that are available for my system(several GB), because drkonqi was not able to find any usefull info packages, so the backtrack
is such optimal as it can be.

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f1f8f172534 in dbus_bus_release_name (connection=0x6c8240, name=0x7fffacf449a0 "@Q\364\254\377\177", error=0x408a14d1058b4996) at dbus-bus.c:1251
#7  0x0000000000df4570 in ?? ()
#8  0x00007f1f8f183b1d in do_noncefile_create (noncefile=0x7fffacf44970, error=0x7fffacf45140) at dbus-nonce.c:278
#9  _dbus_noncefile_create (noncefile=0x7fffacf44970, error=0x7fffacf45140) at dbus-nonce.c:367
#10 0x00007f1f94e38999 in QObject::event (this=0x7fff0000003b, e=<value optimized out>) at kernel/qobject.cpp:1175
#11 0x00007f1f93fc5cd4 in QApplicationPrivate::notify_helper (this=0x6c8240, receiver=0x6b5630, e=0x7fffacf45140) at kernel/qapplication.cpp:4445
#12 0x00007f1f93fce1ca in QApplication::notify (this=<value optimized out>, receiver=0x6b5630, e=0x7fffacf45140) at kernel/qapplication.cpp:4324
#13 0x00007f1f95aa7816 in KApplication::notify (this=0x7fffacf45510, receiver=0x6b5630, event=0x7fffacf45140) at /usr/src/debug/kdelibs-4.5.4/kdeui/kernel/kapplication.cpp:310
#14 0x00007f1f94e24e2c in QCoreApplication::notifyInternal (this=0x7fffacf45510, receiver=0x6b5630, event=0x7fffacf45140) at kernel/qcoreapplication.cpp:732
#15 0x00007f1f94e52658 in sendEvent (this=0x6c0bb0) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x6c0bb0) at kernel/qeventdispatcher_unix.cpp:618
#17 0x00007f1f94e4f3d8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#19 0x00007f1f90965a93 in g_main_dispatch (context=0x6bf920) at gmain.c:1960
#20 IA__g_main_context_dispatch (context=0x6bf920) at gmain.c:2513
#21 0x00007f1f90966270 in g_main_context_iterate (context=0x6bf920, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2591
#22 0x00007f1f90966510 in IA__g_main_context_iteration (context=0x6bf920, may_block=1) at gmain.c:2654
#23 0x00007f1f94e4fa8f in QEventDispatcherGlib::processEvents (this=0x6c8060, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#24 0x00007f1f9406aeae in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007f1f94e24262 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f1f94e24475 in QEventLoop::exec (this=0x7fffacf45450, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007f1f94e288db in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#28 0x00007f1f855fd045 in kdemain (argc=5, argv=0x69c360) at /usr/src/debug/kdebase-4.5.4/apps/dolphin/src/main.cpp:98
#29 0x00000000004074a9 in launch (argc=5, _name=0x69bad8 "/usr/bin/dolphin", args=<value optimized out>, cwd=0x0, envc=<value optimized out>, envs=<value optimized out>, reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x69bb31 "linux-3zjc;1293024827;736362;4818_TIME396755") at /usr/src/debug/kdelibs-4.5.4/kinit/kinit.cpp:723
#30 0x0000000000407fc5 in handle_launcher_request (sock=8, who=<value optimized out>) at /usr/src/debug/kdelibs-4.5.4/kinit/kinit.cpp:1215
#31 0x000000000040873a in handle_requests (waitForPid=<value optimized out>) at /usr/src/debug/kdelibs-4.5.4/kinit/kinit.cpp:1408
#32 0x0000000000409390 in main (argc=4, argv=0x7fffacf46ab8, envp=0x7fffacf46ae0) at /usr/src/debug/kdelibs-4.5.4/kinit/kinit.cpp:1892

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-12-22 22:25:56 UTC
Thanks for the bug report! The crash looks related to D-Bus - I'm wondering if it might be related to bug 226725, which is a bug in D-Bus versions < 1.3.1. Could you try to run "rpm -qa | grep dbus" to check your D-Bus version? Thanks.
Comment 2 Christoph Feck 2011-01-28 18:13:07 UTC
If you can provide the information requested in comment #1, please add it to this bug.
Comment 3 maninred 2011-01-29 15:03:02 UTC
Sorry,
I´ve forgotten to post it.
Frank Reininghaus is right. 
I´ve made the mistake to make updates(also on d-bus) in the same run I´ve installed the debug packages for the debugging.
So the crash could has it causes on d-bus.

The output of

rpm -qa | grep dbus

is 

~> rpm -qa | grep dbus
libdbus-1-qt3-0-debuginfo-0.8.1-135.4.x86_64
dbusxml2qt3-debuginfo-0.8.1-135.4.x86_64
dbus-1-debuginfo-32bit-1.4.1-17.1.x86_64
libdbusmenu-qt2-debuginfo-0.6.6-11.1.x86_64
libdbus-1-qt3-0-devel-0.8.1-135.4.x86_64
libeggdbus-1-0-0.6-5.1.x86_64
libeggdbus-1-0-debuginfo-0.6-5.1.x86_64
libdbusmenu-qt-devel-0.6.6-11.1.x86_64
dbus-1-mono-0.63-193.1.x86_64
dbus-1-glib-debuginfo-0.86-1.19.x86_64
dbus-1-x11-1.2.24-1.10.x86_64
dbus-1-glib-0.86-1.19.x86_64
yast2-dbus-server-debuginfo-2.18.1-6.1.x86_64
dbus-1-devel-1.4.1-17.1.x86_64
ndesk-dbus-glib-0.4.1-40.1.noarch
dbus-1-qt3-debuginfo-0.62-228.1.x86_64
libdbusmenu-qt2-0.6.6-11.1.x86_64
ndesk-dbus-0.6.0-68.1.noarch
dbus-1-x11-debuginfo-1.4.1-17.1.x86_64
libdbus-1-qt3-0-0.8.1-135.4.x86_64
dbus-1-32bit-1.4.1-17.1.x86_64
dbus-1-glib-devel-debuginfo-0.86-1.19.x86_64
yast2-dbus-client-2.18.0-5.1.x86_64
dbus-1-python-0.83.0-31.1.x86_64
dbus-1-python-debuginfo-0.83.0-31.1.x86_64
dbus-1-glib-devel-0.86-1.19.x86_64
dbus-1-debuginfo-1.4.1-17.1.x86_64
libdbus-1-qt3-0-debugsource-0.8.1-135.4.x86_64
kdbus-debuginfo-0.8.6_SVN_20070413-195.3.x86_64
dbus-1-glib-32bit-0.86-1.19.x86_64
yast2-dbus-client-debuginfo-2.18.0-5.1.x86_64
libdbusmenu-qt-debugsource-0.6.6-11.1.x86_64
dbus-1-1.4.1-17.1.x86_64
dbus-1-glib-debuginfo-32bit-0.86-1.19.x86_64
dbus-1-devel-32bit-1.4.1-17.1.x86_64
~> 


The crash doesn´t happen anymore since then, so:

mea culpa!
Comment 4 Christoph Feck 2011-01-29 15:09:02 UTC
Thanks for the update! So let's close this bug.