[tor-bugs] #7249 [- Select a component]: Ticket #5433 - May Crash It?

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#7249: Ticket #5433 - May Crash It?
----------------------------------+-----------------------------------------
 Reporter:  DasFox                |          Owner:                               
     Type:  defect                |         Status:  new                          
 Priority:  normal                |      Milestone:  TorBrowserBundle 2.2.x-stable
Component:  - Select a component  |        Version:                               
 Keywords:                        |         Parent:                               
   Points:                        |   Actualpoints:                               
----------------------------------+-----------------------------------------
 Going back to this bug;

 ---------------------------------------------

 https://trac.torproject.org/projects/tor/ticket/5433

 This line by ransom;

  Changed 7 months ago by rransom

     status changed from new to closed
     resolution set to not a bug

 Vidalia uses Qt, and Vidalia in TBB is configured to use the Clearlooks
 theme because loading a system-wide Qt theme may crash it. (Different
 versions of Qt libraries do not mix well.)

 ---------------------------------------------

 Has anyone ever seen a crash when it's set to use GTK+?

 I've used the TBB for as long as it's been around and I've never
 experienced crashes, so when the word 'May' was spoken, what about that it
 may never be an issue either and can't this be tested and allowed to be
 simply changed in the preferences by the end-user?

 I'm not certain why if this is considered a problem then why does Vidalia
 still have Apperance options, if the end-user can't use them?

 In 'start-tor-browser' I changed the line like this;

 ./App/vidalia --datadir Data/Vidalia/ -style GTK+

 So I'm a bit lost here since this was never explained in the past, if this
 was closed because this is a defect, what defect are we talking about here
 and how can this defect be fixed?

 Going back to very early 2.2x versions this was working and I only noticed
 it starting at version 2.2.35-9, so why did it work before this?

 THANKS

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7249>
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