-
Notifications
You must be signed in to change notification settings - Fork 784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
client crashing at login #1110
Comments
Hi all, I just noticed it might be related to the nvidia propietary driver. If I switch to the open source one, the client works as expected. Regards |
I can confirm the same is happening to me on Manjaro fresh install as of 1330 CDT. Here is the output I get upon crash. As an aside, this was working just fine on an Antergos running KDE as of a couple of days ago, but that was installed back in January.
|
Forgot uname -a output:
|
This seems to be an issue with the 4.19.x branch of the Linux kernel. In trying to debug the issue, I changed to the 4.20.15 kernel and the problem went away. I have a feeling this is also not an issue in the 5.0.x kernel either.
|
Same happens with Windows 10, so it doesn't seem to be an OS issue. |
I can approve connection fails, client freezes, on Manjaro with Kernel 4.19.32. It works as expected with Kernel 5.0.5. |
This looks like a duplicate of #1036. Can you please verify that and close if appropriate? |
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you! |
Just because issues are not being worked on or talked about, they don't go away. Why are they being auto-closed? |
@mcnesium Do you still have the issue? The issue is pretty old. |
@FlexW Haven't seen it in a while, but that is not the point. People voluntarily invest time and effort to file issues as their contribution to projects. It is pretty rude imho to have them closed by bots without a comment of what the current status is. At Nextcloud, you seem to do this a lot with issues contributed by the community, and that is really discouraging for people who want to help improving the software. |
@mcnesium I can understand you and the frustration. When this bug was filled, I and most of the other team members were not working for Nextcloud. We currently try to catch up with all the bugs that are partially really old, never got attention, and prioritize them to see where we need to spend time. The bot helps us to see which bugs are already solved or duplicates of others. We also need to have steps to reproduce the problem. Otherwise, it will be very difficult/impossible to solve them. Diagnosing the cause of a crash where you just have a small crash dump, is an art itself. It's even more difficult if the version of the software where the crash was reported is pretty old, and a big part of the code has been replaced in the meantime. We solved a lot of other crash issues in the meantime, and it could very well be that this crash was also resolved. |
Hi all,
the client running in a fresh installed and updated Ubuntu 18.10 x64 is crashing, either from the appimage or from the repository.
The client vesion is 2.5.1-20181204.111806~cosmic.
It's crashing with this output, just after entering the server url and clicking on Next.
Regards
The text was updated successfully, but these errors were encountered: