My Salix-KDE installation had been working perfectly for last many weeks but today, on waking up from 'sleep' mode, the screen got stuck with Dolphin file manager screen (the login screen that generally come up after sleep mode did not appear), the mouse was moving but clicking did not make anything work, nor could alt-tab to change the application. It was frozen and I had to hard reboot. However, now Salix is getting stuck at KDE login screen and is not letting me log in (keeps returning back to login screen). This is despite the fact that earlier I had auto-login enabled in KDE and I never needed to login to start KDE.
Similar thing happened some weeks ago but at that time I found that the disk had become full. After making some space, it worked fine. Now there is about 400mb space but still it is not logging in.
What could be the problem and how can I solve this issue? Thanks for your help.
[SOLVED] Not able to login KDE after 'sleep' mode
[SOLVED] Not able to login KDE after 'sleep' mode
Last edited by rsal on 27. Jun 2016, 06:42, edited 2 times in total.
Re: Not able to login KDE after waking up from 'sleep' mode
what is the output of this command
choose different session type, before login. e.g. plasma, kde, default etc.
Code: Select all
cat ~/.dmrc
[Desktop]
Session=kde-plasma
Re: Not able to login KDE after waking up from 'sleep' mode
Code: Select all
$cat ~/.dmrc
[Desktop]
Session=kde-plasma-safe
Re: Not able to login KDE after waking up from 'sleep' mode
go to init 3 and start kde using startx
This will tell you what is wrong.
This will tell you what is wrong.
Re: Not able to login KDE after waking up from 'sleep' mode
It seems to be loading all right till following, after which errors start coming:
xset: bad font path element (#9), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
Re: Not able to login KDE after waking up from 'sleep' mode
It seems that some kde configuration or packages has been removed or missing.
do these:
sudo fc-cache -fv
mv ~/.kde ~/.kde-old
if this does not solve the problem
then
or better create a new user and try to boot kde using this new user account.
If problem does not be solved then
maybe have to reinstall kde
sudo slapt-get -i --reinstall kde
do these:
sudo fc-cache -fv
mv ~/.kde ~/.kde-old
if this does not solve the problem
then
or better create a new user and try to boot kde using this new user account.
Code: Select all
sudo usersetup
maybe have to reinstall kde
sudo slapt-get -i --reinstall kde
Re: Not able to login KDE after waking up from 'sleep' mode
I tried above suggestions (except reinstalling KDE) but they did not work. I noted in messages that libsqlite3.so.0 was not being found. I had removed it earlier since it was an older version and I was using a newer portable version of sqlite3. On reinstalling original sqlite from slackware repository, KDE has started as before, without any problem.
Thanks for your help.
PS: The sqlite version 3.7.17 in Slackware repository has some bugs and should be upgraded.
Thanks for your help.
PS: The sqlite version 3.7.17 in Slackware repository has some bugs and should be upgraded.
Re: [SOLVED] Not able to login KDE after 'sleep' mode
So do not remove packages that may brake your system. Sqlite till to 3.12.2 in slackware current was break clementine and i had to build it with -DSQLITE_ENABLE_FTS3_TOKENIZER=1. Otherwise clementine cannot run.
As i see latest sqlite 3.13.0 in slackware current was build without -DSQLITE_ENABLE_FTS3_TOKENIZER=1 or it has this as default ( i did not checked the code) do not break clementine.
So when something is running do not touch it especially when it is used as your main system.
As i see latest sqlite 3.13.0 in slackware current was build without -DSQLITE_ENABLE_FTS3_TOKENIZER=1 or it has this as default ( i did not checked the code) do not break clementine.
So when something is running do not touch it especially when it is used as your main system.
Re: [SOLVED] Not able to login KDE after 'sleep' mode
Yes. I did not know sqlite was for the main system. I thought it was only for users as a database utility. Also, I had used removepkg to remove it. Had I used slapt-get, I would have got warning!
Code: Select all
# slapt-get --remove sqlite
Reading Package Lists...Done
The following packages will be REMOVED:
PyQt akonadi kde-workspace kdepimlibs kde-runtime kdewebdev kde-baseapps ark
konsole httpd apr-util geany-plugins kactivities kate okular kdelibs
filelight kcalc kmix kolourpaint kplayer ksnapshot libkexiv2 libkipi
nepomuk-core nepomuk-widgets partitionmanager polkit-kde-agent-1
polkit-kde-kcmodules-1 svgpart wicd-kde jack vlc libsamplerate alsa-utils
twolame libsndfile libsoup webkitgtk mozilla-firefox seamonkey-solibs
mozilla-nss php QScintilla attica automoc4 avahi cmake grantlee herqq
libbluedevil libdbusmenu-qt phonon phonon-gstreamer polkit-qt-1 qca
qimageblitz qjson qupzilla soprano strigi wicd qt redland sqlite
0 upgraded, 0 reinstalled, 0 newly installed, 65 to remove, 0 not upgraded.
After unpacking 757.0MB disk space will be freed.
Do you want to continue? [y/N]
Abort.
#