[mythtv] [mythtv-commits] Ticket #8512: Mythwelcome spawned frontend crashes when using internal web browser

[Michael PARKER]

> Mike,
> 
> Thanks for reporting back.  I'm going to go ahead and close 
> the ticket.  
> Since Otto said he was getting the crash with OpenJDK's IcedTeaPlugin 
> without using mythwelcome, mythwelcome doesn't seem to be a factor 
> here.  I do understand your concern, but at this point, it's 
> very much 
> more likely that the difference in behavior between 
> mythfrontend/mythbrowser run by mythwelcome and run at the 
> command line 
> is due to some other difference in your configuration.  For example, 
> with a different HOME specified, it's possible that only one of the 2 
> instances actually uses the IcedTeaPlugin (if the plugin is 
> installed in 
> the HOME).  Or it could be some other difference in the environments.
> 
> Futhermore, there's not really anything MythTV does to use 
> plugins--we 
> simply tell Qt's WebKit to enable them and then everything else about 
> them is Qt/WebKit.  So, I really think if there's a bug, it's 
> a Qt bug 
> or an OpenJDK bug.  I'm currently leaning toward it being a Qt 
> bug--simply because Adobe Flash 10.1 beta for GNU/Linux 
> x86_64 (possibly 
> also 32-bit) also crashes WebKit.  That said, it's possible 
> it's fixed 
> in a newer version of Qt (perhaps in the Qt 4.7 snapshot).
> 
> I'll also try to find some way that we can log a message 
> indicating what 
> plugins are enabled in webkit to help users diagnose issues like this.
> 
> Thanks,
> Mike

Mike,

OK - thanks for the explanation. Let me know if I can be of any help in debugging further.

Is there any way in which MythTV can warn users of potentially incompatible packages at installation
time? 

Some sort of rpm lookup that can produce user-directed "You've got XYZ installed that may cause
problems"-type warnings?

Otherwise, with OpenJDK the default of (at least) Fedora, we could be revisiting this thread
again... and again etc. 

Cheers,

Mike