Bug 13205

Summary:	TiMidity++ service is broken on Mageia 4, worked fine on Mageia 3
Product:	Mageia	Reporter:	Zombie Ryushu <zombie_ryushu>
Component:	RPM Packages	Assignee:	Shlomi Fish <shlomif>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	luigiwalser
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:	MGA4TOO MGA5TOO
Source RPM:	timidity	CVE:
Status comment:

Description Zombie Ryushu 2014-04-13 18:38:01 CEST

Timidity++ is completely broken on Mageia 4, and cannot start correctly as a system service. Under Mageia 3, Timidity could be loaded as a system service and other Midi Applications such as Rose Garden, and Totem could use Timidity++ as a resource. That isn't so on Mageia 4. For some reason, Timidity++ will hard lock the sound card such that no other applications can use it if it is loaded before Pulse Audio, and it will fail to load if it is loaded after Pulse Audio. This is major as it breaks all applications that rely on Midi.

Reproducible: 

Steps to Reproduce:

Manuel Hiebel 2014-04-14 21:23:05 CEST

Keywords: (none) => Triaged
Source RPM: TiMidity++ => timidity
Assignee: bugsquad => mageia

Comment 1 David Walser 2014-04-15 15:01:21 CEST

I don't know if it needs any upstream fixes from git for this, or if the setup-virmidi stuff added by Bero in omdv would help, but those are a couple of possible things to look at:
https://abf.rosalinux.ru/openmandriva/TiMidity++/commit/08e1b33f8e0b28a4b540123f8660f5e62712e2ed

Summary: TiMidity++ is completely broken on Mageia 4, worked fine on Mageia 3 => TiMidity++ service is broken on Mageia 4, worked fine on Mageia 3
CC: (none) => luigiwalser

Comment 2 Samuel Verschelde 2015-09-21 13:18:05 CEST

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Rémi Verschelde 2015-09-21 14:03:35 CEST

Assignee: mageia => bugsquad

Comment 3 Zombie Ryushu 2015-09-21 17:29:01 CEST

Still an issue in Mageia 5.

Version: 4 => Cauldron

Zombie Ryushu 2015-09-21 17:29:55 CEST

Whiteboard: (none) => MGA4TOO MGA5TOO

Comment 4 Samuel Verschelde 2016-10-17 13:37:32 CEST

Assigning to timidity++'s maintainer Shlomi Fish.

Assignee: bugsquad => shlomif

Comment 5 Aurelien Oudelet 2020-09-09 18:20:36 CEST

Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to RESOLVED:OLD

Keywords: Triaged => (none)
Resolution: (none) => OLD
Status: NEW => RESOLVED