| Summary: | Cannot configure polari with gnome-online-accounts | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | daniel-wtd <daniel> |
| Component: | polari | Assignee: | Florian Müllner <fmuellner> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | andrea.veri, fmuellner |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-08 16:49:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
daniel-wtd
2016-08-26 12:16:38 UTC
(In reply to Daniel from comment #0) > Open gnome-online-accounts -> no IRC entry there This is a decision of Fedora to compile gnome-online-accounts/gnome-control-center without telepathy support. > Open Polari -> no way to configure your password or channels there That's not correct, polari always had its own UI for setting up networks: click (+) in the header bar, select (Add Network) Hey Florian, thanks for your fast response. :) Very nice! 1. I have installed Polari completely fresh via "dnf install polari" 2. Opened Polari 3. Clicked on the "+" 4. Choosing Freenode 5. Set "fedora" for Roomname (is only one allowed here? 6. Password is empty (I think it is the channel password or, isn't it?) 7. Connected So, now my Questions: Where Can I set additional channels? How can I store my SASL/NickServ Auth? Interestingly, Polari is asking me for a Password, even if I haven't chosen my correct Nick yet. :/ 8. Right click on "Freenode" in the sidenav and choosen Nick & Realname 9. Reconnect 10. Cannot connect to Freenode. -> Error message I cannot see a way to see my Credentials with Polari. I cannot see a way to store my Password during creation. I cannot see a way to enter multiple channels. Is it me or are these options missing? Don't missunderstand me, I really love minimalism and simplicity. But for me some needed options are missing and I cannot use Polari for IRC. (In reply to Daniel from comment #2) > So, now my Questions: > Where Can I set additional channels? There is not way to configure channels, polari remembers joined channels and restores them the next time it starts. Joining multiple channels at once is planned, but the work has stalled (see https://bugzilla.gnome.org/show_bug.cgi?id=763200) > How can I store my SASL/NickServ Auth? SASL isn't supported, and NickServ support is coming in 3.22 (though probably not quite like you expect - you don't configure your password, Polari detects when you use the "identify" password and offers to save it in the keyring). Hmmm, that sounds at least interesting. Currently it is... let me describe it ;) - I add a new nework/server. - Want to join it. - Polari has set my Nick to my Username from Gnome (which is not wrong) - The connection requires a password. (Because the nick is already in use for somebody?) - I rightclick the server and change my nick to my registered nick on freenode. - No connection to freenode is possible due to a "network error". PS: Even If I'm setting a totally rubish nick like TZDBNVrfvndsfgatf, this occures. :/ I don't know what I'm doing wrong and why it feels some kind of complicated. I'm ale to use weechat, xchat, hexchat and had even my time with irssi. With Polari I cannot see my Problem. :'( This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |