Hello,
2008/5/5 Dan Kegel <[EMAIL PROTECTED]>:
> On Mon, May 5, 2008 at 6:41 PM, Steven Edwards <[EMAIL PROTECTED]> wrote:
> > On Mon, May 5, 2008 at 8:45 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> > > As a token of our thanks, we will pick one of the users who submits
> > > a healthy set o
On Tue, May 6, 2008 at 1:36 AM, Maarten Lankhorst
<[EMAIL PROTECTED]> wrote:
> Improved from James Hawkins suggestions.
> ---
>
Just to clear my name, this is not what I suggested :-)
--
James Hawkins
On Tue, May 6, 2008 at 1:40 AM, Joerg Mayer <[EMAIL PROTECTED]> wrote:
> On Mon, May 05, 2008 at 05:45:57PM -0700, Dan Kegel wrote:
> > 0. Make sure your machine runs glxgears properly
> > (if it crashes, you may need to update your graphics drivers)
>
> Why would I need working glxgears? Wine w
On Mon, May 05, 2008 at 05:45:57PM -0700, Dan Kegel wrote:
> 0. Make sure your machine runs glxgears properly
> (if it crashes, you may need to update your graphics drivers)
Why would I need working glxgears? Wine works fine for my every day work
and I haven't had working 3D acceleration for the p
Pavel Troller wrote:
> So, what can I do to help fixing these problems ? Should I open a bug for
To solve most/all problems related to hardware one needs to have such
hardware. It's nearly impossible to "simulate" the behavior while reading logs.
> every such a program ? Or just open one bug an
Hi!
I have really BIG problems running any application, which needs to comm over
a serial port:
- My ham TCVR
- My GPS
- My multimeter
- A lot of my mobiles
- A lot of devices used in my work (special telco equipment, comms varying
from simple AT-style commands up to complex proprie
Howdy,
Tried compiling wine on Nexenta (Opensolaris kernel with GNU
userland). Trying to test out the conformance test, but can't get it
to compile:
make[2]: Entering directory `/export/home/austin/wine/libs/wpp'
gcc -c -I. -I. -I../../include -I../../include-Wall -pipe
-fno-strict-aliasing -
On Mon, May 5, 2008 at 6:41 PM, Steven Edwards <[EMAIL PROTECTED]> wrote:
> On Mon, May 5, 2008 at 8:45 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> > As a token of our thanks, we will pick one of the users who submits
> > a healthy set of useful test results and send him or her a tasteful
> >
On Mon, 2008-05-05 at 12:16 +0200, Alexandre Julliard wrote:
> Steven Elliott <[EMAIL PROTECTED]> writes:
>
> > Maybe I'm making some bad assumptions about why the socket file can't be
> > placed in ~/.wine (that not all users have a writable home directory).
> > I'm guessing based on the snippet
On Mon, 2008-05-05 at 09:11 +0200, Marcus Meissner wrote:
> On Mon, May 05, 2008 at 08:47:52AM +0200, Francois Gouget wrote:
> >
> > In /tmp I see the following:
> >
> >.X0-lock
> >.X11-unix/
> >fgouget/
> >gconfd-fgouget/
> >vmware-fgouget/
> >xmms_fgouget.0
> >
> > So i
On Mon, May 5, 2008 at 8:45 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> As a token of our thanks, we will pick one of the users who submits
> a healthy set of useful test results and send him or her a tasteful
> Wine-themed goodie of some sort.
Maybe we should all pitch in or tap the Wine party
Package: wnpp
Severity: normal
Since my time may be limited in the future, I am seeking comaintainers
for the Wine package in Debian, at least to ensure that new Wine releases
may continue to be uploaded in a timely fashion, and to keep the package's
bug count down. (And given that pretty much hal
So, what should we be asking wine users to be
doing once rc1 is out? How about this:
--- snip ---
Calling all wine users!
Today, after 15 years of development, the first release
candidate for wine-1.0.0 was released.
Wine has been under heavy development in recent
months, and some applications th
Hi.
I would like to have rights to change bug status. I fix some bugs myself and
also occasionally do some bug-triaging, so it would be handy. Thanks.
Hi Andrew,
Andrew Talbot wrote:
> Often this is so. But some bugs may not be revealed by such a test. Also,
> sometimes it would be useful to ask an expert what was intended by a bit of
> code. For example, consider the following code (from
> mshtml/mshtmloption.c), to pick something at random:
>
Alistair Leslie-Hughes wrote:
> "Alexandre Julliard" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
>> Module: wine
>> Branch: master
>> Commit: 29d8c366bb278a6b73c3669817063087d7cd080d
>> URL:
>> http://source.winehq.org/git/wine.git/?a=commit;h=29d8c366bb278a6b73c36698170630
Hello Zachary,
2008/5/5 Zachary Goldberg <[EMAIL PROTECTED]>:
> I think that a missing factor in making this decision is the shape of
> an automatic test suite. Its been mentioned a dozen times and has the
> potential to tip the scales in favor of the time-based releases
> (making QA easier ->
"Alexandre Julliard" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Module: wine
> Branch: master
> Commit: 29d8c366bb278a6b73c3669817063087d7cd080d
> URL:
> http://source.winehq.org/git/wine.git/?a=commit;h=29d8c366bb278a6b73c3669817063087d7cd080d
>
> Author: Jacek Caban <[EMAIL
Hello Alex,
2008/5/5 Alex Villacís Lasso <[EMAIL PROTECTED]>:
> The patch:
>
> 3066116f76c0c44950fde3552485b37dce24d1f8
> quartz: Clean up pullpin code.
>
> causes a regression in a test application I have. I see the following
> message in the console:
>
> pin.c:1236: PullPin_Init: La declar
On Mon, 5 May 2008, Maarten Lankhorst wrote:
[...]
> > When do you see a crash? Winetest itself already checks if a dll is
> > present. If it's not, the tests are skipped as can be seen on
> > test.winehq.org..
> It was crashing when I ran the test directly. But if that behavior is
> ok I'll just
I think that a missing factor in making this decision is the shape of
an automatic test suite. Its been mentioned a dozen times and has the
potential to tip the scales in favor of the time-based releases
(making QA easier -> shorter freezes). In the event that we are able
to maintain QA (by test
The patch:
3066116f76c0c44950fde3552485b37dce24d1f8
quartz: Clean up pullpin code.
causes a regression in a test application I have. I see the following
message in the console:
pin.c:1236: PullPin_Init: La declaración `pCustomRequest' no se cumple.
And I get an "Automation error" in a message
Hello Paul,
2008/5/5 Paul Vriens <[EMAIL PROTECTED]>:
> Maarten Lankhorst wrote:
>
> >
> > This is better then downright crashing on the missing dlls.
> >
> > This patch was created using grep and sed. :-)
> > ---
> >
> >
> >
Le lundi 05 mai 2008, Juan Lang a écrit :
> Patches without your full name are unlikely to get accepted. Would
> you mind resending with your full name? Thanks,
> --Juan
Okay, here it is:
When Altium 6 is used with a license server, it need the WSAIoctl() with
SIO_KEEPALIVE_VALS control code t
Dan Kegel wrote:
> Andrew Talbot wrote:
>> witness my current
>> postings: "XBOOL, XBYTE, XINT8, etc." and "Five functions that cannot
>> handle a NULL parameter",
>
> I haven't seen those posts, where are they?
Hi Dan,
I posted them to wine-devel on Saturday.
> I'd say a conformance test woul
Maarten Lankhorst wrote:
> This is better then downright crashing on the missing dlls.
>
> This patch was created using grep and sed. :-)
> ---
>
>
>
>
>
Hi Maarten,
When do you see a crash? Winetest itself already check
Andrew Talbot wrote:
> Frequently, I am finding minor bugs that I probably cannot fix myself, that
> are probably not suitable for a Bugzilla bug report and that are likely to
> be ignored if posted to wine-devel (witness my current postings: "XBOOL,
> XBYTE, XINT8, etc." and "Five functions that c
Stefan Dösinger wrote:
> Am Montag, 5. Mai 2008 17:42:51 schrieb Andrew Talbot:
>> I have moved the TRACEs to where I think they belong. Please give
>> feedback if this patch is incorrect.
> on a quick look it looks OK. Did you check if any output is written in the
> case of failures in those func
Am Montag, 5. Mai 2008 17:42:51 schrieb Andrew Talbot:
> I have moved the TRACEs to where I think they belong. Please give feedback
> if this patch is incorrect.
on a quick look it looks OK. Did you check if any output is written in the
case of failures in those functions?
Hi,
Frequently, I am finding minor bugs that I probably cannot fix myself, that
are probably not suitable for a Bugzilla bug report and that are likely to
be ignored if posted to wine-devel (witness my current postings: "XBOOL,
XBYTE, XINT8, etc." and "Five functions that cannot handle a NULL
para
2008/5/5 Kai Blin <[EMAIL PROTECTED]>:
> On Monday 05 May 2008 05:13:16 Dan Kegel wrote:
> > I just wrote up an idea related to release management for post-1.0
> > wine releases. It's online at
> > http://wiki.winehq.org/TimeBasedReleases
> > Essentially, the idea is to release in March and
"Dan Kegel" <[EMAIL PROTECTED]> writes:
> That wasn't the distro; that was an upstream kernel vulnerability fix
> announced in February,
> http://kerneltrap.org/Linux/Patching_CVE-2008-0600_Local_Root_Exploit
It's the distro that changed the mmap config, not the kernel. I'm not
sure I understand
On Mon, May 5, 2008 at 6:54 AM, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> It's the distro that changed the mmap config, not the kernel. I'm not
> sure I understand their reasoning, apparently this was an attempt to
> work around the vulnerability without fixing the kernel.
Oh, right. I t
Alexandre Julliard wrote:
> Scott Ritchie <[EMAIL PROTECTED]> writes:
>
>> The alternative, truthfully, is choosing between shipping Ubuntu with a
>> 2+months out of date Wine version or an untested one. Either option sucks.
>
> I don't see how we can possibly have a tested release ready every t
On Mon, May 5, 2008 at 5:12 AM, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> I don't see how we can possibly have a tested release ready every time
> some distro decides to ship.
That wasn't the proposal. The proposal was to ship every 6 months, and
to pick a release date that made some sens
Scott Ritchie <[EMAIL PROTECTED]> writes:
> The alternative, truthfully, is choosing between shipping Ubuntu with a
> 2+months out of date Wine version or an untested one. Either option sucks.
I don't see how we can possibly have a tested release ready every time
some distro decides to ship. On
On Mon, May 05, 2008 at 04:12:52AM -0700, Scott Ritchie wrote:
> Dan Kegel wrote:
> > I just wrote up an idea related to release management for post-1.0
> > wine releases. It's online at
> > http://wiki.winehq.org/TimeBasedReleases
> > Essentially, the idea is to release in March and September,
Dan Kegel wrote:
> I just wrote up an idea related to release management for post-1.0
> wine releases. It's online at
> http://wiki.winehq.org/TimeBasedReleases
> Essentially, the idea is to release in March and September,
> in time for the April and October releases of Ubuntu.
You have my 120%
Steven Elliott <[EMAIL PROTECTED]> writes:
> Maybe I'm making some bad assumptions about why the socket file can't be
> placed in ~/.wine (that not all users have a writable home directory).
> I'm guessing based on the snippet from my original post that includes
> "Since that might not be possible
On Monday 05 May 2008 05:13:16 Dan Kegel wrote:
> I just wrote up an idea related to release management for post-1.0
> wine releases. It's online at
> http://wiki.winehq.org/TimeBasedReleases
> Essentially, the idea is to release in March and September,
> in time for the April and October releas
On Mon, May 05, 2008 at 08:47:52AM +0200, Francois Gouget wrote:
> On Wed, 30 Apr 2008, Steven Elliott wrote:
>
> > 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 e
41 matches
Mail list logo
