Re: extragear/multimedia/kmplayer/debian

2006-01-08 Thread Achim Bohnet
On Sunday 08 January 2006 18:14, Koos Vriezen wrote:
 SVN commit 495689 by vriezen:
 
 A working shlib would be nice indeed ..

What's breaks when you use

Depends: ${shlibs:Depends}

?
 
 
  M  +1 -1  control  
 
 
 --- trunk/extragear/multimedia/kmplayer/debian/control #495688:495689
 @@ -14,7 +14,7 @@
  Package: kmplayer-lib
  Architecture: any
  Section: sound
 -Depends: kdelibs4 (= 4:3.1.0-1) | kdelibs4c2 (= 4:3.4.0-1), libxine1 | 
 libxine1c2, libgstreamer0.8-0, libgstreamer-plugins0.8-0
 +Depends: kdelibs4 (= 4:3.1.0-1) | kdelibs4c2a (= 4:3.4.0-1), libxine1 | 
 libxine1c2, libgstreamer0.8-0, libgstreamer-plugins0.8-0


That's  cheating ;)  The same deb can't work in a environment
compiled with g++  g++ 3.4 _and_ and an environment compiled
with  g++ 4.0.

  
^^

and at least this should then be libxine1c2a too.

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: extragear/multimedia/kmplayer/debian

2006-01-08 Thread Achim Bohnet
On Sunday 08 January 2006 20:45, Koos Vriezen wrote:
 On Sun, Jan 08, 2006 at 07:56:39PM +0100, Achim Bohnet wrote:
  On Sunday 08 January 2006 18:14, Koos Vriezen wrote:
   SVN commit 495689 by vriezen:
   
   A working shlib would be nice indeed ..
  
  What's breaks when you use
  
  Depends: ${shlibs:Depends}
  
  ?
 
 I tried that some time ago, and the dependency was empty. Strangly
 enough now trying it again, I do get the dependency:
 
 Depends: kdelibs4c2a (= 4:3.4.3-1), libaudio2, libc6 (= 2.3.5-1),
 libfontconfig1 (= 2.3.0), libfreetype6 (= 2.1.5-1), libgcc1 (=
 1:4.0.2), libglib2.0-0 (= 2.8.0), libgstreamer-plugins0.8-0 (= 0.8.0),
 libgstreamer0.8-0 (= 0.8.11), libice6, libjpeg62, libpng12-0 (=
 1.2.8rel), libpopt0 (= 1.7), libqt3-mt (= 3:3.3.5), libsm6, libstdc++6
 (= 4.0.2-4), libx11-6, libxcursor1 ( 1.1.2), libxext6, libxft2 (
 2.1.1), libxi6, libxine1 (= 1.0.1), libxinerama1, libxml2 (= 2.6.21),
 libxrandr2, libxrender1 (= 1:0.9.0.2), libxt6, zlib1g (= 1:1.2.1)

Hi Koos,

Great.
 
 I guess I made a mistake back then.
 
 Thanks for reminding,
 
 Koos
 
 Btw. is there anyone that would like to adopt kmplayer for debian
 inclusion. At least for the plugin there is no real alternative. It
 would require a small patch to set xine as default backend (instead of
 mplayer), and maybe a 'powered by debian' intro animation if the
 application would go in as well.

I checked and it looks like noone is working on a debian inclusion.
For ubuntu Tonio_ started polishing it for inclusion but ran out
of time:  http://revu.tauware.de/details.py?upid=287
When I asked him for his plan, jpatrick offered to take over.
I'll keep an eye on it.

When kubuntu is pleased with the packaging, I can ask some of the
kubuntu devels that are debian developers too if they are
interested to upload it to debian.   If not I contact you again.

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#346310: kmail: Open file as new message for sending, including headers

2006-01-07 Thread Achim Bohnet
[...]
 It would be nice to be able to use KMail with reportbug, but KMail doesn't
 support opening a file as an entire message for sending.  It has --msg and
 --body, but neither of those reads the headers from the file and sets them
 accordingly (e.g. the from, to, and subject headers).  It would be really
 nice if KMail has an option for it.

You are not the first one ;) Bug/wish is reported upstream.
Please vote for http://bugs.kde.org/show_bug.cgi?id=89882

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: branches/KDE/3.5/kdebase

2005-12-23 Thread Achim Bohnet
On Thursday 22 December 2005 13:49, Script Kiddy wrote:
 SVN commit 490585 by scripty:
 
 Fix FSF address (mainly old address and s/Cambridge/Boston/ )
 (goutte)
 
 
  M  +2 -2  debian/local/kdm.options.5  
Hi,

Is there a reason why branches/KDE/3.5/kdebase/debian is still in
KDE svn?

Achim

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#343214: Manpages for lisa and reslisa

2005-12-13 Thread Achim Bohnet
On Tuesday 13 December 2005 18:49, François Wendling wrote:
 Package: lisa
 Version: 3.3.2-5
 Tags: patch
 
 
 Manpages for lisa and reslisa were missing. I join them.

Hi François,

great!

You're using the GFDL for the manpages.  This license is considered
non-free by The Debian Free Software Guidelines (DFSG).
http://www.de.debian.org/social_contract.en.html#guidelines
It would be really great if you change the license to, e.g. GPL.
Otherwise our manpages have to notadded/removed or go into the
non-free section before the next debian release.

Mhmm you used resLISa and LISa.  Way upstream likes it or typo?

Thx for your contribution,
Achim
 
 Regards
 
 François.
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#343214: Manpages for lisa and reslisa

2005-12-13 Thread Achim Bohnet
On Tuesday 13 December 2005 20:39, François Wendling wrote:
 Achim Bohnet wrote:
 
  You're using the GFDL for the manpages.  This license is considered
  non-free by The Debian Free Software Guidelines (DFSG).
  http://www.de.debian.org/social_contract.en.html#guidelines
  It would be really great if you change the license to, e.g. GPL.
  Otherwise our manpages have to notadded/removed or go into the
  non-free section before the next debian release.
 
 Modified versions are joined...lisa is licensed under the terms of the GPL, 
 the associated manpages should be too :)

Thx a lot.
 
  Mhmm you used resLISa and LISa.  Way upstream likes it or typo?
 
 Upstream, resLISa and LISa are used, but reslisa and lisa too. Some lines 
 from 
 the README.gz, written by the author :
 
 LISa is intended to provide a kind of network neighbourhood but only [...]
 
 lisa and reslisa are distributed under the GNU General Public License.
 
 IMHO, lisa stands for the program, and LISa for the concept.

Fine.  Thx for the info.

Achim
 
 
 François.
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#238770: In /etc/kde3/kdm/Xservers no -dpi Option is set

2005-11-15 Thread Achim Bohnet
On Wednesday 09 November 2005 17:55, Erik Moeller wrote:
 I experienced the same problem again after updating to KDE 3.4 on
 testing. It turned out that a change in the syntax of the kdmrc file was
 the cause: /etc/kde3/kdm/kdmrc now directly specifies the X server
 parameters, rather than using the Xservers file to look them up. The
 default there is, again, to use no dpi setting (which I find problematic
 since figuring out the correct DisplaySize setting in xorg.conf is much
 harder for a newbie). Changing ServerArgsLocal to

Well, do you think figuring out the correct dpi value for ServerArgsLocal is
easier for a newbie than adding 

DisplaySize 284 213  # width and height in mm of the display

to the Monitor section?  And anyone asking what I mean with 'correct dpi'
value has already proven that I'm right ;)

Note: Both DisplaySize or -dpi settings is only necessary if the gfx
driver and monitor can't exchange the DisplaySize information automaticly.
[Works here already in correctly in 2/3 of the used hardware .  Hopefully
more with next xorg release.
 
 ServerArgsLocal=-nolisten tcp -dpi 100

That's is almost always wrong ;)  Are you sure that your monitor has
100 dpi?

If your fonts are too small _and_ dpi is right.  the right thing is to
use bigger fonts that to fake dpi value.  Remember dpi == dot per inch
and what an inch and a dot is, is well defined.  I really prefer that
A4 or letter printout have exactly the same size as the paper.
 
 solved the problem for me.

It's wrong.  DisplaySize is the right thing (tm).

I vote for wontfix

Achim
 
 HTH,
 
 Erik
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: backports of latest kde to stable 3.1?

2005-09-13 Thread Achim Bohnet
On Tuesday 13 September 2005 21:12, Mikhail Ramendik wrote:
 Patrick Dreker wrote:
 
  I will contact Tapio... As I need the backports for internal purposes
  anyways, I could very well coordinate my work with ekhis.org to get clean
  backports with some support even...
 
 Is there a mailing list which this contact/work will go onto? I'd like to 
 sign 
 up to the list, as I'm very interested in all things related to kde on 
 stable.

At least all pkg upload are send to [EMAIL PROTECTED]
see http://lists.kde.org/?l=kalyxo-develr=1b=200509w=2

Achim
 -- 
 Yours, Mikhail Ramendik
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: missing kio_digikamio.so (bugreport?)

2005-09-12 Thread Achim Bohnet
On Monday 12 September 2005 11:54, Reto Spoerri wrote:
 Hi,
 
 Trying to use digikam i've found out that the kio_digikamio.so seems to be 
 missing in 3.4.2 (unstable) (it's giving me an error when i try to move a 
 directory in left sided tree structure). If you have any hints please cc me 
 as im not on this list.

Hi Reto,

install libdigikam-dev and the error goes away (there is already
a bug report #326786)

the kio_*.la files are in libdigikam-dev instead of libdigikam0.
I didn't like the splitout of lib and -dev pkgs (see #324592)
and the next sid upload will undo the split.

Achim
 
 
 Reto
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#327191: kdm resets after login because of problem in ~/*profile

2005-09-09 Thread Achim Bohnet
On Friday 09 September 2005 14:42, Jean de Largentaye wrote:
 The exact line which seems to have posed problem was 
 export DISPLAY=john:0.0

use ssh -X and remove the DISPLAY setting.

Achim

 in .bash_profile. I'm a bit stumped as to why that is troublesome,
 though I guess it must conflict with the env var set by X (which is
 just 0:0).
 I think I added that line when I had XDMCP enabled and was doing stuff
 on another display-less machine. That way when I'd login through SSH,
 I could immediately launch a program that would display on my local
 machine.
 
 I guess I'll have to do a little more work for the script to
 distinguish between being launched by X or during a login.
 
   It would be useful to warn the user of this 'new' behaviour, maybe in
   /usr/share/doc/NEWS.Debian.
  
  This seems quite reasonable. For the record, are you requesting that the new
  behaviour be reverted, or simply that users be given better notice to allow
  them to adapt with less hassle and frustration?
 
 Oh no, I wouldn't dare request a behaviour change. After all, I expect
 that being The Great Respected Maintainer, you know what you're doing
 ;).
 No, just giving users better notice should be enough. For example, a
 nice blatant warning during the pre-configure phase, as well as
 something in /usr/share/doc/kdm other than the changelog (through
 which I went, and must've missed that part, or dismissed as
 irrelevant)
 
 John
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: extragear/multimedia/kmplayer

2005-08-12 Thread Achim Bohnet
On Saturday 06 August 2005 14:05, Koos Vriezen wrote:
 SVN commit 443468 by vriezen:
 
 Update for 0.9.0b
 Don't install application/x-mplayer2.desktop with debian, conflicts with
 kaffeine 0.6

If someone does not have kaffeine installed, there's no
x-mplayer2.desktop file?  Isn't it better to move this file to
mplayer or kdelibs and remove from kaffeine too?

If this goes in kdelibs before the kdelibs C++ trans kaffeine and
kmplayer can silently rely on it's availabilty without require a
given version ;)

[...]
 --- trunk/extragear/multimedia/kmplayer/debian/changelog #443467:443468
 @@ -1,3 +1,9 @@
 +kmplayer (0.9.0.2-1) unstable; urgency=low
 +
 +  *  0.9.0b release

a note about the x-mplayer2.desktop change can't hurt
 +
 + -- Koos Vriezen [EMAIL PROTECTED]  Sat, 06 Aug 2005 12:08:47 +0200
 +
  kmplayer (0.9.0.1-1) unstable; urgency=low
  
*  0.9.0a release
 --- trunk/extragear/multimedia/kmplayer/debian/kmplayer-lib.install 
 #443467:443468
 @@ -6,7 +6,6 @@
  debian/tmp/usr/share/apps/kmplayer/bookmarks.xml
  debian/tmp/usr/share/apps/kmplayer/noise.gif
  debian/tmp/usr/share/mimelnk/application/x-kmplayer.desktop
 -debian/tmp/usr/share/mimelnk/application/x-mplayer2.desktop
  debian/tmp/usr/share/mimelnk/video/x-ms-wmp.desktop

Another x-ms-wmp.desktop:  another candidate?

Maybe it's a bloody stupid idea (low gain/work ration):
add a check to cdbs kde.mk (or lintian if mimelnk are used/
planed by freedesktop) to check for mimelnk
files and complain/warn if there is one. ignoring x-my-appname.desktop
by default).  Collecting them in it's own pkg, with a small
footprint.

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#320212: /usr/bin/kfontview: /usr/lib/libkfontinst.so.0: undefined symbol: FTC_SBit_Cache_New

2005-07-27 Thread Achim Bohnet
On Wednesday 27 July 2005 18:49, Tom Epperly wrote:
 Package: kcontrol
 Version: 4:3.3.2-1
 Severity: normal
 File: /usr/bin/kfontview

Short story for unstable users: unstable is currently borked due
to the C++ transition. Wait until kde 3.4.? enters sid and the
error will go way.


Longer story for sarge (and curious sid) users:
 
 When I try to run kfontview, it fails to start up.
 
 [EMAIL PROTECTED]kfontview /usr/share/fonts/truetype/freefont/FreeSans.ttf
 QPixmap: Cannot create a QPixmap when no GUI is being used
 QPixmap: Cannot create a QPixmap when no GUI is being used
 QPixmap: Cannot create a QPixmap when no GUI is being used
 QPixmap: Cannot create a QPixmap when no GUI is being used
 kbuildsycoca running...

I get those too if I start kfontview in a slogin [EMAIL PROTECTED] shell,
not when started in a KDE session (via KDM). I.e, the msg come
from the KDE daemons that are started.  Nothing to worry about.

 kfontview: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file 
 kfontviewui.rc

This file is wasn't available/was forgotten in KDE 3.3 upstream. 
It was added in KDE 3.4:

$ svn ls --recursive 
svn://anonsvn.kde.org/home/kde/branches/KDE/3.3/kdebase/kcontrol/kfontinst | 
fgrep .rc
viewpart/kfontviewpart.rc
$ svn ls --recursive 
svn://anonsvn.kde.org/home/kde/branches/KDE/3.4/kdebase/kcontrol/kfontinst | 
fgrep .rc
viewpart/kfontviewpart.rc
viewpart/kfontviewui.rc
svn log 
svn://anonsvn.kde.org/home/kde/branches/KDE/3.4/kdebase/kcontrol/kfontinst/viewpart/kfontviewui.rc
...

r370422 | dfaure | 2004-12-13 20:41:56 +0100 (Mon, 13 Dec 2004) | 4 lines

Fixed runtime warning
kfontview: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file 
kfontviewui.rc
It's quite unusual to have no .rc file, so I'd rather not hide the warning.



To fix it:

svn cat 
svn://anonsvn.kde.org/home/kde/branches/KDE/3.4/kdebase/kcontrol/kfontinst/viewpart/kfontviewui.rc
  kfontviewui.rc

and copy this file as root to /usr/share/apps/kfontinst/

 kfontview: relocation error: /usr/lib/libkfontinst.so.0: undefined symbol: 
 FTC_SBit_Cache_New
 [EMAIL PROTECTED]Mutex destroy failure: Device or resource busy

that's a temporary sid/unstable problem.  Does not happen with sarge.

 which kfontview
 /usr/bin/kfontview
 [EMAIL PROTECTED]ICE default IO error handler doing an exit(), pid = 29019, 
 errno = 0

Happen only for slogin -X [EMAIL PROTECTED], not for KDE session (maybe at 
logout)
nothing to worry about IMHO.

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#315533: kdebase-kio-plugins: missing audiocd.docbook

2005-06-23 Thread Achim Bohnet
On Thursday 23 June 2005 11:52, Andrew Schulman wrote:
 Package: kdebase-kio-plugins
 Version: 4:3.4.1-1
 Severity: normal
 Tags: experimental
 
 The Info Center help page for audiocd:/ is missing.  I see that
 usr/share/doc/kde/HTML/en/kioslave/audiocd.docbook isn't present in
 this package, as it was in 3.3.4.  Thanks, Andrew.
Hi Andrew,

the audio cd lib  _and_ doc are in kdemultimedia-kio-plugins:

$ dlocate -L kdemultimedia-kio-plugins | grep kio_audiocd
/usr/share/doc/kde/HTML/en/kio_audiocd
/usr/share/doc/kde/HTML/en/kio_audiocd/audiocd.docbook
/usr/lib/kde3/kio_audiocd.la
/usr/lib/kde3/kio_audiocd.so 

Nevertheless something is wrong:

1) Assumed that audiocd is expeted to be a standalone docu now,
the installed files needed are

kio_audiocd/index.docbook
kio_audiocd/index.cache.bz2

   (maybe even strip op kio_ prefix so help:/audiocd works)

   See http://lists.kde.org/?l=kde-i18n-docm=111933784315601w=2

2) Assumed audiocd should be merged into the other ioslave one needs

kioslave/audiocd.docbook

but here we have the problem that the audiocd.docbook file is not
in index.cache.bz  because this file is from kdebase-kio-plugins.


Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#306144: kitchensync: Kitchensync headers missing

2005-04-25 Thread Achim Bohnet
On Sunday 24 April 2005 15:49, Thomas Claveirole wrote:
 Package: kitchensync
 Version: 4:3.3.2-3

kdebluetooth sync stuff needs features from kde 3.4.  In KDE 3.4
the headers are in kdepim-dev.

You can try the deb from http://fred.hexbox.de/debian/.
For kdebluetooth problems contact [EMAIL PROTECTED]

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: KDE 3.4: packages that require libc6 (= 2.3.2.ds1-21)

2005-04-22 Thread Achim Bohnet
On Friday 22 April 2005 13:16, Pierre Habouzit wrote:
  Is that intentional? This would exclude Debian Sarge users from
  testing KDE 3.4. I can update to newer libc but would loose X related
  development packages.
 
 kde 3.4 won't be shipped with sarge. kde 3.3.2 will. if you want to use 
 kde 3.4 atm, you have to use unstable, or wait until sarge is out, and 
 the kde 3.4 migration into etch.

Or if libc is the only dependency problem (re)build it yourself
Martin. It's not complicated.

Achim

 
 -- 
 O  Pierre Habouzit
 O
 OOOhttp://www.madism.org
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: New font defaults for new users - feedback wanted!

2005-04-08 Thread Achim Bohnet
On Friday 08 April 2005 17:22, Bastian Venthur wrote:
 Pierre Habouzit wrote:
 
  afaik, when using kdm, dpi is guessed by X.
  my dpi was read on my both screens (the physical ones) and resulted in
  x-dpi and y-dpi (I mean the horiz and vertical dpi weren't the same).
  
  maybe then if fallbacks to 75dpi if no information is found on the
  hardware ...
  
  Personnaly I *manually* force the dpi in kdmrc, and I run startx with
  -- -dpi 75

Uh, why?
 
 Thats exactly the reason why i thought, that kde is optimized for 75dpi,
 because on it looks best on my 14''laptop-display as well as on my 19''
 deskop-display with 75dpi.

Some times back kdm Xservers file forced 100 dpi.   AFAIR never 75 dpi.
All this looks best cheating with dpi was a somehow usefuls hack with
CRT monitors and in limited available sizes of bitmap fonts.

With scalable fonts and TFTs dpi tweaking is stupid (IMO or course).

 
 Calculating the dpi for both displays would give me some values about
 92-96dpi but I think 75dpi looks kind of better.

No.  Wrong approach.  Choose another font size (in pt).
 
 Personaly I find dpi as it pretty useless for monitor-description, since
 we have already all data needed: 1280x1024 (19'') for example. But i
 admint, that i may have not fully understood this hole graphics-thingy.

dpi much more accurate that the 1'' steps used in monitor descriptions
(and only there ;)  Ever seen a 14.31'' monitor? I'm looking right now at one ;)
Further dpi in x and dpi in y are often not identical and then the
dimension of the diagonal is to less information.

I've 14'' TFT with 75 dpi, 98 dpi, 125 dpi and a 15'' with 133 dpi.
On all of them I use 10pt font settings and on all monitors the font
have identical size.  Windows (almost) identical size.  Restored or
copied setting look almost identical.  Great.

rant
If I would force 75 dpi, without changing font size.  The fonts would
be on the 133 dpi almost half the size as on the old TFT with 75 dpi.
Same for windows sizes.  PDL documentation tell you A4 but it looks
like A5.  Argl!   Recalibration size with gimp for every monitor,
what fun.
/rant
 
 BTW as far as i remember XP has only two settings for dpi 96(default) and
 some-other-but-not-75 (don't remember the exact value).

style=flame
yeah, brain dead windows has only std 2 font sizes.  And brain dead MS
programmer hard code pixel size of buttons so that only one font works
well.  That's worser than the unix situation year ago.
And MS solution? scale up everything on hires monitor.
Lose all the sharpness one can expect from a hires monitor.
HAA brilliant!
/style
 
  I don't know how startx work anyway.
 
 Me too ;)
 
 I wish someone at kde.org could implement some inside-kde-solution for
 setting the dpi, so we finaly have a common basis for things like setting
 the default fontsize.

KDE has the solution some years already.   They specify fonts size in
pt  (72pt == 1 inch) not pixels.   Then there no need at all to even
know about dpi as long as the Xserver gets the right value from the
hardware.

In the old days monitor had ~ 75 dpi. So 1 px ~ 1 pt = 1 dot.
People are used to font size of 10.   They always think this are pixels
but are really used to 10 pt fonts.


Achim
 
 
 Nice Weekend
 
 Bastian
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: New font defaults for new users - feedback wanted!

2005-04-08 Thread Achim Bohnet
On Friday 08 April 2005 22:28, Pierre Habouzit wrote:
  With scalable fonts and TFTs dpi tweaking is stupid (IMO or course).
 the point is I use bitmap fonts for monospace fonts in my terminals, and 
 I can assure you the dpi is quite important then ;)
 
 give me a nice looking monospaced font ... and I'll see. but it does not 

