Lorne Shantz wrote: >Yup. same thing here. I'm concerned that since there is never any response from >anyone that they aren't paying attention to some MAJOR issues. I'm growing >discouraged. The same issues will make it into the final release and their >credibility suffers. Quite a few major problems, but total silence. Even though I >donated money to the cause I can't even write a trouble ticket out without paying >them MORE money. ?? I'm pretty pissed off right now. > >The newer version of KDE does the same thing. If you log in as root it works, but >of course that isn't the proper way to go. A file or symbolic link is getting >deleted on shut down. I forget which one now, so I guess a work around is to copy >the file somewhere, then copy it back during boot up. ?? > >Praedor Tempus wrote: > >>As usual, KDE DCOP strokes out on a new login/restart. Doesn't matter if I >>shut down normally or not, upon the next startup here we go again...and of >>course artsd is broken too. It frickin' refuses to work at better than every >>so once in a while. I am running KDE 2.2.2 on Mandrake 8.1. Here are the >>excerpts from my .xsession-errors file: >> >>For DCOP: >> >>Loading required GL library /usr/X11R6/lib/libGL.so.1.2.030402 >>Creating link /home/praedor/.kde/socket-d152-159. >>Created link from "/home/praedor/.kde/socket-d152-159" to >>"/tmp/ksocket-praedor" >>DCOPServer up and running. >>Loading required GL library /usr/X11R6/lib/libGL.so.1.2.030402 >>Loading required GL library /usr/X11R6/lib/libGL.so.1.2.030402 >>kdeinit: Shutting down running client. >>kio (KLauncher): ERROR: KLauncher: KDEInit communication error! Commiting >>suicide! >>DCOP aborting (delayed) call from 'kded' to 'klauncher' >>--------------------------------- >>It looks like dcopserver is already running. If you are sure >>that it is not already running, remove /home/praedor/.DCOPserver_d152-159_:0 >>and start dcopserver again. >>--------------------------------- >> >>And here's artsd. Doesn't matter if I remove all mcop, .DCOP, >>~/.kde/socket-* nonsense, artsd will not work. It DID work yesterday and >>nothing has changed since then. It turns out to be hit or miss with artsd: >> >>warning: leaving MCOP Dispatcher and still 9 object references alive. >> - Arts::SampleStorage >> - Arts::Synth_MULTI_ADD >> - Arts::Synth_MULTI_ADD >> - Arts::Synth_PLAY >> - Arts::StereoVolumeControl >> - Arts::StereoEffectStack >> - Arts::Synth_BUS_DOWNLINK >> - Arts::SoundServerV2 >> - Arts::MidiManager >>warning: leaving MCOP Dispatcher and still 69 types alive. >>sound server terminated >>sh: -c: line 1: unexpected EOF while looking for matching ``' >>sh: -c: line 2: syntax error: unexpected end of file >>Loading required GL library /usr/X11R6/lib/libGL.so.1.2.030402 >>KMixPrefDlg::apply() >>okay >>sound server terminated >>warning: leaving MCOP Dispatcher and still 13 object references alive. >> - Arts::SampleStorage >> - Arts::Synth_MULTI_ADD >> - Arts::Synth_MULTI_ADD >> - Arts::Synth_PLAY >> - Arts::StereoVolumeControl >> - Arts::StereoEffectStack >> - Arts::Synth_BUS_DOWNLINK >> - Arts::SoundServerV2 >> - Arts::AudioManagerClient >> - Arts::Synth_BUS_UPLINK >> - Arts::Synth_PLAY_WAV >> - Arts::Synth_AMAN_PLAY >> - Arts::MidiManager >>warning: leaving MCOP Dispatcher and still 69 types alive. >>Can't connect to sound server >> >>What the hell does it take to make artsd actually work all the time? What >>files must I destroy to make artsd work again? Restarting artsd doesn't >>work. The correct kernel modules are loaded and the mixer is properly setup. >> >>praedor >> >> ------------------------------------------------------------------------ >>Want to buy your Pack or Services from MandrakeSoft? >>Go to http://www.mandrakestore.com >> > >-- > >Lorne Shantz >Note: Unfortunately if you send a message to me without it having my email >address specifically in a to or CC: field, I will not see it. This is because of >all the junk mail sent in this manner, so I've had to filter it. > > > > > Well, you get KDE the way it comes from KDE.org without mods beyond the menu and hiding some things that would be destructive to our system. And we donate money to them for a better product, too. Unfortunately, KDE 2.2.2 is a final bugfix on the 2.0 series (with a lot of bugs left unanswered) while kde.org is working on KDE3.0.
I am unsure what the usability of 3.0 will be. Seems more engineer's toys made it into the beta than in 2.2, and I hope some of those complexities go away. As for artsd.... Well we have several legislations against that one. First, the linux kernel isn't really designed for sound. It does not use a very high bandwidth for sound events. Next, the sound drivers are fragmented and in disarray. I have helped numerous individuals who somehow managed to be running both ALSA and OSS at the same time. (Thing is, XMMS will still sort-of cooperate so they think it is a driver error or some weird intermittent.) Anyway, neither OSS nor ALSA support all of them, and sometimes the dodges to install sound properly require a few incantations and a bit of voodoo. (For the SiS 735 chipset, chkconfig --del alsa then wipe the sound-slot-0 line from /etc/modules.conf then run sndconfig. For the SiS530, don't run sndconfig, but rather put esssolo1 in place of snd-ess1938 and chkconfig --del alsa.) A non-working DCOPserver is usually a sign of an improperly done update. We have found and fixed one in MandrakeUpdate, but going from, say, KDE 2.2.1 to 2.2.2 has its hazards. My approach is to urpme qt2 and then reinstall qt and kde and mostly I have no trouble with DCOP. Praedor, I saw an earlier post from you criticizing OpenOffice, but I see an error in your logic. You impute a motive of making a faster load then criticize the package on that basis. This might follow if such a motive existed, but it does not, at least not as a primary motive. The first reason to split the functionality among several packages was to minimize the bugs from what we call side effects--that is, the effects of one data handler on another, by moving the interoperation to strictly a function of the data file and not the programs themselves. A second and very important motivation was to make the data files OPEN, that is, not proprietary and readable by other programs very simply--via the use of XML. XML is not storage efficient, but with the size of today's hard disks, so what? At least you can write other programs to access the data without having to reverse-engineer the files. Now, following the first rule of program optimization: that is, the speed of a non-working program is irrelevamt, they want to achieve some stability on the primary objectives before optimizing the speed. Of course to say the load speed is slow one must have something to make a comparison with. I assume you are comparing it with Office of the microsoft kind. To make a fair comparison, load OpenOffice and roll it up on your desktop. Then unroll it when you want to use it and see if the load is comparable to Office. Because that is what Microsoft does behind its hidden system--they load most of Office at boot time and just add the interface when you call for it. Civileme >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
