onioncircuits, the replacement for vidalia is now in ubuntu (yakkety)
http://packages.ubuntu.com/yakkety/onioncircuits
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable
Vidalia has been replaced in tails, and now in debian by OnionCircuits
https://packages.debian.org/sid/utils/onioncircuits
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was
This isn't much of a bug in wily since vidalia is gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
correct name
** Changed in: vidalia (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
hey arsalan, i think you are not using root to open these commsnds
In command prompt type:su
It will ask password for root. After that you can edit those changes.
P.S. su means super user.
post of Wetware Random Number Generator (tnrng-purge-deactivatedaccount)
worked for my case that
I'm new and using ubuntu 14,
I can't find out what should I do and what does it mean:
sudo ln -s /etc/apparmor.d/usr.bin.vidalia /etc/apparmor.d/disable/
sudo apparmor_parser -R /etc/apparmor.d/usr.bin.vidalia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Same here I faced the problem in Ubuntu 14.10 and
https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/comments/8;
fixed the issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Same here I faced the problem in Ubuntu 14.10 and
https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/comments/8;
fixed the issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
After reboot, vidalia can't connect with D-BUS again. To solve my new
/etc/apparmor.d/usr.bin.vidalia looks like is:
#include tunables/global
/usr/bin/vidalia {
#include abstractions/lightdm
#include abstractions/kde
#include abstractions/nameservice
owner @{HOME}/.vidalia/ rw,
owner
Confirmed, #31
(https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/comments/31)
works for me, but previous #8
(https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/comments/8)
adding the line /usr/bin/tor Ux, does not.
---
My system:
lsb_release -a
No LSB modules are
Confirmed on Ubuntu 14.04.1 LTS.
I edited my /etc/apparmor.d/usr.bin.vidalia to look like this:
#include tunables/global
/usr/bin/vidalia {
#include abstractions/kde
#include abstractions/nameservice
#include abstractions/dbus-session
#include abstractions/dconf
#include
Running : Ubuntu 14:10 beta
Used Sam Edwards Workaround to get Vidalia running.:
https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/comments/8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed on Kubuntu 14.04.1 LTS
Vidalia is unusable to me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
correct
Same here also. Tried all the above fixes, and vidalia does not run.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
UPDATE, as a test, I disabled apparmor completely, and vidalia runs.
Using Gnome-ubuntu 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your
Same here running Xubuntu 14.04.
The bugfix does not solve the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
Same here! I edited my /etc/apparmor.d/usr.bin.vidalia to look like
this:
#include tunables/global
/usr/bin/vidalia {
#include abstractions/kde
#include abstractions/nameservice
/usr/lib/** mr,
/usr/bin/tor Ux,
owner @{HOME}/.vidalia/ rw,
owner @{HOME}/.vidalia/** rwmk,
Hello all, I came here redirected by this bug report:
https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/1290107/comments/5
lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
aptitude show vidalia
Package: vidalia
State: installed
I also encounter
https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/comments/22
in Ubuntu 13.10 and based on the previous comments in this thread was
able to fix it by adding:
/usr/bin/tor Ux,
to /etc/apparmor.d/usr.bin.vidalia and then running sudo apparmor_parser
-r
I confirm this bug on saucy.
Adding the /usr/sbin/tor Ux, line to AppArmor configuration does NOT fix the
issue to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was
In the kernel log I found the following lines:
Feb 11 13:14:34 Base kernel: [ 515.502544] type=1400 audit(1392120874.882:50):
apparmor=DENIED operation=open parent=2110 profile=/usr/bin/vidalia
name=/usr/share/kde4/config/kdebugrc pid=5065 comm=vidalia
requested_mask=r denied_mask=r
** Changed in: vidalia (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
Jack Wearden, in which line should I paste the line /usr/sbin/tor
Ux,? After /usr/share/icons/*/index.theme k,?
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia
It doesn't matter exactly which line, you can place it anywhere as long as
it has the trailing comma :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor.
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
correct name and location of your Tor
** Bug watch added: Debian Bug tracker #718901
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718901
** Also affects: vidalia (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718901
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: vidalia (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
correct
Thanks for submitting this bug to Debian!
So based on that, my understanding is:
This is a bit of a wishlist bug in Debian, since AppArmor isn't
installed in Debian by default, and this only affects one specific mode
of operation in Vidalia. Is this accurate?
But in Ubuntu, AppArmor is
I've finally got around to attempting to fix this bug properly - I'm not
the package maintainer though so it has to be reviewed before it is
accepted. If you're interested in following the progress of this, see
here https://code.launchpad.net/~jackweirdy/vidalia/680192/+merge/178623
--
You
** Branch linked: lp:~jackweirdy/vidalia/680192
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
correct name and
Fixed as well. Thanks Jack Wearden.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
correct name and location of
** Attachment removed: Updated tor permissions
https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/+attachment/3449072/+files/apparmor-profile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adam;
Open up a terminal and run the command
gksudo gedit /etc/apparmor.d/usr.bin.vidalia
this should open up a text editor with root permissions so you can
overwrite the file with the new one. Then paste in the following line:
/usr/sbin/tor Ux,
--
You received this bug notification because
I have this problem as well, and am wondering how to apply patch to file
etc/apparmor.d/usr.bin.vidalia. New ubuntu user. Tried to insert
command line myself, couldn't save it due to gedit being unable to
backup the file. I understand that this is very nooby, any advice?
--
You received this
Same bug here, solved as suggested by Jack Wearden. Then I just issued the
following command to replace apparmor definitions:
sudo apparmor_parser -r /etc/apparmor.d/usr.bin.vidalia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: raring
** Tags added: precise quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
correct name
Patch attached: Patches debian/apparmor-profile to allow access to tor
binary
** Attachment added: Updated tor permissions
https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/+attachment/3449072/+files/apparmor-profile
--
You received this bug notification because you are a member
Oops, uploaded the file, not the patch!
** Attachment added: apparmor-profile-patched
https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/+attachment/3449073/+files/apparmor-profile-patched
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The attachment apparmor-profile-patched of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag
Hello all,
This appears to be a problem with AppArmor not allowing Vidalia to
launch the Tor binary. The package maintainer should probably fix the
AppArmor profile.
Until then, a suitable workaround is to disable the usr.bin.vidalia
AppArmor profile:
sudo ln -s /etc/apparmor.d/usr.bin.vidalia
I can confirm that apparmor is the cause.
A safer alternative to Sam Edwards' suggestion is to allow Vidalia
access to the tor binary, by adding the following line to
/etc/apparmor.d/usr.bin.vidalia:
/usr/sbin/tor Ux,
also ensure that the tor service isn't running (by running service tor
stop,
This is the output of `vidalia -loglevel debug`:
(unknown:7310): IBUS-WARNING **: Unable to load /var/lib/dbus/machine-
id: Failed to open file '/var/lib/dbus/machine-id': Permission denied
(unknown:7310): GVFS-RemoteVolumeMonitor-WARNING **: cannot open directory
I've the same experience as Jack Wearden on 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure the
correct name and
On 12.10 (freshly installed) , I've the same experience as Jack Wearden
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
Vidalia was unable to start Tor. Check your settings to ensure
I'm experiencing this bug even when I confirm the tor service is stopped
(either through `service tor status` or `service tor stop`), so it looks
like this may not be the issue.
What's more, running `/usr/sbin/tor` from the command line *does* start
tor.
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vidalia (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680192
Title:
This is because tor is starting as a system service.
$ ls -l /etc/rc2.d/S20tor
lrwxrwxrwx 1 root root 13 May 23 2009 /etc/rc2.d/S20tor - ../init.d/tor
When you run Vidalia, tor needs to run tor under your user account.
Vidalia tries to start tor but can't, because it's already running. So
you
** Description changed:
Binary package hint: vidalia
I installed Vidalia using Ubuntu Software center in Ubuntu Desktop 10.10
64 bit edition.
When I try to start vidalia, I get the following error:
Vidalia was unable to start Tor. Check your settings to ensure the
correct
Does the vidalia package in Ubuntu need to be update?
http://www.torproject.org/docs/debian-vidalia.html.en
--
Vidalia was unable to start Tor. Check your settings to ensure the correct name
and location of your Tor executable is specified.
https://bugs.launchpad.net/bugs/680192
You received
49 matches
Mail list logo
