Bug 445988 - Dolphin segmentation-faults
Summary: Dolphin segmentation-faults
Status: RESOLVED UPSTREAM
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 21.08.2
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-11-23 18:44 UTC by Thijs Withaar
Modified: 2023-12-08 12:00 UTC (History)
3 users (show)

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


Attachments
New crash information added by DrKonqi (3.43 KB, text/plain)
2021-11-26 15:11 UTC, Thijs Withaar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thijs Withaar 2021-11-23 18:44:29 UTC
Application: dolphin (21.08.2)

Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.14.0-4-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.23.3 [KCrashBackend]

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

Start up dolphin, wait a little while, typically less than 30 seconds.
The amount of mouse-activity does not seems to affect things muc.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  QAccessibleInterface::tableCellInterface (this=0x0) at ../../../include/QtGui/../../src/gui/accessible/qaccessible.h:510
#5  AtSpiAdaptor::tableInterface (this=0x5592e1db7990, interface=0x5592e1f39980, function=..., message=..., connection=...) at ./src/platformsupport/linuxaccessibility/atspiadaptor.cpp:2434
#6  0x00007fe4f777d49e in AtSpiAdaptor::handleMessage (this=this@entry=0x5592e1db7990, message=..., connection=...) at ./src/platformsupport/linuxaccessibility/atspiadaptor.cpp:1290
#7  0x00007fe4fdd9894f in QDBusConnectionPrivate::activateObject (this=0x7fe4e800c8f0, node=..., msg=..., pathStartPos=27) at ./src/dbus/qdbusintegrator.cpp:1458
#8  0x00007fe4fdd9b0c8 in QDBusActivateObjectEvent::placeMetaCall (this=0x5592e1f85000) at ./src/dbus/qdbusintegrator.cpp:1617
#9  0x00007fe4fcd30d6e in QObject::event (this=0x5592e1db7990, e=0x5592e1f85000) at kernel/qobject.cpp:1314
#10 0x00007fe4fd7d86af in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007fe4fcd0475a in QCoreApplication::notifyInternal2 (receiver=0x5592e1db7990, event=0x5592e1f85000) at kernel/qcoreapplication.cpp:1063
#12 0x00007fe4fcd077a7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5592e1130ef0) at kernel/qcoreapplication.cpp:1817
#13 0x00007fe4fcd5c733 in postEventSourceDispatch (s=0x5592e122a690) at kernel/qeventdispatcher_glib.cpp:277
#14 0x00007fe4fa7d0c7b in g_main_dispatch (context=0x7fe4f0005000) at ../../../glib/gmain.c:3381
#15 g_main_context_dispatch (context=0x7fe4f0005000) at ../../../glib/gmain.c:4099
#16 0x00007fe4fa7d0f28 in g_main_context_iterate (context=context@entry=0x7fe4f0005000, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4175
#17 0x00007fe4fa7d0fdf in g_main_context_iteration (context=0x7fe4f0005000, may_block=1) at ../../../glib/gmain.c:4240
#18 0x00007fe4fcd5bdb4 in QEventDispatcherGlib::processEvents (this=0x5592e1231d00, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#19 0x00007fe4fcd0316b in QEventLoop::exec (this=this@entry=0x7fff66aec140, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#20 0x00007fe4fcd0b440 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#21 0x00005592e0d9f2ae in ?? ()
#22 0x00007fe4fc6abe4a in __libc_start_main (main=0x5592e0d9e190, argc=1, argv=0x7fff66aec3d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff66aec3c8) at ../csu/libc-start.c:314
#23 0x00005592e0d9f66a in ?? ()
[Inferior 1 (process 16016) detached]

The reporter indicates this bug may be a duplicate of or related to bug 411503.

Possible duplicates by query: bug 411503.

Reported using DrKonqi
Comment 1 Thijs Withaar 2021-11-26 15:11:52 UTC
Created attachment 143968 [details]
New crash information added by DrKonqi

dolphin (21.08.2) using Qt 5.15.2

- What I was doing when the application crashed:

Dolphin was running in the background, I was not interacting with it, but my mouse might have hovered over.
This is debian bookworm, with a lot of Qt libraries updated since the stacktrace from the previous report.

I get the impression it happens more/quicker when one of the tabs is pointing to an smb share, but it's hard to be sure.

-- Backtrace (Reduced):
#4  QAccessibleInterface::tableCellInterface (this=0x0) at ../../../include/QtGui/../../src/gui/accessible/qaccessible.h:510
#5  AtSpiAdaptor::tableInterface (this=0x563d4af29710, interface=0x563d4b1f7950, function=..., message=..., connection=...) at ./src/platformsupport/linuxaccessibility/atspiadaptor.cpp:2434
#6  0x00007f37d47fc49e in AtSpiAdaptor::handleMessage (this=this@entry=0x563d4af29710, message=..., connection=...) at ./src/platformsupport/linuxaccessibility/atspiadaptor.cpp:1290
#7  0x00007f37dae1a94f in QDBusConnectionPrivate::activateObject (this=0x7f37c400c930, node=..., msg=..., pathStartPos=27) at ./src/dbus/qdbusintegrator.cpp:1458
#8  0x00007f37dae1d0c8 in QDBusActivateObjectEvent::placeMetaCall (this=0x563d4aea7f00) at ./src/dbus/qdbusintegrator.cpp:1617
Comment 2 Akseli Lahtinen 2023-12-08 12:00:12 UTC
Crash seems to be with Qt and it has been updated since the bug report. Please reopen if you encounter this issue again with current Dolphin version, thank you!