https://bugs.winehq.org/show_bug.cgi?id=41438
Bug ID: 41438
Summary: fastone image viewer 5.9 "crop" window do not show if
called by hotkey from full screen mode
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: unxed(a)mail.ru
Distribution: ---
steps to reproduce:
1. get faststone image viewer from here:
http://www.faststone.org/FSViewerDownload.htm
2. select any image
3. press "enter" to go to fullscreen mode
4. prexx "x" for crop properties window
5. the window will be shown in background, with no way to switch to it:
actually unusable
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=8028
tokktokk <fdsfgs(a)krutt.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fdsfgs(a)krutt.org
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45099
Bug ID: 45099
Summary: SetWindowPlacement doesn't restore the normal position
correctly
Product: Wine
Version: 3.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: vz-wine(a)zeitlins.org
Distribution: ---
Consider an application which calls GetWindowPlacement() on its main window to
store its geometry on exit and SetWindowPlacement() on startup to restore the
previously stored values. If the window of such application is maximized on
exit, then the window is correctly restored to the maximized state during the
next run, but restoring this window, i.e. returning it to the normal,
unmaximized state, doesn't restore it to the previous position (although it
does restore its size).
Here are some excerpts from the logs I see with WINEDEBUG=win for the last
execution:
0009:trace:win:WINPOS_SetPlacement 0x10050: setting min 0,0 max 0,55 normal
(3440,1910)-(3840,2160) flags 6 ajusted to min 0,0 max 0,55 normal
(3440,1910)-(3840,2160)
0009:trace:win:SetWindowPos hwnd 0x10050, after (nil), 3440,1910 (400x250),
flags 00000014
...
0009:trace:win:WINPOS_MinMaximize 0x10050 3
0009:trace:win:GetWindowPlacement 0x10050: returning min -1,-1 max 0,55 normal
(3440,1910)-(3840,2160)
0009:trace:win:GetWindowRect hwnd 0x10050 (3440,1910)-(3840,2160)
... I restore the window here ...
0009:trace:win:WINPOS_MinMaximize 0x10050 9
0009:trace:win:GetWindowPlacement 0x10050: returning min -1,-1 max 0,55 normal
(3440,1910)-(3840,2160)
... almost immediately after ...
0009:trace:win:USER_SetWindowPos status flags = 1807
0009:trace:win:GetWindowRect hwnd 0x10064 (3445,2119)-(3835,2155)
0009:trace:win:GetWindowRect hwnd 0x10064 (3445,2119)-(3835,2155)
0009:trace:win:GetWindowRect hwnd 0x10064 (3445,2119)-(3835,2155)
0009:trace:win:GetWindowRect hwnd 0x10050 (3440,1910)-(3840,2160)
0009:trace:win:SetWindowPos hwnd 0x10050, after (nil), 115,87 (400x250), flags
00000015
... when closing the program ...
0009:trace:win:GetWindowPlacement 0x10050: returning min -1,-1 max 0,55 normal
(115,87)-(515,337)
I.e. SetWindowPlacement() is passed the correct position (3440,1910
corresponding to the lower right corner), and even restoring it still uses the
same correct position, but then the window is somehow moved to the wrong
position (115,87) for some reason which I don't understand.
This is just a minor irritant, of course, but I'd still like to open this bug
just in case it's also simple to fix.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=6893
tokktokk <fdsfgs(a)krutt.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fdsfgs(a)krutt.org
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45107
Bug ID: 45107
Summary: Total Commander 8.01 crashes with GTK+3 theming
enabled
Product: Wine-staging
Version: 3.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bodqhrohro(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 61287
--> https://bugs.winehq.org/attachment.cgi?id=61287
stderr
Looks like it fails decorating the TreeView widget.
Theme: OneStepPlat.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45146
Bug ID: 45146
Summary: IBus not working properly for MS Word 2010 输入法工作不正常
Product: Wine
Version: 3.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: taisfmq(a)live.cn
Distribution: ---
OS: Fedora 27
Wine: 3.7 from dl.winehq.org
WINEARCH=win32
winetricks winxp
1. Install Word and MS Pinyin Input from official Office 2010 Chinese Volume
ISO 从中文版官方批量授权版ISO安装Word 2010和微软拼音输入法
2.a. Deactivate IME control in Word settings, and Western characters are
inputted flawlessly, but Chinese characters will be inputted after a delay via
IBus
取消勾选“选项”-“高级”-“输入法控制处于活动状态”,则IBus输入的字符将在下一个字符键入后才显示。例:键入ceshi<Space>,没有反应,再键入字符j,文档中出现“测试”二字,再键入ingya<Space>,没有反应,必须再键入一个英文字母才能输入“惊讶”二字。若键入完ceshi<Space>后键入数字或特殊字符,则“测试”二字不会被输入,必须重新键入拼音
2.b. Activate IME control in Word settings, Chinese characters can be inputted
without IBus, but the candidates list will not be displayed
勾选“选项”-“高级”-“输入法控制处于活动状态”,则将IBus调至英语语言后可正常输入中文,但微软拼音输入法的候选词窗口不会显示
3. There is no way to open MS Pinyin IME settings 不知道怎么开启微软拼音输入法的设置
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=5402
Kyle Auble <kyle.auble(a)zoho.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|kyle.auble(a)zoho.com |
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30762
Bug #: 30762
Summary: msxml3/domdoc tests flaky
Product: Wine
Version: 1.5.4
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msxml3
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Classification: Unclassified
ca48dac8821e128db8991dc54b4dedc8c321e816 and
9c0486d7a802c2f618a56a2074c5d790d329e3cf
both seem to have introduced some flaky tests in msxml3/domdoc.
Here's the result of 455 runs in a loop on ubuntu 12.04 (though I
also saw these on Centos 6):
342 domdoc.c:11537: Test failed: got L"http://blahblah.org"
342 domdoc.c:11542: Test failed: got L"http://blah.org"
350 domdoc.c:11647: Test failed: got L"http://blahblah.org"
350 domdoc.c:11652: Test failed: got L"http://blah.org"
3 domdoc.c:2098: Test failed: can't create file
C:\users\dank\Temp\leading_spaces.xml: 32
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=28578
Bug #: 28578
Summary: Editing a wiki page strips out carriage returns from
all preformatted text on that page
Product: WineHQ.org
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dimesio(a)earthlink.net
Classification: Unclassified
This most recently happened with the Regression Testing page (bug 28575), but
I've seen it before on other pages: carriage returns are removed from
preformatted text, even if that part is not edited directly, and the
preformatted text turns into an unreadable mess. It used to be possible to
avoid this by staying in GUI mode and not previewing, but that seems to no
longer work.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=33470
Bug #: 33470
Summary: Don't allow to create wiki pages with external links
Product: WineHQ.org
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dmitry(a)baikal.ru
CC: dimi(a)lattica.com
Classification: Unclassified
Just have a look at http://wiki.winehq.org/RecentChanges, it really starts
to take quite a bit of an effort to clean Wine wiki from spam.
Apparently, spammers can't be stopped by keywords listed in the stop list
http://wiki.winehq.org/LocalBadContent, and that's another problem.
Disallowing to create wiki pages with external links is considered main and
very efficient way to stop wiki spam, there are many resources explaining how
to do that for various wiki engines.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.