Re: [SLE] kde 3.4 oops
From: BandiPat (penguin0601_at_earthlink.net)
Date: 03/18/05
- Previous message: CorvusE: "[SLE] KDE 3.4 and System Notification Problem SOLVED"
- In reply to: Joe Morris (NTM): "Re: [SLE] kde 3.4 oops"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: suse-linux-e@suse.com Date: Fri, 18 Mar 2005 13:26:52 -0500
On Friday 18 March 2005 10:21 am, Joe Morris (NTM) wrote:
> Mike wrote:
> >On March 18, 2005 03:00 am, Darryl Gregorash wrote:
> >>Mike wrote:
> >>>Big bunch of patches yesterday upgraded to kde 3.4. When I
> >>> restart I now get fvwm as my windowmanager.
> >>
> >>Make sure there is a soft link /usr/X11R6/bin/kde -->
> >>/opt/kde3/bin/startkde. Then run wmlist and see if it returns kde
> >> as one of the available managers (it should). If necessary, you
> >> can set the environment variable WINDOWMANAGERLIST=kde in
> >> ~/.xinitrc
> >
> >Thanks for the confirmation.
> >
> >The next question is why was the link removed during the upgrade?
>
> Not sure if this will help, but I used apt to upgrade to 3.4, and
> noticed in the process there was a new rpm, kdebase3_session. Since
> I usually have apt to only upgrade what I have installed, it was not
> autoselected, but I selected it and installed it, and other than my
> older kdmrc file needing updating, I didn't have any problems. HTH.
> --
> Joe Morris
> New Tribes Mission
> Email Address: Joe_Morris@ntm.org
> Registered Linux user 231871
==========
Ok, Joe has hit upon a couple of things here that corrects some problems
with KDE 3.4 files. As this discussion has again appeared on the main
list as well as the suse-kde list, I'll address it here to possibly a
wider audience.
Joe, whether by mistake or you actually knew to include in your mail, it
was the needed info I needed to track down at least two problems.
Several, including myself complained about no longer being able to log
into KDE as root. It would either just stop or lock up. I know why
would you want to and I don't, but I don't like it not working either.
I too had missed the file kdebase3-sessions when I updated, so did
indeed install that and suddenly issuing the "wmlist" command showed
kde again. It also shows gnome, but that's not in the list at the
login screen. I haven't figured that one out yet. Ok, so one problem
solved.
The next thing you mention is the kdmrc file you had to update. I
checked and checked that file many times, but never came up with
anything until I thought about regenerating it. Usually if it's been
altered sometime by the user, it's not overwritten or "fixed" when
SuSE-config runs. What I did was to run "/opt/kde3/bin/genkdmconfig",
which does generate new files, kdmrc included
in /etc/opt/kde3/share/config/kdm/. Once doing this, things worked for
root and still worked well for user logins to kde! In your login
screen, things go back to default, but that's easily fixed later in the
control center. Oh, I might add, after running the genkdmconfig
program, you should restart KDE by dropping to init 3 then back to init
5.
Thanks Joe, whether you knew what you did or not! ;o)
Now if I can get gnome to show up in the sessions menu, things will be
back to normal.
Cheers,
Lee
--
--- KMail v1.8 --- SuSE Linux Pro v9.2 ---
Registered Linux User #225206
Sign at college bookstore:
Accepted at more colleges than you were--VISA
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
- Previous message: CorvusE: "[SLE] KDE 3.4 and System Notification Problem SOLVED"
- In reply to: Joe Morris (NTM): "Re: [SLE] kde 3.4 oops"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
