Hi BM:
Thanks for the reply. I was not ignoring your message - just
trying some more things as time permitted. I have another system
that is very similar to this one (same m'board, BIOS, SCSI
driver, ... ) and took it down to do an install with RC2. It
appears that this is a UPGRADE related problem because mdkkdm
runs on the clean install.
I have not yet found the problem/resolution but I have included a
LOT of more info here if you are (still) interested in this
'upgrade 9->9.2' problem.
kdm was removed by the RC2 installer but not
re-installed(upgraded) during the upgrade from 9 -> 9.2RC2. I
later installed kdm with other KDE upgrades from cooker in hopes
that it would resolve the problems.
After installing kdm, I found it had the same problem as mdkkdm(
figures... :) So, basically the info here applies to both QT
dm's.
startx works to load KDE, so, yes, AFAIK, KDE and QT are okay. I
do not use KDE much but have used kpackage quite a bit and it
works as well as expected. KDE desktop _looked_ okay ...
Fortunately, gdm and startxfce (and startxfce4, too) work. ...
There's a lot of post-config problems here (mostly minor but very
annoying) and I just have not had the time/desire to hone-in on
this one. I am just not a QT guy: time to find pb & resolve it
is prohibitive for me. It is sooo late in the BETA/RC cycle that,
well I hope others do not have these problems ...
However, since you asked( and know about QT much more/better than
I ) here's the ldd for kdm_greet ( ldd mdkkdm_greet has same
output ):
#> ldd /usr/bin/kdm_greet
libXtst.so.6 => /usr/X11R6/lib/libXtst.so.6 (0x40029000)
libkdeui.so.4 => /usr/lib/libkdeui.so.4 (0x4002f000)
libkdecore.so.4 => /usr/lib/libkdecore.so.4 (0x4029d000)
libDCOP.so.4 => /usr/lib/libDCOP.so.4 (0x40431000)
libdl.so.2 => /lib/libdl.so.2 (0x40464000)
libresolv.so.2 => /lib/libresolv.so.2 (0x40467000)
libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2
(0x40478000)
libkdefx.so.4 => /usr/lib/libkdefx.so.4 (0x40490000)
libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3
(0x404bc000)
libpng.so.3 => /usr/lib/libpng.so.3 (0x40b51000)
libz.so.1 => /lib/libz.so.1 (0x40b78000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40b86000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40b95000)
libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40c78000)
libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40c81000)
libpthread.so.0 => /lib/i686/libpthread.so.0 (0x40c98000)
libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1
(0x40ce9000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40cf1000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40daa000)
libm.so.6 => /lib/i686/libm.so.6 (0x40db3000)
libc.so.6 => /lib/i686/libc.so.6 (0x40dd6000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
libaudio.so.2 => /usr/X11R6/lib/libaudio.so.2
(0x40f07000)
libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40f1d000)
libmng.so.1 => /usr/lib/libmng.so.1 (0x40f71000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40fcf000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x40fee000)
libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x4103b000)
libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x41052000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6
(0x41065000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1
(0x410b9000)
libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0x410e1000)
libexpat.so.0 => /usr/lib/libexpat.so.0 (0x41573000)
===
As you can see
libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3 (0x404bc000)
which is correct, AFAIK.
These are the libqt-mt* on the system(from slocate db):
2003-08-30 11:56 /usr/lib/qt3/lib/libqt-mt.prl
2003-09-13 00:37 /usr/lib/qt3/lib/libqt-mt.so ->
libqt-mt.so.3.1.2*
2003-09-13 00:32 /usr/lib/qt3/lib/libqt-mt.so.3 ->
libqt-mt.so.3.1.2*
2003-09-13 00:32 /usr/lib/qt3/lib/libqt-mt.so.3.1 ->
libqt-mt.so.3.1.2*
2003-08-30 11:58 /usr/lib/qt3/lib/libqt-mt.so.3.1.2*
There is one other anomally from the messages (not kdm log) that
said that it did not recognize " [Desktop0] "- the first line in
kdmrc. That is quite odd since " [Desktop0] " is in the
kdmrc.rpmnew file also.
Here's the related 'messages' output:
kdm_config[3113]: Unrecognized section name [Desktop0] at
/usr/share/config/kdm/kdmrc:1
kdm[3116]: Greeter exited unexpectedly
kdm[3116]: Abnormal helper termination, code 127, signal 0
kdm[3125]: Greeter exited unexpectedly
kdm[3125]: Abnormal helper termination, code 127, signal 0
kdm[3134]: Greeter exited unexpectedly
kdm[3134]: Abnormal helper termination, code 127, signal 0
kdm[3143]: Greeter exited unexpectedly
kdm[3143]: Abnormal helper termination, code 127, signal 0
kdm[3114]: Display :0 is being disabled (restarting too fast)
AT least once there was also this:
kdm_config[1161]: Invalid option value 'All' at
/usr/share/config/kdm/kdmrc:68
The "Line 68" is:
ShowUsers=All
I checked the kdmrc.rpmnew and "ShowUsers=All " was not in it.
On the off chance that kdmrc was at fault, I removed my kdmrc and
replaced it with the kdmrc.rpmnew, started KDE and the login
manager to verify/config it.
Note that I used the KDE Control Center ... Login Manager to
config kdm so there should not be a config problem...
But, maybe there is because it (the Login Manager) reinserted the
Line 68 "...All" ; i.e., I again had the "Invalid option" error.
I did try just the vanila kdmrc.rpmnew - no go there either.
I also did a strace of mdkkdm and kdm and put the outputs in two
files and compared them. Unfortunately it is mostly gobblygook
to me since I am not familiar with what it is supposed to be
doing. Nothing obvious other than it heavily depends on
libX11.so.6 and spends a lot of time looking for files in the
wrong places - Dangnabbit!! I was hoping it would hop-up and
say '' HEY! The error is right here! Fix this. '' but I could not
find that line. :-)
I have pretty much given up on it as, since doing the install on
the other system and seeing mdkkdm, I have come to the conclusion
that it is a blessing in disguise that it does not run.
If, however, you want more info, I will provide. Also, if it is
still a problem with final, I'll file a bug report and do what I
can to assist in huntin' & killin' it.
--- Buchan Milne <[EMAIL PROTECTED]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Robert Fox wrote:
> > Thanks for your reply - the one thing that caught my eye was:
> >
> > "Sep 17 12:33:34 amda7v kernel: Got silent jpeg."
> >
>
> Bootsplash related, I don't think it has any bearing here.
>
> > What does that mean?
> >
> > On Fri, 2003-09-19 at 18:58, Ric Johnson wrote:
> >
> >>check the var/log/mdkkdm.log.
> >>You may have somethiing like this:
> >>
> >>/usr/bin/kdm_greet: error while loading shared libraries:
> >>libqt-mt.so.3: cannot open shared object file: No such file
> or
> >>directory
> >>
> >>That one from my log is for KDM but it is the same log
> message
> >>for mdkkdm_greet: Neither KDM or MDKKDM will run here *at
> all*
> >>since upgrade of 9 to 9.2RC2. cooker upgrades have not
> helped so
> >>far.
> >>I have not found out what the message really means since
> >>libqt-mt* all do exist.
>
> But maybe the loader doesn't find them? What do you have in
> /etc/ld.so.conf, and what do you get with:
>
> $ ldd /usr/bin/kdm_greet
>
> Do other Qt apps run or not?
>
> >>BTW, this is an ASUS P2B-DS w/ 768MB and GF4-ti4200 - using
> >>nVidia drivers I built for each kernel update, currently
> >>2.4.22-10SMP. And, kdm ran flawlessly before the
> >>upgrade here too.
>
> Don't think this is hardware related.
>
> Regards,
> Buchan
Regards to you,
rj
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
