Weird digikam_KDE3 bug

Hi,

I just discovered a weird bug with the KDE3 version of digiKam.
I have two different databases (album root paths) and was able to switch
between perfectly in the past. But now digiKam hangs when switching.
The splashscreen shows "Updating items without a date" and that's it.

The weird part comes now: I can't kill it. All kioslaves refuse to die,
digiKam refuses to kill, even as root. I need to restart the whole system!

Switching to INIT1 doesn't help either. When shutting down, INIT sends KILL to
all remaining processes, even this doesn't work. It hangs!! At this moment I
turn off power because most of the data should be written from RAM to disk.

What is that? I've never seen that you are not able to kill a process, at
least root always was able to do that.

Unfortunately there are no backtraces, debug messages etc that would help.

Can anyone confirm this?
If so, this is a serious probelm!!

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

What is also very bad in this case:
When shutting down, the kernel is not able to umount /home, / etc, because
digiKam is still running. This leads to a bad filesystem on reboot with a lot
of errors that luckily could be fixed all the time.

It is no general problem, my system runs fine, it always appears when I switch
the collection in digiKam_KDE3.

Andi

On Saturday 13 December 2008 11:32:55 Andi Clemens wrote:

> Hi,
>
> I just discovered a weird bug with the KDE3 version of digiKam.
> I have two different databases (album root paths) and was able to switch
> between perfectly in the past. But now digiKam hangs when switching.
> The splashscreen shows "Updating items without a date" and that's it.
>
> The weird part comes now: I can't kill it. All kioslaves refuse to die,
> digiKam refuses to kill, even as root. I need to restart the whole system!
>
> Switching to INIT1 doesn't help either. When shutting down, INIT sends KILL
> to all remaining processes, even this doesn't work. It hangs!! At this
> moment I turn off power because most of the data should be written from RAM
> to disk.
>
> What is that? I've never seen that you are not able to kill a process, at
> least root always was able to do that.
>
> Unfortunately there are no backtraces, debug messages etc that would help.
>
> Can anyone confirm this?
> If so, this is a serious probelm!!
>
> Andi
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

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

Can nobody confirm this?
I just tested it again and the computer gets stuck again, I can not confirm
this with 0.9.4.
Please test this, some people use more than one collection in digiKam 0.9.x
and they might run in serious problems. It makes your computer absolutely
instable and I don't think this is good :-)

