mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #429] Bugfix: chromium open multiple tabs is only supported when remote debugging is enabled #288
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#288
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @arturi on GitHub (Aug 8, 2020).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/429
Thank you for the awesome work on ArchiveBox!
Describe the bug
Getting the below error on
archivebox addwhen trying to make pdf/screenshot with chromium. Additionally gettingxdg-settings: not found.Steps to reproduce
Ran ArchiveBox as
archivebox add https://example.comSoftware versions
@pirate commented on GitHub (Aug 10, 2020):
Can you run these commands manually and post the output:
@zachscheider commented on GitHub (Aug 11, 2020):
I was also getting the 'multiple tabs' error with that same chromium snap version. It impacted screenshots and DOM dumps too.
Updating to edge fixed it for me.
sudo snap refresh --edge chromiumhttps://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887795
@pirate commented on GitHub (Aug 11, 2020):
Since this can be fixed by upgrading chromium, I'm going to close it here. Thanks for reporting this and posting the link to the fix!