Opened 10 years ago

Last modified 9 years ago

#1012 closed defect (Duplicate)

Torbutton makes tons of preference changed popups

Reported by: stars Owned by:
Priority: High Milestone:
Component: Applications/Torbutton Version: Torbutton: 1.2.1
Severity: Keywords:
Cc: stars Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hello,

i have firefox 3.0.11 with new profile, so no plugins added and run on linux jaunty 64 bits.

When i open the browser i can enable-Tor but when it will restart it cannot enable it.

my best

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Attachments (1)

torbutton-1012.xpi (301.6 KB) - added by mikeperry 10 years ago.
Also fix locale strings

Download all attachments as: .zip

Change History (15)

comment:1 Changed 10 years ago by mikeperry

Can you please try out the .xpi I attached to Bug 1006:
https://bugs.torproject.org/flyspray/index.php?do=details&id=1006&area=attachments

and let me know if it gives you a new alert message?

comment:2 Changed 10 years ago by stars

well try it but now when i will open the preference for exemple, i become the error message and "torbutton" crash

Erreur d'analyse XML : entité non définie
Emplacement : chrome://torbutton/content/preferences.xul
Numéro de ligne 113, Colonne 26 : <label value="&torbutton.prefs.no_proxies_on;" control="torbutton_noProxiesOn"/>


in terminal: [07-30 11:39:32] Torbutton NOTE: Blocking redirect: https://bugs.torproject.org/flyspray/index.php?do=authenticate

i have firefox 3.0.12 in jaunty 64 bits x86 64

Changed 10 years ago by mikeperry

Attachment: torbutton-1012.xpi added

Also fix locale strings

comment:3 Changed 10 years ago by mikeperry

Ah, I didn't update the xpi with any other languages than english.

Can you try the xpi in the attachments tab for this bug? It should have english
placeholder strings now.

comment:4 Changed 10 years ago by stars

i have test your patch xpi and the message up are what torbutton say with it

comment:5 Changed 10 years ago by stars

sorry i have not see was a new one..

Well yet it make no more error :=)

Now are a new problem: when i confirm with ok i need click almost 10 times to can confirm and close the windows:

"Vous devez activer/désactiver Tor ou redémarrer pour que vos changements soient pris en compte."

The biggest problem of torbutton are the security fails....

I.E: on http://analyze.privacy.net:

it seem too much infos give as we can do : http://pastebin.ca/1519271

on https://www.jondos.de/en/anontest :http://pastebin.ca/1519272

on http://decloak.net/ : http://pastebin.ca/1519273

now what i obtain with my config optimized and with jondofox 2.2.3 the new one

on http://analyze.privacy.net/ : http://pastebin.com/m2ae022a4

on https://www.jondos.de/en/anontest http://pastebin.com/m64a8d79c

on http://decloak.net/ http://pastebin.com/m4bad2350

well with my config i obtain a many better load time for the page web

So i hope you can fix the last problem with the "ok" in torbutton when we will conirm a changement in "preference" and about speed

A great thing are to can observe and look about the new config for made by jondofox. are really somethings to can be used and the config of browser too need to be change.

While we need look wiki and make the same config on firefox beacause torbutton don't change that

with torbutton, i don't have the menu " a propos" or "about" where we can change a few things like "KEEP_ALIVE 600"

thanks for all


comment:6 Changed 10 years ago by mikeperry

Hrmm... Your pastebin posts expired already, and all those tests look good to me using the latest torbutton XPI
I attached here. Can you repaste the complete set of test results again with an expiration time longer than
1 day?

Also, I'm confused as to what you're talking about as far as speed settings.

Also, about those messages about needing to toggle your tor settings: do they happen randomly or only when
you change a large number of preferences?

comment:7 Changed 10 years ago by stars

ok, about the problem to quit the preference: that's do all the time and without change something, when i will quit the windows it need 10x to can do.

About test , that's a comparaison between torbutton and jondofox.

Some test say torbutton as not very secure, look the test...

torbutton:

http://pastebin.com/f77844d7 for : http://analyze.privacy.net/

http://pastebin.com/f2ddbd9f1 for: https://www.jondos.de/en/anontest

http://pastebin.com/f6c9ff299 for : decloak

http://pastebin.com/f72a4f33 for xenobite

you will see on all test except decloak are singaled bad!

another important point are the extrem slow loading for the web page with torbutton.

So if you compare test and maybe test the last jondofox, you will see the difference with loading and all test are signaled good .

i hope that's will help you. Anyway i will use torbutton when it will performant and don't give so much infos from our system

my best

comment:8 Changed 10 years ago by mikeperry

So JohnDoNym focuses more on HTTP headers than we do. I'm planning on integrating their header stuff at some point
but it is a lower priority than major bugs, IP address leaks, and Firefox 3.5 compatibility.

Do you have a URL for the xenobite test suite? I am trying to collect a bunch of these test suites for future
reference.

For your preference quitting bug, what other addons do you have installed? It seems like something might be
changing your preferences out from under you. Can you try to create a fresh firefox profile with:

firefox -P -no-remote

and gradually adding addons and seeing if you can find which one causes it?

comment:9 Changed 10 years ago by stars

i have already create a new proile for torbutton but i can try with "-no-remote" one more time.

link for xenobite: https://torcheck.xenobite.eu/index.php

actually seem only the hidden service down but all test anyway.

well sure the tweaks are not a priority and like you say compatibility and leaks are the most important.

that's why i look of both and take idea or compare. Anyway there look about torbutton too ;)

well great that's help you and i keep in touch with another one new profile tomorow.

The profile actuel with torbutton have no plugins, only torbuuton from your attachement added.

comment:10 Changed 10 years ago by stars

well no difference with no remote, same problem.

i have found a crash reported by a friend and found by me too , can be see in terminal

LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/nphelix.so mauvaise classe ELF: ELFCLASS32
[08-11 07:00:26] Torbutton NOTE: Conflict between noncrashed and normal_exit states.. Assuming crash but no session restore..
[08-11 07:00:26] Torbutton NOTE: Crash detected, attempting recovery
[08-11 07:00:26] Torbutton NOTE: Restoring cookie status
[08-11 07:00:27] Torbutton NOTE: Loading non-tor jar after crash
[08-11 07:00:27] Torbutton NOTE: Restoring tor state

seem a bug by many peoples

comment:11 Changed 10 years ago by stars

i have found with terminal some error and maybe will help you

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:29887): Gdk-CRITICAL : gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed
LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/nphelix.so mauvaise classe ELF: ELFCLASS32
[08-21 00:01:11] Torbutton NOTE: First time startup completed
LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/nphelix.so mauvaise classe ELF: ELFCLASS32
[08-21 00:01:11] Torbutton NOTE: Restoring tor state
LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/nphelix.so mauvaise classe ELF: ELFCLASS32
[08-21 00:01:24] Torbutton NOTE: Restoring tor state
[08-21 00:01:26] Torbutton NOTE: Some other addon tried to clear user agent settings.

comment:12 Changed 10 years ago by stars

i have see at https://torcheck.xenobite.eu/index.php? after made test it will propose addon to fix the problem, it propose "RefControl" for headers, that's a add-on mozilla, cookie cuter and no script , like you say on tor doc.

I think if you add the refcontrol and use postion, give the adresse of the source of site , so it make like with jonofox, it give only where you are :=)

utf-8 for charset will perfect and */* for content type

with that i think torbutton will almost perfect, about cookie cut killer are not really optimal.

comment:13 Changed 10 years ago by mikeperry

flyspray2trac: bug closed.
This bug has devolved. As near as I can tell, the current comments are a dup of 1089

comment:14 Changed 9 years ago by erinn

Version: 1.2.1Torbutton: 1.2.1

Updating the version from 1.2.1 to Torbutton: 1.2.1 so I can close #1743.

Note: See TracTickets for help on using tickets.