Hi all, Anyone else ventured into installing the new SuSE KDE 3.4 files yet? Remember the problem with the system sounds concerning the new arts files last time? Well, it seems they are back with the new 3.4 files too. It seems as simple a solution to fix though. I just recompiled the SuSE src.rpm to my system and sounds work nicely again. Don't know what's happening with those arts files or what Adrian is compiling them on, but they certainly don't seem to work. As far as the rest of KDE 3.4, it's looking pretty cool. Some new eye candy and features abound. Speed doesn't seem bad, but of course, I know this will improve substantiately with KDE 4. That is what I'm hearing at least. Thanks SuSE for the updates and maybe Adrian might let one of us compile the arts files for him next time! ;o) 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
On Thursday 17 March 2005 05:23, BandiPat wrote:
Hi all, Anyone else ventured into installing the new SuSE KDE 3.4 files yet?
Yup. Installed them yesterday (16th) morning. No problems at all so far.
Remember the problem with the system sounds concerning the new arts files last time?
Please refresh my memory. :)
Well, it seems they are back with the new 3.4 files too.
Really? I have arts-{,devel-}1.4.0-8.i586.rpm installed (arts-gmcop is not installed). Seems to work well.
It seems as simple a solution to fix though. I just recompiled the SuSE src.rpm to my system and sounds work nicely again. Don't know what's happening with those arts files or what Adrian is compiling them on, but they certainly don't seem to work.
Well, this working/non-working state of arts must depend on something that is different from my and your system.
Speed doesn't seem bad, but of course, I know this will improve substantiately with KDE 4.
Hmm, interesting! :)
Thanks SuSE for the updates and maybe Adrian might let one of us compile the arts files for him next time! ;o)
Just mark yours with arts-bandipat. ;) Adrians arts packages do work over here. Cheers, Leen
On Thursday 17 March 2005 07:00 am, Leendert Meyer wrote:
On Thursday 17 March 2005 05:23, BandiPat wrote:
Hi all, Anyone else ventured into installing the new SuSE KDE 3.4 files yet?
Yup. Installed them yesterday (16th) morning. No problems at all so far.
Remember the problem with the system sounds concerning the new arts files last time?
Please refresh my memory. :)
Well, it seems they are back with the new 3.4 files too.
Really? I have arts-{,devel-}1.4.0-8.i586.rpm installed (arts-gmcop is not installed). Seems to work well.
It seems as simple a solution to fix though. I just recompiled the SuSE src.rpm to my system and sounds work nicely again. Don't know what's happening with those arts files or what Adrian is compiling them on, but they certainly don't seem to work.
Well, this working/non-working state of arts must depend on something that is different from my and your system.
Speed doesn't seem bad, but of course, I know this will improve substantiately with KDE 4.
Hmm, interesting! :)
Thanks SuSE for the updates and maybe Adrian might let one of us compile the arts files for him next time! ;o)
Just mark yours with arts-bandipat. ;) Adrians arts packages do work over here.
Cheers,
Leen =============
Hi Leen, I just built mine with a different build number to separate them actually. Maybe the gcomp file is the breaking point then, because I have all three files installed. I hadn't even considered that one file might be causing the problems with it all. If you are running a basic 9.2 system, only updating from the SuSE mirrors and Packman, then our systems are alike! I've been pretty prudent with 9.2 and everything has worked well because of that. Might be a nice experiment then, to have you install the third file to see if it breaks things? :o) later, 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
On Thursday 17 March 2005 14:53, BandiPat wrote:
On Thursday 17 March 2005 07:00 am, Leendert Meyer wrote:
On Thursday 17 March 2005 05:23, BandiPat wrote:
Hi all, Anyone else ventured into installing the new SuSE KDE 3.4 files yet?
Yup. Installed them yesterday (16th) morning. No problems at all so far.
Remember the problem with the system sounds concerning the new arts files last time?
Please refresh my memory. :)
Well, it seems they are back with the new 3.4 files too.
Really? I have arts-{,devel-}1.4.0-8.i586.rpm installed (arts-gmcop is not installed). Seems to work well.
It seems as simple a solution to fix though. I just recompiled the SuSE src.rpm to my system and sounds work nicely again. Don't know what's happening with those arts files or what Adrian is compiling them on, but they certainly don't seem to work.
Well, this working/non-working state of arts must depend on something that is different from my and your system.
Speed doesn't seem bad, but of course, I know this will improve substantiately with KDE 4.
Hmm, interesting! :)
Thanks SuSE for the updates and maybe Adrian might let one of us compile the arts files for him next time! ;o)
Just mark yours with arts-bandipat. ;) Adrians arts packages do work over here.
Cheers,
Leen
=============
Hi Leen, I just built mine with a different build number to separate them actually. Maybe the gcomp file is the breaking point then, because I have all three files installed. I hadn't even considered that one file might be causing the problems with it all. If you are running a basic 9.2 system, only updating from the SuSE mirrors and Packman, then our systems are alike! I've been pretty prudent with 9.2 and everything has worked well because of that.
Might be a nice experiment then, to have you install the third file to see if it breaks things? :o)
What is arts-gmcop for? Let's make a deal: - You try uninstalling arts-gmcop (perhaps just temporary) and see if that gets your sound back (I suppose you need to uninstall your arts, arts-devel, and arts-gmcop, and install adrian's instead, without gmcop) - I install arts-gmcop and report back if the system-sounds work. I'll logout of KDE during installing the package. BTW, *** please name 1 system sound in particular that I should test and is a good indicator if system sounds work ***. BRB, Cheers, Leen
On Thursday 17 March 2005 16:07, Leendert Meyer wrote:
Hi Leen, I just built mine with a different build number to separate them actually. Maybe the gcomp file is the breaking point then, because I have all three files installed. I hadn't even considered that one file might be causing the problems with it all. If you are running a basic 9.2 system, only updating from the SuSE mirrors and Packman, then our systems are alike! I've been pretty prudent with 9.2 and everything has worked well because of that.
Might be a nice experiment then, to have you install the third file to see if it breaks things? :o)
Nevermind. I just discovered that my system sounds do not work either. Shoot! I assumed sound was working ok because I was watching TV (TV-card) and I responded during a break. Hmm. Well, at least the sound of my tv-card works! ;D
What is arts-gmcop for?
Hmm, I would like an answer to this one^.
Let's make a deal:
Just forget about it. ;)
BTW, *** please name 1 system sound in particular that I should test and is a good indicator if system sounds work ***.
Cheers, Leen
On Thursday 17 March 2005 10:15 am, Leendert Meyer wrote: [...]
Nevermind. I just discovered that my system sounds do not work either. Shoot! I assumed sound was working ok because I was watching TV (TV-card) and I responded during a break.
Hmm. Well, at least the sound of my tv-card works! ;D
What is arts-gmcop for?
Hmm, I would like an answer to this one^.
Let's make a deal:
Just forget about it. ;)
BTW, *** please name 1 system sound in particular that I should test and is a good indicator if system sounds work ***.
Cheers,
Leen
Ah ha! Ok, well now we know it is the arts files! It's deceiving when other things like your tv card works, isn't it? But that is basically how it appears. All other music, movies, etc sound works, but the basic KDE sounds, program sounds, log in sounds, don't. Ok, it's good to know and it's easy to fix with a new compile. Here is the description for arts-gmcop: A modular software synthesizer that generates real-time audio streams, supports midi, is easily extendable, and uses CORBA for separation of GUI and synthesis. Sounds like you should install it also. Lee
On Thursday 17 March 2005 16:30, BandiPat wrote:
On Thursday 17 March 2005 10:15 am, Leendert Meyer wrote: [...]
Nevermind. I just discovered that my system sounds do not work either. Shoot! I assumed sound was working ok because I was watching TV (TV-card) and I responded during a break. ... It's deceiving when other things like your tv card works, isn't it?
Yes, indeed. OTOH, what also was deceiving is that, when you wrote 'sound does not work', you actually meant 'sound does partially not work'. ;P But we figured this out. ;)
But that is basically how it appears. All other music, movies, etc sound works, but the basic KDE sounds, program sounds, log in sounds, don't.
Ok, it's good to know and it's easy to fix with a new compile. Here is the description for arts-gmcop: A modular software synthesizer that generates real-time audio streams, supports midi, is easily extendable, and uses CORBA for separation of GUI and synthesis.
Compare that to the description of arts itself. Apart from a few signs, it is /more or less/ the *same* description. (To compare, I used mc on two different virtual consoles, on the one I opened arts-*.rpm, and opened the 'HEADER' file, on the other I did the same with arts-gmcop.)
Sounds like you should install it also.
Really? How do I know that I /need/ that package? BTW, I'm going to try if clearing out /tmp and /var/tmp helps. Cheers, Leen
On Thursday 17 March 2005 16:55, Leendert Meyer wrote:
BTW, I'm going to try if clearing out /tmp and /var/tmp helps.
No. BTW, upon logging in KDE returned half way starting up back to KDM. The solution was in ~/.X.err: /tmp/.ICE-unix had to be owned by root (and not by me). After changing ownership, KDE started as usual (i.e. *without* working system sounds). However, I can play the system sound files with Kafeïne. Cheers, Leen
On Thursday 17 March 2005 07:00 am, Leendert Meyer wrote:
On Thursday 17 March 2005 05:23, BandiPat wrote:
Hi all, Anyone else ventured into installing the new SuSE KDE 3.4 files yet?
Yup. Installed them yesterday (16th) morning. No problems at all so far.
Remember the problem with the system sounds concerning the new arts files last time?
Please refresh my memory. :) [...] Cheers,
Leen ========= Sorry, forgot to answer this. The last arts files broke the system sounds as did this version for 3.4. All other sounds worked, music, movies or CD audio, just not the system beeps, sounds. A simple recompile of the src.rpm on my system, fixed it though. Several others reported success using my files for their system as well.
It would be interesting to know if the one file (gcomp) is the reason. regards, 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
Am Donnerstag, 17. März 2005 05:23 schrieb BandiPat:
Hi all, Anyone else ventured into installing the new SuSE KDE 3.4 files yet? Remember the problem with the system sounds concerning the new arts files last time? Well, it seems they are back with the new 3.4 files too. It seems as simple a solution to fix though. I just recompiled the SuSE src.rpm to my system and sounds work nicely again. Don't know what's happening with those arts files or what Adrian is compiling them on, but they certainly don't seem to work.
As far as the rest of KDE 3.4, it's looking pretty cool. Some new eye candy and features abound. Speed doesn't seem bad, but of course, I know this will improve substantiately with KDE 4. That is what I'm hearing at least. Thanks SuSE for the updates and maybe Adrian might let one of us compile the arts files for him next time! ;o)
Hi, I´m not lucky with my KDE 3.3 to 3.4 update last night. After a normal user log in, KDE started with a freezed screen. Only Root has no Problem. The logs are empty, so it´s hard to find the reason for me. Rene
On Thursday 17 March 2005 07:26 am, René Falk wrote:
Am Donnerstag, 17. März 2005 05:23 schrieb BandiPat:
Hi all, Anyone else ventured into installing the new SuSE KDE 3.4 files yet? Remember the problem with the system sounds concerning the new arts files last time? Well, it seems they are back with the new 3.4 files too. It seems as simple a solution to fix though. I just recompiled the SuSE src.rpm to my system and sounds work nicely again. Don't know what's happening with those arts files or what Adrian is compiling them on, but they certainly don't seem to work.
As far as the rest of KDE 3.4, it's looking pretty cool. Some new eye candy and features abound. Speed doesn't seem bad, but of course, I know this will improve substantiately with KDE 4. That is what I'm hearing at least. Thanks SuSE for the updates and maybe Adrian might let one of us compile the arts files for him next time! ;o)
Hi,
I´m not lucky with my KDE 3.3 to 3.4 update last night. After a normal user log in, KDE started with a freezed screen. Only Root has no Problem.
The logs are empty, so it´s hard to find the reason for me.
Rene ==================
Hi René, Yes, I experienced that same thing in the beginning, so restarted the machine and everything came up. I do believe our impatience may have played a part though, as the first time for kde 3.4 took a little longer to set itself up. I suspect that we just didn't wait long enough for things finish building. That was my case at least, because everything came up beautifully after the restart. regards, 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
At thursday, March 17th 2005 14:45 wrote BandiPat:
Hi René, Yes, I experienced that same thing in the beginning, so restarted the machine and everything came up. I do believe our impatience may have played a part though, as the first time for kde 3.4 took a little longer to set itself up. I suspect that we just didn't wait long enough for things finish building. That was my case at least, because everything came up beautifully after the restart.
regards, Lee
Hi Lee, I think my problem is another one. A few moments ago I deleted the KDE-files in the /tmp and /var/tmp folders. Since then: Normal user log in -> Screen turns black for 3-4 seconds -> fall back to log in Root No Problems at all. I believe that there is a programm or config, who´s incompatible with KDE 3.4. regards René
On Thursday 17 March 2005 09:00 am, René Falk wrote:
At thursday, March 17th 2005 14:45 wrote BandiPat:
Hi René, Yes, I experienced that same thing in the beginning, so restarted the machine and everything came up. I do believe our impatience may have played a part though, as the first time for kde 3.4 took a little longer to set itself up. I suspect that we just didn't wait long enough for things finish building. That was my case at least, because everything came up beautifully after the restart.
regards, Lee
Hi Lee,
I think my problem is another one. A few moments ago I deleted the KDE-files in the /tmp and /var/tmp folders. Since then:
Normal user log in -> Screen turns black for 3-4 seconds -> fall back to log in
Root No Problems at all.
I believe that there is a programm or config, who´s incompatible with KDE 3.4.
regards
René
Ok, what you are experiencing is different than what I did that one time. Sounds like something is amiss indeed, but I, like you, would have cleared out the /tmp directory first. That's probably not a bad idea anyway for a big update of this nature. Keep us posted on what you find. regards, Lee
On Thursday, March 17th 2005 15:05 BandiPat wrote:
**************** Ok, what you are experiencing is different than what I did that one time. Sounds like something is amiss indeed, but I, like you, would have cleared out the /tmp directory first. That's probably not a bad idea anyway for a big update of this nature. Keep us posted on what you find.
Hi, now after some days without access to my e-mail account after a big mistake of my Provider (He had to learn, that is no good idea to give important work to an irish server administrator on the evening of St. Patrick´s Day ) I´ m posting the solution for my log in problem. After some different ideas without a positv result, I decided to rename the /.kde folder and that´s it. Like the try and error method I tested one file after the other from the old renamed /.kde folder and found out that the file /.kde/share/config/kgpgrc from KDE3.3 was the reason for all the trouble. Kgpg was configurated to start up with KDE for the normal user and so I got a freezed KDE every time the normal user started KDE. Well, the log in problem is solved but now, gpg don´t work right. Encryption works fine but decryption doesn´ t at all. Kgpg told my that the gpg-agent is not running but that in the gpg-config the entry was made for it. bye René
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 17 March 2005 15:00, René Falk wrote:
Hi Lee,
I think my problem is another one. A few moments ago I deleted the KDE-files in the /tmp and /var/tmp folders. Since then:
Normal user log in -> Screen turns black for 3-4 seconds -> fall back to log in
Root No Problems at all.
I believe that there is a programm or config, who´s incompatible with KDE 3.4.
regards
René For me it's EXACTLY the opposite, it is possible without any problem to open a session as a "normal user" but non as root since KDE 3.4 is installed... what happens ???
M$-Internet Exploder est le cancer de l'Internet, voyez pourquoi ici : http://www.aful.org/publi/articles/msie_et_la_securite/index_html/view - -- (°- Bernard Lheureux Gestionnaire des MailingLists ML, TechML, LinuxML //\ http://www.bbsoft4.org/Mailinglists.htm ** MailTo:root@bbsoft4.org v_/_ http://www.bbsoft4.org/ <<<<<< * >>>>>> http://www.portalinux.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFCOgNSJCL6nUSjNr8RAqsEAJ4xofJeboXx01vH0JDvnotDri5Z3QCgmOkS BoLYoaYoX243NAniqhYmi0o= =Vr4P -----END PGP SIGNATURE-----
On Thursday 17 March 2005 05:23 pm, Bernard Lheureux wrote:
On Thursday 17 March 2005 15:00, René Falk wrote:
Hi Lee,
I think my problem is another one. A few moments ago I deleted the KDE-files in the /tmp and /var/tmp folders. Since then:
Normal user log in -> Screen turns black for 3-4 seconds -> fall back to log in
Root No Problems at all.
I believe that there is a programm or config, who´s incompatible with KDE 3.4.
regards
René
For me it's EXACTLY the opposite, it is possible without any problem to open a session as a "normal user" but non as root since KDE 3.4 is installed... what happens ???
Bernard, I'm noticing the same problem logging in as Root to a KDE session. It did once, but things were not right. Cleaned out /tmp and would not log in at all after that. I seem to have lost my Gnome session type as well from the menu and for the life of me cannot find where they have that now! Usually it is in kdmrc, but not now and I can't find anything in the KDE control center to add a new session type. Another thing, try using the control center for the Login Manager and log in as administrator. It bombs on me. Ah yes, the update blues, it has a beautiful sound, maybe. ;o) Lee
On Friday 18 March 2005 00:23, BandiPat wrote:
Cleaned out /tmp and would not log in at all after that.
Yup, that happened to me too. According to the errormessage in ~/.X.err, I had to `chown root: /tmp/.ICE-unix`: drwxrwxrwt 2 root root 112 2005-03-17 20:17 /tmp/.ICE-unix (permissions were already ok) Cheers, Leen
On Thursday 17 March 2005 06:29 pm, Leendert Meyer wrote:
On Friday 18 March 2005 00:23, BandiPat wrote:
Cleaned out /tmp and would not log in at all after that.
Yup, that happened to me too. According to the errormessage in ~/.X.err, I had to `chown root: /tmp/.ICE-unix`:
drwxrwxrwt 2 root root 112 2005-03-17 20:17 /tmp/.ICE-unix
(permissions were already ok)
Cheers,
Leen ============
Leen, I didn't have a ~/.X.err, but did have a ~/.xsession-errors file. I tried several things, but still didn't have any luck getting kde started as root. I can start any other window manager as root, but not KDE. Very odd and they've hidden things in different locations again, making it difficult to trace now. This is what my .xsession-errors file mentions though: startkde: Starting up... kbuildsycoca running... kdecore (KLibLoader): WARNING: KLibrary: /opt/kde3/lib/kde3/kcm_kdnssd.so: undefined symbol: init_kdnssd kded: Fatal IO error: client killed kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. klauncher: Exiting on signal 1 DCOP aborting call from 'anonymous-11768' to 'klauncher' kdeinit: sending SIGTERM to children. kdeinit: Exit. I've tried creating a link, as it was with 3.3 from /var/tmp/kdecache-root/ksycoca to /tmp/kde-root/ksycoca got this error after doing that: /opt/kde3/share/config/kdm/Xsession: line 51: /root/.xsession: no such file or directory Removed /tmp/.ICE-unix Checked owners for that and as you found, it was ok At the moment, I'm at a loss, but will continue tracking. Sure, you're not suppose to be logging in as root anyway, but I hate it when something doesn't work. :o) regards, Lee
Hmm, neither of the solutions discussed below work for me. I've upgraded to KDE 3.4 on two machines running Suse 9.2 Professional. Both machines had KDE 3.3.4 previously. Upgrade was performed via Yast2. On one machine KDE works like a treat after the upgrade. No issues with arts or KDM, On another, no user can login via KDM - neither normal nor root - just like described below. Although starting X via "startx" works for any user. After some playing with the KDE startup scripts on the first machine, I've determined that the problem occurs on like 242 of /opt/kde3/bin/startkde: LD_BIND_NOW=true kdeinit +kcminit which fails with the error messages shown below. BTW, splitting the above line into two, as was suggested on this thread earlier, had no effect. kdeinit: Shutting down running client. Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server kded: cannot connect to X server :0 DCOP aborting call from 'anonymous-20990' to 'kded' kded: ERROR: Communication problem with kded, it probably crashed. Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server kdeinit: Can't connect to the X Server. kdeinit: Might not terminate at end of session. Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server kcminit: cannot connect to X server :0 Ideas? Regards, Vadym Krevs BandiPat wrote:
On Thursday 17 March 2005 06:29 pm, Leendert Meyer wrote:
On Friday 18 March 2005 00:23, BandiPat wrote:
Cleaned out /tmp and would not log in at all after that.
Yup, that happened to me too. According to the errormessage in ~/.X.err, I had to `chown root: /tmp/.ICE-unix`:
drwxrwxrwt 2 root root 112 2005-03-17 20:17 /tmp/.ICE-unix
(permissions were already ok)
Cheers,
Leen
============
Leen, I didn't have a ~/.X.err, but did have a ~/.xsession-errors file. I tried several things, but still didn't have any luck getting kde started as root. I can start any other window manager as root, but not KDE. Very odd and they've hidden things in different locations again, making it difficult to trace now.
This is what my .xsession-errors file mentions though: startkde: Starting up... kbuildsycoca running... kdecore (KLibLoader): WARNING: KLibrary: /opt/kde3/lib/kde3/kcm_kdnssd.so: undefined symbol: init_kdnssd kded: Fatal IO error: client killed kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. klauncher: Exiting on signal 1 DCOP aborting call from 'anonymous-11768' to 'klauncher' kdeinit: sending SIGTERM to children. kdeinit: Exit.
I've tried creating a link, as it was with 3.3 from /var/tmp/kdecache-root/ksycoca to /tmp/kde-root/ksycoca got this error after doing that: /opt/kde3/share/config/kdm/Xsession: line 51: /root/.xsession: no such file or directory Removed /tmp/.ICE-unix Checked owners for that and as you found, it was ok
At the moment, I'm at a loss, but will continue tracking. Sure, you're not suppose to be logging in as root anyway, but I hate it when something doesn't work. :o)
regards, Lee
********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
On Saturday 19 March 2005 03:36 pm, Vadym Krevs wrote:
Hmm, neither of the solutions discussed below work for me. I've upgraded to KDE 3.4 on two machines running Suse 9.2 Professional. Both machines had KDE 3.3.4 previously. Upgrade was performed via Yast2.
On one machine KDE works like a treat after the upgrade. No issues with arts or KDM, On another, no user can login via KDM - neither normal nor root - just like described below. Although starting X via "startx" works for any user. After some playing with the KDE startup scripts on the first machine, I've determined that the problem occurs on like 242 of /opt/kde3/bin/startkde:
LD_BIND_NOW=true kdeinit +kcminit [...]
Have you tried running "/opt/kde3/bin/genkdmconfig" to generate a new kdmrc file/s? It sounds as if that might be your last resort. Leave the LD_BIND_NOW line alone, that's not causing you any grief to be sure. regards, 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
On Saturday, March 19th 2005 23:33 BandiPat wrote:
On Saturday 19 March 2005 03:36 pm, Vadym Krevs wrote:
Hmm, neither of the solutions discussed below work for me. I've upgraded to KDE 3.4 on two machines running Suse 9.2 Professional. Both machines had KDE 3.3.4 previously. Upgrade was performed via Yast2.
On one machine KDE works like a treat after the upgrade. No issues with arts or KDM, On another, no user can login via KDM - neither normal nor root - just like described below. Although starting X via "startx" works for any user. After some playing with the KDE startup scripts on the first machine, I've determined that the problem occurs on like 242 of /opt/kde3/bin/startkde:
LD_BIND_NOW=true kdeinit +kcminit
[...] ************
Have you tried running "/opt/kde3/bin/genkdmconfig" to generate a new kdmrc file/s? It sounds as if that might be your last resort. Leave the LD_BIND_NOW line alone, that's not causing you any grief to be sure.
Hi, I wrote "kdeint +knotify" between test -n "$KDEWM" && KDEWM=3D"--windowmanager $KDEWM" kwrapper ksmserver $KDEWM and it works (Well, it´s dirty too). Someone in the German suse-multimedia list wrote, that it is necessary for this method that in ~/.kde/share/config/knotifyrc the following things must be set Arts Init=3Dtrue KNotify Init=3Dtrue Use Arts=3Dtrue=20 bye René
participants (5)
-
BandiPat -
Bernard Lheureux -
Leendert Meyer -
René Falk -
Vadym Krevs