Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#3597 - When Muine is already started and a song is double clicked to play, it plays but an error is given.
Attached to Project:
Arch Linux
Opened by Luke Hoersten (lhoerste) - Wednesday, 07 December 2005, 19:57 GMT
Last edited by arjan timmerman (blaasvis) - Tuesday, 20 December 2005, 07:48 GMT
Opened by Luke Hoersten (lhoerste) - Wednesday, 07 December 2005, 19:57 GMT
Last edited by arjan timmerman (blaasvis) - Tuesday, 20 December 2005, 07:48 GMT
|
Detailsmuine-0.8.3-6
mono-1.1.10-2 When Muine is already started and a song is double clicked to play (in nautilus for example), it plays but a popup error is given: "The Application "muine" has quit unexpectedly. You can inform the developers of what happened to help them fix it. Or you can restart the application right now." Muine does not in fact quit and plays the song like it should, but its just annoying having to close this popup every time I want to play a song. |
This task depends upon
Closed by Jan de Groot (JGC)
Tuesday, 31 January 2006, 23:25 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with latest muine and gtk-sharp-2 and mono and whatever update more fixed it.
Tuesday, 31 January 2006, 23:25 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with latest muine and gtk-sharp-2 and mono and whatever update more fixed it.
Comment by Tobias Kieslich (tobias) -
Tuesday, 20 December 2005, 08:44 GMT
http://bugs.archlinux.org/task/3641#comments
Comment by Luke Hoersten (lhoerste) -
Sunday, 15 January 2006, 05:49 GMT
My confusion comes from the fact that other distros have it working fine. If the rapid development of mono is causing instabilities (which I can definately see why) in the packages then would freezing and stabalizing mono be an option?
Comment by Tobias Kieslich (tobias) -
Thursday, 26 January 2006, 00:10 GMT
even if this happens, I doubt it inherits from our previous mono problems and I think that's more of a gnome or upstream problem. Opinions?