when in command line (because i cannot start plasma either) i get an error message stating [/usr/lib/YaST2/bin/y2base: symbol lookup error: /usr/lib64/libstdc++.so.6:undefined symbol: _ZNst_num_getIcSt19istreambuf_iteratorIcSt11char_traitsIcEEE2idE, version GLIBCXX_3.4] i would like to know how bad it is and if it can possibly can be fixed. PLEASE HELP!!!
Is this a fresh install and if so, have you checked the md5sum of your installation media?
no, i have had it working since about 3 weeks ago. yesterday i ended up upgrading packages to that of the factory suse repository and then i found that dolphin was not working and so i restarted and plasma stopped working. i then disabled the factory repository and tried downgrading all the packages back to their former repositories and now i cant do much without help
Which repositories exactly did you use? What is the output of
rpm -qa zypper
?
zypper-1.2.8-0.1.3.x86_64
i was using typically the opensuse 11.2 oss repository i believe
on startup it also asks me if my temporary-something is full just before the part where it would usually show the kde splash startup
Please post the outputs of
df -h
du -h /tmp | tail -n 1
zgrep BOOTUP /etc/sysconfig/cron
df -h
[file system used avail mounted on]
[/dev/sda2 20G 13G / ]
[udev 1.9G 1.9G /dev ]
[/dev/sda3 272G 166G /home ]
du -h /tmp | tail -n 1
du: cannot read directory ‘/tmp/YaST2-06375-okiqb4’: permission denied tail: l: invalid number of lines
zgrep BOOTUP /etc/sysconfig/cron
CLEAR_TMP_DIRS_AT_BOOTUP=‘no’
Please post the full output of
df -h
…as you seem to have shorten it and post only the last line of the output of
du -h /tmp
Please use code-tags:
[noparse]
put command-line output in here
[/noparse]
[filesystem size used avail use% mountedon]
[/dev/sda2 20G 6.2G 13G 34% /]
[udev 1.9G 272k 1.9G 1% /dev]
[/dev/sda3 272G 92G 166G 36% /home]
for du -h /tmp it says for the last 3 lines
[du: cannot read directory ‘tmp/YaST2-23703-suPe1M’: permission denied]
[4.0k /tmp/YaST2-23703-suPe1M]
[5.9M /tmp]
how do you use code tags?
how do you use code tags?
As I wrote:
…then it will be formatted neatly when posted and can be read more easily.
Anyway, I had the idea that a full /-partition might cause your trouble, but this is obviously not the case - I suppose that your YaST-packages got mixed up (which factory repositories were you using anyway?) and it will need some work to tidy this, since YaST is composed by using many many packages… but well, since there’s no easy way to solve this: please post the output of:
rpm | -qa yast
its says
put command-line output in here[if '-qa' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf -qa]the full message at startup is
call to lnusertemp failed (temporary directories full?). Check your installation.
Um… I meant using code tags here in the forum when posting outputs. 
Not in the command line itself. I’ll give you an example. if I have this output:
kalle@hoppers:~> nslookup forums.opensuse.org
Server: 213.191.74.12
Address: 213.191.74.12#53
Non-authoritative answer:
Name: forums.opensuse.org
Address: 130.57.4.15
…I will put it in code-tags like this:
[noparse]
kalle@hoppers:~> nslookup forums.opensuse.org
Server: 213.191.74.12
Address: 213.191.74.12#53
Non-authoritative answer:
Name: forums.opensuse.org
Address: 130.57.4.15
[/noparse]
…so it looks like this:
kalle@hoppers:~> nslookup forums.opensuse.org
Server: 213.191.74.12
Address: 213.191.74.12#53
Non-authoritative answer:
Name: forums.opensuse.org
Address: 130.57.4.15
You see?
Again, please post the output of
rpm | -qa yast
…and put that in code-tags, okay?
if '-qa' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf -qa
it then shows me commands for RPM. are you under the impression that i can copy and paste these answers as i go? the GUI is not working right now and so i am strictly using command line and retyping on another computer other than the one thats not working to get and recieve answers.
- This:
rpm -qa | grep yast
…is one command, one line.
- Wild guessing from me will not help you. If we shall help you with this problem, we definitely need some kind of information, since we can hardly hack into your system and look that up ourselves. There are ways of saving commandline outputs to a textfile on, for example, a USB-stick, for example:
rpm -qa | grep yast > /media/disk/output.txt
…but before doing so you will need some knowledge on how to mount and access to such a media without a GUI, which I doubt you have and I will not explain this from scratch here, since that’d be a bit too extensive (please understand that).
- No offense meant, but I do not understand why someone who apparently has little basic knowledge about SuSE or Linux in general would fiddle with a factory-repository. These sources mainly are for testing and bughunting, not for endusers. I seriously doubt that you will be able to tidy this mess even if we’d give you step-by-step instructions (because even then you’ll have to know some stuff), plus I do not like to post commands which the user does not understand himself at all - I bet I could post a forkbomb and you would execute that without even thinking about what this could be for.
Again, no offense meant, but I think you should read a bit about basic SuSE-concepts and shell-commands, start from scratch with a fresh install and avoid such repositories for a while.
yea i understand where your coming from, i tend to go overboard with messing around with every system i own and i should probably use alot more caution in the future, but it is my nature to tinker with things until they are perfect or break. where can i learn more about basic SuSE-concepts and shell-commands? i agree that it would probably take too long to diagnose the problem and so i will be doing a fresh install. good thing i had nothing of importance on it.
I’m glad you understand my concerns, really…
The user apfing opened a thread yesterday asking for links explaining basic Linux / SuSE-concepts, you will find some useful sites →there.
Good luck and don’t give up!