desktop: Previous profiles not showing in updated profiles tab (1.9b)

Captchas

  • I have read the instructions.
  • I have searched existing issues and avoided creating duplicates.
  • I am not filing an enhancement request.

What happened?

Before update i was using Url about:profiles for switching profiles which is still working properly but after updating to version 1.9b , the profile button is added in account tab and there is no existing profile showing but showing in about:profiles url

Reproducible?

  • I have checked that this issue cannot be reproduced on Mozilla Firefox.

Version

1.9b

What platform are you seeing the problem on?

Windows

Relevant log output if applicable


About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 8
  • Comments: 20 (1 by maintainers)

Most upvoted comments

These profiles are still in dev in Firefox itself, and I honestly wouldn’t try to switch to them at all, until there’s at least some word about them from Firefox. As things stand now, they’re still an expeiment with zero guarantees on its stability…

Zen should’ve held out on enabling this until it’s at least a little more baked (not necessarily fully stable on FF, just good enough) with a proper migration path (whether it’s auto or manual). But at the same time it probably works fine for new users, so it’s a good idea to onboard them on the new system early on (though if this changes and breaks in the future, that won’t be great).

Maybe I’m understanding it wrong or missing something, but for now I just pinned about:profiles…

@Skaldebane Valid. Though if it is this undercooked, not only it should not have been enabled while essentially alpha code, but the original profile chooser should not have been removed. The impulse change just busted workflow for anyone who used multi-profile setup. Sure, you can make shortcut that prompts for profile selection on start, you can pin about:profiles, but it still is annoyance when there was a perfectly valid system that got abandoned and nuked in favor of native alpha code.

I think Firefox uses some new method to manage profiles? I tried creating a profile from the menu, but then if I access about:profiles I see a message that the profiles were modified elsewhere and I need to restart the browser. After a restart, the new profile only shows in the menu but not inside about:profiles. A way to migrate the old profiles to the new format would be nice.

@arpadgabor I have been poking around because it was intriguing to me how the new profiles work, and found out this:

Zen made a new folder called Profile Groups in your profiles folder. This folder holds SQLite databases. Each profile made with about:profiles will gets its own database on its 1st launch in any Zen version with the new profile system present, and the filename of this database is without the file extension noted down on its entry in profiles.ini, in the StoreIDparameter. The new profile system profiles are not recorded into profiles.ini, but they instead are grouped with a parent profile that created them in its SQLite store.

If you wish to immediately “import” your profile created with about:profiles, without waiting for any possible future import mechanisms, you will need to:

  1. Close Zen.
  2. Backup your whole profiles folder (~/.zen folder on Linux, not sure on other OSes of top of my head) before doing any changes!!! That way you don’t lose your profiles if anything goes south.
  3. In profiles.ini, find StoreID of your desired parent for your other profile. This will also be the file name of its SQLite store in the Profile Groups folder.
  4. Open the SQLite store (<StoreID>.sqlite) of the profile you want to parent the other profile with in any SQLite database browser, open its Profiles table, and create an entry for your other profile in there, similar to the one already present. Simplest way is to copy whole row, and replace just the profile path and profile name (By default, relative paths are used, so just put profile’s folder name into path column. I don’t know if absolute paths work in the new system, but I never saw anyone use a profile outside the profile folder…). You can do other edits to it later in Zen using “Edit profile” option in the new profile manager. Editing the parameters too much straight in the database is asking for a trouble.
  5. Save the database changes after you are done adding and editing the row.
  6. Edit the parented profile in profiles.ini to use same StoreID as its new parent profile, and set ShowSelector=1 to enable the profile selector. After saving, run Zen at least once in this state - this should make the profile hook up properly with its parent in the new profile manager.
  7. After running Zen to make the profiles pair together, close it, and delete the profiles.ini entry for the profile you parented to prevent the old profile manager from touching it. From now on, the profile will behave as if created with the new system, which means not being listed on about:profiles, and usable only from its new parent profile.

Closing this issue as part of a repo cleanup

Due to technical-debt we had in the past, we are currently clearing out old, duplicate, stale, and non-actionable issues to improve issue tracking and make it easier to focus on fixing real bugs.

If this issue is still relevant, please open a new issue using our updated issue template, which will help us categorize and address it more efficiently.

Thanks for your understanding and for helping us improve the project! 🚀

This issue can be reopened at: https://github.com/zen-browser/desktop/issues/new?template=bug_report.yml&title=Previous profiles not showing in updated profiles tab (1.9b)

I think Firefox uses some new method to manage profiles? I tried creating a profile from the menu, but then if I access about:profiles I see a message that the profiles were modified elsewhere and I need to restart the browser. After a restart, the new profile only shows in the menu but not inside about:profiles. A way to migrate the old profiles to the new format would be nice.

These profiles are still in dev in Firefox itself, and I honestly wouldn’t try to switch to them at all, until there’s at least some word about them from Firefox. As things stand now, they’re still an expeiment with zero guarantees on its stability…

Zen should’ve held out on enabling this until it’s at least a little more baked (not necessarily fully stable on FF, just good enough) with a proper migration path (whether it’s auto or manual). But at the same time it probably works fine for new users, so it’s a good idea to onboard them on the new system early on (though if this changes and breaks in the future, that won’t be great).

Maybe I’m understanding it wrong or missing something, but for now I just pinned about:profiles…

rampa3: Tried the new 1.10b release to see if stuff got better, but it is still busted.

I did as well, I can swap profiles from the triple dot menu but cannot edit them. This is ‘good enough’ for me, so I will not roll back for now…

Skaldebane: Zen should’ve held out on enabling this until it’s at least a little more baked…it’s a good idea to onboard them on the new system early on…

I completely agree. I have about:profiles pinned, it works fine but wanted to see if I could get them working with the new system now with whatever pros/cons are associated with that. If that’s the way we’re going I might as well (imo, maybe unpopular opinon) work through the growing pains now. But agreed, like you said, Zen probably should’ve stayed out of the new system until it was a bit more baked… it is barely even a batter right now.

@jackgraddon Tried the new 1.10b release to see if stuff got better, but it is still busted. I say we should make a standalone issue about the breaking profiles, unless it will work with profiles made with the new system flawlessly, or Firefox has busted it upstream too. I will go test fresh profiles and vanilla Firefox if I get a free moment. Sadly I am very busy lately… For now, back to 1.9b.

@jackgraddon Downgrade to 1.9b and re-adding the child theme into profiles.ini for a single launch fixed it. I bet if I update, it will bust again. But yeah, one version back it works fully after the migration done as I described above.