Re: [arch-general] Emerald crashing on theme change or edit in Gnome
On 04/13/2010 04:03 PM, Firmicus wrote: >>> 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. >> >> > It appears to be related to some ancient and incompatible configuration > settings under $HOME/.gconf/, because the problem disappeared after I > renamed ~/.gconf and restarted gnome/metacity. I have not tracked this > down further though: I just copied over the settings I really care for, > and left the rest in a backup. > > F Ooh, Good information. I'll give it a go and see if I can get appearance working without the familiar bug reporting tool appearing. Thanks. -- 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
Re: [arch-general] Emerald crashing on theme change or edit in Gnome
On 13/04/2010 22:30, David C. Rankin wrote: 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 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. It appears to be related to some ancient and incompatible configuration settings under $HOME/.gconf/, because the problem disappeared after I renamed ~/.gconf and restarted gnome/metacity. I have not tracked this down further though: I just copied over the settings I really care for, and left the rest in a backup. F
Re: [arch-general] Emerald crashing on theme change or edit in Gnome
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 >> 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
Re: [arch-general] Emerald crashing on theme change or edit in Gnome
On 12/04/2010 02:04, Alexander Lam wrote: On Sun, Apr 11, 2010 at 6:31 PM, David C. Rankin 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
Re: [arch-general] Emerald crashing on theme change or edit in Gnome
On Sun, Apr 11, 2010 at 6:31 PM, David C. Rankin 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 -- Alexander Lam
[arch-general] Emerald crashing on theme change or edit in Gnome
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. The problem prevent you from being able to look at more than one theme or edit the emerald themes. The issue isn't with any new theme, I have a set that I've been using without error for a while, it seems like one of the recent updates may be the cause (new Xorg?). I will look at it in kde later this evening. Has anyone else experienced this or got any more information on this new emerald trick? I know emerald well from a user's standpoint, but not from the developer standpoint. I have checked all the logs I could think of (messages.log, everything.log, Xorg.0.log, errors.log ~/.xsession-errors), but I didn't find anything. Is there somewhere else I should be looking? I'll try to provide more information on the behavior in kde and see if I can get anything else from the command line. However, if you have any suggestions in the interim, I would sure appreciate it. Thanks. -- 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
