* Can you re-run using: "SHOTWELL_LOG=1 SHOTWELL_LOG_FILE=:console: shotwell | tee shotwell_log.txt" and then attach shotwell_log.txt to this bug? * Can you re-run using: "strace -o strace_log.txt shotwell" and then attach "strace_log.txt" to this bug? * Can you attach the output of the commands "dpkg -l" and "ldd $(which shotwell)"?
--- * The most valuable info would be if you could get a backtrace that shows where Shotwell crashes/aborts or exits. Do the following steps: A) enable the ddebs repository, as explained in this page: https://wiki.ubuntu.com/DebuggingProgramCrash (just execute the commands in steps 1 to 6 in a terminal, except that step 6 should "sudo apt-get install shotwell-dbgsym=0.5.0+dfsg-1.1" instead). B) start "gdb shotwell" and inside the debugger prompt type "break exit" and also "break abort" (the latter will say the breakpoint is just pending but that's ok). Now type "run" into the debugger prompt and shotwell should start. C) Once shotwell crashes/exits or aborts, then have a look at the debugger prompt again and type "bt full" there and copy paste the output onto this bug report. PS. If you're interested you can read more about backtraces here; https://wiki.ubuntu.com/Backtrace -- Shotwell crashes on clicking on sidebar options https://bugs.launchpad.net/bugs/604053 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
