The file jar:file:///usr/lib/seamonkey-2.0.4/chrome/messenger.jar!/content/messenger/am-newsblog.xul cannot be found. Please check the location and try again.

Bug #593571 reported by yamo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
seamonkey (Ubuntu)
Fix Released
Medium
Chris Coulson
Lucid
Fix Released
Medium
Chris Coulson

Bug Description

Binary package hint: seamonkey

Hi,
To see this bug, go in the mail window to RSS and click on "View settings for this account".

And the RSS feeds not work, with the same profile with Seamonkey 2.1a2pre there are new posts but not with Seamonkey 2.04 lucid.

$ dpkg -l | grep seamonkey
ii seamonkey 2.0.4+nobinonly-0ubuntu1 The Seamonkey Internet Suite
ii seamonkey-browser 2.0.4+nobinonly-0ubuntu1 Seamonkey Navigator (Internet browser) and C
ii seamonkey-chatzilla 2.0.4+nobinonly-0ubuntu1 Seamonkey Chatzilla IRC client
ii seamonkey-dbg 2.0.4+nobinonly-0ubuntu1 Debugging symbols for the Seamonkey Internet
ii seamonkey-gnome-support 2.0.4+nobinonly-0ubuntu1 Gnome Depends for the Seamonkey Internet Sui
ii seamonkey-mailnews 2.0.4+nobinonly-0ubuntu1 Seamonkey Mail & Newsgroups and Address Book

$ lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04

$ uname -a
Linux eeepc 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux

$ apt-cache policy seamonkey
seamonkey:
  Installé : 2.0.4+nobinonly-0ubuntu1
  Candidat : 2.0.4+nobinonly-0ubuntu1
 Table de version :
 *** 2.0.4+nobinonly-0ubuntu1 0
        500 http://fr.archive.ubuntu.com/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status

Tags: lucid
Revision history for this message
yamo (stephane-gregoire) wrote :

With official build from ftp.mozilla.org it's work :

getting ftp://ftp.mozilla.org/pub/seamonkey/releases/2.0.4/linux-i686/fr/seamonkey-2.0.4.tar.bz2 extract it to /tmp and after :

$ sudo chown root:root /tmp/seamonkey
$ sudo mv /tmp/seamonkey /tmp/seamonkey.2.0.4
$ sudo mv /tmp/seamonkey.2.0.4/ /usr/local/

and then launch
/usr/local/seamonkey.2.0.4/seamonkey https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/593571

Revision history for this message
yamo (stephane-gregoire) wrote :

I have the same bug on another Ubuntu PC which runs a 64 bit Ubuntu.

Revision history for this message
Micah Gersten (micahg) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided, I'm going to mark it as Triaged. Thanks for taking the time to make Ubuntu better! Please report any other issues you may find.

Changed in seamonkey (Ubuntu):
assignee: nobody → Micah Gersten (micahg)
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

bzr commit -m '* Fix LP: #593571 - searching for am-newsblog.xul in the wrong chrome package
  Install the newsblog.js XPCOM component
  - update debian/seamonkey-browser.install' --fixes 'lp:593571'
Committing to: /home/chr1s/src/seamonkey/seamonkey-2.0.dev/
modified debian/changelog
modified debian/seamonkey-browser.install
Committed revision 221.

This will be fixed in Maverick this afternoon

Changed in seamonkey (Ubuntu):
assignee: Micah Gersten (micahg) → Chris Coulson (chrisccoulson)
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package seamonkey - 2.0.6+build1+nobinonly-0ubuntu1

---------------
seamonkey (2.0.6+build1+nobinonly-0ubuntu1) maverick; urgency=low

  * New upstream release v2.0.6 (SEAMONKEY_2_0_6_BUILD1)
  * Fix LP: #593571 - searching for am-newsblog.xul in the wrong chrome package
    Install the newsblog.js XPCOM component
    - update debian/seamonkey-browser.install
  * Fix some Lintian warnings
    - update debian/control
    - add debian/README.source
 -- Chris Coulson <email address hidden> Wed, 14 Jul 2010 14:45:32 +0100

