Konsole issues

2008-09-30 Thread Zoe Parsons
Hi, I just resurrected my desktop box after it's been languishing in a 
corner for months and decided to bring it up to date and also put KDE4 on 
it in a single swoop.


Whilst it eventually worked (I'm not sure if I did something odd or if my 
apt-get has gone funny as I had to manually specify a large number of the 
dependencies on the command line rather than just kde4 itself, which 
meant I somehow missed out on systemsettings...), I don't think hugely of it's 
looks at the moment and am trying to make it a bit more comparable to my 
old KDE3 setup.


The only major issue I've had thus far (that I've found) is that on 
konsole the cursor seems to be pretending to be several spaces over to the 
right. The text appears in the correct place, but the cursor is 
mispositioned... I've fiddled with the font settings but that doesn't seem 
to change.


And oh yes, this is on a completely fresh account, no user settings at 
all.


I'm probably missing something obvious TBH...

--
ZoeP


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



xfonts-konsole issues

2003-04-28 Thread Ralf Nolden
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi guys,

while trying to figure out why the heck I sometimes have a problem with 
konsole on some machines and not on other machines I found out the following 
issue: xfonts-* packages have a call for 

update-fonts-dir update-fonts-alias

in their postinst/postrm

so those probably need to be added to the xfonts-konsole package too in their 
respective postinst/postrm. Further, xfonts-konsole packages:


/usr/share/fonts/9x15.pcf.gz
/usr/share/fonts/console8x16.pcf.gz
/usr/share/fonts/console8x8.pcf.gz
/usr/X11R6/lib/X11/fonts/misc/console8x8.pcf.gz
/usr/X11R6/lib/X11/fonts/misc/console8x16.pcf.gz

which means that 9x15.pcf.gz is missing in /usr/X11R6/lib/X11/fonts/misc/.

Also the question is why they get installed in /usr/share/fonts instead of 
/usr/share/fonts/misc.

Chris, Daniel, do you know anything about that ? I would very much like to 
bring this into a usable state so people don't run into the same problems 
over and over again. A postinst/postrm scheme for processing the update-fonts 
commands can be found in the respective xfree86 packages, so it is kind of 
easy to add that to kdebase in CVS for KDE_3_1_BRANCH and HEAD.

Ralf

- -- 
We're not a company, we just produce better code at less costs.
- 
Ralf Nolden
[EMAIL PROTECTED]

The K Desktop Environment   The KDevelop Project
http://www.kde.org  http://www.kdevelop.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+rTWbu0nKi+w1Ky8RAg2sAJwJSIMps97WTAD9iMm5Oa8eqBkStQCeJ293
k6kk0k2QW89v9aQll0be3Jo=
=Ke34
-END PGP SIGNATURE-





Re: xfonts-konsole issues

2003-04-28 Thread Daniel Stone
On Mon, Apr 28, 2003 at 04:07:17PM +0200, Ralf Nolden wrote:
 while trying to figure out why the heck I sometimes have a problem with 
 konsole on some machines and not on other machines I found out the following 
 issue: xfonts-* packages have a call for 
 
 update-fonts-dir update-fonts-alias
 
 in their postinst/postrm
 
 so those probably need to be added to the xfonts-konsole package too in their 
 respective postinst/postrm. Further, xfonts-konsole packages:
 
 
 /usr/share/fonts/9x15.pcf.gz
 /usr/share/fonts/console8x16.pcf.gz
 /usr/share/fonts/console8x8.pcf.gz
 /usr/X11R6/lib/X11/fonts/misc/console8x8.pcf.gz
 /usr/X11R6/lib/X11/fonts/misc/console8x16.pcf.gz
 
 which means that 9x15.pcf.gz is missing in /usr/X11R6/lib/X11/fonts/misc/.
 
 Also the question is why they get installed in /usr/share/fonts instead of 
 /usr/share/fonts/misc.
 
 Chris, Daniel, do you know anything about that ? I would very much like to 
 bring this into a usable state so people don't run into the same problems 
 over and over again. A postinst/postrm scheme for processing the update-fonts 
 commands can be found in the respective xfree86 packages, so it is kind of 
 easy to add that to kdebase in CVS for KDE_3_1_BRANCH and HEAD.

I could believe that, yeah. Looks like:
* They need to go in /usr/share/fonts/misc, or /usr/X11R6/lib/X11/fonts/misc.
* postinst/postrm *DEFINITELY* needs to call update-fonts-*!

-- 
Daniel Stone [EMAIL PROTECTED]
Developer, Trinity College, University of Melbourne


pgp0vrvz4Bm4C.pgp
Description: PGP signature


Re: xfonts-konsole issues

2003-04-28 Thread Ralf Nolden
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Montag, 28. April 2003 16:18, Daniel Stone wrote:
 On Mon, Apr 28, 2003 at 04:07:17PM +0200, Ralf Nolden wrote:
  while trying to figure out why the heck I sometimes have a problem with
  konsole on some machines and not on other machines I found out the
  following issue: xfonts-* packages have a call for
 
  update-fonts-dir update-fonts-alias
 
  in their postinst/postrm
 
  so those probably need to be added to the xfonts-konsole package too in
  their respective postinst/postrm. Further, xfonts-konsole packages:
 
 
  /usr/share/fonts/9x15.pcf.gz
  /usr/share/fonts/console8x16.pcf.gz
  /usr/share/fonts/console8x8.pcf.gz
  /usr/X11R6/lib/X11/fonts/misc/console8x8.pcf.gz
  /usr/X11R6/lib/X11/fonts/misc/console8x16.pcf.gz
 
  which means that 9x15.pcf.gz is missing in
  /usr/X11R6/lib/X11/fonts/misc/.
 
  Also the question is why they get installed in /usr/share/fonts instead
  of /usr/share/fonts/misc.
 
  Chris, Daniel, do you know anything about that ? I would very much like
  to bring this into a usable state so people don't run into the same
  problems over and over again. A postinst/postrm scheme for processing the
  update-fonts commands can be found in the respective xfree86 packages, so
  it is kind of easy to add that to kdebase in CVS for KDE_3_1_BRANCH and
  HEAD.

 I could believe that, yeah. Looks like:
 * They need to go in /usr/share/fonts/misc, or
 /usr/X11R6/lib/X11/fonts/misc.

They are currently, for whatever reason, installed in both except 9x15.pcf.gz. 
Where do they have to go to now ? I'd propose /usr/X11R6/lib/X11/fonts/misc 
because that's where they belong to. 

 * postinst/postrm *DEFINITELY* needs to call
 update-fonts-*!

Should we copy + paste this from your xf4.3/debian/xfonts-base.postinst/postrm 
? I'm on IRC if you want to do this now :-)

Ralf

- -- 
We're not a company, we just produce better code at less costs.
- 
Ralf Nolden
[EMAIL PROTECTED]

The K Desktop Environment   The KDevelop Project
http://www.kde.org  http://www.kdevelop.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+rT5Yu0nKi+w1Ky8RAqsxAJ9xRAKtlzwyWFAhll9fN1jFg8UpuQCeM5RJ
lRf85wA90nOJMSqOHICVF4w=
=rAK6
-END PGP SIGNATURE-





Re: xfonts-konsole issues

2003-04-28 Thread Ralf Nolden
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Montag, 28. April 2003 16:18, Daniel Stone wrote:
 On Mon, Apr 28, 2003 at 04:07:17PM +0200, Ralf Nolden wrote:
  /usr/share/fonts/9x15.pcf.gz
  /usr/share/fonts/console8x16.pcf.gz
  /usr/share/fonts/console8x8.pcf.gz
  /usr/X11R6/lib/X11/fonts/misc/console8x8.pcf.gz
  /usr/X11R6/lib/X11/fonts/misc/console8x16.pcf.gz
 
Update:

debian/xfonts-konsole.links just creates the two links for console*pcf.gz 
files, not for the 9x15.pcf.gz file. Those three get installed into 
/usr/share/fonts, so what's needed is probably:

xfonts-konsole.install: fix location to /usr/share/fonts/misc
xfonts-konsole.links: add missing symlink and change /usr/share/fonts - 
/usr/share/fonts/misc.

