Bug 505273
Summary: | Nautilus help crash | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alessandro Nazzani <alessandro.nazzani> | ||||||||||
Component: | yelp | Assignee: | Matthew Barnes <mbarnes> | ||||||||||
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | low | Docs Contact: | |||||||||||
Priority: | low | ||||||||||||
Version: | 11 | CC: | mbarnes, mcepl, pmarion19, tbzatek | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | i686 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2009-06-29 04:31:07 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: |
|
Can you please either grab bug-buddy output or manually grab the backtrace? https://fedoraproject.org/wiki/StackTraces Reassigning to yelp, common gnome help viewer. Also, please post an address which document crashes the help viewer (before clicking on the "Keyboard Accessibility Monitor Manual" or such link, right click and select "Copy Link Address"). Nautilus' manual should be part of the Gnome Desktop User Guide Please post version of your 'yelp' and 'xulrunner' packages Created attachment 347422 [details]
Backtrace
I'm fairly new to gdb, so I hope I did it correctly: 1) issued command "gdb yelp" 2) run 3) reproduced the problem (no crash log this time) 4) saved the terminal output (see attachment) > please post an address which document crashes the help viewer file:///usr/share/gnome/help/accessx-status/C/accessx-status.xml#gosnautilus-27 > Please post version of your 'yelp' and 'xulrunner' packages $ yum list yelp Loaded plugins: refresh-packagekit Installed Packages yelp.i586 2.26.0-3.fc11 installed $ yum list xulrunner Loaded plugins: refresh-packagekit Installed Packages xulrunner.i586 1.9.1-0.20.beta4.fc11 installed HTH. Alessandro The process exited with SIGABRT, however it should be possible to grab backtrace anyway, showing the place where it failed. To get stacktrace, use these steps: https://fedoraproject.org/wiki/StackTraces#Obtaining_a_stack_trace_using_just_GDB Created attachment 347534 [details]
Stacktrace
My bad, apologies. The 3rd attachment is the snippet of the final part of the session. Good, now please install all required debuginfo packages according to https://fedoraproject.org/wiki/StackTraces#What_is_debugging_symbols.2C_and_why_are_they_important.3F You should see gdb reporting something like Missing separate debuginfo for /usr/lib/librarian.so.0 Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/41/11dac6cd104d86a74791addc7f3b7f8690e204.debug Oh my! Are you saying I have to run ALL the "Try: yum --enablerepo..." lines I find in the stacktrace? That's quite a lot of work (100, maybe more): any way to automate it somehow? Never mind: script working right now... :) Created attachment 347575 [details]
Stacktrace 2
Full session stacktrace uploaded after debuginfo packages installation. Regards. Good work! Thank you for the trace, now yelp developers should have enough information to fix this bug. An identical bug has been reported upstream, so I'll refer you there. Please see [1] for further updates. [1] http://bugzilla.gnome.org/show_bug.cgi?id=530589 *** Bug 539474 has been marked as a duplicate of this bug. *** |
Created attachment 347366 [details] Crash log Description of problem: Nautilus help crashed Version-Release number of selected component (if applicable): 2.26.3 How reproducible: Always Steps to Reproduce: 1. Open Nautilus help 2. Search for "side pane" (without quotes) 3. Click on the first result (Keyboard Accessibility Monitor Manual) Actual results: Window apparently hangs: mouse cursor indicates some activity but nothing seems to happen until I click a second time on the link. At this point I get a crash report (see attachment). Expected results: Additional info: