Opened 7 years ago

Last modified 3 years ago

#3544 new enhancement

Add to menu option for TBB

Reported by: phobos Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-usability
Cc: mildred-pub.tor@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

In a survey of the three people who've called me in the past week, all have said they don't use TBB because it doesn't appear in their application menu; whether this is the start menu in windows, gnome/kde/xfce menu.

If there was an option to let the user put a link to 'start tor browser' on their desktop or in their menu, that would make these people happy.

I suspect this desire is more common than not, but so far 3 out of 3 people that have called me, wanted it.

Child Tickets

Change History (9)

comment:1 Changed 7 years ago by mikeperry

Component: Tor BrowserTor bundles/installation
Owner: changed from mikeperry to erinn

comment:2 Changed 7 years ago by mikeperry

This is tricky.. It definitely shouldn't be a default.. more first-run popups for vidalia?

comment:3 Changed 7 years ago by chiiph

I'd vote for this being a plugin. It should be pretty straight forward, but it will be in the alpha bundles only.

comment:4 Changed 7 years ago by mikeperry

Milestone: TorBrowserBundle 2.3.x-stable

comment:5 Changed 7 years ago by mildred593

Cc: mildred-pub.tor@… added

Hi,

I was one of these people that didn't use the bundle, in part because it was not integrated in the desktop (gnome-shell). Another reason is that it was not packaged with the distribution. Also, I think that the tor daemon should be like any other daemons, started by the system init.

Now that TorButton cannot be switched off, I removed it from Firefox and tried to get the TBB.

Unfortunately, the TBB just shows a shell script on linux versions, and there is no .desktop file. Consequently, there is no way to start it from the gnome-shell. I created a simple .desktop file, but it misbehaves with the dock.

The reason is that TBB starts two applications (as seen by gnome-shell) and my .desktop file is a 3rd application in my dock.

There are two ways to get it right I think:

  • have two applications:
    • TBB: this is the one the user starts, when started, it start automatically vidalia (if not already started).
    • vidalia: started automatically by other bundle applications, or started manually when one just wants the tor daemon running with no application. Additionally, it could feature a menu as suggested in #5693
  • have all three applications joined in a single one. If you only have a browser it's manageable, but it becomes a bit messy if there are other bundled application such as a chat application. It could feature the icon presented in #5467

Of course, a .desktop file should be bundled in. At startup, the .desktop files should be symlinked to ~/.local/share/applications and the user just have to "favourite" the application to make it appear permanently in the dock.

(the symlink to ~/.local/share/applications is essential because if not, the "favourite" action to keep the application in the dock will most probably feature an incorrect Exec= line in the .desktop entry)

comment:6 in reply to:  5 Changed 6 years ago by arma

Replying to mildred593:

Of course, a .desktop file should be bundled in.

Can you write a sample one for us? I think none of the Tor developers use an environment that wants one.

comment:7 Changed 4 years ago by erinn

Keywords: needs-triage added

comment:8 Changed 4 years ago by erinn

Component: Tor bundles/installationTor Browser
Owner: changed from erinn to tbb-team

comment:9 Changed 3 years ago by lunar

Keywords: tbb-usability added; needs-triage removed
Milestone: TorBrowserBundle 2.3.x-stable
Severity: Normal

There is now a .desktop file that works nicely, and even a --register command line script that can copy the .desktop file in the right location. What is missing is something like a question on the first run where users could opt-in to get the icon added to the menu without having to drop to the command line.

Note: See TracTickets for help on using tickets.