Bug 46654 – VMware/Vritualbox xserver config after systemsetup broken

Bug 46654 - VMware/Vritualbox xserver config after systemsetup broken


Summary:	VMware/Vritualbox xserver config after systemsetup broken

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	General
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:	46487
Blocks:
	Show dependency tree / graph

Reported:	2018-03-14 11:37 CET by Jürn Brodersen
Modified:	2021-05-14 16:38 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Release Management
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Appliance
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Jürn Brodersen

2018-03-14 11:37:38 CET

+++ This bug was initially created as a clone of Bug #46487 +++

Note: this bug is for xserver usage after the setup. The setup works!

With xorg/autoconfig=yes the xserver doesn't start at all in vmware.

In Virtualbox the xserver seems to choose the framebuffer driver instead of vesa resulting in a 800x600 desktop.

Comment 1 Ingo Steuwer

2021-05-14 16:38:03 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.