Your message dated Mon, 20 Nov 2017 14:17:02 +0100
with message-id <20171120131702.GJ9456@debian>
and subject line Re: Bug#855522: [Pkg-privacy-maintainers] Bug#855522: 
torbrowser-launcher: torbrowser won't start because of apparmor
has caused the Debian Bug report #855522,
regarding torbrowser-launcher: torbrowser won't start because of apparmor
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.)


-- 
855522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855522
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.2.6-3
Severity: grave
Justification: renders package unusable

Hi,

As of now the AppArmor profile for torbrowser-launcher renders it unusable.
Workaround consists in launching this command :
sudo aa-disable torbrowser.start-tor-browser

If you don't do so, here's the output from the shell :
orbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.6
https://github.com/micahflee/torbrowser-launcher
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve
property `gtk-primary-button-warps-slider' of type `gboolean' from rc file
value "((GString*) 0x55a679ff8840)" of type `gboolean'
Launching './Browser/start-tor-browser --detach'...
/usr/bin/env: « bash »: Permission non accordée

'Permission non accordée' = 'Permission denied'



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates  20161130
ii  gnupg            2.1.18-3
ii  python-gtk2      2.24.0-5.1
ii  python-lzma      0.5.3-3
ii  python-parsley   1.2-1
ii  python-psutil    5.0.1-1
ii  python-twisted   16.6.0-2
ii  python-txsocksx  1.15.0.2-1
pn  python:any       <none>
ii  wmctrl           1.07-7

Versions of packages torbrowser-launcher recommends:
ii  tor  0.2.9.9-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.11.0-2
pn  python-pygame  <none>

-- Configuration Files:
/etc/apparmor.d/usr.bin.torbrowser-launcher changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message ---
tags 855522 - moreinfo
fixed 855522 0.2.8-5
thanks

Hi,

Sorry for the late response, had to recover from a surgery:

On 17-11-09 10:24:34, intrigeri wrote:
> This bug seems to be about the torbrowser.start-tor-browser profile,
> that we stopped shipping a while ago, but apparently failed to remove
> from systems upon upgrade. I think it's a duplicate of #838817. If you
> can reproduce this bug because of an obsolete
> torbrowser.start-tor-browser conffile left behind, then that's indeed
> #838817. I've suggested a rather straightforward fix in #838817#31.

This analysis is correct, thanks for the upload you've made, it fixed
the problem for me. Therefore, closing this bug and marking as fixed in
version 0.2.8-5.

Cheers,
Georg

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to