[Digikam-devel] [digikam] [Bug 278049] Crash during tagging while scanning run in background

eric e.longuemare at laposte.net
Wed Oct 2 17:28:12 BST 2013


Hello,

Should you give a copy of digikam components : in digikam : menu help
then component, copy and paste the list ?

Where are your collection, on local disk or on a network share ?

For gdb you should install it if it is not. But wait for the moment.

Greatings,

Eric


Le mercredi 02 octobre 2013 à 13:15 +0000, Lucas Linard a écrit :
> https://bugs.kde.org/show_bug.cgi?id=278049
> 
> --- Comment #67 from Lucas Linard <lucaslinard at outlook.com.br> ---
> How do I launch digikam from gdb. I'm no developer just a regular user trying
> to help. What can I do?
> 
> [llinard at Inspiron ~]$ cat /proc/cpuinfo 
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 58
> model name      : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz
> stepping        : 9
> microcode       : 0x19
> cpu MHz         : 1674.000
> cache size      : 3072 KB
> physical id     : 0
> siblings        : 4
> core id         : 0
> cpu cores       : 2
> apicid          : 0
> initial apicid  : 0
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 13
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
> aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16
> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c
> lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept
> vpid fsgsbase smep erms
> bogomips        : 3591.83
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
> 
> processor       : 1
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 58
> model name      : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz
> stepping        : 9
> microcode       : 0x19
> cpu MHz         : 1692.000
> cache size      : 3072 KB
> physical id     : 0
> siblings        : 4
> core id         : 1
> cpu cores       : 2
> apicid          : 2
> initial apicid  : 2
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 13
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
> aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16
> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c
> lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept
> vpid fsgsbase smep erms
> bogomips        : 3591.83
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
> 
> processor       : 2
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 58
> model name      : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz
> stepping        : 9
> microcode       : 0x19
> cpu MHz         : 1782.000
> cache size      : 3072 KB
> physical id     : 0
> siblings        : 4
> core id         : 0
> cpu cores       : 2
> apicid          : 1
> initial apicid  : 1
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 13
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
> aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16
> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c
> lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept
> vpid fsgsbase smep erms
> bogomips        : 3591.83
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
> 
> processor       : 3
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 58
> model name      : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz
> stepping        : 9
> microcode       : 0x19
> cpu MHz         : 1710.000
> cache size      : 3072 KB
> physical id     : 0
> siblings        : 4
> core id         : 1
> cpu cores       : 2
> apicid          : 3
> initial apicid  : 3
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 13
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
> aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16
> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c
> lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept
> vpid fsgsbase smep erms
> bogomips        : 3591.83
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
> 
> 
> > From: e.longuemare at laposte.net
> > To: lucaslinard at outlook.com.br
> > Subject: [digikam] [Bug 278049] Crash during tagging while scanning run in background
> > Date: Wed, 2 Oct 2013 07:36:57 +0000
> > 
> > https://bugs.kde.org/show_bug.cgi?id=278049
> > 
> > --- Comment #66 from e.longuemare at laposte.net ---
> > Hello,
> > 
> > Should you do face confirmation without launching anything else out or
> > in digikam (no scanning ...) and see if it crash ?
> > 
> > -restart the computer, launch digikam in gdb and do face tag
> > confirmation
> > 
> > Should you give the result of $cat /proc/cpuinfo ?
> > 
> > cordialement,
> > 
> > Eric
> > 
> > 
> > 
> > Le mercredi 02 octobre 2013 à 00:34 +0000, Lucas Linard a écrit :
> > > https://bugs.kde.org/show_bug.cgi?id=278049
> > > 
> > > --- Comment #65 from Lucas Linard <lucaslinard at outlook.com.br> ---
> > > Created attachment 82599
> > >   --> https://bugs.kde.org/attachment.cgi?id=82599&action=edit
> > > New crash information added by DrKonqi
> > > 
> > > digikam (3.4.0) on KDE Platform 4.11.1 using Qt 4.8.5
> > > 
> > > - What I was doing when the application crashed:
> > > Trying to use face detect tool to try to rescan the files with no confirmation
> > > 
> > > - Unusual behavior I noticed:
> > > Simply Crashes.
> > > 
> > > -- Backtrace (Reduced):
> > > #6  0x0000003421b9d70b in clear (d=0x5d16c30) at kernel/qvariant.cpp:290
> > > #7  0x000000344ff35c11 in node_destruct (this=<optimized out>, n=0x5948158) at
> > > /usr/include/QtCore/qlist.h:388
> > > #8  erase (alast=..., afirst=..., this=0x2062b18) at
> > > /usr/include/QtCore/qlist.h:803
> > > #9  Digikam::ImageModel::removeRowPairs (this=this at entry=0x20606a0,
> > > toRemove=...) at
> > > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:1025
> > > #10 0x000000344ff36ec2 in Digikam::ImageModel::finishIncrementalRefresh
> > > (this=this at entry=0x20606a0) at
> > > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:844
> > >
> > 
> > -- 
> > You are receiving this mail because:
> > You are on the CC list for the bug.
> 





More information about the Digikam-devel mailing list