October 2004 - openSUSE KDE - openSUSE Mailing Lists

Problem with CD-ROM Drive
by Lugg William H Civ OO-ALC/MASFE 26 Oct '04

26 Oct '04

I am having a most curious problem with a new installation of SuSE 9.1/KDE 3.2 on an older machine. When I log in to KDE the CD tray opens. If I close it, it waits about 1 minute and opens again. I find that I can still read CDs, but I'm concerned I'm going to hit the tray and break it at some point. What might be causing this and how do I fix it? Thanks. ----- Bill Lugg Software Engineer, MilStar AF Command Post Terminal Software Support OO-ALC/MASFE, Peterson AFB, CO William.Lugg(a)cisf.af.mil <mailto:william.lugg@cisf.af.mil> And we know that in all things God works for the good of those who love him, who have been called according to his purpose. -- Romans 8:28

2 1

Konq. doesn't stop loading new instances
by ianseeks 26 Oct '04

26 Oct '04

HI Konqueror has developed a problem when I try and load a link from Kmail, it just keeps opening up new instances. As soon as you close one, another opens or if you don;t close them they still load up. The only way to cure it is to log off. I don't have time to check anything as it loads every second. I use Suse 91 and KDE 3.3.1 - i'm not sure when this started as I rarely use Konqueror, i ususally copy the link into Opera. Does anyone have any ideas as what to do with this reloading issue? Thanks Ian

2 3

Icon directory -- group not valid <9.1 pro>
by Jake 25 Oct '04

25 Oct '04

I've noticed that launching any KDE app from Konsole results in the warning: "kdecore (KIconLoader): WARNING: Icon directory /opt/kde3/share/icons/slick/ group not valid". The applications seem to work as normal. Is this a problem?

2 1

KDE and networking
by Ben Gross 22 Oct '04

22 Oct '04

How do I network on KDE? __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

2 1

Playing Audio CD
by Robert Fitzpatrick 21 Oct '04

21 Oct '04

I'm running SuSE 9.1 desktop PC with sound card. I can read the titles of an audio CD and the sound works when testing sounds in the control panel, but audio cd's don't play. The timer starts and the cd player runs, but no sound. WAV files from our voice mail system play fine as well. Any ideas where I can look to find the problem? -- Robert

2 1

yast/kde integration lost after upgrade to KDE 3.3.1 on SuSE 8.2
by Robert Graf-Waczenski 21 Oct '04

21 Oct '04

Hi! I'm running SuSE 8.2 and have recently upgraded the stock KDE 3.1.0 to KDE 3.3.1 using the rpms from the SuSE LinuKS download page. I ran into dependency problems, most notably kdebase3-SuSE needed to be uninstalled, but i can live without this. (And this is also a known issue among KDE users on SuSE). However, another dependency problem is more severe: I had to uninstall susewm-kcmyast and susewm in order to upgrade to KDE 3.3, which means that YAST2 integration with KDE is no longer available. Trying to re-install susewm and susewm-kcmyast with rpm -Fvh fails with conflicts. (I *think* the conflicts are with OpenOffice applink stuff, can't remember the details, though...) One idea would of course to use rpm --nodeps -force -Fvh, but this is somewhat rude and probably leads to an inconsistent system. I don't want to upgrade to 9.1 or even 9.2, so i'd like to know if anybody out there has a similar problem. Robert

2 1

SuSE 8.2 and the SFU 3.5
by uhomm＠t-online.de 20 Oct '04

20 Oct '04

Hi, i use an W2K DC with the SFU 3.5 installed (NIS and NFS-Service) Now i want the Users of the W2K DC to be NIS-Users which can work from an SuSE 8.2 on their homes. Basically this works fine with a non-graphical login (also with the fvwm2 as WM) But if the user login with the KDE the first time, the profile for the KDE will be created in the users home...all things seem to be oK. But after an reboot of the SuSE Box the login with the KDE hang up the Client PC. I used the network monitor of the W2K DC to look where the box hangs up an i saw that this occurs, when the client access per NFS the file $HOME/.kde/tmp-obelix (where obelix is the name of the client) which is an symlink for /tmp/kde-uhomm (where uhomm is the name of the user) $HOME lies on the W2K DC and is exported by NFS. Logins with fvwm2 or non-graphical logins works fine.... Has anyone any ideas, how i can fix the problem? -- \\|// (@ @) -------------------------oOO---(_)--OOo--------------------------- Mit freundlichen Grüssen Uwe Homm

1 0

Log level for .xsession-errors
by Mario Streiber 19 Oct '04

19 Oct '04

Hi, is there a way to change the log level for .xsession-errors? At the moment it seems every action of every program is logged into this file and this file grows at a rate of nearly 1 MB per hour. So if the system is up for a few days this file grows beyond 100MB. And if there really was an error it would be hard to find it. Thanks Mario

2 6

Lost ability to login as user
by Mel Andres 18 Oct '04

18 Oct '04

I was trying to resolve a conflict while upgrading with apt-get. In the process I removed gdm2-2.4.1.6-92.ximian.8.5. I had tried XD2 for awhile, but had changed my session back to kde some time ago. I have tried changing my grom GDM to KDM and XDM, but can login to my user account only in failesafe mode to a dingle Xwindow. I can login to a KDE session as root, and I created a new user, which can login just fine as well. Seems I read in the past that something needed to be deleted in /tmp or something for a similar problem, but so far I haven't hit on the resolution. Mel

4 4

Problem with Program-Autostart in KDE 3.1 (Kiosk-Mode)
by Marc Klünder 18 Oct '04

18 Oct '04

Hello, I'd like to autostart a program for a special user (is logged in automatically) at the startup of KDE. I use Suse Linux Prof. 8.2 and KDE 3.1 Version 3.1.1-17 (Standardinstallation of Suse 8.2). Actually the program ist started automatically for the desired user by adding a start-script in '$HOME/.kde/Autostart/'. But before starting the program all parts of KDE (KDesktop, Kicker/Panel(control bar)) are loaded and started. Until the start of the program it is possible to interact with the System (with the help of kde). But this should not be possible. I want to avoid that the special user can interact with anything other than the desired program. Based on some tips and hints I tried to load the start-script with the help of the file '$HOME/.xinitrc'. Part of the edited file: . . # #Add your own lines here # exec <start-script> & # # exec $WINDOWMANAGER #all failsafe exit 0 With this implementation the program ist loaded in the background, before the windowmanager (KDE) is loaded and started. But the program was also started just after the startup of KDesktop, Kicker and the other parts of KDE. The interaction with KDE was also possible for the user. I edited the .xinitrc again: . . # # exec $WINDOWMANAGER & exec <start-script> #all failsafe exit 0 After the modification the windowmanager was loaded in the background and the program was loaded and started directly. But some of the KDE-parts were loaded after the program-start. As a result the Kicker/Panel was displayed over the program. This wasn't what I wanted, because there is also interaction possible (for a longer time than the other solutions). The files in '/opt/kde3/share/autostart/' seem to advise KDE what services to load in which order. This files seem to be responsible for the whole system (all users). I found no possibility to edit the startup-options for only one user. Because of that I thought about editing the rights of the files and to add a command to the .xinitrc of the special user to move the files (in /opt/kde3/share/autostart/) to a subdirectory before executing the windowmanager. Another command before the command 'exit 0' should write the files back into the right directory. But I don't think, that this is really safe. When the system hang up during the execution of the program the files are not written back. Is there another simple way that is more safe? Greets, Marc ----------- Deutsch --------------------------------------------------------------------------------------- Hallo, ich würde gerne bei einem bestimmten Benutzer (wird mittels Autologin automatisch angemeldet) beim Start vom KDE automatisch ein KDE-Programm laden. Als System verwende ich Suse Linux Prof. 8.2 KDE 3.1 Version 3.1.1-17 (Standardinstallation unter Suse 8.2). Bisher habe ich dazu in dem Verzeichnis '$HOME/.kde/Autostart/' ein Skript hinzugefügt, welches das gewünschte Programm startet. Allerdings wird das Programm natürlich erst geladen, wenn alle KDE-Komponenten, wie z.B. der KDesktop und die Kontrollleiste (Kicker/Panel) geladen wurden. In der Zeit bis zm Programmstart ist somit eine Interaktion mit dem System (mittels KDE) möglich. Dies sollte nicht möglich sein. Anhand verschiedener Tips und Hinweise habe ich das Skript zum Programmstart dann in der Datei '$HOME/.xinitrc' laden lassen. Dies sah dann folgendermassen aus: . . . # #Add your own lines here # exec <Skriptname> & # # exec $WINDOWMANAGER #all failsafe exit 0 Somit wurde das Programm bereits vor dem Windowmanager in Hintergrund geladen, und dann erst KDE. Der eigentliche Start des Programm erfolgte allerdings weiterhin erst nach dem Start von KDesktop, Kicker & Co. Auch hier war leider eine zwischenzeitliche Interaktion möglich. Ich habe die .xinitrc schließlich nochmals modifiziert: . . . # # exec $WINDOWMANAGER & exec <Skriptname> #all failsafe exit 0 Dadurch wurde der Windowmanager im Hintergrund geladen, aber das Programm direkt gestartet und auch angezeigt. Da allerdings noch die gesamten KDE-Komponenten geladen wurden hatte ich nach dem Ladevorgang das Problem, dass die Kontrollleiste mein Programm überlagerte. Nicht nur dass das blöd aussah, es war wiederum die unerwünschte Interaktion möglich. Die Vorgaben, welche KDE-Komponenten geladen werden stehen scheinbar im Verzeichnis '/opt/kde3/share/autostart/'. Leider gelten diese Einstellungen systemweit, also für alle Benutzer. Ich habe keine Möglichkeit gefunden, entsprechende Einstellungen für einzelne Benutzer vorzunehmen. Meine Idee war folglich, die Dateiberechtigungen für die enthaltenen Dateien zu erweitern und in die .xinitrc des gewünschten Benutzers vor dem Laden des Windowmanagers einen Befehl einfügen, welcher die (in der .../share/autostart/) enthaltenen Dateien in einen Unterordner verschiebt. Weiterhin würde dann vor dem Befehl exit 0 ein Befehl eingefügt, welcher die Dateien wieder zurückschreibt. Dies finde ich allerdings weder sicher noch elegant. Denn schon bei einem möglichen Absturz des System im Programmbetrieb würden die Daten nicht wieder zurückgeschrieben. Gibt es evtl. eine andere Lösung, die einfacher/eleganter und vor allem sicherer ist? Grüße, Marc

4 6