Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Digikam in GNOME 3.14.2

  1. #1
    Join Date
    Jul 2013
    Location
    Whitley Bay, Tyne & Wear, United Kingdom.
    Posts
    182

    Default Digikam in GNOME 3.14.2

    Hi,
    I've been trying to install digikam from the repos, but when I start it, it won't launch... crashes immediately. I've searched everywhee, tried every online advice, all to no avail. Tried deleting all config files etc and reinstalling.
    I'm running GNOME 3.14.2 with Linux kernel 3.18
    here's the roll-out starting it from the command line.
    ANyone an idea?
    Part I
    ** Error in `digikam': realloc(): invalid pointer: 0x0000000000c14260 ***
    ======= Backtrace: =========
    /lib64/libc.so.6(+0x7283f)[0x7f1298a2b83f]
    /lib64/libc.so.6(+0x77c1e)[0x7f1298a30c1e]
    /lib64/libc.so.6(realloc+0x26a)[0x7f1298a34dfa]
    /usr/lib64/libQt5Core.so.5(_ZN9QListData7reallocEi+0x1e)[0x7f1287e8490e]
    /usr/lib64/libQt5Core.so.5(_ZN9QListData6appendEi+0x6a)[0x7f1287e849ca]
    /usr/lib64/libQt5Core.so.5(+0x1d6f5c)[0x7f1287f4cf5c]
    /usr/lib64/libQt5Core.so.5(_Z21qRegisterResourceDataiPKhS0_S0_+0x2b9)[0x7f1287f49409]
    /usr/lib64/libQt5Core.so.5(+0x807e3)[0x7f1287df67e3]
    /lib64/ld-linux-x86-64.so.2(+0xeaaa)[0x7f129fe60aaa]
    /lib64/ld-linux-x86-64.so.2(+0xeb93)[0x7f129fe60b93]
    /lib64/ld-linux-x86-64.so.2(+0x11ba)[0x7f129fe531ba]
    ======= Memory map: ========
    00400000-00a0a000 r-xp 00000000 08:07 2361094 /usr/bin/digikam
    00c09000-00c0a000 r--p 00609000 08:07 2361094 /usr/bin/digikam
    00c0a000-00c15000 rw-p 0060a000 08:07 2361094 /usr/bin/digikam
    00c15000-00c19000 rw-p 00000000 00:00 0
    024a0000-024c1000 rw-p 00000000 00:00 0 [heap]
    7f127aded000-7f127ae19000 r-xp 00000000 08:07 2365944 /usr/lib64/libvorbis.so.0.4.7
    7f127ae19000-7f127b019000 ---p 0002c000 08:07 2365944 /usr/lib64/libvorbis.so.0.4.7
    7f127b019000-7f127b01a000 r--p 0002c000 08:07 2365944 /usr/lib64/libvorbis.so.0.4.7
    7f127b01a000-7f127b01b000 rw-p 0002d000 08:07 2365944 /usr/lib64/libvorbis.so.0.4.7
    7f127b01b000-7f127b021000 r-xp 00000000 08:07 2365866 /usr/lib64/libogg.so.0.8.1
    7f127b021000-7f127b220000 ---p 00006000 08:07 2365866 /usr/lib64/libogg.so.0.8.1
    7f127b220000-7f127b221000 r--p 00005000 08:07 2365866 /usr/lib64/libogg.so.0.8.1
    7f127b221000-7f127b222000 rw-p 00006000 08:07 2365866 /usr/lib64/libogg.so.0.8.1
    7f127b222000-7f127b23d000 r-xp 00000000 08:07 2366822 /usr/lib64/libgraphite2.so.3.0.1
    7f127b23d000-7f127b43c000 ---p 0001b000 08:07 2366822 /usr/lib64/libgraphite2.so.3.0.1
    7f127b43c000-7f127b43e000 r--p 0001a000 08:07 2366822 /usr/lib64/libgraphite2.so.3.0.1
    7f127b43e000-7f127b43f000 rw-p 0001c000 08:07 2366822 /usr/lib64/libgraphite2.so.3.0.1
    7f127b43f000-7f127b4be000 r-xp 00000000 08:07 2370753 /usr/lib64/liborc-0.4.so.0.23.0
    7f127b4be000-7f127b6bd000 ---p 0007f000 08:07 2370753 /usr/lib64/liborc-0.4.so.0.23.0
    7f127b6bd000-7f127b6bf000 r--p 0007e000 08:07 2370753 /usr/lib64/liborc-0.4.so.0.23.0
    7f127b6bf000-7f127b6c3000 rw-p 00080000 08:07 2370753 /usr/lib64/liborc-0.4.so.0.23.0
    7f127b6c3000-7f127b6c4000 r--p 00000000 08:07 2364441 /usr/lib64/libicudata.so.54.1
    7f127b6c4000-7f127b8c3000 ---p 00001000 08:07 2364441 /usr/lib64/libicudata.so.54.1
    7f127b8c3000-7f127b8c4000 r--p 00000000 08:07 2364441 /usr/lib64/libicudata.so.54.1
    7f127b8c4000-7f127b8e8000 r-xp 00000000 08:07 2367386 /usr/lib64/libv4lconvert.so.0.0.0
    7f127b8e8000-7f127bae8000 ---p 00024000 08:07 2367386 /usr/lib64/libv4lconvert.so.0.0.0
    7f127bae8000-7f127baea000 r--p 00024000 08:07 2367386 /usr/lib64/libv4lconvert.so.0.0.0
    7f127baea000-7f127baeb000 rw-p 00026000 08:07 2367386 /usr/lib64/libv4lconvert.so.0.0.0
    7f127baeb000-7f127bb3d000 rw-p 00000000 00:00 0
    7f127bb3d000-7f127bb54000 r-xp 00000000 08:07 2367301 /usr/lib64/libusb-1.0.so.0.1.0
    7f127bb54000-7f127bd53000 ---p 00017000 08:07 2367301 /usr/lib64/libusb-1.0.so.0.1.0
    7f127bd53000-7f127bd54000 r--p 00016000 08:07 2367301 /usr/lib64/libusb-1.0.so.0.1.0
    7f127bd54000-7f127bd55000 rw-p 00017000 08:07 2367301 /usr/lib64/libusb-1.0.so.0.1.0
    7f127bd55000-7f127bd61000 r-xp 00000000 08:07 2368839 /usr/lib64/libraw1394.so.11.1.0
    7f127bd61000-7f127bf60000 ---p 0000c000 08:07 2368839 /usr/lib64/libraw1394.so.11.1.0
    7f127bf60000-7f127bf61000 r--p 0000b000 08:07 2368839 /usr/lib64/libraw1394.so.11.1.0
    7f127bf61000-7f127bf62000 rw-p 0000c000 08:07 2368839 /usr/lib64/libraw1394.so.11.1.0
    7f127bf62000-7f127bf99000 r-xp 00000000 08:07 2371967 /usr/lib64/libgsttag-1.0.so.0.405.0
    7f127bf99000-7f127c198000 ---p 00037000 08:07 2371967 /usr/lib64/libgsttag-1.0.so.0.405.0
    7f127c198000-7f127c19a000 r--p 00036000 08:07 2371967 /usr/lib64/libgsttag-1.0.so.0.405.0
    7f127c19a000-7f127c19b000 rw-p 00038000 08:07 2371967 /usr/lib64/libgsttag-1.0.so.0.405.0
    7f127c19b000-7f127c19e000 r-xp 00000000 08:07 2371218 /usr/lib64/libgmodule-2.0.so.0.4200.1
    7f127c19e000-7f127c39d000 ---p 00003000 08:07 2371218 /usr/lib64/libgmodule-2.0.so.0.4200.1
    7f127c39d000-7f127c39e000 r--p 00002000 08:07 2371218 /usr/lib64/libgmodule-2.0.so.0.4200.1
    7f127c39e000-7f127c39f000 rw-p 00003000 08:07 2371218 /usr/lib64/libgmodule-2.0.so.0.4200.1
    7f127c39f000-7f127c3a5000 r-xp 00000000 08:07 2369053 /usr/lib64/libIlmThread-2_1.so.11.0.0
    7f127c3a5000-7f127c5a4000 ---p 00006000 08:07 2369053 /usr/lib64/libIlmThread-2_1.so.11.0.0
    7f127c5a4000-7f127c5a5000 r--p 00005000 08:07 2369053 /usr/lib64/libIlmThread-2_1.so.11.0.0
    7f127c5a5000-7f127c5a6000 rw-p 00006000 08:07 2369053 /usr/lib64/libIlmThread-2_1.so.11.0.0
    7f127c5a6000-7f127c5c3000 r-xp 00000000 08:07 2368693 /usr/lib64/libIex-2_1.so.11.0.0
    7f127c5c3000-7f127c7c2000 ---p 0001d000 08:07 2368693 /usr/lib64/libIex-2_1.so.11.0.0
    7f127c7c2000-7f127c7c6000 r--p 0001c000 08:07 2368693 /usr/lib64/libIex-2_1.so.11.0.0
    7f127c7c6000-7f127c7c7000 rw-p 00020000 08:07 2368693 /usr/lib64/libIex-2_1.so.11.0.0
    7f127c7c7000-7f127c7de000 r-xp 00000000 08:07 2368934 /usr/lib64/libspeex.so.1.5.0
    7f127c7de000-7f127c9de000 ---p 00017000 08:07 2368934 /usr/lib64/libspeex.so.1.5.0
    7f127c9de000-7f127c9df000 r--p 00017000 08:07 2368934 /usr/lib64/libspeex.so.1.5.0
    7f127c9df000-7f127c9e0000 rw-p 00018000 08:07 2368934 /usr/lib64/libspeex.so.1.5.0
    7f127c9e0000-7f127ca6d000 r-xp 00000000 08:07 2370649 /usr/lib64/libvorbisenc.so.2.0.10
    7f127ca6d000-7f127cc6c000 ---p 0008d000 08:07 2370649 /usr/lib64/libvorbisenc.so.2.0.10
    7f127cc6c000-7f127cc88000 r--p 0008c000 08:07 2370649 /usr/lib64/libvorbisenc.so.2.0.10
    7f127cc88000-7f127cc89000 rw-p 000a8000 08:07 2370649 /usr/lib64/libvorbisenc.so.2.0.10
    7f127cc89000-7f127ccc6000 r-xp 00000000 08:07 2361237 /usr/lib64/libFLAC.so.8.3.0
    7f127ccc6000-7f127cec6000 ---p 0003d000 08:07 2361237 /usr/lib64/libFLAC.so.8.3.0
    7f127cec6000-7f127cec7000 r--p 0003d000 08:07 2361237 /usr/lib64/libFLAC.so.8.3.0
    7f127cec7000-7f127cec8000 rw-p 0003e000 08:07 2361237 /usr/lib64/libFLAC.so.8.3.0
    7f127cec8000-7f127cedc000 r-xp 00000000 08:07 523469 /lib64/libresolv-2.20.so
    7f127cedc000-7f127d0db000 ---p 00014000 08:07 523469 /lib64/libresolv-2.20.so
    7f127d0db000-7f127d0dc000 r--p 00013000 08:07 523469 /lib64/libresolv-2.20.so
    7f127d0dc000-7f127d0dd000 rw-p 00014000 08:07 523469 /lib64/libresolv-2.20.so
    7f127d0dd000-7f127d0df000 rw-p 00000000 00:00 0
    7f127d0df000-7f127d0f0000 r-xp 00000000 08:07 2367423 /usr/lib64/libgpg-error.so.0.13.0
    7f127d0f0000-7f127d2ef000 ---p 00011000 08:07 2367423 /usr/lib64/libgpg-error.so.0.13.0
    7f127d2ef000-7f127d2f0000 r--p 00010000 08:07 2367423 /usr/lib64/libgpg-error.so.0.13.0
    7f127d2f0000-7f127d2f1000 rw-p 00011000 08:07 2367423 /usr/lib64/libgpg-error.so.0.13.0
    7f127d2f1000-7f127d3cb000 r-xp 00000000 08:07 2366118 /usr/lib64/libgcrypt.so.20.0.2
    7f127d3cb000-7f127d5cb000 ---p 000da000 08:07 2366118 /usr/lib64/libgcrypt.so.20.0.2
    7f127d5cb000-7f127d5cc000 r--p 000da000 08:07 2366118 /usr/lib64/libgcrypt.so.20.0.2
    .....

  2. #2

    Default AW: Digikam in GNOME 3.14.2

    Quote Originally Posted by johnoshock View Post
    Hi,
    I've been trying to install digikam from the repos,
    From which repo?

    ** Error in `digikam': realloc(): invalid pointer: 0x0000000000c14260 ***
    ======= Backtrace: =========
    /lib64/libc.so.6(+0x7283f)[0x7f1298a2b83f]
    /lib64/libc.so.6(+0x77c1e)[0x7f1298a30c1e]
    /lib64/libc.so.6(realloc+0x26a)[0x7f1298a34dfa]
    /usr/lib64/libQt5Core.so.5(_ZN9QListData7reallocEi+0x1e)[0x7f1287e8490e]
    /usr/lib64/libQt5Core.so.5(_ZN9QListData6appendEi+0x6a)[0x7f1287e849ca]
    /usr/lib64/libQt5Core.so.5(+0x1d6f5c)[0x7f1287f4cf5c]
    /usr/lib64/libQt5Core.so.5(_Z21qRegisterResourceDataiPKhS0_S0_+0x2b9)[0x7f1287f49409]
    /usr/lib64/libQt5Core.so.5(+0x807e3)[0x7f1287df67e3]
    /lib64/ld-linux-x86-64.so.2(+0xeaaa)[0x7f129fe60aaa]
    /lib64/ld-linux-x86-64.so.2(+0xeb93)[0x7f129fe60b93]
    /lib64/ld-linux-x86-64.so.2(+0x11ba)[0x7f129fe531ba]
    Your digikam crashes inside Qt5, i.e. you installed the KDE Frameworks 5 version that is not even released yet.
    It should work (it does here), but you probably have an incompatibe Qt5 installed.

    Install digikam (_not_ digikam5) that should work. It is included in the distribution, you don't need any extra repo.
    Last edited by wolfi323; 19-Jan-2015 at 08:14.

  3. #3
    Join Date
    Jul 2013
    Location
    Whitley Bay, Tyne & Wear, United Kingdom.
    Posts
    182

    Default Re: Digikam in GNOME 3.14.2

    I wrote up a ticket on the KDE site... it got solved... the newest updates solved it

  4. #4

    Default Re: Digikam in GNOME 3.14.2

    Quote Originally Posted by johnoshock View Post
    I wrote up a ticket on the KDE site... it got solved... the newest updates solved it
    Yes, digikam5 does work fine here.

    But again, why don't you just use the stable KDE4 version instead, which is included in the distribution?
    digikam5 has not been released yet, there are only unstable development snapshots available.

  5. #5
    Join Date
    Jul 2013
    Location
    Whitley Bay, Tyne & Wear, United Kingdom.
    Posts
    182

    Default Re: Digikam in GNOME 3.14.2

    Quote Originally Posted by wolfi323 View Post
    Yes, digikam5 does work fine here.

    But again, why don't you just use the stable KDE4 version instead, which is included in the distribution?
    digikam5 has not been released yet, there are only unstable development snapshots available.
    hmmmm, I think there's some mistake.. I've been using Digikam 4 all along. I only use what the repos provide. I've got Digikam 4.6, but qt5 is on my machine because of some other apps I have the are using it.
    But anyhow a developer from the KDE Digikam group replied to me and explained how it happened, it was packaged wrongly and that is now rectified.

  6. #6

    Default Re: Digikam in GNOME 3.14.2

    Quote Originally Posted by johnoshock View Post
    hmmmm, I think there's some mistake.. I've been using Digikam 4 all along. I only use what the repos provide. I've got Digikam 4.6, but qt5 is on my machine because of some other apps I have the are using it.
    YaST uses Qt5.

    But digikam 4.6 is _not_ in the standard repos either for any released distribution.
    Are you using Tumbleweed?
    You should have mentioned that, and better even asked in the specific Tumbleweed forum then.

    But anyhow a developer from the KDE Digikam group replied to me and explained how it happened, it was packaged wrongly and that is now rectified.
    Well, your backtrace clearly shows that Qt5 has been loaded, causing the crash.
    If you used digikam4, which is based on Qt4, it might have loaded Qt5 indirectly somehow (maybe because of that packaging problem you mention).

    And when an application uses both Qt4 and Qt5, it crashes.

  7. #7
    Join Date
    Jul 2013
    Location
    Whitley Bay, Tyne & Wear, United Kingdom.
    Posts
    182

    Default Re: Digikam in GNOME 3.14.2

    Quote Originally Posted by wolfi323 View Post
    YaST uses Qt5.

    But digikam 4.6 is _not_ in the standard repos either for any released distribution.
    Are you using Tumbleweed?
    You should have mentioned that, and better even asked in the specific Tumbleweed forum then.


    Well, your backtrace clearly shows that Qt5 has been loaded, causing the crash.
    If you used digikam4, which is based on Qt4, it might have loaded Qt5 indirectly somehow (maybe because of that packaging problem you mention).

    And when an application uses both Qt4 and Qt5, it crashes.
    Yes, I'm using Tumbleweed, I'll bare that in mind in future..Thanks for trying to help
    a backtrace was also given to the Digikam developers along with some other information they required who then responded as I indicated above..... the problem is now solved it was updated within 2 days. .. They said the problem did not lie with openSUSE or myself

  8. #8

    Default Re: Digikam in GNOME 3.14.2

    Quote Originally Posted by johnoshock View Post
    a backtrace was also given to the Digikam developers along with some other information they required who then responded as I indicated above..... the problem is now solved it was updated within 2 days. .. They said the problem did not lie with openSUSE or myself
    Hm, the only recent change in the digikam package is this:
    Code:
    Sat Jan 24 15:44:27 UTC 2015 - adrian@suse.de
     
     - old libkgeomap package provides older lib with same so name, adding
       an explizit requires 
    Which clearly was an openSUSE (packaging) problem.

    Out of curiosity, could you please point me to the bug report?

    As I said, according to the backtrace you posted it was crashing inside Qt5, which digikam should not load at all. And if it is loaded indirectly it would rather sound like a packaging error to me, not an upstream bug.

    Although, it doesn't really matter anyway if it is working now...

  9. #9
    Join Date
    Jul 2013
    Location
    Whitley Bay, Tyne & Wear, United Kingdom.
    Posts
    182

    Default Re: Digikam in GNOME 3.14.2

    Quote Originally Posted by wolfi323 View Post
    Hm, the only recent change in the digikam package is this:
    Code:
    Sat Jan 24 15:44:27 UTC 2015 - adrian@suse.de
     
     - old libkgeomap package provides older lib with same so name, adding
       an explizit requires 
    Which clearly was an openSUSE (packaging) problem.

    Out of curiosity, could you please point me to the bug report?

    As I said, according to the backtrace you posted it was crashing inside Qt5, which digikam should not load at all. And if it is loaded indirectly it would rather sound like a packaging error to me, not an upstream bug.

    Although, it doesn't really matter anyway if it is working now...
    https://bugs.kde.org/show_bug.cgi?id=343031

  10. #10

    Default Re: Digikam in GNOME 3.14.2

    Quote Originally Posted by johnoshock View Post
    Thanks.

    But in that bug report the digikam developer actually states that this was probably an openSUSE packaging problem.

    As there has not really been a change to the digikam package that might have fixed this particular crash, it might have been a problem with some underlying library that digikam uses.
    As I said, according to your backtrace it crashed in Qt5, so probably it loaded some library/plugin that has been built against Qt5 by mistake.
    Your backtrace doesn't really give a hint which one that might have been, but it's fixed now anyway.

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •