I'm seeing unusual behavior in X/gnome after today's update.
1. The desktop switcher is gone from my default gnome session, now replaced by a new trash can. (This may be a feature of the new gnome-theme, perhaps.)
2. After a reboot and a fresh login to X, things look pretty much normal on the desktop, but whenever I launch a gnome-terminal, all window decorations disappear and the launched terminal is anchored and immovable in the upper left corner of the display. Subsequent gnome-term launches overlay the previous instance in the same location. It's as if the window manager stops running. Starting metacity manually returns the desktop to normal.
3. Thunderbird disappears. It's still running, but the window is no longer displayed. Upon logout, the window flashes briefly.
4. There are no clues in syslog or Xlog. :(
5. Is this one of those instances where removing all gconf stuff in $HOME is called for?
Jay Cliburn wrote:
I'm seeing unusual behavior in X/gnome after today's update.
- Thunderbird disappears. It's still running, but the window is
no longer displayed. Upon logout, the window flashes briefly.
The disappearance occurs whenever I minimize Thunderbird, and there's no way to maximize it since the window list app no longer runs by default. This is solved by adding the window list app to the panel.
Jay Cliburn wrote:
I'm seeing unusual behavior in X/gnome after today's update.
- The desktop switcher is gone from my default gnome session, now
replaced by a new trash can. (This may be a feature of the new gnome-theme, perhaps.)
- After a reboot and a fresh login to X, things look pretty much
normal on the desktop, but whenever I launch a gnome-terminal, all window decorations disappear and the launched terminal is anchored and immovable in the upper left corner of the display. Subsequent gnome-term launches overlay the previous instance in the same location. It's as if the window manager stops running. Starting metacity manually returns the desktop to normal.
- Thunderbird disappears. It's still running, but the window is
no longer displayed. Upon logout, the window flashes briefly.
There are no clues in syslog or Xlog. :(
Is this one of those instances where removing all gconf stuff
in $HOME is called for?
I moved $HOME/.gconf{d} out of the way and my desktop defaults have returned to normal (show desktop app, window list app, desktop switcher app are present), however metacity psuedo-death still occurs upon first launch of gnome-terminal.
On Sat, 2006-08-12 at 10:05 -0500, Jay Cliburn wrote:
Jay Cliburn wrote:
I'm seeing unusual behavior in X/gnome after today's update.
- The desktop switcher is gone from my default gnome session, now
replaced by a new trash can. (This may be a feature of the new gnome-theme, perhaps.)
- After a reboot and a fresh login to X, things look pretty much
normal on the desktop, but whenever I launch a gnome-terminal, all window decorations disappear and the launched terminal is anchored and immovable in the upper left corner of the display. Subsequent gnome-term launches overlay the previous instance in the same location. It's as if the window manager stops running. Starting metacity manually returns the desktop to normal.
- Thunderbird disappears. It's still running, but the window is
no longer displayed. Upon logout, the window flashes briefly.
There are no clues in syslog or Xlog. :(
Is this one of those instances where removing all gconf stuff
in $HOME is called for?
I moved $HOME/.gconf{d} out of the way and my desktop defaults have returned to normal (show desktop app, window list app, desktop switcher app are present), however metacity psuedo-death still occurs upon first launch of gnome-terminal.
For what it's worth, I have a completely updated i386 system, have rebooted, and have none of the problems you list above. I wonder if it is the result of the nautilus dependency errors problem you had a couple of days ago. Gerry
On Sat, Aug 12, 2006 at 12:20:34PM -0500, Gerry Tool wrote:
On Sat, 2006-08-12 at 10:05 -0500, Jay Cliburn wrote:
I'm seeing unusual behavior in X/gnome after today's update.
For what it's worth, I have a completely updated i386 system, have rebooted, and have none of the problems you list above.
That is strange unless you updated from some mirror which is bit behind. gnome-session-2.15.90-3.fc6 has a typo in /usr/bin/gnome-wm script and this actually kills startup procedures. See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202312 Tim Vismor complains there only about compiz but really any window manager is affected.
The quoted report has a fix (';;' missing) or you may back off to gnome-session-2.15.90-2.fc6.
Michal
Michal Jaegermann wrote:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202312 Tim Vismor complains there only about compiz but really any window manager is affected.
The quoted report has a fix (';;' missing) or you may back off to gnome-session-2.15.90-2.fc6.
Excellent. Thanks Michal. Adding the missing ';;' fixed it for me.
Jay
On Sat, 2006-08-12 at 13:39 -0600, Michal Jaegermann wrote:
On Sat, Aug 12, 2006 at 12:20:34PM -0500, Gerry Tool wrote:
On Sat, 2006-08-12 at 10:05 -0500, Jay Cliburn wrote:
I'm seeing unusual behavior in X/gnome after today's update.
For what it's worth, I have a completely updated i386 system, have rebooted, and have none of the problems you list above.
That is strange unless you updated from some mirror which is bit behind. gnome-session-2.15.90-3.fc6 has a typo in /usr/bin/gnome-wm script and this actually kills startup procedures. See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202312 Tim Vismor complains there only about compiz but really any window manager is affected.
The quoted report has a fix (';;' missing) or you may back off to gnome-session-2.15.90-2.fc6.
Judging from
[root@fc6t2 ~]# rpm -q gnome-session gnome-session-2.15.90-3.fc6
I wouldn't say the mirror was behind, and I do not see the problem.
Gerry
On Sat, Aug 12, 2006 at 08:35:44PM -0500, Gerry Tool wrote:
Judging from
[root@fc6t2 ~]# rpm -q gnome-session gnome-session-2.15.90-3.fc6
I wouldn't say the mirror was behind, and I do not see the problem.
Then you are lucky here. :-) /usr/bin/gnome-wm has an obvious bug in it. Maybe your gnome-session clients happen to start in some "right" order or you enviroment makes gnome-wm to "flow around" the trouble spot? Difficult to tell without tracing.
Michal
-
Gerry Tool -
Jay Cliburn -
Michal Jaegermann