Is Digikam stable on KDE SC 4.4?

[Jim Dory-2]

It seems it was pretty stable on KDE4.4 for me for awhile, but now is crashing every time I fiddle with tags. I haven't tried anything else - except that I noticed it wasn't letting me rotate certain images - but that might be another problem. I'm not at that computer right now so can't upload any errors from the shell but could later.

I'm just curious if others are able to run it on kde4.4 - I have seen a post or two from someone who had to downgrade to 4.3. That's why I ask.

cheers, Jim

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Johannes Wienke-3]

Am 26.02.2010 18:36 schrieb Jim Dory:
> It seems it was pretty stable on KDE4.4 for me for awhile, but now is
> crashing every time I fiddle with tags. I haven't tried anything else -
> except that I noticed it wasn't letting me rotate certain images - but that
> might be another problem. I'm not at that computer right now so can't upload
> any errors from the shell but could later.
>
> I'm just curious if others are able to run it on kde4.4 - I have seen a post
> or two from someone who had to downgrade to 4.3. That's why I ask.

I'm also running digikam on 4.4 and it works stable. But we received
some complaints about crashes on 4.4 or Qt 4.6. If you could provide
some backtraces of the crashes, we could debug this much better.

Johannes


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[pshute]

You haven't said which version of digiKam you're running. I had issues with 1.0.0 beta5, but not with later versions.


--------------------------
Sent using BlackBerry

---

From: Jim Dory
To: [hidden email]
Sent: Sat Feb 27 04:36:16 2010
Subject: [Digikam-users] Is Digikam stable on KDE SC 4.4?

It seems it was pretty stable on KDE4.4 for me for awhile, but now is crashing every time I fiddle with tags. I haven't tried anything else - except that I noticed it wasn't letting me rotate certain images - but that might be another problem. I'm not at that computer right now so can't upload any errors from the shell but could later.

I'm just curious if others are able to run it on kde4.4 - I have seen a post or two from someone who had to downgrade to 4.3. That's why I ask.

cheers, Jim

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jim Dory-2]

Apologies for sparce info:
Digikam-1.1.0
built with:
doc geolocation glib lensfun semantic-desktop thumbnails (those might be gentoo specific things ?- USE flags)
Albums on NFS share.

Please for a quick tutorial on backtrace? I could rebuild with USE flag "debug" for more info from shell perhaps?

thx, Jim

On Fri, Feb 26, 2010 at 8:51 AM, Peter Shute <[hidden email]> wrote:

You haven't said which version of digiKam you're running. I had issues with 1.0.0 beta5, but not with later versions.


--------------------------
Sent using BlackBerry

---

From: Jim Dory
To: [hidden email]
Sent: Sat Feb 27 04:36:16 2010
Subject: [Digikam-users] Is Digikam stable on KDE SC 4.4?

It seems it was pretty stable on KDE4.4 for me for awhile, but now is crashing every time I fiddle with tags. I haven't tried anything else - except that I noticed it wasn't letting me rotate certain images - but that might be another problem. I'm not at that computer right now so can't upload any errors from the shell but could later.

I'm just curious if others are able to run it on kde4.4 - I have seen a post or two from someone who had to downgrade to 4.3. That's why I ask.

cheers, Jim

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jim Dory-2]

Below are all USE flags as it is presently. I had just rebuilt using doc to see if that would provide help files but didn't seem to. But don't think it created instability.


ebuild   R   ] media-gfx/digikam-1.1.0  USE="doc geolocation glib lensfun semantic-desktop thumbnails -addressbook (-aqua) -debug -gphoto2 (-kdeenablefinal)" LINGUAS="-ar -be -bg -ca -ca@valencia -cs -da -de -el -en_GB -eo -es -et -eu -fa -fi -fr -ga -gl -he -hi -hne -hr -hu -is -it -ja -km -ko -lt -lv -nb -nds -ne -nl -nn -pa -pl -pt -pt_BR -ro -ru -se -sk -sl -sv -th -tr -uk -vi -zh_CN -zh_TW" 0 kB

/jim

On Fri, Feb 26, 2010 at 9:14 AM, Jim Dory <[hidden email]> wrote:

Apologies for sparce info:
Digikam-1.1.0
built with:
doc geolocation glib lensfun semantic-desktop thumbnails (those might be gentoo specific things ?- USE flags)
Albums on NFS share.

Please for a quick tutorial on backtrace? I could rebuild with USE flag "debug" for more info from shell perhaps?

thx, Jim

On Fri, Feb 26, 2010 at 8:51 AM, Peter Shute <[hidden email]> wrote:

You haven't said which version of digiKam you're running. I had issues with 1.0.0 beta5, but not with later versions.


--------------------------
Sent using BlackBerry

---

From: Jim Dory
To: [hidden email]
Sent: Sat Feb 27 04:36:16 2010
Subject: [Digikam-users] Is Digikam stable on KDE SC 4.4?

It seems it was pretty stable on KDE4.4 for me for awhile, but now is crashing every time I fiddle with tags. I haven't tried anything else - except that I noticed it wasn't letting me rotate certain images - but that might be another problem. I'm not at that computer right now so can't upload any errors from the shell but could later.

I'm just curious if others are able to run it on kde4.4 - I have seen a post or two from someone who had to downgrade to 4.3. That's why I ask.

cheers, Jim

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Look here :

http://www.digikam.org/drupal/contrib

Gilles Caulier

2010/2/26 Jim Dory <[hidden email]>:

> Below are all USE flags as it is presently. I had just rebuilt using doc to
> see if that would provide help files but didn't seem to. But don't think it
> created instability.
>
>
> ebuild   R   ] media-gfx/digikam-1.1.0  USE="doc geolocation glib lensfun
> semantic-desktop thumbnails -addressbook (-aqua) -debug -gphoto2
> (-kdeenablefinal)" LINGUAS="-ar -be -bg -ca -ca@valencia -cs -da -de -el
> -en_GB -eo -es -et -eu -fa -fi -fr -ga -gl -he -hi -hne -hr -hu -is -it -ja
> -km -ko -lt -lv -nb -nds -ne -nl -nn -pa -pl -pt -pt_BR -ro -ru -se -sk -sl
> -sv -th -tr -uk -vi -zh_CN -zh_TW" 0 kB
>
> /jim
>
>
> On Fri, Feb 26, 2010 at 9:14 AM, Jim Dory <[hidden email]> wrote:
>>
>> Apologies for sparce info:
>> Digikam-1.1.0
>> built with:
>> doc geolocation glib lensfun semantic-desktop thumbnails (those might be
>> gentoo specific things ?- USE flags)
>> Albums on NFS share.
>>
>> Please for a quick tutorial on backtrace? I could rebuild with USE flag
>> "debug" for more info from shell perhaps?
>>
>> thx, Jim
>>
>>
>> On Fri, Feb 26, 2010 at 8:51 AM, Peter Shute <[hidden email]> wrote:
>>>
>>> You haven't said which version of digiKam you're running. I had issues
>>> with 1.0.0 beta5, but not with later versions.
>>>
>>>
>>> --------------------------
>>> Sent using BlackBerry
>>>
>>> ________________________________
>>> From: Jim Dory
>>> To: [hidden email]
>>> Sent: Sat Feb 27 04:36:16 2010
>>> Subject: [Digikam-users] Is Digikam stable on KDE SC 4.4?
>>> It seems it was pretty stable on KDE4.4 for me for awhile, but now is
>>> crashing every time I fiddle with tags. I haven't tried anything else -
>>> except that I noticed it wasn't letting me rotate certain images - but that
>>> might be another problem. I'm not at that computer right now so can't upload
>>> any errors from the shell but could later.
>>>
>>> I'm just curious if others are able to run it on kde4.4 - I have seen a
>>> post or two from someone who had to downgrade to 4.3. That's why I ask.
>>>
>>> cheers, Jim
>>>
>>> _______________________________________________
>>> Digikam-users mailing list
>>> [hidden email]
>>> https://mail.kde.org/mailman/listinfo/digikam-users
>>>
>>
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jim Dory-2]

