Created attachment 1328744 [details]
File: backtrace

Created attachment 1328745 [details]
File: cgroup

Created attachment 1328746 [details]
File: core_backtrace

Created attachment 1328747 [details]
File: cpuinfo

Created attachment 1328748 [details]
File: dso_list

Created attachment 1328749 [details]
File: environ

Created attachment 1328750 [details]
File: limits

Created attachment 1328751 [details]
File: maps

Created attachment 1328752 [details]
File: open_fds

Created attachment 1328753 [details]
File: proc_pid_status

Created attachment 1328754 [details]
File: var_log_messages

Similar problem has been detected:

I tried to launch GNOME Boxes and it crashed after a few seconds, without even interacting with it. Meanwhile, 9 SELinux prompts appeared. 

reporter:       libreport-2.9.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: boxes_app_setup_default_source_co
executable:     /usr/bin/gnome-boxes
journald_cursor: s=0e7f738497d44b6b9af11ec981092452;i=95627;b=e88fd4c63f314a13baa67f49ed112acf;m=c06d92a2;t=55c0a75445246;x=c6da61d781a871be
kernel:         4.13.8-300.fc27.x86_64
package:        gnome-boxes-3.26.1-2.fc27
reason:         gnome-boxes killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1510707 has been marked as a duplicate of this bug. ***

*** Bug 1516846 has been marked as a duplicate of this bug. ***

*** Bug 1520790 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Crash if .local/share/gnome-boxes is a broken symlink.

reporter:       libreport-2.9.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: boxes_app_setup_default_source_co
executable:     /usr/bin/gnome-boxes
journald_cursor: s=2f7fdcb0425b428293e3a5f3816bd107;i=38b0;b=5667eac1d67741d88116230adac8df31;m=36fb73f8;t=55fd2dc4a52cf;x=bf853d5d521b6a7c
kernel:         4.13.9-300.fc27.x86_64
package:        gnome-boxes-3.26.1-4.fc27
reason:         gnome-boxes killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1026

Similar problem has been detected:

No se la causa simplemente inicie el programa y antes de que pudiera hacer algo me apareció el mensaje que algo salio mal

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: boxes_app_setup_default_source_co
executable:     /usr/bin/gnome-boxes
journald_cursor: s=c4d63e1fb4e1471aa1834d02fbc7f1db;i=cdf2;b=407e20828eaf486789a6a144635221b8;m=406ff1a99;t=560ca91782ecd;x=e43b8bd1bb7b40be
kernel:         4.14.6-300.fc27.x86_64
package:        gnome-boxes-3.26.2-2.fc27
reason:         gnome-boxes killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1530604 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Intial launch of Gnome Boxes on a freshly installed and up-to-date Fedora 27 copy.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: boxes_app_setup_default_source_co
executable:     /usr/bin/gnome-boxes
journald_cursor: s=7b006619224b4e10b3c0569d266cfa6f;i=9650;b=64536a0bf1f3457aba2b377b67559fbe;m=b9dfe54d7;t=5625525479e39;x=b9270de82489c3ac
kernel:         4.14.11-300.fc27.x86_64
package:        gnome-boxes-3.26.2-2.fc27
reason:         gnome-boxes killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1534637 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Click "boxes" at main menu ("applications-system-boxes") with pointing device. Application "boxes" don't start.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: boxes_app_setup_default_source_co
executable:     /usr/bin/gnome-boxes
journald_cursor: s=6bfe78c2f41b4f279a16f758a674a45b;i=787d8;b=f0a17071b76549488e7bdd91a411da06;m=3126ed36;t=5638a67c271cf;x=e92da84cfdbe2e77
kernel:         4.14.14-300.fc27.x86_64
package:        gnome-boxes-3.26.2-2.fc27
reason:         gnome-boxes killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1541275 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

By starting boxes, it crashed immediately

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: boxes_app_setup_default_source_co
executable:     /usr/bin/gnome-boxes
journald_cursor: s=e7f8edaa79af4f658c80f3b2e342ea6c;i=aafaf;b=0521700a16614fafaa5cd83a742f8b50;m=1bcdadb06;t=56477a16a90ba;x=cf33f1d4345665c8
kernel:         4.14.16-300.fc27.x86_64
package:        gnome-boxes-3.26.2-2.fc27
reason:         gnome-boxes killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1546482 has been marked as a duplicate of this bug. ***

*** Bug 1549193 has been marked as a duplicate of this bug. ***

Christophe, is there any update to this bug or any known workaround? I've been unable to use boxes for months, which impacts my normal workflow.

I don't think there are any reproducers, are there? Seems to denote something going wrong when creating/parsing ~/.config/gnome-boxes/sources/QEMU\ Session, or with the connection to qemu:///session (is 'virsh -c qemu:///session list --all' working for you when Boxes crashes at startup?)

Christophe, thanks for the quick response! Unfortunately, this isn't my area of expertise, but here is what I've got.

# cat ~/.config/gnome-boxes/sources/QEMU\ Session 
[source]
name=QEMU Session
type=libvirt
uri=qemu+unix:///session
save-on-quit=true

# virsh -c qemu:///session list --all
 Id    Name                           State
----------------------------------------------------

*** Bug 1551303 has been marked as a duplicate of this bug. ***

*** Bug 1558691 has been marked as a duplicate of this bug. ***

*** Bug 1561163 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I just run Boxes. After ~1 sec, it crashes.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        gnome-boxes
crash_function: boxes_app_setup_default_source_co
executable:     /usr/bin/gnome-boxes
journald_cursor: s=ab91be4b3f2f4fd0ab7a38ea5c88beb7;i=b2a57a;b=e746daaf2c5b4e12949c3639000ec65f;m=587b167e60;t=5688068710eb2;x=e032527747038f1d
kernel:         4.15.9-300.fc27.x86_64
package:        gnome-boxes-3.26.2-3.fc27
reason:         gnome-boxes killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

$ cat ~/.config/gnome-boxes/sources/QEMU\ Session
[source]
name=QEMU Session
type=libvirt
uri=qemu+unix:///session
save-on-quit=true

[display fc66e659-5a59-4727-8d1c-5a070c7595ec]
last-seen-name=Fedora-Python-Classroom-Live-x86_64-26-1
uuid=fc66e659-5a59-4727-8d1c-5a070c7595ec
access-last-time=1502718775015019
access-ntimes=5
access-total-time=5641


$ virsh -c qemu:///session list --all
error: failed to connect to the hypervisor
error: Cannot recv data: Connection reset by peer

I cannot provide any additional info since I am using F28 ; I also see there has been fix provided. Shouldn't we close the bug?

I can confirm that an update to F28 has fixed this issue for me. 

Additionally, gnome-boxes --checks helped to diagnose any other problems.

I would recommend this be closed - currentrelease, and reopened if this surfaces in F28 again.

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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

Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.