http://bugs.winehq.org/show_bug.cgi?id=30186
Bug #: 30186
Summary: Wine Bugzilla quick search return zero result for
keywords
Product: WineHQ Bugzilla
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
If I remember correctly, it works yesterday.
Today I try to search some short keywords in Wine Bugzilla quick search box,
and found it doesn't work as before:
For example, search for "win","mac","wow", "aj", "a", the result is empty.
Here is a example URL:
http://bugs.winehq.org/buglist.cgi?query_format=specific&order=relevance%20…
Bug or feature?
--
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=21424
Summary: Cygwin 1.7.1 bash crashes
Product: Wine
Version: 1.1.36
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
cygwin installs now, but one sees the following crash
10 [main] bash 9 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
1271 [main] bash 9 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
err:ntdll:RtlpWaitForCriticalSection section 0x736d2784 "loader.c:
loader_section" wait timed out in thread 0036, blocked by 003c, retrying (60
sec)
during postinstall, and also when running bash interactively.
--
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=19713
Summary: Some serial port communication functions behave
differently in Wine and Windows.
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fenixk19(a)mail.ru
Created an attachment (id=23025)
--> (http://bugs.winehq.org/attachment.cgi?id=23025)
Test program
This makes test program to hang in Wine, but in MS it is ok. Test program
attached.
--
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=13296
Summary: regression problem in upgrade to Ubuntu Hardy/1.0-rc1:
Palm Hotsync over serial Segmentation Fault
Product: Wine
Version: 1.0-rc1
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jan-winehq(a)h-i-s.nl
Created an attachment (id=13150)
--> (http://bugs.winehq.org/attachment.cgi?id=13150)
Logging output
I upgraded to Ubuntu Hardy, and wine 1.0-rc1.
Hotsync manager 1.0 for Palm Pilot worked fine before.
http://appdb.winehq.org/objectManager.php?sClass=version&iId=10362
Now it crashes half-way synchronising over the serial port, sometimes after a
few seconds, sometimes much later in the process.
These crashes reproduce well, and yield a segmentation fault without further
information
$ wine hotsync.exe
Segmentation fault
$
I do not know if this means that a part of Wine crashes, or just the
application.
I added logging, where it seems that the problem lies within the call below:
0009:CallTo16(func=111f:072a,ds=1087,118f,7404,0000,0006) ss:sp=1087:ffd0
I am not sure if the problem lies with wine, or that other problems with Ubuntu
Hardy may relate to this.
It is disappointing that an application that used to work fine, and I came to
depend on, is now broken.
--
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=25083
Summary: HyperTerminal unable to loop back on COM1 (RS-232)
Product: Wine
Version: 1.3.6
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: graham(a)nerve.org.za
On a machine with an on-board RS-232 port at COM1, HyperTerminal (as shipped
with Windows XP) is firstly unable to detect the port until changes are made in
the WINE registry, thereafter, after attaching a simple loopback adapter (pins
2 and 3 of a DB9F shorted) no characters are echoed to the screen.
Obtaining the software:
>From a Windows XP installation, copy the files hypertrm.exe and htrn_jis.dll
from 'C:\Program Files\Windows NT' and hticons.dll and hypertrm.dll from
C:\Windows\System32' into a suitable directory below .wine/drive_c
or
Download a free 30 day trial of HyperTerminal Private Edition 7.0 from
http://www.hilgraeve.com/hyperterminal/
Create a symbolic link for COM1, documented here:
http://www.winehq.org/docs/wineusr-guide/misc-things-to-configure
ln -s /dev/ttyS0 ~/.wine/dosdevices/com1
At this point, starting HyperTerminal will result in no serial ports being
shown.
Now, create a registry entry in WINE for the serial port, mentioned in this bug
report:
http://bugs.winehq.org/show_bug.cgi?id=4282
Add the following lines to .wine/system.reg [Hardware\\Devicemap\\SerialComm]
"Serial0"="COM1"
Now HyperTerminal can be started, COM1 can be selected and configured, but no
characters are echoed to the screen.
However, the free terminal program, simply named 'Terminal' and available here:
https://sites.google.com/site/terminalbpp/
Does echo characters to the screen.
--
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=10051
Summary: Parallax SX Key IDE cannot detect serial port under WINE
Product: Wine
Version: 0.9.46.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-setupapi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ultimatedevr(a)yahoo.com
Created an attachment (id=8599)
--> (http://bugs.winehq.org/attachment.cgi?id=8599)
Result of running SXKey.exe in wine with the +setupapi debug flag.
I am trying to run the Parallax SX Key IDE through WINE, however the IDE does
not detect any of my serial ports. I have symlinked them to ~/.wine/dosdevices/
and added them to my registry, however the IDE still cannot detect my serial
ports.
I am currently running WINE v.0.9.46 (the same problem exists in the CVS
version as well).
(BTW, I have heard of others getting this to work, yet others who couldn't:
http://forums.parallax.com/forums/default.aspx?f=15&m=217429&g=221692)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=23326
Summary: Cannot change printer settings, Family Tree 7
Product: Wine
Version: 1.2-rc4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jamesl(a)bestweb.net
Created an attachment (id=29072)
--> (http://bugs.winehq.org/attachment.cgi?id=29072)
FTW7 print dialogue, compare Wine to XP
Cannot select printer/change print settings with Family Tree Maker 7. Dialogue
box comes up, drop-down boxes are working, but radio buttons for switching
between "default printer" and an alternate printer are not selectable. Have
compared the print dialogue between Wine vs a native install under Windows XP
(SP3) and notice some text from the Windows install does not show up under
Wine.
Also tried the same thing with the "free" version of FTM2005se available at
http://past.familytreemaker.com/download/starter.aspx and found it's behavior
is the same. So I will describe steps from there, since it would be eaier for
someone to get that to test against.
STEPS TO RECREATE:
1: Set up wine profile with "WINEPREFIX=/home/jelabarre/wine-apps/ftw2005
winecfg"; set winver to "Windows XP", point the Documents directory under
Desktop Integration to my own Documents directory
2: install FTW2005 by running
"WINEPREFIX=/home/jelabaWINEPREFIX=/home/jelabarre/wine-apps/ftw2005 wine
./FamilyTreeMaker2005se.exe", accept all defaults.
3: open FTW 2005 from "Wine" menu entry on Gnome menu. Selected "Buy Later"
from popup window (does not affect outcome, as same print problem occurrs in a
regular retail version of FTM7)
4: create new file, or use existing file (same result either way)
5: select "File | Print Setup", then try to select radio button for either
"Default Printer" or "Specific Printer". Neither can be selected
6: try selecting a "specific printer" from drop-down box. Printer can be
selected, but radio buttons still not functional.
7: after selecting a printer other than the default (such as print-to-PDF) and
then try printing. Output will still go to the Linux default printer, no edits
of the print settings will take effect.
The "Family Archive Viewer v6.0" at
http://familytreemaker.genealogy.com/abtffiv.html and "Family Archive Viewer
v11.0" at http://www.genealogy.com/abtffiv.html are other variants that
exhibits this behavior.
Have attached sample screenshots of Wine vs WinXP versions of the print
dialogue.
--
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=30155
Bug #: 30155
Summary: secdrv.sys from SafeDisc v2.05.030 does not work
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: stefan(a)codeweavers.com
Classification: Unclassified
Created attachment 39336
--> http://bugs.winehq.org/attachment.cgi?id=39336
service,relay,winedevice,ntoskrnl log
SafeDisc 2.05.030 does not work out of the box. The user-visible symptom is
that the application exits with exit code 0 without any output. This affects
for example the Command and Conquer Red Alert 2 installer, which is safedisc
protected for some reason.
The problem seems to be related to the specific secdrv.sys version. If I take a
secdrv.sys from a newer safedisc version(e.g. 2.40.010 from the RA2 Yuri's
revenge expansion) and put it in C:\windows\system32\drivers, the installer
works.
ProtectId says:
Scanning -> D:\Setup\Setup.exe
File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 1308863 (013F8BFh)
Byte(s)
-> File has 733375 (0B30BFh) bytes of appended data starting at offset 08C800h
[File Heuristics] -> Flag : 00000000000000000100000000100111 (0x00004027)
[!] Safedisc v2.05.030 detected !
[i] Appended data contents....
[.] o: 0x0008C828 / t: <0x00000001> <0x00000000> <0x00000001> / s: 00194947
byte(s) -> ~de7bc4.tmp
[.] o: 0x000BC1D2 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00030208
byte(s) -> clcd32.dll
[.] o: 0x000C37F9 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00006784
byte(s) -> clcd16.dll
[.] o: 0x000C529D / t: <0x00000001> <0x00000000> <0x0000044D> / s: 00067584
byte(s) -> mcp.dll
[.] o: 0x000D5AC5 / t: <0x00000001> <0x00000000> <0x00000000> / s: 00327220
byte(s) -> ~df394b.tmp
[.] o: 0x00125920 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00034304
byte(s) -> drvmgt.dll
[.] o: 0x0012DF47 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00018768
byte(s) -> secdrv.sys
[.] o: 0x001328BF / t: <0x00000001> <0x00000000> <0x00000000> / s: 00053248
byte(s) -> ~ef7194.tmp
[CompilerDetect] -> Visual C++ 6.0
- Scan Took : 0.640 Second(s)
The md5sum of the broken secdrv.sys is XXX. The md5sum of the working 2.40.010
driver is f376a1580204e47f37a721e1cbc5582a.
I am attaching a +relay,+service,+winedevice+ntoskrnl log of a failed run of
the setup tool.
--
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=9378
Summary: CM: Shock Force 'Could not initialize graphics display'
Product: Wine
Version: 0.9.43.
Platform: PC
URL: http://www.battlefront.com/products/cmsf/downloads.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mailing_list(a)orange.nl
After starting Combat Mission: Shock Force Demo it stops with the message:
'Could not initialize graphics display. REQUIRED 1024x768, 32-bit
color'.
The terminal output doesn't provide any clues:
wine 'CM Shock Force DEMO.exe'
ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0
ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file
or directory
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=18889
Summary: Live Messenger 2008 fails to load - possible actctx
problem
Product: Wine
Version: 1.1.16
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andras(a)csevego.net
Created an attachment (id=21730)
--> (http://bugs.winehq.org/attachment.cgi?id=21730)
+actctx,+relay log
Starting of installed (on windows) Msn 2009 wil result:
err:module:import_dll Library MSVCR80.dll (which is needed by
L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe") not
found
err:module:LdrInitializeThunk Main exe initialization for
L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe" failed,
status c0000135
Same load failure, when I manually install with wine (from msi packages)
MSVCRT 8.0 is installed, as shown attached +actctx,+relay log
I suspect here an Activation Context failure.
--
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.