Sorry for late feedback, but I installed the update just yesterday. It's crashing on every startup with SIGTRAP. See https://retrace.fedoraproject.org/faf/reports/2112642/ and https://retrace.fedoraproject.org/faf/reports/2226345/ . Unfortunately I can't seem to be able to report it using abrt as the retrace server says it's an uknown package and refuses to run a retrace job and I don't have time and bandwith to generate the stack trace locally.
@rathann: I'm not able to reproduce this for whatever reason. I didn't notice it when I was testing the update. As it turns out, on one of my test machines, I was actually hit by #1577571 (presumably totally unrelated to your issue), so I wasn't getting notifications at all there. But where they do work, I haven't encountered this (I just re-tested manually using notify-send). There must be something specific about your environment that's different.
This update has been submitted for testing by raveit65.
This update has been pushed to testing.
No regressions noted.
This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
This update has been submitted for batched by raveit65.
This update has been submitted for stable by raveit65.
This update has been pushed to stable.
Sorry for late feedback, but I installed the update just yesterday. It's crashing on every startup with SIGTRAP. See https://retrace.fedoraproject.org/faf/reports/2112642/ and https://retrace.fedoraproject.org/faf/reports/2226345/ . Unfortunately I can't seem to be able to report it using abrt as the retrace server says it's an uknown package and refuses to run a retrace job and I don't have time and bandwith to generate the stack trace locally.
@rathann: I'm not able to reproduce this for whatever reason. I didn't notice it when I was testing the update. As it turns out, on one of my test machines, I was actually hit by #1577571 (presumably totally unrelated to your issue), so I wasn't getting notifications at all there. But where they do work, I haven't encountered this (I just re-tested manually using notify-send). There must be something specific about your environment that's different.