| Summary: | ksmserver sometimes crash at logout | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Alex Couture <ac586133> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | ac586133, bugwatch, kb9vqf, luizromario2, michele.calgaro, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2246 | ||
| Attachments: |
ksmserver kcrash debug info output
Another kcrash output from ksmserver ksmserver crash backtrace |
||
Does this crash still happen if you use Plastik instead of QtCurve? Thanks! Hi, Good question! I just switched to Plastik, so I will be able to give you an answer about it in the next few hours, at worse at the beginnig of the week. Thank you! -Alexandre Hi Tim, I'm sorry, but it still does the same bug with Plastik... A strage thing is that the kcrash output was the only time I have been able to retrieve the kcrash output, because the input field of TDESUDO didn't work. I tried to plug a USB keyboard, to see if it would work, but it didn't either. By the way, I sent a few weeks ago some kcrash output for Kontact. Did someone received it? Where does the message go when it is sent from kcrash? Thank you for your hard work on TDE! -Alexandre (In reply to Alex Couture from comment #3) > Hi Tim, > > I'm sorry, but it still does the same bug with Plastik... > A strage thing is that the kcrash output was the only time I have been able > to retrieve the kcrash output, because the input field of TDESUDO didn't > work. I tried to plug a USB keyboard, to see if it would work, but it didn't > either. > > By the way, I sent a few weeks ago some kcrash output for Kontact. Did > someone received it? Where does the message go when it is sent from kcrash? > > Thank you for your hard work on TDE! > -Alexandre OK, thanks for testing that. All crash reports go here: http://crashreport.trinitydesktop.org/ Tim Hi, Ok, good to know! -Alexandre Created attachment 2241 [details]
Another kcrash output from ksmserver
Hi, Can someone take a look at the second kcrash output log? It seems to contain more info than the first one, maybe it could help to resolve the bug. Thank you! -Alexandre *** Bug 2253 has been marked as a duplicate of this bug. *** Created attachment 2450 [details]
ksmserver crash backtrace
Hi,
*** This bug really needs attention! ***
Here is another backtrace for this bug.
I am currently sticking to 3.5.13.2 because of these kind of issues...
Thank you!
-ALexandre
I'm fairly certain this is the same issue reported in Bug 2167. It was fairly difficult to track down due to being a race condition while clients were exiting, and this difficulty was compounded by the backtraces being incomplete for various reasons (e.g. distros providing invalid debug symbol packages, gcc optimizations removing debug-critical code paths, etc.) *** This bug has been marked as a duplicate of bug 2167 *** |
Created attachment 2230 [details] ksmserver kcrash debug info output Hi, On Ubuntu 14.04 with recent TDE R14 nightly build, ksmserver sometimes crash at logout. I have not been able to identify an exact cause as to when it crash at logout. As an attachment, I provided the kcrash debug info output. -Alexandre