Heh, use custom font set to to a TTF like, e.g., 'Courier New' and be done ;)
[AFAIR SuSE also has a usable TTF font in konsole.]

E.g. on IRC I suggested:

cat  /etc/kde3/konsolerc EOT
[Desktop Entry]
defaultfont=Monospace,10,-1,5,50,0,0,0,0,0
font=8
EOT

If you don't like this font in konsole you will not like it
in kate either.  So using a pixel font for konsole is no
general solution.  I'll try my SuSE live CDROM next Monday
to find out what they use.  It wasn't the nonfree M$ courier new.

 exists (antialiasing is a pain for monospace fonts in my vim IMHO)

konsole and antialiasing isn't a goot idea I fully agree.

Achim
 -- 
 O  Pierre Habouzit
 O
 OOOhttp://www.madism.org
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: wrong locale in kpackage kde 3.3.2

2005-02-16 Thread Achim Bohnet
On Friday 11 February 2005 15:17, Mauro Darida wrote:
 On Thursday 10 February 2005 19:04, Frans Pop wrote:
  On Friday 04 February 2005 20:51, Mauro Darida wrote:
   I have noticed that every time I install a package from kpackage it
   gives the following warnings:
   perl:warning:Setting locale failed.
   perl:warning:Please check that your locale settings:
   LANGUAGE=(unset)
   LC_ALL=en_US
   LANG=(unset)
   are supported and installed on your system
   perl:warning:Falling back to the standard locale (C).
  
   This is what I have in my system locale settings:
   # cat /etc/profile
   # /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
   # and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
 
  [...]
 
   #
   # Imposto la localizzazione
   [EMAIL PROTECTED]
   export LANG
   [EMAIL PROTECTED]
   export LC_CTYPE
   [EMAIL PROTECTED]
   export LC_ALL
 
  AFAIK /etc/profile is not read when you log in through KDM.
  The proper place to set default LANG and LANGUAGE is /etc/environment.
 
  If you want per user settings, I think ~/.kde/env/some script is the
  proper place.
 
 Ok, I modified /etc/environment:
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
 and removed LC_ALL from /etc/profile. This is the new kpackage output:
 
 perl: warning: Setting locale failed.
 perl: warning: Please check that your locale settings:
  LANGUAGE = (unset),
  LC_ALL = en_US,
  LANG = [EMAIL PROTECTED]
 are supported and installed on your system.

Try: 
o first reboot ;)
o grep in your home .* and in /etc/  where the bogus LC_ALL is set.
  (then find and pester the orignator with a bug report ;)

Workarounds:
o Try to start kdm/gdm/startx from a console window that has a
  korrect LC* and LANG settings.  (Check with locale command)
o start kpackage is a window that has correct  LC* and LANG
  settings (Check with locale command)

Achim
[...]  

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#283339: Forward upstream, please?

2004-12-21 Thread Achim Bohnet
On Monday 13 December 2004 21:24, Riku Voipio wrote:

 Achim, can you forward this issue upstream? After reading this
[...]
Hi Riku,

as Renchi mentioned on digikam-devel, the bug is already reported
upstream:

 http://bugs.kde.org/show_bug.cgi?id=93359

Achim
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: No Text! in kde menu bar and duplicated items

2004-10-15 Thread Achim Bohnet
On Friday 15 October 2004 08:22, Massimiliano Mirabello wrote:
 Achim Bohnet wrote:
   What do you get:
  
  $ locate ui_standards.rc
 
 [EMAIL PROTECTED] /etc/kde3/ui/ui_standards.rc
 
  $ kde-config --path config
 
 [EMAIL PROTECTED] /home/ach/.kde/share/config/
^^^
Uh, that's my username, not 'test' user.  Are you sure
that the ouput of the command:

 kde-config --path config

And what's the output of

 ls -l /usr/share/config
 dpkg -l *kdelibs\* kpdf kedit | grep ^[^up]

Achim
 
 Maybe this is the problem.
 How it could be fixed?
 
 Massimiliano
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: No Text! in kde menu bar and duplicated items

2004-10-15 Thread Achim Bohnet
On Thursday 14 October 2004 14:07, Kevin Krammer wrote:
 On Thursday 14 October 2004 11:44, Achim Bohnet wrote:
 
  Let's find the really problem, before we declare it solved ;)
 
 Good idea :)
 
 [snip]
 
  $ kde-config --path config
  /home/ach/.kde/share/config/:/etc/kde3/
 
 If I do that it looks like this:
 
 /home/kevin/.kde/share/config/:/usr/local/share/config/:/usr/local/kde/share/config/
 
 I have KDEDIRS set to
 /usr:/usr/local:/usr/local/kde
 
 If I create a symlink
 ln -s /etc/kde3 /usr/share/config
 I get this from kde-config
 /home/kevin/.kde/share/config/:/etc/kde3/:/usr/local/share/config/:/usr/local/kde/share/config/
 
 I used the same KDEDIRS value with the KDE3.1.packages for Woody without 
 problems, but maybe they created that symlink?

Quite some time back KDE used /etc/kderc to define search path
(bad idea (tm) ;).If you like the symlink solution, keep
it until you update to KDE 3.2.3 or KDE 3.3.  AFAIK there Chris
added /etc/kde3 to the C++ code.

Achim
 
 Cheers,
 Kevin
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: No Text! in kde menu bar and duplicated items

2004-10-15 Thread Achim Bohnet
On Thursday 14 October 2004 19:26, Michael Peddemors wrote:
 On October 14, 2004 02:44 am, Achim Bohnet wrote:
  On Thursday 14 October 2004 10:22, Massimiliano Mirabello wrote:
  Let's find the really problem, before we declare it solved ;)
 
   A message sent in debian-kde list (subject was:Missing Text Items...
   Tracked Down.) helped me.
   Problem is caused by a missing config file in all users home (this is not
   created with user and some programs don't look for deafault shared
   ui_standards.rc)
  
   Greetings,
   Massimiliano
 
  On Sunday 10 October 2004 00:55, Michael Peddemors wrote:
   Just an FYI for anyone upgrading from 3.1.4 to 3.2.xx series, the gotcha
   in the woody debs, is that the new packages in some cases (kedit,kpdf
   etc) only
 
  What version of do you use?
 
   dpkg -l *kdelibs\* kpdf kedit | grep ^[^up]
 
 ii  kdelibs3.2.2-0.credat KDE core libraries metapackage
 ii  kdelibs-bin3.2.2-0.credat KDE core binaries
 ii  kdelibs-data   3.2.2-0.credat KDE core shared data
 ii  kdelibs4   3.2.2-0.credat KDE core libraries
 ii  kpdf   3.2.2-0.credat PDF viewer for KDE
 ii  kedit  3.2.2-0.credat KDE text editor

Nice. I switched to testing before I could they they woody debs.

  What your output of:
 
  $ strace kpdf 21 | grep ui_standards
 
 It was via strace that I found that it didn't hit 
 the /etc/kde3/ui/ui_standards.rc file..

Yeah, but I wanted to check what dirs your 'non-working' kpdf
is trying to check compared to an working app ;)

 
   Possibly new users will get this file created, I did not check yet.
 
  No.
 
 Ouch.. Then the packages need fixing..

The point is that ui_standard is a very important zentral file.
KDE simply expects to find at least one in the search path.  No
plan B to fix the 'broken' environment.
 
   Without that file in the users home directories, the app specific text
   items will only show.  This also causes duplicate items somehow, but was
   resolved also by adding this file.
 
  that's a workaround that hides the real problem ;)
 
 I know.. That's why I mentioned it shoudl go to the dvelopers lists.
 
   Really, the programs should be looking for the presence of a default
   standards file, if the users one is missing.
 
  Right.  This normally is the standard kde behaviour.

Okay,  what's the output of

 echo $KDEHOME
 echo $KDEDIR
 echo $KDEDIRS
 kde-config --path config
 ls -l /etc/kderc /usr/share/config
 strace kpdf 21 | grep ui_standards

Achim
 
 
 
 -- 
 Catch the Magic of Linux...
 
 Michael Peddemors - Senior Systems Developer 
 LinuxAdministration - Internet Services
 NetworkServices - Programming - Security
 Wizard IT Services http://www.wizard.ca 
 Linux Support Specialist - http://www.linuxmagic.com
 LinuxMagic is a Registered TradeMark of Wizard Tower TechnoServices Ltd.
 
 (604)589-0037 Beautiful British Columbia, Canada
 
 This email and any files transmitted with it are confidential and
 intended solely for the use of the individual or entity to which they
 are addressed. If you have received this email in error please notify
 the system manager. Please note that any views or opinions presented in
 this email are solely those of the author and do not necessarily
 represent those of the company.
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: No Text! in kde menu bar and duplicated items

2004-10-15 Thread Achim Bohnet
On Friday 15 October 2004 09:52, Massimiliano Mirabello wrote:
 Massimiliano Mirabello wrote:
 
 Sorry, pickput errors.
 
  Achim Bohnet wrote:
   What do you get:
  
  $ locate ui_standards.rc
 
 [EMAIL PROTECTED] locate ui_standards.rc
 /etc/kde3/ui/ui_standards.rc
 
  
  $ kde-config --path config
  
 
 [EMAIL PROTECTED] kde-config --path config
 /home/test/.kde/share/config/

Mhmm, strange.  I guess you use a KDE version that
relies on the /etc/kderc.  Output of

 cat /etc/kderc

and for completeness:

 dpkg -l *kdelibs\* kpdf kedit | grep ^[^up]


You can try to (move dir /usr/share/config away if it exists)
 
 ln -s /usr/share/config  /etc/kde3

What's the output of kde-config --path config  should
include /etc/kde3 and ui_standards.rc should be found.

Achim


  Maybe this is the problem.
  How it could be fixed?
  
  Massimiliano
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: No Text! in kde menu bar and duplicated items

2004-10-14 Thread Achim Bohnet
On Thursday 14 October 2004 10:22, Massimiliano Mirabello wrote:
 Matej Cepl wrote:
  Sorry, no idea what to do next.
 
  Matej
 
 
 Tank you all anyway.
 
 I SOLVED!!!

Let's find the really problem, before we declare it solved ;)
 
 A message sent in debian-kde list (subject was:Missing Text Items...
 Tracked Down.) helped me.
 Problem is caused by a missing config file in all users home (this is not
 created with user and some programs don't look for deafault shared
 ui_standards.rc)
 
 Greetings,
 Massimiliano
 

On Sunday 10 October 2004 00:55, Michael Peddemors wrote:
 Just an FYI for anyone upgrading from 3.1.4 to 3.2.xx series, the gotcha in 
 the woody debs, is that the new packages in some cases (kedit,kpdf etc) only 

What version of do you use?

 dpkg -l *kdelibs\* kpdf kedit | grep ^[^up]

What your output of:

$ strace kpdf 21 | grep ui_standards
access(/home/ach/.kde/share/config/ui/ui_standards.rc, R_OK) = -1 ENOENT (No 
such file or directory)
access(/etc/kde3/ui/ui_standards.rc, R_OK) = 0
stat64(/etc/kde3/ui/ui_standards.rc, {st_mode=S_IFREG|0644, st_size=6130, 
...}) = 0
open(/etc/kde3/ui/ui_standards.rc, O_RDONLY|O_LARGEFILE) = 10

compare with output of a app that finds the ui_standards file in /etc/.
What version has this package?

 look for the ~/.kde/share/config/ui/ui_standards.rc only, and not the 
 default /etc/kde3/ui/ui_standards.rc file.

that's strange.  What do you get:

$ locate ui_standards.rc
/etc/kde3/ui/ui_standards.rc

$ kde-config --path config
/home/ach/.kde/share/config/:/etc/kde3/

$ ls -l /usr/share/config
ls: /usr/share/config: No such file or directory

 Possibly new users will get this file created, I did not check yet.

No.

 Without that file in the users home directories, the app specific text items 
 will only show.  This also causes duplicate items somehow, but was resolved 
 also by adding this file.

that's a workaround that hides the real problem ;)
 
 Really, the programs should be looking for the presence of a default 
 standards 
 file, if the users one is missing.

Right.  This normally is the standard kde behaviour.
 
 I am not on the developers list, but someone who is might see if this is 
 already mentioned there.
 

I suggest any sarge KDE user with problems to include
testing-proposed-updates in it's sources list: E.g.,

deb http://ftp.de.debian.org/debian sarge-proposed-updates main contrib non-free

don't forget to logout/login and restart kdm ;)

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: Creating a Bookmark Button?

2004-10-13 Thread Achim Bohnet
On Wednesday 13 October 2004 20:49, Doug Holland wrote:
 On Saturday 09 October 2004 9:56 am, Robert wrote:
  Sure, just right-click the bar on the left side of the bookmarks toolbar
  (or top of toolbar if you have it set up vertically)
  change text position and icon size.
 
  hth,
 
  Robert
 
  On October 9, 2004 11:04 am, Robert Tilley wrote:
   Instead of the list of long text names of bookmarks in the Bookmark
   Toolbar, is it possible to change them to small icons?
 
 One thing that would be nice to do in this case is customize each icon.  
 Having a row of identical icons isn't exactly user friendly. :p

that is implemented in the bookmark editor at least since 3.2.3 ;)

Achim
 
 Doug
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Bug#275955: kdm/kde shows everything in black/white usually black, and unusable - not an X problem

