Your message dated Tue, 19 Aug 2014 14:23:23 -0400
with message-id <[email protected]>
and subject line Re: [Pkg-anonymity-tools] Bug#757918: tbb 4.0 alpha fails
has caused the Debian Bug report #757918,
regarding tbb 4.0 alpha fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
757918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757918
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: torbrowser-launcher

Hi,

so the launcher (version 0.1.2 still) today tried to upgrade to tbb 4.0-alpha, 
which IMO it shouldnt do, but anyway, it also failed:

Starting launcher dialog
LATEST VERSION 4.0-alpha-1
Checked for update within 24 hours, skipping
TBB is out of date, attempting to upgrade to 4.0-alpha-1
Running task: download_sha256
Downloading https://www.torproject.org/dist/torbrowser/4.0-
alpha-1/sha256sums.txt
Updating over Tor
Finished receiving body: Response body fully received
Running task: download_sha256_sig
Downloading https://www.torproject.org/dist/torbrowser/4.0-
alpha-1/sha256sums.txt-mikeperry.asc
Updating over Tor
Finished receiving body: Response body fully received
Running task: download_tarball
Downloading https://www.torproject.org/dist/torbrowser/4.0-alpha-1/tor-
browser-linux64-4.0-alpha-1_en-US.tar.xz
Updating over Tor
Finished receiving body: Response body fully received
Running task: verify
Verifying signature
gpg: Signature made Thu Aug  7 22:30:53 2014 CEST using RSA key ID 0E3A92E4
gpg: Good signature from "Mike Perry (Regular use key) 
<[email protected]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: C963 C21D 6356 4E2B 10BB  335B 2984 6B3C 6836 86CC
     Subkey fingerprint: D734 B622 C7B5 D164 D665  0CB8 717F 1F13 0E3A 92E4
Running task: extract
Extracting tor-browser-linux64-4.0-alpha-1_en-US.tar.xz
Running task: run
Running /home/foo/.torbrowser/tbb/x86_64/tor-browser_en-US/start-tor-browser
Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py", line 911, 
in dispatcher
    return func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py", line 
1462, in _finishResponse_WAITING
    self._giveUp(Failure(reason))
  File "/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py", line 
1511, in _giveUp
    self._disconnectParser(reason)
  File "/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py", line 
1499, in _disconnectParser
    parser.connectionLost(reason)
--- <exception caught here> ---
  File "/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py", line 532, 
in connectionLost
    self.response._bodyDataFinished()
  File "/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py", line 911, 
in dispatcher
    return func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py", line 
1154, in _bodyDataFinished_CONNECTED
    self._bodyProtocol.connectionLost(reason)
  File "/usr/bin/torbrowser-launcher", line 833, in connectionLost
    self.all_done(reason)
  File "/usr/bin/torbrowser-launcher", line 844, in response_finished
    self.run_task()
  File "/usr/bin/torbrowser-launcher", line 787, in run_task
    self.verify()
  File "/usr/bin/torbrowser-launcher", line 996, in verify
    self.run_task()
  File "/usr/bin/torbrowser-launcher", line 791, in run_task
    self.extract()
  File "/usr/bin/torbrowser-launcher", line 1040, in extract
    self.run_task()
  File "/usr/bin/torbrowser-launcher", line 795, in run_task
    self.run()
  File "/usr/bin/torbrowser-launcher", line 1043, in run
    subprocess.Popen([self.common.paths['tbb']['start']])
  File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child
    raise child_exception
exceptions.OSError: [Errno 13] Permission denied

I assume this is due to me using apparmor, from the journal

Aug 12 13:32:31 matrix kernel: audit: type=1400 audit(1407843151.609:1377): 
apparmor="DENIED" operation="open" profile="/usr/bin/torbrowser-launcher" 
name="/usr/bin/python2.7" pid=20218 comm="file" requested_mask="r" 
denied_mask="r" fsuid=1002 ouid=0

And here I'm lost... at least for the moment :)


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message ---
Hi,

On Samstag, 16. August 2014, intrigeri wrote:
> > so the launcher (version 0.1.2 still) today tried to upgrade to tbb
> > 4.0-alpha,
> > which IMO it shouldnt do, but anyway, it also failed:
> 0.1.2-1 worked for me 2 days ago on sid. Not tried 0.1.3-1 yet.

I'm closing this bug now, mostly to keep the BTS clean and assuming that 4.0 
will work once its released. Or we can file a new bug then :)
 
> > exceptions.OSError: [Errno 13] Permission denied
> > I assume this is due to me using apparmor,
> Quite possibly, as the AppArmor profiles shipped in 0.1.2-1 are only
> partly updated wrt. the XDG-compliant dirs, were clearly never fully
> tested on current sid, and are totally broken:

0.1.3-1 works for me using tbb 3.6.4 + apparmor.
 
>   https://github.com/micahflee/torbrowser-launcher/issues/124
>   https://github.com/micahflee/torbrowser-launcher/pull/125

cool!
 
> (They are even more broken once combined with the fact that
> torbrowser-launcher downloads 4.0-alpha, that changes the location of
> many directories. Addressed too in my pull request.)

nods, cool!
 
> This specific one is innocuous, and I've proposed to hide it with
> commit bfabd82 that's on the #125 pull request. Did you see any other
> AppArmor denial message that could help confirm that the AppArmor
> profiles were at fault on that one?

not anymore.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to