Change:
mkDerivation rec { pname = "nextcloud-client"; <del> version = "3.0.3"; </del> <ins> version = "3.1.3"; </ins> src = fetchFromGitHub { owner = "nextcloud"; repo = "desktop"; rev = "v${version}"; <del> sha256 = "0idh8i71jivdjjs2y62l22yl3qxwgcr0hf53dad587bzgkkkr223"; </del> <ins> sha256 = "sha256-8Ql6tOvWOjAvMJA87WlT9TbpnbciBsjDxRuYlMVi/m8="; </ins> }; patches = [ <ins> # Explicitly move dbus configuration files to the store path rather than `/etc/dbus-1/services`. </ins> ./0001-Explicitly-copy-dbus-files-into-the-store-dir.patch ];

Discussion:
Describe the bug Since I last updated, the Nextcloud client consistently crashes. I've installed it via home-manager. To Reproduce Steps to reproduce the behavior: Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(turion): nixpkgs: Maintainer information:
Unfortunately I'm not familiar with , but let's try and figure this out. Can you find out the exact channel version of the last configuration before the crash? Is it normal that you have and channels enabled at the same time?
This also happens for me when using on nixos without home-manager.
Do you have any interesting error messages apart from the segfault when running the client with debug enabled:
No but I made an odd observation. I wanted to check if 3.0.2 also crashes so I reverted in my nixpkgs. As I expected version 3.0.2 did not crash. So "un-reverted" the above commita and went back to 3.0.3. And to my suprise it is working now too. What I don't know know is if the problem was that I went from an older version (3.0.0 or 3.0.1, unfortunatly I ran garbage collect so I don't know) directly to 3.0.3 and there was some incompatiblity in the config that was fixed by having 3.0.2 in between?
I was able to reproduce the issue locally after switching temporarily from to . I would guess it's an upstream bug.
Would you be able to checkout nixpkgs at and cherry-pick ? If it also crashes, we know it's an upstream bug.
Just did this myself (after figuring out how that works, hadn't done it in a while) and indeed still crashes after cherry-picking onto , so it's almost certainly an upstream bug.
Note to myself: breaks the Nix build for 3.1.0-rc1:
Now I arrived at the same point as in where the crash is suddenly no longer reproducible.
It would probably help to the nextcloud-client, but I have no clue how this works in Nix. (, as suggested in the , doesn't work.)

If anybody finds out how the package can be built with (or ), it would be possible to have a look at the (identified via and displayed via ), which hopefully has a stacktrace to narrow down the culprit. PS: Other things I tried that didn't work: Adding to the . Running (caused everything to be built with , not just our ).
If anybody just wants a quickfix (using 3.0.2 instead of 3.0.3) you can use this overlay
Would any of you be able to provide ?
Unfortunalty I'm not able to reproduce the issue anymore.
Same here. Just rebuild my system with nextcloud from the channel, seems to work perfectly...
Same :/ very strange. Close? Or write a nixos test and bisect?
In my case the segfault yields: So apparenty, at least for me, the segfault is related to keychain. Guys, what's your working 3.0.3 package hash? I've got a chance to test these two and both segfault in the same way:
Thanks! I have forwarded to the repository. Out of interest, how did you manage to retrieve that backtrace ? Update: Oh, I'm getting the same debug line now. Afaik it's not a proper backtrace though.
It's just what it spews to the stdout :) I was kind of surprised I didn't see that information anywhere above, that's why I posted it. I can try to do the actual backtrace if it may be beneficial.
I have: So probably exactly the same executables. But I didn't observe any segfaults since a few days. Weird.
If you want, we can check whether the build was reproducible:
My binaries have the same checksum so I guess the problem may not be in the nextcloud client itself.
Yes, that would help a lot. I didn't manage to create a debug build of the package.
I also have the same issue. Meanwhile I'm using an older version installed from 20.03 , but I would much prefer have a new version. So far I can still reproduce the bug: However, I'm not sure to know how to get a backtrace, let me know how I could provide more information.

-- EDIT -- Ok, the it appears to be a problem of cache (explains why some of you solved the problem), and the solution is given on the upstream bug report :
Guys just to update, I started using the Nextcloud client from the master branch, currently everything is working fine, but I'm working on a version bump for it.
I already opened the PR, if anyone can test I appreciate :D