| Summary: | KolorManager v0.95 crashes on most actions | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | richard.jabkowski |
| Component: | general | Assignee: | Kai-Uwe Behrmann <ku.b> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | j.simon.iii |
| Priority: | NOR | ||
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Collection of PPDs used to reproduce error. | ||
|
Description
richard.jabkowski
2012-04-21 07:46:58 UTC
Unfortunately I can not reproduce. It looks like the crash happens in the Oyranos CUPS module. But that appears to have no debug symbols. Can you post your PPD's, under which the crash occurs, in the hope to reproduce? The PPD's with crash Oyranos are appreciated to see. Do you by any chance have multiple printers/printer drivers installed? It seems that I can slightly reproduce the error by installing 3 or more PPDs on my system. (In reply to comment #3) > Do you by any chance have multiple printers/printer drivers installed? It > seems that I can slightly reproduce the error by installing 3 or more PPDs > on my system. Great, so you can already reproduce. Can you send me your PPD's please? I would like to install them here temporarily and check. valgrind keeps here totally silent. Created attachment 70574 [details]
Collection of PPDs used to reproduce error.
All three of these PPD files should be used together to reproduce bug.
(In reply to comment #5) > Created attachment 70574 [details] > Collection of PPDs used to reproduce error. > > All three of these PPD files should be used together to reproduce bug. Thanks, can reproduce. pushed a fix into Oyranos git 76412f29 * [CUPS]: check string lenght Please let us know, if that fixes the issue. (In reply to comment #1) > Unfortunately I can not reproduce. > It looks like the crash happens in the Oyranos CUPS module. But that appears > to have no debug symbols. > Can you post your PPD's, under which the crash occurs, in the hope to > reproduce? Sorry, i have not been online over the weekend. Do you still need the PPDs? I have three different printers installed. Btw. one of them is shown three times in the KolorManager window. (In reply to comment #8) > (In reply to comment #1) > > Unfortunately I can not reproduce. > > It looks like the crash happens in the Oyranos CUPS module. But that appears > > to have no debug symbols. > > Can you post your PPD's, under which the crash occurs, in the hope to > > reproduce? > > Sorry, i have not been online over the weekend. > Do you still need the PPDs? > I have three different printers installed. > Btw. one of them is shown three times in the KolorManager window. Can you check Oyranos from git? How does you build Oyranos on ubuntu? (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #1) > > > Unfortunately I can not reproduce. > > > It looks like the crash happens in the Oyranos CUPS module. But that appears > > > to have no debug symbols. > > > Can you post your PPD's, under which the crash occurs, in the hope to > > > reproduce? > > > > Sorry, i have not been online over the weekend. > > Do you still need the PPDs? > > I have three different printers installed. > > Btw. one of them is shown three times in the KolorManager window. > > Can you check Oyranos from git? How does you build Oyranos on ubuntu? (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #1) > > > Unfortunately I can not reproduce. > > > It looks like the crash happens in the Oyranos CUPS module. But that appears > > > to have no debug symbols. > > > Can you post your PPD's, under which the crash occurs, in the hope to > > > reproduce? > > > > Sorry, i have not been online over the weekend. > > Do you still need the PPDs? > > I have three different printers installed. > > Btw. one of them is shown three times in the KolorManager window. > > Can you check Oyranos from git? How does you build Oyranos on ubuntu? i have installed the one, provided via GetDeb. never tried to deploy it myself. i will have a look at it - maybe i am able to build it. The CUPS plug-in had a print queue string length limit of 24 characters inside. As a workaround you might want to test shorter print queue names. (In reply to comment #11) > The CUPS plug-in had a print queue string length limit of 24 characters > inside. As a workaround you might want to test shorter print queue names. after building oyranos and kolorManager from git, i do not see any devices at all.... (In reply to comment #12) > (In reply to comment #11) > > The CUPS plug-in had a print queue string length limit of 24 characters > > inside. As a workaround you might want to test shorter print queue names. > > after building oyranos and kolorManager from git, i do not see any devices > at all.... I think to had to remove all elder Oyranos modules and after that devices showed up again. (In reply to comment #13) > (In reply to comment #12) > > (In reply to comment #11) > > > The CUPS plug-in had a print queue string length limit of 24 characters > > > inside. As a workaround you might want to test shorter print queue names. > > > > after building oyranos and kolorManager from git, i do not see any devices > > at all.... > > I think to had to remove all elder Oyranos modules and after that devices > showed up again. thx - its working now (without crashing)!! just one additional question: i have my new monitor connected via display port and get always: WARNING 8.390000: [-1] oyranos_monitor_x11.c:179 oyX1Monitor_getProperty_() found issues bytes_after_return: 128 WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:414 oyX1GetMonitorInfo_() found /var/log/Xorg.0.log in ":0.0": FUS 2031 2560x1440+0+0 WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:450 oyX1GetMonitorInfo_() no EDID available from X properties: "XFree86_DDC_EDID1_RAWDATA"/"EDID_DATA" using Xorg log fallback. any hint ? (In reply to comment #14) > thx - its working now (without crashing)!! Thanks for reporting! > just one additional question:
> i have my new monitor connected via display port and get always:
>
> WARNING 8.390000: [-1] oyranos_monitor_x11.c:179 oyX1Monitor_getProperty_()
> found issues bytes_after_return: 128
> WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:414
> oyX1GetMonitorInfo_() found /var/log/Xorg.0.log in ":0.0": FUS 2031
> 2560x1440+0+0
> WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:450
> oyX1GetMonitorInfo_()
> no EDID available from X properties:
> "XFree86_DDC_EDID1_RAWDATA"/"EDID_DATA"
> using Xorg log fallback.
>
> any hint ?
Some drivers do not appropriately report EDID information from monitors. Oyranos needs that information to identify the device and eventually create as a fallback a basic ICC profile.
$ xprop -len 4 -root | grep EDID
or
$ xrandr --props
should show you the availability of a EDID data block.
You use ATI, nvidia, intel graphics and with proprietary or open source driver?
(In reply to comment #16) > > just one additional question: > > i have my new monitor connected via display port and get always: > > > > WARNING 8.390000: [-1] oyranos_monitor_x11.c:179 oyX1Monitor_getProperty_() > > found issues bytes_after_return: 128 > > WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:414 > > oyX1GetMonitorInfo_() found /var/log/Xorg.0.log in ":0.0": FUS 2031 > > 2560x1440+0+0 > > WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:450 > > oyX1GetMonitorInfo_() > > no EDID available from X properties: > > "XFree86_DDC_EDID1_RAWDATA"/"EDID_DATA" > > using Xorg log fallback. > > > > any hint ? > > Some drivers do not appropriately report EDID information from monitors. > Oyranos needs that information to identify the device and eventually create > as a fallback a basic ICC profile. > $ xprop -len 4 -root | grep EDID > or > $ xrandr --props > should show you the availability of a EDID data block. > You use ATI, nvidia, intel graphics and with proprietary or open source > driver? its an ATI FirePro V4800 using the proprietary driver for 10bit. here is the output of the commands above: rj@Desktop:~/Downloads/test/kolor-manager/build$ xprop -len 4 -root | grep EDID XFree86_DDC_EDID1_RAWDATA(INTEGER) = 0, -1, -1, -1 rj@Desktop:~/Downloads/test/kolor-manager/build$ xrandr --props Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 2560 x 2560 DFP1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm _ICC_PROFILE: ... EDID_DATA: 00ffffffffffff001ab3ef07c6020000 2f150104b53c22783a8e05ad4f33b026 0d5054a54b00a940b300950081008180 010101010101565e00a0a0a029503020 350055502100001e000000fd00174c0f 631e000a202020202020000000fc0050 3237542d36204950530a2020000000ff 00595635573030303731300a202001dc SignalFormat: DisplayPort ConnectorType: DisplayPort 2560x1440 60.0*+ ...... |