Bug 25475 - gPodder hangs after update of Python stack
Summary: gPodder hangs after update of Python stack
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Shlomi Fish
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-26 15:54 CEST by aguador
Modified: 2019-09-26 22:09 CEST (History)
1 user (show)

See Also:
Source RPM: gpodder-3.10.9-2.mga8.src.rpm
CVE:
Status comment:

Attachments
Output from launch of gpodder in terminal (10.27 KB, text/plain)
2019-09-26 15:55 CEST, aguador 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description aguador 2019-09-26 15:54:12 CEST 
Since updating the python stack on my Cauldron machine, gPodder hangs up after launching.

Updating python produced this error:
gpodder-3.10.9-1.mga8.noarch
 (debido a que no se satisfizo python(abi) == 3.7,
  debido a que falta python3dist(podcastparser))

However, gpodder-3.10.9-2 installed afterwards. I have also tried reinstalling this to no avail. The datafiles are not found and several errors are produced. See file with terminal output.
Comment 1 aguador 2019-09-26 15:55:29 CEST 
Created attachment 11290 [details]
Output from launch of gpodder in terminal
Comment 2 Jani Välimaa 2019-09-26 18:27:47 CEST 
Should be fixed in gpodder-3.10.9-3.mga8, please test.

CC: (none) => jani.valimaa

Comment 3 Lewis Smith 2019-09-26 19:58:48 CEST 
(In reply to Jani Välimaa from comment #2)
> Should be fixed in gpodder-3.10.9-3.mga8, please test.
Thank you Jani for replying so quickly.

@aguador : Indeed, please do try this new version, and report back.

Assigning this to Shlomi, for info, because he has 'gpodder'.

Assignee: bugsquad => shlomif

Comment 4 aguador 2019-09-26 22:09:26 CEST 
Yes, thank you Jani for a super fast fix.
Updated and functioning normally.
Closing bug report.

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