


Various KDE 1.-4. Improvements by smileaf 237 comments

Various KDE 1.-4. Improvements by lucher 176 comments
Open source is not about asking the user to help you make a better product so you can go out and charge others for the support due to screw ups in your code. Unfortuantly this is the thrust of the current crop of FOSS programmers.
The current crop of people such as yourself are killing linux. It is your lack of attention to detail, your unwillingness to put the effort into doing it right the first time, your unwillingness to take ownership of your problems and using your brain enough so that you can provide adequate support on minor problems--instead of major defects like kpager2 is.
Kpager2 is so bad that there's only one single distro that has an rpm for it built today. That one is suse. In fact, many months after the release of this, that one distro only has an older 0.5.x version of it. The 0.6.x version doesn't even work. I think that says alot for anyone coming here criticizing kpager2--they are justified.
These guys need to cease work on this and go save the whales. - Aug 17 2005
I would like to recommend a couple things.
1) The min/max/close button should have a 3d recessed or raised feature as an option. Often times it is hard to see the buttons because they are being masked by either a dark or light colored desktop background.
2) When a window, such a small dialog that pops up over a main window, have it accept the transparent look of the borders but not that of the desktop. Doing it the way you have sort of gives it an amateurish look.
I just don't think the child dialogs of a main window should take the transparent look and show through to the desktop.
Or actually for that matter any part of the window not overlapping the desktop background directly.
This is brilliant work and deserves alot of praise. You did a great job. - Aug 13 2005