2004-10-11 Thread Achim Bohnet
Hi,
what happens when you open the remote login on a host
with a xfree 4.3 server? Is it all black there too?
(I'll assume you restarted kdm already, right?)

As soon as autobuilder work for testing-proposed-updates most
of the packages waiting in 

deb http://ftp.de.debian.org/debian sarge-proposed-updates main contrib non-free

will enter sarge.  Maybe you can install them the kde debs from t-p-u
and check if the kdm problem is already fixed?

I tried to remote login window from a host running kde from s-p-u
(kdm = 3.2.3-1.sarge.2) and the remote login window looks fine.
But I only had radeon X-server to test the remote login window.

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: Leaving Debian

2004-10-04 Thread Achim Bohnet
On Monday 04 October 2004 09:37, Dominique Devriese wrote:

Hi Dominique,

it's a pity that you leave!  Neverhteless I wish you all
the best!!

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: security of KDE 3.2 in testing/sarge

2004-09-17 Thread Achim Bohnet
On Thursday 16 September 2004 19:49, Ross Boylan wrote:
 On Thu, Sep 16, 2004 at 07:28:53PM +0200, Adeodato Simó wrote:
  * Ross Boylan [Thu, 16 Sep 2004 10:15:39 -0700]:
   I noticed some security advisories in August concerning KDE and Qt:
   DSA 539-1
   DSA 542-1
  
   Are these bugs present in the current testing 3.2?  Are there any
   plans to fix them?
  
DSA 542 (#267092), which is a QT vulnerability, is fixed in
qt-x11-free 3:3.3.3-4, which will enter testing as soon as it gets
built on arm (there is a hard-to-solve FTBFS, see #270202).
 
 That's interesting.  So sarge will ship with qt 3.3 and kde 3.2?
 
  
wrt DSA 539, there have been uploads of kdebase and kdelibs to
testing-proposed-updates by Ben Burton (IIRC):
  
  kdelibs_4:3.2.3-3.sarge.2
  kdebase_4:3.2.3-1.sarge.2
 Great.  I assume these will make it into the testing update stream
 eventually.  Or should I try to grab them from somewhere directly?
 Where?

deb http://ftp.de.debian.org/debian sarge-proposed-updates main contrib non-free

Achim
 
 
  
sarge will ship with these, which address all the security issues.
  
cheers,
  
 Thanks for the good news.
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Bug#271893: kwrite: KWrite doesn't show a status line.

2004-09-16 Thread Achim Bohnet
Hi,
wild guess: did you check that Settings - Show statusbar
is activated?  If not try to activate it.  Fixed this 'bug' here ;)

Achim



Bug#269265: patch for startkde

2004-09-14 Thread Achim Bohnet
Hi,
[sorry if this sounds harsh.  Not my day, I'm in a hurry
and need some sleep :(  All my fault]

why copy complete $KDEHOME, when only one file should be modified?
There's also the need to take customized $KDEHOME, $KDEDIR and $KDEDIRS
into consideration.  A general substitution rule without taking the relevant
group into account makes me also a bit nervous (but AFAIU this could be
fixed with a more sed magic ;)

For all KDE path stuff I would recommend
to use kde-config.  echo only perl can parse perl | sed s/perl/KDE/g
;).   Some useful examples in your case:

kde-config --localprefix
kde-config --path config
kde-config --expand --install xdgdata-apps
kde-config --path apps
...

Nevertheless I would suggest to first have a look at kdeconf_update.
It's the kde way to port incompatible changes in config files.

There are also kdereadconfig and kdewriteconfig, but if you use it
for kickerrc manipulations make sure kicker depends on kdebase-bin.

$ dpkg -S /usr/bin/{kde-config,kwriteconfig,kreadconfig,kconf_update,startkde}
kdelibs-bin: /usr/bin/kde-config
kdebase-bin: /usr/bin/kwriteconfig
kdebase-bin: /usr/bin/kreadconfig
kdelibs-bin: /usr/bin/kconf_update
ksmserver: /usr/bin/startkde

Keep up the good work!
Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: Howto load i18n?

2004-09-13 Thread Achim Bohnet
On Sunday 12 September 2004 00:58, Anousak wrote:
 Yes, I have that as shown:
 $ head -n 2 /usr/share/locale/lo/entry.desktop
 [KCM Locale]
 Name=Lao
 
 Any other suggestions?

This should show a translated kwrite 

KDE_LANG=lo  kwrite

If not check

kde-config --path locale
KDE_LANG=lo  strace -o lo.log kwrite

search lo.log to check were KDE tried to find *.mo files.

Achim
 
 Sak
 
 
 -Original Message-
 From: Hendrik Sattler [mailto:[EMAIL PROTECTED] 
 Sent: Saturday, September 11, 2004 6:51 PM
 To: debian-kde@lists.debian.org
 Subject: Re: Howto load i18n?
 
 Am Sonntag, 12. September 2004 00:45 schrieben Sie:
  Yes, I am the team coordinator for Lao KDE. I created those mo files and
  put them in /usr/share/locale/lo/LC_MESSAGES/*mo. The files are there, but
  how do you tell the system, KDE, that there is kde-i18n-lo? Any particular
  file(s) I need to create or tweak?
 
 Probably something like this:
 $ head -n 3 /usr/share/locale/de/entry.desktop
 [KCM Locale]
 Name=German
 Name[af]=Duits
 
 This file is part of the kde-i18n-de package
 
 HS
 
 -- 
 Mein GPG-Key ist auf meiner Homepage verfügbar:
 http://www.hendrik-sattler.de
 oder über pgp.net
 
 PingoS - Linux-User helfen Schulen: http://www.pingos.org
 
 
 
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: Howto load i18n?

2004-09-13 Thread Achim Bohnet
On Monday 13 September 2004 22:32, you wrote:
 Thanks, Achim.
 
 When I issued KDE_LANG=lo kwrite, it shows the Lao menu. However, is there a

Well, at least now it's clear that the *.mo files are at the right location ;)
Have you checked that for whatever reason you never define KDE_LANG?  In
this case kcontrolcenter setting would be ignored.

 way to set it through Control Panel (center) such as menu fonts and
 language? I tried to set it under Control Center, it didn't work. I mean I
 don't really want to load any other applications manually, ie. KDE_LANG=lo
 kde apps. 

I've almost no glue about this i18n business so my tips to debug
the problem tips could be completely wrong.

Has your ~/.kde/share/config/kdeglobals a section like

[Locale]
Country=lo
Language=lo

Did you try setting the language with kpersonalizer (aka desktop settings
wizard)?

Sorry, I've no idea why your Lao language setting via controlcenter
does not work.

Achim
 
 Thanks,
 
 Anousak
 
 -Original Message-
 From: Achim Bohnet [mailto:[EMAIL PROTECTED] 
 Sent: Monday, September 13, 2004 3:50 PM
 To: Debian KDE
 Subject: Re: Howto load i18n?
 
 On Sunday 12 September 2004 00:58, Anousak wrote:
  Yes, I have that as shown:
  $ head -n 2 /usr/share/locale/lo/entry.desktop
  [KCM Locale]
  Name=Lao
  
  Any other suggestions?
 
 This should show a translated kwrite 
 
   KDE_LANG=lo  kwrite
 
 If not check
 
   kde-config --path locale
   KDE_LANG=lo  strace -o lo.log kwrite
 
 search lo.log to check were KDE tried to find *.mo files.
 
 Achim
  
  Sak
[...]
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: Howto load i18n?

2004-09-13 Thread Achim Bohnet
[please cc debian-kde. Maybe others have an idea]

On Monday 13 September 2004 23:35, you wrote:
 Hi Achim,
 
 Thanks for a quick reply. Now I understand it further. I have no idea why
 kcontrol didn't take effect when I change it to Laos.
 
 As I looked under, per your suggestion, /.kde/share/config/kdeglobals, I
 found that all fonts had changed accordingly. But the following changed to:
 
 [Locale]
 Country=la
 Language=

Was lo aka 'Loa' listed in kpersonalizer and in control center 
'Country/Region  Language'?

I doubt that there's anything hardcoded in the control center
module but that something is missing or miss configured.

Check ~/.xsession-error is, there's something about 'lo'.
 
 
 So I added lo to the language as 
 
 [Locale]
 Country=la
 Language=lo
 
 Issued this command 'KDE_LANG= kwrite', it works...
 
 Open many KDE apps like kmail, konsole, kate, and etc...the Only program
 didn't work now is conqueror.
 
 How do I report the problem where the language id didn't get assign from
 kcontrol.

As I wrote I still think it's a config problem not a control center
problem.  Double check if your /usr/share/locale/lo has entries
and contents like, e.g.,

$ l /usr/share/locale/de | grep -v cups_
total 52
-rw-r--r--  1 root root 6 2000-01-29 21:51 charset
-rw-r--r--  1 root root  1458 2004-05-28 11:39 entry.desktop
-rw-r--r--  1 root root   357 1999-05-31 15:48 flag.png
drwxr-xr-x  2 root root 32768 2004-09-13 23:00 LC_MESSAGES
drwxr-xr-x  2 root root  4096 2004-07-28 14:47 LC_TIME


If this does not help, ask on the general kde-i18n KDE
lists.

Achim

 
 
 Thanks so much for your good pointers.
 
 Anousak
 
 
 -Original Message-
 From: Achim Bohnet [mailto:[EMAIL PROTECTED] 
 Sent: Monday, September 13, 2004 5:18 PM
 To: Anousak
 Cc: debian-kde@lists.debian.org
 Subject: Re: Howto load i18n?
 
 On Monday 13 September 2004 22:32, you wrote:
  Thanks, Achim.
  
  When I issued KDE_LANG=lo kwrite, it shows the Lao menu. However, is there
 a
 
 Well, at least now it's clear that the *.mo files are at the right location
 ;)
 Have you checked that for whatever reason you never define KDE_LANG?  In
 this case kcontrolcenter setting would be ignored.
 
  way to set it through Control Panel (center) such as menu fonts and
  language? I tried to set it under Control Center, it didn't work. I mean I
  don't really want to load any other applications manually, ie. KDE_LANG=lo
  kde apps. 
 
 I've almost no glue about this i18n business so my tips to debug
 the problem tips could be completely wrong.
 
 Has your ~/.kde/share/config/kdeglobals a section like
 
 [Locale]
 Country=lo
 Language=lo
 
 Did you try setting the language with kpersonalizer (aka desktop settings
 wizard)?
 
 Sorry, I've no idea why your Lao language setting via controlcenter
 does not work.
 
 Achim
  
  Thanks,
  
  Anousak
  
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Bug#270429: KDM doesn't display the login window anymore

2004-09-07 Thread Achim Bohnet
On Tuesday 07 September 2004 12:59, Didier Verna wrote:
 
 Package: kdm
 Version: 4:2.2.2-14.7
 Distribution: unstable

Hi,

uh? kdm in unstable is 4:3.3.0-1.  kdm 2.2.2 sounds like your using woody.
Assuming your using unstable:
Please make sure that you're pkgs are up to date  'apt-get -u dist-upgrade'
then send us the output of 'reportbug --template kdm'.

Achim
 
 Hi !
 
 As of my upgrade this morning (but it's been 14 days since my last X
 shutdown), KDM doesn't display the login window anymore: it only displays the
 background image. I can't enter my username and password.
 
 Thanks !
 
 -- 
 Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier
 
 EPITA / LRDE, 14-16 rue Voltaire   Tel.+33 (1) 44 08 01 85
 94276 Le Kremlin-Bicêtre, France   Fax.+33 (1) 53 14 59 22   [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#270429: KDM doesn't display the login window anymore

2004-09-07 Thread Achim Bohnet
On Tuesday 07 September 2004 17:49, Didier Verna wrote:
 Achim Bohnet [EMAIL PROTECTED] wrote:
 
  On Tuesday 07 September 2004 12:59, Didier Verna wrote:
 
  Package: kdm
  Version: 4:2.2.2-14.7
  Distribution: unstable
 
  Hi,
 
  uh? kdm in unstable is 4:3.3.0-1.  kdm 2.2.2 sounds like your using woody.
 
 Hmmm. 2.2.2-14.7 was the contents of the Version line from apt-cache
 show. The version displayed by dpkg -l kdm is 3.3.0-1.

Well, if you insist in using apt-cache then better use apt-cache policy kdm ;)
 
 
  Assuming your using unstable: Please make sure that you're pkgs are up to
  date 'apt-get -u dist-upgrade' then send us the output of 'reportbug
  --template kdm'.
 
 I'd like to, but reportbug --template kdm outputs nothing ... :-/

Eh? I'm using sarge

$ reportbug --template kdm | wc -l
52
$ reportbug --version
reportbug 2.63

Okay, back to topic ;)  Did you try

/etc/init.d/kdm restart

maybe some share libs stuff broke kdm.  Does

grep kdm /var/log/daemon.log

show any strange messages?

Did you try to search if others had already the problem?
I know there were several problems related to kdm 3.3 but
because I'm using sarge I did not follow closely.  Try

o  reportbug kdm# and check the contents of related bug
o  search kde-debian mailing list archive

Achim

 --
 Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier
 
 EPITA / LRDE, 14-16 rue Voltaire   Tel.+33 (1) 44 08 01 85
 94276 Le Kremlin-Bicêtre, France   Fax.+33 (1) 53 14 59 22   [EMAIL PROTECTED]

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




'Best' way to develop debs of kdeextragear* apps inside KDE CVS

2004-07-21 Thread Achim Bohnet
Hi,
I'm working on debs for keg modules libexif, libkipi, kipi-plugins
and digikam (as test app) to ease preparation by a DD or ITP them later
myself when they will be released (maybe end of august??)

Untils the upstream release:
I find it quite inconvinient to create a tar ball and then follow
the std procedure again and again (I've to copy every change back
to kde cvs.  Has anyone some tips, URLs, how to best 'prepare'
a deb pkg inside kdeextragear cvs?   What I would like to do is
to
cvs up
make -f Makefile.cvs
cd module
while ! happy; do
  whats-necessary; debuild; dpkg -i ../xxx; test; test; test
done

Appended are my current work arounds.  I hope someone found
something better, to deal with the problem.  Any hint  tip
appreciated!

After the upstream release:
Has anyone a script that makes it simpler to incorporate
changes between the .orig.tar.gz and a (stable) branch into
debian/patches/*?  Ditto vice versa possible changes in src
tree back into kde cvs tree?

Achim
P.S. here my kde cvs workaround

For the kdebluetooth rules I use hacks like

ifeq $(wildcard ./admin) 
# okay uppacked tar ball
else
# in keg*/module
fi

and for libkexif/kipi kipi-plugins,digican (with cdbs) stuff
like:

cat keg-x/module/configure
#!/bin/bash
cd ..  ./configure $@

works for all but kipi-plugins where I also have to add

ln -s . obj-i386-linux

still to investigate why cdbs created where a obj-i386-linux
build dir and not in the other cases.

Achim
-- - .
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: revising the first cd contents...

2004-06-29 Thread Achim Bohnet
On Saturday 26 June 2004 15:41, Joey Hess wrote:
 Chris Cheney wrote:
  kde-core is enough to get KDE running, it includes arts/kdelibs/kdebase,
  but it doesn't include any of the other official KDE packages. It does
  include basic apps like kate, konqueror and konsole. The kde package
  installs the full official KDE release, but doesn't include 3rd party
  apps they are included in the kde-extras package instead.
 
 Would the KDE people be satisfied if the first debian CD installed a KDE
 that was only kde-core for the desktop task? Installs from more than

Hey, KDE people wake up! ;) ;)  kde-core contains all of the great base
other KDE apps can and do use.  But from the applicataion/user point of
view there is the konqueror, kwrite(kate) and konsole  That's all!

kde-core has: no mailer (kmail), no cd player (kscd), no mixer
(kmix), no addressbook (kaddressbook), no pdfviewer (kghostview).

Well, that's my minimum list of apps.  If others send their
top 5 KDE apps we  get a _small_ but useful new kde-destop-environment
pkgs before sarge+1.

Achim
 just the first CD would include all of KDE as they do now, and could
 even include the kde-extras stuff if you want me to add it.
 
 -- 
 see shy jo
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: kdebluetooth (WAS: Re: Extragears in Debian)

2004-05-26 Thread Achim Bohnet
On Wednesday 26 May 2004 10:23, Hendrik Sattler wrote:
 Am Wednesday 26 May 2004 02:07 schrieb Achim Bohnet:
  does it mean that you can click several times on
  the kbluetooth icon in the systrack and the 2nd or 3rd
  invocation of bluetooth:/ konqueror does not kill all
  other bluetooth;/ konq processes?
 
 Yes.

Okay.
 
  If you get a crash, please add your config to
  http://bugs.kde.org/show_bug.cgi?id=79262 ;)
 
 Sorry, I cannot confirm this bug with version 0.0.cvs20040519-1

Thanks for the info,
Achim
 
 HS
 
 -- 
 Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de
 oder über pgp.net
 
 PingoS - Linux-User helfen Schulen: http://www.pingos.org
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




KDM xauth (WAS: KDE is preventing laptop disk spindown by incessant configfile-writing)

2004-05-26 Thread Achim Bohnet
On Tuesday 18 May 2004 21:53, [EMAIL PROTECTED] wrote:
[...]
 P.S.  On the off chance that this had something to do w/using gdm as
 my display manager, I edited /etc/X11/default-display-manager to be
 /usr/bin/kdm instead of /usr/bin/gdm.  Didn't help, although it was
 -intensely- irritating that kdm then created /var/run/xauth and
 /var/run/xdmctl directories that then broke any attempt to launch
 applications from a shell, as opposed to from the KDE popup menus
 (e.g., emacs  from an xterm gave authentication errors, as did
 xhost! so I couldn't -fix- whatever auth problems were going on...).

By default, xservers started by kdm do not listen on tcp ports to
xhost can't work and btw. xhost is devil ;)

 Fortunately, I found the /var/run stuff by looking for any
 recently-modified files, and just nuked those directories, and then I
 could start X apps again (under gdm, anyway; I didn't go back to kdm
 after that).  This seems like a bug; if it's documented behavior, I'd
 love to know why.  (I haven't checked carefully to see what those dirs
 think they're doing, and since deleting them fixed the behavior, I'm
 assuming they were responsible.)

I doubt it ;)

/var/run/xauth tells the _xserver_ what cookies to accept.
~/.Xauthority contains the same cookie after login and those are
used by any X11 application to authorize to the xserver.

/var/run/xdmctl is used by a kde to controls kdm.  emacs
and xterm know nothing about it and should therefore not be
affected ;)

I only remember once a damaged .Xauthority file in the last years
running kdm on dozens of hosts.  Logout, removing the
~user/.Xauthority, login fixed it.

I guess that the start/stop logout/login fixed your problem too.
If you feel like it.  Stop gdm, remove .Xauthority and
.ICEauthority files in the home directory.  Start kdm (and
never have this problem again ;)

Achim

 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




kdebluetooth (WAS: Re: Extragears in Debian)

2004-05-25 Thread Achim Bohnet
On Monday 24 May 2004 14:24, Hendrik Sattler wrote:
 Am Monday 24 May 2004 11:07 schrieb Tomàs Núñez:
  Is there any plan (or any thought) to put KDE extragears in Debian? We have
  most of this apps as separate packets (eg K3b, kwifimanager), but not all
  of them. So will debian have (shortly or in the future) a meta-packet named
  kdeextragear-1 (or 2 or 3)?
 
 At least for kdebluetooth, you can get a cvs-snapshot debian package from the 
 projects site.
 I use it and it works pretty well.

Hi Hendrik,
does it mean that you can click several times on
the kbluetooth icon in the systrack and the 2nd or 3rd
invocation of bluetooth:/ konqueror does not kill all
other bluetooth;/ konq processes?

If you get a crash, please add your config to
http://bugs.kde.org/show_bug.cgi?id=79262 ;)

Achim
 
 HS
 
 -- 
 Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de
 oder über pgp.net
 
 PingoS - Linux-User helfen Schulen: http://www.pingos.org
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




kdeextragear-3/kdebluetooth/debian

2004-05-10 Thread Achim Bohnet
CVS commit by ach: 

build also with bluez-utils 2.6 from experimental. Alternative
libsdp2-dev build-dep can be removed when bluez-utils 2.6 enters
unstable in the next days.


  M +1 -1  control   1.5


--- kdeextragear-3/kdebluetooth/debian/control  #1.4:1.5
@@ -3,5 +3,5 @@
 Priority: optional
 Maintainer: Fred Schaettgen [EMAIL PROTECTED]
-Build-Depends: debhelper ( 4.0.0), kdelibs4-dev (= 3.1.4), 
libbluetooth1-dev (= 2.5),
+Build-Depends: debhelper ( 4.0.0), kdelibs4-dev (= 3.1.4), 
libbluetooth1-dev (= 2.6) |
  libsdp2-dev (= 1.5), xmms-dev (= 1.2.7)
 Standards-Version: 3.5.9




Re: Bug#247821: kdm exits after one run

2004-05-07 Thread Achim Bohnet
On Friday 07 May 2004 13:22, Patrick Cornelißen wrote:
 Anton Ivanov wrote:
  Package: kdm
  Version: 4:3.2.2-1
  Severity: grave
  
  It will exit after the user logs out and has to be started again
  manually. This appeared after upgrade from 3.1 to 3.2 and is
  reproducible.
 Additional Info:
 I had this problem on our systems too. I solved it by removing the ldap 
 checks in /etc/pam.d
 For authentication nsswitch was enough. Just the per Host acces 
 restriction doesn't work this way :-(

Try
grep kdm /var/log/*.log  kdm.before
.. start kdm and login/logout and after kdm exits
grep kdm /var/log/*.log  kdm.after
diff -u kdm.before kdm.after 

and send the diff output. Maybe there are additional hints
what kdm did not like.

Achim
 
 -- 
 Bye,
   Patrick Cornelissen
   http://www.p-c-software.de
   ICQ:15885533
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#247196: kdm: clarify documentation

2004-05-04 Thread Achim Bohnet
On Monday 03 May 2004 21:35, Ross Boylan wrote:
 Package: kdm
 Version: 4:3.2.2-1
 Severity: wishlist

Hi Ross,
 
 1) The current documentation makes several references to the xdm
 manpage, but users may not have xdm installed.  For this and other
 reasons, a kdm manpage would be good (see also bug #193527).

Agreed. Care to write (parts) of it?  That would be great.
 
 2) README.Debian does indicate it is for xdm, but it would be helpful
 to have a few lines explaining how this translates to kdm.  Among the
 interpretations that occurred to me were
   * kdm uses the same files
   * kdm uses files of the same name but in /etc/kde3 (seems to be the
 case)
   * kdm uses its own files with different names (e.g., starting with a
 k)
 README.gz did allow me to infer it was the second, but that's a bit
 obscure.  Perhaps README.Debian could be removed?

I had a look at README.Debian and I agree to that the file is
more confusing that helpful and should be removed.

The only debian specific infos worth to note IMHO would be
how and where debian select what x display manager gets used,
because that really Debian specific.

Hmm, because default entries in Xserver use -tcp nolisten one can
also mention that 'Remote Session' in the kdm greeter menu
will not work.

 3) README.Debian includes confusions and redundancies.  It refers to
 The above three files, but there only seemed to be one file
 (xdm-config) that had been mentioned (Xresources is a directory,
 though perhaps not outside of Debian.  Even so, that's only two
 files).  The phrase See the X(1) manual page for more information
 about X resources occurs twice, and the surrounding discussion is a
 bit repetitive in other ways.
 
 4) README.gz has a discussion headed The command FiFos which doesn't

s/command/Command/ in README.gz so source string matches target string
(for tools with case sensitive search).

 quite indicate, from a user perspective, how to use them.  I tried
 echo commands to the relevant files, and that seemed to work.  While
 the cogniscenti may know that already, saying it explicitly would
 be useful.

Care to provide better description?

 The discussion seems to imply that the low level interface doesn't
 matter because there are higher level tools: ksmserver and kdesktop.
 I tried starting the former and it messed up my session so badly I had
 to kill it.  I assume the latter is always running; I looked on my
 menus but didn't see anything that seemed related to this.

with reserve lines in Xservers your k-menu and kscreensaver should
have 'Start new session' menu entries and buttons, respectively.
Works fine here.

 I was specifically looking for how to start up a session that had been
 specified in Xservers with the reserve word.  There seem to be other
 problems with that, which I reported in a previous bug.  The point
 here is that while some of the functionality is accessible from the
 desktop (e.g., shutdown and restart), reserve and other functionality
 does not seem to be.

No.  'Start new session' exposes reserve command on the gui.

Achim
 
 
 -- System Information:
 Debian Release: testing/unstable
   APT prefers testing
   APT policy: (990, 'testing'), (50, 'unstable')
 Architecture: i386 (i686)
 Kernel: Linux 2.4.24advncdfs
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
 
 Versions of packages kdm depends on:
 ii  debconf 1.4.22   Debian configuration management 
 sy
 ii  kdebase-bin 4:3.2.2-1KDE Base (binaries)
 ii  kdelibs44:3.2.2-2KDE core libraries
 ii  libart-2.0-22.3.16-5 Library of functions for 2D 
 graphi
 ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries 
 an
 ii  libfam0c102 2.7.0-5  client library to control the 
 FAM 
 ii  libgcc1 1:3.3.3-6GCC support library
 ii  libice6 4.3.0-7  Inter-Client Exchange library
 ii  libpam-runtime  0.76-19  Runtime support for the PAM 
 librar
 ii  libpam0g0.76-19  Pluggable Authentication Modules 
 l
 ii  libpng12-0  1.2.5.0-5PNG library - runtime
 ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime 
 v
 ii  libsm6  4.3.0-7  X Window System Session 
 Management
 ii  libstdc++5  1:3.3.3-6The GNU Standard C++ Library v3
 ii  libx11-64.3.0-7  X Window System protocol client 
 li
 ii  libxext64.3.0-7  X Window System miscellaneous 
 exte
 ii  libxrender1 0.8.3-7  X Rendering Extension client 
 libra
 ii  libxtst64.3.0-7  X Window System event recording 
 an
 ii  xbase-clients   4.3.0-7  miscellaneous X clients
 ii  xlibs   4.3.0-7  X Window System client libraries 
 m
 ii  zlib1g  1:1.2.1-5compression 

Bug#247193: kdm: reserve doesn't seem to work

2004-05-04 Thread Achim Bohnet
On Monday 03 May 2004 21:18, Ross Boylan wrote:
 Package: kdm
 Version: 4:3.2.2-1
 Severity: normal
 
 I uncommented the first commented display line in /etc/kde3/kdm/Xservers:
 :1 [EMAIL PROTECTED] reserve /usr/X11R6/bin/X -nolisten tcp :1 vt8
 and did 
   invoke-rc.d kdm restart
 
 Despite this /var/run/xdmctl/ only showed xdmctl and xdmctl-:0.

Reserve is working fine here (can start other parallel session
with k-menu - 'Start new session'.  Nevertheless I only have
xdmctl and xdmctl-:0 too.  When I start the first new session
xdmctl-:1 is created.   So xdmctl-:? are only created when really
used and not when defined in Xservers. 
 
 As I understand it, there should have been an xdmctl-:1 to which I
 could direct 
echo reserve
 to start up the second login screen.

From my tests it looks like you miss understood something ;)
 
 I also tried restarting my X server on vt7.  This didn't help.
 
 I have xfree86-common version 4.3.0-7, and am in a mostly testing
 system. 
 
 I may not have understood how this is supposed to work, but this is
 what I got from the docs.

I had a look at the /usr/share/doc/kdm/README.gz and

echo reserve  /var/run/xdmctl/xdmctl-$DISPLAY

works fine here (as user log in on $DISPLAY).  You should send
the reserve command to the xdmctl file responsible for your display.


I guess you get confused by the assumption that xdmctl
file should exist for every reserve setting in Xservers.

If you've some suggestion how to enhance kdms README please
send a patch.  Otherwise I suggest to close the bug report.

Achim
P.S.  The word 'seem' in the subject is an indication that
the report is better first send to debian-kde list to make
sure it's a bug ;)
 
 -- System Information:
 Debian Release: testing/unstable
   APT prefers testing
   APT policy: (990, 'testing'), (50, 'unstable')
 Architecture: i386 (i686)
 Kernel: Linux 2.4.24advncdfs
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
 
 Versions of packages kdm depends on:
 ii  debconf 1.4.22   Debian configuration management 
 sy
 ii  kdebase-bin 4:3.2.2-1KDE Base (binaries)
 ii  kdelibs44:3.2.2-2KDE core libraries
 ii  libart-2.0-22.3.16-5 Library of functions for 2D 
 graphi
 ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries 
 an
 ii  libfam0c102 2.7.0-5  client library to control the 
 FAM 
 ii  libgcc1 1:3.3.3-6GCC support library
 ii  libice6 4.3.0-7  Inter-Client Exchange library
 ii  libpam-runtime  0.76-19  Runtime support for the PAM 
 librar
 ii  libpam0g0.76-19  Pluggable Authentication Modules 
 l
 ii  libpng12-0  1.2.5.0-5PNG library - runtime
 ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime 
 v
 ii  libsm6  4.3.0-7  X Window System Session 
 Management
 ii  libstdc++5  1:3.3.3-6The GNU Standard C++ Library v3
 ii  libx11-64.3.0-7  X Window System protocol client 
 li
 ii  libxext64.3.0-7  X Window System miscellaneous 
 exte
 ii  libxrender1 0.8.3-7  X Rendering Extension client 
 libra
 ii  libxtst64.3.0-7  X Window System event recording 
 an
 ii  xbase-clients   4.3.0-7  miscellaneous X clients
 ii  xlibs   4.3.0-7  X Window System client libraries 
 m
 ii  zlib1g  1:1.2.1-5compression library - runtime
 
 -- debconf information:
 perl: warning: Setting locale failed.
 perl: warning: Please check that your locale settings:
   LANGUAGE = (unset),
   LC_ALL = (unset),
   LANG = en_US.UTF-8
 are supported and installed on your system.
 perl: warning: Falling back to the standard locale (C).
 locale: Cannot set LC_CTYPE to default locale: No such file or directory
 locale: Cannot set LC_MESSAGES to default locale: No such file or directory
 locale: Cannot set LC_ALL to default locale: No such file or directory
   kdm/stop_running_server_with_children: false
 * kdm/default_servers_nolisten_tcp: 
 * kdm/default_servers_100dpi: 
 * kdm/kdmrc: 
   shared/default-x-display-manager: kdm
 * kdm/default_nolisten_udp: 
   kdm/daemon_name: /usr/bin/kdm
   kdm/oldconfig: 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: Arts, network transparency, nas.

2004-05-04 Thread Achim Bohnet
rOn Monday 03 May 2004 11:22, Anders Ellenshøj Andersen wrote:
 I have a setup where I have a server hidden away close to my stereo set, and 
 a 
 laptop where I sit. The server has a soundblaster PCI 64 for output to the 
 stereo. (Old I know but I am just using it as a testbed for my final system.)
 
 I was trying to figure out the best way to set it up so I can use the laptop 
 to control the sound output from the server (which has ogg files). My first 
 idea was to install nas on the server, set up some kind of network filesystem 
 and mount it on my laptop, use kaffeine on my laptop for decoding, and 
 visualisations and stuff, and then output back to the server via nas. But 
 this stumpled when I found out xine didn't do nas output.
 
 Then I took a look at arts since I saw it claimed to have network 
 transparency 
 build in. But several hours of documentation scrounching couldn't explain to 
 me how to set this up. I see two options potentially related to network 
 transparency in KControl. First one is a simple tick-of setting, and the 
 second is the output driver where nas output seems to be available. I can't 
 understand how this can work without further setup. How does the nas driver 
 know which server to use for output? How does arts for that matter? The 

nas output method does it as documented in NAS documentation ;)
there a special environment variable (don't remember the name)
that tells NAS which nas server to use.  If not given it uses
DISPLAY.   Check NAS docs for further details.   Last time I tried
(guess around 3.0.*) nas output was okay for system sounds but
not for songs.

For network sound setup search the kde-multimedia list.
You should find several threads about this topic.

AFAIR if you send and 'URL' to remote artsd it interpreted
on the artsd server side (at least for wav files) and not
on the client side.  That was a killer 'bug' for my xterminal
environment.

In your case, with the sounds on the server
host, it may be that the right thing (tm) ;)
AFAIR you need to configure .mcop* to point to
the remote server running artsd (without KDE).
I would replace arts on your laptop with a script
that just copied the MCOP cookie from the server
and stored it on your laptop.  Then all arts/MCOP
aware apps should automaticly use the artsd on
the server.

Details what to do (too long ago for my memory)
are on the kde-multimedia list.

 network sound documentation for KDE sucks.

Agreed ;)

 Ideas anyone?

Well X11 guys seem to favor mas.  There is also a mas arts
output plugin, but I don't know how stable it is.  At least
it's not included in debian artsd. There's also NMN and JACK.
As usual you have the choice.  Last time I checked
kde-multimedia there was quite some discussion what to use
instead of arts for KDE4 in the KDE multimedia framework.

Achim
 
 Anders
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Bug#246110: konqueror: Fails to install with fresh install of sarge. Conflicting file /usr/bin/kfmexec

2004-04-27 Thread Achim Bohnet
On Tuesday 27 April 2004 11:30, Nick Hill wrote:
 Package: konqueror
 Version: 4:3.1.5-2
 Severity: normal
 
 This system has only testing in the sources.list pointing to a local 
 apt-cache server. The files on a hard drive have been written freshly 
 using debootstrap. This is a fresh sarge install.
 The system has been booted with Knoppix. i have then chrooted into the 
 fresh install to set up packages.
 
 I run
 apt-get install kde
 
 The installation process halts with the following:
 installed.)Unpacking konqueror (from
 .../konqueror_4%3a3.1.5-2_i386.deb) ...dpkg: error processing
 /var/cache/apt/archives/konqueror_4%3a3.1.5-2_i386.deb
 (--unpack): trying to overwrite `/usr/bin/kfmexec', which is also
 in package kdelibs-bindpkg-deb: subprocess paste killed by signal
 (Broken pipe)Errors were encountered while processing:
 /var/cache/apt/archives/konqueror_4%3a3.1.5-2_i386.debE:
 Sub-process /usr/bin/dpkg returned an error code (1)

will be fixed when konqueror 3.2.2 enters testing.

$ dpkg -L konqueror | grep kfmexec
$ dpkg -l konqueror
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version  Description
+++---
ii  konqueror3.2.2-1  KDE's advanced File Manager, Web 
Browser and Document Vi

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#126406: kppp: Alternative for using noauth as suggested by README

2004-04-22 Thread Achim Bohnet
On Thursday 22 April 2004 07:36, Ernst Kloppenburg wrote:
 On Wed, Apr 21, 2004 at 00:29:54 +0200, Achim Bohnet wrote:
  
  FWIW here's my alternative:
  to avoid setting noauth in /etc/peer/options I use
  
  allee[0] ~ # cat /etc/ppp/peers/kppp-options
  noauth
  
  and added 'call kppp-options' to kppps 'Customize pppd arguments'
  option.
  
  I assume that it would not be compilicated to patch kppp to
  add 'call kppp-options' as default for new connections and
  include the simple /etc/ppp/peers/kppp-option to the kppp pkg.
  
 
 yes, this seems to be the real solution. Better than any advice in a
 README. Who would make the change?

Well, pkgs maintainer always get a copy if one CC [EMAIL PROTECTED] ;)

I got a laptop with a working modem card working on linux to fix some
problems.  And realized

o noauth is already the default additional pppd option

o only possibility (I found) to get kpp to work with
  pap/chap is to suid it to root because kppp writes
  stuff to /etc/ppp/{pap,chap}-secrets (cp,modify,rename AFIAR)
  (looks like worth another bug report)

I don't have access to the laptop anymore.  So could you please try if

'noauth' instead of 'call kppp-options' works if you do

dpkg-statoverride --force --add  root 4754 root dip /usr/sbin/kppp # 
permanent
or
chmod 4754 /usr/sbin/kppp  # until next kppp upgrade
?

At least here in Germany all ISP require either PAP or CHAP
authentification (guess somewhere else too) and this makes
kppp unusable as it is now (kppp in 2.* was setuid root AFAIR
and 2.* was done by Ivan who also wrote the README.  Hmm..., aaahhh
http://lists.debian.org/debian-kde/2003/debian-kde-200303/msg00339.html
http://lists.debian.org/debian-kde/2003/debian-kde-200303/msg00316.html
http://lists.debian.org/debian-kde/2003/debian-kde-200310/msg00076.html
;)

I really suspect now that noauth okay but suid bit is missing.
If I miss the trick to the get PAP and/or CHAP working with
only sgid dip, please let me know.

Achim
P.S. When suid root is the route to go I would vote to keep
'noauth' instead of my 'call kppp-options' because it more secure.

 
 E. Kloppenburg
 
 -- 
 Ernst Kloppenburg
 Stuttgart, Germany
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#245149: kdelibs4: preinst script removes conffile system.kdeglobal

2004-04-21 Thread Achim Bohnet
Package: kdelibs4
Version: 4:3.2.2-1
Severity: serious
Justification: Policy 10.7.3


kdelibs4.preinst has

rm /etc/kde3/system.kdeglobals  /dev/null || true

This was formerly a conffile and we used it here to redefine
default fonts, etc.  Because KDE does not save a config option in
$KDEHOME if the systemwide option has the same value, all users
suddenly got debian default font (helvatica is ugly here).

As a fix I suggest to add dummy system.kdeglobals file:

# Note: Debian KDE pkg  3.2.1 DO NOT need the
# dir_* entries in [Directory] and TerminalApplication
# in [General] anymore.  Please delete them!

If system.kdeglobals was not touched people will not
be bothered and if the modified it the diff tells them
what's the right thing (tm) to do ;)

Achim
P.S curious: why not the simple rm -f?  AFIAK it does the same:
$ rm -f does-not-exists-here
$ echo $?
0

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (100, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.3-laptop-1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages kdelibs4 depends on:
ii  kdelibs-bin4:3.2.2-1 KDE core binaries
ii  kdelibs-data   4:3.2.2-1 KDE core shared data
ii  libart-2.0-2   2.3.16-3  Library of functions for 2D graphi
ii  libarts1   1.2.2-1   aRts Sound system
ii  libasound2 1.0.4-1   Advanced Linux Sound Architecture 
ii  libaudio2  1.6c-3The Network Audio System (NAS). (s
ii  libaudiofile0  0.2.6-3   Open-source version of SGI's audio
ii  libbz2-1.0 1.0.2-1   A high-quality block-sorting file 
ii  libc6  2.3.2.ds1-11  GNU C Library: Shared libraries an
ii  libcupsys2 1.1.20final+cvs20040330-1 Common UNIX Printing System(tm) - 
ii  libesd-alsa0 [ 0.2.29-1  Enlightened Sound Daemon (ALSA) - 
ii  libfam0c1022.7.0-5   client library to control the FAM 
ii  libgcc11:3.3.3-6 GCC support library
ii  libgcrypt1 1.1.12-4  LGPL Crypto library - runtime libr
ii  libglib2.0-0   2.2.3-1   The GLib library of C routines
ii  libgnutls7 0.8.12-5  GNU TLS library - runtime library
ii  libice64.3.0-7   Inter-Client Exchange library
ii  libjpeg62  6b-9  The Independent JPEG Group's JPEG 
ii  libmad00.15.0b-3 MPEG audio decoder library
ii  libogg01.1.0-1   Ogg Bitstream Library
ii  libpcre3   4.5-1.1   Perl 5 Compatible Regular Expressi
ii  libpng12-0 1.2.5.0-5 PNG library - runtime
ii  libqt3c102-mt  3:3.2.3-2 Qt GUI Library (Threaded runtime v
ii  libsm6 4.3.0-7   X Window System Session Management
ii  libstdc++5 1:3.3.3-6 The GNU Standard C++ Library v3
ii  libtasn1-0 0.1.2-1   Manage ASN.1 structures (runtime)
ii  libtiff3g  3.5.7-2   Tag Image File Format library
ii  libvorbis0a1.0.1-1   The Vorbis General Audio Compressi
ii  libvorbisfile3 1.0.1-1   The Vorbis General Audio Compressi
ii  libx11-6   4.3.0-7   X Window System protocol client li
ii  libxext6   4.3.0-7   X Window System miscellaneous exte
ii  libxml22.6.8-1   GNOME XML library
ii  libxrender10.8.3-7   X Rendering Extension client libra
ii  libxslt1.1 1.1.5-1   XSLT processing library - runtime 
ii  libxt6 4.3.0-7   X Toolkit Intrinsics
ii  xbase-clients  4.3.0-7   miscellaneous X clients
ii  xlibs  4.3.0-7   X Window System client libraries m
ii  zlib1g 1:1.2.1-5 compression library - runtime

-- no debconf information

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#237491: KDE applications select wrong font

2004-04-21 Thread Achim Bohnet
On Wednesday 21 April 2004 17:42, Andreas Tille wrote:
 Josh, thanks for your hints and sorry for my late answer.

[...]
 Now I leave it to you to find out which setting would care for the
 font as a reasonable default if somebody works like me and does
 not call kpersonalizer but instead run KDE appllications from
 Gnome or any other WM. ;-)

Ah, today is systemwide defaultfont day ;) We use since kde 3.0.x

/etc/kde3/kdesktoprc
[FMSettings]
StandardFont=Arial,10,-1,5,50,0,0,0,0,0

/etc/kde3/system.kdeglobals
...
[General]
...

StandardFont=Arial,10,-1,5,50,0,0,0,0,0
activeFont=Arial,10,-1,5,75,0,0,0,0,0
fixed=Courier New,10,-1,5,25,0,0,0,0,0
font=Arial,10,-1,5,50,0,0,0,0,0
menuFont=Arial,10,-1,5,50,0,0,0,0,0
toolBarFont=Arial,10,-1,5,50,0,0,0,0,0


/etc/kde3/konsolerc
[Desktop Entry]
defaultfont=Courier,10,-1,5,50,0,0,0,0,0
font=8
...

Substitute the fonts,size with your favorites.
Please note that upgrade to KDE 3.2.2-1 removes
/etc/kde3/system.kdeglobals (see #245149)

Achim

 Please tell me whether you need any further hints to debug the
 problem.
 
 Kind regards and thanks for your help
 
   Andreas.
 
 PS: Feel free to downgrade severity from important to normal because
 I think if this problem is documented in this bug report the
 severity can be lowered.
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#126406: kppp: Alternative for using noauth as suggested by README

2004-04-20 Thread Achim Bohnet
Hi,

FWIW here's my alternative:
to avoid setting noauth in /etc/peer/options I use

allee[0] ~ # cat /etc/ppp/peers/kppp-options
noauth

and added 'call kppp-options' to kppps 'Customize pppd arguments'
option.

I assume that it would not be compilicated to patch kppp to
add 'call kppp-options' as default for new connections and
include the simple /etc/ppp/peers/kppp-option to the kppp pkg.

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: How to determine konsole tab name?

2004-04-20 Thread Achim Bohnet
On Wednesday 21 April 2004 00:56, Rob Sims wrote:
 I want to be able to run different startup sequences when starting my 
 desktop that contains konsole windows with multiple tabs.  For example, 
 in a window with tabs hosta and hostb, I want my startup script to ssh 
 hosta and ssh hostb in their respective tabs.  I can find a list of 
 all tabs for the parent window, but can't discriminate among them.

Why don't you define konsole session for 'ssh hosta' etc.
Then konsole session mgmt does the restart for you.

$ cat .kde/share/apps/konsole/ssh-lost.desktop
[Desktop Entry]
Type=KonsoleApplication
Name=lost
Comment=slogin lost
Exec=ssh lost.in.space

Achim
[...]
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Bug#243611: crash: i broke the page selector

2004-04-19 Thread Achim Bohnet
On Wednesday 14 April 2004 02:43, Zack Cerza wrote:
 Package: kpdf
 Version: 4:3.2.1-1
 Severity: normal
 Tags: sid
 
 Open a PDF with multiple pages. In the listbox on the left, 1
 should be selected. Click on 1, just to give the listbox focus.
 Now press the down arrow on your keyboard a few times, and hit PgUp.
 Normally, this would just bring you to the previous page. Instead, it
 will probably get a SIGGSEGV.
 
 Doh!

FWIW: Same with kpdf from 3.2.2-1.

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#242520: kmail: temporary solution

2004-04-07 Thread Achim Bohnet
On Wednesday 07 April 2004 18:00, Gal Ben-Haim wrote:
 a temporary solution is to set the environment variable
 KDE_UTF8_FILENAMES=true, and to run kmail with: env LANG=he_IL kmail
 appearntly this fixes the problem + another problem that outgoing
 messages are by default encoded with UTF-8, which is not widely used
 with hebrew messages and needed to be changed on each outgoing message
 to either ISO8859-8-I or to CP1255, I guess that a pernament solution
 will be to have config options for default locale, like in

Hmm, doesn't this do what you want for outgoing mails?:
Settings - Configure kmail ... - Composer - Charset
Just add ISO8859-8-I and CP1255 before utf.
Achim

 mozilla-thunderbird where you can set the default incoming and outgoing
 locales..
 
 
 -- System Information:
 Debian Release: testing/unstable
   APT prefers unstable
   APT policy: (500, 'unstable')
 Architecture: i386 (i686)
 Kernel: Linux 2.6.4-1-686
 Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8
 
 Versions of packages kmail depends on:
 ii  kdebase-kio-plugins 4:3.2.1-1KDE I/O Slaves
 ii  kdelibs44:3.2.1-1KDE core libraries
 ii  ktnef   4:3.2.1-1KDE TNEF viewer
 ii  libart-2.0-22.3.16-3 Library of functions for 2D 
 graphi
 ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries 
 an
 ii  libfam0c102 2.7.0-5  client library to control the 
 FAM 
 ii  libgcc1 1:3.3.3-6GCC support library
 ii  libice6 4.3.0-7  Inter-Client Exchange library
 ii  libjpeg62   6b-9 The Independent JPEG Group's 
 JPEG 
 ii  libkcal24:3.2.1-1KDE calendaring library
 ii  libkdenetwork2  4:3.2.1-1KDE Network library
 ii  libkdepim1  4:3.2.1-1KDE PIM library
 ii  libksieve0  4:3.2.1-1KDE mail/news message filtering 
 li
 ii  libmimelib1 4:3.2.1-1KDE mime library
 ii  libpcre34.5-1.1  Perl 5 Compatible Regular 
 Expressi
 ii  libpng12-0  1.2.5.0-5PNG library - runtime
 ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime 
 v
 ii  libsm6  4.3.0-7  X Window System Session 
 Management
 ii  libstdc++5  1:3.3.3-6The GNU Standard C++ Library v3
 ii  libx11-64.3.0-7  X Window System protocol client 
 li
 ii  libxext64.3.0-7  X Window System miscellaneous 
 exte
 ii  libxrender1 0.8.3-7  X Rendering Extension client 
 libra
 ii  xlibs   4.3.0-7  X Window System client libraries 
 m
 ii  zlib1g  1:1.2.1-5compression library - runtime
 
 -- no debconf information
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#242614: kppp: Customizable Device List

2004-04-07 Thread Achim Bohnet
On Wednesday 07 April 2004 19:54, Benoit Panizzon wrote:
 Package: kppp
 Version: 4:3.1.5-1
 Severity: wishlist
 
 
 Yo kppp Maintainer.
 
 I use a System with IRDA, Bluetooth and an Lucent Winmodem (Linmodem)
 Those serial Devices are called
 
 /dev/ircomm0
 /dev/rfcomm0
 /dev/LTmodem

fixed-upstream!

In kppp of KDE 3.2.1 ircomm and rfcomm are included by default.
And it's possible to add more (e.g., I added /dev/ttySHSF0).

Achim
 
 and are not included in kppp's device list.
 The easy solution is just to add a softlink from /dev/modem to the wanted 
 device.
 But as I use all three connections quite often, I get a bit annoyed to change 
 that symlink every time I want to use 
 another device.
 
 As I read, the device list displayed by kppp is hardcoded in the headers 
 depending on the os kppp is compiled on.
 
 Would it be possible for further releases to add a user expandable device 
 list that would be saved in kppprc?
 
 -Benoit-
 
 
 -- System Information:
 Debian Release: testing/unstable
   APT prefers testing
   APT policy: (500, 'testing')
 Architecture: i386 (i686)
 Kernel: Linux 2.6.5
 Locale: LANG=de_CH, LC_CTYPE=de_CH
 
 Versions of packages kppp depends on:
 ii  kdelibs44:3.1.5-1KDE core libraries
 ii  libart-2.0-22.3.16-3 Library of functions for 2D 
 graphi
 ii  libaudio2   1.6c-3   The Network Audio System (NAS). 
 (s
 ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries 
 an
 ii  libfam0c102 2.7.0-5  client library to control the 
 FAM 
 ii  libfontconfig1  2.2.2-1  generic font configuration 
 library
 ii  libfreetype62.1.7-2  FreeType 2 font engine, shared 
 lib
 ii  libgcc1 1:3.3.3-5GCC support library
 ii  libpng12-0  1.2.5.0-5PNG library - runtime
 ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime 
 v
 ii  libstdc++5  1:3.3.3-5The GNU Standard C++ Library v3
 ii  libxcursor1 1.0.2-5  X Cursor management library
 ii  libxft2 2.1.2-6  FreeType-based font drawing 
 librar
 ii  libxrender1 0.8.3-7  X Rendering Extension client 
 libra
 ii  xlibmesa3-gl [libgl1]   4.2.1-12.1   Mesa 3D graphics library 
 [XFree86]
 ii  xlibs   4.3.0-7  X Window System client libraries 
 m
 ii  zlib1g  1:1.2.1-5compression library - runtime
 
 -- no debconf information
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#242520: kmail: the encoding settings doesn't affect the message's subject

2004-04-07 Thread Achim Bohnet
On Wednesday 07 April 2004 08:53, Gal Ben-Haim wrote:

FYI: Gal Ben-Haim reported it upstream: 
http://bugs.kde.org/show_bug.cgi?id=79254
Please vote ;)

Achim



Re: pkg-kde: commit - rev 90 - in trunk/packages/kdelibs/debian: . dh-make

2004-04-06 Thread Achim Bohnet
On Tuesday 06 April 2004 02:32, Christopher Martin wrote:
 On April 5, 2004 08:05 pm, Ben Burton wrote:
  IMO it's still worth encouraging it in Packaging.txt - even KDE users
  encouter the missing icons nowadays in the Debian menu, where all the
  KDE apps are duplicated (AIUI).  And for people who don't use KDE (or
  GNOME?), unless we supply icons in the debian menu files, they won't
  have any icons for these KDE apps at all.
 
  Even if you're not adding icons to kdebase right now, it's still worth
  encouraging packagers of new apps to do it properly. :)
 
 While we're on the subject of good practice, I've also noticed that 
 the .desktop files that constitute the KDE menu are spread 
 between /usr/share/applications/kde and /usr/share/applnk. Both locations 
 seem to work, but is there a preferred standard? I've always used applnk, 
 but with 3.2 applications/kde seems to have become more popular. If there 
 is a preferred place, then this might be worth mentioning in 
 Packaging.txt as well.

.desktop files in /usr/share/applications and /usr/share/applnk are not
identical.  So there is only one 'right' location depending if it follows
'old' kde desktop files rules or new 'xdg' rules.  

Of course the prefered way (tm) are now xdg compliant desktop files. 
That has the advantage that at least in gnome all kde apps should have
an icon without adding 84 times xpm them in debian specific .menu files ;)
(A kde desktop files has normally also much translations)

Achim

Achim
 
 Thanks,
 Christopher Martin
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: RFS: Need a sponsor for my konversation package

2004-04-06 Thread Achim Bohnet
On Tuesday 06 April 2004 17:05, Dominique Devriese wrote:
[...]
  and AFAICT, the kde.mk class in cdbs contains more up-to-date
  best-packaging-practices.  

Hi Nathaniel

Maybe you can write a small paragraph for inclusion in Packages.txt
about CDBS replacement of the dh_make rules file?
 
 Oh, I see, I didn't notice that you were using CDBS...  Never mind
 then :)

Achim

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: pkg-kde: commit - rev 90 - in trunk/packages/kdelibs/debian: . dh-make

2004-04-06 Thread Achim Bohnet
On Tuesday 06 April 2004 19:18, Dominique Devriese wrote:
 
 calc, scroll to the bottom :)
 
 Christopher Martin writes:
 
   If there is a preferred place, then this might be worth
   mentioning in Packaging.txt as well.
 
  AIUI, Packaging.txt is about packaging a normal, well-behaving kde
  app.  These use the kde build system, and as such, should
  automatically choose the right location, no ?
 
  Hmmm, I've built packages (3rd party/extragear stuff) that, by
  default, use either. oKle - applnk. Gwenview -
  applications/kde. Those using applnk may be in need of an update,
  either upstream or in the packaging, certainly, but for whatever
  reason plenty of apps still do use applnk (K3b and kopete, for
  instance), and may not bother to change since everything still
  appears to be working fine. 
 
 The Kopete developers consciously decided to not use the new dir,
 because they still support KDE 3.1.  I'm not sure about the rest.  In
 any case, if you encounter a package that uses applnk, that didn't
 consciously decide to do so, then it's most probably a bug in the
 Makefile.am.  For example, in August, someone committed this change to
 kdeedu/kig/kig/Makefile.am:
 diff -u -r1.23 -r1.24
 --- Makefile.am 27 Jun 2003 12:26:56 -  1.23
 +++ Makefile.am 29 Aug 2003 19:59:44 -  1.24
 @@ -27,8 +27,7 @@
  kig_LDADD   = $(LIB_KPARTS)
 
  # this is where the desktop file will go
 -shelldesktopdir   = $(kde_appsdir)/Edutainment/Mathematics
 -shelldesktop_DATA = kig.desktop
 +xdg_apps_DATA = kig.desktop
 
  # this is where the shell's XML-GUI resource file goes
  shellrcdir   = $(kde_datadir)/kig
 The upstream authors should do something similar ( and make sure they
 have a recent admin/ dir, so that xdg_appsdir is defined, of course ).

.. and make sure the desktop file has a Categories= entry. Because
that whats used AFAIU to put the app in a (sub)menu.

http://www.freedesktop.org/standards/menu-spec/menu-spec-0.8.html

http://freedesktop.org/Standards/desktop-entry-spec/desktop-entry-spec-0.9.4.html

Achim
 
  Thus a small mention in Packaging.txt might help to nudge packagers
  (especially new packagers) towards the correct location, in case
  their sources still default to applnk, for whatever reason.
 
 Agreed, care to write the patch, perhaps ?
 
  Perhaps also the /u/s/doc/kdelibs4-dev/dh-make/debiandirs should add
  the following:
  export kde_appsdir=/usr/share/applications/kde
 
 No, this would be wrong.
 
  The only problem with this is that apps that had hitherto created a
  subdirectory in /u/s/applnk (like Multimedia, or Graphics) would now
  do the same in /u/s/applications/kde...
 
 Indeed.
 
  One final thing. Packaging.txt currently contains an elaborate
  description of how to take the kdelibs4-dev debianrules script,
  place it in MYPACKAGE_SRCDIR/debian/ and convert it, using perl,
  into the debian/debiandirs file which then sets crucial
  variables. However, kdelibs4-dev doesn't provide debianrules
  anymore, but debiandirs directly (in the dh-make directory), so
  unless I'm mistaken there's no need for any perl kung-fu. 
 
  All I've been doing is copying the
  /u/s/doc/kdelibs4-dev/dh-make/debiandirs file into
  MYPACKAGE_SRCDIR/debian/ and then adding:
 
  -include debian/debiandirs
 
  in debian/rules before any targets are defined, and it works
  well. 
 
  Am I doing something wrong, or can the Packaging.txt
  instructions be simplified?
 
 Well, I agree with you that either debianrules should be installed
 instead of debiandirs, or Packaging.txt should be adapted.  I'm not
 certain what calc wanted to do, but installing debianrules instead of
 debiandirs seems like the best solution to me personally. Anyway,
 calc, please shed some light on this !
 
 cheers
 domi
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: Quanta, new project

2004-04-05 Thread Achim Bohnet
On Sunday 04 April 2004 23:01, Alan Chandler wrote:
 I am failing totally to set up a project with a set of files which should 
 become my web site.  Can someone help be do so.
 
 I have a set of files that will make up my personal web site.  They are a 
 revamped version of http://www.chandlerfamily.org.uk (or rather where this 
 appears to be).  I have been using subversion to version control the set of 
 files.  The checkout current version is sitting in ~/blue (blue being the 
 name of the project).  I want to turn this directory into a quanta project by 
 importing all the files. 
 
 When ever I try to do this I get an error message saying quanta can't do 
 something with /home/alan/file:/home/alan/blue
 
 Is this a quanta problem or how I am filling in one of the dialog boxes?

Looks like a qanta problem: see

http://lists.kde.org/?l=kde-cvsw=2r=1s=andras+coolo+file%3Aq=b

For the final status search or ask on the quanta list.  I just remembered
that I saw something similar on kde-cvs.

Achim
 -- 
 Alan Chandler
 [EMAIL PROTECTED]
 First they ignore you, then they laugh at you,
  then they fight you, then you win. --Gandhi
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: customize menu all users

2004-04-02 Thread Achim Bohnet
On Friday 02 April 2004 01:21, Chris Cheney wrote:
 On Thu, Apr 01, 2004 at 08:48:31AM -0300, Raul Montagne wrote:
   Note that the directory /usr/local/share/applications may not exist [1], 
   but
   you need only create it, and it will be searched by the KDE menu system.
  1.-which is the search order of KDE for the menus?
 
 I am not certain, but if it doesn't look in /usr/local first it is buggy
 since the freedesktop.org basedir spec states it must look there first.

$ kde-config --types
...
xdgconf-menu - XDG Menu layout (.menu files)
xdgdata-apps - XDG Application menu (.desktop files)
xdgdata-dirs - XDG Menu descriptions (.directory files)
$ kde-config --path xdgdata-app
/home/ach/.local/share/applications/:/usr/local/share/applications/:/usr/share/applications/

Yupp, /usr/local before /usr ;)

Raul, note kde-config only shows directories of the search path that exists
to prevent unnecessary lookups.

Achim
 
  2.- the applications I want to *add* in the KDE menu, I would put in
  /usr/local/share/applications. But if I want to weed out some
  applications?
  I have to weed out this apps from the KDE menu, in the very same
  /usr/share/application (for KDE 3.2) isn't it?
 
 You should be able to simply put a .desktop file into the local
 directory with the same name as the one you want to replace with the
 NoDisplay=True value set in the .desktop file
 
  3.- (last...for the time being) where, how to customize a standard
  panel for a machine for every user?
 
 I think this is set via the list in /usr/share/apps/kicker/default-apps
 if so you should be override it via /usr/local as well.
 
 Chris
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: Bug#240288: KDE 3.2.1 - Debian Testing?

2004-03-31 Thread Achim Bohnet
On Wednesday 31 March 2004 17:51, Dominique Devriese wrote:
 
 CC'ing the kdelibs and kdebase maintainer to hear his opinion on the
 issue.  Please keep the CC to #240288.
 
 Clemens Brunner writes:
 
  Hi Dominique!  I've been waiting for KDE 3.2.1 to move into Debian
  Testing for weeks now, and it finally seemed to happen - until you
  filed your fake bug, saying that you thought it was probably not a
  good idea to move kdelibs into Testing.
 
 Yes, I'm sorry, I should have provided more info in the report, but I
 had little time when I was writing it.
 
  Could you explain why you filed that bug? 
 
 kdebase is not yet ready for testing, and it's not a good idea for
 sarge to have a different kdebase than kdelibs version, for various
 reasons.  I just want to avoid the sarge release hitting us at a point
 where kdelibs is at 3.2, and kdebase at 3.1.  If kdebase is ready, I
 have no problem with both propagating to testing.

How about the combination arts 1.2 from KDE3.2.1 release + KDE* 3.1.5
I've just seen on debian-release:

snip-
On Sun, Mar 28, 2004 at 10:42:50PM -0500, Nathanael Nerode wrote:
 These should both work right now.

 easy mono/0.30.2-1 mcs/0.30.2-1

 easy arts/1.2.1-2 xmms-arts/0.7.1-1

Added.

-- 
Steve Langasek
postmodern programmer
snap-

AFAIU this means arts from 3.2.1 enters testing in two days according
to http://packages.qa.debian.org/a/arts.html.  Does this
make sense without kde* 3.2.1?

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: customize menu all users

2004-03-31 Thread Achim Bohnet
On Wednesday 31 March 2004 18:31, Raul Montagne wrote:
 Which is the way to customize the KDE menu (big K) for all the users
 in a machine.
 Is it there something as .profile, or some kde-menu.config in
 /etc/skel ?
 KDE v. 3.1

Add / modify desktop files in:

KDE 3.1:  /usr/share/applnk/...
KDE 3.2:  /usr/share/applications/*

Achim

 Debian...mixture of stable-testing
 thanks
 talueguito
 raul
 -- 
 
   RAUL MONTAGNE   
 Phone   +55-81-21268450 int. 2266 Fax +55-81-32740359 
 Laboratorio de Fisica Teorica e Computacional - DF - UFPE
 50670-901 Recife PE   BRASIL
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: KDM problem

2004-03-30 Thread Achim Bohnet
On Monday 29 March 2004 09:07, Anders Ellenshøj Andersen wrote:
 On Monday 29 March 2004 08:43, you wrote:
  On Sun, Mar 28, 2004 at 11:44:52PM +0200, Anders Ellensh?j Andersen wrote:
  With the amount of people who choke on this, there can't possible be a
   good enough excuse for it to not give you a kde session by default.
 
  I wholeheartedly agree.  I've been using Linux since '97, Debian since
 
 Ok enough mumbling about.
 
 I have filed a bug report on KDM.

that's wrong ;) Please reassign to ksmserver.

Achim
 
 Anders

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Bug#238135: keyboard shortcuts ctrl+[ and ctrl+] don't work when konqueror started from the menu

2004-03-18 Thread Achim Bohnet
On Monday 15 March 2004 15:27, Amit Shah wrote:
 Package: konqueror
 Version: 4:3.2.1-1
 Severity: normal
 
 A very queer bug: Ctrl+[ and Ctrl+] don't work when konqueror is started
 from the K menu. When konqueror is started from the run command dialog
 (Alt+F2), the keyboard shortcuts work fine.

Crtl-[ and Crtl-] work as expected here (testing + KDE 3.2.1 + xf 4.3 from
unstable) when started from k-menu or kicker and command line. 
I created the second tab with ctrl-shift-n and with file- new tab.

Achim
 
 
 -- System Information:
 Debian Release: testing/unstable
   APT prefers unstable
   APT policy: (500, 'unstable')
 Architecture: i386 (i686)
 Kernel: Linux 2.6.3-mm3
 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
 
 Versions of packages konqueror depends on:
 ii  kcontrol4:3.2.1-1KDE Control Center
 ii  kdebase-kio-plugins 4:3.2.1-1KDE I/O Slaves
 ii  kdelibs44:3.2.1-1KDE core libraries
 ii  kdesktop4:3.2.1-1KDE Desktop
 ii  kfind   4:3.2.1-1KDE File Find Utility
 ii  libart-2.0-22.3.16-1 Library of functions for 2D 
 graphi
 ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries 
 an
 ii  libfam0c102 2.7.0-5  client library to control the 
 FAM 
 ii  libgcc1 1:3.3.3-2GCC support library
 ii  libice6 4.3.0-5  Inter-Client Exchange library
 ii  libjpeg62   6b-9 The Independent JPEG Group's 
 JPEG 
 ii  libkonq44:3.2.1-1Core libraries for KDE's file 
 mana
 ii  libpcre34.5-1.1  Perl 5 Compatible Regular 
 Expressi
 ii  libpng12-0  1.2.5.0-5PNG library - runtime
 ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime 
 v
 ii  libsm6  4.3.0-5  X Window System Session 
 Management
 ii  libstdc++5  1:3.3.3-2The GNU Standard C++ Library v3
 ii  libx11-64.3.0-5  X Window System protocol client 
 li
 ii  libxext64.3.0-5  X Window System miscellaneous 
 exte
 ii  libxrender1 0.8.3-7  X Rendering Extension client 
 libra
 ii  xlibs   4.3.0-5  X Window System client libraries 
 m
 ii  zlib1g  1:1.2.1-5compression library - runtime
 
 -- no debconf information
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Bug#237026: Please support a kind of polling for xdms

2004-03-18 Thread Achim Bohnet
On Tuesday 09 March 2004 13:12, Torsten Knodt wrote:
 Package: kdm
 Severity: wishlist
 Tags: sid
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hello,
 first, as far as I understood, kdm is a fork of xdm. Thats why I filed this
 wish against kdm. If not, please reassign to xdm.
 It would be nice, if there would be a way to poll for other xdms, which cant
 be reached by broadcasts.

Polling xdms?  If you mean getting a chooser or login window from
another host, that's not the task of kdm but of the xserver.  Or
 According to the xaccess help, there is only one entry matching. As a change
 of minimal impact, I suggest to extend the CHOOSER syntax in a way, that
 BROADCAST isnt an alternate to the host list, but a reserved word in the
 list.

If you mean that the chooser is provided by the local kdm, search for
ChooserHosts in /etc/kde3/kdm/kdmrc and you'll find your wish already
implemented.

Let us know if this fixes you wishlist.

Achim

 
 With kind regards
  Torsten
 
 - -- System Information:
 Debian Release: testing/unstable
   APT prefers unstable
   APT policy: (990, 'unstable')
 Architecture: ? (i586)
 Kernel: Linux 2.6.3
 Locale: LANG=C, LC_CTYPE=C
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.2.4 (GNU/Linux)
 
 iD8DBQFATbSpX1/CjdwsodIRAv3cAJ4mH6IVc24ckipvHje6Il9ZeyMe/QCbB15t
 1bSM7Ql7RElUcQzGBqiStSA=
 =dLE7
 -END PGP SIGNATURE-
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: KDE_3_2_BRANCH: kdegraphics/kpdf

2004-03-16 Thread Achim Bohnet
On Friday 12 March 2004 17:37, Stephan Kulow wrote:
 CVS commit by coolo: 
 
 try to find /etc/kpdfrc
 
 
   M +6 -1  configure.in.in   1.5.2.1
 
 
 --- kdegraphics/kpdf/configure.in.in  #1.5:1.5.2.1
 @@ -37,4 +37,9 @@
  AC_SUBST(LIBPAPER_LIBS)
  
 -
  AC_CHECK_FUNCS(fseek64 mkstemp mkstemps popen)
 +
 +AC_FIND_FILE(xpdfrc, [/etc /usr/local/etc], xpdfrc)

Care to add /etc/xpdf/?  Debian stores xpdfrc there.

Achim
 +if test $xpdfrc != NO; then
 +  AC_DEFINE_UNQUOTED(SYSTEM_XPDFRC, $xpdfrc/xpdfrc, [Define the location 
 your xpdfrc])
 +fi
 +
 
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: Using deb and CVS version alternately?

2004-03-05 Thread Achim Bohnet
On Thursday 04 March 2004 23:03, Michael Schuerig wrote:
 
 I've got a break-neck question...
 Is it possible to keep one KDE 3.2 installed from debs and another build 
 from CVS (in /usr/local/kde) in parallel and use them alternately? If 
 anyone has tried such a thing, I'd be interested to hear who you did 
 it.

Just make sure that KDEHOME is not ~/.kde when you
login to your own KDE build (or be prepared that sooner or later
some KDE 3.2 apps show strange effects after you used KDE cvs.)

 I know that it's possible to keep another KDE in jail (that is in a 
 chrooted environment) that's what I'm already doing. I'm considering a 
 more thrilling experience.

Bad timing.  Not that much new in CVS compared to KDE 3.2(.1).  Try
again later ;)

Achim
 
 Michael
 
 -- 
 Michael Schuerig What if the enemy / Isn't in a distant land
 mailto:[EMAIL PROTECTED] What if it lies behind / The voice of command
 http://www.schuerig.de/michael/   --Ani DiFranco, Roll With It
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: Problems with kdeprint under KDE 3.2 from experimental

2004-03-03 Thread Achim Bohnet
On Wednesday 03 March 2004 15:35, Bruce Miller wrote:
 I am trying to track down the source of the return of problems with 
 kdeprint.
 
 linuxprinting.org has declared my Canon multifunction printer to be a 
 Linux paperweight. I therefore run it off a Windows box linked to my 
 main Linux host with Samba.
 
 The first problem I have found is:
 [EMAIL PROTECTED]:/home/bruce# dpkg-reconfigure kdeprint
 sh: line 1: /usr/bin/kdm-update-menu: No such file or directory
 [EMAIL PROTECTED]:/home/bruce#

Same here. 

There's a /etc/menu-methods/kdm from June 2002 that's not containted
in any pkg.  My guess is that it's from an old version of kde. It
refers to /usr/bin/kdm-update-menu that got removed as it should
on upgrade.

Anyone knows what happens on upgrade with config files that
a no longer in newer version of a pkg? Looks like they are
kept on disk.   Does policy allow to remove config files
that are no longer used?  If yes, we should file a bug report
against kdm.

Mhmm,  /etc/menu-methods/kicker is form pkg kicker, but every
kde apps that has a 'start/open/view with ..' dialog uses the
menu tree. Looks like /etc/menu-methods/kicker should go to
kdelibs-bin or something a pkg like that that every kde app
pulls in via Depends

Achim

 I shall continue troubleshooting the overall problem and will report any 
 relevant findings to this list.
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: Report: KDE 3.1.x/Woody Screensaver Situation

2004-03-03 Thread Achim Bohnet
On Tuesday 02 March 2004 03:29, Nick Boyce wrote:
 Re: my previous reports to this list (Jan.2003  Feb.2004) about how on 
 my Woody system with KDE 3.1.x,  (a) the OpenGL screensavers were very 
 slow (unaccelerated), and (b) most of the ~160 screensavers listed in 
 Kcontrol don't work at all :
 http://lists.debian.org/debian-kde/2003/debian-kde-200301/msg00718.html
 http://lists.debian.org/debian-kde/2004/debian-kde-200402/msg00177.html
 
 I've been experimenting, and have made two improvements in the situation 
 :
 
 1)  I now have beautiful glorious fully accelerated GL screensavers (the 
 KDE ones anyway); I fixed the problem by installing a package I hadn't 
 previously realised I needed : libglide3, Graphics library for 3Dfx 
 Voodoo based cards;  I suppose users of other brand graphics cards 
 don't need any such helper library (or do they ?).
 
 2)  I managed to remove the entries for approx 145 screensavers which 
 don't work from the list offered by the screensaver applet of Kcontrol 
 (leaving 29 working native KDE screensavers).  The screensavers listed 
 by Kcontrol are those for which a .desktop file exists in 
 /usr/share/applnk/System/ScreenSavers, so I just moved the broken 
 ones out of the way.

Looks like kscreensaver should require xscreenssaver* not only recommend
them.  Or split the package should be split into two pkgs native/external
screen savers.
 
 I tried to find out why exactly the broken screensavers are broken, and 
 noted that the first few lines of a working screensaver .desktop file 
 are like this :
 
   /usr/share/applnk/System/ScreenSavers$ more KPyro.desktop
   [Desktop Entry]
   Encoding=UTF-8
   Exec=kpyro.kss
   Icon=kscreensaver
   Type=Application
   Actions=Setup;InWindow;Root
   Name=Pyro
 
 and the Exec line names an executable file to be run :
 
   /usr/share/applnk/System/ScreenSavers$ which kpyro.kss
   /usr/bin/kpyro.kss

I've tried to run krandom.kss and it refused to run.  I've started
kswarm as root - okay; ^C - keyboard dead :(

Looks like the *.kss are not meant to be run standalone. AFAIF FHS
requires/suggests to put the into /usr/lib/kscreensaver/

http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA
 
 but for a broken screensaver (e.g. Zoom), the named executable :
 
   /usr/share/applnk/System/ScreenSavers$ more duff/zoom.desktop
   [Desktop Entry]
   Encoding=UTF-8
   Exec=zoom
   Icon=kscreensaver
   Type=Application
   Actions=InWindow;Root;Setup
   Name=Zoom
 
 doesn't exist in any directory on the path on my system :
 
   /usr/share/applnk/System/ScreenSavers$ which zoom
   /usr/share/applnk/System/ScreenSavers$
 
 I did a search of the system, and discovered that the zoom screensaver 
 module *is* on my system, in a place which isn't on the path, so it 
 doesn't work :
 
   /usr/lib/xscreensaver/zoom

Ah, according to FHS ;)

 
 Thus enlightened, I tried editing the zoom.desktop file to add the full 
 path for the screensaver module to each Exec line (there are 4 such 
 lines).  This fixed the basic brokenness of the Zoom saver, such that 
 it will now actually work if selected in Kcontrol - *but* didn't fix 
 the Kcontrol screensaver preview pane (which stays dark), or the Test 
 button (which does nothing at all)... and the Setup button just says 

Did the preview and/or and test button ever work with xscreensavers?
If this is/was ever supported I assume that two of the exec lines
should have special options for xscreensaver to tell it run embeded
in a widget in kcontrol or in test more.  Maybe some options have
changed?

 No configuration available for Zoom.   This situation seems to be the 
 same for each of the xscreensaver modules - all the .desktop files are 
 broken in the same way, and all can be fixed by adding the full path 
 to the executable module.
 
 So where does zoom.desktop come from ?
 
 glimmer:~# dpkg -S zoom.desktop
 kscreensaver: /usr/share/applnk/System/ScreenSavers/zoom.desktop
 
 glimmer:~# apt-cache policy kscreensaver
 kscreensaver:
   Installed: 4:3.1.4-0woody1
   Candidate: 4:3.1.4-0woody1
   Version Table:
  *** 4:3.1.4-0woody1 0
 500 http://download.kde.org stable/main Packages
 100 /var/lib/dpkg/status
 
 Okay  it's a fault in the kscreensaver package at download.kde.org.
 Should I bug this ?   Ralf ?
 
 End of report.
 
 Questions:  
 (1) Should I fix all 145 broken xscreensaver .desktop files - or just 
 move the xscreensaver modules to a directory on the path ?  

IMO: file a bug report that the desktop files need a path.  I don't
think that 3.1.4 get's fixed but problem is still in 3.2.0-1 pkgs.

 That would allow them to be selected directly from Kcontrol.
 
 (2) After that, is there any further need for the XScreenSaver.desktop 
 file ?  Its only purpose seems to be to allow Kcontrol to run 
 xscreensaver -setup to give the horrible Motif-y xscreensaver 
 configuration dialog ... which I suppose *does* provide the ability to 
 have a subset of the 

Re: admin/debianrules kde_configdir issue

2004-02-25 Thread Achim Bohnet
On Wednesday 25 February 2004 11:01, Chris Cheney wrote:
 I am trying to decide whether I should revert the move of kde_configdir
 from /etc/kde3 to /usr/share/config that was changed in experimental. It
 has caused at least one noticable problem, kdm doesn't use the normal
 kde path lookup like everything else so you can't override its config
 files in /etc/kde3. It also is probably a policy violation to have config
 files in /usr/share even though they can be overriden in /etc/kde3. Also
 since the config files disappeared from /etc/kde3 upgrades from earlier
 kde 3.x releases will keep their old config files in /etc/kde3 and use
 them instead of the newer ones in /usr/share/config.
 
 If I revert back to /etc/kde3 I think I will need to make a symlink from
 /usr/share/config - /etc/kde3 so that I still won't need /etc/kderc and
 /etc/kde3/system.kdeglobals. I will probably also need to check and
 remove any existing /etc/kderc /etc/kde3/system.kdeglobals files...
 
 Any comments?

Hi Chris,
I still think that /etc/kde3  /usr/share/config symlink  ...
is the right thing (tm) to do.

I'll agree with Ben that migration can be a bit tricky.
Are packages in experimental required to provide a smooth
upgrade path too?

Btw: is Xfree86 4.3 a release goal for sarge?  Some of the
experimental kde 3.2 pkgs depend already on 4.3.

Achim
 
 Thanks,
 Chris
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#233775: kdm stores/uses config files in /usr/share/config/kdm

2004-02-19 Thread Achim Bohnet
Package: kdm
Version: 4:3.2.0-0pre1v1
Severity: normal


kdm 3.2.0 from people repo installs config files in /usr/share/config/kdm.
The files in this this have additional hardcoded path to the same dir.
Unfortunately /usr/share/config is _not_ a link to /etc/kde3 but a real
dir.

Strange is that kdm ignores the /etc/kde3/kdm/kdmrc despite the fact
that kde-config --path config lists:
/root/.kde/share/config/:/etc/kde3/:/usr/share/config/

Proposed solution:  Continue to not install /etc/kderc and make 
/usr/share/config
a link to /etc/kde3.   Additionally the patch in kdm/* should be
adjusted to use /etc/kde3/... paths and not /usr/share/config.

Achim

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux allee 2.4.22-20030830-marlow #1 l�r aug 30 21:17:29 CEST 2003 i686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages kdm depends on:
ii  debconf  1.3.22  Debian configuration management sy
ii  kdelibs4 4:3.2.0-0pre1v1 KDE core libraries
ii  libart-2.0-2 2.3.16-1Library of functions for 2D graphi
ii  libc62.3.2.ds1-11GNU C Library: Shared libraries an
ii  libfam0c102  2.6.10-6client library to control the FAM 
ii  libgcc1  1:3.3.3-0pre3   GCC support library
ii  libpam0g 0.76-15 Pluggable Authentication Modules l
ii  libpng12-0   1.2.5.0-4   PNG library - runtime
ii  libqt3c102-mt3:3.2.3-2   Qt GUI Library (Threaded runtime v
ii  libstdc++5   1:3.3.3-0pre3   The GNU Standard C++ Library v3
ii  libxrender1  0.8.3-5 X Rendering Extension client libra
ii  xbase-clients4.2.1-12.1  miscellaneous X clients
ii  xlibs4.2.1-12.1  X Window System client libraries
ii  zlib1g   1:1.2.1-3   compression library - runtime

-- debconf information excluded

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Bug#233775: kdm stores/uses config files in /usr/share/config/kdm

2004-02-19 Thread Achim Bohnet
On Thursday 19 February 2004 23:53, Chris Cheney wrote:
 On Thu, Feb 19, 2004 at 11:08:50PM +0100, Achim Bohnet wrote:
  Package: kdm
  Version: 4:3.2.0-0pre1v1
  Severity: normal
  
  
  kdm 3.2.0 from people repo installs config files in /usr/share/config/kdm.
  The files in this this have additional hardcoded path to the same dir.
  Unfortunately /usr/share/config is _not_ a link to /etc/kde3 but a real
  dir.
  
  Strange is that kdm ignores the /etc/kde3/kdm/kdmrc despite the fact
  that kde-config --path config lists:
  /root/.kde/share/config/:/etc/kde3/:/usr/share/config/
  
  Proposed solution:  Continue to not install /etc/kderc and make 
  /usr/share/config
  a link to /etc/kde3.   Additionally the patch in kdm/* should be
  adjusted to use /etc/kde3/... paths and not /usr/share/config.
 
 Installing directly into /etc/kde3 is not a good solution for the
 upstream config files since dpkg at various times decides not to
 install the config files at all, which completely breaks KDE. This has
 been the source of problems with KDE in Debian for a long time. However,
 I will bug upstream about the problem with respect to it not looking in
 kde-config --path config.

Unfortunately that's no solution (IMHO). First time KDE users would have
an empty /etc/kde3 and therefore even installing, e.g., and Xservers
file in /etc/kde3/kdm does not help because kdmrc explicitely
refers to Xservers in /usr/share/config/kdm.   Second: to customize
things one would have to do a cp /usr/share/config/whatever /etc/kde3/
and the edit it.  Aren't we here in trouble with policy?!

AFAIU only reason for dpkg not to install a config file is when
the old and new pkg had the config file but the config file does
not exist when a pkg was updated.  But then the apps did also
not work before the update.

So either dpkg has a not yet reported RC bug or KDE upgrade
is broken.   Anyone recall another reason dpkg does not install
a config file beside the one I described above?

Achim
 
 Chris
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: kdeextragear, and kdenonbeta

2004-02-18 Thread Achim Bohnet
On Wednesday 18 February 2004 16:40, Alejandro Exojo wrote:
 Hi.
 
 I know that kdeextragear* and kdenonbeta are not official KDE modules, but 
 some applications are packaged for Debian, but some interesting others 
 (kimdaba, amarok, ...) are not.

Well there are no official pkgs, but ;) I've announced woody/sid
kimdaba KDE 3.2 pkg on the kimdaba list. And I've on my system a
amorak pkg.  AFAIR  I've found them on the amarok home page.

I hope that kalyxo.org will sometime in the future provide a
pool of all those non-official kde pkgs for woody and sarge
(when sarge is called stable) ;)

Achim

 I'm packaging konserve [*], which is in kdenonbeta, and upstream will release 
 a new version next monday. I realized that working without a SVN/CVS 
 repository is a bit tricky, so I considered different options:
 
 a) Use a local repository in my machine. Problem: it doesn't allows others to 
 check my sources.
 b) Open an alioth project, as many others, just for konserve. Problem: I plan 
 to package others in the future, as soon as my skills improve, and I don't 
 want to create a project for each.
 c) Use KDE's CVS repository.
 d) Ask Qt/KDE mantainers what's their opinion. Maybe someday my package moves 
 to an official module, and it's interesting to keep history. I don't know 
 possible benefits or possible problems of this option, so that's the reason 
 I'm asking to you ;-).
 
 Any suggestions?
 Thanks in advance.
 
 
 [*] It isn't in Debian yet because my sponsor is at Malaga's conference, and 
 he has been a bit busy this days, but a lot of initial minor fixes had been 
 done. If you are curious:
 
 deb http://darkshines.net/debian unstable konserve
 deb-src http://darkshines.net/debian unstable konserve
 
 -- 
 Alex
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: debiandir

2004-02-17 Thread Achim Bohnet
On Tuesday 17 February 2004 02:29, Ben Burton wrote:
 
  I'm no expert in makefiles but doesn't the include cause the
  debian/debiandirs call to be made?
 
 This is the way it has always worked for me.
 
 (i.e., the include calls the file to be made and then included in the
 same make run).

O, right hand side of include is generated if missing
(file:/usr/share/doc/make-doc/make_3.html#SEC16). And it
looks like variable expansion is done later.

allee(0) ~ $ cat mm
-include mm.inc

mm.inc: /bin/echo
/bin/echo bla=hello   mm.inc

all:
echo $(bla)world

allee(0) ~ $ rm mm.inc ; make -f mm all
/bin/echo bla=hello   mm.inc
echo hello world
hello world
allee(0) ~ $ 


So everything should be fine.

Achim
 
 Ben.
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



debiandir

2004-02-16 Thread Achim Bohnet
Hi,
I've seen Chris updating debianrules CVS and wondered how to
handle this in other kde pkgs.   I had a look that svn trunk:
debiandirs is ...
o is not in svn
o created and removed by rules
o -included'ed in rules file.

What confused me is that for the first run  -include debian/debiandirs
can't succeed because it not there.  The debian/debiandir rule
that creates the file does not fail (to force another build run).
Now configure would be called with an empty config_kde.

So shouldn't the debiandir rules read:

debian/debiandirs: admin/debianrules
perl -w admin/debianrules echodirs  debian/debiandirs
false

to force another debuild run with an existing debian/debiandirs?

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



enable-final

2004-02-16 Thread Achim Bohnet
Hi,
new debianrules does not set --enable-final.  Any special reason
why it's no longer the default?

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



kdeextragear-3/kdebluetooth/debian

2004-02-16 Thread Achim Bohnet
CVS commit by ach: 

Fix rules so debuild works in extragear environment


  M +18 -7 rules   1.5


--- kdeextragear-3/kdebluetooth/debian/rules  #1.4:1.5
@@ -12,10 +12,20 @@
 DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 
+ifeq $(wildcard ./admin) 
+# Builds in kdeextragear-3
+CVS_BUILD=true
+deb_cfg_dir=..
+deb_src_dir=.
+else
+# ./admin exists - build outside kdeextragear-3
+deb_cfg_dir=.
+deb_src_dir=kdebluetooth
+endif
+
 -include debian/debiandirs
 
-debian/debiandirs: admin/debianrules
-perl -w admin/debianrules echodirs  debian/debiandirs
+debian/debiandirs: $(deb_cfg_dir)/admin/debianrules
+perl -w $(deb_cfg_dir)/admin/debianrules echodirs  debian/debiandirs
 
-CVS_BUILD=true
 ifneq (, $(findstring true,$(CVS_BUILD)))
   configkde += --enable-debug=full
@@ -38,5 +48,5 @@
 #
 #   # run configure with build tree $(objdir)
-./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) 
$(configkde)
+cd $(deb_cfg_dir)  ./configure --host=$(DEB_HOST_GNU_TYPE) 
--build=$(DEB_BUILD_GNU_TYPE) $(configkde)
 
 touch configure-stamp
@@ -61,12 +71,13 @@
 dh_testroot
 rm -f build-stamp configure-stamp
+rm -f debian/debianrules
 
 # Add here commands to clean up after the build process.
 -$(MAKE) distclean
 ifneq $(wildcard /usr/share/misc/config.sub) 
-cp -f /usr/share/misc/config.sub config.sub
+cp -f /usr/share/misc/config.sub $(deb_cfg_dir)/config.sub
 endif
 ifneq $(wildcard /usr/share/misc/config.guess) 
-cp -f /usr/share/misc/config.guess config.guess
+cp -f /usr/share/misc/config.guess $(deb_cfg_dir)/config.guess
 endif
 
@@ -92,5 +103,5 @@
 dh_testdir
 dh_testroot
-dh_installchangelogs ChangeLog
+dh_installchangelogs $(deb_src_dir)/ChangeLog
 dh_installdocs
 dh_installexamples




Re: ro svn checkout of svn.debian.org/svn/pkg-kde/

2004-02-12 Thread Achim Bohnet
On Thursday 12 February 2004 04:59, Chris Cheney wrote:
 On Wed, Feb 11, 2004 at 11:42:13PM +0100, Achim Bohnet wrote:
  Hi,
  
  what's the method to check out a ro copy of svn pkg-kde repository
  at svn.debian.org/svn/pkg-kde/
  o http: and https: always return 405 Method Not Allowed
(okay webdav disabled as mention on the home page ;)
  o svn claims no repository found
  o svn+ssh://[EMAIL PROTECTED]  does not accept my alioth account
  o svn manual does not help any more :(
  What do I wrong?
 
 http is disabled as mentioned on the svn.debian.org main page. If I
 remember correctly to check out anonymously you need to do something
 like:
 
 svn co svn://svn.debian.org/pkg-kde/trunk

Ahhh,  http: URL on svn.debian.org had an additonal /svn in the path
that has to be removed in the svn: URL.  Thx!! 
 
 to do a regular checkout you need to do:
 
 svn co svn+ssh://svn.debian.org/svn/pkg-kde/trunk
 
 you can't put your username in the URL, you can either setup the special
 svn way (I forgot what its called) or you add something like the
 following to your .ssh/config file:
 
 Host svn.debian.org
   User ccheney
 
 The other svn way is explained in the svnbook.

Neither the .ssh/config,  user@ nor --username does work
with svn+ssh:  (always the same error msg).  So I assume that
svn+ssh:  mean rw access and that's of course denied (no problem
for me).
 
  Btw. what's the status/usage of debian/ in KDE's cvs and pkg-kde
  at alioth?
  
  Chris pkgs:
  KDE 3.2 for woody in kde cvs
  KDE 3.2 for sid in pkg-kde
 
 I will probably remove the debian dirs from my packages at kde.org soon
 unless there is a pressing reason for it to be there.

Ralf?

Achim
 
  Ben
  everything in kde-cvs
  Right?
 
 Yes at this time.
 
 
 Chris
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



ro svn checkout of svn.debian.org/svn/pkg-kde/

2004-02-11 Thread Achim Bohnet
Hi,

what's the method to check out a ro copy of svn pkg-kde repository
at svn.debian.org/svn/pkg-kde/
o http: and https: always return 405 Method Not Allowed
  (okay webdav disabled as mention on the home page ;)
o svn claims no repository found
o svn+ssh://[EMAIL PROTECTED]  does not accept my alioth account
o svn manual does not help any more :(
What do I wrong?

Btw. what's the status/usage of debian/ in KDE's cvs and pkg-kde
at alioth?

Chris pkgs:
KDE 3.2 for woody in kde cvs
KDE 3.2 for sid in pkg-kde
Ben
everything in kde-cvs
Right?

Achim

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



sarge: kde 3.1.5 - 3.2 (people.debian.org)

2004-02-04 Thread Achim Bohnet
Hi,
during update from sarge + sid KDE 3.1.5 + KO 1.3 to ChrisBen 3.2
the following conflicts occur ('cause pkgs are not in debian
yet I thought I report here).  It's just FYI, I'm not complaining. 

Thx for working on 3.2 pkgs!!

Achim

Preparing to replace kdelibs-bin 4:3.1.5-1 (using 
.../kdelibs-bin_4%3a3.1.95-1_i386.deb) ...
Unpacking replacement kdelibs-bin ...
dpkg: error processing 
/var/cache/apt/archives/kdelibs-bin_4%3a3.1.95-1_i386.deb (--unpack):
 trying to overwrite `/usr/bin/kfmexec', which is also in package konqueror


Preparing to replace kdelibs-data 4:3.1.5-1 (using 
.../kdelibs-data_4%3a3.1.95-1_all.deb) ...
Unpacking replacement kdelibs-data ...
dpkg: error processing 
/var/cache/apt/archives/kdelibs-data_4%3a3.1.95-1_all.deb (--unpack):
 trying to overwrite `/usr/share/mimelnk/application/mathml+xml.desktop', which 
is also in package koffice-data


Unpacking libkdepim1 (from .../libkdepim1_4%3a3.1.95-1_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/libkdepim1_4%3a3.1.95-1_i386.deb 
(--unpack):
 trying to overwrite `/usr/lib/libkdepim.so.1.0.0', which is also in package 
kdepim-libs
dpkg-deb: subprocess paste killed by signal (Broken pipe)


Unpacking libkcal2 (from .../libkcal2_4%3a3.1.95-1_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/libkcal2_4%3a3.1.95-1_i386.deb 
(--unpack):
 trying to overwrite `/usr/lib/libkcal.so.2.0.0', which is also in package 
kdepim-libs


Preparing to replace libkdenetwork2 4:3.1.5-1 (using 
.../libkdenetwork2_4%3a3.1.95-1_i386.deb) ...
Unpacking replacement libkdenetwork2 ...
dpkg: error processing 
/var/cache/apt/archives/libkdenetwork2_4%3a3.1.95-1_i386.deb (--unpack):
 trying to overwrite 
`/usr/share/apps/kconf_update/kpgp-3.1-upgrade-address-data.pl', which is also 
in package kgpgcertmanager


Unpacking replacement kdebase-data ...
dpkg: warning - unable to delete old file `/usr/share/applnk/Graphics': 
Directory not empty
dpkg: warning - unable to delete old file `/usr/share/applnk/Games': Directory 
not empty
dpkg: warning - unable to delete old file `/usr/share/applnk/Development': 
Directory not empty


Unpacking konsolekalendar (from .../konsolekalendar_4%3a3.1.95-1_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/konsolekalendar_4%3a3.1.95-1_i386.deb (--unpack):
 trying to overwrite `/usr/bin/konsolekalendar', which is also in package 
korganizer


Unpacking libkgantt0 (from .../libkgantt0_4%3a3.1.95-1_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/libkgantt0_4%3a3.1.95-1_i386.deb 
(--unpack):
 trying to overwrite `/usr/lib/libkgantt.so.0.0.2', which is also in package 
kdepim-libs


Unpacking libkpimexchange1 (from .../libkpimexchange1_4%3a3.1.95-1_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libkpimexchange1_4%3a3.1.95-1_i386.deb (--unpack):
 trying to overwrite `/usr/lib/libkpimexchange.so.1.0.0', which is also in 
package kdepim-libs

Preparing to replace ksmserver 4:3.1.5-2 (using 
.../ksmserver_4%3a3.1.95-1_i386.deb) ...
Unpacking replacement ksmserver ...
dpkg: error processing /var/cache/apt/archives/ksmserver_4%3a3.1.95-1_i386.deb 
(--unpack):
 trying to overwrite `/etc/gdm/Sessions/KDE', which is also in package kwin


Preparing to replace kwin 4:3.1.5-2 (using .../kwin_4%3a3.1.95-1_i386.deb) ...
Unpacking replacement kwin ...
dpkg: warning - unable to delete old file `/etc/kde3/debian': Directory not 
empty
dpkg: warning - unable to delete old file `/etc/gdm/Sessions': Directory not 
empty
dpkg: warning - unable to delete old file `/etc/gdm': Directory not empty


-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: woody KDE 3.1.4 - 3.2 update report

2004-02-04 Thread Achim Bohnet
On Wednesday 04 February 2004 10:09, David Baer wrote:
 On Tuesday 03 February 2004 21:11, Achim Bohnet wrote:
  Only problem is that I have to life without k3b it's deb is fixed :(
  Lets collect some 3.2 experience now, ah, oh, ...
 
 is there any chance, that problems with k3b-dependencies will be fixed soon?
 i don't want to live without k3b ;)

If you like dirty hacks you can install kdelibs-data (not k3b) with

  dpkg -i --force-conflicts 
/var/cache/apt/archives/kdelibs-data_4%3a3.2.0-0woody1_all.deb

Achim
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




woody KDE 3.1.4 - 3.2 update report

2004-02-03 Thread Achim Bohnet
Hi,

replacing latest with 3.2 in download.kde.org deb line I run into
the (small) upgrade problems reported below.  Nothing serious,
but it would be nice if the appropriate Replaces: would be added.

Only problem is that I have to life without k3b it's deb is fixed :(
Lets collect some 3.2 experience now, ah, oh, ...

Great job!!  Thx for the 3.2 pkgs!!!
Achim

Repeated runs of 'apt-get -u dist-upgrade' and 'apt-get -f install'
uncovered the following problems:

Unpacking replacement kdelibs-data ...
dpkg: error processing 
/var/cache/apt/archives/kdelibs-data_4%3a3.2.0-0woody1_all.deb (--unpack):
 trying to overwrite `/usr/share/mimelnk/application/x-cue.desktop', which is 
also in package k3b

k3b version installed is 0.10.3-1   (workaroun: dpkg --remove k3b)

Unpacking replacement kdelibs-data ...
dpkg: error processing 
/var/cache/apt/archives/kdelibs-data_4%3a3.2.0-0woody1_all.deb (--unpack):
 trying to overwrite `/usr/share/mimelnk/application/x-kudesigner.desktop', 
which is also in package kugar

kugar 1.2.1-0woody2 is/was installed(workaroun: dpkg --remove kugar koffice)

Unpacking replacement kdepim-libs ...
dpkg: error processing 
/var/cache/apt/archives/kdepim-libs_4%3a3.2.0-0woody1_i386.deb (--unpack):
 trying to overwrite `/usr/lib/libkgantt.la', which is also in package 
libkgantt0

libkgantt0 3.1.0-0woody3 is/was installed (workaround: dpkg --remove libkgantt0)

Unpacking replacement kdepim-libs ...
dpkg: error processing 
/var/cache/apt/archives/kdepim-libs_4%3a3.2.0-0woody1_i386.deb (--unpack):
 trying to overwrite `/usr/lib/libkcal.la', which is also in package libkcal2

Okay same prodecure as above for:

Unpacking replacement kde-i18n-de ...
dpkg: error processing 
/var/cache/apt/archives/kde-i18n-de_4%3a3.2.0-0woody1_all.deb (--unpack):
 trying to overwrite `/usr/share/locale/de/LC_MESSAGES/kgamma.mo', which is 
also in package kgamma

That were all upgrade problem;

Then I tried to reinstall removed pkgs and

libkcal2-- no longer exists (not needed I guess)
libkgantt0  -- 
kgamma  -- automaticly reinstalled

kugar, and k3b 0.10.3-1 (from planet-moll) can't be installed right now.

Achim

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: RFS(3): kdiff3 - compares and merges 2 or 3 files or directories

2004-01-13 Thread Achim Bohnet
On Tuesday 13 January 2004 01:44, Eike \ wrote:
 Hello!
 
 I'm still(*) looking for someone to test and upload the following package. 

Hi,

I've rebuild kdiff3 on woody and had a quick look and test merge.
Only strange thing that I could spot is why there are:

drwxr-xr-x root/root 0 2004-01-12 02:15:47 ./usr/share/doc/kde/HTML/en/
drwxr-xr-x root/root 0 2004-01-12 02:15:48 
./usr/share/doc/kde/HTML/en/kdiff3/
-rw-r--r-- root/root 21727 2004-01-12 02:13:44 
./usr/share/doc/kde/HTML/en/kdiff3/index.cache.bz2
-rw-r--r-- root/root 70907 2004-01-12 02:11:51 
./usr/share/doc/kde/HTML/en/kdiff3/index.docbook
-rw-r--r-- root/root  7856 2003-12-22 09:01:09 
./usr/share/doc/kde/HTML/en/kdiff3/index.html

Dupicates of those files + html output + manpage(!) are also in

/usr/share/doc/HTML/en/kdiff3

 The diff file has become even smaller because upstream has accepted my
 man page in his new version.

Well, removing some duplicate docs will make the deb smaller too ;)

Nice pkgs, nice app!

Achim

 kdiff3 is a graphical diff. I think the most useful difference to many 
 other diff programs is that the difference is shown by character, 
 not by line. Additionally, it integrates well into KDE.
 
 Package name: kdiff3
 Version : 0.9.81
 URL : http://kdiff3.sourceforge.net
 License : GPL
 Description: compares and merges 2 or 3 files or directories
  KDiff3 compares two or three input files and shows the differences 
  line by line and character by character. It provides an automatic 
  merge facility and an integrated editor for comfortable solving of 
  merge conflicts. KDiff3 allows recursive directory comparison and 
  merging as well.
 
 The package lintian and linda clean. It can be found at:
 http://user.cs.tu-berlin.de/~eikes/debian/kdiff3/
 
 Ciao,
 Eike
 
 PS: Posted separately to *.mentors and *.qt-kde.
 How can I crosspost with gmane?
 
 (*) My former sponsor seems to be MIA (Rene, are you out there?).
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: Packaging problem.

2004-01-08 Thread Achim Bohnet
On Wednesday 07 January 2004 05:20, Chris Cheney wrote:
 On Tue, Jan 06, 2004 at 12:00:19PM +0100, Jean-Michel Kelbert wrote:
  To my mind it is not a good idea to include lib in a binary package, so
  I don't want to do only one package.
 
 To be honest I don't know why most of the kde programs have libraries at
 all. Except for the ones that have kparts or plugins it makes very
 little sense since they will only be used by the one program. Libraries

AFAIU it the libraries are needed for the kdeinit hack, to speed
up startup time.

 that are only used by one program shouldn't be split out at all imho.
 And generally the ftp admin team frowns on the library packaging guide
 that states to split everything library into a libfoo libfoo-bin
 libfoo-dev. If we did that for all of KDE there would probably be an
 extra 300-400 packages, that would be pointless...

I agree.  If lib is only needed by one program there should be
no extra pkgs.

Achim
 
 Chris
-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: Struggling with dpkg-buildpackage with kdebase (latest CVS)

2003-12-28 Thread Achim Bohnet
On Sunday 28 December 2003 11:06, Alan Chandler wrote:
 I am trying to build myself some up to date debs (in a sid chroot inside my 
 existing debian system) 
 
 The apidocs part is failing - thus.  
 
 Error: tag HTML_HEADER: header file `../apidocs/common/header.html' does not 
 exist
 make[3]: *** [apidox-am-yes] Error 1
 
 In checking up, it appears that ../apidocs/common is a unsatisfied link to 
 /usr/share/doc/HTML/en/common  (the HTML directory does not yet exist in my 
Hi Alan,

Normally KDE docs are installed into /usr/share/doc/kde/HTML (note
additional kde/ subdir).  HTML dir is one of the dirs where KDEs
'everything below one prefix' does not match FHS with prefix set to
/usr.

 chroot  - despite having installed kdelibs from the freshly built debs)
 
 The relevent piece of makefile in kdebase/admin/Doxyfile.am seems to be the 
 following. 
 
 
if test ! -x $(top_builddir)/apidocs/common; then \
 if test -d $(top_srcdir)/doc/common; then \
common_dir=`cd $(top_srcdir)/doc/common  pwd` ;\
 else \
common_dir=$(kde_libs_htmldir)/en/common ;\
 fi ;\
 $(LN_S) $$common_dir $(top_builddir)/apidocs/common; \
 fi ;\
 
 Which sort of makes me think that $(kde_libs_htmldir) is being set to the 
 final target rather than the obj-i386-linux build directory during the 
 building of the debs.  I presume in most peoples case they will have 
 established the /usr/share/docs/HTML hierarchy from previous builds so not 
 noticed the problem.

I had a look at one of my debiandirs files and found only

export kde_htmldir=/usr/share/doc/kde/HTML
...
configkdevelop=...--with-kdelibsdoc-dir=/usr/share/doc/kdelibs3-doc/html...


So kde_libs_htmldir is not set/exported and not defined for configkde.

I've not installed kdelibs3-doc so can't check where it's docs are installed.
Please check where kdelibs3-doc installs it's docu and add do configkde
--with-kdelibsdoc-dir=/usr/share/doc/kdelibs?/html.  I guess exporting
additionaly kde_libs_htmldir in debiandirs does not hurt.

Does this fix the problem?   If yes, kde-common/admin/debianrules needs to
be updated.
 
 I've scouted around the KDE CVS repository looking for recent relevent 
 changes 
 around this area and I can't find any - normally an indication that I am way 
 off beam with my thinking.  Since I am new to this area and on a steep 
 learnign curve, can anyone shortcut this for me and help me understand why it 
 is like the way it is (and what needs to change).

The KDEs 'everything below' prefix and the quirks used in debian to follow
FHS, do not play well together.  Untils we find/agree on an algorithm how
to handle a KDE installations distrubuted accross

a) FHS (easy ;)
b) /usr/local
c) somewhere else (e.g. /opt or /home/joeUsers/ etc) via KDEDIR(s)

and patch kstandarddirs.*.in accordingly the KDE dir layout versus FHS
layout issue will catch us again and again.

Achim


 
 -- 
 Alan Chandler
 [EMAIL PROTECTED]
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: Bad install defaults for KDElibs

2003-12-16 Thread Achim Bohnet
On Friday 12 December 2003 20:29, Chris Cheney wrote:
 On Fri, Dec 12, 2003 at 03:03:40PM +0100, Achim Bohnet wrote:
  On Friday 12 December 2003 13:31, Thomas Zander wrote:
   -BEGIN PGP SIGNED MESSAGE-
   Hash: SHA1
   
   Hi,
   
   in the package kdelibs-data the /etc/kderc file is present (its a 
   symlink), this is not very nice since that means it becomes impossible to 
   have another version of KDE running on the same machine.
  
  Right.  I usualy delete the file.  dpkg-divert did not work (tried long 
  ago).
 
 I don't understand why deletion is actually needed as mentioned below,
 but ymmv.

Hi Chris,

yes, mmdv ;)  /etc/kderc settings affect all KDE installation on host.
/usr/share/config/system.kdeglobals (aka /etc/kde3/system.kdeglobals)
affects only those with $prefix=/usr, e.g., not the private kde cvs
install of a user.
 
   KDE allows multiple versions by using the KDEDIR env-var to be set before 
   calling startkde.  Unfortunately the new (own-compiled) version will then
  
  KDEDIR is no solution for Debian because debian follows the fhs and can't
  install everything under a common root KDEDIR.   Next environment var are
  fragile and error prone.
 
 Indeed, I don't even think if Debian tried to use KDEDIR it would work
 for the reason mentioned below about how kde_confdir works.
 
   find the paths to the /usr/bin and /usr/lib and start using that, getting 
   a nice mix of versions on my desktop.
   
   I recommend to use KDEDIR and friends instead of the kderc file.
  
  No need for KDEDIR(S):  KDE std dir lookup includes
  
a) /etc/kderc # used by all KDE installations
b) $kdeconf_dir/system.kdeglobals # aka /etc/kde3/ on Debian
c) hardcoded stuff in kstandarddirs.cpp(.in)
  
  As a) points to b),  a) is just a duplicate but at the same time
  confuses other parallel KDE
  installations.  AFAIR remember most (if not all) vars in system.kdeglobals
  are identical to compiled in values in kstandarddirs.cpp(.in).  All derived 
  from
  debian/debiandirs file.
 
 If you don't use /etc/kderc and don't store configs in
 $prefix/share/config (iow use /etc/kde3) then KDE will not know where

But Debian stores config in $prefix/share/config - /etc/kde3, right?
Therefore system.kdeglobals is found and there's no need for /etc/kderc.

 to locate other files since it forces everything to be located under the
 $prefix it was installed in. IOW $kdeconf_dir = $prefix/share/config
 which is hardcoded into the library itself, yes its a f*cking nasty
 hack (KDE is filled with them), but I don't know how to patch around
 it cleanly so I just use the /etc/kderc to override it. Also the KDE
 lookup looks in KDEDIR before /etc/kderc or did the last time I checked.
 
 For example:
 
 /home/ccheney/.kde/bin/:/usr/local/bin/:/usr/bin/
 
 with KDEDIR=/opt/kde3 it should show as:
 
 /home/ccheney/.kde/bin/:/opt/kde3/bin:/usr/local/bin/:/usr/bin/
 
 Am I missing something?
 
 BTW the only things I have listed in system.kdeglobals now are things
 that differ from upstream KDE since I realized the others weren't really
 needed.
 
  Summary: get rid of /etc/kderc, Debians KDE will not notice.
 
 For reasons noted above KDE definitely would notice...

Not here.  Try, with /usr/share/config - /etc/kde3:

for d in `kde-config --types | awk '{print $1}'`; do kde-config --path $d; done

once with and once without the /etc/kderc - kde3/system.kdeglobals links
I've never found a difference here.

Achim
 
 Chris
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



kde deb pkg questions

2003-12-16 Thread Achim Bohnet
Hi,

While packaging some kde apps for woody and I run into some
annoying problems:

o Some Makefile.am use KDE 3.2 xdg_appsdir and destop
  files end up in /usr/share/applications/kde also for
  kde 3.1.4.  My current workaround is to use in rules
make install xdg_appsdir=/usr/share/applnk/Graphics ...
  Is there an better way?  E.g., Makefile.am changes or
  starting automake with some magic so kde 3.1.4 install
  in applnk and kde 3.2 installs into applications?

o upstream tar balls comes with po/*/*.gmo files.  Those
  are updated during make but not removed by distclean.
  So a second debuild fails due to binary changes compared
  to .orig.tar.  What's the right way handle this?
