Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31627 - [virtualbox] cannot be used with dark theme

Attached to Project: Community Packages
Opened by Roman Kosenko (kite) - Thursday, 20 September 2012, 22:01 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 02 October 2012, 21:10 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ionut Biru (wonder)
Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Low
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
New VirtualBox OSE 4.2.0 from ArchLinux repository looks like at attached screenshot. So, with dark Qt-theme text almost cannot be read. In previous version (4.1.22) everything was ok.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Tuesday, 02 October 2012, 21:10 GMT
Reason for closing:  No response
Comment by Sébastien Luttringer (seblu) - Saturday, 22 September 2012, 10:40 GMT
This can be:
- Misconception in theme
- Use of a different color reference in vbox

Do you have solution? If not, you should report this upstream directly. There is something releated with packaging here?
Comment by Roman Kosenko (kite) - Saturday, 22 September 2012, 17:41 GMT
Original VirtualBox, as I know, uses static linked Qt and doesn't use system theme. So problem is related to ArchLinux package, which uses dynamic linked Qt. I don't think mainsteam will do anything with this.
I don't know solution for now. When I'll be free I'll compare sources of 4.1.22 and 4.2.0 and maybe will found what change breaks this.
Comment by Sébastien Luttringer (seblu) - Sunday, 23 September 2012, 00:27 GMT
Original? virtualbox-bin (from AUR) use static compiled library. AFAIR theming doesn't works at all.

Our version is compiled with upstream makefiles and upstream Qt. So others distro should be affected like us.
A test with another distros can help to see if it's only ArchLinux related. That I don't believe today. Can you test this?

Loading...