Bug 831444
Summary: | [abrt] NetworkManager-gnome-0.9.4.0-9.git20120521.fc17: __GI_raise: Process /usr/bin/nm-connection-editor was killed by signal 6 (SIGABRT) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jerry James <loganjerry> | ||||||||
Component: | gtk3 | Assignee: | Matthias Clasen <mclasen> | ||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 17 | CC: | 0601422, 100domicil, bbarros, danw, dcbw, gopal.iiit, hyperthinker1024, jklimes, mclasen, sabitzer, w_pirker | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:3d9c59e0fbf1d95a982ce49a92ac36a1883c1012 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-08-01 04:04:30 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
Jerry James
2012-06-13 01:00:36 UTC
Created attachment 591309 [details]
File: backtrace
Created attachment 591310 [details]
File: maps
Created attachment 591311 [details]
File: dso_list
It looks like a bug in GTK to me. Are you able to reproduce? Btw, I *can* see .crt in supported certificate extensions. What authentication type did you choose? Would you mind attaching a screenshot? I poked at this a little yesterday, and noticed that the dialog doesn't just filter by file extension, it actually checks the content of the files too. So if you have a ".crt" file that isn't a valid PEM-encoded certificate in one of the formats network-manager-openvpn recognizes, then it won't show up. I can't reproduce. When I tried, I saw .crt in the completion list, it opened my certificate file successfully, and the VPN connection is now set up and functioning. I don't know what happened that first time, but it wasn't letting me choose the same certificate file that is now in use. *** Bug 832422 has been marked as a duplicate of this bug. *** I opened a torrent link from Firefox. It happened numerous time. No pattern that I can see. backtrace_rating: 4 Package: transmission-gtk-2.50-3.fc17 OS Release: Fedora release 17 (Beefy Miracle) Fresh installation of fedora 17 and rhythmbox (via graphical yum). When trying to "import" my music-collection rhythmbox crashed (during scan of collection). backtrace_rating: 4 Package: rhythmbox-2.97-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) when submitting a similar bug via abrt, it showed that it might be a duplicate of this bug (831444). https://bugzilla.redhat.com/show_bug.cgi?id=880791 This happens when trying to open a torrent, When another one has not been confirmed added. *It has been happening since Fedora 15. In the exact same way, With Transmission GTK+ and Firefox. Not only will it then lose the recently added torrents but will load one I have not added in weeks, even months. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed. |