After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 741062 - java symbol lookup error
java symbol lookup error
Status: RESOLVED FIXED
Product: java-atk-wrapper
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: java-atk-wrapper maintainer(s)
java-atk-wrapper maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-12-03 12:03 UTC by Magdalen Berns (irc magpie)
Modified: 2015-02-27 16:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to fix error (2.14 KB, patch)
2014-12-03 12:17 UTC, Magdalen Berns (irc magpie)
committed Details | Review
output from my installation (62.17 KB, text/plain)
2014-12-06 08:32 UTC, Jose Vilmar Estacio de Souza
  Details
config.log created during the build (27.40 KB, text/plain)
2014-12-06 08:35 UTC, Jose Vilmar Estacio de Souza
  Details
Patch to help with problem (1.14 KB, patch)
2014-12-06 10:52 UTC, Magdalen Berns (irc magpie)
committed Details | Review
log (62.05 KB, text/plain)
2014-12-30 20:52 UTC, Jose Vilmar Estacio de Souza
  Details

Description Magdalen Berns (irc magpie) 2014-12-03 12:03:30 UTC
java: symbol lookup error: /usr/lib/libatk-wrapper.so.0.0.20: undefined symbol: jaw_misc_get_type

It seems some of the misc interface is still hanging around in jawutil.h and AtkWrapper.c and it needs to be tidied away so there are no symbol lookup errors.
Comment 1 Magdalen Berns (irc magpie) 2014-12-03 12:17:37 UTC
Created attachment 292065 [details] [review]
Patch to fix error
Comment 2 Peter Vágner 2014-12-03 12:48:22 UTC
Hello,
I'm the one who brought this issue on a Sonar GNU linux support email list.
Unfortunatelly it appears there is something going wrong with my system.
This is the terminal output before applying the patch.

$ java SwingSet2
java: symbol lookup error: /usr/lib/libatk-wrapper.so.0.0.20: undefined symbol: jaw_misc_get_type

After applying the patch the output differs however I guess this time it is looking for an exported function which should be there.
$ java SwingSet2
java: symbol lookup error: /usr/lib/libatk-wrapper.so.0.0.20: undefined symbol: atk_bridge_adaptor_init

Thanks for all the work and energy you are putting into this I will try to look up more info although at this point I don't know what else I might provide in order to help.

Greetings

