Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 616194 - dev-util/clion-2017.1-r1 subversion plugin fails
Summary: dev-util/clion-2017.1-r1 subversion plugin fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Proxy Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-21 10:37 UTC by juergen.vogl
Modified: 2017-07-23 14:24 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description juergen.vogl 2017-04-21 10:37:47 UTC 
Subversion Plugin fails with message:

Unable to save plugin settings: The plugin Subversion failed to save settings and has been disabled. Please restart CLion

Also happens with dev-util/clion-2017.1
Works with dev-util/clion-2016.2.1
Comment 1 Michael Palimaka (kensington) gentoo-dev 2017-04-23 11:41:20 UTC 
Assigning directly to proxy-maint as the maintainer has no bugzie account.
Comment 2 Christian Strahl 2017-04-26 16:41:52 UTC 
This seems to be an upstream bug:

https://youtrack.jetbrains.com/issue/IDEA-170912
Comment 3 Christian Strahl 2017-05-19 12:10:29 UTC 
(In reply to juergen.vogl from comment #0)
> Subversion Plugin fails with message:
> 
> Unable to save plugin settings: The plugin Subversion failed to save
> settings and has been disabled. Please restart CLion

I just saw that you have voted for the upstream bug.
Can you please share your IDEA.log from 2017.1 upstream?
(Since I don't use subversion, I cannot reproduce this bug.)
Comment 4 Christian Strahl 2017-07-21 14:16:15 UTC 
This problem should be fixed in version 2017.2

@juergen.vogl
could you please close this bug with resolution fixed, if the bug is fixed for you?
Comment 5 Patrice Clement gentoo-dev 2017-07-23 14:24:45 UTC 
(In reply to Christian Strahl from comment #4)
> This problem should be fixed in version 2017.2
> 
> @juergen.vogl
> could you please close this bug with resolution fixed, if the bug is fixed
> for you?

Done.