LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-19-2017, 08:46 AM   #1
BW-userx
Senior Member
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Void Linux / Slackware 14.2
Posts: 4,690

Rep: Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865
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.

Last edited by BW-userx; 06-19-2017 at 08:48 AM.
 
Old 06-19-2017, 09:04 AM   #2
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 3,786

Rep: Reputation: 1852Reputation: 1852Reputation: 1852Reputation: 1852Reputation: 1852Reputation: 1852Reputation: 1852Reputation: 1852Reputation: 1852Reputation: 1852Reputation: 1852
Quote:
Originally Posted by BW-userx View Post
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.
looks like the first time you wrote pcmamfm and not pcmanfm.
 
Old 06-19-2017, 09:08 AM   #3
BW-userx
Senior Member
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Void Linux / Slackware 14.2
Posts: 4,690

Original Poster
Rep: Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865
Quote:
Originally Posted by ponce View Post
looks like the first time you wrote pcmamfm and not pcmanfm.
perhaps but that does not excuse the reason why my menu and my keyboard shortcuts to open them are no longer working.

terminology is now opening but minutes laters between hitting the KB shortcut and it actually opens from before when it was nanosecond delay

and OK
Code:
userx%slackwhere ⚡ ~ ⚡> pcmanfm
userx%slackwhere ⚡ ~ ⚡>
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 ?

Code:
good morning userx
userx%slackwhere ⚡ ~ ⚡> ps -aux | grep pcmanfm
userx     2095  0.0  0.0   9656  1876 pts/1    S+   09:11   0:00 grep pcmanfm
userx%slackwhere ⚡ ~ ⚡>
it does not even show it to be running
Code:
userx%slackwhere ⚡ ~ ⚡> pgrep pcmanfm
userx%slackwhere ⚡ ~ ⚡> pgrep firefox
1707
userx%slackwhere ⚡ ~ ⚡>
I deleted its conf dir ./config/pcmanfm and tried it again and still nothing.

Last edited by BW-userx; 06-19-2017 at 09:15 AM.
 
Old 06-19-2017, 12:36 PM   #4
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,632

Rep: Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571
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
Code:
cat /var/log/packages/pcmanfm*
 
Old 06-19-2017, 12:48 PM   #5
BW-userx
Senior Member
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Void Linux / Slackware 14.2
Posts: 4,690

Original Poster
Rep: Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865
Quote:
Originally Posted by Didier Spaier View Post
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.
 
Old 06-19-2017, 01:03 PM   #6
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,632

Rep: Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571
Quote:
Originally Posted by BW-userx View Post
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.
 
Old 06-19-2017, 01:05 PM   #7
BW-userx
Senior Member
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Void Linux / Slackware 14.2
Posts: 4,690

Original Poster
Rep: Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865
Quote:
Originally Posted by Didier Spaier View Post
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.

Thanks
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] ssh, cron, etc not starting at boot anymore Sefyir Linux - Newbie 15 03-14-2016 11:35 AM
[SOLVED] udevd not starting anymore m-h Linux - General 5 07-09-2010 02:10 AM
Debian Testing: why the scripts into /etc/rc2.d are not starting anymore ? frenchn00b Debian 1 06-14-2010 11:21 PM
Proftpd, ssh, webmin not starting at startup anymore black669 Linux - Software 16 01-06-2010 02:31 AM
Debian isn't starting anymore need help! Hi-Tak Debian 4 04-22-2004 03:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:15 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration