Bug 493748

And how does it affect function of X? Does it work at all? Poorly?

Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Please add full dmesg as well, as uncompressed text/plain attachment.

---
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #1)
> And how does it affect function of X? Does it work at all? Poorly?

X works for some things, has other bugs which I'm in the process of reporting.
But it does come up.

> Please attach your X server config file (/etc/X11/xorg.conf, if available) and
> X server log file (/var/log/Xorg.*.log) to the bug report as individual
> uncompressed file attachments using the bugzilla file attachment link below.
> 
> We will review this issue again once you've had a chance to attach this
> information.
> 
> Thanks in advance.  

There is no X server config file.  As I said, I'm running the Fedora test day livecd.  You can get any file from it as easily as I can; it's your CD.

I don't see any purpose to sending in the Xorg.0.log file for a kernel bug.  The message appears with or without the X server.  In particular, it appears before the X server is ever started, during the boot sequence.

I also don't see any purpose to sending in the entire dmesg log before you'll look at the one individual kernel message that I reported.  If I had sent you the entire dmesg log, you'd have complained that you don't know what part of it is wrong.  Since I sent you an excerpt, now you complain that you want to see the whole thing.

If you're interested in fixing bugs, then fix the (%*$()# bug.  If you're just interested in improving your "bugs closed" stats, you'll have to do better than making useless form-letter requests of the bug reporters, and then claiming that their non-response is the reason you had to close out the bug.

I was testing on an HP dc5750 machine.  It's HP's BIOS that is probably reporting the connector type that the kernel couldn't handle.  I note that you never asked what kind of machine I was testing on.

John, if the issue is in the kernel and not X, why have you filed it on the X driver package? That's why the triagers are asking you for X logs.

We ask for xorg.conf in case you've created one for some reason; some people do so, because they 'obviously' need this or that parameter to make X work, and then don't tell you in the bug report. This is obviously less likely on live CDs, but Matej may not have noticed you were using the live CD (it's only mentioned in passing in your report).

We are asking for the full dmesg to have the full context about your system. Imagine you filed a bug about an app that crashed, and included the single line of console output that basically said "Oh dear, I seem to have crashed". If you were then asked for a full traceback so the issue could be accurately identified, would you complain about that? You can't necessarily identify and fix an error based solely on the error message itself, and that holds true for kernel errors just as much as anything else. All "[drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector
type: 8" tells us is *what's gone wrong*. It doesn't tell us anything in particular about why, necessarily.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I think I can speak for the whole bugzapper team in saying that we only strive for better quality, not for statistics. As Adam said, the dmesg output has a little more data than the error message itself - otherwise, it would not make sense for it to be this long, right ?

More to the point, while we can't claim to know enough to fix this bug outright, we happen to have a good idea of what kind of data is needed for maintainers to close on the bug and fix it without losing too much time.

One last thing, we use the xorg-x11-drv-ati component for KMS related bugs, not only because we don't want to swamp the kernel guys with ATI-related issues, but because there is a single maintainer for both DDX and KMS on Radeon.

Switching back to NEEDMOREINFO, please provide the required logs. 

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Closing this as CLOSED INSUFFICIENT_DATA.

Please note, I am not doing this because I am "interested in improving your "bugs closed" stats". I am closing this because the original reporter was asked multiple times to provide follow-up data and has not done so. In fact, one of the developers asked for data and even took the time to justify the need for it.

Original Reporter, if you disagree with this closure, that is your prerogative, and, in fact, you can re-open it if you wish. If you do, please provide the data that has been asked for, or, if you are no longer able to do so, please at least verify that this is still an issue with your specific hardware, using an up-to-date LiveCD. I have attempted to reproduce this bug and have not been able to do so.

Thank you, very much, for your efforts in testing Fedora and going the next step and reporting bugs.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers