October 2002 - openSUSE KDE - openSUSE Mailing Lists

No Help from KDE help as help doesn't start
by James Mohr 12 Oct '02

12 Oct '02

Hi All! I just did an Upgrade to KDE 3.0.3 from the SuSE RPMs. Now, whenever I select Help from any application menu, nothing happens. Running something like "khelpcenter help:/kmail" directly from the command works with out a problem. However, the help menu within Kmail does nothing (or at least nothing I can see). Seems like I got a path screwed up somewhere, but I really don't know where to look. Regards, jimmo -- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info --------------------------------------- NOTE: All messages sent to me in response to my posts to newsgroups or forums are subject to reposting.

2 2

Problems Installing KDE 304
by Alex K 11 Oct '02

11 Oct '02

Hi, I am installing KDE 304 and I am following all indications from Trolltech's documentation regarding the environment variables. Unfortunately even after the setup mentioned in the install guide QTDIR still points to the older "qt2". I looked everywhere to find out where is setup this variable but I did not find. I will appreciate your help. Thanks a lot. Alex __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com

2 1

Kghostviewer Help Needed
by Ralph De Witt 11 Oct '02

11 Oct '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi: I did a fresh install of SuSE 8.1 When I left click on file with a .ps extenstion I get a dialouge box that states Error - KGhostViewer Could not start Ghostscript. This is most likely caused by an incorrectly specified interpreter. Can anyone help me, to correct this error? Thanks. - -- Yours, Ralph. It said Use Windows XP or better, so I installed SuSE-Linux 8.1 Register Linux User 168814 ICQ #49993234 AIM ralphdewitt jabber.org ralphdewitt GPG Public Key available at http://www.keyserver.net Key fingerprint = 6426 1CFF 0987 9D51 76D6 06BC F22A CFF4 559A 03E7 Kernel version 2.4.19-4GB Current Linux uptime: 7:19, days users hours minutes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9putr8irP9FWaA+cRAlzgAJ0SrFgftwMZz7mS6ZUEBvOJdmZwdwCeMB0L ybbyfnHDa9fgjXYSzSrgboM= =LU/8 -----END PGP SIGNATURE-----

1 0

hi there can you help?
by pied2 11 Oct '02

11 Oct '02

This is a problem i've been having to do with my x windows. Basically i've got an optiplex260 with on board graphics. I've harassed the newsgroup at my university and i don't know what to do next tro get suse running(8.0).Maybe something to do with my partitioning? I've done some investigating and have found that my computer video controllers and the sound, video and game controllers are on-board video = Intel 845G PCI Accelerated SVGA , sound sound, video and game = Intel Pro 1000 MT Network I have problems getting the floppy working so am unable to post the log files.However upon looking at it thoroughly i found in the boot.log file : <3> Unknown bridge resource 2 :assuming transparent PCI-IDE :unknown IDE controller on PCI bus 00devicef9 VID=8086 DID24cb PCI: Device 00:1f .1 not available because of resource collisions PCI_IDE: (ide _setup_pci_device:)could not enable device. This seems to me to be the problem. However in investigating ways of accessing my log files I came acoss an interesting program called ltools which allows you to access linux filesystems on your windows pc or vice-versa. It checked my partitions on my computer which are as follows: /dev/hda1 :de 31MB from CHS /dev/hda2: NTFS/HPFS 43182MB /dev/hda3: Win ExPar 33126MB /dev/hda5:Linux Swap2047MB /dev/hda6:Linux EXT2 31078MB It told me that I have 'Bad Magic Number in superblock. Not Linux. Error loading superblock. This got me thinking, is my partioning incorrect? I used the partition magic 7 wizard to set up a linux partition booting from lilo.

8 13

Help needed geting Korganizer Plug-ins Configured SuSE 8.1
by Ralph De Witt 11 Oct '02

11 Oct '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi: I did a fresh install of SuSE 8.1. I am trying to configure the two plug-ins for Korganizer, but nothing is working, no error messages etc. Has anyone gotten these to configure? Can anyone help? Thanks - -- Yours, Ralph. It said Use Windows XP or better, so I installed SuSE-Linux 8.1 Register Linux User 168814 ICQ #49993234 AIM ralphdewitt jabber.org ralphdewitt GPG Public Key available at http://www.keyserver.net Key fingerprint = 6426 1CFF 0987 9D51 76D6 06BC F22A CFF4 559A 03E7 Kernel version 2.4.19-4GB Current Linux uptime: 1:06, days users hours minutes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9ppNy8irP9FWaA+cRAnapAJ9cbg77HDnKwCZPuIp0eBiiz1yPSgCglYWS m/Qy3i01M7jvbbdqr2NImnQ= =alAb -----END PGP SIGNATURE-----

1 0

how to get rid of something stupid with apt & kde
by Piet Roorda 10 Oct '02

10 Oct '02

