| Summary: | data transfer crash | ||
|---|---|---|---|
| Product: | [I don't know] kde | Reporter: | GK <gm5729> |
| Component: | general | Assignee: | Unassigned bugs <unassigned-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | aseigo, zahl |
| Priority: | NOR | ||
| Version First Reported In: | 4.2.2 | ||
| Target Milestone: | --- | ||
| Platform: | Slackware | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
GK
2009-05-31 05:42:06 UTC
upgrade to 4.3beta and see how many of your problems that solves http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports We really need a backtrace to diagnose 1) and 2). 3) needs more information, and you should do a new bug report for it (Actually, 1) & 2) have nothing to do with each either also, so you should done three bug reports.) Your problems seem to be: 1) you transfer files via wifi and then ...? (plasma crashes? it says it is plasma?) I think this is a duplicate of something in kio. 2) a segfault when ripping DVDs (does the crash window say it is plasma that crashed?) What program are you using? Is it a KDE one? 3) encryption integration 4) the 5% --> 50% thing: run top, I bet X is using lots, it's probably your video drivers or something, or it might be something fixed in a later version You can get tech support on your disto's irc channel as well, and on the forums: http://forum.kde.org the cpu issue when zooming out is due to Qt performance on X11; sadly on other platforms it's rather fast. the backtrace doesn't have any information in it (perhaps install the debug packages). the issue with plasma bits and pieces not painting is covered in a few other bug reports, most (or all at this point?) have been addressed in later 4.2.x, in 4.3 and/or in Qt 4.5.x development. the issue with email/gpg (i suppose kontact?) has nothing to do with plasma. the crash related to large file transfers, could be any number of causal factors, including ones that have since been fixed. i get your frustration; it doesn't sound like you've had a great time of things. for us to help you via b.k.o, however, we will need _one report per issue_ and full backtraces of the crashes along with as much "how to reproduce" as possible (e.g. on the transfer-over-wifi thing, does it matter that it's a wifi transfer or does it happen with wired network or local transfers?) You know this majorly sux.. KDE is so screwed over now! I provided as much information as KDE gives me!!! As far as I know on a complete KDE 4.2.3 install which is the only thing in Slack repos available there is debugging integrated. I can only install what is in my repos I'm not going to take hours to put in a "beta " because obviously this "beta" isn't working. I had the same kind of issue with plasma crashing in 4.0 but at that time it didn't give me any err codes it just took down the whole session. I don't understand which part of YES it is PLASMA that is crashing. I don't know if it would happen on a wired hookup. I don't have a wired hookup available I run totally wifi. Then to fkn mark this as resolved and invalid is a crock of sht! It may have debugging, but not *kde* debugging. Check what slackware offers for support, and see if they can help you. As aseigo says, there isn't much we can do with this from what we know. There have been many many many changes since that version: we need a backtrace to tell us in what section it crashes, we can't randomly guess. And again, you can't put 5 different things into one bug report. |