KDE 3.1.3 Released!

Tuesday, 29 July 2003  |  Dmueller

The KDE Project announced KDE 3.1.3 today. It's the third maintenance release of the successful KDE 3.1.x series and ships with many bugfixes and improved translations. KDE 3.1.3 also contains a fix for a possible HTTP authentication leak in the HTTP referrer header. Users of KDE 3.x are advised to upgrade to KDE 3.1.3. Read the change log or directly jump to the download links on the KDE 3.1.3 Info Page. The Konstruct build toolset was updated accordingly.

Comments:

Congratulations... - Chakie - 2003-07-29

... to all the developers!

Re: Congratulations... - Robert Schouwenburg - 2003-07-29

And thanks....

Re: Congratulations... - obi - 2003-07-29

You guys really rock. Thank you !

Gcc 3.4+ - Ruediger Knoerig - 2003-07-29

First a big,big THANK'S to the developer! I've seen a lot of comments related to gcc3.4+ compilation issues. Is gcc3.4+ ready for production systems? The actual snapshot of gideon had some trouble as I tried to compile it with gcc3.3.1 (prerelease from Jul. 20). I remember some trouble like char *dst=QString (assignment (const char *) to (char *)), a double 'const' in a xpm file (const char *name const = ...) and a lot of 'using default value for ... parameter of ( bool ... = false in the .cpp) in the Ada related stuff.

Re: Gcc 3.4+ - fault - 2003-07-29

const char *name const is perfectly valid C++, and is correct.. afaik.

Re: Gcc 3.4+ - Arno Nym - 2003-07-29

It is not ready until it has been released. 3.3.x is the current stable branch. The reason for the numerous gcc 3.4 fixes is that the 3.4 branch has a new C++ parser, which is a little bit more picky about the standard.

Re: Gcc 3.4+ - Dirk Mueller - 2003-07-29

GCC 3.4+ is not ready for use it, nonetheless we try to keep our code compatible to as many compilers as possible. It is not recommended to use gcc 3.4 with KDE yet as it still contains a few miscompilations and bugs that won't make the result of compilation usable for end users. But if you're adventurous and not afraid of tracking down bugs and fix them, you're welcome to try :-)

Re: Gcc 3.4+ - Daniel Stone - 2003-07-30

I don't even recommend using GCC 3.3, as it's absolutely awful. ICEs on xfree86 and kdebase on multiple architectures (including, but not limited to: arm, mips and mipsel), used to ICE on i386, miscompiles ?dm authentication at -O2 on every architecture (AFAICS - at least amd64, i386, ia64, powerpc and sparc), and more. If you care about your code, stay back at 3.2 until they unbreak 3.3 (haw!). Oh yeah, and it fails to compile aspseek (a 3.2 regression), because its parser is horribly broken, and they're not planning to fix that one till 3.4. Nice one!

Re: Gcc 3.4+ - Garen - 2003-07-30

dm authentication? I don't see a bug like that over at gcc.gnu.org/bugzilla. If you could generate a minimal test case for it and file a bugreport there I'm sure it would be useful.

Re: Gcc 3.4+ - Daniel Stone - 2003-08-01

It's been filed already, and I think they've fixed it in 3.4.

Re: Gcc 3.4+ - Leo Savernik - 2003-07-30

With gcc 3.4, can KDE finally be compiled with precompiled headers? How much faster will gcc 3.4 w/pch compile kde compared to gcc 2.95?

Re: Gcc 3.4+ - Tim Jansen - 2003-07-30

This won't work until somebody adjusts the make system (and possibly the sources), because gcc can only use one precompiled header per compilation unit. So you have to create header files that contain all headers that a program uses, then precompile this header file and include it from all sources.

Re: Gcc 3.4+ - perraw - 2003-07-30

But what if all qt headers are pre compiled in to qt_all.h and all kde headers are compiled into kde_all.h Then all qt headers first include qt_all.h and the same with kde? Wouldn't that help? Or what approach is one suppose to take? I really hope we don't have to change all kde program and use ifdef using gcc-3.4 then one big fat file, else all different headers?

Re: Gcc 3.4+ - Tim Jansen - 2003-07-30

It would work, but I am not sure whether including 1000 precompiled headers is still faster than 50 that are not precompiled :) The intended way seems to be that each application/module/library has an all.h with all headers that it needs.

Re: Gcc 3.4+ - perraw - 2003-08-02

MFC in Visual C++ you just include stdafx.h and you are done. Anyway, it will be really interesting to see what will happen when we have gcc 3.4 around. I bet there will be a big flame fest on what we should do about it. Just thing about how easy it is to use a QThatClass without including the header for people not using PCH ;=)

Re: Gcc 3.4+ - cbcbcb - 2003-07-31

I've seen a few different approaches to compiled headers. The one I think makes most sense is that each program includes just the header files it requires. An all_headers.h is created which #includes all of the header files. Then to use the precompiled headers the build system adds -include precomp.h to the gcc command line. (The multiple inclusion guards in the original header files still work so they do not need to be parsed again) This mechanism means that systems without precompiled headers don't suffer from including every single header file.

Re: Gcc 3.4+ - Alistair Strachan - 2003-07-31

