[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2022-01-13 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Version Fixed In||7.5.0
 Resolution|--- |FIXED

--- Comment #17 from caulier.gil...@gmail.com ---
No feedback. not reproducible with 7.5.0. Closed

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2021-12-15 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #16 from caulier.gil...@gmail.com ---
Axel,

Stable digiKam 7.4.0 is published. Please check if problem is reproducible.

https://www.digikam.org/download/

Thanks in advance

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2021-05-09 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #15 from caulier.gil...@gmail.com ---
Axel,

Please give us a feedback using current digiKam 7.3.0 pre-release appimage
bundle available here :

https://files.kde.org/digikam/

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2021-03-29 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #14 from caulier.gil...@gmail.com ---
digiKam 7.2.0 official release is published with more than 360 files closed
from bugzilla:

https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/

Can you reproduce the dysfunction with this version ?

Thanks in advance for your feedback

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2020-07-14 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #13 from caulier.gil...@gmail.com ---
Hi,

Can you check if this problem still exist with last weekly bundle build of
digiKam 7.0.0 available here:

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2019-07-13 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|RESOLVED|REPORTED

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2019-06-03 Thread Axel Schmidt 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #12 from Axel Schmidt  ---
Log files for the error

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2019-06-03 Thread Axel Schmidt 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #11 from Axel Schmidt  ---
Gilles,

i tried both version for linux now under (K)Ubuntu 18.04:
digikam-6.2.0-git-20190503T152230-qtwebengine-x86-64.appimage
digikam-6.2.0-git-20190503T152230-qtwebengine-x86-64.appimage

both doesn't work. Both couldn't connect to mysql and than stops or exiting
with error. The original digikam 5.6.0 from system start, can connect to mysql
and work as expected and now under (K)Ubuntu  18.04 the error is gone...

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2019-06-03 Thread Maik Qualmann 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #10 from Maik Qualmann  ---
If you have not been on a digiKam-6.x.x before, make a backup of your database,
changes will be made on the database schema.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2019-06-03 Thread Maik Qualmann 
https://bugs.kde.org/show_bug.cgi?id=389355

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #9 from Maik Qualmann  ---
AppImage does not work with "localhost" as server address. Use 127.0.0.1 to
test the AppImage.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2019-06-03 Thread Axel Schmidt 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #8 from Axel Schmidt  ---
Created attachment 120513
  --> https://bugs.kde.org/attachment.cgi?id=120513&action=edit
ErrorLog digikam-6.2.0-git-20190503T152230-qtwebengine-x86-64.appimage.log

start with error can't connect to mysql and then exit with error

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2019-06-03 Thread Axel Schmidt 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #7 from Axel Schmidt  ---
Created attachment 120512
  --> https://bugs.kde.org/attachment.cgi?id=120512&action=edit
Errorlog digikam-6.2.0-git-20190529T102951-qtwebkit-x86-64.appimage

Start with error can't connect to mysql, but mysql is working and than hang on
icc profile on start screen with no more response. klick on startscreen than it
disappear but no program window showed. digikam hang in tasklist without any
cpu time...

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2019-06-02 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #6 from caulier.gil...@gmail.com ---
Alex please review my comment #4, and give us a fresh feedback using AppImage
bundle that we provide. 

Without any feedback, i will close this file.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2019-03-09 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #5 from caulier.gil...@gmail.com ---
Axel,

Any feedback from this file ?

Thanks in advance

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2018-08-11 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #4 from caulier.gil...@gmail.com ---
Axel,

I don't know how to install Dk as well with your Linux box. It's too much
specific, or you can compile and install yourself the code, but it's a little
bit complicated.

There is a simple way to test with current code from your side : use the Linux
AppImage bundle that we provide. The current development one is here :

https://files.kde.org/digikam/

There is nothing to install. Download the bunble, set it as executable and run
it. The bundle do not install anything on your system and can be used in
parallel with the official digiKam version already installed on your system.


Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2018-05-22 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|general |Metadata-Maintenance

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2018-03-15 Thread Axel Schmidt 
https://bugs.kde.org/show_bug.cgi?id=389355

--- Comment #3 from Axel Schmidt  ---
Sorry i didn't saw your first answer!

Comment #1: I'm not possible to test this problem, because i get before a
exception, if i go into a album qand than stops the programm:

gdb digikam
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...(no debugging symbols found)...done.
(gdb) catch throw
Haltepunkt 1 (throw)
(gdb) run
Starting program: /usr/bin/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffbffbd700 (LWP 24459)]
[New Thread 0x7fffb7b68700 (LWP 24460)]
[New Thread 0x7fffb6957700 (LWP 24461)]
[New Thread 0x7fffb6156700 (LWP 24462)]
[Thread 0x7fffb6156700 (LWP 24462) exited]
[New Thread 0x7fffb6156700 (LWP 24463)]
[New Thread 0x7fffa520f700 (LWP 24465)]
[New Thread 0x7fff647c4700 (LWP 24466)]
[New Thread 0x7fff63925700 (LWP 24467)]
[New Thread 0x7fff63124700 (LWP 24468)]
[New Thread 0x7fff62923700 (LWP 24469)]
[New Thread 0x7fff62122700 (LWP 24470)]
QFSFileEngine::open: No file name specified
[New Thread 0x7fff60ebb700 (LWP 24471)]
[New Thread 0x7fff4bfff700 (LWP 24472)]
[New Thread 0x7fff4b7fe700 (LWP 24473)]
[New Thread 0x7fff4affd700 (LWP 24474)]
[New Thread 0x7fff4a7fc700 (LWP 24475)]
[New Thread 0x7fff49ffb700 (LWP 24476)]
[New Thread 0x7fff497fa700 (LWP 24477)]
[New Thread 0x7fff48ff9700 (LWP 24478)]
[New Thread 0x7fff27fff700 (LWP 24479)]
[New Thread 0x7fff1f7fe700 (LWP 24480)]
[New Thread 0x7fff277fe700 (LWP 24481)]
[New Thread 0x7fff26ffd700 (LWP 24482)]
[New Thread 0x7fff267fc700 (LWP 24483)]
[New Thread 0x7fff25ffb700 (LWP 24484)]
[New Thread 0x7fff257fa700 (LWP 24485)]
[New Thread 0x7fff24ff9700 (LWP 24486)]
[New Thread 0x7fff1700 (LWP 24487)]
[New Thread 0x7fff1effd700 (LWP 24488)]
[New Thread 0x7fff1e7fc700 (LWP 24489)]
[New Thread 0x7fff1dffb700 (LWP 24490)]
[New Thread 0x7fff1d7fa700 (LWP 24491)]
[New Thread 0x7fff1cff9700 (LWP 24492)]
[New Thread 0x7ffee7fff700 (LWP 24493)]
[New Thread 0x7ffee77fe700 (LWP 24494)]
[New Thread 0x7ffee6ffd700 (LWP 24495)]
[New Thread 0x7ffee67fc700 (LWP 24496)]
QFSFileEngine::open: No file name specified
[New Thread 0x7ffee5ffb700 (LWP 24497)]
[New Thread 0x7ffee57fa700 (LWP 24499)]
[New Thread 0x7ffee4ff9700 (LWP 24500)]
[New Thread 0x7ffee47f8700 (LWP 24502)]
[Thread 0x7ffee4ff9700 (LWP 24500) exited]
[New Thread 0x7ffee4ff9700 (LWP 24503)]
[Thread 0x7ffee57fa700 (LWP 24499) exited]
[Thread 0x7ffee5ffb700 (LWP 24497) exited]
[Thread 0x7ffee47f8700 (LWP 24502) exited]
[Thread 0x7ffee4ff9700 (LWP 24503) exited]
[New Thread 0x7ffee4ff9700 (LWP 24504)]
[Thread 0x7ffee4ff9700 (LWP 24504) exited]
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
[New Thread 0x7ffee4ff9700 (LWP 24505)]
[Thread 0x7ffee4ff9700 (LWP 24505) exited]
[New Thread 0x7ffee4ff9700 (LWP 24506)]
[New Thread 0x7ffee4ff9700 (LWP 24507)]
[Thread 0x7ffee4ff9700 (LWP 24506) exited]
[New Thread 0x7ffee47f8700 (LWP 24508)]
[New Thread 0x7ffee5ffb700 (LWP 24509)]
[New Thread 0x7ffee57fa700 (LWP 24510)]
[New Thread 0x7ffec2c8e700 (LWP 24511)]
[New Thread 0x7ffec248d700 (LWP 24512)]
[New Thread 0x7ffec1c8c700 (LWP 24513)]
[New Thread 0x7ffec148b700 (LWP 24514)]
[Thread 0x7ffee4ff9700 (LWP 24507) exited]
[Thread 0x7ffec248d700 (LWP 24512) exited]
[Thread 0x7ffec2c8e700 (LWP 24511) exited]
[Thread 0x7ffec1c8c700 (LWP 24513) exited]
[Thread 0x7ffee57fa700 (LWP 24510) exited]
[Thread 0x7ffee5ffb700 (LWP 24509) exited]
[Thread 0x7ffee47f8700 (LWP 24508) exited]
[New Thread 0x7ffee47f8700 (LWP 24554)]
[Thread 0x7ffee47f8700 (LWP 24554) exited]
[Thread 0x7ffee7fff700 (LWP 24493) exited]
[Thread 0x7ffee77fe700 (LWP 24494) exited]
[Thread 0x7ffee67fc700 (LWP 24496) exited]
[Thread 0x7ffee6ffd700 (LWP 24495) exited]
[Thread 0x7ffec148b700 (LWP 24514) exited]
[New Thread 0x7ffec148b700 (LWP 24561)]
[New Thread 0x7ffee67fc700 (LWP 24562)]
[Thread 0x7ffec148b700 (LWP 24561) exited]
[New Thread 0x7ffec148b700 (LWP 24571)]
[Thread 0x7ffec148b700 (LWP 24571) exited]
[New Thread 0x7ffec148b700 (LWP 24583)]
[Thread 0x7ffec148b700 (LWP 24583) exited]
[New Thread 0x7ffec148b700 (LWP 24590)]
[Thread 0x7ffec148b700 (LWP 24590) exited]
[New Thread 0x7ffec148b700 (LWP 24597)]
[Thread 0x7ffec148b700 (LWP 2459

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2018-03-14 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from caulier.gil...@gmail.com ---
Any feedback here, following my tips from comment #1 ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album

2018-01-23 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=389355

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
1/ Your baktrace do not provide any debug symbols. Run digiKam in GDB to
provide more information to hack. See this page for details :

https://www.digikam.org/contribute/

2/ Try to use last 5.8.0 release (Linux AppImage) to seeif bug is reproducible.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.