Created attachment 54200 [details] xsession-errors Version: 4.5 (using KDE 4.5.3) OS: Linux I was using the computer with a Fedora 14 64 bit and I was running VirtualBox with Windows 7. Suddendly I got KDE very unresponsive, instead VirtualBox was ok. After a few seconds KDE got completely freezed, and I had to halt the computer by logging in shell with ctrl+alt+f2 and doing an halt command. I rebooted but when I login into KDE, the transition images of the login load at a distance of some minutes each one by the other. When KDE is finally active, the gui is freezed. I know that it is a problem of KDE because shell is ok, and when I was using VirtualBox, the virtual machine was ok. The computer is new and the rams are ok, I've tested them for 21 hours with memetest86 I attach a xsession-errors. The bug is reproducible, so if you need other logs please tell me. Hardware: Motherboard: Gigabyte 890FXA-UD5 CPU: AMD Phenom II X2 550 RAM: 4x2gb Corsair XMS 3 1333mhz DDR3 VGA: nVidia Geforce GTX 260 with nVidia drivers by rpmfusion repository Sound board: Asus Xonar Essence ST Reproducible: Always Steps to Reproduce: Just boot the computer and do a login Actual Results: GUI freezed I selected major severity because the entire system is not usuable
it happens also with nouveau drivers
No desktop effects. Attached xsession-errors using nouveau drivers
Created attachment 54225 [details] xsession-errors using nouveau driver
If nobody ask for other logs, on 15th December I will format the disk because I need the computer working.
Even if I renamed /home/~/.kde and I tried with failsafe mode, nothing had changed
I also installed Enlightenment and it works well.
Talking in IRC some people told me that it is not very clear what Virtualbox matters in this bug. So to clarify I can say that: I wrote about Virtualbox only to explain what I was doing the first time the bug happened. The computer was running Fedora 14, and Virtualbox was running Windows 7.
I reinstalled Fedora 14 and now it works well.
I just had this very same thing happen to me on 64bit Intel hardware, though I was not using virtualbox... just had a vnc viewer open and banshee... now the only way I can use the PC is command line or run GNOME. Also, I don't dare open a KDE app in GNOME or I end up having to xkill it... ---------- ---------- ---------- ---------- ---------- I get this message in xsession-errors when trying to start 'systemsettings' from a GNOME terminal: systemsettings(3443): Communication problem with "systemsettings" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " ---------- ---------- ---------- ---------- ---------- OS: Fedora 14 Hardware: Samsung qx410 laptop CPU: intel i5 m460 RAM: 4gb LSPCI info (if it's of any use): [adam@qx410 ~]$ lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05) 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) 01:00.0 3D controller: nVidia Corporation GT218 [GeForce 310M] (rev a2) 02:00.0 Network controller: Intel Corporation Centrino Advanced-N + WiMAX 6250 (rev 5f) 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8059 PCI-E Gigabit Ethernet Controller (rev 11) 3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) 3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) 3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) 3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02) 3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02) 3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02) ---------- ---------- ---------- ---------- ---------- I have since done a reinstall as this is my work machine. This time however I've started keeping LVM snapshots so if I run into the problem again I "May" be able to figure out how to reproduce it.
2 strong suspicions, something is either corrupted or broken permissions-wise in one or both of: /tmp/kde-<username> /var/tmp/kdecache-<username> Please confirm permissions/ownership of all items in there, and/or logout and remove everyting and start over. In every case I've seen or heard about, that has 100% solved the problem.
Just to let you know, today I discovered that my ram got corrupted even if a month ago they passed 21 hours of memtest. So maybe this bug could be also related to this.
Comment 10 solved all problems. Be careful with folder permission when cleaning them, or you will do a mess as I did
This bug is happening on several machines that I installed by zero
What are the permission once the folders are corrupted? and how is the owner of them?
> What are the permission once the folders are corrupted? and how is the owner of > them? Don't know, try asking to Rex Dieter
What is the status of this bug? Does it still happen with a recent KDE version, such as 4.6.5 or 4.7.x? Please add a comment.
Luckly this is not longer happening. I just have got a confirmation from a friend that has been having this problem so many times. Please check if the status I selected is correct.