On Sun, Nov 13, 2016 at 6:36 PM, David C. Rankin
On 11/13/2016 11:16 AM, David C. Rankin wrote:
Alt + F2, then type 'xterm' (and hit return)
Make that Alt + F2, then type 'konsole' (and hit return)
Thanks for all the replies here on the thread. Well no I am not that kind of a noob :) , but I come across all kinds of weird stuff in my life, so sorry to disappoint. Even alt+f2 and running/typing konsole there fires up the konsole with an mc inside. All started pretty simple: Leap 42.2 system upgraded just the other day, wanted to mess with some files, so zypper in mc as root midnight commander appears in kde startmenu. I click it there. fires up a konsole with mc inside. Working with it a bit. Closing mc (f10) again. That konsole vanishes as well. Then every new konsole comes up with an mc inside, be it alt+f2, be it from kde start menu typing konsole there or selecting it from recent applications. So eventually, there must be some config file or resource stuff on the disk that tells some running stack of the kde to load some kterm with some subsequent command after that. Thats what I figured, as finally I even zypper rm mc as root and firing up a konsole via alt+f2 or kde start menu or recent applications, all give me a konsole, but with a red error message line at the very first message before the bash prompt, telling me some krunner or kstart or whatever I cant remember, was failing to trigger mcedit or was it only mc or whatever stuff. Eventually i logged out of the kde session and ctrl+alt+backspace several times or so, and relogging into kde again and the konsole now behaves again normally, even without that red error message it had before. So is this some very weird bug, does this need bugreport or more serious testing? I am feeling very frustrated many times over when I am experiencing the linux graphical interfaces world, maybe I have dwelt too long on the windows side of life and a lot of stuff on kde is just feeling fricken insane or absolutely incomplete unfinished and not even started to bake yet :( Or is most people constantly clean installing their stuff from scratch or never come across such bugs, or dont care or is this level of quality the standard of the linux or kde world? Where does this kstart or krunner or whatever it was called put its information into or take into consideration what apps or programs or scripts to fetch and start that tie into a konsole start? but i tried to grep for "mc" pretty much everywhere in my ~ directory, .* and* but i have seen no meaningful hits from grep when trying to find out why the heck a konsole would become populated with a midnight commander :( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org