abort in fullscreen mode
Submitted by an unknown user
Link to original bug (#717891)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-05-21 09:06:00 -0700 ----
Original Redmine bug id: 3637
Original URL: http://redmine.yorba.org/issues/3637
Searchable id: yorba-bug-3637
Original author: wrobell -
Original description:
not sure if it is duplicate of #3577 (closed), but
- choose a photo
- press F11 to see it in fullscreen
- press ENTER
- press SPACE
shotwell aborts with the message on the console
ERROR:src/PhotoPage.c:3928:editing_host_page_set_photo: assertion failed: (view != NULL)
Aborted
this is with shotwell 0.9.3.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:39:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 2 years ago
- Target version set to 0.10
- Priority set to Urgent
I can reproduce this in the current trunk like this:
Start Shotwell.
Rapidly press F11, Enter and then Space over and over again.
Before long, Shotwell will crash with the assertion mentioned above.
Comment 2
Updated by Adam Dingle over 2 years ago
- Target version changed from 0.10 to 0.10.1
Comment 3
Updated by Adam Dingle over 2 years ago
- Target version changed from 0.10.1 to 0.11
Comment 4
Updated by Eric Gregory over 2 years ago
There's a much simpler way to reproduce the problem:
-
Start Shotwell
-
Select a photo and hit F11 to enter fullscreen mode
-
Press Enter, then press either the left or right arrow
You'll then hit the assertion immediately.
Comment 5
Updated by Eric Gregory over 2 years ago
- Resolution set to fixed
- % Done changed from 0 to 100
Fixed in 49da369c
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:54 UTC ---
This bug was previously known as bug 3637 at http://redmine.yorba.org/show_bug.cgi?id=3637
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