Bug #15024
Tor Browser cannot print to file
100%
Description
This regression was introduced in Tails 3.3 when that imports Tor Browser 7.0.10-build2.
When printing to file it looks like it succeeds (dialog’s progress goes to 100%, no errors are shown) but the file is not created, and I can see this written to the journal:
Dec 08 13:49:50 amnesia firefox[12397]: /build/glib2.0-2.50.3/./gobject/gsignal.c:3492: signal name 'selection_changed' is invalid for instance '0x7dd7c1dc2740' of type 'MaiAtkType319'
Note:
- the above journal error is not emitted when printing in Tor Browser in Tails 3.2,
- but it is also emitted in Tails 3.3 when printing with a real printer too, and that works
Subtasks
Related issues
Related to Tails - |
Resolved | 2017-07-03 | |
Related to Tails - Bug #15336: "The persistent Tor Browser directory is usable" test suite scenario is fragile | In Progress | 2018-02-20 | |
Has duplicate Tails - |
Duplicate | 2017-11-17 | |
Has duplicate Tails - |
Duplicate | 2017-12-14 | |
Blocks Tails - |
Resolved | 2017-06-29 | |
Blocked by Tails - |
Resolved | 2018-01-18 |
History
#1 Updated by anonym 2017-12-08 14:55:16
- blocks
Feature #13244: Core work 2017Q4: Foundations Team added
#2 Updated by intrigeri 2017-12-08 16:43:56
Looks like Bug #13403 but worse. I think this is well tracked upstream already but I’ll double check.
#3 Updated by intrigeri 2017-12-08 16:44:07
- related to
Bug #13403: Can't print to file from Tor Browser when Tails session not in English added
#4 Updated by intrigeri 2017-12-08 18:03:29
Reproduced on Debian sid.
#5 Updated by intrigeri 2017-12-08 18:04:30
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 10
- Type of work changed from Code to Wait
That’s upstream bug https://trac.torproject.org/projects/tor/ticket/23970 which is on the Tor Browser team roadmap for December.
#6 Updated by intrigeri 2017-12-09 06:37:44
To do when closing this ticket
Revert commit:15ff263293c612f69138e03f7fb2f9aedd006e23
#7 Updated by intrigeri 2017-12-15 07:08:15
- has duplicate
Bug #14978: Print to file doesn't work in Tails 3.3 added
#8 Updated by intrigeri 2017-12-15 07:09:14
- has duplicate
Bug #15066: Printing to PDF with Tor Browser does not work anymore added
#9 Updated by intrigeri 2017-12-16 07:33:40
- % Done changed from 10 to 20
Fixed in the Tor Browser tor-browser-52.5.2esr-7.5-2 branch => asked when the fix will make it into a stable Tor Browser release.
#10 Updated by intrigeri 2017-12-19 10:53:28
- Assignee changed from intrigeri to anonym
This should be fixed in the next Tor Browser stable release. anonym, please confirm when you’ll import it :)
#11 Updated by intrigeri 2017-12-19 10:53:45
- % Done changed from 20 to 50
#12 Updated by intrigeri 2018-01-01 16:38:45
- blocked by deleted (
)Feature #13244: Core work 2017Q4: Foundations Team
#13 Updated by intrigeri 2018-01-01 16:38:49
- blocks
Feature #13245: Core work 2018Q1: Foundations Team added
#14 Updated by intrigeri 2018-01-19 10:53:13
- blocked by
Feature #15197: Upgrade to Tor Browser 7.5 added
#15 Updated by intrigeri 2018-01-19 10:53:31
- QA Check set to Ready for QA
#16 Updated by anonym 2018-01-22 13:52:26
- Feature Branch set to feature/15197-tor-browser-7.5
So, this works fine with Tor Browser 7.5, except that the default directory that is selected is tor-browser
(which presumably is the executable’s directory, i.e. /usr/local/lib/tor-browser
). I set a pref
(print.print_to_filename
) to make ~/Tor Browser
the default directory.
#17 Updated by anonym 2018-01-22 22:22:43
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
#18 Updated by anonym 2018-01-23 19:51:27
- Status changed from Fix committed to Resolved
#19 Updated by anonym 2018-02-20 14:40:44
- related to Bug #15336: "The persistent Tor Browser directory is usable" test suite scenario is fragile added