Operating system
Linux
Version
Version 0.20.1.1 (Official Build, Chromium 156.0.8078.47) deb (x86_64)
Have you tested that this is not an upstream issue or an issue with your configuration?
- I have tried reproducing this issue in Chrome and it could not be reproduced there
- I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
- I have tried reproducing this issue in Helium with a new and empty profile using
--user-data-dircommand line argument and it could not be reproduced there
Description
When Helium starts, the bookmarks bar is missing on the first New Tab page. It only shows up if I manually open another tab.
Crash ID
No response
How to Reproduce?
- Open Helium settings and set the bookmarks bar to "Only show on New Tab page".
- Close Helium completely.
- Open Helium again. It automatically opens a New Tab page.
- Look at the top of the window: the bookmarks bar is gone.
- Press Ctrl+T to open a second tab.
- The bookmarks bar appears immediately.
Actual behavior
The bookmarks bar is hidden on the first tab after launch. I have to manually open a new tab to make it visible.
Expected behavior
The bookmarks bar should be visible on the initial New Tab page. The setting is already set to "Only show on New Tab page", so it shouldn't be hidden.
Additional context
I've attached a screen recording. You can see the setting is on "Only show on New Tab page", but the bar is missing when the browser opens. It only appears after opening a new tab. Also, this bug didn't exist in the previous version. It started happening after the latest update.
https://github.com/user-attachments/assets/8aba6999-23d5-48ba-bc80-e91a90d1f7c5
Activity
3I'm on Linux but I wasn't able to replicate it. Did you try in a brand new profile?
5. I'm on Linux but I wasn't able to replicate it. Did you try in a brand new profile?
https://github.com/user-attachments/assets/27b6da88-632d-40f7-8904-12211c0778fc
I just created a brand new test profile and added a test bookmark there. I went straight into it, but the result was exactly the same. I've attached a video of this test as well.
Thanks for checking. It seems this bug only happens on the Linux version.