KDE 3.2 Beta 1

I know there are some KDE-Addicts among the Arch-Linux users!
Did anyone already compile the packages for the new KDE 3.2 Beta 1 and could put them into incoming?

KDE 3.2 sounds promising according to KDE's website:
<i>"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..."</i>
http://www.kde.org/announcements/announce-3.2beta1.php

Similar Messages

Kde 3.4 beta 2 transparency in taskbar

kde 3.4 beta 2 rocks...one tiny thing though, and im not sure if its a kde problem or a package problem...when i select the transparency option for the panel, a small section towards the right of the panel doesnt show the underlying wallpaper perfectly...its just a little bit messed up, but only in that one area, which is rectified if i hide/unhide the panel...just a small problem...happens every time i log on..does anyone have a soultion?
Thanks!

I don't use KDE 3.4beta2 yet... but I could suggest the following:
1. post a screenshot
2. http://bugs.kde.org (it might get fixed in the release) - make sure you link the screenshot also

[SOLVED] [no actual solution inside] No sound in KDE 4.1 beta

Installed KDE 4.1 beta as found here
There is no sound and device list in KDE control center shows ESD
I installed pulseaudio and added it and esd in the deamons in rc.conf and added the user in the groups and added the auth file in home
Now the module shows both ESD and the hardware device and still there is no sound
Any clue ?
EDIT
No miracle with the speakers being plugged in the microphone port
Last edited by 11010010110 (2008-07-20 13:26:02)

Try the latest RC and make sure to have phonon installed.

Anyone tried KDE 4.2 Beta?

Anyone tried KDE 4.2 Beta? I'm thinking of testing out KDE 4.2 if it is better than the current KDE(Mod)4 in the repos.

Yep, so it says in your original link I have no gripes whatsoever about 4.1.96-1 apart from aforesaid kppp. Anyway, only three days to go until 4.2 proper comes out. I'll be counting the days 'til it hits the repos!

Only a temp KDE 4.5 beta 1 i686 repo

OK, After I heard that KDE 4.5 beta 1 is out, and kde-unstable is hold it, I remove kdemod as soon as possible to change to the offical kde and finally found that there is no i686 available!
I know a few days later they may set i686 repo up. But I can't wait ..
So I set up an kde-unstable repo for any one who want it.
If you want to use this one, it's your own risk.
It contains all kde package, support libs, and only some of the newer l10n package (many l10n packages don't compile..) and recompiled 4.4.3 kdepim (because new kdepim will not out with kde 4.5).
Backup your ~/.kde4 before updating
I don't promise to keep this repo sync with the offical repo, so if offical kde 4.5 beta is available in kde-unstable, you should switch to it.
If you have any problems like depend is missing, you should try to enable testing or tell me.
It will be fully available in few minutes, I'm uploading the final kdeedu packages.
i686 only!
[kde-unstable]
Server=http://csslayer-aur-repo.googlecode.com/files/

duendetuc wrote:Thanks. Now it works. But why I had to do this? Is the order important?
Yes. If packages with the same names exist in several repos, the order of repos is decisive.

KDE Applications look better in Cinammon. Solved

I am trying to get a decent desktop going. have installed KDE, KDE-Base etc.
But the KDE apps have very poor color scheme/fonts/ Thin light grey letters on a light grey tool bar.
I have tried to use KDE to change the themes but no luck.
I have installed Cinnamon, and when I run Konqueror etc under Cinnamon they look MUCH better. Menus and letters are readable.
Is there a way to fix KDE so the apps look right?
pgmer6809
Last edited by pgmer6809 (2014-05-09 20:50:12)

K Thanks for the pointers.
'looks right' means that under cinnamon the desktop does not look like kde (duh!) and the menu structures are all different, and the bar at the bottom is using non KDE icons etc.
Under KDE the fonts were grey on grey and very hard to read. (number one complaint).
However now fixed mostly. Changed the theme from CDE to Oxygen. and just to be safe the appplication appearance ditto.
KDE now seems useable.
Next step is to get X, KDE, and network to start automatically at boot.
Thanks again for the help.
pgmer6809

KDE 4.2 Beta Crash

I've been using KDE 4 SVN for a while now without problems. But I think ever since I upgraded to Xorg 7.4, my KDE 4 crashes. It crashes a few seconds after the desktop is fully loaded. Does anyone know why this is happening?

You need to be more specific. No we don't know why this happens, because we don't have your log files, we don't have your hardware details, and we don't know what crashing is. Try searching the Wiki for 'Xorg Hotplugging', that might be the answer to your problem.
You can find your log files at /var/log
.log files contain the log of the current session
.old files contain the log of the last session (this is what you want, because this is where the crash would be)
next time please be more informative

Kde-unstable beta 2 shows blank white screen

installed kde 4.3 beta 2 with pacman -R kde (4.2.4) and pacman -S kde-meta
after logging in the splash screen appears and later disappears leaving white blank screen
there used to be red X button (with title could not load this plasmoid when hovering over it) in the place where i had folder view in 4.2.4. it disppeared after i deleted ~/.kde4
the screen shows no reaction o any keys or clicks except alt F2 and alt ctrl del
in alt F2 commands can be typed but cannot be launched (as if they dont exist). task manager can be opened from there and it shows the normal kde apps (plasma etc) up and running
alt ctrl del logout menu works normal
UPDATE
i installed and installed kde and kde-meta few times more. nowi have kde 4.2.4 that won't open konqueror and few other apps and it has visual artifacts of kde 4.3
Last edited by ash (2009-07-14 11:58:29)

Try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar

Sound don't work in KDE

Hello,
I've installed arch linux with KDE in my laptop. I've installed meta packages "kde" and "phonon-xine".
The sound don't work in the desktop.
Mi hardware sound is:
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
The headphones work fine, but the speakers don't work.
What can I do?.
Best regards.

Zom wrote:
http://lpix.org/images/public/f6ecd9adb … lata10.png
That's what I have on my options panel, but that might have been added in the KDE 4.6 beta.
What sound system are you using? (Alsa/OSSv4/Pulse?)
I don't known that sound system am I using, how can I see it. I'm using xine engine.
Anyway, the sound work fine now. The problem was that speaker element don't show in mixer. I've selected and work now.
I'm not in the audio group. Why work?.
Best regards.

Kde 4.1

KDE 4.1 beta was released a few days ago. Is it available for Arch Linux yet?

somairotevoli wrote:actually, they are updated daily. Try reading the thread. Your answer on how to get 4.1 is in the very first post of that thread.
My mistake. However, the first post says nothing about 4.1

Itunes alternative for KDE. Rythmbox is not integrating well

Hi,
I am not finding much information on this so I thought I would start a post. I have been using rhythmbox for music. I recently decided to bring our main computer to the KDE world from LXDE. I am trying to stick to strictly KDE programs for better integrating. I have not found an alternative to iTunes or rythmbox though. Any ideas? The problem I am having right now is that every time I try to sync with the iPod rythmbox just shuts down below starting with line 6 is what is produced during the shutdown. The previous is the initial start up of the program
I also had to install the gnome-icon-theme package which is not something that I really wanted to do.
[of@of ~]$ rhythmbox
(rhythmbox:23882): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running
(rhythmbox:23882): libdmapsharing-WARNING **: Unable to initialize mDNS: Daemon not running
(rhythmbox:23882): libdmapsharing-WARNING **: Unable to notify network of media sharing: The avahi MDNS service is not running
(rhythmbox:23882): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
(rhythmbox:23882): Rhythmbox-CRITICAL **: playlist_track_removed: assertion `track != NULL' failed
Segmentation fault

Gcool wrote:Amarok would be the qt alternative.
Or Clementine, which most prefer nowadays.

KDE 3.4 pre packages in TUR tpowa available

hi
greetings to all kde users out there.
a short question to you all, do you want kde3.4 pre packages for testing?
i would upload them to my TUR if the demand is there.
i need next week for some more testing/building and next weekend i could make them public.
thanks for your feedback
greetings
tpowa

Tpowa, are there any things in there that require dependencies updated on the base system? I would like to make those shared across gnome 2.9 beta and kde 3.4 beta, since both are releasing final versions at about the same time (gnome will have API freeze next week, only a few weeks until first betas arrive, etc, you know the drill).
It would be nice if experimental users could test both at the same time. Gnome currently doesn't build anything against KDE stuff, but gnome requires some things in the rest of arch to be updated and added. I don't think that's different for KDE too.
I keep all my changes in CVS at http://jgc.homeip.net/cgi-bin/viewcvs.cgi , which is down at this moment until wednesday when I come home from Norway to fix my server.

GCC with Symbol Visibility patch = faster apps (KDE 3.4)

I've checked gcc CVS PKGBUILD and I can't seem to find this patch in it. The patch is already present in GCC 4.
What is this patch useful for? (quote from here)
1. It very substantially improves load times of your DSO (Dynamic Shared Object)
For example, the TnFOX Boost.Python bindings library now loads in eight seconds rather than over six minutes!
2. It lets the optimiser produce better code
PLT indirections (when a function call or variable access must be looked up via the Global Offset Table such as in PIC code) can be completely avoided, thus substantially avoiding pipeline stalls on modern processors and thus much faster code. Furthermore when most of the symbols are bound locally, they can be safely elided (removed) completely through the entire DSO. This gives greater latitude especially to the inliner which no longer needs to keep an entry point around "just in case".
3. It reduces the size of your DSO by 5-20%
ELF's exported symbol table format is quite a space hog, giving the complete mangled symbol name which with heavy template usage can average around 1000 bytes. C++ templates spew out a huge amount of symbols and a typical C++ library can easily surpass 30,000 symbols which is around 5-6Mb! Therefore if you cut out the 60-80% of unnecessary symbols, your DSO can be megabytes smaller!
4. Much lower chance of symbol collision
The old woe of two libraries internally using the same symbol for different things is finally behind us with this patch. Hallelujah!
What I've understood from that webpage is that, in order to turn this on, the applications must be compiled with some certain flags (this provides GCC backward compatibility, even with this patch applied, IMO).
A comment here states that KDE 3.4 (upcomming version) supports this compile flag and it's (a lot) faster.
I haven't seen the PKGBUILD of KDE 3.4 beta 2 to check if it uses "-fvisibilty=hidden", but I suppose it does not since GCC is not patched.
Fedora, MDK 10.2 and Gentoo have this patch applied to GCC 3.4 (and KDE 3.4 betas are compiled with fvisibility in those distros, according to the comments there.
There's also "-fvisibility-inlines-hidden" which does not require any support from the application, but I think that's overriden by -fvisibility flag.

Well there are plenty of non-kde and kde specific features that are supplied as extras and would only benefit those users that need them (cups, samba, etc) to the rest of the users who may not like, want, or need them they get them anyway right now because in order to not keep recompiling package to add features Arch maintainers add the features in right from the get go. Modularity means that the packages may be built to support such features but will run without the supporting packages and the feature only works or gets enabled when you install the supporting packages.
Take transcode for example it really only has about four true dependencies but it can support all sorts of features all one has to do is install what supporting packages it needs to use these features. thsi allows the user to use whatever features or codecs they like and not have to rebuild in order to use a specific feature. It makess the maintainer's jobs alot easier because they can build all support in with only the minimal dependencies in the end.
Modularity works for all level and need of the user. The developers of KDE have to know that many users will want it all and many will want a slim KDE that is the nature of the user base in linux. Modularity caters to both.
(Modualrity has been a standard in kernels for years and should be the standard for big projects like kde,gnome, etc.)

Mixing themes KDE 4.1 and 4.2

i run KDE 4.2 beta and like it. but there are some stuff i liked more in 4.1 and 4.0 (older versions of some plasmoids and the oxygen theme)
is there way to install them in parallel as oxygen_1 etc ?

Nice question - I also think that 4.2 kicks and can't wait for it to be released proper on 27.1.
In particular I am missing stock quote plasmoids available from aur for 4.1...

[SOLVED] KDE's Plasma doesn't take GTK theme

I use the latest stable KDE 4.3.4 on my desktop machine and am trying to achieve a uniform look between my QT and GTK apps. QTcurve is nice and renders 90% correct, but still not all the apps take it like I would want them to. For example: tabs in GIMP and Firefox don't have hover effects etc.
Anyway, on gnome I always like Shiki-Brave GTK theme (http://gnome-look.org/content/show.php/ … tent=86717) + window border and also QT apps look stunning with the theme imho. So I set this as my GTK theme and chose GTK+ as my QT theme. All QT apps take it as it should, but when right-clicking apps in the task manager or icons in the panels, I see that the menus don't take the GTK colors and widgets. Also when clicking the plasma icon in the right corner and choosing Desktop Settings give me a window with other GTK-like widgets but they don't fit in with my Shiki theme at all.
For a test I also tried other GTK themes, even based on other GTK engines like Murrine, but they all give the same problem. Rebooting doesn't help either.
Hopefully the problem is clear, if not I can provide screenshots (tonight, I'm at work now ). Please feel free to test it on your own machine, it doesn't break anything. Maybe it is solved in KDE 4.4 (beta) or with QT 4.6 but I'm not sure about that...
Last edited by ulukai (2010-01-06 09:38:42)

ulukai wrote:
I use the latest stable KDE 4.3.4 on my desktop machine and am trying to achieve a uniform look between my QT and GTK apps. QTcurve is nice and renders 90% correct, but still not all the apps take it like I would want them to. For example: tabs in GIMP and Firefox don't have hover effects etc.
Anyway, on gnome I always like Shiki-Brave GTK theme (http://gnome-look.org/content/show.php/ … tent=86717) + window border and also QT apps look stunning with the theme imho. So I set this as my GTK theme and chose GTK+ as my QT theme. All QT apps take it as it should, but when right-clicking apps in the task manager or icons in the panels, I see that the menus don't take the GTK colors and widgets. Also when clicking the plasma icon in the right corner and choosing Desktop Settings give me a window with other GTK-like widgets but they don't fit in with my Shiki theme at all.
For a test I also tried other GTK themes, even based on other GTK engines like Murrine, but they all give the same problem. Rebooting doesn't help either.
Hopefully the problem is clear, if not I can provide screenshots (tonight, I'm at work now ). Please feel free to test it on your own machine, it doesn't break anything. Maybe it is solved in KDE 4.4 (beta) or with QT 4.6 but I'm not sure about that...
who said plasma uses your qt theme? because it does not and never will. you have to create your own plasma theme to match your qt/gtk one.

KDE 3.2 Beta 1

Similar Messages

Maybe you are looking for