Reply to topic

Custom Shortcut to open Konsole doesn't work

User avatar sammuirhead
Registered Member
Posts
162
Karma
1
OS
I used one of the example Custom Shortcuts to give me the same functionality for opening a terminal that I'm used to from Unity: Ctrl+Alt+T should bring up a new terminal window.
Image

Unfortunately when I press Ctrl+Alt+T, Konsole flickers into life and then immediately fades out. (See screengrab)

Have I set something wrong, or should I file a bug? If so, against what do I file the bug? Plasma 5? Konsole? other?


http://www.cameralibre.cc
Free Culture videos made with Free/Libre/Open Source Software about Open Hardware, Open Data, Open Everything
User avatar Rog131
Registered Member
Posts
828
Karma
10
At here:

Qt: 5.5.1
KDE Frameworks: 5.17.0
Konsole: 15.12.0
KDE Plasma 5.5.2
Distro: Arch Linux


Seems to work: http://i.imgur.com/LqEBRbV.gifv


Have you tried with a new user ?
- viewtopic.php?f=14&t=38828

Looked the logs ?
- .xsession-errors
- systemd journal:
Code: Select all
journalctl -b
luebking
Karma
0
The shortcut works, but konsole immediately exits (crashes?)

Is there one/several konsole processes running?

Can you start konsole otherwise?

Do you get coredumps (or crashdialogs, after installing drkonqi) from the shortcut launch?
User avatar sammuirhead
Registered Member
Posts
162
Karma
1
OS
Thanks for your suggestions!

More information on my system:

Qt: 5.4.2
KDE Frameworks: 5.15.0
Konsole: 15.08.0
KDE Plasma: 5.4.2
Kubuntu 15.10


With a new user, it works fine - so the problem must be in my settings somewhere.

I checked .xsession-errors: here's the most recent output, after attempting to launch Konsole a couple more times.
There is a lot that seems relevant, for example:

kdeinit5: Got EXT_EXEC 'konsole' from launcher.
kdeinit5: preparing to launch 'libkdeinit5_konsole'
QXcbConnection: XCB error: 3 (BadWindow), sequence: 40839, resource id: 27262977, major code: 18 (ChangeProperty), minor code: 0
QCoreApplication::arguments: Please instantiate the QApplication object first
QXcbConnection: XCB error: 3 (BadWindow), sequence: 40844, resource id: 27262978, major code: 18 (ChangeProperty), minor code: 0
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kdeinit5: PID 5020 terminated.


But I don't quite know what to do with this information. I guess I should, um, instantiate the QApplication object..?
Also: Baloo keeps crashing as well, I don't know if this is in any way related or not?

Any suggestions you can offer would be great!


http://www.cameralibre.cc
Free Culture videos made with Free/Libre/Open Source Software about Open Hardware, Open Data, Open Everything
luebking
Karma
0
The warnings should be harmless and do not explain the termination of the konsole process.
I'd rather assume it terminates because a running konsole instance is detected?

Test the behavior avoiding the shortcut, try to start "konsole" from eg. xterm (to obtain direct output)
User avatar sammuirhead
Registered Member
Posts
162
Karma
1
OS
This is the output from xterm:
[email protected]:~$ konsole
QCoreApplication::arguments: Please instantiate the QApplication object first
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
[email protected]:~$ Invalid Context= "Apps" line for icon theme: "/usr/share/icons/Paper/[email protected]/apps"
Invalid Context= "Mimetypes" line for icon theme: "/usr/share/icons/Paper/[email protected]/mimetypes"
Invalid Context= "Mimetypes" line for icon theme: "/usr/share/icons/Paper/symbolic/mimetypes"
The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.



I just realised I forgot to mention in my last post that konsole works fine when launched from synapse, kickoff or krunner. The problem is only when launching with the Ctrl+Alt+T shortcut.


http://www.cameralibre.cc
Free Culture videos made with Free/Libre/Open Source Software about Open Hardware, Open Data, Open Everything
luebking
Karma
0
What happens if you open konsole in a "traditional" way, activate it and press "ctrl+alt+t"?
User avatar sammuirhead
Registered Member
Posts
162
Karma
1
OS
exactly the same - another konsole window briefly appears and then disappears - the original konsole window stays open.


http://www.cameralibre.cc
Free Culture videos made with Free/Libre/Open Source Software about Open Hardware, Open Data, Open Everything
luebking
Karma
0
ah, sorry. how does it behave with the hotkey deactivated?
User avatar sammuirhead
Registered Member
Posts
162
Karma
1
OS
With the hotkey either deactivated or activated, Konsole windows open normally (when launched from krunner/other terminals/launcher etc).
This issue only occurs when using the shortcut - all other aspects of Konsole work as expected.


http://www.cameralibre.cc
Free Culture videos made with Free/Libre/Open Source Software about Open Hardware, Open Data, Open Everything
luebking
Karma
0
what i meant is:
deactivate the shortcut, open konsole, press (and release) ctrl+alt+t as if the shortcut wasn't deactivated and see what happens to the active konsole.

(there must be some reason for the immediate exit and i suspect the particular key release events to be invoked)
User avatar sammuirhead
Registered Member
Posts
162
Karma
1
OS
nothing happens - there's no output in the active konsole.


http://www.cameralibre.cc
Free Culture videos made with Free/Libre/Open Source Software about Open Hardware, Open Data, Open Everything
luebking
Karma
0
gnarf.

what happens with other shortcuts? (ctrl+alt+u)
what if you change the executed comand to "sleep 2; konsole"?
User avatar sammuirhead
Registered Member
Posts
162
Karma
1
OS
ctrl + alt + u brings up a dialog:
"No suitable Zmodem software wasfound on this system..."

"sleep 2; konsole" works though! it pauses and then opens Konsole as expected.


http://www.cameralibre.cc
Free Culture videos made with Free/Libre/Open Source Software about Open Hardware, Open Data, Open Everything
luebking
Karma
0
Sounds as if it doesn't the key grab and/or press state?

What if you run "sleep 5; konsole" (from eg. xterm), open a popup menu (NOT the alt+f3 titlebar menu, it will autp-close with new windows) and keep the up arrow pressed?

Since ctrl+alt+u seems somehow grabbed(?) try a random other combination (ctrl+alt+s etc.) to cross-check whether it is only this particular grab.

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], dcihon, Google [Bot], Sogou [Bot]