Bug 251225

Summary:	Dolphin crash when using the program OpenOffice.
Product:	[Applications] dolphin	Reporter:	Santiago <yoprideone>
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	frank78ac
Priority:	NOR
Version:	16.12.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Santiago 2010-09-14 17:32:50 UTC

Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

The application Dolphin closed only when I was using two OpenOffice.org at the same time.
Kde versión 4.5.1 "Release 3"
And the Dolphin Version is 1.5

Reproducible: Didn't try




Application: Dolphin (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  _dbus_connection_lock (connection=0x747865742e746e65) at dbus-connection.c:355
#7  0x00007febbaa8fb1d in _dbus_pending_call_get_connection_and_lock (pending=0x7feba40632f0) at dbus-pending-call.c:307
#8  0x00007febbaa81fce in reply_handler_timeout (data=0x7feba40632f0) at dbus-connection.c:3163
#9  0x00007febbdd3acef in q_dbus_timeout_handle (this=0x690730, e=0x7fff477c0a70) at qdbus_symbols_p.h:172
#10 QDBusConnectionPrivate::timerEvent (this=0x690730, e=0x7fff477c0a70) at qdbusintegrator.cpp:1035
#11 0x00007febc090922e in QObject::event (this=0x690730, e=0x7fff477c0a70) at kernel/qobject.cpp:1212
#12 0x00007febbfacc4d4 in QApplicationPrivate::notify_helper (this=0x6a58c0, receiver=0x690730, e=0x7fff477c0a70) at kernel/qapplication.cpp:4302
#13 0x00007febbfad4aca in QApplication::notify (this=<value optimized out>, receiver=0x690730, e=0x7fff477c0a70) at kernel/qapplication.cpp:4185
#14 0x00007febc155d1e6 in KApplication::notify (this=0x7fff477c0ec0, receiver=0x690730, event=0x7fff477c0a70) at /usr/src/debug/kdelibs-4.5.1/kdeui/kernel/kapplication.cpp:310
#15 0x00007febc08f7e4c in QCoreApplication::notifyInternal (this=0x7fff477c0ec0, receiver=0x690730, event=0x7fff477c0a70) at kernel/qcoreapplication.cpp:726
#16 0x00007febc09230c9 in sendEvent (this=0x69be20) at kernel/qcoreapplication.h:215
#17 QTimerInfoList::activateTimers (this=0x69be20) at kernel/qeventdispatcher_unix.cpp:618
#18 0x00007febc091fff8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#19 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#20 0x00007febbc480a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007febbc481270 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007febbc481510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007febc092067f in QEventDispatcherGlib::processEvents (this=0x6a5760, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#24 0x00007febbfb6d14e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007febc08f7292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007febc08f7495 in QEventLoop::exec (this=0x7fff477c0e00, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007febc08fb88b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#28 0x00007febb0edc085 in kdemain (argc=6, argv=0x675950) at /usr/src/debug/kdebase-4.5.1/apps/dolphin/src/main.cpp:98
#29 0x00000000004074a9 in _start ()

Comment 1 Frank Reininghaus 2010-09-14 17:54:07 UTC

Thanks for the bug report! This looks like an issue in the D-Bus library which
has been reported already. It is fixed in D-Bus 1.3.x:

http://bugreports.qt.nokia.com/browse/QTBUG-7475
https://bugs.freedesktop.org/show_bug.cgi?id=17754

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

Comment 2 Santiago 2010-09-14 18:27:33 UTC

Hi and Thank you.

I have in my OpenSuse D-Bus version 1.2

As I do not understand the layout, I will continue to send me return paths,
if the path is not D-Bus library.
Is this right?

2010/9/14 Frank Reininghaus <frank78ac@googlemail.com>

> https://bugs.kde.org/show_bug.cgi?id=251225
>
>
> Frank Reininghaus <frank78ac@googlemail.com> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |RESOLVED
>                 CC|                            |frank78ac@googlemail.com
>         Resolution|                            |DUPLICATE
>
>
>
>
> --- Comment #1 from Frank Reininghaus <frank78ac googlemail com>
>  2010-09-14 17:54:07 ---
> Thanks for the bug report! This looks like an issue in the D-Bus library
> which
> has been reported already. It is fixed in D-Bus 1.3.x:
>
> http://bugreports.qt.nokia.com/browse/QTBUG-7475
> https://bugs.freedesktop.org/show_bug.cgi?id=17754
>
> *** This bug has been marked as a duplicate of bug 226725 ***
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

Comment 3 Frank Reininghaus 2010-09-14 18:31:14 UTC

I'm not sure if I understood your last comment.

If you see Dolphin crash and the backtrace contains "dbus", it is probably the same crash. It does not need to be reported again.

If you have a backtrace that does not contain "dbus", it's a different issue and should probably be reported.

I hope that answers your question :-)

Comment 4 Santiago 2010-09-14 18:38:42 UTC

Okay, from now on I'll see if Dbug said a few times on the track.

Dbus If you can not find in the report, not reported. But if I have
questions, send the report and see if it is duplicated or not.

Thanks!

2010/9/14 Frank Reininghaus <frank78ac@googlemail.com>

> https://bugs.kde.org/show_bug.cgi?id=251225
>
>
>
>
>
> --- Comment #3 from Frank Reininghaus <frank78ac googlemail com>
>  2010-09-14 18:31:14 ---
> I'm not sure if I understood your last comment.
>
> If you see Dolphin crash and the backtrace contains "dbus", it is probably
> the
> same crash. It does not need to be reported again.
>
> If you have a backtrace that does not contain "dbus", it's a different
> issue
> and should probably be reported.
>
> I hope that answers your question :-)
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>