On Thu, 2014-09-25 at 10:28 +0800, Paul Wise wrote:
> I'm having this issue too.
I ran it with sh -x and it seems to be something to do with directory
layouts. It was failing to find Tor/tor, which was causing the
architecture issue. After that it couldn't find where firefox was.
Anyway, I delet
> and give more output, please? I am simply not quite sure about the empty
> variable assertion. As a matter of fact, it seems to be empty on my
> machine too :)
Actually i tried to research this a bit more.
So, when i echo $TORARCHITECTURE and $SYSARCHITECTURE, i get
64
64
However if i unset TO
On Thu, 2014-09-25 at 09:06 +0200, Holger Levsen wrote:
> always or sometimes?
Always, the analysis already in the bug seems correct to me.
> For me to torbrowser-launches fails to launch torbrowser approx. once in ten
> attempts to run it... then I retry and it works...
Hmm.
--
bye,
pabs
h
Hi,
I'm also running TBL on Debian Jessie & Wheezy, with AppArmor enabled,
using different window managers.
I can't, however, reproduce that bug. I have never seen it actually.
The start-tor-browser executable is part of the downloaded Tor Browser
Bundle itself.
Would you be able to run
./star
Hi Paul,
On Donnerstag, 25. September 2014, Paul Wise wrote:
> I'm having this issue too.
always or sometimes?
For me to torbrowser-launches fails to launch torbrowser approx. once in ten
attempts to run it... then I retry and it works...
cheers,
Holger
signature.asc
Description: Th
Daniel González Gasull wrote (25 Sep 2014 05:35:02 GMT) :
> It didn't work. First of all, the version built from GitHub was a
> lower version than the one I had from the Debian repositories.
I was suggesting to update the AppArmor profiles only, not
everything else. But anyway, Paul can reproduce
intrigeri,
It didn't work. First of all, the version built from GitHub was a
lower version than the one I had from the Debian repositories. Bad
numbering, I guess:
dpkg: warning: downgrading torbrowser-launcher from 0.1.4-2 to 0.1.4-1
Then, torbrowser-launcher outputs the same error with exit
Package: torbrowser-launcher
Version: 0.1.4-2
Followup-For: Bug #758935
I'm having this issue too.
I don't have apparmor installed and I'm on Debian amd64.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experiment
Hi,
I don't think I have AppArmor enabled. I have not enabled it manually, and
I get the following output when running various status tools:
albin@hecate ~ % sudo
aa-status
AppArmor available in kernel.
AppArmor not enabled. (Kernel not booted with "security=apparmor"?)
albin@hecate ~ % systemctl
Hi Daniel and Albin,
do you have AppArmor enabled? If so, may you please retry with the
updated profiles I've just submitted upstream?
--> https://github.com/micahflee/torbrowser-launcher/pull/133
Thanks!
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.o
I have the same issue persistently, even after deleting my
~/.config/torbrowser.
The output when running torbrowser-launcher on the console is:
albin@hecate ~ % torbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under GPLv3
version 0.1.4
https://github.com/micahflee/torbrowser-launc
Hi Holger.
On Sun, Aug 24, 2014 at 7:10 PM, Holger Levsen wrote:
> what arch are you running this on? what's the output of "file $(which tor)"?
$ uname -m
x86_64
$ file $(which tor)
/usr/bin/tor: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for G
Hi Daniel,
On Sonntag, 24. August 2014, Daniel González Gasull wrote:
> I didn't see anything in the output from the terminal that could help
> investigate the issue. It just says that the I'm running the latest
> version. I thought the exit code 127 would be the most informative
> part.
>
> He
Hi Holger.
I didn't see anything in the output from the terminal that could help
investigate the issue. It just says that the I'm running the latest
version. I thought the exit code 127 would be the most informative
part.
Here is the output from the command line:
$ torbrowser-launcher
Tor Brow
control: severity -1 important
control: tags -1 + unreproducible moreinfo
Hi Daniel,
On Freitag, 22. August 2014, Daniel Gonzalez Gasull wrote:
> torbrowser-launcher fails to start.
thanks for your bug report, but "sadly" I cannot reproduce it here, thus
downgrading and tagging accordingly.
>
Package: torbrowser-launcher
Version: 0.1.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
torbrowser-launcher fails to start.
* What led up to the situation?
Starging torbrowser-launcher.
* What was the outcome of this action?
Window that said "Tor Brows
16 matches
Mail list logo
