So according to the backtrace the interesting value is optimized ... Maybe you could rebuild the gconf2 package with debug (https://wiki.ubuntu.com/DebuggingProgramCrash) to figure what gconf key is the issue? -- [Dapper] Sound-juicer crashes after editing gconf keys https://launchpad.net/malone/bugs/38300
-- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
