Permission denied trying to change window manager

Please post any bugs you have found
Post Reply
Message
Author
musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

Permission denied trying to change window manager

#1 Post by musher0 »

Hello all.

Has any of you ever encountered this bug on a Puppy:

I get a "permission denied" message on trying to change
/etc/windowmanager with the usual < xwin jwm > or < xwin wmx >
command. The window manager I'm trying to change from is pekwm.

In parallel to this, I have a similar "permission denied" problem when I
try to edit scripts in /usr/local/bin with geany.

In this case, a .goutputstream-XYZBLABLA file gets created when I try to
save the edit. There are various threads about this on Unix Exchange and
Ubuntu forums, but nothing quite on-the-button.

The ubuntu thread refers to this bug as an Ubuntu bug tied to gedit and
scheduled to be fixed, which seems to be of no help for a Debian Puppy
user using geany.

Tentative Description
-- this seems to happen after say an hour or two into my session -- as if
heat of the CPU had something to do with it. However, I set up CPU-Freq
and lm-sensors and I did manage to bring the temperature down to a
reasonable +/- 38 C - 52 C. And the bug is still present.

At the beginning of a session, I can edit, but the /etc/windowmanager file
seems to be locked permanently.

-- .goutputstream files from geany are created every time I click on the
close button in the message window with the mouse.

Other notes
-- computer is an hp compaq 6517b laptop.

-- as mentioned in the sub-title, Pup is a Puduan-6.

-- When I look at the properties of these files I see "root, root" as user
(1st line of the properties panel). Is this ok? I thought I saw only "root"
as user on that line in other Pups.

I tried to be as precise as possible in the above, but if you need more
info, please ask.

First time this has ever happened to me. No other Pup has ever done this.

Thanks in advance for any help or pointer.
Last edited by musher0 on Thu 22 Dec 2016, 19:14, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#2 Post by musher0 »

Add'l notes:
-- only dirs /usr/local/bin and /etc seem to be "protected". I can edit
a script normally in ~/my-applications/bin

-- happens at the beginning of a session too, if I try to change wm at that
time

-- I must add that I have created a script to choose various colors of wmx
which resides in /usr/local/bin.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#3 Post by musher0 »

Hello all.

Still no reply. Oh well.

PuppyLinux always running as root, no Puppyist is too keen about file
permissions, I suppose.

I guess I'll have to educate myself about them as I rebuild that pupsave
in my spare time.

It's a good thing that you can create a 2nd pupsave file easily in Puppy.
And that you can set up 2 or 3 different Puppies on the same computer:
they can act as backup for one another.

I must have clicked in a wrong box in a Properties panel +/- a week ago,
but I just can't backtrack what I did...

Thanks anyway. If you have any leads or pointers, please chime in. Even
in the New Year! I'm not marking this thread as solved anytime soon.

BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

Post Reply