Re: Bad toolbars
On Mon, 2003-09-15 at 12:23, Peter Clark wrote: > First, apologies for the binary attachment. I just updated my system, > and > suddenly the toolbars are just a pixel or two too short. I tried every style, > and they all had the same problem, except for Keramic. The pic is of kmail's > toolbar, and as you can see, the bottom black line is broken. I tried > changing the icon size, adding and removing text, etc., but with no luck. Has > anyone run into this before? > :Peter I too began experiencing this on my unstable system, and I too just did an apt-get update && apt-get upgrade. Thats unstable for you! -- Crispin Wellington <[EMAIL PROTECTED]> http://crispin.aeonline.net/ In the fullness of time, at the first opportunity, maybe... signature.asc Description: This is a digitally signed message part
Re: screen capture
On Wed, 2002-04-10 at 21:38, Quenten Griffith wrote: > I can't seem to find the tool in KDE for capturing the screen, I think > its called kapture. Is it apart of another package in "testing". I use import. import -window root filename.png It automatically saves in the format specified in the filename extension. png, jpg etc. To wait before a capture go... sleep 5; import -window root filename.png I just mention it because knowing things on the command line will come in useful one day. (like capturing a screen remotely). Kind Regards Crispin Wellington -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kghostview dependency problem and vi cursors still broken in woody
Did a fresh install of woody. Installation ran without a hitch. Firstly, Im having dependency problems with kghostview and koffice-libs koffice-libs recommends kghostview >= 2.2-0 which is not available. Even sid doesn't seem to have such an advanced version of kghostview. Im assuming the dependency info in koffice-libs is incorrect. Anyone else experiencing this? Any work arounds? Has a bug report been submitted? Secondly, the arrow keys in vi are still broken (was discussed without adequate resolution in Febrary on debian-testing) :( Has a bug report been submitted to the vi maintainer? Kind Regards Crispin Wellington
