Bug 205601 - Unknown showfoto crash
Summary: Unknown showfoto crash
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Showfoto-Core (show other bugs)
Version: 0.10.0
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-29 19:03 UTC by alvaro islas
Modified: 2022-01-20 06:41 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alvaro islas 2009-08-29 19:03:22 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Mandriva RPMs

A Fatal Error Occurred
The application showFoto (showfoto) crashed and caused the signal 11 (SIGSEGV).
Comment 1 alvaro islas 2009-08-29 19:05:48 UTC
I just installed it using the software management tool.
It crashed as I tried to open it.
Comment 2 caulier.gilles 2009-08-29 19:47:18 UTC
Which version you use ?

Sound like a broken package or a broken dependency.

Here showfoto work fine under mandriva.

Give us a gdb backtrace please

Gilles Caulier
Comment 3 Dario Andres 2009-08-30 17:34:02 UTC
@alvaro: take a look at http://techbase.kde.org/User:DarioAndres/CreateUsefulReports to know how to get the backtrace. Also, you are not using KDE4.3 (the crash message you posted is from KDE<4.3) ; what KDE version are you using?
Thanks
Comment 4 alvaro islas 2009-08-31 02:27:56 UTC
I got 4.1.3. Thank you for your help,

Dr. Alvaro Islas
Department of Mathematics
University of Central Florida
Phone: (407) 823-3961
Fax: (407) 823-6253


--- On Sun, 8/30/09, Dario Andres <andresbajotierra@gmail.com> wrote:

> From: Dario Andres <andresbajotierra@gmail.com>
> Subject: [Bug 205601] A Fatal Error Occurred, The application showFoto (showfoto) crashed and caused the signal 11 (SIGSEGV).
> To: alislas@yahoo.com
> Date: Sunday, August 30, 2009, 11:34 AM
> https://bugs.kde.org/show_bug.cgi?id=205601
> 
> 
> Dario Andres <andresbajotierra@gmail.com>
> changed:
> 
>            What 
>   |Removed           
>          |Added
> ----------------------------------------------------------------------------
>              
>    CC|         
>                
>   |andresbajotierra@gmail.com
> 
> 
> 
> 
> --- Comment #3 from Dario Andres <andresbajotierra gmail
> com>  2009-08-30 17:34:02 ---
> @alvaro: take a look at
> http://techbase.kde.org/User:DarioAndres/CreateUsefulReports
> to know how to get
> the backtrace. Also, you are not using KDE4.3 (the crash
> message you posted is
> from KDE<4.3) ; what KDE version are you using?
> Thanks
> 
> -- 
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 5 Dario Andres 2009-09-01 01:31:20 UTC
@Alvaro: can you get the backtrace of the crash using the information link I gave to you ? Thanks
Comment 6 alvaro islas 2009-09-06 16:57:42 UTC
Dario,
Here is the backtrace from the moment I enter gdb. I hope this works.
Alvaro

$ gdb showfoto                                              
GNU gdb 6.8-6mdv2009.1 (Mandriva Linux release 2009.1)                          
Copyright (C) 2008 Free Software Foundation, Inc.                               
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>   
This is free software: you are free to change and redistribute it.              
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"      
and "show warranty" for details.                                                
This GDB was configured as "i586-mandriva-linux-gnu"...                         
(no debugging symbols found)                                                    
Missing debug package(s), you should install: digikam-debug-0.10.0-6mdv2009.1.i586                                                                              
(gdb) run                                                                       
Starting program: /usr/bin/showfoto                                             
[Thread debugging using libthread_db enabled]                                   
[New Thread 0xb54076d0 (LWP 28608)]                                             
[New Thread 0xb3ad7b90 (LWP 28611)]                                             
[New Thread 0xb32d6b90 (LWP 28612)]                                             
[New Thread 0xb2a94b90 (LWP 28613)]                                             
Starting to load Plugins.                                                       
=== MarbleDirs: ===                                                             
Local Path: "/home/cschober/.marble/data"                                       
Plugin Local Path: "/home/cschober/.marble/plugins"                             
                                                                                
Marble Data Path (Run Time) : ""                                                
Marble Data Path (Compile Time): "/usr/share/apps/marble/data"                  
                                                                                
Marble Plugin Path (Run Time) : ""                                              
Marble Plugin Path (Compile Time): "/usr/lib/kde4/plugins/marble"               
                                                                                
System Path: ""                                                                 
Plugin System Path: ""                                                          
===================                                                             
"Module.symvers"  -  "/Module.symvers"                                          

Program received signal SIGSEGV, Segmentation fault.
0xb724f1cf in operator<< () from /usr/lib/libQtCore.so.4
(gdb) thread apply all backtrace                        

Thread 4 (Thread 0xb2a94b90 (LWP 28613)):
#0  0xffffe430 in __kernel_vsyscall ()   
#1  0xb604ec45 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/libpthread.so.0                  
#2  0xb65b58dd in pthread_cond_wait () from /lib/i686/libc.so.6
#3  0xb713e3eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb7db52fc in Digikam::LoadSaveThread::run ()                     
---Type <return> to continue, or q <return> to quit---                
   from /usr/lib/libdigikamcore.so.1                                                                                         
#5  0xb713d2e3 in ?? () from /usr/lib/libQtCore.so.4                                                                         
#6  0xb604b315 in start_thread () from /lib/i686/libpthread.so.0                                                             
#7  0xb65a825e in clone () from /lib/i686/libc.so.6                                                                          
                                                                                                                             
