On Quantal, a [CRT] message appears if the user enters, then exits, fullscreen.
Submitted by cli..@..ba.org
Assigned to cli..@..ba.org
Link to original bug (#718844)
Description
---- Reported by clinton@yorba.org 2012-09-06 11:22:00 -0700 ----
Original Redmine bug id: 5774
Original URL: http://redmine.yorba.org/issues/5774
Searchable id: yorba-bug-5774
Original author: Clinton Rogers
Original description:
Steps to reproduce:
- On Quantal Quetzal, launch Shotwell from the console.
- With any image, enter the photo page.
- Press F11.
- Press F11 again and carefully observe the console used for step one.
Notice that an error message similar to the following appears in the console:
L 4236 2012-09-06 11:21:52 [CRT] library_window_init_view_filter: assertion
IS_CHECKERBOARD_PAGE (page)' failed`
Note: the application continues to run at this point.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Clinton Rogers about 1 year ago
- Subject changed from A [CRT] appears if the user enters, then exits, fullscreen. to On Quantal, a [CRT] message appears if the user enters, then exits, fullscreen.
- Description updated (diff)
Comment 2
Updated by Adam Dingle about 1 year ago
- Assignee set to Clinton Rogers
- Priority changed from High to Urgent
Good catch.
Comment 3
Updated by Clinton Rogers about 1 year ago
- Status changed from Open to Review
- % Done changed from 0 to 80
Comment 4
Updated by Clinton Rogers about 1 year ago
- Status changed from Review to 5
- % Done changed from 80 to 100
- Resolution set to fixed
Comment 5
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:58 UTC ---
This bug was previously known as bug 5774 at http://redmine.yorba.org/show_bug.cgi?id=5774
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.13
Resolution: RESOLVED FIXED