[documentation] How can I test first-start issues in PureBrowser?
Closed, ResolvedPublic

Description

I noticed an issue with PureBrowser the first time I started it and reported it (e.g. https://tracker.pureos.net/T394 ). Since then I have been using PureBrowser and modified my browser profile such that the issue no longer occurs.

An update has landed and I want to confirm the fix. How can I do this without losing my new profile settings?

d3vid created this task.Jul 25 2018, 10:02 AM
d3vid closed this task as "Resolved".Jul 25 2018, 10:06 AM

You can create a fresh profile, launch PureBrowser and then delete the profile:

  1. Close any running instances of PureBrowser
  2. Start with purebrowser --ProfileManager
  3. In the profile manager window, create a new profile "temp"
  4. Click "Start PureBrowser"

You can now test for the first-start issue. When you are done...

  1. Close any running instances
  2. Start with purebrowser --ProfileManager
  3. Delete the profile "temp" (delete profile and files)
  4. Close the profile manager window
d3vid changed the title from "[query] How can I reproduce/test PureBrowser start issues?" to "[query] How can I test first-start issues in PureBrowser?".Jul 25 2018, 10:08 AM

Thanks for sharing. I do believe, however, that wiki is a better medium for sharing best practices than an issue tracker.

Not sure how to act on this, so I guess I'll simply leave it for others - e.g. either followup and "fix" this "issue", or move the content to a wiki, mention here where it moved, and then close it.

d3vid changed the title from "[query] How can I test first-start issues in PureBrowser?" to "[documentation] How can I test first-start issues in PureBrowser?".Aug 8 2018, 12:23 PM
d3vid reopened this task as "Open".
d3vid triaged this task as "Low" priority.

I've reassigned this to myself to post these steps on the https://tracker.pureos.net/w/troubleshooting/ page.

Add Comment