Bug 1594290 - Fedora 28 : crash in gnome-shell
Summary: Fedora 28 : crash in gnome-shell
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 28
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-22 14:25 UTC by Philippe.Berthault@Atos.net
Modified: 2019-05-28 23:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:36:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Philippe.Berthault@Atos.net 2018-06-22 14:25:02 UTC
Description of problem:
I installed Fedora 28 from scratch on a Dell x86_64 platform.

Version-Release number of selected component (if applicable):
Fedora 28 is up to date.

$ uname -a
Linux B020259-UX.frcl.bull.fr 4.16.16-300.fc28.x86_64 #1 SMP Sun Jun 17 03:02:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I'm using the GNOME default session, so it's wayland.
$ echo $XDG_SESSION_TYPE
wayland

How reproducible:
This crash has already occurred on my PC.
It seems this crash occurs when I try to past a text selected with the mouse from one window to another window or an editor with the middle mouse button but it's not systematic.

The core dump taken by Fedora is too big to be sent you. The proxy of my company (Atos) will reject the transfer.

Best Regards.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Here informations from journalctl :
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: == Stack trace for context 0x55d7ba4d1220 ==
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #0 0x7ffebaeb5ed0 b   resource:///org/gnome/shell/ui/userWidget.js:59 (0x7f3a60154560 @ 212)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #1 0x7ffebaeb5f30 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f3a740b5de0 @ 71)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #2 0x7ffebaeb6680 b   resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f3a2f854890 @ 59)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #3 0x7ffebaeb6d90 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f3a740b5de0 @ 71)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #4 0x7ffebaeb6e50 b   self-hosted:915 (0x7f3a740ebf78 @ 367)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: == Stack trace for context 0x55d7ba4d1220 ==
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #0 0x7ffebaeb5ed0 b   resource:///org/gnome/shell/ui/userWidget.js:60 (0x7f3a60154560 @ 274)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #1 0x7ffebaeb5f30 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f3a740b5de0 @ 71)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #2 0x7ffebaeb6680 b   resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f3a2f854890 @ 59)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #3 0x7ffebaeb6d90 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f3a740b5de0 @ 71)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #4 0x7ffebaeb6e50 b   self-hosted:915 (0x7f3a740ebf78 @ 367)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: == Stack trace for context 0x55d7ba4d1220 ==
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #0 0x7ffebaeb5ed0 b   resource:///org/gnome/shell/ui/userWidget.js:65 (0x7f3a60154560 @ 365)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #1 0x7ffebaeb5f30 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f3a740b5de0 @ 71)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #2 0x7ffebaeb6680 b   resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f3a2f854890 @ 59)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #3 0x7ffebaeb6d90 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f3a740b5de0 @ 71)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #4 0x7ffebaeb6e50 b   self-hosted:915 (0x7f3a740ebf78 @ 367)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: == Stack trace for context 0x55d7ba4d1220 ==
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #0 0x7ffebaeb6680 b   resource:///org/gnome/shell/ui/components/polkitAgent.js:343 (0x7f3a2f854890 @ 84)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #1 0x7ffebaeb6d90 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f3a740b5de0 @ 71)
juin 22 15:43:28 B020259-UX.frcl.bull.fr org.gnome.Shell.desktop[943]: #2 0x7ffebaeb6e50 b   self-hosted:915 (0x7f3a740ebf78 @ 367)
juin 22 15:43:28 B020259-UX.frcl.bull.fr gnome-shell[943]: Object St.Bin (0x55d7ba468940), has been already finalized. Impossible to set any property to it.
juin 22 15:43:28 B020259-UX.frcl.bull.fr gnome-keyring-pkcs11.desktop[6793]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
juin 22 15:43:28 B020259-UX.frcl.bull.fr gnome-keyring-secrets.desktop[6795]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
juin 22 15:43:28 B020259-UX.frcl.bull.fr gnome-shell[943]: Object St.Bin (0x55d7ba468940), has been already finalized. Impossible to set any property to it.
juin 22 15:43:28 B020259-UX.frcl.bull.fr gnome-shell[943]: Object St.Bin (0x55d7ba468940), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
juin 22 15:43:28 B020259-UX.frcl.bull.fr gnome-shell[943]: Object St.Bin (0x55d7ba468940), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
juin 22 15:43:28 B020259-UX.frcl.bull.fr systemd-coredump[6639]: Process 1469 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 1469:
#0  0x00007f2791df9e5b raise (libpthread.so.0)
#1  0x0000556509b02b83 n/a (gnome-shell)
#2  0x00007f2791df9fc0 __restore_rt (libpthread.so.0)
#3  0x00007f2793bd67e5 _g_log_abort (libglib-2.0.so.0)
#4  0x00007f2793bd921c g_log_writer_default (libglib-2.0.so.0)
#5  0x00007f2793bd7467 g_log_structured_array (libglib-2.0.so.0)
#6  0x00007f2793bd7ea2 g_log_structured_standard (libglib-2.0.so.0)
#7  0x00007f2791338b2b _gdk_x11_display_error_event (libgdk-3.so.0)
#8  0x00007f2791345993 gdk_x_error (libgdk-3.so.0)
#9  0x00007f27907e0ec2 _XError (libX11.so.6)
#10 0x00007f27907ddd67 handle_error (libX11.so.6)
#11 0x00007f27907dde0d handle_response (libX11.so.6)
#12 0x00007f27907de72d _XEventsQueued (libX11.so.6)
#13 0x00007f27907d0257 XPending (libX11.so.6)
#14 0x00007f279133fee9 gdk_event_source_check (libgdk-3.so.0)
#15 0x00007f2793bd0601 g_main_context_check (libglib-2.0.so.0)
#16 0x00007f2793bd0b90 g_main_context_iterate.isra.21 (libglib-2.0.so.0)
#17 0x00007f2793bd0fa2 g_main_loop_run (libglib-2.0.so.0)
#18 0x00007f27920b6de0 meta_run (libmutter-2.so.0)
#19 0x0000556509b024d8 n/a (gnome-shell)
#20 0x00007f2791a4c18b __libc_start_main (libc.so.6)
#21 0x0000556509b0262a n/a (gnome-shell)

