| Summary: | [abrt] remmina-0.9.3-3.fc15: poll_for_event: Process /usr/bin/remmina was killed by signal 6 (SIGABRT) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brian Millett <bmillett> | ||||||
| Component: | remmina | Assignee: | Christoph Wickert <cwickert> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | cwickert, splinux25 | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://sourceforge.net/tracker/?func=detail&aid=3310803&group_id=278330&atid=1181674 | ||||||||
| Whiteboard: | abrt_hash:cd5ef27a39ebdefb4fbd0759e3d502b02aae116e | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-06-02 19:36:36 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
Brian Millett
2011-05-15 20:53:11 UTC
Created attachment 499048 [details]
File: maps
Created attachment 499049 [details]
File: backtrace
What did you do when remmina crashed? Can you reproduce the crash when you do the same again? just duplicated it. opened 5 ssh connections so one window, 5 tabs. typed 'exit' in the first, ok. it closed. Second, ok, third crash. Thansk for the feedback. I have forwarded your report to the developers at https://sourceforge.net/tracker/?func=detail&aid=3310803&group_id=278330&atid=1181674 Feel free to subscribe to the upstream bug report to get notified of any changes. I will get back to you if I need more info and let you know when the issue is resolved in Fedora. Further investigation of this crash should take place in the upstream bug tracker, therefor I am now closing this report. |