Vidalia does not start. AppArmor prevents

[John Doe]

Hello.

I installed Vidalia from the repos and it's not able to start up. So I tried to run it in a terminal to see what's wrong and got this:

<quote>
vidalia

(process:5629): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)

(<unknown>:5629): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)

(<unknown>:5629): IBUS-WARNING **: Unable to load /var/lib/dbus/machine-id: Datei »/var/lib/dbus/machine-id« konnte nicht geöffnet werden: Keine Berechtigung
</quote>

This Bug may be related to this: http://ubuntuforums.org/showthread.php?t=2206493

kind regards

JD

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: vidalia 0.2.21-1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Mar 9 20:48:24 2014
InstallationDate: Installed on 2014-03-08 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: vidalia
UpgradeStatus: No upgrade log present (probably fresh install)

[Jamie Strandboge (jdstrand)]

Can attach the output of 'grep DEN /var/log/syslog'?

[Kurt Hallavej (kridhvidneger)]

~$ grep DEN /var/log/syslog
Mar 22 15:51:33 rasmus-HP-Pavilion-dv6-Notebook-PC dbus[2805]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="Hello" mask="send" name="org.freedesktop.DBus" pid=8217 profile="/usr/bin/vidalia" peer_profile="unconfined"
Mar 22 15:51:33 rasmus-HP-Pavilion-dv6-Notebook-PC kernel: [ 3944.253516] type=1400 audit(1395499893.618:94): apparmor="DENIED" operation="open" profile="/usr/bin/vidalia" name="/etc/xdg/Trolltech.conf" pid=8217 comm="vidalia" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Mar 22 15:51:33 rasmus-HP-Pavilion-dv6-Notebook-PC kernel: [ 3944.261187] type=1400 audit(1395499893.626:95): apparmor="DENIED" operation="open" profile="/usr/bin/vidalia" name="/proc/8217/cmdline" pid=8217 comm="vidalia" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Mar 22 15:51:33 rasmus-HP-Pavilion-dv6-Notebook-PC kernel: [ 3944.295584] type=1400 audit(1395499893.658:96): apparmor="DENIED" operation="open" profile="/usr/bin/vidalia" name="/usr/share/themes/Ambiance/gtk-2.0/gtkrc" pid=8217 comm="vidalia" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Mar 22 15:51:33 rasmus-HP-Pavilion-dv6-Notebook-PC kernel: [ 3944.295649] type=1400 audit(1395499893.658:97): apparmor="DENIED" operation="open" profile="/usr/bin/vidalia" name="/usr/share/themes/Default/gtk-2.0-key/gtkrc" pid=8217 comm="vidalia" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Mar 22 15:51:33 rasmus-HP-Pavilion-dv6-Notebook-PC kernel: [ 3944.301620] type=1400 audit(1395499893.666:98): apparmor="DENIED" operation="open" profile="/usr/bin/vidalia" name="/usr/share/glib-2.0/schemas/gschemas.compiled" pid=8217 comm="vidalia" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

[Omadas (bsperger)]

It looks as though the patch for bug #680192 has been denied and is as of now:

https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192
(This is the official bug report from the original bug reporter's link)

https://code.launchpad.net/~jackweirdy/vidalia/680192/+merge/178623
(This link can be used to monitor the patch submission)

Applying these fixes from the patch, nothing was wrong in the terminal and Vidalia was able to run as a regular user without having to use gksu or sudo. I was ably to start Vidalia, but still received warnings that got flagged in the message box and was unable to use Vidalia in any meaningful way. These are the messages I received:

[Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
[Warning] /var/run/tor is not owned by this user (brandon, 1000) but by debian-tor (118). Perhaps you are running Tor as the wrong user?
[Warning] Before Tor can [not] create a control socket in "/var/run/tor/control.authcookie", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)
[Warning] Failed to parse/validate config: Failed to bind one of the listener ports.

For now, I recommend TOR/Ubuntu Users run the Tor Browser Bundle.
(https://www.torproject.org/projects/torbrowser.html.en)

As an alternative you can follow my instructions here:
1A) Installing the packages 'tor, tor-geoipdb, and torsocks' in Ubuntu Software Center or Synaptic.
1B) In the command prompt type 'aptitude install tor-geoipdb torsocks tor' with 'sudo'.
2) Navigating by Menu>System Settings>Network.
3) Click on the network Proxy.
        Where it says 'Method' select 'Manual'.
        Where it says Socks Host type '127.0.0.1' into the first field and '9050' into the second field.
4) Click 'Apply System Wide'.
5) Enter your password in the confirmation dialog.
-Tor is now set to be used by all users for all internet activity-
You can restore normal use by following step 2, except in step 3 where it says 'Method' select 'Automatic'. Your manual settings will be saved, making it easy to visually start The Onion Router without further configuration.

[Jamie Strandboge (jdstrand)]

Thanks for the feedback. This is not a bug in apparmor but rather in Vidalia's apparmor profile, which is shipped in the vidalia package. Probably the easiest thing to do would be to add the comments in #4 to bug #680192 and to mark this bug as a duplicate of bug #680192.

[Omadas (bsperger)]

You should now be using TOR Browser and not vidalia/tor. This bug report is invalid and no longer maintained. Maintainer please close Bug Report.