This issue has also been reported against the ownCloud client - see bug 1487700. Description of problem: If you click on the application launcher, the client's settings window isn't shown, even if the app is already running. This is the incorrect behaviour according to the upstream developers [1]. It is also inconsistent with how the ownCloud client behaves on other platforms (I've tested Ubuntu and Arch) as well as the upstream development version [2]. Version-Release number of selected component (if applicable): nextcloud-client-2.3.2-1.fc26.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Find the Nextcloud desktop client launcher, click on it. Actual results: Nothing happens. Expected results: The application window is shown. [1] https://github.com/owncloud/client/issues/5986 [2] https://software.opensuse.org/download/package?project=isv:ownCloud:community:testing&package=owncloud-client
Created attachment 1321069 [details] strace
From Fedora 27, this issue will mean that it won't be possible to access the Nextcloud client window, since status icons won't be displayed by default.
This is a serious issue that needs to be fixed in my opinion. You cannot access Nextcloud's status and settings without some heavy workaround: Installing Top Icons Plus (Gnome Addon) is not enough as the icon is for some reason missing after booting. I have to kill the running nextcloud process and rerun it to see the status icon which lets me access the status and settings window. A startup delay might help to get the icon in Top Icons Plus but this is still a workaround for the workaround: https://help.nextcloud.com/t/no-nextcloud-icon-in-panel-on-mint/10548
Owncloud version of the bugreport https://bugzilla.redhat.com/show_bug.cgi?id=1487700
I am asking Workstation SIG for help, because I cannot figure out where is the bug
Are you using Wayland or Xorg?
I can reproduce this bug using: Fedora 26 Wayland Fedora 26 Xorg Fedora 27 Xorg (I can't easily check Fedora 27 with Wayland due to Nvidia drivers. I'd assume it's the same there.) The special problem using Fedora 27 is, that the status icon isn't shown unless you install some gnome addon to display icons and kill and restart the Nextcloud process. So without knowing and using this workaround you can't control nextcloud in any way. What i've tried so far: - Searched for log files. Didn't find much: The --logfile and --logwindow options only show log items related to sychronization but don't notice if another instance is launched. If another instance is already running the new nextcloud command just returns after a moment without showing or writing any log. - Had a look in "journalctl --follow": There is some nextcloud related stuff but mostly from nautilus and nothing special if a second instance is launched. - Played around with strace: It seems to me that the main instance gets notified when a new nextcloud instance is started as it "stat"s the config file and accesses some socket named "qtsingleapp-Nextcl-84" which seems interesting to me: stat("/home/da/.local/share/data/Nextcloud/nextcloud.cfg", {st_mode=S_IFREG|0664, st_size=592, ...}) = 0 accept4(19, {sa_family=AF_UNIX}, [110->2], SOCK_CLOEXEC) = 32 getsockname(32, {sa_family=AF_UNIX, sun_path="/tmp/qtsingleapp-Nextcl-84"}, [28->35]) = 0 getpeername(32, {sa_family=AF_UNIX}, [35->2]) = 0 getsockopt(32, SOL_SOCKET, SO_TYPE, [1], [4]) = 0 fcntl(32, F_GETFL) = 0x2 (flags O_RDWR) fcntl(32, F_SETFL, O_RDWR|O_NONBLOCK) = 0 ppoll([{fd=32, events=POLLIN}], 1, {tv_sec=30, tv_nsec=0}, NULL, 8 ) = 1 ([{fd=32, revents=POLLIN}], left {tv_sec=29, tv_nsec=996677372}) Here is the full strace output of another run (FDs may have changed): main instance: https://paste.fedoraproject.org/paste/WyLqTwLhVJgtmEHBrhrgrg second instance: https://paste.fedoraproject.org/paste/ykiG6Jc3PKcs9vi7u9dRqg another second instance: https://paste.fedoraproject.org/paste/CUW-Eyfnv6jDA1tjZ~rs-Q Further ideas on how to proceed from here: - Try other packages and/or compile from source to see if the bug is in there. - Try on a fresh install (Worth the effort?) - Have a look at the source code. - Maybe find someone with experience in debugging such issues. I'm new to bugzilla and I hope I'm doing this right. Please tell me if I'm doing anything wrong or if you think I should read some guide first ;)
*** Bug 1487700 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.
Can this issue please get reopened? It still applies to fedora 28, even more so since the topicon plus extension doesn't properly work anymore with gnome-shell 3.28 on wayland (it isn't maintained for a while now). Basicly this bug means the nextcloud client is broken for a default fedaro installation atm, which makes for a pretty bad experience. Related nextcloud issue: https://github.com/nextcloud/desktop/issues/203
*** Bug 1582758 has been marked as a duplicate of this bug. ***
nextcloud-client-2.5.0-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7255a8cc56
nextcloud-client-2.5.0-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-54b3fd08be
nextcloud-client-2.5.0-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b9f641bf49
Please test it and report if there is any need to reconfigure login access mode
nextcloud-client-2.5.0-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-54b3fd08be
nextcloud-client-2.5.0-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b9f641bf49
nextcloud-client-2.5.0-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-7255a8cc56
nextcloud-client-2.5.1-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-117007362a
nextcloud-client-2.5.1-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-184842aa8c
nextcloud-client-2.5.1-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-184842aa8c
nextcloud-client-2.5.1-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-117007362a
nextcloud-client-2.5.2-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c5d5d5aef3
nextcloud-client-2.5.2-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-5705bd6549
nextcloud-client-2.5.2-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c5d5d5aef3
nextcloud-client-2.5.2-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-5705bd6549
nextcloud-client-2.5.2-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.