[Digikam-devel] [Bug 137958] New: 0.9rc1crashes (SIGABRT) when i try to connect to camera (PowerShot G6)

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=137958         
           Summary: 0.9rc1crashes (SIGABRT) when i try to connect to camera
                    (PowerShot G6)
           Product: digikam
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: NEW
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: wbsoft xs4all nl


Version:           0.9.0-rc1 (using KDE 3.5.5, Gentoo)
Compiler:          gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)
OS:                Linux (i686) release 2.6.16-gentoo-r2

Digikam crashes with signal 6 (SIGABRT) when I start the camera dialog. The camera window appears for a very short time, but then Digikam crashes. A small backtrace is produced by drKonqi, I hope it's useful.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1245341504 (LWP 31959)]
[New Thread -1256735840 (LWP 32119)]
0xb6041277 in pthread_mutex_lock () from /lib/libpthread.so.0
#0  0xb6041277 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0xb6995843 in QRecursiveMutexPrivate::lock (this=0x80667e8)
    at qmutex_unix.cpp:235
#2  0xb6995d80 in QMutex::lock (this=0x807e598) at qmutex_unix.cpp:464
#3  0xb7dd6266 in QMutexLocker (this=0x806680c, m=0xb6c887f0) at qmutex.h:96
#4  0xb65f8a27 in QApplication::sendPostedEvents (receiver=0x0, event_type=70)
    at qapplication.cpp:3209
#5  0xb65f89f1 in QApplication::sendPostedEvents (receiver=0x0, event_type=0)
    at qapplication.cpp:3203
#6  0xb65f89b8 in QApplication::sendPostedEvents () at qapplication.cpp:3181
#7  0xb6592286 in QEventLoop::processEvents (this=0x80873b0, flags=4)
    at qeventloop_x11.cpp:144
#8  0xb660fb09 in QEventLoop::enterLoop (this=0x80873b0) at qeventloop.cpp:198
#9  0xb660fa24 in QEventLoop::exec (this=0x80873b0) at qeventloop.cpp:145
#10 0xb65f7de9 in QApplication::exec (this=0xbfd24370)
    at qapplication.cpp:2758
#11 0x0804a916 in main (argc=134637580, argv=0x806680c) at main.cpp:269
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=137958         
caulier.gilles kdemail net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Camera GUI



------- Additional Comments From caulier.gilles kdemail net  2006-11-27 11:54 -------
Wilbert,

It's not reproductible here. Are you using Gphoto2 drivers or mount your camera like an UMS ?

Can you start digiKam under gdb and get a backtrace. Look into HACKING file for details.

Thanks in advance.

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

[Gilles Caulier-2]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=137958         




------- Additional Comments From caulier.gilles kdemail net  2006-12-12 09:22 -------
Wilbert,

This crash still reproductible using digiKam/DigikamImagePlugins 0.9.0-RC2, Exiv2 0.12, and a fresh update of libgphoto2 ?

Thanks in advance for your feedback.

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

[Arnd Baecker]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=137958         




------- Additional Comments From arnd.baecker web de  2007-06-01 18:29 -------
I would suggest to close this bug
(and other bugs where the original poster
does not respond over such a long period -
Already closing two weeks after an enquiry would be OK in my opinion, as
the bug can always we re-opened)
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=137958         
caulier.gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From caulier.gilles gmail com  2007-06-01 19:16 -------
Right Arnd,

No need to full B.K.O with unresolvable files (:=)))

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

[Arnd Baecker]

On Fri, 1 Jun 2007, Gilles Caulier wrote:

> No need to full B.K.O with unresolvable files (:=)))

;-)

The B.K.O  currently 323 open bugs just for digikam ...
What about a bug-squashing week-end at some point,
to go through all bugs, see if they are still valid, try
to get fresh feed-back, or even provide fixes?
(This is also something where non-coders could contribute!)

Also - is there a way to mark some bugs to be addressed
at some later stage (i.e. 0.9.3, ....)?
Somehow the KDE bug tracker does not seem to be that feature-rich ...

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

[Gilles Caulier-4]

2007/6/1, Arnd Baecker <[hidden email]>:

On Fri, 1 Jun 2007, Gilles Caulier wrote:

> No need to full B.K.O with unresolvable files (:=)))

;-)

The B.K.O  currently 323 open bugs just for digikam ...
What about a bug-squashing week-end at some point,

totally agree.
 

to go through all bugs, see if they are still valid, try
to get fresh feed-back, or even provide fixes?
(This is also something where non-coders could contribute!)

Absolutly. All Crash reports must be do in priority.

And also :

- moving bugs on the right component if necessary.
- post messages to get more debug informations if necessary (gdb, valgrind).
- post messages to get more context informations to reproduce the bug.
 

Also - is there a way to mark some bugs to be addressed
at some later stage (i.e. 0.9.3, ....)?
Somehow the KDE bug tracker does not seem to be that feature-rich ...

because you need more right to do it. Here, with my account, i can do it.

If you is interressed to help us in this task (and we need really help for that), you need to contact bugzilla admin to cahnge your account. I'm not admin myself, i cannot do it...

On B.K.O page, you can see that it maintened by " [hidden email]". I'm not sure if it's the right way to change bugzilla account properties, but i cannot find others way...

Gilles
 

Best, Arnd
_______________________________________________
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

[Arnd Baecker]

On Sat, 2 Jun 2007, Gilles Caulier wrote:
[...]
> > The B.K.O  currently 323 open bugs just for digikam ...
> > What about a bug-squashing week-end at some point,
>
> totally agree.

What about 15, 16, 17 June (Fri, Sat, Sun)? ;-)
((I won't be able to do much before then ...))

In addition, what about if I send an e-mail on
digikam-users to ask that everyone has a look at the
bugs he has filed so far and to check if the reported problems
still persist with current svn.
Maybe this could already clear up quite a few before mid June?

[...]

> If you is interressed to help us in this task (and we need really help for
> that), you need to contact bugzilla admin to cahnge your account. I'm not
> admin myself, i cannot do it...
>
> On B.K.O page, you can see that it maintened by "[hidden email]". I'm not
> sure if it's the right way to change bugzilla account properties, but i
> cannot find others way...

OK, I have sent an e-mail to the sysadmin at kde.org.

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