Re: [suse-kde] How to make KDE the default for startx -- :1
--- Anders Johansson <andjoh@rydsbo.net> wrote:
On Saturday 16 April 2005 05:01, elefino wrote:
Is there a reason you suggested creating the link, rather than just editing lines in xinitrc? I'm not really good at implications unless they're spelled out, or I trip over them.
Functionally there's no difference, you could have solved your problem either way. It's just that if I have a choice between editing a script or creating a symlink, I'll go for the symlink.
The symlink is the 'correct' solution anyway, since the rpm should have created one, and I suspect the next update will again
-- ....snip.... I have upgraded & have same problem. Symlink however, still does not do the job. Error message received: "could not start kstartupconfig. Check your installation." Any ideas or useful pointers appreciated. ----robert To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
Have A Healthy, Prosperous Day!!Registered Linux User #356732 __________________________________ Do you Yahoo!? Plan great trips with Yahoo! Travel: Now over 17,000 guides! http://travel.yahoo.com/p-travelguide
On Sunday 17 April 2005 12:53 am, Robert Williams wrote:
The symlink is the 'correct' solution anyway, since the rpm should have created one, and I suspect the next update will again
-- ....snip....
I have upgraded & have same problem. Symlink however, still does not do the job. Error message received: "could not start kstartupconfig. Check your installation." Any ideas or useful pointers appreciated.
Look at the bin folders that Anders' symlink use. Make sure you have the kde and kdeinit or whatever the file should be, sitting there. I have deleted his message so I dont have it in front of me. Anyway, on my machine the files were missing so the link didnt do anything. I had to reinstall the kde stuff to get it all back. I think the problem came in when some files were deleted before the upgrade happened and those files were never reinstalled. So far my only problem has been on my laptop. The other machines upgraded without a hitch. Go figure. On the laptop I had to downgrade back to 3.3.3 to get it all working again. Richard
participants (2)
-
Richard -
Robert Williams