To reproduce:
1. make a backup, just for security reasons
2. get / compile latest digiKam for KDE3
3. create a new folder somewhere in your system (not under the current album
library path) and copy some images to it
4. start digiKam and enter this folder as your new album library path.
5. After digiKam has finished importing, close it.
6. restart digiKam, it gets stuck while displaying "Updating items without a
date" in the splashscreen.
7. restart your computer (because killing the slaves or digiKam doesn't work).

If only one other person can confirm this, we need to fix this immediately,
this is a serious problem and I never seen such a behavior from a normal
desktop application (at least killing the process always worked for me, but
in this case it isn't).
We can't deliver a digiKam stable version that acts in this way.

Andi

On Saturday 13 December 2008 11:38:12 Andi Clemens wrote:

> What is also very bad in this case:
> When shutting down, the kernel is not able to umount /home, / etc, because
> digiKam is still running. This leads to a bad filesystem on reboot with a
> lot of errors that luckily could be fixed all the time.
>
> It is no general problem, my system runs fine, it always appears when I
> switch the collection in digiKam_KDE3.
>
> Andi
>
> On Saturday 13 December 2008 11:32:55 Andi Clemens wrote:
> > Hi,
> >
> > I just discovered a weird bug with the KDE3 version of digiKam.
> > I have two different databases (album root paths) and was able to switch
> > between perfectly in the past. But now digiKam hangs when switching.
> > The splashscreen shows "Updating items without a date" and that's it.
> >
> > The weird part comes now: I can't kill it. All kioslaves refuse to die,
> > digiKam refuses to kill, even as root. I need to restart the whole
> > system!
> >
> > Switching to INIT1 doesn't help either. When shutting down, INIT sends
> > KILL to all remaining processes, even this doesn't work. It hangs!! At
> > this moment I turn off power because most of the data should be written
> > from RAM to disk.
> >
> > What is that? I've never seen that you are not able to kill a process, at
> > least root always was able to do that.
> >
> > Unfortunately there are no backtraces, debug messages etc that would
> > help.
> >
> > Can anyone confirm this?
> > If so, this is a serious probelm!!
> >
> > Andi
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-devel
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

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

I tested this on a fresh virtual machine, and it also crashes this machine.
Can someone please please please test this issue, or at least comment on this?
We can not ship digiKam in this state, you are not able to work with your
system after switching to a new database.

Andi

On Wednesday 17 December 2008 11:05:22 Andi Clemens wrote:

> Can nobody confirm this?
> I just tested it again and the computer gets stuck again, I can not confirm
> this with 0.9.4.
> Please test this, some people use more than one collection in digiKam 0.9.x
> and they might run in serious problems. It makes your computer absolutely
> instable and I don't think this is good :-)
>
> To reproduce:
> 1. make a backup, just for security reasons
> 2. get / compile latest digiKam for KDE3
> 3. create a new folder somewhere in your system (not under the current
> album library path) and copy some images to it
> 4. start digiKam and enter this folder as your new album library path.
> 5. After digiKam has finished importing, close it.
> 6. restart digiKam, it gets stuck while displaying "Updating items without
> a date" in the splashscreen.
> 7. restart your computer (because killing the slaves or digiKam doesn't
> work).
>
> If only one other person can confirm this, we need to fix this immediately,
> this is a serious problem and I never seen such a behavior from a normal
> desktop application (at least killing the process always worked for me, but
> in this case it isn't).
> We can't deliver a digiKam stable version that acts in this way.
>
> Andi
>
> On Saturday 13 December 2008 11:38:12 Andi Clemens wrote:
> > What is also very bad in this case:
> > When shutting down, the kernel is not able to umount /home, / etc,
> > because digiKam is still running. This leads to a bad filesystem on
> > reboot with a lot of errors that luckily could be fixed all the time.
> >
> > It is no general problem, my system runs fine, it always appears when I
> > switch the collection in digiKam_KDE3.
> >
> > Andi
> >
> > On Saturday 13 December 2008 11:32:55 Andi Clemens wrote:
> > > Hi,
> > >
> > > I just discovered a weird bug with the KDE3 version of digiKam.
> > > I have two different databases (album root paths) and was able to
> > > switch between perfectly in the past. But now digiKam hangs when
> > > switching. The splashscreen shows "Updating items without a date" and
> > > that's it.
> > >
> > > The weird part comes now: I can't kill it. All kioslaves refuse to die,
> > > digiKam refuses to kill, even as root. I need to restart the whole
> > > system!
> > >
> > > Switching to INIT1 doesn't help either. When shutting down, INIT sends
> > > KILL to all remaining processes, even this doesn't work. It hangs!! At
> > > this moment I turn off power because most of the data should be written
> > > from RAM to disk.
> > >
> > > What is that? I've never seen that you are not able to kill a process,
> > > at least root always was able to do that.
> > >
> > > Unfortunately there are no backtraces, debug messages etc that would
> > > help.
> > >
> > > Can anyone confirm this?
> > > If so, this is a serious probelm!!
> > >
> > > Andi
> > > _______________________________________________
> > > Digikam-devel mailing list
> > > [hidden email]
> > > https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-devel
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

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

Since nobody seems to read this, I will create a B.K.O entry now...

On Friday 30 January 2009 18:09:52 Andi Clemens wrote:

> I tested this on a fresh virtual machine, and it also crashes this machine.
> Can someone please please please test this issue, or at least comment on
> this? We can not ship digiKam in this state, you are not able to work with
> your system after switching to a new database.
>
> Andi
>
> On Wednesday 17 December 2008 11:05:22 Andi Clemens wrote:
> > Can nobody confirm this?
> > I just tested it again and the computer gets stuck again, I can not
> > confirm this with 0.9.4.
> > Please test this, some people use more than one collection in digiKam
> > 0.9.x and they might run in serious problems. It makes your computer
> > absolutely instable and I don't think this is good :-)
> >
> > To reproduce:
> > 1. make a backup, just for security reasons
> > 2. get / compile latest digiKam for KDE3
> > 3. create a new folder somewhere in your system (not under the current
> > album library path) and copy some images to it
> > 4. start digiKam and enter this folder as your new album library path.
> > 5. After digiKam has finished importing, close it.
> > 6. restart digiKam, it gets stuck while displaying "Updating items
> > without a date" in the splashscreen.
> > 7. restart your computer (because killing the slaves or digiKam doesn't
> > work).
> >
> > If only one other person can confirm this, we need to fix this
> > immediately, this is a serious problem and I never seen such a behavior
> > from a normal desktop application (at least killing the process always
> > worked for me, but in this case it isn't).
> > We can't deliver a digiKam stable version that acts in this way.
> >
> > Andi
> >
> > On Saturday 13 December 2008 11:38:12 Andi Clemens wrote:
> > > What is also very bad in this case:
> > > When shutting down, the kernel is not able to umount /home, / etc,
> > > because digiKam is still running. This leads to a bad filesystem on
> > > reboot with a lot of errors that luckily could be fixed all the time.
> > >
> > > It is no general problem, my system runs fine, it always appears when I
> > > switch the collection in digiKam_KDE3.
> > >
> > > Andi
> > >
> > > On Saturday 13 December 2008 11:32:55 Andi Clemens wrote:
> > > > Hi,
> > > >
> > > > I just discovered a weird bug with the KDE3 version of digiKam.
> > > > I have two different databases (album root paths) and was able to
> > > > switch between perfectly in the past. But now digiKam hangs when
> > > > switching. The splashscreen shows "Updating items without a date" and
> > > > that's it.
> > > >
> > > > The weird part comes now: I can't kill it. All kioslaves refuse to
> > > > die, digiKam refuses to kill, even as root. I need to restart the
> > > > whole system!
> > > >
> > > > Switching to INIT1 doesn't help either. When shutting down, INIT
> > > > sends KILL to all remaining processes, even this doesn't work. It
> > > > hangs!! At this moment I turn off power because most of the data
> > > > should be written from RAM to disk.
> > > >
> > > > What is that? I've never seen that you are not able to kill a
> > > > process, at least root always was able to do that.
> > > >
> > > > Unfortunately there are no backtraces, debug messages etc that would
> > > > help.
> > > >
> > > > Can anyone confirm this?
> > > > If so, this is a serious probelm!!
> > > >
> > > > Andi
> > > > _______________________________________________
> > > > Digikam-devel mailing list
> > > > [hidden email]
> > > > https://mail.kde.org/mailman/listinfo/digikam-devel
> > >
> > > _______________________________________________
> > > Digikam-devel mailing list
> > > [hidden email]
> > > https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-devel
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

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

[Gilles Caulier-4]

yes, it's better (:=))).

Gilles

2009/2/10 Andi Clemens <[hidden email]>

Since nobody seems to read this, I will create a B.K.O entry now...

On Friday 30 January 2009 18:09:52 Andi Clemens wrote:
> I tested this on a fresh virtual machine, and it also crashes this machine.
> Can someone please please please test this issue, or at least comment on
> this? We can not ship digiKam in this state, you are not able to work with
> your system after switching to a new database.
>
> Andi
>
> On Wednesday 17 December 2008 11:05:22 Andi Clemens wrote:
> > Can nobody confirm this?
> > I just tested it again and the computer gets stuck again, I can not
> > confirm this with 0.9.4.
> > Please test this, some people use more than one collection in digiKam
> > 0.9.x and they might run in serious problems. It makes your computer
> > absolutely instable and I don't think this is good :-)
> >
> > To reproduce:
> > 1. make a backup, just for security reasons
> > 2. get / compile latest digiKam for KDE3
> > 3. create a new folder somewhere in your system (not under the current
> > album library path) and copy some images to it
> > 4. start digiKam and enter this folder as your new album library path.
> > 5. After digiKam has finished importing, close it.
> > 6. restart digiKam, it gets stuck while displaying "Updating items
> > without a date" in the splashscreen.
> > 7. restart your computer (because killing the slaves or digiKam doesn't
> > work).
> >
> > If only one other person can confirm this, we need to fix this
> > immediately, this is a serious problem and I never seen such a behavior
> > from a normal desktop application (at least killing the process always
> > worked for me, but in this case it isn't).
> > We can't deliver a digiKam stable version that acts in this way.
> >
> > Andi
> >
> > On Saturday 13 December 2008 11:38:12 Andi Clemens wrote:
> > > What is also very bad in this case:
> > > When shutting down, the kernel is not able to umount /home, / etc,
> > > because digiKam is still running. This leads to a bad filesystem on
> > > reboot with a lot of errors that luckily could be fixed all the time.
> > >
> > > It is no general problem, my system runs fine, it always appears when I
> > > switch the collection in digiKam_KDE3.
> > >
> > > Andi
> > >
> > > On Saturday 13 December 2008 11:32:55 Andi Clemens wrote:
> > > > Hi,
> > > >
> > > > I just discovered a weird bug with the KDE3 version of digiKam.
> > > > I have two different databases (album root paths) and was able to
> > > > switch between perfectly in the past. But now digiKam hangs when
> > > > switching. The splashscreen shows "Updating items without a date" and
> > > > that's it.
> > > >
> > > > The weird part comes now: I can't kill it. All kioslaves refuse to
> > > > die, digiKam refuses to kill, even as root. I need to restart the
> > > > whole system!
> > > >
> > > > Switching to INIT1 doesn't help either. When shutting down, INIT
> > > > sends KILL to all remaining processes, even this doesn't work. It
> > > > hangs!! At this moment I turn off power because most of the data
> > > > should be written from RAM to disk.
> > > >
> > > > What is that? I've never seen that you are not able to kill a
> > > > process, at least root always was able to do that.
> > > >
> > > > Unfortunately there are no backtraces, debug messages etc that would
> > > > help.
> > > >
> > > > Can anyone confirm this?
> > > > If so, this is a serious probelm!!
> > > >
> > > > Andi
> > > > _______________________________________________
> > > > Digikam-devel mailing list
> > > > [hidden email]
> > > > https://mail.kde.org/mailman/listinfo/digikam-devel
> > >
> > > _______________________________________________
> > > Digikam-devel mailing list
> > > [hidden email]
> > > https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-devel
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

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

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