On Thu, Oct 08, 2009 at 16:34:16 -0400, Thomas H. George wrote: > On Thu, Oct 08, 2009 at 07:33:22PM +0200, Florian Kulzer wrote: > > On Thu, Oct 08, 2009 at 09:28:26 -0400, Thomas H. George wrote: > > > On Thu, Oct 08, 2009 at 10:58:41AM +0200, Florian Kulzer wrote: > > > > [...] > > > > > > > Given the command totem trial001.mov the one that can't responds > > > > [...] > > > > > > > ** (totem:8648): WARNING **: Failed to create dbus proxy for > > > > > org.gnome.SettingsDaemon: Could not get owner of name > > > > > 'org.gnome.SettingsDaemon': no such name > > > > > Segmentation fault
[...] > > > > find /usr/share/dbus-1/services/ -name 'org.gnome.*' > > > > > > > > > > Script started on Thu 08 Oct 2009 09:23:32 AM EDT > > > dragon:~# find /usr/share/dbus-1/services -name 'org.gnome.*' > > > /usr/share/dbus-1/services/org.gnome.seahorse.service > > > /usr/share/dbus-1/services/org.gnome.keyring.service > > > /usr/share/dbus-1/services/org.gnome.PolicyKit.AuthorizationManager.service > > > /usr/share/dbus-1/services/org.gnome.Epiphany.service > > > /usr/share/dbus-1/services/org.gnome.GConf.service > > > /usr/share/dbus-1/services/org.gnome.PolicyKit.service > > > dragon:~# exit > > > > Does the working system have a file called "org.gnome.SettingsDaemon" in > > this directory? (Note that I do not know Gnome very well, so Iam just > > guessing based on what I know about dbus.) > > > Neither system has this file - that is locate -i > org.gnome.settingsdaemon returns nothing! Both systems have a directory > /etc/dbus-1/system, a directory /usr/share/dbus-1/services and a > directory /usr/share/PolicyKit/policy with many entries of the form > org.gnome.foo. OK, the gnome settings daemon does not interact with dbus in the way that I would have expected. Somebody with more knowledge of Gnome may be able to shed more light on this; I still think that the dbus proxy warning is not necessarily connected to the reason for the segfault. [...] > > ldd `which totem` > > > Here is the output - rather a lot of dependencies. The output of the > working system looks similar but as yet I have not transfered the output > from one system to the other to run a comparison. [...] I was suspecting that you have an outdated or broken library in /user/local/ that is responsible for your problem (the ldd output should have shown this) but that does not seem to be the case. Well, time for the big guns: Install the packages "totem-dbg" and "gdb", then start gdb like this gdb totem and type run trial001.mov at the gdb prompt that comes up. This sequence of commands will run totem in the GNU debugger, which should catch the segfault. Once it does, type bt at the gdb prompt and post the resulting output (the backtrace) here. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
