[opensuse-factory] Running konsole remotely
I run konsole remotely (ssh -X othermachine konsole). This may seem odd, but there are reasons why I find this useful - in particular that I can open a new tab in the same directory that I'm working in. With recent Tumbleweed versions I find that a new konsole run this way will become totally unresponsive for about 10 seconds the first time that I do a tab complete in bash inside it. If I run a konsole on a remote Leap 42.2, I don't see this issue. Can anyone shed any light on this? -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-06-28 11:51, Roger Whittaker wrote:
I run konsole remotely (ssh -X othermachine konsole).
This may seem odd, but there are reasons why I find this useful - in particular that I can open a new tab in the same directory that I'm working in.
Curious. It will run somewhat slower. You could try to use "tmux" instead. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Wed, Jun 28, 2017 at 12:11:17PM +0200, Carlos E. R. wrote:
You could try to use "tmux" instead.
Sure - I realise there are plenty of alternatives to what I'm doing, but I'm concerned by the fact that konsole in Tumbleweed seems to have fairly recently started behaving in this way. I guess not many people run it remotely, but this is odd... -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Roger Whittaker
I run konsole remotely (ssh -X othermachine konsole).
This may seem odd, but there are reasons why I find this useful - in particular that I can open a new tab in the same directory that I'm working in.
With recent Tumbleweed versions I find that a new konsole run this way will become totally unresponsive for about 10 seconds the first time that I do a tab complete in bash inside it.
If I run a konsole on a remote Leap 42.2, I don't see this issue.
Can anyone shed any light on this?
fwiw: I see the same unresponsiveness but a little longer than 10 seconds. I do not employe konsole in this manner, but tmux/yakuake. I can open a remote konsole from within the tmux session at a remote site and do not see the hang-ups. It basically accomplishes the same effect you describe of opening in the same directory but w/o the hang-ups -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Mittwoch, 28. Juni 2017, 10:51:08 schrieb Roger Whittaker:
With recent Tumbleweed versions I find that a new konsole run this way will become totally unresponsive for about 10 seconds the first time that I do a tab complete in bash inside it.
Are you sure it is about 10 seconds, and not 25s? ;-) This sounds like https://bugs.kde.org/show_bug.cgi?id=380974. In short, that 25s delay happens for every KDE application that tries to display a notification when no notifications service is running (or it cannot be found because you run the application as different user or via ssh). It's caused by changes in Plasma 5.10 and Frameworks 5.33.0, so doesn't exist in 42.2 (or 42.3 for that matter). If that is your problem, removing the file /usr/share/dbus-1/services/org.kde.plasma.Notifications.service should "fix" it (delete it or move it to a different directory, just renaming it won't help). There are two konsole bug reports that sound similar to your problem, and are likely have the same cause as the abovementioned bug: https://bugs.kde.org/show_bug.cgi?id=381115 https://bugs.kde.org/show_bug.cgi?id=380923 Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Jun 28, 2017 at 06:25:38PM +0200, Wolfgang Bauer wrote:
Am Mittwoch, 28. Juni 2017, 10:51:08 schrieb Roger Whittaker:
With recent Tumbleweed versions I find that a new konsole run this way will become totally unresponsive for about 10 seconds the first time that I do a tab complete in bash inside it.
Are you sure it is about 10 seconds, and not 25s? ;-)
Well - I didn't have a stopwatch...
This sounds like https://bugs.kde.org/show_bug.cgi?id=380974.
Yes.
In short, that 25s delay happens for every KDE application that tries to display a notification when no notifications service is running (or it cannot be found because you run the application as different user or via ssh). It's caused by changes in Plasma 5.10 and Frameworks 5.33.0, so doesn't exist in 42.2 (or 42.3 for that matter).
If that is your problem, removing the file /usr/share/dbus-1/services/org.kde.plasma.Notifications.service should "fix" it (delete it or move it to a different directory, just renaming it won't help).
Yes - this works.
There are two konsole bug reports that sound similar to your problem, and are likely have the same cause as the abovementioned bug: https://bugs.kde.org/show_bug.cgi?id=381115 https://bugs.kde.org/show_bug.cgi?id=380923
I opened an openSUSE bug (1046458) - I'll make a note there of this discussion. Thanks very much. -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Carlos E. R. -
Patrick Shanahan -
Roger Whittaker -
Wolfgang Bauer