Bug 164622 - crash using timeline when switching from month to week to month view
Summary: crash using timeline when switching from month to week to month view
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Searches-TimeLine (show other bugs)
Version: 0.9.4
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-21 22:11 UTC by Simon Oosthoek
Modified: 2012-08-02 09:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 0.9.5
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Oosthoek 2008-06-21 22:11:41 UTC
Version:           0.9.4rc1 (using KDE 3.5.9)
Installed from:    Ubuntu Packages
Compiler:          gcc (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) 
OS:                Linux

digikam stopped responding to anything after I switched from month view to week and then back to month. This was using the new timeline feature in 0.9.4(rc1)

On the commandline I saw this:
 QDate::setYMD: Invalid date -001-12-01
QDate::setYMD: Invalid date -001-12-01

So perhaps it's just a lack of input check for a function?

Cheers

Simon
Comment 1 Simon Oosthoek 2008-06-21 22:13:37 UTC
Sorry, I'm using gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
Comment 2 caulier.gilles 2008-06-21 22:19:51 UTC
Please, give us a gdb backtrace to hack. Look here for details:

http://www.digikam.org/drupal/contrib

Gilles Caulier
Comment 3 Simon Oosthoek 2008-06-22 10:39:50 UTC
I can't reproduce it right now, though I did notice that after starting digikam again, it was busy for a long time (not responding) and then everything seemed normal again. When I looked at the timeline again, the date was set to October 98798278 (a large number, not this particular number ;-)

If I notice it again, I'll see about getting a trace for you...

/Simon
Comment 4 Andi Clemens 2008-08-16 15:40:32 UTC
Simon,

if you can't confirm this anymore right now, I'd like to close it. We can reopen it if the problem should be noticed again. Since this is a "crash" report it has a high priority, and we want to fix those as fast as possible.

Andi
Comment 5 Simon Oosthoek 2008-08-16 20:27:45 UTC
On Sat, Aug 16, 2008 at 01:40:33PM -0000, Andi Clemens wrote:

> if you can't confirm this anymore right now, I'd like to close it. We can
> reopen it if the problem should be noticed again. Since this is a "crash"
> report it has a high priority, and we want to fix those as fast as
> possible.


Sorry, I think it was a one off thing, though I've not used the timeline
since then ;-)

Better close it if nobody else confirmed this. If I ever see it again, I'll
reopen it...

/Simon
Comment 6 Andi Clemens 2008-08-16 20:56:41 UTC
Right now this is not reproducible anymore... closing it.