On Sun, 2011-07-24 at 12:25 +0100, philip taylor wrote: > Hi > I get the following errors, in dmesg, when i try and start gnome-shell > with debian sid + debian experimental, it only started yesterday. > > > [ 4229.154477] gnome-settings-[22046]: segfault at b44514d0 ip > b44514d0 sp bff3183c error 14 in libdbus-1.so.3. > 5.7[b448f000+48000] > [ 4263.901480] gnome-settings-[20423]: segfault at b47634d0 ip > b47634d0 sp bfd1d64c error 14 in libdbus-1.so.3. > 5.7[b47a1000+48000] > [ 4288.843020] gnome-shell[20597]: segfault at bc ip b73df5f9 sp > bfbaec10 error 4 in libmozjs.so.4d[b73bd000+30 > 7000] > [ 4293.674309] gnome-shell[20659]: segfault at bc ip b74285f9 sp > bf814bc0 error 4 in libmozjs.so.4d[b7406000+30 > 7000] > [ 4297.287525] gnome-settings-[20562]: segfault at b455d4d0 ip > b455d4d0 sp bfef745c error 14 in libdbus-1.so.3. > 5.7[b459b000+48000] > [ 4326.532173] gnome-settings-[20720]: segfault at b47804d0 ip > b47804d0 sp bfe426dc error 14 in libdbus-1.so.3. > 5.7[b47be000+48000] > > > > > it then sends me to the force logout screen, and says something > serious has happened. > any ideas, on how this could be solved please. > thank you, > Philip Firstly the gnome-shell mailing list might not be the best place to send such messages. If the solution will not be find soon it is likely that the message get lost in archives and be forgotten. I would suspect that the problem is downstream/not in gnome-shell and possibly should be reported on Debian bugzilla. If you think that problem is upstream report it on Gnome bugzilla. In any case you are more likely to receive support. It also be good to get a stacktrace[1] of gnome-shell[2] and gnome-settings-daemon as all that can be said is that it is not suppose to happened. Regards PS. I'm not gnome-shell developer. [1] http://live.gnome.org/GettingTraces/Details [2] http://live.gnome.org/GnomeShell/Debugging
Attachment:
signature.asc
Description: This is a digitally signed message part