aptosid.com

Software - bash: cannot set terminal process group

arwa - 13.02.2012, 08:17
Post subject: bash: cannot set terminal process group
After todays dist-upgrade when executing the "sux" command to switch to root, the following message is printed after authentication:

$ sux
Password:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

Maybe this has to do with a modification of /etc/login.defs that I think the package "login" asked me to let it do. It did change an entry "ENCRYPT_METHOD SHA256" to "ENCRYPT_METHOD SHA512" IIRC.

As I do not know if this is critical or not, I do not post this in the dist-upgrading warning forum.

arwa
w7rms - 13.02.2012, 17:10
Post subject: Re: bash: cannot set terminal process group
I'm also having the same issue, but for the last few days I've also been getting * No device configured for user "root".


Rick


      Code:

rick@aptosidbox:~$ sux
* No device configured for user "root".
Password:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
root@aptosidbox:/home/rick#

root@aptosidbox:/home/rick# infobash -v3
Host/Kernel/OS  "aptosidbox" running Linux 3.2-5.slh.2-aptosid-amd64 x86_64 [ aptosid 2010-03 Ἀπάτη - kde-full - (201012262151) ]
CPU Info        4x Intel Core i5 760 @ 8192 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 2801.000 MHz ]
Videocard       nVidia GT215 [GeForce GT 240]  X.Org 1.11.3.901  [ 1680x1050@50.0hz ]
Network cards   Realtek RTL8111/8168B PCI Express Gigabit
Processes 174 | Uptime 32min | Memory 1085.9/7989.4MB | HDD Hitachi HDS72105 Size 500GB (13%used) | GLX Renderer GeForce GT 240/PCI/SSE2 | GLX Version 3.3.0 NVIDIA 290.10 | Client Shell | Infobash v3.41


hubi - 13.02.2012, 20:50
Post subject: RE: Re: bash: cannot set terminal process group
Same here only with sux, not with su. Unfortunatelly I cannot offer a solution but reverting to the package "login" from testing.

hubi
DeepDayze - 15.02.2012, 23:40
Post subject: Re: RE: Re: bash: cannot set terminal process group
      hubi wrote:
Same here only with sux, not with su. Unfortunatelly I cannot offer a solution but reverting to the package "login" from testing.

hubi


Did that correct the problem? if so maybe a bug report should then be filed to correct the package
hubi - 16.02.2012, 04:56
Post subject: RE: Re: RE: Re: bash: cannot set terminal process group
There is a bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659878

hubi
Lat - 24.02.2012, 04:19
Post subject: RE: Re: RE: Re: bash: cannot set terminal process group
I'm a bit confused. The problem is with login/password 4.1.5-1 and login/password 4.1.4.2+svn3283-3 is not affected, is it?

If all the above is true, why 4.1.4.2+svn3283-3 is not any longer the testing version?

Or is this like a prescription drug? 4.1.5-1 is not the solution, but it has better side effects than 4.1.4.2+svn3283-3 ?

I still have4.1.4.2+svn3283-3, should I hold both login and password, or upgrade to 4.1.5-1
Thank you
browe - 24.02.2012, 19:57
Post subject: RE: Re: RE: Re: bash: cannot set terminal process group
Maybe someone could describe what the real problem is. I see the bash messages, but what negative effect does it give? Any commands I have issued seem to work as usual.
arwa - 25.02.2012, 12:28
Post subject: RE: Re: RE: Re: bash: cannot set terminal process group
There are two problems I have with the sux-shell: Pressing Ctrl+c does close it, instead of just ending the running command. Also a logout requires some (6-10?) seconds, as it is waiting for the sux-shell to end.
x-un-i - 25.02.2012, 19:52
Post subject: RE: Re: RE: Re: bash: cannot set terminal process group
su does not suffer any problem/limitation

sux was conceived as a wrapper around su with transfered X credentials so the main purpose is/was start a X application as root ( is that really needed?)

the changed was due to a security leak http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659878#10 caused by the sux not su so sux got limited capabilities...

just one proposal: use su not sux ( use the last one only when you want to start some X appl and not as a root shell)

Advantages: you spare one letter (x) when becoming root and avoid the (actual) underlying probs.
hubi - 25.02.2012, 22:16
Post subject: RE: Re: RE: Re: bash: cannot set terminal process group
Despite the warning, sux still works. I use it in "ssh -X" sessions with a remote computer when I want to access GUI applications as root. Aptosid only on all boxes.

hubi
arwa - 26.02.2012, 09:09
Post subject: RE: Re: RE: Re: bash: cannot set terminal process group
Using su instead of sux helps regarding the error message. Also ctrl+c is possible again, without exiting the bash. So I will use su as long I do not need the x. Thanks so far.

But the issue of konsole hanging for some seconds when logging out from KDE also happens with su.
manul - 24.04.2012, 20:13
Post subject: RE: Re: RE: Re: bash: cannot set terminal process group
Not much progress here http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659832
I wonder will sux continue to be maintained to have the same functionality as before?
Or I should look into making some aliases or something to workaround the current broken behaviour.
All times are GMT - 12 Hours
Powered by PNphpBB2 © 2003-2010 The Zafenio Group
Credits