Re: MousAxess
In message <20140207124551.ga5...@parsifal.org.uk> John-Mark Bell wrote: >On Fri, Feb 07, 2014 at 03:19:20AM -0800, Dave Higton wrote: >> >> Discussion having taken place, all relevant information should go into >> a report in the issue tracker. > >I sense you're missing my point: if the issue is not reported in the >issue tracker, it will not cross the radar of the developers. Discuss >what you want, where you want, but the only sure way of ensuring that a >developer is aware of the issue is to report it on the issue tracker. Is that not the point that I was agreeing with? Dave GET FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at http://www.inbox.com/smileys Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails
Re: Sockets
In message Geoffrey Baxendale wrote: >Yes, seems to work here. Available sockets drop to the low 60s and seem >to stay around there. Agree with both points. >I seem to think that this is subtly different to 1614 which would close >sockets as you opened a new window, but I could be wrong. > >Thanks to JMB for a rapid fix. And, again, thanks to all in the Netsurf team for all their work. Dave GET FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at http://www.inbox.com/smileys Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails
Re: Sockets
In message David Pitt wrote: > Dave Higton, on 7 Feb, wrote: > > > On Thu, 06 Feb 2014 23:38:10 GMT Geoffrey Baxendale wrote: > > > > > In message > > > Dave Higton wrote: > > > > > > > In message > > >> David Pitt wrote: > > [snip] > > > > > > I have resurrected a Socket Counter application, !SockCtr, which > > > > > dates back to the time when Oregano2 managed to do a similar trick. > > > > > It is a frontend to David Ruck's SocketCount. > > >>> > > > > > http://pittdj.co.uk/software/index.htm > [snip] > > > As far as I can tell, 1614 is OK and 1635 not. Don't have any builds > > > between those here. When I have more time I will try and narrow it down > > > further. (All Non JS) > > > > Geoff, can you use SockCtr and see if 1614 reclaims sockets under the same > > circumstances as 1356? This is worth adding to the bug report. > > Or try #1699, bug 2064 is now marked as resolved. > > The socket count has not gone below 60 here so far, having started at 90 on > the Raspberry Pi. > Yes, seems to work here. Available sockets drop to the low 60s and seem to stay around there. I seem to think that this is subtly different to 1614 which would close sockets as you opened a new window, but I could be wrong. Thanks to JMB for a rapid fix. TTFN -- Geoff. Using Acorn StrongARM Kinetic RiscPC. Oxymoron of the day: "Government Organisation"
Re: Sockets
In message <1ae3fc690f8.0729d...@davehigton.me.uk> Dave Higton wrote: > On Thu, 06 Feb 2014 23:38:10 GMT Geoffrey Baxendale wrote: > > > In message > > Dave Higton wrote: > > > >> In message > >> David Pitt wrote: > >> > >> >Geoffrey Baxendale, on 4 Feb, wrote: > >>> > Is it just me, or is Netsurf's sockets system awry. After a modest > browsing session Internet access freezes up due, I think, > to sockets being used up. Qitting Netsurf restores order. It seems to > have started about a couple of weeks ago. Not sure of the exact time. > > Risc Os 6.2 NS R1681. (JSoff) > >>> > >> >The same thing happens here with #1694 on a Raspberry Pi, OS5.21 > >> (31Jan14). > >>> > >> >I have resurrected a Socket Counter application, !SockCtr, which dates > >> back > >> >to the time when Oregano2 managed to do a similar trick. It is a > >> frontend to > >> >David Ruck's SocketCount. > >>> > >> >http://pittdj.co.uk/software/index.htm > >> > >> Thank you for that useful app, David. It confirms Netsurf's problem > >> nicely. The number of sockets starts off for me at 90, and gradually > >> collapses. When it reaches 0, NS can't resolve the link. The number > >> rarely increases at all. > >> > >> But the clincher is: quit NS, and the number instantly goes back up > >> to 90. > >> > >> I'm confirming it with build 1694 and 1615. There's a big gap in > >> the versions I've kept; the latest before 1615 is 1356, which behaves > >> very differently. Curiously, the sockets are recovered not when a > >> page closes, but when a new one is opened. > >> > >> Dave > >> > > As far as I can tell, 1614 is OK and 1635 not. Don't have any builds > > between those here. When I have more time I will try and narrow it down > > further. (All Non JS) > > Geoff, can you use SockCtr and see if 1614 reclaims sockets under the > same circumstances as 1356? This is worth adding to the bug report. > > Dave > Don't suppose there is much point now JMB has fixed whatever was wrong! Thanks! I had been using SockCtr3. Thanks to whoever posted the link to that. There is another prog !SockMgr by Dave Thomas which lists data on all the open sockets. http://www.tristone.co.uk/davespace/software/dpt.html TTFN -- Geoff. Using Acorn StrongARM Kinetic RiscPC. Oxymoron of the day: "Humane Warfare"
Re: Bad archive
On Fri, Feb 07, 2014 at 05:49:57PM -, Dave Lawton wrote: > On Tue, 4 February, 2014 9:04 am, Vincent Sanders wrote: > > > Snip > > > > The CI system is no longer generating jsoff builds at all for any > > target that supports a build with javascript. > > > > The ability to disable javascript as an option remains. > > > > This was a decision made at the developer workshop (it is on the > > whiteboard) > > http://vincentsanders.blogspot.co.uk/2014/01/netsurf-developer-workshop-redux.html > > Hi Vincent, > I may be missing the blindingly obvious, but I can't > find any mention of the above, nor anything relating > to the detail of work done at the developer workshop > on the link you have kindly provided. > > Could you please provide explicit directions ? All the text on the page Vince posted mentions much about what we did at the workshop. It doesn't include direct mention of us no longer building JavaScriptless builds, but then that's a minor detail; we've not supported automatic downloaders etc since we provided RiscPkg files. B.
Re: Bad archive
On Tue, 4 February, 2014 9:04 am, Vincent Sanders wrote: > Snip > > The CI system is no longer generating jsoff builds at all for any > target that supports a build with javascript. > > The ability to disable javascript as an option remains. > > This was a decision made at the developer workshop (it is on the > whiteboard) > http://vincentsanders.blogspot.co.uk/2014/01/netsurf-developer-workshop-redux.html > Hi Vincent, I may be missing the blindingly obvious, but I can't find any mention of the above, nor anything relating to the detail of work done at the developer workshop on the link you have kindly provided. Could you please provide explicit directions ? -- Regards, Dave Lawton HTML emails are just a security risk, and nobody needs that.
Re: Paypal bank transfer
On 20 Jan 2014 as I do recall, Harriet Bazley wrote: > I can't seem to withdraw money to my bank account from Paypal using > Netsurf any more (it just gives a page saying there may have been an > error) -- is it a temporary glitch or have they introduced a JavaScripty > dependency since I last withdrew money in October? > I'm happy to notice that this feature is now working again as of version 1699. The 'Send money' feature also seems to work, although I didn't go all the way and actually dispatch the funds: at any rate Netsurf got past the screen it got stuck on last time. :-) -- Harriet Bazley == Loyaulte me lie == Do not underestimate the power of the Force.
Re: MousAxess
On Fri, 7 Feb 2014 15:21:21 + Vincent Sanders wrote: > As mentioned in previous mails to the list about the new bug system, > yes almost everything got imported from the old system, including > their accounts etc. > > however sourceforge "sanitised" the data they made available to us so > the import is a bit incomplete in places. > > Imported users will need to use the "forgotten password" interface to > re-verify their account. Once verified they can login and change the > email address to something more suitable. > > If (as in your case) they have lost everything, please contact > h...@netsurf-browser.org with a request to change details. > > On this occasion I have reset your account Thank you, Vincent, for speeding up the process. Richard: it's easy to log in to Mantis when you have an account. From there I'm sure it's easy to report an issue. (I'm not going to report a fictitious issue for test purposes, though.) Dave FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more!
Re: MousAxess
> Yes. And I can't log in either (FF, Windows - at work). I can't remember > my credentials. > > I haven't logged in since the bug tracker changed to Mantis. I've also > changed email address some months ago; I can't remember whether I > updated them in the previous bug tracker. So I don't know whether my > credentials have been ported; and even if they have; I can't remember > them :-( As mentioned in previous mails to the list about the new bug system, yes almost everything got imported from the old system, including their accounts etc. however sourceforge "sanitised" the data they made available to us so the import is a bit incomplete in places. Imported users will need to use the "forgotten password" interface to re-verify their account. Once verified they can login and change the email address to something more suitable. If (as in your case) they have lost everything, please contact h...@netsurf-browser.org with a request to change details. On this occasion I have reset your account (davehigton) email to d...@davehigton.me.uk. you now need to retrieve your password and login. -- Regards Vincent http://www.kyllikki.org/
Re: MousAxess
On Fri, Feb 07, 2014 at 02:19:05PM +, Richard Torrens (lists) wrote: > In article <20140207125751.gb5...@parsifal.org.uk>, >John-Mark Bell wrote: > > > You log in, click the "Report Issue" link, fill in the form, and click > > "Submit Report". > > That page, at the bottom has a link: bug reporting interface. > > That takes me to http://bugs.netsurf-browser.org/mantis/my_view_page.php > > which has no "Report Issue" link... > > I suspect the key is the "my_view_page" bit. It probably only works for > logged-in members As I explained in the previous email, you must log in to the bug tracker to report issues. John-Mark.
Re: MousAxess
On Fri, Feb 07, 2014 at 03:09:51PM +, Daniel Silverstone wrote: > > Unfortunately the old tracker was hard for the developers to use and stopped > being accessible from NetSurf entirely thanks to SourceForge fecking up. All of this was covered in Vince's email announcing the new bug tracker: http://vlists.pepperfish.net/pipermail/netsurf-users-netsurf-browser.org/2013-December/012100.html Please read this if you haven't already done so! John-Mark.
Re: MousAxess
On Fri, Feb 07, 2014 at 06:50:56 -0800, Dave Higton wrote: > Yes. And I can't log in either (FF, Windows - at work). I can't remember > my credentials. > > I haven't logged in since the bug tracker changed to Mantis. I've also > changed email address some months ago; I can't remember whether I > updated them in the previous bug tracker. So I don't know whether my > credentials have been ported; and even if they have; I can't remember > them :-( If you've not logged in to Mantis ever, then you don't have any credentials. > The previous bug tracker was easy enough to use. Some of the names it > used were not intuitive; that's the worst I could say about it, i.e. I > regard it as OK. I'll have to see what the new one looks like from > RISC OS NS. Unfortunately the old tracker was hard for the developers to use and stopped being accessible from NetSurf entirely thanks to SourceForge fecking up. D. -- Daniel Silverstone http://www.netsurf-browser.org/ PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69
Re: MousAxess
In article <53d64596f0li...@torrens.org.uk>, Richard Torrens (lists) wrote: > In article <53d63f0cd7brian.jord...@btinternet.com>, >Brian Jordan wrote: [Snip] > > If you haven't yet done so, I'll post yours along with one of my own > > which is a log of I crash I provoked when scrolling with the menu > > button. > Thanks. > It's definitely MoussAxess related. I now do RMKill Moussaxess before > surfing - if I remember! I reported this at 13:59. I received a confirmatory email at 14:16 saying the issue has been referred to Steve Fryatt. Apparently the problem is: "Caused by failed assertion in RISC OS mouse handling: riscos/mouse.c", line 183: ro_mouse_track_start: Assertion failed: ro_mouse_poll_end_callback == NULL && ro_mouse_poll_track_callback == NULL && ro_mouse_poll_data == NULL" -- _ Brian Jordan Virtual RPC-AdjustSA on Windows 8.1 Pro RISC OS 6.20 _ --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
Re: MousAxess
On Fri, 07 Feb 2014 14:19:05 + (GMT) Richard Torrens wrote: > That page, at the bottom has a link: bug reporting interface. > > That takes me to http://bugs.netsurf-browser.org/mantis/my_view_page.php > > which has no "Report Issue" link... > > I suspect the key is the "my_view_page" bit. It probably only works for > logged-in members Yes. And I can't log in either (FF, Windows - at work). I can't remember my credentials. I haven't logged in since the bug tracker changed to Mantis. I've also changed email address some months ago; I can't remember whether I updated them in the previous bug tracker. So I don't know whether my credentials have been ported; and even if they have; I can't remember them :-( I'll try from home tonight. The previous bug tracker was easy enough to use. Some of the names it used were not intuitive; that's the worst I could say about it, i.e. I regard it as OK. I'll have to see what the new one looks like from RISC OS NS. Dave FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth
Re: MousAxess
In article <20140207124551.ga5...@parsifal.org.uk>, John-Mark Bell wrote: > I sense you're missing my point: if the issue is not reported in the > issue tracker, it will not cross the radar of the developers. Discuss > what you want, where you want, but the only sure way of ensuring that a > developer is aware of the issue is to report it on the issue tracker. I first posted here to ascertain that it was indeed an issue and not something peculiar to my set-up. But reporting to the bug-tracker is not easy. Too many hoops to jump through, I think. Although I could see no instructions as to what to do next. I would be happy to email such. I am not prepared to log in and work out how to report when it is unclear how to do so! -- Richard Torrens. http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats and more!
Re: MousAxess
In article <53d63f0cd7brian.jord...@btinternet.com>, Brian Jordan wrote: > In article <53d63916ddli...@torrens.org.uk>, >Richard Torrens (lists) wrote: > [Snip] > > Well I went there, then to the next page. How do I report a bug? > > Life's too short to open accounts and log in or to work out complicated > > routines, sorry. > > If someone else can do this, there are 3 log at > > http://www.torrens.org.uk/documents/Logs/ > If you haven't yet done so, I'll post yours along with one of my own > which is a log of I crash I provoked when scrolling with the menu button. Thanks. It's definitely MoussAxess related. I now do RMKill Moussaxess before surfing - if I remember! -- Richard Torrens. http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats and more!
Re: MousAxess
In article <20140207125751.gb5...@parsifal.org.uk>, John-Mark Bell wrote: > > > That's http://bugs.netsurf-browser.org/ of course. > > > > Well I went there, then to the next page. How do I report a bug? > You log in, click the "Report Issue" link, fill in the form, and click > "Submit Report". That page, at the bottom has a link: bug reporting interface. That takes me to http://bugs.netsurf-browser.org/mantis/my_view_page.php which has no "Report Issue" link... I suspect the key is the "my_view_page" bit. It probably only works for logged-in members -- Richard Torrens. http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats and more!
Re: MousAxess
In article <53d63f0cd7brian.jord...@btinternet.com>, Brian Jordan wrote: [Snip] > If you haven't yet done so, I'll post yours along with one of my own > which is a log of I crash I provoked when scrolling with the menu > button. [Snip] OK. It's done. -- _ Brian Jordan Virtual RPC-AdjustSA on Windows 8.1 Pro RISC OS 6.20 _ --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
Re: MousAxess
In article <53d63916ddli...@torrens.org.uk>, Richard Torrens (lists) wrote: [snip] > Netsurf crashes erratically, but this appears to be caused by MouseAxess. > It is associated with use of the menu button, for instance to scroll the > window. > It is not new - though recent releases may be more sensitive. I have > noticed it most on an Iyonix (5.18). That's out of action, I write now on > an RPC (4.39 (28 Apr 2004) [Kernel 6.80]) where the Logs were generated. It sounds to me as though it just might be RISC OS version related. Here, on VRPC 4.02, I've never seen this behaviour. > These 3 logs were vry close together: it's not difficult to cause it, but > I still have no clue as to the exact button/drag sequence.
Re: MousAxess
In article <53d63916ddli...@torrens.org.uk>, Richard Torrens (lists) wrote: [Snip] > Well I went there, then to the next page. How do I report a bug? > Life's too short to open accounts and log in or to work out complicated > routines, sorry. > If someone else can do this, there are 3 log at > http://www.torrens.org.uk/documents/Logs/ If you haven't yet done so, I'll post yours along with one of my own which is a log of I crash I provoked when scrolling with the menu button. > Netsurf crashes erratically, but this appears to be caused by > MouseAxess. It is associated with use of the menu button, for instance > to scroll the window. [Snip] -- _ Brian Jordan Virtual RPC-AdjustSA on Windows 8.1 Pro RISC OS 6.20 _ --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
Re: MousAxess
On Fri, Feb 07, 2014 at 12:05:12PM +, Richard Torrens (lists) wrote: > In article <53d5cd2686t...@netsurf-browser.org>, >Michael Drake wrote: > > > That's http://bugs.netsurf-browser.org/ of course. > > Well I went there, then to the next page. How do I report a bug? You log in, click the "Report Issue" link, fill in the form, and click "Submit Report". > Life's too short to open accounts and log in or to work out complicated > routines, sorry. The report form requires merely 3 fields to have content. However, the more information you provide in a report, the more likely it will be looked at. A report saying "it crashed", and attaching a log file is very unlikely to have much priority; particularly when other reports contain much more circumstantial information about *what* the user was doing when things went wrong. This kind of information is invaluable when investigating issues, even if it seems irrelevant to the reporter, so please include as much detail as possible when reporting issues -- more information is always better in this case. As for creating an account, we require this so that we can continue to contact the reporter for feedback when things are not clear from the information provided. Anonymous reports prevent this, and are a waste of our time, and the reporter's. As I said in another thread; the *only* place to report issues to the developers is the issue tracker. If you are unable or unwilling to report issues there, then they are guaranteed not to get investigated or fixed, unless someone else happens to report the same issue. John-Mark.
Re: MousAxess
On Fri, Feb 07, 2014 at 03:19:20AM -0800, Dave Higton wrote: > On Thu, 6 Feb 2014 17:25:34 + John-Mark Bell wrote: > > > More generally; all issues should be reported on the issue tracker, with > > sufficient detail to describe the problem fully. Any issue which is not > > reported in this way will almost certainly not be investigated, and will > > certainly not be tracked properly, so will be forgotten. > > > > So, if you want something fixed, then report it on the issue tracker! > > In general, I agree with you. However, the MousAxxess and sockets issues > were not obviously Netsurf's fault. Discussion on list has helped add > information. This discussion would have not taken place if the OP had > done nothing more than reported to the issue tracker. > > Discussion having taken place, all relevant information should go into > a report in the issue tracker. I sense you're missing my point: if the issue is not reported in the issue tracker, it will not cross the radar of the developers. Discuss what you want, where you want, but the only sure way of ensuring that a developer is aware of the issue is to report it on the issue tracker. In fact, if you can go a step further and include a link to the relevant discussion in the mailing list archives, that would be even better! John-Mark.
Re: MousAxess
On Fri, Feb 07, 2014 at 12:05:12PM +, Richard Torrens (lists) wrote: > > Well I went there, then to the next page. How do I report a bug? > > Life's too short to open accounts and log in or to work out complicated > routines, sorry. Then use a stable release :) B.
Re: MousAxess
In article <53d5cd2686t...@netsurf-browser.org>, Michael Drake wrote: > In article <53d4c22179li...@torrens.org.uk>, >Richard Torrens (lists) wrote: > > I hav found Netsurf very inclined to crash. It feels like it's caused > > bey switch bounce, usually from the menu button. But removing MouseAxess > > seems to stop it. > Please could someone who is seeing this crash file a bug report with a > Log file attached. Otherwise it is unlikely ever to be investigated. > Cheers, > That's http://bugs.netsurf-browser.org/ of course. Well I went there, then to the next page. How do I report a bug? Life's too short to open accounts and log in or to work out complicated routines, sorry. If someone else can do this, there are 3 log at http://www.torrens.org.uk/documents/Logs/ Netsurf crashes erratically, but this appears to be caused by MouseAxess. It is associated with use of the menu button, for instance to scroll the window. It is not new - though recent releases may be more sensitive. I have noticed it most on an Iyonix (5.18). That's out of action, I write now on an RPC (4.39 (28 Apr 2004) [Kernel 6.80]) where the Logs were generated. These 3 logs were vry close together: it's not difficult to cause it, but I still have no clue as to the exact button/drag sequence. -- Richard Torrens. http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats and more!
Re: MousAxess
On Thu, 6 Feb 2014 17:25:34 + John-Mark Bell wrote: > More generally; all issues should be reported on the issue tracker, with > sufficient detail to describe the problem fully. Any issue which is not > reported in this way will almost certainly not be investigated, and will > certainly not be tracked properly, so will be forgotten. > > So, if you want something fixed, then report it on the issue tracker! In general, I agree with you. However, the MousAxxess and sockets issues were not obviously Netsurf's fault. Discussion on list has helped add information. This discussion would have not taken place if the OP had done nothing more than reported to the issue tracker. Discussion having taken place, all relevant information should go into a report in the issue tracker. Dave FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium
Re: Sockets
Dave Higton, on 7 Feb, wrote: > On Thu, 06 Feb 2014 23:38:10 GMT Geoffrey Baxendale wrote: > > > In message > > Dave Higton wrote: > > > > > In message > >> David Pitt wrote: [snip] > > > > I have resurrected a Socket Counter application, !SockCtr, which > > > > dates back to the time when Oregano2 managed to do a similar trick. > > > > It is a frontend to David Ruck's SocketCount. > >>> > > > > http://pittdj.co.uk/software/index.htm [snip] > > As far as I can tell, 1614 is OK and 1635 not. Don't have any builds > > between those here. When I have more time I will try and narrow it down > > further. (All Non JS) > > Geoff, can you use SockCtr and see if 1614 reclaims sockets under the same > circumstances as 1356? This is worth adding to the bug report. Or try #1699, bug 2064 is now marked as resolved. The socket count has not gone below 60 here so far, having started at 90 on the Raspberry Pi. -- David Pitt
