On 2023-07-03 23:26 +0200, Axel Beckert wrote:
> Package: xserver-xorg-video-nouveau
Wrong package, this driver is not involved in the crash. In fact, it is
not even used on your system (or by default, except for really ancient
graphics cards).
> (Feel free to reassign this bug to e.g. xserver-
erver error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
Switching to xserver-xorg-video-nvidia with nvidia-kernel-dkms (but not
nvidia-open-kernel-source — which made X show up on only one screen
without any xrandr or nvidia-settings capabilities) fixed the
issue. Hence reporting this
nal 11 (Segmentation fault).
Server aborting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator an
error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional
information.
(EE)
(EE) Server terminated with er
/libc.so.6
(__libc_start_main+0xfd) [0x7fbe5d7e8ead]
[1305277.661] 9: /usr/bin/Xorg (0x7fbe5f799000+0x4219d) [0x7fbe5f7db19d]
[1305277.661]
[1305277.661] Segmentation fault at address 0x637f4870
[1305277.661]
Fatal server error:
[1305277.661] Caught signal 11 (Segmentation fault). Server aborting
A ba
Hi!
On Fri, Feb 1, 2013 at 9:22 AM, Michel Dänzer wrote:
> BTW, I presume you're not intentionally running the game with indirect
> rendering, are you? If you installed the 32 bit version of the demo,
> installing the libgl1-mesa-{glx,dri}:i386 packages might help.
Hum... I had libgl1-mesa-glx:i
On Don, 2013-01-31 at 16:54 -0200, Nelson A. de Oliveira wrote:
> Package: xserver-xorg-core
> Version: 2:1.12.4-4
> Severity: important
>
> Hi!
>
> While trying to run Aeon Command Demo (from
> http://www.desura.com/games/aeon-command) my X restarted.
>
> In Xorg.0.log it's possible to see:
>
Hi!
On Thu, Jan 31, 2013 at 5:28 PM, Julien Cristau wrote:
> That attachment doesn't show an error.
The right log was sent on another email.
> Also please get a backtrace from gdb if the bug is reproducible (with
> xserver-xorg-core-dbg and libgl1-mesa-dri-dbg installed).
gdb bt full is attach
] 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xfd)
> [0x7ff649572ead]
> [1729023.649] 12: /usr/bin/Xorg (0x7ff64b523000+0x4219d) [0x7ff64b56519d]
> [1729023.649]
> [1729023.649] Segmentation fault at address 0x3c
> [1729023.649]
> Fatal server error:
> [172902
Your message dated Tue, 19 Apr 2011 03:06:03 +
with message-id
and subject line Bug#622653: fixed in xserver-xorg-video-intel 2:2.15.0-1
has caused the Debian Bug report #622653,
regarding Fatal server error: Caught signal 11 (Segmentation fault). Server
aborting
to be marked as done.
This
Modestas Vainius (17/04/2011):
> The bug is i965 specific. Upstream has just fixed it hence the fix
> is NOT included in the latest 2.15.0 release. It would great if you
> could add the attached patch (which is a backport from upstream) to
> the 2.15.0 package.
Thanks for the tip, will c-p that.
t; > > > [ 5306.687] 11: /usr/bin/Xorg (0x40+0x48909) [0x448909]
> > > > [ 5306.687] 12: /usr/bin/Xorg (0x40+0x257ab) [0x4257ab]
> > > > [ 5306.687] 13: /lib/libc.so.6 (__libc_start_main+0xfd)
> > > > [0x7f5207e55c4d] [ 5306.687] 14: /usr/bin/Xorg
0: /usr/bin/Xorg (0x40+0x46082) [0x446082]
> > > [ 5306.687] 11: /usr/bin/Xorg (0x40+0x48909) [0x448909]
> > > [ 5306.687] 12: /usr/bin/Xorg (0x40+0x257ab) [0x4257ab]
> > > [ 5306.687] 13: /lib/libc.so.6 (__libc_start_main+0xfd)
> > > [0x7f5207e55c4d] [ 5306.68
]
> > [ 5306.687] 10: /usr/bin/Xorg (0x40+0x46082) [0x446082]
> > [ 5306.687] 11: /usr/bin/Xorg (0x40+0x48909) [0x448909]
> > [ 5306.687] 12: /usr/bin/Xorg (0x40+0x257ab) [0x4257ab]
> > [ 5306.687] 13: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f5207e55c4d]
&g
Processing commands for cont...@bugs.debian.org:
> forwarded 622653 https://bugs.freedesktop.org/show_bug.cgi?id=36319
Bug #622653 [xserver-xorg-video-intel] Fatal server error: Caught signal 11
(Segmentation fault). Server aborting
Set Bug forwarded-to-address to
'https://bugs.freedes
ibc_start_main+0xfd) [0x7f5207e55c4d]
> [ 5306.687] 14: /usr/bin/Xorg (0x40+0x25339) [0x425339]
> [ 5306.687] Segmentation fault at address (nil)
> [ 5306.687]
> Fatal server error:
> [ 5306.687] Caught signal 11 (Segmentation fault). Server aborting
> [ 5306.687]
> [ 530
On Do, 2011-04-14 at 09:43 +0200, Julian Andres Klode wrote:
> On Mi, 2011-04-13 at 19:33 +0200, Cyril Brulebois wrote:
> > It'd be nice if you could test the commit you mentioned and let us
> > know.
> I've built the 903 pre-release and will install it now.
This commit actually reverts a commit ma
4294967295, 0, 1, 8152312, 0, 0, 22193824, 0}}, sa_flags = -1708665870, sa_restorer = 0x1}
sigs = {__val = {32, 0 }}
#2 0x0045ca2e in OsAbort () at ../../os/utils.c:1274
No locals.
#3 0x0046786d in ddxGiveUp () at ../../../../hw/xfree86/common/xf86Init.c:940
i =
Processing commands for cont...@bugs.debian.org:
> severity 622653 important
Bug #622653 [xserver-xorg-video-intel] Fatal server error: Caught signal 11
(Segmentation fault). Server aborting
Severity set to 'important' from 'grave'
> severity 622635 wishlist
Bug #622
severity 622635 important
thanks
Hi,
Julian Andres Klode (13/04/2011):
> Backtrace:
> [ 5306.687] 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x4aacc8]
> [ 5306.687] 1: /usr/bin/Xorg (0x40+0x61e59) [0x461e59]
> [ 5306.687] 2: /lib/libpthread.so.0 (0x7f52090f9000+0xef60) [0x7f5209107f60]
> [
Segmentation fault at address (nil)
> [ 5306.687]
> Fatal server error:
> [ 5306.687] Caught signal 11 (Segmentation fault). Server aborting
> [ 5306.687]
> [ 5306.687]
This may be fixed in 59ed6b05db99d7e5144f4f8499c67cee9b833673.
Revert "i965: Convert to relative relocations for
/bin/Xorg (0x40+0x25339) [0x425339]
[ 5306.687] Segmentation fault at address (nil)
[ 5306.687]
Fatal server error:
[ 5306.687] Caught signal 11 (Segmentation fault). Server aborting
[ 5306.687]
[ 5306.687]
-- Package-specific info:
X server symlink status
Your message dated Sat, 6 Mar 2010 17:20:40 +0100
with message-id <20100306162040.ga7...@loulous.org>
and subject line Re: Bug#406061: "X: user not authorized to run the X server,
aborting" -> /etc/X11/Xwrapper.config missing
has caused the Debian Bug report #406061,
reg
On Wed, Jan 13, 2010 at 14:09:16 +0800, Peng Tao wrote:
> Not sure if this is related. But I'm expericing GDM segfault after
> last update on Jan 11. I can't use GDM at all now. At first, I thought
> this might be becase I was using local compiled xserver/mesa. But as I
> reinstall xserver package
Not sure if this is related. But I'm expericing GDM segfault after
last update on Jan 11. I can't use GDM at all now. At first, I thought
this might be becase I was using local compiled xserver/mesa. But as I
reinstall xserver package from sid repository, GDM still segfaults
every time I start it.
a859]
18: /usr/bin/X (0x40+0x25b85) [0x425b85]
19: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f22d8956abd]
20: /usr/bin/X (0x40+0x25779) [0x425779]
Segmentation fault at address (nil)
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
When I reboot my box agai
Your message dated Sat, 28 Nov 2009 21:37:34 +
with message-id
and subject line Bug#550970: fixed in xserver-xorg-input-evdev 1:2.3.1-1
has caused the Debian Bug report #550970,
regarding xserver-xorg: Caught signal 11. Server aborting
to be marked as done.
This means that you claim that
reassign 550970 xserver-xorg-input-evdev
tag 550970 fixed-upstream
forwarded 550970 http://bugs.freedesktop.org/show_bug.cgi?id=23048
kthxbye
On Thu, Oct 15, 2009 at 06:31:17 +0200, Giuseppe Sacco wrote:
> Il giorno mer, 14/10/2009 alle 17.28 +0200, Julien Cristau ha scritto:
> > On Wed, Oct 14,
Processing commands for cont...@bugs.debian.org:
> reassign 550970 xserver-xorg-input-evdev
Bug #550970 [xserver-xorg] xserver-xorg: Caught signal 11. Server aborting
Bug reassigned from package 'xserver-xorg' to 'xserver-xorg-input-evdev'.
Bug No longer marked as found i
Il giorno mer, 14/10/2009 alle 17.28 +0200, Julien Cristau ha scritto:
> On Wed, Oct 14, 2009 at 16:30:02 +0200, Giuseppe Sacco wrote:
[...]
> > Backtrace:
> > 0: /usr/bin/X(xorg_backtrace+0x3b) [0x81314cb]
> > 1: /usr/bin/X(xf86SigHandler+0x51) [0x80c57f1]
> > 2: [0xb7f4b400]
> > 3: /usr/bin/X(Blo
On Wed, Oct 14, 2009 at 17:55:29 +0200, Giuseppe Sacco wrote:
> It seems the patch is not for this package: do you know what package
The xserver-xorg package is mostly empty...
> should I patch and recompile?
>
xserver-xorg-input-evdev.
Cheers,
Julien
--
To UNSUBSCRIBE, email to debian-x-r
Hi Julien,
Il giorno mer, 14/10/2009 alle 17.28 +0200, Julien Cristau ha scritto:
> On Wed, Oct 14, 2009 at 16:30:02 +0200, Giuseppe Sacco wrote:
[...]
> > Backtrace:
> > 0: /usr/bin/X(xorg_backtrace+0x3b) [0x81314cb]
> > 1: /usr/bin/X(xf86SigHandler+0x51) [0x80c57f1]
> > 2: [0xb7f4b400]
> > 3: /u
On Wed, Oct 14, 2009 at 16:30:02 +0200, Giuseppe Sacco wrote:
> About once a week, I see X restarted while I have an X session running.
> I did not find a reason for that. This time it happened while
> reconnecting the power cord to the laptop.
>
> Xorg.0.log.old ends with these lines:
>
> [...]
/X(BlockHandler+0x94) [0x8090454]
4: /usr/bin/X(WaitForSomething+0x124) [0x812ee74]
5: /usr/bin/X(Dispatch+0x96) [0x808c5f6]
6: /usr/bin/X(main+0x3aa) [0x8071b8a]
7: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7bdd7a5]
8: /usr/bin/X [0x8071051]
Fatal server error:
Caught signal 11. Server aborting
Your message dated Sun, 04 Oct 2009 17:05:35 +
with message-id
and subject line Bug#548716: fixed in xorg-server 2:1.7.0-1
has caused the Debian Bug report #548716,
regarding xserver-xorg_1%3a7.4+4_i386.deb - Caught signal 11. Server aborting
to be marked as done.
This means that you claim
Your message dated Wed, 30 Sep 2009 22:56:39 +
with message-id
and subject line Bug#548724: fixed in xorg-server 2:1.6.4-2
has caused the Debian Bug report #548724,
regarding xserver-xorg_1%3a7.4+4_i386.deb - Caught signal 11. Server aborting
to be marked as done.
This means that you claim
Your message dated Wed, 30 Sep 2009 14:29:04 +0300
with message-id <200909301429.04920.sha...@ukr.net>
and subject line dup of 548719
has caused the Debian Bug report #549010,
regarding xserver-xorg_1%3a7.4+4_i386.deb - Caught signal 11. Server aborting
to be marked as done.
This means th
Will Set wrote:
> Package: xserver-xorg
> Version: 1:7.4+3
> Severity: minor
>
> After upgrading Sept 28 2009 X aborted.
Aborted with what messages at the end of Xorg.0.log ?
> My first thought was to upgrade from 2.6.30-2-686 to 2.6.31 to match to the
> build machine.
>
Should be useless.
0-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages xserver-xorg depends on:
ii console-setup 1.45 console font and keymap setup prog
ii hal0.5.13-3 Hardware Abs
01fff000:end of stolen memory
(II) intel(0): 0x01fff000-0x0fff: DRI memory manager (229380 kB)
(II) intel(0): 0x1000:end of aperture
(II) intel(0): BO memory allocation layout:
(II) intel(0): 0x01fff000:start of memory manager
(II) intel(0): 0x0202-0x028
Shaddy Baddah writes:
> (II) Bus 1: bridge is at (0:1:1), (0,1,1), BCTRL: 0x0023 (VGA_EN is cleared)
> (--) PCI:*(1:2:0) ATI Technologies Inc 3D Rage Pro 215GP rev 92, Mem @
> 0xe100/24, 0xe200/12, BIOS @ 0xe102/0
> (--) PCI: (2:1:0) S3 Inc. 86c764/765 [Trio32/64/64V+] rev 84, Mem @
>
uot;X.Org Foundation"
compiled for 1.4.2, module version = 0.1.0
ABI class: X.Org Video Driver, version 2.0
Backtrace:
Fatal server error:
Caught signal 11. Server aborting
---
Contents of /var/log/Xorg.1.log:
X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, R
Your message dated Sun, 01 Jun 2008 13:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#455313: fixed in xserver-xorg-video-sunffb 1:1.1.0-4
has caused the Debian Bug report #455313,
regarding Caugh signal 11. Server aborting (sparc64 system)
to be marked as done.
This
signal
11. Server aborting"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have n
reassign 467388 xserver-xorg-core
forcemerge 463222 467388
thank you
Nelson A. de Oliveira wrote:
> There is already some time that X is crashing here, with no apparent
> motive.
> I can reproduce it by opening OpenOffice and clicking on the "File"
> menu. It crashs X instantly, then it restart
Processing commands for [EMAIL PROTECTED]:
> reassign 467388 xserver-xorg-core
Bug#467388: xserver-xorg: X is crashing with "Fatal server error: Caught signal
11. Server aborting"
Bug reassigned from package `xserver-xorg' to `xserver-xorg-core'.
> forcemerge 463
e0) [0xa7cb4450]
10: /usr/bin/X(FontFileCompleteXLFD+0x205) [0x8073a81]
Fatal server error:
Caught signal 11. Server aborting
And there is also another line that appears on the log:
(WW) intel(0): Existing errors found in hardware state.
My xorg.conf is available at
http://people.debian.org/~n
Adam Cécile (Le_Vert) a écrit :
Brice Goglin a écrit :
Adam Cécile (Le_Vert) wrote:
Did this work in this past? Accordingly to bug #392514, some Sun
Elite3D
are not supported in Xorg.
I can't tell you if it worked because I just got this hardware.
Xorg seems to detect the card and
Processing commands for [EMAIL PROTECTED]:
> reassign 463794 xserver-xorg-video-sunffb
Bug#463794: Caugh signal 11. Server aborting (sparc64 system)
Bug reassigned from package `xorg' to `xserver-xorg-video-sunffb'.
> forcemerge 455313 463794
Bug#455313: xserver-xorg-video-sunf
reassign 463794 xserver-xorg-video-sunffb
forcemerge 455313 463794
forwarded 455313 https://bugs.freedesktop.org/show_bug.cgi?id=14347
thank you
Adam Cécile (Le_Vert) wrote:
> I managed to get a gdb backtrace but everything seems to be related to
> sunfb driver, which doesn't have any debug pack
Brice Goglin a écrit :
Adam Cécile (Le_Vert) wrote:
Did this work in this past? Accordingly to bug #392514, some Sun Elite3D
are not supported in Xorg.
I can't tell you if it worked because I just got this hardware.
Xorg seems to detect the card and initialize it properly, so I gue
Brice Goglin a écrit :
Adam Cécile (Le_Vert) wrote:
Package: xorg
Version: 1:7.3+10
Severity: important
Hello,
Both current lenny (1:7.2-5) and sid (1:7.3+10) xorg don't work on my
SunBlade 1000 with two Sun Elite3D framebuffer video cards.
/var/log/Xorg.0.log is attached to this bug report
Adam Cécile (Le_Vert) wrote:
>> Did this work in this past? Accordingly to bug #392514, some Sun Elite3D
>> are not supported in Xorg.
>>
> I can't tell you if it worked because I just got this hardware.
> Xorg seems to detect the card and initialize it properly, so I guess
> it's not related to
Adam Cécile (Le_Vert) wrote:
> Package: xorg
> Version: 1:7.3+10
> Severity: important
>
> Hello,
>
> Both current lenny (1:7.2-5) and sid (1:7.3+10) xorg don't work on my
> SunBlade 1000 with two Sun Elite3D framebuffer video cards.
> /var/log/Xorg.0.log is attached to this bug report.
Did this
"
(**) Option "CustomKeycodes" "off"
(**) Generic Keyboard: CustomKeycodes disabled
(**) Option "Protocol" "ImPS/2"
(**) Configured Mouse: Device: "/dev/input/mice"
(**) Configured Mouse: Protocol: "ImPS/2"
(**) Option "CorePointer"
(**) Configured Mouse: always reports core events
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 9
(**) Configured Mouse: Sensitivity: 1
(II) evaluating device (Configured Mouse)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) evaluating device (Generic Keyboard)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Backtrace:
Fatal server error:
Caught signal 11. Server aborting
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
The only possibility out of the listed that I think could have occurred was
that xserver-common was purged at some point after the etch upgrades.
Processing commands for [EMAIL PROTECTED]:
> tags 406061 moreinfo
Bug#406061: "X: user not authorized to run the X server, aborting" ->
/etc/X11/Xwrapper.config missing
There were no tags set.
Tags added: moreinfo
> thank you
Stopping processing here.
Please contact me if
tags 406061 moreinfo
thank you
I don't see how your Xwrapper.config could have been removed with the
current preinst/postinst scripts in x11-common. Do you have some
Xwrapper.config.dpkg-*?
I wonder whether you had this file right before the upgrade. x11-common
postinst does not recreate one if
Hi,
Olaf, you got no /etc/X11/Xwrapper.config at all after upgrading
x11-common? Or an empty one?
I do not remember, this is more than 3 months ago...
> Do you remember seeing any error in the
postinst script output?
I got several errors AFAIK which seems to be normal for a dist-upgrade. B
In my case, I had no Xwrapper.config at all; plenty of space.
kitlann, what did you get? an empty Xwrapper.config? a file containing a
wrong allowed_users= line?
Hi,
Olaf, you got no /etc/X11/Xwrapper.config at all after upgrading
x11-common? Or an empty one? Do you remember seeing any error in the
postinst script output?
kitlann, what did you get? an empty Xwrapper.config? a file containing a
wrong allowed_users= line?
Did you guys have space available
I had the same problem. Running "dpkg-reconfigure x11-common" caused the
Xwrapper.config file to be regenerated.
--
Ted Lin
Your message dated Wed, 17 Jan 2007 19:16:36 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#304108: xserver-xfree86: Fatal server error: Caught signal
11. Server aborting
has caused the attached Bug report to be marked as done.
This means that you claim that the problem ha
On 01/17/07 10:01, Brice Goglin wrote:
[...]
> Did you reproduce this problem recently?
[...]
The good news is that I haven't.
The bad news is that we seem to have lost the
chance to debug it.
Thanks,
Kingsley
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tro
Hi, Brice
BG> About 2 years ago, you reported a bug to the Debian BTS regarding the X
BG> server failing to start when trying to load glx, getting signal 11. Did
BG> you reproduce this problem recently? If not, I will close this bug in
BG> the next weeks.
Problem is NOT gone. I've got a war again
Hi Kinsley,
About 2 years ago, you reported a bug to the Debian BTS regarding the X
server being called by signal 11 on a Geforce3 TI200 board. Did you
reproduce this problem recently? If not, I will close this bug in the
next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Hi Alexey,
About 2 years ago, you reported a bug to the Debian BTS regarding the X
server failing to start when trying to load glx, getting signal 11. Did
you reproduce this problem recently? If not, I will close this bug in
the next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PRO
Package: xorg
Version: 1:7.1.0-9
Severity: critical
Justification: X is only usable by root after upgrade from sarge
I just dist-upgraded from sarge to etch and could not start X as a normal
user, only as root. Creating the file /etc/X11/Xwrapper.config with one line
containing "allowed_users=cons
I just upgraded
ttf-freefont, xfs, freetype2, libttf2, oneko,
procmeter, rxvt, tkdesk, xboing, xtron
and removed
xf86setup, xfonts-pex, xfntil2, xesslite,
oledit, pavuk-x86-linux-glibc1-xt,
pointerlite, rv50-linux20, tk42, wabi,
wordperfect, xesslite, xlib6
and the GIM
* Kingsley G. Morse Jr. wrote:
> X can be made to crash by doing the following:
[...]
No crash when I tried that on my sarge box.
Norbert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
g/XFree86.0.log.old for
Fatal server error:
Caught signal 11. Server aborting
It crashed every time I tried, even with the "nv"
driver.
Thanks,
Kingsley
-- Package-specific info:
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500,
Your message dated Mon, 20 Dec 2004 04:13:48 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#284306: xserver-common: Problem with Xwrapper : X: user
not authorized to run the X server, aborting.
has caused the attached Bug report to be marked as done.
This means that you
Processing commands for [EMAIL PROTECTED]:
> tag 284306 - patch
Bug#284306: xserver-common: Problem with Xwrapper : X: user not authorized to
run the X server, aborting.
Tags were: patch
Tags removed: patch
> tag 284306 + unreproducible
Bug#284306: xserver-common: Problem with Xwrapp
On Fri, Dec 10, 2004 at 10:50:02PM +0100, Olaf Zaplinski wrote:
> Branden Robinson wrote:
> >Hmm...did you perhaps upgrade your kernel?
>
> Yes, but after building my own 2.6.9, everything worked for several days up
> to 'day X'. I can only imagine that cron-apt updated some packages, other
> ch
Hi!
Branden Robinson wrote:
Hmm...did you perhaps upgrade your kernel?
Yes, but after building my own 2.6.9, everything worked for several days up
to 'day X'. I can only imagine that cron-apt updated some packages, other
changes were not done.
What I did then was:
- dumping my former-Wood
.6
#3 0x08464b8c in ddxGiveUp () at xf86Init.c:1173
#4 0x08464c6b in AbortDDX () at xf86Init.c:1224
#5 0x08508bd7 in AbortServer () at utils.c:436
#6 0x0850a563 in FatalError (f=0x8a26ea0 "Caught signal %d. Server
aborting\n") at utils.c:1421
#7 0x0847fbf5 in xf86SigHandl
Processing commands for [EMAIL PROTECTED]:
> retitle 281885 xserver-xfree86: [i810] SEGV when initializing int10 on 82865G
> Integrated Graphics Device rev 2
Bug#281885: Caught signal 11. Server aborting
Changed Bug title.
> severity 281885 important
Bug#281885: xserver-xfree86: [i
user not authorized to run the X server, aborting.
Regards.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (900, 'testing'), (70, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap
: Intel(r)865G Graphics Chip Accelerated VGA BIOS
(II) I810(0): VESA VBE OEM Software Rev: 1.0
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(r)865G Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): Integrated
Processing commands for [EMAIL PROTECTED]:
> tag 270806 - upstream moreinfo
Bug#270806: xserver-xfree86: [ati/r128] SEGV at startup on Rage 128 RL/VR AGP
rev 0
Tags were: moreinfo upstream
Tags removed: upstream, moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistan
Branden Robinson wrote:
Fatal server error:
Caught signal 11. Server aborting
Please try reverting to the "ati" driver, but leaving "UseFBDev" set to
false.
Does the bug stay gone?
I have tried the four combinations of driver and UseFBDev. Two work, two
don't,
xe400
(--) R128(0): MMIO registers at 0xe900
Symbol xf86ForceHWCursor from module /usr/X11R6/lib/modules/drivers/r128_drv.o
is unresolved!
Symbol xf86ForceHWCursor from module /usr/X11R6/lib/modules/drivers/r128_drv.o
is unresolved!
*** If unresolved symbols were reported above, they mig
Processing commands for [EMAIL PROTECTED]:
> retitle 270806 xserver-xfree86: [ati/r128] SEGV at startup on Rage 128 RL/VR
> AGP rev 0
Bug#270806: /usr/X11R6/bin/startx: Caught signal 11. Server aborting
Changed Bug title.
> tag 270806 + upstream moreinfo
Bug#270806: xserver-xfree86:
Debian Bug Tracking System wrote:
I have a workaround. This works:
Section "Device"
Identifier "Generic Video Card"
# Driver "ati"
Driver "r128"
Option "UseFBDev" "false"
Option "SWcursor" "true"
EndSection
I tried vesa and vesafb drivers but they reduc
Your message dated Wed, 8 Sep 2004 06:09:35 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#270561: xserver-xfree86: Fatal server error: Caught signal
11. Server aborting
has caused the attached Bug report to be marked as done.
This means that you claim that the p
m writing is to report that its
> intermittently crashing.
>
> The last error message it reports in
> /var/log/XFree86.0.log.old is
>
> Fatal server error:
> Caught signal 11. Server aborting
>
> The contents of the whoe file are included below.
> * xserver-x
86.0.log.old is
Fatal server error:
Caught signal 11. Server aborting
The contents of the whoe file are included below.
-- Package-specific info:
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i68
!
Fatal server error:
Caught signal 4. Server aborting
***
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82)
01:00.0 Class 0300: 102b:0525 (rev 82)
### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X
!
Fatal server error:
Caught signal 4. Server aborting
***
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82)
01:00.0 Class 0300: 102b:0525 (rev 82)
### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X
Hi,
i own a NVidia GeForce2.
i use X 4.2.1 on Debian Sarge and when starting X Server Aborting.
joined Config and log
what's wrong ?
regards.
--
Founder of PhpFr.Org: http://www.phpfr.org
Member of The Association Gcu-Squad : http://gcu-squad.org
PhpFr.Org is a member of Ne
Hi,
i own a NVidia GeForce2.
i use X 4.2.1 on Debian Sarge and when starting X Server Aborting.
joined Config and log
what's wrong ?
regards.
--
Founder of PhpFr.Org: http://www.phpfr.org
Member of The Association Gcu-Squad : http://gcu-squad.org
PhpFr.Org is a member of Ne
Package: xfree86-common
Version: 4.1.0-16
Severity: grave
Justification: renders package unusable
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux Apricot 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages xfree86-common
Package: xfree86-common
Version: 4.1.0-16
Severity: grave
Justification: renders package unusable
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux Apricot 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages xfree86-common
Hello.
try
dpkg-reconfigure xserver-common
At Thu, 7 Dec 2000 22:26:29 -0500 (EST),
Kyle Sallee wrote:
>
> After updating XFree86 in woody from 4.0.1-9 to a 4.0.10
> a previously perfectly running XFree86 decides that now
> only root is permitted to startx.
:
Hello-
Yes, I've the same problem when using startx. Logging in through xdm
works, though.
-Dave Barnett
On Thu, 7 Dec 2000, Kyle Sallee wrote:
> After updating XFree86 in woody from 4.0.1-9 to a 4.0.10
> a previously perfectly running XFree86 decides that now
> only root is permitted to sta
After updating XFree86 in woody from 4.0.1-9 to a 4.0.10
a previously perfectly running XFree86 decides that now
only root is permitted to startx. The second line of
/etc/Xserver is Console and I have even tried Anybody
but still no change. When I backed out of the update
back to the version
Hello.
try
dpkg-reconfigure xserver-common
At Thu, 7 Dec 2000 22:26:29 -0500 (EST),
Kyle Sallee wrote:
>
> After updating XFree86 in woody from 4.0.1-9 to a 4.0.10
> a previously perfectly running XFree86 decides that now
> only root is permitted to startx.
:
--
To UNSUBSCRIBE, email to [E
Hello-
Yes, I've the same problem when using startx. Logging in through xdm
works, though.
-Dave Barnett
On Thu, 7 Dec 2000, Kyle Sallee wrote:
> After updating XFree86 in woody from 4.0.1-9 to a 4.0.10
> a previously perfectly running XFree86 decides that now
> only root is permitted to st
After updating XFree86 in woody from 4.0.1-9 to a 4.0.10
a previously perfectly running XFree86 decides that now
only root is permitted to startx. The second line of
/etc/Xserver is Console and I have even tried Anybody
but still no change. When I backed out of the update
back to the version
99 matches
Mail list logo
