[digikam] [Bug 337737] New: Settings and installation windows freeze when valid mariadb/mysql db connection is available

[meku-2]

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

meku <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |CONFIRMED

--- Comment #18 from meku <[hidden email]> ---
*** This bug has been confirmed by popular vote. ***

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Leonardo Montecchi]

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

Leonardo Montecchi <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #19 from Leonardo Montecchi <[hidden email]> ---
Yes, I can confirm this too in Debian sid, Digikam 4.3.0. I also tried to stop
the MySQL daemon, but the configuration page still freezes even if the database
is not reachable.

I must say I am reliefed from finding this bug report, I thought my settings
were messed in some way....

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[otherland]

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

otherland <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #20 from otherland <[hidden email]> ---
I can also confirm this bug:
Fedora 20
digikam-libs-4.3.0-2.fc20.x86_64
digikam-4.3.0-2.fc20.x86_64
mariadb-devel-5.5.39-1.fc20.x86_64
mariadb-embedded-5.5.39-1.fc20.x86_64
mariadb-5.5.39-1.fc20.x86_64
mariadb-server-5.5.39-1.fc20.x86_64
mariadb-libs-5.5.39-1.fc20.x86_64

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

Bernie <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #21 from Bernie <[hidden email]> ---
Following config also suffers from this bug:

Linux Mint 17 / KDE
digikam 4:4.3.0-trusty~ppa1
digikam-data 4:4.3.0-trusty~ppa1
kipi-plugins-common 4:4.3.0-trusty~ppa1
libkdcraw23 4:4.13.0-0ubuntu1
libkipi11 4:4.13.0-0ubuntu1
libkipi-data 4:4.13.0-0ubuntu1
kipi-plugins 4:4.3.0-trusty~ppa1

with the wokring MySQL database running on a QNAP NAS.

When going to settings menu --> database migration, I experience exact the same
behaviour, eg digikam eating 100% cpu after a few seconds, even when the DB
connection is not available (and digikam correctly presents a error message
during startup).

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Tom Wilczek]

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

Tom Wilczek <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #22 from Tom Wilczek <[hidden email]> ---
Created attachment 89156
  --> https://bugs.kde.org/attachment.cgi?id=89156&action=edit
quick'n'dirty hack to prevent freeze when using mysql db backend

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Tom Wilczek]

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

--- Comment #23 from Tom Wilczek <[hidden email]> ---
The reported freezing seems to be related to the delayed checking of the
database file path which is unused for external DB server connections. Somehow
that code runs amok and causes 100% load on one cpu core - I didn't have the
time to investigate the real reason behind that behavior. In the attached patch
I've just moved both connect() calls of that file path input field to a "later"
code position and made it conditional based on type of DB backend.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|MYSQL : settings and        |MYSQL : settings and
                   |installation windows freeze |installation windows freeze
                   |when valid mariadb/mysql db |when valid mariadb/mysql db
                   |connection is available     |connection is available
                   |                            |[patch]

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

[hidden email] <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #24 from [hidden email] <[hidden email]> ---
Sorry but how to you add such patch ?  Really missing MYSQL with Digikam.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Tom Wilczek]

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

--- Comment #25 from Tom Wilczek <[hidden email]> ---
(In reply to [hidden email] from comment #24)
> Sorry but how to you add such patch ?  Really missing MYSQL with Digikam.

...uuuhm - I just hope we talk about the same thing here: that patch is only
"useful" if you have the digikam source code at hand and know how to (re-)build
it from scratch. My assumption is, that if you know how to compile the source
tree, you should also know how to apply patch files to your working copy -
sorry, but it's not a "end-user-friendly" solution to the problem ;)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #26 from [hidden email] <[hidden email]> ---
Tom, you guessed me right.  I'm not building Digikam from source and was hoping
this would be easier to apply.  Hope they incorporate your patch to rpms or I
might just learn how to build from source :-)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
   Version Fixed In|                            |4.5.0
         Resolution|---                         |FIXED
      Latest Commit|                            |http://commits.kde.org/digi
                   |                            |kam/f0400ec7e518e753e0c4cca
                   |                            |b4eb2b8b022f91767

--- Comment #27 from Gilles Caulier <[hidden email]> ---
Git commit f0400ec7e518e753e0c4ccab4eb2b8b022f91767 by Gilles Caulier.
Committed on 28/10/2014 at 14:58.
Pushed by cgilles into branch 'master'.

apply patch #89156
FIXED-IN: 4.5.0

M  +2    -1    NEWS
M  +19   -16   libs/widgets/common/databasewidget.cpp

http://commits.kde.org/digikam/f0400ec7e518e753e0c4ccab4eb2b8b022f91767

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Leonardo Montecchi]

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

--- Comment #28 from Leonardo Montecchi <[hidden email]> ---
Thank you for fixing this bug. I will try the patch as soon as possible :)

@fsalvert: if you are using some pacakge-based distribution, you may try to
look at guides for creating patched packages. Something exists for debian, for
example. It may be easier than rebuilding all from source, but still some
advanced knowledge and skills are required.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Jean-Pierre Vandermolen]

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

Jean-Pierre Vandermolen <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #29 from Jean-Pierre Vandermolen <[hidden email]> ---
Thank you Gillles for you patch.
I'am using fedora 20, 64 bits version.
I have downloaded 4.4.0 digikam version from fedora updates repository.
I have only replaced databasewidget.cpp by new version and recreated  a new rpm
with 'rpmbuild -ba'
I can now use Digikam  4.4.0 configuration to add a new collection.
Before , after each "yum update" , I was replacing current digikam version with
3.5.0 version from fedora releases repository.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #30 from [hidden email] <[hidden email]> ---
Jean-Pierre, can you post your final rpm ?  Will try it out on openSuse.
Thanks

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Jean-Pierre Vandermolen]

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

--- Comment #31 from Jean-Pierre Vandermolen <[hidden email]> ---
Created attachment 89378
  --> https://bugs.kde.org/attachment.cgi?id=89378&action=edit
digikam-libs

It's named 4.4.2-9 to be sure that   next  version  from fedora without that
patch will not remove my version  but, in fact it is the 4.4.0 with Gilles
caulier patch.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #32 from [hidden email] <[hidden email]> ---
Thanks...openSuse does not seem to use this package digikam-libs normally.
Will try it anyways and see if it works :-)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Jean-Pierre Vandermolen]

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

--- Comment #33 from Jean-Pierre Vandermolen <[hidden email]> ---
I do'nt have checked where the patch goes. but you need 2 packages in fedora:
digikam and digikam-libs , but the package digikam is too big to be posted
directly here.

I can provide access to my ftp server, if you want to have acces to anything
generated.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #34 from [hidden email] <[hidden email]> ---
Hi,

Just to post out there that SQL is fixed in openSuse with Digikam version
4.4.0-28.1.  Great !

Thanks

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Leonardo Montecchi]

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

--- Comment #35 from Leonardo Montecchi <[hidden email]> ---
I can confirm that the patch works on digikam 4.4. I tried it on the current
Debian sid version, which is 4.4.0-1.

I created patched debian packages for me, but maybe they can be useful to
someone else (only amd64 architecture):
https://www.dropbox.com/sh/xo6vshks7ehtvzi/AAANiZxu2TtK8fz3_UyZyp_wa?dl=0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Mysql

--
You are receiving this mail because:
You are the assignee for the bug.