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 384 - plasma-desktop.kde4 is started along with trinity
Summary: plasma-desktop.kde4 is started along with trinity
Status: RESOLVED INVALID
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: 3.5.12 [Trinity]
Hardware: amd64 Other
: P5 critical
Assignee: Timothy Pearson
URL:
Depends on: 274
Blocks:
  Show dependency treegraph
 
Reported: 2010-12-12 08:00 CST by Francois Andriot
Modified: 2012-10-19 15:13 CDT (History)
3 users (show)

See Also:
Compiler Version: gcc-4.4
TDE Version String: trinity 5:54 /kde-Plasma 5:64
Application Version:
Application Name: plasma-desktop.kde4 / kdm-trinity


Attachments
Ugly fix to prevent plasma-desktop launch (92 bytes, patch)
2011-06-25 16:00 CDT, Francois Andriot
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Francois Andriot 2010-12-12 08:00:42 CST
Hello,
I've compiled Trinity 3.5.12 final from sources on RHEL 6.0, and I've got the exact same issue as described below.
Trinity starts normally, but just after it's finished loading, there is a plasma desktop from KDE4 appearing along with the KDE3 Desktop !

Where should I look for ?


+++ Ce bogue a été initialement cloné à partir du bogue numéro 274 +++

after starting the trinity-desktop via kdm (selection trinity) or "/opt/trinity/bin/startkde" from the console the plasma-desktop.kde4 will be startet too. (That means trinity and kde4 is overlapping; "2 kicker-applets, 2taskbars (the kde4-kicker for example doesn't allow to log out)  

I have to kill the process of "plasma-desktop.kde4" and afterwards the trinity desktop is working as it should be.

How can I avoid that plasma-desktop.kde4 (kde4) is startet too when I selected trinity from kdm (or /opt/trinity/bin/startkd from console) ?

(my system: debian-squeeze, i386, trinity was installed after kde4)

I can start kde4 from kdm for example without any problem.

Thank you very much for your help in advance !
Comment 1 Francois Andriot 2011-06-25 16:00:49 CDT
Created attachment 68 [details]
Ugly fix to prevent plasma-desktop launch

Place this script in your PATH (ex: /opt/trinity/bin/) BEFORE the actual /usr/bin/plasma-desktop.
The script will be launched by Trinity instead of the actual plasma-desktop, and exit immediatly.
Comment 2 Francois Andriot 2011-10-26 16:16:48 CDT
Arg, this issue is back with kdebase 3.5.13 (SVN 1260901) under Fedora 15 !
The same version under RHEL 6 does not seem to be affected.

I guess I will need my old wrapper script again !
Comment 3 Timothy Pearson 2011-10-26 16:58:17 CDT
This is a KDE4/distribution bug, not a Trinity one.  Workarounds can be posted to this bug report, but I am going to mark it as invalid since we have no control over the KDE4 source code.

By the way a similar problem apparently can exist with Gnome--it really depends on the quality of the distribution's KDE4 packages.
Comment 4 Timothy Pearson 2011-10-26 16:59:30 CDT
(In reply to comment #3)
> This is a KDE4/distribution bug, not a Trinity one.  Workarounds can be posted
> to this bug report, but I am going to mark it as invalid since we have no
> control over the KDE4 source code.
> 
> By the way a similar problem apparently can exist with Gnome--it really depends
> on the quality of the distribution's KDE4 packages.

Typing too fast--that last line should read "on the quality of the distribution's desktop base packages.