Version-Release number of selected component:
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor: Fedora Project
runlevel: N 5
Thread no. 1 (10 frames)
#4 meta_window_unmanage at core/window.c:1389
#5 meta_wayland_surface_destroy_window at wayland/meta-wayland-surface.c:408
#6 xdg_toplevel_destructor at wayland/meta-wayland-xdg-shell.c:165
#7 destroy_resource at src/wayland-server.c:611
#8 wl_resource_destroy at src/wayland-server.c:626
#9 meta_wayland_xdg_surface_shell_client_destroyed at wayland/meta-wayland-xdg-shell.c:1429
#10 xdg_shell_destructor at wayland/meta-wayland-xdg-shell.c:1877
#11 destroy_resource at src/wayland-server.c:611
#12 for_each_helper at src/wayland-util.c:373
#13 wl_map_for_each at src/wayland-util.c:386
Created attachment 1230539 [details]
Created attachment 1230540 [details]
Created attachment 1230541 [details]
Created attachment 1230542 [details]
Created attachment 1230543 [details]
Created attachment 1230544 [details]
Created attachment 1230545 [details]
Created attachment 1230546 [details]
Created attachment 1230547 [details]
Created attachment 1230548 [details]
Created attachment 1230549 [details]
Created attachment 1230550 [details]
I was running weston-flower and clicked "Close" in its menu.
*** Bug 1406141 has been marked as a duplicate of this bug. ***
I can reproduce this bug (although it is quite unconventional and I haven't found a way to break this down to a simple reproducer):
1. you'll need a GNOME+Wayland session
2. `git clone https://github.com/exaile/exaile.git`
3. run `exaile`. If you don't want to get its config data, add `--all-data-dir=/tmp/foo` to its cmdline
4. In main menu, "Edit" click "Preferences"
5. In Preferences, page "Plugins", enable "Simple Console"
6. close the console
tested with exaile git revision 7df1418, but works with older versions too. Haven't tested newer versions because there are none ;)
These are the steps I used to get bug #1406141.
I can reproduce this bug. This happen every time I open search or replace box on POEdit.
It freezing around 1-2 seconds then crash and auto logout.
See https://bugzilla.redhat.com/show_bug.cgi?id=1408674 for more detail about poedit process
I can also reproduce this crash when I open search box in poedit, also cf #1408674
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
(In reply to Christian Stadelmann from comment #15)
> I can reproduce this bug (although it is quite unconventional and I haven't
> found a way to break this down to a simple reproducer):
Those steps don't work any more, so I guess this bug has been fixed. Upstream says so too.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.