[Bug 166310] DOCS-NEEDED Boolean checkbox
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=166310
David Lawrence <dkl(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution| |CURRENTRELEASE
--- Comment #5 from David Lawrence <dkl(a)redhat.com> 2008-09-16 13:36:03 EDT ---
Thanks for looking at this. Those interested may reopen this bug if they feel
it has been closed prematurely.
Dave
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 7 months
[Bug 166310] DOCS-NEEDED Boolean checkbox
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=166310
--- Comment #4 from Karsten Wade <kwade(a)redhat.com> 2008-09-16 13:25:30 EDT ---
I think various checkboxes/flags and human process has been added that resolve
or supercede this discussion. I certainly cannot speak for Content Services
in this regard, but they will have taken care of their own needs separately.
We do have the Fedora release notes flag. It would be nice to have a generic
"needs Fedora documentation" flag that only component owners could switch, but
to be honest ... there has not been a flood of usage for the release notes flag
over the years, so I doubt YAFlag will make much of a difference.
Thus, we can close this instead of verifying it against the new BZ version,
unless someone else sees merit in keeping it open.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 7 months
[Bug 166310] DOCS-NEEDED Boolean checkbox
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=166310
David Lawrence <dkl(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|2.18 |3.2
--- Comment #3 from David Lawrence <dkl(a)redhat.com> 2008-09-16 12:53:18 EDT ---
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and
therefore this bug will need to be re-verified against the new release. With
the updated code this bug may no longer be relevant or may have been fixed in
the new code.
Updating bug version to 3.2.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 7 months
fedora_requires_release_note granted: [Bug 458864] RANDR 1.2 drivers should allocate enough memory that resizing works sensibly
by Red Hat Bugzilla
Product: Fedora
Version: rawhide
Component: xorg-x11-server
Adam Jackson <ajax(a)redhat.com> has granted fedora_requires_release_note:
Bug 458864: RANDR 1.2 drivers should allocate enough memory that resizing works
sensibly
https://bugzilla.redhat.com/show_bug.cgi?id=458864
------- Additional Comments from Adam Jackson <ajax(a)redhat.com>
Right, committed for Radeon, nVidia G80, and Intel drivers.
The behaviour here is subtle and should be documented in the release notes.
Something like the following:
---
The radeon, nv, and intel drivers will now attempt to allocate sufficient
memory to enable display hotplugging to just work in more situations. If your
graphics card has more than 64M of video memory, the driver will preallocate
enough space for two 1920x1200 displays set side by side. It is not possible
to do this automatically for 64M and smaller cards without impacting 3D
functionality. Also note that this does not apply to nVidia cards older than
the GeForce 7 series due to software limitations, or to Intel chips older than
the 965 series due to hardware limitations.
---
This may still be subject to change before release, as a working memory manager
makes this moot.
15 years, 7 months
fedora_requires_release_note granted: [Bug 461311] /etc/X11/xorg.conf fixed by installation; start-up hangs with new video card installed.
by Red Hat Bugzilla
Product: Fedora
Version: 9
Component: anaconda
Jerry D. Laney <jailaney(a)yahoo.com> has granted fedora_requires_release_note:
Bug 461311: /etc/X11/xorg.conf fixed by installation; start-up hangs with new
video card installed.
https://bugzilla.redhat.com/show_bug.cgi?id=461311
------- Additional Comments from Jerry D. Laney <jailaney(a)yahoo.com>
Description of problem: /etc/X11/xorg.conf is fixed during installation;
start-up hangs if new video card is installed.
Version-Release number of selected component (if applicable):
Linux version 2.6.25.11-97.fc9.x86_64 (mockbuild@) (gcc version 4.3.0 20080428
(Red Hat 4.3.0-8) (GCC) ) #1 SMP Mon Jul 21 01:09:10 EDT 2008
How reproducible:
Install FC9 on PC with mainboard (MSI) video chips, then install a new video
card such as MSI-R3450 PCI Express card (ATI-Radeon chips.
Steps to Reproduce:
1. Install FC9 on PC
2. Boot and configure FC9
3. Shutdown PC, and install new video card
4. Boot PC
Actual results: Video start-up fails, PC monitor shows text only login.
Expected results: Expected on video failure, that autodetection of video card
would be done and xorg.conf corrected.
Additional info:
The Release Notes contained a clue with its statement to delete the
/etc/X11/xorg.conf file to initiate autodetection; however, there was no
reference to the fact that the xorg.conf file is frozen and no explanation of
what would happen if video cards were exchanged. It would be best to NOT freeze
the xorg.conf file, and always permit autodetection, even at the cost of some
startup time. Off and on it cost me several days to diagnose and fix this
problem by deleting the xorg.conf file!! (My test PC has 4 other Linux
distributions under test, and all do autodetection, and in one case, ubuntu,
the system gave the option to find and install a compatible vendor supplied
proprietary driver.)
15 years, 8 months