Bug 653707 - "gcm-apply --login" crashes.
Summary: "gcm-apply --login" crashes.
Keywords:
Status: CLOSED DUPLICATE of bug 653419
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-color-manager
Version: rawhide
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-16 00:20 UTC by sangu
Modified: 2010-11-16 09:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-16 09:06:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description sangu 2010-11-16 00:20:09 UTC
Description of problem:
Core was generated by `gcm-apply --login'.
Program terminated with signal 11, Segmentation fault.
#0  cmsSetEncodedICCversion (hProfile=0x0, Version=2) at cmsio0.c:876
876	    Icc -> Version = Version;

(gdb) bt
#0  cmsSetEncodedICCversion (hProfile=0x0, Version=2) at cmsio0.c:876
#1  0x00007f812bbc0235 in gcm_profile_create_from_chroma (
    profile=<value optimized out>, gamma=<value optimized out>, 
    red=<value optimized out>, green=<value optimized out>, 
    blue=<value optimized out>, white=<value optimized out>, 
    error=<value optimized out>) at gcm-profile.c:1292
#2  0x000000000040ca30 in gcm_device_xrandr_generate_profile (
    device=<value optimized out>, error=<value optimized out>)
    at gcm-device-xrandr.c:426
#3  0x0000000000405d4c in gcm_apply_create_icc_profile_for_edid (argc=1, argv=
    0x7fffe178e588) at gcm-apply.c:44
#4  main (argc=1, argv=0x7fffe178e588) at gcm-apply.c:157


Version-Release number of selected component (if applicable):
2.91.2-1.fc15.x86_64

How reproducible:
always

Steps to Reproduce:
1. login in gdm.
2.
3.
  
Actual results:


Expected results:


Additional info:
lcms2-2.0a-3.fc14.x86_64
ORBit2-2.14.19-1.fc15.x86_64

Comment 1 Richard Hughes 2010-11-16 09:06:54 UTC

*** This bug has been marked as a duplicate of bug 653419 ***


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