Then the missing postinst/postrm and we're set.

Ralf


  which means that 9x15.pcf.gz is missing in
  /usr/X11R6/lib/X11/fonts/misc/.
 
  Also the question is why they get installed in /usr/share/fonts instead
  of /usr/share/fonts/misc.
 
  Chris, Daniel, do you know anything about that ? I would very much like
  to bring this into a usable state so people don't run into the same
  problems over and over again. A postinst/postrm scheme for processing the
  update-fonts commands can be found in the respective xfree86 packages, so
  it is kind of easy to add that to kdebase in CVS for KDE_3_1_BRANCH and
  HEAD.

 I could believe that, yeah. Looks like:
 * They need to go in /usr/share/fonts/misc, or
 /usr/X11R6/lib/X11/fonts/misc. * postinst/postrm *DEFINITELY* needs to call
 update-fonts-*!

- -- 
We're not a company, we just produce better code at less costs.
- 
Ralf Nolden
[EMAIL PROTECTED]

The K Desktop Environment   The KDevelop Project
http://www.kde.org  http://www.kdevelop.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+rUP0u0nKi+w1Ky8RAndrAKCw7XwaLNCw2fSdZJ7a9M9CVSKprgCgh5Sk
KYkaFWDilQSTs5T15Ehqlqc=
=TO70
-END PGP SIGNATURE-





Re: xfonts-konsole issues

2003-04-28 Thread Chris Cheney
On Mon, Apr 28, 2003 at 04:07:17PM +0200, Ralf Nolden wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi guys,
 
 while trying to figure out why the heck I sometimes have a problem with 
 konsole on some machines and not on other machines I found out the following 
 issue: xfonts-* packages have a call for 
 
 update-fonts-dir update-fonts-alias
 
 in their postinst/postrm
 
 so those probably need to be added to the xfonts-konsole package too in their 
 respective postinst/postrm. Further, xfonts-konsole packages:

I think this should be taken care of by dh_installxfonts which is already
in the rules file but I don't remember why it is isn't happening for kde
right now.

 /usr/share/fonts/9x15.pcf.gz
 /usr/share/fonts/console8x16.pcf.gz
 /usr/share/fonts/console8x8.pcf.gz
 /usr/X11R6/lib/X11/fonts/misc/console8x8.pcf.gz
 /usr/X11R6/lib/X11/fonts/misc/console8x16.pcf.gz
 
 which means that 9x15.pcf.gz is missing in /usr/X11R6/lib/X11/fonts/misc/.
 
 Also the question is why they get installed in /usr/share/fonts instead of 
 /usr/share/fonts/misc.

Isn't this really an upstream issue? The fonts are being dumped directly
into fontdir, which is (/usr/share/fonts) in our case, by it. Also a
9x15 font is already in Xfree xfonts-base package so that font in
xfonts-konsole should likely go away entirely, to keep from confusing
the font subsystem.

usr/X11R6/lib/X11/fonts/misc/9x15.pcf.gzx11/xfonts-base

 Chris, Daniel, do you know anything about that ? I would very much like to 
 bring this into a usable state so people don't run into the same problems 
 over and over again. A postinst/postrm scheme for processing the update-fonts 
 commands can be found in the respective xfree86 packages, so it is kind of 
 easy to add that to kdebase in CVS for KDE_3_1_BRANCH and HEAD.

Regardless of the above issues this shouldn't be the reason people are
having font problems with KDE since Qt no longer uses the standard Xfree
method for locating fonts. According to puetzk the reason we see font
substitions happening is because Qt lists fonts that Xfree can see but
can't actually use them. If I remember correctly the fix is in Qt 3.1.2
and is to not list fonts from Xfree at all.

Chris




Re: xfonts-konsole issues

2003-04-28 Thread Ralf Nolden
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Montag, 28. April 2003 18:44, Chris Cheney wrote:
 On Mon, Apr 28, 2003 at 04:07:17PM +0200, Ralf Nolden wrote:
  Also the question is why they get installed in /usr/share/fonts instead
  of /usr/share/fonts/misc.

 Isn't this really an upstream issue? The fonts are being dumped directly
 into fontdir, which is (/usr/share/fonts) in our case, by it. Also a
 9x15 font is already in Xfree xfonts-base package so that font in
 xfonts-konsole should likely go away entirely, to keep from confusing
 the font subsystem.

