Segmentation Fault with an umlaut in a channels.conf with ISO-8859 encoding

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start gnome-mplayer
2. File -> TV -> Open Digital TV
3. Open playlist (F9)
4. Move your mouse pointer above an entry with an umlaut, "ö" in my case. See 
channels.conf .

What is the expected output? What do you see instead?
There should be a mouseover popup, like "dvb://arte". Once the mouse pointer 
reaches the guilty entry, gnome-mplayer crashes with a Segmentation Fault, see 
backtrace.txt .
The "ö" in that entry was displayed as a box with two diagonal lines in the 
playlist window.

What version of the product are you using? On what operating system?
gnome-mplayer-1.0.4 on  gentoo x86.
See depgraph.txt for versions of dependencies and useflags.txt for the useflags 
that are set (for example, "gnome" is not set, I'm using xfce4).
System info is in emerge-info.txt .

Please provide any additional information below.
- I wasn't sure if I should post this here or on bugs.gentoo.org. The latter 
seemed to be more about ebuild problems.
- The backtrace was made with gnome-mplayer compiled with CFLAGS="-01 
-march=core2 -ggdb", CXXFLAGS="${CFLAGS}" and portage's "splitdebug" feature 
set.
- The channels.conf is "ISO-8859 text" according to 'file'.
- I don't know what happened before gnome-mplayer-1.0.4 or gtk+-3
- Everything works fine if I remove the "ö" in line 15 of 
.mplayer/channels.conf
- I just tried to make a UTF-8 encoded channels.conf with an "ö". It works 
well, the "ö" is displayed properly and nothing crashes.

Original issue reported on code.google.com by michi.bu...@googlemail.com on 20 Sep 2011 at 5:01

Attachments:

• channels.conf
• backtrace.txt
• depgraph.txt
• useflags.txt
• emerge-info.txt

[GoogleCodeExporter]

Considering that utf8 is the preferred encoding on Unix, I think you have found 
your work around. 

Original comment by kdeko...@gmail.com on 20 Sep 2011 at 5:45

[GoogleCodeExporter]

I see, but I thought gnome-mplayer still shouldn't crash with a segmentation 
fault, so I reported it. When I found that solution the report was finished 
anyway...

Original comment by michi.bu...@googlemail.com on 20 Sep 2011 at 6:50