desktop-packages team mailing list archive

[Alonso Andres <868095@xxxxxxxxxxxxxxxxxx>]

I'm also having the same problem.

I was able to track the cause of this problem and find a workaround that
seems to work.

1 - Cause:

The event deconfiguring-networking is fired whenever
"/etc/init.d/networking stop" is called.

If you read the source of /etc/init.d/networking you can see this line:

    initctl emit deconfiguring-networking

D-Bus is configured to stop working whenever the event deconfiguring-
networking is fired.

If you read the source of /etc/init/dbus.conf you can see this line:

    stop on deconfiguring-networking

gnome-settings-daemon segfaults whenever D-Bus is killed.

You can see this in the syslog:

   Suspend VMware:
     Oct 25 15:33:54 ubuntu kernel: [ 4317.379836] init: dbus main process (10856) killed by TERM signal
     Oct 25 15:33:54 ubuntu kernel: [ 4317.382712] init: Disconnected from system bus

   Resume VMware:
     Oct 25 15:36:01 ubuntu kernel: [ 4444.539639] gnome-settings-[11048]: segfault at 8 ip b43f15a8 sp bf96b790 error 4 in libpower.so[b43e2000+18000]


2 - How VMware is related to this:

VMware Tools is able to run scripts on the virtual machine poweron, suspend, resume etc.
The script /etc/vmware-tools/scripts/vmware/network calls "/etc/init.d/networking stop" when the machine is suspended.

Since stopping the networking services creates this chain reaction that
ends up crashing gnome-settings-daemon, it's always going to happen when
the virtual machine gets suspended and VMware Tools runs this network
script.

3 - My workaround:

    sudo chmod 644 /etc/vmware-tools/scripts/vmware/network

Yeah, that's all, just remove the "executable" flag on this script. Of
course it won't run when you suspend/resume your VM, but I actually
didn't miss it. The network in my VM kept working after
suspending/resuming.

Of course this is not the solution to the actual problem.

4 - What is the solution?

This problem means that whenever I decide to restart the network by
typing

    /etc/init.d/networking stop
    /etc/init.d/networking start

D-bus will get killed and gnome-settings-daemon will segfault. This
shouldn't really be the intended behavior.

So the question is, why does D-Bus has to stop working whenever the
network goes down?

---

I hope I was able to help you figure out this problem.
Meanwhile my workaround seems to be working and brought me peace again. :-)

** Changed in: gnome-settings-daemon (Ubuntu)
       Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868095

Title:
  gnome-settings-daemon crashes on resume in VMware

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  gnome-settings-[2165]: segfault at 8 ip 00d5a5a8 sp bf8051f0 error 4
  in libpower.so[d4b000+18000]

  Reliable gnome-settings-daemon crash every time an oneiric system is
  suspended then resumed in VMware Player.  Occurs under both VMware
  Player 3.x and the newest 4 version.  Crash occurs when tried with
  open-vm tools and the official VMware bundle.

  When gnome-settings-daemon crashes the desktop has no theming and
  broken menus.  A restart is needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu2
  Architecture: i386
  Date: Wed Oct  5 00:59:00 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to oneiric on 2011-09-05 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/868095/+subscriptions