On 04/12/2010 04:46 PM, Firmicus wrote: > On 12/04/2010 02:04, Alexander Lam wrote: >> On Sun, Apr 11, 2010 at 6:31 PM, David C. Rankin >> <drankinatty@xxxxxxxxxxxxxxxxxx> wrote: >> >>> Guys, >>> >>> For some reason, emerald has started crashing when changing >>> themes in Gnome. It >>> changes the theme just fine, but then crashes. (disappears - no error >>> shown or >>> in any logs). The crash occurs as soon as you click on a new theme to >>> change it. >>> This happens when you select the first theme 3/4 of the time. Other >>> times, you >>> can click on two, or maybe even three themes looking for the one you >>> want before >>> the crash occurs at other times. The result is the same, >>> emerald-theme-manager >>> just disappears into thin air. A restart restores emerald without >>> error as well. >>> >> >> Same issue here - compiz standalone setup >> >> > > Happens also without compiz, just latest gnome with metacity: starting > "gnome-appearance-properties" yields > "Fatal IO error 104 (Connection reset by peer) on X server :0.0." > and X crashes. Not yet sure what's causing this. > > F > I know that there is a conflict in older versions of gnome/metacity/gtk and the gstreamer-ugly plugin, but I don't think that is the problem with the current Arch package. I don't know what the issue is, but I can confirm the appearance-properties crash as well. On my system, it crashes, the bug reporting tool comes up, I send the bug in, and then I can continue to use the appearance tool without further problems. I can also confirm that this behavior occurs on Gnome 2.2 and the current arch version. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
