firefox-3.6.2pre from safe-upgrade fails to work in some ssl2 sites

Bug #517469 reported by Hilario J. Montoliu (hjmf)
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: firefox

Hi all,

Today's firefox "safe-upgrade" from aptitude in karmic has caused problems with firefox accessing ssl2 sites.

Steps to reproduce:
-------------------

* Try to access a ssl2 site, ie vmware-server 2 VI Web console

Error:
------

* The site times out.

I've reproduced the issue with two different vwmare servers; also I've got a timeout here in https://bugs.edge.launchpad.net (though I cannot confirm that the issue wasn't caused by the server.

Workarround:
------------

* Set security.enable_ssl2;true (as it defaults to false)

This seems to be a known issue with firefox-3.6 either in mozilla [1] and in vmware [2]

[1] http://support.mozilla.com/nl/forum/1/564314
[2] http://communities.vmware.com/thread/252218

System description
------------------

root@ulises-devel:~# lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

root@ulises-devel:~# apt-cache policy firefox
firefox:
  Installed: 3.6.2~hg20100205r33554+nobinonly-0ubuntu1~umd1~karmic
  Candidate: 3.6.2~hg20100205r33554+nobinonly-0ubuntu1~umd1~karmic
  Version table:
 *** 3.6.2~hg20100205r33554+nobinonly-0ubuntu1~umd1~karmic 0
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     3.5.7+nobinonly-0ubuntu0.9.10.1 0
        500 http://archive.ubuntu.com karmic-updates/main Packages
        500 http://security.ubuntu.com karmic-security/main Packages
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://archive.ubuntu.com karmic/main Packages

PS: I haven't been able to post this bug through "apport-bug firefox" because of error: "*Problem in Firefox* The problem cannot be reported: This is not a genuine Ubuntu package"

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

Not related to this issue, but just in case anyone wants to know it: the vmware remote console plugin extension doesn't work with ff3.6

I had to install another instance of firefox (3.5.7) in order to manage our vmware-servers

HTH

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

Just for the record; the problem persists with today's update:

root@ulises-devel:~# dpkg -l 'firefox*' | awk '/^ii/ {print $2" "$3}'
firefox 3.6.2~hg20100205r33566+nobinonly-0ubuntu1~umd1~karmic
firefox-branding 3.6.2~hg20100205r33566+nobinonly-0ubuntu1~umd1~karmic
firefox-gnome-support 3.6.2~hg20100205r33566+nobinonly-0ubuntu1~umd1~karmic

root@ulises-devel:~# LC_ALL=C apt-cache policy firefox
firefox:
  Installed: 3.6.2~hg20100205r33566+nobinonly-0ubuntu1~umd1~karmic
  Candidate: 3.6.2~hg20100205r33566+nobinonly-0ubuntu1~umd1~karmic
  Version table:
 *** 3.6.2~hg20100205r33566+nobinonly-0ubuntu1~umd1~karmic 0
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     3.5.7+nobinonly-0ubuntu0.9.10.1 0
        500 http://archive.ubuntu.com karmic-updates/main Packages
        500 http://security.ubuntu.com karmic-security/main Packages
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://archive.ubuntu.com karmic/main Packages

The timeout ends with:

The connection to the server was reset while the page was loading.

    * The site could be temporarily unavailable or too busy. Try again in a few
          moments.

    * If you are unable to load any pages, check your computer's network
          connection.

    * If your computer or network is protected by a firewall or proxy, make sure
          that Namoroka is permitted to access the Web.

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

Ups, I've forgotten to say that all the tests I've made are done with a fresh profile

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Presumably this problem was a one time occurrence and/or is no longer an issue? Can the bug report now be closed? If we do not hear from you the bug report will close itself in approximately 60 days time.

Thank you again for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in firefox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]

Changed in firefox (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.