[feisty] liferea crash with undefined symbol PR_NewMonitor

[Fabien Tassin]

Binary package hint: liferea

Liferea 1.2.10b-0ubuntu1 is crashing for some feeds.
Crash 100% reproducible.

Started from a shell, it says:
$ liferea
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
/usr/bin/liferea-bin: symbol lookup error: /usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: PR_NewMonitor
$

I can click on the feed and see its entries but it crashes when I click on any entry.
On restart, the corresponding feed lost its cache.

this is a freshly updated feisty.

liferea 1.2.10b-0ubuntu1
sun-java5-bin 1.5.0-11-1ubuntu1
firefox 2.0.0.3+1-0ubuntu1

[Emilio Pozuelo Monfort (pochu)]

Hi, can you please report a full crash? That would help us a lot.

[Fabien Tassin (fta)]

Sorry, no crash info from liferea in /var/crash, no core dumped anywhere.
The debug option of liferea does not produce anything relevant other than what I've already said.

This is an i386 install.

Just tried on another box (feisty amd64), same problem except that it only seems to die on entries containing embeded application/x-shockwave-flash objects.

[Emilio Pozuelo Monfort (pochu)]

Looks like a java issue. Matthias, can you confirm it?

Fabien, do you have sun-java5-plugin installed? If not, can you install it and try again?

[Emilio Pozuelo Monfort (pochu)]

Sorry, sun-java5-bin should be enough.

[Emilio Pozuelo Monfort (pochu)]

You can also try sun-java6-bin, it may fix it.

[Emilio Pozuelo Monfort (pochu)]

Sorry for the spam :)

If you try sun-java6-bin, you should have to run:
update-alternatives --config java
before running liferea.

[Fabien Tassin (fta)]

regarding sun-java5-plugin, on amd64, obviously, I don't have it as there's no such thing (same thing for java6). On i386, I have sun-java5-{bin,jre,plugin} 1.5.0-11-1ubuntu1 installed. I don't think the plugin package is relevant to my problem as it's -bin that is used.

BTW, I also have ia32-sun-java5-bin installed (only on amd64).

[Fabien Tassin (fta)]

try this podcast http://radiofrance-podcast.net/podcast/rss_16277.xml

it dies in liferea 1.2.* (feisty) while it was okay in 1.0.* (edgy).

[Emilio Pozuelo Monfort (pochu)]

Fabien: Can you try with sun-java6-bin in your i386 box? If you can, run "update-alternatives --config java" before launching liferea.

This problem may have already been fixed.

[Fabien Tassin (fta)]

root@xx:~ # update-alternatives --config java

There are 4 alternatives which provide `java'.

  Selection Alternative
-----------------------------------------------
          1 /usr/lib/jvm/java-1.5.0-sun/jre/bin/java
          2 /usr/bin/gij-wrapper-4.1
*+ 3 /usr/lib/jvm/java-gcj/jre/bin/java
          4 /usr/lib/jvm/java-6-sun/jre/bin/java

Press enter to keep the default[*], or type selection number: 4
Using `/usr/lib/jvm/java-6-sun/jre/bin/java' to provide `java'.

Restart of liferea, same issue:
/usr/bin/liferea-bin: symbol lookup error: /usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: PR_NewMonitor

Now, if I restart firefox:
/usr/bin/liferea-bin: symbol lookup error: /usr/lib/jvm/java-6-sun-1.6.0.00/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: PR_NewMonitor

so it may be a problem with firefox...
I have firefox 2.0.0.3+1-0ubuntu1.

[Emilio Pozuelo Monfort (pochu)]

Fabien, does the 1.2.10c release fix your issues?

[Fabien Tassin (fta)]

Emilio,

sorry, no change:
/usr/bin/liferea-bin: symbol lookup error: /usr/lib/jvm/java-6-sun-1.6.0.00/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: PR_NewMonitor

liferea 1.2.10c-0ubuntu1
firefox 2.0.0.3+1-0ubuntu2
sun-java6 6-00-2ubuntu2

Did you try the feed I've given in comment #8 ? does it work for you ? for me, I crashes in 3 completly different feisty boxes.

[Emilio Pozuelo Monfort (pochu)]

Yeah, I tried it, and it worked fine.

I've tried again, launching liferea from the terminal, and it works, but I see this output:

emilio@kiko:~$ liferea
GTK Accessibility Module initialized
LoadPlugin: failed to initialize shared library /usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/plugin/i386/ns7/libjavaplugin_oji.so [/usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: _ZTVN10__cxxabiv121__vmi_class_type_infoE]

But does not crash here.

[Emilio Pozuelo Monfort (pochu)]

Does not happen anymore with 1.2.13.

[Fabien Tassin (fta)]

hmm, will 1.2.13 be in Ubuntu any time soon ?
Will it be in Feisty or Gutsy ?

[Emilio Pozuelo Monfort (pochu)]

It should be in Gutsy really soon!

[Fabien Tassin (fta)]

hmm, sorry but :

$ liferea -v
liferea 1.2.13
$ liferea
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
/usr/bin/liferea-bin: symbol lookup error: /usr/lib/jvm/java-6-sun-1.6.0.00/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: PR_NewMonitor

this is a fresh gutsy box.

[Emilio Pozuelo Monfort (pochu)]

Does that happen with the same feed you told me?
http://radiofrance-podcast.net/podcast/rss_16277.xml

I've tried with it, and I can't reproduce this anymore.

If you're trying with another feed, let me know which one it is.

Thanks
Emilio

[Fabien Tassin (fta)]

Yes. From that site, all podcasts produce the PR_NewMonitor issue.
I also have that with a dozen other feeds from very different sources.

Here is another one http://feeds.feedburner.com/CommeCaDuJapon

[Emilio Pozuelo Monfort (pochu)]

> Here is another one http://feeds.feedburner.com/CommeCaDuJapon

I can't reproduce it with that, though I could with the other in the past.

Can you try with a clean profile?

Also, can you run liferea under gdb to get a backtrace? You should
launch liferea with:

"LD_LIBRARY_PATH=/usr/lib/firefox gdb liferea-bin"

Look at https://wiki.ubuntu.com/Backtrace to get the backtrace.

Thanks
Emilio

[Fabien Tassin (fta)]

See Bug #112384 https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/112384/comments/3

(bug disapeared after a rebuild without firefox-dev)

here is the relevant part of configure for that build:

checking pkg-config is at least version 0.9.0... yes
checking for LIBNOTIFY... yes
checking for LUA50... yes
checking for LUA51... no
checking for XULRUNNER... no
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking for GTKHTML2... yes
checking for MOZILLA... no
mozilla: no
checking for MOZILLA... no
firefox: no
checking for MOZILLA... no
seamonkey: no

====
config.log :

configure:24281: checking for MOZILLA
configure:24289: $PKG_CONFIG --exists --print-errors "$gecko_provider-gtkmozembed"
Package mozilla-gtkmozembed was not found in the pkg-config search path.
Perhaps you should add the directory containing `mozilla-gtkmozembed.pc'
to the PKG_CONFIG_PATH environment variable
No package 'mozilla-gtkmozembed' found
configure:24292: $? = 1
configure:24307: $PKG_CONFIG --exists --print-errors "$gecko_provider-gtkmozembed"
Package mozilla-gtkmozembed was not found in the pkg-config search path.
Perhaps you should add the directory containing `mozilla-gtkmozembed.pc'
to the PKG_CONFIG_PATH environment variable
No package 'mozilla-gtkmozembed' found
configure:24310: $? = 1
No package 'mozilla-gtkmozembed' found
configure:24338: result: no
configure:24350: result: mozilla: no
configure:24357: checking for MOZILLA
configure:24365: $PKG_CONFIG --exists --print-errors "$gecko_provider-gtkmozembed"
Package nspr was not found in the pkg-config search path.
Perhaps you should add the directory containing `nspr.pc'
to the PKG_CONFIG_PATH environment variable
Package 'nspr', required by 'XPCOM', not found
configure:24368: $? = 1
configure:24383: $PKG_CONFIG --exists --print-errors "$gecko_provider-gtkmozembed"
Package nspr was not found in the pkg-config search path.
Perhaps you should add the directory containing `nspr.pc'
to the PKG_CONFIG_PATH environment variable
Package 'nspr', required by 'XPCOM', not found
configure:24386: $? = 1
Package nspr was not found in the pkg-config search path.
Perhaps you should add the directory containing `nspr.pc'
to the PKG_CONFIG_PATH environment variable
Package 'nspr', required by 'XPCOM', not found
configure:24414: result: no
configure:24426: result: firefox: no
configure:24433: checking for MOZILLA
configure:24441: $PKG_CONFIG --exists --print-errors "$gecko_provider-gtkmozembed"
Package seamonkey-gtkmozembed was not found in the pkg-config search path.
Perhaps you should add the directory containing `seamonkey-gtkmozembed.pc'
to the PKG_CONFIG_PATH environment variable
No package 'seamonkey-gtkmozembed' found
configure:24444: $? = 1
configure:24459: $PKG_CONFIG --exists --print-errors "$gecko_provider-gtkmozembed"
Package seamonkey-gtkmozembed was not found in the pkg-config search path.
Perhaps you should add the directory containing `seamonkey-gtkmozembed.pc'
to the PKG_CONFIG_PATH environment variable
No package 'seamonkey-gtkmozembed' found
configure:24462: $? = 1
No package 'seamonkey-gtkmozem...

[Emilio Pozuelo Monfort (pochu)]

Hi Fabien

I think it doesn't find the mozilla engine because it now needs libnspr4-dev, due to a change in firefox. I've uploaded the debs to http://emilio.pozuelo.org/deb/ , just in case you want to test them.

Maybe I should build also the gtkhtml engine to test whether this only happens with the mozilla engine. (and even I can build the xulrunner engine).

Regards
Emilio

[Fabien Tassin (fta)]

Emilio,

I've removed my own debs, installed yours, the core dump on startup is gone but PR_NewMonitor symbol is still missing and makes liferea die for some feeds as before.

Gdb doesn't help much:

(no debugging symbols found)
[Thread -1337984112 (LWP 29980) exited]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
(no debugging symbols found)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
(no debugging symbols found)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
(no debugging symbols found)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
(no debugging symbols found)
/usr/bin/liferea-bin: symbol lookup error: /usr/lib/jvm/java-6-sun-1.6.0.00/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: PR_NewMonitor

Program exited with code 0177.
(gdb)

[Emilio Pozuelo Monfort (pochu)]

Fabien:

Where you able to reproduce it with a clean profile? I've just remembered I cleaned my profile some time ago, so that might be the reason I'm no longer experiencing this.

e.g. do a "mv ~/.liferea_1.2 ~/.liferea_1.2_backup", so you don't lose your data (or you can also create a different user, and try there, which might be better).

[Fabien Tassin (fta)]

Yes, I did. I moved out my profile, readded one of the feeds and no change. liferea still aborts with the same missing symbol.
(it's an abort, not a crash)

firefox seems to be moving everyday in gutsy (it is not upgradable for me at the moment) so I'll wait a few days until it stabilizes. In the meantime, I'll use my own debs compiled with gtkhtml2 only.

I'll update the case when I'll have something new.
Thanks for your patience :)

[Fabien Tassin (fta)]

same issue with liferea 1.2.14-0ubuntu1.

I only have mozilla as internal viewer. Could you build gtkhtml2 too next time ?
Thanks.

[Emilio Pozuelo Monfort (pochu)]

I can build it and upload to my server, so you can test it. However, I won't enable it for the official repository, since it's really buggy.

[Emilio Pozuelo Monfort (pochu)]

slomo> pochu: with gtkhtml no java would be used at all

So this is...

slomo> either java or firefox
slomo> both ugly and huge pieces of software... no idea which one is at fault here ;)

So I'm adding firefox to the bug report. Let's see what's the Mozilla people's input!

[Emilio Pozuelo Monfort (pochu)]

Steps to reproduce:

Launch liferea from the terminal (because it might not crash for some people):
$ liferea

Add the following feeds:
http://radiofrance-podcast.net/podcast/rss_16277.xml
http://feeds.feedburner.com/CommeCaDuJapon

Go and view the items in those feeds. Then Liferea should either crash or print an error in the terminal.

I should also say that I can't reproduce it in gutsy (not sure in feisty), though I could some time ago in Feisty. I've noticed that I don't have sun-java-* installed, so I've installed it, and still can't reproduce it.

[Fabien Tassin (fta)]

Try this feed http://trains-idf.net/feed/atom/
1st entry produces the PR_NewMonitor error.

using a conversion filter, I've removed (commented out) all <embed> tags in this feed, it worked.

Those <embed> objects are regular dailymotion application/x-shockwave-flash stuff.
This 1st entry is fine in firefox.

Does that ring a bell ?

[Emilio Pozuelo Monfort (pochu)]

I've been talking about this bug with Alexander Sack (the Mozilla maintainer), and it seems that the symbol is there.

As asked by him, can you run the following command and print here the output? (in gutsy)

"ldd /usr/lib/liferea/libli* | grep nspr"

Cheers
Emilio

[Fabien Tassin (fta)]

$ ldd /usr/lib/liferea/libli* | grep nspr
        libnspr4.so.0d => /usr/lib/libnspr4.so.0d (0xb765c000)
$ ls -l /usr/lib/libnspr*
-rw-r--r-- 1 root root 197904 2007-04-03 17:44 /usr/lib/libnspr4.so
-rw-r--r-- 1 root root 193772 2007-05-02 21:58 /usr/lib/libnspr4.so.0d
$ dlocate /usr/lib/libnspr4.so
libnspr4-0d: /usr/lib/libnspr4.so.0d
libnspr4: /usr/lib/libnspr4.so
$ apt-cache show libnspr4-0d
Package: libnspr4-0d
Priority: optional
Section: libs
Installed-Size: 300
Maintainer: Ubuntu Core Developers <email address hidden>
Original-Maintainer: Maintainers of Mozilla-related packages <email address hidden>
Architecture: i386
Source: nspr
Version: 4.6.6-3
Depends: libc6 (>= 2.5-5)
Filename: pool/main/n/nspr/libnspr4-0d_4.6.6-3_i386.deb
Size: 114376
...

[Emilio Pozuelo Monfort (pochu)]

Bug in Gentoo bug tracker: http://bugs.gentoo.org/show_bug.cgi?id=152255

[Fabien Tassin (fta)]

Emilio,

I just fixed my issue !

I tried to re-compile liferea myself to see if a debug version could be built.
To do so, I've had to (re)install firefox-dev (2.0.0.3+3-0ubuntu3) which wanted to remove gaim, libnspr-dev, libnspr4 and libnss3
and also install libnspr4-dev (4.6.6-3) + libnss3-dev (3.11.5-3). I did just that.

While compiling, I suddenly had an idea. With libnspr4 and libnss3 gone, I thought that could make a difference.
I've edited one of my faulty feed prefs to remove the filter (that get rid of flash objects), then I've restarted both liferea and firefox.
It worked ! So no more need for my own liferea debs or for my filters. Flash is now okay. Everything looks normal. Good.

Maybe liferea should add a Conflict on libnspr4.

There's a new message now but it's not fatal:
LoadPlugin: failed to initialize shared library /usr/lib/jvm/java-6-sun-1.6.0.00/jre/plugin/i386/ns7/libjavaplugin_oji.so [/usr/lib/jvm/java-6-sun-1.6.0.00/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: _ZTVN10__cxxabiv121__vmi_class_type_infoE]

[Emilio Pozuelo Monfort (pochu)]

Fabien:

Does it happen again if you install libnspr4?

[Fabien Tassin (fta)]

There's a conflict between libnspr4 and libnspr4-dev as the later comes from libnspr4-0d, not libnspr4.

The following packages will be REMOVED:
  firefox-dev libnspr4-dev libnss3-dev
The following NEW packages will be installed:
  libnspr4

That's a real mess. One is from mozilla, the other is customized by firefox. The two are clearly not exchangeable without side effects so no reason to pretend by sharing lib names, include files and package names. That's just confusing and source of problems difficult to troubleshoot (like this one).

[Emilio Pozuelo Monfort (pochu)]

You don't need the -dev libraries, do you? ;)

[John Vivirito (gnomefreak)]

Fabien that is not a liferea issue. that is nss and nspr builds. I will see what can be done about it sometime this week.

[John Vivirito (gnomefreak)]

You only need the -dev packages to build/compile it. so you will only run into that if you build it. I havent gottten up with Alexander yet but will today/tomorrow on that.

[John Vivirito (gnomefreak)]

The nss and nspr issue was fixed in gutsy, now it shouldnt ask you to remove one when installing the other. Is this bug still shown in firefox if so please provide a step by step instructions on how to reproduce this in firefox.

[Emilio Pozuelo Monfort (pochu)]

John,

This crash has never happened in Firefox, but it's affecting it, since the crash is in a symbol provided by libnspr.

Fabien, is it still crashing for you with Gutsy up-to-date?
I've tried it, but I can't reproduce it with 3 feeds that should make liferea crash.

[John Vivirito (gnomefreak)]

Than shouldnt we file it against nspr or libnspr? If you ask me you have more than one issue on this bug report. you have nss and nspr conflict and liferea crash they should be separate bug reports.

[Emilio Pozuelo Monfort (pochu)]

John,

I added firefox since when this bug was created, libnspr was created by the firefox source package.
I've added nspr now too, since now liferea depends on libnspr4-0d, which has a different source package than firefox.

Regarding the libnspr conflict, I don't think this bug is about it. This is about a liferea crash, though we might have talked about it in order to try to reproduce it / solve the liferea crash. But there's no conflict anymore, since libnspr-4 isn't built anymore.

So feel free to close the firefox task, if you think this bug doesn't affect firefox anymore.

[John Vivirito (gnomefreak)]

We may reopen at a later time but since it only affects nspr and liferea i dont see any reason to leave firefox task open.

[Fabien Tassin (fta)]

not a java issue

[Fabien Tassin (fta)]

fixed for a while, was a transiant libnspr issue.

[Fabien Tassin (fta)]

fixed by a rebuild of liferea using proper libnspr a while ago

[Ingo Planz (planz)]

Gutsy Beta i386 still has the bug. (liferea 1.4.2-0ubuntu1)

[Burhan Khalid (burhankhalid)]

Just wanted to add that on a default clean install of Gutsy, I am facing the same issue with Miro.

TIMING feed update for: http://revision3.com/diggnation/feed/quicktime-large too slow (0.428 secs)
TIMING timeout (Save database) too slow (0.570 secs)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
/usr/bin/python2.5: symbol lookup error: /usr/lib/jvm/java-6-sun-1.6.0.03/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: PR_NewMonitor

[Emilio Pozuelo Monfort (pochu)]

Burhan, is it reproducible for you? If so, which what feed?

I can't reproduce it here, with any feed posted on this report, including http://revision3.com/diggnation/feed/quicktime-large

[Emilio Pozuelo Monfort (pochu)]

Reopening, as some people still has this.

[Emilio Pozuelo Monfort (pochu)]

What architecture have those of you who can reproduce this?

This link may be useful to reproduce it: http://tweakers.net/feeds/mixed.xml

Also, I don't think this is related to Liferea at all, but since it affects it (indirectly), I'll leave this opened.

[Leon van der Ree (lvanderree)]

I am running on 64bit, with java1.4 because there is no other 64bit mozilla-java-plugin (I saw java mentioned in the debug output.)

[Alexander Sack (asac)]

On Tue, Oct 16, 2007 at 10:16:15PM -0000, leon van der Ree wrote:
> I am running on 64bit, with java1.4 because there is no other 64bit
> mozilla-java-plugin (I saw java mentioned in the debug output.)
>

we have now icedtea-java7 in gutsy.

 - Alexander

[Leon van der Ree (lvanderree)]

Thanks did not knew that. (actually never heard of it either)

I removed all sun java part (from 4 to 6) and now have only installed icedtea-java7 en guess what, liferea does not seem to crash anymore on the sites I mentioned...

[kamuz (kamuz2000)]

I installed Liferea on Gutsy (my OS is an upgrade from Feisty) and i got the PR_NewMonitor error with some feeds. So after i found out which java alternative was the one affecting the plugin for liferea which is

 update-alternatives --config iceape-javaplugin.so

I noticed my error was fixed when choosing Java 1.5 and i said "hey, lets try java 1.7(icedtea)" and it worked too, but then i came back to 1.6 just to reproduce the error and it was working! even if 1.6 was the "default" when i had problems.

I have no idea what happened but it works now. Still i have no clue what update-alternatives did... hope this info helps in squashing the bug.

[Will Guaraldi Kahn-Greene (willkahngreene)]

We've had user reporting issues with both Feisty and Gutsy where Miro crashes with the PR_NewMonitor undefined symbol error if the user has either sun-java6-plugin or sun-java5-plugin installed.

We've heard accounts of this happening with the packages we've been building as well as the 0.9.8 package that's in the Gutsy universe repository.

No one has mentioned having the problem with icedtea-java7-plugin yet.

The problem seems intermittent and I haven't seen any pattern related to system updates, reboots, or other usage except if sun-java5-plugin and sun-java6-plugin are both removed.

Figured I'd state everything I knew about the issue here here so that it's centralized.

[Scott Lewin (sclewin)]

I have been having this problem with Miro, I installed the icedtea-java7 as requested (Don't have a clue what it is :) ) and the problem, for the moment, seems to have gone away; Miro did not crash. I will report back if Miro crashed again.

[Mackenzie Morgan (maco.m)]

Is it *just* the icedtea plugin that's needed by liferea? I can't make icedtea my default Java because it's not fully Sun-compatible yet, and I have to write a lot of Java for class. Just changing the plugin (and using the Sun one for java compiling and running plain apps, not applets) would be fine, but would that work? If it needs to have the regular Java JRE changed to icedtea, then is there a way to make liferea use the icedtea one and have everything else use the Sun one?

[Emilio Pozuelo Monfort (pochu)]

Perhaps you can configure icedtea to be the default, and use Eclipse for writing your java classes? In Eclipse you can set the default compiler, so then you will have all the system using icedtea, but your classes being compiled by sun-java. Would that work?

Regarding the bug report, It's clear it isn't Liferea or Miro's fault, but Java, right? I won't close Liferea's task though, so I don't forget about this...

[Mackenzie Morgan (maco.m)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm vim user :-/ My software engineering teacher is all "bah! vi is
bad! use emacs!" and most of the rest of the class swears by BlueJ (like
IDLE for Java). Maybe I can make icedtea the default and alias a
nickname for java.

Emilio Pozuelo Monfort wrote:
> Perhaps you can configure icedtea to be the default, and use Eclipse for
> writing your java classes? In Eclipse you can set the default compiler,
> so then you will have all the system using icedtea, but your classes
> being compiled by sun-java. Would that work?
>
> Regarding the bug report, It's clear it isn't Liferea or Miro's fault,
> but Java, right? I won't close Liferea's task though, so I don't forget
> about this...
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHO9yaojm3DbyNMmkRAsJ2AKCzSPWtemYfHYKS7EG7TjdC6JcNIwCggcdU
ktVaIPW0SDR3ZDj2XeFHoXE=
=9/P0
-----END PGP SIGNATURE-----

[Emilio Pozuelo Monfort (pochu)]

Reconsidering my decision of not closing liferea's task...

[Andres Mujica (andres.mujica)]

Confirmed in miro.

Also the icedtea workaround seems to work, in fact you can go back to sun6 as default java plugin (miro remembers the icedtea ubication, or something like that)

[Andres Mujica (andres.mujica)]

forgot the ubuntuforum's thread

http://ubuntuforums.org/showthread.php?t=588617

[Bryce Harrington (bryce)]

This was a bug in or related to sun-java6-plugin. In any case seems to have long since been fixed so I think we can close this bug report.