http://bugs.winehq.org/show_bug.cgi?id=3303
------- Additional Comments From muziwind(a)yahoo.com.cn 2005-21-12 19:48 -------
if u want to have printsetup dialog in notepad, confige ur printer first.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3885
Speeddymon(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #1378 is|0 |1
obsolete| |
Attachment #1379 is|0 |1
obsolete| |
------- Additional Comments From Speeddymon(a)gmail.com 2005-21-12 19:10 -------
Created an attachment (id=1559)
--> (http://bugs.winehq.org/attachment.cgi?id=1559&action=view)
Console output for test 17
Since the Previous outputs were only applicable to the app error, they are now
obsolete, due to the hack that gets things working up to this point.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3885
------- Additional Comments From Speeddymon(a)gmail.com 2005-21-12 19:07 -------
Even only running test 17, it dies into debugger, so it's something that isnt
supported, although the debugger mentions heap allocation:
Backtrace:
=>1 0x4019ef6f HEAP_CreateFreeBlock(size=0x10fff0)
[/home/speeddy/wine/dlls/ntdll/../../include/wine/list.h:78] in ntdll (0x4019ef6f)
Ill post the full output in a sec.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4120
picasa(a)jlm.ofb.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|wine-bugs(a)winehq.org |dank(a)kegel.com
------- Additional Comments From picasa(a)jlm.ofb.net 2005-21-12 18:17 -------
So, where do I file this bug?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=4120
dank(a)kegel.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From dank(a)kegel.com 2005-21-12 18:14 -------
It looks like the picasa2 wrapper script is used to wrap
both picasa2 itself and the installer.
This may be what led to the confusion; the script ran
up the installer when it should have ran picasa itself.
In any case this is not a wine bug.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=4120
------- Additional Comments From picasa(a)jlm.ofb.net 2005-21-12 18:05 -------
Dan Kegel reports this is a consequence of choosing a location other than
~/picasa2 for the install, which is apparently hardcoded somewhere. If the
picasa installer is unpacked into ~/picasa2 and picasa installed into
~/picasa2, then running picasa as ~/picasa2/bin/picasa2 does start picasa
without crashing.
So in the short term:
* unpacker should only unpack into ~/picasa2
* installer should only install into ~/picasa2
In the longer term, Picasa should obviously be made to function even if it's
installed to other than ~/picasa2.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=3885
------- Additional Comments From Speeddymon(a)gmail.com 2005-21-12 17:59 -------
CORRECTION: It still crashes under 2.4 with builtin. I had it set to native
mode still.. BUT when running native with 2.4 and winxp, like I said, it
reliably goes all the way to test 17 before dieing.. Under 2.6, it dies in
random places after test 1....
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4109
andy.elvey(a)paradise.net.nz changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From andy.elvey(a)paradise.net.nz 2005-21-12 17:57 -------
I have good news :-) -
Thanks to Vitaliy's help, I've now been able to get both CodeBlocks and
Dev-C++ running on Wine 0.9.3. I have attached screenshots to show this.
Just in case someone else comes across a similar problem, here is what I did -
1) Vitaliy mentioned that I should check where Wine was installed, and put the
path into the file '/etc/ld.so.conf' then run 'ldconfing'.
I did this. I then tried to run CodeBlocks again, but got similar errors to
the first time. So, I took a closer look at the errors (duh-I should have done
this first, before posting this bug ;-) ), The file libXxf86vm seemed to be
missing, according to the error messages.
2) So, I went into Synaptic and sure enough, libXxf86vm was not installed.
***Doh*** ...
( By the way, that file is (I found out) an X video mode selection library.)
The Debian version (in "unstable") has a version number of 6.8.2.dfsg.1-11.
3) I installed that using Synaptic. Then, I ran "wine codeblocks-1.0rc2.exe" ,
and it ran perfectly! I then ran wine devcpp-4.9.9.2_setup.exe and *it* ran
perfectly as well!
So, to summarise - I have been able to both install and then run both
CodeBlocks and Dev-C++ successfully.
( CodeBlocks is unable to open files, but that is a CodeBlocks bug, not a Wine
one. It is a Codeblocks error-message that appears, so I can log that with them)
Anyway, I've learned heaps - especially about ld.so.conf ... - so this should
stand me in good stead in the future. Very many thanks Vitaliy (and all of the
other Wine devs too. )
I believe that this "bug" (which wasn't really a bug) can now be marked as
"invalid" , and then closed.
- Andy
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3885
------- Additional Comments From Speeddymon(a)gmail.com 2005-21-12 17:56 -------
Ok, after rebooting, it wouldnt startup with builtin, but still would with
native. I checked into winecfg, and ralized I had set winver to win2k
inadvertently. After changing that back to XP, I can get it to start with
builtin and go all the way to test 17 (reliably, using the hack Aric gave me)
before it dies into the debugger. I'm going to disable all tests but 17 and see
if it dies due to the stack corruption issue mentioned before, or if it dies
because of something that isnt supported. Then I will reboot back into 2.6, and
test out winver xp again under there.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.