I've accidently uninstalled zeitgeist by running sudo apt-get purge zeitgeist*
I can't login anymore. I've the following error message : "Session returned error code 1"
Error message from io.elementary.greeter
Observations :
It tests the password (if I don't tip the right one, it tells me wrong password)
I can login use the command line tty (by pressing Ctrl Alt F1).
When I try to run io.elementary.greeter, I've the error message "Unable to init server: Impossible to connect: Connection refused" (and it tells me it can't use GTK on this display but nevermind)
When I try the same command line with sudo, I've more errors : "dconf-warning **: 18:28:41.795: failed to commit changes to dconf: Impossible de lancer automatiquement D-bus sans $DISPLAY X11" (this last sentence meaning "Impossible to automaticly run D-bus without $DISPLAY X11")
If any of you know any solution instead of uninstalling the whole OS and reinstalling, I'll be realy thanksful.
[ RESOLVED ]
Following this link that leads to this other link, I've repaired it.
2 steps :
1 - I've removed the .Xauthority file in my home directory and then I've run sudo apt-get update ; sudo apt-get upgrade
2 - I've run sudo apt-get install pantheon-xsession-settings and reboot (command reboot)
Now seems to work fine :-)
I hope it will help, GL HF ! ;-)
Related
I just undeliberately deleted my bin/tempfile, please don't ask why.
I experienced no issues, however, after a reboot, I wasn't able to login anymore. When I entered my password and pressed ENTER, I got a black screen, and 2 seconds later the login screen appeared again.
My system is Kubuntu 17.10 on 4.14.11 Kernel.
I did some research on it, but I still got no clue what this file does, or how I can restore it (it was deleted by rm).
Until now I did the following:
touch /bin/tempfile
chown root:root /bin/tempfile
chmod 755 /bin/tempfile
Finally I got back into KDE, and everything works fine this far, except an error, which I receive immediately after logging in: Xsession: Xsession: Warning: unable to write to ; X session may exit. The message is not in the style of my normal KDE desktop windows, it looks like a very old design, because the message probably comes from X itself. (I have no clue about this, sorry if it's rubbish)
In your case you can easily fix your issue by executing the following command:sudo apt-get --reinstall install debianutils.
Hope this helps.
I wanted to change my terminal to enable e.g. mouse interaction. So I got the gnome-terminal code, but when I wanted to generate it (without changing anything), the following problem occured:
When I run ./autogen.sh --without-pcre2 I get the error message Requested 'vte-2.91 >= 0.45.0' but version of vte is 0.42.5.
So I've tried to install vte-2.91 higher than 0.45.0 but the highest I could find was 0.44.2 (and I could not install that either)
Does anyone know how to get a vte-2.91 version >= 0.45.0?
Ok, found a solution myself.
just runsudo apt-get build-dep gnome-terminal .
Also to get the Code one can simply use apt-get source gnome-teminal
or for the VTE-Code: apt-get source libvte-2.91-0 .
So i am new to arch linux and i am following a guide to get KDE plasma installed, so i've go going along through this script and now all of a sudden i get the following error:
Archlinux ARM: Error: failed to init transaction (unable to lock database)
error: could not lock database: read-only file system
and the command i am using is:
pacman -S kf5 kf5-aids
Now from the fact that i know how to read i see that the second error states that all files are currently read only. What i want to know is how or what would have caused that to happen and how to fix my all round issue.
Do you have root privileges?
Try sudoing:
# sudo pacman -S kf5 kf5-aids
If you haven't installed (and configured) sudo, just log in as root:
# su -
And execute the command under the new user.
I have fedora16 on my computer and omnet++ 4.2.1.
I just installed omnet++ 4.2.2.
when I restart my system from now I am unable to login as my user name.
Fedora is giving me this error message : Could not update ICEauthority file/home... .ICEauthority.
It leaves me at the desktop background without access to anything.
Any suggestion for this error would be appreciated.
Its probably because of permission errors. When the error pops up, Try this:
1) switch to a new virtual terminal ctrl alt F2 and login
2) sudo chown username ./ -R
That solved the problem for me.
That sounds really stupid.
On Lubuntu 10.10, I did:
echo "deb http://oss.oracle.com/debian unstable main non-free" >> /etc/apt/sources.list
apt-get update ; apt-get install oracle-xe
That brings me Oracle XE 10.2.0.1. And then:
/etc/init.d/oracle-xe configure
Everything looks ok, including the password prompt and so. After that, I go to http://127.0.0.1:port/apex, and when I try to login with the username "SYSTEM", and the password I just typed. I get a "Invalid Login Credentials" error.
I also tried:
sqlplus /nolog
CONNECT
[ .. login and password .. ]
ERROR:
ORA-01017: invalid username/password; logon denied
Setting the environment variables also don't help.
sh oracle_env.sh
Well.. I just don't know what's happening. I repeated this procedure trying to find peculiar things, but always got the same results. Also tried some other users as "SYS". useless...
Thanks in advance.
Guys, I've been breakin my head with the same issue and finally got it logging in.. Here is the key.. http://www.linoob.com/2010/02/setting-up-oracle-xe-10g-in-ubuntu/
in case u ve already installed oracle, just remove it and purge and then reinstall with the steps in the given link..
And don't forget to give a longer password this time.. "minimum 8 chars" as I picked it up from some forum..
Exactly the same is happening to me in CentOS 5. With user SYSTEM or SYS, just after install and configure I cannot log in.
Yes, make sure the pw is >= 8 characters in length. It won't complain when setting on less than 8, but you won't be able to login ! With >= 8 in length, a successful login !!
Check whether Oracle is running before trying log in
/etc/init.d/oracle-xe start (Should be run as root).
Then in sql terminal try log in.
connect / as sysdba