When quiting alsaplayer gtk interface from the "Exit" menu, I get the following: Erreur de segmentation That mean "segmentation eoor" in English. I don't get it when installing from the sources. Reproducible: Always Steps to Reproduce: 1. emerge alsaplayer 2. launch alsaplayer with "alsaplayer" 3. exit from the exit menu Actual Results: It quit, but I get "Erreur de segmentation". Expected Results: At the program just quit without the above error. I try to use directly ./configure or make in the ebuild, as well as to comment out my CFLAGS, CXXFLAGS and LDFLAGS in make.conf, but it didn't helped. It doesn't append when installing this software by hand from the svn or from 0.99.77 tarball with just ./configure, make and make install.
Created attachment 119690 [details] my emerge --info
Please, remove the gtk support (again). It's been fubared for ages (see Bug 103751, Bug 125479 and others) and I have no idea why the flag was reintroduced.
Maybe because users want it. This bug is not about why or not to have the gtk interface with alsaplayer. It is an use flag for it and an user that doesn't want it can emerge with USE=-gtk. This bug is about a segfault that doesn't appear when compiling by hand but appear only when compiling with portage. So it is a specific gentoo issue. When the fact at alsaplayer don't have a modern graphical interface is an upstream problem. And gtk-1.2 is supported on gentoo.
(In reply to comment #3) > Maybe because users want it. This bug is not about why or not to have the gtk > interface with alsaplayer. It is an use flag for it and an user that doesn't > want it can emerge with USE=-gtk. That's wonderful that users want it. Then the users should provide patches upstream to make gtk2 GUI usable, instead of the crappy gtk+-1 stuff. I can't reproduce this because the GUI crashes right at startup on unicode locales since gtk+-1 is FUBARed. Why are we providing known-to-be-screwed feature in the ebuild? </rant> Regardless the above rant, you should provide a backtrace if you want anything done about this bug. http://www.gentoo.org/proj/en/qa/backtraces.xml
By request. There are warnings when the package is emerged warning of crashes and recommending people not liking them use another audio player. Dominique, i do need a backtrace, and maybe also the output of emerge -v --info too. Does this occur when you have a file loaded, or can you just run alsaplayer and immediately exit to reproduce?
(In reply to comment #5) > By request. There are warnings when the package is emerged warning of crashes > and recommending people not liking them use another audio player. I'm afraid requests for features known to bomb out are not acceptable. Users who want such stuff can use EXTRA_ECONF and then they are on their own.
Created attachment 119741 [details] my emerge -v --info Here is my emerge -v --info. For the backtrace, I will make it, but you will have to wait until I get the time to reinstall world with the needed CFLAGS. I get this seg error no matter when I quit. I even try to remove the ~/.alsaplayer directory, start the player with "alsaplayer -i gtk" and exit with the menu and I get the same error. When playing a song, same error. With or without loaded playlist when not playing a song, same error.
(In reply to comment #7) > For the backtrace, I will make it, but you will > have to wait until I get the time to reinstall world with the needed CFLAGS. That's really an overkill; recompiling alsaplayer plus it's dependencies with those will do it.
'emerge -evp alsaplayer' give me 338 packages, so it will take some time. BTW. I fully agree when you said at users must provide patches to make the gtk2 interface usable. They can also provide patches for the new python bindings module that is fully usable and provide all the core functionality.
Created attachment 119843 [details] backtrace of the problem. I am sorry for the derangement. The backtrace showed me at the problem is not coming from the Alsaplayer but from a scope plugin that is not in portage. After removing this scope plugin from my system, alsaplayer is running fine. So, I guess at you can mark this bug as wont solve or whatever is appropriate. I joined the backtrace so at you can see it for yourself.
(In reply to comment #4) > (In reply to comment #3) >. I can't > reproduce this because the GUI crashes right at startup on unicode locales > since gtk+-1 is FUBARed. Are you sure at it come from your unicode locales. I also have unicode locales. Another source of troubles with gtk1 programs and modern systems is the transparency support. Does alsaplayer also crash when you start it with XLIB_SKIP_ARGB_VISUALS=1 alsaplayer
I am currently working with Madej from Poland on a new gtk2 interface. He is allready in the svn and will be includded in the next release. You can already use it with this ebuild: http://svnweb.tuxfamily.org/filedetails.php?repname=proaudio%20(proaudio)&path=%2Ftrunk%2Foverlays%2Fproaudio%2Fmedia-sound%2Falsaplayer%2Falsaplayer-9999.ebuild&rev=0&sc=0 Madej just send me a fix for the levelmeter scope for the gtk2 version. It was doing the same with transparency support in the gtk2 interface. So, it was a bug in AP. We are still working on thos gtk2 interface in order to provide nice working stuff. Madej is a very good programmer, so we can expect at some bugs will be found and fixed in the process. That was the good news of the day. You are free to try it and any bug report or suggestion directly to me or upstream will be welcomed.
Closing.
