SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
recently i was without internet for a week or so, and during that time mc would take a long time to start up. i did have the machine on a local network though. once i got internet again mc takes about a second to load.... at the same time, i see the message in the terminal window that says "no protocol specified" as mc loads. is mc trying to "phone home" or something? i'm guessing the two are related. where in the settings for mc would i look to change this behavior?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,086
Rep:
Something similar has happened with Midnight Commander on my machine. If I open a terminal window, sign-in as root, and then try to run mc it either takes a very long time to start up or it doesn't start at all. Not a problem when I start mc in a terminal window as a user.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,086
Rep:
Thirty Seconds to Start Midnight Commander.
This is still a problem and has been a consistent problem for quite a while.
I just opened a console, as user, and typed, mc, and hit enter. It took 30 seconds for the midnight commander to appear.
It would appear to have something to do with being online at the time.
Using 14.2-current and it doesn't matter if the desktop is Xfce or KDE, the result is the same.
Last edited by cwizardone; 07-14-2016 at 12:20 PM.
Reason: Typo.
I do not see this behavior with /var/log/packages/mc-4.8.16-x86_64-2 coming with Slackware, whether being on- or off-line.
I am on Xfce; with Wicd as networkmanager.
I have seen, though, problems with other filemanagers (Thunar especially) when I had distant file-shares mounted via cifs at the time the computer was sent to sleep (say at work, leaving for the station) and resuming outwith the previous network (say on the train home). The whole system became sluggish. The way around that was making sure that everything distant was unmounted before suspend. So something else related to your network could cause this. More info seems needed to find out whether it is really mc.
It's possible mc is trying to reach for DNS if certain conditions are met, in my case it only hangs if the interface is up but the gateway is down.
Maybe logging outgoing packets would help identify the cause, so that one can filter them with iptables and eliminate any delays.
Bringing down the interface every time the gateway is down, well that would probably fix it, but I'm fine with the current setup and I don't mind rebuilding the package since I only use it locally.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.