Stack trace of thread 1471:
#0  0x00007f2791b18589 __poll (libc.so.6)
#1  0x00007f2793bd0be6 g_main_context_iterate.isra.21 (libglib-2.0.so.0)
#2  0x00007f2793bd0d10 g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007f2793bd0d61 glib_worker_main (libglib-2.0.so.0)
#4  0x00007f2793bf8f2a g_thread_proxy (libglib-2.0.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1528:
#0  0x00007f2791df552c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f2789d5dd08 n/a (libmozjs-52.so.0)
#2  0x00007f2789d5dfc5 n/a (libmozjs-52.so.0)
#3  0x00007f278a148ff0 n/a (libmozjs-52.so.0)
#4  0x00007f278a169fd6 n/a (libmozjs-52.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1472:
#0  0x00007f2791b18589 __poll (libc.so.6)
#1  0x00007f2793bd0be6 g_main_context_iterate.isra.21 (libglib-2.0.so.0)
#2  0x00007f2793bd0fa2 g_main_loop_run (libglib-2.0.so.0)
#3  0x00007f27941c16ba gdbus_shared_thread_func (libgio-2.0.so.0)
#4  0x00007f2793bf8f2a g_thread_proxy (libglib-2.0.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1522:
#0  0x00007f2791b18589 __poll (libc.so.6)
#1  0x00007f27693f8d75 n/a (libpulse.so.0)
#2  0x00007f27693ea368 pa_mainloop_poll (libpulse.so.0)
#3  0x00007f27693ea9b2 pa_mainloop_iterate (libpulse.so.0)
#4  0x00007f27693eaa60 pa_mainloop_run (libpulse.so.0)
#5  0x00007f27693f8cbd n/a (libpulse.so.0)
#6  0x00007f276919798c n/a (libpulsecommon-11.1.so)
#7  0x00007f2791def594 start_thread (libpthread.so.0)
#8  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1525:
#0  0x00007f2791df552c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f2789d5dd08 n/a (libmozjs-52.so.0)
#2  0x00007f2789d5dfc5 n/a (libmozjs-52.so.0)
#3  0x00007f278a148ff0 n/a (libmozjs-52.so.0)
#4  0x00007f278a169fd6 n/a (libmozjs-52.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1530:
#0  0x00007f2791df552c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f2789d5dd08 n/a (libmozjs-52.so.0)
#2  0x00007f2789d5dfc5 n/a (libmozjs-52.so.0)
#3  0x00007f278a148ff0 n/a (libmozjs-52.so.0)
#4  0x00007f278a169fd6 n/a (libmozjs-52.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1474:
#0  0x00007f2791b18589 __poll (libc.so.6)
#1  0x00007f2793bd0be6 g_main_context_iterate.isra.21 (libglib-2.0.so.0)
#2  0x00007f2793bd0d10 g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007f277daebe4d dconf_gdbus_worker_thread (libdconfsettings.so)
#4  0x00007f2793bf8f2a g_thread_proxy (libglib-2.0.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1523:
#0  0x00007f2791df552c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f2789d5dd08 n/a (libmozjs-52.so.0)
#2  0x00007f2789d5dfc5 n/a (libmozjs-52.so.0)
#3  0x00007f278a148ff0 n/a (libmozjs-52.so.0)
#4  0x00007f278a169fd6 n/a (libmozjs-52.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1524:
#0  0x00007f2791df552c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f2789d5dd08 n/a (libmozjs-52.so.0)
#2  0x00007f2789d5dfc5 n/a (libmozjs-52.so.0)
#3  0x00007f278a148ff0 n/a (libmozjs-52.so.0)
#4  0x00007f278a169fd6 n/a (libmozjs-52.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1529:
#0  0x00007f2791df552c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f2789d5dd08 n/a (libmozjs-52.so.0)
#2  0x00007f2789d5dfc5 n/a (libmozjs-52.so.0)
#3  0x00007f278a148ff0 n/a (libmozjs-52.so.0)
#4  0x00007f278a169fd6 n/a (libmozjs-52.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1526:
#0  0x00007f2791df552c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f2789d5dd08 n/a (libmozjs-52.so.0)
#2  0x00007f2789d5dfc5 n/a (libmozjs-52.so.0)
#3  0x00007f278a148ff0 n/a (libmozjs-52.so.0)
#4  0x00007f278a169fd6 n/a (libmozjs-52.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Stack trace of thread 1527:
#0  0x00007f2791df552c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f2789d5dd08 n/a (libmozjs-52.so.0)
#2  0x00007f2789d5dfc5 n/a (libmozjs-52.so.0)
#3  0x00007f278a148ff0 n/a (libmozjs-52.so.0)
#4  0x00007f278a169fd6 n/a (libmozjs-52.so.0)
#5  0x00007f2791def594 start_thread (libpthread.so.0)
#6  0x00007f2791b2300f __clone (libc.so.6)

