**Steps to reproduce** 1: open Geany 2: open two different txt-documents, both very long, so that only two tabs exist 3: close Geany 4: reopen Geany (result: the txt-document what is in focus is shown correctly) 5: switch to the other tab where the other txt-document is located
**Result** The problem is that this happens only sometimes and one need to scroll to look for double lines (I did all the steps above about 20 times): The txt-document is not shown correctly. Some lines of the document are shown 2x. What is also strange is that the cursor is stretched over two lines. Once I saw lines not only 2x but 4x.
![screen-2022-08-31-20-18-30](https://user-images.githubusercontent.com/68117017/187753179-bd522db8-ebe8-4...)
**Remark** This is really a big issue. It started some weeks ago. I thought that it was caused by the plugin Geany Preview or by using Geany by PPA (https://github.com/xiota/geany/issues/2 and https://github.com/xiota/geany/issues/3). But today I reinstalled Lubuntu 22.04, I installed Geany, I installed geany-plugins, I installed some software for kvantum for having the dark mode, and I used Sleepy Pastel as colorschemes in Geany. And then the issue was there again. I can't remember that I saw this issue in Geany 1.37.
Lubuntu 22.04 Geany 1.38
The issue disappears when during the Geany session `View`>`Show Line Numbers` will be activated. By deactivating it again, the issue does not appear any more in the Geany session. Same for `Document`>`Line Wrapping`.
I think that the issue only appears when `Document`>`Line Wrapping` is activated.
Can't reproduce with latest Git Geany. Can you try that, the Scintilla has changed significantly.
Possibly #2559 and #1521 duplicate which reference https://sourceforge.net/p/scintilla/bugs/1949/ where it appears changes were made for GTK2 but no changes for GTK3 even though Colomban confirmed it occurs with GTK3, but rarely.
If you can confirm it with Geany git version or latest Scite then please report to Scintilla referencing this issue.
I can't reproduce my own report. But it happened once. And I made a screenshot. And it happened always when I was using Geany 1.39 by PPA with the plugin Geany Preview and with two lua-scripts.
I can't reproduce https://github.com/geany/geany/issues/2559, because in my case in the moment where line numbers are visible, then the issue does not exist. I can't reproduce https://github.com/geany/geany/issues/1521. And I can't confirm the description. In my case the issue didn't happen when I was typing. The issue appeared when I was scrolling.
If you can confirm it with Geany git version or latest Scite then please report to Scintilla referencing this issue.
I don't know how to install Geany git version or latest Scite. But I will report it to Scintilla.
I just reported the bug at https://sourceforge.net/p/scintilla/bugs/2349/.
One comment on sourceforge.net is:
I have seen this rarely. A possibility is that buffered drawing is on and that an error in the drawing code causes return to the by-line loop without any new drawing into the buffer bitmap. Then the previous line's image is drawn onto the new line. You could turn off buffered drawing (SCI_SETBUFFEREDDRAW) if it is on to check this - I don't know if Geany supports changing this setting.
Another possibility is that there is a bug in the line wrap positions so that the same subline is present twice.
Is there a possibility to turn off buffered drawing (SCI_SETBUFFEREDDRAW) in Geany?
You could comment out the ifdefs [here](https://github.com/geany/geany/blob/5cdfe35cf26ca6935eddc652cceb799e0cbad142...) so it happens on all platforms and GTK versions to see if it fixes it.
You could comment out the ifdefs [here](https://github.com/geany/geany/blob/5cdfe35cf26ca6935eddc652cceb799e0cbad142...) so it happens on all platforms and GTK versions to see if it fixes it.
Do you mean like this? ``` /*#ifdef GDK_WINDOWING_QUARTZ*/ /*# if ! GTK_CHECK_VERSION(3,16,0)*/ /* "retina" (HiDPI) display support on OS X - requires disabling buffered draw * on older GTK versions */ /*SSM(sci, SCI_SETBUFFEREDDRAW, 0, 0);*/ /*# endif*/ /*#endif*/ ``` And what are the disadvantages when it is turned off?
Do you mean like this?
Almost, leave the SSM line uncommented, thats the one that turns it off.
And what are the disadvantages when it is turned off?
Probably none on current platforms.
https://www.scintilla.org/ScintillaDoc.html#SCI_SETBUFFEREDDRAW
Almost, leave the SSM line uncommented, thats the one that turns it off.
To avoid misunderstanding: Is the following correct? ``` /*#ifdef GDK_WINDOWING_QUARTZ*/ /*# if ! GTK_CHECK_VERSION(3,16,0)*/ /* "retina" (HiDPI) display support on OS X - requires disabling buffered draw * on older GTK versions */ SSM(sci, SCI_SETBUFFEREDDRAW, 0, 0); /*# endif*/ /*#endif*/ ```
Correct.
Can't reproduce with latest Git Geany. Can you try that, the Scintilla has changed significantly.
Today I reinstalled Lubuntu 22.04, and I did ``` sudo apt update sudo apt dist-upgrade sudo add-apt-repository ppa:xiota/geany-plugins sudo apt update sudo apt install geany-git ``` In Geany I did only this: I activated in both txt-documents: Document>Line Wrapping.
The issue is still there (the stretched cursor is just before the word github):
![screen-2022-09-04-11-33-06](https://user-images.githubusercontent.com/68117017/188307372-98ee2708-a661-4...)
Please post the lines of `Help->Debug Messages` that list Geany version, GTK and Glib versions.
Please post the lines of Help->Debug Messages that list Geany version, GTK and Glib versions.
``` 12:20:14.967704: Geany INFO : Geany 1.39, unknown 12:20:14.967743: Geany INFO : GTK 3.24.33, GLib 2.72.1 ```
As comparion: In FeatherPad 1.0.1 it is shown correctly (the cursor is not stretched just before the word github):
![screen-2022-09-04-12-24-58](https://user-images.githubusercontent.com/68117017/188308823-ef45e4b9-4d5b-4...)
In Geany I did only this: I activated in both txt-documents: Document>Line Wrapping.
Did you make the changes discussed [here](https://github.com/geany/geany/issues/3271#issuecomment-1236121036)?
Did you make the changes discussed https://github.com/geany/geany/issues/3271#issuecomment-1236121036?
I don't know how to to build and change a geany-git, so asked here for a help: https://github.com/xiota/geany/issues/2#issuecomment-1236301587
Ahh it wasn't a source repository, so I guess you can't change it.
Why not build from the [nightly tarball](https://download.geany.org/geany_git.tar.gz) in accordance with [these instructions](https://github.com/geany/geany#installing-from-a-release-tarball)
Why not build from the [nightly tarball](https://download.geany.org/geany_git.tar.gz) in accordance with [these instructions](https://github.com/geany/geany#installing-from-a-release-tarball)
Well, I can try. Should I not remove geany first, and if yes, with kind of command?
To the following commands: Should I not write something behind the commands, like `geany_git.tar.gz`?
``` $ ./configure $ make (as root, or using sudo) % make install ```
I'm just a software user. I never built a software before.
Oh, ok, for some reason I thought you had built Geany before, so thanks in advance.
You will need some tools, I'm not sure of the commands on Ubuntu, I use Synaptic to install them, `build-essential` and the `libgtk-3-dev` development packages. Don't bother with the tools to build the manual, see the extra option on the `configure` command below.
Ok, create a directory in your home, say `geany_build` and untar the nightly tarball there. I think it will create a directory called `geany_git` so cd to it then:
``` ./configure --prefix=/the/full/path/to/home/geany_build --disable-html-docs make install cd ../bin ./geany -c ../config ```
This will build an isolated version of geany and run it with its own config, so it won't touch your system install or your user config, so you can play to your hearts content :-)
And just delete the whole directory tree `geany_build` to remove it when done.
I suggest you build it from the tarball first and confirm the problem still occurs, then comment out the parts of `src/editor.c` using an editor, might I suggest Geany (your newly built version ;-) run `make install` again and see if it makes any difference (don't forget to cd back and forward to the right directory `geany-git` to run `make install` and `bin` to run `./geany -c ../config`.
this is what I did in Lubuntu 22.04:
``` sudo apt install build-essential sudo apt install libgtk-3-dev ```
(Note: change the expression USERFILE to user name)
in /home/USERFILE I created the file `geany_build`
then I downloaded the nightly tarball from https://download.geany.org/geany_git.tar.gz then I untared the nightly tarball called `geany_git.tar.gz`; then I copied the content of the untared geany_git in the file `geany_build`
in the terminal I went into the content of geany_build by the command `cd geany_build`
then I did this: `./configure --prefix=/home/USERFILE/geany_build --disable-html-docs` the answer is: `bash: ./configure: No such file or directory`
If you use `geany_git.tar.gz`, you must call `./autogen.sh` before `./configure` (for release tarballs this step is not required).
in the terminal I went into the content of geany_build by the command `cd geany_build`
then I did this: `./autogen.sh` The answer is: ``` **Warning**: I am going to run `configure' with no arguments. If you wish to pass any to it, please specify them on the `./autogen.sh' command line.
Processing configure.ac ./autogen.sh: 33: autoreconf: not found ``` then I did this: `./configure --prefix=/home/USERFILE/geany_build --disable-html-docs` the answer is: `bash: ./configure: No such file or directory`
As mentioned in the [README](https://github.com/geany/geany#using-autotools), you need to install a few build time dependencies:
autopoint, automake, autoconf, libtool, gettext
OK, this what I did: ``` sudo apt install autopoint sudo apt install automake sudo apt install autoconf sudo apt install libtool sudo apt install gettext ``` `Install [...] and the GLib development files` What is the command for that?
The GLib development files already have been installed as dependencies of `libgtk-3-dev`.
You should now be able to run `.autogen.sh`.
in the terminal I went into the content of geany_build by the command `cd geany_build`
then I did: `.autogen.sh`
The answer: `.autogen.sh: command not found`
Not sure why it doesn't exist for you, I just checked it *is* included in https://download.geany.org/geany_git.tar.gz.
autogen.sh is there
Ah, sorry it was ./autogen.sh
I forgot the slash.
Ah, it must be `./autogen.sh` of course. I guess this was my typo above, sorry.
Background: `./` in front of a command tells the shell to look for the command following this sequence in the current directory. Linux shells do *not* consider the current directory for looking up commands to be executed by default.
How can I remove the geany version that I downloaded with `sudo apt install geany` to be sure, that the new geany is running?
How can I remove the geany version that I downloaded with
sudo apt install geany to be sure, that the new geany is running?
I found an easy solution: I will reinstall Lubuntu.
Or just `apt remove geany`
To be sure which version of Geany is running, you can check Help->Debug Messages, there are the system paths logged which the current instance use. These should match with your installation prefix passed to `./configure`.
I reinstalled Lubuntu, but this time the installation of Geany nightly tarball failed. This is what I did: this is the step-by-step-description how to install Geany from the nightly tarball in Lubuntu 22.04:
``` sudo apt install build-essential sudo apt install libgtk-3-dev sudo apt install autopoint sudo apt install automake sudo apt install autoconf sudo apt install libtool sudo apt install gettext ```
(Note: change the expression USERFILE to user name)
in /home/USERFILE create the file `geany_build`
then download the nightly tarball from https://download.geany.org/geany_git.tar.gz
then untar the nightly tarball called `geany_git.tar.gz` in the file `geany_build`
so, in the file `geany_build` there is the file `geany_git`
then in the terminal go to the content of geany_build by the command `cd geany_build` then in the terminal go to the content of geany_git by the command `cd geany_git`
then do this in the terminal: ``` ./autogen.sh ./configure --prefix=/home/USERFILE/geany_build --disable-html-docs sudo make make install cd ../bin ./geany -c ../config ```
Already for `sudo make` there seemed to be a problem: ``` sciwrappers.c: In function ‘sci_set_lexer’: sciwrappers.c:679:9: warning: ‘LexerNameFromID’ is deprecated [-Wdeprecated-declarations] 679 | ILexer5 *lexer = CreateLexer(LexerNameFromID(lexer_id)); | ^~~~~~~ In file included from sciwrappers.c:38: ../scintilla/lexilla/include/Lexilla.h:91:47: note: declared here 91 | DEPRECATE_DEFINITION const char *LEXILLA_CALL LexerNameFromID(int identifier); | ^~~~~~~~~~~~~~~ ```
And same for `sudo make install`: ``` libtool: warning: relinking 'classbuilder.la' mv: cannot move 'classbuilder.so' to 'classbuilder.soU': Permission denied libtool: error: error: relink 'classbuilder.la' with the above command before installing it make[2]: *** [Makefile:629: install-pluginLTLIBRARIES] Error 1 make[2]: Leaving directory '/home/t/geany_build/geany_git/plugins' make[1]: *** [Makefile:911: install-am] Error 2 make[1]: Leaving directory '/home/t/geany_build/geany_git/plugins' make: *** [Makefile:590: install-recursive] Error 1 ```
What should I do? What did I do wrong this time?
./autogen.sh ./configure --prefix=/home/USERFILE/geany_build --disable-html-docs sudo make make install cd ../bin ./geany -c ../config
`make` must be called as and if at all only `make install` with `sudo`. But since you install into your home directory, you don't need `sudo` at all.
sciwrappers.c: In function ‘sci_set_lexer’: sciwrappers.c:679:9: warning: ‘LexerNameFromID’ is deprecated [-Wdeprecated-declarations] 679 | ILexer5 *lexer = CreateLexer(LexerNameFromID(lexer_id)); | ^~~~~~~ In file included from sciwrappers.c:38: ../scintilla/lexilla/include/Lexilla.h:91:47: note: declared here 91 | DEPRECATE_DEFINITION const char *LEXILLA_CALL LexerNameFromID(int identifier); | ^~~~~~~~~~~~~~~
This is a harmless warning, can be ignored.
libtool: warning: relinking 'classbuilder.la' mv: cannot move 'classbuilder.so' to 'classbuilder.soU': Permission denied libtool: error: error: relink 'classbuilder.la' with the above command before installing it make[2]: *** [Makefile:629: install-pluginLTLIBRARIES] Error 1 make[2]: Leaving directory '/home/t/geany_build/geany_git/plugins' make[1]: *** [Makefile:911: install-am] Error 2 make[1]: Leaving directory '/home/t/geany_build/geany_git/plugins' make: *** [Makefile:590: install-recursive] Error 1
This is a follow-up error because `make` was executed with `sudo`.
Best you clean up your environment and try again.
Use `sudo chown -R t:t /home/t/geany_build/geany_git` (assuming "t" is your username). Afterwards run `make` and `make install` again.
Use sudo chown -R t:t /home/t/geany_build/geany_git (assuming "t" is your username). Afterwards run make and make install again.
Now Geany works. Thank you for your help.
This is the step-by-step-description how to install Geany from the nightly tarball in Lubuntu 22.04:
``` sudo apt install build-essential sudo apt install libgtk-3-dev sudo apt install autopoint sudo apt install automake sudo apt install autoconf sudo apt install libtool sudo apt install gettext ```
(Note: change the expression USERFILE to user name)
in /home/USERFILE create the file `geany_build`
then download the nightly tarball from https://download.geany.org/geany_git.tar.gz
then untar the nightly tarball called `geany_git.tar.gz` in the file `geany_build`
so, in the file `geany_build` there is the file `geany_git`
then in the terminal go to the content of geany_build by the command `cd geany_build` then in the terminal go to the content of geany_git by the command `cd geany_git`
then do this in the terminal: ``` ./autogen.sh ./configure --prefix=/home/USERFILE/geany_build --disable-html-docs make make install cd ../bin ./geany -c ../config
The issue is still there:
![screen-2022-09-04-18-36-49](https://user-images.githubusercontent.com/68117017/188323918-b2067765-b678-4...)
In the editor FeatherPad I replaced in `src/editor.c` this code
``` #ifdef GDK_WINDOWING_QUARTZ # if ! GTK_CHECK_VERSION(3,16,0) /* "retina" (HiDPI) display support on OS X - requires disabling buffered draw * on older GTK versions */ SSM(sci, SCI_SETBUFFEREDDRAW, 0, 0); # endif #endif ```
by this code:
``` /*#ifdef GDK_WINDOWING_QUARTZ*/ /*# if ! GTK_CHECK_VERSION(3,16,0)*/ /* "retina" (HiDPI) display support on OS X - requires disabling buffered draw * on older GTK versions */ SSM(sci, SCI_SETBUFFEREDDRAW, 0, 0); /*# endif*/ /*#endif*/ ```
Then I saved the document. I closed the document in the editor.
In the terminal I did: ``` cd geany_build cd geany_git make install cd ../bin ./geany -c ../config ```
The issue is not there any more. I will report this also at https://sourceforge.net/p/scintilla/bugs/2349/.
Document>Line Wrapping is activated
Now there are two new disadvantages: - there is an empty line where I can't even place the cursor (between 15 and 16) - if I navigate on the keyboard with the key arrow-down from line 13 to 16, the cursor will stop at line 15 at the end of the line; even if I press again many times the key arrow-down, the cursor will not move (but navigating with the key arrow-up from line 17 to line 13, then there are no problems)
![screen-2022-09-04-19-27-02](https://user-images.githubusercontent.com/68117017/188326246-8692c22e-82d2-4...)
I think that all the problems are because the line stops at the right border. One reason could be that there is not enough place for the wrapping-symbol on the right side.
Should I do some other tests? I ask this question because I would like to reinstall Lubuntu in the next days.
If you use geany_git.tar.gz, you must call ./autogen.sh before ./configure (for release tarballs this step is not required).
@eth16, I didn't know this, the point of using the tarball was to save @ralf3u installing autofools, if the nightly tarball needs the full toolset might as well have cloned git, sorry @ralf3u
@ralf3u best to report the strange blank line behaviour to Scintilla as well, it might help narrow down the problem. And looks like Neil thinks you are a developer too, giving you patches to try in Scintilla ;-)
I would like to make some remarks to this issue before reporting to Scintilla.
The issue appears **ONLY** if Document>Line Wrapping is activated. I recognized today that there are three variations of the issue: 1. short line, so the text does not go to the right border (that means that one can still add some words in the line) (image from https://github.com/xiota/geany/issues/2#issuecomment-1233148860)
![1](https://user-images.githubusercontent.com/68117017/188452903-af065f90-cac4-4...)
2. last line of a paragraph (image from https://github.com/xiota/geany/issues/2#issuecomment-1226190192)
![2](https://user-images.githubusercontent.com/68117017/188452997-3c9a54c5-dbe8-4...)
3. line goes to the right border (image from https://github.com/geany/geany/issues/3271#issuecomment-1236386886)
![3](https://user-images.githubusercontent.com/68117017/188453168-725190e8-5a22-4...)
In the nightly tarball I can not confirm 1 and 2, so 1 and 2 seem to be solved. But I have to check 1 and 2 with the plugin Geany Preview and two-lua-scripts what I will do in the next days if 1 and 2 were really solved. Geany by PPA was also built yesterday (https://github.com/xiota/geany/issues/2#issuecomment-1236227970).
to point 3: to reproduce the issue: this line in a 22-inch-display in Full HD with a brand new Geany: `>You could comment out the ifdefs [here](https://github.com/geany/geany/blob/5cdfe35cf26ca6935eddc652cceb799e0cbad142...) so it happens on all platforms and GTK versions to see if it fixes it.`
The empty line and the two disadvantages of https://github.com/geany/geany/issues/3271#issuecomment-1236386886 occur **ONLY** if an other tab with a txt-document is right away in focus after a restart of Geany. In other words: If the tab of the corresponding txt-document is right away in focus after a restart of Geany, then there is no issue. Because of that, I think that not Scientilla is the problem, but Geany, but maybe I'm wrong.
What do you think about that?
In the nightly tarball I can not confirm 1 and 2, so 1 and 2 seem to be solved.
Is that with or without the changes of https://github.com/geany/geany/issues/3271#issuecomment-1236382367?
I doubt that the plugins will have any effect.
Geany by PPA was also built yesterday
Thanks to @xiota, but please keep using the Geany made from the tarball, you can make changes to that.
Because of that, I think that not Scintilla is the problem, but Geany, but maybe I'm wrong.
What do you think about that?
To be clear, the whole display of the edit window is Scintilla control, its unlikely it will be anything Geany did, initial focus is just passed to Scintilla, so if it is in fact having an effect it will still be in Scintilla. Do pass _all_ the observations you have made above on to Scintilla though, as I said before anything you can provide to help may make it easier to narrow down the cause or make it easier for Neil to reproduce the problem.
@ralf3u thanks again for your effort here, since nobody else with Geany has managed to reproduce it with the current GIt (or they are not saying so) there is not much we can do to help, and its up to you to help Neil.
Is that with or without the changes of https://github.com/geany/geany/issues/3271#issuecomment-1236382367?
without the changes
I doubt that the plugins will have any effect.
I could reproduce 1 and 2 every time with the plugin Geany Preview and two lua-scripts.
Thanks to @xiota, but please keep using the Geany made from the tarball, you can make changes to that.
OK.
[...] and its up to you to help Neil.
From now on I will continue to report the issue at Scintilla, so I don't need to report it twice. But I let this issue at github open till there is a result at sourceforge. If you have a better handling, just let it me know.
Neil said:
Run the application inside a debugger. When the problem occurs, break into the debugger and examine the state of the line wrap positions.
How should I run Geany in a debugger? Do I have to install a debugger? And how can I break into the debugger? Thank you in advance for an answer.
@elextr and @eht16: Hey, that's too complicated to work with a debugger for me. I have an alternative: I could try to reproduce it on a 15.6-inch-FHD-notebook on Lubuntu-Live-ISO with Geany installed by PPA (that uses geany-git from last Sunday), with two txt-documents. I could then upload the two txt-documents so that you could see the bug and work on it with Neil.
Are you using a 15.6-inch-Full HD-display notebook?
I had this issue almost a year ago, but it was transient. I thought it was fixed with a scintilla update. I am not able to reproduce it now with Lubuntu 22.04 in a VM.
@ralf3u It's my understanding that this occurs on only one of your computers? If so, would you please provide specs. CPU, GPU, RAM, display resolution.
@xiota thanks for trying, IIUC GFX in a VM is different to GFX in a bare metal OS, so that might be why it doesn't happen, or as you said maybe its hardware specific, or it could be X11 vs Wayland specific, or maybe GTK version, so many moving parts :-(.
Like you I can confirm I saw the repeated lines a while ago and then it went away, but I also can't reproduce it now, or the end of line thing.
@ralf3u do you have Geany full screen? If not the display size and resolution shouldn't matter. If you are doing it full screen please try it in a window sized so the end of line falls at the edge.
@xiota and @elextr
Thank you for your help. Neil accepted to try to run a Live ISO Lubuntu. So I would like to continue first with him.
The step-by-step-description is now online how to see the bug:
https://sourceforge.net/p/scintilla/bugs/2349/#05d7
@ralf3u What resolution are you using on each computer? `xrandr --current` should give the resolution and how the monitor is connected.
What GPU and driver are you using on each computer? Use `lspci -v`, and look for "VGA compatible controller". The kernel module should also be listed there.
Since window managers do compositing, the mesa driver could be relevant: `glxinfo | grep -i opengl`. Also, see if the bug occurs if you run `LIBGL_ALWAYS_SOFTWARE=true geany`.
desktop-PC with 22´´-Full-HD-display `xrandr --current`: ``` Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 476mm x 268mm 1920x1080 60.00*+ 50.00 59.94 1920x1080i 60.00 50.00 59.94 1600x900 60.00 1280x1024 75.02 60.02 1152x864 75.00 1280x720 60.00 50.00 59.94 1024x768 75.03 60.00 800x600 75.00 60.32 720x576 50.00 720x576i 50.00 720x480 60.00 59.94 720x480i 60.00 59.94 640x480 75.00 60.00 59.94 720x400 70.08 DP-1 disconnected (normal left inverted right x axis y axis) ```
`lspci -v`: ``` 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03) DeviceName: Onboard - Other Flags: bus master, fast devsel, latency 0
00:00.3 System peripheral: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor Gaussian Mixture Model Flags: fast devsel, IRQ 23 Memory at a1330000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: <access denied>
00:02.0 VGA compatible controller: Intel Corporation GeminiLake [UHD Graphics 605] (rev 03) (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: Micro-Star International Co., Ltd. [MSI] GeminiLake [UHD Graphics 605] Flags: bus master, fast devsel, latency 0, IRQ 125 Memory at a0000000 (64-bit, non-prefetchable) [size=16M] Memory at 90000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915
00:0e.0 Audio device: Intel Corporation Celeron/Pentium Silver Processor High Definition Audio (rev 03) DeviceName: Onboard - Sound Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor High Definition Audio Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a1310000 (64-bit, non-prefetchable) [size=16K] Memory at a1000000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci_intel_apl
00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor Trusted Execution Engine Interface Flags: bus master, fast devsel, latency 0, IRQ 126 Memory at a132f000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: mei_me Kernel modules: mei_me
00:12.0 SATA controller: Intel Corporation Celeron/Pentium Silver Processor SATA Controller (rev 03) (prog-if 01 [AHCI 1.0]) DeviceName: Onboard - SATA Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor SATA Controller Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 124 Memory at a1314000 (32-bit, non-prefetchable) [size=8K] Memory at a132e000 (32-bit, non-prefetchable) [size=256] I/O ports at f090 [size=8] I/O ports at f080 [size=4] I/O ports at f060 [size=32] Memory at a132d000 (32-bit, non-prefetchable) [size=2K] Capabilities: <access denied> Kernel driver in use: ahci Kernel modules: ahci
00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 120 Bus: primary=00, secondary=05, subordinate=05, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: a1200000-a12fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport
00:13.3 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 121 Bus: primary=00, secondary=06, subordinate=06, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: a1100000-a11fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport
00:15.0 USB controller: Intel Corporation Celeron/Pentium Silver Processor USB 3.0 xHCI Controller (rev 03) (prog-if 30 [XHCI]) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor USB 3.0 xHCI Controller Flags: bus master, medium devsel, latency 0, IRQ 123 Memory at a1300000 (64-bit, non-prefetchable) [size=64K] Capabilities: <access denied> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
00:16.0 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO I2C Host Controller (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor Serial IO I2C Host Controller Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at a132c000 (64-bit, non-prefetchable) [size=4K] Memory at a132b000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:16.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO I2C Host Controller (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor Serial IO I2C Host Controller Flags: bus master, fast devsel, latency 0, IRQ 28 Memory at a132a000 (64-bit, non-prefetchable) [size=4K] Memory at a1329000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:16.2 Signal processing controller: Intel Corporation Device 31b0 (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Device b171 Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at a1328000 (64-bit, non-prefetchable) [size=4K] Memory at a1327000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:16.3 Signal processing controller: Intel Corporation Device 31b2 (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Device b171 Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at a1326000 (64-bit, non-prefetchable) [size=4K] Memory at a1325000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Device b171 Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at a1324000 (64-bit, non-prefetchable) [size=4K] Memory at a1323000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:17.1 Signal processing controller: Intel Corporation Device 31b6 (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Device b171 Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at a1322000 (64-bit, non-prefetchable) [size=4K] Memory at a1321000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:17.2 Signal processing controller: Intel Corporation Device 31b8 (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Device b171 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at a1320000 (64-bit, non-prefetchable) [size=4K] Memory at a131f000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:17.3 Signal processing controller: Intel Corporation Device 31ba (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Device b171 Flags: bus master, fast devsel, latency 0, IRQ 34 Memory at a131e000 (64-bit, non-prefetchable) [size=4K] Memory at a131d000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:19.0 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO SPI Host Controller (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor Serial IO SPI Host Controller Flags: bus master, fast devsel, latency 0, IRQ 35 Memory at a131c000 (64-bit, non-prefetchable) [size=4K] Memory at a131b000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:19.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO SPI Host Controller (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor Serial IO SPI Host Controller Flags: bus master, fast devsel, latency 0, IRQ 36 Memory at a131a000 (64-bit, non-prefetchable) [size=4K] Memory at a1319000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:19.2 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO SPI Host Controller (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor Serial IO SPI Host Controller Flags: bus master, fast devsel, latency 0, IRQ 37 Memory at a1318000 (64-bit, non-prefetchable) [size=4K] Memory at a1317000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci
00:1f.0 ISA bridge: Intel Corporation Celeron/Pentium Silver Processor LPC Controller (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor LPC Controller Flags: bus master, medium devsel, latency 0
00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03) DeviceName: Onboard - Other Subsystem: Micro-Star International Co., Ltd. [MSI] Celeron/Pentium Silver Processor Gaussian Mixture Model Flags: medium devsel, IRQ 20 Memory at a1316000 (64-bit, non-prefetchable) [size=256] I/O ports at f040 [size=32] Kernel driver in use: i801_smbus Kernel modules: i2c_i801
05:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) DeviceName: Onboard - RTK Ethernet Subsystem: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] Flags: bus master, fast devsel, latency 0, IRQ 127 Memory at a1200000 (64-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: iwlwifi Kernel modules: iwlwifi
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: Micro-Star International Co., Ltd. [MSI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Flags: bus master, fast devsel, latency 0, IRQ 21 I/O ports at e000 [size=256] Memory at a1104000 (64-bit, non-prefetchable) [size=4K] Memory at a1100000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: r8169 Kernel modules: r8169 ``` `glxinfo | grep -i opengl`: I had to install mesa-utils first. Then: ``` OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 605 (GLK 3) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.5 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.0.5 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: ```
`LIBGL_ALWAYS_SOFTWARE=true geany`: the issue is there
To my last comment: I forgot to mention some information about Geany. So, here they are:
Geany INFO : Geany 1.38, en_US.UTF-8 Geany INFO : GTK 3.24.33, GLib 2.72.1 Geany INFO : OS: Ubuntu 22.04.1 LTS (jammy)
@xiota
What resolution are you using on each computer?
Today I wanted to upload the data of the 15.6´-FHD-notebook. But the bug could be reproduced (https://sourceforge.net/p/scintilla/bugs/2349/#498c). Do you still need the information?
No, I just thought additional info would be helpful for reproducing the issue. Since upstream is able to reproduce it, they can keep an eye out for a fix.
Today I saw a short line twice in the Geany-git by PPA that was built around 10 days ago, so the issue for short lines is still there. But I couldn't reproduce it. If I can reproduce it, I will mention it here and I will open a new issue at sourceforge.net.
When short lines starts to appear twice, then the top line of the editor is completely red (from the left border to the right border of the editor) for some seconds. A saw this behavior many times in the past.
Today I saw a short line twice (https://github.com/xiota/geany/issues/2#issuecomment-1246325734).
The issue of short lines and last lines of paragraphs disappears when buffered drawing (SCI_SETBUFFEREDDRAW) is turned off (https://github.com/xiota/geany/issues/2#issuecomment-1249414773 and https://github.com/xiota/geany/issues/2#issuecomment-1249501316).
@eht16 and @elextr
As I mentioned above in comment https://github.com/geany/geany/issues/3271#issuecomment-1236986241, there are three different issues: short lines, last lines of paragraphs and lines that are going till the right border.
For the lines that are going till the right border I opened already at sourceforge a new bug, because in the moment where buffered drawing (SCI_SETBUFFEREDDRAW) is turned off, there is an empty line and there is still a problem with the keyboard-navigation (https://sourceforge.net/p/scintilla/bugs/2349/#b6c6).
For short lines and last lines of paragraphs, I would like to open a new bug at sourceforge by mentioning those facts: - When buffered drawing (SCI_SETBUFFEREDDRAW) is turned on, then the issue occurs on the geany-git by PPA that was built about 16 days ago (https://github.com/xiota/geany/issues/2#issuecomment-1236227970) on two different computers five days ago (https://github.com/xiota/geany/issues/2#issuecomment-1248033244), on a 15.6´´-FHD-notebook and standalone PC connected to a 22´-display. - When buffered drawing (SCI_SETBUFFEREDDRAW) is turned off on the geany-git by PPA that was built about four days ago (https://github.com/xiota/geany/issues/2#issuecomment-1248808860), then the issue does not appear any more (https://github.com/xiota/geany/issues/2#issuecomment-1249414773 and https://github.com/xiota/geany/issues/2#issuecomment-1249501316).
Because of that: Is it OK if I ask at sourceforge to turn off buffered drawing (SCI_SETBUFFEREDDRAW) by default?
To my knowledge, I have not turned off SCI_SETBUFFEREDDRAW in my PPA builds. The recent build you refer to has removed for testing the `IS_WIDGET_MAPPED` check in `ScintillaGTK.cxx`, as suggested in [this comment](https://sourceforge.net/p/scintilla/bugs/2349/#bb06) on the scintilla bug report.
I have not turned off SCI_SETBUFFEREDDRAW in my PPA builds
Oh, I'm sorry. I thought it was the case.
The recent build you refer to has removed for testing the IS_WIDGET_MAPPED check in ScintillaGTK.cxx, as suggested in [this comment](https://sourceforge.net/p/scintilla/bugs/2349/#bb06) on the scintilla bug report. The patch follows: [...]
OK. In the next hours I will mention here the link to the new bug at sourceforge.
I just opened a new bug at sourceforge: https://sourceforge.net/p/scintilla/bugs/2354/
@xiota
Is the report OK?
I don't understand why a new bug report is necessary.
Are all of the line duplication issues resolved by removing the `IS_WIDGET_MAPPED` check?
Are all of the line duplication issues resolved by removing the IS_WIDGET_MAPPED check?
Yes. I couldn't see an issue any more.
I don't understand why a new bug report is necessary.
I thought that it they were different issues.
Unless scintilla devs asked you to open multiple bug reports, the problems seem closely related enough to fall under one report, especially if a single patch addresses all of them.
@xiota
Would it be possible to rebuild a geany-git with the new patch of https://sourceforge.net/p/scintilla/bugs/2349/?page=1#f567, so I can test it?
I could test the new patch only with Xorg because I think that Lubuntu does not use Wayland. Do you know an ISO distribution that uses Wayland?
The bug was fixed today at Scintilla (https://sourceforge.net/p/scintilla/bugs/2349/?page=1#e800).
Closed #3271 as completed.
github-comments@lists.geany.org