if app does not detatch from tty, quicklauncher hangs

[Bruce Edge]

If an app started from quicklauncher does not background itself, then quicklauncher goes unresponsive, as is everything in the panel (except systray icons).

Killing the app lets applauncher run again and kicker works again too.

Specifically, I added an item to the kmenu that runs "screen -x" and uses "in a terminal window". This works fine from the kmenu. Starting this from quicklauncher hangs quicklauncher as described. When I kill the window, I get the message:

    KDEInit could not launch 'konsole'.

and then quicklauncher and kicker are fine again.

[Bruce Edge (bruce-edge)]

This is dapper current as of Feb 2:
ii kicker 3.5.1-0ubuntu7 desktop panel for KDE

[Francois-Denis Gonthier (fdgonthier)]

I cannot reproduce this, and I've tried your exact example. I'm running Dapper up to date as of March 22.

Does it still happen with the current Dapper? If so, I'll need a more detailed example.

[Bruce Edge (bruce-edge)]

I have a KDE menu item with the following settings:

Name: screen
Command: screen -x
Run in terminal: X

Nothing else checked.

There needs to be a screen session already running for "screen -x" to connect to. So, run "screen" in another console before trying this.

When this is in the quicklauncher, starting it from there yields the above problem.
When I terminate the konsole that it kicked off, I get a dialog stating:
KDEInit could not launch 'konsole'.

The panel is then responsive after that konsole is closed.

This is dapper updated 3/23.

[Francois-Denis Gonthier (fdgonthier)]

Hello, thank you for your good bug report.

I've done the exact steps you wrote and still cannot reproduce the problem. I add the item to the quicklauncher and when it starts I get the little dancing icon along with my cursor but nothing freezes and everything stay responsive.

[Bruce Edge (bruce-edge)]

Hi, Sorry for the difficult to reproduce issue.

I just updated my dapper install and reverified that it still hangs.

When you start konsole from the quick launcher, does it successfully connect to the already running screen session?
It doesn't exhibit the problem if there is no screen session already running for it to connect to.

[Francois-Denis Gonthier (fdgonthier)]

No. I see konsole appearing and then disappearing quickly. I just retried and still can't reproduce.

Randomly question: have you looked at your ~/.xsession-errors when or after that happens?

[Bruce Edge (bruce-edge)]

This implies that the "screen -x" command cannot attatch to a screen session.
Try this. In a different shell, run "screen". That will start the screen server.
Then try the quicklauncher to start the "screen -x" konsole.
When "screen -x" finds a screen session to attatch to, it will not disappear.

This is not related to ~/.xsession-errors, but I looked anyway, nothing of interest in there, just a bunch of ALSA complaints.

[Jonathan Jesse (jjesse)]

Good morning,

I noticed the last update for this bug is March of 2006. I am wondering if you are still having this problem on an up to date version of Dapper or if you have upgraded to Edgy and are still having problems with this bug.
Whether or not you are having problems w/ this report can you please update this page?

Thanks,

Jonathan

[Bruce Edge (bruce-edge)]

I've upgraded to edgy and this no longer happens.

Thanks, Bruce

[Jonathan Jesse (jjesse)]

I don't know what fix was released that changed this from a bug to a fix but according to original reporter this is working correctly in edgy.
https://launchpad.net/distros/ubuntu/+source/kdebase/+bug/32141/comments/9

Marking bug as fixed released.