After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 658478 - [color] Color manager shows [invalid UTF-8]
[color] Color manager shows [invalid UTF-8]
Status: RESOLVED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: Color
3.1.x
Other Linux
: Normal minor
: ---
Assigned To: Richard Hughes
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-09-07 15:27 UTC by Pedro Villavicencio
Modified: 2015-07-27 22:52 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-09-07 15:27:00 UTC
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/841821

"Settings manager -> Color -> monitor name shows with invalid UTF-8:

[Invalid UTF-8] - VBOX monitor"

this is on 3.1.91
Comment 1 Richard Hughes 2011-09-07 15:41:51 UTC
Can you get me the result of "colormgr get-devices" please. Thanks.
Comment 2 Sebastien Bacher 2011-09-07 16:42:00 UTC
submitter reply

"florin@florin-VirtualBox:~$ colormgr get-devices
Object Path: /org/freedesktop/ColorManager/devices/xrandr_VBOX_monitor_50333014
Created:        1315411347
Modified:       1315411347
Type:   display
Model:  VBOX monitor
Vendor: [Invalid UTF-8]
Serial: 50333014
Scope:  temp
Colorspace:     rgb
Device ID:      xrandr-VBOX monitor-50333014
Profile 1:      /org/freedesktop/ColorManager/profiles/icc_bed9bbed20bc15596df35e1f1080fabf
Metadata:       XRANDR_name=VBOX0"
Comment 3 Sebastien Bacher 2011-09-07 16:43:05 UTC
colord's version is 0.1.11
Comment 4 Richard Hughes 2011-09-07 17:44:30 UTC
Eeek. Could you please get the reporter to get me the dump of thier virtual EDID, or give me precise instructions how to setup virtualbox. Thanks dude.
Comment 5 Richard Hughes 2011-09-08 14:33:12 UTC
I've played with this for a bit, and I can't seem to get any sensible EDID from any virtualbox guest, with and without the client tools. Please can you grab me the EDID as a blob, and I'll have a look here. Thanks.
Comment 6 Pedro Villavicencio 2011-09-29 13:49:00 UTC
comment from the reporter:

"I updated&dist-upgraded the oneiric machine. Running that line gives this output; the file will be attached after this comment.

florin@florin-VirtualBox:~$ sudo get-edid | parse-edid &> edid2.txt
get-edid: get-edid version 2.0.0

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 200
 VBE string at 0xc7f06 "VirtualBox VBE BIOS http://www.virtualbox.org/"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function unsupported
 Call failed

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function unsupported
 Call failed

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged
florin@florin-VirtualBox:~$
"

file with the info he got it:

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/841821/+attachment/2433588/+files/edid2.txt

Please don't hesitate in requesting any other info you might need, thanks in advance!.
Comment 7 Bastien Nocera 2013-04-18 16:13:55 UTC
We'd need the unparsed edid, as requested in comment 5.
Comment 8 Sam Morris 2013-04-19 01:04:39 UTC
FWIW these days gnome-control-center just describes the monitor as 'VBOX monitor', and 'colormgr get-devices' displays 'unknown' as the vendor. get-edid still fails with 'Error: output block unchanged'.
Comment 9 Alexandre Franke 2015-07-27 22:52:17 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!