Bug 487718

Summary: dolphin crashing on double tapping the spacebar.
Product: [Applications] dolphin Reporter: saurabh2023
Component: view-engine: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: dariocambie, felixernst, kfm-devel, shehabmadko
Priority: NOR    
Version: 24.02.2   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: screen recording on double tapping the spacebar
New crash information added by DrKonqi

Description saurabh2023 2024-05-29 00:41:44 UTC
Created attachment 169925 [details]
screen recording on double tapping the spacebar

OS: Fedora Linux 40 (KDE Plasma) x86_64
Host: Inspiron 3584
Kernel: Linux 6.8.10-300.fc40.x86_64
Uptime: 2 hours, 9 mins
Packages: 2738 (rpm), 13 (flatpak)
Shell: bash 5.2.26
Display (AUO38ED): 1920x1080 @ 60Hz (as 960x540) [Built-in]
DE: KDE Plasma 6.0.5
WM: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (Dark) [QT], Breeze [GTK3]
Icons: breeze-dark [QT], breeze-dark [GTK3/4]
Font: Noto Sans (10pt) [QT], Noto Sans (10pt) [GTK3/4]
Cursor: Adwaita (24px)
Terminal: konsole 24.2.2
CPU: Intel(R) Core(TM) i3-7020U (4) @ 2.30 GHz
GPU: Intel HD Graphics 620 @ 1.00 GHz [Integrated]
Memory: 4.92 GiB / 7.65 GiB (64%)
Swap: 754.25 MiB / 7.65 GiB (10%)
Disk (/): 59.60 GiB / 231.30 GiB (26%) - btrfs
Local IP (wlp2s0): 192.168.136.223/24 *
Battery: 26% [Discharging]
Locale: en_US.UTF-8
Comment 1 Dario CambiƩ 2024-05-29 12:18:41 UTC
Can reproduce also on Fedora 40 (Dolphin 24.02.2).
Essentially, when no file is selected (status bar shows the number of files in the folder) and the space bar is pressed, instead of activating selection mode, dolphin crashes.

Thread 1 (Thread 0x7f69cde3a000 (LWP 5172)):
[KCrash Handler]
#4  0x00007f69d3de95ce in QObject::deleteLater() () at /lib64/libQt6Core.so.6
#5  0x0000557b1c6e05b1 in SelectionMode::BottomBarContentsContainer::contextActionsFor (this=0x557b1e2627c0, selectedItems=..., baseUrl=<optimized out>) at /usr/src/debug/dolphin-24.02.2-2.fc40.x86_64/src/selectionmode/bottombarcontentscontainer.cpp:486
#6  SelectionMode::BottomBarContentsContainer::slotSelectionChanged (this=0x557b1e2627c0, selection=..., baseUrl=<optimized out>) at /usr/src/debug/dolphin-24.02.2-2.fc40.x86_64/src/selectionmode/bottombarcontentscontainer.cpp:133
#7  0x0000557b1c6b8bd9 in SelectionMode::BottomBar::slotSelectionChanged (this=0x557b1e286150, selection=..., baseUrl=...) at /usr/src/debug/dolphin-24.02.2-2.fc40.x86_64/src/selectionmode/bottombar.cpp:103
#8  DolphinViewContainer::setSelectionModeEnabled (this=0x557b1dd29d00, enabled=<optimized out>, actionCollection=0x557b1d95a890, bottomBarContents=<optimized out>) at /usr/src/debug/dolphin-24.02.2-2.fc40.x86_64/src/dolphinviewcontainer.cpp:367
#9  0x0000557b1c699f00 in DolphinMainWindow::toggleSelectionMode (this=0x557b1d939e40) at /usr/src/debug/dolphin-24.02.2-2.fc40.x86_64/src/dolphinmainwindow.cpp:979
#10 0x00007f69d3dfa752 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt6Core.so.6
#11 0x00007f69d4a23ec4 in QAction::triggered(bool) () at /lib64/libQt6Gui.so.6
#12 0x00007f69d4a26eff in QAction::activate(QAction::ActionEvent) () at /lib64/libQt6Gui.so.6
#13 0x00007f69d4a27f42 in QAction::event(QEvent*) () at /lib64/libQt6Gui.so.6
#14 0x00007f69d4f8b168 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt6Widgets.so.6
#15 0x00007f69d3d95b18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6
#16 0x00007f69d4a3a658 in QShortcutMap::dispatchEvent(QKeyEvent*) () at /lib64/libQt6Gui.so.6
#17 0x00007f69d4a3b56f in QShortcutMap::tryShortcut(QKeyEvent*) () at /lib64/libQt6Gui.so.6
#18 0x00007f69d464e458 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags<Qt::KeyboardModifier>, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () at /lib64/libQt6Gui.so.6
#19 0x00007f69d45e20ea in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /lib64/libQt6Gui.so.6
#20 0x00007f69d464952c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Gui.so.6
#21 0x00007f69d4b54e74 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt6Gui.so.6
#22 0x00007f69d211a6ac in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0
#23 0x00007f69d217b708 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0
#24 0x00007f69d211bb23 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#25 0x00007f69d407cb53 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6
#26 0x00007f69d3da2713 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6
#27 0x00007f69d3d9e69c in QCoreApplication::exec() () at /lib64/libQt6Core.so.6
#28 0x0000557b1c696612 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/dolphin-24.02.2-2.fc40.x86_64/src/main.cpp:253
Comment 2 Felix Ernst 2024-05-30 22:43:19 UTC

*** This bug has been marked as a duplicate of bug 485599 ***
Comment 3 Shehab 2024-06-07 04:58:56 UTC
Created attachment 170218 [details]
New crash information added by DrKonqi

dolphin (23.08.3) using Qt 5.15.11

Flashing some times when closing or tapping bet. diffrent taps .

-- Backtrace (Reduced):
#6  0x00007fabe96a6bb1 in QGraphicsScene::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x00007fabe9350763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x00007fabe88588ea in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007fabe96c4825 in QGraphicsView::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007fabe939395e in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
Comment 4 Felix Ernst 2024-06-07 09:33:46 UTC
@Shebab, your crash is unrelated to the crash reported in this bug. It has a completely different stack trace and therefore wasn't fixed when this bug report was.