digikam does not start

[Martin Gustafsson]

Binary package hint: digikam

First time I start digikam after reboot there is no problem. When I quit digikam and try to start it again, the plash screen shows up but the start progress stops at "loading cameras". The plug-ins never load.
A simple "ps -u my_username" shows two digikam processes. As soon as I kill the first of the, digikam starts.
It seems like digikam does not quit properly and leaves a process behind, which locks other instances.

Reproducable: Yes
Ubuntu Dapper i386 on a via c3 laptop

[Lionel Porcheron (lionel.porcheron)]

It starts well here.

Can you explain your installation (Ubuntu, Kubuntu) ? Did you start with a camera pluged in ?

[Martin Gustafsson (martin-gustafsson)]

My installation is Ubuntu, digikam, digikamimageplugins and
kipi-plugins. I am not sure, but I suspect the problem started after I
installed the kipi-plugins.
It makes no difference if I start with the camera plugged in or not.

Martin

On Wed, 2006-07-05 at 05:40 +0000, Lionel Porcheron wrote:
> It starts well here.
>
> Can you explain your installation (Ubuntu, Kubuntu) ? Did you start
> with a camera pluged in ?
>
> ** Changed in: digikam (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> ** Changed in: digikam (Ubuntu)
> Assignee: (unassigned) => MOTU
>

[Lionel Porcheron (lionel.porcheron)]

I can not reproduce it with an Ubuntu + digikam + digikamimageplugins + kipi-plugins

[Achim Bohnet (allee)]

can't reproduce here too.

can you try

  strace -o digikam.log digikam

and when digikam hangs, check the end of digikam.log
what the last log entries are?

Further try to remove kipi-plugins to check if you suspect
is right that kipi-plugins are the cause of this bug.

Achim

[Tom Albers (tomalbers-deactivatedaccount)]

Do you have your images on a nfs/cifs/sambafs mounted partition?

[Martin Gustafsson (martin-gustafsson)]

Ok, I tried to start with kipi-plugins removed, but no luck.

My images reside in my home directory, which is an ordinary
ext3-partition.

The last lines in the output from strace -o digikam.log digikam look
like:

stat64("/home/martin/Pictures/martin/.evolution/calendar",
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 57399}, NULL) = 0
write(13, ":\0\1\0l\1\2\0000\0/home/martin/Pictures/"..., 58) = 58
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 58497}, NULL) = 0
time([1152209945]) = 1152209945
stat64("/home/martin/Pictures/martin/.evolution/calendar/config",
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 60679}, NULL) = 0
write(13, "A\0\1\0m\1\2\0007\0/home/martin/Pictures/"..., 65) = 65
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 61649}, NULL) = 0
time([1152209945]) = 1152209945
stat64("/home/martin/Pictures/martin/.evolution/calendar/local",
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 64263}, NULL) = 0
write(13, "@\0\1\0n\1\2\0006\0/home/martin/Pictures/"..., 64) = 64
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 67080}, NULL) = 0
time([1152209945]) = 1152209945
stat64("/home/martin/Pictures/martin/.evolution/calendar/local/system",
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 69788}, NULL) = 0
write(13, "G\0\1\0o\1\2\0=\0/home/martin/Pictures/"..., 71) = 71
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 71034}, NULL) = 0
time([1152209945]) = 1152209945
stat64("/home/martin/Pictures/martin/.evolution/calendar/views",
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 73219}, NULL) = 0
write(13, "@\0\1\0p\1\2\0006\0/home/martin/Pictures/"..., 64) = 64
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 74227}, NULL) = 0
time([1152209945]) = 1152209945
stat64("/home/martin/Pictures/martin/.evolution/mail", {st_mode=S_IFDIR|
0755, st_size=4096, ...}) = 0
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 76494}, NULL) = 0
write(13, "6\0\1\0q\1\2\0,\0/home/martin/Pictures/"..., 54) = 54
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 77523}, NULL) = 0
time([1152209945]) = 1152209945
stat64("/home/martin/Pictures/martin/.evolution/mail/config",
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 79914}, NULL) = 0
write(13, "=\0\1\0r\1\2\0003\0/home/martin/Pictures/"..., 61) = 61
select(14, [13], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1152209945, 82573}, NULL) = 0
time([1152209945]) = 1152209945
sta...

[Tom Albers (tomalbers-deactivatedaccount)]

Can you try with an empty pictures folder and with some folders of your current pictures folder and maybe see if the .evolution folder is the cause of this?

[Martin Gustafsson (martin-gustafsson)]

Solved. I removed everything in my Picture folder and now digikam
starts. Maybe the database or something else in the folder was corrupt.

Martin

On Thu, 2006-07-06 at 18:58 +0000, Tom Albers wrote:
> Can you try with an empty pictures folder and with some folders of your
> current pictures folder and maybe see if the .evolution folder is the
> cause of this?
>

[Tom Albers (tomalbers-deactivatedaccount)]

Could you invest a couple of minutes and place some data back and find out what is the root cause? If you are bit by it, others will too, maybe we can fix it in digiKam.

[Martin Gustafsson (martin-gustafsson)]

I managed to reproduce the bug again. If I from Digikam select to import
a folder with pictures, select nothing and click "ok" (my home folder is
imported) funny things start to happen. Does digikam create a copy of
the imported folder inside "Picture"? It seems like an infinite
recursive loop is started.

Martin

On Thu, 2006-07-06 at 20:21 +0000, Tom Albers wrote:
> Could you invest a couple of minutes and place some data back and find
> out what is the root cause? If you are bit by it, others will too, maybe
> we can fix it in digiKam.
>

[Martin Gustafsson (martin-gustafsson)]

Clarification.
I canceled the import-procedure after a while since there was too much
data. When I tried to start digikam next time, digikam hung.

Martin

[Sebastian Rode (sebastian-ro-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[Sebastian Rode (sebastian-ro-deactivatedaccount)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!