You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for creating vimb! I've been using it as my primary browser for a few months now and I wildly prefer it to Firefox, but I still seem to need Firefox because I can't seem to link Trello and Github (and I require this at work).
The authorization is initiated from Trello. A new window is created with the Github OAuth authorization page. At some point at the end of the flow, but before Trello has received authorization from Github vimb crashes. It does this every time and I haven't found any work-around (except to use Firefox :( ).
Go to Trello.com and log in or sign up if you need to. Create a new Trello board.
On the new board, click "Show Menu" in the top right corner and then click "Power-Ups" in the menu.
Find the "GitHub" power-up and press the green "Add" button. The button will disappear and will be replaced by a gear button.
Click the gear button and select "Authorize Account" and then "Link Your Github Account". This will open a new window to the GitHub authorization page.
Proceed with GitHub authorization.
Expected behaviour
After a bunch of redirects the new window should close and only the window with the Trello board should remain; the Trello GitHub power-up should be enabled and the gear menu for the power-up should look like this (produced with Firefox):
Actual behaviour
Both vimb windows disappear - both the one with your trello board, and the new window with the GitHub authorization page. Re-launching vimb and navigating to Trello, you'll see that the new board is still there, the GitHub power-up is enabled, but clicking the gear button next to the power-up still prompts you to "Authorize Account", implying that the authorization didn't work.
If you try to authorize with Github again then the crash will happen again too.
When running vimb from the console the crash produces this output:
@eskilandreen I can reproduce this issue by a simple html file with following link <a href="#" onclick="window.close()">Close Pop-Up</a>. If I fire this link, vimb crashes.
@eskilandreen Wow github feature closed this issue by coincidence of special commit message together with the issue number. I've fixed a segfault in case a window was cloase by JavaScript window.close(); so could you please check if this fixes also your issue?
Thanks for creating vimb! I've been using it as my primary browser for a few months now and I wildly prefer it to Firefox, but I still seem to need Firefox because I can't seem to link Trello and Github (and I require this at work).
The authorization is initiated from Trello. A new window is created with the Github OAuth authorization page. At some point at the end of the flow, but before Trello has received authorization from Github vimb crashes. It does this every time and I haven't found any work-around (except to use Firefox :( ).
Commit: 5cc4709
WebKit compile: 2.22.4
WebKit run: 2.22.5
GTK compile: 3.24.1
GTK run: 3.24.3
libsoup compile: 2.64.2
libsoup run: 2.64.2
Extension dir: /usr/lib/vimb
Steps to reproduce
Expected behaviour
After a bunch of redirects the new window should close and only the window with the Trello board should remain; the Trello GitHub power-up should be enabled and the gear menu for the power-up should look like this (produced with Firefox):
Actual behaviour
Both vimb windows disappear - both the one with your trello board, and the new window with the GitHub authorization page. Re-launching vimb and navigating to Trello, you'll see that the new board is still there, the GitHub power-up is enabled, but clicking the gear button next to the power-up still prompts you to "Authorize Account", implying that the authorization didn't work.
If you try to authorize with Github again then the crash will happen again too.
When running vimb from the console the crash produces this output:
coredumpctl info shows the following:
The text was updated successfully, but these errors were encountered: