Bug 391424 - KDE crash when opening bookmarks menu
Summary: KDE crash when opening bookmarks menu
Status: RESOLVED FIXED
Alias: None
Product: Smb4k
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Alexander Reinholdt
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-03-05 11:40 UTC by Jill
Modified: 2018-04-02 15:30 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 2.0.90


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jill 2018-03-05 11:40:49 UTC
Application: smb4k (2.0.80)

Qt Version: 5.10.1
Frameworks Version: 5.43.0
Operating System: Linux 4.15.7-1-kiwi x86_64
Distribution: "Arch Linux"

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

I just tried to open the bookmarks menu as it's not displayed when using the Global Menu KDE widget
Repeatedly pressed Alt+B and then it crashed...

The crash can be reproduced every time.

-- Backtrace:
Application: Smb4K (smb4k), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ffa14ca2800 (LWP 11040))]

Thread 4 (Thread 0x7ff9c5ffb700 (LWP 11071)):
#0  0x00007ffa10f58879 in syscall () at /usr/lib/libc.so.6
#1  0x00007ffa0a253dcd in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0
#2  0x00007ffa0a1e0753 in  () at /usr/lib/libglib-2.0.so.0
#3  0x00007ffa0a1e0d3e in g_async_queue_timeout_pop () at /usr/lib/libglib-2.0.so.0
#4  0x00007ffa0a235d81 in  () at /usr/lib/libglib-2.0.so.0
#5  0x00007ffa0a23526a in  () at /usr/lib/libglib-2.0.so.0
#6  0x00007ffa0c1e208c in start_thread () at /usr/lib/libpthread.so.0
#7  0x00007ffa10f5de7f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7ff9e216a700 (LWP 11065)):
#0  0x00007ffa0a253b94 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x00007ffa0a20c969 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x00007ffa0a20cf96 in  () at /usr/lib/libglib-2.0.so.0
#3  0x00007ffa0a20d10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#4  0x00007ffa1189f314 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#5  0x00007ffa118413db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#6  0x00007ffa116507ae in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x00007ffa11655b4d in  () at /usr/lib/libQt5Core.so.5
#8  0x00007ffa0c1e208c in start_thread () at /usr/lib/libpthread.so.0
#9  0x00007ffa10f5de7f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7ff9fd00d700 (LWP 11060)):
#0  0x00007ffa10f5397b in poll () at /usr/lib/libc.so.6
#1  0x00007ffa0a20cff3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x00007ffa0a20d10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#3  0x00007ffa1189f314 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#4  0x00007ffa118413db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#5  0x00007ffa116507ae in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x00007ffa0d920416 in  () at /usr/lib/libQt5DBus.so.5
#7  0x00007ffa11655b4d in  () at /usr/lib/libQt5Core.so.5
#8  0x00007ffa0c1e208c in start_thread () at /usr/lib/libpthread.so.0
#9  0x00007ffa10f5de7f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7ffa14ca2800 (LWP 11040)):
[KCrash Handler]
#5  0x00007ff9ff0a59bc in  () at /usr/lib/qt/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#6  0x00007ffa12756ff2 in QMenuBar::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5
#7  0x00007ffa125c0fec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#8  0x00007ffa125c89c6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#9  0x00007ffa11842da0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#10 0x00007ffa11de5bd9 in QShortcutMap::dispatchEvent(QKeyEvent*) () at /usr/lib/libQt5Gui.so.5
#11 0x00007ffa11de5cae in QShortcutMap::tryShortcut(QKeyEvent*) () at /usr/lib/libQt5Gui.so.5
#12 0x00007ffa11d931ed in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags<Qt::KeyboardModifier>, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () at /usr/lib/libQt5Gui.so.5
#13 0x00007ffa11db2d18 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /usr/lib/libQt5Gui.so.5
#14 0x00007ffa11db7f66 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5
#15 0x00007ffa11d8f29c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
#16 0x00007ffa02f2148d in  () at /usr/lib/libQt5XcbQpa.so.5
#17 0x00007ffa118413db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#18 0x00007ffa1184a7d8 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#19 0x000055bcd528bb93 in  ()
#20 0x00007ffa10e88f4a in __libc_start_main () at /usr/lib/libc.so.6
#21 0x000055bcd528a66a in _start ()

Reported using DrKonqi
Comment 1 Alexander Reinholdt 2018-03-07 19:48:26 UTC
Thank you for reporting this issue. 

Can you please answer the following two questions: Have you compiled Smb4K yourself? What do you mean by '... as it's not displayed when using the Global Menu KDE widget'?
Comment 2 Jill 2018-03-08 12:31:06 UTC
- I tried with both the version in the arch linux community repository and a version I compiled from git (to check if it was a bug fixed in master)
- I meant that when clicking on the "Bookmarks" menu in the widget, nothing was displayed, as if the menu was "stuck", actually it happens with some menus on the app itself too. Again, only when I have the Global Menu widget on my desktop
Comment 3 Alexander Reinholdt 2018-03-30 19:14:11 UTC
The problem with the bookmarks menu should be fixed lately. Could you please try version 2.0.90 and confirm that the problem is fixed?