im very new to suse linux, I just switched over to suse from kubuntu after my hard drive failed(was new to kubuntu too). Here’s my problem: I install from the live cd utilizing the whole hard drive it all works fine until I install all the updates through the autoupdate. afterwards I get “su returned an error” running YAST or even trying to view the system log. I was messing around with commands in console…either they arent recognized or i get “bus error”. ??? where do i start here?
when i run terminal as super user it returns a “warning program ‘su’ crashed”.
piro133a adjusted his/her AFDB on Friday 24 Jul 2009 09:16 to write:
> when i run terminal as super user it returns a “warning program ‘su’
I presume this is stopping you from updating/re-installing or back stepping
Can you login as root on a console?
If at KDE/Gnome either you can logout and at the login window there should
be a dropdown box with “Console login” choose that and you will be dropped
to a console, login as root and enter the root pass.
Does that work?
Or if in KDE/Gnome press Ctrl+Alt+F1 this will drop you straight to a
console login ( but leave the GUI running on vt 7 ) try the root and pass
from there, to get back to the GUI just press Alt+F7.
If you can do this then at the console you should be able run YaST by
this will bring up the ncurses version of YaST which can do nearly all of
the GUI version, navigate with the Tab or easier use the Alt+<letter> way of
getting around, if you go to the software management you should find in
there a “Verify” function which will check if your system has any conflicts
or such, try that and see if it will fix any packages that need updating or
If Yast will not start you could also use zypper to verify or update:
should sort out any conflicts or deps and
That is ref for REFresh the repos, lu to give you a List of Updates and in
to INstall any needed packages
Nullus in verba
Nil illegitimi carborundum
Thankyou so much for the help, unfortunately it didnt work though.
whenever I logout then do a console login it fails. I will enter “root” as login and it just thinks for awhile then gives me a line with the version of suse im using and prompts for login again. When i try to login using my standard user name “mike” it does the same thing. logging into the KDE desktop through GUI works just fine though. im basically trapped in a little world of usability here. I dont have caps on either, the login names were right. Is this because I am using KDE?
I am able to run the zypper command through the console when i login to the GUI.
mike@linux-ku1j:~> zypper ref
Root privileges are required for refreshing system repositories.
mike@linux-ku1j:~> sudo zypper ref
Repository ‘openSUSE-11.1-Debug’ is up to date.
Repository ‘openSUSE-11.1-Non-Oss’ is up to date.
Repository ‘openSUSE-11.1-Oss’ is up to date.
Repository ‘openSUSE-11.1-Source’ is up to date.
Repository ‘openSUSE-11.1-Update’ is up to date.
All repositories have been refreshed.
mike@linux-ku1j:~> sudo zypper verify
Loading repository data…
Reading installed packages…
Dependencies of all installed packages are satisfied.
This reads like a bad install, possibly because the installation CD is bad. Did you do the md5sum on the iso file BEFORE you burned the CD ? Did you burn the CD at the slowest speed your burner allows ? How many years difference in age between the CD drive where you burned the openSUSE live CD, and the CD drive that you are using to install openSUSE (ie it could be a big difference in CD drive calibration) ?
mike@linux-ku1j:~> sudo dolphin
<unknown program name>(3882)/: KUniqueApplication: Cannot find the D-Bus session server
<unknown program name>(3881)/: KUniqueApplication: Pipe closed unexpectedly.
mike@linux-ku1j:~> kdesu dolphin
when i do the last command the computer thinks for awhile then i get “su returned with an error”. Which logs would i want to view and how would i view them with my current limitation? I want to give more info. im really thinking about reinstalling and not doing the updates…they caused all this!
I didnt run an md5 sum on the disk, but before in installed i used the “check installation media” option that i was given isnt that the same?. I dont think it could be a bad install though, because everything works fine before i do the (50 some) updates. could it be something to do with how the partitions are laid out? i think the first sda(0?) was set as swap, shouldnt the first partition be set as root?
piro133a adjusted his/her AFDB on Friday 24 Jul 2009 11:56 to write:
> I am able to run the zypper command through the console when i login to
> the GUI.
> mike@linux-ku1j:~> zypper ref
> Root privileges are required for refreshing system repositories.
> mike@linux-ku1j:~> sudo zypper ref
> root’s password:
> Repository ‘openSUSE-11.1-Debug’ is up to date.
> Repository ‘openSUSE-11.1-Non-Oss’ is up to date.
> Repository ‘openSUSE-11.1-Oss’ is up to date.
> Repository ‘openSUSE-11.1-Source’ is up to date.
> Repository ‘openSUSE-11.1-Update’ is up to date.
> All repositories have been refreshed.
> mike@linux-ku1j:~> sudo zypper verify
> Loading repository data…
> Reading installed packages…
> Dependencies of all installed packages are satisfied.
let me see if I am getting this wrong please bear with me here.
Instead of using sudo what happens if you use just su?
sudo does not work the same in SuSE as it does in ubuntu, in SuSE sude only
executes the first command with root privs, as soon as the first command is
executed it reverts back to user privs so you will get permission errors on
any command afterwards, on ubuntu IIRC sudo keeps the privs for that session
and so executes all commands as the sudo user.
su will give you root control over the complete session until you issue and
exit, Ctrl+c or close the console/terminal you will notice that the #> turns
to a # to indicate that your are in fact root.
If this is way off mark then I do apologise but I just wanted to get
something straight in my own mind here to see which way to go.
Nullus in verba
Nil illegitimi carborundum