Bug 699015
| Summary: | [abrt] telepathy-mission-control: g_str_hash: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Scotty Delicious <scottydelicious> | ||||||||||||
| Component: | telepathy-mission-control | Assignee: | Peter Robinson <pbrobinson> | ||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 19 | CC: | amit.shah, awilliam, bdpepple, bnocera, elad, gbauman, hrafn, hundred17, icj, jamescape777, jan.public, jcs, josian2200, kaj, keramidasceid, luf, marek90, maxx, mikhail.v.gavrilov, mtinberg, murray.alex, nicolas.mailhot, pbrobinson, pcfe, pedrogfrancisco, penthium2, p.mayers, redhat, reinouts, sanjay.ankur, sanne, sbogrin.bugs, ssabcew, twaugh, vamp898 | ||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:92603020fbd1e9a57b203f2e13c58b4f976fe48d | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2015-02-18 13:33:00 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
Scotty Delicious
2011-04-22 15:53:42 UTC
Created attachment 494255 [details]
File: maps
Created attachment 494256 [details]
File: dsos
Created attachment 494257 [details]
File: backtrace
Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Started empathy. I have an xmpp and an irc account in there. Empathy tries to download my xmpp contacts, but it doesn't work. It keeps spinning the 'wait-a-moment-icon'. Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Opened Empathy Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Had new messages from offline users and wanted to open them. They opened but i got this crash-report anyway (In reply to comment #6) > Package: telepathy-mission-control-5.7.11-1.fc15 > Architecture: i686 > OS Release: Fedora release 15 (Lovelock) > > > Comment > ----- > Had new messages from offline users and wanted to open them. They opened but i > got this crash-report anyway i have only two XMPP Accounts (if this matters) Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I do not know how this happened. Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I do not know how this happened. Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Typing on jabber account Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Typing on jabber account Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Just started empathy Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Facebook refuses to login or connection is lost frequently. Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Facebook refuses to login or connection is lost frequently. Package: telepathy-mission-control-5.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 17 (Rawhide) Comment ----- on log in (empathy is started as part of the user session) Package: telepathy-mission-control-5.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 17 (Rawhide) Comment ----- on log in (empathy is started as part of the user session) Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- login to user after a control-alt-backspace logout. previous session un-usable after disconnect of second display. Package: telepathy-mission-control-5.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 17 (Rawhide) Comment ----- on log in (empathy is launched as part of the session) Package: telepathy-mission-control-5.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 17 (Rawhide) Comment ----- on log in (empathy is launched as part of the session) Package: telepathy-mission-control-5.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 17 (Rawhide) Comment ----- on log in telepathy-mission-control-5.8.0-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/telepathy-mission-control-5.8.0-1.fc15 Package telepathy-mission-control-5.8.0-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing telepathy-mission-control-5.8.0-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/telepathy-mission-control-5.8.0-1.fc15 then log in and leave karma (feedback). Package: telepathy-mission-control-5.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I don't know Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Don't know. Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- just boot Package: telepathy-mission-control-5.7.11-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- just boot telepathy-mission-control-5.8.0-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. I just hit this in F16, need the fix there too... (In reply to comment #28) > I just hit this in F16, need the fix there too... what version if f-16? Its on a different release branch to f-15 looks like that was with 1:5.9.2-1.fc16.x86_64 - by the looks of yum history, I'd updated it just the morning before that comment. I just saw this with telepathy-mission-control-5.9.2-1.fc16.x86_64 on F-16 as well. Still hitting this in F-16. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Setting status to available from the GNOME shell. Created attachment 525546 [details]
abrt.log
Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- From updates-testing, crashing while opening an IRC /msg window on freenode. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- still crashes but only crashes in Gnome? Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Started empathy. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Crash when clicking on the user icon in the status tray to open the "real" chat window. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Crash when clicking on the user icon in the status tray to open the "real" chat window. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Logged in, waited for empathy to connect to the #fedora chat, clicked the icon in the notification bar. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Just died Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Logged in. Empathy connected to my accounts and it crashed. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Working with empathy. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Crash on startup. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- This probably has to with Empathy not resuming correctly after suspend. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I haven't the foggiest Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Sending message. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Trying to click on the user icon to bring up a chat window. Window came up, got the report. Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Send a message telepathy-mission-control-5.9.3-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/telepathy-mission-control-5.9.3-1.fc16 Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Clicking on user icon in the notification area in GNOME Shell. Package telepathy-mission-control-5.9.3-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing telepathy-mission-control-5.9.3-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/telepathy-mission-control-5.9.3-1.fc16 then log in and leave karma (feedback). Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Just using Empathy while connected to google talk and Lotus Sametime servers Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- i right clicked on a contact in the notification area, then in open Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I clicked on a chat notification in the bottom bar in GNOME shell. Up came an Empathy window, then this crash occurred. updated to 5.9.3 and all worked wihout a crash ( might Add i also rebooted the machine to then logged into Empathy ) Package: telepathy-mission-control-5.9.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Happened when starting empathy. I've updated to 5.9.3-1.fc16 and it seems to be working again. Thanks! telepathy-mission-control-5.9.3-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers telepathy-mission-control-5.14.0-1.fc18.x86_64 Happened again; can't say how -- abrt had flagged it and identified this bug where the problem was already reported, so re-opening. https://retrace.fedoraproject.org/faf/reports/13643/ is the other link given by abrt-gui, shows the backtrace as well as 'hits' this bug is getting. I am getting this bug report during every login with Fedora 18 beta. I just login to fresh booted system. backtrace_rating: 4 Package: telepathy-mission-control-5.14.0-2.fc18 OS Release: Fedora release 18 (Spherical Cow) It seems to me this is related to https://bugzilla.redhat.com/show_bug.cgi?id=889623 (i.e. the crash in mission-control-5 may be either causing or caused by the crash in empathy)? Crash on F19 duped to this I seem to have this from an evolution instance? All my imap/microsoft exchange accounts disappeared and this crash message came up. This was just after gnome-online-accounts crashed. Not really sure which one triggered it. This problem persists in Fedora 19 Beta TC4. It is reported immediately after login as a FreeIPA user. The problem does not occur after a login as a local user. Also happens on latest F19 bits with local login (no freeipa). lol this Bug exists since 2 years and is still not fixed. Well I never expected it to he fixed, I expected that like with the most bugs they get automatically closed because the fedora version is no longer supported, but this is just ridiculous. Especially that this bug doesn't appear on any other distribution. I would recommend to close this bug and tell its a feature to check if abrt is working properly, that's the last way to get this bug closed while keeping a face. The people are used to this Bug since Fedora 15 and some may already built a relationship with it and would actually miss it. Some may even fell in love with it and would loose there sense in live without this bug. (In reply to Vamp898 from comment #70) > lol this Bug exists since 2 years and is still not fixed. > > Well I never expected it to he fixed, I expected that like with the most > bugs they get automatically closed because the fedora version is no longer > supported, but this is just ridiculous. > > Especially that this bug doesn't appear on any other distribution. > > I would recommend to close this bug and tell its a feature to check if abrt > is working properly, that's the last way to get this bug closed while > keeping a face. > > The people are used to this Bug since Fedora 15 and some may already built a > relationship with it and would actually miss it. Some may even fell in love > with it and would loose there sense in live without this bug. Please stop ranting on bugzilla. If you see the comment thread, multiple updates have attempted to fix the bug. Rather than rant, why don't you do something constructive like file it with the upstream tracker at bugzilla.gnome.org? It'd take less time than it took you to type that useless comment. Please, I insist that you not rant over bugzilla in the future. It's not the place to do it. Warm regards, Ankur Dear Ankur, im not able to reproduce this bug in Archlinux or Gentoo so i dont see any need to file an upstream bug. As Archlinux uses an nearly Vanilla GNOME and Gentoo also it seems rather like an packaging/pre-configuring/patching issue in RedHat. Why not just stop useless brandings, patches and pre-configurings and deliver Vanilla Software. The Developers created the software without this bug so why even include it? Save zjr time and give developers more time to do constrctive stuff. 2 years is _way_ to long for an bug that can't be reproduced in other distributions and so highly look distribution specific. As long Red Hat/Fedora developers dont stop to break upstream packages, such bugs cant be purged completely. We are here on the Bug-Tracker to purge bugs and the purge this bug we have to accept that something went terribly wrong here. 2 years, 5 fedora Versions, some people can reproduce it every reboot and only fedora does have it. I made the sad experience that sometimes ranting is the only way to get developers to fix a bug and after such a long time its really needed. Sorry for that but i wonder why it was even released with such a bug as nearly everyone is able to reproduce it. How do i have to imagine the conversation? "Hey there is a bug which appears on every login and nearly everyone is able to reproduce it.... release it anyway, they wont notice". To fix such bugs in the future there are 2 things needed 1. provide Vanilla Software 2. Give the people the possibility to test such Software without breaking the whole system. Nobody wants a broken system and only very few people install separated test-machines and thats why such bugs starting to exist. Gentoo and Archlinux can do it too, why not fedora? This bug is not only "Telepathy mission control annoys on login", its rather "fundamental problems in the distribution keep bugs like this alive" There should be a Bug called "Fundamental Fedora problems" and this bug should depend on that bug. That would be a proper workflow. There is really nothing that much productive a user can say about this bug. It crashes, it crashes only in Fedora --> nothing more to say --> Fedora Developers have to take a look and it seems like they are not able to fix it in 2 years so something _have_ to change finally. Please do stop ranting. > im not able to reproduce this bug in Archlinux or Gentoo so i dont see any > need to file an upstream bug. As Archlinux uses an nearly Vanilla GNOME and > Gentoo also it seems rather like an packaging/pre-configuring/patching issue > in RedHat. Just because you can't reproduce it in other distros it doesn't mean it's not an upstream bug. We use vanilla non modified upstream source. > Why not just stop useless brandings, patches and pre-configurings and > deliver Vanilla Software. The Developers created the software without this > bug so why even include it? Save zjr time and give developers more time to > do constrctive stuff. We do. Our sources for the package are here and there's not a single patch and we use pretty vanilla config options. http://pkgs.fedoraproject.org/cgit/telepathy-mission-control.git/tree/ > 2 years is _way_ to long for an bug that can't be reproduced in other > distributions and so highly look distribution specific. Distributions are highly complex beasts and each package depends on 100s of others. > As long Red Hat/Fedora developers dont stop to break upstream packages, such > bugs cant be purged completely. In the case of telepathy-mission-control I can honestly say upstream has been pretty god damn broken over the years upstream and it's getting slowly better. > I made the sad experience that sometimes ranting is the only way to get > developers to fix a bug and after such a long time its really needed. It's rarely the way I can tell you. > Sorry for that but i wonder why it was even released with such a bug as > nearly everyone is able to reproduce it. It's not that reproducible. Yet neither you or anyone else has bothered to put a recent backtrace. > To fix such bugs in the future there are 2 things needed > > 1. provide Vanilla Software We do. > 2. Give the people the possibility to test such Software without breaking > the whole system. How does this bug "break the whole system"? > This bug is not only "Telepathy mission control annoys on login", its rather > "fundamental problems in the distribution keep bugs like this alive" > > There should be a Bug called "Fundamental Fedora problems" and this bug > should depend on that bug. That would be a proper workflow. I would hardly call it a show stopper or a "Fundamental Fedora problems" and there's a lot worse issues than a few crashes in recent releases. Looking back through the bug I can see the following stats: * XX total abrt updates on this bug * 45 of those were <= Fedora 16 * No crashes reported in F-17 at all * 3 on F-18 but not one has put a new back trace or any details on the F-18 reports * 3 circumstantial reports for F-19 but there has been no back trace with debug symbols attached > It crashes, it crashes only in Fedora --> nothing more to say --> Fedora > Developers have to take a look and it seems like they are not able to fix it > in 2 years so something _have_ to change finally. So I don't think the two are actually related. There's probably a snippet of code that makes the new ones look like the old one to the auto tools. So if you really do want it fixed I need the following technical details rather than crappy rants of useless information. Details needed: * a full recent back trace with all debug symbols so I can debug it. * A list of all types of accounts you have configured in Empathy and Gnome online accounts. I have configured MSN, three IRC, three XMPP/Jabber accounts and I don't see any crashes on it and haven't since the fix in F16 Hello Peter, I'm one of the reporter with F18. * it's not my problem that abrt didn't include newer back trace :( and also nobody asked me for new one * I have no Empathy account and also no Gnome online account. Can you give me a hint what debug symbols packages I need to install? (In reply to Ludek Finstrle from comment #74) > Hello Peter, > > I'm one of the reporter with F18. > > * it's not my problem that abrt didn't include newer back trace :( and also > nobody asked me for new one > * I have no Empathy account and also no Gnome online account. > > Can you give me a hint what debug symbols packages I need to install? It depends on your system. If you run through the initial bits of a abrt report it should be able to generate it for you if you select the local option and before you submit it you can view it and cut and paste it into a text file to attach here There is a 'debuginfo-install' command you can use: 'debuginfo-install telepathy-mission-control' should get most of what you need. I don't know if this helps but in fairly quick succession I had bz #889623 at 10:26:47, then bz #905168 or #827158 (which may be unrelated, I installed the update-testing clutter 1.12-2 anyway) then at 11:13:56 when I logged out I got this bug which abrt says is linked to https://retrace.fedoraproject.org/faf/reports/18366/ It would seem that the telepathy and empathy issues might be related in some way. HTH Telepathy is the backend for Empathy. Created attachment 755459 [details]
ABRT trace directory
Can people confirm if they get the crash only if they don't have any gnome-online-accounts configured. Can people confirm if they get the crash only if they don't have any gnome-online-accounts or empathy accounts configured. (In reply to Peter Robinson from comment #81) > Can people confirm if they get the crash only if they don't have any > gnome-online-accounts or empathy accounts configured. I have accounts in g-o-a configured with a gmail and a facebook account. I experience this crash too. I haven't been able to reproduce this at will though so I'm really not certain of what triggers it. Warm regards, Ankur (In reply to Peter Robinson from comment #81) > Can people confirm if they get the crash only if they don't have any > gnome-online-accounts or empathy accounts configured. I have google and facebook chat accounts configured through GOA as well as an additional Jabber, IRC, and zeroconf accounts configured directly in empathy as those types aren't exposed in the system Settings app. I don't have gnome-online-accounts but should have empathy accounts (though empathy have not been working for months in rawhide due to a run-time dependence on a gl .so file which is not present in the repo. Yay for not exposing your needs in package metadata) Just hit this in a VM in which I was testing the fix for https://bugzilla.redhat.com/show_bug.cgi?id=968951 . I fresh installed F19 Final TC5 from DVD, created a user in gnome-initial-setup , configured an Owncloud account for that user, went into Settings, created a new user account, logged out of user1 and logged in as user2, completed g-i-s for user2, verified that the Owncloud account of user1 was not present in user2's configuration (that's 968951), logged out of user2 and back into user1, at which point I saw this crash. This has happened to me once again. Here is how I think have triggered this bug. 1. Run kinit 2. Change password with kpasswd 3. A while later notice there are two kerberos accounts under GOA 4. Remove one of the kerberos accounts so that only one remain ABRT caught the crash immediately after I did step 4. Sorry, I should have mentioned that I have logged out and the logged in back again between steps 2. and 3. I can confirm Erwan's repro in comment #86 - using the new "multiple cred cache" if you have two, and remove one via g-o-accounts, the backtrace happens. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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. I at least had this in F19, so bumping. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. |