LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   files being rendered non-executable after GSB crashes. (https://www.linuxquestions.org/questions/slackware-14/files-being-rendered-non-executable-after-gsb-crashes-674008/)

adityavpratap 10-03-2008 01:07 PM

files being rendered non-executable after GSB crashes.
 
Hi,
I have installed GSB Gnome 2.22.1 on my Slackware 12.1 installation. I have found it to be rather unstable when compared to Dropline Gnome I was using before I upgraded to 12.1 from 12.
GSB becomes unresponsive rather frequently. Sometimes the only way out is using the Magic Key sequence Alt+SysRq+r+e+i+s+u+b. Upon rebooting I find that many of the critical files have been rendered un-executable. For example /etc/rc.d/rc.local, /usr/sbin/crond, etc., become un-excecultable. I have to manually chmod them to make them executable again.
This is a new phenomenon that started after the installation of GSB.
Has anyone else observed this?
Is there a solution to this problem?

jong357 10-04-2008 10:57 PM

Been using gnome-system-tools for anything?

adityavpratap 10-04-2008 10:58 PM

No, I don't think so!

jong357 10-04-2008 11:15 PM

Oh. They are notoriously dangerous on Slackware is the reason I ask. Will do exactly as you mentioned.

Changing the time thru the clock is using the gnome-system-tools package so you might have used it without even knowing. time-admin will royally screw perms system wide, in the /etc/rc.d directory and abroad.

They have no business being on Slack, maintained or otherwise IMO (which they are in a severe state of disrepair ATM).

I believe GSB dropped them on 2.22.x


All times are GMT -5. The time now is 12:29 AM.