I'll include a bit more before the crash to give some context (at the time I was working on a jpeg - not a raw file):

digikam(16372)/digikam (core) Digikam::TagEditDlg::createTAlbum: ("Wilders")                                                                                                 
digikam(16372)/digikam (core) Digikam::TagEditDlg::createTAlbum: "Wilders"  ::  "/people/Bands/Wilders"                                                                      
digikam(16372)/KDCRAW KDcrawIface::KDcraw::loadEmbeddedPreview: Failed to load embedded RAW preview                                                                          
digikam(16372)/digikam (core) Digikam::DImg::load: "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000176.jpg"  : JPEG file identified                             
digikam(16372)/digikam (core) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile.                                               
digikam(16372)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation =>  1
digikam(16372)/KDCRAW KDcrawIface::KDcraw::loadEmbeddedPreview: Failed to load embedded RAW preview
digikam(16372)/digikam (core) Digikam::DImg::load: "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000177.jpg"  : JPEG file identified
digikam(16372)/digikam (core) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile.
digikam(16372)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation =>  1
digikam(16372)/KDCRAW KDcrawIface::KDcraw::loadEmbeddedPreview: Failed to load embedded RAW preview
Warning: XMP toolkit support not compiled in.
Warning: Failed to decode XMP metadata.
digikam(16372)/digikam (core) Digikam::DImg::load: "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000175.jpg"  : JPEG file identified
Warning: XMP toolkit support not compiled in.
Warning: Failed to decode XMP metadata.
digikam(16372)/digikam (core) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile.
Warning: XMP toolkit support not compiled in.
Warning: Failed to decode XMP metadata.
digikam(16372)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation =>  1
digikam(16372)/digikam (core) Digikam::DMetadata::setImageComments: "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"  ==> Comment:  QMap()
digikam(16372)/digikam (core) Digikam::DMetadata::setImageRating: "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"  ==> Rating:  0
digikam(16372)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords: /mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg  ==> Iptc Keywords:  minnesota,music,festival,Wilders
digikam(16372)/KEXIV2 KExiv2Iface::KExiv2::save: File Extension:  "jpg"  is supported for writing mode
digikam(16372)/digikam (core) Digikam::DImg::load: "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"  : JPEG file identified
digikam(16372)/digikam (core) Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1540 "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"

Program received signal SIGSEGV, Segmentation fault.
0xb62e5beb in QString::operator==(QString const&) const () from /usr/lib/qt4/libQtCore.so.4
(gdb) bt
#0  0xb62e5beb in QString::operator==(QString const&) const () from /usr/lib/qt4/libQtCore.so.4
#1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
#2  0x08e4baa0 in ?? ()
#3  0xbfffd9f4 in ?? ()
#4  0x00000020 in ?? ()
#5  0xb62f73ef in QVectorData::allocate(int, int) () from /usr/lib/qt4/libQtCore.so.4
#6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
#7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
#8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
#9  0xbfffd93c in ?? ()
#10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
#11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
#12 0x00000001 in ?? ()
#13 0x0ab8a06e in ?? ()
#14 0x0ab8a0f4 in ?? ()
#15 0xbfffd624 in ?? ()
#16 0x00000000 in ?? ()
(gdb) quit
A debugging session is active.

        Inferior 1 [process 16372] will be killed.

On Fri, Feb 26, 2010 at 9:24 AM, Gilles Caulier <[hidden email]> wrote:

Look here :

http://www.digikam.org/drupal/contrib

Gilles Caulier

2010/2/26 Jim Dory <[hidden email]>:

> Below are all USE flags as it is presently. I had just rebuilt using doc to
> see if that would provide help files but didn't seem to. But don't think it
> created instability.
>
>
> ebuild   R   ] media-gfx/digikam-1.1.0  USE="doc geolocation glib lensfun
> semantic-desktop thumbnails -addressbook (-aqua) -debug -gphoto2
> (-kdeenablefinal)" LINGUAS="-ar -be -bg -ca -ca@valencia -cs -da -de -el
> -en_GB -eo -es -et -eu -fa -fi -fr -ga -gl -he -hi -hne -hr -hu -is -it -ja
> -km -ko -lt -lv -nb -nds -ne -nl -nn -pa -pl -pt -pt_BR -ro -ru -se -sk -sl
> -sv -th -tr -uk -vi -zh_CN -zh_TW" 0 kB
>
> /jim
>
>
> On Fri, Feb 26, 2010 at 9:14 AM, Jim Dory <[hidden email]> wrote:
>>
>> Apologies for sparce info:
>> Digikam-1.1.0
>> built with:
>> doc geolocation glib lensfun semantic-desktop thumbnails (those might be
>> gentoo specific things ?- USE flags)
>> Albums on NFS share.
>>
>> Please for a quick tutorial on backtrace? I could rebuild with USE flag
>> "debug" for more info from shell perhaps?
>>
>> thx, Jim
>>
>>
>> On Fri, Feb 26, 2010 at 8:51 AM, Peter Shute <[hidden email]> wrote:
>>>
>>> You haven't said which version of digiKam you're running. I had issues
>>> with 1.0.0 beta5, but not with later versions.
>>>
>>>
>>> --------------------------
>>> Sent using BlackBerry
>>>
>>> ________________________________
>>> From: Jim Dory
>>> To: [hidden email]
>>> Sent: Sat Feb 27 04:36:16 2010
>>> Subject: [Digikam-users] Is Digikam stable on KDE SC 4.4?
>>> It seems it was pretty stable on KDE4.4 for me for awhile, but now is
>>> crashing every time I fiddle with tags. I haven't tried anything else -
>>> except that I noticed it wasn't letting me rotate certain images - but that
>>> might be another problem. I'm not at that computer right now so can't upload
>>> any errors from the shell but could later.
>>>
>>> I'm just curious if others are able to run it on kde4.4 - I have seen a
>>> post or two from someone who had to downgrade to 4.3. That's why I ask.
>>>
>>> cheers, Jim
>>>
>>> _______________________________________________
>>> Digikam-users mailing list
>>> [hidden email]
>>> https://mail.kde.org/mailman/listinfo/digikam-users
>>>
>>
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Johannes Wienke-3]

Am 26.02.2010 20:38 schrieb Jim Dory:

> digikam(16372)/digikam (core) Digikam::DImg::load:
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"  :
> JPEG file identified
> digikam(16372)/digikam (core)
> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1540
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb62e5beb in QString::operator==(QString const&) const () from
> /usr/lib/qt4/libQtCore.so.4
> (gdb) bt
> #0  0xb62e5beb in QString::operator==(QString const&) const () from
> /usr/lib/qt4/libQtCore.so.4
> #1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
> #2  0x08e4baa0 in ?? ()
> #3  0xbfffd9f4 in ?? ()
> #4  0x00000020 in ?? ()
> #5  0xb62f73ef in QVectorData::allocate(int, int) () from
> /usr/lib/qt4/libQtCore.so.4
> #6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
> #7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
> #8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
> #9  0xbfffd93c in ?? ()
> #10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
> #11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
> #12 0x00000001 in ?? ()
> #13 0x0ab8a06e in ?? ()
> #14 0x0ab8a0f4 in ?? ()
> #15 0xbfffd624 in ?? ()
> #16 0x00000000 in ?? ()
> (gdb) quit
> A debugging session is active.

Can you try to install the kdelibs-dbg packages and try to reproduce the
crash?

Regards,
Johannes


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Johannes Wienke-3]

Am 26.02.2010 20:52 schrieb Johannes Wienke:

> Am 26.02.2010 20:38 schrieb Jim Dory:
>> digikam(16372)/digikam (core) Digikam::DImg::load:
>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"  :
>> JPEG file identified
>> digikam(16372)/digikam (core)
>> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1540
>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0xb62e5beb in QString::operator==(QString const&) const () from
>> /usr/lib/qt4/libQtCore.so.4
>> (gdb) bt
>> #0  0xb62e5beb in QString::operator==(QString const&) const () from
>> /usr/lib/qt4/libQtCore.so.4
>> #1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
>> #2  0x08e4baa0 in ?? ()
>> #3  0xbfffd9f4 in ?? ()
>> #4  0x00000020 in ?? ()
>> #5  0xb62f73ef in QVectorData::allocate(int, int) () from
>> /usr/lib/qt4/libQtCore.so.4
>> #6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
>> #7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
>> #8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
>> #9  0xbfffd93c in ?? ()
>> #10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
>> #11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
>> #12 0x00000001 in ?? ()
>> #13 0x0ab8a06e in ?? ()
>> #14 0x0ab8a0f4 in ?? ()
>> #15 0xbfffd624 in ?? ()
>> #16 0x00000000 in ?? ()
>> (gdb) quit
>> A debugging session is active.
>
> Can you try to install the kdelibs-dbg packages and try to reproduce the
> crash?

Just noticed you're on gentoo. You will ahve to recompile kdelibs with
the debug use flag.

Johannes


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jim Dory-2]

Ok, re-compiled kdelibs with USE="debug" but the output hasn't improved much. Let me know if there is another step to improve back trace. I'll post below with a bit more context:

digikam(15816)/khtml (caret) DOM::Selection::validate: Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] 0
digikam(15816)/khtml (caret) DOM::Selection::validate: [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
digikam(15816)/digikam (core) Digikam::DMetadata::setImageComments: "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  ==> Comment:  QMap()
digikam(15816)/digikam (core) Digikam::DMetadata::setImageRating: "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  ==> Rating:  0
digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords: /mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg  ==> Iptc Keywords:  Carol,nome alaska,hike,water,Dorothy creek
digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::save: File Extension:  "jpg"  is supported for writing mode
digikam(15816)/digikam (core) Digikam::DImg::load: "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  : JPEG file identified
digikam(15816)/digikam (core) Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1457 "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"

Program received signal SIGSEGV, Segmentation fault.
0xb62a6beb in QString::operator==(QString const&) const () from /usr/lib/qt4/libQtCore.so.4
(gdb) bt
#0  0xb62a6beb in QString::operator==(QString const&) const () from /usr/lib/qt4/libQtCore.so.4
#1  0xb6b4f717 in ?? () from /usr/lib/libkio.so.5
#2  0x09081470 in ?? ()
#3  0xbfffd444 in ?? ()
#4  0xbfffd444 in ?? ()
#5  0xb62aa4a6 in QString::append(QString const&) () from /usr/lib/qt4/libQtCore.so.4
#6  0x00000000 in ?? ()
(gdb)


/jim

On Fri, Feb 26, 2010 at 10:54 AM, Johannes Wienke <[hidden email]> wrote:

Am 26.02.2010 20:52 schrieb Johannes Wienke:

> Am 26.02.2010 20:38 schrieb Jim Dory:
>> digikam(16372)/digikam (core) Digikam::DImg::load:
>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"  :
>> JPEG file identified
>> digikam(16372)/digikam (core)
>> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1540
>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0xb62e5beb in QString::operator==(QString const&) const () from
>> /usr/lib/qt4/libQtCore.so.4
>> (gdb) bt
>> #0  0xb62e5beb in QString::operator==(QString const&) const () from
>> /usr/lib/qt4/libQtCore.so.4
>> #1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
>> #2  0x08e4baa0 in ?? ()
>> #3  0xbfffd9f4 in ?? ()
>> #4  0x00000020 in ?? ()
>> #5  0xb62f73ef in QVectorData::allocate(int, int) () from
>> /usr/lib/qt4/libQtCore.so.4
>> #6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
>> #7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
>> #8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
>> #9  0xbfffd93c in ?? ()
>> #10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
>> #11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
>> #12 0x00000001 in ?? ()
>> #13 0x0ab8a06e in ?? ()
>> #14 0x0ab8a0f4 in ?? ()
>> #15 0xbfffd624 in ?? ()
>> #16 0x00000000 in ?? ()
>> (gdb) quit
>> A debugging session is active.
>
> Can you try to install the kdelibs-dbg packages and try to reproduce the
> crash?

Just noticed you're on gentoo. You will ahve to recompile kdelibs with
the debug use flag.

Johannes


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

It's KDirWatch bug :

https://bugs.kde.org/show_bug.cgi?id=228562

Update KDE to 4.1

Gilles Caulier

2010/2/26 Jim Dory <[hidden email]>:

> Ok, re-compiled kdelibs with USE="debug" but the output hasn't improved
> much. Let me know if there is another step to improve back trace. I'll post
> below with a bit more context:
>
> digikam(15816)/khtml (caret) DOM::Selection::validate: Selection[ Position(
> 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
> Position( 0x0 "null" : 0 ) 1 ] 0
> digikam(15816)/khtml (caret) DOM::Selection::validate:
> [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0 "null"
> : 0 )
> digikam(15816)/digikam (core) Digikam::DMetadata::setImageComments:
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  ==>
> Comment:  QMap()
> digikam(15816)/digikam (core) Digikam::DMetadata::setImageRating:
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  ==>
> Rating:  0
> digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords:
> /mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg  ==>
> Iptc Keywords:  Carol,nome alaska,hike,water,Dorothy creek
> digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::save: File Extension:  "jpg"  is
> supported for writing mode
> digikam(15816)/digikam (core) Digikam::DImg::load:
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  :
> JPEG file identified
> digikam(15816)/digikam (core)
> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1457
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb62a6beb in QString::operator==(QString const&) const () from
> /usr/lib/qt4/libQtCore.so.4
> (gdb) bt
> #0  0xb62a6beb in QString::operator==(QString const&) const () from
> /usr/lib/qt4/libQtCore.so.4
> #1  0xb6b4f717 in ?? () from /usr/lib/libkio.so.5
> #2  0x09081470 in ?? ()
> #3  0xbfffd444 in ?? ()
> #4  0xbfffd444 in ?? ()
> #5  0xb62aa4a6 in QString::append(QString const&) () from
> /usr/lib/qt4/libQtCore.so.4
> #6  0x00000000 in ?? ()
> (gdb)
>
>
> /jim
>
>
> On Fri, Feb 26, 2010 at 10:54 AM, Johannes Wienke <[hidden email]>
> wrote:
>>
>> Am 26.02.2010 20:52 schrieb Johannes Wienke:
>> > Am 26.02.2010 20:38 schrieb Jim Dory:
>> >> digikam(16372)/digikam (core) Digikam::DImg::load:
>> >> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>> >>  :
>> >> JPEG file identified
>> >> digikam(16372)/digikam (core)
>> >> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1540
>> >> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>> >>
>> >> Program received signal SIGSEGV, Segmentation fault.
>> >> 0xb62e5beb in QString::operator==(QString const&) const () from
>> >> /usr/lib/qt4/libQtCore.so.4
>> >> (gdb) bt
>> >> #0  0xb62e5beb in QString::operator==(QString const&) const () from
>> >> /usr/lib/qt4/libQtCore.so.4
>> >> #1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
>> >> #2  0x08e4baa0 in ?? ()
>> >> #3  0xbfffd9f4 in ?? ()
>> >> #4  0x00000020 in ?? ()
>> >> #5  0xb62f73ef in QVectorData::allocate(int, int) () from
>> >> /usr/lib/qt4/libQtCore.so.4
>> >> #6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
>> >> #7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
>> >> #8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
>> >> #9  0xbfffd93c in ?? ()
>> >> #10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
>> >> #11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
>> >> #12 0x00000001 in ?? ()
>> >> #13 0x0ab8a06e in ?? ()
>> >> #14 0x0ab8a0f4 in ?? ()
>> >> #15 0xbfffd624 in ?? ()
>> >> #16 0x00000000 in ?? ()
>> >> (gdb) quit
>> >> A debugging session is active.
>> >
>> > Can you try to install the kdelibs-dbg packages and try to reproduce the
>> > crash?
>>
>> Just noticed you're on gentoo. You will ahve to recompile kdelibs with
>> the debug use flag.
>>
>> Johannes
>>
>>
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jim Dory-2]

I don't think I understand. Surely you don't mean kde 4.1. That is not very usable. But you must, as I don't think a 4.4.1 has been released yet. Don't see it on the mirrors. There is an unstable 4.4.65.. but doubt you meant that. I looked at the bug and didn't see any discussion about it. I followed some of the duplicate bug links and found a bit more discussion, but no solution. I'll admit I'm used to gentoo's bug reports and not these - so might be missing something.

If you mean kde 4.1, then I'll have to not use Digikam until this bug gets resolved one way or another.

thanks for the help, Jim

On Fri, Feb 26, 2010 at 10:46 PM, Gilles Caulier <[hidden email]> wrote:

It's KDirWatch bug :

https://bugs.kde.org/show_bug.cgi?id=228562

Update KDE to 4.1

Gilles Caulier

2010/2/26 Jim Dory <[hidden email]>:

> Ok, re-compiled kdelibs with USE="debug" but the output hasn't improved
> much. Let me know if there is another step to improve back trace. I'll post
> below with a bit more context:
>
> digikam(15816)/khtml (caret) DOM::Selection::validate: Selection[ Position(
> 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
> Position( 0x0 "null" : 0 ) 1 ] 0
> digikam(15816)/khtml (caret) DOM::Selection::validate:
> [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0 "null"
> : 0 )
> digikam(15816)/digikam (core) Digikam::DMetadata::setImageComments:
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  ==>
> Comment:  QMap()
> digikam(15816)/digikam (core) Digikam::DMetadata::setImageRating:
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  ==>
> Rating:  0
> digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords:
> /mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg  ==>
> Iptc Keywords:  Carol,nome alaska,hike,water,Dorothy creek
> digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::save: File Extension:  "jpg"  is
> supported for writing mode
> digikam(15816)/digikam (core) Digikam::DImg::load:
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  :
> JPEG file identified
> digikam(15816)/digikam (core)
> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1457
> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb62a6beb in QString::operator==(QString const&) const () from
> /usr/lib/qt4/libQtCore.so.4
> (gdb) bt
> #0  0xb62a6beb in QString::operator==(QString const&) const () from
> /usr/lib/qt4/libQtCore.so.4
> #1  0xb6b4f717 in ?? () from /usr/lib/libkio.so.5
> #2  0x09081470 in ?? ()
> #3  0xbfffd444 in ?? ()
> #4  0xbfffd444 in ?? ()
> #5  0xb62aa4a6 in QString::append(QString const&) () from
> /usr/lib/qt4/libQtCore.so.4
> #6  0x00000000 in ?? ()
> (gdb)
>
>
> /jim
>
>
> On Fri, Feb 26, 2010 at 10:54 AM, Johannes Wienke <[hidden email]>
> wrote:
>>
>> Am 26.02.2010 20:52 schrieb Johannes Wienke:
>> > Am 26.02.2010 20:38 schrieb Jim Dory:
>> >> digikam(16372)/digikam (core) Digikam::DImg::load:
>> >> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>> >>  :
>> >> JPEG file identified
>> >> digikam(16372)/digikam (core)
>> >> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1540
>> >> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>> >>
>> >> Program received signal SIGSEGV, Segmentation fault.
>> >> 0xb62e5beb in QString::operator==(QString const&) const () from
>> >> /usr/lib/qt4/libQtCore.so.4
>> >> (gdb) bt
>> >> #0  0xb62e5beb in QString::operator==(QString const&) const () from
>> >> /usr/lib/qt4/libQtCore.so.4
>> >> #1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
>> >> #2  0x08e4baa0 in ?? ()
>> >> #3  0xbfffd9f4 in ?? ()
>> >> #4  0x00000020 in ?? ()
>> >> #5  0xb62f73ef in QVectorData::allocate(int, int) () from
>> >> /usr/lib/qt4/libQtCore.so.4
>> >> #6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
>> >> #7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
>> >> #8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
>> >> #9  0xbfffd93c in ?? ()
>> >> #10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
>> >> #11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
>> >> #12 0x00000001 in ?? ()
>> >> #13 0x0ab8a06e in ?? ()
>> >> #14 0x0ab8a0f4 in ?? ()
>> >> #15 0xbfffd624 in ?? ()
>> >> #16 0x00000000 in ?? ()
>> >> (gdb) quit
>> >> A debugging session is active.
>> >
>> > Can you try to install the kdelibs-dbg packages and try to reproduce the
>> > crash?
>>
>> Just noticed you're on gentoo. You will ahve to recompile kdelibs with
>> the debug use flag.
>>
>> Johannes
>>
>>
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Yes, i want mean KDE 4.4.1 (:=)))

