Announcing KDE 3.2 Beta 1 "Rudi"
Monday, 3 November 2003 | Coolo
With the new year fast approaching, beta testing of the upcoming KDE 3.2 release has begun. The KDE Project is excited to announce the immediate availability of "Rudi", the first beta version of KDE 3.2. Sharing its name with the Kastle conference's host coordinator, Rudi represents the culmination of the KDE Project's efforts to date.
As no further features will be added between the release of Rudi and KDE 3.2, this is an excellent opportunity to preview the most advanced and powerful KDE yet. Packages may be downloaded from download.kde.org. As of this writing there are sources and binaries for SuSE and Conectiva, but other distributions will follow. The Konstruct build toolkit was updated.
With its 25 page feature plan, nearly 10,000 bugs closed and over 2,000 user wishes processed a complete report on what one can expect from Rudi would be so long that by the time you finished reading it, there would probably be a more current KDE release to try out. The only way to truly appreciate this release is to experience it first hand, but here are a few of the highlights anyways...
Read on in the full announcement.
Comments:
Rock on! - Eike Hein - 2003-11-03
I thought the announcement was written incredibly well - a nice overview :o). Now, excuse me while I hunt for the download ;-).
Re: Rock on! - Debian User - 2003-11-03
Hi, I can only second that. The announcement reads just "right". Congratulations to the KDE developers, rarely ever did I more look forward to a software than KDE 3.2 for the great many new features and consolidations. Yours, Kay
Re: Rock on! - Bob - 2003-11-03
Here here! A wonderful announcement very clearly written and with a nice presentation of facts. One minor quibble, though. The word "nor" is almost exclusively used after the word "neither." The release should use the word "or" instead.
Re: Rock on! - ed - 2003-11-03
Well, if we're quibbling you should write "hear hear" instead of "here here" ;-) ... a quick google gives a few links of proof:<p> <a href="http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=hear">hear</a> <p> <a href="http://www.parliament.the-stationery-office.co.uk/pa/cm199596/cmhansrd/vo950116/debtext/60116-32.htm">60116-32.htm</a> <p> I believe it comes from "hear him, hear him", used in the UK House of Commons.
Re: Rock on! - Bob - 2003-11-03
Very true! I realized my mistake shortly after posting it. I thought it would have made me too much of a grammar nut to correct my own posting about grammar. There's nothing funner than posting a response telling others to get smart and then screwing that up yourself :-)
Re: Rock on! - Melchior FRANZ - 2003-11-03
> I believe it comes from "hear him, hear him", used in the UK House of Commons. AFAIK it comes from the heralds who went through the towns with a drum to announce what the king/emperor had to say. (in German it's "Hoert, hoert!")
Re: Rock on! - Sean O'Dell - 2003-11-04
Actually, one uses "nor" in conjunction with "neither" and "or" in conjunction with "either." I believe the author was correct.
Rudi KNOPPIX would be great for testing - probono - 2003-11-03
A KNOPPIX version with Rudi would be great for testing - perhaps someone is already working on this? It would make sense for people who do not want to change their existing KDE installs but who would like to participate in the beta testing process.
Re: Rudi KNOPPIX would be great for testing - Eike Hein - 2003-11-03
I second that - and I'm pretty confident there will be a Rudi-Knoppix available in no time :).
Me too - Alex - 2003-11-04
I don't want to upgrade my 3.1.4, but I definitely want to preview and test 3.2b.
Re: Rudi KNOPPIX would be great for testing - jadrian - 2003-11-04
Yes I would definitly try it! This computer is used others to so I got to keep it stable, knoppix would be really great! I know some of my friends would be willing to try it too.
Very nice announcement.. - anon - 2003-11-03
well written.. no mention of programs:/ and settings:/ in konqi though, which are great =)
Re: Very nice announcement.. - cies - 2003-11-03
Maybe it's not too late to change it... (I kind of expected the authors name/e-adress on the end of the annoucement) This announcement will probably be revised/extended and than used for the final release.
Re: Very nice announcement.. - Anonymous - 2003-11-03
The announcement was written by Aaron Seigo (aseigo).
Re: Very nice announcement.. - Aaron J. Seigo - 2003-11-03
we had to leave _something_ for the final announcement piece, right? ;-) the beta1 article was over 2200 words in first draft form. this was eventually trimmed down to be in the low 1700s, and even that's a bit long IMHO for a beta release announcement. getting it down to "just" that big required picking what to mention this time around and what to leave out for this announcement; i think that says a lot about the significance of KDE 3.2. but have no fear, i'm sure the article for the 3.2 final release will be larger and more comprehensive.
I guessed right! - Alex - 2003-11-04
I knew it was you since I saw your name in a recent CVS Digest or Traffic where you asked KDE develoeprs to tell you about some important features tehy've added.
Re: Very nice announcement.. - Pedro Jurado Maqueda - 2003-11-05
Can you send me the article a few days before the release?. It's just for translate and publish in Spanish in our web page http://es.kde.org (KDE-Hispano). If you give me a few days more, maybe I can translate just at time for all KDE spanish speakers users. Thanks in advance. My e-mail is melenasIHATESPAM@kdehispano.org
programs:/ and settings:/ - tanghus - 2003-11-03
These protocols doesn't really do anything here, but as there are no programs in the K-menu and nothing in KControl I guess its a SuSE specific problem as mentioned in a thread below...
Beta - Sandro - 2003-11-03
Congratulations :o) i've downloaded KDE3.2 Beta, but after the installation there is no menu, nothing in the kcontrol-center and i can't open any directory on my desktop, does someone know what this is? i'm using SuSE 8.2
Re: Beta - MacBerry - 2003-11-03
Same problem here. Also SuSE 8.2. Seems the rpms are horribly broken.
Re: Beta - sam - 2003-11-03
I'm also affected from this Problems (SuSE 82). Kcontrol doesn't show any configuration-items, KMenu also seems to be broken. I hope this will be fixed ...
Re: Beta - ac - 2003-11-03
did you tried moving ~/.kde out of the way?
Re: Beta - star-flight - 2003-11-03
Same here (SuSE 9.0). I've downloaded from ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/people/adrian/KDE-CVS-BUILD/build.3.1.93_2003110113 a new kdelibs-/kdebase-package and it works :)
Re: Beta - Max Howell - 2003-11-03
I did this, but made no difference to me. I still have nothing in the control center. I don't know how the control center works so I've not a clue how to fix it. Otherwise things seem fairly bug-free, I've noticed some quirks. No doubt I'll be bugzilling tonight.
Re: Beta - Max Howell - 2003-11-03
I had to revert to 3.1.4 until the menus and panel are sorted. It's too soon since I installed SuSE 9 to not have various coolness. I run a cvs copy anyway so it's not too important.
Re: Beta - Jarl E. Gjessing - 2003-11-04
I also had to revert. All KControl items are listed under Applications. Fonts for the konsole is missing and lots, lots more.
Re: Beta - Sandro - 2003-11-04
Yes, i've tried to move .kde into another dir, but it doesn't work :-( it must be a bug with the SuSE-Version of the Beta, 'cause the Alpha II of KDE 3.2 worked fine...
Re: Beta - nicka - 2003-11-11
It's not just SuSE, I've built it from source using konstruct on Red Hat 9 and my kontrol panel is also empty!
Re: Beta - anon - 2003-11-11
It's known and fixed. Read the full thread and you will find solutions: http://dot.kde.org/1067849710/1067875849/ Especially the stuff in /etc/xdg/. I saw the bug report but I can't remember where. The solution is to make symlinks and/or copies from default_(*) to (*) in that directory.
Re: Beta - Dirk - 2003-11-03
That makes two of us. I don't know how to fix it. It's a pity :-(
Re: Beta - Tariq Firoz - 2003-11-04
same problem with mandrake 9.1, kde 3.2 alpha2 was fine ;-(, dunno what is the problem ?
Re: Beta - ac - 2003-11-04
Those bugs you call, are new features, don't you like them? ;)
Re: Beta - Nobody - 2003-11-04
Buahhahhah!!! :-D Cool features! Luckily Gentoo-versions work just fine... ;-)
Re: Beta - Sandro - 2003-11-04
Your Gentoo-Version works? but then You dont have the new features *hehe*
Re: Beta - Micha - 2003-11-04
The README tells you ... <br><br> <a href="ftp://ftp.de.kde.org/pub/kde/unstable/3.1.93/SuSE/README"> ftp://ftp.de.kde.org/pub/kde/unstable/3.1.93/SuSE/README</a>
Re: Beta - Sandro - 2003-11-04
Thank You! i've downloaded this file and now it works! Congratulations again and keep up the great work :o)
Re: Beta - Ben Roe - 2003-11-05
From 'rrh' on the gentoo forums, this should fix your problem: cd /usr/kde/3.2/etc/xdg/menus/ ln -s default_kde-settings.menu kde-settings.menu and then logout/login. Works for me using the gentoo ebuild, and your symptoms sound identical
Re: Beta - Andrey V. Panov - 2003-11-05
I have similar problem with KDE compiled from sources on Slackware-9.1. This command does not help.
Re: Beta - Andrey V. Panov - 2003-11-05
OK. The ~/.kde directory should be removed or new KDEHOME must be created.
Re: Beta - Eggert - 2003-11-05
No. I use a fresh new user dedicated to kde3.2-beta. The problem is still there. The symlink did not help either. Eggert
Re: Beta - Caleb Tennis - 2003-11-05
After making the sym-link, be sure to do a 'kbuildsycoca'
Re: Beta - Z - 2003-11-05
Worked for me. I'm running RH9 and built KDE3.2-beta1 using konstruct. Thanks!
Re: Beta - Eggert - 2003-11-06
Sorry, not for me. This is a SuSE 9.0 system, kde 3.2 beta1 built by Konstruct. Running kbuildsycoca (as root) produced a lot of messages like kbuildsycoca: WARNING: 'katepart.desktop' specifies undefined mimetype/servicetype 'text/x-c' kbuildsycoca: WARNING: 'katepart.desktop' specifies undefined mimetype/servicetype 'text/x-c++' kbuildsycoca: WARNING: 'katepart.desktop' specifies undefined mimetype/servicetype 'text/x-shellscript' Still, my Controllcenter only contains "Peripherals", "System", "Yast2".
Re: Beta - Z - 2003-11-09
Running it as root won't fix the control center for your regular user account. Try running the kbuildsycoca command as the regular user you are signed in as after you make the symlink as root. Good luck.
Re: Beta - Eggert - 2003-11-10
Ooops.. sometimes things are too simple. It works. Thank you.
Re: Beta - k18 - 2004-02-24
Excuse me!! Where i put the symlink?
Hmm... - TomL - 2003-11-05
If I remove ~/.kde, what happens to my addressbook, calendar, etc? I don't want to enter all that data twice!
Re: Hmm... - cm - 2003-11-10
You're right. In any case make a backup copy first. But: Backing up your valuable files regularly to an external medium (floppy, CVS, CD-R) is a good idea anyway.
Re: Hmm... - tizianoo portenier - 2003-11-28
it's ot important to remove da whole kdehome-directory (~/.kde) only the responsible files should be removed, e. g. to make kcontrol running, make the links discussed above and remove the file KDEHOME/share/config/kcontrolrc greetings
Re: Beta - Andrey V. Panov - 2003-11-05
OK. The ~/.kde directory should be removed or new KDEHOME must be created.
Re: Beta - luimarma - 2003-11-06
OK SuSe users, First install desktop-data-SuSE-8.2.99-61.noarch.rpm at the noarch directory. Second execute following commands as root: #cd /etc/xdg/menus/ #cp default_kde-information.menu information.menu #cp default_kde-information.menu information.menu.kde #cp default_kde-screensavers.menu screensavers.menu #cp default_kde-screensavers.menu screensavers.menu.kde #cp default_kde-settings.menu settings.menu #cp default_kde-settings.menu settings.menu.kde That works for me like charm. Luis
problems with konstruct - Ed Moyse - 2003-11-03
I've not been able to use konstruct for months now ... I've tried several times, and I always get errors with the mirror download.kde.org assigns to me. Does anyone know who I should write to about this? It's extremely frustrating! Connecting to download.kde.org[131.246.103.200]:80... connected. HTTP request sent, awaiting response... 302 Found Location: ftp://ftp.lip6.fr/pub/X11/kde/unstable/3.1.93/src/kdebase-3.1.93.tar.bz2 [following] --19:24:21-- ftp://ftp.lip6.fr/pub/X11/kde/unstable/3.1.93/src/kdebase-3.1.93.tar.bz2 => `download/kdebase-3.1.93.tar.bz2' Resolving ftp.lip6.fr... done. Connecting to ftp.lip6.fr[195.83.118.1]:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /pub/X11/kde/unstable/3.1.93/src ... No such directory `pub/X11/kde/unstable/3.1.93/src'.
Re: problems with konstruct - binner - 2003-11-03
I have uploaded a new version of Konstruct which reduces the number of files you have to change to enforce the download from a specific mirror to one file (kde.conf.mk). Those mirrors omitting unstable/ should probably be excluded from download.kde.org rotation.
Re: problems with konstruct - Jayenell - 2003-11-04
I have the same problem with the new konstruct. There's the eunet server from NL, that not have the unstable version yet. I think it should be easy for the konstruct-constructors, to make sure of a alt-server or maybe event two alt-servers. That must be a easy change. Cheers, J
Re: problems with konstruct - Stefan Heimers - 2003-11-04
When I tryed it, konstruct had the same problem. It sometimes tries different mirrors if you restart it, but it is boring to keep restarting it. How about having it retry different mirrors automatically in the case of a failure?
Re: problems with konstruct - binner - 2003-11-04
Just add more mirrors (or duplicate the download.kde.org entry) in kde.conf.mk.
easier way - TomL - 2003-11-04
I just run it this way for i in $(range 1 1000) do make install done range is a bash function I have.
Re: easier way - Bertie - 2003-11-04
> range is a bash function I have which presumably does the same thing as `seq 1 1000`, a unix command everyone (?) has....
You are right! - TomL - 2003-11-04
I guess I've had it for so long.
theorz - theorz - 2003-11-03
Wow! 10,000 bugs closed 2,000 user wishes processed 30 new applications This release is shaping up to be amazing.
Re: theorz - John Allsup - 2003-11-03
I'm not knocking the KDE people in any way, but... 1) 10,000 bugs closed means that there were at least 10,000 bugs to begin with. One should wonder about the methodologies at work in the software production: the thinking, the planning, the workflow, etc. You should ask if the process behind the software can be improved so that, without too much loss in development time, these bugs can be prevented _before_ they happen, not fixed after they happen. Software development is one area where prevention certainly is better than cure. (But cure is better than nothing at all, and <sick joke>nothing at all is better than M$...<duck/></sick joke>) 2) 2,000 user wishes processed doesn't indicate how well the needs of the user were thought about to begin with. You could increase this figure in the short term by brainstorming for user wishes in advance, plus a little asking around, and then not implementing the wishes until they land in the 'user wish' inbox, at which point you wheel the feature out and count it as another 'user wish' processed. 3) 30 new applications. What is/isn't an application? What do they do? Surely better KOffice (exceeding OOo everywhere), with a complete GIMP+Cinepaint equivalent (using the new KDE interface stuff... only 1 new application so far) and deeper framework inprovements would be better than the 'new application' count? Whether the release is shaping up to be amazing has nothing much to do with the numbers, rather it has everything to do with what those numbers are referring to. Numbers can, and routinely are massaged, fiddled, adjusted, corrected, and forced to lie under various forms of torturous duress. Don't listen to numbers alone. That, ladies and gentlement, concludes today's lecture.
Re: theorz - Hydralisk - 2003-11-03
A "bug" in Bugzilla is not the same as a bug anywhere else. Conservatively, more than half of those bugs were enhancements, feature requests, TODOS, or duplicates.
Re: theorz - Mojo_risin - 2003-11-03
"nearly 10,000 bugs closed" I think the intention is good but gives the impression of too many bugs... Like John said, is good to correct them but is better that they don't exist at all. Moura
Re: theorz - George Staikos - 2003-11-03
10000 bugs is only one bug for every ~400 lines of code. That's incredible in comparison to industry standards.
Re: theorz - katakombi - 2003-11-03
once, i used to write so many lines of comments as well! *looool* katakombi >8^)
Re: theorz - Datschge - 2003-11-04
It's actually even less per line of code since usually people compare all collected bugy reports to the current amount of lines, while they ignore the fact that a lot of rewrites/additions/removals predate the current number of lines. According to http://libresoft.dat.escet.urjc.es/cvsanal/kde-cvs/ the current amount of about 4 million lines has be reached through about 60 million lines (excluding websites and qt-copy) of added and rewritten code in the last 6 1/2 years.
Re: theorz - Chefren - 2003-11-04
It was 1 bug per 400 lines *fixed* bugs, not total bugs. Who knows how many bugs are still lurking in all those lines of code. For a mature project like KDE which does not have to worry about strict deadlines, I'd say it's just about normal.
Re: theorz - Tom - 2003-11-03
I think those numbers are simply interesting, in a strange sort of way. It just sounds impressive that 10,000 bugs have been processed; it gives an idea of the scale of the project. The announcement lists plenty of specific improvements and additions, and doubtless when 3.2 final comes out we will see several documents explaining it all in depth.
Re: theorz - a.c. - 2003-11-04
John, I am guessing that you are a PM? Yes?
Re: theorz - John Allsup - 2003-11-04
PM=? Prime minister? Nope.... that'd be a B*****d control freak called Tony. Pure Mathematician? Yes. (See e.g. my profile on slashdot.) I tend to share my pedantry with the mathematical logicians, which is understandable given my research area. (specifically, I'm a postgraduate student working in models of Peano Arithmetic.) Other PM? please advise. (I've given up guessing.) But yes: pure mathematics does tend to make you think about what numbers are, what they mean, and what they can also mean, given someone's intended meaning. (Undergraduate statistics books quite often have explanations of various scams that work effectively on the unwary...) John.
Bug count - Ingo Klöcker - 2003-11-04
I'm a pure mathematician, too. Furthermore I'm a KDE developer (KMail, to be precise), so I know exactly what those numbers mean with regard to KMail. We have loads of bug reports which are: - duplicates of already reported bugs (cf. http://bugs.kde.org/duplicates.cgi) - invalid, i.e. distribution specific bugs, user error, bugs in the libraries we use, etc. - not reproducible (so it's not clear whether there's really a bug) - missing features which are reported as bugs Some numbers (bug counts for kmail since 2003-01-28, the day KDE 3.1 was released): - total number of new bug reports (excluding wishes): 855 - total number of closed bug reports: 684 - closed as FIXED: 213 - closed as DUPLICATE: 170 - closed as WORKSFORME: 163 - closed as INVALID: 115 - closed as WONTFIX: 20 - closed as LATER: 3 - still open: 171 Some more numbers (bug counts for all of KDE since 2003-01-28): - total number of new bug reports (excluding wishes): 9788 - total number of closed bug reports: 6866 - closed as FIXED: 3052 - closed as DUPLICATE: 1267 - closed as WORKSFORME: 1304 - closed as INVALID: 984 - closed as WONTFIX: 218 - closed as other: 41 - still open: 2922
Re: Bug count - Aaron J. Seigo - 2003-11-04
great numbers... maybe we should enlist you to write the pure math version of the release announcements ;-)
Re: theorz - Derek Kite - 2003-11-04
The methodology goes as follows: Developer works on feature, fix, cleanup, whatever. Developer commits changes for review. Other developers or users test changes, either email bugs or submit bug report. Developer responds, fixes bugs. rinse... repeat. Sounds pretty good to me. Derek
Re: theorz - John Allsup - 2003-11-04
That's a very simplistic view. Where is the deep, large-scale thinking as to how everything goes together? Where is the end-user-pov thinking, looking not at particular features or whatever but on how they are going to use the UI as a whole to get done whatever they want to get done? Before you even get to the point of working on features, the large scale thinking lets you prioritise things so that the important features are well planned (rather than hacked up out of comparatively spur of the moment interest) and have far fewer bugs than average. Also, thinking about the workflow of the people doing the programming (this is a huge thing to think over in its entirety, and many books have been written on the various aspects of it,) what procedures allow the amount of debugging/correction to be reduced? Part of the problem of development is that, when it actually comes round to writing things, you have to do so a feature at a time (well, pretty much anyhow.) But thinking and planning things according to the features doesn't tend to produce the best results. Consider building a car, starting with the best tyres you can afford, and that really cool supercharger your mate has in his hot-hatch. If you go along that road, you'll be lucky to end up with something that even works. What you describe as the methodology is only really appropriate if you're working on an already planned out project, following the guide to what features are/aren't needed, where they go and what they do. It is only recently IMO (i.e. post GNOME 2 and KDE 3) that the two main competing OSS desktops (GNOME and KDE) have really started to come around to this kind of thinking and planning. John.
Re: theorz - Derek Kite - 2003-11-04
Interesting perspective. I think you underestimate the work involved in the few lines that I used to describe the process. There are two ways of going about this. One is to try to figure out the requirements, come up with an infrastructure design, hash out the implementation details for a few years, then start writing code from a spec. For a project like KDE, this is an impossibility. For one thing, how do you attract other developers except with working or almost working code? The second way it to write it. Find what doesn't work, throw it out, rewrite it. Repeat. 7 years later you have a mature and stable desktop, with few bugs. Actually, you have about 3 versions of a stable workable desktop. There are a few core developers that are still around, but many have come, contributed, then moved on. User interface stuff is details, getting basic functionality is the bulk of the work. A few months ago there was a lengthy discussion here about configuration, how complicated etc. it is. Someone banged out a 4 or 5 liner that produced a simple narrowly focussed configuration dialog, that worked. Literally. To say there isn't a good solidly designed infrastructure behind that is plain ignorance. That is one example. Khtml was written, the rewritten. Features, as in capabilities to view web pages built with unusual technology, are added to the basic engine. There is a design, a good design according to the apple people, that is extensible. Another example is the intercommunication mechanism. At one time KDE used CORBA, but it was found to be too slow and heavy for the purpose. So based on what they learned, they designed a new one, and wrote it in rather short order. I would say the second way comes up with better real world design. I work in a construction related industry, and know the value of design and specifications. But it is a very different industry dealing with very different constraints. First, you can't build, throw out and rebuild. Actually you can, but progress takes generations. Second, very seldom does anything new come along, I mean really new and unprecedented. Most technologies I deal with have been around since the 16th and 17th century, at least in someone's mind. The new stuff is new / faster / cheaper ways of doing the same thing. With software, this is not at all the case. Some of what the KDE folks have done is different than anything anybody else has done. It is truly new ground. How does one formally design that, other than writing it and seeing how it works? And throwing it away if it doesn't? Or letting someone else look at it to improve or trash it? Derek
Re: theorz - Datschge - 2003-11-04
Dear John, before you continue rambling about how software development should work in your opinion I'd like to make you aware that in the last 7 years KDE's development model transparently grew without any big break, without any kind of top down rules/rulers. Of course there *is* a development model as well as a grown community culture. For an introduction to those I suggest you to read http://www.kde.org/whatiskde/devmodel.php as well as the other related pages in that section. If after reading those you think we are doing it totally wrongly anyway I suggest you to look for other projects which fit better to you and may listen to your suggestions. Thank you. Respectfully, Datschge
Re: theorz - Aaron J. Seigo - 2003-11-04
well put Datschge! if something works really well and is a huge success, you shouldn't come along and say it doesn't work; if its churning out good product, efforts are better put to enhancing the mechanism rather than trying to turn the boat around for no reason at all.
Re: theorz - Tim Gollnik - 2003-11-06
So, you shouldn't work. Nature proves best that this IS a possible way. Sometimes it's better if someone comes along with a vision or so, i agree. But there ARE contributors with such visions. See how Bernd Gehrmann started with a new kdevelop (gideon), and now it's the one kdevelop none of us can wait for.. So where is the problem? Best wishes Tim
Re: theorz - James Richard Tyrer - 2003-11-07
I don't think that it works that way. AND, that is why it isn't working. But, perhaps I should see if my latest bug report *actually* is fixed in 3.2 before I go into this in detail. -- JRT
Re: theorz - Aaron J. Seigo - 2003-11-04
first off, that isn't 10,000 unique bugs but 10,000 bug reports. some of those were undoubtedly duplicates, some of those were against development versions that were never in production releases. however, many were against older versions. seeing as there's nearly 4 million LOC and people like to report every fiddly little bug they come across, i think that's not too bad at all. perhaps you like to show us your million+ LOC complex multi-program GUI project that's been over with a fine tooth comb by thousands as a comparison? with regard to user wishes, you are exactly right in that it doesn't say anything about the final outcome of those wishes. some were duplicates, some were denied. still, many were implemented. how many? i don't know for sure since i haven't counted them (anyone know how to get bugzilla to spit out such a report?). at the same time, it's almost irrelevant. what IS relevant is that these reports from users get read, considered and dealth with. that means there is a real user->developer communication going on. as for your "sand-bagging the user wishes" conspiracy theory, believe me when i say that those in the KDE project have better things to do with our time. honestly. most of us get our enjoyment from writing code, not dicking with statistics. you asked what is and isn't an application. here's a short list of new apps and components in 3.2: juk, devices applet (kicker), universal sidebar (kicker extension), khotkeys2, kdialog, ksplash(ml), kwallet, kmag, kmousetool, mouth, Konqi Mozila-like web sidebar, vimpart, plastik, Kig, KBruch, KGoldrunner, kopete, kontact, kcachegrind, umbrello, kgpg, kdelirc, kpdf, quanta's kommander, Kicker menubar applet, fsview, kcmrandr + systemtray tool, kcmuserinfo, kcmgamma, konq-plugins/auto-refresh, konq-plugins/crash, kuiviewer/ui thumbnails, kwifimanager, ksvg, a couple of new trivial ioslaves, libkcddb .... i'll bet i've even missed one or two in that list still. but remember, this is a beta announcement. wait for the final release announcement for more detailed coverage of the whole thing. and btw, KOffice has gotten better (though it isn't counted in the KDE Desktop release) and in some places does exceed OOo. look up the word "maturing". as for the GIMP+Cinepaint equiv you mention, hey, great, you've found a place KDE doesn't have a better app. to which i'd say where's Scribus, the K3B, KStars, or the KSVG? and just wait as apps like Kexi get into shape. i could go on, but i think you get the point, which is that both sides have holes in their application coverage. and without taking anything away from the great efforts made by the Gtk+/GNOME folks, i can confidently and honestly say that KDE is filling its application gaps at a terrific pace. you are also right that the KDE 3.2 release has everything to do with what the numbers are refering to rather than the numbers themselves. you seemed to question whether the numbers actually referred to anything, however; let me assure you they do. but most people don't have great attention spans, and most people don't like to read. knowing that, one of the things to remember when writing announcments and other such PR bits is that while one wants to offer substance, you can only offer so much before it becomes wasted, and even retrograde, effort. ergo the shorthand and trotting out, hopefully impressive, summary concepts and numbers. of course, if you show me factual errors in the piece, i'll be happy to correct them. as it is, i stand by everything in that article.
Re: theorz - Aaron J. Seigo - 2003-11-04
gah.. i really ought to Preview rather than just add ;-) when i said "to which i'd say where's Scribus, the K3B, KStars, or the KSVG?" i of course meant "to which i'd say where's the Scribus, K3B, KStars, or KSVG apps for Gtk+/GNOME?"
Re: theorz - Eric Laffoon - 2003-11-04
> as for the GIMP+Cinepaint equiv you mention, hey, great, you've found a place KDE doesn't have a better app. However it does appear that there is once again work on paint apps as well as Krita so these holes could become more a matter of choice of apps. Not having the Gimp's hideous UI for editing several files is such a big plus for me I'd live with less features. I mean when your picklist display is limited by your screen resolution and you can't find anything without the taskbar you're talking UI from hell. > i'll bet i've even missed one or two in that list still Yes, in the Quanta module there are kxsldbg and KFileReplace. KFileReplace is just included as a kpart plugin at this time but it shows up on konqueror toolbars and is the coolest multi file find and replace ever.
Re: theorz - Josep - 2003-11-04
> Yes, in the Quanta module there are kxsldbg and KFileReplace. KFileReplace is just included as a kpart plugin at this time but it shows up on konqueror toolbars and is the coolest multi file find and replace ever. Are there any way to remove the kfilereplace icon on the Konqueror toolbar, without removing the other two listview icons? Don't get me wrong I like it on Quanta.
Re: theorz - Andras Mantia - 2003-11-04
I don't know how can you do this. It seems that Konqueror puts every KPArt that handled inode/directory on the toolbar. Cervisia is also there if you have kdesdk installed. Ask it on kde-devel or some other mailing list and if nobody know you should fill a wish item for kdelibs or Konqueror. I'm not sure which one is the best. Andras
Re: theorz - Eric Laffoon - 2003-11-05
Yeah I was actually a little surprised to see this myself when I opened konqueror after installing it. Then again I'm not sure how I feel about Cervisia being there as I usually use the application or as a plugin in Quanta. My personal preference would be to complete the upgrades to the stand alone app for KFileReplace, but for now we will see what the options for the toolbar are at this time.
Re: theorz - Melchior FRANZ - 2003-11-04
> i'll bet i've even missed one or two in that list still Yes. I'm quite upset that you didn't mention kclock.kss! m. ;-)
Re: theorz - Aaron J. Seigo - 2003-11-04
/me quickly adds that to the list no. seriously. and the binary clock, speaking of clocks.
Re: theorz - anonon - 2003-11-05
> I'm quite upset that you didn't mention kclock.kss! Yes! It immediately became my default screensaver! :) I might have missed KDevelop3 in that list, which is the first official release of an app that has been in the making for years.
Re: theorz - Datschge - 2003-11-04
with regard to user wishes, you are exactly right in that it doesn't say anything about the final outcome of those wishes. some were duplicates, some were denied. still, many were implemented. how many? i don't know for sure since i haven't counted them (anyone know how to get bugzilla to spit out such a report?). ---- *cough* Coolo asked me to add statistic scripts like this in vein of like the existing "weekly summary" and "old bug" reports. I'm kinda late, but promise that I'll work on it.
Re: theorz - John Allsup - 2003-11-04
I'll give a long answer to this. It will probably produce more questions+retorts than answers, but here goes. I stated quite clearly at the start of my previous comment. I AM NOT KNOCKING KDE IN ANY WAY. I am not. (Not much anyway.) (You seem to be reacting as if I were.) The original point was intended to stress that the numbers (namely the 10000, 2000 and 30) aren't that important, and those that are impressed by the numbers should try not to be. Instinctively, when faced with things like '90% fat free' and 'and amazing 1000 combinations', one should ask what these numbers are talking about. Don't listen to the numbers all that hard. In the particular case of the numbers in the comment I replied to, it is certainly not the case that more=better. Neither is it the case that less=better. All that can be judged from the numbers is a rough amount of effort, and even then you need to be familiar with what the terms 'bug', 'user wish' and 'application' mean here. My response to the parent comment was mainly aimed at the 'Wow! look at the big numbers' aspect, it was certainly NOT aimed at the actual article. I read the article, was impressed by what KDE had achieved with the current pre-release, but saw someone spouting numbers and thought 'here we go again... I'll just throw something back at the statistics this time.' Maybe I was falling for a troll, but I don't think the original comment was one. > as for your "sand-bagging the user wishes" conspiracy theory, believe me > when i say that those in the KDE project have better things to do with our > time. honestly. most of us get our enjoyment from writing code, not dicking > with statistics. Did I suggest such a conspiracy theory? I apologise for doing so if I did: that was not the intention. (It was a knee-jerk reaction to yet more empty statistics.) The point about an artificial way of increasing the 'use wishes' count was intended as a reasonably direct counterpoint to the 'more the merrier' attitude to the numbers. Again, the numbers themselves don't say that much. Personally, I think it's better to say 'this, that, the other, and approx. x many other user wishes accounted for' rather than 'x user wishes accounted for.' This is more informative and places less emphasis on the numbers. As to the what is/isn't an application: The easy way to answer this question is: 'One pile of code with a name=one application.' I'll offer an alternative view, taking the list in your comment. In short, applications are things like Photoshop, GIMP, OpenOffice Writer, etc. Kicker, Konqueror, etc. are features of the environment (i.e. what you have before you run any applications.) A possibly controversial view, but I do not consider Konqueror to be an application, but an integral part of the underlying environment. Applets are applets: they are generally little gizmos that get something done, but are auxiliary to the main purpose at hand (whatever it is you are doing at your desktop.) Personally, I consider things like WinAmp and friends to be applets: you have them lying around making life a little easier, but you don't _work_ in them. You do work inside something like Quanta or KSpread. (If you are wondering where I'm coming from, this point of view starts from the dumb-user end of things, looks at what they are trying to accomplish, and thinks things from there.) Note that when I say 'framework', this is to be thought to be everything available (from KDE) to the developer as a tool to get the UI to do something for the user. Possibly 'environment infrastructure' would be a better term. * kwallet: should this be considered an application, or as an applet frontend to something (namely the functionality it provides) that should be and should be considered to be an integral part of the KDE framework. I have thought for a long time that authentication management should be intimately intertwined with a framework such as KDE's. My first meeting with it was when I saw the capability model of security (where there was fine grained, abstract authentication management, such that the authority to do something could be sent around in a controlled way.) Right now I think it's an application, but longer term it should not be. *juk: Again, this is an application. Much of the functionality it provides, however, should not lie in the application. Longer term, the ability to do things like keeping track of MP3's, forming playlists and such should be a feature of the underlying filesystem abstraction in the framework. I'll not elaborate on this very much here: I'll think this through a little better, read through the other stuff on storage frameworks + the obligatory how BeOS did it, and stick something in my blog. That said, much of what juk provides as an application should be a trivial thing to build on top of the underlying framework. It is not at the moment, and hopefully that will change in the future. *devices applet (kicker): clearly this is an applet. I consider applets not to be applications (and I consider many applications to be applets in disguise... my view: others may or may not share it.) *universal sidebar (kicker extension): As I see it, kicker is part of the environment, and this is an extension to it. (As you might guess by now, I do not consider plugins to be applications per se.) *khotkeys2, kdialog, ksplash(ml): part of the framework. *kmag: desktop gizmo. You do not do work within kmag: it's something to help you when working within some applications. *as for kmousetool, mouth, Konqi Mozilla-like web sidebar, vimpart, etc. you should get the picture. Of the things you listed, I consider Kig and Kbuch to be applications, though whether they should be amalgamated into a larger, more general 'KDE Maths Education Assistant' is another question. KGoldrunner is a game (not IMO an application.) I'll count Kopete as an application, but again it should really considered part of the underlying environment. Kontact is an application. Kcachegrind is certainly an application, as is umbrello. So far as new applications, according to my definition I count about 10 or 11 out of your list. (Again, I am not forcing this view on anyone, just offering an IMO important alternative view to what applications are and how to count them.) I like to view the application count as a rough indicator as to how much useful stuff there is for getting work done. (So 'three applications' means things like 'KWord, KSpread and Quanta', not things like 'Kicker, Konqueror and KWallet') The point is that the actual number of applications according to the 'pile-of-code+name=application' definition is not in itself an indicator of much except maybe effort. In many ways, if the same amount of stuff was done by fewer applications, and instead by enriching the framework, the result would be better (and possibly less confusing for the casual end user.) > KOffice has gotten better (though it isn't counted in the KDE Desktop release) > and in some places does exceed OOo. look up the word "maturing". I'm familiar with the word maturing. KOffice has come a long way, and has a long way to go. There isn't an office suite that doesn't. > as for the GIMP+Cinepaint equiv you mention, hey, great, you've found a place > KDE doesn't have a better app. And also a place where, if proper thought is given, KDE can do a better job (as an application.) Between GIMP and Cinepaint, they do a good job of managing the image data. Getting that image management/manipulation/high-performance-display aspect abstracted into an efficient 'engine' so that a nice KDE appliation can be written around it is probably the best way to do things from the KDE point of view. (I know little about the state of the art with GIMP's development, so I don't know how much or how little GIMP's image manipulation engine is coupled to the UI. Hopefully not that much.) >to which i'd say where's Scribus Technically a Qt application last time I looked. >K3B I agree that this looks good. > or the KSVG? An important and well needed part of the framework. > and just wait as apps like Kexi get into shape. The caveat is that, as with all 'just wait for' things, you don't know what you'll get, you don't know whether or not the developers will get bored/fall out/etc. There are, and have been many 'just wait for' things in the long history of free software that haven't come to anything. I sincerely hope Kexi is not one of those. Database frontends tend to be important and useful these days. > i could go on, but i think you get the point, So could I. I tend to enjoy a good, reasonably informed and heated discussion, with sufficiently different points of view that the talking doesn't just amount to 'preaching to the converted.' > which is that both sides have holes in their application coverage. You tend to suggest that there are two sides: surely there are <i>many</i> more (and many more even than that...) > ...by the Gtk+/GNOME folks I'm not here to start up a KDE vs. GNOME holy war. (Please don't think that that is my intention: it is not.) >I can confidently and honestly say that KDE is filling its application gaps > at a terrific pace. But 'filling application gaps' is not the be-all and end-all of producing a good UI environment. Surely it is better to do what you do very well at the expense of a few holes? > you are also right that the KDE 3.2 release has everything to do with what the > numbers are referring to rather than the numbers themselves. Yes. That was the main point. The rest was a surrounding discussion (which I thought better to include than a tired quote such as 'there are lies...statistics.') > you seemed to question whether the numbers actually referred to anything, > however; More accurately, I questioned how much meaning the numbers can actually have, giving a few examples as to how they can be misleading or inaccurate depending on how they are calculated and how people read them. Many replies gave further weight to the fact that they can be easily misread and misunderstood. This misunderstanding is why I tend to question the numbers and try to look straight past them. > let me assure you they do. But most people don't have great attention spans, > and most people don't like to read. Knowing that, one of the things to > remember when writing announcements and other such PR bits is that while one > wants to offer substance, you can only offer so much before it becomes wasted, > and even retrograde, effort. ergo the shorthand and trotting out, hopefully >impressive, summary concepts and numbers. That is a problem. It can be a big problem. Salesmen tend to love using numbers to confuse people for this very reason (they take the numbers and don't have the attention span, motivation or whatever-else to think things through.) I guess there's an art to writing announcements that are deliberately informative (and aim for the minimum confusion) just as there is a whole industry based around doing quite the opposite! Finally, I am not questioning any factual errors in the piece. I never was: I just don't consider the raw statistics to be very meaningful. John.
Konqueror is no application? - Ingo Klöcker - 2003-11-04
Konqueror is no application? But I guess Mozilla and Opera are. Where's the difference? Just because Konqueror is more integrated with the rest of KDE it doesn't count as application? Is KDE (whatever that is) an application? Anyway, as pure mathematician I won't dispute your definition for "application", even if you are pretty much alone with it.
Re: Konqueror is no application? - John Allsup - 2003-11-04
It's an iffy one. In its web browser mode, it quite possibly is. In its file manager mode, it should be considered as part of the underlying environment. It depends what you see as being built on what. Basically, if you chop the KDE things into those bits that are 'built in' or at least appear to be 'built in' and those that are not, which side of the fence does Konqueror fall on? (Note that I would say that M$IE appears to be a 'built in' part of the Windows user environment, ignoring the question of whether it actually is.) Would you consider Konqueror as being built in to KDE? I would, and for my mind that disqualifies it from being called an application. (Equally, I would not call M$IE an application, so much as part of the user environment, which being (at least so far as appearances are concerned) integrated into the Explorer, it very much is.) Any good desktop UI environment will have something that manages files and is considered part of the desktop environment. e.g. the Finder on MacOS, explorer on Windows, and the default file manager applications. People expect these things to just 'be there', and they are. For example, if you start with an empty KDE desktop and open a file window, do you consider yourself having opened any applications? In this context I would say no. The only bit that picks it out as an application is when it is used as a browser, but even then one would consider Konqueror to be KDE's built in browser. That said, I think the word 'application' is heavily overused. There needs to be a terms for many things, and whether you split things up based on technical definitions (e.g. a KDE application is a program involving a class that extends KApplication) or UI-point-of-view centric ideas (such as a KDE application is a program above and beyond the basic environment that is designed to do some kind of task.) Ok: this is not a good attempt at a qualitative definition, but you get the point. Think first about how someone who knows nothing about how everything is put together will think about it. That is the intuitive idea of what's what, and it makes a lot of sense to keep coming back to it when it comes to explaining things. (This will make things easier when it comes to getting inexperienced people into using KDE: the terminology will make far more 'intuitive' sense far earlier on, and subsequent discussion may be less confusing.) In any case, the point of view as I put it across was a little extreme in the 'this isn't an application' direction, but I thought it necessary to counterbalance the 'a kicker extension is an application' sort of thinking in the comment I was replying to. As to Mozilla and Opera: I would consider them applications. They tend to be all enclosing environments dedicated to a particular collection of tasks (i.e those involving using the internet.) I guess I'll have to think through my point of view of what's what, and try and put it down in writing. It does make a lot of sense, honest, it just requires a little unlearning. That said, part of it involves effectively having one set of definitions for the user point of view and another for the developer point of view. Setting things down in a way that avoids ambiguity is something I've yet to do. p.s. I also noticed why the 'Quality not quantity' title didn't appear--silly old me stuck it in the email box. Damn, I'm getting old. John.
Consider the 'naive' user's point of view - John Allsup - 2003-11-05
A slightly easier way of looking at my perspective on 'what is/isn't an application.' Consider a mac user who doesn't care about technical definitions or implementation deatils. (We'll assume that its an old one that still has something called a floppy drive.) [He sits down at his computer, the desktop is 'empty' except for the usual icons and stuff.] YOU: Do you have any applications open? USER: No. I haven't opened anything yet. [He sticks a floppy in with his work on and 'opens the floppy' by double clicking on the floppy icon.] YOU: Do you have any applications open? USER: No. I'm just getting around to that... I've got my work here, and I'm going to open it up in X (here X represents his favourite application, e.g. Word, Photoshop, Quark) YOU: But really, that folder window is an application: it's called the Finder. USER: Huh? Well, if you say so. But isn't it just my floppy disk with my files on? YOU try to explain the details to USER. USER gets confused. USER: Well, personally, I don't care. Applications are things that I open my documents in. Folder windows are, well, just folders. They're not application. [Another time, another user, this time you don't try to confuse them by explaining what the finder really is. He sits down at his computer, the desktop is 'empty' except for the usual icons and stuff.] YOU: Do you have any applications open? USER: No. I haven't opened anything yet. [He sticks a floppy in with his work on and 'opens the floppy' by double clicking on the floppy icon.] YOU: Do you have any applications open? USER: No. I'm just getting around to that... I've got my work here, and I'm going to open it up in X (here X represents his favourite application, e.g. Word, Photoshop, Quark) [USER double clicks on the Word document. Microsoft Word opens and the document is displayed on the screen.] YOU: Do you have any applications open now? USER: Yes, obviously (feeling patronised.) I've got Word out with my document, see. YOU: I see. [USER now double clicks the Excel spreadsheet. Microsoft Excel opens and the document is displayed on the screen.] YOU: So, which applications do you have open now? USER: Word and Excel. Note that the typical user will NOT consider things like the Finder to be an application. (And most Windows users didn't/don't realise that the taskbar, folder windows and now web browser are all part of the (Internet) Explorer 'application'.) Where the boundary gets a little iffy is things like Windows' integrated IE and KDE's integrated browser. Now consider the 'casual user' sitting down at KDE. Like the previous mac user, he/she does not care about technical details or implementation details, only getting his/her work done. [He sits down at his computer, the desktop is 'empty' except for the usual icons and stuff, including the KDE bar at the bottom.] YOU: Do you have any applications open? USER: No. I haven't opened anything yet. [He sticks a Zip disk in with his work on and 'opens the disk' by double clicking on the mount zip disk icon.] YOU: Do you have any applications open? USER: No. I'm just getting around to that... I've got my work here, and I'm going to open it up in X. (here X represents his favourite application, e.g. Word, Photoshop, Quark) YOU: But really, that folder window is an application: it's called Konquror: you can see its name on the title bar. USER: Huh? Well, if you say so. But isn't it just my zip disk with my files on? Why does it need to be called Konqueror: isn't just a window with my files in? YOU: Ok, I agree, it's just a file window. But see that address bar, try typing in the URL for a website in. USER: He types in 'www.google.com' and google appears. YOU: Now, do you have any applications open? USER: I'm not sure. It's sort of like a browser now. Is it an application now that it's a browser, or is this what you meant when you said it's an application before? It's an application that sort of disguises itself as the built in file manager when its not doing any web browsing. But if that's the case, where are the 'built in' folder windows? Are there any? YOU: (now also confused) Well, Konqueror sort of IS the built in file manager, but it's also the web browser application... USER: (still confused) I give up. Can I get on with my work now? You see how it goes. It makes a lot of sense to go back to the basic intuitive view of how people see and expect computers to work, document that and work with it rather than against it (whilst learning is important, making it that little bit more effortless to understand what's going on can surely help most users, whether technically minded or not). As such, there are two points of view: the 'enlightened' technical users' point of view, where they know what sort of programs need to be running in order for things to appear like an 'empty' intuitive desktop environment. There is also the view of the 'naive' user who just sits down and clicks on what they want, not being interested in how the computer really works, only that it does. They will see things differently. Personally, I think the 'naive' view is a better one in this case, since it is easier to get a good picture in your mind of what should be going on, without getting clouded by implementation details. (My view: others may not share it.) Thanks everybody for the discussion, I suspect this thread has long since passed the point of being labelled a 'troll fest' in everybody's minds, which was never the intention. John.
Re: Consider the 'naive' user's point of view - Datschge - 2003-11-07
You know your artifical case you build around Konqueror is actually exactly the same with Explorer under Windows. That being said you indirectly got a point, even though I'm very sure you aren't aware of that: the term 'application' and all related terms (take 'quit' for example) are way too abtract and technical for being included a usable desktop referring to metaphors. KDE already has been moving to a more task oriented (versus application centric) metaphor in the past, I'm sure this will continue and be intensified after the release KDE 3.2, hopefully also getting rid of the remaining inconsistencies. (The problem that commercial desktop will prefer application centrism due to marketing reasons will probable lead to KDE promotion 'incorrectly' keeping referring to 'applications' since this sadly is the only way branding really works nowadays. See http://www.newsforge.com/software/03/11/05/146225.shtml for a nice article about exactly this topic.)
Re: theorz - Datschge - 2003-11-04
You know you are splitting hairs here, way too many hairs actually. You talk about applications, applets and shells as if it makes a difference to the end user whether Konqueror is one of those. (Btw. Konqueror is technically a shell for the KPart framework, but I don't see any user caring about that.) Where this does matter is the development, being able to share as much code as possible allows developers to save time, stream line their applications, focus on their purposes, and all that while not having to reinvent every little wheel and even keep consistency with all other appplications in that desktop environment, that's the purpose K desktop environment exist for after all. You could come and say KDE has no single applications, it's all libraries and other shared stuff, and all applications users are using are actually only shells. And you know what, I actually think such a state would be the ideal case for KDE. And don't come with an excuse that your only point was showing that statistics are worthless, everyone knows that, but you still took the time to churn up a lot of arguments unrelated to that point.
Re: theorz - Aaron J. Seigo - 2003-11-04
> I like to view the application count as a rough indicator as to > how much useful stuff there is for getting work done. and then you discount 2/3rds of the useful stuff as not being applications, as if somehow that makes them less interesting because they are stand alone apps. i *could* be pedantic in my writing and label exactly what each thing is (apps / applets / kparts / libraries), but how would that be useful besides to make the announcements even longer (not a good thing ;). when i mentioned you should wait for the final release announcement for more details, i meant it. in particular your distinction between "underlying environment" and "application" is pretty irrelevant when trying to communicate the delta between this release and the last one to a general audience, which was the point of the announcement. you are correct that enriching the underlying environment can be a better option over stand alone apps, and as you noted many of the new items in 3.2 do exactly that (from KWallet to KHotKeys to libkcddb to....). i think what you say about emphasis on framework, results not just efforts, etc align with the technical reality that is KDE. but most people (e.g. the target audience for this article) don't have the technical background to understand those shades-of-grey(-but-important) differences. when i've got my writer's hat on, i try to write to a specific audience, and this time it isn't you or me, but the average KDE user =) imagine if KDE actually spoke to the masses in a language they understood and enjoyed.
Re: theorz - Eric Laffoon - 2003-11-05
I've always enjoyed your writing Aaron. However after a few talkbacks your responses start to look like a really long compile string. Reading this reminds me something... Didn't we get to be friends over an argument we had on the Dot? It's good not to be the only hot blooded guy in KDE. Keep up the good fight man. ;-)
Re: theorz - Aaron J. Seigo - 2003-11-05
haha.. yeah, i suck at talkbacks. my informal writing is usually way too verbose and expository of my internal modes of thought to be generally useful =) i also forget to use light-hearted words and phrases and come off sounding amazingly serious. video would be way better, as i'm a far better speaker than i am a conversational writer. btw, the new Quanta smokes... yum yum!
Re: theorz - Eric Laffoon - 2003-11-06
> haha.. yeah, i suck at talkbacks. my informal writing is usually way too verbose and ... Yeah man, whatever dude. ;-) Hey I really do love your writing though. I remember a Linux magazine article where I suddenly experienced a rush of excitement as I realized it wasn't just warmed over newbie fluff, but there were things I didn't know about KDE... Who was this guy... Aha! Nice work! > video would be way better, as i'm a far better speaker than i am a conversational writer. And in person would be even better as I'm trying to stay away from video beer. > btw, the new Quanta smokes... yum yum! Thanks! That's high praise indeed. Best of all we're just getting up a head of steam. I'm already dreaming about what 3.3/4.0 will look like. ;-)
Re: theorz - Debian User - 2003-11-04
Hi, let me compliment you for your obvious intelligence. It's a refreshing read. This is not ironic, but: You being a mathematican and probably even native English speaker is a good excuse for declaring applet and application two different things. It is in the style of people who love to be right. KDE is a framework. As such many of its apps are services as well as stand-alone applications. Your judgement by the GUI can be best demonstrated by asking you what Apache is. An applet or an application. Last time I thought of it, that was a application, but you are free to define as you like. For communication it's more practical to agree on definitions though. As to the numbers. Why do you imply that everybody is unaware of how the process of development of KDE works. Most people here know what bug reports are, what wishes mean and so on. Most people here are even part of the process. We enjoy the numbers, because we know what they mean. Your implication of absence of planning and design is insulting to those who did. The examples were listed. It's no doubt that e.g. Linux 0.1 was really really bad design. To some it seems now it has the best design of all. I assume you fail to understand how you need bad code to attract people willing to improve it. Development of software is a social process not a mathematical. Esp. with Free Software. It may be true that a lot of individual time is wasted. But that's only so to explore all possibilties. What you demand to happen has an example: GNU Hurd. It took many years to design and probably already next year, it may support virtual memory or filesystems larger than 1G. GNU Hurd is one of the best planned products and a complete failure compared to Linux that just happened to become nearly useful. Think about it and share your opinion with me. This bit about intelligence was really not ironic. :-) Yours, Kay
Re: theorz - Eric Laffoon - 2003-11-05
> I'll give a long answer to this. It will probably produce more questions+retorts than answers, but here goes. I have to give you credit there. Then again, it diminished the point doesn't it? ;-) > I stated quite clearly at the start of my previous comment. I AM NOT KNOCKING KDE IN ANY WAY. I am not. (Not much anyway.) And when producing the long answer it's good to be clear... sort of. ;-) > The original point was intended to stress that the numbers (namely the 10000, 2000 and 30) aren't that important, and those that are impressed by the numbers should try not to be. Instinctively, when faced with things like '90% fat free' and 'and amazing 1000 combinations', one should ask what these numbers are talking about. Don't listen to the numbers all that hard. So in simple terms we can reduce this to that point, agree and say "so what". As Aaron pointed out the alternative is to list the items, which with those numbers is inherently ridiculous. Now if this was being disseminated by corporate conglomerate "X" with intent to mislead and stick their hand in my pocket as opposed to stand up programmers looking for a way to summarize I think it would be a lot more valid. As it is I think one of my favorite programming phrases applies which says basically abstraction is knowing what you don't have to pay attention to. Some details are in fact counter productive. > Personally, I think it's better to say 'this, that, the other, and approx. x many other user wishes accounted for' rather than 'x user wishes accounted for.' This is more informative and places less emphasis on the numbers. Sure, and to be fair you mention them all or... you say how many there are after giving some example so that it gives the reader an idea of scope. Just because you can lie with statistics doesn't mean all statistics are lies. > I like to view the application count as a rough indicator as to how much useful stuff there is for getting work done. (So 'three applications' means things like 'KWord, KSpread and Quanta', not things like 'Kicker, Konqueror and KWallet') This is the second time you mentioned Quanta in your talkback. That gets you enough points with me that I now agree with everything you said. ;-) > Finally, I am not questioning any factual errors in the piece. I never was: I just don't consider the raw statistics to be very meaningful. Maybe it's a matter of personal taste. In my business endeavors I can think of few things that have been more useful to me in assessing and planning. Then again that's not the same as a release but maybe I'm geeky enough to to get a kick out of it.
screenies - ac - 2003-11-03
screenshots where?
Re: screenies - Rayiner Hashem - 2003-11-04
Try <a href="http://www.prism.gatech.edu/~gtg990h/kde_32_screenshots"> http://www.prism.gatech.edu/~gtg990h/kde_32_screenshots</a>
Re: screenies - Bart - 2003-11-05
Is it just me or has the Mac-like menu swallower at the top of some of the screenshots now an actual applet? So that I can add other buttons/applets to the same panel?
Re: screenies - Datschge - 2003-11-05
Yes, it's an applet now. And yes, it's cool. =o)
Re: screenies - anon - 2003-11-05
yup, that's the general idea =)
Re: screenies - Tim_F - 2003-11-09
Curious as to what font is being used there. It looks great, and I can never get my desktop to look quite that clean with the fonts. Any tips?
Kicker loses tray icons when crashing - Macolu - 2003-11-03
Does anybody know if bug 66371 has been corrected ? It's really annoying :-/ http://bugs.kde.org/show_bug.cgi?id=66371 Anyway, very good announcement !
Re: Kicker loses tray icons when crashing - Evan "JabberWokky" E. - 2003-11-03
Looks like there was a bug in the bug database. It's marked closed as a duplicate of another bug (which it is), which is itself marked closed as a duplicate of another bug. But that third bug does not seem to have anything to do with the systray bug that you're describing. It may have been fixed, may not have been. I'm not running CVS, or I'd check and reopen the bug if necessary. It looks like an accident, but may not be (that third bug *could* be the same).
Konstruct compilation problem? - Charlie - 2003-11-04
Anyone have any luck building it with Konstruct? It appears to be failing for me in libs/arts/work/arts-1.1.93/mcop (debug.cc, line 789). In file included from libmcop_la.all_cc.cc:35: debug.cc: In function `char *arts_strdup_vprintf (const char *, void *)': debug.cc:789: `vasprintf' undeclared (first use this function) debug.cc:789: (Each undeclared identifier is reported only once for each function it appears in.) asyncstream.h: At top level: debug.cc:491: warning: `gsize printf_string_upper_bound (const gchar *, int, void *)' defined but not used make[6]: *** [libmcop_la.all_cc.lo] Error 1 make[6]: Leaving directory `/scratch/kde-3.1.93/konstruct/libs/arts/work/arts-1.1.93/mcop' make[5]: *** [all-recursive] Error 1 It appears to be related to "HAS_VASPRINTF"... Any advice is greatly appreciated! Thanks, Charlie
Re: Konstruct compilation problem? - David Hiltz - 2003-11-04
Try this.. cd /scratch/kde-3.1.93/konstruct/libs/arts/work/arts-1.1.93 ./configure make install {go back to the meta/kde directory and continue on with 'make install'
Re: Konstruct compilation problem? - binner - 2003-11-04
This likely installs to a wrong prefix! Removing "--enable-final" from libs/arts/Makefile and calling "make garchive clean install" while being in the libs/arts/ directory is better.
WOhoO! - Alex - 2003-11-04
I am definittely looking forward to KDE 3.2 come early February! Great works! Also, my browser gives a 28 page printout when i look at the features guide =0
_Unwind_Resume_or_Rethrow@GCC_3.3 - Pedro Sam - 2003-11-04
I am consistently getting compilation errors from the gcc-3.3.x series compiler. Has anyone encountered this problem? p2sam-pc:~/software/src/konstruct/libs/arts/work/arts-1.1.93/soundserver$ make /bin/sh ../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -O2 -I/home/p2sam/software/kde3.2-beta1/include -I/usr/X11R6/include -L/home/p2sam/software/kde3.2-beta1/lib -L/usr/X11R6/lib -O2 -pipe -I/home/p2sam/software/kde3.2-beta1/include -I/usr/X11R6/include -L/home/p2sam/software/kde3.2-beta1/lib -L/usr/X11R6/lib -O2 -pipe -I/home/p2sam/software/kde3.2-beta1/include -I/usr/X11R6/include -L/home/p2sam/software/kde3.2-beta1/lib -L/usr/X11R6/lib -O2 -pipe -I/home/p2sam/software/kde3.2-beta1/include -I/usr/X11R6/include -L/home/p2sam/software/kde3.2-beta1/lib -L/usr/X11R6/lib -O2 -pipe -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -ftemplate-depth-99 -L/home/p2sam/software/kde3.2-beta1/lib -L/usr/X11R6/lib -L/home/p2sam/software/kde3.2-beta1/lib -L/usr/X11R6/lib -L/home/p2sam/software/kde3.2-beta1/lib -L/usr/X11R6/lib -L/home/p2sam/software/kde3.2-beta1/lib -L/usr/X11R6/lib -o artsd artsd.all_cc.o libsoundserver_idl.la ../flow/libartsflow.la ../mcop_mt/libmcop_mt.la /opt/gcc-3.3.2/lib/./libstdc++.so: undefined reference to `_Unwind_Resume_or_Rethrow@GCC_3.3' collect2: ld returned 1 exit status make: *** [artsd] Error 1 p2sam-pc:~/software/src/konstruct/libs/arts/work/arts-1.1.93/soundserver$
Re: _Unwind_Resume_or_Rethrow@GCC_3.3 - Jo - 2003-11-04
i had the same Problem (Ark linux) it comes from a bad gcc build/rpm (old library versions laying around or someting like that) just download the latest gcc version from http://www.gnu.org/software/gcc/gcc.html and do the usual stuff ./configure --prefix=/usr make bootstrap make install it worked for me and doesn't take long (compared to the complete kde build ;-)
Re: _Unwind_Resume_or_Rethrow@GCC_3.3 - Pedro Sam - 2003-11-04
ahh, thanks for the response. This problem had been plaguing me for months. Would you happen to know of a way to install both versions of gcc cleanly without blowing away the default system compiler? thanks, Pedro
Re: _Unwind_Resume_or_Rethrow@GCC_3.3 - Jo - 2003-11-04
you could us a different prefix for example /usr/local/gcc and then create some aliases to that location if you want to uses the new gcc. (alias gcc='/usr/local/gcc/bin/gcc' - don't forget the others g++, cc, etc.......) and you have to add /usr/local/gcc/lib to your /etc/ld.so.conf. but why would you want to do that ? if this error occurs your gcc suite is broken. the best would be to completely replace it with your own build - there won't be any binary incompatibilitys if that's your concern.
Great Read Aarom! - Alex - 2003-11-04
indepth, and well written, but I did find some small errors,s o maybe you can correct them later. "The only way to truly appreciate this release is to experience it first hand, but here are a few of the highlights anyways..." should be The only way to truly appreciate this release is to experience it first hand, but here are a few of the highlights anyway... Also, if KDE wants to get mroe donations and developers, which it definitely needs, it NEEDS TO BE MORE ASSERTIVE! KDE NEEDS BETTER WAYS TO ENCOURAGE PEOPLE TO DONATE! GNOME IS DOING AN OUTSTANDING JOB AT THIS AND WE SHOULD LEARN FROM THEM. I've filled a wishlist about many ways that KDE ould encourage its users to give back a little something. Please check it out and vote for it if you agree, this is a priority. http://bugs.kde.org/show_bug.cgi?id=63868
Re: Great Read Aarom! - Aaron J. Seigo - 2003-11-04
i agree with you that it would be an very worthy goal to have a fundraising drive with clear goals for KDE. that's a big job, however, and probably not the sort of thing that most of the people involved with KDE are very good at. i think that Open Source projects like KDE could learn quite a bit from organizations like NPR and PBS, but i also think we really need some fundraising savvy people who are personally invested (as in they want it to succeed) to spearhead such an effort. oh, and thanks for yours (and everyone else's) kind words re: the article.
Re: Great Read Aarom! - Waldo Bastian - 2003-11-04
To donate to KDE please visit <a href="http://www.kde.org/support.html">http://www.kde.org/support.html</a>
Waldo - Alex - 2003-11-05
SUSE is set to be acquired by Novell by January though a $210,000,000 deal as of course you already know since you work there. Does that mean SUSE will change its desktop preference, rewrite YAST in GTK, quit sponsoring KDE, switch everyoen to GNOME related technologies etc. If that happens than I have just lost my favourite distribution ;( I also think it would make more sense to keep SUSE the way it currently is, or they might screw it up as they have other things in the past when they tried to change it too radically. If everything becomes GNOME, not only is this uncompetitive environment goign to hurt Linux, but it will mean that ther ewon't be much difference between Redhat and SUSE and I definitely would not have any incentive to buy it anymore, but I do like 9.0 a lot, even though I think the real stellar releases will come in 2004 when linux 2.6, samba 3, KDE 3.2, KDevelop 3, OpenOffice.org 2, GIMP 1.4, GNOME 2.6, Xfree 4.4, etc. can all be incorporated. Any information on this, or has hell just begun?
Re: Waldo - Waldo Bastian - 2003-11-05
> Does that mean SUSE will change its desktop preference, rewrite YAST in GTK, > quit sponsoring KDE, switch everyoen to GNOME related technologies etc. There are no indications of that. Novell expressed in general terms that it very much likes what SUSE is doing and wants SUSE to continue in its current direction. Cheers, Waldo
God, I sure hope so! - Alex - 2003-11-06
if they install XD2 on it though, it will kill KDE I know because I've installed it and all my icons were not working, and KDE crashed everytime I went to the kicker and clicekd something, it was useless. It totally sabatoged my KDE.
Re: Great Read Aarom! - azza-bazoo - 2003-11-05
Methinks your spelling error-hunt was a bit too pedantic. After all, "anyways" is perfectly valid (well, depending on who you ask) as an informal spelling of that word. It's fairly common in normal speech, and this isn't exactly a formal environment ... Not that I don't like pedantry, but there's a time and a place -- like on b.k.o, to make sure that 3.2 really rocks!
standard theme? - L1 - 2003-11-04
does anyone know, if everaldos screenshot (http://www.kde-look.org/content/preview.php?file=8341-1.jpg) is just a mockup? this looks incredible. something right between m$ xp and mac osx. just better. if this is the way, kde 3.2 will look, i will switch. really, fantastic work!!!!
Re: standard theme? - Rayiner Hashem - 2003-11-04
Those icons look like Crystal SVG, but I can't tell what that widget style is.
Re: standard theme? - emmanuel - 2003-11-04
i think it's a mockup, the splitter is collapsable, which the QT with KDE 3.1 definitely can't do. i don't think it can do it now. or can it? :O)
Re: standard theme? - Datschge - 2003-11-04
It could be just "painted" onto the widget indicating that the splitter is movable without offering anything like a button (which is possible and would actually make sense to me). I thought it might be a style Conectiva (for whom Everaldo worked initially) is using. But just now I saw that rounded, non-dotted selection in the navigation panel, so I guess it's indeed a mockup. Oh well...
Re: standard theme? - kinema - 2003-11-04
AFAIK the theme/style of KDE 3.2 will not change. It has been decided that KDE can not drasticly change the way it look between every minor release. 4.0 will be the earliest that you will see a change. --adam
Excellent. - regeya - 2003-11-04
December 8th will mark the day I can completely stop relying on apps like Mozilla Firebird, Evolution, and others that are currently infesting ;-D my desktop. The Alphas were great, and it sounds like the beta is even more impressive. Here's hoping that 3.2 can release <i>before</i> schedule.
Re: Excellent. - John - 2003-11-04
I assume that you will not be viewing pictures with your web browser then? Konqueror is horribly slow and blocks KDE completely when loading a large picture... In fact this is practically the only reason I still have to use Mozilla... See the current discussion at the kfm-devel list. John
Re: Excellent. - Aaron J. Seigo - 2003-11-04
and see how they are working towards a solution on the kfm-devel list.
Re: Excellent. - john - 2003-11-04
But of course Aaron, this has always been the reason I love opensource!! Things might take awhile, but generally the direction is towards progress. This is why my wife now exclusively uses kde and konqueror for her studies. And why I do want to keep using it, also for photo sites. I guess I'm growing a bit impatient because this particular bug has always bugged me. BTW my 'reward' for fixing the bug (10 euro) still stands! Anybody want to join? And to let you see I mean it, my email adress is in the bug report. I'm the van Spaandonk John. Just don't want to post it in public. John
Please release in 2004!!!! - Mario - 2003-11-05
I want 3.2, to rock, and if it is released in 2003, than I think it will be rushed ther eis a lot to do before a final and there are still many many bugs which are pretty critical. Really, why does it matter if you relase in december or a month later? After all, 80% of the people won't even get it until march when their distro ships with it, no point in rushing. I would rather see a stellar release.
Re: Please release in 2004!!!! - Eric Laffoon - 2003-11-05
Are you running CVS? Do you have a basis in facts? Do you watch the commits and talk with the developers like the release manager? Once you put a person in the position of release manager you have to trust him. Coolo had the development schedule on hold to fix bugs for some time. This release is aready much longer than previous major point releases. Unless you can come up with something real you're just spreading FUD. If there needs to be a delay there will and if there doesn't there won't. If there is a delay it would be to 2004. Right now there is no delay planned.
Re: Please release in 2004!!!! - Aaron J. Seigo - 2003-11-05
yeah, the hard part of the release cycle is indeed coming: at what point is it good enough to be good enough? test the betas, provide quality factual feedback... that counts a LOT towards the project's decision making when it comes to judging releases ready.
here are the facts - Alex - 2003-11-07
Even after removing almost half of the planned features from the 3.2 feature plan, 25% of the features are still in the to do list. http://developer.kde.org/development-versions/kde-3.2-features.html To have these features be stable and well tested, i think December 8 is too early and I have heard other say the same thing. Anyway, this si an opinion, not a mathematical equation.
Re: here are the facts - Datschge - 2003-11-07
My suggestion: Stop reading paper, paper doesn't blush after all. Test the real thing before masking uninformed sounding comments. Thanks.
Re: Please release in 2004!!!! - ryan - 2003-11-19
for those with real distros like gentoo, we $emerge rsync $emerge -u world practically every week, so I'd like to see it soon (but not buggy)
Just switched from a old cvs version to 3.2b1.. - axe - 2003-11-04
Looks pretty solid. I'd have to say that kwallet is pretty annoying though. It should have a checkbox "don't ask me again"... pretty much, it should act just like Mozilla's PSM does.
questions questions - ac - 2003-11-04
Are the 'new sidebars' in KDevelop Qt or KDE widgets which every developer can now implement, or are they currently 'exclusive' hacks for KDevelop? Does anyone have screenshots of the new konqueror tabs? I never saw them and do not know how closing tabs will work in 3.2 thanks
answers, answers - Datschge - 2003-11-04
KDevelop (and Kate btw.) are using KMDI's IDEAl mode, which is available ("standardized") in KDE's core libraries now, see: http://developer.kde.org/documentation/library/cvs-api/kmdi/html/index.html The "new" Konqueror tabs don't look different at all, but now resize to fit into the width, show the tab title in other colors than black when loading and after finished loading but not viewed, each tab can be close by clicking on its little site icon, and optionally you can show buttons for creating new tabs and closing the current tab a la mozilla.
Re: answers, answers - cbcbcb - 2003-11-04
IMHO the new tabs are an absolute disaster. They change size and move about several times while the page loads, and the different colours just look a mess. Half the time the page title isn't there.
Re: answers, answers - anon - 2003-11-04
I absolutely agree. I am someone who uses Tabs and I'm surprised this hasn't been fixed.
Re: answers, answers - Aaron J. Seigo - 2003-11-04
not at all. right now the tabs show up prior to loading a page, are quite configurable, have visual feedback as to loading status (icon animation would be better than colours, though), support drag and drop, etc... compared to the tabs in 3.1 they are frieking brilliant. they still have room for improvement, such as the titles getting replaced sooner (right now it waits until the whole document is loaded, uck!), fewer repaints and perhaps some nicer loading feedback. but the improvement from "huh, we have tabs. so what." to "wow, these tabs are actually useful." is, at least for me, quite noticeable.
Re: answers, answers - Hamish Rodda - 2003-11-05
I believe you need to have a patched qt-copy to see tabs in their full flicker-free glory... eg. http://webcvs.kde.org/cgi-bin/cvsweb.cgi/qt-copy/patches/0013-qtabwidget-less_flicker.patch?sortby=date#dirlist
Something is rotten in the state of SuSERPM. :-) - arcade - 2003-11-04
Okay, probably just me, but according to the README, it should work with an rpm -Fvh *rpm Here's my output: error: Failed dependencies: libartsbuilder.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsgui.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsgui_idl.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsgui_kde.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsmidi_idl.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsmodules.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsmodulescommon.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsmoduleseffects.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsmodulesmixers.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsmodulessynth.so.0 is needed by kdeaddons3-sound-3.1.93-0 libartsbuilder.so.0 is needed by kdemultimedia3-3.1.93-0 libartsgui.so.0 is needed by kdemultimedia3-3.1.93-0 libartsgui_idl.so.0 is needed by kdemultimedia3-3.1.93-0 libartsgui_kde.so.0 is needed by kdemultimedia3-3.1.93-0 libartsmidi_idl.so.0 is needed by kdemultimedia3-3.1.93-0 libartsmodules.so.0 is needed by kdemultimedia3-3.1.93-0 libartsmodulescommon.so.0 is needed by kdemultimedia3-3.1.93-0 libartsmoduleseffects.so.0 is needed by kdemultimedia3-3.1.93-0 libartsmodulesmixers.so.0 is needed by kdemultimedia3-3.1.93-0 libartsmodulessynth.so.0 is needed by kdemultimedia3-3.1.93-0 libartsbuilder.so.0 is needed by kdemultimedia3-video-3.1.93-0 libartsgui.so.0 is needed by kdemultimedia3-video-3.1.93-0 libartsgui_idl.so.0 is needed by kdemultimedia3-video-3.1.93-0 libartsgui_kde.so.0 is needed by kdemultimedia3-video-3.1.93-0 libartsmidi_idl.so.0 is needed by kdemultimedia3-video-3.1.93-0 libartsmodules.so.0 is needed by kdemultimedia3-video-3.1.93-0 libartsmodulescommon.so.0 is needed by kdemultimedia3-video-3.1.93-0 libartsmoduleseffects.so.0 is needed by kdemultimedia3-video-3.1.93-0 libartsmodulesmixers.so.0 is needed by kdemultimedia3-video-3.1.93-0 libartsmodulessynth.so.0 is needed by kdemultimedia3-video-3.1.93-0 libgnokii.so.1 is needed by kdepim3-3.1.93-0 libvcard.so.0 is needed by (installed) kbarcode-1.4.1-53 libvcard.so.0 is needed by (installed) myldapklient-0.6.6-143 libvcard.so.0 is needed by (installed) quanta-3.1.4-29 libvcard.so.0 is needed by (installed) synce-kde-0.6-48 libvcard.so.0 is needed by (installed) koffice-extra-1.2.92-60 libvcard.so.0 is needed by (installed) koffice-illustration-1.2.92-60 libvcard.so.0 is needed by (installed) koffice-presentation-1.2.92-60 libvcard.so.0 is needed by (installed) koffice-spreadsheet-1.2.92-60 libvcard.so.0 is needed by (installed) koffice-wordprocessing-1.2.92-60 libvcard.so.0 is needed by (installed) koffice-1.2.92-67 libartsbuilder.so.0 is needed by (installed) brahms-1.02-794 libartsgui_idl.so.0 is needed by (installed) brahms-1.02-794 libartsgui_kde.so.0 is needed by (installed) brahms-1.02-794 libartsmidi.so.0 is needed by (installed) brahms-1.02-794 libartsmidi_idl.so.0 is needed by (installed) brahms-1.02-794 libartsmodules.so.0 is needed by (installed) brahms-1.02-794 On a quite vanilly SuSE 9.0 installation, btw.
Re: Something is rotten in the state of SuSERPM. :-) - standsolid - 2003-11-04
it looks like you need to insatll the libarts package before all teh KDE packages.
Re: Something is rotten in the state of SuSERPM. :-) - Peter Wiersig - 2003-11-11
Try '-Uhv', because new rpms might be added by an upgrade, which were not installed by the previous Release.
Re: Something is rotten in the state of SuSERPM. :-) - asterix - 2004-02-01
I have got the same problem. Installing the KDE 3.2 RC Packages on SuSE 9.0 Professional (especially kdemultimedia3-sound.rpm) brings a dependency failure because of the libarts modules.... Have you got any solution? Regards Asterix
Re: Something is rotten in the state of SuSERPM. : - Philipp - 2004-02-22
Had the same problems. I downloaded kdemultimedia3-common-3.2......rpm and noatun-3.2.0....rpm. (both not from SuSE ??) This solved my dependencies problem but now i have another problem: I can´t play any sound Any suggestions? philipp
I hope I can view images with Konqy in 3.2 - John - 2003-11-04
Because right now it's too slow to be usefull.... See [Bug 39693] loading images blocks konqueror From the bug report: [...] I made a 6000x6000 jpeg with GIMP that was filled completely black with a few lines drawn in the middle (~750k). gqview took 3 seconds to load it - using /tmp/test.jpg xv took 4 seconds to load it - using /tmp/test.jpg kuickshow took 7 seconds to load it - using /tmp/test.jpg konq-HEAD took 24 seconds to load it - using /tmp/test.jpg konq-HEAD took 49 seconds to load it - using http://localhost/test.jpg MozillaFirebird took 4 seconds to load it - using /tmp/test.jpg MozillaFirebird took 5 seconds to load it - using http://localhost/test.jpg opera 6.12 took 3 seconds to load it - using /tmp/test.jpg opera 6.12 took 3 seconds to load it - using http://localhost/test.jpg [...] Let's all vote for this one people! For my part, I offer ten euros (in an envelope, including a nice card) to the guy who fixes it! John
Re: I hope I can view images with Konqy in 3.2 - anon - 2003-11-04
See http://lists.kde.org/?t=106773453700001&r=1&w=2 It apparently has to do with Konq's progressive image loading code and fast(er) connections
Debian packages for woody? - Debian User - 2003-11-04
As a translator for kde I need to try the work done before final release. As a Debian User I need packages to install because konstruct report problems (after a daily "cvs -l update"). Someone can help me?
Re: Debian packages for woody? - cies - 2003-11-04
use orths kdecvs .deb's, see: "ggl: orth kdecvs" there great!
Superb - a revolutionary KDE release... - Ruediger Knoerig - 2003-11-04
with my nickname! I'm famous!!!!
Apple's impovements? - Manux - 2003-11-04
What about Apple improvements? I cannot see any information about any KDE3.2 improvements "promised" by Apple some months ago. Manux
Re: Apple's impovements? - anon - 2003-11-04
Many changes have already Replybeen merged. Some have not been.
OT: SuSE baught by Novell - Thomas - 2003-11-04
no joke http://www.novell.com/news/press/archive/2003/11/pr03069.html with SuSE as a big supporter of KDE now being merged into Novell. Does this affect KDE? I'm still not quite sure what to think of it... Novell baught Ximian which is clearly focused on gnome... SuSE will have to drop support for KDE to concentrate on the server (My guess is it's Ximian for the desktop and SuSE for the server)
Re: OT: SuSE baught by Novell - Waldo Bastian - 2003-11-04
This was actually the first question that was asked after the merger was announced to the SUSE personnel. The response was along the lines that Novell and its customers value choice and that there is demand from the market for both solutions. It will certainly be interesting to see how things will work out in practice. For me personally I think this will offer a great opportunity to work closer with Ximian and GNOME via for example the FreeDesktop.org initiative to provide better integration of technologies from the two different desktops so that we can present independant software developers with a unified set of standards for the Linux desktop. Cheers, Waldo SUSE/Novell
Re: OT: SuSE baught by Novell - Thomas - 2003-11-04
So it's good news after all... I'd be delighted to see something like the red carpet technology delivering the newest and freshest KDE ;) to the enterprise desktop. (I'll still be able to use konstruct at home...)
Re: OT: SuSE baught by Novell - jmk - 2003-11-04
> So it's good news after all... Let's not swallow just yet. This is what always gets said, and then all of a sudden, track two is discarded in silence.
What they bought Ximian for... - The Badger - 2003-11-05
If I were a GNOME advocate, I'd be more worried that Novell really bought Ximian for the Red Carpet stuff (noting that many of their "big wins" seemed to be Red Carpet roll-outs) and bought SuSE for the KDE desktop expertise. However, this gives both camps a real opportunity to work together and integrate the desktops in a more sophisticated way than Red Hat managed to do.
Re: OT: SuSE baught by Novell - Navindra Umanee - 2003-11-04
Hmmm, that doesn't sound like much of a reply from Novell. Btw, didn't the company used to be called SuSE? Why is it now SUSE all of a sudden?
Re: OT: SuSE baught by Novell - Datschge - 2003-11-04
Well, SuSE is/was a German acronym (Gesellschaft für *S*oftware- *u*nd *S*ystem-*E*ntwicklung mbH) nearly noone even in Germany really understood while Suse is a nice femal name and SUSE all in caps makes it look really important, so Novell noticed them finally. Other than that I've no idea. =P PS: I however do like their new chameleon better than the old one.
Re: OT: SuSE baught by Novell - Roberto Alsina - 2003-11-05
Do germans really use words like "Gesellschaft" and "Entwicklung mbH"? Man, if I were german, I would have to untie my tongue every noght before going to bed :-)
Re: OT: SuSE baught by Novell - ac - 2003-11-05
You don't want to say that these words are long, right? Because they aren't ;) And BTW, "mbH" is not a word but an abreviation for "mit beschraenkter Haftung" (with limited liability).
Re: OT: SuSE baught by Novell - Roberto Alsina - 2003-11-05
It's not a matter of length, but of low vowel density :-) For example, the spanish equivalent of mbH would be "de responsabilidad limitada". it's actually longer (25 letters vs 22, and each one has to be pronounced ;-)
Re: OT: SuSE baught by Novell - ac - 2003-11-07
"It's not a matter of length, but of low vowel density :-)" Ah, ok. But it looks a bit worse than it actually is, because, for example "sch" is only one sound (like the "sh" in english "shoe"), same goes for the "ll" before it, and "ck" is also only a special kind of "k". ;) "...and each one has to be pronounced" I guess that's the difference ;)
Re: OT: SuSE baught by Novell - Thomas - 2003-11-05
> Man, if I were german, I would have to untie my tongue every noght before going to bed Well, yes, that's exactly what we're doing over here. It might be a bit uncomfortable to untie your tongue every evening but ýou get used to it ;-)
Re: OT: SuSE baught by Novell - Waldo Bastian - 2003-11-05
> Why is it now SUSE all of a sudden? <br><br> It's part of the new branding that was introduced a few weeks ago. We also have shiny new pictures on the <a href="http://www.suse.com">website</a>.
Re: OT: SuSE baught by Novell - Roberto J. Dohnert - 2003-11-04
Im going to be very blunt and very honest in my feelings here. I think this whole deal is bullshit. SUSE should never have even considered selling to Novell. SUSE was my main desktop and Linux distro since version 6.4 anytime I ever developed anything for Linux I made sure it was SuSE compliant. Now, you expect me to get googoo eyed over having to more and likely change my GUI tools and learn GTK. GTK sucks KDE and QT are the best, asking Novell, a GNOME company, to sell KDE is like asking Ford to sell a Toyota car off of their lot. Its not going to happen. But i of course being as faithful as I am to SuSE will stay and see whats happening, if everything backfires and starts to go south i will then go back to Windows I guess. If Novell pulls the retail box sets of SUSE Linux, I will be going with Windows because I like having a box with manuals, screw that download ISO off the web and burn it crap. Thats for the dogs.
Re: OT: SuSE baught by Novell - anon - 2003-11-04
Who said that Novell was a GNOME company? Novell was in talks to buy SuSE a while before they bought Ximian. Their initial offers were quite low ($140 million), and as such, were rejected by SuSE. With the help of IBM, and their $50 million investment in Novell, they were able to finally buy SuSE for $210 mill, who they obviously desperatly wanted. If Novell had succeded in buying SuSE _before_ they bought Ximian, people would be sitting on news.gnome.org talking about Novell is going to pull the plug on Ximian's GNOME support and the world was going to be blown apart and such. Guess what, they're wrong too.
Re: OT: SuSE baught by Novell - Roberto J. Dohnert - 2003-11-04
<< Who said that Novell was a GNOME company? >> Novell owns Xiamian, a GNOME company << people would be sitting on news.gnome.org talking about Novell is going to pull the plug on Ximian's GNOME support and the world was going to be blown apart and such. Guess what, they're wrong too. >> Kind of brings up the old question. Is the enemy of my enemy my friend? or my enemy? I dont trust Novell and I say this the letters N-O-V-E-L-L spell D-O-O-M for KDE and SUSE
missed my point COMPLETELY - anon - 2003-11-04
> Novell owns Xiamian, a GNOME company So, now that they own SuSE, they are now a KDE company too? Erm, you missed my point COMPLETELY. My point is that Novell was actually trying to buy SuSE _first_, before Ximian, but couldn't do so because of market conditions. They aren't tied to KDE nor GNOME, and aren't a KDE nor GNOME company. They own subsidiaries that certainly are though.
Re: OT: SuSE baught by Novell - anon2 - 2003-11-04
Mod's note: I'm deleting all these trolls with extreme prejudice, given that they are from the wiggle troll. Someone I have already warned and effectively banned. -N. <!-- "integration" -- fine, as long as it doesn't involve Qt and its odious licensing quagmire finding its way into GNOME... and the legendary KDE bloat and slowness stays firmly on its own side of the fence. -->
Re: OT: SuSE baught by Novell - Thomas - 2003-11-05
hm... ;) don't know why, but your comment made me smile somehow. Well, I guess it's simply my elitist arrogance...
Re: OT: SuSE baught by Novell - anon2 - 2003-11-05
Mod's note: I'm deleting all these trolls with extreme prejudice, given that they are from the wiggle troll. Someone I have already warned and effectively banned. -N. <!-- More likely your staggering lack of knowledge and foresight. -->
Re: OT: SuSE baught by Novell - anon2 - 2003-11-05
Mod's note: baleeted! <!-- You have got ot be the worst system administrator I've ever seen. Not only you do you ban, indiscriminately, anyone you disagree with -- but you can't even lie well. 1. You have never warned me. 2. What's a wiggle troll. 3. You have never banned me, effectively or not. 4. If you are going to delete something, then delete the thread. Leaving the replies is, at best intellectually dishonest. 5. I did not engage in flaming or abuse (that was all directed my way). I simply took some facts from the Novell Purchases and drew some logical conclusions which are not favourable to KDE. Apparently, this is a banning offense. -->
Re: OT: SuSE baught by Novell - jmk - 2003-11-05
> It will certainly be interesting to see how things will work out in practice. For me personally I > think this will offer a great opportunity to work closer with Ximian and GNOME via for example > the FreeDesktop.org As a longtime KDE and SuSE user I truly hope that this will be possible. However, as a corporate junkie myself, i don't think any large corporation at times like this will include two units one way or the other competing with each other. In the long run, other one will be ditched. It's just a matter of choosing which one. There's no-one surely saying either way, but if it was KDE that got selected to be number one priority, ximian purchase wouldn't still be void - just a trick to 'buy out' competition.
Re: OT: SuSE baught by Novell - Debian User - 2003-11-05
Hi, I am convinced that Novell doesn't care that much for the desktop at this point. SUSE was in my opinion picked for the Server applications that have come out of SUSE lately. I hope that more SUSE work will now focus on integration of LDAP-everything-server-world into a KDE worthy and integrated Free Software (not Yast licence if we dare hope so) frontend. It will be interesting to see wether Yast will remain non-free. Yast is still unique, nothing from Redhat (or anybody I am aware of) comes even close. I hope Novell shall release Yast as Free Software to push GNU/Linux as a whole over competing systems. If I were Novell, I would take Ximian Connector and integrate it into Kontact. That would be a great thing too. Yours, Kay
Re: OT: SuSE baught by Novell - anon - 2003-11-04
Don't be so sure. From /.: I have recently listened to some talks inside the GNOME Irc channel where I heard some Ximian employees mentioning that Novell told them to work on KDE stuff now. From the internals of Novell it sounds like their employees are more interested to work with KDE rather than GNOME because that employee listed a long list of complaints that the Novell people raised which they found in GNOME to be totally out of use. ---------------- Don't forget that many buy SuSE /for/ KDE. Novell would be silly not to recognize that.
Re: OT: SuSE baught by Novell - Anonymous - 2003-11-04
That would make sense, because when you want to beat RedHat in U.S. you have to make something different - like using another desktop environment.
Re: OT: SuSE baught by Novell - Datschge - 2003-11-04
Red Hat never offered a product targeted to the home desktop computer, they're getting rid of their entry level server distribution right now. And using a different *desktop* environment on a *server* product doesn't sound like something which would achieve more market shares.
Re: OT: SuSE baught by Novell - Ian Monroe - 2003-11-04
Your forgetting about the server admins who need a desktop environment to run a server. But your right, most folks don't really care.
Re: OT: SuSE baught by Novell - anon2 - 2003-11-04
Mod's note: I'm deleting all these trolls with extreme prejudice, given that they are from the wiggle troll. Someone I have already warned and effectively banned. -N. <!-- Nonsense. That simple fact is that Novell is already sending Ximian employees out to train Novell developers in GTK/GNOME -- you need only read the GNOME developers blogs to see this, and its also been published (see website in other message). GNOME will be the Novell desktop, and KDE is out in the cold with no corporate support other than Trolltech's pals and SCO. -->
Re: OT: SuSE baught by Novell - anon - 2003-11-04
novell employees==outsourced indian contracters in bangalore.. I remember when Sun did the same thing with wipro. The more this happens the better for kde actually ;) Novell's strategy looks like using a KDE-based desktop (SuSE Linux) and GNOME-based tools (Evolution, mono) to create a nice balance =) Of the two companies, though, Novell's investment in SuSE is much larger than their investment in Ximian-- remember that Ximian is still a pretty small company compared to SuSE (about 1/4th-1/5th the size) Their "desktop" is neither GNOME nor KDE, but solutions based on both. That's where the money is. Capitalism talks, zealotry and old UNIX-style flame wars don't.
Re: OT: SuSE baught by Novell - anon2 - 2003-11-05
Mod's note: I'm deleting all these trolls with extreme prejudice, given that they are from the wiggle troll. Someone I have already warned and effectively banned. -N. <!-- *Novell's strategy looks like using a KDE-based desktop (SuSE Linux) SuSE's desktop has always been the weakest part of its distro. * and GNOME-based tools (Evolution, mono) to create a nice balance =) If you use Evolution, you use GNOME. Fact. Evolution touches every single part of the GNOME desktop, with the exception of the panel. It was the biggest driving force behind the design and development of GNOME 2.x. For Novell to run the KDE desktop with Evolution was would be the height of idiocy. There's not one single reason to go with KDE (for those whose minds are not clouded with zealotry)... it costs a fortune to develop with (thanks TrollTech), is exceedingly bloated, and it's slow to load without bandaging it up with hacks. And besides, all the best apps run under GNOME, not KDE, and GNOME has far better i18n and (most important of all) accessiblity. Frankly, it's no contest as far as corporate desktops are concerned. -->
Re: OT: SuSE baught by Novell - Thomas - 2003-11-05
> Evolution touches every single part of the GNOME desktop, with the exception of > the panel. It was the biggest driving force behind the design and development of > GNOME 2.x ? Don't think, any gnome developer needs to post on the dot as "anon2" just to make statements like that... plz spare us further interpretations of "driving forces" behind gnome or kde...
Re: OT: SuSE baught by Novell - anon2 - 2003-11-05
Mod's note: I'm deleting all these trolls with extreme prejudice, given that they are from the wiggle troll. Someone I have already warned and effectively banned. -N. <!-- * Don't think, any gnome developer needs to post on the dot as "anon2" just to make statements like that... plz spare us further interpretations of "driving forces" behind gnome or kde.. Don't believe me then! You can always go and check the GNOME mail archives. Evolution uses virtually every part of GNOME and GTK (including many custom widgets) -- it was designed that way, and was a testbed for much of the technology that debuted in GNOME 1.4 and reached maturity in GNOME 2.x -- it's extensively bonoboised for a start. It is simply ridiculous to think that Novell would install KDE to use for a few panels and then GNOME to use for apps like Evolution (and don't kid yourself, Evo was one of the prizes that Novell went after Ximian for. KMail is simply not up to the job in the corporate world), especially when you consider that GNOME is far superior in the basics of a desktop (such as 18n and a10y). If you had even the slightest understanding of software development (beyond a 3 line hello world KDE window and widget that you think makes you so l33t), you would understand this. Face it zealot, SuSE is now GNOMEed, and KDE has lost its biggest distro. -->
Re: OT: SuSE baught by Novell - Datschge - 2003-11-05
Your sheer stunning technical knowledge makes me afraid already... ...afraid, that you don't know what you are talking about. =P Help out 'your' community instead wasting everyone's and your own time with this kind of repetitive child's plays.
Re: OT: SuSE baught by Novell - anon2 - 2003-11-05
Mod's note: I'm deleting all these trolls with extreme prejudice, given that they are from the wiggle troll. Someone I have already warned and effectively banned. -N. <!-- Point out where I'm wrong, or crawl back into your zealot-hole. I do realise that hardcore fanatics, like the ones native to dot.kde.org, are rarely able to see the truth... but some of you *must* be able to see the ramifications of the SuSE purchase? It's not hard... all you need is a basic understanding of the real world, a bit of clear thinking and some basic understanding of software development. Oh... what am I saying... this is dot.kde.org after all! -->
Re: OT: SuSE baught by Novell - Datschge - 2003-11-05
You are at the wrong place, this is not a Gnome news site so everything you were writing here so far is simply irrelevant. Regarding the SUSE purchase everything we heard so far is that SUSE will keep its brand, keep its own head office in Nuremberg and continue their current line of Linux products which will be offered and supported by Novell's retail chain as well, additionally they'll obviously add several new Linux product for Novell related solutions as well as support additional IBM server hardware. Regarding the support of open source projects Novell states "From advocacy and development resources to events and support of open source efforts like kernel projects, XFree86, ReiserFS, KDE, GNOME and Mono, Novell stands side-by-side with the open source community." The order of the mentioned project may be interesting as well, but nothing specific has been said regarding changes in SUSE's product development policy. In doubt they'll just be allowed to continue their current already proven policy while being able to dramatically expand with the help of Novell's existing retail chain. Nothing more has been said so far, neither with regard to Gnome nor KDE (it shouldn't matter for any of both projects anyway). End of the story as for now.
Re: OT: SuSE baught by Novell - Datschge - 2003-11-04
http://www.suse.com/us/company/press/press_releases/archive03/novell_suse.html "From advocacy and development resources to events and support of open source efforts like kernel projects, XFree86, ReiserFS, KDE, GNOME and Mono, Novell stands side-by-side with the open source community." We'll see. Perhaps they'll want to merge KDE, GNOME and Mono? =P
Re: OT: SuSE baught by Novell - Sven Langkamp - 2003-11-04
I don't think they'll try to merge KDE and GNOME, but an integration of Mono would be really cool. If Mono would be integrated into both desktops it would be easy to port an app from one desktop to the other. Perhaps Mono will be a part of KDE 4.0...
Re: OT: SuSE baught by Novell - anon - 2003-11-09
The issue with mono is that it has got a huge patent problem. Microsoft has a nice package of patents: When they start to dislike Mono, they will find a patent infringement and stop it. That's why no sane Linux vendor will distribute it.
Re: OT: SuSE baught by Novell - Anonymous - 2003-11-04
> with SuSE as a big supporter of KDE now being merged into Novell. Does this affect KDE? I'm sure that it affects KDE somehow. But I wouldn't expect it to affect much, eg it will not kill either GNOME or KDE.
Re: OT: SuSE baught by Novell - anon - 2003-11-04
It's going to be tough since GNOME now has a strong foothold at Novell already: http://nat.org/2003/october/#16-October-2003 http://economictimes.indiatimes.com/cms.dll/html/uncomp/articleshow?msid=256142
Make 3.2 ROCK!!! - Mario - 2003-11-05
If that happens than Novell will have to pay attention and face demand. Besides, i think it would be a bad business decision to focus only on GNOME since what would really differentiate them and after all there are special needs and SUSE would have to change everything.
Re: Make 3.2 ROCK!!! - James Richard Tyrer - 2003-11-05
Forget ROCKing. What we need is a commercial quality application. Perhaps we can finally get some commercial support to help make a stable product. Also: RedHat is discontinuing consumer products: http://www.computerworld.com/softwaretopics/os/linux/story/0,10801,86827,00.html?nas=AM-86827 -- JRT
Re: Make 3.2 ROCK!!! - cjacker - 2003-11-07
Yes, "commercial quality" "stable" is most important.
Re: Make 3.2 ROCK!!! - Datschge - 2003-11-07
That's a nice collection of practically useless buzz words.
The slow death of KDE - anon2 - 2003-11-04
Mod's note: I'm deleting all these trolls with extreme prejudice, given that they are from the wiggle troll. Someone I have already warned and effectively banned. -N. <!-- How ironic. A new version of KDE is announced, and at virtually the same time it's death warrant is signed by Novell. This is indeed bad news day for the KDE desktop. Not only is TrollTech in a close business relationship with SCO (SCO owns a significant chunk in fact)... but now SuSE, the main KDE supporter is suddenly snapped up by Novell -- which just recently bought Ximian for their GNOME desktop technology and expertise. Ominous for the KDE project is Novell sending Ximian engineers out to India to train them in developing with C/GTK/GNOME See here: http://economictimes.indiatimes.com/cms.dll/html/uncomp/articleshow?msid=256142 Taken as a whole, the recent weeks have been catastrophic for the KDE project's future. I'm afraid I don't see much chance for it: It costs too much to develop for (no-one *wants* to pay the TrollTech tax to develop closed-source stuff) and has now even its meagre corporate support has been cut out from underneath it. GNOME has always been the commercial Linux desktop of choice, but this just seals it. KDE's only remaining support is TrollTech and the widely despised lawyer-pit SCO -- beyond that, it can only look to an ever shrinking band of noisy and unproductive zealots who give it a bad name with their unprofessional behaviour. How long before the "KDE is dying" troll arrives on Slashdot? Not long, I think. -->
Re: The slow death of KDE - Anonymous - 2003-11-04
> How long before the "KDE is dying" troll arrives on Slashdot? Not long, I think. The earlier you go there, the happier I'm.
Re: The slow death of KDE - Dominic - 2003-11-05
"no-one *wants* to pay the TrollTech tax to develop closed-source stuff" And Microsoft is a poor little company because no one wants to pay the MS tax to develop closed-source stuff. Go away.
Re: The slow death of KDE - regeya - 2003-11-07
The cute thing about these trolls is that they like to point out (I'm flying by the seat of my pants since I didn't see the original message) that, unlike KDE, you don't have to pay licensing fees for GNOME! Well, what the heck? The libraries are good enough to develop on, but not good enough to pay for when you want to write a closed-source for-profit app? I'm not sure I *want* software written by someone who wants to make a profit, but is completely unwilling to pay for their toolkit. For me, the argument that GNOME is free as in beer for closed-source authors just isn't a good argument.
What a bad release - Mendel Mobach - 2003-11-04
Don't understand me wrong, I test every version of KDE but I don't have the time to report bugs or so, a big sorry first but there are other software-for-free jobs who need my effords some more than the good KDE guys, there are plenty supporters of KDE.... And now the little story: I'm very lucky with a big-fat-workstation for my work so I tried to compile kde with konstruct, it worked somewhat but what a very bad release, It looks like alpha. After that I thougth that the problem was on my site and I tried to install the SuSE-build RPM's on my good (old?) SuSE 8.2 workstation, everything was/looks corrupted and it doesn't work very well. Next time better I hope, but I stuck with kde3.2-alpha2. It is the best 3.2 release until now. A little description of the problems: - self compiled arts doesn't work (it did in alpha2) (SuSE arts works, but read more...) - The content of kcontrol is gone. Damn what a big shame. - [somewhat longer list, will post it when I have some time] Maybe they should switch the alpha and beta names....... BTW: the features are cool and wanted by me, but don't forget somewhere the word stable when releasing.... Kind regards, Mendel - big KDE supporter :-)[1] [1]: Yes I understand the development process and I realy hope and pray that the KDE RC is somehow better. I'll still check the CVS version from week to week, but I don't work on CVS.
Re: What a bad release - cjacker - 2003-11-05
It is your problem or your system "SuSe"'s problem. I compiled kde-3.2cvs from Aug Cvs to beta1 with our own release MagicLinux. It works very well, of course, There is some bugs such as "switch noatun interface will cause noatun crash". I never used tools like konstruct, just write spec files and apply some patch I made(Chinese support patch). and build the whole release with a bash script.
Re: What a bad release - Mendel Mobach - 2003-11-05
I tested some more and even if I compile it by hand it has so much bugs everywhere. I will test it today or so on SuSE 9.0
Re: What a bad release - Debian User - 2003-11-06
Hi, none of your problems exist here. Actually I haven't found a bug so far in the last 2 days, only occasional crashes (KDevelop and Kontact). One thing Konstruct doesn't do for you is to make sure that the tools used actually work well enough or that all needed dev packages are there. I e.g. made the mistake to compile/install alpha2 on one machine as user and it had many more bugs than the installation as root. I slap myself for that. You probably need to find out what you did wrong or what's wrong on your Suse system. Yours, Kay
libltdl issues - PaulSeamons - 2003-11-05
Can any body help me with this error? It happened on mandrake 9.1 building meta/kde from konstruct-20031104.tar.bz2: Making install in libltdl make[4]: Entering directory `/home/pauls/konstruct/kde/kdelibs/work/kdelibs-3.1.93/libltdl' /bin/sh ../libtool --silent --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I.. -I../dcop -I../kio/kssl -DQT_THREAD_SUPPORT -I/home/pauls/kde3.2-beta1/include -I/usr/X11R6/include -I/home/pauls/kde3.2-beta1/include -I/usr/X11R6/include -I/home/pauls/kde3.2-beta1/include -I/usr/X11R6/include -D_REENTRANT -ansi -W -Wall -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2 -I/home/pauls/kde3.2-beta1/include -I/usr/X11R6/include -L/home/pauls/kde3.2-beta1/lib -L/usr/X11R6/lib -O2 -pipe -I/home/pauls/kde3.2-beta1/include -I/usr/X11R6/include -L/home/pauls/kde3.2-beta1/lib -L/usr/X11R6/lib -O2 -pipe -I/home/pauls/kde3.2-beta1/include -I/usr/X11R6/include -L/home/pauls/kde3.2-beta1/lib -L/usr/X11R6/lib -O2 -pipe -Wformat-security -Wmissing-format-attribute -c -o ltdl.lo `test -f 'ltdl.c' || echo './'`ltdl.c ltdl.c:183: `LTDL_OBJDIR' undeclared here (not in a function) ltdl.c:269: `malloc' undeclared here (not in a function) ltdl.c:271: `free' undeclared here (not in a function) ltdl.c: In function `rpl_strdup': ltdl.c:368: warning: implicit declaration of function `strlen' ltdl.c:371: warning: implicit declaration of function `strcpy' ltdl.c: In function `rpl_realloc': ltdl.c:516: warning: implicit declaration of function `realloc' ltdl.c: In function `presym_init': ltdl.c:1108: warning: unused parameter `loader_data' ltdl.c: In function `presym_exit': ltdl.c:1149: warning: unused parameter `loader_data' ltdl.c: In function `presym_open': ltdl.c:1195: warning: unused parameter `loader_data' ltdl.c: In function `presym_close': ltdl.c:1241: warning: unused parameter `loader_data' ltdl.c: In function `presym_sym': ltdl.c:1251: warning: unused parameter `loader_data' ltdl.c: In function `lt_dlpreload': ltdl.c:1352: warning: unused variable `errormsg' ltdl.c: In function `lt_dlexit': ltdl.c:1382: warning: unused variable `errormsg' ltdl.c: In function `find_module': ltdl.c:1569: warning: implicit declaration of function `sprintf' ltdl.c:1599: warning: implicit declaration of function `strcat' ltdl.c: In function `find_file': ltdl.c:1698: warning: assignment discards qualifiers from pointer target type ltdl.c:1732: warning: implicit declaration of function `strncpy' ltdl.c:1748: `FILE' undeclared (first use in this function) ltdl.c:1748: (Each undeclared identifier is reported only once ltdl.c:1748: for each function it appears in.) ltdl.c:1748: `file' undeclared (first use in this function) ltdl.c:1748: warning: implicit declaration of function `fopen' ltdl.c: In function `load_deplibs': ltdl.c:1783: warning: unused parameter `deplibs' ltdl.c: In function `lt_dlopen': ltdl.c:2043: warning: implicit declaration of function `memset' ltdl.c:2072: warning: assignment discards qualifiers from pointer target type ltdl.c:2097: `FILE' undeclared (first use in this function) ltdl.c:2097: `file' undeclared (first use in this function) ltdl.c:2122: warning: implicit declaration of function `isalnum' ltdl.c:2140: parse error before ')' token ltdl.c:2143: parse error before ')' token ltdl.c:2180: warning: implicit declaration of function `fclose' ltdl.c:2187: warning: implicit declaration of function `feof' ltdl.c:2189: warning: implicit declaration of function `fgets' ltdl.c:2214: warning: implicit declaration of function `strncmp' ltdl.c:2257: warning: assignment discards qualifiers from pointer target type ltdl.c:2257: `NULL' undeclared (first use in this function) ltdl.c:2342: warning: implicit declaration of function `getenv' ltdl.c: At top level: ltdl.c:473: warning: `rpl_memcpy' defined but not used make[4]: *** [ltdl.lo] Error 1 make[4]: Leaving directory `/home/pauls/konstruct/kde/kdelibs/work/kdelibs-3.1.93/libltdl' make[3]: *** [install-recursive] Error 1 make[3]: Leaving directory `/home/pauls/konstruct/kde/kdelibs/work/kdelibs-3.1.93' make[2]: *** [install-work/kdelibs-3.1.93/Makefile] Error 2 make[2]: Leaving directory `/home/pauls/konstruct/kde/kdelibs' make[1]: *** [dep-../../kde/kdelibs] Error 2 make[1]: Leaving directory `/home/pauls/konstruct/kde/kdebase' make: *** [dep-../../kde/kdebase] Error 2
Re: libltdl issues - Anonymous - 2003-11-05
How about using http://bugs.kde.org and watching http://bugs.kde.org/show_bug.cgi?id=67228 ?
Re: libltdl issues - Johan Veenstra - 2003-11-05
> ltdl.c:183: `LTDL_OBJDIR' undeclared here (not in a function) > ltdl.c:269: `malloc' undeclared here (not in a function) > ltdl.c:271: `free' undeclared here (not in a function) > ltdl.c:368: warning: implicit declaration of function `strlen' > ltdl.c:371: warning: implicit declaration of function `strcpy' > ltdl.c:516: warning: implicit declaration of function `realloc' > ltdl.c:1569: warning: implicit declaration of function `sprintf' > ltdl.c:1599: warning: implicit declaration of function `strcat' > ltdl.c:1732: warning: implicit declaration of function `strncpy' > ltdl.c:1748: `FILE' undeclared (first use in this function) > ltdl.c:1748: `file' undeclared (first use in this function) Looks like you need to install some development packages. When the compiler cannot find basic things like 'malloc', 'free', 'strlen' etc, it's a lot more likely your fault or konstructs fault (unlikely, but maybe konstruct should detect missing devel-packages).
libltd.h error - Daniel Garcia - 2004-11-20
hi, i need help for install Apollon (gift enhanced) when i try to configure i receive this error message... 'note: that i have libltdl, libtool and libguile installed, but the installer dont have found the file.' checking for lt_dlopen in -lltdl... no checking ltdl.h usability... no checking ltdl.h presence... no checking for ltdl.h... no * configure: error: * libltdl support is temporarily required. Please install the appropriate * library and header files (which includes the -dev package). See config.log * for more details. Thanx Daniel
Re: libltdl issues - Michael Mueller - 2004-02-04
Paul, Ever sort this out it I am having hte same problem on mandrake 9.1 with the just released kde 3.2
Re: libltdl issues - Anonymous - 2004-02-04
Install autoconf-2.5.
Re: libltdl issues - MadPenguin - 2004-02-04
I have the same problem. I'm currently looking for the package to satisfy the function call. I've found this thread a couple other places saying to install autoconf, but my version is at 2.53. Very curious. I'm using konstruct as well. If anyone gets a hint as to what package is needed, I'd appreciate the answer as well.
Re: libltdl issues - MadPenguin - 2004-02-04
Shame on me. Went and read the bug tracker. Should have it resolved shortly. Sorry for the useless posts. Thanks to previous poster with bug track info.
Re: libltdl issues - tclark - 2004-02-16
bump
Kcontrol - no modules - edfardos - 2003-11-05
I searched the bugtracker, for this, but kcontrol comes up empty, no module tree. I used konstruct to build from source on this RH9 box. prefix/share/applnk/Settings only has a couple of dirs in it, all the desktop modules are missing. crazy.. can't mess with themes and stuff! dang - looks great otherwise!! edfardos
Re: Kcontrol - no modules - Amir Michail - 2003-11-05
I have the same problem, also on RH9. Amir
Re: Kcontrol - no modules - Robert Schouwenburg - 2003-11-05
It seems you are not alone. I have the same problem. There is a bug filed in Bugzilla: See http://bugs.kde.org/show_bug.cgi?id=67192
Re: Kcontrol - no modules - Waldo Bastian - 2003-11-05
See <a href="http://bugs.kde.org/show_bug.cgi?id=67192"> http://bugs.kde.org/show_bug.cgi?id=67192</a> and <a href="http://bugs.kde.org/show_bug.cgi?id=67271"> http://bugs.kde.org/show_bug.cgi?id=67271</a> for solutions.
Re: Kcontrol - no modules - Robert Schouwenburg - 2003-11-05
Thanks! Your workaround works like a charm.
I' m having the same problem! - Vittorio - 2003-11-07
And the bugs.kde.org is down! can anyone post the work around here please ?
Re: I' m having the same problem! - Anonymous - 2003-11-07
Try again, patience is not one of your strengths?
not when it comes to a new kde release! - Vittorio - 2003-11-07
;-)
Re: Kcontrol - no modules - Georg - 2004-02-08
Hi, I have this problem too und I dont have any solution for it. The workarounds posted above expect the directory /usr/kde/3.2 which is not available by me. Where can I find the directory? thanks
How to use xdelta? - xdelta - 2003-11-05
How to use xdelta?
Re: How to use xdelta? - Anonymous - 2003-11-06
man xdelta
Re: How to use xdelta? - xdelta - 2003-11-11
how to use man?
Re: How to use xdelta? - Slv - 2004-04-22
man man
Re: How to use xdelta? -- Don't Bother! - howto-waste your time - 2004-12-08
bash-2.05b$ xdelta bash: xdelta: command not found ... bash-2.05b$ xdelta3 --help VERSION=3_PRERFC_0 usage: xdelta3 [command/options] [input [output]] commands are: encode encodes the input decode decodes the input config prints xdelta3 configuration test run the builtin tests special commands for VCDIFF inputs: printhdr print information about the first window printhdrs print information about all windows printdelta print information about the entire delta options are: -c use stdout instead of default -d same as decode command -e same as encode command -f force overwrite -n disable checksum (encode/decode) -D disable external decompression (encode/decode) -R disable external recompression (decode) -N disable small string-matching compression -S [djw|fgk] disable/enable secondary compression -A [apphead] disable/provide application header -s source source file to copy from (if any) -B blksize source file block size -W winsize input window buffer size -v be verbose (max 2) -q be quiet -h show help -V show version -P repeat count (for profiling) .... bash-2.05b$ xdelta3 -d kdelibs-3.3.1-3.3.2.tar.xdelta xdelta3: not a VCDIFF input: Invalid argument .... bash-2.05b$ xdelta3 -d -s kdelibs-3.3.1-3.3.2.tar.xdelta [silence] ^C ... bash-2.05b$ xdelta3 -d <kdelibs-3.3.1-3.3.2.tar.xdelta xdelta3: not a VCDIFF input: Invalid argument ... bash-2.05b$ rm kdelibs-3.3.1-3.3.2.tar.xdelta
Re: How to use xdelta? -- Don't Bother! - Anonymous - 2004-12-08
> bash: xdelta: command not found How about installing it then? :-) > bash-2.05b$ xdelta3 --help xdelta3 is incompatible to xdelta2 is incompatible to xdelta. > bash-2.05b$ rm kdelibs-3.3.1-3.3.2.tar.xdelta Thanks for proving your dumbness.
Re: How to use xdelta? -- Don't Bother! - Joshua Rodman - 2005-02-04
In all fairness, xdelta is a bit tricky to use. I've been wrestling with it for the last few hours trying to figure out exactly what sorts of things 'encode' and 'decode' are supposed to work well on. The only case where it beats the size of gzip is when I cat a file A to file B eight times, and inflate the input window to 100times the normal size. In this case clearly it was a diff meant to be applied to the tar file, but bafflingly, that's not the default mode for xdelta3. Further the incompatabilities bewteen xdelta 1 2 and 3 are kind of confusing, since one is self contained, one is a library, and one is a front end, and the docs are thin on the ground.
Re: How to use xdelta? -- Don't Bother! - Josh MacDonald - 2006-09-28
I promise xdelta3 will support xdelta1 inputs, one day soon. I tried to make the command-line syntax of xdelta3 as close to gzip/bzip2 as I could, which meant breaking compatibility with previous versions. xdelta2 was never finished, and it was a storage system, not an application or a library—as you say.
Re: How to use xdelta? -- Don't Bother! - Aaron Peterson - 2008-03-24
So.. how do I use it? aaron@Speck /cygdrive/c/ZZ_ISO $ ./xdelta3.0t.x86-32.exe -d KDE-Four-Live.i686-1.0.1-1.0.2.iso.xdelta KDE-Four -Live.i686-1.0.1.iso xdelta3: not a VCDIFF input: XD3_INVALID_INPUT
Re: How to use xdelta? -- Don't Bother! - Anonymous - 2008-03-24
As said earlier, xdelta3 is incompatible to xdelta1 diffs.
Re: How to use xdelta? - sponix2ipfw - 2005-09-06
Here goes nothing.. I don't have my box right in front of me to check against, but I am going to do my best to give a working example of what I did to upgrade from kde-3.4.0 to kde-3.4.1 with xdelta files The tricky part (what took me forever to figure out) was it was looking to apply the *.xdelta patches against the tarBalls (.tar files) not the source dir's, or the tar.bz2 files... (found this out by actually doing a vim (edit) on the xdelta file itself and it shows the name of the file it expects to patch against) So, something like this... for i in *.tar.bz2;do bunzip2 -v $i;done will take the bz2 off and leave you with a bunch of tarBalls doing an ls on the dir should give you filenames like: kdebase-3.4.0.tar kdelibs-3.4.0.tar and so on and then for i in *.xdelta;do xdelta patch $i;done will apply all the xdelta files one by one it would be: xdelta patch kdebase-3.4.0-3.4.1.xdelta and it should patch against your kdebase-3.4.0.tar file and the file it will spit out should be named kdebase-3.4.1.tar One more thing.. I've you've played with the sources already (built them and then repacked them) the odds are its checksum will fail (mine did). So try to work with tarBalls you haven't tinkered with yet. I've never seen such crazy stuff before, so I ended up logging a couple hours a day, for close to a week tinkering before I stumbled on it. When the man page says it patches from one file to another you just never expect it to be a plain .tar file with no compression *Grin*. If this helps you, or you still need help, feel free to spam me at sponix2ipfw@hotmail.com I get plenty of viagra mail there anyway, a little Linux question might brighten my day...
Re: How to use xdelta? - Nicolas Goutte - 2005-09-06
The answer why not .tar.bz2 is simple: try to xdelta a bzi2-ed file. You will see that the xdelta file is huge. (The problem, which is not xdelta specific) is that already for a (uncompressed) changed bit, you can have very different compression streams.) So you can use xdelta only on uncompressed tar files. Have a nice day!
Re: How to use xdelta? - Josh MacDonald - 2006-09-28
Actually, xdelta3 implements specific "external compression" routines, so that it recognizes compressed inputs and decompresses them to temporary files. This appears somewhere in the code: { "xdelta3", "-cfq", "xdelta3", "-dcfq", "X", "\xd6\xc3\xc4", 3, RD_NONEXTERNAL }, { XDELTA1PATH,"delta", XDELTA1PATH, "patch", "1", "%XD", 3, 0 }, { "bzip2", "-cf", "bzip2", "-dcf", "B", "BZh", 3, 0 }, { "gzip", "-cf", "gzip", "-dcf", "G", "\037\213", 2, 0 }, { "compress", "-cf", "uncompress", "-cf", "Z", "\037\235", 2, 0 },
Re: How to use xdelta? - Josh MacDonald - 2006-09-28
Like gzip with the additional -s SOURCE. Like gzip, -d means to decompress, and the default is to compress. For output, -c and -f flags behave likewise. Unlike gzip, xdelta3 defaults to stdout (instead of having an automatic extension). Without -s SOURCE, xdelta3 behaves like gzip for stdin/stdout purposes. Compress examples: xdelta3 -s SOURCE TARGET > OUT xdelta3 -s SOURCE TARGET OUT xdelta3 -s SOURCE < TARGET > OUT Decompress examples: xdelta3 -d -s SOURCE OUT > TARGET xdelta3 -d -s SOURCE OUT TARGET xdelta3 -d -s SOURCE < OUT > TARGET
Re: How to use xdelta? - Chiv - 2006-10-13
Can someone point out what i could be doing wrong here... or why my checksums are not matching? I'm assuming it has to do with the fact that I'm dealing with gzip's... but i'm really not sure. Example (for demo purposes): [newinstall /tmp]# ls -l *.tgz -rw-r--r-- 1 root root 2116253 Oct 12 17:06 sb-11.tgz -rw-r--r-- 1 root root 4230637 Oct 13 12:53 sb-12.tgz xdelta3 -s sb-11.tgz sb-12.tgz sb.xd Now i will rename sb-12.tgz to sb-12.tgz.orig.... and restore it with xdelta3 -d sb.xd Now i have: -rw-r--r-- 1 root root 2116253 Oct 12 17:06 sb-11.tgz -rw-r--r-- 1 root root 4230637 Oct 13 13:16 sb-12.tgz -rw-r--r-- 1 root root 4230637 Oct 13 12:53 sb-12.tgz.orig -rw-r--r-- 1 root root 2083135 Oct 13 13:15 sb.xd sb-12.tgz and sb-12.tgz.orig are the same number of bytes.. butttttt: [newinstall /tmp]# md5sum sb-12.tgz sb-12.tgz.orig d6fd1878fe4a941169d0f4b9e0d67909 sb-12.tgz 310b8c0a6bc6d8d5879ea9fea907eb12 sb-12.tgz.orig Ultimately the delta will be transfered via xml-rpc for largescale remote backup purposes so matching checksums on either end are important... what am I doing wrong. If it helps here's the output from xdelta3 config: VERSION=3_PRERFC_0 VCDIFF_TOOLS=1 REGRESSION_TEST=1 SECONDARY_FGK=0 SECONDARY_DJW=1 GENERIC_ENCODE_TABLES=1 GENERIC_ENCODE_TABLES_COMPUTE=0 EXTERNAL_COMPRESSION=1 XD3_POSIX=1 XD3_DEBUG=2 XD3_USE_LARGEFILE64=1 XD3_ENCODER=1 XD3_DEFAULT_WINSIZE=262144 XD3_DEFAULT_SRCBLKSZ=262144 XD3_DEFAULT_SRCWINSZ=8388608 XD3_DEFAULT_MEMSIZE=262144 XD3_ALLOCSIZE=8192 XD3_HARDMAXWINSIZE=8388608 XD3_NODECOMPRESSSIZE=16777216 XD3_DEFAULT_IOPT_SIZE=
Re: How to use xdelta? - Martin - 2007-07-26
xdelta 3 is very confusing compared to xdelta(1) All I want to do is create a binary diff of 2 files???
Re: How to use xdelta? - alce - 2008-08-01
Please. How compress archives at xdelta3? Commandos and options? Compress in 7z and arc at xdelta3? Please explanation. Please. Thanks for answer.
Konstruct - TomL - 2003-11-05
For some reason, my konqueror can't seem to use http web pages. I built using konstruct on RH9. Any ideas?
More info - TomL - 2003-11-05
Apparently no mime types were installed. Does that make sense? I don't know why it would say that now.
ksvg inline on web pages? - Vic - 2003-11-05
I get image placeholders instead of SVG images when browsing pages with svg images in them. Is this supposed to be working in CVS/Beta now, or should I just hold my horses a little more?
Re: ksvg inline on web pages? - Jilks - 2003-11-05
Are you sure the images are being sent with the proper svg mime type?
Re: ksvg inline on web pages? - Vic - 2003-11-06
No, I'm not sure. But I would expect at least some websites with svg would do this correctly, and yet none work that I've tried.
Re: ksvg inline on web pages? - Rob Buis - 2003-11-06
I noticed the same thing, it worked a few weeks ago. I suspect a khtml change, will look into it... Cheers, Rob.
moving icons in the panel, no more? - edfardos - 2003-11-05
Okay, maybe I'm just clueless, but is there an obvious way to slide the panel icons around? We used to simply middle-button click on an icon, and it'd slide back and forth.. never more, with 3.2b1. Is there a hotkey work around perhaps? kde3.2b1 rocks - other than this! edfardos
Re: moving icons in the panel, no more? - Vic - 2003-11-06
I've been right-clicking and selecting "Move" recently, but I'd appreciate having the middle-click drag back as well.
Re: moving icons in the panel, no more? - Anonymous - 2003-11-06
Middle mouse button on panel to move items is still there. It seems that a running khotkeys makes the middle mouse button stop working (http://bugs.kde.org/show_bug.cgi?id=67376).
Re: moving icons in the panel, no more? - Melchior FRANZ - 2003-11-08
It's not khotkeys by itself, but rather its mouse gesture support, which can be turned off (-> "gesture settings"). MMB grabbing also breaks Blender navigation.
-lreadline not found when compiling kpilot - Amit Shah - 2003-11-06
I just got this error while building from konstruct, make -C meta/kde install: /usr/bin/ld: cannot find -lreadline collect2: ld returned 1 exit status make[6]: *** [kpilot] Error 1 make[6]: Leaving directory `/home/Amit/sources/konstruct/kde/kdepim/work/kdepim-3.1.93/kpilot/kpilot'
Re: -lreadline not found when compiling kpilot - Anonymous - 2003-11-06
Check that you have the "readline" and "readline-devel" packages of your distribution installed.
Re: -lreadline not found when compiling kpilot - Amit Shah - 2003-11-06
It was due to missing the -dev package of readline. Wonder why that was needed. Thanks anyways.
Re: -lreadline not found when compiling kpilot - Amit Shah - 2003-11-06
k, solved. It needed libreadline4-dev too. (btw, I'm using Debian sid.) Don't know why the -dev package too needs to be installed.
Catch up - More-OSX_KDE_Interpollination - 2003-11-06
on features and applications I'd say KDE is now equal to Win98/ME (and as a GUI about as stable luckily it runs on some damn stable OSes (bsd/linux/unix). So hopefully kde desktops will soon have the market share of those legacy applications/platforms ... XP and Longhorn can occupy a small chunk of the market (20-25%) and MacOS/X 15-20 but the rest - the bulk of everything - will be all Linux/BSD :-D Of course - and some noted it here - multi-media on Unix sux horribly. It would be nice if MAS (network media server like X) or gstreamer (only using dbus and not corba) could provide cross platform and cross desktop framework for supporting MM ... sort of like how CUPS works for printing.
Re: Catch up - Rayiner H. - 2003-11-06
On applications, maybe, but in terms of features, its definately got an edge over even WinXP. XP can't *hope* to do some of the stuff KDE can do. And don't get me started on the API! The polish level needs work though (and I say this as a KDE user). And exactly why does multimedia on UNIX suck?
Re: Catch up - The Guru - 2003-11-07
I agree. A common, cross-platform/cross-desktop framework for multimedia is where linux is SEVERELY lacking. There is alot of discussion about this over on gnomedesktop. I suppose the hope is that GStreamer/MAS become the common standard. I hope both the GNOME & KDE people can agree on something soon!!!
SuSE 8.2 rpm missing libarys - spackenmann - 2003-11-06
Hello! Would very much like to try out 3.2 beta... I am probaly just missing some package because when trying to install I get the following output: Thanks for any help! linux:# rpm -Fvh *rpm Fehler: fehlgeschlagene Paket-Abhängigkeiten: libkateinterfaces.so.0 wird von kdeaddons3-kate-3.1.93-0 gebraucht libkateutils.so.0 wird von kdeaddons3-kate-3.1.93-0 gebraucht libkonqsidebarplugin.so.1 wird von kdeaddons3-konqueror-3.1.93-0 gebraucht libartsbuilder.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsgui.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsgui_idl.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsgui_kde.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmidi_idl.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmodules.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmodulescommon.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmoduleseffects.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmodulesmixers.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmodulessynth.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht kdebase3 = 3.1.93 wird von kdebase3-devel-3.1.93-0 gebraucht libfribidi.so.0 wird von kdegraphics3-3.1.93-0 gebraucht libexif.so.9 wird von kdegraphics3-kamera-3.1.93-0 gebraucht libartsbuilder.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsgui.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsgui_idl.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsgui_kde.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmidi_idl.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmodules.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmodulescommon.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmoduleseffects.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmodulesmixers.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmodulessynth.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libkdeinit_noatun.so wird von kdemultimedia3-video-3.1.93-0 gebraucht libgnokii.so wird von kdepim3-3.1.93-0 gebraucht libvcard.so.0 wird von quanta-3.1-112 gebraucht libvcard.so.0 wird von kdebase3-3.1.1-63 gebraucht
Re: SuSE 8.2 rpm missing libarys - Anonymous - 2003-11-06
> I am probaly just missing some package because when trying to install I get the following output: Exactly, and it's not even hard to guess those with output like > kdebase3 = 3.1.93 wird von kdebase3-devel-3.1.93-0 gebraucht
Re: SuSE 8.2 rpm missing libarys - spackenmann - 2003-11-06
Thanks very much! I in need didnt have that package. But unluckily I still cant install. This time the missing package isn't so easy to spot (for me...) :-/. Where can I find information when I want to learn more about this kind of problems? linux: # rpm -Fvh *rpm Fehler: fehlgeschlagene Paket-Abhängigkeiten: libartsbuilder.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsgui.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsgui_idl.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsgui_kde.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmidi_idl.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmodules.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmodulescommon.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmoduleseffects.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmodulesmixers.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libartsmodulessynth.so.0 wird von kdeaddons3-sound-3.1.93-0 gebraucht libfribidi.so.0 wird von kdegraphics3-3.1.93-0 gebraucht libexif.so.9 wird von kdegraphics3-kamera-3.1.93-0 gebraucht libartsbuilder.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsgui.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsgui_idl.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsgui_kde.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmidi_idl.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmodules.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmodulescommon.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmoduleseffects.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmodulesmixers.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libartsmodulessynth.so.0 wird von kdemultimedia3-video-3.1.93-0 gebraucht libkdeinit_noatun.so wird von kdemultimedia3-video-3.1.93-0 gebraucht libgnokii.so wird von kdepim3-3.1.93-0 gebraucht libvcard.so.0 wird von quanta-3.1-112 gebraucht
Re: SuSE 8.2 rpm missing libarys - Anonymous - 2003-11-06
I guess they are not surprisingly called libvcard, libgnooki, libexif, libfribidi and, what's causing the most entries, kdemultimedia.
Niederdeutsch - gerd - 2003-11-06
Will KDe be translated to niederdeutsch (iso-code nds)?
Re: Niederdeutsch - Datschge - 2003-11-07
No, it's not listed on http://i18n.kde.org/teams/ , but this shouldn't stop anyone from starting such a translation and letting it include in KDE when it has proven to be well maintained.
fantastic - Ben Roe - 2003-11-07
What an incredible release! KDE 3.1 had become my desktop of choice after cycling through pretty much every other DE/WM out there. 3.2beta is so much better: - It's faster - more responsive generally, konqueror renders faster - It's easier to use - my few annoyances with 3.1 (mostly fitt's law violations) are gone - The new mac os style child-panel menu is great - it would be nice if it was clearer how to create one, though - it looks better - the UI has been tidied up all over the place. Even KMix is improved! - integrated apps greatly improved - juk and kontact are useful, kate is better than before. The new address book looks great
Re: fantastic - anon - 2003-11-07
> it would be nice if it was clearer how to create one, though Indeed.. a lot of people are pretty confused about this particular feature. Perhaps it should prompt the user to create an empty panel with this applet if it is selected in kcontrol.
Re: fantastic - JC - 2003-11-07
Yes, it's wohoo faster on my laptop. :) Many good improvments on GUI here and there. And I love the new open and save dialog too. More options and great icons.
Common Sound Server for KDE 3.4 & Gnome 2.6?? - The Guru - 2003-11-07
C'mon people... When are we going to see a common sound server that is used for both KDE and GNOME? This ESD/Artsd mess is really painful for both users and developers. Is there any chance of KDE adopting the GStreamer framework for KDE 3.4 or KDE4?? Also, a potentially good sound server could be MAS. C'mon folks, we need a common sound/multimedia subsystem for our desktops. It matters not if you are a KDE or a Gnome person. A common multimedia framework will only benefit both desktops! PLEASE!!!!! =)
I would like to see that in KDE 4 too - Alex - 2003-11-07
A common sound server is needed and I heard that there were plans to replace arts anyway.
Re: Common Sound Server for KDE 3.4 & Gnome 2.6?? - anon - 2003-11-07
> Is there any chance of KDE adopting the GStreamer framework for KDE 3.4 No chance in hell: 1. There probably won't be a KDE 3.4.. the next version of KDE will probably be KDE 3.3 followed by KDE 4.0. 2. We can't possibly change away from arts until KDE 4.0, for compatability reasons. 3. It probably won't be gstreamer that we switch to. Not only is it immature, but it basically has the similiar problems that arts does for KDE (uses glib, so kde developers can't hack on it much)
Re: Common Sound Server for KDE 3.4 & Gnome 2.6?? - cjacker - 2003-11-08
GNOME is always GNOME;KDE is always KDE. you can not use the two great desktop ENV at same time. So you must choose one. I choose KDE, and never use anything related to GNOME. never use xmms to play music(only because it like winamp?!) remove gtk+ from your system, if you need gimp-1.3.x, keep gtk2, otherwise, remove it too, remove anything related to g*, and you will find that KDE can do anything. We have no compatable problem.
Re: Common Sound Server for KDE 3.4 & Gnome 2.6?? - Henrique Pinto - 2003-11-09
> you can not use the two great desktop ENV at same time. You actually can run both environments at the same time. Do you know you can have more than one X server running? Right now, I have KDE 3.1 on :0.0 and KDE CVS on :142857.0. So, technically, you can run GNOME and KDE at the same time. For the XMMS part, amaroK is just "better". KDE solutions are generally better (and better integrated) than GTK+ ones, so I agree with you in this point. However, I don't understand why this relates to a common media framework, what is indeed a very good idea.
Re: Common Sound Server for KDE 3.4 & Gnome 2.6?? - Guest - 2003-11-27
If KDE won't move to Gstreamer (I really think a common MM framework is a benefit for both desktops).. How about at least adopting MAS as the sound server instead of Artsd? Maybe we can convince the Gnome folk to use MAS as well, and at least we would have a common Sound Server! Please look into interoperability for USERS! PLEASE!
Re: Common Sound Server for KDE 3.4 & Gnome 2.6?? - Stephen Douglas - 2003-11-27
So what you're saying is... if KDE isn't prepared to move to a new mm framework (GStreamer), then we should instead move to a different new mm framework (MAS)?