remove *.gmo files for orig.tar
touch gmo files so there are not rebuild
modify distclean
  ?
  
Thx for any advise,
Achim


-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: Bad install defaults for KDElibs

2003-12-12 Thread Achim Bohnet
On Friday 12 December 2003 13:31, Thomas Zander wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi,
 
 in the package kdelibs-data the /etc/kderc file is present (its a 
 symlink), this is not very nice since that means it becomes impossible to 
 have another version of KDE running on the same machine.

Right.  I usualy delete the file.  dpkg-divert did not work (tried long ago).

 KDE allows multiple versions by using the KDEDIR env-var to be set before 
 calling startkde.  Unfortunately the new (own-compiled) version will then

KDEDIR is no solution for Debian because debian follows the fhs and can't
install everything under a common root KDEDIR.   Next environment var are
fragile and error prone.

 find the paths to the /usr/bin and /usr/lib and start using that, getting 
 a nice mix of versions on my desktop.
 
 I recommend to use KDEDIR and friends instead of the kderc file.

No need for KDEDIR(S):  KDE std dir lookup includes

  a) /etc/kderc # used by all KDE installations
  b) $kdeconf_dir/system.kdeglobals # aka /etc/kde3/ on Debian
  c) hardcoded stuff in kstandarddirs.cpp(.in)

