Registered Member
|
I cannot get into the desktop to post lots of information on this issue.
My main computer, which is AMD64, HP Pavilion dv8000 all of a sudden is getting a seg fault upon loading the desktop. I ran Gparted live to check disk for errors but it persists. I am using Debian latest release stable with backports, did a dist-upgrade via the console but still no desktop. Please help. |
Manager
|
1st determine if the issue is a config file by creating and testing a new user
did this occur after an upgrade? |
Administrator
|
Also, can you please mention which application is crashing - the KDE Crash Assistant should give the name of the application which crashed.
If you would like to fix your existing user account (if a new one works) then please post the contents of the "Developer Information" tab.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Thanks for quick answer. The application that was crashing was plasma-desktop. I did not respond earlier because I am not getting those "Topic reply notification" emails, but that is another issue. I finally did manage to get into the desktop (writing from it), after going into recovery mode. Then I removed the wicd-client widget. I am now consistently being able to access the desktop but wicd is still misbehaving, that is the reason why I installed that widget, in order to try to remedy. I am not sure that this is a KDE issue, because my little netbook has both the KDE nemo and wicd and it works fine, it could be a problem with the amd64 arch of the problem machine. Anyway, will post the whole issue in the Debian forums and continue to troubleshoot. Will post here if I can find out what exactly was causing plasma-desktop to crash. Best regards. |
Administrator
|
Unusual - I have never had problems receiving these, although you are not the first to report that they are not arriving for some reason. Could you please PM me the provider of your email account, so I can investigate? With regards to the Plasma Desktop crash - generating a "backtrace" using the Developer Information tab, and posting that here would be a good step to determining the reason for the crash. The Wicd Client widget you are referring to - is this an actual Plasma applet, or is it a system tray application?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Hi Mr. Cooksley, thanks for being so dedicated. Regarding notifications, I just checked my profile and it is correct: my email is there, it is working, and I am allowing emails. I will PM info. Regarding the plasma-desktop crash, the wicd-client is a plasmoid you can enable if you have wicd installed, which I no longer have. It is one of those widgets just like any other: dictionary, weather forecast, etc. Wicd was behaving erratically on my system, connecting randomly, I tried to fix by enabling widget, and I am pretty sure that is what caused the plasma-desktop crash. After purging wicd and installing plasma-widget-networkmanagement everything is working so far. |
Registered Member
|
I cannot find a way to PM bcooksley so here is my email ckosloff at hardwarealien.com.
The wicd-client I am refering to is a system tray application. |
Administrator
|
I've checked the email logs - we only have a record of one email being sent to you, on the 22nd, and it was received successfully by your provider.
Private Messaging can be accessed through the user control panel (accessible via the drop down menu beside "Logged in as .."). Good to hear that Network Management is working properly for you. In this case I suspect the system tray was indeed causing the crash (although without a backtrace it is impossible to confirm). If you manage to reproduce this again, please capture the information from the Developer Information tab and post it here, so we can investigate further.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Unlikely because I completely purged wicd from the 64-bit system, but I think the systray app was the culprit because wicd was failing to connect to D-Bus, in other words the daemon was already running but the UI could not work properly. I could never fix wicd on 64-bit but it works fine in 32, cannot understand why because both computers have same configuration. On another note, I did get your email. Thanks for everything. |
Administrator
|
Not a problem - i'll investigate that email notification issue.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]