Failure of "Konsole" thru' 'No protocol specified'

**thebigming** · 29-Aug-2018, 11:27

A few days ago the Konsole on Tumbleweed became unusable. It had been running perfectly well; I had been using it but closed it down while I went off and worked at something else; when I tried to re-open it, during the same session, it started opening multiple windows, totally filling the screen, each one bearing the logo "No protocol specified".

I've hunted around on the internet and found a few references to the "Nps" message, most of which, I confess, I didn't understand & didn't seem to be relevant to me anyway. I've fired up the Gnome terminal but I don't like much. I want to get back to Konsole.

I've tried removing & re-installing Konsole (nbg) and also I have rather hoped that the Tumbleweed updates I've done might correct something (no). If anyone would be interested I have backups of the output from the updates but they are seriously long documents - there are close to 1000 items thru' August..

I'm at my wits end! Ok,. I could simply expunge & reload Tumbleweed, though that seems defeatest; I can soldier on with Gnome-Terminal but I don't want to; and I cant help thinking that writing a protocol can't be that complicated (although advice on that seems thin on the internet).

Any advice will be gladly received.

dmk

**gogalthorp** · 29-Aug-2018, 13:38

Try a test user may be a problem in your cofig files

**wolfi323** · 29-Aug-2018, 13:45

And how exactly are trying to start Konsole?

Does it work if you run "konsole" in xterm e.g.?

**thebigming** · 31-Aug-2018, 02:21

Wolfi - Thanks for your reply - Xterm runs fine. I've never used it because, in comparison with Konsole, it's always seemed limited but yes Xterm & Gnome-Terminal are both good. I tried running Konsole from within Xterm but got the same screenful of "Nps" messages.

dmk

**nrickert** · 31-Aug-2018, 04:47

There's possibly something broken in the configuration for "konsole". And I'm referring to your personal configuration (user settings).

The configuration uses: "~/.config/konsolerc"
and one or more profiles in directory "~/.local/share/konsole"

If you just want to get it working, then try:

Code:

cd
rm .config/konsolerc
rm .local/share/konsole/*.*

That should get you back to the initial setup of "konsole".

If you want to debug this, then you could instead rename the files and directories, and later compare the old version with the new versions.

**thebigming** · 31-Aug-2018, 08:49

nrickert - Thanks for that, I'll have a butchers toot and sweet BUT I logged on for something which may well have some bearing on the matter!

This afternoon I installed 'gparted' to do something but I couldn't get it to run so tried launching from the Gnome-Terminal:

Bash - 4.4.23 : gparted
Unit boot.mount does not exist, proceeding anyway.
Unit sysroot.mount does not exist, proceeding anyway.
Unit usr-share.mount does not exist, proceeding anyway.
Unit usr.mount does not exist, proceeding anyway.
Unit var.mount does not exist, proceeding anyway.
No protocol specified
No protocol specified

Well I never! I'm on to your comments right away and will get back shortly

Thanks again

dmk

**nrickert** · 31-Aug-2018, 12:34

There must be something else going on. Apparently that "No protocol specified" is not just konsole.

As a test, I just tried "gparted" from a root xterm. And I got a bunch of "does not exist, proceeding anyway" messages. But "gparted" then started.

Hmm, maybe I should try starting as an ordinary user instead of as root: Okay, tried that. It was the same as starting as root, except that I was also asked for the root password. But that prompt for root password was before any of those "does not exist" messages.

Are you running KDE on X11 or are you running it on Wayland? My tests have been with X11.

**thebigming** · 31-Aug-2018, 16:36

nrickert - sorry about the delay. I'm afraid "stuff" (i.e a few drinks + dinner) delayed me. However your first answer - "delete ~/.config/konsolerc and one or more profiles in directory ~/.local/share/konsol" - worked fine (apart from the fact that there was no ~/.config/konsolerc) and I now have Konsole back up and running, for which I'm very grateful.

However, the problem with gparted persists but it's 28 minutes past midnight where I am. Time to take my mug of Horlicks up to bed, don my nightcap & start piling up the Z's.

Thanks for your help

dmk

**thebigming** · 31-Aug-2018, 16:44

nrickert - Sorry, I didn't answer your question. I have, I'm ashamed to say, no idea of what Wayland is. I would assume I'm working on X11.

dmk

**nrickert** · 31-Aug-2018, 17:27

Originally Posted by thebigming

nrickert - Sorry, I didn't answer your question. I have, I'm ashamed to say, no idea of what Wayland is. I would assume I'm working on X11.

Wayland is an alternative graphic management system that might one day replace X11. Gnome works pretty well on Wayland, but KDE still only has incomplete support.

Yes, you are probably using X11. If you were using Wayland, you would know.

So I fired up KDE on Wayland in Tumbleweed. And "gparted" still works fine here with Wayland.