hello my problem is everytime I run something like dolphin or iplist/block as root from the terminal it just hangs, so I "monitor input and output of the process and I get the following message “failed to attach to process 11,830” or someother number also all my sudo permissions are what they should be so anyone have any idea on what could be causing this and how to fix it? thanks
sorry I know I’m not giving much info is there any event logs I should be checking?
Same thing here. Weird. Even weirder when you read this:
If I ‘ssh -X’ from my laptop to my laptop, it does work…
“su -c yast2” : does nothing, cursor just waiting, no prompt
“ssh -X ownIP”, then “su -c yast2”: works
Realy weird.
threatingbehaviour wrote:
> hello my problem is everytime I run something like dolphin or
> iplist/block as root from the terminal it just hangs, so I "monitor
> input and output of the process and I get the following message “failed
> to attach to process 11,830” or someother number anyone have any idea on
> what could be causing this and how to fix it? thanks
are you also running:
- AMD Athlon X2 6.0 GHz, 8 GB DDR2-800, 1,5 TB diskspace, EVGA 9800GT,
opensuse 11.1,kernel 2.6.29, KDE4-Factory+Qt45 - ASUS A7T laptop, 2 GB opensuse Factory, KDE4-Factory+Qt45.
as is “Knurpht”?
might you be so kind as to share more about your setup…
–
platinum
Give a hacker a fish and you feed him for a day.
Teach “information is power” and you feed him for a lifetime.
You think it’s a 64bit problem? My other machines, running 64bit 11.0 and 11.1 with default kernel etc. don’t have the problem.
Cannot find anything in logs or .xsession-errors.
> You think it’s a 64bit problem? My other machines, running 64bit 11.0
> and 11.1 with default kernel etc. don’t have the problem.
> Cannot find anything in logs or .xsession-errors.
personally, i GUESS it is a problem introduced through your KDE4.x
upgrading path…but, i’m just guessing…are you running
KDE4.bleedingEdge on both machines?
–
platinum
sorry haven’t been on in awhile just got a new job (finally) an they’ve been working me to death but anyway here’s my setup.
Intel Centrino duo 1.60ghz 2gigs DDR2 Ram Kernel 2.6.27.25-0.1-pae i686 with kde 4.1.3 and it is a 32bit system so the problem isn’t limited to only 64 bit systems.
Running KDE4 Factory Desktop on both. But: other machines in the house running 11.1 and Factory Desktop don’t have it. I’m not on it too much (do either X or completely CLI)
OK. Congrats on new job.
I found out this:
su
yast2
does not work.
But:
su - (please not the ‘minus’ sign)
yast2
does work.
This indeed is by no means related to 32/64bit. Rather looks like something wrong in settings for root/su.
For now, I don’t have the time to dive into this any deeper (deadline for huge project on 1st of October), so I suggest you use ‘su -’ for the time being.
> looks like something wrong in settings for root/su.
no…if “su -” works correctly that proves that there is nothing
wrong with root’s environment…
see, when you just “su” you get root powers but keep your own
environment (path, bashrc, etc etc etc)…but, when you use any of
the following, you both get root powers AND move from your
environment to that of root:
su root
su -l
su --login
su -
for more info:
man su
info su
when “su -” works but “su” does not then you have somehow damaged
your environment…
i’d guess you can prove that to yourself by creating a new user, log
in as that user and you will see that if you use just “su” from there
then it will work ok (initially, until that environment gets somehow
damaged [maybe by logging into the gui as root, or preforming chmod
777 to try to get around those pesky “permission” problems, which are
not problems…instead they are there to keep the boogymen out, and
regular users from killing the administrator’s system]…
personally, i never use just su, and i never log into any Linux
desktop/gui as root…
ymmv
platinum
yes but any ideas on how I would of damaged my enviroment? I dont mess with things that I don’t understand so any ideas?
I think I’ve done it to a few of my setups by running graphical root programs using ‘su’.
My understanding of it - which may be entirely wrong (and I can’t find where I read it…) - is the fact that you’re running with your users environment variables but as root can ‘mix’ settings (particularly ownership of dotfiles) or permissions across from one account to another.
So, I’ve read that to avoid this you should only ever run graphical root things with ‘kdesu’, ‘gnomesu’, ‘gksudo’ (if you find it anywhere still) or ‘su -’
threatingbehaviour wrote:
> yes but any ideas on how I would of damaged my enviroment? I dont mess
> with things that I don’t understand so any ideas?
sorry, i can’t give the specifics you seek…but agree with
Confuseling’s musings, and add some info like: http://tinyurl.com/6ry6yd
i trust those old men who told me…
–
platinum
ah I see well adding another user didn’t fix the problem so now I ask…any repairs I can run to try and fix it?
You could try to find hidden files in your users home directory that are owned by root, I suppose. But you certainly shouldn’t change anything without verifying with someone who knows what they’re talking about (or perhaps just comparing against a newly created user).
Probably easier though just to create a new user and move your files across…
alright thanks I’ll give it a try