Color manager shows [invalid UTF-8]

[florin]

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

[Invalid UTF-8] - VBOX monitor

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
Date: Mon Sep 5 16:30:41 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to oneiric on 2011-09-01 (3 days ago)

[florin (florin-arjocu)]

This virtualbox machine just had a set of update & dist-upgrade.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Pedro Villavicencio (pedro)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=658478

[Pedro Villavicencio (pedro)]

florin, may you please give us the result of "colormgr get-devices" ? just attach the results to the report, Thanks in advance.

[florin (florin-arjocu)]

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
florin@florin-VirtualBox:~$

[Sebastien Bacher (seb128)]

Pedro can you get the details for upstream?

[Pedro Villavicencio (pedro)]

florin can you get us the output of get-edid | parse-edid &> edid.txt ? please upload that file as an attachment to the report, it would help upstream to fix the issue, thanks.

[florin (florin-arjocu)]

@Pedro - sorry for late answer, I was offline.

I did not have read-edit and had to install it:
sudo apt-get install read-edid

There is a problem with the command line:
florin@florin-VirtualBox:~$ get-edid | parse-edid &> edid2.txt
get-edid: get-edid version 2.0.0
mmap /dev/zero: Operation not permitted
get-edid: error initialising realmode interface
get-edid: do you have full superuser (root) permissions?

And the file contains only this:
parse-edid: parse-edid version 2.0.0
parse-edid: IO error reading EDID

[Pedro Villavicencio (pedro)]

could you run that with sudo? as in: sudo get-edid | parse-edid &> edid2.txt ? Thanks.

[florin (florin-arjocu)]

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:~$

[florin (florin-arjocu)]

The file generated by that line.

[florin (florin-arjocu)]

Confirming that with all updates&dist-upgrades until this moment the bug is still present in my installation.

[Sebastien Bacher (seb128)]

seems you got the infos you need pedro ;-)

[Pedro Villavicencio (pedro)]

info went upstream, unassigning from it until they request any other info, thanks again.

[Richard Hughes (richard-hughes)]

Florin, can you upload the file created by "sudo get-edid > edid.bin" please. I need the actual EDID blob, not the parsed version. Thanks.

[florin (florin-arjocu)]

It's an empty file and the command output is this:

florin@florin-VirtualBox:~$ sudo get-edid > edid.bin
[sudo] password for florin:
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:~$

[florin (florin-arjocu)]

If you want you can try later (when I come back home) a remote connection to this machine and see there what the problem really is. I use GMT+3 Time.

[Sebastien Bacher (seb128)]

the bug has seen no activity in years and upstream closed, doing the same, feel free to reopen a bug if you still get issues in newer versions