Your message dated Sat, 27 Jan 2018 11:52:11 +
with message-id
and subject line Re: Bug#885919: amdgpu: Can't start X with amdgpu kernel module
has caused the Debian Bug report #885919,
regarding amdgpu: Can't start X with amdgpu kernel module
to be marked as done.
This means that
Package: xserver-xorg-video-amdgpu
Version: 1.4.0-1
Severity: important
File: amdgpu
Dear Maintainer,
After a recent upgrade, I'm not able to start X with the amdgpu kernel module.
I had to blacklist amdgpu module to be able to start X using the Intel's IGP.
I attach some information I think it
For your information :
sarge::Info::libc::sockets::localnamespace::details has :
w
You should compute the LENGTH parameter for a socket address in the
local namespace as the sum of the size of the `sun_family' component
and the string length (_not_
Hi David.
> Have you seen the annotation that Aurelien did on Jan 2nd
> in the upstream bug report?:
Yes, it is another approach to fix it.
In fact, this coding style is already used i.e. in
extras/Mesa/src/glx/mini/miniglx_events.c
GNU/kFreeBSD has problem with
namelen = strlen(sockname.s
El miércoles, 9 de noviembre de 2005 09:25, Petr Salinger escribió:
[...]
> this bug started as
>
http://lists.alioth.debian.org/pipermail/glibc-bsd-devel/2005-November/000628.html
>
> On debian/kFreeBSD is not defined HasBSD44Sockets.
> It shouldn't be problem because FreeBSD kernel 5.4 and 6.0
>
Package: xorg-x11
Version: 6.8.2.dfsg.1-10
Tags: patch
Hi,
this bug started as
http://lists.alioth.debian.org/pipermail/glibc-bsd-devel/2005-November/000628.html
On debian/kFreeBSD is not defined HasBSD44Sockets.
It shouldn't be problem because FreeBSD kernel 5.4 and 6.0
tries to be compatible
On Sun, Oct 17, 2004 at 10:51:17PM -0700, Hardian Boby wrote:
> i've Installed latest Debian release but unable to
> configure X, just will not configure at all no matter
> what settings I try. Can anyone give me any advice
> such as generic settings I may try? Thanks in
> anticipation, everything
i've Installed latest Debian release but unable to
configure X, just will not configure at all no matter
what settings I try. Can anyone give me any advice
such as generic settings I may try? Thanks in
anticipation, everything was successfully installed.my
dektop is acer veriton 5500 with intel 828
tag 268731 + woody upstream
retitle 268731 xserver-xfree86: [vmware] crash with call to unresolved function
on PCI SVGA (FIFO) rev 0
thanks
On Sun, Aug 29, 2004 at 12:29:26AM +0300, Daniel Suha wrote:
> Package: xserver-xfree86
> Version: 4.1.0.1
> Severity: important
>
> Hi There,
>
> Whenever
Processing commands for [EMAIL PROTECTED]:
> tag 268731 + woody upstream
Bug#268731: Can't Start X Window
There were no tags set.
Tags added: woody, upstream
> retitle 268731 xserver-xfree86: [vmware] crash with call to unresolved
> function on PCI SVGA (FIFO) rev 0
Bug#268731:
Package: xserver-xfree86
Version: 4.1.0.1
Severity: important
Hi There,
Whenever I try to start the x window, this error message comes:
PEXExtensionInit: Couldn't open default PEX font file Roman_M
This should not happen!
An unresolved function was called!
I have just install
Your message dated Tue, 12 Aug 2003 11:24:40 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#204972: Can't start x
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 it
Package: xserver-xfree86
Version: 4.1.0.1
Debian 3.0 kernel 2.4
Laptop: HP Omnibook XE3 Mod: F3950JT GF
When I turn on my computer, X Server doesn't start. If I run
# startx
manually, it generates the following log (XFree86.0.log):
(above I attach lsdev and lspci outputs)
BEGIN OF LO
Your message dated Tue, 12 Aug 2003 11:24:40 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#204972: Can't start x
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 it
Package: xserver-xfree86
Version: 4.1.0.1
Debian 3.0 kernel 2.4
Laptop: HP Omnibook XE3 Mod: F3950JT GF
When I turn on my computer, X Server doesn't start. If I run
# startx
manually, it generates the following log (XFree86.0.log):
(above I attach lsdev and lspci outputs)
BEGIN OF LO
merge 178496 179894
thanks
On Wed, Feb 05, 2003 at 12:02:39PM +, Matt Hodges wrote:
> I can't start an X server with this version; there are unresolved
> symbols such as __glXLastContext. Version 4.2.1-3 works, and I've
> downgraded to this.
>
> There are also thousands of Elf_RelocateEntry e
Processing commands for [EMAIL PROTECTED]:
> merge 178496 179894
Bug#178496: xserver-xfree86: [core server] module loading broken on Alpha due
to GCC 3.2's new relocation type
Bug#179894: xserver-xfree86: Can't start X server (unresolved symbols).
Bug#178358: xserver-xfree86:
merge 178496 179894
thanks
On Wed, Feb 05, 2003 at 12:02:39PM +, Matt Hodges wrote:
> I can't start an X server with this version; there are unresolved
> symbols such as __glXLastContext. Version 4.2.1-3 works, and I've
> downgraded to this.
>
> There are also thousands of Elf_RelocateEntry e
Processing commands for [EMAIL PROTECTED]:
> merge 178496 179894
Bug#178496: xserver-xfree86: [core server] module loading broken on Alpha due to GCC
3.2's new relocation type
Bug#179894: xserver-xfree86: Can't start X server (unresolved symbols).
Bug#178358: xserver-xfree86:
Package: xserver-xfree86
Version: 4.2.1-5
Severity: important
I can't start an X server with this version; there are unresolved
symbols such as __glXLastContext. Version 4.2.1-3 works, and I've
downgraded to this.
There are also thousands of Elf_RelocateEntry errors in the log file:
Elf_Relocate
Package: xserver-xfree86
Version: 4.2.1-5
Severity: important
I can't start an X server with this version; there are unresolved
symbols such as __glXLastContext. Version 4.2.1-3 works, and I've
downgraded to this.
There are also thousands of Elf_RelocateEntry errors in the log file:
Elf_Relocate
Hi! I'm trying to migrate from Mandrake to Debian, but I can't make
X work. 9 out of 10 times I start it (be it via gdm, startx or just plain
'X') it will die with a signal 11. Sometimes it will start, and then I can
use it for hours in a row and it won't freeze or die.
I'm using XF
Hi! I'm trying to migrate from Mandrake to Debian, but I can't make
X work. 9 out of 10 times I start it (be it via gdm, startx or just plain
'X') it will die with a signal 11. Sometimes it will start, and then I can
use it for hours in a row and it won't freeze or die.
I'm using X
On Mon, Dec 11, 2000 at 10:49:14PM -0500, Branden Robinson wrote:
> Not sure what the problem is here; I don't know what would make the X
> server become a zombie process.
Actually, I do know. There was a bug in the X server wrapper. It's fixed
in 4.0.1-11.
--
G. Branden Robinson |
On Mon, Dec 11, 2000 at 10:49:14PM -0500, Branden Robinson wrote:
> Not sure what the problem is here; I don't know what would make the X
> server become a zombie process.
Actually, I do know. There was a bug in the X server wrapper. It's fixed
in 4.0.1-11.
--
G. Branden Robinson
Dunkel <[EMAIL PROTECTED]> -
> >
> > From: Harald Dunkel <[EMAIL PROTECTED]>
> > To: Branden Robinson <[EMAIL PROTECTED]>
> > Subject: gdm and kdm can't start X
> > Date: Mon, 11 Dec 2000 20:30:59 +0100
> > Delivered-To: [EMAIL PROTECTED
Dunkel <[EMAIL PROTECTED]> -
> >
> > From: Harald Dunkel <[EMAIL PROTECTED]>
> > To: Branden Robinson <[EMAIL PROTECTED]>
> > Subject: gdm and kdm can't start X
> > Date: Mon, 11 Dec 2000 20:30:59 +0100
> > Delivered-To: [EMAIL PROTECTED
unkel <[EMAIL PROTECTED]> -
>
> From: Harald Dunkel <[EMAIL PROTECTED]>
> To: Branden Robinson <[EMAIL PROTECTED]>
> Subject: gdm and kdm can't start X
> Date: Mon, 11 Dec 2000 20:30:59 +0100
> Delivered-To: [EMAIL PROTECTED]
> Delivered-To: [EMAIL PROTECTED]
&
Not sure what the problem is here; I don't know what would make the X
server become a zombie process.
- Forwarded message from Harald Dunkel <[EMAIL PROTECTED]> -
From: Harald Dunkel <[EMAIL PROTECTED]>
To: Branden Robinson <[EMAIL PROTECTED]>
Subject: gdm and kdm
unkel <[EMAIL PROTECTED]> -
>
> From: Harald Dunkel <[EMAIL PROTECTED]>
> To: Branden Robinson <[EMAIL PROTECTED]>
> Subject: gdm and kdm can't start X
> Date: Mon, 11 Dec 2000 20:30:59 +0100
> Delivered-To: [EMAIL PROTECTED]
> Delivered-To: [EMAIL PROTECTED]
&
Not sure what the problem is here; I don't know what would make the X
server become a zombie process.
- Forwarded message from Harald Dunkel <[EMAIL PROTECTED]> -
From: Harald Dunkel <[EMAIL PROTECTED]>
To: Branden Robinson <[EMAIL PROTECTED]>
Subject: gdm and
31 matches
Mail list logo
