Hmmm. Maybe this belongs in a separate thread, but here's my 12.2 information:
And from /var/log/packages/mozilla-firefox-3.0.11-1686-1:
None of those libs are contained in any seamonkey packages at 12.2.

But everything appears to work fine, despite the "not found" errors from ldd.

Cheers.

FWIW, I have installed the Seamonkey solibs, as well as SM itself, and nothing is any different that I can detect. Everything that worked before still works, and I can't find too much that's broken in general. I haven't had/seen any LDD errors anywhere either.

There are a few tiny things that I notice now and then, which I think I will call bugs, but I can't say that any of them are attributable to Slackware64 proper, but instead I think that the behind-the-scenes stuff of XFCE, KDE-services, and X/nvidia has a couple bugs and application-mis-communications sometimes (I'm using XFCE as I am not really swept away by the new KDE and its background services like nepomuk thing, strigi-whatever-it-is -- that might change with time, but as I adjust to XFCE I come to like its relative simplicity. Plus, the new Konqueror lacks one or two things I really appreciated in the 3.5.4 edition, including the ability to configure different background colors for Konqueror for root vs myself--- I can't seem to get that set up)

Here's a few 'things' I notice, but I really have not been compiling a list of 'problems' because there doesn't seem to be any severe items to report:

1 - starting additional X sessions doesn't always work; X starts, but the DE doesn't take over.
2 - applications (some of them) start on the wrong/other monitor (even works both ways!)
3 - I restarted rc.messagebus the other day and was booted out to login (maybe this is to be expected?)
4 - I can't get X/randR working, but as stated elsewhere, this is probably 'cause of my video/monitor/Xinerama setup.
5 - kdesu sometimes borks, failing to start anything
5b- kdesu sometimes decides not to accept root password anymore -- same old bug as KDE-3.5.4 I think, whereby kdeinit (and now also kdeinit4) need to be re-executed in a console because the KDE background service(s) which depend on it all stop working)
6 - mc takes a LONG time to start in an Xterm -- like 5 seconds or more, when it's typically instantaneous (lib issues??)
7 - starting some apps causes a "Starting Knotify" taskbar item to appear for about 10 secs, then it goes away. The app usually starts.
8 - konqueror's 'Go' dropdown menu is full of 'Malformed URL' items. Can't 'go' anywhere from the 'Go' menu.

All in all, Slackware64-current seems as stable as should be expected; no crashes, no bizarre fatal errors, etc.. Works well.

Sasha

Do you by any chance got a lot of files and directories where mc started?
In this case you might notice a / going round like a timer indicate loading in the top right of the screen.

Hmm, doesn't seem to matter how many files/folders are where I am starting mc, and I have not noticed any little progress spinner thing either during the delay, though there could conceivably be one somewhere.

I'm gonna have to do a reboot and run mc during various stages of the full boot, because it doesn't happen all the time, or even most of the time. Right now, mc starts like it always did: FAST. But I will reboot and try it from a console first, both as root and as user, and then from the desktop as root and user, and see what happens. If it's still weird, I'll start a new Slack64 thread on it.

Sasha

UPDATE - well, beats me, but I can't re-create the delay currently. mc worked fine in the console and on desktop after reboot.. Who knows.

From a usenet post I've recently seen:

@ Rupa -- thank you for posting that information there, that *might* just be related to the issue... Maybe.

For the first few days (until today actually) I had had my machine's hostname set to 'hostname', and that caused an error message (harmless one) from XFCE at login to the effect that ".. stuff would probably not work right because XFCE cannot resolve the hostname hostname..." so this message, plus taking into account the info that you posted above, makes me inclined to think that perhaps (for whatever reason) mc was also looking at hostname or DNS information when it first started; on subsequent startups, it had already written off the hostname, so the delay was gone/skipped.

For the record, I have no remotely mounted shares or drives, no NFS or anything like that. I do have an FTP server running on another machine, but I don't access it with mc. And finally, my delay was about 5-7 seconds, not 30, but that could simply be a config/compilation option somewhere set differently.

I suppose I should do a test -- change the hostname back to 'hostname' and see if the problem re-appears. Will do that tomorrow or so, it's getting late for reboots

Thanks again Rupa for that post, whether or not that's the cause -- it seems possible to me.

Sasha