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

If debugging packages are available for your distribution, or components can be built with debug symbols included, please install them for Qt, KDELibs, and Plasma itself, as well as any applets you use, and try to regenerate the backtrace.

Additionally, do you experience these problems with a new user?

I filed bug 194706. There are NO debugging packages that I know of in my distros repos. It would seem to me that this should be a "feature" that is built into the build. Right now the only applets on the plasma desktop are the desktop folder, weather applet, moon, twitter, and the big shut down/lock screen applet. I have run the picture frrame and rss feeds too. Dolphin particularly is the only application that comes down with seg 11 and 15 but plasma also comes down on the same error codes with the dialog boxes that popup and the detail area. I can only give you the information that it gives me. At present the only "fix" I can do is killall plasma && plasma ..... then I get temporary reprieve until the next time this happens. I guess I have to say that plasma integration has "improved" since 4.0 when I was on another distribution and the whole plasma area would come down and crash the session.
The thing that **** me off is that this bug report has been glossed over and taken as invalid when it is occuring repeatedly doing the same kind of tasks. It is seriously making me consider going back to 3.5.10 which I KNOW is stable and then maybe waiting til KDE 5.0 comes out in a few years or something.

bcooksley wrote:If debugging packages are available for your distribution, or components can be built with debug symbols included, please install them for Qt, KDELibs, and Plasma itself, as well as any applets you use, and try to regenerate the backtrace.

Additionally, do you experience these problems with a new user?

You may need to contact your distribution for information on getting debugging symbols available. Given that you are also having problems with other programs such as gpg and Dolphin, I would also recommend ensuring your system is in a stable and undamaged state.

Gpg is not the issue Kgpg and gpg talking together and integrating properly with any mail program whether it be Kmail or Claws is the issue. Kgpg ate my whole keyring when for some reason it got stuck. I wasn't to thrilled with that function. Gpg on the command line does fine. UPDATE to Dolphin: I just did a 10GB wifi smb dl with the information box and it did not crash, the caveat is it was running on Xfce 4.6. So that tells me that Dolphin is stable it is the plasmas and their blinking and disappearing and finally getting to the point where either I have to killall or it just crashes by itself and restarts. Debugging symbols would involve me obtaining source code from KDE and compiling it myself. I did qt4 once and it took me 6 hrs on a different install. So I'll stick with Xfce and use the KDE apps that will run properly on it and check back periodically when there is an update in my repo. Something slowly must be getting done right because on 4.0 with another distro plasma would just bomb and crash the whole session. Now plasma crashes and the apps minus poor dolphin bite the dust. This is a fresh install, I've been running Linux/Gnu for 6 years and have used Gnome, Xfce, Fluxbox, Openbox, Awesome, Xmonad, IceWM and never had any problems with any desktop except for the 4.x series. The only time I ever had a total lockup is when Flash was released about 1.5yrs ago. Firefox and Flash did not play nice together for a lot of ppl til patch was put out.

Okay I see there is a separate Plasma sub-forum. Didn't notice that the other day. Thanks for the move.

I'm not harping on you all. Yes I am flustered with the quirkiness of Plasma. I've read the reasons why the change because the legacy code was totally unmaintainable. OK... I prefer KDE and have used it most of the time as my main desktop. It sucks that legacy code is broken and at 4.x start new code was broken too. This is the situation I have right now.

Running Xfce 4.6 with Dolphin from 4.2.3 .... I did about 30gb worth of data transfer both ways with wifi using smb in Dolphin. I'm guessing the information box is from Xfce to tell how long it is before complete, etc etc etc. Dolphin did NOT crash at all. But sure would have after 4-500 MB of data. Everything would have started flashing and Plasma would have crashed along with Dolphin. However, it did leave behind when I finally found the culprit over 3gb of /tmp files in kde-$user directory. Why after 2 hours before when I closed the application were there still temp files in queue? These files were numeric prefixes with a .part suffix. I'm glad the file transfers succeeded but question what needs to be done to make sure Dolphin cleans up after itself. Having to manually delete them after preforming these kind of operations is really not optimal.

GK

The part files are merely partly completed file transfers, and are usually only left behind on the file destination. This is possibly a bug in the Samba KIO slave, which should be reported at bugs.kde.org.