SUSE 10.0 STILL problem on KDE Exit

1kyle · 10-07-2005, 04:28 AM

I see on 10.0 the problem with exiting KDE into the console STILL hasn't been fixed (same prob as I've had with the BETA 4, RC1 and even the alpha 10.1)

This is now on the OFFICIAL SUSE 10.0

What happens is that when you logout of KDE ( I have RUN Level 3 as default) I get these messages

waiting for X sever to shut down kdeinit: Fatal IO error: Client killed
klauncher: Exiting on signal 15
kded: Fatal IO error client killed
starting artsd! (what on earth is THIS artsd ???? my comment here)

kcminit: cannot connect to X server 0:0

Now I press CTRL-Z

I then get message

[1]+ Stopped /usr/X11R6/bin/startx ${1+"$@"} 2>&1 | tee $HOME/ .Xerr

Then the normal console prompt

I can start X again or login as a different user

Any ideas -- it's not a mega problem but it's messy for a NEW release

also whats the artsd message --is that anything to do with it.

Cheers

-K

TigerLinux · 10-07-2005, 06:00 AM

this advised me to stick to suse 9.3 the stable version.

1kyle · 10-07-2005, 06:21 AM

Hi there -- it really is only a niggle -- 10.0 runs like greased lightning compare with 9.3. Anyway if I get / find a fix I'll post.

I had some Nvidia / X-configuration problems with 9.3 which started me on the upgrade path in the first place -- two desktops with Nvidia cards would never start X again once YAST was used to install ANY piece of software --never did get to the bottom of that problem and it was only on 2 out of 15 supposedly identical desktops --- but "generic Cloned " Nvidia cards made in different factories probably are sufficiently different for "Random" Hardware problems.

No probs on 10.0 other than the above and as I've posted elsewhere.

Cheers

-K

abisko00 · 10-07-2005, 07:27 AM

Quote:

Originally posted by 1kyle
what on earth is THIS artsd ???? my comment here

Quote:

http://www.linuxdj.com/audio/lad/resourcesapi.php
aRTs started as a modular synthesizer and has been generalized to become the backbone of the KDE multimedia architecture. Yet it depends neither on the KDE nor the Qt libs.
Since it is being distributed along with KDE, it already has a wide user base.
Unfortunately, aRTs has some fundamental problems operating in extreme-low-latency situations of professional harddisk recording. This is why alternatives were developed, although aRTs had been around already for quite a while. For normal desktop use however, it provides all you can dream of.

http://www.arts-project.org/

I know, this doesn't help with your problem, but it may answer your side-question.

TigerLinux · 10-07-2005, 10:02 AM

suse 10.0RC1 won't allow me to change ATI driver, what it detected is slightly different from the real one (ATI radeon 9200SE),
but suse 9.3 allow me to change,
why like that?

jayptr · 10-10-2005, 08:04 AM

I get a similar problem with KDE on shutdown. I don't seem to be getting the messages though. When I go to end my KDE session, the screen goes black but then the KDE taskbar reappears as though it has started back up or something, then it goes black and either reboots, shutdowns, or goes to login screen depending on what I chose. I am using the NVidia driver available through Yast. I have a AMD64 3500+ with an NVidia video card, and two WD Harddrives. I am using the x86_64 version of 10.0. I had been running my two drives in a software Raid 0, then switched to an LVM to see if KDE would continue doing this, and then just Linux Native partitions, such as swap and a reiserfs partition. Using standard Linux Native partitions, the problem in KDE disappeard.

Another problem I have also been having is during shutdown. When it goes through shutdown process, I get a missing in red , and failed in red on the right side. It appears to be on a line that has nothing on it to the left to identify what process is causing it, it appears just before the scripts that run for unmounting the hard drives.

I also forgot to mention that, I also getting a fuzzy screen when using the NVidia drivers. It seems to be whenever the screen has to clear and bring back X. Such as from login screen to KDE desktop and back. Sometimes turning off my flat LCD Monitor fixes it, other times it does not. I didn't seem to have this problem with the fuzzy display when I used native partitions either.

I did find if I added the second hard drive as a native partition during install or after install, the problems with the screen and KDE shutdown returned. It appears to be something with using two hard drives.

ferdybassi · 10-19-2005, 12:27 PM

Hi!
I'm experiencing exactly the same problem with SUSE 10.0...
Could you please explain me if and how you solved it?
Thanks in advance...
Ferdinando
ferdybassi@tin.it

1kyle · 10-20-2005, 03:36 AM

when you get back into the console just hit CTRL-Z and then you'll get the normal console prompt and you can continue.

It's not a major problem but would be nice to have it fixed so it looks "cleaner".

I mostly run Linux as a print, file and Mysql server so I don't need to use X very often on the server.

Cheers

-K