Activity for mmartz
-
mmartz modified a wiki page
Metadata_Block
-
Metadata_Block
-
Metadata_Block
-
Metadata_Block
-
Metadata_Block
-
Metadata_Block
-
Additional compatibility fix for SM 2.53.14+
-
Compatibility fix with SM 2.53.14+
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
Metadata_Block
-
Greasemonkey_Manual:API
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
GM_info
-
Greasemonkey_Manual:API
-
Thanks for the tip with apt. Usually I install in KDE with a double click in Dolphin, loading Package Installer, and it complains/finishes with all dependencies but I used dpkg just for this issue to see if I could trace something that might be missing from that methodology... and easier than screenshots. :) Currently I run the server at server.localdomain registered in hosts for about the last year and today when I went to go mark a call as bad in my client this error appeared. I did notice that...
-
Oh one other miscellaneous note... "The ncid clients tries to avoid them, but, apparently, not yours." Did add NCID Android to my Android, about a month or so ago, with a SMS message logged 4 days ago as having a thumbs up emoji received from an iOS phone, and perhaps that's where it is enabling the font failure on the Linux side?
-
Oh one other miscellaneous note... "The ncid clients tries to avoid them, but, apparently, not yours." Did add NCID Android to my Android, about a month or so ago, with a SMS message logged 4 days ago as having a thumbs up emoji received from an iOS phone, and perhaps that's where it is enabling the font failure on the Linux side?
-
Oh one other miscellaneous note... Did add NCID Android to my Android, about a month or so ago, with a SMS message logged 4 days ago as having a thumbs up emoji received from an iOS phone, and perhaps that's where it is enabling the font failure on the Linux side?
-
Thanks for the tip with apt. Usually I install in KDE with a double click in Dolphin, loading Package Installer, and it complains/finishes with all dependencies but I used dpkg just for this issue to see if I could trace something that might be missing from that methodology... and easier than screenshots. :) Currently I run the server at server.localdomain registered in hosts for about the last year and today when I went to go mark a call as bad in my client this error appeared. I did notice that...
-
Oh one other miscellaneous note... Did add NCID Android to my Android, about a month or so ago, with a message logged 4 days ago as having a thumbs up emoji received from an iOS phone, and perhaps that's where it is enabling the font failure on the Linux side?
-
Oh one other miscellaneous note... Did add NCID Android to my Android, about a month or so ago, with a message logged 4 days ago as having a thumbs up emoji, and perhaps that's where it is enabling the font failure on the Linux side?
-
Thanks for the tip with apt. Usually I install in KDE with a double click in Dolphin, loading Package Installer, and it complains/finishes with all dependencies but I used dpkg just for this issue to see if I could trace something that might be missing from that methodology... and easier than screenshots. :) Currently I run the server at server.localdomain registered in hosts for about the last year and today when I went to go mark a call as bad in my client this error appeared. I did notice that...
-
Thanks for the tip with apt. Usually I install in KDE with a double click in Dolphin, loading Package Installer, and it complains/finishes with all dependencies but I used dpkg just for this issue to see if I could trace something that might be missing from that methodology... and easier than screenshots. :) Currently I run the server at server.localdomain registered in hosts for about the last year and today when I went to go mark a call as bad in my client this error appeared. I did notice that...
-
Corrections in console: $ #ncid client v1.11.0 ... bash comment should be $ #ncid client v1.11.0 and 1.12.0 and ... $ #ncid client v1.12.0 ... bash comment should be $ #ncidd server v1.12.0. Apologies for the extra noise and no permission to edit the ticket for the corrections btw. Ref: https://sourceforge.net/p/forge/documentation/Tickets/#creating-and-editing-tickets Thanks.
-
No available working CID clients and latest server dep issue
-
p.s. My modem won't work if I don't use a 2 amp power supply for the Raspberry Pi 3-B. I've found this to be similarly true on HP EliteDesk 800 G1 SFF onboard USB 2.0 and 3.0 (3.1 gen 1) as well. Had to put in a PCIe USB board with a built in power amplifier or external connection to the systems very low powered PSU. Multiple motherboards tested with the Zoom 3095. I presume if any other PSU is bigger than these SFFs have (~130W) and is actively pulling from the PSU it should work (like in one machine...
-
Metadata_Block
-
Metadata_Block
-
Metadata_Block
-
@ed_attfield Thanks for the explanation. This was also on my TODO list when I got back (and I am now) but was beat to it. ;) :)
-
A little update (or step forward perhaps)... For now, you best bet is to stop the ModemManager from starting at boot... What I just did to combat ModemManager (mm) in Ubuntu 18.04.1 (bionic) from interefering is to create/add a udev rule in /etc/udev/rules.d/99-ttyacm.rules (your vendorID and productID will vary depending on device(s)) of: ATTRS{idVendor}=="0803" ATTRS{idProduct}=="3095", ENV{ID_MM_DEVICE_IGNORE}="1" ** and ** modify all related ModemManager.service files from: - ExecStart=/usr/sbin/ModemManager...
-
If you've done make ubuntu at the top level of the ncid source file tree... You mean both at https://sf.net/p/ncid/code/ci/ac7d23/tree/Makefile#l25 and https://sf.net/p/ncid/code/ci/ac7d23/tree/Makefile#l26 currently. ... the path should be /var/lock/LCK..ttyACM0 when the modem is /dev/ttyACM0. As per the ncidd.conf it should be however it was not. It mimicked the # Fedora : /var/lock/lockdev/LCK..modem path which doesn't exist and was reported as a failure in the logs (which have since been cleared...
-
If you've done make ubuntu at the top level of the ncid source file tree... You mean both at https://sf.net/p/ncid/code/ci/ac7d23/tree/Makefile#l25 and https://sf.net/p/ncid/code/ci/ac7d23/tree/Makefile#l26 currently. ... the path should be /var/lock/LCK..ttyACM0 when the modem is /dev/ttyACM0. As per the ncidd.conf it should be however it was not. It mimicked the # Fedora : /var/lock/lockdev/LCK..modem path which doesn't exist and was reported as a failure in the logs (which have since been cleared...
-
If you've done make ubuntu at the top level of the ncid source file tree... You mean both at https://sf.net/p/ncid/code/ci/ac7d23/tree/Makefile#l25 and https://sf.net/p/ncid/code/ci/ac7d23/tree/Makefile#l26 currently. ... the path should be /var/lock/LCK..ttyACM0 when the modem is /dev/ttyACM0. As per the ncidd.conf it should be however it was not. It mimicked the # Fedora : /var/lock/lockdev/LCK..modem path which doesn't exist and was reported as a failure in the logs (which have since been cleared...
-
If you've done make ubuntu at the top level of the ncid source file tree... You mean both at https://sf.net/p/ncid/code/ci/ac7d236/tree/Makefile#l25 and https://sf.net/p/ncid/code/ci/ac7d236/tree/Makefile#l26 currently. ... the path should be /var/lock/LCK..ttyACM0 when the modem is /dev/ttyACM0. As per the ncidd.conf it should be however it was not. It mimicked the # Fedora : /var/lock/lockdev/LCK..modem path which doesn't exist and was reported as a failure in the logs (which have since been cleared...
-
Encountered this particular crash with the client today while trying out NCID from a Mercurial checkout of this project (I had to do a checkout because the ncid_1.10.1-1_amd64.deb and the ncid-1.10.1-src.tar.gz wasn't all that stable with this system for some reason for the past few days). Applied the patch recommended above of: --- a/client/ncid.sh Tue Jan 22 13:08:18 2019 -0500 +++ b/client/ncid.sh Thu Sep 05 02:47:46 2019 -0600 @@ -1295,7 +1295,8 @@ # set temperory color to $linetype # hup array...
-
If you've done make ubuntu at the top level of the ncid source file tree... You mean both at https://sf.net/p/ncid/code/ci/default/tree/Makefile#l25 and https://sf.net/p/ncid/code/ci/default/tree/Makefile#l26 currently. ... the path should be /var/lock/LCK..ttyACM0 when the modem is /dev/ttyACM0. As per the ncidd.conf it should be however it was not. It mimicked the # Fedora : /var/lock/lockdev/LCK..modem path which doesn't exist and was reported as a failure in the logs (which have since been cleared...
-
Metadata_Block
-
Metadata_Block
-
Encountered this particular crash with the client today while trying out NCID from a Mercurial checkout of this project (I had to do a checkout because the ncid_1.10.1-1_amd64.deb and the ncid-1.10.1-src.tar.gz wasn't all that stable with this system for some reason for the past few days). Applied the patch recommended above of: --- a/client/ncid.sh Tue Jan 22 13:08:18 2019 -0500 +++ b/client/ncid.sh Thu Sep 05 02:47:46 2019 -0600 @@ -1295,7 +1295,8 @@ # set temperory color to $linetype # hup array...
-
Home
-
GM_deleteValue
-
GM_getValue
-
GM_listValues
-
GM_setClipboard
-
GM_setValue
-
GM_getResourceText
-
GM_getResourceURL
-
GM_addStyle
-
GM_openInTab
-
GM_log
-
GM_xmlhttpRequest
-
GM_xmlhttpRequest
-
GM_log
-
GM_openInTab
-
GM_registerMenuCommand
-
Metadata_Block
-
Greasemonkey_Manual:Getting_Started
-
Version_history
-
Version_history
-
Version_history
-
Version_history
-
Version_history
-
Greasemonkey_Manual:Getting_Started
-
Greasemonkey_Manual:Getting_Started
-
Greasemonkey_Manual:Getting_Started
-
Version_history
1 >