As a) points to b),  a) is just a duplicate but at the same time
confuses other parallel KDE
installations.  AFAIR remember most (if not all) vars in system.kdeglobals
are identical to compiled in values in kstandarddirs.cpp(.in).  All derived from
debian/debiandirs file.

Summary: get rid of /etc/kderc, Debians KDE will not notice.

Achim
 
 See also:
 http://bugs.kde.org/show_bug.cgi?id=70208
 
 - -- 
 Thomas Zander
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.2.3 (GNU/Linux)
 
 iD8DBQE/2bUVCojCW6H2z/QRAj3fAKCwsoTUqn3a6Hfu00ooi8H4yKHIJQCfSMad
 GVbzYuNbQwsKSIo8R8pyXts=
 =s6cU
 -END PGP SIGNATURE-

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]



Re: kaudiocreator questions

2003-12-08 Thread Achim Bohnet
On Monday 08 December 2003 13:05, jerry garcia wrote:
 Hi all!
 
 I'm in the process of setting up a music server, and replacing all my 300 
 disk 
 cd changers permanently, but have run into a snag.
 
 I've got a question about kaudiocreator.  I'm using sarge/sid, and when I run 
 kaudiocreator, even though I've marked the box that says 'save wav file as 
 well as encoded file'  only the lame encoded mp3 is saved. any suggestions on 
 which file I need to edit to force this?

