http://bugs.winehq.org/show_bug.cgi?id=13832
Summary: Circuitmaker schematic does not print to a printer Product: Wine Version: 1.0-rc4 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: brodo@o2.pl
Created an attachment (id=13887) --> (http://bugs.winehq.org/attachment.cgi?id=13887) snapshots of the "printing" effect
In schematic section of the Circuitmaker 2000 invoking printing operation directed to a printer gives no printing at all and the screen is losing wired connections. I am enclosing snapshots of the normal view of the design and the broken (after printing attempt) one. Refreshing screen can be made only by reopening the design file, so some work can be lost while invoking printing of an unsaved file/design.
http://bugs.winehq.org/show_bug.cgi?id=13832
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |printing
--- Comment #1 from Austin English austinenglish@gmail.com 2008-06-10 14:07:46 --- Does printing from wine notepad work? Please attach terminal output.
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #2 from OlekA brodo@o2.pl 2008-06-10 16:45:06 --- (In reply to comment #1)
Does printing from wine notepad work? Please attach terminal output.
Yes, printing from wine notepad works. Also printing from PCB section (Traxmaker.exe) of Circuitmaker 2000 is OK. Only schematic part (cirmaker.exe) fails in this regard. Some months ago it worked too, but I do not remember which Wine version I had those days.
Maybe I'll try to catch some verbose msgs while invokong printing ? How can I do it ?
http://bugs.winehq.org/show_bug.cgi?id=13832
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #3 from Lei Zhang thestig@google.com 2008-06-19 11:33:41 --- Can you downgrade and try some older version of Wine to see which ones worked?
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #4 from OlekA brodo@o2.pl 2008-06-19 17:55:25 --- (In reply to comment #3)
Can you downgrade and try some older version of Wine to see which ones worked?
It seems that I should do it in order to push things forward :) I'll try to find the last working version as soon as I can.
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #5 from OlekA brodo@o2.pl 2008-06-20 18:54:36 --- (In reply to comment #4)
(In reply to comment #3)
Can you downgrade and try some older version of Wine to see which ones worked?
I did a test today. Wine-0.9.45 does exhibit this bug but Wine-0.9.40 does not ! I used the latest Slackware-current environment to compile Wine. Building script was taken from slacky.eu site and adopted to the mentioned Wine versions. Should I further follow my searches to find the last version that allowed printing from Circuitmaker's schematic editor ?
One more effect: the famous "simview error" while starting schematic editor is gone in these versions now. But it existed several months ago when I routinely compiled almost every freshly issued Wine version as always. So maybe the culprit is in the version of Glibc, kernel, Xorg, GL or the like ?
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #6 from Austin English austinenglish@gmail.com 2008-06-21 19:38:17 --- (In reply to comment #5)
(In reply to comment #4)
(In reply to comment #3)
Can you downgrade and try some older version of Wine to see which ones worked?
I did a test today. Wine-0.9.45 does exhibit this bug but Wine-0.9.40 does not ! I used the latest Slackware-current environment to compile Wine. Building script was taken from slacky.eu site and adopted to the mentioned Wine versions. Should I further follow my searches to find the last version that allowed printing from Circuitmaker's schematic editor ?
One more effect: the famous "simview error" while starting schematic editor is gone in these versions now. But it existed several months ago when I routinely compiled almost every freshly issued Wine version as always. So maybe the culprit is in the version of Glibc, kernel, Xorg, GL or the like ?
Please run a regression test: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #7 from OlekA brodo@o2.pl 2008-06-23 17:31:35 ---
Please run a regression test: http://wiki.winehq.org/RegressionTesting
I must tell that I am not a programmer so I don't know if I can handle regression testing. Maybe somebody will encourage me ? :)
I narrowed my scope: the last printing version was the 0.9.41.
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #8 from James Hawkins truiken@gmail.com 2008-06-23 17:38:02 --- The directions for running the regression test are outlined in the URL given by Austin. It's a simple process and requires no programming skills.
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #9 from OlekA brodo@o2.pl 2008-06-26 04:32:51 --- (In reply to comment #8)
The directions for running the regression test are outlined in the URL given by Austin. It's a simple process and requires no programming skills.
I did that. The last output from bisect is this :
olek@linux:~/wine-git$ git bisect bad Bisecting: 0 revisions left to test after this [4b53154f361b9fdc504be5e099e84c6686f940fe] winspool: Return the full path for the driver.
olek@linux:~/wine-git$ ./wine --version wine-0.9.41-394-ga2daf75
Where is the info about the author of the patch ? It should be already shown as described in this example: http://wiki.winehq.org/RegressionTesting
What should I do next ?
http://bugs.winehq.org/show_bug.cgi?id=13832
L. Rahyen mail@science.su changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mail@science.su
--- Comment #10 from L. Rahyen mail@science.su 2008-06-26 05:16:42 ---
... The last output from bisect is this : ... Bisecting: 0 revisions left to test after this [4b53154f361b9fdc504be5e099e84c6686f940fe] winspool: Return the full path for the driver. ... What should I do next ?
"0 revisions left to test after this" means no more revisions left *after* current one. Therefore you need to test your application once more (that is, one more git-bisect good/bad step is necessary).
BTW, in Regression Testing guide ( http://wiki.winehq.org/RegressionTesting ) in the "Testing the Actual Program" section you can find big notice specific to this message:
"If you see: Bisecting: 0 revisions left to test after this
THEN YOU ARE NOT DONE YET!"
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #11 from OlekA brodo@o2.pl 2008-06-26 06:17:10 ---
"0 revisions left to test after this" means no more revisions left *after* current one. Therefore you need to test your application once more (that is, one more git-bisect good/bad step is necessary).
BTW, in Regression Testing guide ( http://wiki.winehq.org/RegressionTesting ) in the "Testing the Actual Program" section you can find big notice specific to this message:
"If you see: Bisecting: 0 revisions left to test after this
THEN YOU ARE NOT DONE YET!"
Yes, I recompiled it again and got this:
olek@linux:~/wine-git$ git bisect bad 4b53154f361b9fdc504be5e099e84c6686f940fe is first bad commit commit 4b53154f361b9fdc504be5e099e84c6686f940fe Author: Detlef Riekenberg wine.dev@web.de Date: Thu Jul 26 23:05:27 2007 +0200
winspool: Return the full path for the driver.
:040000 040000 696dbd0389c83249ca54aa4b228360a348f14088 8825f509c1d92b07c610ac1c79f63cbb3748dc2d M dlls
olek@linux:~/wine-git$ ./wine --version wine-0.9.41-393-g4b53154
what can I do next (if any) ? Bug 13832 is already opened...
http://bugs.winehq.org/show_bug.cgi?id=13832
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine.dev@web.de Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #12 from OlekA brodo@o2.pl 2008-09-05 04:57:08 ---
Yes, I recompiled it again and got this:
olek@linux:~/wine-git$ git bisect bad 4b53154f361b9fdc504be5e099e84c6686f940fe is first bad commit commit 4b53154f361b9fdc504be5e099e84c6686f940fe Author: Detlef Riekenberg wine.dev@web.de Date: Thu Jul 26 23:05:27 2007 +0200
winspool: Return the full path for the driver.:040000 040000 696dbd0389c83249ca54aa4b228360a348f14088 8825f509c1d92b07c610ac1c79f63cbb3748dc2d M dlls
olek@linux:~/wine-git$ ./wine --version wine-0.9.41-393-g4b53154
When can we expect to do sth with this bug ? :)
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #13 from OlekA brodo@o2.pl 2008-09-05 05:01:08 --- (In reply to comment #12)
Yes, I recompiled it again and got this:
olek@linux:~/wine-git$ git bisect bad 4b53154f361b9fdc504be5e099e84c6686f940fe is first bad commit commit 4b53154f361b9fdc504be5e099e84c6686f940fe Author: Detlef Riekenberg wine.dev@web.de Date: Thu Jul 26 23:05:27 2007 +0200
winspool: Return the full path for the driver.:040000 040000 696dbd0389c83249ca54aa4b228360a348f14088 8825f509c1d92b07c610ac1c79f63cbb3748dc2d M dlls
olek@linux:~/wine-git$ ./wine --version wine-0.9.41-393-g4b53154
When can we expect to do sth with this bug ? :)
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #14 from OlekA brodo@o2.pl 2008-12-17 09:45:47 --- How about this bug ? Lack of printing is definitely a serious bug . . . .
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #15 from OlekA brodo@o2.pl 2009-06-08 15:45:01 --- Hello ! How about this unresolved bug ? Are there any chances to fix it ?
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #16 from Austin English austinenglish@gmail.com 2009-12-31 13:02:41 --- Jeremy did a bit of printing work recently, it may help (not sure what bugs he fixed).
http://bugs.winehq.org/show_bug.cgi?id=13832
John Voltz johnvoltz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |johnvoltz@gmail.com
--- Comment #17 from John Voltz johnvoltz@gmail.com 2010-06-20 18:26:48 --- I can confirm this bug still exists in wine 1.2rc4. Circuitmaker will not print.
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #18 from John Voltz johnvoltz@gmail.com 2010-06-20 18:40:53 --- It's strange, printing a schematic does not work, yet printing a waveform does. Also, Olek, your connections in the schematic are not disappearing, what is happening is they are being turned black. If you reset your background to white you will see what I'm talking about.
http://bugs.winehq.org/show_bug.cgi?id=13832
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |mstefani@redhat.com Ever Confirmed|0 |1
--- Comment #19 from Michael Stefaniuc mstefani@redhat.com 2010-11-17 09:00:35 CST --- Confirming as per comment #17
http://bugs.winehq.org/show_bug.cgi?id=13832
fhmanas fhmanas@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fhmanas@yahoo.com
--- Comment #20 from fhmanas fhmanas@yahoo.com 2010-12-21 02:57:37 CST --- Would like to suggest using native comdlg32.dll as it may be because of a bad dialog box or unsupported feature like collation.
http://bugs.winehq.org/show_bug.cgi?id=13832
Henri Verbeet hverbeet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |4b53154f361b9fdc504be5e099e | |84c6686f940fe
http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #21 from Austin English austinenglish@gmail.com 2012-02-13 14:34:49 CST --- http://source.winehq.org/git/wine.git/commitdiff/bea70326875077c488cb42f2d48... should help here.
http://bugs.winehq.org/show_bug.cgi?id=13832
Detlef Riekenberg wine.dev@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |bea70326875077c488cb42f2d48 | |7d777e5721b2e Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #22 from Detlef Riekenberg wine.dev@web.de 2012-02-13 16:01:15 CST --- The "non printing issue" marked as regression in Comment #11 should be fixed in current git by http://source.winehq.org/git/wine.git/commit/bea70326875077c488cb42f2d487d77...
When the screen is still loosing wired connections, please fill a new bug.
http://bugs.winehq.org/show_bug.cgi?id=13832
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #23 from Alexandre Julliard julliard@winehq.org 2012-02-17 13:50:28 CST --- Closing bugs fixed in 1.4-rc4.
https://bugs.winehq.org/show_bug.cgi?id=13832
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Component|-unknown |comdlg32
-
wine-bugs＠winehq.org