After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 718197 - Press escape in fullscreen mode causes close of shotwell
Press escape in fullscreen mode causes close of shotwell
Status: RESOLVED FIXED
Product: shotwell
Classification: Other
Component: general
0.12
Other All
: Urgent normal
: ---
Assigned To: Shotwell Maintainers
Shotwell Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-11-06 05:10 UTC by Shotwell Maintainers
Modified: 2013-05-01 06:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb.txt (14.78 KB, text/plain)
2011-11-08 22:13 UTC, Shotwell Maintainers
Details

Description Charles Lindsay 2013-11-25 21:55:19 UTC


---- Reported by shotwell-maint@gnome.bugs 2011-11-06 09:10:00 -0800 ----

Original Redmine bug id: 4350
Original URL: http://redmine.yorba.org/issues/4350
Searchable id: yorba-bug-4350
Original author: Pierre Willaime
Original description:

I want to escape from fullscreen mode (F11) to go back to the normal view of
shotwell.

If I press "escape" in fullscreen mode, shotwell (0.11.4) just closes and I
have to restart it.

I have this error in terminal :

@(shotwell:9661): Gtk-CRITICAL **: IA__gtk_widget_unrealize: assertion
`GTK_IS_WIDGET (widget)' failed

(shotwell:9661): Gtk-CRITICAL **: IA__gtk_widget_is_toplevel: assertion
`GTK_IS_WIDGET (widget)' failed

Erreur de segmentation

@



---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----

### History

####

#1

Updated by Adam Dingle about 2 years ago

Pierre,

I can't reproduce this either in 0.11.4, 0.11.5 or the current git master
build. What operating system version are you running?

####

#2

Updated by Pierre Willaime about 2 years ago

It's archlinux (up-to-date) with gnome-shell 3.2.1-1. Shotwell's version is
the 0.11.4-2.

.xsession-error just says :

    
    (shotwell:17840): Gtk-CRITICAL **: IA__gtk_widget_unrealize: assertion `GTK_IS_WIDGET (widget)' failed
    
    (shotwell:17840): Gtk-CRITICAL **: IA__gtk_widget_is_toplevel: assertion `GTK_IS_WIDGET (widget)' failed

####

#3

Updated by Stéphane Maniaci about 2 years ago

I can reproduce this on Fedora 16. There is an entry on the RedHat bugzilla,
where I attached my backtrace (before finding it here).

This is Fedora 16, shotwell 0.10.1-1.fc16.

EDIT: forgot the link! https://bugzilla.redhat.com/show_bug.cgi?id=748155

####

#4

Updated by Adam Dingle about 2 years ago

  * **Priority** changed from _High_ to _Urgent_
  * **Target version** set to _0.12_

OK: since this has been observed on both Arch and Fedora, we should
investigate further.

####

#5

Updated by Adam Dingle about 2 years ago

This was a known bug in Shotwell 0.10 which was fixed in Shotwell 0.11: see
#3637. That explains the crash Stephane is seeing. It doesn't, however,
explain the crash Pierre is seeing in 0.11.4.

####

#6

Updated by Lucas Beeler about 2 years ago

  * **Category** set to _4_
  * **Assignee** set to _Lucas Beeler_

####

#7

Updated by Adam Dingle about 2 years ago

  * **Assignee** deleted (<strike>_Lucas Beeler_</strike>)

I can't reproduce this in git master on either Ubunutu Oneiric or Fedora 16.
Looks like it may be specific to Arch.

####

#8

Updated by Pierre Willaime about 2 years ago

  * **Resolution** set to _fixed_

Like it seems to be a bug specific to Arch, I open a bug report in the
archlinux bugtracker (https://bugs.archlinux.org/task/26811) and close this
one.

####

#9

Updated by Stéphane Maniaci about 2 years ago

  * **File** gdb.txt added

I can reproduce this with Shotwell 0.11.1 (git checkout shotwell-0.11.1,
compiled with valac 0.12.1). Git master works fine (and looks great with
GTK3!). Adam, can you reproduce this on Fedora 16? The default yum package has
the crash for both my laptop and desktop machines. EDIT: ignore that last
part, we know that 0.10 has the bug. Can you reproduce when compiling 0.11?

Attaching the gdb backtrace here, since #3637 doesn't have the same segfault
message.

####

#10

Updated by Adam Dingle about 2 years ago

  * **Resolution** deleted (<strike>_fixed_</strike>)

On Fedora 16, I can reproduce this in 0.11.6. In git master, everything works
fine.

####

#11

Updated by Adam Dingle about 2 years ago

  * **Status** changed from _Open_ to _5_
  * **Resolution** set to _fixed_

On Fedora, we were able to reproduce this in Shotwell 0.11 but not in git
master, so I presume that this was fixed by the port to GTK 3. Closing.
Pierre, perhaps you could try building Shotwell from git master on Arch. If
the crash occurs there, feel free to reopen.

####

#12

Updated by Charles Lindsay 7 months ago

  * **Status** changed from _5_ to _Fixed_



--- Bug imported by chaz@yorba.org 2013-11-25 21:55 UTC  ---

This bug was previously known as _bug_ 4350 at http://redmine.yorba.org/show_bug.cgi?id=4350
Imported an attachment (id=262252)

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.