Bug 24793 - flatpak Segmentation fault (core dumped) while installing
Summary: flatpak Segmentation fault (core dumped) while installing
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-09 01:42 CEST by Ezequiel Partida
Modified: 2019-09-23 16:27 CEST (History)
3 users (show)

See Also:
Source RPM: flatpak-1.0.8.1
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Ezequiel Partida 2019-05-09 01:42:59 CEST 
Description of problem:

I reinstalled my laptop with Mageia 7 fresh install since I changed my Hard drive.

Now everytime I want to install an app I get: 

Installing: org.freedesktop.Sdk/x86_64/18.08 from flathub
[##                  ] Downloading files: 756/30339 865.0 kB (216.2 kB/s)Segmentation fault (core dumped)

I had this problem before but it started working...

Version-Release number of selected component (if applicable):

flatpak 1.0.8.1


How reproducible:

flatpak -y install flathub com.spotify.Client

or

flatpak install flathub com.wps.Office

or any other application to be installed.

Regards
Comment 1 Marja Van Waes 2019-05-09 09:42:13 CEST 
Assigning to our registered flatpak maintainer.
CC'ing a recent submitter.

Source RPM: (none) => flatpak-1.0.8.1
Assignee: bugsquad => ngompa13
CC: (none) => marja11, shlomif

Comment 2 Neal Gompa 2019-06-17 01:03:55 CEST 
I've bumped up the flatpak stack to a supported version, and I can no longer reproduce this issue locally.

It's sitting in updates-testing for cauldron right now as part of a freeze move request: https://ml.mageia.org/l/arc/dev/2019-06/msg00126.html

Please give it a try.

Status: NEW => ASSIGNED

Comment 3 Morgan Leijström 2019-09-23 16:27:23 CEST 
No activity for long here, and i see we are at version 1.4.1 in mga7.

CC: (none) => fri
Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.