Description of problem:
Testing initial-setup with a new user. The dialog box to add accounts comes up fine. I selected facebook, didn't enter any details and clicked cancel. At this time, it crashed.
Going to create another account and confirm this behaviour.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 magazine_chain_pop_head at gslice.c:545
#1 thread_memory_magazine1_alloc at gslice.c:848
#2 g_slice_alloc at gslice.c:1007
#3 g_slist_prepend at gslist.c:267
#4 prepend_and_ref_widget at gtktooltip.c:707
#5 gtk_grid_forall at gtkgrid.c:546
#6 child_location_foreach at gtktooltip.c:763
#11 gtk_window_forall at gtkwindow.c:7611
#12 _gtk_widget_find_at_coords at gtktooltip.c:894
#13 find_topmost_widget_coords_from_event at gtktooltip.c:937
Created attachment 820798 [details]
Created attachment 820799 [details]
Created attachment 820800 [details]
Created attachment 820801 [details]
Created attachment 820802 [details]
Created attachment 820803 [details]
Created attachment 820804 [details]
Created attachment 820805 [details]
Created attachment 820806 [details]
Created attachment 820807 [details]
Created attachment 820808 [details]
Reproduced this again. Steps:
- Create new user
- Logout and in as new user
- in g-i-s, reach "add accounts" step
- Click "add"
- Select owncloud/facebook/flickr/windows-live/exchange/other (anything other than google apparently)
- Do nothing, click cancel
- Accounts list dialog disappears and g-i-s crashes
seen in f20 live RC5 desktop x86_64 also
(D/L from Koji)
In VirtualBox install after reboot and in g-i-s; clicked on add account (facebook) then [cancel] button
got same error and behavior
on power off/reboot; login g-i-s reappears and finishes. No damage seems to have occurred to install
Has this been filed upstream? If not, can someone do so? It's usually a good idea for GNOME bugs.
During the Gnome initial setup process, on the Online Accounts page, click the "Add account" button and Cancel without adding any account. This will kill the gnome-initial-setup process.
reason: Process /usr/libexec/gnome-initial-setup was killed by signal 11 (SIGSEGV)
runlevel: N 5
This has been fixed upstream, but the fix has not made it downstream, I don't believe. It would be nice if it could. Proposing as a Final freeze exception (initial-setup bugs can't be fixed post-release, naturally).
FWIW, I found a different way to hit this crash, described in https://bugzilla.gnome.org/show_bug.cgi?id=719458 .
gnome-initial-setup-22.214.171.124-3.fc20 has been submitted as an update for Fedora 20.
126.96.36.199-3.fc20 works fine
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-initial-setup-188.8.131.52-3.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
gnome-initial-setup-184.108.40.206-4.fc20 has been submitted as an update for Fedora 20.
Discussed at 2013-12-02 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-02/f20-blocker-review-%234.2013-12-02-17.02.log.txt . Accepted as a freeze exception issue as a bug that obviously can't be easily fixed post-install, gives a bad user experience, and is relatively easy to hit.
gnome-initial-setup-220.127.116.11-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.