[norepro] Crash when an internal harddrive is unmounted
Submitted by an unknown user
Link to original bug (#716981)
Description
---- Reported by shotwell-maint@gnome.bugs 2010-11-26 01:04:00 -0800 ----
Original Redmine bug id: 2881
Original URL: http://redmine.yorba.org/issues/2881
Searchable id: yorba-bug-2881
Original author: Peter Thor
Original description:
My setup:
Ubuntu 10.10
Shotwell 0.7.2+trunk
The situation:
Trying to start shotwell results in a segmentation fault. I recently attached a new SATA drive, previously I was using one HD for the OS and one HD for images (here reffered as “imagesâ€), both PATA. All drives are internal drives, I am setting up a raid array why I take this slowly and have duplicated data/drives.
When I attached the SATA drive during startup I got some mountproblems causing me to having to ignore the mounting This means that the drive “images†is unmounted after startup. If I mount it and start shotwell everything is fine, if I unmount it shotwell will crash. This is reproduced in the log files.
I use links to my image repository (>40k images).
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:46:00 -0700 ----
History
Comment 1
Updated by Adam Dingle almost 3 years ago
- Priority set to Urgent
This looks very much like the following bug, which we closed because the reporter was no longer able to reproduce it:
https://bugs.launchpad.net/ubuntu/source/shotwell/bug/659122
Comment 2
Updated by Peter Thor almost 3 years ago
Yes,
I confirm the exact sequence mentioned in the bug in the link (progress indicator at 50% then crash and mounting it fixes it).
Comment 3
Updated by Jim Nelson almost 3 years ago
- Status changed from Open to Review
- Assignee changed from Anonymous to Jim Nelson
Comment 4
Updated by Adam Dingle almost 3 years ago
- Priority changed from Urgent to High
- Subject changed from Crash when an internal harddrive is unmounted to [norepro] Crash when an internal harddrive is unmounted
We can't reproduce this here and only one user has reported it, so we probably cannot fix it for 0.8. Dropping to high.
Comment 5
Updated by Adam Dingle almost 3 years ago
- Assignee changed from Jim Nelson to Anonymous
Comment 6
Updated by Adam Dingle over 2 years ago
- Resolution set to invalid
- % Done changed from 0 to 0
This bug is old and not reproducible, so I'm closing it. If this still affects anyone with a current Shotwell build, feel free to reopen.
Comment 7
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:48 UTC ---
This bug was previously known as bug 2881 at http://redmine.yorba.org/show_bug.cgi?id=2881 Imported an attachment (id=261865) Imported an attachment (id=261866)
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED INVALID