Two failures after a recent Fedora 20 update...

[Michael H. Warfield]

I'm kind of at a loss here.  I recently (yesterday, May 12) updated my
Fedora 20 laptop (originally a fresh install of F20 a couple of months
ago, no update from previous rev).  I had previously updated it on April
30, less that 2 weeks ago.  Now two critical applications, liferea and
evolution, are failing catastrophically in a very similar manner.

For reference - I run XFCE with the Enlightenment 0.16 Window Manager.
I run 6 virtual desktops, each of which are 4 screen viewports wide by 3
high.  Don't ask why, just understand they are need and used...  I don't
think that's a factor.  Gnome3 is not an option and it's abject lack of
performance (and viewports within desktops) would be prohibitive.

Both apps segfault and have OpenJDK messages just after the backtrace
and before the segfault message...

This is from evolution:

[mhw@canyon ~]$ evolution

(evolution:16883): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (evolution:16883): WARNING **: Failed to add service '[e-mail] (Remus)' ([e-mail]): No provider available for protocol 'imap4'
1   0x3da6712537 /lib64/libjavascriptcoregtk-3.0.so.0(WTFCrash+0x17) [0x3da6712537]
2   0x3da671a07c /lib64/libjavascriptcoregtk-3.0.so.0(_ZN3WTF10fastMallocEm+0x2ec) [0x3da671a07c]
3   0x3da674622b /lib64/libjavascriptcoregtk-3.0.so.0(_ZN3WTF10StringImpl6createEPKhj+0x2b) [0x3da674622b]
    :
28  0x31d2c155ea /lib64/libgobject-2.0.so.0() [0x31d2c155ea]
29  0x31d2c17814 /lib64/libgobject-2.0.so.0(g_object_new_valist+0x354) [0x31d2c17814]
30  0x31d2c17c11 /lib64/libgobject-2.0.so.0(g_object_new+0xf1) [0x31d2c17c11]
31  0x3dac61fcde /usr/lib64/evolution/3.10/libevolution-shell.so() [0x3dac61fcde]
java version "1.7.0_55"
OpenJDK Runtime Environment (fedora-2.4.7.0.fc20-x86_64 u55-b13)
OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
Segmentation fault (core dumped)
[mhw@canyon ~]$

I get very similar results from liferea.  Initial bitching seems to be
about Javascript and it ends with a java version, OpenJDK messages and a
segfault and core dump.

With Evolution, I got it to work for a while by removing all
of .local/share/evolution .cache/evolution and .config/evolution and
then restarting it.  After many many hours of downloading my information
from my imap servers (I have several hundred folders and multiple
sites), it was running again.  Next time I had to close it and restart,
it hurled chunks again.  Screwed...

Liferea has been similar.  It won't start with my old subscription list.
So, I eliminated .local/share/liferea .cache/liferea and .config/liferea
and and restarted.  But...  The moment I touch any subscription to look
at the articles, it crashes with an error very similar to what's above.
ForGetAboutIt when it comes to importing an old list.

None of Liferea, Evolution, or OpenJDK were updated between April 30 and
May 12.

A Bugzilla has been opened on the Liferea problem and the auto ABRT
report has been sent on Evolution.  I'm having to resort to an (up to
date) tower that's running Fedora 19 and afraid to update it to Fedora
20 as this point.

Anyone have any idea what the hell has gone wrong here and what I might
do to work around it?

Regards,
Mike

[Michael Schwendt]

On Tue, 13 May 2014 16:36:13 -0400, Michael H. Warfield wrote:
> I'm kind of at a loss here.  I recently (yesterday, May 12) updated my
> Fedora 20 laptop (originally a fresh install of F20 a couple of months
> ago, no update from previous rev).  I had previously updated it on April
> 30, less that 2 weeks ago.

yum history
yum history undo …
> I get very similar results from liferea.  Initial bitching seems to be
> about Javascript and it ends with a java version, OpenJDK messages and a
> segfault and core dump.

JavaScript != Java
> None of Liferea, Evolution, or OpenJDK were updated between April 30 and
> May 12.
>
> Anyone have any idea what the hell has gone wrong here and what I might
> do to work around it?

Try reverting the last yum update via yum history undo.
Then try to reproduce after repeating a yum update of individual
packages.

[Michael H. Warfield]

On Tue, 2014-05-13 at 22:56 +0200, Michael Schwendt wrote:
> On Tue, 13 May 2014 16:36:13 -0400, Michael H. Warfield wrote:
> > I'm kind of at a loss here.  I recently (yesterday, May 12) updated my
> > Fedora 20 laptop (originally a fresh install of F20 a couple of months
> > ago, no update from previous rev).  I had previously updated it on April
> > 30, less that 2 weeks ago.
> yum history
> yum history undo …
> > I get very similar results from liferea.  Initial bitching seems to be
> > about Javascript and it ends with a java version, OpenJDK messages and a
> > segfault and core dump.
> JavaScript != Java

