Shotwell unresponsive while generating video thumbnails
Submitted by Adam Dingle
Assigned to Eric Gregory
Link to original bug (#717712)
Description
---- Reported by adam@yorba.org 2011-08-04 09:26:00 -0700 ----
Original Redmine bug id: 3927
Original URL: http://redmine.yorba.org/issues/3927
Searchable id: yorba-bug-3927
Original author: Adam Dingle
Original description:
It's great that Shotwell can now generate missing video thumbnails on the fly when new GStreamer codecs have been installed. I just tried this and found that while Shotwell was generating thumbnails, it was unresponsive: when I scrolled up and down there were sometimes several-second pauses during which the application seemed to be hung. And there was no progress message saying what was going on. I think we should display a progress message and/or make Shotwell more responsive while this is happening.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:39:00 -0700 ----
History
Comment 1
Updated by Jim Nelson over 2 years ago
- Priority changed from Normal to High
Comment 2
Updated by Fred van Zwieten over 2 years ago
Why not put a progress box in front of the main window when this happens. It informs users of what's going on and they see they have to wait and they see how long it will (more or less) take.
Comment 3
Updated by Lucas Beeler over 2 years ago
- Assignee set to Eric Gregory
Comment 4
Updated by Eric Gregory over 2 years ago
- Status changed from Open to Review
Comment 5
Updated by Eric Gregory over 2 years ago
- Status changed from Review to 5
- Resolution set to fixed
Fixed in bb4ed7d5
Comment 6
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:53 UTC ---
This bug was previously known as bug 3927 at http://redmine.yorba.org/show_bug.cgi?id=3927
Unknown Component Using default product and component set in Parameters 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.
Version: 0.11
Resolution: RESOLVED FIXED