Bug 181522 - Starting a second konsole displays error popup or crashes plasma
Summary: Starting a second konsole displays error popup or crashes plasma
Status: RESOLVED DUPLICATE of bug 181477
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-kickoff (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-21 20:38 UTC by Christopher Neufeld
Modified: 2009-01-21 23:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Neufeld 2009-01-21 20:38:24 UTC
Version:            (using Devel)
Compiler:          gcc-4.2.4 
OS:                Linux
Installed from:    Compiled sources

Sometime after revision 902646, a problem appeared in the launching of konsoles.  I have a convenience konsole icon in a folder view on the desktop.  Launching the first konsole is fine.  If a second is launched without closing the first, the konsole appears, but a popup also appears with the message:  "KDEInit could not launch '/usr/local/kde4/bin/konsole'."

If I try to launch a konsole from the K Menu System->Terminal, it crashes plasma, but the new konsole window still appears.

It is possibly informative that launching a second konsole window does not create a new process or a new thread.  Launching the first konsole window creates the konsole process, but new windows launched separately feed off that original process without spawning any new process table entries.

My uninformed speculation is this:  something in changeset 911168 doesn't like it when a new application is launched that doesn't create a new process.
Comment 1 Christopher Neufeld 2009-01-21 20:52:00 UTC
One revision that exhibits the problem is 914691.
Comment 2 Dario Andres 2009-01-21 23:52:07 UTC
The plasma crash when launching an app from KMenu is another already reported issue :) Thanks

*** This bug has been marked as a duplicate of bug 181477 ***