Bugzilla Bug 80053

There are at least a couple of threads in the forum complaining about
nautilus-cd-burner-2.8.6 not working. This one for example:
http://forums.gentoo.org/viewtopic.php?t=272701&highlight=nautiluscdburner
I have the problem too. It's possible to mask it in /etc/portage/package mask,
but then gnome-base/gnome-2.8.2 depends on that specific version of
nautilus-cd-burner, and the whole thing becomes annoying.

nautilus-cd-burner-2.8.5 works, so what I would do is create a
gnome-base/gnome-2.8.2-r1.ebuild that doesn't explicitely require
nautilus-cd-burner-2.8.6, and maybe hard mask nautilus-cd-burner-2.8.6 (this is
not absolutely necessary if we can mask it locally, though)

I'm not a developper, however...

Reproducible: Always
Steps to Reproduce:
1. emerge nautilus-cd-burner-2.8.6 or gnome-2.8.2
2. try and burn a CD

Actual Results:  
See forum posts.

Expected Results:  
See forum posts.

Here's my 'emerge info', in case that helps.

Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.4.3,
glibc-2.3.4.20041102-r0, 2.6.10-ck5 i686)
=================================================================
System uname: 2.6.10-ck5 i686 AMD Athlon(tm) XP 1600+
Gentoo Base System version 1.6.8
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Dec 10 2004, 01:36:58)]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r1, 2.15.92.0.2-r2
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -Os -fomit-frame-pointer -ftracer -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -Os -fomit-frame-pointer -ftracer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://mir.zyrianes.net/gentoo/
http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://gentoo.osuosl.org
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 3dnow 3dnowex X Xaw3d a52 alsa apm avi berkdb bitmap-fonts canna
cdparanoia cdr cjk crypt curl divx4linux dmx dvd dvdr edl encode esd f77 faac
faad fam flac font-server foomaticdb fortran fpx gcj gd gdbm gif gmail gnome
gpm
graphviz gtk gtk2 hal imagemagick imlib java javascript jbig jpeg lcms libg++
libwww live lzo mad mikmod mime mmx mmx2 motif mozilla mozsvg mpeg mpi ncurses
network nls nntp nptl nptlonly nvidia oggvorbis opengl oss pam pdflib perl pic
png python quicktime readline real rtc sdl slp sndfile speex spell sse ssl
tcltk
tcpd theora tiff truetype truetype-fonts type1-fonts unicode userlocales wmf
xanim xml2 xmms xv xvid xvmc zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS

Yep, we know, and we've got the fix. It's in cdrtools - waiting for a patch to
be applied. Marking it as a dependency of this bug.

You can help out of course - by testing the patched ebuild in the cdrtools bug
28369

I just did, and it works. Should we close this bug or wait for the solution to
bug 28369 to be effective ?

This is still happening with the patched cdrtools.

The problem is that nautilus-cd-burner-2.8.6 calls mkisofs with "-input-charset
utf8", which is understood only when cdrtools is compiled with the unicode USE
flag.  (So if you're using cdrtools-2.01-r2 and still seeing the bug, this is
probably why.)  This is mentioned in the Gnome bug report
<http://bugzilla.gnome.org/show_bug.cgi?id=149486>, but as the report is
closed, it doesn't look like anything is going to happen upstream.  Should
cdrtools simply always get the Unicode patch?

Correct, 2.8.* require USE="unicode" cdrtools. I've added a check in this for
2.8.7 which is just about to hit stable as part of GNOME 2.8.3.

Brad, if you can reproduce with USE="unicode" emerge cdrtools, then reopen.