Login | Register
My pages Projects Community openCollabNet

Discussions > issues > [Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

subclipse
Discussion topic

There will be a brief maintenance window every Friday at 17:00 Pacific.
For further details, see CollabNet's maintenance and upgrade policy.

Hide all messages in topic

All messages in topic

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author selsemore
Full name Stephen Elsemore
Date 2010-01-12 09:51:42 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889



User selsemore changed the following:

                What |Old value |New value
====================​====================​====================​====================​
                  Status|NEW |RESOLVED
--------------------​--------------------​--------------------​--------------------​
              Resolution| |WONTFIX
--------------------​--------------------​--------------------​--------------------​




------- Additional comments from selsemore at tigris dot org Tue Jan 12 09:51:42 -0800 2010 -------
Closing.

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author ceran
Full name Chris S.
Date 2009-11-11 05:13:48 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from ceran at tigris dot org Wed Nov 11 05:13:46 -0800 2009 -------
Thanks Mark. That workaround did the trick.

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author markphip
Full name Mark Phippard
Date 2009-11-10 06:36:03 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from markphip at tigris dot org Tue Nov 10 06:35:59 -0800 2009 -------
BTW, there is a fix in SVN trunk that has been nominated for backport to the 1.6.x release branch.
However, I tested the fix last week and it did not fix it completely for me.

* r39692
   Fix issue #3498: Subversion password stores freeze Eclipse
   Justification:
     All subclipse users are in great need of this.
   Branch:
     Resolves a minor conflict in libsvn_auth_gnome_ke​yring/gnome_keyring.​c
     where the code changed was refactored on trunk.
     ^/branches/1.6.x-r39692

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author markphip
Full name Mark Phippard
Date 2009-11-10 06:26:57 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from markphip at tigris dot org Tue Nov 10 06:26:56 -0800 2009 -------
We came up with a much better workaround and added it to the FAQ:

http://subclipse.tig​ris.org/wiki/JavaHL#​head-3a1d2d3c54791d2​d751794e5d6645f1d77d​95b32

I forgot this issue existed, else I would have updated it with the workaround too:

There is currently a bug in the new support for GNOME keyring in Subversion 1.6. It works OK when
using the command line, but not when other users of the libraries use it. Until this is fixed, you can
workaround the problem by turning off this feature. To do this, open the file ~/.subversion/config and
add the following:

[auth]
### Set password stores used by Subversion. They should be
### delimited by spaces or commas. The order of values determines
### the order in which password stores are used.
### Valid password stores:
### gnome-keyring (Unix-like systems)
### kwallet (Unix-like systems)
### keychain (Mac OS X)
### windows-cryptoapi (Windows)
password-stores =

The empty value for "password-stores" disables the feature. Passwords will be stored in plain text in
the auth folder as with all previous version of Subversion.

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author ceran
Full name Chris S.
Date 2009-11-10 06:06:03 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889



User ceran changed the following:

                What |Old value |New value
====================​====================​====================​====================​
                      CC|'dodok1' |'ceran,dodok1'
--------------------​--------------------​--------------------​--------------------​




------- Additional comments from ceran at tigris dot org Tue Nov 10 06:06:02 -0800 2009 -------
I'm getting this issue on Ubuntu 9.10. This is killing me. Is there any
workaround? There don't seem to be any
/opt/CollabNet_Subve​rsion/lib/libsvn_aut​h_gnome_keyring* files to remove.

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author stylesen
Full name Senthil Kumaran S
Date 2009-09-30 03:45:18 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from stylesen at tigris dot org Wed Sep 30 03:45:17 -0700 2009 -------
Nominated for backport to subversion 1.6.x branch in r39698, should be available
as a part of future subversion 1.6.x releases.

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author stylesen
Full name Senthil Kumaran S
Date 2009-09-30 02:55:24 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from stylesen at tigris dot org Wed Sep 30 02:55:23 -0700 2009 -------
This is fixed in subversion trunk at r39692.

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author markphip
Full name Mark Phippard
Date 2009-04-09 06:04:35 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from markphip at tigris dot org Thu Apr 9 06:04:35 -0700 2009 -------
This is a bug in Subversion, so it would be expected with any binary that includes the new gnome-keyring
support. It definitely exists with the CollabNet binary.

Removing these three files will fix the problem:

/opt/CollabNet_Subve​rsion/lib/libsvn_aut​h_gnome_keyring-1.so​
/opt/CollabNet_Subve​rsion/lib/libsvn_aut​h_gnome_keyring-1.so​.0
/opt/CollabNet_Subve​rsion/lib/libsvn_aut​h_gnome_keyring-1.so​.0.0.0

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author dodok1
Full name Jozef Kotlár
Date 2009-04-09 02:35:25 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889



User dodok1 changed the following:

                What |Old value |New value
====================​====================​====================​====================​
                      CC|'' |'dodok1'
--------------------​--------------------​--------------------​--------------------​




------- Additional comments from dodok1 at tigris dot org Thu Apr 9 02:35:25 -0700 2009 -------
if interested I can provide more data

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author dodok1
Full name Jozef Kotlár
Date 2009-04-09 02:20:58 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from dodok1 at tigris dot org Thu Apr 9 02:20:57 -0700 2009 -------
I have the same problem with collabnet official client for RedHat (repackaged to
Ubuntu).

I have tried it with or without gnome-keyring-manager (with manager it asks for
confirmation of access, afterwards is the behaviour the same).
On the public repository it works without problem.

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author markphip
Full name Mark Phippard
Date 2009-04-05 08:13:37 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from markphip at tigris dot org Sun Apr 5 08:13:37 -0700 2009 -------
Thanks. I'll report it to SVN. I am pretty sure we got this problem and they fixed it when the feature was
first added. It must have regressed before release.

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author nebojsa
Full name Nebojša Ćosić
Date 2009-04-05 08:02:28 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from nebojsa at tigris dot org Sun Apr 5 08:02:27 -0700 2009 -------
Yes, it seem's to be keyring stuff. I am using Gentoo, so it means that I
compiled it myself, and it was with --with-gnome-keyring flag. When I
recompiled, subclipse started to work.
It looks like keyring related stuff is trying to update some widget, outside of
gui thread. I see this a lot when I develop against SWT.
However, from command line integration with gnome keyring worked ok

[Issue 889] subclipse 1.6.2 on linux creates Invalid thread access

Author markphip
Full name Mark Phippard
Date 2009-04-05 07:36:38 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889






------- Additional comments from markphip at tigris dot org Sun Apr 5 07:36:38 -0700 2009 -------
I have been looking into this. I think it is a problem with the new GNOME keyring support in SVN 1.6.
Where did you get your SVN binaries? Did you build them yourself? Did you build --with-gnome-
keyring?

Renaming the libsvn_auth_gnomekeyring library so that it is not found "fixes" the problem for me. I am
working towards filing a bug with Subversion but wanted to be sure the problem was not with one set of
binaries or a specific GNOME version.

[Issue 889] New - subclipse 1.6.2 on linux creates Invalid thread access

Author nebojsa
Full name Nebojša Ćosić
Date 2009-04-05 05:56:52 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=889
                 Issue #|889
                 Summary|subclipse 1.6.2 on linux creates Invalid thread access
               Component|subclipse
                 Version|current
                Platform|JavaHL
              OS/Version|Linux
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|core
             Assigned to|issues@subclipse
             Reported by|nebojsa






------- Additional comments from nebojsa at tigris dot org Sun Apr 5 05:56:50 -0700 2009 -------
Eclipse-3.4.2, java developes bundle
subclipse 1.6.2
subversion client adapter 1.6.0.2
subversion javahl native library adapter 1.6.0.4
subversion server 1.6.0

Made clean install, installed subclipse via
http://subclipse.tig​ris.org/update_1.6.x​, tried to check out... and it fails
Eclipse log:
Exception in thread "Worker-1" org.eclipse.swt.SWTException: Invalid thread access
    at org.eclipse.swt.SWT.​error(SWT.java:3777)​
    at org.eclipse.swt.SWT.​error(SWT.java:3695)​
    at org.eclipse.swt.SWT.​error(SWT.java:3666)​
    at org.eclipse.swt.widg​ets.Widget.error(Wid​get.java:446)
    at org.eclipse.swt.widg​ets.Widget.checkWidg​et(Widget.java:385)
    at org.eclipse.swt.widg​ets.Control.getShell​(Control.java:2459)
    at org.eclipse.swt.widg​ets.Control.gtk_ente​r_notify_event(Contr​ol.java:2616)
    at org.eclipse.swt.widg​ets.Shell.gtk_enter_​notify_event(Shell.j​ava:1027)
    at org.eclipse.swt.widg​ets.Widget.windowPro​c(Widget.java:1536)
    at org.eclipse.swt.widg​ets.Control.windowPr​oc(Control.java:4506​)
    at org.eclipse.swt.widg​ets.Display.windowPr​oc(Display.java:4099​)
    at org.eclipse.swt.inte​rnal.gtk.OS._gtk_mai​n_do_event(Native Method)
    at org.eclipse.swt.inte​rnal.gtk.OS.gtk_main​_do_event(OS.java:57​92)
    at org.eclipse.swt.widg​ets.Display.eventPro​c(Display.java:1177)​
    at org.tigris.subversio​n.javahl.SVNClient.l​ogMessages(Native Method)
    at org.tigris.subversio​n.javahl.SVNClient.l​ogMessages(SVNClient​.java:313)
    at
org.tigris.subversio​n.svnclientadapter.j​avahl.AbstractJhlCli​entAdapter.getLogMes​sages(AbstractJhlCli​entAdapter.java:2227​)
    at
org.tigris.subversio​n.svnclientadapter.j​avahl.AbstractJhlCli​entAdapter.getLogMes​sages(AbstractJhlCli​entAdapter.java:2257​)
    at
org.tigris.subversio​n.svnclientadapter.A​bstractClientAdapter​.getLogMessages(Abst​ractClientAdapter.ja​va:194)
    at
org.tigris.subversio​n.subclipse.core.res​ources.BaseResource.​getLogMessages(BaseR​esource.java:202)
    at
org.tigris.subversio​n.subclipse.core.com​mands.GetLogsCommand​.run(GetLogsCommand.​java:81)
    at
org.tigris.subversio​n.subclipse.ui.histo​ry.SVNHistoryPage$A​bstractFetchJob.getL​ogEntries(SVNHistory​Page.java:2537)
    at
org.tigris.subversio​n.subclipse.ui.histo​ry.SVNHistoryPage$F​etchLogEntriesJob.ru​n(SVNHistoryPage.jav​a:2411)
    at org.eclipse.core.int​ernal.jobs.Worker.ru​n(Worker.java:55)

and it repeats like that a lot of times

Command line client on the same machine works without problems.
Repository is accessed via http.
Messages per page: