| Summary: | [abrt] virt-manager-0.9.0-7.el6: IA__gdk_draw_pixbuf: Process /usr/bin/python was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Stanislav Graf <sgraf> | ||||||
| Component: | virt-manager | Assignee: | virt-mgr-maint | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.2 | CC: | dallan, gkong, hjiang, jwu, mzhan, rwu, yupzhang, zpeng | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:0325261a7b601eaf97ec287f1f61243bb7d3dc41 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-07-24 17:04:29 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Stanislav Graf
2012-03-21 17:41:42 UTC
Created attachment 571794 [details]
File: backtrace
Created attachment 571795 [details]
File: maps
Dear Stanislav Graf, I tried to reproduce this bug with the following packages: virt-manager-0.9.0-7.el6.x86_64 kernel-2.6.32-220.7.1.el6.x86_64 abrt-2.0.8-1.el6.x86_64 since abrt-2.0.5 is not existed. But i could not reproduce it. And i also use other different versions of virt-manager, kernel, and abrt. However i could not reproduce it either. Could you please tell me more details about how to reproduce it? Thank you very much. I do something like this: (1) Network setup: br0(eh0) - ip address assigned wlan0 - up but not connected (2) Start virt-manager I have there local connection and also some qemu/ssh on br0(eht0) network. (3) Hibernate (still wired network, dock-station, no wifi connected) - use virt-manager - at the and of work, be sure to disconnect from all hosts/connections - also no local VM is running (4) Resume in different network No wired network, no dock-station, wifi connected br0(eh0) - no cable connection wlan0 - up and ip address assigned (5) Wait couple of minutes without touching virt-manager --- I will try to reproduce again. Given lack of clear reproducer, moving to 6.4 I cannot reproduce this bug by following comment 5. Version-Release number of selected component (if applicable): 2.6.32-220.7.1.el6.x86_64 abrt-2.0.8-1.el6.x86_64 virt-manager-0.9.0-7.el6.x86_64 Steps: 1. Update kernel and abrt to above builds. 2. Launch virt-manager; 3. Click "Edit->Connection Details->Network Interface"; 4. Add a Bridge, set it as "copy configure from eth0"; 5. Connect to localhost and an ssh remote connection through br0. 6. Disconnect all of them and bring host into hibernate. 7. Unplug the network cable. 8. Power on the host and connect to a wireless network. 9. Waiting. Actual result: 1. Nothing happened after step 9. Is there anything wrong in my steps? I've tried several times but it is always OK. Can you provide some suggestions? I tried several times to reproduce too, but I also cannot reproduce. I think I got this error twice (one time in this BZ, the other time I accidentally destroyed coredump). If backtrace doesn't provide any useful information, feel free to close the bug. I will reopen or create new one if I get this error again. Thank you for your comments. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. (In reply to comment #8) > I tried several times to reproduce too, but I also cannot reproduce. I think > I got this error twice (one time in this BZ, the other time I accidentally > destroyed coredump). If backtrace doesn't provide any useful information, > feel free to close the bug. I will reopen or create new one if I get this > error again. > > Thank you for your comments. Ok, thanks for the report. |