Starting totem ( 0.100-r2 ) fails with a crash. It seems that not having a cdrom is the trigger for this. By starting from a terminal, the following error can be seen: GConf-CRITICAL **: gconf_client_set_string: assertion 'val != NULL' failed Looking through totem bugzilla I found the following relevant bugs: http://bugzilla.gnome.org/show_bug.cgi?id=163445 http://bugzilla.gnome.org/show_bug.cgi?id=166536 The first has entries referring to --disable-debug for gconf being the cause. I have tried rebuilding gconf, orbit and totem with USE=debug but this makes no difference. The second says it has been fixed in totem (I assume after 0.101 from the top of the bug report). It seems that emerging totem-1.0.1 wants to pull in all sorts of gnome 2.10 and I'm not brave enough to chance that. Is there any chance of a fix before gnome-2.10 is unmasked?
Having seen this be assigned to gstreamer, I should probably have said originally that I'm using xine-lib (although I don't know if that makes any difference).
Hey we're nice people, we fix xine-backend problems as well as gstreamer backend issues :) I guess thats why the CC. It is a xine-lib backend problem, and I have fixed it in portage with totem 0.100-r3. You should get it in your next sync.
Got it, it works now. Excellent. Thank you.
