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.
Dot Categories:
Comments
Of course. That's what I did from the begining. :)
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
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.
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.
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.
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
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-so...
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 :)
THANKS!
You're doing a great service and I really appreciate it.
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.
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.
Wow. RedHat making KDE packages. I must remember to take my meds on time...
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.
See http://kde-redhat.sf.net/ for rh73-rh9 KDE RPMS.
Any ideas why?
Steinchen
Down for maintenance?
PS: What happened to the translations to Klingon and Latin?
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.
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.
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,
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!
Thanks, that has done the trick, don't know why I didn't try that myself.
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.
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.
> 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? ;-)
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
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
>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.
3: press ctrl+alt+esc and kill
I think you mean just CTRL+ESC.
unless of course you're thinking about NT.*... :-)
nevermind...
I was thinking SHIFT and not ALT...
Sorry...
[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?)
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.
"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
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
Do not feed the trolls.
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
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...)
>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
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.
>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
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
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
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.
> 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.
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?
> 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.
> "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?
because Swiss makes sense as a Helvetica ripoff and Swis doesn't ;-)
>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
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//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
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