It won't be. Precompiled headers reduce compile time, because headers that are included repeatedly through a lot of sources do not have to be continuously parsed by the preprocessor. The compiled output may be marginally different, but I doubt it will be significantly faster.

Re: Gcc 3.4+ - Justin - 2003-07-31

Microsoft Visual C++ 6.0 supports precompiled headers, and it makes a world of difference. When I build Psi on Linux (gcc 3.2) and Windows (MSVC++ 6), the MSVC build process blows gcc away in terms of speed. It's probably 4 or 5 times faster. To further rub it in, I'll note that my Linux box is a P4 1.6GHz and my Windows box is a P2 400MHz. I am very much looking forward to precompiled headers in gcc.

Re: Gcc 3.4+ - Richard - 2003-07-31

This has been my experience as well. I used to do MFC programming on a P3 600MHz w/ 128MB RAM. It was quite snappy. But when developing a small Qt application on Linux, My 1.33GHz w/ 768MB RAM (that's more than twice as fast) it's a serious pain in the ass. GCC 2.95.x used to be very reasonable in compile speed, but 3.x has changed dramatically. It's funny though that no one has commented on your message yet. I bet no one wants to believe that GCC is not all that great when it comes to compile times. Maybe it's because we shouldn't complain because it's free anyway so we should fix it ourselves. I've been looking forward to gcc 3.4 ever since 3.2 was released. I was dissapointed to learn that it was delayed for 3.4 though, I wanted this in 3.3 :)

Re: Gcc 3.4+ - SadEagle - 2003-07-31

No, it's probably because everyone has complained about g++'s compile times so much it's getting old on us already :-).

Re: Gcc 3.4+ - Rayiner Hashem - 2003-08-02

Everybody and their mother knows that G++ is glacially slow. Searching for "gcc slow" on google nets 112,000 Google hits. Its acknowledged even in the gcc mailing lists.

Re: Gcc 3.4+ - Leo Savernik - 2003-08-02

> GCC 2.95.x used to be very reasonable in compile speed, but 3.x has changed dramatically. Awww, if you call gcc 2.95's speed reasonable, then gcc 3.x must be really, utterly, painfully slow. So I'll stay with gcc 2.95 another 4 years :-(

yes, it will be significantly faster - precompiled - 2004-12-01

i've seen the difference of compiling a wxWidgets application on a PII400, with and without precompiled headers. the compile time dropped from 3 minutes to something like 40 seconds. the difference is more than obvious.

debian /usr/bin/startkde bug - FreakOne - 2003-07-29

A bug that already occured in the debian packages of kde 3.1.2 found its way again into 3.1.3: In /usr/bin/startkde line 150 LD_BIND_NOW=true kdeinit +kcminit +knotify doesnt start kdeinit, what leads to the situation that all arts-related programs like kaboodle and noatun cant be startet. I fixed it changing to LD_BIND_NOW=true kdeinit +kcminit +knotify Did this happen to anybody else? By the way, great work guys!

Re: debian /usr/bin/startkde bug - SadEagle - 2003-07-29

The LD_BIND_NOW=true is there for a reason, the change you're suggesting is incorrect. Can you please elaborate on what exactly crashes, and further; I'd suggest you check your libvorbis install. (Although this prolly should go into bugzilla..)

Re: debian /usr/bin/startkde bug - FreakOne - 2003-07-29

To me the original line seemed like a typo - like someone missed a line break between the variable definition and the call of kdeinit. With the litle change it works... What didnt work was that after logging into the kde session with kdm there was no sound with every kde app like kaboodle and noatun. No startup buzz and an error message claiming that kde couldnt initalize e.g. kaboodle.

Re: debian /usr/bin/startkde bug - SadEagle - 2003-07-29

Well, as I said, the change is wrong. It effectively turns the assignment into a no-op. FOO=bar ./app sets FOO into apps environment. Doing it on a separate line merely sets a shell local.

Mandrake pkgs - AC - 2003-07-29

Perhaps this is a dumb question, but how come there are no binary packages for Mandrake lately?

Re: Mandrake pkgs - Bojan - 2003-07-29

Not a dumb question at all, I was asking myself the same thing...

Re: Mandrake pkgs - Arno Nym - 2003-07-29

I think because Mandrake needs money and only provides them for a fee (club members or whatever they are called, not a mdk user myself...)

Texstar - JLP - 2003-07-29

I think they will be up on Texstars RPM mirrors quite soon for users of Mandrake 9.1. The packages for 9.2 Beta 1 are already available on the offical Mandrake Cooker RPM mirrors.

Debs for Woody! - Jeremiah Cornelius - 2003-07-30

Add to your /etc/apt/sources.list: deb ftp://ftp.uni-kl.de/pub/linux/kde/stable/3.1.3/Debian woody main

Re: Debs for Woody! - BenjyD - 2003-07-30

What! Debian has 3.1.3 before Gentoo? Something's wrong here.

Re: Debs for Woody! - Debian user - 2003-07-30

What about sid aka unstable?

Re: Debs for Woody! - Burrhus - 2003-07-31

Gentoo has 3.1.3, but it's still in testing. If you really can't wait a few more days, you can comment it out in /usr/portage/profiles/package.mask.

Re: Mandrake pkgs - Amund - 2003-07-30

Texstar provides rpm packages of kde 3.1.3 for Mandrake. If you have not installed any sw source for Texstar, you can do it with this comand under Mandrake 9.1: urpmi.addmedia texstar ftp://ftp.ibiblio.org/pub/Linux/distributions/contrib/texstar/mandrake/9.1/rpms with hdlist.cz If the ftp server is not reachable, then you can try this: urpmi.addmedia texstar2 ftp://ftp.bahcesehir.edu.tr/pub/texstar/mandrake/9.1/rpms with hdlist.cz If you are not running 9.1, you can find a mirror here: http://plf.zarb.org/~nanardon/ Import the keys: wget -O - ftp://ftp.ibiblio.org/pub/Linux/distributions/contrib/texstar/linux/distributions/mandrake/9.1/gpgkey/pubring.gpg | gpg --import Finaly you may Upgrade kde: urpmi kdebase Or you may upgrade everything: urpmi --auto-select (Later, you can find new SW at texstar and update your urpmi database: urpmi.update texstar or urmpi.update -a Then you can updrade all: urpmi --auto-select )

Re: Mandrake pkgs - a.c. - 2003-07-30

you need to change this slightly to: wget -O - ftp://ftp.ibiblio.org/pub/Linux/distributions/contrib/texstar/mandrake/gpgkey/pubring.gpg | gpg --import

Re: Mandrake pkgs - AC - 2003-07-31

Wow. Very informative. Thanks.

Re: Mandrake pkgs - Richard Jones - 2003-08-01

Thanks for this advice, it works a treat (with the fix mentioned in the other reply). I ended up doing --auto-select, and had about 730Mb of RPMs to install (about 770 in total). I had done *no* RPM updating except for mandrake's security fixes since installing 9.1 from CD. There were a couple of very minor dependency issues: 1. saslauthd needed libcom_err.so.3 but I couldn't easily find something to satisfy it, so I uninstalled it (and postfix) :) 2. kdebase-kdm-config-file wasn't updated for 3.1.3, so I installed the 3.1.2 version instead, having to go --nodeps 'cos *that* wanted kdebase-3.1.2 ;) All done in single-user mode, of course. Everything appears to be running just fine now.

Yay! - Coolvibe - 2003-07-29

Kudos for this release. Also, FreeBSD already merged it into the ports tree. head on over at rabarber.fuitsalad.org for precompiled packages if you want to be compiling for the next few days.

Re: Yay! - Coolvibe - 2003-07-29

run sed -e s/if you want/if you _don't_ want/ on that sentence... Damn, I should have previewed...

SuSe - Hiryu - 2003-07-29

I switched from 5 years of debian to SuSe 8.2 recently (Love both but don't wanna feel like a sys admin at home anymore). How does one auto upgrade in an apt-like way to kde 3.1.3 in SuSe? I'm unclear on this matter... I hope this fixes this small but annoying konqueror bug. :/ Thanks.

Re: SuSe - Richard - 2003-07-29

You need to be a little patient before the rpms arrive in the suse-8.2 apt repository. Just watch: http://linux01.gwdg.de/apt4rpm/freshrpms.html More about apt for suse at: http://linux01.gwdg.de/apt4rpm

Re: SuSe - Evan "JabberWokky" E. - 2003-07-29

You can use the text or X interface of 'yast', and do Software/Online Update (or 'yast online_update')... or just go to the KDE Control Center and choose "Yast/Software/Online Update".

Re: SuSe - Hiryu - 2003-07-29

Thanks for the replies. 1st of all, I checked to make sure there were suse 8.2 rpms for kde 3.1.3 before posting (though I'm still with 3.1.1 so even just getting 3.1.2 would be fine). Those rpms are found here: ftp://ftp.kde.org/pub/kde/stable/3.1.3/SuSE/i386/8.2 I have tried the online update too but it didn't seem to work for me. Most likely I entered the url incorrectly. I'm still not entirely sure what files yast looks for so I can add urls correctly (on my first attempt anyway). I'll go experiment a bit now and see what I can pull off. Again, thanks.

Re: SuSe - Anonymous - 2003-07-30

You have to add an URL ending with "yast-source/" directory to YaST like ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_8.2/yast-source or equivalent on mirrors - atm this only holds KDE 3.1.2 but I would expect this to be updated soon to KDE 3.1.3 once the packages are more mature/tested.

Re: SuSe - Hiryu - 2003-07-31

Thanks... Now that I have it added, what do I do? Nothing seems to get me to the versions of the packages on the url (which appears to be 3.1.1 now).

Re: SuSe - Anonymous - 2003-07-31

Call "Install and Remove Software" or "Online Update". :-)

Re: SuSe - Hiryu - 2003-08-01

Neither of which seem to be doing the trick... Very strange, I'll try it some more however and see what happens. Thanks.

Re: SuSe - jadrian - 2003-08-01

I think you have to move that new ftp url up to the first place in the list... J.A.

Re: SuSe - Hiryu - 2003-08-01

Of course. That's what I did from the begining. :)

Re: SuSe - info - 2003-07-31

Hi, hier is an other way: get the rpm-fils from the link e.g.: ftp://ftp.kde.org/pub/kde/stable/3.1.3/SuSE/i386/8.2 and copy them into a directory. Go to rumlevel 1 by typing init 1 and then install the files with the rpm command : rpm -ivh --force --nodeps *.rpm good luck no guarantee CU

Re: SuSe - Aaron J. Seigo - 2003-07-31

when upgrading RPMS manually, use -Uvh, NOT -ivh... in fact, use -Uvh when installing any package that doesn't require parallel installations with previous versions (e.g. the kernel)... as for --force and --nodeps, that's a recipe for seriously messing up your system. at that point, why even bother having a package manager? dependencies are there for a reason, listen to them.

Re: SuSe - CE - 2003-07-31

With SuSE he could also use "yast2 -i" to install (or "yast2 --help" for more options, of course). I don't know it, but I guess it is better with yast2.

Re: SuSe - Ingo Klöcker - 2003-08-01

Actually you should use -Fhv (F == freshen). Then you can simply do a 'rpm -Fhv *.rpm' in the directory to which you downloaded all the KDE 3.1.3 RPMs and rpm will only install newer versions of already installed RPMs. If you use -Uhv instead then rpm will install all RPMs which are in this directory. I agree with Aaron that using --force and --nodeps is very dangerous and should be avoided at all cost.

Re: SuSe - faa - 2003-08-01

wget -r -l1 ftp://your.favourite.host/pub/kde/stable/3.1.3/SuSE/i386/8.2/ cd your.favourite.host/pub/kde/stable/3.1.3/SuSE/i386/8.2/ rpm -Fvh *.rpm enjoy

Re: SuSe - gunni - 2003-08-01

I did this yesterday with my suse 8.2 system. I fired up yast2 control center, selected Change Source of Installation Clicked Add, ftp and put in the following url: ftp://ftp.kde.org/pub/suse/i386/supplementary/KDE/update_for_8.2/yast-source Then I enabled it on and moved it above all the other lines in that window Next I clicked Install and Remove Software, and for each group relating to KDE I did a update if newer version is available. This can be done in Package->All in this list. That's it, it took a while and the new packages work fine. Hope this works for u :)

Whoever does the RedHat packages... - ac - 2003-07-30

THANKS! You're doing a great service and I really appreciate it.

Re: Whoever does the RedHat packages... - Anonymous - 2003-07-30

Unless somewhere is stated that they are unofficial, they should be coming from RedHat. It would be nice to have packages for the two or the three latest RedHat releases though.

Re: Whoever does the RedHat packages... - Anon - 2003-07-30

I just checked, the packages are provided by Red Hat (thanks!). Upgrading a stock RH 9 install was as easy as "rpm -Fvh *rpm". Quite an improvement, only a year or two ago basically only source tarballs were provided. Now people might actually upgrade instead of just waiting for the next distro version to include them. I know I couldn't be bothered unless the packages were available.

Re: Whoever does the RedHat packages... - ac - 2003-07-30

Wow. RedHat making KDE packages. I must remember to take my meds on time...

Also - Maynard - 2003-08-02

It seems to me that people are wuite ready to forgive anything Mandrake does but not Redhat. Imagine if Redhat did not provide rpms of KDE. This was just compiling them. I am sure the debate about whether Redhat does not like KDE would go on for ever. But since its Mandrake, the small company, well, people are willing to gloss over that and tell you to buy the retail if you want the 'service'. Just an observation.

Re: Whoever does the RedHat packages... - Rex Dieter - 2003-07-30

See http://kde-redhat.sf.net/ for rh73-rh9 KDE RPMS.

i18n.kde.org offline - Steinchen - 2003-07-30

Any ideas why? Steinchen

Re: i18n.kde.org offline - CE - 2003-07-30

Down for maintenance? PS: What happened to the translations to Klingon and Latin?

Re: i18n.kde.org offline (latin?) - stupid anon /.-poster - 2003-07-31

No idea, but if you have any more information on the latin translation, please let me know. i was and still i am interested in a latin translation for kde :) gratias tibi ago, - deucalion. PS: if anyone knows any urls or mailing-lists please reply with more information containing them, thx.

