Your message dated Sun, 1 Jan 2017 14:00:53 -0700
with message-id 
<CAJabFbgk99M+Y_Q+5pug+AbpmpynGpQfT3Zu+1+WVA=d-3v...@mail.gmail.com>
and subject line Re: Bug#675716: fvwm corrupts a sticky window over FvwmPager 
at desktop change
has caused the Debian Bug report #675716,
regarding fvwm corrupts a sticky window over FvwmPager at desktop change
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
675716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675716
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fvwm
Version: 1:2.5.30.ds-1.1+local1
Severity: normal

The following sequence can trigger a display problem with my config
file (see a part of my fvwmrc below):
1. Open a GNU Emacs window where "File" (in the menu) is over the
   FvwmPager (where there will be a change below).
2. Set the window as sticky.
3. Change the desktop (e.g. with Ctrl-Meta-arrow).

-> A part of the Emacs menu bar can be corrupted. See attached
snapshots as examples.

I think that what happens at (3) is the following: due to the
desktop switching, the contents of FvwmPager change. Normally
this change shouldn't be visible because the Emacs window is
over the FvwmPager window and is sticky, but this change is
partly done on the screen as if the Emacs window weren't there.

I can easily reproduce this bug with Emacs, Calcoo and Qalculate,
but not with some other applications, like gnome-terminal.

Note: my fvwm package is a locally rebuilt version with the
shape-hints patch in bug 588537.

My fvwmrc contains in particular:

DeskTopSize     2x2
OpaqueMoveSize  80
EdgeResistance  -1

HilightColor    Black   #c06077

ButtonStyle 1 5 25x40@1 25x60@1 75x60@0 75x40@0 25x40@1
ButtonStyle 2 5 40x25@1 40x75@1 60x75@0 60x25@0 40x25@1
ButtonStyle 4 5 25x25@1 25x75@1 75x75@0 75x25@0 25x25@1

Style "*"               BorderWidth 4, HandleWidth 4
Style "*"               Color Black/#60a0c0
Style "*"               MWMBorder, MWMButtons, MWMDecor, NoIcon
Style "*"               ActivePlacement
Style "*"               DecorateTransient
Style "*"               DontRaiseTransient, DontLowerTransient
Style "*"               EdgeMoveDelay -1, EdgeMoveResistance 20
Style "Fvwm*"           NoTitle, NoHandles, Sticky, WindowListSkip, \
                        BackColor #60c0a0

Style Display !AllowShapeHints

DefaultFont     "xft:Bitstream:size=10"
WindowFont      "xft:Bitstream:size=9"
IconFont        "xft:Bitstream:size=9"

AddToFunc RestartFunction \
        "I" Module FvwmPager 0 0
+       "I" Module FvwmButtons
+       "I" Module FvwmWinList

AddToFunc InitFunction \
        "I" Desk 0 0
+       "I" RestartFunction
[...]

DestroyFunc EWMHActivateWindowFunc
AddToFunc EWMHActivateWindowFunc I Focus

Mouse 0         1       A       Windowops-or-Die
Mouse 1         2       A       Raise-and-Fct Maximize 0 100
Mouse 2         2       A       Maximize 0 grow
Mouse 3         2       A       Maximize 0 100
Mouse 0         3       A       Stick
Mouse 1         4       A       Raise-and-Fct Maximize 100 100
Mouse 2         4       A       Maximize grow grow
Mouse 3         4       A       Maximize 100 100
Mouse 0         5       A       Iconify
Mouse 0         6       A       Iconify

Key Left        A       CM      Scroll -100 0
Key Right       A       CM      Scroll +100 0
Key Up          A       CM      Scroll 0 -100
Key Down        A       CM      Scroll 0 +100

*FvwmPagerGeometry      89x72+0+0
*FvwmPagerFont          "xft:Bitstream:size=9"
*FvwmPagerFore          Black
*FvwmPagerBack          #4040c0
*FvwmPagerHilight       #9878a8

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fvwm depends on:
ii  libc6                                  2.13-32
ii  libcairo2                              1.10.2-7
ii  libfontconfig1                         2.9.0-6
ii  libfribidi0                            0.19.2-3
ii  libgdk-pixbuf2.0-0                     2.26.1-1
ii  libglib2.0-0                           2.32.3-1
ii  libice6                                2:1.0.8-2
ii  libpng12-0                             1.2.49-1
ii  libreadline6                           6.2-8
ii  librplay3                              3.3.2-14
ii  librsvg2-2                             2.36.1-1
ii  libsm6                                 2:1.2.1-2
ii  libstroke0                             0.5.1-6
ii  libtinfo5                              5.9-7
ii  libx11-6                               2:1.4.99.901-2
ii  libxcursor1                            1:1.1.13-1
ii  libxext6                               2:1.3.1-2
ii  libxft2                                2.2.0-3
ii  libxinerama1                           2:1.1.2-1
ii  libxpm4                                1:3.5.10-1
ii  libxrender1                            1:0.9.7-1
ii  perl                                   5.14.2-11
ii  perl-modules [libperl4-corelibs-perl]  5.14.2-11
ii  zlib1g                                 1:1.2.7.dfsg-11

Versions of packages fvwm recommends:
ii  fvwm-icons            20070101-1
ii  libx11-protocol-perl  0.56-2
ii  perl-tk               1:804.029-1.2

Versions of packages fvwm suggests:
pn  cpp          4:4.7.0-6
pn  fvwm-themes  <none>
pn  m4           1.4.16-3
pn  menu         2.1.46
pn  wm-icons     <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
The bug appears to be a graphics driver (nouveau) bug and not a fvwm
bug. Since it has been a few years and the user is no longer using
nouveau the bug may or may not be still present in nouveau.

Closing the bug. (Re)open the bug against nouveau if using those
drivers still cause the display issue.

jaimos

--- End Message ---

Reply via email to