"Are you in unity or classic desktop? If in classic, do you have the appmenu applet running?"
This Natty system is a VMware virtual machine without graphics acceleration, so I believe it's a classic desktop (Xorg is the windowing server, and I run applications by selecting them from a menu which is a GNOME panel applet, and I don't have the dock-like bar on the left side of the screen that characterizes Unity), but I haven't actually *selected* classic desktop. In some previous daily builds a while back, I used to get a message telling me to select classic desktop because I didn't have graphics acceleration. That is no longer the case. In GDM the session type selection is "Ubuntu Desktop Edition". Since this is currently my only Natty system, I don't know for sure exactly what the interface is *supposed* to look like, so just in case there's something obvious that I'm missing, I'll attach two screenshots. One is what the desktop looks like during the first login after boot-up. The other is what the desktop looks like during all subsequent logins. This is to say that if I log out (of that first login) and log back in, it's differently themed. I've been meaning to report that as a bug--I hope to get around to doing so later today. The theme that appears the first time I log on after rebooting is the same theme as was in use when I initially booted the live CD, messed around with changing the screen resolution a number of times, and installed Ubuntu. In case it's relevant, this is a 32-bit uniprocessor virtual machine with 1 GB of RAM being virtualized by VMware Workstation 7.1.3 build-324285. VMware Tools version 8.4.5-324285 (the guest drivers) is installed in the virtual machine, but of course wasn't installed in the live CD system where I first experienced bug 729065. However, some of the drivers for VMware guest systems are included with Ubuntu--this is to say that presumably xserver-xorg-video-vmware 1:11.0.3-1ubuntu2 and xserver-xorg-input-vmmouse 1:12.6.99.901-1ubuntu2, which are installed on and running in this Natty system (i.e. this virtual machine), were also installed and running on the (of course also virtualized) live CD system. In case it's useful, I've attached Zim.vmx, which is the file that contains the virtual hardware specifications for this virtual machine. The *host* system running VMware is itself a Maverick amd64 system with about 4GB of RAM (slightly less for the onboard Intel GMA video) and a 2.2 GHz Intel Core 2 Duo processor; this host system runs kernel version 2.6.35-28-generic. "Do you switch resolutions or just try to (I know you just try to on the last time, when it crashes, but other times you open the dialog, you actually switch resolutions?)" Both crashes (i.e. bug 729065 and this bug) occur when I expand the drop-down menu to see the list of resolutions. But when it doesn't crash, I have gone ahead and actually changed the resolution. I have quit gnome-display-properties after changing the resolution; thus, when I change it (or try to change it) the next time, I reopen gnome-display-properties. "Any pattern to crashes vs. non-crashes that might be a clue?" I think the correct answer to this is: no, I have not noticed such a pattern. However, it has occurred to me that most of the crashes on the live CD system were when trying to switch the resolution from 800x600 *back* to 1024x768, whereas most of the crashes on the installed system were when trying to switch the resolution from 1024x768 *back* to 800x600. (That is, the live CD system had decided 1024x768 should be its default resolution, and I didn't change the default; on the installed system, one of the first things I did after installation was to specify 800x600 as the default resolution; I did this in gnome-display- properties itself.) I am not really confident that this description (of which direction caused more crashes) is even accurate, and even if it is, it may well be explainable by pure chance--I doubt I've done this enough times to have a statistically significant sampling. I'm really reaching, with this suggestion. Furthermore, with the new version of appmenu-gtk (from your PPA), I have only actually produced this crash once. If it would be useful, I can try to produce it some more. If that is useful, please let me know if it would also be useful to file separate duplicate bug reports if/when I succeed. (If memory corruption is happening, perhaps there will be some variability which might be diagnostically useful to know about? I don't know, maybe I just like filing bug reports... ;-) ) Since the crash in bug 729230 was produced on a live CD system, presumably this one can be produced on one too. If it would help, I could try that. Please let me know. Since this is a virtual machine, I could compress it and send it, if you can specify a way you'd like to receive a really big file. Since I just installed Natty today and have not customized it or installed much in the way of additional applications, it shouldn't be extraordinarily huge --perhaps 2.5 GB compressed. But since bug 729230 happened when running from the live CD, perhaps I could just send a virtual machine identical to this one before installation. Such a system would easily and quickly compress down to a size where it could be easily attached here on Launchpad. Of course, if you don't have a suitable VMware virtualization product, then sending a VMware virtual machine on which this bug occurs would probably not be helpful. (You might be able to convert the virtual machine to run on VirtualBox, but this bug wouldn't necessarily persist with the new virtual hardware.) VMware Player is free-as-in-beer-ware for noncommercial use, but I think commercial use might require a paid license. ** Attachment added: "Zim.vmx (virtual hardware specification for this machine)" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/729230/+attachment/1886244/+files/Zim.vmx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/729230 Title: gnome-display-properties crashed with SIGSEGV in invoke_get_all_properties_in_idle_cb() -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
