Using gxine from the command line with filenames encoded in UTF-8 I get the following output: (gxine:11823): Gtk-CRITICAL **: gtk_window_set_default_icon: assertion `GDK_IS_PIXBUF (icon)' failed Gtk-Message: The filename "datah\303\244r\303\266ily.prproj" couldn't be converted to UTF-8. (try setting the environment variable G_FILENAME_ENCODING): Invalid byte sequence in conversion input Gtk-Message: The filename "\303\244mp\303\244ri" couldn't be converted to UTF-8. (try setting the environment variable G_FILENAME_ENCODING): Invalid byte sequence in conversion input Gtk-Message: The filename "\303\244\303\244net" couldn't be converted to UTF-8. (try setting the environment variable G_FILENAME_ENCODING): Invalid byte sequence in conversion input Gtk-Message: The filename "ven\303\244j\303\244.txt" couldn't be converted to UTF-8. (try setting the environment variable G_FILENAME_ENCODING): Invalid byte sequence in conversion input The file names which have utf-8 characters do not show up in the GTK file chooser. After setting G_FILENAME_ENCODING in my environment no errors are reported on the command line and the files are shown in the file chooser. Reproducible: Always Steps to Reproduce: 1. start gxine and select File --> Open 2. go to a directory containing files which have utf-8 characters in their names betelgeuse@pena ~/BattleStar Galactica $ emerge info Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12-gentoo-r7 i686) ================================================================= System uname: 2.6.12-gentoo-r7 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.12.0_pre3 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.4 [enabled] dev-lang/python: 2.4.1-r1 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=pentium4 -pipe -mfpmath=sse -ffast-math -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/init.d /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -pipe -mfpmath=sse -ffast-math -fomit-frame-pointer" DISTDIR="/usr/src/distfiles" FEATURES="autoaddcvs autoconfig ccache cvs distlocks fixpackages noauto sandbox sfperms strict" GENTOO_MIRRORS=" http://trumpetti.atm.tut.fi/gentoo http://lame.lut.fi/linux/gentoo " LANG="en_US.utf8" LC_ALL="en_US.utf8" LINGUAS="fi" MAKEOPTS="-j2" PKGDIR="/home/pkg/" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/overlays/betelgeuse /usr/local/overlays/gentopia" SYNC="cvs://betelgeuse@cvs.gentoo.org:/var/cvsroot" USE="x86 X aac acl acpi alsa apm audiofile avi bash-completion berkdb bitmap-fonts browserplugin bzip2 bzlib cdb cddb cdparanoia cdr crypt cups curl dbus divx4linux dts dvd dvdr dvdread emboss esd fam flac foomaticdb freetype gcj gif gstreamer gtk2 hal imagemagick java jpeg kde kdeenablefinal kdexdeltas libg++ libwww logitech-mouse lzo mad makecheck mikmod mjpeg mmx mmx2 mp3 mpeg ncurses network nptl nptlonly nsplugin nvidia offensive ogg oggvorbis opengl pam pdflib png python qt quicktime readline real rtc ruby samba slp spell sse sse2 ssl subversion svg symlink tcpd theora tiff truetype truetype-fonts type1-fonts unicode usb userlocales vorbis win32codecs xine xml xml2 xv xvid zlib video_cards_nvidia linguas_fi userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS
video herd, can G_FILENAME_ENCODING be set as part of the ebuild(s) themselves? It is not something that we should force the users to set. Or work out so that the configure/make stuff knows how to deal with UTF-8 set (either USE="unicode" or by checking the locale).
This seems more a problem for gnome herd (that manages gtk) than media-video. I'll leave it in CC just to be sure.
I think this problem is with every program using gtk so this belongs to the gnome herd. Adding unicode use flag to gtk+ and putting G_FILENAME_ENCODING to /etc/env.d/50gtk2 would definitely solve this problem.
That error message only appears when you have broken locale settings. If your locale data matches your filesystem data there should be no problems. The only way I could reproduce this problem was to create UTF-8 filename and then start gxine with `LC_ALL=C gxine`. In general there really should be no reason to meddle with G_FILENAME_ENCODINGs or G_BROKEN_FILENAMEs if the system is set up correctly.
betelgeuse@pena ~ $ env | grep -i utf LC_ALL=en_US.UTF-8 betelgeuse@pena ~ $ gxine (gxine:25577): Gtk-CRITICAL **: gtk_window_set_default_icon: assertion `GDK_IS_PIXBUF (icon)' failed Gtk-Message: The filename "datah\303\244r\303\266ily.prproj" couldn't be converted to UTF-8. (try setting the environment variable G_FILENAME_ENCODING): Invalid byte sequence in conversion input betelgeuse@pena ~ $ LC_ALL=fi_FI.utf8 gxine (gxine:25624): Gtk-CRITICAL **: gtk_window_set_default_icon: assertion `GDK_IS_PIXBUF (icon)' failed Gtk-Message: The filename "datah\303\244r\303\266ily.prproj" couldn't be converted to UTF-8. (try setting the environment variable G_FILENAME_ENCODING): Invalid byte sequence in conversion input betelgeuse@pena ~ $ G_FILENAME_ENCODING="UTF-8" gxine (gxine:25596): Gtk-CRITICAL **: gtk_window_set_default_icon: assertion `GDK_IS_PIXBUF (icon)' failed betelgeuse@pena ~ $
Getting this error might have something to do with that I am running KDE. I can try inside Gnome at some point to see what happens there.
What is your setting for NLS in the Kernel? GTK+ is entirely UTF-8 based and therefore, a unicode useflag does not make sense. AllanonJL and I were unable to reproduce your error.
(In reply to comment #7) > What is your setting for NLS in the Kernel? GTK+ is entirely UTF-8 based and > therefore, a unicode useflag does not make sense. AllanonJL and I were unable > to reproduce your error. > utf8 is the default
