Terminator java fails on Fedora 27

23 views
Skip to first unread message

Jan Soubusta

unread,
Jan 10, 2018, 4:45:20 PM1/10/18
to terminat...@googlegroups.com
Hi all,
I installed org.jessies.terminator-27.137.7049-2.x86_64.
I had to rebuild rpm using the following command:
rpmrebuild -pe org.jessies.terminator.x86_64.rpm
I removed lines setting permissions on /, /usr, /usr/bin, because it was in conflict with package filesystem.
These permissions are migrated from debian by alien and it would cool, if it can be fixed as well.

Then I execute terminator from both terminal or from applications.
It fails with java stack trace, see attached log.
I execute it as user logged in Gnome.

  Jan Soubusta

terminator-17162.log

Martin Dorey

unread,
Jan 10, 2018, 6:05:27 PM1/10/18
to terminator-users, Jan Soubusta
> I installed org.jessies.terminator-27.137.7049-2.x86_64.

That appears to be up-to-date.

> I removed lines setting permissions on /, /usr, /usr/bin

Which lines are they?  I've looked for but failed to find any of our code that might be doing that.  I've tried to look at the rpm too and failed to find any --scripts or such that might do that.

it was in conflict with package filesystem.

I see the package does contain:

martind@swiftboat:~/jessies/work/terminator/.generated/amd64_Linux/bin$ rpm -qvlp org.jessies.terminator-27.137.7049-2.x86_64.rpm 
drwxr-xr-x    2 root    root                        0 Jan 10 13:58 /
drwxr-xr-x    2 root    root                        0 Jan 10 13:58 /usr
drwxr-xr-x    2 root    root                        0 Jan 10 13:58 /usr/bin

Similar doesn't seem to be the case for the first random small .rpm I pulled off the interwebs:


But does seem to be the same for:


martind@swiftboat:/tmp$ dpkg --contents electric-fence_2.2.5_amd64.deb 
drwxr-xr-x root/root         0 2017-01-29 04:24 ./
drwxr-xr-x root/root         0 2017-01-29 04:24 ./usr/
drwxr-xr-x root/root         0 2017-01-29 04:24 ./usr/lib/

... so I should have taken this at its face value:

These permissions are migrated from debian by alien and it would cool, if it can be fixed as well.

... as meaning that there's a problem with alien rather than with our code.  If there is, then surely someone else will have reported it before.

...

alien: Converted rpm won't be installed on Fedora system

The submitter, presumably the same one who came up with that distressingly general title, helpfully quotes an error message:

	   file /usr/bin from install of pigz-2.3.1-1.i386 conflicts with file from package filesystem-3.2-10.fc19.i686
Suddenly, another meaning for "in conflict with package filesystem" clicks into place.  Yeah, that must have been it.  It's not (yet) noted in the Debian bug but I see it's been reported upstream:

Generated RPM files un-necessarily conflict with package "filesystem"

(That's a better title!)

That ticket's still open and there hasn't been a release since.  https://tracker.debian.org/pkg/alien says that alien is orphaned in Debian (after joey's departure, http://joeyh.name/blog/entry/on_leaving/).  While it's seemingly not orphaned upstream, I don't see any version control system or indeed any source except the most recent release.

On, I guess, to the main course, where you get:

2018-01-10T22:36:12.879+0100 Terminator: Java 1.8.0_151 (VM 25.151-b12, runtime 1.8.0_151-b12)
2018-01-10T22:36:12.879+0100 Terminator: Linux 4.14.11-300.fc27.x86_64/amd64 x4
2018-01-10T22:36:12.879+0100 Terminator: Couldn't start Terminator.
Associated exception:
java.lang.ExceptionInInitializerError
at terminator.Terminator$4.run(Terminator.java:224)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.awt.HeadlessException
at sun.awt.HeadlessToolkit.getMenuShortcutKeyMask(HeadlessToolkit.java:236)
at e.util.GuiUtilities.<clinit>(GuiUtilities.java:29)
... 15 more

That's much like I get if I don't have the DISPLAY variable set:

2018-01-10T13:51:28.1-0800 Terminator: Java 1.8.0_131 (VM 25.131-b11, runtime 1.8.0_131-8u131-b11-1~bpo8+1-b11)
2018-01-10T13:51:28.1-0800 Terminator: Linux 3.16.0-5-amd64/amd64 x8
2018-01-10T13:51:28.1-0800 Terminator: Couldn't start Terminator.
Associated exception:
java.lang.ExceptionInInitializerError
at terminator.Terminator$4.run(Terminator.java:224)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.awt.HeadlessException: 
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
at sun.awt.HeadlessToolkit.getMenuShortcutKeyMask(HeadlessToolkit.java:236)
at e.util.GuiUtilities.<clinit>(GuiUtilities.java:29)
... 15 more

Just that one pesky difference that mine says:

No X11 DISPLAY variable was set, but this program performed an operation which requires it.

... and that we would expect that you *do* have DISPLAY set.  I wonder though if you only have the headless JRE installed.  Hmm, looking at what's in the Debian equivalent, I'm not sure I see why it'd fail.  Ah, if I set this environment variable:

_JAVA_OPTIONS="-Djava.awt.headless=true" terminator

... then I get just the message you got.

--
You received this message because you are subscribed to the Google Groups "terminator-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to terminator-users+unsubscribe@googlegroups.com.
To post to this group, send email to terminator-users@googlegroups.com.
Visit this group at https://groups.google.com/group/terminator-users.
For more options, visit https://groups.google.com/d/optout.

Jan Soubusta

unread,
Jan 11, 2018, 2:37:23 AM1/11/18
to Martin Dorey, terminator-users
Martin,
first of all I would like to thank you for such a quick response!

Unfortunately headless JDK is default in Fedora 27:
yum list installed | grep jdk
java-1.8.0-openjdk-headless.x86_64         1:1.8.0.151-1.b12.fc27      @updates 

yum install java-1.8.0-openjdk

and voila! Terminator works as expected :-)

Thanks

  Jan

čt 11. 1. 2018 v 0:05 odesílatel Martin Dorey <marti...@gmail.com> napsal:
To unsubscribe from this group and stop receiving emails from it, send an email to terminator-use...@googlegroups.com.
To post to this group, send email to terminat...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages