Bug 5688

apr 30 01:27:02.692 [Warning] /var/lib/tor is not owned by this user (kristoffer, 500) but by toruser (483). Perhaps you are running Tor as the wrong user?
apr 30 01:27:02.692 [Warning] Failed to parse/validate config: Couldn't access/create private data directory "/var/lib/tor"

4. Start Vidalia.
how ?

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0
Severity: critical => normal

Click on Activities-menu followed by Programs & then type vidalia in the searchfield & then you click Vidalia to open it.

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Problem solved for me.

I made an Mageia 3 Errata entry that explains how.
I haven't learned how to make a patch so I wish someone could do this for me.

https://wiki.mageia.org/en/Mageia_3_Errata

your entry in the errata is useless..

anyway reassign then

Keywords: NEEDINFO => (none)
Status: UNCONFIRMED => NEW
Assignee: bugsquad => cazzaniga.sandro
Summary: Can't start Tor-service => Can't start vidalia
Ever confirmed: 0 => 1
Source RPM: tor => vidalia

And HOW did you solve it, please??

(In reply to comment #6)
> And HOW did you solve it, please??

I changed the rights for /var/lib/tor to be executed.

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Issue is solved for me, but no fix has been commited as an update.

Sorry, I was waiting for my new computer which arrived today. I'll do it
tonight or tomorrow without fail.

(In reply to comment #10)
> Sorry, I was waiting for my new computer which arrived today. I'll do it
> tonight or tomorrow without fail.

Give me a pastebin-link of which medias you've set by typing urpmq --list-media.

Then Login as root in Terminal & do chmod a+x to /usr/bin/tor & then start Vidalia again.

(In reply to comment #11)
> (In reply to comment #10)
> > Sorry, I was waiting for my new computer which arrived today. I'll do it
> > tonight or tomorrow without fail.
> 
> Give me a pastebin-link of which medias you've set by typing urpmq
> --list-media.
> 
> Then Login as root in Terminal & do chmod a+x to /usr/bin/tor & then start
> Vidalia again.

Again....... chmod a+x /usr/bin/tor

The fix is ready on my computer, but the build system is down for today. Push it ASAP!

Are you sure this bug concern vidalia.spec? Or tor.spec?

I'm no expert, but my vote is for the latter. That's what I've had issues with. Tor is need for Vidalia to start as well.

(In reply to comment #15)
> Tor is need for Vidalia to start as well.

That's ok, as vidalia is just a Qt frontend to tor. But /usr/bin/tor is executable when it's installed, isn't it?

With the new update it should be yeah.

Can you try with tor-0.2.2.38-1.mga3? I uploaded it today in Core/release, Cauldron. Should be available soon (~1h).

Thanks.

Re-assigned to QA.

Assignee: cazzaniga.sandro => bugsquad

Sandro, is this an update for cauldron or mga1/2?

If cauldron then it's not something QA needs to validate and you can just close the bug as resolved, if it has been.

It's for cauldron and also in mageia 2.

There doesn't appear to be any update built for mga2 Sandro.

Speaking on IRC, it seems this was fixed in a previous update for mga2.

Closing the bug as there is nothing here to QA \o/

Status: NEW => RESOLVED
Resolution: (none) => FIXED