Bug 169341 - KDE starts different application on startup, then what was saved on logout
Summary: KDE starts different application on startup, then what was saved on logout
Status: RESOLVED WORKSFORME
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-18 09:52 UTC by Gergely Czuczy
Modified: 2008-08-19 13:15 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gergely Czuczy 2008-08-18 09:52:40 UTC 
Version:            (using KDE 4.1.0)
Compiler:          gcc (GCC) 3.4.6 [FreeBSD] 20060305 
OS:                FreeBSD
Installed from:    FreeBSD Ports

I "run..." /usr/local/bin/kopete (that's 3.5), because the kopete in 4.1 has some serious bugs (unable to connect to msn and gtalk). When i log out, KDE tries hard to save my session, but when I log on, it starts /usr/local/kde4/bin/kopete. So I'm using /usr/local/bin/kopete, but KDE confuses it with /usr/local/kde4/bin/kopete.
Comment 1 Lubos Lunak 2008-08-19 12:31:31 UTC 
You probably just need to modify your /usr/local/bin/kde3 script to set PATH to find the KDE3 version and run Kopete using this script.
Comment 2 Gergely Czuczy 2008-08-19 12:50:39 UTC 
I am _do_ using KDE4 with kodepete from 3.5.8. So, fixing /usr/local/bin/kde3 won't help much, since i'm using kde4.
Comment 3 Lubos Lunak 2008-08-19 13:15:15 UTC 
How about you actually try it? And either way, writing paths to binaries in session has more disadvantages than advantages, so if you don't like the official solution, create a wrapper script that will launch the proper binary.