Opened 7 months ago

Last modified 3 months ago

#32329 new defect

After upgrading Tor Browser 8.5.1 -> 9.0, history contains place:sort=8&maxResults=10

Reported by: cypherpunks Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-update, TorBrowserTeam202006
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Configuration: Xubuntu Linux 18.04 LTS 32-bit

I noticed this issue when upgrading Tor Browser 8.5.1 to 9.0. I do not know if the issue also occurs when using a newly extracted copy of Tor Browser 9.0.


  1. Extract Tor Browser 8.5.1 (32-bit) from the file tor-browser-linux32-8.5.1_en-US.tar.xz
  2. Open the tor-browser_en-US directory and launch Tor Browser Setup.
  3. Click Connect in the dialog box that talks about adjusting network settings for certain situations.
  4. Once the Tor Browser window (with the address bar) opens, choose "Check for Tor Browser Update..." from the onion menu.
  5. Tor Browser will download an update. Once the window indicates that the update will be installed when Tor Browser is restarted, click Restart Later and then close the Tor Browser window.
  6. In the tor-browser_en-US directory, launch Tor Browser.
  7. Once the Tor Browser window opens, click in the address bar.
  8. Type "s" (without quotes.)
  9. The history will contain the entry place:sort=8&maxResults=10

The information about Places query URIs from Mozilla may be relevant.

Child Tickets

Change History (4)

comment:1 Changed 7 months ago by gk

Keywords: tbb-update added

Interesting, although harmless at first glance.

comment:2 Changed 7 months ago by sysrqb

Keywords: TorBrowserTeam202002 added

I agree. I see this in the Tor Browser installation I am using, as well. It upgraded from 8.5.5.

comment:3 Changed 4 months ago by sysrqb

Deferring some more tickets from February 2020 to June 2020. Too many tickets, not enough time.

comment:4 Changed 3 months ago by sysrqb

Keywords: TorBrowserTeam202006 added; TorBrowserTeam202002 removed

Second attempt at deferring tickets until June.

Note: See TracTickets for help on using tickets.