Bug 641421 - Add release note indicating that vbetool will no longer be installed by default
Summary: Add release note indicating that vbetool will no longer be installed by default
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: release-notes
Version: devel
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: eric
QA Contact: Karsten Wade
URL:
Whiteboard:
Depends On: 528022
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-08 16:51 UTC by James Laska
Modified: 2013-09-02 06:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-21 12:57:12 UTC
Embargoed:


Attachments (Terms of Use)
Release Notes text (678 bytes, text/plain)
2010-10-10 17:08 UTC, eric
eric: review?
Details

Description James Laska 2010-10-08 16:51:47 UTC
Description of problem:

To resolve bug#528022, vbetool will no longer be installed by default.  As a result, users that have uncommon VGA adapters (not nVidia, ati or intel) may have problems suspending and resuming laptops.

As a result, affected users will need to manually install vbetool.  However, note that vbetool may not work in all cases and is provided as a convenience.

Comment 1 eric 2010-10-10 17:08:33 UTC
Created attachment 452599 [details]
Release Notes text

This is the text I'm proposing to add to the Release Notes.

Comment 2 James Laska 2010-10-11 15:49:51 UTC
(In reply to comment #1)
> Created attachment 452599 [details]
> Release Notes text
> 
> This is the text I'm proposing to add to the Release Notes.

"Due to problems with <package>vbetool</package>, this package has been removed from the default installation of Fedora.  This change may impact users with suspending and resuming their computers.  These problems should only affect users of uncommon VGA adaptors and not users of nVidia, ati, or Intel adaptors."

Adam Jackson confirmed on IRC that that the above content looks good.

One though, perhaps we want to add a link or comment about what affected users should do?  Is there a recommended procedure for such users?


Note You need to log in before you can comment on or make changes to this bug.