Summary: | Digikam crashed at startup | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | cirdan52 |
Component: | ColorManagement-Backend | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aiyazen, ba.stuttgart, caulier.gilles, Dieter.Stuebinger, dima_31, durgeshpathak1975, f.leerink, freddy.ellul, gerhard.schappe, gilant, jonathan_zaccaria, jotapequental, leo, lucaspglinard, marc.wuerde, Markus.Strittmatter, pierre.5933, rfsrossi, richardsanabria, ronnywilde, termi, werner.ittner, zamasp, zawertun |
Priority: | NOR | ||
Version: | 3.0.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 3.2.0 | |
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
cirdan52
2013-04-22 14:41:57 UTC
It crash in lcms library. What's your Color Management setup ? Which lcms version you use ? Go to Help/Component Info dialog for details. Gilles Caulier On Monday, April 22, 2013 3:13:24 PM you wrote:
> https://bugs.kde.org/show_bug.cgi?id=318721
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |caulier.gilles@gmail.com Component|general
> |Color Management
>
> --- Comment #1 from Gilles Caulier <caulier.gilles@gmail.com> ---
> It crash in lcms library.
>
> What's your Color Management setup ?
> Which lcms version you use ? Go to Help/Component Info dialog for details.
>
> Gilles Caulier
lcms version is 2.4-2.1.1
Created attachment 79380 [details]
New crash information added by DrKonqi
digikam (3.0.0) on KDE Platform 4.10.2 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:
Start Digikam.
Digikam scans collection.
Digikam crashes.
-- Backtrace (Reduced):
#8 0x00007f60013b0a58 in vsnprintf (__ap=0x7fff4403e068, __fmt=0x7f5ffffcbcb0 "Tag '%lx' not found", __n=1023, __s=0x7fff4403e080 "") at /usr/include/bits/stdio2.h:77
#9 cmsSignalError (ContextID=ContextID@entry=0x3000, ErrorCode=ErrorCode@entry=4294753456, ErrorText=ErrorText@entry=0x64657363 <Address 0x64657363 out of bounds>) at cmserr.c:409
#10 0x00007f5ffffae7ad in _cmsSearchTag (sig=icSigProfileDescriptionTag, Profile=<optimized out>, lSignalError=<optimized out>) at cmsio0.c:292
#11 _cmsSearchTag (Profile=Profile@entry=0x26bd5b0, sig=sig@entry=icSigProfileDescriptionTag, lSignalError=lSignalError@entry=1) at cmsio0.c:279
#12 0x00007f5ffffb40d0 in cmsReadICCTextEx (hProfile=hProfile@entry=0x26bd5b0, sig=sig@entry=icSigProfileDescriptionTag, Name=Name@entry=0x7f60001d7320 <Name.7711> "", size_max=size_max@entry=512) at cmsio1.c:1675
Have now installed lcms2 2.4-76.1-x86_64 from obs://build.opensuse.org/home:mrdocs Digikam still crashes. Application: digikam (3.0.0) KDE Platform Version: 4.10.2 "release 1" Qt Version: 4.8.4 Operating System: Linux 3.7.10-1.1-desktop Distribution: "openSUSE 12.3 (x86_64)" *** Bug 318730 has been marked as a duplicate of this bug. *** *** Bug 318744 has been marked as a duplicate of this bug. *** Created attachment 79389 [details]
New crash information added by DrKonqi
digikam (3.0.0) on KDE Platform 4.10.2 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:
I just re-install (apper) digikam and remove digikamrc. When i restart digikam, i have configurated it , and it crashes just when the appli starts. cause segmentation fault 11. (I started it fron Konsole to see what appends)
-- Backtrace (Reduced):
#8 0x00007fed93e1aa58 in vsnprintf (__ap=0x7fff32e1ebd8, __fmt=0x7fed92a35cb0 "Tag '%lx' not found", __n=1023, __s=0x7fff32e1ebf0 "") at /usr/include/bits/stdio2.h:77
#9 cmsSignalError (ContextID=ContextID@entry=0x3000, ErrorCode=ErrorCode@entry=2460179632, ErrorText=ErrorText@entry=0x64657363 <Address 0x64657363 out of bounds>) at cmserr.c:409
#10 0x00007fed92a187ad in _cmsSearchTag (sig=icSigProfileDescriptionTag, Profile=<optimized out>, lSignalError=<optimized out>) at cmsio0.c:292
#11 _cmsSearchTag (Profile=Profile@entry=0x2d80760, sig=sig@entry=icSigProfileDescriptionTag, lSignalError=lSignalError@entry=1) at cmsio0.c:279
#12 0x00007fed92a1e0d0 in cmsReadICCTextEx (hProfile=hProfile@entry=0x2d80760, sig=sig@entry=icSigProfileDescriptionTag, Name=Name@entry=0x7fed92c41320 <Name.7711> "", size_max=size_max@entry=512) at cmsio1.c:1675
*** Bug 318762 has been marked as a duplicate of this bug. *** Upgrading to Digikam 3.1.0 from the openSUSE 12.3 KDE:Release:410 repository provides a fix. 8) I concur with Leo, upgrading to 3.1.0 resolves the issue (In reply to comment #11) > I concur with Leo, upgrading to 3.1.0 resolves the issue Ok,I thank you so much, it works for me. Good bye. Created attachment 79406 [details]
New crash information added by DrKonqi
digikam (3.0.0) on KDE Platform 4.10.2 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:
Solo intente abrir digikam y se cerro, antes pude llenar la insformacion de configuracion del programadespues se cerro no volvio a abrir incluso desinstalando y reinstalando, reinciando, ningun nntennto funciono.
-- Backtrace (Reduced):
#8 0xb37393b6 in vsnprintf (__ap=0xbf982aac "\022s\027\263 /\030\263@Hx\267", __fmt=0x64657363 <Address 0x64657363 out of bounds>, __fmt@entry=0xb3176fb0 "Tag '%lx' not found", __n=1023, __s=0xbf98268c "") at /usr/include/bits/stdio2.h:77
#9 cmsSignalError (ContextID=ContextID@entry=0x3000, ErrorCode=ErrorCode@entry=3004657584, ErrorText=ErrorText@entry=0x64657363 <Address 0x64657363 out of bounds>) at cmserr.c:409
#10 0xb31573ce in _cmsSearchTag (sig=icSigProfileDescriptionTag, Profile=<optimized out>, lSignalError=<optimized out>) at cmsio0.c:292
#11 _cmsSearchTag (Profile=Profile@entry=0x8c22d00, sig=sig@entry=icSigProfileDescriptionTag, lSignalError=lSignalError@entry=1) at cmsio0.c:279
#12 0xb315d62a in cmsReadICCTextEx (hProfile=hProfile@entry=0x8c22d00, sig=sig@entry=icSigProfileDescriptionTag, Name=Name@entry=0xb3182f20 <Name.7468> "", size_max=size_max@entry=512) at cmsio1.c:1675
I am using suse 12.3, . why to upgrade to Digikam 3.00, do wee expect to get no issue for digikam 3.00 Thanks Pierre Created attachment 79432 [details]
New crash information added by DrKonqi
digikam (3.0.0) on KDE Platform 4.10.2 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:
Just started digikam
- Unusual behavior I noticed:
Crashes after start
- Custom settings of the application:
None. Fresh install. Just updated from the regular repos.
-- Backtrace (Reduced):
#8 0x00007f50da80ea58 in vsnprintf (__ap=0x7fff36b1fc58, __fmt=0x7f50d9429cb0 "Tag '%lx' not found", __n=1023, __s=0x7fff36b1fc70 "") at /usr/include/bits/stdio2.h:77
#9 cmsSignalError (ContextID=ContextID@entry=0x3000, ErrorCode=ErrorCode@entry=3645021360, ErrorText=ErrorText@entry=0x64657363 <Address 0x64657363 out of bounds>) at cmserr.c:409
#10 0x00007f50d940c7ad in _cmsSearchTag (sig=icSigProfileDescriptionTag, Profile=<optimized out>, lSignalError=<optimized out>) at cmsio0.c:292
#11 _cmsSearchTag (Profile=Profile@entry=0x1c02450, sig=sig@entry=icSigProfileDescriptionTag, lSignalError=lSignalError@entry=1) at cmsio0.c:279
#12 0x00007f50d94120d0 in cmsReadICCTextEx (hProfile=hProfile@entry=0x1c02450, sig=sig@entry=icSigProfileDescriptionTag, Name=Name@entry=0x7f50d9635320 <Name.7711> "", size_max=size_max@entry=512) at cmsio1.c:1675
*** Bug 318842 has been marked as a duplicate of this bug. *** To be clear, crash come from LCMS shared lib. It sound like a binary compatibility issue with 3.0.0 in some distro. Updating to last 3.1.0 fix the problem. Gilles Caulier *** Bug 318848 has been marked as a duplicate of this bug. *** *** Bug 318861 has been marked as a duplicate of this bug. *** *** Bug 318859 has been marked as a duplicate of this bug. *** for mee I unistall Digikam, and others concerning it lang ETc and also about kipi the package is in the Factory despository http://software.opensuse.org/ymp/openSUSE:Factory/standard/digikam.ymp?base=openSUSE%3AFactory&query=digikam Thanks to Gilles Gaulier I have to correct my post #21. the solution using the factory depot causes the update of the system for factory deposit and suse 12.3 creashes. immediately after the deposit Factory must be disabled *** Bug 318987 has been marked as a duplicate of this bug. *** *** Bug 318989 has been marked as a duplicate of this bug. *** *** Bug 318991 has been marked as a duplicate of this bug. *** Am 26.04.2013 09:36, schrieb pierre.5933@gmail.com: > https://bugs.kde.org/show_bug.cgi?id=318721 > > --- Comment #22 from pierre.5933@gmail.com --- > I have to correct my post #21. the solution using the factory depot causes the > update of the system for factory deposit and suse 12.3 creashes. immediately > after the deposit Factory must be disabled > A better way: https://bugs.kde.org/show_bug.cgi?id=318848 zypper arhttp://download.opensuse.org/update/12.3-test update-test zypper up -r update-test digikam Best regards *** Bug 319070 has been marked as a duplicate of this bug. *** *** Bug 319144 has been marked as a duplicate of this bug. *** *** Bug 319166 has been marked as a duplicate of this bug. *** *** Bug 319674 has been marked as a duplicate of this bug. *** I followed these steps and now digikam 3.1 is correctly installed: http://dia-scan.blogspot.fr/2013/03/how-to-compile-digikam-31-on-ubuntu-1204.html Jonathan ZACCARIA jonathan_zaccaria@yahoo.it +33 (0)628 43 61 76 www.collectifpolaire.org On 05/11/2013 06:51 PM, Gilles Caulier wrote: > https://bugs.kde.org/show_bug.cgi?id=318721 > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |jonathan_zaccaria@yahoo.it > > --- Comment #30 from Gilles Caulier <caulier.gilles@gmail.com> --- > *** Bug 319674 has been marked as a duplicate of this bug. *** > *** Bug 319690 has been marked as a duplicate of this bug. *** *** Bug 320357 has been marked as a duplicate of this bug. *** *** Bug 326347 has been marked as a duplicate of this bug. *** |