Re: [Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.

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.

[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.

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

[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.

** 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

[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.

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

[Bug 983827] Re: kazam crashed with ValueError in function(): %f not in range %f to %f

Looks like on app.py line 578 audio2_vol is -infinity, I've fixed it locally by prepending with the line: if audio2_vol 0: audio2_vol = 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983827 Title:

[Bug 983827] Re: kazam crashed with ValueError in function(): %f not in range %f to %f

After branching from lp:kazam, the code is different to what I get from running apt-get source kazam. I don't know enough about Ubuntu packaging to figure out where the repo is for the code being installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 805725] Re: ctrl alt l does not work in Ubuntu 11.04

This is affecting me in 12.10. UK keyboard, similarly to comments above ctrl+alt+l or ctrl+alt+delete don't work but ctrl+alt+f1,f2 etc do work, along with alt-f4 and similar shortcuts. If I assign the shortcut to ctrl+alt+l manually it works again, but appears to break after a reboot. -- You

[Bug 983827] Re: kazam crashed with ValueError in function(): %f not in range %f to %f

I'm still experiencing this bug, and Chris' solution of making the input volume non-zero fixes this for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983827 Title: kazam crashed with ValueError

[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.

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

[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.

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

[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.

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,

[Bug 1002515] Re: padsp does not work, ld.so can't find libpulsedsp.so

Running Americas Army 2.5 through 25 Assist, I get the following error: $ padsp ./armyops-bin ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded: ignored. open /dev/[sound/]dsp: No such file or directory (the last line is from the

[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.

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

[Bug 46520] Re: d-i does not provide a way to select which drive to install grub to

Experienced this issue running the server installation for 10.04 LTS from a USB stick to a RAID - Ubuntu was installed to the RAID but grub was installed to the USB stick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report.

[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.

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