James McKenzie <[EMAIL PROTECTED]> wrote:
> Dan Kegel wrote:
> > And we can probably make high-res users happier still
> > by defaulting to Xft.dpi (used by Gnome and maybe KDE;
> > it's set by default to 96, but is increased by some users
> > of high-res displays).
> >
> This will break Darwine.
Maarten Lankhorst skrev:
> Wine checks ownership of the socket and directory, so race conditions
> aren't really a problem. This means that despite being put in a public
> directory there is no chance of a race condition. I don't see a
> security risk here, if someone is evil they could create that
Dan Kegel wrote:
> And we can probably make high-res users happier still
> by defaulting to Xft.dpi (used by Gnome and maybe KDE;
> it's set by default to 96, but is increased by some users
> of high-res displays).
>
>
This will break Darwine. Xft.dpi does not exist on Apple's X11
implementati
Hell Ove,
2008/4/30 Ove Kaaven <[EMAIL PROTECTED]>:
> Maarten Lankhorst skrev:
>
>
> > The latter won't work, they could create the directory and then delete
> > it after wineserver started. I don't think it is really a problem, by
> > the time someone else can put that directory in /tmp chances a
Hi,
2008/4/23 Jeremy White <[EMAIL PROTECTED]>:
> > http://kegel.com/wine/wine-penguin-corkscrew.png
>
> Jon Parshall is proud of his ability to draw those penguins,
> and we'd gladly send that artwork to anyone that wanted to make a T-shirt.
>
> Note, though, that we felt we had to (very sadly
Maarten Lankhorst skrev:
> The latter won't work, they could create the directory and then delete
> it after wineserver started. I don't think it is really a problem, by
> the time someone else can put that directory in /tmp chances are that
> they can do a lot more malicious things then just makin
Hello Steven,
2008/4/30 Steven Elliott <[EMAIL PROTECTED]>:
> I have some concerns about the location of the socket file that
> wineserver uses. Since by default the current location is in /tmp my
> concern is that anyone can stop anyone else from using wine just by
> creating a directory name
Hi,
I'll be working on msxml3.dll. I'm planning to implement SAX (Simple API for
XML) and fix as much bugs related to this dll as I can. My main goal is to
fix part of 8945 bug related to msxml.
I'm from Poland. I'm a second year computer science student at University of
Wroclaw. I was working
> I think that is an excellent idea and I can see it being immediately
> useful in rpcrt4, if not other areas.
Indeed, I also think it's an excellent idea. The crypt32 chain tests
are another good candidate for this approach.
--Juan
Alex Villacís Lasso escribió:
> EM_FINDTEXT and EM_FINDTEXTEX have different rules for interpreting
> ranges for 1.0 and 2.0 modes:
>
> In 1.0 emulation cpMin > cpMax is invalid and always fails.
> In 1.0 emulation, search is always done between cpMin and cpMax, even
> backwards search.
> In 1.0
Francois Gouget wrote:
> My idea is that
> some platforms (e.g. Wine) could ask for stricter checks, by using
> strict_wine a bit like they use todo_wine to request looser checks.
>
> So for instance you would do:
>
>strict_wine ok(expected_cond || buggy(this_is_a_bug), ...);
>
> Then on Wind
I have some concerns about the location of the socket file that
wineserver uses. Since by default the current location is in /tmp my
concern is that anyone can stop anyone else from using wine just by
creating a directory named /tmp/.wine-500.
As far as I know the only risk is denial of service
On Wed, 30 Apr 2008, Robert Reif wrote:
[...]
> I am suppling a minimal patch to the alsa driver and a single wave test to
> illustrate this concept. I hope this allows valid tests to remain in spite of
> buggy windows drivers.
I think it should be a more general winetest concept. My idea is that
"ByeongSik Jeon" <[EMAIL PROTECTED]> wrote:
> I have attached new one.
Looks good to me.
--
Dmitry.
Robert Reif <[EMAIL PROTECTED]> writes:
> The returned result of some audio functions on windows may be
> inconsistent because a driver may actually supply the returned value.
>
> This presents a problem for the wine regression tests because a buggy
> driver may return an unexpected result which c
On Tue, 22 Apr 2008, Austin English wrote:
[...]
> On Tue, Apr 22, 2008 at 5:25 AM, Alexandre Julliard <[EMAIL PROTECTED]>
> wrote:
>
> > "Austin English" <[EMAIL PROTECTED]> writes:
> >
> > > I've been working on some of the documentation, then remembered that
> > > Scott requested a move to XML:
Maarten Lankhorst wrote:
> Hello Robert,
>
> 2008/4/29 Robert Reif <[EMAIL PROTECTED]>:
>
>> The returned result of some audio functions on windows may be inconsistent
>> because a driver may actually supply the returned value.
>>
>> This presents a problem for the wine regression tests because
Dnia 24-04-2008, czw o godzinie 12:48 +0200, Tomasz Jezierski - Tefnet
pisze:
> For more information check bug report.
>
Hi.. what's the status of this patch? I haven't found any comments on
wine-devel about it.
"ByeongSik Jeon" <[EMAIL PROTECTED]> wrote:
> +while (TRUE)
> +{
> +if ( PeekMessage(&msg, 0, 0, 0, PM_REMOVE) )
> +{
> +struct message posted_msg;
> +
> +msg_count++;
> +
> +trace("posted message[%d]: %p, %04x, %08lx, %08lx\n
Maarten Lankhorst a écrit :
> Hi all,
>
> I was trying to switch to a different thread in winedbg, however I
> don't see any command for that in the winedbg online reference at
> http://www.winehq.org/site/docs/winedev-guide/dbg-commands . Does
> anyone know if it's possible?
>
> Cheers,
> Maarten.
Am Mittwoch, 30. April 2008 07:21:19 schrieb Jens Albretsen:
> A quick one is Lego Island, just forget to put in the disc a there is black
> screen, with this patch is shows a message to put the cdrom in the drive.
>
> Is it something like this?
>
> create (1,1) rendertarget
> clear rendertarget wi
Robert Shearman <[EMAIL PROTECTED]> writes:
> The way I see it, we have a choice between having a framework that uses
> the makefile to run individual tests of the parser without checking the
> content or a framework that runs every test in one go, but is capable of
> checking the output of the
Hi all,
I was trying to switch to a different thread in winedbg, however I
don't see any command for that in the winedbg online reference at
http://www.winehq.org/site/docs/winedev-guide/dbg-commands . Does
anyone know if it's possible?
Cheers,
Maarten.
On Tue, 29 Apr 2008, Robert Reif wrote:
> First of all, requesting 4 bytes is not invalid but a perfectly
> reasonable thing to do. It is just reading the manufactures id and
> product id. However this behavior is not documented in MSDN so at best
> it's just unspecified behavior. The reason
24 matches
Mail list logo
