Summary: | Start up of KDE cause a couple of SEGV (after recent update) 1 | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Christian Groove <christian.groove> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | adaptee, cfeck |
Priority: | NOR | Keywords: | reproducible |
Version: | 4.8 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
a crashinfo file on knotify4
kcminit_startup crashinfo file kded4 crashinfo file |
Description
Christian Groove
2012-06-05 04:04:27 UTC
Created attachment 71594 [details]
a crashinfo file on knotify4
Created attachment 71595 [details]
kcminit_startup crashinfo file
and other services Created attachment 71596 [details]
kded4 crashinfo file
kded4 is also dying. This prevents us to use the crashtool cause it demmand kded to run.
Please help, current state of KDE is unusable
Are you using Nvidia card and driver? See bug 286388 . By the way, please always paste backtrace inline instead of attaching it. *** This bug has been marked as a duplicate of bug 286388 *** No Sirs, this is not a NVIDIA bug. 1)Having a SEGV in kde-lib means that the KDE programmers did something wrong. 2) The NVIDIA problems i hat seen before had been already fixed. I recently had a kde update, hat messed up the login. So dear Frined: Having a SEGV on login does not mean, that the origin bug was related to a NVIDIA problem. Its a KDE problem!" > Having a SEGV in kde-lib means that the KDE programmers did something wrong. If only you could read backtraces ... *** This bug has been marked as a duplicate of bug 286388 *** |