August 2002 - openSUSE KDE - openSUSE Mailing Lists

Fwd: Problems with KDE3.0.2
by Federico Damonte 08 Aug '02

08 Aug '02

at Randall's request, i forward his mail to the relevant lists. As for the comments that my original post generated, I would like to point out that many people failed to realize that I did NOT upgrade to KDE 3.0.2 intentionally. I only installed it beacuse the patches were on YOU and I did an automatic update (which i will never do again, I learned my lesson). That upgrade was supposed to fix bugs and security holes and left me with a very broken system - not a nice surprise. federico ---------- Forwarded Message ---------- Subject: Problems with KDE3.0.2 Date: Wed, 7 Aug 2002 20:07:09 -0400 From: Randall Wood <rsw22(a)cornell.edu> To: federico.damonte(a)unipd.it Hello Federico: You saved my Linux system. Thanks so much. I was surfing the SuSE Linux suse-kde mailing list archives on line, and your message about KDE3.02 problems on SuSE were an exact match for the problems I've had with my machine, and I've been tearing my hair out trying to fix them. So thanks for your detailed message with gave me the info I needed to fix my problems: Yast2, kppp, and kinternet. Do me a favor and help me help the rest of the SuSE community by posting my message to the mailing list, to reaffirm that yes, other people are having the same troubles as you describe. I visited the SuSE support database daily in search of new articles describing why Yast2 had choked; nothing. I sent in support requests by email; nothing. I tried applying to the mailing list myself but was unable to (which is why I'd appreciate your posting my message on my behalf; I couldn't get subscribed). Nothing I tried found me the answers. I even tried removing and reinstalling the KDE3.0.2 RPMs to see if that would help. Tonight I was planning on reinstalling SuSE 8.0 to get a functioning Yast2; last night I even backed up all the home directories in preparation for tonight's ordeal. Thanks for the info. Help me help the rest of the group by posting this message, confirming your experience and mine were the same. I suspect SuSE's in trouble, but I don't know why. Their support lines are unresponsive, their servers seem to be perpetually DOSed, and their latest SDB articles include one about how to send a proper help request email so that their spam filters don't weed it out. I think someone's either DOSing them or something; don't know what, but I agree with you: I can forgive SuSE for putting out bad RPMs, given the immediate demand users have for the latest software. But I resent the lack of communication on SuSE's part. I have no reason to believe they even read my email; I've heard nothing from them. Best wishes, Randy Wood -- My Home Page: http://www.therandymon.com -------------------------------------------------------

2 1

kmail addressbook mailing list...
by Alexander Beck-Ratzka 07 Aug '02

07 Aug '02

Dear KDE users, I have two problems with kmail of kde 3.0 on SuSE Linux 8.0. first ... If I got an entry in my addressbook <adresse1(a)tt.com>, <adresse2(a)tt.com> always the SECOND(!!) address is used, if I enter an name to this addressbook entry, under which it shall be used afterwards. The problem still exitsts, even if I change the entry in the email field to: adresse1(a)tt.com, adresse2(a)tt.com or <adresse1(a)tt.com, adresse2(a)tt.com> If I try to use the entry for the second or third mail address, only the last email address will be used, if I click afterwards on the addressbook entry So my question is? How can I create a mailing list in the kmail addressbook of KDE 3.0. I never got this problem with a KDE 1.** version! ------------------------------------ my second problem ... How can I import addressbooks from kde 1.** (I mean the KDE version, which was delivered with SuSE Linux 6.4) into the addressbook of kmail of kde 3.0?? Hoping for a lot of answers ;-) Alexander

1 0

kmail Adressbuch Mailingliste...
by Alexander Beck-Ratzka 07 Aug '02

07 Aug '02

Liebe KDE-Freunde, ich habe gestern Abend gleich zwei Probleme mit dem Adressbuch von kmail bei kde 3.0 (SuSE 8.0). zum ersten ... Wenn ich im Adressbuch einen Eintrag der Art <adresse1(a)tt.com>, <adresse2(a)tt.com> so wird immer nur die ZWEITE(!!) Adresse verwendet, wenn man dieser Liste einen Namen gibt, unter dem diese eingetragen werden soll. Das Problem bleibt bestehen, wenn ich im email-Feld einen Eintrag adresse1(a)tt.com, adresse2(a)tt.com oder aber <adresse1(a)tt.com, adresse2(a)tt.com> anlege. Versuche ich bei die Felder für zweite email und dritte email zu verwenden, so wird auch immer nur die LETZTE email-Adresse verwendet. Wie erzeuge ich im Adressebuch Mailaliase??? Damit meine ich Adresseinträge, hinter welchen mehrere email-Adressen stehen. Wohlgemerkt, ich rede vom kmail für kde 3.0. Mit einer 1er-Version gab es diese Probleme nicht. ------------------------------------ zum zweiten ... Wie importiere ich Adressbücher von kde 1.** (ich meine die kde-Version, welche mit SuSE 6.4 daherkam) ins Adressbuch von kmail des kde 3.0?? In der Hoffnung auf jede Menge Anworten ;-) Gruß Alexander

1 0

KDE International characters does not work now...
by Alberto Curro 07 Aug '02

07 Aug '02

Hi again, after upgraded from KDE 2.x to KDE 3.0.1 (and to X 4.2.0) I have now a very annoying bug that is getting me crazy. I'm spanish and use the spanish keyboard, and have everything configured in KDE Control Panel. In our language, as in some others too, we use quoted characters (á, é, etc) and now I can only see some of them. For example, the quoted 'e' does not appear now, in its place I can see (and print) an strange character, everytime different depending of the previous character, or even no character at all. Some other characters, as, i.e. quoted 'u', is shown different (bigger or smaller, it depends) than the rest of them.... You can see a sample of what I should see and what I see really in the attached bitmap. It's very annoying, since I cannot use any word-processor to write my documents. I have this problem on every KDE (and non-KDE, but running over KDE) application, including code editors, mail clients, etc. The most annoying in this )%(%&/&"·" thing is that in some apps I can see the characters perfectly. If I go to any wordprocessor and try to change the font, I can see in the 'previous' panel (if available) the sample phrases perfectly. I can see the characters if you send me a mail with them, or any document. That's : I can see them if someone (different of me, of course) write them in some place, and I read it. This happens not only with my common user, also with root and every user (two more) on my system. I have tested every font installed on my system (I have xfstt with 50 TTF fonts and some APF fonts too), and now I have configured as keyboard : spanish, country : spain, codepages : tested with iso-8859-1 and iso-8859-15, and my keyboard is a 105-keys (Intl) PC one. Any idea????? Regards Alberto Curro

1 0

KDE 3.0.2 sources kstyle??
by jochen issing 05 Aug '02

05 Aug '02

Hi List, I have compiled the complete KDE 3.0.2 sources and installed them successfully after a a while. Now I want to use another KDE style and installed Acqua for KDE 3. The colors, the wallpaper, the icons and the window decoration are available, but I cannot activate the acqua widget-style. Has anyone fixed the problem, or any hint?! I really don't have the time to fix the bug in the source, but if there's no other way... Greetings, jochen -- jochen issing mailto:jochen@nrpl.de GPG ID: 210442F5

1 0

Re: [SLE] Problems with KDE 3.0.2 upgrades
by Federico Damonte 04 Aug '02

04 Aug '02

> On Sunday 04 August 2002 16:45, Federico Damonte wrote: > > 3. Kinternet does not work. > > > > Solution: to the file with the name of your provider in > > /etc/sysconfig/network/providers add the line "STUPIDMODE="yes"" (mind > > the quotation marks around "yes") > > This has absolutely nothing to do with the kde upgrade. Stupid mode is > sometimes needed because of the way some ISP server software is > implemented. It is a feature of wvdial. If you need it after the kde > upgrade you needed it before the upgrade > indeed, i did not use kinternet before kppp stopped working. THanks for pointing that out. > It is a bug, however, that there is no way to set Stupid Mode through the > YaST2 internet setup. it is indeed

1 0

Problems with KDE 3.0.2 upgrades
by Federico Damonte 04 Aug '02

04 Aug '02

Dear all, It seems a lot of people have been having problems after upgrading their SuSE 8.0 to KDE 3.0.2. I would like to comment on these briefly, since I am thinking of wrting a serious compliant letter to SuSE and I would like to hear your opinion. But first, since some of these problems have been reported here more than once, it is perhaps useful to list them again, together with the solutions that worked for me: 1. Yast2 cannot be accessed through a GUI, only through its clumsy text interface. If you try to start the GUI interface Yast2 does fire up (but some people even experienced some segfaults), but the interface does not show up. Solution: I downloaded and installed qt3-non-mt-3.0.4-87 2. KPPP does no longer work. Solution: create the file /etc/ppp/peers/kppp and add "plugin passwordfd.so" to it. 3. Kinternet does not work. Solution: to the file with the name of your provider in /etc/sysconfig/network/providers add the line "STUPIDMODE="yes"" (mind the quotation marks around "yes") 4. Apps handbook no longer work. Solution: none that i know of (correct me if I am wrong) Now, in my opinion these are very serious defects for a relatively minor upgrade version. You would expect such problems when upgrading to a X.0 version, not from 3.0.1 to 3.0.2.. And since KDE 3.0.2 is mainly a maintance release i cannot but conclude that SuSE did a poor job of packaging the upgrade files. Now, this can happen, nobody is perfect, but where SuSE really disappointed me is in its reaction to these problems, namely there was no reaction, just silence, and this is simply not acceptable. Speaking for myself, I cannot allow any serious fault in my box: I work on it and I very much want it to be stable (for instance, right now i have on it the 60 abstracts of a conference I am organizing). That's why i keep it always updated with YOU and I never launch myself into upgrading from source or install any development package. Finding myself unable to launch Yast2 and connect to the internet (another thing I need for my job) was really upsetting. Furthermore, none of these problems were solved by support at SuSE, but only by experimenting and by all the helpful people here on this list (thanks again, folks!). These hassles certainly cost me lot of time and effort. All this is surprising, since SuSE was not obliged to put those KDE 3.0.2 upgrade packages in YOU to start with. SuSE is very clear about not providing update patches, but only bugfixes, so there was no reason to include KDE 3.0.2 in YOU. It was already available on their LINUKS page so those who wanted it could get it there, but those of us who prefer a stable system could keep on updating with YOU. Since then, SuSE's behavior only got worse: the KDE 3.0.2 packages were silently removed from YOU and then (silently) put back again, with no word from SuSE warning people of the problems found in the original upgrade packages. We don't even know whether the "handbook" bug has been solved at all. This not the way any serious firm, be it big or small, behaves. So, to conclude, i was going to send SuSe a feedback letter asking for: 1. the removing of all the unstable or broken pacakges from YOU, including KDE 3.0.2 and any other eventual broken package, and an open disclosure of all the problems those pacakges had. 2. new, patched packages of KDE 3.0.2 that those of use that already installed the original ones should upgarde to - again. Only these patches should appear in YOU, not the general KDE 3.0.2 packages. 3. A major cleanup of the "linuks" update packages. From what i can see, the old KDE 3.0 packages are still there, end even some KDE 2.x packages all of them mixed up in the same place. In my opinion, exactly as the "Linuks" page is divided into SuSE version it should also be divided into KDE version so that, for instance, a 7.3 user that did not upgrade to KDE 3.0 before can do it now. All these corrections are very simple to implement, and it is surprising that SuSE did not already do them. SuSE is certainly a great distribution and the problems with KDE 3.0.2 or the deficiencies of the Yast2 text interface do not change this simple fact. But SuSE's reaction to the KDE 3.0.2 problems is managing to do this. It is in SuSE own interest to provide KDE updates, and that's the reason they do it, but we have the right to expect those updates not to break anything in our systems and to be replaced by pached one if they do. It' as simple as that. Let me know wht you think. fred

2 2

Re: [suse-kde] Problems with KDE 3.0.2 upgrades
by Carl 04 Aug '02

04 Aug '02

. On Sunday 04 August 2002 09:45 am, you wrote: > Now, this can happen, nobody is perfect, but where SuSE really disappointed > me is in its reaction to these problems, namely there was no reaction, just > silence, and this is simply not acceptable. Speaking for myself, I cannot > allow any serious fault in my box: I work on it and I very much want it to > be stable (for instance, right now i have on it the 60 abstracts of a > conference I am organizing). That's why i keep it always updated with YOU > and I never launch myself into upgrading from source or install any > development package. Finding myself unable to launch Yast2 and connect to > the internet (another thing I need for my job) was really upsetting. > Furthermore, none of these problems were solved by support at SuSE, but > only by experimenting and by all the helpful people here on this list > (thanks again, folks!). These hassles certainly cost me lot of time and > effort. I have to agree, except we only made it to K3.0.1 . Overt, complex failures, on PRODUCTION machines cost my company 3 weeks of downtime due solely to our 'upgrade' to Suse8. And it wasn't just problems with K... numerous problems and bugs owing to the packager (Suse). We were forced back to 7.3 in order simply to get anything done. My boss is furious. Of course 7.3 has its problems (right now we have only TWO FONTS in K, and cannot PRINT nor FAX) but at least we can function to a degree. I've noticed in postings to this list that at least two members of the Suse *team* are still running 7.3, as of two weeks ago. I realize that since the layoffs Suse is short of manpower, and we sympathise with that. But major instabilities in this "stable" shipping product effectively shift hidden costs to us, and we can't (shouldn't) afford that, particularly since no one on this list has been able to answer my questions. (the most urgent is reproduced below) I can only conclude that those who say they're not having problems with 8 are simply not using their machines very much. And you're right: Suse doesn't say a word. Which is in keeping with the current cultural view that admitting mistakes (and/or apologising), is only a sign of weakness. (a cultural view which is negative and ossifying, but which has become pervasive) We are waiting for Suse8.1 . If this release is nearly as bad as 8.0 we must abandon Suse altogether. It's a question of survival. Please do better Suse. We hope to see 8.1 soon. Carl

1 0

Kmenue, KDE3.0.2
by Michael 04 Aug '02

04 Aug '02

Hello, since I updated my system, SuSE 7.3 pro, to KDE 3.0.2 I had a problem with kmenu. For me it works, I got the new kmenu and also the new icons. But for all other users it didn't work. They got still the KDE 2 icons and also the programs. The button "Menueditor" is gone. Also it is impossible to at new programs to the menu, like OpenOffice or StarOffice. If I hit in kmenu "Kontrolleiste einrichten --> Hinzufügen --> Knopf" I see all the new stuff and it's able to take them to the Kontrolleiste, but not to kmenu. Does somebody knows whats going wrong and how I can repair it? Michael

1 0

Konqueror 3.0.2.
by Hans Krueger 02 Aug '02

02 Aug '02

I'm having trouble with Konqueror 3.0.2.remembering passwords does any body have a fix ? thanks -- Hans Krueger hans007(a)prexar.com "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin

1 0