Bug 958697

Summary: [abrt] virt-manager-0.10.0-0.1.gitd3f9bc8e.fc19: g_settings_schema_get_value: Process /usr/bin/python2.7 was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Petr Schindler <pschindl>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: berrange, crobinso, hbrock, jforbes, michele, mkrizek, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e2fb5f52ace5c142aa0c1635d4ed6b634e2adfd2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-03 07:11:47 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: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Petr Schindler 2013-05-02 09:00:30 UTC 
Description of problem:
I was trying to set up new virtual machine when it chrased. It crashed after I choosed a installation media (which I have in pool).

Version-Release number of selected component:
virt-manager-0.10.0-0.1.gitd3f9bc8e.fc19

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/share/virt-manager/virt-manager
crash_function: g_settings_schema_get_value
executable:     /usr/bin/python2.7
kernel:         3.9.0-301.fc19.x86_64
runlevel:       N 5
uid:            1000
ureports_counter: 1
var_log_messages: May  2 10:49:42 localhost abrt[10959]: Saved core dump of pid 10635 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-05-02-10:49:41-10635 (109961216 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_settings_schema_get_value at gsettingsschema.c:640
 #3 g_settings_schema_key_init at gsettingsschema.c:751
 #4 g_settings_get_value at gsettings.c:1079
 #5 ffi_call_unix64 at ../src/x86/unix64.S:76
 #6 ffi_call at ../src/x86/ffi64.c:522
 #7 g_callable_info_invoke at girepository/gicallableinfo.c:680
 #8 g_function_info_invoke at girepository/gifunctioninfo.c:274
 #9 _invoke_callable at pygi-invoke.c:64
 #10 pygi_callable_info_invoke at pygi-invoke.c:662
 #11 ext_do_call at /usr/src/debug/Python-2.7.4/Python/ceval.c:4408
Comment 1 Petr Schindler 2013-05-02 09:00:35 UTC 
Created attachment 742539 [details]
File: backtrace
Comment 2 Petr Schindler 2013-05-02 09:00:38 UTC 
Created attachment 742540 [details]
File: cgroup
Comment 3 Petr Schindler 2013-05-02 09:00:43 UTC 
Created attachment 742541 [details]
File: core_backtrace
Comment 4 Petr Schindler 2013-05-02 09:00:49 UTC 
Created attachment 742542 [details]
File: dso_list
Comment 5 Petr Schindler 2013-05-02 09:00:51 UTC 
Created attachment 742543 [details]
File: environ
Comment 6 Petr Schindler 2013-05-02 09:00:54 UTC 
Created attachment 742544 [details]
File: limits
Comment 7 Petr Schindler 2013-05-02 09:00:56 UTC 
Created attachment 742545 [details]
File: maps
Comment 8 Petr Schindler 2013-05-02 09:01:01 UTC 
Created attachment 742546 [details]
File: open_fds
Comment 9 Petr Schindler 2013-05-02 09:01:05 UTC 
Created attachment 742547 [details]
File: proc_pid_status
Comment 10 Petr Schindler 2013-05-02 10:06:45 UTC 
I just noticed, that my user isn't in libvirt group and that libvirt group doesn't exist at all. Isn't it a bug? Shouldn't be this group created through the installation of libvirt?
Comment 11 Martin Krizek 2013-05-02 10:46:03 UTC 
I hit this when I connect an iso, virt-manager crashes. If an the is already connected, the vm machine boots fine.
Comment 12 Petr Schindler 2013-05-03 07:11:47 UTC 

*** This bug has been marked as a duplicate of bug 958641 ***