Control: tags -1 + upstream patch
On Fri, 2016-08-12 at 00:20 +0800, Paul Wise wrote:
> [297584.554] Failed to compile VS: 0:13(43): error: `pos' undeclared
> 0:13(14): error: operands to arithmetic operators must be numeric
> 0:13(13): error: operands to arithmetic operators must be numeric
The
Processing control commands:
> tags -1 + upstream patch
Bug #834054 [xserver-xorg-core] Xorg: Fatal server error: GLSL compile failure:
Failed to compile VS: 0:13(43): error: `pos' undeclared
Added tag(s) patch and upstream.
--
834054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bu
ffset + primitive.xy + pos) * fill_size_inv;
}
[297584.554] (EE)
Fatal server error:
[297584.554] (EE) GLSL compile failure
-- Package-specific info:
X server symlink status:
lrwxrwxrwx 1 root root 13 Apr 6 2013 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Jul 20 11:00
Your message dated Mon, 12 May 2014 09:47:53 -0500
with message-id <20140512144753.ga6...@blackpatchpanel.com>
and subject line Re: Bug#747841: Acknowledgement (xorg: Fatal server error:
(EE) no screens found(EE))
has caused the Debian Bug report #747841,
regarding xorg: Fatal server erro
ersion 15.0
[ 431.984] (WW) Falling back to old probe method for vesa
[ 431.984] (II) Loading sub module "dri2"
[ 431.984] (II) LoadModule: "dri2"
[ 431.984] (II) Module "dri2" already built-in
[ 431.984] (EE) NOUVEAU(0): [drm] failed to set drm interface ver
X THE 'fbdev' DRIVER!
(EE)
Fatal server error:
(EE) Server is already active for display 0
Despite this, xorg seems to work ok. Reproduced on laptop and VirtualBox.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact li
Your message dated Thu, 14 Jun 2012 10:17:22 +0200
with message-id <20120614081722.gc26...@mraw.org>
and subject line Re: Bug#677451: Fatal server error: xf86OpenConsole: Cannot
find a free VT
has caused the Debian Bug report #677451,
regarding Fatal server error: xf86OpenConsole: Cannot
Bug solved with downgrade of core xorg files to 1.11.4-1 and xorg input
files to lower versions matching the 1.11.4-1 release dates. This is
followed with install of fglrx driver version 12-4-1 .
Further information as below:
On 06/11/2012 06:01 AM, Issam Mehssani wrote:
I believe the pr
quot;
[ 312.881] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 312.881] (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
[ 312.881] compiled for 1.4.99.906, module version = 8.96.4
[ 312.881] (II) ATI Proprietary Linux Driver Version Identifier:8.96.4
[ 312.881] (II
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.
5205e34000+0x27473)
> > > > [0x7f5205e5b473] [ 5306.687] 8: /usr/bin/Xorg (miPolyRectangle+0xd8)
> > > > [0x550228]
> > > > [ 5306.687] 9: /usr/bin/Xorg (0x40+0xdf142) [0x4df142]
> > > > [ 5306.687] 10: /usr/bin/Xorg (0x40+0x46082) [0x446082]
&g
0: /usr/bin/Xorg (0x40+0x46082) [0x446082]
> > > [ 5306.687] 11: /usr/bin/Xorg (0x400000+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
On Mi, 2011-04-13 at 19:33 +0200, Cyril Brulebois wrote:
> 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]
> > [ 530
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]
> [
[ 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 (0x40+0x25339) [0x425339]
> [ 5306.687]
/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 Tue, 22 Feb 2011 20:39:05 +0100
with message-id <20110222193905.ga7...@debian.org>
and subject line Re: Bug#508614: How it was fixed
has caused the Debian Bug report #508614,
regarding fatal server error: lockup after changing screen resolutions
to be marked as done.
This
Your message dated Tue, 13 Jul 2010 16:17:33 +
with message-id
and subject line Bug#579910: fixed in xserver-xorg-video-vmware 1:11.0.1-2
has caused the Debian Bug report #579910,
regarding xorg: Xorg -configure: Fatal server error: Caught signal 11
(Segmentation Fault)
to be marked as done
d kernel module "vmwgfx""
(II) vmware: Using vmwlegacy driver everything is fine.
Backtrace:
0: Xorg (xorg_backtrace+0x3b) [0x80addcb]
1: Xorg (0x8048000+0x5ab75) [0x80a2b75]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb77a240c]
3: Xorg (0x8048000+0x104294) [0x814c294]
4: Xorg (xf86LoadModules+0xe8) [0x80ae5a8]
5: Xorg (DoConfigure+0x7b) [0x80c07ab]
6: Xorg (InitOutput+0x1da) [0x80b04ba]
7: Xorg (0x8048000+0x1e73b) [0x806673b]
8: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xb74d7c76]
9: Xorg (0x8048000+0x1e4e1) [0x80664e1]
Segmentation fault at address (nil)
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional
information.
On Tue, Jun 29, 2010 at 15:51:24 -0700, Jorge Quintana wrote:
> Sorry about that, it is the first time I report something like this,
> not to mention I wasn´t sure on where to look for the logs, but I
> found this two in /var/log
>
Weird error.. I'd guess a bad interaction with xen is the most l
alling packages until I installed xserver-xorg and xorg
> using aptitude (this also installed all of the drivers)
> Everything was working fine (startx, xterm, mwm) until I´ve installed the xen
> kernel and booted into it
> 2.6.26-1-xen-amd64
>
> Now everytime I run startx I
of the drivers)
Everything was working fine (startx, xterm, mwm) until I´ve installed the xen
kernel and booted into it
2.6.26-1-xen-amd64
Now everytime I run startx I get the following error:
Fatal Server error:
xf86MapVidMem: Could not mmap framebuffer (0xc000,0x7f) (Invalid
argument)
I
Your message dated Sat, 6 Mar 2010 16:49:42 +0100
with message-id <20100306154942.ga7...@loulous.org>
and subject line Re: Bug#491205: xserver-xorg-video-intel causes X to crash
irrecoverably and without warning (fatal server error: lockup)
has caused the Debian Bug report #491205,
reg
Your message dated Sun, 28 Feb 2010 21:05:57 +0100
with message-id <20100228200557.ga32...@debian.org>
and subject line Re: Bug#491230: xserver-xorg: X crashes with "Fatal Server
Error: lockup"
has caused the Debian Bug report #491230,
regarding xserver-xorg: X crashes with &qu
Try the patch available here:
https://bugs.freedesktop.org/show_bug.cgi?id=19643
I had rebuild package xserver-xorg-core with this patch, but there is no
effect. After 30 minutes of work new crash happened.
I found out that this problem is not with Firefox (Iceweasel). I watched
the cras
On Saturday 29 August 2009, Grigory Koshcheev wrote:
> I have the same problem for a long time. X crashes once at the month
> and I didn't think that it is great problem. For a last week X crashes
> every day, sometimes twice and more.
Try the patch available here:
https://bugs.freedesktop.org/sho
004d90 head: 0x4db4 len: 0x0001f001 start 0x
eir: 0x esr: 0x emr: 0x
instdone: 0xfa41 instpm: 0x
memmode: 0x0306 instps: 0x800f04c4
hwstam: 0xfffe ier: 0x0002 imr: 0x iir: 0x0070
Ring at virtual 0xa78a4000 head 0x4db4 tail 0x4d90 count 32759
4d34
On Thu, Jul 17, 2008 at 02:40:43PM -0500, kev wrote:
> Package: xserver-xorg
> Version: 1:7.3+12
> Severity: important
>
>
> During normal use of debian/lenny X suddenly crashes. in the error log
> it says "Fatal Server Error: lockup"
Does this still happen with
On Thu, Jul 17, 2008 at 06:46:08PM +0300, Arthur A wrote:
> Package: xserver-xorg-video-intel
> Version: 2:2.3.2-2
> Severity: important
>
> Seemingly at random, and infrequently, X will crash and I will often lose
> all open work. After a number of attempts to automatically restart I will
> be g
On Sun, 2009-04-05 at 22:26 +1000, Shaddy Baddah wrote:
> First up, contents of /proc/version:
>
> Linux version 2.6.26-1-sparc64 (Debian 2.6.26-13lenny2)
> (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian
> 4.1.2-25)) #1 Fri Mar 13 17:42:29 UTC 2009
>
weird, i would have exp
On 04/05/2009 07:39 PM, Julien Cristau wrote:
reassign 522605 xserver-xorg-core
forcemerge 488669 522605
kthxbye
On Sun, 2009-04-05 at 17:46 +1000, Shaddy Baddah wrote:
My understanding from
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500358 is that X on
sparc was basket-cased except for
Processing commands for cont...@bugs.debian.org:
> reassign 522605 xserver-xorg-core
Bug#522605: xserver-xorg-video-mga: Fatal server error: xf86MapDomainMem():
mmap() failure
Bug reassigned from package `xserver-xorg-video-mga' to `xserver-xorg-core'.
> forcemerge 488669 5
reassign 522605 xserver-xorg-core
forcemerge 488669 522605
kthxbye
On Sun, 2009-04-05 at 17:46 +1000, Shaddy Baddah wrote:
> My understanding from
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500358 is that X on
> sparc was basket-cased except for the builtin cards of various 64 bit
> spa
ly included the warning, as it
seems pertinent):
...
(==) MGA(0): MMIO registers at 0x10
(--) MGA(0): BIOS at 0x100
(II) Attempted to read BIOS 128KB from
/sys/bus/pci/devices/:02:03.0/rom: got 0KB
(WW) MGA(0): Video BIOS info block not detected!
Fatal server error:
xf86MapDomainMem():
Is someone going to answer this, and, dare I say, fix it, or is filing a bug
report a study in masturbation?
Your message dated Mon, 2 Feb 2009 16:52:27 +0900
with message-id <20090202165227.f2031684.jo...@csc.jp>
and subject line Re: Bug#498359: It cannot use at all by fatal server error
has caused the Debian Bug report #498359,
regarding It cannot use at all by fatal server error
to be marked a
Brice wrote:
> These patches have been applied upstream and 1.7.0 has been released.
> I'll try to package 1.7.0 today (for experimental only I think, is that
> fine for you?)
>
> Brice
>
Thank you, I appreciate.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of
Processing commands for cont...@bugs.debian.org:
> forwarded 498359 http://bugs.freedesktop.org/show_bug.cgi?id=18816
Bug#498359: It cannot use at all by fatal server error
Noted your statement that Bug has been forwarded to
http://bugs.freedesktop.org/show_bug.cgi?id=18816.
> tags
forwarded 498359 http://bugs.freedesktop.org/show_bug.cgi?id=18816
tags 498359 +fixed-upstream
thank you
Jonny wrote:
> Hi,
>
> It solved by applying the following patch:
> http://lists.freedesktop.org/archives/xorg/2008-December/041044.html
> http://lists.freedesktop.org/archives/xorg/2008-Dece
Your message dated Sat, 27 Dec 2008 12:51:51 +0200
with message-id <20081227105151.ga10...@localhost>
and subject line Sorry, the wrong package
has caused the Debian Bug report #509834,
regarding xdm: The X-server crashes with fatal server error "lockup"
to be marked as done.
Thi
Package: xdm
Version: 1:1.1.8-5
Severity: normal
The X-server crashes from time to time with the following error in the logs:
Fatal server error:
lockup.
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable&#
found 508614 2:2.3.2-2+lenny5
kthxbye
On Fri, Dec 19, 2008 at 02:24:55 -0600, Jeff Cliff wrote:
> currently installed:
> xserver-xorg-core v.2:1.4.2-9
> xserver-xorg-intel v.2:2.3.2-2+
the -intel version number looks incomplete, but thanks, I assume it's
the latest in lenny/sid.
> I saved a few
Processing commands for cont...@bugs.debian.org:
> found 508614 2:2.3.2-2+lenny5
Bug#508614: fatal server error: lockup after changing screen resolutions
Bug marked as found in version 2:2.3.2-2+lenny5.
> kthxbye
Stopping processing here.
Please contact me if you need assistance.
Debi
currently installed:
xserver-xorg-core v.2:1.4.2-9
xserver-xorg-intel v.2:2.3.2-2+
I saved a few xorg logs at the following URL
http://thedark.jabberwocky.ca/themusicgod1/xorg/
jeff
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
On Fri, Dec 12, 2008 at 19:43:38 -0600, themusicgod1 wrote:
> 3) ran gdm / gnome, got me to the login screen, and as others have been
> complaining about it was at the 'default' what, 640x480 resolution or
> something low(never got to find out what), went to change the resoultion
> in the gnome re
000102d0: 0720
000102d4:
000102d8: 0720
000102dc: 4000
000102e0: 0720
000102e4: 1900
Ring end
space: 28 wanted 32
Fatal server error:
lockup
Deleted xorg.conf...same error above now. dpkg-reconfigure no longer
allows me to choose my dri
Hi,
It solved by applying the following patch:
http://lists.freedesktop.org/archives/xorg/2008-December/041044.html
http://lists.freedesktop.org/archives/xorg/2008-December/041126.html
http://bugs.freedesktop.org/show_bug.cgi?id=18816
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
Your message dated Sat, 29 Nov 2008 10:40:17 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#491205: Consider closed
has caused the Debian Bug report #491205,
regarding xserver-xorg-video-intel causes X to crash irrecoverably and without
warning (fatal server error:
On Monday 17 November 2008, Tino Keitel wrote:
> you might try if the lockups go away if you put this line into the
> device section of /etc/X11/xorg.conf:
>
> Option "FramebufferCompression" "off"
>
> If it solves the problem, then you are hit by a bug that is solved in
> version 2.4 of the intel
Hi,
you might try if the lockups go away if you put this line into the
device section of /etc/X11/xorg.conf:
Option "FramebufferCompression" "off"
If it solves the problem, then you are hit by a bug that is solved in
version 2.4 of the intel driver.
Regards,
Tino
--
To UNSUBSCRIBE, email to
On Tue, Sep 9, 2008 at 21:18:31 +0900, Jonny wrote:
> Is xorg-server 1.5.0 supported?
>
It should be. Can you try building the version from upstream git, to
see if the problem you're seeing has been fixed?
The repo is at
git://anongit.freedesktop.org/git/xorg/driver/xf86-video-siliconmotion
Ch
0 0x03c0 - 0x03df (0x20) IS[B]
Fatal server error:
AddScreen/ScreenInit failed for driver 0
xorg.conf.gz
Description: Binary data
Xorg.0.log.gz
Description: Binary data
XINPUT: Adding extended input device "Keyboard" (type: KEYBOARD)
(--) Touchpad auto-dev sets device to /dev/input/event7
(**) Option "Device" "/dev/input/event7"
(--) Touchpad touchpad found
(--) Mouse: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse: ps2Ena
Frans Pop wrote:
On Friday 18 July 2008, Julien Cristau wrote:
Can you try the ExaNoComposite option in xorg.conf, see if this works
around the bug?
The problem is is knowing if it makes any difference or not because the
actual crash is so hard to reproduce. Personally I think I'd prefer to
On Friday 18 July 2008, Julien Cristau wrote:
> Can you try the ExaNoComposite option in xorg.conf, see if this works
> around the bug?
The problem is is knowing if it makes any difference or not because the
actual crash is so hard to reproduce. Personally I think I'd prefer to
wait for another
On Fri, Jul 18, 2008 at 13:09:35 +0300, Arthur A wrote:
>> Arthur A wrote:
>>> Seemingly at random, and infrequently, X will crash and I will often
>>> lose all open work. After a number of attempts to automatically restart
>>> I will be given a message saying that X has crashed and cannot be
>>>
Arthur A wrote:
Seemingly at random, and infrequently, X will crash and I will often
lose all open work. After a number of attempts to automatically restart
I will be given a message saying that X has crashed and cannot be
restarted. Switching to a different terminal killing all Xsessions and
GDM
Package: xserver-xorg
Version: 1:7.3+12
Severity: important
During normal use of debian/lenny X suddenly crashes. in the error log
it says "Fatal Server Error: lockup"
-- Package-specific info:
Contents of /var/lib/x11/X.roster:
xserver-xorg
/var/lib/x11/X.md5sum does not exist.
Processing commands for [EMAIL PROTECTED]:
> forcemerge 482425 483486
Bug#482425: xwindows can not be started after xinit 1.0.9-1 has been installed
Bug#483486: xinit: Fatal Server Error
Bug#482527: xorg: login by startx broken. System unusable.
Forcibly Merged 482425 482527 483486.
> tha
Package: xinit
Version: 1.0.8-1
Severity: normal
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=
Your message dated Sat, 17 May 2008 16:31:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#467058: This issue seems fixed in 2:1.4.1~git20080131-3
has caused the Debian Bug report #467058,
regarding xserver-xorg: X is crashing with "Fatal server error: Caught
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
nplanes = 4294967295
No matching visual for __GLcontextMode with visual class = 1 (32774),
nplanes = 4294967295
No matching visual for __GLcontextMode with visual class = 1 (32774),
nplanes = 4294967295
No matching visual for __GLcontextMode with visual class = 1 (32774),
420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800XT (R420) JP (AGP), ATI Radeon X800 SE (R420) (AGP),
ATI Radeon AIW X800 VE (R420) JT (AGP),
ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R
Here's a summary of what happen about this PCI breakage during the last
days:
Since umount /sys fixed the problem, it is clear that the bug is in the
sys-based PCI domain code. Jim rebuilt the server using David
Woodhouse's patch [1] which is applied in Fedora and disables the sysfs
code on archit
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.2
> retitle 422077 xserver-xorg: Fatal server error on sparc: xf86MapPciMem failed
Bug#422077: xserver-xorg: Fatal server error: xf86MapPciMem
Changed Bug title to xserver-xorg:
Your message dated Sun, 06 May 2007 23:34:21 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#406044: kdm crash: Fatal server error
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Hi Jim,
Fatal server error:
xf86MapPciMem: Could not mmap PCI memory
[base=0x426000,hostbase=0x426000,size=2000] (Inappropriate ioctl for device)
Could you try running Xorg within strace in case it helps us know which
ioctl fails?
Thanks,
Brice
,
ATI Radeon X800 (R420) JH (AGP), ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800XT (R420
sks. I downloaded
the X window package with tasksel.
When I reboot, X windows doesn't start and comes up with the following error
messages:
Fatal server error: no screens found
and (WW) ATI: PCI/AGP Mach64 in slot 0:17:0 could not be detected
(EE)No device detected
What
Eric Hanchrow wrote:
> I haven't repro'd this recently, but I'm 85% sure that if I tried, it
> would repro. It's pretty catastrophic (it forces me to reboot, iirc)
> that I don't want to do so unless you really think it'd be helpful.
>
What do you prefer me to do? Keep open until you get a cha
Hi Eric,
About 3 years ago, you reported a bug to the Debian BTS regarding the
debug XFree86 server frequently crashing unless NoAccel is set. 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]
I haven't repro'd this recently, but I'm 85% sure that if I tried, it
would repro. It's pretty catastrophic (it forces me to reboot, iirc)
that I don't want to do so unless you really think it'd be helpful.
--
Asking the Iraqi people to assume Saddam's debts
is rather like telling a man who has b
Hi,
About 4 years ago, you reported a bug to the Debian BTS regarding X not
working on a Mach64 board, possibly becaue of a wrong configuration.
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
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 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]
Hey Brice -
I have not seen this bug recently, no. In fact, I believe the problem
may have been caused by a faulty memory system on my machine. Please
feel free to close this bug --- and thanks for checking!! ;-)
-Rob
On 1/11/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
Hi Rob,
About 2 year
Your message dated Thu, 11 Jan 2007 20:42:13 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#289615: xserver-xfree86: [ati/atimisc] 'Fatal server
error: WaitForSomething(): select: errno=22' on Mach64 LP rev 220
has caused the attached Bug report to be marked as d
Hi Barry,
About 2 years ago, you reported a problem to the Debian BTS about the X
server crashing because of a select error. 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]
with a subject of
Hi Rob,
About 2 years ago, you reported a bug to the Debian BTS regarding a
crash of the X server when freeing a wrong resource. Did you reproduce
this problem recently? If not, I will close the bug in the next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
I no longer have access to laptop due to a change in... err...
circumstances.
I can't help, sorry.
--
OoberMick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi,
About 2 years ago, you reported (or replied to) a bug to the Debian BTS,
regarding a lockup of the Xserver while playing a video after suspend on
82845G chipset. Did any of you guys reproduce this problem recently? If
not, I will close the bug in the next weeks.
Thanks,
Brice
--
To UNSUBS
Processing commands for [EMAIL PROTECTED]:
> reassign 406044 xserver-xorg-core
Bug#406044: kdm crash: Fatal server error
Bug reassigned from package `kdm' to `xserver-xorg-core'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
nInit: Couldn't open default PEX font file Roman_M
(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Configured Mouse: Protocol: "ImPS/2"
(**) Configured Mouse: Core Pointer
(==) Configured Mouse: Buttons: 3
(**) Generic Mouse: Protocol: "ImPS/2"
(**)
rg-video-nv'.
> reassign 370137 xserver-xorg-video-nv
Bug#370137: Fatal server error: Caught signal 11. Aborting.
Bug reassigned from package `xorg' to `xserver-xorg-video-nv'.
> # Fix severity
> severity 370137 normal
Bug#370137: Fatal server error: Caught signal 11. Abor
with visual class = 1 (32774),
nplanes = 4294967295
No matching visual for __GLcontextMode with visual class = 1 (32774),
nplanes = 4294967295
No matching visual for __GLcontextMode with visual class = 1 (32774),
nplane
I get this error trying to start xdm 1.0.1-1 -
[...]
Could not init font path element /usr/share/fonts/X11, removing from
list!
Fatal server error:
could not open default font 'fixed'
[...]
I think all the necessary xfonts packages are installed -
ii xfo
Michel Dänzer wrote:
Good, but I'd recommend switching to a 2.6 kernel instead. :)
Yup, the box was flat anyway, so I've just re-installed with a 2.6 base.
BTW, what version of the radeon DRM does the 2.4 kernel have?
Ahh, I've got rid of the 2.4, sorry about that.
--
To UNSUBSCRIBE, emai
t up with DRI enabled because driver
> is incompatible with 2.4 kernel DRM since 6.9
Bug#353865: xserver-xorg: X crashes with Fatal Server Error. Caught Signal 11
Changed Bug title.
> kthxbye
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking syste
retitle 352840 [ati/radeon] Fails to start up with DRI enabled because driver
is incompatible with 2.4 kernel DRM since 6.9
retitle 353865 [ati/radeon] Fails to start up with DRI enabled because driver
is incompatible with 2.4 kernel DRM since 6.9
kthxbye
On Wed, 2006-02-22 at 11:59 +, Simon
On Wed, 2006-02-22 at 08:33 +, Simon Woodward wrote:
>
> I have reconfigured as you suggested but am still getting some problems.
>
> I have attached the current log and config file for you.
Thanks. This looks like a duplicate of
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352840 .
--
1 - 100 of 156 matches
Mail list logo
