Bug #7771

Attempting to print hangs the Unsafe Browser

Added by kytv 2014-08-10 23:29:32 . Updated 2014-10-16 08:10:46 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_1.2
Start date:
2014-08-10
Due date:
% Done:

100%

Feature Branch:
bugfix/7771-disable-cups-in-unsafe-browser
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description

Hitting CTRL+P or going to File -> Print in the unsafe-browser will cause the browser window to hang for several minutes while attempting to reach CUPS. Of course, unsafe-browser can’t reach CUPS due to restrictions in ferm.

The soon-to-be-referenced branch solves this problem for me by disabling CUPS within unsafe-browser.

(I would have done this sooner but I just found it while working on the upcoming “I2P Browser”).

Subtasks

Related issues

Related to Tails - Bug #10395: Tor Browser is slow at printing in Jessie Rejected 2015-10-20

History

#1 Updated by kytv 2014-08-10 23:32:24

  • QA Check set to Ready for QA
  • Feature Branch set to kytv:bugfix/7771-disable-cups-in-unsafe-browser

My fix available at git://repo.or.cz/tails/kytv.git in the branch bugfix/7771-disable-cups-in-unsafe-browser

#2 Updated by intrigeri 2014-08-11 13:34:52

  • Subject changed from printing in unsafe-browser leads to browser hang to Attempting to print hangs the Unsafe Browser
  • Status changed from New to Confirmed
  • Assignee set to intrigeri
  • Target version set to Tails_1.1.1

#3 Updated by intrigeri 2014-08-11 13:47:50

  • Status changed from Confirmed to In Progress
  • Feature Branch changed from kytv:bugfix/7771-disable-cups-in-unsafe-browser to bugfix/7771-disable-cups-in-unsafe-browser

Rebased on top of the stable branch, since I’d like to see it merged for 1.1.1.

#4 Updated by intrigeri 2014-08-11 14:29:59

  • Assignee changed from intrigeri to kytv
  • QA Check changed from Ready for QA to Info Needed

Replied on tails-dev@.

#5 Updated by anonym 2014-09-02 05:12:48

  • Target version changed from Tails_1.1.1 to Tails_1.2

#6 Updated by kytv 2014-09-21 15:55:39

  • Assignee deleted (kytv)

Also written to tails-dev:

I set up a freshly installed virtual machine for testing, borrowing
“our” ferm configs. The goal was to see if Firefox attempts to contact
CUPS on port 631 even though it was disabled with the
print.postscript.cups.enabled configuration variable being set to false.

Results:

- Debian Wheezy’s Iceweasel: Fails

- Mozilla’s Firefox 24.7.0 ESR: Fails
- Mozilla’s Firefox 31: Pass

tl;dr:

They fixed the problem sometime between Firefox 24 and Firefox 31.

With testing I found that this regression was introduced into Tails with 4b6248d0e7a77e78ee23465a1a70c3fdccf3dc5e.

#7 Updated by intrigeri 2014-09-22 13:07:11

  • QA Check changed from Info Needed to Ready for QA

#8 Updated by anonym 2014-09-25 10:57:11

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

In Tails 1.1.2 with Iceweasel 24, I get just a 1-2 second delay without your fix, but with the fix it’s immediate. In an image built from feature/tor-browser-bundle, which uses Firefox 31, it takes minutes without your patch but it’s immediate with your fix. Great!

For 1.2 we’re gonna migrate to TBB (feature/tor-browser-bundle) and the unsafe-browser script has diverged so the current commit wouldn’t work. I’ve therefore adapted it appropriately and pushed it to that branch, see commit d4cbd24.

Thanks!

#9 Updated by anonym 2014-10-16 08:10:46

  • Status changed from Fix committed to Resolved

#10 Updated by intrigeri 2015-10-23 08:20:56

  • related to Bug #10395: Tor Browser is slow at printing in Jessie added