| Summary: | Weechat don´t connect anymore | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Holger Mainz <Ed_Werder> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | lewyssmith, marja11 |
| Version: | 8 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Holger Mainz
2021-09-09 10:33:09 CEST
Please give more detailed info about the issue. Is there any error msgs showing up in the app?
Marja Van Waes
2021-09-09 21:57:38 CEST
Keywords:
(none) =>
NEEDINFO I can't reproduce the issue, both in Mageia 8 and in Cauldron weechat connects fine here (I connected to a Mageia channel on Liberachat). That doesn't mean there isn't a bug. It is still possible that you hit a bug, but if so: without more information there is nothing we can do! https://wiki.mageia.org/en/How_to_report_a_bug_properly Think of information like: * the error messages Jani asked for * which IRC network do you try to connect to? * Which channel (if it's public) * are you using SASL? Note that since some months, no one can connect to Freenode with his old credentials. Also, many projects, including Mageia, moved away from Freenode. Status:
NEW =>
UNCONFIRMED
Lewis Smith
2021-09-10 20:05:20 CEST
CC:
(none) =>
lewyssmith Hello, i noticed lots of python errors with the weechat start, and figured, it has something to do with an package update, so i wanted to file. But i am experiencing the same with weechat on raspbian, so, we can pull this bug. Background seems to be, freenode does not eat 6667 connections and wants SASL instead. Error notes 2 ? anotify: No module named 'pynotify' 1422 ? python: stdout/stderr: (?): Traceback (most recent call last): 1422 ? python: stdout/stderr: (?): File "/home/me/.weechat/python/autoload/anotify.py", line 406, in <module> 1422 ? python: stdout/stderr: (?): def a_notify(notification, title, description, priority=pynotify.URGENCY_LOW): 1422 ? python: stdout/stderr: (?): NameError: name 'pynotify' is not defined 1422 ? ? python: Datei "/home/me/.weechat/python/autoload/anotify.py" Analyse nicht möglich 1422 ? python: stdout/stderr: (?): Traceback (most recent call last): 1422 ? python: stdout/stderr: (?): File "/home/me/.weechat/python/autoload/otr.py", line 127, in <module> 1422 ? python: stdout/stderr: (?): import potr 1422 ? python: stdout/stderr: (?): ModuleNotFoundError: No module named 'potr' 1422 ? ? python: Datei "/home/me/.weechat/python/autoload/otr.py" Analyse nicht möglich 1422 ? python: stdout/stderr: (?): File "/home/me/.weechat/python/autoload/grep.py", line 660 1422 ? python: stdout/stderr: (?): except Exception, e: 1422 ? python: stdout/stderr: (?): ^ 1422 ? python: stdout/stderr: (?): SyntaxError: invalid syntax 1422 ? ? python: Datei "/home/me/.weechat/python/autoload/grep.py" Analyse nicht möglich (In reply to Holger Mainz from comment #3) > Background seems to be, freenode does not eat 6667 connections and wants > SASL instead. I believe so; and thank you for this diagnosis. You did not say earlier that the problem was with Freenode; nor whether it happens with other IRC sites. > But i am experiencing the same with weechat on raspbian, so, we can pull > this bug. Thank you, closing. You can re-open the bug if you think it is still valid. Status:
UNCONFIRMED =>
RESOLVED |