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.
https://bugs.winehq.org/show_bug.cgi?id=44823
Bug ID: 44823
Summary: Steam doesn't close on exit. Will continue running in
background.
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vblanton(a)gmail.com
Distribution: ---
Created attachment 60857
--> https://bugs.winehq.org/attachment.cgi?id=60857
Steam system information and version
Running the latest Steam client, I find that Steam doesn't actually close
entirely after I exit normally with Steam>Exit. I have to open System Monitor
and kill all steam and wine related processes. I can't open steam again until I
do so, and the Steam.exe and wineserver processes chew 17% of my CPU each in
the background until I do so.
--
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=42360
Bug ID: 42360
Summary: Terragen 4 fails to start
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: eneeen(a)gmail.com
Distribution: ---
Created attachment 57137
--> https://bugs.winehq.org/attachment.cgi?id=57137
tgd4_backlog
Using Kubuntu 16.10
I've attached backlog.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=35866
Bug ID: 35866
Summary: AvP 2000 game: some ingame text has red boxes around
it
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bob.mt.wya(a)gmail.com
Created attachment 47886
--> http://bugs.winehq.org/attachment.cgi?id=47886
In game HUD : red boxes
Using the Steam version of Aliens Vs Predator Classic (2000). Some ingame text
has red boxes around each individual character. Appears under both recent
Nvidia (proprietary) and AMD radeon (kernel) drivers.
I didn't even notice this glitch before. But having booted into Windows 7 to
double check... The red boxes are not present when the game is run natively
under Windows.
I don't see anything of significance in the console log when I launch AvP
manually (with Steam running in the same 64-bit Wineprefix).
Any thoughts if this is low hanging fruit to fix?
Thanks
Robert
--
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=46221
Bug ID: 46221
Summary: League of Legends 8.23 crash after champion select
Product: Wine
Version: 3.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lollinos(a)hotmail.com
Distribution: ---
i think it's the same error about anti-cheat lol had last patches.
After Champion select end, game crash with message: "A critical error has
occurred and the process must be terminated. Would you liek to create a crash
dump to aid the developers in troubleshooting this issue? This may take up to 5
minutes. NOYE: The process may appear unresponsive during this time. [YES]
[NO]".
Steps:
- WINEPREFIX=~/.wine WINEARCH=win32 wine winecfg
- WINEPREFIX=~/.wine WINEARCH=win32 wine winetricks --gui, set to true capture
mouse, virtual Desktop and Windows version to XP (I've tried with 7-10 too)
- wineboot -u, winetricks -q d3dx9
- cd .wine/drive_c/, ln -s ~/path/lol-installer.exe
- wine start lol-installer.exe
- wine reg add 'HKEY_CURRENT_USER\Software\Wine\DllOverrides' /v 'msvcp140' /t
'REG_SZ' /d 'native,builtin' /f
- wine reg add 'HKEY_CURRENT_USER\Software\Wine\DllOverrides' /v 'wininet' /t
'REG_SZ' /d 'builtin,native' /f
- wine start 'C:\Riot Games\League of Legends\LeagueClient.exe'
I tried a lot of settings, but i cant make it works after champion select.
Some way to fix this bug?
ii wine-staging 3.21.0~stretch
amd64 WINE Is Not An Emulator - runs MS Windows programs
ii wine-staging-amd64 3.21.0~stretch
amd64 WINE Is Not An Emulator - runs MS Windows programs
ii wine-staging-i386:i386 3.21.0~stretch
i386 WINE Is Not An Emulator - runs MS Windows programs
ii winehq-staging 3.21.0~stretch
amd64 WINE Is Not An Emulator - runs MS Windows programs
ii winetricks 0.0+20170101-1
all package manager for Wine to install software easily
--
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=35690
Bug ID: 35690
Summary: Steam network hang ups.
Product: Wine
Version: 1.7.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hellsy22(a)gmail.com
Created attachment 47657
--> http://bugs.winehq.org/attachment.cgi?id=47657
Installing and using steam
Unpredictable hangups while establishing connection for downloading updates,
loggining in, downloading games, etc.
There are no problems with network for everything except wine/Steam. Win Steam
works perfect, all other services - too.
--
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.