Re: i18n.kde.org offline - Chris Howells - 2003-07-30

The hard disk on the server failed, apparently. Unfortunately the DNS was hosted on the same machine as the web server. Hopefully we can try and get something more robust sorted out when the machine is up again.

Debian Woody packages - Anonymous - 2003-07-30

Hi all, I've just added a line for my local kde mirror to sources.list, run apt-get update and apt-get upgrade but apt reports this to me: # apt-get upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back amor ark artsbuilder atlantik eyesapplet fifteenapplet flashkard kaboodle kalarm kalzium kamera kaphorism kappfinder karm kasteroids kate kate-plugins katomic kaudiocreator kbackgammon kbattleship kblackbox kbounce kcalc kcharselect kcmlinuz kcoloredit kcontrol kcron kdat kdeaddons-kfile-plugins kdeadmin kdeadmin-kfile-plugins kdeartwork kdeartwork-style kdeartwork-theme-window kdebase kdebase-bin kdebase-kio-plugins kdegames kdegraphics kdegraphics-kfile-plugins kdelibs-bin kdelibs-data kdelibs4 kdelibs4-dev kdemultimedia kdemultimedia-kfile-plugins kdemultimedia-kio-plugins kdenetwork kdenetwork-kfile-plugins kdepasswd kdepim-libs kdeprint kdesktop kdessh kdeutils kdf kdict kdm kdvi kedit keduca kenolaba kfax kfind kfloppy kfouleggs kgeo kget kghostview kgpgcertmanager khangman khelpcenter khexedit kicker kicker-applets kiconedit kit kiten kjots kjumpingcube klaptopdaemon klettres klickety klines klipper kmahjongg kmail kmailcvt kmenuedit kmessedwords kmid kmidi kmines kmix kmoon kmplot kmrml knewsticker knode knotes kodo kolf konq-plugins konqueror konqueror-nsplugins konquest konsole kooka korganizer korn kpackage kpager kpaint kpat kpercentage kpersonalizer kpf kpoker kpovmodeler kppp krdc krec kreversi krfb kruler ksame kscd kscreensaver kshisen ksim ksirc ksirtet ksmiletris ksmserver ksnake ksnapshot ksokoban kspaceduel ksplash kstars ksysguard ksysguardd ksysv kteatime ktimer ktip ktouch ktron ktuberling ktux kuickshow kuser kverbos kview kviewshell kvoctrain kweather kwin kwin4 kworldclock kxconfig kxmlrpc libarts1-mpeglib libkdeedu1 libkdegames1 libkdenetwork2 libkonq4 libkregexpeditor libkscan1 lskat megami mpeglib noatun noatun-plugins quanta secpolicy 17 packages upgraded, 0 newly installed, 0 to remove and 178 not upgraded. Need to get 10.7MB of archives. After unpacking 12.3kB will be freed. Do you want to continue? [Y/n] I've never had this problem before and have no iead why all these packages are been held back. How do find out what is causing this? Thanks,

