http://bugs.winehq.org/show_bug.cgi?id=6856
------- Additional Comments From mikolaj.zalewski(a)gmail.com 2007-04-05 16:13 -------
Created an attachment (id=6119)
--> (http://bugs.winehq.org/attachment.cgi?id=6119&action=view)
example XPath program
I've found that to start a XPath query from a non-root node one has to set the
node field of the xmlXPathContext and use xmlXPathEval - at least that's what
libxslt is doing. I'm attaching an example program to show how it works.
However I still couldn't understand how MSXML treats namespaces and I've found
that unless you change it with IXMLDOMDocument2_setProperty(doc,
"SelectionLanguage", "XPath"), selectSingleNode doesn't use XPath but something
called XSLPattern. That's probably what's implemented in
xsltCompMatchPatternList. I'll have to look into how it works.
--
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=8275
------- Additional Comments From juan_lang(a)yahoo.com 2007-04-05 15:49 -------
It looks as though the second log still uses builtin crypt32, else we wouldn't
see all the trace:crypt:CryptHashData calls. So the bug must be in rsaenh
somewhere.
It looks superficially as though CryptAcquireContext might be failing, since
when using builtin rsaenh, the HCRYPTPROV argument to CryptCreateHash et al is
NULL. But the builtin rsaenh returns an index into a handle table rather than a
pointer, so the first returned handle is always 0. So the bug appears to be
elsewhere.
--
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=6391
me(a)gn0me.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From me(a)gn0me.org 2007-04-05 15:48 -------
I am no longer encountering this issue.
--
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=8276
Summary: Hitting screenshot button (printscreen) triggers two
screenshots
Product: Wine
Version: CVS
Platform: PC
URL: http://iro.ragnarokonline.com
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-msvcrt
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: me(a)gn0me.org
Hitting the PrintScreen button takes two screenshots, one for the keydown and
one for the keyup. I disabled the gnome-based screenshot program, it is only the
in-game screenshotter that's doing it. In Windows it never used to take two, so
I think this is a bug. Confirmed by my friend that the client doesn't take two
in Windows; however, can anyone confirm that they are also getting two in Wine?
--
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=8266
------- Additional Comments From o.oudin(a)free.fr 2007-04-05 15:40 -------
For the crash describe in this bug, as I had installed nvidia driver 97.55 with
the envy script (which is not officially supported by ubuntu for edgy), so I
remove it.
Then I install nvidia-glx (nvidia driver 87.76) and nvidia-restricted-module*
for my kernel from the official depot, and retest : It crash as well :(
--
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=7940
------- Additional Comments From assasukasse(a)gmail.com 2007-04-05 15:37 -------
i was able to perform a regression test, and posted the result here
--
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.