Bug 1214907 - webkit2gtk3 update 2.38.6 -> 2.40.5 broke evolution all to pieces
Summary: webkit2gtk3 update 2.38.6 -> 2.40.5 broke evolution all to pieces
Status: RESOLVED DUPLICATE of bug 1214878
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Upgrade Problems (show other bugs)
Version: Leap 15.5
Hardware: x86-64 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-03 08:21 UTC by Mike Galbraith
Modified: 2023-09-03 09:15 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Galbraith 2023-09-03 08:21:26 UTC
I usually run as root (yeah yeah, I know;), with evolution set up to run as and in the home directory of an unprivileged user.  After this update to 2.40.5, when evolution is started, you get a banner "Something has gone wrong when displaying the message", which repeats as you move from message to message, so it's graveyard dead, all you can do is shut it down.

If manually started as that unprivileged user, things are a little better for a very loose definition of better - the thing doesn't moan, but also does not display message text, so is effectively just as dead.

Reverting to 2.38.6 and nailing it to the floor gets evolution working again.

FWIW (not much) I even built (steal packages from osc and rpmbuild locally in leap-15.5) everything required to get evolution+data-server upgraded to factory rev (3.48.4) in one of my VMs, and when that build-fest was over, shiny new 3.48 evolution was broken in the same way as stock 3.42 was.. so use locally built packages while waiting for hiccup to get resolved didn't work out, so I'm back to nailing the working 2.38.6 webkit2gtk3 to the floor.
Comment 1 hui 2023-09-03 09:15:20 UTC
dup

*** This bug has been marked as a duplicate of bug 1214878 ***