On Thursday 26 August 2004 01:56, Wolfgang Jeltsch wrote:
> Hello,
>
> will KDE 3.2 make it into the next stable release or will there be a
> mixture of 3.2 and 3.1 as it is currently the case in testing?
Haven't seen any KDE 3.1 stuff in Sarge (but I'm not using the whole KDE
system so maybe...)
* Steffen Hein [Thu, 26 Aug 2004 12:26:19 +0200]:
> PS [OT]: Can anyone tell if GIMP 2.0 will make it into Sarge? It would be a
> shame if Debian would release with 1.2 a half year after the 2.0 release...
effort is being put in ensuring so.
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es |
On Wednesday 25 August 2004 01:03, Paul Scott wrote:
[...]
> That was good to know. But still when I try:
>
> jackd -d alsa
>
> I get :
> [EMAIL PROTECTED]:~/tex/pima/f2004/tec239$ sudo jackd -d alsa
> jackd 0.98.1
> Copyright 2001-2003 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRA
Hello,
the .desktop files originally in /usr/share/applnk/ have now apparently
migrated to /usr/share/applications/kde/...
Since the default kicker quickstart icons used those files, KDE installations
from woody and pre-3.2 sarge lose those quick access icons (well they're
defunct, not gone).
Mariusz Zielinski wrote:
On Wednesday 25 August 2004 01:03, Paul Scott wrote:
[...]
That was good to know. But still when I try:
jackd -d alsa
I get :
[EMAIL PROTECTED]:~/tex/pima/f2004/tec239$ sudo jackd -d alsa
jackd 0.98.1
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTEL
Hi. I have a LAN network with /home shared with NFS. In my main PC (where I
frequently use KOrganizer) I can use konsolekalendar without problems. But on
another one, when i try to run it, i get:
konsolekalendar: ERROR: No database available!
konsolekalendar: ERROR: No database available!
konsol
On Thursday 26 August 2004 7:19 pm, Tom Chapin wrote:
> > */1* * * * bciadmin
> > /bciadmin/bin/aclu_encrypt
>
> I don't understand your cron entry here What about simply:
>
> * * * * * /bciadmin/bin/aclu_encrypt
actually, we fixed i
* Rafael Rodriguez [Thu, 26 Aug 2004 23:07:20 +0100]:
> Don't know what can be happening. The main PC is debian sid, while the second
> one is Sarge.
perhaps the above message can be the result of konsolekalendar 3.2
being unable to read updated 3.3 databases? (if your sid machine
already
8 matches
Mail list logo