Re: digikam broken in unstable?

2009-12-17 Thread Dietz Pröpper
Achim Schaefer: > > it seems that something is severely broken with digikam in unstable > > atm (at least on my box ;-). > > I' using as well mainly unstable, but e.g. qt 4.6 from experimental. > BTW I'm using the i386 architectur. And digikam goes up to 95%+ for at least 30min? (I stoped it afte

Re: KDEDIRS is not set to /usr/local

2009-12-17 Thread Sune Vuorela
On 2009-12-17, Vedran Fura?? wrote: > I install my custom/non-debian software to /usr/local and KDE doesn't > search there (e.g. for plasmoids). What's best way to set KDEDIRS to > "/usr:/usr/local"? Put it in /etc/kde4/kdm/Xsession or /etc/environment > (which should then be read by pam_env) or s

KDEDIRS is not set to /usr/local

2009-12-17 Thread Vedran Furač
I install my custom/non-debian software to /usr/local and KDE doesn't search there (e.g. for plasmoids). What's best way to set KDEDIRS to "/usr:/usr/local"? Put it in /etc/kde4/kdm/Xsession or /etc/environment (which should then be read by pam_env) or something else? Longterm, i think you should p

Re: digikam broken in unstable?

2009-12-17 Thread Stéphane Péchard
> Digikam eats up 95%+ of the cpu and does not terminate properly. > (bug ##560893) Upstreams says, this might be a Debian problem. Hi, I confirm this bug with last version 1.0.0~rc-1 in sid. Stéphane -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe

Re: digikam broken in unstable?

2009-12-17 Thread Achim Schaefer
Hi, > Hi, > > it seems that something is severely broken with digikam in unstable atm (at > least on my box ;-). I' using as well mainly unstable, but e.g. qt 4.6 from experimental. BTW I'm using the i386 architectur. > > Digikam eats up 95%+ of the cpu and does not terminate properly. > (bug ##5

Re: digikam broken in unstable?

2009-12-17 Thread Adam
Dietz Pröpper pisze: Hi, it seems that something is severely broken with digikam in unstable atm (at least on my box ;-). Digikam eats up 95%+ of the cpu and does not terminate properly. (bug ##560893) Upstreams says, this might be a Debian problem. Therefore, can anyone confirm the behaviou