Regedit issues, not owned by root

Mokuren · Post by **Mokuren** » Wed Aug 05, 2009 1:25 pm

Hello.

I have been pretty satisfied with wine since I have become aware of its existance and am having a pretty good time with it. There are, however, a couple issues I can't wrap my head around.

First of all, I cannot run regedit as root, it says:

Code: Select all

wine: /home/mokuren/.wine is not owned by you

I don't know how the root is supposed to "not own" something. This isn't a real problem since regedit runs fine not as root, but well...

Second issue: I cannot rename keys in regedit.

I need to create a Direct3D and a DirectInput key with a couple strings in order to fix some issues (one minor, one game-breaking) with a couple games. However, I am only able to create the keys, any attempt at renaming gives no benefit.

It doesn't matter how many times and how hard I press F2 or how many times I right-click and choose "rename", it absolutely refuses to allow me to change a registry key's name.

What went wrong?

austin987 · Post by **austin987** » Wed Aug 05, 2009 1:37 pm

On Wed, Aug 5, 2009 at 1:25 PM, Mokuren<[email protected]> wrote:

Hello.

I have been pretty satisfied with wine since I have become aware of its existance and am having a pretty good time with it. There are, however, a couple issues I can't wrap my head around.

First of all, I cannot run regedit as root, it says:

Why do you need to run regedit as root?

Code:
wine: /home/mokuren/.wine is not owned by you

I don't know how the root is supposed to "not own" something. This isn't a real problem since regedit runs fine not as root, but well...

Exactly. Root doesn't own it, mokuren does.

Second issue: I cannot rename keys in regedit.

I need to create a Direct3D and a DirectInput key with a couple strings in order to fix some issues (one minor, one game-breaking) with a couple games. However, I am only able to create the keys, any attempt at renaming gives no benefit.

It doesn't matter how many times and how hard I press F2 or how many times I right-click and choose "rename", it absolutely refuses to allow me to change a registry key's name.

What went wrong?

When you say rename, do you mean recase? That fails on windows as
well. If renaming fails though, something is wrong.

--
-Austin

Mokuren · Post by **Mokuren** » Wed Aug 05, 2009 2:21 pm

austin987 wrote:Why do you need to run regedit as root?

No reason, it just felt weird that I couldn't

austin987 wrote:When you say rename, do you mean recase? That fails on windows as
well. If renaming fails though, something is wrong.

I'm talking about renaming, I can create new keys that go by the default name (New Key #1 and so on) but any attempt at renaming does... Absolutely nothing.

I mean: it's not that I rename it and the name doesn't stick, I don't even get to edit the name in the first place, the command does absolutely nothing

austin987 · Post by **austin987** » Wed Aug 05, 2009 2:29 pm

On Wed, Aug 5, 2009 at 2:21 PM, Mokuren<[email protected]> wrote:

austin987 wrote:
Why do you need to run regedit as root?
No reason, it just felt weird that I couldn't

Playing around with root is dangerous.

austin987 wrote:
When you say rename, do you mean recase? That fails on windows as
well. If renaming fails though, something is wrong.
I'm talking about renaming, I can create new keys that go by the default name (New Key #1 and so on) but any attempt at renaming does... Absolutely nothing.

I mean: it's not that I rename it and the name doesn't stick, I don't even get to edit the name in the first place, the command does absolutely nothing

Try in a clean wineprefix. What wine version?

--
-Austin

Mokuren · Post by **Mokuren** » Wed Aug 05, 2009 2:38 pm

austin987 wrote:Try in a clean wineprefix. What wine version?

Wine version is 1.1.26

As a matter of fact, I have never used wineprefix, since regedit is builtin.

austin987 · Post by **austin987** » Wed Aug 05, 2009 2:47 pm

On Wed, Aug 5, 2009 at 2:38 PM, Mokuren<[email protected]> wrote:

austin987 wrote:
Try in a clean wineprefix. What wine version?
Wine version is 1.1.26

Ok.

As a matter of fact, I have never used wineprefix, since regedit is builtin.

Right, but if the registry is corrupted for some reason, could give
weird errors. Especially since you tried sudo'ing and such.

Try:
$ mv ~/.wine ~/.wine.bak
$ wine regedit

and see if it works.

--
-Austin

Mokuren · Post by **Mokuren** » Wed Aug 05, 2009 3:13 pm

austin987 wrote:Right, but if the registry is corrupted for some reason, could give
weird errors. Especially since you tried sudo'ing and such.

Try:
$ mv ~/.wine ~/.wine.bak
$ wine regedit

and see if it works.

Yes, yes it works now.

Could be because I installed/uninstalled some software in weird ways and such.

Is there a way to fix this without reinstalling wine?

austin987 · Post by **austin987** » Wed Aug 05, 2009 3:23 pm

On Wed, Aug 5, 2009 at 3:13 PM, Mokuren<[email protected]> wrote:

austin987 wrote:
Right, but if the registry is corrupted for some reason, could give
weird errors. Especially since you tried sudo'ing and such.

Try:
$ mv ~/.wine ~/.wine.bak
$ wine regedit

and see if it works.
Yes, yes it works now.

Could be because I installed/uninstalled some software in weird ways and such.

Probably your root escapades.

Is there a way to fix this without reinstalling wine?

Try:
$ sudo chown -R mokuren ~/.wine

--
-Austin

Mokuren · Post by **Mokuren** » Wed Aug 05, 2009 4:59 pm

austin987 wrote:Probably your root escapades.

I was thinking winetricks actually, it always crashes after installing DirectX (thought they do work)

austin987 · Post by **austin987** » Wed Aug 05, 2009 5:18 pm

On Wed, Aug 5, 2009 at 4:59 PM, Mokuren<[email protected]> wrote:

austin987 wrote:
Probably your root escapades.
I was thinking winetricks actually, it always crashes after installing DirectX (thought they do work)

That wouldn't foobar the registry that badly.

--
-Austin

DaVince · Post by **DaVince** » Thu Aug 06, 2009 8:03 am

I'll just emphasize it once more: NEVER run Wine as root. It messes things up, for example the rights over one or several of Wine's folders and possible corruption of the registry.