Bug 1476547

Summary: [abrt] gnome-initial-setup: g_variant_is_trusted(): gnome-initial-setup killed by signal 11
Product: [Fedora] Fedora Reporter: ToFabricio <ToFabricio_90>
Component: gnome-initial-setupAssignee: Rui Matos <tiagomatos>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: 181gaming, allen.welkie, flast, f_sender, ivo.n.nenchev, jstpierr, ma39isy, otugodennis, paulo, pmpcdg, redhat, rmarcand, ryan.plauche, tcfxfzoi, tiagomatos, whouh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b1bd857e0b0c138a289b6623e27f1ecb87b5ff97
Whiteboard: abrt_hash:6f7e42131e7d804a467bf44ef2d26974b54081b0;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:56:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description ToFabricio 2017-07-30 06:24:43 UTC
Version-Release number of selected component:
gnome-initial-setup-3.24.2-1.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-initial-setup --existing-user
crash_function: g_variant_is_trusted
executable:     /usr/libexec/gnome-initial-setup
journald_cursor: s=fb5f3655afd94262a117b2e0cce3e660;i=8bc;b=58b2bf6fd0224b23b587c2b3420cc876;m=1183da40;t=55586fb783bac;x=d2ccae39fbc58244
kernel:         4.11.8-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_variant_is_trusted at gvariant-core.c:607
 #1 g_variant_builder_add_value at gvariant.c:3491
 #2 g_variant_valist_new at gvariant.c:5197
 #3 g_variant_new_va at gvariant.c:5373
 #4 g_variant_new at gvariant.c:5308
 #5 nmdbus_manager_call_add_and_activate_connection at introspection/org.freedesktop.NetworkManager.c:3533
 #6 nm_manager_add_and_activate_connection_async at libnm/nm-manager.c:994
 #7 nm_client_add_and_activate_connection_async at libnm/nm-client.c:1143
 #8 row_activated at gis-network-page.c:512
 #13 gtk_list_box_activate at gtklistbox.c:1777

Comment 1 ToFabricio 2017-07-30 06:24:47 UTC
Created attachment 1306485 [details]
File: backtrace

Comment 2 ToFabricio 2017-07-30 06:24:49 UTC
Created attachment 1306486 [details]
File: cgroup

Comment 3 ToFabricio 2017-07-30 06:24:51 UTC
Created attachment 1306487 [details]
File: core_backtrace

Comment 4 ToFabricio 2017-07-30 06:24:52 UTC
Created attachment 1306488 [details]
File: cpuinfo

Comment 5 ToFabricio 2017-07-30 06:24:55 UTC
Created attachment 1306489 [details]
File: dso_list

Comment 6 ToFabricio 2017-07-30 06:24:56 UTC
Created attachment 1306490 [details]
File: environ

Comment 7 ToFabricio 2017-07-30 06:24:58 UTC
Created attachment 1306491 [details]
File: exploitable

Comment 8 ToFabricio 2017-07-30 06:24:59 UTC
Created attachment 1306492 [details]
File: limits

Comment 9 ToFabricio 2017-07-30 06:25:03 UTC
Created attachment 1306493 [details]
File: maps

Comment 10 ToFabricio 2017-07-30 06:25:04 UTC
Created attachment 1306494 [details]
File: open_fds

Comment 11 ToFabricio 2017-07-30 06:25:06 UTC
Created attachment 1306495 [details]
File: proc_pid_status

Comment 12 ToFabricio 2017-07-30 06:25:07 UTC
Created attachment 1306496 [details]
File: var_log_messages

Comment 13 Renato Marcandier 2017-08-04 10:44:21 UTC
*** Bug 1478333 has been marked as a duplicate of this bug. ***

Comment 14 ToFabricio 2017-08-07 18:17:37 UTC
Similar problem has been detected:

Fue la primera vez que inicie y la primera ventana que se abrio 

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-initial-setup --existing-user
crash_function: g_variant_is_trusted
executable:     /usr/libexec/gnome-initial-setup
journald_cursor: s=9533ead7cd654e7c9e9f35573980d552;i=817;b=e01c5701b678473c9a07d55ce0a0b018;m=1a69668e;t=5562db612e3dc;x=7595ca99670c6ca7
kernel:         4.11.8-300.fc26.x86_64
package:        gnome-initial-setup-3.24.2-1.fc26
reason:         gnome-initial-setup killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Allen Welkie 2017-08-09 01:12:59 UTC
*** Bug 1479615 has been marked as a duplicate of this bug. ***

Comment 16 paulomarcelo 2017-08-10 16:42:31 UTC
*** Bug 1480317 has been marked as a duplicate of this bug. ***

Comment 17 whouh 2017-08-30 06:26:58 UTC
Similar problem has been detected:

First GUI after install from USB stick (from windows fedora imager)
Had just chosen wifi AP and entered WPA2 passphrase
It seemed that it took a long time (90 seconds? 2 minutes?), and i clicked or double-clicked on the display line for the AP with the spinning beachball
Although it crashed, the host is now connected to the AP

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-initial-setup --existing-user
crash_function: g_variant_is_trusted
executable:     /usr/libexec/gnome-initial-setup
journald_cursor: s=c52f2bd5bcb2436590a8950086fb4b6f;i=b9d;b=afcb084decf246b8900b3531621c8085;m=81e1f04;t=557e5b2ef29be;x=ce536b3594a720d2
kernel:         4.11.8-300.fc26.x86_64
package:        gnome-initial-setup-3.24.2-1.fc26
reason:         gnome-initial-setup killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 18 Ma'isy Yazid I 2017-09-03 07:55:25 UTC
*** Bug 1487908 has been marked as a duplicate of this bug. ***

Comment 19 Paulo Matos 2017-09-03 16:14:00 UTC
*** Bug 1487948 has been marked as a duplicate of this bug. ***

Comment 20 Nicholas 2017-09-21 00:14:54 UTC
*** Bug 1493793 has been marked as a duplicate of this bug. ***

Comment 21 ivonenchev 2017-09-21 07:36:44 UTC
*** Bug 1493922 has been marked as a duplicate of this bug. ***

Comment 22 ryan.plauche 2017-10-05 02:03:49 UTC
*** Bug 1498709 has been marked as a duplicate of this bug. ***

Comment 23 Dennis W. Otugo 2017-10-05 02:58:46 UTC
*** Bug 1498713 has been marked as a duplicate of this bug. ***

Comment 24 Dmitriy 2017-11-09 07:24:24 UTC
*** Bug 1511326 has been marked as a duplicate of this bug. ***

Comment 25 Christian Kujau 2017-12-22 12:08:34 UTC
Still happening with F27: https://retrace.fedoraproject.org/faf/reports/1922941/

Comment 26 Fedora End Of Life 2018-05-03 08:31:04 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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 '26'.

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 26 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 27 Fedora End Of Life 2018-05-29 11:56:13 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.