Xfce Forum

Sub domains
 

You are not logged in.

#1 2022-01-17 00:47:56

renshijun
Member
Registered: 2022-01-17
Posts: 13

mousepad problem

I just installed xfce4.16. when I type in mousepad, trouble comes.

Type in mousepad

The locale is set as: export LANG=zh_CN.UTF-8

If I set: export LANG=   

then mousepad works fine. 

Its curious......

Offline

#2 2022-01-17 10:42:34

Tamaranch
Member
Registered: 2020-12-31
Posts: 93

Re: mousepad problem

I guess the right link is https://tieba.baidu.com/p/7697235600
Which version of Mousepad do you use? Also, which versions of GtkSourceView and GTK?

Offline

#3 2022-01-17 12:03:24

renshijun
Member
Registered: 2022-01-17
Posts: 13

Re: mousepad problem

GTK+-3.24.30, GtkSourceView4-4.8.1.  I try both Mousepad-0.5.6 and Mousepad-0.5.8. The result is the same.

Offline

#4 2022-01-17 12:07:29

renshijun
Member
Registered: 2022-01-17
Posts: 13

Re: mousepad problem

when locale is posix or C, mousepad works fine. But if the locale is set to chinese: zh_CN.UTF-8, mousepad display with ugly mess as if it omitted redrawing the contents.

Offline

#5 2022-01-17 12:15:15

renshijun
Member
Registered: 2022-01-17
Posts: 13

Re: mousepad problem

when I logout xfce4 session and enter an openbox session, even locale set to zh_CN.UTF-8, mousepad works fine. 

If I unchecked the compositor in xfce4 and start runing picom, mousepad works fine in xfce4.

Offline

#6 2022-01-17 12:38:33

Tamaranch
Member
Registered: 2020-12-31
Posts: 93

Re: mousepad problem

This seems to be a bug in GTK 3 - GSV 4.
You should be able to reproduce the problem with Gedit for example, which also uses these libraries.

With GTK 3.24.31 and GSV 4.8.2 on Arch Linux, it's much less serious for me than what you show on your screenshot, but I still have a kind of blinking of the view when the window loses then regains focus.
It is especially visible if the "Display whitespace" option is enabled.

However, I can't reproduce the problem with gnome-text-editor which uses GTK 4 - GSV 5, nor with an experimental branch of Mousepad which also uses GTK 4 - GSV 5.

As for what you say about the window manager and the compositor, I can't reproduce it, but it may temper the problem without fixing it: I'm still convinced that it comes from GTK 3 - GSV 4.
I'll open an issue about this a little later upstream and put the link here.

Last edited by Tamaranch (2022-01-17 12:43:06)

Offline

#7 2022-01-17 13:16:00

renshijun
Member
Registered: 2022-01-17
Posts: 13

Re: mousepad problem

@Tamaranch thank you for your reply.

I just tested and found that when I press: 1 enter, 2 enter, 3 enter, ......

from 1 to 8, the mess remains. when I press 9 enter and no matter what I types afterwards, mousepad works fine.

Offline

#8 2022-01-17 13:39:06

renshijun
Member
Registered: 2022-01-17
Posts: 13

Re: mousepad problem

renshijun wrote:

@Tamaranch thank you for your reply.

I just tested and found that when I press: 1 enter, 2 enter, 3 enter, ......

from 1 to 8, the mess remains. when I press 9 enter and no matter what I types afterwards, mousepad works fine.

It can be called: eight line messing problem.

Offline

#9 2022-01-17 15:40:41

Tamaranch
Member
Registered: 2020-12-31
Posts: 93

Re: mousepad problem

Tamaranch wrote:

I'll open an issue about this a little later upstream and put the link here.

See https://gitlab.gnome.org/GNOME/gtk/-/issues/4646

renshijun wrote:

I just tested and found that when I press: 1 enter, 2 enter, 3 enter, ......
from 1 to 8, the mess remains. when I press 9 enter and no matter what I types afterwards, mousepad works fine.

Wouldn't this coincide with the appearance of the vertical scrollbar?
If you change the size of the window, does the number of lines at which the problem disappears vary?

Offline

#10 2022-01-18 00:06:39

renshijun
Member
Registered: 2022-01-17
Posts: 13

Re: mousepad problem

Tamaranch wrote:
Tamaranch wrote:

I'll open an issue about this a little later upstream and put the link here.

See https://gitlab.gnome.org/GNOME/gtk/-/issues/4646

renshijun wrote:

I just tested and found that when I press: 1 enter, 2 enter, 3 enter, ......
from 1 to 8, the mess remains. when I press 9 enter and no matter what I types afterwards, mousepad works fine.

Wouldn't this coincide with the appearance of the vertical scrollbar?
If you change the size of the window, does the number of lines at which the problem disappears vary?

yes, it is. when I type enough lines to trigger scrolling, mess disappears.

Offline

#11 2022-01-18 05:30:07

renshijun
Member
Registered: 2022-01-17
Posts: 13

Re: mousepad problem

The mousepad mess problem have been solved by downgrading xfwm4-4.16.1 to xfwm4-4.14.5.  @Tamaranch

Offline

#12 2022-01-18 05:45:50

renshijun
Member
Registered: 2022-01-17
Posts: 13

Re: mousepad problem

If replace the compositor.h and compositor.c in xfwm4-16 with the same name files in  xfwm4-14, compiling error appears:

compositor.c:1581:72: note: expected 'GLXPixmap' {aka 'long unsigned int'} but argument is of type 'GLXDrawable *' {aka 'long unsigned int *'}
compositor.c:1582:35: error: assignment to expression with array type
1582 |         screen_info->glx_drawable = None;
      |                                   ^
compositor.c: In function 'unredirect_win':
compositor.c:1955:76: error: 'DisplayInfo' {aka 'struct _DisplayInfo'} has no member named 'composite_mode'
1955 | iteUnredirectWindow (display_info->dpy, cw->id, display_info->composite_mode);
      |                                                             ^~

compositor.c: In function 'compositorIsUsable':
compositor.c:3983:26: error: 'DisplayInfo' {aka 'struct _DisplayInfo'} has no member named 'composite_mode'
3983 |     else if (display_info->composite_mode != CompositeRedirectManual)
      |                          ^~
compositor.c: In function 'compositorInitDisplay':
compositor.c:4370:17: error: 'DisplayInfo' {aka 'struct _DisplayInfo'} has no member named 'composite_mode'
4370 |     display_info->composite_mode = 0;
      |                 ^~
compositor.c: In function 'compositorSetCompositeMode':
compositor.c:4395:21: error: 'DisplayInfo' {aka 'struct _DisplayInfo'} has no member named 'composite_mode'
4395 |         display_info->composite_mode = CompositeRedirectManual;
      |                     ^~
compositor.c:4399:21: error: 'DisplayInfo' {aka 'struct _DisplayInfo'} has no member named 'composite_mode'
4399 |         display_info->composite_mode = CompositeRedirectAutomatic;
      |                     ^~
compositor.c: In function 'compositorManageScreen':
compositor.c:4462:86: error: 'DisplayInfo' {aka 'struct _DisplayInfo'} has no member named 'composite_mode'
4462 | windows (display_info->dpy, screen_info->xroot, display_info->composite_mode);
      |                                                             ^~

compositor.c:4465:21: error: 'DisplayInfo' {aka 'struct _DisplayInfo'} has no member named 'composite_mode'
4465 |     if (display_info->composite_mode == CompositeRedirectAutomatic)
      |                     ^~
compositor.c:4544:35: error: assignment to expression with array type
4544 |         screen_info->glx_drawable = None;
      |                                   ^
compositor.c: In function 'compositorUnmanageScreen':
compositor.c:4729:49: error: 'DisplayInfo' {aka 'struct _DisplayInfo'} has no member named 'composite_mode'
4729 |                                     display_info->composite_mode);
      |                                                 ^~
make[2]: *** [Makefile:723: xfwm4-compositor.o] Error 1
make[2]: Leaving directory '/var/cache/scratchpkg/work/xfwm4/src/xfwm4-4.16.1/src'
make[1]: *** [Makefile:510: all-recursive] Error 1
make[1]: Leaving directory '/var/cache/scratchpkg/work/xfwm4/src/xfwm4-4.16.1'
make: *** [Makefile:442: all] Error 2
==> ERROR: Build 'xfwm4-4.1614.1-1' failed.

Offline

#13 2022-01-18 10:49:25

Tamaranch
Member
Registered: 2020-12-31
Posts: 93

Re: mousepad problem

I think there is something specific in your configuration, related to the window manager, that adds to the problem, but is not the primary cause.

Changing the window manager or its version doesn't change anything for me: the flickering problem I reported upstream remains.

As for tinkering with the xfwm4 code, that's a whole other topic, so please don't pursue that in this thread smile

Offline

Board footer

Powered by FluxBB