Summary: | KCMInit (kdeinit4), signal: Segmentation fault | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | pierrelud |
Component: | kdeinit | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | cfeck, silvan.calarco, wstephenson |
Priority: | NOR | ||
Version: | 4.6 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
pierrelud
2011-01-31 14:06:25 UTC
When did the crash occur? What is your distribution? Are you using NVIDIA binary drivers? When did the crash occur? >>Today 32Jan2011. When I log into KDE and KDE is starting (initializing) What is your distribution? >>openSuse 11.3 usingyast KDE 4.6 Are you using NVIDIA binary drivers? >>How would I know that? Do you know of a command I can issue? and this one also occurs at the same time https://bugs.kde.org/show_bug.cgi?id=264951 To check if you are running NVIDIA drivers, please provide the output of this Konsole command: lsmod | grep nv If you are using those, I fear this is a duplicate of or related to bug 251719. "lsmod | grep nv" returns nothing. Here is more info Vendor: ATI Technologies Inc Model: Mobility FireGL V5200 2D driver: radeon 3D driver: R300 classic (7.8.2) Thanks for the update. Since the backtrace mentions strigi, could you check if you have the newest version of strigi libraries installed? The KDE repositories from openSUSE should offer version 0.7.3.99. To check the currently installed strigi version, use "zypper info libstrigi0". If you can provide the information requested in comment #6, please add it and reopen the bug. Yes, I'm on 0.7.3.99-55.1 Hi Christoph, Where would I re-open the bug? Can't find that option. Thanks for the update. Still no idea on this crash, we probably need a valgrind log. But the backtrace doesn't even indicate which module is causing it. I had a similar problem and fixed it by upgrading soprano components from version 2.5.3 to 2.6.0. To debug kcminit crashes, enable debug output, specifically debug area 1208, and run kcminit from the command line. It will output the module it is trying to run before crashing. If this is still a problem, please do this. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |