Your message dated Thu, 28 Jan 2016 10:58:54 +0100
with message-id <[email protected]>
and subject line Re: Bug#768857: torbrowser-launcher (0.1.6-1): processes do 
not terminate on exit and tor browser cannot be reopened
has caused the Debian Bug report #768857,
regarding torbrowser-launcher: torbrowser-launcher (0.1.6-1): processes do not 
terminate on exit and tor browser cannot be reopened
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.)


-- 
768857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768857
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.1.6-1
Severity: important

Dear Maintainer,

Problem cannot always be reproduced, but one out of about 4 time opening tor 
browser, exit will be unclean (processes do not die):

1. open tor browser
2. do some surfing
2. close tor browser

On close, the window disappears but even after 10 minutes, those processes 
remain:

13.1  4.8 669328 194916 ?       Sl   19:24   0:53 ./firefox --class Tor Browser 
-profile TorBrowser/Data/Browser/profile.default
0.1  1.0 213204 40564 pts/2    S+   19:17   0:00 /usr/bin/python 
/usr/bin/reportbug torbrowser-launcher
0.0  0.0   4328   752 pts/2    S+   19:18   0:00 sh -c /usr/bin/sensible-editor 
 '/tmp/reportbug-torbrowser-launcher-20141109-20534-2o2U4C'
0.0  0.0   4328   796 pts/2    S+   19:18   0:00 /bin/sh 
/usr/bin/sensible-editor 
/tmp/reportbug-torbrowser-launcher-20141109-20534-2o2U4C
0.0  0.0  18904  3532 pts/2    S+   19:18   0:00 /usr/bin/joe 
/tmp/reportbug-torbrowser-launcher-20141109-20534-2o2U4C
0.3  1.5 221036 60952 ?        S    19:24   0:01 /usr/bin/python 
/usr/bin/torbrowser-launcher
0.0  0.0  13528  3076 ?        S    19:24   0:00 /bin/bash 
/home/gpall/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-tor-browser
13.1  4.8 669328 194916 ?       Sl   19:24   0:53 ./firefox --class Tor Browser 
-profile TorBrowser/Data/Browser/profile.default
0.0  0.1 451144  7620 ?        Sl   Nov08   0:00 
/usr/lib/gvfs/gvfs-udisks2-volume-monitor

And so clicking again on tor browser icon gives the well known message about
firefox already running etc. After manually killing processes, tor browser
can be used again.

Thanks, 
Giorgos

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages torbrowser-launcher depends on:
ii  gnupg            1.4.18-4
ii  python           2.7.8-2
ii  python-gtk2      2.24.0-4
ii  python-lzma      0.5.3-2+b1
ii  python-parsley   1.2-1
ii  python-psutil    2.1.1-1+b1
ii  python-twisted   14.0.2-2
ii  python-txsocksx  1.13.0.3-1
ii  tor              0.2.5.10-1
ii  wmctrl           1.07-7

torbrowser-launcher recommends no packages.

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

-- no debconf information

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

closing as unreproducible today.


cheers,
        Holger

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


--- End Message ---

Reply via email to