Gilles

2010/2/27 Jim Dory <[hidden email]>:

> I don't think I understand. Surely you don't mean kde 4.1. That is not very
> usable. But you must, as I don't think a 4.4.1 has been released yet. Don't
> see it on the mirrors. There is an unstable 4.4.65.. but doubt you meant
> that. I looked at the bug and didn't see any discussion about it. I followed
> some of the duplicate bug links and found a bit more discussion, but no
> solution. I'll admit I'm used to gentoo's bug reports and not these - so
> might be missing something.
>
> If you mean kde 4.1, then I'll have to not use Digikam until this bug gets
> resolved one way or another.
>
> thanks for the help, Jim
>
>
>
> On Fri, Feb 26, 2010 at 10:46 PM, Gilles Caulier <[hidden email]>
> wrote:
>>
>> It's KDirWatch bug :
>>
>> https://bugs.kde.org/show_bug.cgi?id=228562
>>
>> Update KDE to 4.1
>>
>> Gilles Caulier
>>
>> 2010/2/26 Jim Dory <[hidden email]>:
>> > Ok, re-compiled kdelibs with USE="debug" but the output hasn't improved
>> > much. Let me know if there is another step to improve back trace. I'll
>> > post
>> > below with a bit more context:
>> >
>> > digikam(15816)/khtml (caret) DOM::Selection::validate: Selection[
>> > Position(
>> > 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
>> > Position( 0x0 "null" : 0 ) 1 ] 0
>> > digikam(15816)/khtml (caret) DOM::Selection::validate:
>> > [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0
>> > "null"
>> > : 0 )
>> > digikam(15816)/digikam (core) Digikam::DMetadata::setImageComments:
>> > "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
>> > ==>
>> > Comment:  QMap()
>> > digikam(15816)/digikam (core) Digikam::DMetadata::setImageRating:
>> > "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
>> > ==>
>> > Rating:  0
>> > digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords:
>> > /mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg  ==>
>> > Iptc Keywords:  Carol,nome alaska,hike,water,Dorothy creek
>> > digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::save: File Extension:  "jpg"
>> > is
>> > supported for writing mode
>> > digikam(15816)/digikam (core) Digikam::DImg::load:
>> > "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  :
>> > JPEG file identified
>> > digikam(15816)/digikam (core)
>> > Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1457
>> > "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
>> >
>> > Program received signal SIGSEGV, Segmentation fault.
>> > 0xb62a6beb in QString::operator==(QString const&) const () from
>> > /usr/lib/qt4/libQtCore.so.4
>> > (gdb) bt
>> > #0  0xb62a6beb in QString::operator==(QString const&) const () from
>> > /usr/lib/qt4/libQtCore.so.4
>> > #1  0xb6b4f717 in ?? () from /usr/lib/libkio.so.5
>> > #2  0x09081470 in ?? ()
>> > #3  0xbfffd444 in ?? ()
>> > #4  0xbfffd444 in ?? ()
>> > #5  0xb62aa4a6 in QString::append(QString const&) () from
>> > /usr/lib/qt4/libQtCore.so.4
>> > #6  0x00000000 in ?? ()
>> > (gdb)
>> >
>> >
>> > /jim
>> >
>> >
>> > On Fri, Feb 26, 2010 at 10:54 AM, Johannes Wienke <[hidden email]>
>> > wrote:
>> >>
>> >> Am 26.02.2010 20:52 schrieb Johannes Wienke:
>> >> > Am 26.02.2010 20:38 schrieb Jim Dory:
>> >> >> digikam(16372)/digikam (core) Digikam::DImg::load:
>> >> >>
>> >> >> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>> >> >>  :
>> >> >> JPEG file identified
>> >> >> digikam(16372)/digikam (core)
>> >> >> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1540
>> >> >>
>> >> >> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>> >> >>
>> >> >> Program received signal SIGSEGV, Segmentation fault.
>> >> >> 0xb62e5beb in QString::operator==(QString const&) const () from
>> >> >> /usr/lib/qt4/libQtCore.so.4
>> >> >> (gdb) bt
>> >> >> #0  0xb62e5beb in QString::operator==(QString const&) const () from
>> >> >> /usr/lib/qt4/libQtCore.so.4
>> >> >> #1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
>> >> >> #2  0x08e4baa0 in ?? ()
>> >> >> #3  0xbfffd9f4 in ?? ()
>> >> >> #4  0x00000020 in ?? ()
>> >> >> #5  0xb62f73ef in QVectorData::allocate(int, int) () from
>> >> >> /usr/lib/qt4/libQtCore.so.4
>> >> >> #6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
>> >> >> #7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
>> >> >> #8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
>> >> >> #9  0xbfffd93c in ?? ()
>> >> >> #10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
>> >> >> #11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
>> >> >> #12 0x00000001 in ?? ()
>> >> >> #13 0x0ab8a06e in ?? ()
>> >> >> #14 0x0ab8a0f4 in ?? ()
>> >> >> #15 0xbfffd624 in ?? ()
>> >> >> #16 0x00000000 in ?? ()
>> >> >> (gdb) quit
>> >> >> A debugging session is active.
>> >> >
>> >> > Can you try to install the kdelibs-dbg packages and try to reproduce
>> >> > the
>> >> > crash?
>> >>
>> >> Just noticed you're on gentoo. You will ahve to recompile kdelibs with
>> >> the debug use flag.
>> >>
>> >> Johannes
>> >>
>> >>
>> >> _______________________________________________
>> >> Digikam-users mailing list
>> >> [hidden email]
>> >> https://mail.kde.org/mailman/listinfo/digikam-users
>> >>
>> >
>> >
>> > _______________________________________________
>> > Digikam-users mailing list
>> > [hidden email]
>> > https://mail.kde.org/mailman/listinfo/digikam-users
>> >
>> >
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Arnd Baecker]

On Sat, 27 Feb 2010, Gilles Caulier wrote:

> Yes, i want mean KDE 4.4.1 (:=)))

Hmm, does that mean to get a stable digikam
one has to install the svn version of the upcoming 4.4.1 ?
I.e., should one follow
http://techbase.kde.org/Getting_Started/Build/KDE4
and install kdelibs, kdepimlibs, and of kdebase the runtime part
(is that all which is needed?).
Of course, to not screw the system wide KDE installation,
this would mean to install everything to a seperate place
and set up all paths accordingly?

I am asking because with my old ubuntu 08.04 it seems
that I have to go along that route
(updating is not possible at this point ... ;-( )

Best, Arnd

> Gilles
>
> 2010/2/27 Jim Dory <[hidden email]>:
> > I don't think I understand. Surely you don't mean kde 4.1. That is not very
> > usable. But you must, as I don't think a 4.4.1 has been released yet. Don't
> > see it on the mirrors. There is an unstable 4.4.65.. but doubt you meant
> > that. I looked at the bug and didn't see any discussion about it. I followed
> > some of the duplicate bug links and found a bit more discussion, but no
> > solution. I'll admit I'm used to gentoo's bug reports and not these - so
> > might be missing something.
> >
> > If you mean kde 4.1, then I'll have to not use Digikam until this bug gets
> > resolved one way or another.
> >
> > thanks for the help, Jim
> >
> >
> >
> > On Fri, Feb 26, 2010 at 10:46 PM, Gilles Caulier <[hidden email]>
> > wrote:
> >>
> >> It's KDirWatch bug :
> >>
> >> https://bugs.kde.org/show_bug.cgi?id=228562
> >>
> >> Update KDE to 4.1
> >>
> >> Gilles Caulier
> >>
> >> 2010/2/26 Jim Dory <[hidden email]>:
> >> > Ok, re-compiled kdelibs with USE="debug" but the output hasn't improved
> >> > much. Let me know if there is another step to improve back trace. I'll
> >> > post
> >> > below with a bit more context:
> >> >
> >> > digikam(15816)/khtml (caret) DOM::Selection::validate: Selection[
> >> > Position(
> >> > 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
> >> > Position( 0x0 "null" : 0 ) 1 ] 0
> >> > digikam(15816)/khtml (caret) DOM::Selection::validate:
> >> > [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0
> >> > "null"
> >> > : 0 )
> >> > digikam(15816)/digikam (core) Digikam::DMetadata::setImageComments:
> >> > "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
> >> > ==>
> >> > Comment:  QMap()
> >> > digikam(15816)/digikam (core) Digikam::DMetadata::setImageRating:
> >> > "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
> >> > ==>
> >> > Rating:  0
> >> > digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords:
> >> > /mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg  ==>
> >> > Iptc Keywords:  Carol,nome alaska,hike,water,Dorothy creek
> >> > digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::save: File Extension:  "jpg"
> >> > is
> >> > supported for writing mode
> >> > digikam(15816)/digikam (core) Digikam::DImg::load:
> >> > "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  :
> >> > JPEG file identified
> >> > digikam(15816)/digikam (core)
> >> > Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1457
> >> > "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
> >> >
> >> > Program received signal SIGSEGV, Segmentation fault.
> >> > 0xb62a6beb in QString::operator==(QString const&) const () from
> >> > /usr/lib/qt4/libQtCore.so.4
> >> > (gdb) bt
> >> > #0  0xb62a6beb in QString::operator==(QString const&) const () from
> >> > /usr/lib/qt4/libQtCore.so.4
> >> > #1  0xb6b4f717 in ?? () from /usr/lib/libkio.so.5
> >> > #2  0x09081470 in ?? ()
> >> > #3  0xbfffd444 in ?? ()
> >> > #4  0xbfffd444 in ?? ()
> >> > #5  0xb62aa4a6 in QString::append(QString const&) () from
> >> > /usr/lib/qt4/libQtCore.so.4
> >> > #6  0x00000000 in ?? ()
> >> > (gdb)
> >> >
> >> >
> >> > /jim
> >> >
> >> >
> >> > On Fri, Feb 26, 2010 at 10:54 AM, Johannes Wienke <[hidden email]>
> >> > wrote:
> >> >>
> >> >> Am 26.02.2010 20:52 schrieb Johannes Wienke:
> >> >> > Am 26.02.2010 20:38 schrieb Jim Dory:
> >> >> >> digikam(16372)/digikam (core) Digikam::DImg::load:
> >> >> >>
> >> >> >> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
> >> >> >>  :
> >> >> >> JPEG file identified
> >> >> >> digikam(16372)/digikam (core)
> >> >> >> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1540
> >> >> >>
> >> >> >> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
> >> >> >>
> >> >> >> Program received signal SIGSEGV, Segmentation fault.
> >> >> >> 0xb62e5beb in QString::operator==(QString const&) const () from
> >> >> >> /usr/lib/qt4/libQtCore.so.4
> >> >> >> (gdb) bt
> >> >> >> #0  0xb62e5beb in QString::operator==(QString const&) const () from
> >> >> >> /usr/lib/qt4/libQtCore.so.4
> >> >> >> #1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
> >> >> >> #2  0x08e4baa0 in ?? ()
> >> >> >> #3  0xbfffd9f4 in ?? ()
> >> >> >> #4  0x00000020 in ?? ()
> >> >> >> #5  0xb62f73ef in QVectorData::allocate(int, int) () from
> >> >> >> /usr/lib/qt4/libQtCore.so.4
> >> >> >> #6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
> >> >> >> #7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
> >> >> >> #8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
> >> >> >> #9  0xbfffd93c in ?? ()
> >> >> >> #10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
> >> >> >> #11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
> >> >> >> #12 0x00000001 in ?? ()
> >> >> >> #13 0x0ab8a06e in ?? ()
> >> >> >> #14 0x0ab8a0f4 in ?? ()
> >> >> >> #15 0xbfffd624 in ?? ()
> >> >> >> #16 0x00000000 in ?? ()
> >> >> >> (gdb) quit
> >> >> >> A debugging session is active.
> >> >> >
> >> >> > Can you try to install the kdelibs-dbg packages and try to reproduce
> >> >> > the
> >> >> > crash?
> >> >>
> >> >> Just noticed you're on gentoo. You will ahve to recompile kdelibs with
> >> >> the debug use flag.
> >> >>
> >> >> Johannes
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Digikam-users mailing list
> >> >> [hidden email]
> >> >> https://mail.kde.org/mailman/listinfo/digikam-users
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > Digikam-users mailing list
> >> > [hidden email]
> >> > https://mail.kde.org/mailman/listinfo/digikam-users
> >> >
> >> >
> >> _______________________________________________
> >> Digikam-users mailing list
> >> [hidden email]
> >> https://mail.kde.org/mailman/listinfo/digikam-users
> >
> >
> > _______________________________________________
> > Digikam-users mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-users
> >
> >
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Johannes Wienke-3]

Am 27.02.2010 13:05 schrieb Arnd Baecker:

> On Sat, 27 Feb 2010, Gilles Caulier wrote:
>
>> Yes, i want mean KDE 4.4.1 (:=)))
>
> Hmm, does that mean to get a stable digikam
> one has to install the svn version of the upcoming 4.4.1 ?
> I.e., should one follow
> http://techbase.kde.org/Getting_Started/Build/KDE4
> and install kdelibs, kdepimlibs, and of kdebase the runtime part
> (is that all which is needed?).
> Of course, to not screw the system wide KDE installation,
> this would mean to install everything to a seperate place
> and set up all paths accordingly?
>
> I am asking because with my old ubuntu 08.04 it seems
> that I have to go along that route
> (updating is not possible at this point ... ;-( )

Well, the strange thing is that digikam runs completely stable on my
system and I'm not using kdelibs from svn. Got no idea what's going on
there.

Johannes

>> 2010/2/27 Jim Dory <[hidden email]>:
>>> I don't think I understand. Surely you don't mean kde 4.1. That is not very
>>> usable. But you must, as I don't think a 4.4.1 has been released yet. Don't
>>> see it on the mirrors. There is an unstable 4.4.65.. but doubt you meant
>>> that. I looked at the bug and didn't see any discussion about it. I followed
>>> some of the duplicate bug links and found a bit more discussion, but no
>>> solution. I'll admit I'm used to gentoo's bug reports and not these - so
>>> might be missing something.
>>>
>>> If you mean kde 4.1, then I'll have to not use Digikam until this bug gets
>>> resolved one way or another.
>>>
>>> thanks for the help, Jim
>>>
>>>
>>>
>>> On Fri, Feb 26, 2010 at 10:46 PM, Gilles Caulier <[hidden email]>
>>> wrote:
>>>>
>>>> It's KDirWatch bug :
>>>>
>>>> https://bugs.kde.org/show_bug.cgi?id=228562
>>>>
>>>> Update KDE to 4.1
>>>>
>>>> Gilles Caulier
>>>>
>>>> 2010/2/26 Jim Dory <[hidden email]>:
>>>>> Ok, re-compiled kdelibs with USE="debug" but the output hasn't improved
>>>>> much. Let me know if there is another step to improve back trace. I'll
>>>>> post
>>>>> below with a bit more context:
>>>>>
>>>>> digikam(15816)/khtml (caret) DOM::Selection::validate: Selection[
>>>>> Position(
>>>>> 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
>>>>> Position( 0x0 "null" : 0 ) 1 ] 0
>>>>> digikam(15816)/khtml (caret) DOM::Selection::validate:
>>>>> [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0
>>>>> "null"
>>>>> : 0 )
>>>>> digikam(15816)/digikam (core) Digikam::DMetadata::setImageComments:
>>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
>>>>> ==>
>>>>> Comment:  QMap()
>>>>> digikam(15816)/digikam (core) Digikam::DMetadata::setImageRating:
>>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
>>>>> ==>
>>>>> Rating:  0
>>>>> digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords:
>>>>> /mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg  ==>
>>>>> Iptc Keywords:  Carol,nome alaska,hike,water,Dorothy creek
>>>>> digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::save: File Extension:  "jpg"
>>>>> is
>>>>> supported for writing mode
>>>>> digikam(15816)/digikam (core) Digikam::DImg::load:
>>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"  :
>>>>> JPEG file identified
>>>>> digikam(15816)/digikam (core)
>>>>> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1457
>>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
>>>>>
>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>> 0xb62a6beb in QString::operator==(QString const&) const () from
>>>>> /usr/lib/qt4/libQtCore.so.4
>>>>> (gdb) bt
>>>>> #0  0xb62a6beb in QString::operator==(QString const&) const () from
>>>>> /usr/lib/qt4/libQtCore.so.4
>>>>> #1  0xb6b4f717 in ?? () from /usr/lib/libkio.so.5
>>>>> #2  0x09081470 in ?? ()
>>>>> #3  0xbfffd444 in ?? ()
>>>>> #4  0xbfffd444 in ?? ()
>>>>> #5  0xb62aa4a6 in QString::append(QString const&) () from
>>>>> /usr/lib/qt4/libQtCore.so.4
>>>>> #6  0x00000000 in ?? ()
>>>>> (gdb)
>>>>>
>>>>>
>>>>> /jim
>>>>>
>>>>>
>>>>> On Fri, Feb 26, 2010 at 10:54 AM, Johannes Wienke <[hidden email]>
>>>>> wrote:
>>>>>>
>>>>>> Am 26.02.2010 20:52 schrieb Johannes Wienke:
>>>>>>> Am 26.02.2010 20:38 schrieb Jim Dory:
>>>>>>>> digikam(16372)/digikam (core) Digikam::DImg::load:
>>>>>>>>
>>>>>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>>>>>>>>  :
>>>>>>>> JPEG file identified
>>>>>>>> digikam(16372)/digikam (core)
>>>>>>>> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1540
>>>>>>>>
>>>>>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.jpg"
>>>>>>>>
>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>> 0xb62e5beb in QString::operator==(QString const&) const () from
>>>>>>>> /usr/lib/qt4/libQtCore.so.4
>>>>>>>> (gdb) bt
>>>>>>>> #0  0xb62e5beb in QString::operator==(QString const&) const () from
>>>>>>>> /usr/lib/qt4/libQtCore.so.4
>>>>>>>> #1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
>>>>>>>> #2  0x08e4baa0 in ?? ()
>>>>>>>> #3  0xbfffd9f4 in ?? ()
>>>>>>>> #4  0x00000020 in ?? ()
>>>>>>>> #5  0xb62f73ef in QVectorData::allocate(int, int) () from
>>>>>>>> /usr/lib/qt4/libQtCore.so.4
>>>>>>>> #6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
>>>>>>>> #7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
>>>>>>>> #8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
>>>>>>>> #9  0xbfffd93c in ?? ()
>>>>>>>> #10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
>>>>>>>> #11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
>>>>>>>> #12 0x00000001 in ?? ()
>>>>>>>> #13 0x0ab8a06e in ?? ()
>>>>>>>> #14 0x0ab8a0f4 in ?? ()
>>>>>>>> #15 0xbfffd624 in ?? ()
>>>>>>>> #16 0x00000000 in ?? ()
>>>>>>>> (gdb) quit
>>>>>>>> A debugging session is active.
>>>>>>>
>>>>>>> Can you try to install the kdelibs-dbg packages and try to reproduce
>>>>>>> the
>>>>>>> crash?
>>>>>>
>>>>>> Just noticed you're on gentoo. You will ahve to recompile kdelibs with
>>>>>> the debug use flag.
>>>>>>
>>>>>> Johannes

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

For me it crashes all the time, too. No useful backtraces though...

On Saturday 27 February 2010 13:08:29 Johannes Wienke wrote:

> Am 27.02.2010 13:05 schrieb Arnd Baecker:
> > On Sat, 27 Feb 2010, Gilles Caulier wrote:
> >> Yes, i want mean KDE 4.4.1 (:=)))
> >
> > Hmm, does that mean to get a stable digikam
> > one has to install the svn version of the upcoming 4.4.1 ?
> > I.e., should one follow
> > http://techbase.kde.org/Getting_Started/Build/KDE4
> > and install kdelibs, kdepimlibs, and of kdebase the runtime part
> > (is that all which is needed?).
> > Of course, to not screw the system wide KDE installation,
> > this would mean to install everything to a seperate place
> > and set up all paths accordingly?
> >
> > I am asking because with my old ubuntu 08.04 it seems
> > that I have to go along that route
> > (updating is not possible at this point ... ;-( )
>
> Well, the strange thing is that digikam runs completely stable on my
> system and I'm not using kdelibs from svn. Got no idea what's going on
> there.
>
> Johannes
>
> >> 2010/2/27 Jim Dory <[hidden email]>:
> >>> I don't think I understand. Surely you don't mean kde 4.1. That is not
> >>> very usable. But you must, as I don't think a 4.4.1 has been released
> >>> yet. Don't see it on the mirrors. There is an unstable 4.4.65.. but
> >>> doubt you meant that. I looked at the bug and didn't see any
> >>> discussion about it. I followed some of the duplicate bug links and
> >>> found a bit more discussion, but no solution. I'll admit I'm used to
> >>> gentoo's bug reports and not these - so might be missing something.
> >>>
> >>> If you mean kde 4.1, then I'll have to not use Digikam until this bug
> >>> gets resolved one way or another.
> >>>
> >>> thanks for the help, Jim
> >>>
> >>>
> >>>
> >>> On Fri, Feb 26, 2010 at 10:46 PM, Gilles Caulier
> >>> <[hidden email]>
> >>>
> >>> wrote:
> >>>> It's KDirWatch bug :
> >>>>
> >>>> https://bugs.kde.org/show_bug.cgi?id=228562
> >>>>
> >>>> Update KDE to 4.1
> >>>>
> >>>> Gilles Caulier
> >>>>
> >>>> 2010/2/26 Jim Dory <[hidden email]>:
> >>>>> Ok, re-compiled kdelibs with USE="debug" but the output hasn't
> >>>>> improved much. Let me know if there is another step to improve back
> >>>>> trace. I'll post
> >>>>> below with a bit more context:
> >>>>>
> >>>>> digikam(15816)/khtml (caret) DOM::Selection::validate: Selection[
> >>>>> Position(
> >>>>> 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0
> >>>>> ) Position( 0x0 "null" : 0 ) 1 ] 0
> >>>>> digikam(15816)/khtml (caret) DOM::Selection::validate:
> >>>>> [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0
> >>>>> "null"
> >>>>>
> >>>>> : 0 )
> >>>>>
> >>>>> digikam(15816)/digikam (core) Digikam::DMetadata::setImageComments:
> >>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
> >>>>> ==>
> >>>>> Comment:  QMap()
> >>>>> digikam(15816)/digikam (core) Digikam::DMetadata::setImageRating:
> >>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
> >>>>> ==>
> >>>>> Rating:  0
> >>>>> digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords:
> >>>>> /mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg
> >>>>> ==> Iptc Keywords:  Carol,nome alaska,hike,water,Dorothy creek
> >>>>> digikam(15816)/KEXIV2 KExiv2Iface::KExiv2::save: File Extension:
> >>>>> "jpg" is
> >>>>> supported for writing mode
> >>>>> digikam(15816)/digikam (core) Digikam::DImg::load:
> >>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
> >>>>>  : JPEG file identified
> >>>>> digikam(15816)/digikam (core)
> >>>>> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 1457
> >>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000081.jpg"
> >>>>>
> >>>>> Program received signal SIGSEGV, Segmentation fault.
> >>>>> 0xb62a6beb in QString::operator==(QString const&) const () from
> >>>>> /usr/lib/qt4/libQtCore.so.4
> >>>>> (gdb) bt
> >>>>> #0  0xb62a6beb in QString::operator==(QString const&) const () from
> >>>>> /usr/lib/qt4/libQtCore.so.4
> >>>>> #1  0xb6b4f717 in ?? () from /usr/lib/libkio.so.5
> >>>>> #2  0x09081470 in ?? ()
> >>>>> #3  0xbfffd444 in ?? ()
> >>>>> #4  0xbfffd444 in ?? ()
> >>>>> #5  0xb62aa4a6 in QString::append(QString const&) () from
> >>>>> /usr/lib/qt4/libQtCore.so.4
> >>>>> #6  0x00000000 in ?? ()
> >>>>> (gdb)
> >>>>>
> >>>>>
> >>>>> /jim
> >>>>>
> >>>>>
> >>>>> On Fri, Feb 26, 2010 at 10:54 AM, Johannes Wienke
> >>>>> <[hidden email]>
> >>>>>
> >>>>> wrote:
> >>>>>> Am 26.02.2010 20:52 schrieb Johannes Wienke:
> >>>>>>> Am 26.02.2010 20:38 schrieb Jim Dory:
> >>>>>>>> digikam(16372)/digikam (core) Digikam::DImg::load:
> >>>>>>>>
> >>>>>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.j
> >>>>>>>> pg"
> >>>>>>>>
> >>>>>>>> JPEG file identified
> >>>>>>>> digikam(16372)/digikam (core)
> >>>>>>>> Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged:
> >>>>>>>> 1540
> >>>>>>>>
> >>>>>>>> "/mnt/readynas/jim-bak/media/images/jims/2004/200407-08/p1000170.j
> >>>>>>>> pg"
> >>>>>>>>
> >>>>>>>> Program received signal SIGSEGV, Segmentation fault.
> >>>>>>>> 0xb62e5beb in QString::operator==(QString const&) const () from
> >>>>>>>> /usr/lib/qt4/libQtCore.so.4
> >>>>>>>> (gdb) bt
> >>>>>>>> #0  0xb62e5beb in QString::operator==(QString const&) const ()
> >>>>>>>> from /usr/lib/qt4/libQtCore.so.4
> >>>>>>>> #1  0xb6bf07fb in ?? () from /usr/lib/libkio.so.5
> >>>>>>>> #2  0x08e4baa0 in ?? ()
> >>>>>>>> #3  0xbfffd9f4 in ?? ()
> >>>>>>>> #4  0x00000020 in ?? ()
> >>>>>>>> #5  0xb62f73ef in QVectorData::allocate(int, int) () from
> >>>>>>>> /usr/lib/qt4/libQtCore.so.4
> >>>>>>>> #6  0xb6d2d5e0 in ?? () from /usr/lib/libkio.so.5
> >>>>>>>> #7  0xb6d2cc50 in ?? () from /usr/lib/libkio.so.5
> >>>>>>>> #8  0xb6d3c7fd in ?? () from /usr/lib/libkio.so.5
> >>>>>>>> #9  0xbfffd93c in ?? ()
> >>>>>>>> #10 0xb58d4f2d in ?? () from /usr/lib/qt4/libQtGui.so.4
> >>>>>>>> #11 0xb3a413a4 in ?? () from /usr/lib/libdbus-1.so.3
> >>>>>>>> #12 0x00000001 in ?? ()
> >>>>>>>> #13 0x0ab8a06e in ?? ()
> >>>>>>>> #14 0x0ab8a0f4 in ?? ()
> >>>>>>>> #15 0xbfffd624 in ?? ()
> >>>>>>>> #16 0x00000000 in ?? ()
> >>>>>>>> (gdb) quit
> >>>>>>>> A debugging session is active.
> >>>>>>>
> >>>>>>> Can you try to install the kdelibs-dbg packages and try to
> >>>>>>> reproduce the
> >>>>>>> crash?
> >>>>>>
> >>>>>> Just noticed you're on gentoo. You will ahve to recompile kdelibs
> >>>>>> with the debug use flag.
> >>>>>>
> >>>>>> Johannes

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Vlado Plaga]

Am Sat, 27 Feb 2010 13:05:36 +0100 (CET)
schrieb Arnd Baecker <[hidden email]>:

> Hmm, does that mean to get a stable digikam
> one has to install the svn version of the upcoming 4.4.1 ?

As of today, stable digiKam is version 1.1 and that is working well
with KDE 4.3. I'm currently using Debian "unstable" which includes
both (KDE 4.3.4 and digiKam 1.1), and is not that unstable after all
(but still occasionally introduces new problems, of course).

[...]

> I am asking because with my old ubuntu 08.04 it seems
> that I have to go along that route
> (updating is not possible at this point ... ;-( )

Ubuntu 8.04 "Hardy Heron"... getting digiKam 1.x to work there might be
difficult indeed. This release did not even include KDE 4 yet!  Why is
updating not possible? Ubuntu 10.04, the next LTS version, is already
knocking at the door (but I'd wait two or three weeks for "beta 1"
before switching to that):

https://wiki.kubuntu.org/LucidLynx/Alpha3/Kubuntu
https://wiki.ubuntu.com/LucidReleaseSchedule

Regards,
Vlado
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Johannes Wienke-3]

Am 27.02.2010 13:28 schrieb Andi Clemens:
> For me it crashes all the time, too. No useful backtraces though...

Could you try to apply the patch for that bug to you kdelibs and see if
this really solves the issue? I'm somewhat confused by these strange
backtraces.

Johannes


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Arnd Baecker]

On Sat, 27 Feb 2010, Vlado Plaga wrote:

> Am Sat, 27 Feb 2010 13:05:36 +0100 (CET)
> schrieb Arnd Baecker <[hidden email]>:
>
> > Hmm, does that mean to get a stable digikam
> > one has to install the svn version of the upcoming 4.4.1 ?
>
> As of today, stable digiKam is version 1.1 and that is working well
> with KDE 4.3. I'm currently using Debian "unstable" which includes
> both (KDE 4.3.4 and digiKam 1.1), and is not that unstable after all
> (but still occasionally introduces new problems, of course).
>
> [...]
>
> > I am asking because with my old ubuntu 08.04 it seems
> > that I have to go along that route
> > (updating is not possible at this point ... ;-( )
>
> Ubuntu 8.04 "Hardy Heron"... getting digiKam 1.x to work there might be
> difficult indeed. This release did not even include KDE 4 yet!

With
  deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu hardy main
in /etc/apt/sources.list    I get
  ii  kdelibs5   4:4.1.2-0ubuntu1~hardy1~ppa1
and compiling digikam from trunk works
fine (apart from two small issues, where newer KDE features
are used, but they can be hacked away  ... ;-).

> Why is
> updating not possible? Ubuntu 10.04, the next LTS version, is already
> knocking at the door (but I'd wait two or three weeks for "beta 1"
> before switching to that):
>
> https://wiki.kubuntu.org/LucidLynx/Alpha3/Kubuntu
> https://wiki.ubuntu.com/LucidReleaseSchedule

Thanks for the pointers - I am well aware of that, but
I have to stay in sync with the other machines we use at
work and we have several additional (private) packages for
the group. So the upgrade will happen earliest at the end of July ...

Best, Arnd
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jim Dory-2]

