Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #201927 > unrolled thread

Strangeness when binary executable overwritten by text -- bug or feature?

Back to article view | Back to linux.debian.user

Contents

  Strangeness when binary executable overwritten by text -- bug or  feature? Richard Owlett <rowlett@cloud85.net> - 2018-10-31 15:20 +0100
    Re: Strangeness when binary executable overwritten by text -- bug  or feature? Curt <curty@free.fr> - 2018-10-31 15:30 +0100
      Re: Strangeness when binary executable overwritten by text -- bug or  feature? Richard Owlett <rowlett@cloud85.net> - 2018-10-31 15:40 +0100
        Re: Strangeness when binary executable overwritten by text -- bug or  feature? Reco <recoverym4n@enotuniq.net> - 2018-10-31 15:40 +0100
          Re: Strangeness when binary executable overwritten by text -- bug or feature? Gene Heskett <gheskett@shentel.net> - 2018-10-31 15:50 +0100
            Re: Strangeness when binary executable overwritten by text -- bug or feature? Gene Heskett <gheskett@shentel.net> - 2018-10-31 16:00 +0100
          Re: Strangeness when binary executable overwritten by text -- bug or feature? Gene Heskett <gheskett@shentel.net> - 2018-10-31 15:50 +0100
        Re: Strangeness when binary executable overwritten by text -- bug  or feature? Curt <curty@free.fr> - 2018-10-31 16:00 +0100
    Re: Strangeness when binary executable overwritten by text -- bug or  feature? Reco <recoverym4n@enotuniq.net> - 2018-10-31 15:30 +0100
      Re: Strangeness when binary executable overwritten by text -- bug or  feature? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-31 15:50 +0100
      Re: Strangeness when binary executable overwritten by text -- bug or  feature? Richard Owlett <rowlett@cloud85.net> - 2018-10-31 16:00 +0100
    Re: Strangeness when binary executable overwritten by text -- bug or feature? rhkramer@gmail.com - 2018-10-31 16:40 +0100
      Re: Strangeness when binary executable overwritten by text -- bug or  feature? Richard Owlett <rowlett@cloud85.net> - 2018-10-31 16:50 +0100
        Re: Strangeness when binary executable overwritten by text -- bug or feature? rhkramer@gmail.com - 2018-10-31 17:00 +0100
          Re: Strangeness when binary executable overwritten by text -- bug  or feature? Curt <curty@free.fr> - 2018-10-31 17:40 +0100
          Re: Strangeness when binary executable overwritten by text -- bug or  feature? Richard Owlett <rowlett@cloud85.net> - 2018-10-31 17:40 +0100
    IT IS A BUG -- Re: Strangeness when binary executable overwritten by  text -- bug or feature? Richard Owlett <rowlett@cloud85.net> - 2018-11-04 14:30 +0100
      Re: IT IS A BUG -- Re: Strangeness when binary executable  overwritten by text -- bug or feature? Andy Smith <andy@strugglers.net> - 2018-11-04 14:40 +0100
        Re: IT IS A BUG -- Re: Strangeness when binary executable overwritten  by text -- bug or feature? Richard Owlett <rowlett@cloud85.net> - 2018-11-05 13:20 +0100
          Re: IT IS A BUG -- Re: Strangeness when binary executable  overwritten by text -- bug or feature? Andy Smith <andy@strugglers.net> - 2018-11-05 13:40 +0100
            Re: IT IS A BUG -- Re: Strangeness when binary executable  overwritten by text -- bug or feature? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-11-05 15:10 +0100
              Re: IT IS A BUG -- Re: Strangeness when binary executable  overwritten by text -- bug or feature? Curt <curty@free.fr> - 2018-11-05 16:10 +0100

Page 1 of 2  [1] 2  Next page →

#201927 — Strangeness when binary executable overwritten by text -- bug or feature?

Debian 9.1 with MATE installed from DVD set.

Due a non-reproducible sequence of events, a binary executable was over 
written by the contents of a man page in pure text format. For unknown 
reason, the resulting file was tagged as executable.

A custom MATE launcher pointed the corrupted file.
When the launcher icon was clicked there was no response whatsoever.
Including *NO ERROR MESSAGE*
Is this a bug or a feature?
If a feature, why?

[toc] | [next] | [standalone]

#201928 — Re: Strangeness when binary executable overwritten by text -- bug or feature?

On 2018-10-31, Richard Owlett <rowlett@cloud85.net> wrote:
> Debian 9.1 with MATE installed from DVD set.
>
> Due a non-reproducible sequence of events, a binary executable was over 
> written by the contents of a man page in pure text format. For unknown 
> reason, the resulting file was tagged as executable.

I want to predict immediately that this can of worms will produce the
longest thread in the history of debian user.

> A custom MATE launcher pointed the corrupted file.
> When the launcher icon was clicked there was no response whatsoever.
> Including *NO ERROR MESSAGE*
> Is this a bug or a feature?
> If a feature, why?
>
>
>


-- 
When you have fever you are heavy and light, you are small and swollen, you
climb endlessly a ladder which turns like a wheel. 
--Jean Rhys, Voyage in the Dark

[toc] | [prev] | [next] | [standalone]

#201931

On 10/31/2018 09:18 AM, Curt wrote:
> On 2018-10-31, Richard Owlett <rowlett@cloud85.net> wrote:
>> Debian 9.1 with MATE installed from DVD set.
>>
>> Due a non-reproducible sequence of events, a binary executable was over
>> written by the contents of a man page in pure text format. For unknown
>> reason, the resulting file was tagged as executable.
> 
> I want to predict immediately that this can of worms will produce the
> longest thread in the history of debian user.

ONLY if members of this group can't or wont read.
I believe I rigorously complied with
[http://www.catb.org/esr/faqs/smart-questions.html]


> 
>> A custom MATE launcher pointed the corrupted file.
>> When the launcher icon was clicked there was no response whatsoever.
>> Including *NO ERROR MESSAGE*
>> Is this a bug or a feature?
>> If a feature, why?
>>
>>
>>
> 
> 

[toc] | [prev] | [next] | [standalone]

#201932

	Hi.

On Wed, Oct 31, 2018 at 09:29:52AM -0500, Richard Owlett wrote:
> On 10/31/2018 09:18 AM, Curt wrote:
> > On 2018-10-31, Richard Owlett <rowlett@cloud85.net> wrote:
> > > Debian 9.1 with MATE installed from DVD set.
> > > 
> > > Due a non-reproducible sequence of events, a binary executable was over
> > > written by the contents of a man page in pure text format. For unknown
> > > reason, the resulting file was tagged as executable.
> > 
> > I want to predict immediately that this can of worms will produce the
> > longest thread in the history of debian user.
> 
> ONLY if members of this group can't or wont read.
> I believe I rigorously complied with
> [http://www.catb.org/esr/faqs/smart-questions.html]

'smartctl -a /dev/sda' output would be nice, but I won't insist on it.

Reco

[toc] | [prev] | [next] | [standalone]

#201934 — Re: Strangeness when binary executable overwritten by text -- bug or feature?

On Wednesday 31 October 2018 10:31:40 Reco wrote:

> 	Hi.
>
> On Wed, Oct 31, 2018 at 09:29:52AM -0500, Richard Owlett wrote:
> > On 10/31/2018 09:18 AM, Curt wrote:
> > > On 2018-10-31, Richard Owlett <rowlett@cloud85.net> wrote:
> > > > Debian 9.1 with MATE installed from DVD set.
> > > >
> > > > Due a non-reproducible sequence of events, a binary executable
> > > > was over written by the contents of a man page in pure text
> > > > format. For unknown reason, the resulting file was tagged as
> > > > executable.
> > >
> > > I want to predict immediately that this can of worms will produce
> > > the longest thread in the history of debian user.
> >
And will follow that rule about opening a can of worms will also 
immediately at least the size of the can to put them back into.

> > ONLY if members of this group can't or wont read.
> > I believe I rigorously complied with
> > [http://www.catb.org/esr/faqs/smart-questions.html]
>
> 'smartctl -a /dev/sda' output would be nice, but I won't insist on it.
>
> Reco



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#201937 — Re: Strangeness when binary executable overwritten by text -- bug or feature?

On Wednesday 31 October 2018 10:39:17 Gene Heskett wrote:

> On Wednesday 31 October 2018 10:31:40 Reco wrote:
> > 	Hi.
> >
> > On Wed, Oct 31, 2018 at 09:29:52AM -0500, Richard Owlett wrote:
> > > On 10/31/2018 09:18 AM, Curt wrote:
> > > > On 2018-10-31, Richard Owlett <rowlett@cloud85.net> wrote:
> > > > > Debian 9.1 with MATE installed from DVD set.
> > > > >
> > > > > Due a non-reproducible sequence of events, a binary executable
> > > > > was over written by the contents of a man page in pure text
> > > > > format. For unknown reason, the resulting file was tagged as
> > > > > executable.
> > > >
> > > > I want to predict immediately that this can of worms will
> > > > produce the longest thread in the history of debian user.
>
> And will follow that rule about opening a can of worms will also
> immediately at least double the size of the can to put them back into.

Correction inserted above, this keyboard is a great keyboard around messy 
machinery, but it silently shifts from insert to overwrite mode entirely 
too easily with my short, somewhat fat fingers trying to type rapidly on 
it. So adjacent keys get pushed which apparently interpreted as the 
magic twanger that controls that particular function.

> > > ONLY if members of this group can't or wont read.
> > > I believe I rigorously complied with
> > > [http://www.catb.org/esr/faqs/smart-questions.html]
> >
> > 'smartctl -a /dev/sda' output would be nice, but I won't insist on
> > it.

I will. Show us Richard.

> > Reco



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#201935 — Re: Strangeness when binary executable overwritten by text -- bug or feature?

On Wednesday 31 October 2018 10:31:40 Reco wrote:

> 	Hi.
>
> On Wed, Oct 31, 2018 at 09:29:52AM -0500, Richard Owlett wrote:
> > On 10/31/2018 09:18 AM, Curt wrote:
> > > On 2018-10-31, Richard Owlett <rowlett@cloud85.net> wrote:
> > > > Debian 9.1 with MATE installed from DVD set.
> > > >
> > > > Due a non-reproducible sequence of events, a binary executable
> > > > was over written by the contents of a man page in pure text
> > > > format. For unknown reason, the resulting file was tagged as
> > > > executable.
> > >
> > > I want to predict immediately that this can of worms will produce
> > > the longest thread in the history of debian user.
> >
> > ONLY if members of this group can't or wont read.
> > I believe I rigorously complied with
> > [http://www.catb.org/esr/faqs/smart-questions.html]
>
> 'smartctl -a /dev/sda' output would be nice, but I won't insist on it.
>
How about this Richard, let us see what smartctl thinks about this drives 
health. So I'll insist on seeing it. Please post its output.

> Reco



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#201936 — Re: Strangeness when binary executable overwritten by text -- bug or feature?

On 2018-10-31, Richard Owlett <rowlett@cloud85.net> wrote:
> On 10/31/2018 09:18 AM, Curt wrote:
>> On 2018-10-31, Richard Owlett <rowlett@cloud85.net> wrote:
>>> Debian 9.1 with MATE installed from DVD set.
>>>
>>> Due a non-reproducible sequence of events, a binary executable was over
>>> written by the contents of a man page in pure text format. For unknown
>>> reason, the resulting file was tagged as executable.
>> 
>> I want to predict immediately that this can of worms will produce the
>> longest thread in the history of debian user.
>
> ONLY if members of this group can't or wont read.
> I believe I rigorously complied with
> [http://www.catb.org/esr/faqs/smart-questions.html]
>

I guess I stumbled immediately upon "non-reproducible sequence of
events." Then I kind of wondered, like, well, can those events be
briefly described, at least? Or maybe 'non-reproducible' means you just
don't know what the hell happened? 

But Reco extracted marrow from your post, and I will gracefully bow
out now and let you boys have at it without further ado.

>> 
>>> A custom MATE launcher pointed the corrupted file.
>>> When the launcher icon was clicked there was no response whatsoever.
>>> Including *NO ERROR MESSAGE*
>>> Is this a bug or a feature?
>>> If a feature, why?
>>>
>>>
>>>
>> 
>> 
>
>
>


-- 
When you have fever you are heavy and light, you are small and swollen, you
climb endlessly a ladder which turns like a wheel. 
--Jean Rhys, Voyage in the Dark

[toc] | [prev] | [next] | [standalone]

#201929

	Hi.

On Wed, Oct 31, 2018 at 09:14:40AM -0500, Richard Owlett wrote:
> Debian 9.1 with MATE installed from DVD set.
> 
> Due a non-reproducible sequence of events, a binary executable was over written by the contents of a man page in pure text format. For unknown reason, the
> resulting file was tagged as executable.

Replace your HDD today, don't give it another chance to corrupt your
data.


> A custom MATE launcher pointed the corrupted file.
> When the launcher icon was clicked there was no response whatsoever.
> Including *NO ERROR MESSAGE*
> Is this a bug or a feature?
> If a feature, why?

A (mis)feature. Any executable text file without defined shebang is a
shell script. In this case - a syntactically invalid shell script.
So it can be executed, but the child shell will exit immediately.

Reco

[toc] | [prev] | [next] | [standalone]

#201933

On Wed, Oct 31, 2018 at 05:27:58PM +0300, Reco wrote:
> A (mis)feature. Any executable text file without defined shebang is a
> shell script.

Not quite.  An attempt to execute a file that doesn't have a valid magic
number in the first few bytes triggers an ENOEXEC from the execve(2) call.
If this attempt was made by a C program, then that's that.  You handle
the error however you choose to handle it.

However, it the attempt to execute the file was done by a shell, then
the shell will typically catch the ENOEXEC and then make a second attempt.
The exact mechanism for this secondary attempt depends on the shell.
Bash reads the first hundred bytes or so looking for NUL bytes.   If it
sees a NUL byte, it decides the file is *not* a script, and you get
"Exec format error" printed on stderr.  If there are no NUL bytes, then
bash launches a child bash process to read the file as a script.

Other shells may launch a copy of themselves, or they may choose to
launch /bin/sh or sh instead, or they may print an error.  GNU's find
-exec launches sh, but I'm uncertain whether that's a GNUism, or a de
facto standard practice.

> In this case - a syntactically invalid shell script.
> So it can be executed, but the child shell will exit immediately.

If there's a syntax error, you'd expect to see a message.  It's possible
that the "script" simply does nothing (e.g. it runs "exit" or "exec true"
or something similar before any commands that would produce output or
errors).

There's really no way to be more precise without a copy of the file's
content for analysis, and some knowledge of how and in what environment
the OP attempted to execute it.  And we all know that these things will
not be provided.

[toc] | [prev] | [next] | [standalone]

#201939

On 10/31/2018 09:27 AM, Reco wrote:
> 	Hi.
> 
> On Wed, Oct 31, 2018 at 09:14:40AM -0500, Richard Owlett wrote:
>> Debian 9.1 with MATE installed from DVD set.
>>
>> Due a non-reproducible sequence of events, a binary executable was over written by the contents of a man page in pure text format. For unknown reason, the
>> resulting file was tagged as executable.
> 
> Replace your HDD today, don't give it another chance to corrupt your
> data.
> 

Cannot reproduce detailed PEBKAC ;<

> 
>> A custom MATE launcher pointed the corrupted file.
>> When the launcher icon was clicked there was no response whatsoever.
>> Including *NO ERROR MESSAGE*
>> Is this a bug or a feature?
>> If a feature, why?
> 
> A (mis)feature. Any executable text file without defined shebang is a
> shell script. In this case - a syntactically invalid shell script.
> So it can be executed, but the child shell will exit immediately.

I think I understand.
Thank you.

[toc] | [prev] | [next] | [standalone]

#201941 — Re: Strangeness when binary executable overwritten by text -- bug or feature?

On Wednesday, October 31, 2018 10:14:40 AM Richard Owlett wrote:
> Debian 9.1 with MATE installed from DVD set.
> 
> Due a non-reproducible sequence of events, a binary executable was over
> written by the contents of a man page in pure text format. 

Just to (maybe?) help with the proper focus, was this a human error or 
something that seemed to happen without human intervention?


> For unknown
> reason, the resulting file was tagged as executable.
> 
> A custom MATE launcher pointed the corrupted file.
> When the launcher icon was clicked there was no response whatsoever.
> Including *NO ERROR MESSAGE*
> Is this a bug or a feature?
> If a feature, why?

[toc] | [prev] | [next] | [standalone]

#201942

On 10/31/2018 10:31 AM, rhkramer@gmail.com wrote:
> On Wednesday, October 31, 2018 10:14:40 AM Richard Owlett wrote:
>> Debian 9.1 with MATE installed from DVD set.
>>
>> Due a non-reproducible sequence of events, a binary executable was over
>> written by the contents of a man page in pure text format.
> 
> Just to (maybe?) help with the proper focus, was this a human error or
> something that seemed to happen without human intervention?

As I replied to Reco, "Cannot reproduce detailed PEBKAC ;< "

> 
> 
>> For unknown
>> reason, the resulting file was tagged as executable.
>>
>> A custom MATE launcher pointed the corrupted file.
>> When the launcher icon was clicked there was no response whatsoever.
>> Including *NO ERROR MESSAGE*
>> Is this a bug or a feature?
>> If a feature, why?
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#201943 — Re: Strangeness when binary executable overwritten by text -- bug or feature?

On Wednesday, October 31, 2018 11:45:15 AM Richard Owlett wrote:
> On 10/31/2018 10:31 AM, rhkramer@gmail.com wrote:
> > On Wednesday, October 31, 2018 10:14:40 AM Richard Owlett wrote:
> >> Debian 9.1 with MATE installed from DVD set.
> >> 
> >> Due a non-reproducible sequence of events, a binary executable was over
> >> written by the contents of a man page in pure text format.
> > 
> > Just to (maybe?) help with the proper focus, was this a human error or
> > something that seemed to happen without human intervention?
> 
> As I replied to Reco, "Cannot reproduce detailed PEBKAC ;< "

Ok, then, it doesn't seem to indicate a disk problem (as some seemed to 
suspect).

[toc] | [prev] | [next] | [standalone]

#201945 — Re: Strangeness when binary executable overwritten by text -- bug or feature?

On 2018-10-31, rhkramer@gmail.com <rhkramer@gmail.com> wrote:
>> >> 
>> >> Due a non-reproducible sequence of events, a binary executable was over
>> >> written by the contents of a man page in pure text format.
>> > 
>> > Just to (maybe?) help with the proper focus, was this a human error or
>> > something that seemed to happen without human intervention?
>> 
>> As I replied to Reco, "Cannot reproduce detailed PEBKAC ;< "
>
> Ok, then, it doesn't seem to indicate a disk problem (as some seemed to 
> suspect).
>

Yeah, I didn't get that hard drive failure part either but thought it
was a question of superior knowledge and cleverness on the part of Mr.
R.

The OP probably should have started by saying, "I don't know how, but I
fucked up and overwrote a binary executable with a man page," and then
we all could've had a good laugh. At least he's reading those man pages.
I do note, however, he didn't say *info* page. 

But I don't have a firm grasp of the issues involved here (if there are
any whatsoever), so I'll bow out (once again).

-- 
When you have fever you are heavy and light, you are small and swollen, you
climb endlessly a ladder which turns like a wheel. 
--Jean Rhys, Voyage in the Dark

[toc] | [prev] | [next] | [standalone]

#201946

On 10/31/2018 10:57 AM, rhkramer@gmail.com wrote:
> On Wednesday, October 31, 2018 11:45:15 AM Richard Owlett wrote:
>> On 10/31/2018 10:31 AM, rhkramer@gmail.com wrote:
>>> On Wednesday, October 31, 2018 10:14:40 AM Richard Owlett wrote:
>>>> Debian 9.1 with MATE installed from DVD set.
>>>>
>>>> Due a non-reproducible sequence of events, a binary executable was over
>>>> written by the contents of a man page in pure text format.
>>>
>>> Just to (maybe?) help with the proper focus, was this a human error or
>>> something that seemed to happen without human intervention?
>>
>> As I replied to Reco, "Cannot reproduce detailed PEBKAC ;< "
> 
> Ok, then, it doesn't seem to indicate a disk problem (as some seemed to
> suspect).
> 

Reco's comment that it could be a "(mis)feature" and Greg's response led 
me to investigate further. I'm personally convinced there is a bug 
having some aspects of being a "corner case".

I think I can create some repeatable test cases. It'll take some time.
I may not be a computer geek, but decades in engineering and/or customer 
support can be enlightening.

[toc] | [prev] | [next] | [standalone]

#202091 — IT IS A BUG -- Re: Strangeness when binary executable overwritten by text -- bug or feature?

On 10/31/2018 09:14 AM, Richard Owlett wrote:
> Debian 9.1 with MATE installed from DVD set.
> 
> Due a non-reproducible sequence of events, a binary executable was over 
> written by the contents of a man page in pure text format. For unknown 
> reason, the resulting file was tagged as executable.
> 
> A custom MATE launcher pointed the corrupted file.
> When the launcher icon was clicked there was no response whatsoever.
> Including *NO ERROR MESSAGE*
> Is this a bug or a feature?
> If a feature, why?

Turns out there was a *YUCKY* choice for a default setting.
In the default profile for mate-terminal there is a choice titled
    "Run command as a login shell".
The option is *not* enabled.

That makes the choice "given"(sic) by Caja of
    "Run in terminal"
and
    "Run"
moot.

I consider this a Debian, not Upstream, bug as each distro should be 
responsible for choosing their defaults.

Please contact me offline if you are willing to help a first time bug 
reporter.
TIA

[toc] | [prev] | [next] | [standalone]

#202093 — Re: IT IS A BUG -- Re: Strangeness when binary executable overwritten by text -- bug or feature?

On Sun, Nov 04, 2018 at 07:24:04AM -0600, Richard Owlett wrote:
> Turns out there was a *YUCKY* choice for a default setting.
> In the default profile for mate-terminal there is a choice titled
>    "Run command as a login shell".
> The option is *not* enabled.
> 
> That makes the choice "given"(sic) by Caja of
>    "Run in terminal"
> and
>    "Run"
> moot.

I think your real issue here is that whatever this GUI launcher is,
it does nothing visible when told to launch an executable file that
is not a valid binary. It may have spewed some error into some log
file, but did not pop up a dialog saying "That isn't a valid binary"
or whatever. I don't think that you would get different results no
matter what setting you had for running terminals as login or not.

So if it bothers you that trying to execute garbage produces no
visible feedback, I think that is the bug you should file.

I don't think the login shell setting has anything to do with it. I
can't see why whether it is a login shell or not has any bearing on
what happens when the system tries to execute a file of junk.

$ dd if=/dev/urandom bs=1k count=100 of=/tmp/foo
100+0 records in
100+0 records out
102400 bytes (102 kB) copied, 0.0142731 s, 7.2 MB/s
$ chmod -c +x /tmp/foo
mode of ‘/tmp/foo’ changed from 0644 (rw-r--r--) to 0755 (rwxr-xr-x)
$ /tmp/foo
/tmp/foo: line 10: syntax error near unexpected token `('
b����fooB�B��A�>O���g�  [j%�9̋Ov��g��í�<���ᲾU��9hj�y3j��(�c5�S��S]Ub���l��)�xdƁU]D�Hho{�v�z� �=}3��
                      (���;g�:5��o���a\Yg��/�┘ˬ�R�L┬�·��*→·V&���d6TEeC/�ܨ�A�⎺�)/S���;O]Pڣ��⎼K���G┤�*ɾ%�π�!ĵ�5_";S��] c�$
N≠·(&%↓Z�����V�│���L⎻/─�┌��7�ݢ≤←b���\ʿ┬:���*2��˸�ٜ���⎼>@'M[�;�K�⎺HL≤�ʠ
                       ���→X@�;�πO$⎽@┴��≥⎺�C9π"≠�)8�⎼�R���)π�b�ߨ�┌π��/��Ѝ│ج�
                                                                            ┌���S(�↓⎺��▒�┌�◆ꍺ)H?#&C┘≥?�E_#��O#���1Џ�_�,̆
*ׅM�     J*�c��%�==�KI��KH��GL≥$≤�=�!▮⎼�R�6�װ��UZ�m��d�'1Dsy"}R�)G
                                                                 ��q=[|�5C-M]2����      0��!ԧG=q�j�hj'
$


Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#202127 — Re: IT IS A BUG -- Re: Strangeness when binary executable overwritten by text -- bug or feature?

On 11/04/2018 07:34 AM, Andy Smith wrote:
> On Sun, Nov 04, 2018 at 07:24:04AM -0600, Richard Owlett wrote:
>> Turns out there was a *YUCKY* choice for a default setting.
>> In the default profile for mate-terminal there is a choice titled
>>     "Run command as a login shell".
>> The option is *not* enabled.
>>
>> That makes the choice "given"(sic) by Caja of
>>     "Run in terminal"
>> and
>>     "Run"
>> moot.
> 

> 
> I don't think the login shell setting has anything to do with it. 

You obviously could not be bothered trying it!

[toc] | [prev] | [next] | [standalone]

#202129 — Re: IT IS A BUG -- Re: Strangeness when binary executable overwritten by text -- bug or feature?

Hello,

On Mon, Nov 05, 2018 at 06:18:17AM -0600, Richard Owlett wrote:
> On 11/04/2018 07:34 AM, Andy Smith wrote:
> >I don't think the login shell setting has anything to do with it.
> 
> You obviously could not be bothered trying it!

I don't run any of the same software as you so it would be a lot of
work to try this out. I'm only trying to help you file the right bug
against the right software, but if that is not welcome just say so
and I am happy to leave you to it.

If I understand correctly:

- You have a launcher file that references an executable. In normal
  cases calling the launcher from your desktop environment (I don't
  know if this is by menu or button or something else) causes the
  binary to run. I'm assuming it is a command line binary and you've
  told it to run in a terminal, so, the expected result is a
  terminal window with this program running in it.

- You accidentally overwrote the binary with the textual output of
  "man" resulting in a file which was still marked executable but
  was not a valid Linux binary or script.

- Now when you call the launcher there is no visual feedback to
  indicate that there was a problem.

- You told the launcher to run a terminal with a login shell and now
  it does do something to indicate there was a failure of the
  binary.

- You therefore conclude that every launcher which uses a terminal
  should default to using a login shell and wish to file a bug to
  that effect.

I'm expressing disbelief that the terminal using a login shell is
what is making the difference, but you weren't clear about what the
difference actually is.

So, assuming I understand the situation (as above), what is the
actual difference in behaviour when you run this corrupt binary from
a launcher that is set to terminal+login as opposed to just
terminal?

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

"I remember the first time I made love.  Perhaps it was not love exactly but I
 made it and it still works." — The League Against Tedium

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web