Oh, I'm very aware of that fact.  The fact remains that both remain in
common in the backtrace and the resulting error output that hurled
chunks.  Just as there should be nothing in common between Evolution and
Liferea, there is something in common that seems to be causing this
problem.  Determining the common factor is the problem.  The fact that
neither seem to be updated seems to point to some deeper common factor,
which is far more disturbing.
> > None of Liferea, Evolution, or OpenJDK were updated between April 30 and
> > May 12.
> >
> > Anyone have any idea what the hell has gone wrong here and what I might
> > do to work around it?
> Try reverting the last yum update via yum history undo.
> Then try to reproduce after repeating a yum update of individual
> packages.

Excellent suggestion.  I'll proceed with that.

Many thanks!

Regards,
Mike

[Michael H. Warfield]

On Tue, 2014-05-13 at 20:04 -0400, Michael H. Warfield wrote:
> On Tue, 2014-05-13 at 22:56 +0200, Michael Schwendt wrote:
> > On Tue, 13 May 2014 16:36:13 -0400, Michael H. Warfield wrote:
> > > I'm kind of at a loss here.  I recently (yesterday, May 12) updated my
> > > Fedora 20 laptop (originally a fresh install of F20 a couple of months
> > > ago, no update from previous rev).  I had previously updated it on April
> > > 30, less that 2 weeks ago.
> > yum history
> > yum history undo …
> > > I get very similar results from liferea.  Initial bitching seems to be
> > > about Javascript and it ends with a java version, OpenJDK messages and a
> > > segfault and core dump.
> > JavaScript != Java
>
> Oh, I'm very aware of that fact.  The fact remains that both remain in
> common in the backtrace and the resulting error output that hurled
> chunks.  Just as there should be nothing in common between Evolution and
> Liferea, there is something in common that seems to be causing this
> problem.  Determining the common factor is the problem.  The fact that
> neither seem to be updated seems to point to some deeper common factor,
> which is far more disturbing.
> > > None of Liferea, Evolution, or OpenJDK were updated between April 30 and
> > > May 12.
> > >
> > > Anyone have any idea what the hell has gone wrong here and what I might
> > > do to work around it?
> > Try reverting the last yum update via yum history undo.
> > Then try to reproduce after repeating a yum update of individual
> > packages.
> Excellent suggestion.  I'll proceed with that.

Can't say this gives me a warm and fuzzy...

Transaction Summary
================================================================================
Remove           4 Packages (+7 Dependent packages)
Downgrade       39 Packages
Not available  416 Packages

416 packages not available.  Not good.  The revert history is a crap
shoot and could make things worse.  Trying it anyways.
> Many thanks!
> Regards,
> Mike

Regards,
Mike

[Michael H. Warfield]

On Tue, 2014-05-13 at 20:17 -0400, Michael H. Warfield wrote:
> On Tue, 2014-05-13 at 20:04 -0400, Michael H. Warfield wrote:
> > On Tue, 2014-05-13 at 22:56 +0200, Michael Schwendt wrote:
> > > On Tue, 13 May 2014 16:36:13 -0400, Michael H. Warfield wrote:
> > > > I'm kind of at a loss here.  I recently (yesterday, May 12) updated my
> > > > Fedora 20 laptop (originally a fresh install of F20 a couple of months
> > > > ago, no update from previous rev).  I had previously updated it on April
> > > > 30, less that 2 weeks ago.
> > > yum history
> > > yum history undo …
> > > > I get very similar results from liferea.  Initial bitching seems to be
> > > > about Javascript and it ends with a java version, OpenJDK messages and a
> > > > segfault and core dump.
> > > JavaScript != Java
> >
> > Oh, I'm very aware of that fact.  The fact remains that both remain in
> > common in the backtrace and the resulting error output that hurled
> > chunks.  Just as there should be nothing in common between Evolution and
> > Liferea, there is something in common that seems to be causing this
> > problem.  Determining the common factor is the problem.  The fact that
> > neither seem to be updated seems to point to some deeper common factor,
> > which is far more disturbing.
> > > > None of Liferea, Evolution, or OpenJDK were updated between April 30 and
> > > > May 12.
> > > >
> > > > Anyone have any idea what the hell has gone wrong here and what I might
> > > > do to work around it?
> > > Try reverting the last yum update via yum history undo.
> > > Then try to reproduce after repeating a yum update of individual
> > > packages.
> > Excellent suggestion.  I'll proceed with that.
> Can't say this gives me a warm and fuzzy...
> Transaction Summary
>
> Remove           4 Packages (+7 Dependent packages)
> Downgrade       39 Packages
> Not available  416 Packages
> 416 packages not available.  Not good.  The revert history is a crap
> shoot and could make things worse.  Trying it anyways.

The good news...  That got Evolution running and Liferea almost back to
normal but both are operational.

The BAD news is something in those 39 downgraded packages is AFU and
causing this problem.  Meaning, I can no longer upgrade till whatever it
is is fixed.  Damn...

A subsequent "update" is saying "90 packages to upgrade".  Damn.
Needless to say, that was a test run to which I said "HELL NO".

Regards,
Mike

[Michael H. Warfield]

On Tue, 2014-05-13 at 20:33 -0400, Michael H. Warfield wrote:
> On Tue, 2014-05-13 at 20:17 -0400, Michael H. Warfield wrote:
> > On Tue, 2014-05-13 at 20:04 -0400, Michael H. Warfield wrote:
> > > On Tue, 2014-05-13 at 22:56 +0200, Michael Schwendt wrote:
> > > > On Tue, 13 May 2014 16:36:13 -0400, Michael H. Warfield wrote:
> > > > > I'm kind of at a loss here.  I recently (yesterday, May 12) updated my
> > > > > Fedora 20 laptop (originally a fresh install of F20 a couple of months
> > > > > ago, no update from previous rev).  I had previously updated it on April
> > > > > 30, less that 2 weeks ago.
> > > > yum history
> > > > yum history undo …
> > > > > I get very similar results from liferea.  Initial bitching seems to be
> > > > > about Javascript and it ends with a java version, OpenJDK messages and a
> > > > > segfault and core dump.
> > > > JavaScript != Java
> > >
> > > Oh, I'm very aware of that fact.  The fact remains that both remain in
> > > common in the backtrace and the resulting error output that hurled
> > > chunks.  Just as there should be nothing in common between Evolution and
> > > Liferea, there is something in common that seems to be causing this
> > > problem.  Determining the common factor is the problem.  The fact that
> > > neither seem to be updated seems to point to some deeper common factor,
> > > which is far more disturbing.
> > > > > None of Liferea, Evolution, or OpenJDK were updated between April 30 and
> > > > > May 12.
> > > > >
> > > > > Anyone have any idea what the hell has gone wrong here and what I might
> > > > > do to work around it?
> > > > Try reverting the last yum update via yum history undo.
> > > > Then try to reproduce after repeating a yum update of individual
> > > > packages.
> > > Excellent suggestion.  I'll proceed with that.
> > Can't say this gives me a warm and fuzzy...
> > Transaction Summary
> >
> > Remove           4 Packages (+7 Dependent packages)
> > Downgrade       39 Packages
> > Not available  416 Packages
> > 416 packages not available.  Not good.  The revert history is a crap
> > shoot and could make things worse.  Trying it anyways.
>
> The good news...  That got Evolution running and Liferea almost back to
> normal but both are operational.
>
> The BAD news is something in those 39 downgraded packages is AFU and
> causing this problem.  Meaning, I can no longer upgrade till whatever it
> is is fixed.  Damn...
> A subsequent "update" is saying "90 packages to upgrade".  Damn.
> Needless to say, that was a test run to which I said "HELL NO".

It appears that I am, once again fully function on both applications
with both previous profiles prior to the recent update fuck up.  I still
have no idea, out of the 39 packages downgraded did the damage.  Makes
it a little tough to post buzilla ticket.  But, I'm a systems developer.
Why am I not surprised.

Many thanks to the feedback.  It was IMMESNSLY valuable and reaffirmed
my recourse to refferring to this list,

I thank you all...

Regards,
Mike

[Michael Schwendt]

On Tue, 13 May 2014 20:17:55 -0400, Michael H. Warfield wrote:
> Transaction Summary
>
> Remove           4 Packages (+7 Dependent packages)
> Downgrade       39 Packages
> Not available  416 Packages
>
> 416 packages not available.  Not good.  The revert history is a crap
> shoot and could make things worse.  Trying it anyways.

Unfortunately, that is a limitation of Fedora's update release habits,
which have changed again with the end of Fedora Extras some years ago.
In the repositories, a new stable update replaces the previous stable
update. Older update packages are only available if you use something
like yum-plugin-local.

So, typically "yum history undo …" works better in conjunction with
updates-testing repo enabled and frequent updates. In that case you can
revert to the last stable updates. "yum downgrade …", on the other hand,
would attempt downgrading to old packages from the "fedora" release repo.

[Michael H. Warfield]

Update...

On Tue, 2014-05-13 at 22:56 +0200, Michael Schwendt wrote:
> On Tue, 13 May 2014 16:36:13 -0400, Michael H. Warfield wrote:
> > I'm kind of at a loss here.  I recently (yesterday, May 12) updated my
> > Fedora 20 laptop (originally a fresh install of F20 a couple of months
> > ago, no update from previous rev).  I had previously updated it on April
> > 30, less that 2 weeks ago.
> yum history
> yum history undo …

Thanks to this bit of advice and some slow updates and testing of
selected packages, the problem was isolated to the gecko-mediaplayer
package from rpmfusion-free-updates repo.  Didn't come from the Fedora
repos at all.  Removing the package, I have a completely updated system.

Many thanks!

Regards,
Mike
> > I get very similar results from liferea.  Initial bitching seems to be
> > about Javascript and it ends with a java version, OpenJDK messages and a
> > segfault and core dump.
>
> JavaScript != Java
> > None of Liferea, Evolution, or OpenJDK were updated between April 30 and
> > May 12.
> >
> > Anyone have any idea what the hell has gone wrong here and what I might
> > do to work around it?
>
> Try reverting the last yum update via yum history undo.
> Then try to reproduce after repeating a yum update of individual
> packages.
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org