October 2002 - openSUSE KDE - openSUSE Mailing Lists

Re: [suse-kde] KDE 3.1b2 is out!
by Dieter Nützel 04 Oct '02

04 Oct '02

On Friday 04 October 2002 14:33, Ken Phelan wrote: > On Friday 04 October 2002 3:54 am, Olle Viksten wrote: > > > > And don't forget to change the links opt/kde2/lib/libkjava.so and > > /opt/kde2/lib/libkjava.so.1 to point to lib/libqtjava.so.1.0.0. Kmail kept > > crashing for until I did that. > > > > Olle > > That's interesting.....I didn't have to perform that particular step. > > In case other rpm users hadn't noticed, the 'kdenetwork' rpms were not > included at the kde/suse/unstable/8.0 directory. I attempted to run the > mandrake rpms for kdenetwork and hosed things up so I went ahead and > compiled the source for kdenetwork and all appears well at this time. > > It's also missing 'kdebindings' but I'm still running the 3.01 version and > haven't noticed anything amiss. Same with SuSE rpm's for 7.3. I compiled kdenetwork-3.0.8.tar.bz2 myself => KMail works. But session management do _NOT_ work! All the needed stuff would be created in .kde/share/config/session/ but ignored during next startup ;-( Regards, Dieter BTW Writing this under SuSE 7.3, KDE 3.1 beta2, KMail 1.4.7. -- Dieter Nützel Graduate Student, Computer Science University of Hamburg Department of Computer Science @home: Dieter.Nuetzel at hamburg.de (replace at with @)

2 1

KDE 3.0.3. upgrade problems
by John Sved 04 Oct '02

04 Oct '02

After installing the KDE upgrade as per http://www.suse.com/us/private/download/linuks/i386/update_for_8_0/index.ht… certain apps crash. For example find files the Crash Handler dump says: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40f05099 in wait4 () from /lib/libc.so.6 #0 0x40f05099 in wait4 () from /lib/libc.so.6 #1 0x40f7fbd8 in __DTOR_END__ () from /lib/libc.so.6 #2 0x40d9a072 in waitpid () from /lib/libpthread.so.0 #3 0x405c1ade in KCrash::defaultCrashHandler () from /opt/kde3/lib/libkdecore.so.4 #4 0x40d97a74 in pthread_sighandler () from /lib/libpthread.so.0 #5 <signal handler called> #6 0x407fb851 in QWidget::checkChildrenDnd () from /usr/lib/libqt-mt.so.3 #7 0x407fb96d in QWidget::setAcceptDrops () from /usr/lib/libqt-mt.so.3 #8 0x4099416e in QTextEdit::init () from /usr/lib/libqt-mt.so.3 #9 0x40993dbd in QTextEdit::QTextEdit () from /usr/lib/libqt-mt.so.3 #10 0x40415a30 in KAboutContainerBase::addLicensePage () from /opt/kde3/lib/libkdeui.so.4 #11 0x40417e85 in KAboutDialog::addLicensePage () from /opt/kde3/lib/libkdeui.so.4 #12 0x404583a1 in KAboutApplication::buildDialog () from /opt/kde3/lib/libkdeui.so.4 #13 0x4045713a in KAboutApplication::KAboutApplication () from /opt/kde3/lib/libkdeui.so.4 #14 0x08055ff3 in QScrollView::mouseReleaseEvent () #15 0x0805698f in QScrollView::mouseReleaseEvent () #16 0x40e7a9ed in __libc_start_main () from /lib/libc.so.6 Similar output is given when some apps like package manager encounter a problem such as a zero result for a search. But the worst of the problem is that Yast2 will not start. The sand clock revolves for a while .......then nothing. I first noticed that Yast2 was sick when I was going to reinstall webcam apps which would not load. i.e. the KDE 303 upgrade did something to the webcam (video) apps. Since Qt3 looks to be involved I installed it again and the option Qt3 stuff , to be sure. But it has not helped. Main apps such as StarOffice, QCad, Mozilla 1.1, Digikam are OK After reading some of the threads in the KDE forum it seems that: Using Package Manager for the KDE upgrade is not safe. Using rpm command line strings is subject to habits (good or bad). It would be really helpful if SuSe had a text that one could cut and past line by line in the correct order to do the upgrade proceedure (gee that's almost a script or some kind of program to automate the process ... i.e. something that YasT should do.) Any suggestions please 1) to stop the crashes 2) procedure to regain "lost" apps like Yast2 3) to do it again but correctly ? thanks, -- John

2 2

AW: [suse-kde] kinternet won't break the connection! and others
by Monaghan, John 04 Oct '02

04 Oct '02

I had real problems with kinternet, so much so that opposite to what Carl has suggested (Not that he is wrong - try his suggestion first), I enabled dial-on-demand and stopped using kinternet. The latest problem I had was that it could not find ippp0 (ISDN) and so kept failing. If you do choose dial-on-demand there are certain provisos: Close your applications when finished, particularly if you use Mozilla Set the time before disconnecting (in Yast2) to a low value Watch your messages log file like a hawk to make sure your machine disconnects. Carl, I am still looking at the fonts problem but have been very busy lately - privately as well as work - I have not found anything. However, I do have a question for everyone which I may have missed first time round.....have you used the Sax program to set fonts (or even edited XF86Config, even though SuSE frowns upon it), to check that the fonts are where you think they are and are being loaded? Regards / Mit freundlichem Gruß / Salutations John Monaghan BSc (hons) Computer Science - Software Engineering (AIRS) Software Engineer Front Office Development Hogatex Software GmbH -----Ursprüngliche Nachricht----- Von: Carl [mailto:quantum@ultra2k.com] Gesendet: Mittwoch, 2. Oktober 2002 23:33 An: suse-kde(a)suse.com Betreff: Re: [suse-kde] kinternet won't break the connection! -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is dial-on-demand enabled? If so, disable it. On Wednesday, 02 October 2002 17:28, Michael McGibben wrote: > Hello. > > I run Suse 8.0 and update as and when it is necessary. I have a peculiar > problem with kinternet. Although I click on stop and the connection seems > to be broken, kinternet then proceeds to re-connect. The only way that I > can break the connection is to log off and shut down. Any suggestions? > > Thanks. > > Michael. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2bZiYACgkQnQ18+PFcZJu+VgCdFm9Zy7VzWMeATbkf0d6mBNpA NBwAn1Dz+bdW1inlzwInFCpyiOO0xzI9 =a5yA -----END PGP SIGNATURE----- -- To unsubscribe, email: suse-kde-unsubscribe(a)suse.com For additional commands, email: suse-kde-help(a)suse.com Please do not cross-post to suse-linux-e

1 0

Fonts and KDE 3 and SuSE 8.0
by Kevin McLauchlan 03 Oct '02

03 Oct '02

So far tonight, I have neglected my diabetic pet, bent the frame of my cubicle from punching it in absolute wordless rage and frustration, and severely frightened the poor woman who came to empty the wastebaskets and saw the look on my face. I have job deadline looming, and documents that aren't anywhere near finished, and no fonts. I have OpenOffice 1.0.1. My documents seem to display in one single sheisenfont. That is, no matter what I choose for the font attribute of a Paragraph Style or a Character Style, they are all and always substituted by the exrementafont. Once again, I have gone to the KDE Control Center, and System, and Font Installer. I heeded the warning that I must use Administrator Mode if I want my font-ish stuff applied globally. I viewed the dual windows with "Install From:" on the left, and "Install To:" on the right. There's nothing of importance in the "Install From:" window. The "Install To:" window already has dozens... hundreds, thousands of fonts in X11 Fonts Directory. There are files in the /75dpi directory, in the /Speedo directory, in the /Type1 directory, in the /URW directory, in the /misc directory, in the /truetype directory, in the /uni directory ... do I really need to go on???? They are bloody THERE! I'm looking at them... hundreds and hundreds of font files of several types. They are sitting there, apparently mocking me, in what this interface implies is ALREADY the place where fonts are supposed to go. There is nothing to suggest that I should need to perform some additional step. There's no other button to press, or field to fill in. Many of the names of those font files appear in the pick-lists within OpenOffice and other K and X applications. But it doesn't matter. I can pick any font I like, for any purpose (except for window dressing, which has flavors of Nimbus, and seems to work). It doesn't matter what I pick, it will be substituted for that one, single, ugly pieceofcrap font. I don't know what the substitute font is (it's something that runs the letters together and generally looks too ugly to NOT be intentional), and I don't care. When the "obvious" things, within the KDE interface did NOTHING to access the fonts that are all sitting there, I looked back in e-mails in this list, and went to the suggested SDB pages for 7.3 and 7.1 and did what they suggested, and it had a wonderful effect... NOT A DAMN THING! There are now a couple of extra files in /etc, and nothing at all has changed. Yes, I exited and restarted. No effect. What are all those .pfa, and .pfb, and .spd, and .pcf.gz, and .ttf files FOR, if they all already appear in the directories where the System>Font Installer (root) expects them to be, and they STILL %$#@&!! refuse to appear in my documents and applications? What is the Font Installer FOR, if not to install the fonts?? I have looked and looked and looked, and there is NO function or button or menu item that says: "Activate all the fonts that are already installed and uselessly sitting there." Really. I looked. I ran the Qt Configuration utility, and it was useless. I don't *need* to specify a substitution font... I need the bloody, actual FONTS! If the KDE Control Center is not able to make all the required things happen, it should not pretend that it can. The night security people are kicking out stragglers now, so I have to leave, with my work undone and in disarray. Tonight would not be a good night for anybody to be jaywalking, or driving badly in my city... Tomorrow will be really fun, explaining why I don't have the work done. Why is it this way? What is the purpose of making it this way? Why the mocking list of all the fonts that refuse to appear in my documents? If there is an "Activate your fonts" function, why must it be hidden somewhere? Whose idea was this? /kevin (beyond frustration in Ottawa, Canada)

8 13

Fwd: Re: [suse-kde] KDE 3.1b2 is out!
by Kevin McLauchlan 03 Oct '02

03 Oct '02

OK, strike my second paragraph, below. Joe answered it. /k ---------- Forwarded Message ---------- Subject: Re: [suse-kde] KDE 3.1b2 is out! Date: Thu, 3 Oct 2002 12:10:30 -0400 From: Kevin McLauchlan <kmclauchlan(a)chrysalis-its.com> To: suse-kde(a)suse.com Can anybody report what version of KDE is included on the SuSE 8.1 release? Is it at least 3.0.3? For those who have tried the beta, does it add anything that you've noticed? Or is it just stability and bug fixes? /kevin ------------------------------------------------------- -- ** DIR-ty DEEDS, and they're DONE dirt cheap. (Sing it, now...)

1 0

kinternet won't break the connection!
by Michael McGibben 02 Oct '02

02 Oct '02

Hello. I run Suse 8.0 and update as and when it is necessary. I have a peculiar problem with kinternet. Although I click on stop and the connection seems to be broken, kinternet then proceeds to re-connect. The only way that I can break the connection is to log off and shut down. Any suggestions? Thanks. Michael.

2 1

Sound Driver Fails on Boot; 1394 Driver fails on Compile
by Carl 02 Oct '02

02 Oct '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am recompiling the Suse kernel to try and make VMware work with Suse8. But now when I boot I get the error message: <notice>/etc/init.d/rc5.d/S13alsasound start Starting sound driver<notice>'/etc/init.d/rc5.d/S13alsasound start' exits with status 0 : snd_cs46xxmodprobe: Can't locate module snd_cs46xx failed A check in modules.conf shows indeed that snd_cs46xx is being called, but the module is actually cs46xx. So I presume there is some invisible massaging, that has now broken. I did disable most sound modules, leaving only the generic ones, Soundblaster, Crystal, and OPL. In addition to the sound driver problem on boot with my custom kernel, when trying to compile modules, it fails on the TI 1394 driver: make[2]: Entering directory `/usr/src/linux-2.4.18.SuSE/drivers/ieee1394' gcc -D__KERNEL__ -I/usr/src/linux-2.4.18.SuSE/include -Wall - -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer - -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 - -march=i686 -DMODULE -DKBUILD_BASENAME=pcilynx -c -o pcilynx.o pcilynx.c pcilynx.c: In function `mem_open': pcilynx.c:647: `num_of_cards' undeclared (first use in this function) pcilynx.c:647: (Each undeclared identifier is reported only once pcilynx.c:647: for each function it appears in.) pcilynx.c:647: `cards' undeclared (first use in this function) pcilynx.c: In function `aux_poll': pcilynx.c:706: `cards' undeclared (first use in this function) make[2]: *** [pcilynx.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/ieee1394' make[1]: *** [_modsubdir_ieee1394] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers' make: *** [_mod_drivers] Error 2 hydra:/usr/src/linux # This is something we need. As I am not a C programmer, I cannot know what is wrong. Does anyone see what's wrong? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2bEdMACgkQnQ18+PFcZJvamwCfXVnnJ6RCTALzzRk/TQBppBi5 hW0An155biVzQkjrSoATr3MTSBvfRm14 =/Urs -----END PGP SIGNATURE-----

3 4

VMware Crashing with Suse8
by Carl 01 Oct '02

01 Oct '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Install and config of VMware 3.2 is proving to be a nightmare. I found this on Google: >VMware has a problem with Suse 8.0. > >Suse decided to include a memory management patch from the 2.5.x >kernel tree in their 2.4.x kernels. Applications that are not >specifically modified for this patch can be severely broken by it. > >VMware was not written to take this patch into account because VMware >only supports 2.2.x and 2.4.x kernels on the host and this patch is >*NOT* part of the 2.2.x or 2.4.x kernels. > >Suse should not be claiming that the kernel shipped with Suse 8.0 is a >2.4.18 kernel. It is not. It is a heavily modified kernel that was >originally based on 2.4.18. VMware is compatible with 2.4.18 >kernels. It is not 100% compatible with the custom kernel installed >by default in Suse 8.0 (please note that Suse 8.0 is not a supported >host OS) > >Replacing your patched Suse kernel with a stock 2.4.18 kernel will >resolve the problem completely. > > >>a fast an simple solution is to limit RAM to 850 MB at bootime, works >>but if you need the RAM.... > >Whether you need the RAM or not, the better solution is to remove that >patch. Apparently even the author of the patch has said that the only >people who should see any benefit from it right now are people with >more than 1GB of RAM, but less than 2GB of RAM who are also running >Oracle on the machine. So removing it should not hurt anything. So is the only fix to use kernel.org kernels? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2XoIIACgkQnQ18+PFcZJtREQCfXcbD8Bfueuky9/0dAe6vH8NX 55cAniZA0uVO5sDKf0La3twX02wKv+Q+ =aqb7 -----END PGP SIGNATURE-----

3 10

Fwd: kicker and external task bar.
by mark king 01 Oct '02

01 Oct '02

Further to my last post. After I restarted KDE the extension task bar which is very conveniently located at the top of the screen ,did not reappear,this happens about once in 10 or 12 openings. I was able to expand the kicker panel to the full screen width using the preferences box. The intermittent extension taskbar problem is still unsolved. KDE1 used to have it at the top of the screen by default so why was it buried in the main kicker bar ? Does not anyone use the extension task bar at top of screen? Cheers Mark -- Marking(a)paradise.net.nz Attachments rejected if no previously authorised ------------------------------------------------------- -- Marking(a)paradise.net.nz Attachments rejected if no previously authorised

1 0

kicker
by mark king 01 Oct '02

01 Oct '02

I am running dual monitors and kicker is only setup on the left hand one. I was wondering how to get it to cover the right hand screen as I viewed Kandalfs useful tips ,it said to click on the right hand end of the tool bar. Whereupon the whole bar slowly moved to the bottom of the right hand screen then kept moving to the right and disappeared. I guess it will reappear when next i bootup. The real point of my mail is how can one move the wanted email addresses from the "recent addresses" to the main address book? Cheers Mark -- Marking(a)paradise.net.nz Attachments rejected if no previously authorised

1 0