Karamba & Superkaramba by vinbob 13 comments
The first solution I stated is what took care of the the first error I reported. I'd been using amarok 1.3 beta2 for some time and, infact, I'd compiled it.
What'd happened only the day before was that I had updated to KDE 3.4.2 from KDE 3.4.0. After doing so I received an error referring to kdeinit (just after logging in--where KDE would set itself up).
I then located and installed the most current Qt I could find. That was the only change I made up to this point. Voila! After installing it I got rid of the kdeinit (at the interprocess communication setup of the KDE launch).
I was pleased.
I also then tested to see if Kaffeine would now work. Yesterday (prior to the QT upgrade) Kaffeine no longer worked. After the upgrade the kdeinit went away and so did the Kaffeine issue.
Next I began my ./configure, make/make install of amarok 1.3 beta3. Upon doing so the first error message disappeared.
But...the next error cropped up.
I thought it might have to do with taglib 1.4. I double checked. I remembered when I first tried to compile it I found that during the compile I'd received the error that taglib wanted a different version of automake (or I was to change the aclocal.m4 file).
I changed the aclocal file and did the compile and was able to get it to compile and make/make install.
(Note: Just in case, though, I decided to download and install automake 1.9.5 as I had 1.9.2.)
I deleted the taglib 1.4 folder and started the compile again in order to ensure I had a clean new make.
Upon doing this I got past the 2nd message I posted.
Even though I had gotten past the 2nd error, I was still faced with a 3rd error--to me the question was "third and how many more?".
I went and reread the requirements document and the optional section and decided to downloaded MAS and a couple others. I then compiled those and installed them.
After those were installed I decided to try the compile again. I received a similar error to the 3rd error. I then chose to delete the beta3 folder and unpacked it again. After doing this I then reran the "./confugire " and then "make". This allowed it to compile properly. I then did a "make install" and finally was able to get it to work.
After this I decided to check out the program.
I went to test visualizations. Amarok reported that I didn't have libvisual installed or possibly the plugins. I was sure I had installed libvisual so I double checked libvisual. I had the recommended version.
I then chose to search for the download of the plugins. I downloaded them from the libvisual site. I then compiled them and installed them. I was able to test that they worked under amarok.
So, now, all is well--so far as I have tested it. - Aug 02 2005
This 1.3 beta3 seems to have trouble at every turn. Maybe some extra work on the developers part would eliminate some of these issues.
The following error occurs after installing (without error) MAS:
/usr/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
I/O error : failed to load external entity "config.docbook"
warning: failed to load external entity "config.docbook"
index.docbook:124: error: Failure to process entity amarok-config
&amarok-config;
^
index.docbook:124: parser error : Entity 'amarok-config' not defined
&amarok-config;
^
make[3]: *** [index.cache.bz2] Error 1
make[3]: Leaving directory `/user/amarok-1.3-beta3/doc/nl'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/user/amarok-1.3-beta3/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/user/amarok-1.3-beta3'
make: *** [all] Error 2
- Aug 02 2005
Now a new issue:
make[3]: Leaving directory `/user/amarok-1.3-beta3/doc/nl'
make[3]: Entering directory `/user/amarok-1.3-beta3/doc/nl'
make[3]: *** No rule to make target `vis_window.png', needed by `index.cache.bz2'. Stop.
make[3]: Leaving directory `/user/amarok-1.3-beta3/doc/nl'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/user/amarok-1.3-beta3/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/user/amarok-1.3-beta3'
make: *** [all] Error 2
- Aug 02 2005
/usr/lib/libkdeui.so: undefined reference to `QProgressBar::~QProgressBar()'
collect2: ld returned 1 exit status
make[5]: *** [graphequalizer] Error 1
make[5]: Leaving directory `/user/amarok-1.3-beta3/amarok/src/scripts/graphequalizer'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/user/amarok-1.3-beta3/amarok/src/scripts'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/user/amarok-1.3-beta3/amarok/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/user/amarok-1.3-beta3/amarok'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/user/amarok-1.3-beta3'
make: *** [all] Error 2
- Aug 01 2005
Boy does it crash. It crashes with almost every breath I take. It is that crazy.
Well, actually, it is a problem with the coders feeling it is not their responsibility to 1) identify exactly which libraries, etc they were using when they developed it, 2) a lack of responsibility when it comes to trapping errors when those libraries don't match the version they were using to develop it.
The problem with the crashes are exactly that. The developers are NOT taking the time to trap the errors that may be generated by 3rd party sound systems. For instance, the user may choose gstreamer and they may also have alsa and arts installed. Choosing any one of those 3 will cause amaroK to crash wildly if it isn't the right version of gstreamer. Yes, you heard it correctly. If you are using arts or alsa but have the wrong version of gstreamer and you choose to not use gstreamer instead choosing arts or alsa, the program will wildly crash.
This is caused mostly by not documenting and trapping the errors or the lack of proper data structures being sent back by the external sound engines.
The problem that makes this 1000 times worse is that the admin on the amarok.kde.org are inpertinent and tend to attack the users, almost reminding me (and others it seems) of meglomania.
They are rude and will attack you when you report the problems and as of the majority of problems listed, even in their specific forum for asking for help, they don't actually help instead they act contrite and attempt to ridicule and demean you.
This is my experience and my opinion.
The answer to most crashes is to go to the gstreamer home page and download the appropriate gstreamer engine. Keep it up to date.
My suggestion for the developers is to get off your butts and to add the proper trapping for these errors. Otherwise people will be extremely unhappy, and alot of us have been unhappy for a very long time. Posting that you have happy people is disingenuous as there are alot of unhappy people and it all centers around the fact that you won't trap these errors because you don't think it is your responsibility.
There's nothing like passing off the song to be played to these engines and then not watching to ensure that you are reading the right return values so you can properly play/display the song data. - Jun 06 2005
2) This program has always been tremendously buggy.
a) It is so bad that people have addressed the bugs on their web site and been lambasted by the admin on that site.
b) The changelog does not indicate that any of the bugs that I have done with their bug reporting tools have been fixed. Not a single one.
All I can say is that it is buggy and continues to be buggy and that they are not approaching it from the perspective of the user. As with most linux software it is being developed by and for the developer not for the users. - May 21 2005
2) This program has always been tremendously buggy.
a) It is so bad that people have addressed the bugs on their web site and been lambasted by the admin on that site.
b) The changelog does not indicate that any of the bugs that I have done with their bug reporting tools have been fixed. Not a single one.
All I can say is that it is buggy and continues to be buggy and that they are approaching it from the perspective of the user. As with most linux software it is being developed by and for the developer not for the users. - May 21 2005

Karamba & Superkaramba by optikSmoke 282 comments

Karamba & Superkaramba by p0z3r 87 comments
Mind considering other icons other than a bomb with all the negative connotations that go with it? - Apr 20 2005

Karamba & Superkaramba by amdfanatyk 5 comments

Various KDE Stuff by probono 6 comments
http://klik.atekon.de/kpearpc/ - Apr 17 2005

Video Players by eean 278 comments
Either way, he's just another, seemingly with nothing really outstanding. There are so many players all of which happen to use the exact same engines.
I personally test this stuff and have become sorely disappointed in the amateurishness of linux programmers hocking their wares here. - Apr 14 2005

Video Players by eean 278 comments
Configuring Codeine...
Verifying Qt 3.x Multithreaded (MT) build environment ... fail
There was an error compiling 'conf'. Be sure you have a proper
Qt 3.x Multithreaded (MT) build environment set up. This
means not just Qt, but also a C++ compiler, the 'make' command,
and any other packages necessary to compile C++ programs.
See configure.log for details.
- Apr 14 2005

KXDocker by stefano 154 comments
This one won't adjust the transparent image when you switch desktops. This one won't size the icons properly. This one stretches some icons and they look horrid. This one seems to need to put itself in the system tray of the kicker. This one doesn't size the gap between the icons and the borders when you set the icons to a certain size. You can't size the whole dock bar by simply grabbing the border like you can in OSX. In OSX the creation of the transparency is done in a slick and instantaneous fashion whereas this one draws slowly and takes a snapshot instead of actually making a transparency. With this one you can't drag and drop reorganize.
FFS get the damn transparency right at least. Stop copying the code from one program to another to add features to yours and make a real transparent window like we see in the commercial operating systems.
On top of that this one doesn't compile.
make[2]: *** No rule to make target `xeplugin_dcop_skel.cpp', needed by `xeplugin_dcop_skel.o'. Stop.
make[2]: Leaving directory `/root/kxdocker-0.30/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/kxdocker-0.30'
make: *** [all] Error 2
- Apr 10 2005

Various Plasma 5 Improvements by dangvd 703 comments
Can't you guys get your acts together and create configure and make files that work right and work the first time? - Apr 09 2005

Fonts by SeanParsons 62 comments
But there is a link on his site to some other site for fonts.
The site that he links to below his is to a site designed to make money off the fonts. Even though the price is cheap it is still a money making scheme. These also have nothing to do with kde nor are they the concept of GPL, imho. - Apr 09 2005

Various KDE 1.-4. Improvements by smileaf 237 comments
what do you mean kde34b? What is the B? - Apr 08 2005

Various KDE 1.-4. Improvements by smileaf 237 comments
- Apr 08 2005

KDM3 Themes by frikiorg 9 comments
Does your theme or do these types of themes not work in FC3? Is redhat pulling a fast one by forcing us to read their company name thus ensuring product recognition? - Apr 07 2005
It makes me exposed to a group of individuals I don't want to be exposed to and it shows that the author of the programs don't want to assume responsibility for their work. Take ownership and make it work, make it work right and make it work the first time. - Apr 05 2005

Various KDE 1.-4. Improvements by lucher 176 comments
Get the following on 'make'
kpager.cpp: In constructor `KPager2::KPager2(KPagerMainWindow*, const char*)':
kpager.cpp:122: error: aggregate `QImage img' has incomplete type and cannot be defined
kpager.cpp:124: error: invalid use of undefined type `struct QImage'
/usr/lib/qt-3.3/include/qwindowdefs.h:74: error: forward declaration of `struct QImage'
kpager.cpp:124: error: invalid use of undefined type `struct QImage'
/usr/lib/qt-3.3/include/qwindowdefs.h:74: error: forward declaration of `struct QImage'
kpager.cpp:125: error: no matching function for call to `QPixmap::convertFromImage()'
/usr/lib/qt-3.3/include/qpixmap.h:118: note: candidates are: bool QPixmap::convertFromImage(const QImage&, QPixmap::ColorMode)
/usr/lib/qt-3.3/include/qpixmap.h:119: note: bool QPixmap::convertFromImage(const QImage&, int)
kpager.cpp:128: error: invalid use of undefined type `struct QImage'
/usr/lib/qt-3.3/include/qwindowdefs.h:74: error: forward declaration of `struct QImage'
kpager.cpp:128: error: invalid use of undefined type `struct QImage'
/usr/lib/qt-3.3/include/qwindowdefs.h:74: error: forward declaration of `struct QImage'
kpager.cpp:129: error: no matching function for call to `QPixmap::convertFromImage()'
/usr/lib/qt-3.3/include/qpixmap.h:118: note: candidates are: bool QPixmap::convertFromImage(const QImage&, QPixmap::ColorMode)
/usr/lib/qt-3.3/include/qpixmap.h:119: note: bool QPixmap::convertFromImage(const QImage&, int)
kpager.cpp: In member function `void KPager2::slotBackgroundChanged(int)':
kpager.cpp:686: warning: format not a string literal and no format arguments
make[2]: *** [kpager.lo] Error 1
make[2]: Leaving directory `/root/kpager2-0.6.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/kpager2-0.6.0'
make: *** [all] Error 2
This is sort of silly. I've seen many apps compile correctly. I have also seen much better configure programs where they check and inform you. I suspect your configure file is inadequate for the task. Code the right stuff into it so we can compile your app or withdraw it from the kde-apps.org repository. It makes no sense to have hundreds of people trying to resolve your problems. - Apr 05 2005

Various KDE Stuff by stefano 91 comments
As well, it won't store changes, specifically changes to the zooming of the icons. I don't like icon zooming. On my mac with osx on it I have zooming turned off. In your program there appears to be a way to turn off zooming. The only problem is that it doesn't work. Now why would that be? Errors, unable to account for variation in distros? - Apr 03 2005

Kopete Styles by yagami 15 comments

Kopete Styles by yagami 15 comments

Card by domseichter 24 comments

Various KDE 1.-4. Improvements by lucher 176 comments
1) The location where you state the .desktop file is located is not there for Fedora Core 3.
2) I have no knowledge about killing the kicker app.
kill kicker does not seem to work.
After locating the kpager2.desktop file I did execute it. This created a window on the desktop. So, once loaded I tried to configure it. Upon selecting some options other options were switched back to their defaults. This should not happen.
When I chose to do the pixmap for the desktop windows any app that is set to display on all desktops doesn't show up until you switch desktops.
I also noticed that clicking on any of the desktops in the windows and the destop main screen does not switch. I have to use my scroll wheel to move between windows. - Mar 31 2005

Various KDE 1.-4. Improvements by lucher 176 comments

Various KDE 1.-4. Improvements by lucher 176 comments
Did ./configure, make, make install--which is wrong to expect users to do such things. This is a modern OS after 10 years one should be able to install these programs by clicking a mouse button or two. The distros really need to create a unified application install for these applications.
Anyway, it did compile correctly but when I went to use it the error I stated was presented. Any ideas? - Mar 31 2005
Any hints on getting this to compile/install properly? Like....hmmmmm....what's the command to start the configure/make/make install, or whatever?
TIA - Mar 31 2005
In the default install you can just open a root terminal and you are asked for a password. In kubunto you are asked for the password but verification fails. As well, when you attempt to sudo you are asked for a password that also seems to fail except that the program that you are executing with sudo appears to continue on.
This is somewhat similar to Mac OSX where the root is shielded from the users and you have to take some purposeful steps to get it to allow you to log in as root.
Another odd thing is that when you go and boot under the default install (which is gnome) and try to do their kubunto install you are told that you need certain dependencies but when you go to mark those dependencies (using synaptic that is) it tells you the dependencies can't be marked because other dependencies aren't met. When you try to resolve those other dependencies you get nailed with the OS trying to uninstall gnome, heh.
I've looked at Ubunto and it look real nice from the standpoint of the average Joe and Jane (Mom and Pop), except that gnome is confusing, limited, and slow and ugly. The features to maintain it aren't there and configuration is a pain. - Mar 30 2005
metabar_widget.cpp:766: error: within this context
make[2]: *** [metabar_widget.lo] Error 1
make[2]: Leaving directory `/root/metabar/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/metabar'
make: *** [all] Error 2
- Mar 23 2005

Karamba & Superkaramba by brunoldi 31 comments
Review of the themes file indicates you have some directory pointing to a program such as 'test/......" but we can only guess where test is and we can only guess what the program should be and what it does as well.
Maybe you might want to clarify how to actually get it done because simply adding the theme, as it is described exactly in your instructions says absolutely nothing about a 3rd party program, period. - Mar 23 2005