Edulix wrote:
>Well, I'm using qt-copy which seems to be 4.2.0-snapshot-20061002 . Do
you mean getting qt 4.2 from trolltech instead?
That snapshot and the released 4.2.0 are one and the same.

El Viernes, 10 de Noviembre de 2006 18:33, Stephan Kulow :
Do you use KDE4 in your normal session or are you using e.g. Xnest? Then
this might be because of this

Greetings, Stephan

I've tested all known methods: Neither via ssh, Xnest or Xephyr does qtconfig
(for qt 4) detect any antialiased font, neither do any KDE4 aplication.

The one which give me more hopes is starting it in a new normal Xorg session
because there when I execute qtconfig it allows me to select among
antialiased fonts. But still, in any KDE4 app (konqueror, konsole, etc) they
only detect not antialiased fonts. I've made a screenshot of an Xorg session
showing this [1]. There you can see qtconfig using BitStream Vera while
konqueror doesn't even shot it in the font list.

Starting KDE4 applications via ssh has not been successful to me, they all
seem to crash. For example, this is the backtrace for kwrite:
Using host libthread_db library "/".
[Thread debugging using libthread_db enabled]
[New Thread -1234851360 (LWP 30754)]
[KCrash handler]
#5 0xffffe410 in __kernel_vsyscall ()
#6 0xb6778770 in raise () from /lib/tls/i686/cmov/libc.so.6
#7 0xb6779ef3 in abort () from /lib/tls/i686/cmov/libc.so.6
#8 0xb76bdbed in kDebugBackend (nLevel=3, nArea=101,
data=0x80b3e30 "FATAL: Session bus not found\n")
at /
#9 0xb76bdcc0 in kdbgstream::flush (this=0xbff5857c)
at /
#10 0xb76b9eb1 in kdbgstream::operator<< (this=0xbff5857c, string=@0xbff583ec)
at /
#11 0xb7ec3ef0 in kdbgstream::operator<< (this=0xbff5857c,
string=0xb7ed2b72 "\n")
at /
#12 0xb7ec3f2d in endl (s=@0xbff5857c)
at /
#13 0xb76b9c0f in kdbgstream::operator<< (this=0xbff5857c,
f=0xb7ec3f06 <endl(kdbgstream&)>)
at /
#14 0xb76ae1ea in KApplication::init (this=0xbff586a8)
at /
#15 0xb76af62a in KApplication (this=0xbff586a8, GUIenabled=true)
at /
#16 0xb7ee7f7f in kdemain (argc=1, argv=0xbff58864)
at /
#17 0x08048746 in main (argc=)
at /

And this is what I did in the terminal:

edulix@sinpalo:~$ ssh -X kde-devel@localhost
kde-devel@sinpalo:~$ dbus-launch # check dbus-running (it is, in Xorg in :20 )
,
DBUS_SESSIN_BUS_PID=31081
kde-devel@sinpalo:~$ kwrite -v # check right version of kwrite
Qt: 4.2.0-snapshot-20061002
KDE: 3.80.2 (>= 20061026)
KWrite: 4.80.2
kde-devel@sinpalo:~$ kwrite
D-Bus library appears to be incorrectly set up; failed to read machine uuid:
Failed to open "/": No such file or
directory
See the manual page for dbus-uuidgen to correct this issue.
Continuing with a bogus made-up machine UUID, which may cause problems.kwrite:
FATAL: Session bus not found
KCrash: crashing crashRecursionCounter = 2
KCrash: Application Name = kwrite path = <unknownpid = 31073
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
D-Bus library appears to be incorrectly set up; failed to read machine uuid:
Failed to open "/": No such file or
directory
See the manual page for dbus-uuidgen to correct this issue.
Continuing with a bogus made-up machine UUID, which may cause problems.
kde-devel@sinpalo:~$

Thanks for your time,
Edulix.

Edulix wrote:
>kde-devel@sinpalo:~$ dbus-launch # check dbus-running (it is, in Xorg in
:20 )
,guid=351757
>456a4d4f4c2a9d2331da95ff00
>DBUS_SESSIN_BUS_PID=31081

