Disappears after usb import

Bug #874166 reported by EricDHH
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Oneiric amd64

When importing some pictures from my dmc-g1 camera over usb, shotwell sudden disappears after the last photo. When restarted everything was imported well. The maverick version was stable in this case.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: shotwell 0.11.2-0ubuntu1 [modified: usr/share/glib-2.0/schemas/gschemas.compiled]
ProcVersionSignature: Ubuntu 3.0.0-12.20-genusername 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
CheckboxSubmission: 72ffaca291c05635776d4a13f9e644e4
CheckboxSystem: 32980ee028b29311fef8e195a759b031
Date: Fri Oct 14 14:34:12 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: shotwell
UpgradeStatus: Upgraded to oneiric on 2011-09-27 (16 days ago)

Revision history for this message
EricDHH (ericdhh) wrote :
Revision history for this message
Clint Rogers (clinton-yorba) wrote :

Hi,

Thank you for reporting this. If you haven't already done so, can you try running Shotwell from the command line with the debugger and logging enabled and try to trigger the bug there? You can do this by typing
     SHOTWELL_LOG=1 gdb shotwell
in a command shell window, then typing 'run' at the '(gdb)' prompt.

If you are able to get Shotwell to crash again after doing this, please type 'bt' at the (gdb) prompt, and copy and paste the resulting info here. We can use this info to determine what Shotwell was trying to do at the time of the crash, and this will aid us in reproducing and fixing the problem.

Revision history for this message
EricDHH (ericdhh) wrote :

This time shotwell goes to greyout and did not return

[Thread 0x7fffd7aee700 (LWP 2624) exited]
[Thread 0x7fffcffff700 (LWP 2625) exited]
**
ERROR:x86_64-linux-gnu/Dialogs.c:2810:import_ui_get_media_specific_string: code should not be reached

Program received signal SIGABRT, Aborted.
0x00007ffff32953a5 in raise () from /lib/x86_64-linux-gnu/libc.so.6

(gdb) bt
#0 0x00007ffff32953a5 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007ffff3298b0b in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007ffff41e54ad in g_assertion_message ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00000000005f7b0f in import_ui_get_media_specific_string ()
#4 0x00000000005f7d2b in import_ui_report_manifest ()
#5 0x000000000054f97c in ?? ()
#6 0x00000000005ea691 in ?? ()
#7 0x00000000005eac62 in ?? ()
#8 0x00007ffff41c323b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x00007ffff41c1a5d in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007ffff41c2258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff41c2792 in g_main_loop_run ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff5d57db7 in gtk_main ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x000000000068b7bc in application_start ()
#14 0x0000000000578404 in library_exec ()
#15 0x00000000005796df in _vala_main ()
#16 0x000000000047b641 in main ()
(gdb)

Revision history for this message
Adam Dingle (adam-yorba) wrote :

This now looks like this bug, which we fixed in Shotwell 0.11.3:

http://redmine.yorba.org/issues/4172

Hopefully Ubuntu will push 0.11.3 (or later) to Oneiric soon.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in shotwell (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.