It is, because you usually install KDE into $KDEDIR - which is by default 
/usr/local/kde; on a SuSE system this would be /opt/kde3. As we're using /usr 
as a prefix, the font files end up in /usr/share/fonts.

I've fixed the issues in both HEAD and BRANCH now like discussed with Chris on 
IRC.

 Regardless of the above issues this shouldn't be the reason people are
 having font problems with KDE since Qt no longer uses the standard Xfree
 method for locating fonts. According to puetzk the reason we see font
 substitions happening is because Qt lists fonts that Xfree can see but
 can't actually use them. If I remember correctly the fix is in Qt 3.1.2
 and is to not list fonts from Xfree at all.

Qt 3.1.2 isn't in unstable :-) and it will take a while since the problem is 
related to glibc IIRC what madkiss said why he couldn't upload it yet. Qt 3.2 
will come out as a beta this week but that won't help too much I guess.

Ralf


 Chris

- -- 
We're not a company, we just produce better code at less costs.
- 
Ralf Nolden
[EMAIL PROTECTED]

The K Desktop Environment   The KDevelop Project
http://www.kde.org  http://www.kdevelop.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+rWVOu0nKi+w1Ky8RApnxAKC38yjK7cYGIcMscUFZwHEgLKgwOACgunK7
Dey6ExE/r75WgyXmVtA+vDI=
=LBhx
-END PGP SIGNATURE-





Re: xfonts-konsole issues

2003-04-28 Thread Chris Cheney
On Mon, Apr 28, 2003 at 07:30:51PM +0200, Ralf Nolden wrote:
  Regardless of the above issues this shouldn't be the reason people are
  having font problems with KDE since Qt no longer uses the standard Xfree
  method for locating fonts. According to puetzk the reason we see font
  substitions happening is because Qt lists fonts that Xfree can see but
  can't actually use them. If I remember correctly the fix is in Qt 3.1.2
  and is to not list fonts from Xfree at all.
 
 Qt 3.1.2 isn't in unstable :-) and it will take a while since the problem is 
 related to glibc IIRC what madkiss said why he couldn't upload it yet. Qt 3.2 
 will come out as a beta this week but that won't help too much I guess.

Yes, I know, the point was that Qt doesn't use XFree's fonts now but
instead substitutes fonts in place of the one you think you are
choosing. The fact that XFree doesn't know about the font, by not being
in its /usr/X11R6/lib/X11/fonts/misc and in fonts.dir file, doesn't
matter to KDE since Qt doesn't actually use them for anything other than
the actual list of fonts anyway. Of course by registering the console
fonts with Xfree other non-Qt and non-fontconfig apps will be able to
use them as well, which is a good thing.

Chris




Re: xfonts-konsole issues

2003-04-28 Thread Alan Chandler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday 28 Apr 2003 3:07 pm, Ralf Nolden wrote:
 Hi guys,

 while trying to figure out why the heck I sometimes have a problem with
 konsole on some machines and not on other machines I found out the
 following issue: xfonts-* packages have a call for

 update-fonts-dir update-fonts-alias

 in their postinst/postrm

Since QT uses fontconfig for locating fonts should not fc-cache be called?



 so those probably need to be added to the xfonts-konsole package too in
 their respective postinst/postrm. Further, xfonts-konsole packages:


 /usr/share/fonts/9x15.pcf.gz
 /usr/share/fonts/console8x16.pcf.gz
 /usr/share/fonts/console8x8.pcf.gz
 /usr/X11R6/lib/X11/fonts/misc/console8x8.pcf.gz
 /usr/X11R6/lib/X11/fonts/misc/console8x16.pcf.gz

 which means that 9x15.pcf.gz is missing in /usr/X11R6/lib/X11/fonts/misc/.

 Also the question is why they get installed in /usr/share/fonts instead of
 /usr/share/fonts/misc.

