By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 93 - KDE3 starts KDE4 "Plasma" without asking
Summary: KDE3 starts KDE4 "Plasma" without asking
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: other (any) (show other bugs)
Version: 3.5.10
Hardware: Other Linux
: P5 enhancement
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2009-05-24 16:01 CDT by Vanessa Ezekowitz
Modified: 2014-03-02 18:02 CST (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
"default" state of KDE3/KDE4, with 'ps' output (attachment corrupted) (602.53 KB, image/png)
2009-05-24 16:01 CDT, Vanessa Ezekowitz 		Details
Output from env. (2.43 KB, text/plain)
2009-06-05 20:29 CDT, Vanessa Ezekowitz 		Details
Output from ps axuwww to go with the env output. (16.75 KB, text/plain)
2009-06-05 20:32 CDT, Vanessa Ezekowitz 		Details
output from the above cat command. (347 bytes, text/plain)
2009-06-05 20:52 CDT, Vanessa Ezekowitz 		Details
Output from locate and dpkg. I took a guess and figured you wanted the /usr/bin/plasma-desktop line applied to dpkg. (964 bytes, text/plain)
2009-06-05 21:19 CDT, Vanessa Ezekowitz 		Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vanessa Ezekowitz 2009-05-24 16:01:26 CDT 
Created attachment 7 [details]
"default" state of KDE3/KDE4, with 'ps' output (attachment corrupted)

In our house are three boxes, two of which run Jaunty with your KDE3 packages.  On one of these (my husband's) has KDE 4.2 installed as well.  On that machine, starting a KDE3 session (via kdm-kde3) causes the KDE4 "plasma-desktop" program to start up at log-in, resulting in an odd mixture of KDE3 and KDE4 bits running together.  There appears to be no way to stop this behaviour, meaning it has to be killed manually each time one logs in.  We've already tried logging out, deleting the .kde/, .kde3/, .qt/ directories and the .kderc file in case any of these is corrupt, and then logging back in, with no success.

My box only has a bare minimum of KDE4-related programs installed, and hence does not have this happen on it.

Attached is a screenshot showing the result, which in this case also represents the default state of the KDE3/KDE4 mixture before any programs have been run or any customizations have been made following the deletion of the above-mentioned directories.  The terminal showing the output from 'ps' is current as of a few seconds before the screenshot was taken.

(Incidentally, the third box still runs Hardy because I'm too lazy to update it ;) )
Comment 1 Timothy Pearson 2009-06-05 15:36:43 CDT 
When KDE3.5 is installed, a new wrapper should be created around plasma.  If this wrapper detects the environment variable DESKTOP_SESSION=kde3 it does not lauch plasma.

It sounds like this variable is either not set or is being ignored.  Can you post the output of env from a Konsole session under KDE3.5 while the odd 3/4 combination is happening?

Thanks!
Comment 2 Vanessa Ezekowitz 2009-06-05 20:29:23 CDT 
Created attachment 8 [details]
Output from env.
Comment 3 Vanessa Ezekowitz 2009-06-05 20:32:04 CDT 
Created attachment 9 [details]
Output from ps axuwww to go with the env output.
Comment 4 Timothy Pearson 2009-06-05 20:45:17 CDT 
OK, that looks good.

What is the output if you go to a terminal and type: cat /usr/bin/plasma

If it is text, can you post it here so I can verify it?  If it is a bunch of odd characters (i.e. a binary file), then there is something else wrong, and I don't need or want it posted here.

Thanks!
Comment 5 Vanessa Ezekowitz 2009-06-05 20:52:17 CDT 
Created attachment 10 [details]
output from the above cat command.
Comment 6 Timothy Pearson 2009-06-05 21:07:59 CDT 
I think I see the problem...

It looks like plasma itself did not start, but plasma-desktop did.  Can you run a couple more commands so that I can start fixing this?

First:
locate plasma-desktop

Then, take the output of that command and run
dpkg -S <output of above command>

and post the output of both commands?  That should give me the information needed to duplicate the issue here.

Thanks!
Comment 7 Vanessa Ezekowitz 2009-06-05 21:19:14 CDT 
Created attachment 11 [details]
Output from locate and dpkg.  I took a guess and figured you wanted the /usr/bin/plasma-desktop line applied to dpkg.
Comment 8 Timothy Pearson 2009-06-05 21:34:38 CDT 
(In reply to comment #7)
> Created an attachment (id=11) [details]
> Output from locate and dpkg.  I took a guess and figured you wanted the
> /usr/bin/plasma-desktop line applied to dpkg.

You guessed correct!

I think I have everything I need; look for a patch in the next couple of weeks at most.
Comment 9 Timothy Pearson 2009-06-17 00:40:05 CDT 
This should now be fixed; can you upgrade, test, and report back?

Thanks!
Comment 10 Vanessa Ezekowitz 2009-06-18 10:09:14 CDT 
After three successful reboots (we generally shut down at night), this does indeed appear to be fixed.  Thanks!
Comment 11 Timothy Pearson 2009-06-18 14:34:53 CDT 
Great!

Thanks for reporting!