Peter
Comment 3 Magdalen Berns (irc magpie) 2014-12-03 12:55:14 UTC
(In reply to comment #2)
> Hello,
> I'm the one who brought this issue on a Sonar GNU linux support email list.
> Unfortunatelly it appears there is something going wrong with my system.
> This is the terminal output before applying the patch.
> 
> $ java SwingSet2
> java: symbol lookup error: /usr/lib/libatk-wrapper.so.0.0.20: undefined symbol:
> jaw_misc_get_type
> 
> After applying the patch the output differs however I guess this time it is
> looking for an exported function which should be there.
> $ java SwingSet2
> java: symbol lookup error: /usr/lib/libatk-wrapper.so.0.0.20: undefined symbol:
> atk_bridge_adaptor_init
> 
> Thanks for all the work and energy you are putting into this I will try to look
> up more info although at this point I don't know what else I might provide in
> order to help.
> 
> Greetings
> 
> Peter

Hi Peter can you try the attached patch out and see how that solves your problem?

Thanks!
Comment 4 Peter Vágner 2014-12-03 13:06:51 UTC
As far as I can see here is a single patch attached to this bug. This is the one I've tested with. In my previous comment to this bug I tried to copy'n'paste two terminal sessions as I've tried to run Swingset2 app. Both of them are showing an error that some symbol is missing. After applying the patch the symbol differs though.
Comment 5 Magdalen Berns (irc magpie) 2014-12-03 13:09:08 UTC
(In reply to comment #4)
> As far as I can see here is a single patch attached to this bug. This is the
> one I've tested with. In my previous comment to this bug I tried to
> copy'n'paste two terminal sessions as I've tried to run Swingset2 app. Both of
> them are showing an error that some symbol is missing. After applying the patch
> the symbol differs though.

Can you paste the output from your terminal so I can see it. Also before reinstalling with the applied patch could you run:

make distclean 

and

git clean -X -f -d
Comment 8 Peter Vágner 2014-12-04 12:51:26 UTC
Hello,
This is my terminal output how I'm building it.
I am not showing how I am installing it as I am using pkgbuild script to install it as an arch package.
At the end of the output there is an error displayed as a result of attempt to run it.
http://pastebin.com/iCdS59gR
Comment 9 Magdalen Berns (irc magpie) 2014-12-04 13:51:27 UTC
(In reply to comment #8)
> Hello,
> This is my terminal output how I'm building it.
> I am not showing how I am installing it as I am using pkgbuild script to
> install it as an arch package.
> At the end of the output there is an error displayed as a result of attempt to
> run it.
> http://pastebin.com/iCdS59gR

Thanks for the information.

Ok, I think I see the where the problem is coming from now. You seem to need to decide whether you want to install this as root or not because when you set /usr as a prefix and you are not root, you are essentially trying to install the wrapper into directories on you machine which root is allowed to write to, but user, peto is not allowed.

If you are keen to do an install without being root then you need to set a prefix you have permissions to write to.

For me that is a directory I created called /opt/gnome/ (which is a convention used many who use a module called jhbuild for development).

After creating that directory with

sudo mkdir /opt/gnome

You can recursively change the ownership of with

sudo chown peto:peto -R /opt/gnome/

then run:

./autogen.sh --prefix=/opt/gnome && make && make install

or if you like, you forget all that stuff and can simply try with

./autogen.sh --prefix=/home/peto/builds && make && make install

Which should also work but since that might get a bit messy in your builds directory so I would recommend using the suggested convention or otherwise something I sometimes do is also

mkdir ~/.local/share

./autogen.sh --prefix=/home/peto/.local/share && make && make install

If you wish to install as root then you can simply run

sudo ./autogen.sh && sudo make && sudo make install

If you could let me know whether you still have this same problem (or any others) just after doing either of those suggestions and we can decide how to deal with things, from there.

Thanks again.
Comment 10 Jose Vilmar Estacio de Souza 2014-12-06 08:32:52 UTC
Created attachment 292230 [details]
output from my installation 

in attach the terminal output generated during the installation.
Comment 11 Jose Vilmar Estacio de Souza 2014-12-06 08:35:46 UTC
Created attachment 292231 [details]
config.log created during the build
Comment 12 Jose Vilmar Estacio de Souza 2014-12-06 08:41:00 UTC
This is my java version:

java version "1.7.0_72"
Java(TM) SE Runtime Environment (build 1.7.0_72-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode)

and the atk version is 2.14.0-1
Comment 13 Magdalen Berns (irc magpie) 2014-12-06 10:11:29 UTC
(In reply to comment #12)
> This is my java version:
> 
> java version "1.7.0_72"
> Java(TM) SE Runtime Environment (build 1.7.0_72-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode)
> 
> and the atk version is 2.14.0-1

Thanks that was really very helpful.

As I am not able to recreate this and you are using an up to date version of ATK I think one of the most likely explanations left seems like this may have something to do with the java version being < 1.8 however it is still hard to say for sure without looking into things more deeply.

I will cc Alejandro (ATK maintainer) to this thread to see if he might be able to offer some insight.

Thanks again.
Comment 14 Magdalen Berns (irc magpie) 2014-12-06 10:15:36 UTC
I have cc'ed Alejandro now just to save confusion for him:

The initial bug in comment #c0 has actually been dealt with, the problem here is actually described in #c2
Comment 15 Magdalen Berns (irc magpie) 2014-12-06 10:20:10 UTC
Jose (or Peter) one other thing that may also be useful to see is a trace for when you try to run SwingSet2. Instructions on getting traces can be found at:

https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#obtain-a-stacktrace

Let us know if you need any help with that.

Thanks again for your perseverance.
Comment 16 Magdalen Berns (irc magpie) 2014-12-06 10:52:18 UTC
Created attachment 292233 [details] [review]
Patch to help with problem

This probably won't solve the problem but it may help somewhat and it seems like a good idea to have done.

I've pushed to master so you don't need to apply to try it out, you can just pull from there.
Comment 17 Peter Vágner 2014-12-06 11:08:51 UTC
Magdalen, I'll be trying steps you recommended however still I wonder why write permissions to the prefix path are needed during the build process. i.e. we should be able to run make without super user privileges and only make install should be running as root. Or is it likelly I am missunderstanding you?
Comment 18 Jose Vilmar Estacio de Souza 2014-12-06 11:15:49 UTC
(In reply to comment #15)
> Jose (or Peter) one other thing that may also be useful to see is a trace for
> when you try to run SwingSet2. Instructions on getting traces can be found at:
> 
> https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#obtain-a-stacktrace
> 
> Let us know if you need any help with that.
> 
> Thanks again for your perseverance.

I am afraid that I can not generate a trace from java.
Here are the results:

Script started on Sat 06 Dec 2014 09:04:45 AM BRST
]0;vilmar@jve:~/Downloads[vilmar@jve Downloads]$ gdb java
GNU gdb (GDB) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from java...(no debugging symbols found)...done.
(gdb) run -jar SwingSet2.jar 
Starting program: /usr/bin/java -jar SwingSet2.jar
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7ffff54a7700 (LWP 24495)]
[New Thread 0x7ffff4501700 (LWP 24496)]
[New Thread 0x7ffff41f8700 (LWP 24497)]
[New Thread 0x7fffec11c700 (LWP 24498)]
[New Thread 0x7fffe7fff700 (LWP 24499)]
[New Thread 0x7fffe7efe700 (LWP 24500)]
[New Thread 0x7fffe6937700 (LWP 24501)]
[New Thread 0x7fffe6836700 (LWP 24502)]
[New Thread 0x7fffe6735700 (LWP 24503)]
[New Thread 0x7fffe6634700 (LWP 24504)]
[New Thread 0x7fffe6533700 (LWP 24505)]
[New Thread 0x7fffe6432700 (LWP 24506)]
[New Thread 0x7fffe6331700 (LWP 24507)]
[New Thread 0x7fffe6230700 (LWP 24508)]
[New Thread 0x7fffe57f1700 (LWP 24509)]
[New Thread 0x7fffe56f0700 (LWP 24510)]
[New Thread 0x7ffff40f7700 (LWP 24512)]
/usr/bin/java: symbol lookup error: /usr/lib/libatk-wrapper.so.0.0.20: undefined symbol: atk_bridge_adaptor_init
[Thread 0x7ffff40f7700 (LWP 24512) exited]
[Thread 0x7fffe56f0700 (LWP 24510) exited]
[Thread 0x7fffe57f1700 (LWP 24509) exited]
[Thread 0x7fffe6230700 (LWP 24508) exited]
[Thread 0x7fffe6331700 (LWP 24507) exited]
[Thread 0x7fffe6432700 (LWP 24506) exited]
[Thread 0x7fffe6533700 (LWP 24505) exited]
[Thread 0x7fffe6634700 (LWP 24504) exited]
[Thread 0x7fffe6735700 (LWP 24503) exited]
[Thread 0x7fffe6836700 (LWP 24502) exited]
[Thread 0x7fffe6937700 (LWP 24501) exited]
[Thread 0x7fffe7efe700 (LWP 24500) exited]
[Thread 0x7fffe7fff700 (LWP 24499) exited]
[Thread 0x7fffec11c700 (LWP 24498) exited]
[Thread 0x7ffff41f8700 (LWP 24497) exited]
[Thread 0x7ffff54a7700 (LWP 24495) exited]
[Thread 0x7ffff7fbc700 (LWP 24491) exited]
[Inferior 1 (process 24491) exited with code 0177]
(gdb)     thread apply all bt 
(gdb) bt
No stack.
(gdb) quit
]0;vilmar@jve:~/Downloads[vilmar@jve Downloads]$ exit


Script done on Sat 06 Dec 2014 09:06:03 AM BRST
Comment 19 Jose Vilmar Estacio de Souza 2014-12-06 11:27:58 UTC
(In reply to comment #16)
> Created an attachment (id=292233) [details] [review]
> Patch to help with problem
> 
> This probably won't solve the problem but it may help somewhat and it seems
> like a good idea to have done.
> 
> I've pushed to master so you don't need to apply to try it out, you can just
> pull from there.


I tried with this patch but the problem persists!
Do you need the config.log again?
Thanks.
Comment 20 Magdalen Berns (irc magpie) 2014-12-06 11:36:27 UTC
(In reply to comment #19)
> (In reply to comment #16)
> > Created an attachment (id=292233) [details] [review] [details] [review]
> > Patch to help with problem
> > 
> > This probably won't solve the problem but it may help somewhat and it seems
> > like a good idea to have done.
> > 
> > I've pushed to master so you don't need to apply to try it out, you can just
> > pull from there.
> 
> 
> I tried with this patch but the problem persists!
> Do you need the config.log again?
> Thanks.

Nah, don't worry about that. I was having a brain fart.

The problem here seems to need fixing in the LDFLAGS linking. However I am still struggling to fathom why I am not able to recreate the same bug. 

One thing that will be handy is if you can run a different stack trace I'm just running through now so I'll post back with some commands to run, if that's not a problem?

Thanks again.
Comment 21 Magdalen Berns (irc magpie) 2014-12-06 11:45:00 UTC
can you run

gbd java
run java -jar SwingSet2
thread apply all bt

Then paste that output please? 

Thanks again
Comment 22 Magdalen Berns (irc magpie) 2014-12-06 12:10:02 UTC
(In reply to comment #18)
> (In reply to comment #15)
> > Jose (or Peter) one other thing that may also be useful to see is a trace for
> > when you try to run SwingSet2. Instructions on getting traces can be found at:
> > 
> > https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#obtain-a-stacktrace
> > 
> > Let us know if you need any help with that.
> > 
> > Thanks again for your perseverance.
> 
> I am afraid that I can not generate a trace from java.

Sorry I just realised what you were saying here on checking out what you did.

To run SwingSet2 on gbd you need to do the following:

java -jar SwingSet2.jar &

This will spit out a number (called the PID) e.g.

java -jar SwingSet2.jar &
[1] 909

Then you run

gdb attach 909

then

thread apply all bt
Comment 23 Magdalen Berns (irc magpie) 2014-12-06 12:38:42 UTC
Here's mine for comparison:

(gdb) thread apply all bt

Thread 15 (Thread 0x7fa5b8cfc700 (LWP 1348))

  • #0 sem_wait
    at ../sysdeps/unix/sysv/linux/x86_64/sem_wait.S line 85
  • #1 os::signal_wait()
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/hotspot/src/os/linux/vm/os_linux.cpp line 2536
  • #2 os::signal_wait()
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/hotspot/src/os/linux/vm/os_linux.cpp line 2560
  • #3 signal_thread_entry(JavaThread*, Thread*)
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/hotspot/src/share/vm/runtime/os.cpp line 244
  • #4 JavaThread::thread_main_inner()
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/hotspot/src/share/vm/runtime/thread.cpp line 1706
  • #5 java_start(Thread*)
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/hotspot/src/os/linux/vm/os_linux.cpp line 827
  • #6 start_thread
    at pthread_create.c line 310
  • #7 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109

Comment 24 Magdalen Berns (irc magpie) 2014-12-06 12:39:36 UTC
(gdb) bt
  • #0 pthread_join
    at pthread_join.c line 92
  • #1 ContinueInNewThread0
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/jdk/src/solaris/bin/java_md_solinux.c line 1034
  • #2 ContinueInNewThread
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/jdk/src/share/bin/java.c line 1909
  • #3 JVMInit
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/jdk/src/solaris/bin/java_md_solinux.c line 1081
  • #4 JLI_Launch
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/jdk/src/share/bin/java.c line 299
  • #5 main
    at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-4.b18.fc21.x86_64/jdk8/jdk/src/share/bin/main.c line 125

Comment 25 Jose Vilmar Estacio de Souza 2014-12-06 13:39:02 UTC
(In reply to comment #22)
> (In reply to comment #18)
> > (In reply to comment #15)
> > > Jose (or Peter) one other thing that may also be useful to see is a trace for
> > > when you try to run SwingSet2. Instructions on getting traces can be found at:
> > > 
> > > https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#obtain-a-stacktrace
> > > 
> > > Let us know if you need any help with that.
> > > 
> > > Thanks again for your perseverance.
> > 
> > I am afraid that I can not generate a trace from java.
> 
> Sorry I just realised what you were saying here on checking out what you did.
> 
> To run SwingSet2 on gbd you need to do the following:
> 
> java -jar SwingSet2.jar &
> 
> This will spit out a number (called the PID) e.g.
> 
> java -jar SwingSet2.jar &
> [1] 909
> 
> Then you run
> 
> gdb attach 909
> 
> then
> 
> thread apply all bt

Script started on Sat 06 Dec 2014 11:34:49 AM BRST
]0;vilmar@jve:~/Downloads[vilmar@jve Downloads]$ java -jar SwingSet2.jar &
[1] 16161
]0;vilmar@jve:~/Downloads[vilmar@jve Downloads]$ java: symbol lookup error: /usr/lib/libatk-wrapper.so.0.0.20: undefined symbol: atk_bridge_adaptor_init
gdb attach 16161
GNU gdb (GDB) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
attach: No such file or directory.
Attaching to process 16161

warning: unable to open /proc file '/proc/16161/status'

warning: unable to open /proc file '/proc/16161/status'
ptrace: No such process.
/data/Downloads/16161: No such file or directory.
(gdb) thread apply all bt
(gdb) bt
No stack.
(gdb) quit
[1]+  Exit 127                java -jar SwingSet2.jar
]0;vilmar@jve:~/Downloads[vilmar@jve Downloads]$ exit
exit

Script done on Sat 06 Dec 2014 11:35:57 AM BRST
Comment 26 Jose Vilmar Estacio de Souza 2014-12-06 13:42:27 UTC
I tried to run with open-jdk but with the same results.
java version "1.7.0_71"
OpenJDK Runtime Environment (IcedTea 2.5.3) (Arch Linux build 7.u71_2.5.3-1-x86_
64)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
Comment 27 Jose Vilmar Estacio de Souza 2014-12-06 13:57:58 UTC
the same problem with java 8.

openjdk version "1.8.0_25"
OpenJDK Runtime Environment (build 1.8.0_25-b18)
OpenJDK 64-Bit Server VM (build 25.25-b02, mixed mode)
Comment 28 Magdalen Berns (irc magpie) 2014-12-06 14:55:04 UTC
(In reply to comment #27)
> the same problem with java 8.
> 
> openjdk version "1.8.0_25"
> OpenJDK Runtime Environment (build 1.8.0_25-b18)
> OpenJDK 64-Bit Server VM (build 25.25-b02, mixed mode)

Can you tell me the output of:

ldd /usr/lib/libatk-wrapper.so.0.0.20
Comment 29 Jose Vilmar Estacio de Souza 2014-12-06 15:31:04 UTC
(In reply to comment #28)
> (In reply to comment #27)
> > the same problem with java 8.
> > 
> > openjdk version "1.8.0_25"
> > OpenJDK Runtime Environment (build 1.8.0_25-b18)
> > OpenJDK 64-Bit Server VM (build 25.25-b02, mixed mode)
> 
> Can you tell me the output of:
> 
> ldd /usr/lib/libatk-wrapper.so.0.0.20



	linux-vdso.so.1 (0x00007fffed7fe000)
	libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00007f8da0442000)
	libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00007f8da0240000)
	libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f8da003c000)
	libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00007f8d9fd86000)
	libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x00007f8d9fb79000)
	libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00007f8d9f92d000)
	libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00007f8d9f5fc000)
	libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00007f8d9f3d7000)
	libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f8d9f186000)
	libgconf-2.so.4 => /usr/lib/libgconf-2.so.4 (0x00007f8d9ef54000)
	libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f8d9ec46000)
	libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f8d9ea2a000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007f8d9e686000)
	libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f8d9e417000)
	libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f8d9e213000)
	libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007f8d9de9b000)
	libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f8d9dc5e000)
	libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f8d9da54000)
	libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00007f8d9d850000)
	libXi.so.6 => /usr/lib/libXi.so.6 (0x00007f8d9d63f000)
	libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00007f8d9d435000)
	libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00007f8d9d229000)
	libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00007f8d9d026000)
	libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f8d9ce23000)
	libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f8d9cc1c000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f8d9c8da000)
	libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f8d9c6c8000)
	libm.so.6 => /usr/lib/libm.so.6 (0x00007f8d9c3c2000)
	libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00007f8d9c1ac000)
	libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f8d9bf54000)
	libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f8d9bcaa000)
	libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00007f8d9b9fd000)
	libEGL.so.1 => /usr/lib/libEGL.so.1 (0x00007f8d9b7d3000)
	libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f8d9b59c000)
	libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x00007f8d9b398000)
	libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00007f8d9b18e000)
	libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f8d9af6b000)
	libz.so.1 => /usr/lib/libz.so.1 (0x00007f8d9ad55000)
	libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f8d9aabb000)
	librt.so.1 => /usr/lib/librt.so.1 (0x00007f8d9a8b2000)
	libffi.so.6 => /usr/lib/libffi.so.6 (0x00007f8d9a6a9000)
	libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0x00007f8d9a480000)
	libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f8d9a237000)
	/usr/lib64/ld-linux-x86-64.so.2 (0x00007f8da08b5000)
	libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007f8d9a01f000)
	libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f8d99df5000)
	libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f8d99bd6000)
	libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f8d999c6000)
	libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0x00007f8d997c4000)
	libxcb-dri2.so.0 => /usr/lib/libxcb-dri2.so.0 (0x00007f8d995be000)
	libxcb-xfixes.so.0 => /usr/lib/libxcb-xfixes.so.0 (0x00007f8d993b6000)
	libxcb-shape.so.0 => /usr/lib/libxcb-shape.so.0 (0x00007f8d991b2000)
	libgbm.so.1 => /usr/lib/libgbm.so.1 (0x00007f8d98fa3000)
	libwayland-client.so.0 => /usr/lib/libwayland-client.so.0 (0x00007f8d98d95000)
	libwayland-server.so.0 => /usr/lib/libwayland-server.so.0 (0x00007f8d98b83000)
	libglapi.so.0 => /usr/lib/libglapi.so.0 (0x00007f8d98958000)
	libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007f8d9874b000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f8d98547000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f8d98340000)
	libxcb-glx.so.0 => /usr/lib/libxcb-glx.so.0 (0x00007f8d98126000)
	libxcb-dri3.so.0 => /usr/lib/libxcb-dri3.so.0 (0x00007f8d97f23000)
	libxcb-present.so.0 => /usr/lib/libxcb-present.so.0 (0x00007f8d97d1f000)
	libxcb-randr.so.0 => /usr/lib/libxcb-randr.so.0 (0x00007f8d97b11000)
	libxcb-sync.so.1 => /usr/lib/libxcb-sync.so.1 (0x00007f8d9790a000)
	libxshmfence.so.1 => /usr/lib/libxshmfence.so.1 (0x00007f8d97706000)
	libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0x00007f8d97500000)