I'm running KDE 3.14 on woody and the wav files are kept
as /tmp/kde-username/kaudiocreator*.tmp.   Maybe a bug
in the sid pkg?
 
 I've still got 500 gig of wav's to encode for the server, so this is fairly 
 important to me.  Under rh 9, this worked well, but as i didn't care for 
 fedora, I migrated over to debian via knoppix.

Welcome!

Achim
 
 Thanks for any help.
 
 jaz
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: kppp problem

2003-10-06 Thread Achim Bohnet
On Monday 06 October 2003 13:03, Zbynek Vrastil wrote:
 Hi all,
 
 I've following problem: I'm using kppp to connect to internet. It works
 perfectly when logged as root. But when I'm logged in as normal user, pppd
 dies with exit status 16 (modem hanged up) when checking username and
 password. I suppose, there's some problem with access permissions, but I've
 no idea where to look. Thanks in advance.
Hi,

a) check that the user user that the kppp user is a member of the
   group dip.

b) kppp tries to add auth info to /etc/ppp/{pap,chap}-secrets.
   That's only possible as root.  Therefore I made kppp setuid root
   (as it was for KDE 2).

 dpkg-statoverride --update --add root dip 4754 /usr/bin/kppp

   You have to decide yourself if this is safe or a security hole.

Achim
 
 Zbynek Vrastil
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: Again: Delays starting KDE apps after upgrade 3.1.3 = 3.1.4

2003-09-19 Thread Achim Bohnet
On Fri, Sep 19, 2003 at 01:41:22AM +0200, Anders Ellenshøj Andersen wrote:
 On Thursday 18 September 2003 23:29, Doug Holland wrote:
 
  2. /tmp/.ICE-unix/ missing or has wrong owner/group/permissions.  To fix,
  execute following commands as root.
  mkdir /tmp/.ICE-unix
  chown root.root /tmp/.ICE-unix
  chmod 1777 /tmp/.ICE-unix
 
 In sid, this directory is created at user login with the users username and 
 users group, but with the same permissions as stated.
 
 I have tried creating these files as root in an init script which get 
 executed 
 on boot, and it doesn't make any difference in speed on my system. Not any 
 that I can notice anyway.

You'll notice the effect when you logout/login. With .ICE-unix chown root:root 
it
takes here ~ 1 sec until KDE session is up and 2-3 sec until all KDE
apps are restored.  With .ICE-unix owned by a normal user the second
login takes 3-4 times longer.

Achim
 
 But I can't complain about the speed in any case. It's as snappy as bulky old 
 XFree86 gets.
 
 Anders




Re: Ownership of /tmp/.ICE-unix and KDE speed

