Page MenuHomePureOS Tracker

purebrowser: never exits
Closed, WontfixPublic


Purebrowser in amber on 19 Sep 2019, purebrowser/amber, now 68.1.0esr+really60.9.0esr-1~deb10u1pureos1 amd64, is on the system nearly unusuable because it never exits.

The window closes, but the instance persists, as evidenced by "ps -e | grep pure".

The problem seems to be that SQlite3.jsm does not want to exit.

Workaround is in


Event Timeline

emmes created this task.Sep 19 2019, 01:24
emmes added a comment.Sep 19 2019, 02:24

Obviously, title should be purebrowser bug and the line in mybrowser that reads "exec /usr/lib/purebrowser/purebrowser" should have $1 appended at the end of the line.

@emmes why did you attach a text file, not post directly the text?!?

jonas.smedegaard renamed this task from pure browser bug to purebrowser: never exits.Sep 19 2019, 04:08
jonas.smedegaard updated the task description. (Show Details)

@emmes your attached notes seem to indicate that this has been an issue for quite a while - when did you first experience this issue?

emmes added a comment.Sep 20 2019, 11:55


I uploaded a file rather than typing in the text directly because i am not familiar with phabricator, and the changes to purebrowser and installed extensions made it even more flakey in my hands, and after having my text twice wiped out, and rushing to catch a plane, it was easier to put a file on my computer. and upload it.
Also when you upload a file to emacs, no one knows it is uploaded as it is simply appended to the buffer, but phabricator chooses not to do that.

the problem started the same day I filed the bug report, immediately after upgrading to 60.9esr.

jonas.smedegaard closed this task as Wontfix.Sep 28 2019, 01:45
jonas.smedegaard claimed this task.

The cause of this issue is likely either that your PureBrowser profile is corrupted or that it contains data only readable by Firefox 68.x not 60.x which PureBrowser is no reverted to.

In either case, a workaround is to "abandon ship" and move to a fresh profile - e.g. by once running purebrowser --ProfileManager from a terminal emulator. After moving to a new profile, you may try to import data from the old profile. Sorry for the trouble.

Properly fixing this issue os too complex to do, and thus marking this as wontfix.