Comment 30 Magdalen Berns (irc magpie) 2014-12-06 16:04:26 UTC
(In reply to comment #29)
> (In reply to comment #28)
> > (In reply to comment #27)
> > > the same problem with java 8.
> > > 
> > > openjdk version "1.8.0_25"
> > > OpenJDK Runtime Environment (build 1.8.0_25-b18)
> > > OpenJDK 64-Bit Server VM (build 25.25-b02, mixed mode)
> > 
> > Can you tell me the output of:
> > 
> > ldd /usr/lib/libatk-wrapper.so.0.0.20
> 
> 
> 
>     linux-vdso.so.1 (0x00007fffed7fe000)
>     libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00007f8da0442000)
>     libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00007f8da0240000)
>     libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f8da003c000)
>     libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00007f8d9fd86000)
>     libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0
> (0x00007f8d9fb79000)
>     libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00007f8d9f92d000)
>     libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00007f8d9f5fc000)
>     libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0
> (0x00007f8d9f3d7000)
>     libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f8d9f186000)
>     libgconf-2.so.4 => /usr/lib/libgconf-2.so.4 (0x00007f8d9ef54000)
>     libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f8d9ec46000)
>     libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f8d9ea2a000)
>     libc.so.6 => /usr/lib/libc.so.6 (0x00007f8d9e686000)
>     libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f8d9e417000)
>     libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f8d9e213000)
>     libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007f8d9de9b000)
>     libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f8d9dc5e000)
>     libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f8d9da54000)
>     libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00007f8d9d850000)
>     libXi.so.6 => /usr/lib/libXi.so.6 (0x00007f8d9d63f000)
>     libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00007f8d9d435000)
>     libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00007f8d9d229000)
>     libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00007f8d9d026000)
>     libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f8d9ce23000)
>     libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f8d9cc1c000)
>     libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f8d9c8da000)
>     libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f8d9c6c8000)
>     libm.so.6 => /usr/lib/libm.so.6 (0x00007f8d9c3c2000)
>     libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00007f8d9c1ac000)
>     libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f8d9bf54000)
>     libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f8d9bcaa000)
>     libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00007f8d9b9fd000)
>     libEGL.so.1 => /usr/lib/libEGL.so.1 (0x00007f8d9b7d3000)
>     libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f8d9b59c000)
>     libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x00007f8d9b398000)
>     libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00007f8d9b18e000)
>     libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f8d9af6b000)
>     libz.so.1 => /usr/lib/libz.so.1 (0x00007f8d9ad55000)
>     libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f8d9aabb000)
>     librt.so.1 => /usr/lib/librt.so.1 (0x00007f8d9a8b2000)
>     libffi.so.6 => /usr/lib/libffi.so.6 (0x00007f8d9a6a9000)
>     libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0x00007f8d9a480000)
>     libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f8d9a237000)
>     /usr/lib64/ld-linux-x86-64.so.2 (0x00007f8da08b5000)
>     libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007f8d9a01f000)
>     libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f8d99df5000)
>     libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f8d99bd6000)
>     libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f8d999c6000)
>     libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0x00007f8d997c4000)
>     libxcb-dri2.so.0 => /usr/lib/libxcb-dri2.so.0 (0x00007f8d995be000)
>     libxcb-xfixes.so.0 => /usr/lib/libxcb-xfixes.so.0 (0x00007f8d993b6000)
>     libxcb-shape.so.0 => /usr/lib/libxcb-shape.so.0 (0x00007f8d991b2000)
>     libgbm.so.1 => /usr/lib/libgbm.so.1 (0x00007f8d98fa3000)
>     libwayland-client.so.0 => /usr/lib/libwayland-client.so.0
> (0x00007f8d98d95000)
>     libwayland-server.so.0 => /usr/lib/libwayland-server.so.0
> (0x00007f8d98b83000)
>     libglapi.so.0 => /usr/lib/libglapi.so.0 (0x00007f8d98958000)
>     libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007f8d9874b000)
>     libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f8d98547000)
>     libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f8d98340000)
>     libxcb-glx.so.0 => /usr/lib/libxcb-glx.so.0 (0x00007f8d98126000)
>     libxcb-dri3.so.0 => /usr/lib/libxcb-dri3.so.0 (0x00007f8d97f23000)
>     libxcb-present.so.0 => /usr/lib/libxcb-present.so.0 (0x00007f8d97d1f000)
>     libxcb-randr.so.0 => /usr/lib/libxcb-randr.so.0 (0x00007f8d97b11000)
>     libxcb-sync.so.1 => /usr/lib/libxcb-sync.so.1 (0x00007f8d9790a000)
>     libxshmfence.so.1 => /usr/lib/libxshmfence.so.1 (0x00007f8d97706000)
>     libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0x00007f8d97500000)

