Bug 4454

Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Version: 1 => Cauldron
Assignee: bugsquad => shlomif
Source RPM: (none) => TiMidity++

(In reply to comment #0)
> If one wants to run timidity as daemon one has to edit /etc/rc.local and add to
> it something like : 
> ---------------
> timidity -Os -iAD
> ----------------
> it would be more user-friendly for beginners if one had just to activate a
> timidity service in MCC. 
> Such a service file exists on other distros like Debian (see attached file).
> 

Unfortunately, no such file was attached.

> It's just a minor thing, but sometimes polishing a distro is what makes the
> difference !

Well, I agree. I didn't realise Timidity could run as a daemon, and I've only adopted it. In any case, we may wish to also make it systemd-friendly (as Mageia 2 contains systemd), and I don't know how to write systemd-compatible services yet. I'll try to investigate, but this bug is not too high-priority for me.

Regards,

-- Shlomi Fish

> 
> Regards,

Status: NEW => ASSIGNED

Created attachment 1527 [details]
debian squeeze timidity service file

Finally, according to what is written here :
http://blog.flameeyes.eu/2007/11/problems-running-timidity-with-pulseaudio
it looks quite dangerous to run timidity as root. 
I checked that it is possible to start it in daemon mode as a plain user : it is. 
So maybe I should change my mind and not ask "timidity -Os -iAD" to be included in bootup services but rather in /etc/xdg/autostart through a .desktop file available for any type of desktop environment, so the user will just have to check it in his desktop environment autostart configuration dialog (at least, that should work for GNOME and XFCE, not sure though for KDE).

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

(In reply to comment #5)
> Hi,
> 
> This bug was filed against cauldron, but we do not have cauldron at the moment.
> 
> Please report whether this bug is still valid for Mageia 2.
> 
> Thanks :)
> 
> Cheers,
> marja

Valid in Mageia 2.

Version: Cauldron => 2
Keywords: NEEDINFO => (none)

Just one more information, I noticed that running "timidity -Os -iAD" as a plain user did not work (cf. https://bbs.archlinux.org/viewtopic.php?id=121189) : one as to run "timidity -Os -iA".
So this is the command that should be included in a timidity.desktop file in /etc/xdg/autostart (cf comment #4)

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and 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.

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.

-- 
The Mageia Bugsquad

still valid in Mageia 3

for the next time, don't forget to change the version then, as explained

Version: 2 => 3

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD

Still valid for Cauldron.

Resolution: OLD => (none)
Status: RESOLVED => REOPENED
Version: 3 => Cauldron

Still valid for Mageia 7

CC: (none) => dbitouze