Slack not starting my pcmanfm anymore and terminology
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.
Slack not starting my pcmanfm anymore and terminology
this has happened before with terminology, where all I had to do was delete my config file for it then it started working again. this is the second time I've had to deal with this.
this time,
I am playing about with libimobiledevice off of git trying to get me a install for the latest one using a SlackBuild when I ran it then that is when this started happening, my ability to start up a a terminology and pcmanfm stopped working.
I deleted the conf for terminology - tried starting it again, didn't work. reboot tried it again, it worked once, now it is not working again off the keyboard short cuts and the menu in Fluxbox .
now my file manager pcmanfm is doing the same thing,
WOW terminology is just opening up that was about a minute or so delay from issuing the command to open one.
but my filemanager is still not working per the code I posted in here, I use sboinstall I removed everything with it using sboremove then re installed it using sboinstall and that is what I am left with,
Code:
userx%slackwhere ⚡ libimobiledevice ⚡> pcmamfm
bash: pcmamfm: command not found
userx%slackwhere ⚡ libimobiledevice ⚡> whereis pcmanfm
pcmanfm: /usr/bin/pcmanfm /usr/lib64/pcmanfm /usr/share/pcmanfm /usr/man/man1/pcmanfm.1.gz
userx%slackwhere ⚡ libimobiledevice ⚡> ls /usr/bin/pcmanfm
/usr/bin/pcmanfm
it is green so yes it is marked executable.
I am not in the mood at this moment to just reinstall Slack again to do that radical fix it move. not that I couldn't.
ok but I am still waiting for it to open off the command line .. still waiting ... tick tick tick goes the clock ... over a minute 30 secs still not opened.. what do I do to check it ?
Well, only you can know what changes you made on your system that triggered this issue. Although I fail to see how "playing about with libimobiledevice off of git"could have such an effect, even though I do not know what you actually did, tersely described as "playing about".
Anyway, both pcmanfm and terminology work here.
Let's try to investigate first about pcmanfm, that I use all the time (it's the default file manager in Slint version 14.2).
What are your system's version and architecture?
Is it a full Slackware installation, with no major modification ?
How did you build pcmanfm? From what source archive? What version?
What happens if you fire up an xterm and type:
Code:
pcmanfm &
Is a process number displayed in the terminal (as it should)?
Does a window for pcmanfm appears?
If yes, how long does it take?
Also, please append or attach to your next post the full output of
Well, only you can know what changes you made on your system that triggered this issue. Although I fail to see how "playing about with libimobiledevice off of git"could have such an effect, even though I do not know what you actually did, tersely described as "playing about".
I was using an SlackBuild for libimobiledevice libimobiledevice.SlackBuild when I cloned git I ran automake.sh to get configure then I tar.bz2 it, then ran libimobiledevice.SlackBuild on it. what I that is when it screwed it up.
the only thing I failed to do was within the tar I made using ark was to rename the actual dir libimobiledevice-1.2.1 that is what caused the error. but does not explain why it tossed Slackware into no longer starting terminology and pcmanfm by any means available
I've reinstalled Slack so and but that does not fix nor explain this phenomenon.
I was using an SlackBuild for libimobiledevice libimobiledevice.SlackBuild when I cloned git I ran automake.sh to get configure then I tar.bz2 it, then ran libimobiledevice.SlackBuild on it. what I that is when it screwed it up.
the only thing I failed to do was within the tar I made using ark was to rename the actual dir libimobiledevice-1.2.1 that is what caused the error. but does not explain why it tossed Slackware into no longer starting terminology and pcmanfm by any means available
I've reinstalled Slack so and but that does not fix nor explain this phenomenon.
In some cases running a SlackBuild can change permissions and ownership among other nasty things. Even if I wrote "it is marked green so it is marked executable"[1], I would have advised you to really check with this command:
Code:
stat /usr/bin/pcmanfm
but now it's too late.
[1]Depending on your settings "green" may mean other things than "executable file", like "binary file".
Last edited by Didier Spaier; 06-19-2017 at 01:07 PM.
n some cases running a SlackBuild can change permissions and ownership among other nasty things. Even if I wrote "it is marked green so it is marked executable", I would have advised you to really check with
Code:
stat /usr/bin/pcmanfm
but now it's too late.
I'll keep that in mind for next time, because as I've stated this is twice it happened to me. with Terminology this second time it took pcmanfm away.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.