Ok that wasn't what I was expecting. I noticed a few differences about your config log that stood out to me. In particular:

/usr/bin/uname -p = unknown

/bin/arch         = unknown

On my system it comes up with x86_64 which by itself might not matter but then mines also got

configure:2054: loading site script /usr/share/config.site


| if test -n "$host"; then
|     # skip when cross-compiling
|     return 0
| fi
| 
| if test "$prefix" = /usr; then
|     test "$sysconfdir" = '${prefix}/etc' && sysconfdir=/etc
|     test "$sharedstatedir" = '${prefix}/com' && sharedstatedir=/var
|     test "$localstatedir" = '${prefix}/var' && localstatedir=/var
| 
|     ARCH=`uname -m`
|     for i in x86_64 ppc64 s390x aarch64; do
|         if test $ARCH = $i; then
|             test "$libdir" = '${exec_prefix}/lib' && libdir='${exec_prefix}/lib64'
|             break
|         fi
|     done
| fi

I also noticed you don't seem to have a PKG_CONFIG_PATH but that seems like it could be a coincidence and to be honest, I am not sure whether any of this is significant or not, (especially not after seeing your ldd output) so I think what I should probably do t this stage is just install arch on my spare laptop and have a play around to try to get to the bottom of things. Bare with me!
Comment 31 Magdalen Berns (irc magpie) 2014-12-06 16:05:08 UTC
Also, thanks!
Comment 32 Jose Vilmar Estacio de Souza 2014-12-06 18:10:26 UTC
Unless I did something wrong, I believe the problem is introduced by the following commit:

