[Bug 1160091] New: Boinc Manager fails to auto-connect to localhost on application start
http://bugzilla.opensuse.org/show_bug.cgi?id=1160091 Bug ID: 1160091 Summary: Boinc Manager fails to auto-connect to localhost on application start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: marix@marix.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- When starting up the Boinc Manager application (boinc-manager) it fails to utilise the credentials in gui_rpc_auth.cfg to automatically connect to the Boinc client running on localhost. Weirdly, the automatic connection to localhost does work if the Boinc Manager is started automatically by KDEs session restore. This works even when the client was not connected to localhost when the previous KDE session was ended. Using boinccmd on the command line also works flawlessly. My initial assumption was that this was somehow related to the desktop file of the Boinc manager. However, explicitly launching boinc-manager from the command line and thus bystepping the desktop file shows the same issue. The behaviour I'd expect would be for the client to behave identical when being launched via the application launcher and via KDE's session restore mechanism, ideally auto-connecting successfully in both cases. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160091 http://bugzilla.opensuse.org/show_bug.cgi?id=1160091#c1 --- Comment #1 from Matthias Bach <marix@marix.org> --- Side note: The password is also not read when explicitly connecting to localhost via the system selection in the file menu and not explicitly providing a connection password. However, I am not sure if it is supposed to read gui_rpc_auth.cfg in this case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160091 http://bugzilla.opensuse.org/show_bug.cgi?id=1160091#c2 Christian Wittmer <chris@computersalat.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |marix@marix.org Flags| |needinfo?(marix@marix.org) --- Comment #2 from Christian Wittmer <chris@computersalat.de> --- is this still valid ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160091 http://bugzilla.opensuse.org/show_bug.cgi?id=1160091#c3 Matthias Bach <marix@marix.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(marix@marix.org) | --- Comment #3 from Matthias Bach <marix@marix.org> --- Thanks for reminding me of this, Christian. I fear the issue itself is still valid. However, I have meanwhile worked around this by specifying the Boinc data directory in /etc/boinc-client/config.properties. While I understand why this causes Boinc to properly find the data directory and thus successfully connect, it is still unclear to me why just having a proper gui_rpc_auth.cfg causes this weird behaviour where an applications start during a session behaves differently than the application being started during a session resumption. Given that a workaround exists, the age of this report, and the fact that this will only ever hit people like me running weird set-ups with non-default Boinc data directories, its probably fair to close this as a won't-fix or a works-for-me. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com