Re: How to diagnose and report a bug

[Richard Hector]

On 16/06/18 01:30, Thomas Schmitt wrote:
> Hi,
> 
>> In pcmanfm's address bar, [...]
>> [...]
>> Any recomendations on how to diagnose and report this bug?
> 
> Since there is a package with name "pcmanfm", there is also a tracker page
> for it
>   https://tracker.debian.org/pkg/pcmanfm
> 
> Registered maintainer contact is the mailing list
>   pkg-lxde-maintain...@lists.alioth.debian.org
> There seems to be life
>   
> https://alioth-lists.debian.net/pipermail/pkg-lxde-maintainers/2018-June/thread.html

I wouldn't trust that either it will be around long, or that anyone
useful is reading it - it was supposed to be turned off on 14 April:

https://alioth-lists.debian.net/pipermail/pkg-lxde-maintainers/2018-April/001964.html

links to:
https://alioth-lists.debian.net/pipermail/pkg-lxde-maintainers/attachments/20180402/4b96edbc/attachment.ksh

> So you could ask there for advise, or you could file a bug for package
> "pcmanfm" by following the description at
>   https://www.debian.org/Bugs/Reporting
> This bug report will appear on the mailing list.

I'd choose the bug report.

I've cc'd the uploaders, with a view to getting the maintainer email set
correctly.

Richard



signature.asc
Description: OpenPGP digital signature

Re: How to diagnose and report a bug

[Curt]

On 2018-06-15, Gene Heskett  wrote:
>> >
>> > Obviously one test to attempt to corner the real culprit in this
>> > affair would be to try another editor. How about gedit, for example?
>> > Or have you done that already?
>
> Gedit can be dangerous to your mental health. At least recommend an 
> editor that does not randomly play 52 pickup with your code when you 
> save it. gedit looks nice, but I no longer allow it on the premises.  
> And life is a heck of a lot simpler.
>

Unsubstantiated, anecdotal, unscientific, cantankerous, off-the-wall,
and excessive.

The adjectives, in fact, fail me.

;-)

As OP navigates in the gtk library world, and the other guy (in the
thread I pointed to) successfully used gedit under similar circumstances
to the OP's, I just blurted out gedit without further intellectual ado
for a simple test of a simple hypothesis.

I wasn't asking him or anybody else to change religions or anything.

But you do you have to be prudent here. There are so many sensibilities,
so many toes, so many ways to go wrong and be chastised in all the
innocence of the generosity of your initial impulses.

Jesus, what a world. I think I'll retire and watch some of that funny
football they play here (Spain-Portugal last night lived up to every
and all expectations).

Re: How to diagnose and report a bug

[Gene Heskett]

On Friday 15 June 2018 12:51:08 Curt wrote:

> On 2018-06-15, Curt  wrote:
> > On 2018-06-15, rv riveravaldez  wrote:
> >> Hi, I've found this bug consistently on debian testing (updated):
> >>
> >> Steps to reproduce:
> >> In pcmanfm's address bar, type:
> >> ssh://user@ip
> >> Write password, Enter.
> >> Navigate to the remote machine user's folder.
> >> Open, edit and save a plain text file with leafpad.
> >> Result:
> >> The file gets blanked (no content at all).
> >
> > Obviously one test to attempt to corner the real culprit in this
> > affair would be to try another editor. How about gedit, for example?
> > Or have you done that already?

Gedit can be dangerous to your mental health. At least recommend an 
editor that does not randomly play 52 pickup with your code when you 
save it. gedit looks nice, but I no longer allow it on the premises.  
And life is a heck of a lot simpler.

> > Reading the little thread below gets me to thinking leafpad is the
> > guilty party rather than pcmanfm:
> >
> > https://raspberrypi.stackexchange.com/questions/27576/leafpad-edit-o
> >ver-sftp-connection
>
> Seems there are already bug reports out in the wild:
>
> https://bugs.archlinux.org/task/44681
> https://bugs.launchpad.net/ubuntu/+source/leafpad/+bug/708829
> https://github.com/stevenhoneyman/l3afpad/issues/13
>
> Anyhoo.
>
> >> Mounting the remote machine with sshfs, and doing the next steps
> >> identically, works fine.
> >>
> >> Packages:
> >> leafpad 0.8.18.1-5
> >> pcmanfm  1.3.0-1
> >> ssh1:7.7p1-2
> >>
> >> Any recomendations on how to diagnose and report this bug?
> >>
> >> Thanks a lot.



-- 
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 

Re: How to diagnose and report a bug

[Curt]

On 2018-06-15, Curt  wrote:
> On 2018-06-15, rv riveravaldez  wrote:
>> Hi, I've found this bug consistently on debian testing (updated):
>>
>> Steps to reproduce:
>> In pcmanfm's address bar, type:
>> ssh://user@ip
>> Write password, Enter.
>> Navigate to the remote machine user's folder.
>> Open, edit and save a plain text file with leafpad.
>> Result:
>> The file gets blanked (no content at all).
>
> Obviously one test to attempt to corner the real culprit in this affair
> would be to try another editor. How about gedit, for example? Or have
> you done that already? 
>
> Reading the little thread below gets me to thinking leafpad is the guilty 
> party
> rather than pcmanfm:
>
> https://raspberrypi.stackexchange.com/questions/27576/leafpad-edit-over-sftp-connection

Seems there are already bug reports out in the wild:

https://bugs.archlinux.org/task/44681
https://bugs.launchpad.net/ubuntu/+source/leafpad/+bug/708829
https://github.com/stevenhoneyman/l3afpad/issues/13

Anyhoo.
>> Mounting the remote machine with sshfs, and doing the next steps
>> identically, works fine.
>>
>> Packages:
>> leafpad 0.8.18.1-5
>> pcmanfm  1.3.0-1
>> ssh1:7.7p1-2
>>
>> Any recomendations on how to diagnose and report this bug?
>>
>> Thanks a lot.
>>
>>
>
>


-- 

Re: How to diagnose and report a bug

[Curt]

On 2018-06-15, rv riveravaldez  wrote:
> Hi, I've found this bug consistently on debian testing (updated):
>
> Steps to reproduce:
> In pcmanfm's address bar, type:
> ssh://user@ip
> Write password, Enter.
> Navigate to the remote machine user's folder.
> Open, edit and save a plain text file with leafpad.
> Result:
> The file gets blanked (no content at all).

Obviously one test to attempt to corner the real culprit in this affair
would be to try another editor. How about gedit, for example? Or have
you done that already? 

Reading the little thread below gets me to thinking leafpad is the guilty party
rather than pcmanfm:

https://raspberrypi.stackexchange.com/questions/27576/leafpad-edit-over-sftp-connection

> Mounting the remote machine with sshfs, and doing the next steps
> identically, works fine.
>
> Packages:
> leafpad 0.8.18.1-5
> pcmanfm  1.3.0-1
> ssh1:7.7p1-2
>
> Any recomendations on how to diagnose and report this bug?
>
> Thanks a lot.
>
>


-- 

Re: How to diagnose and report a bug

[Thomas Schmitt]

Hi,

> In pcmanfm's address bar, [...]
> [...]
> Any recomendations on how to diagnose and report this bug?

Since there is a package with name "pcmanfm", there is also a tracker page
for it
  https://tracker.debian.org/pkg/pcmanfm

Registered maintainer contact is the mailing list
  pkg-lxde-maintain...@lists.alioth.debian.org
There seems to be life
  
https://alioth-lists.debian.net/pipermail/pkg-lxde-maintainers/2018-June/thread.html

So you could ask there for advise, or you could file a bug for package
"pcmanfm" by following the description at
  https://www.debian.org/Bugs/Reporting
This bug report will appear on the mailing list.


Have a nice day :)

Thomas

How to diagnose and report a bug

[rv riveravaldez]

Hi, I've found this bug consistently on debian testing (updated):

Steps to reproduce:
In pcmanfm's address bar, type:
ssh://user@ip
Write password, Enter.
Navigate to the remote machine user's folder.
Open, edit and save a plain text file with leafpad.

Result:
The file gets blanked (no content at all).

Mounting the remote machine with sshfs, and doing the next steps
identically, works fine.

Packages:
leafpad 0.8.18.1-5
pcmanfm  1.3.0-1
ssh1:7.7p1-2

Any recomendations on how to diagnose and report this bug?

Thanks a lot.