Gentoo has a 4.4.65 version available through a kde-testing overlay (repository?) which I'm not sure if that is 4.4.1 development or more likely early development of 4.5. It is usually not that safe to try that until it reaches more like the 4.4.70s-80s. Perhaps I'll watch that and see if it is working for people - if so give it a try. It is a bit of work to set up though - I'm using "sets" which means you don't have to install a monolithic KDE, but just things like kdeutils, kdeadmin, kdegraphics, etc. To switch to the kde-testing overlay I have to muck with my sets files.

/jd

On Sat, Feb 27, 2010 at 3:50 AM, Arnd Baecker <[hidden email]> wrote:

On Sat, 27 Feb 2010, Vlado Plaga wrote:

> Am Sat, 27 Feb 2010 13:05:36 +0100 (CET)
> schrieb Arnd Baecker <[hidden email]>:
>
> > Hmm, does that mean to get a stable digikam
> > one has to install the svn version of the upcoming 4.4.1 ?
>
> As of today, stable digiKam is version 1.1 and that is working well
> with KDE 4.3. I'm currently using Debian "unstable" which includes
> both (KDE 4.3.4 and digiKam 1.1), and is not that unstable after all
> (but still occasionally introduces new problems, of course).
>
> [...]
>
> > I am asking because with my old ubuntu 08.04 it seems
> > that I have to go along that route
> > (updating is not possible at this point ... ;-( )
>
> Ubuntu 8.04 "Hardy Heron"... getting digiKam 1.x to work there might be
> difficult indeed. This release did not even include KDE 4 yet!

With
 deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu hardy main
in /etc/apt/sources.list    I get
 ii  kdelibs5   4:4.1.2-0ubuntu1~hardy1~ppa1
and compiling digikam from trunk works
fine (apart from two small issues, where newer KDE features
are used, but they can be hacked away  ... ;-).

> Why is
> updating not possible? Ubuntu 10.04, the next LTS version, is already
> knocking at the door (but I'd wait two or three weeks for "beta 1"
> before switching to that):
>
> https://wiki.kubuntu.org/LucidLynx/Alpha3/Kubuntu
> https://wiki.ubuntu.com/LucidReleaseSchedule

Thanks for the pointers - I am well aware of that, but
I have to stay in sync with the other machines we use at
work and we have several additional (private) packages for
the group. So the upgrade will happen earliest at the end of July ...

Best, Arnd

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users