Just installed the 7.16 winehq-devel update and it went thru fine.
Afterwards did my normal wine notepad for root user to do the wine update for the new version.
Went thru fine, and notepad screen came up fine.
Then did the same for my regular user.
This time the notepad seemed to open a terminal window with a smaller white window that looked something like notepad.
Had to kill processes.
tried again, and it did same but terminal and white window was smaller.
killed processes again.
run other program and everything in it was fine.
tried notepad again, same issue.
ran winecfg and it seemed fine. Changed the dpi from 144 to 96
then tried notepad again. Still not working.
Found notepad.exe in C:\windows was the same as the one in system32?
renamed it to notepad.xxx and then did wine notepad and it opened correctly.
Then renamed the c:\windows\notepad.xxx back to notepad.exe and tried, and it worked fine??
change dpi back to 144, and it seems to run fine??
This happened on both my notebook and one of my desktop machines running winehq-devel. Others have the Fedora wine that is at 7.12.
So, not sure what issue is/was? and note sure which step actually fixed it, or why root user had no issue, but regular user did?
Machines running Fedora 35.
Thanks.
Strange issue with notepad after 7.16 update??
Re: Strange issue with notepad after 7.16 update??
Tried it again later, and problem was back??
Change DPI back to 96, and then it worked again.
Change DPI back to 144, and the notepad worked as well.
Seems the notepad in 7.16 doesn't like the DPI 144 at some point?
Don't really use notepad, but it was a quick way to have the update process work after a wine upgrade.
Never had issues before?
Change DPI back to 96, and then it worked again.
Change DPI back to 144, and the notepad worked as well.
Seems the notepad in 7.16 doesn't like the DPI 144 at some point?
Don't really use notepad, but it was a quick way to have the update process work after a wine upgrade.
Never had issues before?
Re: Strange issue with notepad after 7.16 update??
Bug 53601 - UI rendering broken for multiple applications (7-Zip, WinRAR, foobar2000, built-in apps) in Wine 7.16 at a non-default DPI
Made a bug report, but is was marked as dupe of 53601. Seems the have a fix if you build wine instead of using rpm.
Don't know a simpler way of doing fix.
diff --git a/dlls/user32/user_main.c b/dlls/user32/user_main.c
index bb728907b01..8332ff55871 100644
--- a/dlls/user32/user_main.c
+++ b/dlls/user32/user_main.c
@@ -222,8 +222,8 @@ static BOOL process_attach(void)
{
NtCurrentTeb()->Peb->KernelCallbackTable = kernel_callback_table;
- dpiaware_init();
winproc_init();
+ dpiaware_init();
/* Initialize system colors and metrics */
SYSPARAMS_Init();
So, seems to be an issue of the order of dpiaware_init from before winproc_init to after??
Made a bug report, but is was marked as dupe of 53601. Seems the have a fix if you build wine instead of using rpm.
Don't know a simpler way of doing fix.
diff --git a/dlls/user32/user_main.c b/dlls/user32/user_main.c
index bb728907b01..8332ff55871 100644
--- a/dlls/user32/user_main.c
+++ b/dlls/user32/user_main.c
@@ -222,8 +222,8 @@ static BOOL process_attach(void)
{
NtCurrentTeb()->Peb->KernelCallbackTable = kernel_callback_table;
- dpiaware_init();
winproc_init();
+ dpiaware_init();
/* Initialize system colors and metrics */
SYSPARAMS_Init();
So, seems to be an issue of the order of dpiaware_init from before winproc_init to after??