Bug 1136184
Summary: | [abrt] xfdashboard: glx_event_filter_cb(): xfdashboard killed by SIGSEGV | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Carlos Morel-Riquelme <morel.riquelme> | ||||||||||||||||||||||||
Component: | xfdashboard | Assignee: | Mukundan Ragavan <nonamedotc> | ||||||||||||||||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||||
Version: | 21 | CC: | kevin, morel.riquelme, nonamedotc | ||||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/aa4acdabe08e552654cf60913a8d120602581a8b | ||||||||||||||||||||||||||
Whiteboard: | abrt_hash:4a3c5ea8636ded903e75cfdb6c94efff87039ea5 | ||||||||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||||
Last Closed: | 2015-04-08 10:25:32 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
Carlos Morel-Riquelme
2014-09-02 06:16:49 UTC
Created attachment 933594 [details]
File: backtrace
Created attachment 933595 [details]
File: cgroup
Created attachment 933596 [details]
File: core_backtrace
Created attachment 933597 [details]
File: dso_list
Created attachment 933598 [details]
File: environ
Created attachment 933599 [details]
File: exploitable
Created attachment 933600 [details]
File: limits
Created attachment 933601 [details]
File: maps
Created attachment 933602 [details]
File: open_fds
Created attachment 933603 [details]
File: proc_pid_status
Created attachment 933604 [details]
File: var_log_messages
You get this crash every time you start it? Or is it sporadic? (In reply to Kevin Fenzi from comment #12) > You get this crash every time you start it? Or is it sporadic? yes,i have this crash every time regards Can you describe any specific action to trigger this crash so that I can try to reproduce this? Thanks for reporting this. (In reply to Mukundan Ragavan from comment #14) > Can you describe any specific action to trigger this crash so that I can try > to reproduce this? > > Thanks for reporting this. hi mukundan, well is not have a specific action, xfdashboard crash if you try to open from xfce menu, but if i run xfdashboard or /usr/bin/xfdashboard this app work fine and not crash. here is a screencast of the issue http://youtu.be/SLkM39Ad8o8 i hope this info can be helpfull regards That's rather strange ... I cannot reproduce it at all. :( I will poke further ... Hi Carlos, could you please give the latest version a go and see if the problem still persists? You can either try 0.3.1 or 0.3.2 which is currently building. Thanks! (In reply to Mukundan Ragavan from comment #17) > Hi Carlos, could you please give the latest version a go and see if the > problem still persists? > > You can either try 0.3.1 or 0.3.2 which is currently building. Thanks! Hi mukundan , well i install xfdashboard 0.3.2 from koji , and the launcher crash when i launch from the xfce menu. later abrt give me the same error , if i run xfdashboard from terminal i give this message output xfdashboard 0.3.2 [n0oir@localhost ~]$ rpm -qa |grep -i xfdashboard xfdashboard-0.3.2-1.fc21 [n0oir@localhost ~]$ xfdashboard (xfdashboard:4413): xfdashboard-CRITICAL **: Could not initialize xfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. -------------------------------------------------------------------------------- Later i install xfdashboard 0.3.1 from koji and also crash from xfce menu, but if i run from terminal this is work fine output xfdasboard 0.3.1 [n0oir@localhost ~]$ rpm -qa |grep -i xfdashboard xfdashboard-0.3.1-1.fc21.x86_64 [n0oir@localhost ~]$ it's all , i hope this can be helpfull, regards Thanks for testing! I think this possibly gives a little more information. I will also open an upstream bug report. (In reply to Mukundan Ragavan from comment #19) > Thanks for testing! I think this possibly gives a little more information. I > will also open an upstream bug report. thank mukundan , i'm not expert using the terminal , so i appreciate any tip o help , my regards :) Is this still a problem? xfdashboard-0.3.90-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/xfdashboard-0.3.90-1.fc21 Package xfdashboard-0.3.90-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing xfdashboard-0.3.90-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4221/xfdashboard-0.3.90-1.fc21 then log in and leave karma (feedback). xfdashboard-0.3.90-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/xfdashboard-0.3.90-2.fc21 xfdashboard-0.3.91-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/xfdashboard-0.3.91-1.fc21 xfdashboard-0.3.91-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. Closing this bug since 0.3.91 should have fixed this issue. Please reopen if the problem persists. |