same happens on current image of 13.04 i386 desktop live environment right after restarting networking service, so basically in my case steps to reproduce look like this:
gnome-settings-daemon segfault occurs according to syslog:
Mar 4 17:29:19 ubuntu kernel: [ 302.709872] gnome-settings-[3658]: segfault at 8 ip b3e336b1 sp bff56430 error 4 in libpower.so[b3e23000+19000]
Mar 4 17:29:21 ubuntu gnome-session[2997]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 11
Mar 4 13:39:10 ubuntu gnome-session[2997]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
same happens on current image of 13.04 i386 desktop live environment right after restarting networking service, so basically in my case steps to reproduce look like this:
1. --2013-03-04 16:19:34-- http:// cdimage. ubuntu. com/daily- live/current/ raring- desktop- i386.iso (gmt +3)
2. boot into system
3. get into another terminal (ctrl+alt+f1)
4. sudo service network-manager stop
5. sudo service networking restart
gnome-settings- daemon segfault occurs according to syslog: [3658]: segfault at 8 ip b3e336b1 sp bff56430 error 4 in libpower. so[b3e23000+ 19000] 2997]: WARNING: Application 'gnome- settings- daemon. desktop' killed by signal 11 2997]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/ dbus/system_ bus_socket: No such file or directory
Mar 4 17:29:19 ubuntu kernel: [ 302.709872] gnome-settings-
Mar 4 17:29:21 ubuntu gnome-session[
Mar 4 13:39:10 ubuntu gnome-session[