You are not logged in.
*nevermind*
Last edited by Rasi (2008-11-27 11:08:29)
He hoped and prayed that there wasn't an afterlife. Then he realized there was a contradiction involved here and merely hoped that there wasn't an afterlife.
Douglas Adams
Offline
@Rasi: no, all built with CMAKE_BUILD_TYPE=Release. The optional qt-snapshot is built with -debug though. Are you comparing both with composite affects on and/or off? kde-svn defaults to composite on if available. I've got a 32bit Kubuntu onboard with 3.5.10 and it feels about the same as kde-svn.
@Solid1986Snake: yes, the difference is remarkable. It even fixes a problem with Qt Creator (or Designer) where widgets did not show up in the forms editor but they do with qt-copy + xorg 1.4.
Last edited by markc (2008-11-27 12:06:59)
Offline
I'm also using xorg 1.5 with nvidia (legacy 96.43.x version though) but i don't have any crashes.
xorg is crashing when i enable BackingStore in xorg.conf.
Backingstore and kwin => crash
Backingstore and copmiz=> no crash
without backingstore no crash with any window manager. I have filed a bug report in nvidia for this matter
But again, i say that i use legacy drivers and not the latest nvidia.
Offline
@capthookb: I suspect the crashes are because of qt-snapshot and some rendering weirdness because of xorg 1.5. It might be okay if kde-svn was built against qt-snapshot. I might try that one evening on my [testing] desktop machine and see if that is the case.
Seeing there seems to be a real issue between [core] + qt-copy and [testing] + qt-snapshot I'll rebuild [lib] and [max] on my [core] build machine from now on. [lib] alsa-1.0.18-*, the ctxfi driver, mlt/mlt++, x264, xvid (more to come) for ffmpeg and mplayer in [max] (also with more to come). Jack svn currently doesn't compile. [dev] capseo/libcaptury from git for i686 are also there but x86_64 won't compile atm.
Offline
hello guys!
i just have some questions about this repo!
i've tried kdemod4-unstable, but get some errors/annoying bugs:
1. shadows are buggy (settings in shadow-module are not recognized, main window has blue shadow, menus gray one)
2. when playing with settings it happens that i crash my setup
3. it feels like, that the special packaging by kdemod is not so good (there are missing icons and so on)
how stable are these packages? how stable is vanilla kde4.2 beta1? are these bugs regular? (can't find information about shadow problem)
thanks, mfg iggy
sorry for my bad english
Offline
@iggy - for the moment, this packages are better. I dont have any crashes.
Offline
Look at it this way: When you're using unstable packages, the more often they get updated the better.
Kdemod-unstable uses trunk snapshots instead of svn checkouts like this repo. Trunk snapshots are made once in about two weeks (they do not have most of extragear and playground apps) so it's far less often than daily packages we have here.
Offline
ok, i installed the kde-svn packages. but i get the same errors.
turned on shadows, but they are all white! (set it to a black color!!!)
why? can i adjust this?
i also have another strange problem:
i can suspend without any problems (pm-utils) - but not when i open a kde4-application. that means, starting a xserver with e17 for example, i can suspend and resume. but when i open dolphin or another qt-application (like opera) it does not work anymore! it suspends, but after pressing the powerbutton to start resume, the laptop turns on and nothing more (no blinking of webcam-led etc.)
last line of pm-suspend.log says going to suspend, but i know, that when i resume, there must be following a line saying "awake". that's not the case!
iggy
Last edited by iggy (2008-11-28 17:58:30)
sorry for my bad english
Offline
I'm also using xorg 1.5 with nvidia (legacy 96.43.x version though) but i don't have any crashes.
xorg is crashing when i enable BackingStore in xorg.conf.
Backingstore and kwin => crash
Backingstore and copmiz=> no crash
without backingstore no crash with any window manager. I have filed a bug report in nvidia for this matter
But again, i say that i use legacy drivers and not the latest nvidia.
Thanks a lot, I was experiencing all kinds of crashes with xorg 1.5 and nvidia drivers (latest beta) for quite some time (had to revert to xorg 1.4), disabling BackingStore fixed it for me.
Offline
Tried out both this repo and kdemods. Some interesting new features, but crashes all over the place and I couldn't get compiz fusion to work. Back to good old 4.1 kdemod which is rock solid stable for me.
Offline
I downgraded my desktop to xorg-server 1.4.2 and plasma still crashed for me so it looks like that qt-snapshot is to blame, in my case. I still might try compiling kde-svn against qt 4.5 on my own desktop just to see if that makes any difference... but the extra patches for qt-copy might make that a tough call... however, it's only an overnight build using mpkg. Speaking of mpkg, one minor change, setting any package to a priority of 1 will build that package and add it to the local repo but actually not install it (think qt-snapshot being built on a system that already uses qt-copy). A priority of 0 still skips a package altogether.
Other minor notes are that the [lib] packages have been built on top of [core] so should be safe to use (alsa 1.0.18, !jack, x264, xvid) and there is a cute little test "charm" called dev/flickcharm that demos "flicking" a bit like on an iPhone, but works with the LMB.
Oh, and the eth-os specific repo sections like [dev] and [gui] will be renamed to [eth-os-dev] and [eth-os-gui] etc but the actually online URLs will stay the same. This change means I can move the KDE4 specific packages currently in [gui] to a [kde-svn-extra] section and it won't clash with the standard [extra] repo section. I'll make this change in a day or so but I'll put softlinks in for a couple of weeks.
If anyone wants to maintain some of their own packages then I am perfectly happy to build and provide hosting for them. You just need to provide an email address (and it doesn't have to be a Google ID, as I just found out) and be prepared to maintain your source packages and keep them uptodate and they'll just get built along with kde-svn.
@b9anders: if you happen to use [testing] then I can imagine visual glitches because of xorg-server 1.5.3 + nvidia, and also, you don't need to pollute a kde-svn system with compiz as KDE4 has it's own composite manager (any conflicts between the two may also explain your crashes) which is simpler and works better than compiz IMVHO.
@iggy: no effort has been put into intergrating these packages with "exotic" features, if something works, great, if not it needs debugging and advising upstream developers. This kde-svn package set is not really the right place to provide long term patches to force things to work in all situations and are by definition (svn) not meant to be a stable desktop solution. They are availble to provide a preview of current development features and trends (same applies to all Eth-OS packages, not just kde-svn).
FWIW: I've added avidemux, dvgrab, ffmpeg and kdenlive to the [max] repo. All untested and may need support packages from [lib]... qtractor, qjackctl, jamin, hydrogen, maybe traverso and/or rosegarden, are next. I can't think of any Qt replacement for Blender so it will be one of the very few non-Qt apps I provide. That should provide a reasonable set of multimedia production apps.
Last edited by markc (2008-11-29 12:47:32)
Offline
Not using testing as xorg from testing doesn't work for me. For some reason, kwin has not allowed me any special effects since 4.1.2 and that didn't change with the 4.2 beta. On a rather standard Intel GMA 945 card at that. Which is a shame, as the new developments there was something I had been looking forward to trying. Been thinking maybe I need a new xorg.conf, but compiz fusion works smoother with this one than anything else.
Still, kwrite crashing when I press the ctrl button, konsole crashing whenever I type + random plasma crashes (with just plain no effects kwin running) was just a bit too much for me to want to troubleshoot the kwin issue at this point.
Last edited by b9anders (2008-11-29 10:46:15)
Offline
kontact doesnt start today. it cant find libkontactinterfaces.so.4, me neither
It's a bug planet!
Offline
@karoshi: just a long shot but try reinstalling kdepim.
@b9anders: my desktop is a mess because I am running on top of qt-snapshot 4.5, plasma starts but it dies and stays dead. It was okay for me up until about 2 weeks ago (on qt-snapshot). In your case it sounds so bad that I'd guess you have installed kde-svn over the top of some other kde and if that is the case then I am not surprised. If so then try a new install on a fresh [core] based system and you might, hopefully, be pleasantly surprised.
Last edited by markc (2008-11-29 13:05:07)
Offline
thx, that helped (ah, the simple things in life )
btw, should kopete work with msn now? i got libmsn installed, but neither can connect to msn nor create an msn account.
It's a bug planet!
Offline
@karoshi: good, I'm not going crazy. I had a look for that lib and it was on one machine but not the other, something like this happened once before so I tried a reinstall and then the lib was there, but I did it so fast I wasn't sure wtf. So, for some strange reason, just upgrading packages constantly can fail to install... some parts, sometimes. Hmmm.
Have you tried testing your account from the shell using msntest ? I don't use kopete (where's the IRC module!!!) but I think it uses akonadi for the backend but msntest may bypass akonadi (me guessing).
Offline
@karoshi: just a long shot but try reinstalling kdepim.
@b9anders: my desktop is a mess because I am running on top of qt-snapshot 4.5, plasma starts but it dies and stays dead. It was okay for me up until about 2 weeks ago (on qt-snapshot). In your case it sounds so bad that I'd guess you have installed kde-svn over the top of some other kde and if that is the case then I am not surprised. If so then try a new install on a fresh [core] based system and you might, hopefully, be pleasantly surprised.
Well, I did uninstall kde completely beforehand and removed any configuration folders before proceeding in either case, which I imagine ought to have sufficed. Not sure I want to set up another arch install just for that. It's taken ages of gradual tweaking to get this one running just the way I like it.
Offline
@b9anders: yeah I know, losing config settings and personal tweaks is a real pain. If you don't have a spare 5 or 10Gb partition then there is always Virtualbox. I know I was pleasantly surprised when I fired up kde-svn on my more stable build machine and it, aside from one plasma crash, worked really well... nvidia 8200 + composite and all.
Offline
For some reason, kwin has not allowed me any special effects since 4.1.2 and that didn't change with the 4.2 beta. On a rather standard Intel GMA 945 card at that. Which is a shame, as the new developments there was something I had been looking forward to trying. Been thinking maybe I need a new xorg.conf
Why don't you post your xorg.conf? Maybe someone has an idea.
Offline
b9anders wrote:For some reason, kwin has not allowed me any special effects since 4.1.2 and that didn't change with the 4.2 beta. On a rather standard Intel GMA 945 card at that. Which is a shame, as the new developments there was something I had been looking forward to trying. Been thinking maybe I need a new xorg.conf
Why don't you post your xorg.conf? Maybe someone has an idea.
That would be great if someone found anything amiss.
Offline
Hmmm... your xorg.conf is very similar to mine with regard to rendering option. The only difference is the offscreen pixmaps value. In the early KDE 4.0 experiments, I experienced considerable shm speedups with the following settings. I haven't tested whether this still hold true. IIRC the DRI option is not necessary since it is implied by other dri settings, but I never removed it.
Section "Device"
[...]
Option "XAANoOffscreenPixmaps" "true"
Option "DRI" "true"
EndSection
I hope this helps, but I doubt it. It should effect the performance, not stability.
I also have vbe and int10 enabled in the module section:
Load "int10"
Load "vbe"
Load "ic2"
They set the mechanism for the video card to talk to the monitor (ic2) and enable the Vesa bios extensions for the monitor to report its settings (vbe and int10, but they should not effect the how rendering is actually done.
Good luck!
Offline
Tried your suggestions. compiz works as smoothly as usual, but still no dice with kwin effects.
Offline
When I use dark theme in KDE then my kickoff menu looks like this:
http://e.imagehost.org/view/0412/artifact
Can anyone confirm this? Or is it something wrong with my config?
I use xorg+nvidia from extra, qt-copy 4.4.3
Offline
@hash: xorg 1.5.3 + nvidia are known to be troublesome when it comes to rendering. It's easy enough to comment out the extra repo section and downgrade xorg and nvidia to see for yourself if it makes the difference, it most likely will. You could up with it until the next xorg+nvidia updates comes along. I wouldn't expect all the kde composite glitches to be fully worked out until 4.2 has been out for a month or so and then the next xorg+nvidia update comes along, you know, after kde 4.2 has been out in the wild for awhile and all the corner case situations that will reveal bugs have had a chance to be reported.
I don't actually use kwin+plasma anymore so I can't comment about the actual glitch in Kickoff although I do use the same xorg+nvidia.
Update: doh, sorry hash, I saw "extra" and read "testing"... scratch this post.
Last edited by markc (2008-11-30 14:02:03)
Offline
@markc Actually as I mentioned above I use nvidia+xorg from [extra] not from [testing], so it is 1.4.2 not 1.5.x. And this glitch happens with composite enabled and disabled.
Offline