Re: Debian Woody packages - cbcbcb - 2003-07-30

try apt-get dist-upgrade. dist-upgrade is like upgrade except it can remove conflicting packages to allow upgrades to proceed. Don't allow it to remove a package that you want to keep though!

Re: Debian Woody packages - Anonymous - 2003-07-30

Thanks, that has done the trick, don't know why I didn't try that myself.

Some problems and suggestions - anon - 2003-07-31

I don't know where to post wishes for improvements to KDE, so I do it here: 1. When moving icons on the desktop I can't move them only a few pixels, so it's hard to place them exactly where I want them. 2. I don't know how many times I have wanted to delete a file with the right-click menu in Konqueror, but instead ended up with a bookmark because I accidentally clicked a bit lower in the menu. A dialog box when adding bookmarks would be nice. 3. When an application doesn't respond and it's impossible to simply close it, it would be nice to have a dialogbox that pops up and tells you that "The application is not responding, would you like to kill it?" (This may be impossible because of how X works, I don't know). 4. Sometimes konqueror locks up for a short time, especially when having several network connections open. Is this a problem with the Linux kernel, KDE, or the distro? I have tried Redhat and Mandrake and the problems seem to be the same. 5. A great feature would be to be able to mount iso-files to a directory with a right-click in Konqueror. 6. Would it be possible to have a movie as a background on the desktop behind the icons? If anyone have some answers to the problems above I would be glad to know. Otherwise I'm very pleased with KDE.

Re: Some problems and suggestions - Joel Carr - 2003-07-31

2. I think a dialog box asking if you want to add a file to the bookmarks when the option is selected from the right click menu would be an excellent idea. It is very frustrating accidently adding it to the bookmarks when you meant to delete it. Of course this option should be configurable. 3. When an application has stopped responding, you can press ctrl-alt-esc and then click on the crashed window, and it will be killed. So a dialog box isn't really necessary, but I guess it would be newbie friendly as long as it could be turned off.

Re: Some problems and suggestions - Eric Laffoon - 2003-07-31

> 2. I think a dialog box asking if you want to add a file to the bookmarks when the option is selected from the right click menu would be an excellent idea. It is very frustrating accidently adding it to the bookmarks when you meant to delete it. Of course this option should be configurable. I think it's a terrible idea. Perhaps configuring your mouse or not roller skating when using the menu? ;-)

Re: Some problems and suggestions - Alex - 2003-08-04

this is in 3.2 (HEAD). and its an option. give this addition a try ~/.qt/kstylerc [Settings] ScrollablePopupMenus=true this will fix the currently heavily b0rked bookmarks menu by allowing you to scroll in it. still buggy though, so, until its fixed i'm not making it anything more than a rc config switch. Alex

Re: Some problems and suggestions - Alex - 2003-08-04

eek. i reread. no. terrible idea. fix your mouse. you could say the same thing about a thousand and one other things in the gui. you can work around this with the new option of course, but its only working from bookmarks menu at the moment and not the right click menu. Alex

Re: Some problems and suggestions - Arno Nym - 2003-07-31

>I don't know where to post wishes for improvements to KDE bugs.kde.org is the right place, mark your report as 'wishlist/feature request'. Do not forget to vote for the bug/feature, especially if it already exists.

Re: Some problems and suggestions - Anonymous - 2003-07-31

3: press ctrl+alt+esc and kill

Re: Some problems and suggestions - Xanadu - 2003-08-01

I think you mean just CTRL+ESC. unless of course you're thinking about NT.*... :-)

Re: Some problems and suggestions - Xanadu - 2003-08-01

nevermind... I was thinking SHIFT and not ALT... Sorry...

Re: Some problems and suggestions - Anonymous coward - 2003-07-31

[Sorry for my bad English.] I guess a lot of what you're asking for is already in kde... 1. Fixed in CVS (I think). 3. You might use ctrl+esc -> kill or ctrl+alt+esc. There's a panel applet that tries to do what you want, too. 5. You should be able to create a "Konqueror service menu" that does just that. Check the article on the subject. 6. Use the "Programm" option and look for a programm that can play a video in the root window... (xscreensaver module?)

Please - Alex - 2003-07-31

Submit all of your original suggestions to bugs.kde.org, but make sure that they are not duplicates and you will find th KDe developers to be very reactive. Posting here will not help these problems dissappear.

Re: Please - James Richard Tyrer - 2003-07-31

"Reactive", yes! Receptive, sometimes I'm not so sure -- like when wish list items are closed in less than 24 hours. Very odd! So, I am going to post this here since I never really received an answer on Bugzilla. Did receive a note from Steven K. (Thanks :-)) but I don't think that he was sure what the problem was. The font names in the font dialog are WRONG in many cases: "Arial Mt" should be "Arial MT" (this is *NIX, case matters) "Swis721 Bt" should be "Swiss721 BT" again case matters but how do you spell 'Swiss'? There also appears to be some confusion over what is part of a: "Font" and what is part of a: "Font style". "Arial Narrow" is listed as a separate font which I think is correct, but with "Helvetica", "Narrow" is thrown in with the: "Font style". "Gill Sans" and "Gillsans" are two separate fonts. The first one has the Helvetica problem, only worse. If this is a problem with Qt, I think it is a show-stopper and somebody better get those trolls to working on it rather than inventing nifty new features. I do really like the nifty new features, but this is more than just an annoyance if you have a bunch of fonts. If this is a problem with KDE, then the 3.2 release MUST be held till it is fixed. -- JRT

Re: Please - cloose - 2003-07-31

You got to be kidding. Hold up a release because some font names are misspelled or have wrong case?? That's ridiculous! It's not like the fonts don't work because they are not shown correctly in the font dialog. It might be an annoyance but it's definitely not a show-stopper. IMO we would be on a very good way if a release would only contain bugs like this. Christian

Re: Please - Arno Nym - 2003-07-31

Do not feed the trolls.

Re: Please - James Richard Tyrer - 2003-07-31

You appear to have missed something. GhostScript can't find the fonts either if the names are wrong. And if you send something out to be printed with the wrong font names ... This IS a serious problem. Not to mention that some of the fonts just don't work on the screen either. -- JRT

Re: Please - Craig Drummond - 2003-07-31

The "Arial MT" being called "Arial Mt" thing maybe due to the fact that X lists fonts in lowercase - so Qt is capitalising the first letter of each "word" so that it looks nicer. (i.e. X gives it "arial mt", so KDE/Qt list "Arial Mt") When printing, if Qt uses the name "ArialMt" as the guessed ps name (which I beleive it does), then this should be OK - as the font installer will create an alias in the Fontmap file that'll map from "ArialMt" to "ArialPSMT" (or whatever its PS name is). (That's the theory anyway...)

