X11 Backing store under suse 11.3

I have just installed a new 11.3 machine which should replace my old one with suse 9.2.

I have some X11 applications which require backing store support. Under 9.2 I added Option “BackingStore” “True” to section “Device” in /etc/X11/xorg.conf.

With 11.3 the arrangement of the X server has changed. I added Option “BackingStore” “True” to file 50-device.conf in /etc/X11/xorg.conf.d. This was enough to activate backing store when a window is partially obscured by another window, but the content of the window is lost : (1) when the window is iconized; (2) when the window is moved to another desktop (I am using fvwm). It is not lost when it is moved to another page in same desktop.

Are there any other options to obtain a backing store working as it used to do in 9.2 (window content was ***always ***preserved).

Hi
So in your Xorg.0.log you are seeing backingstore being enabled ok?


(**) (0): Option "BackingStore" "true"
(**) (0): Backing store enabled"


Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.32.24-0.2-default
up 1 day 16:04, 2 users, load average: 0.05, 0.04, 0.00
GPU GeForce 8600 GTS Silent - Driver Version: 260.19.21

[QUOTE=malcolmlewis;2265840]Hi
So in your Xorg.0.log you are seeing backingstore being enabled ok?


(**) (0): Option "BackingStore" "true"
(**) (0): Backing store enabled"

Yes I do. I did not check, but now I did, and those lines are there.

What I checked before was the behaviour. I created a graphical window with a couple of applications (one is IDL, another one of my own) and verified that their content is **not lost **when the window is partially obscured under another window, moved to a different page in same desktop (fvwm) or made sticky (fvwm), which is good. I also verified the content **is lost ** if the window is iconified and deiconified, or moved to a different desktop (fvwm). This latter behaviour is not desirable, and did not happen under 9.2.

Hi
I’m not a fvwm user so I wonder if some underlying changes with either
Xorg or fvwm is causing issues.

I would log it as a bug at Bugzilla Main Page and
provide the information outlined here with the bug;
openSUSE:Bugreport X - openSUSE Wiki


Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.32.24-0.2-default
up 1 day 16:53, 2 users, load average: 0.11, 0.15, 0.10
GPU GeForce 8600 GTS Silent - Driver Version: 260.19.21

Logged (painfully) the bug.

I can exclude it is a fvwm issue. I tested it under KDE, and it occurs there as well.

Talking of fvwm, I was in correspondence with Thomas Adams (the fvwm mantainer) about another issue on the shipped fvwm config. He has a revised version, and asked me to contact the Suse mantainer for fvwm. But I have no idea who this is ? What is the best way to pass this info to the right person ?

luciochiappetti wrote:
> contact the Suse mantainer for fvwm. But I have no idea who this is
> ? What is the best way to pass this info to the right person ?

most of those folks hang out on a mail list, or IRC, i wouldn’t know
which one the fvwm might be on, but you can find all of them here:
http://en.opensuse.org/openSUSE:Communication_channels

probably easiest to ask who/how on IRC: “The main support channel is
#opensuse on irc.opensuse.org.”


DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]

Hi
Probably the ‘Bug’ owner
https://build.opensuse.org/package/users?package=fvwm2&project=X11%3Awindowmanagers


Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.32.24-0.2-default
up 1 day 19:54, 3 users, load average: 0.09, 0.10, 0.04
GPU GeForce 8600 GTS Silent - Driver Version: 260.19.21