2003-09-19 Thread Achim Bohnet
On Fri, Sep 19, 2003 at 12:34:00PM +0200, Anders Ellenshøj Andersen wrote:
 On Friday 19 September 2003 09:23, Achim Bohnet wrote:
 
  You'll notice the effect when you logout/login. With .ICE-unix chown
  root:root it takes here ~ 1 sec until KDE session is up and 2-3 sec until
  all KDE apps are restored.  With .ICE-unix owned by a normal user the
  second login takes 3-4 times longer.
 
 No matter what the ownership of that file is I get nowhere near that speed. 
 On 
 my ASUS A1300 with 650MHz celeron and 300MB SDRAM, KDE starts up in around 
 10-15 seconds on cold boot. It's a bit faster on relogin at somewhere under 

That's here the same on a cold boot because the disk access is the
limiting factor and therefore your numbers are what I normally get
too (one kde session until shutdown). 

In the case I login/logout/login (tests/reconfig ...), and
verything is in RAM (_no_ disk access according to led here!)
I see a big effect if ICE-unix is owned by root or not.  With
ICE-unix chown root, after login I almost immediately see the
kdesktop  ksplash on the first or second last item indicating
that the apps are restored.

That's on a laptop with 1.4 MHz Pentium, 512 MBRAM. I've seen
the same effect on a 4 way sunserver via an X-terminal.

As soon as disk access is involved the ICE-unix slowdown is
hidden.

Achim
 10 seconds. So 1 second to start the KDE session sounds absolutely incredible 
 to me.
 
 But the ownership of /etc/.ICE-unix doesn't make any difference at all to 
 this, not here anyway.
 
 Anders




Re: kdelibs4-dev and XFree86 4.3.0

2003-09-18 Thread Achim Bohnet
On Wed, Sep 17, 2003 at 11:21:46PM +0200, Andreas Richter wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi,
 
 i have installed the Daniel Stone Backport of XFree86 4.3.0 Packages from 
 http://people.debian.org/~mmagallo/packages/ on my Woody-System. 
 
 Yesterday i upgraded my System to the brand new KDE 3.1.4 Packages from 
 ftp.kde.org. But the Package kdelibs4-dev couldn't be upgraded and now i 
 can't this packages installed. The dependencies need the Package 
 xlibs-pic from the original XFree86 Woody Pakages. 
 
 Hm. What can i do to develop again with my KDE 3.1.4 and XFree86 4.3.0? 
 Have anybody a Reason to solve this Problem?

Well, at least with xfree86 4.2  4.3 it's possible.  It helps a
lot that X11 has a client server architecture ;)  I've updated the
server and fonts to 4.3 but kept the client side libraries for 4.2
I use kdelibs-dev without problems:

[EMAIL PROTECTED](0) ~ $ dpkg -l | egrep ' 4.2.1-'
ii  xbase-clients   4.2.1-3.bunk.5  miscellaneous X clients
ii  xlib6g  4.2.1-3.bunk.5  pseudopackage providing X 
libraries
rc  xlibmesa3   4.2.1-3.bunk.5  XFree86 version of Mesa 3D 
graphics library
ii  xlibs   4.2.1-3.bunk.5  X Window System client 
libraries
ii  xlibs-dev   4.2.1-3.bunk.5  X Window System client 
library development files
ii  xlibs-pic   4.2.1-3.bunk.5  X Window System client 
extension library PIC archives
ii  xnest   4.2.1-3.bunk.5  nested X server
ii  xprt4.2.1-3.bunk.5  X print server
ii  xterm   4.2.1-3.bunk.5  X terminal emulator
ii  xvfb4.2.1-3.bunk.5  virtual framebuffer
X server

[EMAIL PROTECTED](0) ~ $ dpkg -l | egrep ' 4.3.0-'
ii  lbxproxy4.3.0-0ds2.0.0woody2Low Bandwidth X (LBX) proxy 
server
ii  libdps1 4.3.0-0ds2.0.0woody2Display PostScript (DPS) 
client library
ii  libxaw6 4.3.0-0ds2.0.0woody2X Athena widget set library 
(version 6)
ii  libxaw7 4.3.0-0ds2.0.0woody2X Athena widget set library
ii  proxymngr   4.3.0-0ds2.0.0woody2X proxy services manager
ii  twm 4.3.0-0ds2.0.0woody2Tab window manager
ii  x-window-system-core4.3.0-0ds2.0.0woody2X Window System core 
components
ii  xdm 4.3.0-0ds2.0.0woody2X display manager
ii  xfonts-100dpi   4.3.0-0ds2.0.0woody2100 dpi fonts for X
ii  xfonts-100dpi-transcode 4.3.0-0ds2.0.0woody2100 dpi fonts for X 
(transcoded from ISO 10646-1)
ii  xfonts-75dpi4.3.0-0ds2.0.0woody275 dpi fonts for X
ii  xfonts-75dpi-transcoded 4.3.0-0ds2.0.0woody275 dpi fonts for X 
(transcoded from ISO 10646-1)
ii  xfonts-base 4.3.0-0ds2.0.0woody2standard fonts for X
ii  xfonts-cyrillic 4.3.0-0ds2.0.0woody2Cyrillic fonts for X
ii  xfonts-scalable 4.3.0-0ds2.0.0woody2scalable fonts for X
ii  xfree86-common  4.3.0-0ds2.0.0woody2X Window System (XFree86) 
infrastructure
ii  xfwp4.3.0-0ds2.0.0woody2X firewall proxy server
ii  xlibmesa-dev4.3.0-0ds2.0.0woody2Mesa 3D graphics 
development library meta-package [XFree86]
ii  xlibmesa-gl-dev 4.3.0-0ds2.0.0woody2Mesa 3D graphics library 
development files [XFree86]
ii  xlibmesa-glu-dev4.3.0-0ds2.0.0woody2Mesa OpenGL utility library 
development files [XFree86]
ii  xlibmesa4-dri   4.3.0-0ds2.0.0woody2Mesa 3D graphics library 
modules [XFree86]
ii  xlibmesa4-gl4.3.0-0ds2.0.0woody2Mesa 3D graphics library 
[XFree86]
ii  xlibmesa4-glu   4.3.0-0ds2.0.0woody2Mesa OpenGL utility library 
[XFree86]
ii  xserver-common  4.3.0-0ds2.0.0woody2files and utilities common 
to all X servers
ii  xserver-xfree86 4.3.0-0ds2.0.0woody2the XFree86 X server
ii  xspecs  4.3.0-0ds2.0.0woody2X protocol, extension, and 
library technical specifications
ii  xutils  4.3.0-0ds2.0.0woody2X Window System utility 
programs

[EMAIL PROTECTED](0) ~ $ dpkg -l kdelibs\* | grep '^i'
ii  kdelibs-bin 3.1.4-0woody1   KDE core binaries
ii  kdelibs-data3.1.4-0woody1   KDE core shared data
ii  kdelibs43.1.4-0woody1   KDE core libraries
ii  kdelibs4-dev3.1.4-0woody1   KDE core libraries 
(development files)
ii  kdelibs4-doc3.1.4-0woody1   KDE core library 
documentation


So try downgrading to client libs to 4.1 or if this does not work,
goto back to 4.2 fro bunk repository

deb http://www.fs.tum.de/~bunk/debian woody/bunk-1 main contrib non-free

Achim
 
 Thanks 
 
 - -- 
 Gruss/Greetings
 Andreas Richter
 OSZine - Das deutschsprachige Open Source Magazin (http://www.oszine.de)
 GnuPG-PubKey: 

Re: Bug#208205: Stopping kdm does not cleanly logout active kde sessions

2003-09-02 Thread Achim Bohnet
Hi,
autologout on X-server shutdown is IMHO a great feature but
as you see below it freezes my laptop.  Anyone an idea what's
going on?

Achim
On Tuesday 02 September 2003 14:10, Dave Cinege wrote:
 On Tuesday 02 September 2003 06:08, Achim Bohnet wrote:
 
  as root from the command line and my laptop shutdown completely.
 
 DOH!!! Yes I noticed the same when I did this 2 weeks ago...intended to fix 
 it 
 before mailing you.then forgot.  : P
 
 After a good 1.5 hours of searching I finally dug up the needed info from the 
 KDE site. See:
 http://devel-home.kde.org/~danimo/apidocs/kdecore/html/classKApplication.html
 
 The 3 init args to logout are:
 ShutdownConfirm, ShutdownType, ShutdownMode
 
 I had type = 2, which is halt. It should be 0. (None)
 
  If you find how to just logout all users (there can be several
  session on :0 :1 ...) it's a great feature IMHO to should go
  into kdms init.d script.

Thinking more about it the right place for such a peace of code
is not kdm init.d script.  One can log into gnome with kdm or
with gdm into kde.  So it should be a standalone script in kdelibs,
e.g.,

/etc/X11/x-session-logout.d/kde3# gnome, ...

So any x session manager can logout the user regardless what
desktop the user prefers.   That all scripts get executed
should be the duty of /usr/X11R6/bin/X.

Nevertheless such changes take time so until it's implemented
a good temporory home is /etc/init.d/kdm ;)

 
 Maybe this:
   dcop --all-users --all-sessions ksmserver ksmserver logout 0 0 0
 
 

Well, actually worser for me.  I looks like that it does the right
thing but after that my system had freeze :(  Power off/on was the
only solotion.  I had two session running:

allee[0] ~ # dcop --list-sessions --all-users
Active sessions for user /home/ach :
  .DCOPserver_allee__0

Active sessions for user /home/ttt :
  .DCOPserver_allee__1

allee[0] ~ # dcop --all-users --all-sessions ksmserver ksmserver logout 0 0 0
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : 
None of the authentication protocols specified are supported and host-based 
authentication failed
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : 
None of the authentication protocols specified are supported and host-based 
authentication failed
ERROR: Couldn't attach to DCOP server!
allee[1] ~ #

I tried again with the usual std session on :0  I hear the logout sound
screen turn black and #$%$^ hard lock again :(

I really think the 'auto logout before shutting down X server' is a very
good idea but as you can see it could cause trouble and needs further
testing and investigation.

Let me suggest to move the discusson to debian-kde@lists.debian.org

Achim
 
 Dave

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: kscd fails as normal user, works through kdesu -c

2003-06-26 Thread Achim Bohnet
On Wednesday 25 June 2003 23:13, Josh Metzler wrote:
 I can play cd's using kscd as root (by doing kdesu -c kscd).
 
 When I use the icon on the K-menu, kscd appears in the taskbar, then 
 disappears quickly.  The window never appears.  When I try running it from 
 konsole, I get the following errors:
 
 [EMAIL PROTECTED]:~$ kscd
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
 [EMAIL PROTECTED]:~$ CDTEXT INFO: use GET_FEATURE_LIST(0x46)...
 CDTEXT INFO: try to read, how long CDTEXT is?
 CDTEXT INFO: CDTEXT is a 7 byte(s) long
 CDTEXT INFO: try to read CDTEXT
 CDTEXT INFO: read 7 byte(s) of CDTEXT
 CDTEXT INFO: free_cdtext_info() called
 CDTEXT ERROR: invalid packet at 0x: 0x 00 00 00 08 5F 00 55 00 53 00 
 08 08 11 00 00 00 D8 CF
 
 At this point nothing else happens - there is no kscd window, no CD activity, 
 and no sound.  There is brief CD activity around the time of CDTEXT INFO: ... 
  
 Hitting Enter gets me a prompt back, but I must manually kill the kscd 
 process, even though it appears to be doing nothing.

If've had a similar problem last night when I used kscd after a long time
again (but did not try kscd as root).

I had to create /usr/share/apps/kscd/cddb by hand because kscd refused to
start without it.  Then kscd crashed until I disalbed remote freedb in
the kscdrc config file.

Later I could enable remote freedb again and got a crash when I inserted
a CD never played with kscd before while kscd was running.  Restarting kscd
worked this time.  Very strange. I had no time yet to figure out when/what
why something goes wrong.

Achim
 
 I'm guessing it's a permissions problem, since it works kdesu root, but I 
 don't really know where to start.  Any help would be appreciated.
 
 Thanks,
 Josh
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: KDM hangs

2003-06-23 Thread Achim Bohnet
On Tuesday 17 June 2003 15:32, Peter Clark wrote:
   I'm having a minor issue with KDM on my shiny new laptop; I've got it 
 set up 
 so that I loads on both vt7 and vt8. /etc/kde3/kdm/Xservers looks like this:
 
 :0 local /usr/X11R6/bin/X :0 -dpi 75 -nolisten tcp vt7
 :1 local /usr/X11R6/bin/X :1 -dpi 75 -nolisten tcp vt8

Why don't you use

:0 [EMAIL PROTECTED] /usr/X11R6/bin/X :0 -dpi 100 -nolisten tcp vt7
:1 local reserve /usr/X11R6/bin/X :1 -dpi 100 -nolisten tcp vt8
:2 local reserve /usr/X11R6/bin/X :2 -dpi 100 -nolisten tcp vt9
:3 local reserve /usr/X11R6/bin/X :3 -dpi 100 -nolisten tcp vt10

This start Xserver on vt8...vt10 when needed.  With these 'reserved'
entries K-menu and screen saver have a new 'Start new session' entry
that start x-server on vt8 then vt9 ...

Achim
 
 However, whenever I start the laptop, kdm stops loading on one vt until I 
 switch over to the other. Only then will both load. When I say, stops 
 loading, I mean that the black and white fuzz appears, plus the mouse 
 cursor, and then...nothing. Once I switch over, then the wallpaper and login 
 window appear. My desktop has the same setup, but doesn't have an problem 
 loading them separately. (Although it won't start a kdm session until I 
 switch over to the other vt, at which point I have to wait for it to load 
 before continueing. It would be nice if it loaded in the background, but 
 first things first.) Is there anything I'm missing here?
   :Peter
 
 -- 
 Oh what a tangled web they weave who try a new word to conceive!
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: kshowmail with KDE 3.1.2

2003-06-02 Thread Achim Bohnet
On Sunday 01 June 2003 06:47, CRH wrote:
 Has anyone successfully compiled kshowmail 
 http://sourceforge.net/projects/kshowmail/
 with KDE 3.1.2? 
 
 I am unable and I don't know whether it's incompatibility with KDE 3.1 or
 compiler issues. Below are the make errors.

Install libmimelib1-dev

Achim
 
 
 decodeRFC2047.cpp:21:28: mimelib/mimepp.h: No such file or directory
 decodeRFC2047.cpp: In function `QCString decodeQuotedPrintable(const 
 QCString)
':
 decodeRFC2047.cpp:40: error: `DwString' undeclared (first use this function)
 decodeRFC2047.cpp:40: error: (Each undeclared identifier is reported only once
for each function it appears in.)
 decodeRFC2047.cpp:40: error: parse error before `(' token
 decodeRFC2047.cpp:43: error: `dwsrc' undeclared (first use this function)
 decodeRFC2047.cpp:43: error: `dwdest' undeclared (first use this function)
 decodeRFC2047.cpp:43: error: `DwDecodeQuotedPrintable' undeclared (first use
this function)
 decodeRFC2047.cpp: In function `QCString decodeBase64(const QCString)':
 decodeRFC2047.cpp:54: error: parse error before `(' token
 decodeRFC2047.cpp:58: error: `DwDecodeBase64' undeclared (first use this
function)
 make[2]: *** [decodeRFC2047.o] Error 1
 make[2]: Leaving directory 
 `/home/craig/downloads/kshowmail-3.0.4/kshowmail-3.0.4/kshowmail'
 make[1]: *** [all-recursive] Error 1
 make[1]: Leaving directory 
 `/home/craig/downloads/kshowmail-3.0.4/kshowmail-3.0.4'
 make: *** [all] Error 2
 
 
 -- 
 Ciao,
 CRH
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: libcupsys2, used in KDE 3.1.x series

2003-05-21 Thread Achim Bohnet
On Wednesday 21 May 2003 22:55, Michael Peddemors wrote:
 When nolden debs where out there, I know that he used the version..
 Package: libcupsys2
 Versions:
 1.1.18-1woody2(/var/lib/dpkg/status)
 
 but libcupsys2-dev relies on

I'm sure when 'nolden debs' where out there, there was also a
libcupsys2-dev 1.1.8.
 
 libcupsys2-dev: Depends: libcupsys2 (= 1.1.14-4.4) but 1.1.18-1woody2 is to 
 be 
 installed..
 
 Is it safe now that KDE 3.1.x is in woody to go back to 1.1.14-4.4 or do we 
 need to get an updated libcupsys2-dev in woody?

KDE 3.* was and will never be in woody.  It's in an unofficial
apt repository ;) It's save to downgrade to 1.1.14. (as long as
you don't use new cups 1.1.18 features) to downgrade to 1.1.14.
Did it some weeks ago without any problems.

Achim
 
 -- 
 --
 Catch the Magic of Linux...
 
 Michael Peddemors - Senior Consultant
 LinuxAdministration - Internet Services
 NetworkServices - Programming - Security
 Wizard IT Services http://www.wizard.ca
 Linux Support Specialist - http://www.linuxmagic.com
 LinuxMagic is a Registered TradeMark of Wizard Tower TechnoServices Ltd.
 
 (604)589-0037 Beautiful British Columbia, Canada
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 
 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]




Re: Problem with printing in konqueror?

2003-05-11 Thread Achim Bohnet
On Sat, May 10, 2003 at 02:06:47PM -0500, Donald Spoon wrote:
 Paul Cupis wrote:
  -SNIP- 
  
  FWIW, I have CUPS and KDE running fine together on sid, and have done 
  for a while. I vaguely recall that I may have had to blow away my 
  configuration after a CUPS upgrade a while ago  - perhaps kprinter 
  generates a cups.conf which the newer/current CUPS pacakges do not 
  like?
  
  Can anyone having these problems try replcing their cups.conf with the 
  package maintainers version, reconfiguring, and trying again? It would 
  be useful to know if this is the cause of the problem, so that we may 
  try and resolve it.
  
  Thanks.
  
  Paul Cupis
  - -- 
  [EMAIL PROTECTED]
  
 
 Paul,  I had this happen to me about 2 weeks ago.  I had upgraded KDE to 
 3.1.1, and subsequently upgraded from CUPS from Debian testing to the 
 version in unstable.  I elected to keep my existing, moderately 
 modified, conf files during the install.  They had been working OK, so I 
 thought why not?
 
 This turned out to be a BIG mistake... I never could make the new CUPS 
 install work completely as it had before!  It would print locally, and 
 even remotely via SAMBA, but I could never get it to advertise itself 
 to my LAN via CUPS as an available printer.  I finally trashed my old 
 conf file and replaced it with the packager's version and everything 
 started working!
 
 In my case, it was the old /etc/cupsd.conf file that wasn't nice.

Hi Don,

Did you check the difference between the old cups settings and the
new ones?  If we can't track down this problem every(?) upgrade may
break cups.  Not good for debians or cups' reputation ;)

Achim
 
 Submitted FYI...
 
 Cheers,
 -Don Spoon-
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 




Re: Kamera, Pencam, hotplug, perms

2003-05-10 Thread Achim Bohnet
On Sat, May 10, 2003 at 01:39:49AM -0700, Michael Rudmin wrote:
 Hi, I have a problem which seems like it should have
 come up before, but maybe it's new, because it's got a
 little twist.
 
 I installed hotplug usb, and have a Argus DC1500
 [essentially a pencam:  it requires USB data transfer,
 and is not just a USB block device].  When I plug in
 my camera, I see in /proc/bus/usb/001 two files, one
 of which is the driver 001 and one of which is the
 camera, with a different number like 005.

Wild guess:
Check if hotplug loads camera q specific kernel module:

/sbin/lsmod |head
# plugin camera
/sbin/lsmod |head

I could not use the usb with DC2400 until I disabled
autoloading of dc2xx for a Kodak DC240.

 
 Now, I also installed /etc/hotplug/usb/usbcam and all
 that, so that it should adjust the permissions.
 
 I used the usbcam.group as my source for usbcam, and
 adjusted it to be executable.  Then from the command
 line, I addgroup'd camera, and added my user name to
 the group camera with #adduser myuser camera.
 
 Note that usbcam.group refers to the group camera. 
 And now my executable usbcam does, as well.
 
 I also checked that the Argus' control variables, as
 referenced in /proc/bus/usb/devices, is covered by the
 graphics engine that runs all the permissions stuff.
 
 Finally, on KDE I set up (control
 panels)::(peripherals)::(camera) to include my Argus
 DC1500.
 
 When I type in camera:/ in the file manager URL, I get
 my DC1500.  But when I click on it, I get one of two
 messages:  Cannot claim USB Bus, or sometimes I/O
 problem.  Cannot read file  or sometimes Could not
 read file:  bad parameters.
 
 Just to see if it was a permissions problem, I rather
 foolishly logged into KDE as root [I know, not a good
 idea, can wreck things], and tried to access the
 camera from there.  No good -- it says Cannot claim
 USB Bus.  Maybe with time, it would give me the other
 errors instead.  

Try the gphoto2 command line tool. This will test you
if it's a libgphoto/kernel problem or if it KDEs camera
io slave.

If gphoto2 works and camera:/ not you may try digikam.

Achim
 
 Does anyone know what is going on, and what I have to
 do differently?  I've tried to follow the installation
 instructions everywhere, but I seem to be doing
 something wrong.




  1   2   3   >