Re: Please - James Richard Tyrer - 2003-07-31

>The "Arial MT" being called "Arial Mt" thing maybe due to the fact that X >lists fonts in lowercase. The XLFDs are in lower case but the fonts contain the correct case. >When printing, if Qt uses the name "ArialMt" as the guessed ps name (which I >beleive it does) Unfortunatly, it doesn't. As clearly stated in the original bug report: http://bugs.kde.org/show_bug.cgi?id=60105 -- JRT

Re: Please - Craig Drummond - 2003-08-01

As I said - Qt gets the name from the XLFD, not from reading the actual font. It then capitalises the first letter of each "word" - hence what you are seeing. Can you send me a simple ps file with the mistakes that are happening? Its possible that I'll need to add more aliases to the Fontmap files.

Re: Please - James Richard Tyrer - 2003-08-02

>As I said - Qt gets the name from the XLFD This isn't going to work! Qt now uses FontConfig doesn't it? It should get the human readable as well as the PS font name using FontConfig! >Its possible that I'll need to add more aliases to the Fontmap files. I don't think that this is the answer to the problem. Although it will (and does) fix that stupid problem with Swis721/Swiss721, you would have to add an alias for over half of the fonts. -- JRT

Re: Please - James Richard Tyrer - 2003-08-02

I browsed through a little of the Qt code and it appers that Qt uses: XFT_FAMILY to fetch the font family name. IIUC, this is 'thunked' into FC_FAMILY with XFT[2] using FontConfig. In any case, this would be read from the font file, and it is correct in the: "fonts.cache-1" file. I didn't check the PS generation, but since FreeType2 has the facility to obtain the PS font name, I would hope that that is what being used, but it doesn't look that way. I think that the problem is with Qt but I don't understand some of the code in KfontDialog. -- JRT

Re: Please - James Richard Tyrer - 2003-08-04

I have determined that the problem is in Qt :-( I will file a bug report with TrollTech. Perhaps others don't understand, but discussing the problem with others was a great help in determining the exact nature of the problem. -- JRT

Re: Please - Jeff Johnson - 2003-07-31

If this problem is in KDE 3.1.3, I think it should be recalled immediately before too many users are confused by font misnaming.

Re: Please - Chris Howells - 2003-07-31

> like when wish list items are closed in less than 24 hours Some wish list items are quite frankly silly. They would be useful to about 1 in a million people. IMplementing such a feature would often be detrimental to the program. Other items may be extremely hard to implement, or not possible. It's the maintainer's right to decide the direction of the program and close wishlist items that he does not feel are appropriate.

Re: Please - Eric Laffoon - 2003-07-31

These perceptions are only relevent to those who have reasonable expectations not tied to a "consumer" perspective. (a/k/a send a patch) Personally I very much like a statement from "Accelerated C++: Practical Programming by Example"... "Abstraction is selective ignorance". Good design requires decisions affecting a quality user experience for many which must compete for the attention of what few would even care about or notice, let alone want. Sometimes an application of abstraction beyond the programming model is indicated... When someone thinks you should add substantial code for insubstantial issues what do they think will happen with the other substantial code you were going to write?

Re: Please - Aaron J. Seigo - 2003-08-01

> When someone thinks you should add substantial > code for insubstantial issues what do they think will > happen with the other substantial code you were going to write? write it as well, of course. i mean, you are a superhuman coding god[ess] with nothing better to do with your time, right? ;-) just as Free software developers need (or are at least are expected) to be sensitive to user input, users need to be sensitive to the realities of the developer's lives. and i agee about selective ignorance being important.

Re: Please - fault - 2003-07-31

> "Arial Mt" should be "Arial MT" (this is *NIX, case matters) Arial Mt seems to be correct.. as in, WindowsXP does this too... > "Swis721 Bt" should be "Swiss721 BT" again case matters but how do you spell 'Swiss'? I have this font (comes from BeOS), and the real name of this font is Swis, not Swiss. What led to you beleive it was Swiss?

Re: Please - Roberto Alsina - 2003-07-31

because Swiss makes sense as a Helvetica ripoff and Swis doesn't ;-)

Re: Please - James Richard Tyrer - 2003-07-31

>Arial Mt seems to be correct.. as in, WindowsXP does this too... You may have something there as to why the error exists. That probably works fine in Windows, but (again) UNIX is case sensitive and it won't work here. >I have this font (comes from BeOS), and the real name of this font is Swis, >not Swiss. What led to you beleive it was Swiss? BeOS might be where you got it, but it is a standard BitStream font (I probably got it with WordPerfect). This is interesting. The font name as listed in the XLFD *is* swis721" but the Fontmap file has: "Swiss721BT-Roman" So, this may have a different cause which I will have to look into. Open the font with the HEX editor, there appears to be a problem with the font. << Swiss721BT-RomanCopyright 1990-2000 Bitstream Inc. All rights reserved.Swis721 BTSwiss 721Swis721 BT RomanVersion 1.00 >> WordPerfect shows only one 's' [Swis721] Clearly this is still a bug, and I'm not sure of the solution since GhostScript can NOT find it: << Can't find (or can't open) font file Swis721BT-Bold. >> -- JRT

Re: Please - James Richard Tyrer - 2003-08-02

The Swis/Swiss problem would appear to be a GhostScript bug not a KDE bug. To fix it (a work around), just put the attached in your: Fontmap.GS in the "ghostscript/<version>/lib/" directory and it will work even though GhostScript still thinks that it is: "Swiss". You would need the first line any who -- another interesting GhostScript quirk. -- JRT

Re: Please [Followup on Swiss721/Swiss721] - James Richard Tyrer - 2003-08-03

NO, I was wrong. It isn't a GhostScript bug. I parsed the TTF font header by hand: Font Family name: "Swis721 BT" Postscript name: "Swiss721BT-Roman" This would indicate a much more serious bug that is different from the KFontDialog problem. There (in KFontDialog), it is correct for it to be: "Swis721 BT", but the PS name *is*: "Swiss721BT-Roman". Which means that something is getting the PS name wrong. Since all that is needed to get it right is to read the font file or use the FreeType2 library, I presume that unless there is a problem in FreeTyp2 that something isn't designed correctly. I note that: "ttf2pt1" gets it right, so it shouldn't be that hard. So, it could be a Qt, FreeType2, or KDE bug. -- JRT

qt-3.2.0 - Dim - 2003-07-31

Is it possible to build 3.1.3 version with qt-3.2.0? I had a lot of problems... Should we wait for 3.1.4 release?

Re: qt-3.2.0 - CE - 2003-07-31

Perhaps we'll have to wait for the release of 3.2?

Re: qt-3.2.0 - Henrique Pinto - 2003-07-31

Not really. Work is being done in order to make KDE 3.1.4 "compatible" with Qt 3.2. And yes, you can compile 3.1.3 with Qt 3.2, but you should expect some (minor) annoyances.

Re: qt-3.2.0 - Braindead - 2003-08-04

How to compile with qt-3.2: I edited to configure file by searching for the string "qt 3.2" then changing the minor number to 2 from 1 where the configure script checks for the version of qt 3. Then when you run configure it doesn't fail and compiles perfectly.