commit ead528835dfeeb57ac1b4167208d6ff5dd6930eb
Author: Magdalen Berns <m.berns@thismagpie.com>
Date:   Sat Nov 15 16:43:48 2014 +0000

    make atk-bridge available but do not use
    
    The up to date way to call atk-bridge is by calling
    atk_bridge_adaptor_init
    
    Bug: https://bugzilla.gnome.org/show_bug.cgi?id=737125


I used git bisect to investigate.

Thanks.
Comment 33 Magdalen Berns (irc magpie) 2014-12-07 00:04:31 UTC
(In reply to comment #32)
> Unless I did something wrong, I believe the problem is introduced by the
> following commit:
> 
> commit ead528835dfeeb57ac1b4167208d6ff5dd6930eb
> Author: Magdalen Berns <m.berns@thismagpie.com>
> Date:   Sat Nov 15 16:43:48 2014 +0000
> 
>     make atk-bridge available but do not use
> 
>     The up to date way to call atk-bridge is by calling
>     atk_bridge_adaptor_init
> 
>     Bug: https://bugzilla.gnome.org/show_bug.cgi?id=737125
> 
> 
> I used git bisect to investigate.
> 
> Thanks.

I can see why it looks that way but I reckon that if the issue was to do with that method call then it would be easier to recreate on fedora. Also because that call does need to be there.

Essentially what I mean to say is that I think where the error message implicates atk_bridge_adaptor_init this is really is a symptom of the problem we are seeing, rather than its root cause.

I think your (and peters) libraries are not being linked properly. Now, I am not sure at this stage whether that is something that should be fixed in java-atk-wrapper, but I have a theory that this problem is presenting itself in arch and not fedora because the build has yet to be properly configured for an arch build.
Comment 34 Magdalen Berns (irc magpie) 2014-12-30 10:53:33 UTC
Update:

The oracle developer I have been chatting to about the wrapper seems to be having a similar problem to you two but on fedora so I think we can rule out any issues relating to fedora only friendly hard coding in the linking process. 

Having looked into things a bit further it seems like the problem is related to the way these extra symbols are being linked.

https://git.gnome.org/browse/at-spi2-atk/tree/atk-adaptor/atkbridge.symbols
https://git.gnome.org/browse/at-spi2-atk/tree/atk-adaptor/Makefile.am#n48

I still can't recreate this so I am suspicious whether there is a dependency check that needs to be added to the wrapper but for now I am going to cc Bastien to try and get his advice because the gitlog and bug about these symbols is not all too informative. Hopefully he might be able to offer some insight into the problem.
Comment 35 Magdalen Berns (irc magpie) 2014-12-30 18:13:31 UTC
I believe not having this dependency might have been the cause of the problem. 

https://bugzilla.gnome.org/show_bug.cgi?id=742122

Essentially it seems like the at-spi2-atk libraries weren't getting properly linked with LIBADD because this dependency had been missing.

Try pulling the latest master and see whether the problem persists or not anyway and let me know.
Comment 36 Jose Vilmar Estacio de Souza 2014-12-30 19:11:39 UTC
(In reply to comment #35)

> 
> Try pulling the latest master and see whether the problem persists or not
> anyway and let me know.

Now I am receiving the following error:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f82b1c4f130, pid=26600, tid=140199983044352
#
# JRE version: OpenJDK Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
# Java VM: OpenJDK 64-Bit Server VM (25.25-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libglib-2.0.so.0+0x8e130]  g_cond_init+0x0
#
# Core dump written. Default location: /data/Downloads/core or core.26600
#
# An error report file with more information is saved as:
# /data/Downloads/hs_err_pid26600.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)
Comment 37 Magdalen Berns (irc magpie) 2014-12-30 19:18:44 UTC
(In reply to comment #36)
> (In reply to comment #35)
> 
> > 
> > Try pulling the latest master and see whether the problem persists or not
> > anyway and let me know.
> 
> Now I am receiving the following error:
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007f82b1c4f130, pid=26600, tid=140199983044352
> #
> # JRE version: OpenJDK Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
> # Java VM: OpenJDK 64-Bit Server VM (25.25-b02 mixed mode linux-amd64
> compressed oops)
> # Problematic frame:
> # C  [libglib-2.0.so.0+0x8e130]  g_cond_init+0x0
> #
> # Core dump written. Default location: /data/Downloads/core or core.26600
> #
> # An error report file with more information is saved as:
> # /data/Downloads/hs_err_pid26600.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.sun.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> Aborted (core dumped)

That's a bit rubbish. 

What did you run to get that?

Can you upload the error log that is reportedly located in /data/Downloads/hs_err_pid26600.log
Comment 38 Jose Vilmar Estacio de Souza 2014-12-30 20:52:30 UTC
Created attachment 293495 [details]
log

I ran the following command:
java -jar SwingSet2.jar
Comment 39 Magdalen Berns (irc magpie) 2014-12-30 21:33:09 UTC
(In reply to comment #38)
> Created an attachment (id=293495) [details]
> log
> 
> I ran the following command:
> java -jar SwingSet2.jar

Thanks. Gladly, I am able to recreate this one.

I am fairly confident that this problem is a different bug altogether but I won't be getting to the bottom of what causes it tonight. If I do create a new bug for this, I'll cc you so you are able to get updates.

Thanks again for your help.
Comment 40 Magdalen Berns (irc magpie) 2014-12-31 18:35:17 UTC
I'm going to go ahead and close this because it has three different bug reports on it already, two of which seem to have been fixed already.

Generally it seems like good practice to try to keep to one single issue per bug report so that people are more easily able to reference specific bug reports in the future and figure out what went down.

Follow up on comment 36 (and above) at bug 742157 for those cc'ed who are interested in doing so.

Thanks!
Comment 41 André Klapper 2015-02-27 16:58:04 UTC
[Moving at-spi/java-atk-wrapper bugs to separate product. See bug 740075]