Bug 472418 - Dolphin crashes when when screen on after screen saver
Summary: Dolphin crashes when when screen on after screen saver
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 22.12.3
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-07-20 05:45 UTC by ALeXaNDeR
Modified: 2024-03-02 03:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ALeXaNDeR 2023-07-20 05:45:59 UTC
Application: dolphin (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-24-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.04
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
After the timeout, the computer screen went blank, but it was not locked.
After the screen woke up, the dolphin crashed.
A second monitor is connected to the laptop via HDMI. This happens periodically when the screen wakes up after a short sleep.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  __memcpy_evex_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:265
#5  0x00007f3bb7ad353a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x00007f3bb7ad3b59 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x00007f3bb7ad44a9 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x00007f3bbdf0a0c2 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x00007f3bbe579787 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007f3bbe57b339 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f3bbe57d4d8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f3bbe5c7a01 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f3bbe5cb7eb in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f3bbe56bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f3bbd8bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f3bbdd3e8f4 in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x00007f3bbdd164bc in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x00007f3bb7ade54e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#19 0x00007f3bbb71549d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f3bbb770178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f3bbb7141b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f3bbd914e7a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f3bbd8b97cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007f3bbd8c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x000055a2ad02e56a in ?? ()
#26 0x00007f3bbce23a90 in __libc_start_call_main (main=main@entry=0x55a2ad02bc40, argc=argc@entry=1, argv=argv@entry=0x7fff9ca54408) at ../sysdeps/nptl/libc_start_call_main.h:58
#27 0x00007f3bbce23b49 in __libc_start_main_impl (main=0x55a2ad02bc40, argc=1, argv=0x7fff9ca54408, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff9ca543f8) at ../csu/libc-start.c:360
#28 0x000055a2ad02ec65 in ?? ()
[Inferior 1 (process 617525) detached]

Reported using DrKonqi
Comment 1 Akseli Lahtinen 2024-02-01 14:30:01 UTC
Hi, if you still have encountered this bug, can you send  a backtrace with debug symbols?

https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_(Ubuntu,_Kubuntu,_KDE_Neon,_Linux_Mint)

Thank you!
Comment 2 Bug Janitor Service 2024-02-16 03:45:53 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2024-03-02 03:46:56 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!