On 01.09.2011 18:02, Tony Houghton wrote:
> On Mon, 29 Aug 2011 17:08:49 +0400
> Michael Tokarev <m...@tls.msk.ru> wrote:
> 
>> The sequence of events is like,
>>
>>  open a roxterm window as user,
>>  su to root with exec (exec su -  or exec sudo bash)
>>  open new tab or window (Ctrl+Shift+N or Ctrl+Shift+T)
>>
>> it will complain that it can't read /proc/NN/cwd due to
>> permission denied problem and close new window/tab after
>> confirmation dialog.
[]
> Thanks for the report. I can confirm this is reproducible and I've fixed
> it by checking for errors (eg EPERM) reading the link and not trying to
> set the cwd in that case. You're probably right that previous versions
> didn't have this bug because they spawned child processes in a different
> way.

Yes, that's the most obvious thing to do - to ignore certain errors,
or maybe even _all_ errors in this place - it is one of very rare
cases where error handling actually may be omitted ;)

And yes I'm certain that previous versions had no such issue - it always
opened new window in "previous" directory in such situation.  It actually
wasn't always a good idea anyway: eg, I can run "su" from some "random"
directory (it will go stright to root's $HOME), but roxterm will continue
to open new tabs/windows in that "random" directory, even if it makes no
sence anymore.  I understand that roxterm just can't know if that's the
case - with older way to track current dir changes.  But that's all
history now.

> I've fixed it in git but I'd rather hold off release for a little while.
> I've only just released a new version (experimental in Debian) and it
> would be surprising if there aren't any other bugs because there were
> major changes.

Fair enough, I've seen your discussion about roxterm, roxterm-legacy,
roxterm-glib3 et all on debian-devel.  And I haven't asked for an urgent
fix - I hope it was quite obvious, especially having in mind that I've
choosen severity to be minor... ;)

Thank you for your time and efforts!

/mjt



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to