Taking a screenshot in headless CLI hangs on Linux
Categories
(Firefox :: Headless, defect, P3)
Tracking
()
People
(Reporter: alex, Unassigned)
References
Details
(Keywords: hang)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
On Ubuntu 18.04.3 x64, in an X-Server session.
Reproduced with 69.0.2 from official Ubuntu repos, and also with 70.0b14.
Run firefox --screenshot file:///path/to/file.html to reproduce.
Actual results:
Outputs:
*** You are running in headless mode.
Firefox then hangs and the screenshot is not generated. Firefox has to be killed with ctrl + c.
Expected results:
A file named screenshot.png should have generated in the cwd.
|
||
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
|
||
Comment 2•5 years ago
|
||
The priority flag is not set for this bug.
:bdahl, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Updated•5 years ago
|
|
||
Comment 4•4 years ago
|
||
Reproducible at Nightly 83
|
|
||
Comment 5•4 years ago
|
||
Is "Always ask where to save files" set at Preferences?
|
Reporter | |
Comment 6•4 years ago
|
||
(In reply to guest271314 from comment #5)
Is "Always ask where to save files" set at Preferences?
No, it is not set.
|
|
||
Comment 7•4 years ago
|
||
Worked momentarily when removing then reinstalling firefox as .deb https://bugzilla.mozilla.org/show_bug.cgi?id=1412061#c12. Then the results resume to be consistently hanging. The error message when CTRL+C is pressed appears to be from https://searchfox.org/mozilla-central/source/ipc/glue/MessageChannel.cpp#2526, see https://bugzilla.mozilla.org/show_bug.cgi?id=1674584. I have also filed https://bugzilla.mozilla.org/show_bug.cgi?id=1674289.
|
|
||
Comment 8•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
|
|
||
Comment 9•1 year ago
|
||
The severity field is not set for this bug.
:mpohle, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Comment 10•1 year ago
|
||
Because there is a workaround available (the web console can be used) I can only vote for a severity of S3, but I also think that this can make the setup of custom browser automation more difficult, e.g. a bash script to compare a screenshot against a known-good one. Please vote for this bug if you think that this bug is between you and your automation attempts or comment if you have further use cases, which could justify a re-estimation. To get all voices in one place, I will also close the Bug 1674289, because it is a duplicate of this one and not yet prioritized.
|
|
Reporter | |
Comment 12•1 year ago
|
||
Bash script automation and screenshot comparison is the exact use case that made me discover this bug. We want to use FF to generate screenshots of HTML files in a Git repo, to see if a commit introduced an unexpected rendering change.
Description
•