> No. It mostly has screen update problems (too slow) with my main
> application (a networked game). I've noticed network connection problems
> in parts of another application though. The only wine-related problems
> in -current that I know of were related to rfork(). rfork() was broken
> in k
On Wed, 22 Oct 2003, Jonathan E Fosburgh wrote:
> On Wednesday 22 October 2003 10:06 pm, Bruce Evans wrote:
> > It is effectively binary only, since current versions of wine don't
> > run my application correctly and the old version doesn't build under
> > -current.
>
> Is it some application that
On Wed, 22 Oct 2003, C. Kukulies wrote:
>Some (kde) applications now have a warning appear in xconsole:
>
>Warning: pid 595 used static ldt allocation.
>See the i386_set_ldt man page for more info
>Warning: pid 596 used static ldt allocation.
>See the i386_set_ldt man page for more info
>
>Should
On Thu, 23 Oct 2003, Bruce Evans wrote:
> On Wed, 22 Oct 2003, Daniel Eischen wrote:
>
> > On Wed, 22 Oct 2003, C. Kukulies wrote:
> >
> > > Some (kde) applications now have a warning appear in xconsole:
> > >
> > > Warning: pid 595 used static ldt allocation.
> > > See the i386_set_ldt man page
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 22 October 2003 10:06 pm, Bruce Evans wrote:
> On Wed, 22 Oct 2003, Daniel Eischen wrote:
> > On Wed, 22 Oct 2003, C. Kukulies wrote:
>
> It is effectively binary only, since current versions of wine don't
> run my application correctly a
On Wed, 22 Oct 2003, Daniel Eischen wrote:
> On Wed, 22 Oct 2003, C. Kukulies wrote:
>
> > Some (kde) applications now have a warning appear in xconsole:
> >
> > Warning: pid 595 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 596 used static ldt alloca
On Wed, 22 Oct 2003, C. Kukulies wrote:
> Some (kde) applications now have a warning appear in xconsole:
>
> Warning: pid 595 used static ldt allocation.
> See the i386_set_ldt man page for more info
> Warning: pid 596 used static ldt allocation.
> See the i386_set_ldt man page for more info
>
>
In the last episode (Oct 22), Andre Guibert de Bruet said:
> This could also be accomplished by enabling process accounting and
> grepping the output of lastcomm. But yes, this patch is most welcome
> nonetheless. :)
lastcomm doesn't include the pid, so that would be most difficult :)
--
On Wed, 22 Oct 2003, Dan Nelson wrote:
> In the last episode (Oct 22), Steve Kargl said:
> > On Wed, Oct 22, 2003 at 12:09:43PM -0400, Daniel Eischen wrote:
> > > On Wed, 22 Oct 2003, C. Kukulies wrote:
> > > > Some (kde) applications now have a warning appear in xconsole:
> > > >
> > > > Warning
In the last episode (Oct 22), Steve Kargl said:
> On Wed, Oct 22, 2003 at 12:09:43PM -0400, Daniel Eischen wrote:
> > On Wed, 22 Oct 2003, C. Kukulies wrote:
> > > Some (kde) applications now have a warning appear in xconsole:
> > >
> > > Warning: pid 595 used static ldt allocation.
> > > See the
On Wed, Oct 22, 2003 at 12:09:43PM -0400, Daniel Eischen wrote:
> On Wed, 22 Oct 2003, C. Kukulies wrote:
>
> > Some (kde) applications now have a warning appear in xconsole:
> >
> > Warning: pid 595 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 596
On Wed, 22 Oct 2003, C. Kukulies wrote:
> Some (kde) applications now have a warning appear in xconsole:
>
> Warning: pid 595 used static ldt allocation.
> See the i386_set_ldt man page for more info
> Warning: pid 596 used static ldt allocation.
> See the i386_set_ldt man page for more info
>
>
Some (kde) applications now have a warning appear in xconsole:
Warning: pid 595 used static ldt allocation.
See the i386_set_ldt man page for more info
Warning: pid 596 used static ldt allocation.
See the i386_set_ldt man page for more info
Should I worry about that? Rebuild KDE?
--
Chris Christ
13 matches
Mail list logo