Version: [ installed ] - kdebase-runtime-4.2.3-i486-1 [ installed ] - kdebase-workspace-4.2.3-i486-1 [ installed ] - kdeplasma-addons-4.2.3-i486-1 (using KDE 4.2.3) Compiler: Linux[ installed ] - gcc-4.3.3-i486-3 [ installed ] - gcc-g++-4.3.3-i486-3 OS: Linux Installed from: Slackware Packages System: Host vampypengy Kernel 2.6.29.2-smp i686 (32 bit) Distro Slackware 12.2.0 CPU: Dual core Intel T2060 (SMP) cache 1024 KB flags (sse3 nx) bmips 6384.5 Clock Speeds: (1) 1600.00 MHz (2) 800.00 MHz Graphics: Card Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics Controller X.Org 1.4.2 Res: 1024x768@61.0hz GLX Renderer Mesa GLX Indirect GLX Version 1.4 (2.1 Mesa 7.0.2) Direct Rendering No Audio: Card-1 Intel 82801G (ICH7 Family) High Definition Audio Controller driver HDA Intel Card-2 Logitech Inc. QuickCam Messanger driver snd-usb-audio Sound: Advanced Linux Sound Architecture Version 1.0.18a Network: Card-1 Broadcom BCM4311 802.11b/g WLAN driver b43-pci-bridge Card-2 Realtek RTL-8139/8139C/8139C+ driver 8139too v: 0.9.28 at port 2000 Disks: HDD Total Size: 80.0GB (30.9% used) 1: /dev/sda FUJITSU MHV2080B 80.0GB Partition: ID:/ size: 10G used: 6.1G (64%) ID:/home size: 63G used: 24G (39%) ID:swap-1 size: 0.50GB used: 0.00GB (1%) Info: Processes 170 Uptime 2 days Memory 727.9/3027.8MB Client Shell inxi 1.0.11 I do not have any back trace information from the segfaults because that is what the dialog boxes that popup tell me. I have KDE 4.2.3 in Slackware - current and use Dolphin for a file manager to transfer files over wifi within my network. These transfers have been large amounts of data... ie GB's worth. Also when I am ripping a DVD/CD the plasma process is segfaulting. The only way to describe it is that randomly each plasma item, cashew, panel, panel items, widgets on the desktop will flash white and might come back or just disappear. This goes on til a majority of the plasma processes have literally disappeared from the screen. No active programs that are running on the activity/plasma desktop crash except for Dolphin. Man I hate how Konqeuer got raped. Anyway no one has responded to me for days that I have been in #kde on freenode so I'm coming here. There are a few other minor glitches like gpg and email programs not talking properly to one another and not signing/encrypting emails or as a wonderful present getting your whole keyring hosed. I wasn't too thrilled about that one. Thunderbird/Enigmail and FireGpg are the only apps I can use for email and have gpg signing/encrypting capabilities. Lastly, when I pull on the cashew and get an activity view to start more activities why do my cpu cycles/usage jump dramatically to over 50% use when before doing the switch I might have had 5%? Vi^3PP Addition because it happened again with a file transfer using smb over wifi. This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb5e5a8e0 (LWP 18942)] (no debugging symbols found) (no debugging symbols found) 0xb659a23c in nanosleep () from /lib/libc.so.6 [Current thread is 0 (process 18942)] Thread 1 (Thread 0xb5e5a8e0 (LWP 18942)): #0 0xb659a23c in nanosleep () from /lib/libc.so.6 #1 0xb659a05f in sleep () from /lib/libc.so.6 #2 0xb78cef28 in ?? () from /usr/lib/libkdeui.so.5 #3 0x00000000 in ?? () #0 0xb659a23c in nanosleep () from /lib/libc.so.6
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.