Bug 374221 - akregator does not start on MATE
Summary: akregator does not start on MATE
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-27 18:08 UTC by Laurent Bonnaud
Modified: 2017-04-10 15:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laurent Bonnaud 2016-12-27 18:08:47 UTC
Hi,

I usually use akregator along with plasma and it works quite well.

Currently I am temporarily using another desktop than plasma (MATE) and noticed than akregator does not run:

$ akregator
[libprotobuf FATAL google/protobuf/stubs/common.cc:61] This program requires version 3.0.0 of the Protocol Buffer runtime library, but the installed version is 2.6.1.  Please update your library.  If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library.  (Version verification failed in "/build/mir-SAnMsN/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc".)
terminate called after throwing an instance of 'google::protobuf::FatalException'
  what():  This program requires version 3.0.0 of the Protocol Buffer runtime library, but the installed version is 2.6.1.  Please update your library.  If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library.  (Version verification failed in "/build/mir-SAnMsN/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc".)
Aborted (core dumped)

This is strange because it is the exact same binary with the same libraries on the same Ubuntu system:

Package: akregator
Version: 4:16.12.0+p16.04+git20161221.1229-0
Comment 1 Laurent Bonnaud 2017-04-10 15:45:09 UTC
This bug does not exists in Kubuntu 17.04.
Since I do not know if it is reproducible elsewhere I am closing this report.