Created attachment 2807 Stracktrace.txt This bug has been reported on Ubuntu Launchpad as: https://bugs.launchpad.net/bugs/512443 As reported in launchpad: ProblemType: Crash Architecture: amd64 Date: Mon Jan 25 13:32:27 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/xfwm4-settings InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113) NonfreeKernelModules: nvidia Package: xfwm4 4.6.1-1 ProcAttrCurrent: unconfined (enforce) ProcCmdline: xfwm4-settings --socket-id=71303856 ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-11.15-generic SegvAnalysis: Segfault happened at: 0x7f545ce2468a: movlpd (%rsi),%xmm2 PC (0x7f545ce2468a) ok source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)! destination "%xmm2" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: xfwm4 StacktraceTop: ?? () from /lib/libc.so.6 g_str_equal () from /lib/libglib-2.0.so.0 ?? () ?? () g_object_newv () from /usr/lib/libgobject-2.0.so.0 Title: xfwm4-settings crashed with SIGSEGV in g_str_equal() Uname: Linux 2.6.32-11-generic x86_64
I am not a big fan of those automated bug reports tbh. All I can see is that the crash occurs on g_str_equal() called from xfwm_settings_title_alignment_property_changed(). Of the two strings used in g_str_equal() one is not NULL and contains "left". So my guess is that g_value_get_string (value) returned NULL, but that should not happen. So can we get the usual debugging data that are found in all bug reports, ie: - How reproducible? - Steps to reproduce - Degugging data, starting with "xfconf-query -c xfwm4 -lv" and the content of "~/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml"
Until I get some more data to help finding the cause, my guess is that the GValue is of type invalid, will check for that in the code.
*** This bug has been marked as a duplicate of bug 6161 ***
I will work on getting that additional information into these reports.
(In reply to comment #4) > I will work on getting that additional information into these reports. Actually I don't think it's needed anymore, at least for now, this bug is actually a duplicate of another bug which had more information included. Based on the information from bug #6161 I have now committed a fix in git. That would need testing though.