alternative for digikam

[sunrat]

What causes the freeze? I haven't had any problems but I don't use it intensively.
Not upgraded since last week so I still have 3.1.0-4+siduction1 . Maybe I should hold it?

[Lanzi]

Devil: I agree.
As a photographer its quite a lame program.
- no possibility to see Pics on second screen
- no real FUll-Screen
- no configuration to open pics in gimp or rawtherapee with keys
- slow, especially opening!
- no possibility to enter an path

and so on.
its maybe good for families to watch 100 photos from the last holidays, nothing more!

[Santa]

Digikam 3.4.0-90r3 just freezes repoducably here.

If you have time, could you explain the steps to get the freeze?

My patience with this app is slowly coming to an end...

greetz
devil

[spacepenguin]

Digikam 3.4.0-90 here gives me only

Code Select Expand

susan@panther:~$ digikam
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
and a blank window until I kill it.

[mylo]

But it doesn't:

~$ shotwell
**
ERROR:src/db/DatabaseTable.c:1277:database_table_add_column: assertion failed: (res == Sqlite.OK)
Abgebrochen

...
Hi michaa7,

here it works:

Shell feedback:

Code Select Expand


shotwell
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
libusbx: debug [libusb_get_device_list]
libusbx: debug [discovered_devs_append] need to increase capacity
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_config_descriptor] index 0
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_config_descriptor] index 0
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_config_descriptor] index 0
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_config_descriptor] index 0
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_config_descriptor] index 0
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_config_descriptor] index 0
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_config_descriptor] index 0
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_config_descriptor] index 0
libusbx: debug [libusb_get_device_descriptor]
libusbx: debug [libusb_get_config_descriptor] index 0
libusbx: debug [libusb_exit]
libusbx: debug [libusb_exit] destroying default context


After that the program opens. If you want me to check settings or other things for comparing, let me know...

[devil]

Santa,

all I have to do is start it and it freezes.
I guess, deleting the db and/or config would fix that, digikam just causes too much trouble for my liking lately. And I am patient, I went with KDE4 from 4.1 and with amarok since 2.0.x

greetz
devil

[pekkal]

My Digikam was very slow. It appears disabling Kipi export plugins fixed the issue. I disabled all exports & restarted Digikam - I do not know which export caused the issues. See
http://forum.kde.org/viewtopic.php?f=255&t=112131