This is not how you run dbus-launch. It's supposed to be:
eval `dbus-launch`

Either that, or you should run the command it's just output and export the
variables.

But, starting with D-Bus 0.94, you no longer need to do that. D-Bus
starting should be automatic:

>kde-devel@sinpalo:~$ kwrite
>D-Bus library appears to be incorrectly set up; failed to read machine
uuid: Failed to open "/": No
such file or directory
>See the manual page for dbus-uuidgen to correct this issue.

This is it trying to auto-start the daemon. But you seem not to have cared
about proper installation nor read the manual.
Running "dbus-uuidgen " is a post-installation required pass.
(Since it's post-installation, "make install" won't do it).

>Continuing with a bogus made-up machine UUID, which may cause
problems.
kwrite: FATAL: Session bus not found

Hello,

El Domingo, 12 de Noviembre de 2006 14:07, Thiago Macieira :
Edulix wrote:
>kde-devel@sinpalo:~$ dbus-launch
,guid=351757
>456a4d4f4c2a9d2331da95ff00
>DBUS_SESSIN_BUS_PID=31081
>
This is not how you run dbus-launch. It's supposed to be:
eval `dbus-launch`

Good to know. That's all new to me

But, starting with D-Bus 0.94, you no longer need to do that. D-Bus
starting should be automatic:
>kde-devel@sinpalo:~$ kwrite
>D-Bus library appears to be incorrectly set up; failed to read machine
uuid: Failed to open "/": No
such file or directory
>See the manual page for dbus-uuidgen to correct this issue.
>
This is it trying to auto-start the daemon. But you seem not to have cared
about proper installation nor read the manual.
Running "dbus-uuidgen " is a post-installation required pass.
(Since it's post-installation, "make install" won't do it).

*touch* RTFM & RTF!
It's my fault, I should have read the output, no excuse.

Though I don't think it's fair to pretend people should read the manual of
everything they install when you know that most probably they followed the
howto which didn't mention that missing step.I used the howto [1]. I also
know about this other howto [2]. In the later one, that post-instalation step
was added 10 days ago, but I had read it only once and before that date. And
I decided to use the first one, which didn't mention dbus-uuidgen

Now both howtos are updated so new kde developers should not have this
problem ;-).

>Continuing with a bogus made-up machine UUID, which may cause
problems.
kwrite: FATAL: Session bus not found

Now I'm getting this:

kde-devel@sinpalo:~$ ~/kde/bin/kwrite
kwrite: FATAL: Session bus not found
KCrash: crashing crashRecursionCounter = 2
KCrash: Application Name = kwrite path = <unknownpid = 6922
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly

Now with a genuine, non-bogus machine UUID :P

(And still without antialiasedfonts, which is the main problem)

more,
Edulix.

Eduardo Robles Elvira wrote:
>Though I don't think it's fair to pretend people should read the manual
of everything they install when you know that most probably they
followed the howto which didn't mention that missing step.

I'm sorry, this is a new step that is only necessary if you use the
auto-starter. You would never had run into this error message if the
daemon had been started correctly. (the "dbusstart" step, which is no
longer necessary)

I used the
howto [1]. I also know about this other howto [2]. In the later one,
that post-instalation step was added 10 days ago, but I had read it
only once and before that date. And I decided to use the first one,
which didn't mention dbus-uuidgen
>
>Now both howtos are updated so new kde developers should not have this
>problem ;-).

Thank you.

>Now I'm getting this:
>
>kde-devel@sinpalo:~$ ~/kde/bin/kwrite
>kwrite: FATAL: Session bus not found
>KCrash: crashing crashRecursionCounter = 2
>KCrash: Application Name = kwrite path = <unknownpid = 6922
>Warning: connect() failed: : No such file or directory
>KCrash cannot reach kdeinit, launching directly
>
>Now with a genuine, non-bogus machine UUID :P

Can you get me a backtrace of this crash?