Sorry, but the following packages have unmet dependencies: kdebase3-ksysguardd: Obsoletes: kdebase-ksysguardd E: Unmet dependencies. Try using -f. So? what I'll do next? piet

2 1

new kde (3.0.4)
by Frederik Vos 10 Oct '02

10 Oct '02

There are Suse rpm's available for this version. After doing the upgrade, i was not able any longer to change the background, and several other little problems. Fixed: open /opt/kde3/bin/startkde, remove the line: unset QTDIR add a line in /etc/profile.local or in $HOME/profile: export QTDIR="/usr/lib/qt-3.0.5" -- regards, Frederik Vos VosBerg@SuSE & L4L http://www.vosberg.be

2 2

Kernel Compile Fail
by Carl 10 Oct '02

10 Oct '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Does anyone know of a Suse kernel-source build that will actually compile? I need to experiment and try to get VMware running. Build 2.4.18-91 fails as below, consistently. Earlier builds fail in different ways, one in 1394Lynx, and others, elsewhere. I had found one that actually compiled, but have lost track of it. And while I'm at it, why are there two different source sets? (kernel-source and linux) Which one to use? And why does Yast say that linux is the REST of the source, when installing it conflicts with kernel-source? make[2]: Entering directory `/usr/src/linux-2.4.18.SuSE/drivers/block' gcc -D__KERNEL__ -I/usr/src/linux-2.4.18.SuSE/include -Wall - -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common - -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE - -DKBUILD_BASENAME=umem -c -o umem.o umem.c umem.c:136: field `tasklet' has incomplete type umem.c: In function `mm_start_io': umem.c:343: warning: right shift count >= width of type umem.c: In function `mm_unplug_device': umem.c:386: warning: implicit declaration of function `local_bh_disable' umem.c:388: warning: implicit declaration of function `local_bh_enable' umem.c: In function `mm_interrupt': umem.c:646: warning: implicit declaration of function `tasklet_schedule' umem.c: In function `mm_pci_probe': umem.c:1178: warning: implicit declaration of function `tasklet_init' umem.c: In function `mm_pci_remove': umem.c:1313: warning: implicit declaration of function `tasklet_kill' make[2]: *** [umem.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/block' make[1]: *** [_modsubdir_block] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers' make: *** [_mod_drivers] Error 2 hydra:/usr/src/linux # -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2i2dwACgkQnQ18+PFcZJt89QCdEbGM3RN5Lo395JATLmTL3iGd e+4An08UqgYJUpFwbI8z8bBdoIA3NxMB =VXFB -----END PGP SIGNATURE-----

6 11

Koffice Print Preview problem
by Keith Powell 10 Oct '02

10 Oct '02

Hoping that this is the correct list to ask, I have a problem with KOffice in SuSE8.1. Printing with my Epson 670 works correctly in all resolutions, using CUPS. But with all the KOffice programs, when I go to Print Preview, I get the error message:- Could not start Ghostscript. This is most likely caused by an incorrectly specified interpreter. I have looked in the 8.1 manuals, the SuSE databases and Togan's Unofficial FAQ. But this is not mentioned. As printing works, I don't know what is wrong. The printer was automatically found and set up during installation. Can anyone please help with a solution to this problem? Where and what is this interpreter, and how do I check if it is correct? I've not had a problem with previous versions. Many thanks Keith

1 0

Bugs in KMail, KDEInit?
by Glen 10 Oct '02

10 Oct '02

Hi all - I submitted the following bugs to KDE, but I'm wondering if anyone has any insight from a SuSE perspective? BUG # 1 - KMail won't die. On a newly-installed Suse Linux 8.1 system with KDE 3.0.3 and KMail 1.4.3, KMail fails to shut down correctly on exit. Whether I exit with the "X" box or through the File menu, a child KMail process continues running on my server. Compact-Folders-On-Exit is DISABLED, so this is not related to those bugs. This occurs whether I check mail or not, so this is not related to the POP process bugs. Even if I just start KMail, and immediately quit, the process stays there. The process is killable using killall, or the normal signal 15 kill, and it does not appear to use any CPU time, it just sits there... but because it's there, KMail cannot be restarted until that process is killed. I notice that kdeinit is leaving phantom kio_pop3 and kio_smtp processes around, too, but even if there are no such processes, KMail's child still lives on. BUG #2 - KDEInit doesn't die. On a fresh load of Suse 8.1 using KDE 3.0.3, I'm noticing problems with kdeinit's process management. kdeinit child processes - especially smtp, pop3, and http processes, seem to stay in the process table even after konqueror or kmail are completely exited/killed. The kdeinit parent process - and sometimes one or more children - stay running even after I log out. They stay running even if I kill the X server manually, or shut the X server down completely, having already logged out. During the logout process, kdeinit can take a long time (10 seconds or more) to terminate the X server and shut itself down even partially. This problem did not exist under Suse 8.0/KDE 3.0.1. I saw another bug similar to this about KDE 2.2.1, but this appears to be a new problem in 3.0.3

1 0