Changed in seamonkey (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,
When will it be fixed in Lucid?

In lucid we are still in version 2.0.4 and not in 2.0.5 : http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html#seamonkey2.0.5 (I didn't found a bug on that on launchpad).

Changed in seamonkey (Ubuntu Lucid):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Chris Coulson (chrisccoulson)
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Lucid has 2.0.5 now, sorry about that. I will try and fix this in Lucid for 2.0.6, but it might have to wait until 2.0.7. The candidate for 2.0.6 is already built in the staging PPA, and I don't really want to hog the build-daemons any more than i need to

Changed in seamonkey (Ubuntu Lucid):
milestone: none → lucid-updates
Changed in seamonkey (Ubuntu Lucid):
status: Triaged → Fix Committed
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

2.0.7 is now built with this fix in the ubuntu-mozilla-security PPA (ppa:ubuntu-mozilla-security/ppa). Please install and test it :)

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,

It's working on Ubuntu lucid with your PPA.

I've checked RSS Settings and I've subcribed to this bug RSS and this one : http://petrole.blog.lemonde.fr/feed/ .

Thanks a lot for your work.

Now I will use Ubuntu Seamonkey package instead of mozilla archive!

When bug #575160 will be fixed it will be perfect!

Revision history for this message
yamo (stephane-gregoire) wrote :

I've tried with i686 Linux I will try after with a 64 bit PC.

Revision history for this message
yamo (stephane-gregoire) wrote :

It also works on 64 bit linux.

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,
Today I had a crash when writing an email and apport doesn't want to report it.

Revision history for this message
Micah Gersten (micahg) wrote :

@yamo
apport does not have a way to file bugs from a PPA. Your best bet is probably trying apport-retrace locally, please file a new bug if you need help with this.

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,

I don't know how using apport-retrace and I had a crash when using it : bug #448158.

I reported a new bug on seamonkey : bug #/631398.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This is fixed in Lucid now

seamonkey (2.0.7+build1+nobinonly-0ubuntu0.10.04.1) lucid-security; urgency=low

  * New upstream release v2.0.7 (SEAMONKEY_2_0_7_BUILD1)

  * SECURITY UPDATES:
  * MFSA 2010-49: Miscellaneous memory safety hazards (rv:1.9.2.9/ 1.9.1.12)
    - CVE-2010-3169
  * MFSA 2010-50: Frameset integer overflow vulnerability
    - CVE-2010-2765
  * MFSA 2010-51: Dangling pointer vulnerability using DOM plugin array
    - CVE-2010-2767
  * MFSA 2010-52: Windows XP DLL loading vulnerability
    - CVE-2010-3131
  * MFSA 2010-53: Heap buffer overflow in nsTextFrameUtils::TransformText
    - CVE-2010-3166
  * MFSA 2010-54: Dangling pointer vulnerability in nsTreeSelection
    - CVE-2010-2760
  * MFSA 2010-55: XUL tree removal crash and remote code execution
    - CVE-2010-3168
  * MFSA 2010-56: Dangling pointer vulnerability in nsTreeContentView
    - CVE-2010-3167
  * MFSA 2010-57: Crash and remote code execution in normalizeDocument
    - CVE-2010-2766
  * MFSA 2010-58: Crash on Mac using fuzzed font in data: URL
    - CVE-2010-2770
  * MFSA 2010-60: XSS using SJOW scripted functio
    - CVE-2010-2763
  * MFSA 2010-61: UTF-7 XSS by overriding document charset using <object>
    type attribute
    - CVE-2010-2768
  * MFSA 2010-62: Copy-and-paste or drag-and-drop into designMode document
    allows XSS
    - CVE-2010-62
  * MFSA 2010-63: Information leak via XMLHttpRequest statusText
    - CVE-2010-63

  * Refresh patches for new upstream version
    - update debian/patches/seamonkey-fsh.patch
  * Fix LP: #593571 - searching for am-newsblog.xul in the wrong chrome package
    Install the newsblog.js XPCOM component
    - update debian/seamonkey-mailnews.install
 -- Chris Coulson <email address hidden> Thu, 09 Sep 2010 16:26:29 +0100

Changed in seamonkey (Ubuntu Lucid):
status: Fix Committed → Fix Released
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.