Summary: | Crash of Digikam | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Christoph Jüngling <chris> |
Component: | ColorManagement-Backend | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 2.5.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/digikam/c668a445da7e7ac62e42f035e5fef68a8d9571a0 | Version Fixed In: | 3.0.0 |
Description
Christoph Jüngling
2012-08-05 12:00:41 UTC
Sound like it crash in Color Management. Do you assigned a color profile for your screen ? Which icc profile file ? Also it crash internally in Qt screen management ? It sound like a problem with Qt or your X11 video driver. Please investiguate... Gilles Caulier I did not change any color management settings, nor did I assign a particular color profile. Well, sound like a binary compatibility issue in your system with Qt or X11. Also try to use last stable digiKam 2.7.0. Gilles Caulier Code (crash in second line): QDesktopWidget* desktop = QApplication::desktop(); int screenNumber = desktop->screenNumber(widget); We dont check the desktop widget, and from the docs the state of a null desktop widget is not defined/expected, but the crash comes from accessing this. I will add a null pointer check. If there's not a null pointer and still crashes, it's an upstream problem. Git commit c668a445da7e7ac62e42f035e5fef68a8d9571a0 by Marcel Wiesweg. Committed on 03/10/2012 at 15:05. Pushed by mwiesweg into branch 'master'. Add null pointer check because of reported crash here. FIXED-IN: 3.0 M +5 -0 libs/dimg/filters/icc/iccsettings.cpp http://commits.kde.org/digikam/c668a445da7e7ac62e42f035e5fef68a8d9571a0 |