http://bugs.winehq.org/show_bug.cgi?id=2622
truiken(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
------- Additional Comments From truiken(a)gmail.com 2006-12-09 18:49 -------
Joe, you really need to relax. You're running Wine from rpms that we don't
make. These rpms *probably* weren't compiled with the necessary libraries. And
to quote myself, I said "most likely fontforge or freetype-devel", not "you
don't have fontforge and freetype-devel installed and I know it!"
> pequod(~) wine --configure verbose
'Running configure' implies that you have the source code to wine, and you run
pequod(~) ./configure --verbose
to see what libraries you're missing. The fact that winecfg and wine crash
means there's a problem with your Wine rpm, and this bug should be marked
invalid because of that.
> ...and the fact that I uninstalled all traces of wine and then reinstalled
_all_ the wine*-0.9.20-1.fc5 rpms, means that if I am missing files, then the
rpm packaging is broken.
You are exactly right, Joe, your rpm packages are broken. Please file a bug
with your distro (Fedora). You can compile Wine from source and report back.
Here's a link for Fedora's bug tracking system:
https://bugzilla.redhat.com/bugzilla/index.cgi
Here's a link for downloading and compiling Wine from source:
http://winehq.org/site/docs/wineusr-guide/installing-wine-source
I'm marking this as invalid. If you compile from source, or the Fedora packages
are fixed, and the app is still not installed, then reopen the 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=6186
Summary: ñ, dead keys, Alt Gr don't work, Spanish keyboard
Product: Wine
Version: 0.9.20.
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-x11driver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gerardo(a)bridgebase.com
ñ doesn't work.
á shows as a
à shows as `a
â shows as ^a
\ doesn't work as normal key (Alt Gr+ key just below Esc), but Alt Gr+'
>From xorg.conf:
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "es"
EndSection
x11driver as componen is just a (very wild) guess
--
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=2622
joe(a)eshu.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From joe(a)eshu.net 2006-12-09 18:12 -------
James Hawkins' theory would be a nice one, if it fit the facts, but it doesn't.
I _do_ have freetype-devel and fontforge installed, and the fact that I
uninstalled all traces of wine and then reinstalled _all_ the wine*-0.9.20-1.fc5
rpms, means that if I am missing files, then the rpm packaging is broken.
Just because the installer behaves strangely (double dialogs, etc.) and the app
crashes wine immediatley certainly doesn't mean that the bug is _fixed_! What
sort of reasoning could possibly make one believe that the behavior I see is in
any sense acceptable?
Moreover,
pequod(~) wine --configure verbose
crashed just like winecfg, etc.
wine: creating configuration directory '/home/joe/.wine'...
fixme:ole:ITypeInfo_fnRelease destroy child objects
wine: Unhandled page fault on read access to 0x003c002f at address 0x7eea41a7
(thread 0009), starting debugger...
but no debugger.
If this is "fixed", then I might as well be helping to debug Windows XP for all
the concern this shows about quality!
--
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=2622
truiken(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From truiken(a)gmail.com 2006-12-09 17:36 -------
You're getting the strange 'glyphs' because you don't have the necessary
packages installed, most likely fontforge or freetype-devel. Run configure
--verbose to see what you're missing. I'm marking this as fixed. Just because
the app crashes when you try to run it doesn't mean it didn't install correctly,
and looking at the output, and that you're running the installed executable, it
did install the app. Please open a new bug report if you can't run the app.
--
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=2622
------- Additional Comments From joe(a)eshu.net 2006-12-09 17:30 -------
Created an attachment (id=3583)
--> (http://bugs.winehq.org/attachment.cgi?id=3583&action=view)
the console output while wine-0.9.20 was failing to install topo again.
Ahem, running winecfg, after the exception got raised I was presented with a
dialog box filled with random glyphs, and clicked on the right hand button.
However, after I pushed submit when trying:
wine /media/CA_D01/setup.exe
just now, I noticed that I had been once again presented with the same dialog
box full of random glyphs, so for grins I clicked the left hand button, and
remarkably, the installation started. InstallShield quickly threw up a dialog
saying that it had finished and asking me to reboot, but before I could
respond, another InstallShield box appeared, covering the first saying that it
was installing. After the typical message/confirmation dialogs about using the
defaults, then a progress bar of the copying and installation, a second dialog
saying that it had finished and asking me to reboot appeared and I clicked
"yes, reboot now". The first finished/reboot? dialog persisted so I clicked yes
again. Unfortunately, the install appears to have failed, as wine crashes when
I try to run the just installed application. The attachment contains the
console output from this experiment.
--
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=6185
vitaliy(a)kievinfo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|website-bugs |wine-binary
Product|WineHQ Apps Database |Wine
------- Additional Comments From vitaliy(a)kievinfo.com 2006-12-09 17:22 -------
Please attach complete termianl output. And update Wine version.
--
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=6185
------- Additional Comments From fightclubsoap(a)gmail.com 2006-12-09 17:10 -------
By crash I mean stop the game from responding and I have to kill it
--
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=6185
Summary: Diablo II Movies Crash
Product: WineHQ Apps Database
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P4
Component: website-bugs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fightclubsoap(a)gmail.com
Hi, I installed and ran Diablo II: LoD fine, the only problem right now is that
the movies cutscenes randomly freeze, and the storyline is really important to
me, so please don't say as long as you can play it's fine. Is there a fix to this?
--
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=2622
------- Additional Comments From joe(a)eshu.net 2006-12-09 17:04 -------
Ok. I didn't get very far, using the wine-0.9.20-1.fc5 rpm's from Fedora Extras
(as pointed to from the WineHQ download page) on a up-to-date FC5 laptop.
I began by removing my .wine directory. First I tried to run winecfg, which
immediately crashed:
pequod(~) winecfg
wine: creating configuration directory '/home/joe/.wine'...
fixme:ole:ITypeInfo_fnRelease destroy child objects
wine: Unhandled page fault on read access to 0x003c002f at address 0x7eeaf1a7
(thread 0009), starting debugger...
wine: wineprefixcreate failed while creating '/home/joe/.wine'.
Then, after checking that winecfg didn't leave behind any wreckage, I tried:
wine /media/CA_D01/setup.exe
but the result was the same:
wine: creating configuration directory '/home/joe/.wine'...
fixme:ole:ITypeInfo_fnRelease destroy child objects
wine: Unhandled page fault on read access to 0x003c002f at address 0x7eeaf1a7
(thread 0009), starting debugger...
Perhaps when i have some time, I'll give uninstalling the rpms and building wine
from cvs a shot. Sigh.
--
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=5811
------- Additional Comments From truiken(a)gmail.com 2006-12-09 16:54 -------
Concerning your original report:
* The file chooser is accessible.
* The installation is complete.
* Manually entering a new directory still does not work.
On your second report:
* Selecting just "Register Extensions" and "Utility Scripts" still leaves
pythonw.exe not installed.
There are four bugs here, and half of them are fixed. There should only be one
bug per bug report. We can either reopen this bug and mark it invalid, or leave
it as fixed and you can open new, specific bugs that still remain with Git/CVS.
--
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.