Comment 1 RobbieTheK 2018-08-27 15:44:20 UTC
I'm seeing the same in F28:
Aug 27 09:23:11 sobolev journal[17017]: Object St.Widget (0x56228cfe2d70), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Aug 27 09:23:11 sobolev journal[17017]: Object St.Widget (0x56228d0aef30), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: == Stack trace for context 0x56228b3f1050 ==
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #0 0x56228b707078 i   /usr/share/gnome-shell/extensions/background-logo/extension.js:232 (0x7f94440a2a28 @ 15)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #1 0x7ffc888c40a0 b   self-hosted:251 (0x7f94583c4ab0 @ 223)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #2 0x56228b706ff8 i   /usr/share/gnome-shell/extensions/background-logo/extension.js:232 (0x7f94440a29a0 @ 17)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #3 0x56228b706f78 i   /usr/share/gnome-shell/extensions/background-logo/extension.js:225 (0x7f94440a2890 @ 10)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #4 0x7ffc888c5560 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f94583cff78 @ 386)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #5 0x56228b706ec0 i   resource:///org/gnome/shell/ui/layout.js:646 (0x7f9458203560 @ 533)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #6 0x7ffc888c6180 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f94583b5de0 @ 71)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #7 0x56228b706e40 i   resource:///org/gnome/shell/ui/layout.js:591 (0x7f94582034d8 @ 90)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #8 0x7ffc888c7460 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f94583cff78 @ 386)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #9 0x56228b706dc0 i   resource:///org/gnome/shell/ui/background.js:522 (0x7f945820bab0 @ 17)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: == Stack trace for context 0x56228b3f1050 ==
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #0 0x56228b707078 i   /usr/share/gnome-shell/extensions/background-logo/extension.js:232 (0x7f94440a2a28 @ 15)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #1 0x7ffc888c40a0 b   self-hosted:251 (0x7f94583c4ab0 @ 223)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #2 0x56228b706ff8 i   /usr/share/gnome-shell/extensions/background-logo/extension.js:232 (0x7f94440a29a0 @ 17)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #3 0x56228b706f78 i   /usr/share/gnome-shell/extensions/background-logo/extension.js:225 (0x7f94440a2890 @ 10)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #4 0x7ffc888c5560 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f94583cff78 @ 386)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #5 0x56228b706ec0 i   resource:///org/gnome/shell/ui/layout.js:646 (0x7f9458203560 @ 533)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #6 0x7ffc888c6180 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f94583b5de0 @ 71)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #7 0x56228b706e40 i   resource:///org/gnome/shell/ui/layout.js:591 (0x7f94582034d8 @ 90)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #8 0x7ffc888c7460 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f94583cff78 @ 386)
Aug 27 09:23:11 sobolev org.gnome.Shell.desktop[17017]: #9 0x56228b706dc0 i   resource:///org/gnome/shell/ui/background.js:522 (0x7f945820bab0 @ 17)


Aug 27 09:23:55 sobolev journal[17017]: The offending signal was actor-removed on ShellGenericContainer 0x56228da22be0.
Aug 27 09:23:55 sobolev journal[17017]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Aug 27 09:23:55 sobolev org.gnome.Shell.desktop[17017]: == Stack trace for context 0x56228b3f1050 ==
Aug 27 09:23:55 sobolev journal[17017]: The offending signal was destroy on StBin 0x56228da797b0.
Aug 27 09:23:55 sobolev journal[17017]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked

Comment 2 Petr Stodulka 2019-01-23 12:49:02 UTC
Not sure whether this is gnome-shell issue, as I have pretty similar problem (I don't need even middle click or pasting of text, any window is crashing randomly when I click on it with any mouse button) and I am not using any desktop environment, just openbox window manager. Similar issue has been reported to another desktop environment (do not remember which one it was). So problem is hidden somewhere deeper I guess. Anyone else with any tip? I will try to do better report when I will have time next week.

Comment 3 Petr Stodulka 2019-01-23 12:49:27 UTC
The same issue is on Fedora 29 as well.

Comment 4 Ben Cotton 2019-05-02 19:58:43 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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' of '28'.

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 28 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.

Comment 5 Ben Cotton 2019-05-28 23:36:25 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.