When I was trying to find out why konsole never used these fonts, I discovered 
that fontconfig matched a japanese font in preference to these anyway.  This 
was to do with them both having the family name of fixed (the other font 
is in xfonts-base which has to be installed with an xserver).  I suspect 
there is a random choice based upon which order directories are searched. 

I ended up adding some lines into the /etc/fonts/local.conf to specify that I 
wanted the console to be the default fixed font.  

[This is only related to the font that konsole picks in the normal case.  In 
fact there is a potential konsole bug here in that it should ask for 
monospace font rather than fixed so I am not proposing that you do 
anything with the /etc/fonts/* files.]

- -- 
Alan Chandler
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+rXZjuFHxcV2FFoIRAn2FAJ9ZKqW0O43NrPAFkAu+cGZeSIXXFgCgkJ7Y
ThjzFYQxmqaZdOsXSMzq+Oc=
=U9Fc
-END PGP SIGNATURE-




konsole issues

2001-10-22 Thread Justin R. Miller
I'm running unstable, so I have KDE 2.2.1.  Whenever I make an app
launcher and check 'run in terminal', it runs the app (like Mutt) inside
of an xterm and not konsole.  I've even looked into the whole
System::Konsole::General section of kcontrol and those settings have no
effect.  Any ideas as to why this happens?

-- 
Justin R. Miller [EMAIL PROTECTED]
PGP/GnuPG Key ID 0xC9C40C31 (preferred)


pgppEIvvXHB74.pgp
Description: PGP signature


Re: konsole issues

2001-10-22 Thread Wilco Greven
On Mon, Oct 22, 2001 at 05:24:14PM -0400, Justin R. Miller wrote:
 I'm running unstable, so I have KDE 2.2.1.  Whenever I make an app
 launcher and check 'run in terminal', it runs the app (like Mutt) inside
 of an xterm and not konsole.  I've even looked into the whole
 System::Konsole::General section of kcontrol and those settings have no
 effect.  Any ideas as to why this happens?

In the System/Konsole, in kcontrol, there is an option Do not use
Konsole as default terminal application. It should be unchecked.

Greetings,
Wilco




Re: konsole issues

2001-10-22 Thread David Bishop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday 22 October 2001 02:59 pm, Wilco Greven wrote:
 On Mon, Oct 22, 2001 at 05:24:14PM -0400, Justin R. Miller wrote:
  I'm running unstable, so I have KDE 2.2.1.  Whenever I make an app
  launcher and check 'run in terminal', it runs the app (like Mutt) inside
  of an xterm and not konsole.  I've even looked into the whole
  System::Konsole::General section of kcontrol and those settings have no
  effect.  Any ideas as to why this happens?

 In the System/Konsole, in kcontrol, there is an option Do not use
 Konsole as default terminal application. It should be unchecked.


Also, check and see what /etc/alternatives/x-terminal-emulator points to.  
$$'s to donut holes it is pointing to /usr/X11R6/bin/xterm.  Use 
update-alternatives to change that.

HTH.

- -- 
D.A.Bishop
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE71Kx3KEJ4huP2XBERAnEiAJ4wb5jnRN0zPfszlvX47ve93BbABgCaA3oA
iRPjcJRx1W0Gk8AhjGUaasU=
=72PD
-END PGP SIGNATURE-




Re: konsole issues

2001-10-22 Thread Justin R. Miller
Thus spake Jens Benecke ([EMAIL PROTECTED]):

 In kcontrol the 'console' application is probably set for
 'x-terminal-emulator', which is the default 'terminal emulator' for
 _all_ Debian applications. You can either change that (only for KDE)
 or change x-terminal-emulator via 'update-alternatives' which makes
 konsole available to all applications that need a terminal.

Thanks for the tip (you too David) -- using update-alternatives did the
trick.  I still can't figure out why KDE wasn't paying attention to the
setting in kcontrol though -- that is the very one I was toggling.  I'd
like to think that it would work and I wouldn't have to change the
system-wide default (though it's ok in this case). 

-- 
Justin R. Miller [EMAIL PROTECTED]
PGP/GnuPG Key ID 0xC9C40C31 (preferred)


pgpJIUKl8THJT.pgp
Description: PGP signature