Brice Goglin wrote:
Hi,
About 2 years ago, you reported (or replied to) a bug in the Debian BTS
regarding the X server not starting on a Cyrix 6x86 processor. Did any
of you guys reproduce this problem recently? With Xorg/Etch? With latest
xserver-xorg-core in unstable?
Thanks,
Brice
I have
Here is the output of /usr/share/bug/xserver-xorg-core/script 3>&1 from
the correct machine. Please disregard the previous output as it was
from another machine.
Contents of /var/lib/x11/X.roster:
xserver-xorg
/etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum.
X server sym
uh oh. that output was from the wrong machine. sorry. i will send
from the correct machine...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Mon, 28 May 2007 13:26:23 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426336: xorg: X fails to map legacy ROM on recent IA64
kernels
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If th
On Sun, May 27, 2007 at 19:26:15 -0700, [EMAIL PROTECTED] wrote:
> > Could you send the output of
> > /usr/share/bug/xserver-xorg-core/script 3>&1
>
>
> see attached
>
Unfortunately that attachment is empty. Can you resend and make sure
the information is there?
Thanks,
Julien
--
To UN
> "Brice" == Brice Goglin <[EMAIL PROTECTED]> writes:
Brice> Peter Chubb wrote:
>> Here it is. But the problem is that X is trying to map a 1M region
>> from location 0; on this machine you can't do that safely, so the
>> kernel prevents it.
>>
Brice> Right.
Brice> Note for the BTS: for th
Le Fri, May 18, 2007 at 11:39:21AM +0200, Michel Dänzer a écrit :
> On Fri, 2007-05-18 at 18:34 +0900, Charles Plessy wrote:
> >
> > I am not sure to understand the question, but after killing X, gdm
> > restarts it for me.
>
> If the problem was a GPU lockup, that probably wouldn't succeed, the
Peter Chubb wrote:
> Here it is. But the problem is that X is trying to map a 1M region
> from location 0; on this machine you can't do that safely, so the
> kernel prevents it.
>
Right.
Note for the BTS: for the record, see the header of [1], the patch has
been merged in 2.6.22-rc1.
> X Win
On May 27, 2007, at 5:31 PM, Brice Goglin wrote:
Well, it is up to you to decide whether you want the problem to be
fixed
soon or not :)
The question behind the question was (an I apologize for not asking
it directly the first time around), in light of my "real" life
situation, is your
> "Brice" == Brice Goglin <[EMAIL PROTECTED]> writes:
Brice> Peter Chubb wrote:
>> Package: xorg Severity: important
>>
>> Since patch 6d40fc514c9ea886dc18ddd20043a411816b63d1 went into the
>> Linux kernel, X has failed to work.
>>
>> The relevant line in Xorg.0.log is:
>>
>> Fatal server e
>
> When did this problem appear?
>From the point of installation onwards.
> Did you upgrade something as this time?
I upgrade fairly regularly but the problem has persisted.
>
> Could the problem be related to switching to a VT console and then back
> to X?
Definitely not. I happens con
Peter Chubb wrote:
> Package: xorg
> Severity: important
>
> Since patch 6d40fc514c9ea886dc18ddd20043a411816b63d1 went into the Linux
> kernel,
> X has failed to work.
>
> The relevant line in Xorg.0.log is:
>
> Fatal server error:
> xf86MapDomainMem(): mmap() failure
>
Please send the whole
Package: xorg
Severity: important
Since patch 6d40fc514c9ea886dc18ddd20043a411816b63d1 went into the Linux kernel,
X has failed to work.
The relevant line in Xorg.0.log is:
Fatal server error:
xf86MapDomainMem(): mmap() failure
strace says:
open("/sys/class/pci_bus/:00/legacy_mem", O_RD
It will take a little while for me to get to this. I put the machine
in storage when Etch went "live". If there's still interest in the
issue, I'll get it back out and we can do any experiments you want to
do.
Unfortunately, "real" life is taking a bit more time than usual
recently (m
Hi,
About a year ago, you reported a bug to the Debian BTS regarding a crash
of the X server when changing resolution in gnome. Did you reproduce
this problem recently? With Xorg/Etch? With latest xserver-xorg-core in
unstable? If not, I will close this bug in the next weeks.
Thanks,
Brice
--
Hi,
About a year ago, you reported a bug to the Debian BTS regarding the ADS
program not receiving keyboard input. Did you reproduce this problem
recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? If
not, I will close this bug in the next weeks.
Thanks,
Brice
--
To UNSUBSCRI
Hi,
About 2 years ago, you reported a bug to the Debian BTS regarding a
crash of the X server while playing kaffeine. Did you reproduce this
problem recently? With Xorg/Etch? With latest xserver-xorg-core and
xserver-xorg-video-intel in unstable? If not, I will close this bug in
the next weeks.
T
On 5/27/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
Hi,
About 2 years ago, you reported (or replied to) a bug in the Debian BTS
regarding Xorg hanging with a blank screen at exit, apparently solved by
option VBERestore. Did any of you guys reproduce this problem recently?
With Xorg/Etch? With la
Rick Thomas wrote:
> It will take a little while for me to get to this. I put the machine
> in storage when Etch went "live". If there's still interest in the
> issue, I'll get it back out and we can do any experiments you want to do.
>
> Unfortunately, "real" life is taking a bit more time than
Hi,
About 2 years ago, you reported (or replied to) a bug in the Debian BTS
regarding the X server not starting on a Cyrix 6x86 processor. Did any
of you guys reproduce this problem recently? With Xorg/Etch? With latest
xserver-xorg-core in unstable?
Thanks,
Brice
--
To UNSUBSCRIBE, email to
Hi,
About 2 years ago, you reported a bug to the Debian BTS regarding a
crash of the X server while running blender. Did you reproduce this
problem recently? With Xorg/Etch? With latest xserver-xorg-core in
unstable? If not, I will close this bug in the next weeks.
Thanks,
Brice
--
To UNSUBSC
Hi,
About 2 years ago, you reported a bug to the Debian BTS regarding the
xorg.conf file not being found by the server. Did you reproduce this
problem recently? With Xorg/Etch? With latest xserver-xorg-core in
unstable? If not, I will close this bug in the next weeks.
Thanks,
Brice
--
To UNSU
Hi,
About 2 years ago, you reported (or replied to) a bug in the Debian BTS
regarding Xorg hanging with a blank screen at exit, apparently solved by
option VBERestore. Did any of you guys reproduce this problem recently?
With Xorg/Etch? With latest xserver-xorg-core in unstable? If not, I
will clo
Daniel O'Neill wrote:
> Package: xserver-xorg-input-kbd
> Version: 1:1.1.0-4
>
> On a Thinkpad X40 keyboard - tried with both a standard american English
> keyboard and german Deutsch one - there is something extremely bizarre
> going on that seem to involve Caps Lock and Ctrl keys. Intermittently
Package: xserver-xorg-input-kbd
Version: 1:1.1.0-4
On a Thinkpad X40 keyboard - tried with both a standard american English
keyboard and german Deutsch one - there is something extremely bizarre
going on that seem to involve Caps Lock and Ctrl keys. Intermittently
the Caps lock seems to get activ
Hi Nicola,
Thanks a lot for building and testing the latest release of the sis
driver. I found a bug report upstream about problems when switching to
console and back to X, see [1]. It's not a freeze like your problem, but
at least it confirms that the driver has problem in this area. We'll see
wh
Your message dated Sun, 27 May 2007 10:01:10 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
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 is now your responsibili
Your message dated Sun, 27 May 2007 10:01:10 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
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 is now your responsibili
Your message dated Sun, 27 May 2007 10:01:10 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
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 is now your responsibili
Your message dated Sun, 27 May 2007 09:57:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
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 is now your responsibili
30 matches
Mail list logo
