On Son, 2003-03-23 at 01:38, Stian Jordet wrote:
> lør, 2003-03-22 kl. 23:05 skrev Jeffrey Baker:
> > On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> > > On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > > > In 4.2.1-7 prerelease packages, this bug now causes the
> > > > machi
On Son, 2003-03-23 at 01:38, Stian Jordet wrote:
> lør, 2003-03-22 kl. 23:05 skrev Jeffrey Baker:
> > On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> > > On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > > > In 4.2.1-7 prerelease packages, this bug now causes the
> > > > machi
lør, 2003-03-22 kl. 23:05 skrev Jeffrey Baker:
> On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> > On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > > In 4.2.1-7 prerelease packages, this bug now causes the
> > > machine to lock hard.
> >
> > Does this also happen with DRI d
lør, 2003-03-22 kl. 23:05 skrev Jeffrey Baker:
> On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> > On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > > In 4.2.1-7 prerelease packages, this bug now causes the
> > > machine to lock hard.
> >
> > Does this also happen with DRI d
On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > In 4.2.1-7 prerelease packages, this bug now causes the
> > machine to lock hard.
>
> Does this also happen with DRI disabled?
>
> > I have also determined that the trigger of
On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > In 4.2.1-7 prerelease packages, this bug now causes the
> > machine to lock hard.
>
> Does this also happen with DRI disabled?
>
> > I have also determined that the trigger of
On Die, 2003-03-11 at 00:54, Jeffrey Baker wrote:
> On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> > On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > > In 4.2.1-7 prerelease packages, this bug now causes the
> > > machine to lock hard.
> >
> > Does this also happen with DR
On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > In 4.2.1-7 prerelease packages, this bug now causes the
> > machine to lock hard.
>
> Does this also happen with DRI disabled?
>
> > I have also determined that the trigger of
On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> In 4.2.1-7 prerelease packages, this bug now causes the
> machine to lock hard.
Does this also happen with DRI disabled?
> I have also determined that the trigger of this bug is the NerveRot
> XScreenSaver hack, possible with the default or t
On Die, 2003-03-11 at 00:54, Jeffrey Baker wrote:
> On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> > On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > > In 4.2.1-7 prerelease packages, this bug now causes the
> > > machine to lock hard.
> >
> > Does this also happen with DR
On Tue, Mar 11, 2003 at 12:40:08AM +0100, Michel D?nzer wrote:
> On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> > In 4.2.1-7 prerelease packages, this bug now causes the
> > machine to lock hard.
>
> Does this also happen with DRI disabled?
>
> > I have also determined that the trigger of
On Mon, 2003-03-10 at 04:29, Jeffrey Baker wrote:
> In 4.2.1-7 prerelease packages, this bug now causes the
> machine to lock hard.
Does this also happen with DRI disabled?
> I have also determined that the trigger of this bug is the NerveRot
> XScreenSaver hack, possible with the default or t
In 4.2.1-7 prerelease packages, this bug now causes the
machine to lock hard. I have also determined that the
trigger of this bug is the NerveRot XScreenSaver hack,
possible with the default or the "dense" settings. Give it
a try, lock your machine hard.
-jwb
In 4.2.1-7 prerelease packages, this bug now causes the
machine to lock hard. I have also determined that the
trigger of this bug is the NerveRot XScreenSaver hack,
possible with the default or the "dense" settings. Give it
a try, lock your machine hard.
-jwb
--
To UNSUBSCRIBE, email to [EMA
On Mon, Mar 03, 2003 at 06:30:15PM -0800, Jeffrey Baker wrote:
> As requested, the stack trace:
>
> #0 0x40077a51 in kill () from /lib/libc.so.6
> #1 0x40077872 in raise () from /lib/libc.so.6
> #2 0x40078986 in abort () from /lib/libc.so.6
> #3 0x0825137d in ddxGiveUp () at xf86Init.c:1094
>
As requested, the stack trace:
#0 0x40077a51 in kill () from /lib/libc.so.6
#1 0x40077872 in raise () from /lib/libc.so.6
#2 0x40078986 in abort () from /lib/libc.so.6
#3 0x0825137d in ddxGiveUp () at xf86Init.c:1094
#4 0x082b86e0 in AbortServer () at utils.c:436
#5 0x082b9985 in FatalError
On Mon, Mar 03, 2003 at 06:30:15PM -0800, Jeffrey Baker wrote:
> As requested, the stack trace:
>
> #0 0x40077a51 in kill () from /lib/libc.so.6
> #1 0x40077872 in raise () from /lib/libc.so.6
> #2 0x40078986 in abort () from /lib/libc.so.6
> #3 0x0825137d in ddxGiveUp () at xf86Init.c:1094
>
As requested, the stack trace:
#0 0x40077a51 in kill () from /lib/libc.so.6
#1 0x40077872 in raise () from /lib/libc.so.6
#2 0x40078986 in abort () from /lib/libc.so.6
#3 0x0825137d in ddxGiveUp () at xf86Init.c:1094
#4 0x082b86e0 in AbortServer () at utils.c:436
#5 0x082b9985 in FatalError
[Please reply to [EMAIL PROTECTED] so that other users can see what
we're doing to diagnose this problem.]
On Sun, Mar 02, 2003 at 08:55:24PM -0800, Jeffrey Baker wrote:
> On Sun, Mar 02, 2003 at 05:48:22PM -0500, Branden Robinson wrote:
> > On Sun, Mar 02, 2003 at 11:35:46AM -0800, Jeffrey Baker
[Please reply to [EMAIL PROTECTED] so that other users can see what
we're doing to diagnose this problem.]
On Sun, Mar 02, 2003 at 08:55:24PM -0800, Jeffrey Baker wrote:
> On Sun, Mar 02, 2003 at 05:48:22PM -0500, Branden Robinson wrote:
> > On Sun, Mar 02, 2003 at 11:35:46AM -0800, Jeffrey Baker
On Sun, Mar 02, 2003 at 11:35:46AM -0800, Jeffrey Baker wrote:
> I have removed the "freetype" module from my configuration,
> and I still get this crash.
It would be helpful if someone would get me the backtrace that was
discussed on 10 February.
Package: xserver-xfree86-dbg
Priority: optional
S
On Sun, Mar 02, 2003 at 11:35:46AM -0800, Jeffrey Baker wrote:
> I have removed the "freetype" module from my configuration,
> and I still get this crash.
It would be helpful if someone would get me the backtrace that was
discussed on 10 February.
Package: xserver-xfree86-dbg
Priority: optional
S
I have removed the "freetype" module from my configuration,
and I still get this crash.
-jwb
I have removed the "freetype" module from my configuration,
and I still get this crash.
-jwb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Feb 10, 2003 at 08:53:54AM -, Markus Laker scrawled:
> We use a local font server: please see the attached text files.
>
> Could you possibly send a non-stripped version of the package (or the
> executable(s)), so that we can get you a backtrace?
The X server is available unstripped a
On Mon, Feb 10, 2003 at 08:53:54AM -, Markus Laker scrawled:
> We use a local font server: please see the attached text files.
>
> Could you possibly send a non-stripped version of the package (or the
> executable(s)), so that we can get you a backtrace?
The X server is available unstripped a
Michel Dänzer [EMAIL PROTECTED] writes:
> On Son, 2003-02-09 at 18:26, Jeffrey Baker wrote:
> > On Sat, Feb 08, 2003 at 02:22:14PM -0500, Branden Robinson wrote:
> > > On Fri, Feb 07, 2003 at 04:25:30PM -, Markus Laker wrote:
> > > > > Are you using xlock with a particular mode, or just -mode
Michel Dänzer [[EMAIL PROTECTED]] writes:
> On Son, 2003-02-09 at 18:26, Jeffrey Baker wrote:
> > On Sat, Feb 08, 2003 at 02:22:14PM -0500, Branden Robinson wrote:
> > > On Fri, Feb 07, 2003 at 04:25:30PM -, Markus Laker wrote:
> > > > > Are you using xlock with a particular mode, or just -mod
On Mon, 2003-02-10 at 02:08, Jeffrey Baker wrote:
> On Mon, Feb 10, 2003 at 01:57:19AM +0100, Michel D?nzer wrote:
> > Other usual suspects for server crashes are the TrueType font renderer
> > modules (freetype and xtt), do you use those? (Some people claim font
> > servers may also be problematic
On Mon, Feb 10, 2003 at 01:57:19AM +0100, Michel D?nzer wrote:
> Other usual suspects for server crashes are the TrueType font renderer
> modules (freetype and xtt), do you use those? (Some people claim font
> servers may also be problematic, but I haven't had problems with xfs)
My config file can
On Son, 2003-02-09 at 18:26, Jeffrey Baker wrote:
> On Sat, Feb 08, 2003 at 02:22:14PM -0500, Branden Robinson wrote:
> > On Fri, Feb 07, 2003 at 04:25:30PM -, Markus Laker wrote:
> > > > Are you using xlock with a particular mode, or just -mode random?
> > >
> > > I'm using -mode random. If
On Mon, 2003-02-10 at 02:08, Jeffrey Baker wrote:
> On Mon, Feb 10, 2003 at 01:57:19AM +0100, Michel D?nzer wrote:
> > Other usual suspects for server crashes are the TrueType font renderer
> > modules (freetype and xtt), do you use those? (Some people claim font
> > servers may also be problematic
On Mon, Feb 10, 2003 at 01:57:19AM +0100, Michel D?nzer wrote:
> Other usual suspects for server crashes are the TrueType font renderer
> modules (freetype and xtt), do you use those? (Some people claim font
> servers may also be problematic, but I haven't had problems with xfs)
My config file can
On Son, 2003-02-09 at 18:26, Jeffrey Baker wrote:
> On Sat, Feb 08, 2003 at 02:22:14PM -0500, Branden Robinson wrote:
> > On Fri, Feb 07, 2003 at 04:25:30PM -, Markus Laker wrote:
> > > > Are you using xlock with a particular mode, or just -mode random?
> > >
> > > I'm using -mode random. If
On Sat, Feb 08, 2003 at 02:22:14PM -0500, Branden Robinson wrote:
> On Fri, Feb 07, 2003 at 04:25:30PM -, Markus Laker wrote:
> > > Are you using xlock with a particular mode, or just -mode random?
> >
> > I'm using -mode random. If you'd like me to try limiting it to any
> > particular mode,
On Sat, Feb 08, 2003 at 02:22:14PM -0500, Branden Robinson wrote:
> On Fri, Feb 07, 2003 at 04:25:30PM -, Markus Laker wrote:
> > > Are you using xlock with a particular mode, or just -mode random?
> >
> > I'm using -mode random. If you'd like me to try limiting it to any
> > particular mode,
On Fri, Feb 07, 2003 at 04:25:30PM -, Markus Laker wrote:
> > Are you using xlock with a particular mode, or just -mode random?
>
> I'm using -mode random. If you'd like me to try limiting it to any
> particular mode, or avoiding it completely, please let me know.
It would be helpful if you
On Fri, Feb 07, 2003 at 04:25:30PM -, Markus Laker wrote:
> > Are you using xlock with a particular mode, or just -mode random?
>
> I'm using -mode random. If you'd like me to try limiting it to any
> particular mode, or avoiding it completely, please let me know.
It would be helpful if you
On Sat, Feb 08, 2003 at 10:58:46AM +1100, Daniel Stone wrote:
> On Fri, Feb 07, 2003 at 10:40:11AM -0500, Branden Robinson scrawled:
> > On Fri, Feb 07, 2003 at 09:03:46AM +, Markus Laker wrote:
> > > Package: xserver-xfree86
> > > Version: 4.2.1-5
> > > Severity: important
> > >
> > > X serve
On Fri, Feb 07, 2003 at 10:40:11AM -0500, Branden Robinson scrawled:
> On Fri, Feb 07, 2003 at 09:03:46AM +, Markus Laker wrote:
> > Package: xserver-xfree86
> > Version: 4.2.1-5
> > Severity: important
> >
> > X server crashes with SEGV, sometimes interactively but more often when left
> > ru
On Sat, Feb 08, 2003 at 10:58:46AM +1100, Daniel Stone wrote:
> On Fri, Feb 07, 2003 at 10:40:11AM -0500, Branden Robinson scrawled:
> > On Fri, Feb 07, 2003 at 09:03:46AM +, Markus Laker wrote:
> > > Package: xserver-xfree86
> > > Version: 4.2.1-5
> > > Severity: important
> > >
> > > X serve
On Fri, Feb 07, 2003 at 10:40:11AM -0500, Branden Robinson scrawled:
> On Fri, Feb 07, 2003 at 09:03:46AM +, Markus Laker wrote:
> > Package: xserver-xfree86
> > Version: 4.2.1-5
> > Severity: important
> >
> > X server crashes with SEGV, sometimes interactively but more often when left
> > ru
Hi, Branden,
Thanks for the quick response.
> Are you using xlock with a particular mode, or just -mode random?
I'm using -mode random. If you'd like me to try limiting it to any
particular mode, or avoiding it completely, please let me know.
Best regards,
Markus
***
tag 180107 + moreinfo
thanks
On Fri, Feb 07, 2003 at 09:03:46AM +, Markus Laker wrote:
> Package: xserver-xfree86
> Version: 4.2.1-5
> Severity: important
>
> X server crashes with SEGV, sometimes interactively but more often when left
> running xlock.
This usually happens because one of the
Processing commands for [EMAIL PROTECTED]:
> tag 180107 + moreinfo
Bug#180107: xserver-xfree86: ATI Radeon 7500: SEGV at random times, esp in xlock
There were no tags set.
Tags added: moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tr
Hi, Branden,
Thanks for the quick response.
> Are you using xlock with a particular mode, or just -mode random?
I'm using -mode random. If you'd like me to try limiting it to any
particular mode, or avoiding it completely, please let me know.
Best regards,
Markus
***
tag 180107 + moreinfo
thanks
On Fri, Feb 07, 2003 at 09:03:46AM +, Markus Laker wrote:
> Package: xserver-xfree86
> Version: 4.2.1-5
> Severity: important
>
> X server crashes with SEGV, sometimes interactively but more often when left
> running xlock.
This usually happens because one of the
Processing commands for [EMAIL PROTECTED]:
> tag 180107 + moreinfo
Bug#180107: xserver-xfree86: ATI Radeon 7500: SEGV at random times, esp in xlock
There were no tags set.
Tags added: moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tr
Package: xserver-xfree86
Version: 4.2.1-5
Severity: important
X server crashes with SEGV, sometimes interactively but more often when left
running xlock.
-- Package-specific info:
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW [Radeon
7500]
01:05.0 Class 0300: 1002:5157
Package: xserver-xfree86
Version: 4.2.1-5
Severity: important
X server crashes with SEGV, sometimes interactively but more often when left
running xlock.
-- Package-specific info:
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW [Radeon 7500]
01:05.0 Class 0300: 1002:5157
50 matches
Mail list logo
