[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #17379 [Applications/Tor Browser]: Using the same build process in Tor Browser and Tor Messenger

#17379: Using the same build process in Tor Browser and Tor Messenger
--------------------------------------+-----------------------
 Reporter:  boklm                     |          Owner:  boklm
     Type:  task                      |         Status:  new
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  tbb-gitian                |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+-----------------------

Comment (by boklm):

 Replying to [comment:13 boklm]:
 > > After we copied libevent from TB 7.0a1 to the /var/tmp/... path, we
 got further: tor.real started up and completed the bootstrap phase but it
 exited immediately after that point:
 > >  [notice] Owning controller connection has closed -- exiting now.
 > >
 > > We do not know why tor thinks the connection has closed (maybe the
 browser is closing the control port connection or maybe it is not). Is
 this a known problem?
 >
 > I also have the same error, but did not find the reason yet.

 This seems to be fixed now.

 I think the reason was a corrupt omni.ja file, which is fixed by this
 commit:
 https://gitweb.torproject.org/builders/tor-browser-
 build.git/commit/?id=38863663120244e4becc66fe7a10cce92d8e639b

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17379#comment:14>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs