Bug 1639046 - gnome-shell SIGSEGV at shell_app_dispose src/shell-app.c:1485
Summary: gnome-shell SIGSEGV at shell_app_dispose src/shell-app.c:1485
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 29
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-14 19:44 UTC by Markus Linnala
Modified: 2019-11-27 19:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 19:36:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Markus Linnala 2018-10-14 19:44:24 UTC
Description of problem:

Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007efc08be7467 in shell_app_dispose (object=0x563240bb0580) at ../src/shell-app.c:1485


Version-Release number of selected component (if applicable):

gnome-shell-3.30.1-1.fc29

How reproducible:

Always

Steps to Reproduce:
1. Install virtual F29 from Fedora-Workstation-Live-x86_64-29_Beta-1.5.iso to HD, update, reboot.
2. Install passwordsafe from:
https://copr.fedorainfracloud.org/coprs/simger/passwordsafe/
3. Start passwordsafe (pwsafe) click New... | Save | Safe: Combination: a | Verify: a | Yes

Actual results:


Gnome session ends when gnome-shell crashes

Expected results:


Passwordsafe safe window is opened.

Additional info:

I tried to report this from reporter, upload core and so on, but it says it is not possible because trace was not okay. I've tried several times and result is always the same.

Same issue was reported as #1067704 as far as I can see but no action.

https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/src/shell-app.c#L1485

1484  while (app->running_state)
1485    _shell_app_remove_window (app, app->running_state->windows->data);

Here app->running_state->windows is NULL.

Locally I was able to avoid crashing with this patch, but I'm not sure if it is right call as my gnome coding is bit rusty atm.

--- a/src/shell-app.c
+++ b/src/shell-app.c
@@ -1481,8 +1481,13 @@ shell_app_dispose (GObject *object)
 
   g_clear_object (&app->info);
 
-  while (app->running_state)
+  while (app->running_state) {
+    if (app->running_state->windows == NULL) {
+      g_clear_pointer (&app->running_state, unref_running_state);
+      continue;
+    }
     _shell_app_remove_window (app, app->running_state->windows->data);
+  }
 
   /* We should have been transitioned when we removed all of our windows */
   g_assert (app->state == SHELL_APP_STATE_STOPPED);

Comment 1 Ben Cotton 2019-10-31 20:38:26 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 2 Ben Cotton 2019-11-27 19:36:16 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.