Thread 3 (Thread 0xb32d6b90 (LWP 28612)):                                                                                    
#0  0xffffe430 in __kernel_vsyscall ()                                                                                       
#1  0xb604ec45 in pthread_cond_wait@@GLIBC_2.3.2 ()                                                                          
---Type <return> to continue, or q <return> to quit---                                                                       
   from /lib/i686/libpthread.so.0                                                                                            
#2  0xb65b58dd in pthread_cond_wait () from /lib/i686/libc.so.6                                                              
#3  0xb713e3eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4                                                       
#4  0xb7db52fc in Digikam::LoadSaveThread::run ()                                                                            
   from /usr/lib/libdigikamcore.so.1                                                                                         
#5  0xb713d2e3 in ?? () from /usr/lib/libQtCore.so.4                                                                         
#6  0xb604b315 in start_thread () from /lib/i686/libpthread.so.0
#7  0xb65a825e in clone () from /lib/i686/libc.so.6
---Type <return> to continue, or q <return> to quit---

Thread 2 (Thread 0xb3ad7b90 (LWP 28611)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb604ec45 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/libpthread.so.0
#2  0xb65b58dd in pthread_cond_wait () from /lib/i686/libc.so.6
#3  0xb713e3eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb7db52fc in Digikam::LoadSaveThread::run ()
---Type <return> to continue, or q <return> to quit---
   from /usr/lib/libdigikamcore.so.1
#5  0xb713d2e3 in ?? () from /usr/lib/libQtCore.so.4
#6  0xb604b315 in start_thread () from /lib/i686/libpthread.so.0
#7  0xb65a825e in clone () from /lib/i686/libc.so.6

Thread 1 (Thread 0xb54076d0 (LWP 28608)):
#0  0xb724f1cf in operator<< () from /usr/lib/libQtCore.so.4
#1  0xb5f94301 in Marble::PluginManager::loadPlugins ()
---Type <return> to continue, or q <return> to quit---
   from /usr/lib/libmarblewidget.so.4
#2  0xb5f95162 in Marble::PluginManager::PluginManager ()
   from /usr/lib/libmarblewidget.so.4
#3  0xb5f9197a in Marble::LayerManager::LayerManager ()
   from /usr/lib/libmarblewidget.so.4
#4  0xb5f4f2a6 in Marble::MarbleModel::MarbleModel ()
   from /usr/lib/libmarblewidget.so.4
#5  0xb5f598ad in Marble::MarbleMap::MarbleMap ()
---Type <return> to continue, or q <return> to quit---
   from /usr/lib/libmarblewidget.so.4
#6  0xb5f4a31c in Marble::MarbleWidget::MarbleWidget ()
   from /usr/lib/libmarblewidget.so.4
#7  0xb7e83c1c in ?? () from /usr/lib/libdigikamcore.so.1
#8  0xb7e7ff2f in Digikam::ImagePropertiesGPSTab::ImagePropertiesGPSTab ()
   from /usr/lib/libdigikamcore.so.1
#9  0xb7e65866 in Digikam::ImagePropertiesSideBar::ImagePropertiesSideBar ()
   from /usr/lib/libdigikamcore.so.1
---Type <return> to continue, or q <return> to quit---
#10 0x0807bb48 in ?? ()
#11 0x0807fa91 in ?? ()
#12 0x08076d97 in ?? ()
#13 0xb64e26a5 in __libc_start_main () from /lib/i686/libc.so.6
#14 0x080549d1 in _start ()
(gdb)

Dr. Alvaro Islas
Department of Mathematics
University of Central Florida
Phone: (407) 823-3961
Fax: (407) 823-6253


--- On Mon, 8/31/09, Dario Andres <andresbajotierra@gmail.com> wrote:

> From: Dario Andres <andresbajotierra@gmail.com>
> Subject: [Bug 205601] Unknown showfoto crash
> To: alislas@yahoo.com
> Date: Monday, August 31, 2009, 7:31 PM
> https://bugs.kde.org/show_bug.cgi?id=205601
> 
> 
> Dario Andres <andresbajotierra@gmail.com>
> changed:
> 
>            What 
>   |Removed           
>          |Added
> ----------------------------------------------------------------------------
>          
>    Status|UNCONFIRMED     
>            |NEEDSINFO
>          Resolution| 
>                
>           |WAITINGFORINFO
>             Summary|A Fatal
> Error Occurred, The |Unknown showfoto crash
>                
>    |application showFoto     
>   |
>                
>    |(showfoto) crashed and   
>   |
>                
>    |caused the signal 11     
>   |
>                
>    |(SIGSEGV).       
>           |
> 
> 
> 
> 
> --- Comment #5 from Dario Andres <andresbajotierra gmail
> com>  2009-09-01 01:31:20 ---
> @Alvaro: can you get the backtrace of the crash using the
> information link I
> gave to you ? Thanks
> 
> -- 
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 7 caulier.gilles 2009-09-06 17:19:30 UTC
Crash is relevant of MarbleWidget.

Please try to run marble program as stand alone application, and look if crash is reproducible...

Do you have installed all marble data maps ?

Gilles Caulier
Comment 8 Dario Andres 2009-09-06 17:31:02 UTC
Yes, this is problably bug 182144. Thanks
Comment 9 Angelo Naselli 2009-09-06 17:53:42 UTC
it should be the same issue reported here:
https://qa.mandriva.com/show_bug.cgi?id=52374
Comment 10 caulier.gilles 2009-09-06 19:12:29 UTC

*** This bug has been marked as a duplicate of bug 182144 ***
Comment 11 caulier.gilles 2022-01-20 06:41:04 UTC
Fixed with https://bugs.kde.org/show_bug.cgi?id=182144