Gajim - 2018-07-20

  1. concerto I suddenly can't seem to enable the OMEMO plugin
  2. concerto Warning: Error: cannot import name 'MamMessageReceivedEvent'
  3. lovetox concerto, are you using gajim master?
  4. lovetox if so then you should also update the plugins
  5. concerto lovetox: yeah, and I did - it's after that that this happened o.o
  6. lovetox even after restart?
  7. lovetox there is no MamMessageReceivedEvent in the plugins codebase
  8. lovetox so this would suprise me
  9. concerto ._.
  10. concerto lovetox: restart seems to have fixed it. Odd.
  11. lovetox no not really, plugin updating without restart does usually weird things
  12. rom1dep just http-uploaded something in a MUC from gajim, the message came up as authored by <muc's JID>. Seems awfully wrong. Gajim 1.0.3/Windows64
  13. lovetox you mean the full jid`
  14. lovetox ?
  15. concerto lovetox: can that be fixed? Plugins should be updateable without restarting...and it'd be nice to have them update automatically while we're at it.
  16. concerto (better UX)
  17. concerto (better UX, more layperson friendly)
  18. lovetox normal users dont use dev versions
  19. lovetox and get their plugins from the distribution
  20. lovetox not from the plugin installer
  21. lovetox im not so keen on putting more work into the plugin installer, and to duplicate already existing software distribution systems
  22. lovetox we maintain it only for windows and mac
  23. lovetox which have no distribution system
  24. concerto Hm...fair enough
  25. lovetox but plugin reloading is sadly not an easy thing, and auto update may come, i think daniel added that, maybe we can add it when the next version of Gajim is released
  26. concerto Another thing I realized today...the "Join group chat" menu displays titles (?) of MUCs, but doesn't sort them by title. It might be nicer if it did that. 🤔
  27. rom1dep > you mean the full jid` > ? abcd@conference.server.tld, yeah
  28. pep. That's not full, unless resource is empty
  29. pep. I guess lovetox was asking for that as well, of the resource was here
  30. lovetox thats more than unusual then
  31. lovetox really weird
  32. pep. if*
  33. stp I just got message from Gajim's OMEMO-plugin that one of my buddys got a new OMEMO-key & while that's true it took one and a half weeks for Gajim to recognize that. Any explanations why that might be?
  34. zuglufttier stp, did you ever write to him in that time?
  35. zuglufttier I think, Gajim will look up the keys once you try to send something.
  36. stp Yes, multiple times successfully from both Gajim and Conversations, but his replies only showed up in Conversations.
  37. zuglufttier Because the messages where not encrypted for your gajim.
  38. Link Mauve lovetox, you may consider adding Gajim to this page:
  39. Link Mauve Or asterix.
  40. stp Yes, but I wonder how could such a delay happen. He said he changed nothing when his new key suddenly showed up in my Gajim.
  41. lovetox not Gajims fault
  42. lovetox Either the server distribution of keys was broken until someone fixed it
  43. lovetox or the device did a bad job at providing it to the server
  44. lovetox problem/or good thing is with omemo, once you have a session, it is intependent from the server
  45. lovetox so you dont notice that the server distribution of keys is broken, because you simply need it one single time in one moment
  46. lovetox you notice it if there is a new device and you dont receive it
  47. lovetox but you can always run gajim with -l gajim.plugin_system.omemo=DEBUG
  48. lovetox and we could have found out what the problem was
  49. zuglufttier I also believe it's a server thing, it just makes sense ;)
  50. stp :-) ok!
  51. zuglufttier stp, which servers are involved?
  52. stp just
  53. stp will -l gajim.plugin_system.omemo=DEBUG cause constant writing to harddisk?
  54. zuglufttier It will output something to the console.
  55. zuglufttier I don't think, it will write anything to disk.
  56. stp If the server's key distribution was broken Conversations also would not have received the new key though. We wondered if it hindered the process that we had previosly verified the keys of our Android devices via that barcode scan but we never did the same with Gajim. Could that be the culprit?
  57. zuglufttier Yes!
  58. zuglufttier It is.
  59. zuglufttier After you scan the barcode, Conversations goes into "manual mode".
  60. zuglufttier You have to verify the keys by hand then.
  61. lovetox zuglufttier, but that does not have anything to do with Gajim
  62. lovetox the problem was that the key did not arrive at Gajim, not that Conversations is in manual mode
  63. zuglufttier "After such a verification happened Conversations will no longer blindly trust new devices that are created after the verification."
  64. zuglufttier From:
  65. stp Yeah, it worked between Conversations with the new key before we verified that new key.
  66. zuglufttier lovetox, you're right, the key should have arrived anyway...
  67. lovetox speculating does not solve anything, next time we just need debug logs
  68. lovetox then one can say what is going on
  69. stp I'll need to read that linked page later on. Yes, if one of my contacts with a verified key gets a new device I'll log everything.
  70. stp Last question for today: Any news on the Windows nightlies?
  71. lovetox yeah it will be broken for a longer time, until python 3.7.1 is released
  72. stp ok, but is there any place I could grab the latest there was?
  73. stp My current is from 2018-06-07
  74. lovetox no
  75. lovetox sadly server deletes the files
  76. lovetox also there is not really something you need that was done in the last month
  77. stp Allright, thanks!
  78. Link Mauve
  79. bot bodtx created an issue in _gajim_ < >: #9254: < Fltapack 1.0.3 plugin URL preview KO >
  80. Daniel concerto, auto update for plugins is on my list, last time I implemented it something went wrong with plugin reloading while gajim is running. I will re-implement it when I'm back home (but coming home is going to take some more months) ;)
  81. bot Daniel Brötzmann closed an issue in _gajim_ < >: #9254: < Fltapack 1.0.3 plugin URL preview KO >
  82. Link Mauve lovetox, re, you may want to use log.warning('stuff:', exc_info=True) instead, it’s exactly what log.exception() does but with log.error() instead.
  83. Link Mauve Logging the exception itself won’t give you the full traceback.
  84. lovetox im not sure im getting what you mean
  85. lovetox log.warning is like log.error()?
  86. lovetox or log.exception is a log.error
  87. lovetox ah i get it
  88. lovetox kk
  89. lovetox but this would not solve what i wanted to do
  90. lovetox i want to hide the traceback from console
  91. lovetox warning prints also to console always
  92. lovetox i just log the exception, because this is badly solved right now, in the future i want to catch the specific exceptions and act differently on some
  93. Link Mauve Oh, I see.
  94. lovetox originally my intention was to gather exceptions that could arise
  95. lovetox but then i had no time, and people posted these exceptions as bugs
  96. Link Mauve Ah, yeah…
  97. Link Mauve People don’t understand the difference between warning, error and debug.
  98. lovetox ah, its a honest mistake, something doesnt work, they start gajim from console, and get tracebacks posted there, naturally they wonder if this is cause for their problem
  99. bot Goran Mekić created an issue in _gajim_ < >: #9255: < Unable to get local issuer certificate with LetsEncrypt cert >
  100. bot redrosa created an issue in _gajim-plugins_ < >: #334: < Error when I try to "Start a Chat" on latest version in Fedora 28 >
  101. bot redrosa closed an issue in _gajim-plugins_ < >: #334: < Error when I try to "Start a Chat" on latest version in Fedora 28 >
  102. Link Mauve % gajim-history-manager /usr/lib/python3.7/site-packages/gajim/common/ PyGIWarning: Farstream was imported without specifying a version first. Use gi.require_version('Farstream', '0.2') before import to ensure that the right version gets loaded. from gi.repository import Farstream
  103. Link Mauve It’s funny that the history manager tries to load Jingle stuff. ^^'
  104. bot Philipp Hörist created an issue in _python-nbxmpp_ < >: #53: < Unable to get local issuer certificate with LetsEncrypt cert >
  105. bot Philipp Hörist closed an issue in _gajim_ < >: #9255: < Unable to get local issuer certificate with LetsEncrypt cert >
  106. bot Philipp Hörist created an issue in _gajim_ < >: #9256: < Error when I try to "Start a Chat" on latest version in Fedora 28 >
  107. bot Philipp Hörist pushed 1 commit to branch _refs/heads/master_ of _gajim_ < >: *54b5dec6* < > Mock bookmarks for zeroconf Fixes #9256
  108. lovetox Link Mauve, no not funny, its because Gajim doesnt correctly separate xmpp modules from GUI
  109. lovetox but im in the process of fixing this
  110. bot Goran Mekić modified an issue in _gajim_ < >: #9255: < Unable to get local issuer certificate with LetsEncrypt cert >
  111. bot Goran Mekić closed an issue in _gajim_ < >: #9255: < Unable to get local issuer certificate with LetsEncrypt cert >
  112. bot Philipp Hörist closed an issue in _python-nbxmpp_ < >: #53: < Unable to get local issuer certificate with LetsEncrypt cert >
  113. bot Philipp Hörist pushed 1 commit to branch _refs/heads/master_ of _python-nbxmpp_ < >: *d713ce90* < > Load files from FreeBSD specific location Fixes #53