Bug 24675

Summary:	Kontact fails to start after dnf system-upgrade Mga6 -> Cauldron
Product:	Mageia	Reporter:	Ulrich Beckmann <bequimao.de>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	geiger.david68210, marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	Screenshot of Virt-Manager logs of # dnf system-upgrade

Description Ulrich Beckmann 2019-04-16 08:39:32 CEST

I tested a dnf system-upgrade on real hardware with KDE Plasma and Gnome on  2019-04-10 (3196 packages).

Kontact/Kmail crashes as follows:

[beq-mageia@mga7-clon2 ~]$ kontact
kontact: error while loading shared libraries: libsnappy.so.1: cannot open shared object file: No such file or directory
[beq-mageia@mga7-clon2 ~]$

A subsequent upgrade on 2019-04-11 did not change anything (357 Packages).

Version-Release number of selected component (if applicable):
# rpm -qa --last | grep snappy
lib64snappy1-1.1.7-2.mga7.x86_64              Wed 10 Apr 2019 15:23:23 CEST

# ls -l /usr/lib64/*snappy*
lrwxrwxrwx 1 root root    18 Apr 10 15:33 /usr/lib64/libsnappy.so.1 -> libsnappy.so.1.3.0
-rwxr-xr-x 1 root root 39296 Oct  1  2018 /usr/lib64/libsnappy.so.1.1.7*

Best regards
Ulrich

Comment 1 Ulrich Beckmann 2019-04-16 09:00:09 CEST

Created attachment 10940 [details]
Screenshot of Virt-Manager

Same error applies to virt-manager when starting a virtual machine (KVM/Qemu).

Comment 2 David GEIGER 2019-04-16 09:06:01 CEST

Very strange no problem here I can't reproduce with kontact.

$ kontact 
org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
kf5.kxmlgui: cannot find .rc file "kontactsummary_part.rc" for component "kontact"
No such XML file "/home/david/.local/share/kontact/default-.rc"
"https://dot.kde.org/rss.xml"
"https://www.linux.com/feeds/rss"
"https://planetkde.org/rss20.xml"
"https://store.kde.org/content.rdf"
"https://planetkde.org/pt-br/rss20.xml"
"https://planet.kde-espana.org/atom.xml"
$

CC: (none) => geiger.david68210

Comment 3 Ulrich Beckmann 2019-04-16 09:07:16 CEST

Created attachment 10941 [details]
logs of # dnf system-upgrade

I had to append the option --allowerasing to # dnf system-upgrade.
So far I did not spot any problem with erased packages.

Marja Van Waes 2019-04-17 07:41:27 CEST

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 4 Ulrich Beckmann 2019-04-29 21:51:07 CEST

It tested now a system-upgrade in a VM in order to reproduce the bug.

No sucess so far. Kontact/Kmail starts, the link libsnappy.so.1 points to the correct version no.

Known differences:

Now
# dnf system-upgrade download --releasever=7 --allowerasing

Before
# dnf system-upgrade download --releasever=cauldron --allowerasing

Software like virt-manager, qemu-kvm (it*s a guest) and others were not installed.

First try: I corrected the symlink. Everything now works fine. So any confirmation is still needed.

Ulrich

Comment 5 Ulrich Beckmann 2019-09-13 17:20:51 CEST

The bug was only reproducible in installations which were cloned from the same origin. Both tests and the origin are deleted now.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME