Re: IMPORTANT PROBLEMS AFTER INSTALL KDE 3.4.1 ON SUSE 9.2 PROFESSIONAL

Sebastian Koerner <[email protected]>
Newsgroups gmane.linux.suse.programming
Message-ID <[email protected]>
Am Sonntag, 5. Juni 2005 16:56 schrieb Franz Bernasek:
> Dear SUSE,
Wrong number. In my opinion this is a user-to-user Mailinglist. You might want 
to contact suse support.

> now as User from SuSE 9.2 Professional i have upgrade my KDE to 3.4.1
> the complete week all is running normal after the Upgrade with install
> of the KDM Part from KDE .3.4.1 i never can login as ROOT (SU) i use
Where did you get KDE 3.4.1 for SuSE 9.2? From here
ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.2 ?
Well
ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.2/yast-source/content
says 

LABEL.de inoffizielles KDE 3.4 update
LABEL supplementary KDE 3.4 update

You probably won't get support for the kind of update you have done. If you 
have a problem with KDE you should use the System Update function in your 
yast tool. This gives you supported SuSE Updates for a long time

> the reason of this error, where can i fix it ?, its IMPORTANT.
WE UNDERSTOOD AFTER READING THE SUBJECT LINE.

> (3.4.1 KDM) then after my vacation (11.6 to 25.6) we change from SUSE to
> REDHAT.
Very charming! Is this the normal behaviour of businessmen nowadays? Just fix 
what I have messed up. I give you two weeks or I buy from a different 
company? Did this method ever work for you?

If you want help from these Mailing-Lists:
- Use the appropiate list suse-kde (not this one suse-programming)
- Say what you have done step by step
- Say what your System and KDE Version before/after is
- Provide log files like .xsession-errors, kdmlog, messages

Sebastian

-- 
Um die Liste abzubestellen, schicken Sie eine Mail an:
    [email protected]
Um eine Liste aller verfügbaren Kommandos zu bekommen, schicken
Sie eine Mail an: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.