Version: (using KDE 4.3.5) Compiler: x86_64-pc-linux-gnu-4.3.4 OS: Linux Installed from: Gentoo Packages As of a Qt update to 4.6.2-r1, I noticed that the multimedia keys on my keyboard can now, finally, be used in combination with modifier keys (e.g. Shift + Calculator). Therefore, I wanted to change the shortcut for opening a Terminal _panel_ in Dolphin (not a konsole-window on its on) from F4 to something different (e.g. Shift + Calculator). However, when I go to View->Panels->Terminal -> Configure shortcut, my dolphin window crashes and I get a Crash report (which is said to probably not being useful). The same happens when I want to assign the Terminal-panel to the Main Toolbar. Please let me know if you need additional information, or even perhaps the "unuseful" crash report.
Thanks for the bug report! > Please let me know if you need additional information, or even perhaps the > "unuseful" crash report. Yes, please paste the report here.
This is the information that I get: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #5 0x00007fa042fbbc34 in QAction::data() const () from /usr/lib64/qt4/libQtGui.so.4 #6 0x00007fa044d667f0 in KMenu::contextMenuFocusAction() () from /usr/lib64/libkdeui.so.5 #7 0x00007fa044d9fa17 in ?? () from /usr/lib64/libkdeui.so.5 #8 0x00007fa044da084a in ?? () from /usr/lib64/libkdeui.so.5 #9 0x00007fa043e1b167 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #10 0x00007fa042fbbb92 in QAction::triggered(bool) () from /usr/lib64/qt4/libQtGui.so.4 #11 0x00007fa042fbdbd0 in QAction::activate(QAction::ActionEvent) () from /usr/lib64/qt4/libQtGui.so.4 #12 0x00007fa0433e2805 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #13 0x00007fa0433e818f in ?? () from /usr/lib64/qt4/libQtGui.so.4 #14 0x00007fa043018fd2 in QWidget::event(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #15 0x00007fa0433ea2eb in QMenu::event(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #16 0x00007fa042fc1d6d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #17 0x00007fa042fc9e3c in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #18 0x00007fa044c9408b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #19 0x00007fa043e07dab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #20 0x00007fa042fc89cb in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib64/qt4/libQtGui.so.4 #21 0x00007fa04304abc3 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #22 0x00007fa043049bbc in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #23 0x00007fa0430726aa in ?? () from /usr/lib64/qt4/libQtGui.so.4 #24 0x00007fa03fb31d59 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0x00007fa03fb355a8 in ?? () from /usr/lib/libglib-2.0.so.0 #26 0x00007fa03fb3575c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0x00007fa043e3154c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #28 0x00007fa04307224f in ?? () from /usr/lib64/qt4/libQtGui.so.4 #29 0x00007fa043e066d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #30 0x00007fa043e06aa4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #31 0x00007fa043e08ef6 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #32 0x00000000004353fd in _start ()
Thanks for the update! This bug is fixed in KDE SC 4.4.x. It's indeed a regression caused by the update to Qt 4.6. *** This bug has been marked as a duplicate of bug 218485 ***
Thanks for the information and the quick answers. Updating to KDE 4.4.x is not an option for me, at the moment. Is there perhaps some sort of configuration file that stores the assigned shortcuts and where I could then manually enter the desired shortcut? Or how are the shortcuts stored?
There certainly is a configuration file, but I think it would be easier to go to "Configure Shortcuts" in the Settings menu. I think that this configuration dialog is not affected by the bug.
(In reply to comment #5) > There certainly is a configuration file, but I think it would be easier to go > to "Configure Shortcuts" in the Settings menu. I think that this configuration > dialog is not affected by the bug. You're right. This would be easier, but there exists no entry for the Terminal-pager. The more, searching for "F4" (the current shortcut) only reveals me "Open Terminal (Shift + F4)" which is not what I want. Do you have any other suggestion?
Ups - reading the old bug report again, I noticed that there were actually two bugs: the crash and the problem that the shortcuts for showing/hiding the panels could not be configured. The latter bug (see bug 218485 comment 5) has been fixed for KDE SC 4.4.0. I'm afraid that configuring this shortcut is not possible in KDE 4.3.5 :-( Sorry!
(In reply to comment #7) > Ups - reading the old bug report again, I noticed that there were actually two > bugs: the crash and the problem that the shortcuts for showing/hiding the > panels could not be configured. The latter bug (see bug 218485 comment 5) has > been fixed for KDE SC 4.4.0. > > I'm afraid that configuring this shortcut is not possible in KDE 4.3.5 :-( > Sorry! Can you perhaps tell, where the default of "F4" is then specified? One could then adjust it directly for the default, at least for the moment? Or maybe someone else? I mean, I personaly see no reason why one would need to constantly change this shortcut, so a dedicated dialog is not necessary. Besides that it is fixed in 4.4, so I understand why there won't be any big changes on the behavior in 4.3.
> Can you perhaps tell, where the default of "F4" is then specified? One could > then adjust it directly for the default, at least for the moment? Or maybe > someone else? The shortcut is hardcoded in line 1251 of dolphinmainwindow.cpp, see http://websvn.kde.org/tags/KDE/4.3.5/kdebase/apps/dolphin/src/dolphinmainwindow.cpp?view=markup I think the only way to change this would be to build Dolphin from source after changing that line (or edit the binary file with a hex editor, but it would be hard to find the right place).