You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Thursday, March 3rd 2005, 5:33am

artsd soundserver crash

Soundserver (artsd) crash in MDK 10.0 upon boot opening of KDE and every 5-6 seconds until there are 15 or 20 KDE crash notices. Can open everything and everything seems to work but this is beyond annoying. These crash notices open as soon as they are closed and just keep coming.
Have tried to reload defaults in MCC and KDE configuration.
Any ideas?
Thanks

2

Thursday, March 3rd 2005, 11:07am

hi,

because of your rare information :) I just can guess:
1) what version of kde are you running?
2) which kernel?
3) did you change your kernel/modules?
4) post lsmod
5) which soundcard do you have?
6) do you use a soundserver (arts, esound)?
7) do you get any messages in ~/.xsession-errors or on your syslog?

hth,
cheers

3

Thursday, March 3rd 2005, 7:21pm

soundserver crash

Here is info you asked for. This PC has been running fine sincemdk 10.0 install 3 mo. ago. Power was accidentally shutoff 2 wks ago and kde went away, but went into MCC and reselected KDE under boot options and all has been OK until this.

Mandrake Linux 10.0
kernel 2.6.3-7
KDE 3.2
sound card: cmedia cm8738
I have not changed any kernels or mods that I know of. New to linux...I wouldn't even know how.
Don't know what soundserver is... my KsCD music player is working fine
error message is in KDE crashhandler popup..it says:
"soundserver (artsd) crashed and caused signal 6 sigabrt"


# lsmod

[mark@localhost mark]$ lsmod
bash: lsmod: command not found
[mark@localhost mark]$ su
Password:
[root@localhost mark]# lsmod
Module Size Used by
sg 38044 0
st 38616 0
sr_mod 17028 0
sd_mod 16832 0
scsi_mod 114648 4 sg,st,sr_mod,sd_mod
i810 72032 30
parport_pc 32832 1
lp 12200 0
parport 38952 2 parport_pc,lp
snd-seq-oss 31232 0
snd-seq-midi-event 7552 1 snd-seq-oss
snd-seq 51024 4 snd-seq-oss,snd-seq-midi-event
snd-pcm-oss 51812 0
snd-mixer-oss 17952 1 snd-pcm-oss
snd-cmipci 33236 1
snd-pcm 93156 2 snd-pcm-oss,snd-cmipci
snd-page-alloc 11972 1 snd-pcm
snd-opl3-lib 9984 1 snd-cmipci
snd-timer 24484 3 snd-seq,snd-pcm,snd-opl3-lib
snd-hwdep 8928 1 snd-opl3-lib
gameport 4480 1 snd-cmipci
snd-mpu401-uart 7072 1 snd-cmipci
snd-rawmidi 23616 1 snd-mpu401-uart
snd-seq-device 8008 4 snd-seq-oss,snd-seq,snd-opl3-lib,snd-rawmidi

hope this helps
Thanks for the time

4

Thursday, March 3rd 2005, 7:56pm

hmmm, could you please try to log into kde with a "new" user. this means: add an user with (g.e. kuser) and logoff to kdm and logon with the new user....
you also (easier way :)) backup your ~/.kde dir and remove it and login with a "clean" kde installation... perhaps it's just something with config files...

hth,
cheers

5

Friday, March 4th 2005, 5:08am

artsd crash

Yeeaahhh! OK....created new user, logged in and so far no crashes. This means something in my personal config got messed up, but I tried to reset all defaults.
Would a fsck be of any use?
1. What is best way to transfer my existing files to the new user home folder.
2. You said something about backup ~./kde and reload a fresh install of KDE. Am new to linux and CL. I have no idea how to do this. Would it be better to reinstall the OS. Since I don't have a lot of files I could do this in 20 min.
Thanks for the tips!

6

Friday, March 4th 2005, 8:00am

RE: artsd crash

Quoted

Would a fsck be of any use?

well you could make one, but I don't think that it concerns your problem...

Quoted

1. What is best way to transfer my existing files to the new user home folder.

hmmm you mean your files or you kde configs?
your files you can simply copy to your new user account by being root:
root$ cp /home/<olduser>/* /home/<newuser>
root$ chown -R <newuser>:users /home/<newuser>
with this cmd you copy the files and assign them permissions for your new user...
but you don't have to use the new user -> this was just a test.
if you didn't make any significant settings in kde you can simply delete your ~/.kde directory. when logging in to kde you will get a plain installation and the crashes should stop either...

Quoted

Would it be better to reinstall the OS

hey! we are not under windows! don't to this!! :)
the max. is that you reinstall kde but this does also not concern your problem since it seems to be something with config files :)

hth,
cheers

7

Saturday, March 5th 2005, 5:29am

artsd crash and copying files

Am able to use cp to copy files to new user, but not whole folders, which would be faster. Keeps saying ....omitting folder. Also could you please explain exactly how to reinstall kde for the user who has crashes, using the delete ~/kde? Am new to CLI.
thanks

8

Saturday, March 5th 2005, 8:34am

RE: artsd crash and copying files

hi,

you could also copy the files with konqueror using the "superuser" mode.
you can start konqueror in superusermode using: "kdesu konqueror"
copying the files via the CLI: "cp -R <from> <to>" -R means recursive :)

cheers

9

Saturday, March 5th 2005, 7:13pm

new crash scenario

OK....new crash scenario.
MDK 10.0
KDE 3.2

In the process of installing flashdrive for bigger files, I noticed that inserting the flashdrive froze the system and would have to hard boot.
Enter new problem ...on boot, I get to LILO screen>enter linux> get X screen, then instead of KDE, get terminal window in lower right with no borders. Prompt responds sporadically...or not at all, have had to hard boot several times now. When I do get a response I type in “KDE” and receive :
“fatal server error”
server is already active for display0
Have tried rescue with floppy and CD but receive error messages and even if they worked, I've never repaired or would know how.
This is my test PC. Files are not important, although I would like all of my bookmarks in Konqueror. Tried kdesu konqueror...this brings up GUI in lower right corner with no title bar, no borders, no scroll bar, but I do have menu bar available.I do not have access to taskbar on bottom...therefore no logoff or terminal thru GUI. But I can type in a path in location bar.
I think something is really messed up.
How recoverable is linux from a serious crash?
Unfortunately, I will have to set a deadline of this weekend to bring this PC back to life. If not, I will continue using MDK10.0 on another PC and try FC 2 on this one.
Any ideas?
Thanks

This post has been edited 2 times, last edit by "Trio3b" (Mar 5th 2005, 7:25pm)


10

Saturday, March 5th 2005, 7:30pm

RE: new crash scenario

hi,

sorry, I think you have greater problems :)
perhaps with X/QT... (no borders point IMHO to wrong settings in kde concerning the theme/style or a broken qt installation)
or did you do anything with your ~/.kde config files?

you of course can backup the bookmarks from konqueror.
they are in: ~/.kde/share/apps/konqueror

hth,
cheers