xournalpp / xournalpp

Xournal++ is a handwriting notetaking software with PDF annotation support. Written in C++ with GTK3, supporting Linux (e.g. Ubuntu, Debian, Arch, SUSE), macOS and Windows 10. Supports pen input from devices such as Wacom Tablets.
https://xournalpp.github.io
GNU General Public License v2.0
11.29k stars 804 forks source link

Bug when opening Xournal through Windows user interface - Hides pages and tools and/or changes textbox font to brackets font ([][][][]). #3207

Closed Aic-Ma closed 2 years ago

Aic-Ma commented 3 years ago

Affects versions :

Describe the bug The following bugs may happen, either partially in each case, independently, or simultaneously:

Option 1: Hides sidebar page review; Hides menu bar options; Hides main pages.

Option 2: Textbox font is changed to brackets. (eg: << Some textbox text >> might be changed to <<[][][][][][][][][][][][][][][][]>>

To Reproduce Steps to reproduce the behavior:

  1. Step 1: Find Xournal++ from the Windows user interface, or from the Window's search menu.
  2. Step 2: Open file

Expected behavior Open Xournal++ without Debug In pop up. Not hide menu bar options nor the sidebar page review nor the main document. Not encode texboxes with bracket notation.

Screenshots of Problem Document 1 image image

Document 2 Expected behaviour: image Variosu Error combinations. image image

A research on the Textbox Bracket Font Bug image

While working on the research 1 image While working on the research 2 image

Additional context

rolandlo commented 3 years ago

Please try version 1.1.0+dev and report if anything of these issues remain.

Aic-Ma commented 3 years ago

Please try version 1.1.0+dev and report if anything of these issues remain.

Hi @rolandlo . Tried to run the instructions from the WindowsBuild.md, but miserably failed getting the Build Step to work. Thus, I took the easier road of of using downloading the zip file xournalpp-1.1.0.dev-nightly.20210702-windows.zip from the Automated nighly build page. The problem unfortunately persists. The same as so far applies from the OP, with the exception that the Debug In pop up no longer appears.

I'm fully conscious the way to go was to follow the steps from the link provided, and that I somehow messed up on a step. Is there not a photo walkthrough on how to properly compile the setup?

Thanks for the previous answer, by the way.

rolandlo commented 3 years ago

I did not expect you to build Xournal++ from source. You wouldn't get a different result than from the automated nightly build, although of course it would offer more debugging options for you.

No, there is no photo walkthrough on how to compile the setup. If you report the error(s) in the Bulid step we may be able to help.

I'm quite puzzled by the bugs that you report. They have not been reported before, I believe, and I can't reproduce them. Can you share some info on the computer you are using and what Windows version you use? Is it Windows 10?

Aic-Ma commented 3 years ago

@rolandlo, sure, here is some relevant info. I will update the OP to include at least the full OS Name. Current Laptop: OS Name: Microsoft Windows 10 Home Version: 10.0.19041 Build 19041 System Model: 13U70P-G.ARW5U1 System Type: x64-based PC

But I had another computer, pretty much the same, except some 7 years old, which had the same issues, and I just verified downloading the stable version once again that the bug that changes certain settings to that of brackets is also there. Emphatically, the Debug In pop ups keeps appearing, and I the hidden interface bug after another couple of tries also shows up.

However, it may be that these are not fully independent cases. When switching to this newer device, I brought over much of my previous Xournal files, all which always mentioned the Debug In pop up. Therefore, I think this problem can also be due to a virus. I may be able to reset this old one as to see if it keeps happening on fresh settings, but I it will have to be not now but in a couple of days. Other Laptop: OS Name: Microsoft Windows 10 Home Version: 10.0.19043 Build 19043 System Model: SVP13215CDB System Type: x64-based PC

rolandlo commented 3 years ago

The Debug pop ups are to be expected in the stable release (version 1.0.20). The rest is unexpected. Consider uninstalling all Xournal++ versions, removing the contents of C:\Users\<username>\AppData\Local\xournalpp (that contains the settings file) and reinstalling Xournal++ 1.1.0+dev (from the zip-archive).

Aic-Ma commented 3 years ago

Hi, @rolandlo. I have done the steps twice now, the second time having both deleted my Local/xournalpp folder and my Local recent-files.xbel file. It's quite interesting to note both time the affected textbox setting after reopening the file has been Sans Normal 12 pt, which has been the settings I have first used on the file before having it saved and closed. As additional context, no other xournal file had been opened, and these were the first files done after having recently installed Xournal++ 1.1.0+dev from the zip-archive.

I'm running out of ideas here. What do you think we can do?

Thanks for keeping up with me by the way. Here is another picture of the most recent appearance of the bug. image

rolandlo commented 3 years ago

DEFAULT_FONT="Sans" and DEFAULT_FONT_SIZE=12 are hard-coded in Xournal++, so that part looks normal. Can you keep the task manager open and observe CPU and memory usage while you get those hidden pieces of the Journal? Seems your computer is lagging behind because it is overworked. Does other software work fluently at the same time?

Aic-Ma commented 3 years ago

@rolandlo, sorry I'm running late. I have not extensensively used other programs while having any of the bugs active in Xournal, but I did compared certain aspects, like running some live-script on Matlab, or just openning and closing them, while having the various bugs present. Here is a brief comparison of the computer's performance when the xournal is active presenting any or no bug: Performance Tests.

It struck me interesting no significant change seems to happen between the control (no bug) and test groups. The timing at Up time is such because more frequently than not I performed first the test with the bug and then the test without the bug. Airplane mode was adopted in the last tests to minimize interference coming from the wifi processes, although that was already unimportant.

By the way, I was surprised to find using the File -> Recent Documents option to open the file did brought the file with bugs in two occasions.

couldNOTcompute commented 2 years ago

General Information: OS: Microsoft Windows 10 Professional Hardware: i7-1165G7, 15,8 GB, NVMe SSD (as performance was put forward as a possible cause) Version of Xournal++: 1.1.0 Installation method: Official page

Describe the bug:

  1. Textbox font is changed to brackets. [][][][][][][][][][][][][][][][]
  2. (While trying to reproduce the first issue) When I open a file the window itself now has the bracket font, the textboxes inside are unaffected. This Issue varies quite a bit! I tried rebooting, upon first trying it did not produce the bracket font, but instead just the mix of English and German. Closing both windows and just reopening the preexisting file the brackets reappear (all 5 times I tried), opening another file just reverts back to the language mix.

To Reproduce:

  1. I was unable to find a pattern in the appearance of the issue. Hence, I can't provide a guide to reproduce.
  2. There too seems to be no real pattern. At first, I was able to reproduce the issue this way: (Language German) I have one window open an now open a second instance, by clicking a existing file, now the second Instance has the issue while the first is unaffected. Closing and opening the lather window fixes the problem, but now the menus are a strange mix of the en and ger versions.

Expected behavior Xournalpp should keep the font it is set too.

Additional Context:

Screenshot (1) Screenshot (2)

I'm sorry for that my report is a bit incoherent, but I'm pressed for time and just played around with the issue a bit and couldn't find any real pattern. But if you have anything you'd like to test me feel free to ask.

LittleHuba commented 2 years ago

This is caused by a wrong GTK backend. See #3534 Please refer to our nightlies for now or set the environment variable PANGOCAIRO_BACKEND to fc.