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 746280 - The app doesn't respond to request_quit() request if first run dialog is displayed
The app doesn't respond to request_quit() request if first run dialog is disp...
Status: RESOLVED INCOMPLETE
Product: gnome-software
Classification: Applications
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Software maintainer(s)
GNOME Software maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-03-16 13:00 UTC by Vadim Rutkovsky
Modified: 2017-10-24 14:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vadim Rutkovsky 2015-03-16 13:00:21 UTC 
STR:
1. Start Software
2. Run "dbus-send --session --type=method_call --dest='org.gnome.Shell' '/org/gnome/Shell' org.gnome.Shell.Eval string:'Shell.AppSystem.get_default().get_running().forEach(function (app) { app.request_quit(); });'"

Result: Software is still running

This makes Software always show up in Continuous applicationtest screenshots.

gnome-software GNOME_SOFTWARE_3_15_92-1-gefb74973fb7fe22e076befe36d21edba775fb995
Comment 1 Vadim Rutkovsky 2015-03-16 13:15:53 UTC 
This happens only if 'Welcome to Software' screen is displayed
Comment 2 Kalev Lember 2015-03-16 13:19:25 UTC 
Quitting with the first run dialog up works fine here. Here's how I tested it:

killall -9 gnome-software
gsettings reset org.gnome.software first-run
gnome-software &
gapplication action org.gnome.Software quit
Comment 3 Vadim Rutkovsky 2015-03-16 13:35:55 UTC 
(In reply to Kalev Lember from comment #2)
> gapplication action org.gnome.Software quit

This indeed closes Software, however we can't add this to Continuous as there is currently no way to know app name via shell's AppSystem interface
Comment 4 Richard Hughes 2016-02-20 21:14:28 UTC 
Isn't this a shell bug then? Is it even still relevant?