Horizontal scroll and bad margins? - Ricardo Galli - 2003-07-31

I'be upgraded just kdelibs4, which is already in Debian. My question is ¿do you see this bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203626)? ¿or is it just due to missing/upcoming updates? Thanks. ---------------------------------------------- Bug report text: Just upgraded to kdelibs4 3.1.3 (although not yet the rest). As the subject says, horizontal scroll bars appear always, even when not necessary. It seems to me that's related to khtml because the left and right margins dissapeared in this version, so perhaps is a bad width calculation. If a html page has a table of 100% width, part of the text might be occlused by the border. Check for example http://lwn.net o http://bulmalug.net. It's quite annoying. BTW, I also read similar reports in debian-kde mailing list.

Re: Horizontal scroll and bad margins? - Anonymous - 2003-07-31

Already known: http://bugs.kde.org/show_bug.cgi?id=61730

Re: Horizontal scroll and bad margins? - Ricardo Galli - 2003-07-31

Thanks... but the (related?) bad margins are worse, in some pages (with 100% width tables) last characters are hidden and you must scroll horizontally to read them.

Re: Horizontal scroll and bad margins? - mms - 2003-08-04

I built updated packages that may solve your problem (it did for me) : http://profs.insia.org/manu/debian/ just 'dpkg -i *.deb' to avoid dependancies headache :)

WANTED: kdebase3.. SuSE RPM's - sakana - 2003-08-01

Hi, anybody knows whty SuSE didn't upload/update the kdebase-packages on the servers ? i can only find: kdebase3-3.1.2-66.i586.rpm and so on... isn't that strange ? hm, actually the base-packages containing many changes/bugfixes! :(

Re: WANTED: kdebase3.. SuSE RPM's - ulla - 2005-01-19

Found them in e.g. (mirror in Switzerland, try other mirros with similar path): ftp://ftp.solnet.ch/mirror/SuSE/i386/supplementary/KDE/update_for_9.1/base/kdebase3-kdm-3.3.2-7.i586.rpm

No KDE support for TabletPC - NS - 2003-08-01

I am using KDE 3.1.3 now in laptop and desktop. Excellent work! Opie in Ipaq. I am wondering why no one use KDE in TabletPC linux, I guess not support yet. Gnome folks are very active on TabletPC as you can it here: http://www.tuxmobil.org/tablet_unix.html http://handhelds.org/~mallum/xpkgs/tabletpc/ http://handhelds.org/hypermail/tc1000-linux/current/ Opie is very active for Ipaq http://opie.handhelds.org/ http://handhelds.org/hypermail/opie-devel/current/ http://handhelds.org/hypermail/opie/current/ Opie has support calibration, rotation and single stroke recognisation even graffiti, which KDE folks could port to KDE to be useful for TabletPC, I think. http://cvs.handhelds.org/cgi-bin/viewcvs.cgi/opie/inputmethods/

Re: No KDE support for TabletPC - James Richard Tyrer - 2003-08-01

I'm not sure that I understand. Did you try KDE with a tabletPC? Did you have some problems using it? In case you don't understand: the tablet is just another mouse driver in XFree86. You might need to build Qt with: "-tablet" which requires "XFree86 with X11/extensions/XInput.h and libXi" (whatever that means) which XFree86 4.3.0 appears to have. -- JRT

Re: No KDE support for TabletPC - NS - 2003-08-01

I don't have a TablePC yet :-). Ok, I think this is QT problem, not yet for KDE. I google for QT Tablet, result is: Initial support: qt-x11-free-3.2.0b2, built with tablet support mentioned here: http://lists.trolltech.com/qt-interest/2003-07/msg00983.html#msg00983 I guess QT should have this support for TabletPC that I mentioned earliear in my posting since they created those support for QT Embedded.

Re: No KDE support for TabletPC - NS - 2003-08-01

Look what I have found: http://doc.trolltech.com/3.2/qtabletevent.html I guess it is coming soon in KDE, I hope.

Re: No KDE support for TabletPC - ctrlv - 2003-08-01

http://www.lycoris.com/press/tablet.php

Re: No KDE support for TabletPC - NS - 2003-08-02

This is gnome! A big promo for lycoris. No real support. No WiFi support for the built-in wifi. I doubt xstroke even running on lycoris - (xstroke.org). Lycoris is very mediocre for linux user, probably good for MS user. Read this: http://www.osnews.com/story.php?news_id=3935

Re: No KDE support for TabletPC - David Comeau - 2004-08-20

I think the main thing is that for me (a Tablet PC user), is that KDE does not scale and orient itself correctly on the screen. X works correctly, but KDE is still thinking landscape.

Slackware packages - Troy Unrau - 2003-08-12

Anyone have any slackware 8.1 packages ready to go? I can't afford the downtime to upgrade to 9 for KDE 3.1x, and they changed glibc and gcc from 81 to 9. Anyway, if you do, email me or let me know at http://tblog.ath.cx/troy (PS: if anyone needs a place to host a blog, find me at the above address, I have room for many more :))

Re: Slackware packages - Anonymous - 2003-08-12

What's wrong with the packages linked on http://www.kde.org/info/3.1.3.php?