ubuntu18.04打开xmind失败(已解决)

我们是菜鸟,很想起飞,请多点耐心关注和指点
版面规则
我们都知道新人的确很菜,也喜欢抱怨,并且带有浓厚的Windows习惯,但既然在这里询问,我们就应该有责任帮助他们解决问题,而不是直接泼冷水、简单的否定或发表对解决问题没有任何帮助的帖子。乐于分享,以人为本,这正是Ubuntu的精神所在。
回复
云要用
帖子: 4
注册时间: 2018-06-09 17:26
系统: ubuntu18.04
送出感谢: 0
接收感谢: 0

ubuntu18.04打开xmind失败(已解决)

#1

帖子 云要用 » 2018-06-09 17:50

已按提示敲了命令

代码: 全选

sudo sh setup.sh
装好了字体
但是运行Xmind_amd64下的XMind总是出现错误
2018-06-09 17-28-01屏幕截图.png
错误文件
---------------------------------------------------------
既然网上有很多教程,在16.04下是安装成功的,我想可能是java运行环境的问题,看到https://www.jianshu.com/p/2a595afe890c是openjdk9是成功的,就想到要改改java

代码: 全选

sudo update-alternatives --config java
有 2 个候选项可用于替换 java (提供 /usr/bin/java)。

选择 路径 优先级 状态
------------------------------------------------------------
* 0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 自动模式
1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 手动模式
2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 手动模式

要维持当前值[*]请按<回车键>,或者键入选择的编号:2
update-alternatives: 使用 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 来在手动模式中提供 /usr/bin/java (java)
2018-06-15 23-55-32屏幕截图.png
最后花了点时间,把它激活成Xmind Pro版,具体的办法 :em09 呵呵,很简单的
2018-06-16 00-31-19屏幕截图.png
pro版才有的导出pdf
2018-06-16 00-33-26屏幕截图.png
---------------------------------------------------------------------
找了好久看到此贴https://www.jianshu.com/p/d3d8afbb8e6e可以达到同样的效果,做到无公害,就不用上面改全局的java环境
修改Xmind_amd64下的xmind.ini
加入两行

代码: 全选

-vm
/usr/lib/jvm/java-8-openjdk-amd64/bin
搞个图标启动

代码: 全选

sudo gedit /usr/share/applications/xmind.desktop

代码: 全选

[Desktop Entry]
Version = 1.0
Encoding=UTF-8
Type=Application
Name=Xmind
Comment=Xmind
Path=/opt/xmind/XMind_amd64
Exec=/opt/xmind/XMind_amd64/XMind
Icon=/opt/xmind/new_branding_old_logo.png
Terminal=false
Categories=Application
StartupWMClass=XMind
请注意我把文件夹搬到/opt下了,照搬的话会出错的,图标ICON是我在网上找的Icon=/opt/xmind/new_branding_old_logo.png,自带的图标隐藏的比较深难找而且特别小
上次由 云要用 在 2018-06-18 0:23,总共编辑 3 次。
头像
九天星
帖子: 1333
注册时间: 2007-07-14 20:45
送出感谢: 67 次
接收感谢: 38 次

Re: ubuntu18.04打开xmind失败

#2

帖子 九天星 » 2018-06-09 19:47

在软件中心搜XMIND再安装。
云要用
帖子: 4
注册时间: 2018-06-09 17:26
系统: ubuntu18.04
送出感谢: 0
接收感谢: 0

Re: ubuntu18.04打开xmind失败

#3

帖子 云要用 » 2018-06-09 22:58

软件中心里没有XMind?. :Adore
九天星 写了:在软件中心搜XMIND再安装。
云要用
帖子: 4
注册时间: 2018-06-09 17:26
系统: ubuntu18.04
送出感谢: 0
接收感谢: 0

Re: ubuntu18.04打开xmind失败

#4

帖子 云要用 » 2018-06-09 22:59

软件中心里没有XMind?. :Hehe
九天星 写了:在软件中心搜XMIND再安装。
头像
九天星
帖子: 1333
注册时间: 2007-07-14 20:45
送出感谢: 67 次
接收感谢: 38 次

Re: ubuntu18.04打开xmind失败

#5

帖子 九天星 » 2018-06-10 18:12

我怎么有?
E丶游未尽
帖子: 1
注册时间: 2018-06-10 22:25
系统: ubuntu18.04
送出感谢: 0
接收感谢: 0

Re: ubuntu18.04打开xmind失败

#6

帖子 E丶游未尽 » 2018-06-10 22:28

云要用, 兄弟解决了吗,我也同样问题 :Cry
poloshiao
论坛版主
帖子: 18121
注册时间: 2009-08-04 16:33
送出感谢: 21 次
接收感谢: 1934 次

Re: ubuntu18.04打开xmind失败

#7

帖子 poloshiao » 2018-06-11 12:21

2018-06-09 17-28-01屏幕截图.png
把下面指令 複製 貼進終端機 執行
sudo cat /home/go/下载/xmind/workspace/.metadata/.log
把指令及結果直接 選取/複製 貼上來
头像
九天星
帖子: 1333
注册时间: 2007-07-14 20:45
送出感谢: 67 次
接收感谢: 38 次

Re: ubuntu18.04打开xmind失败

#8

帖子 九天星 » 2018-06-11 12:37

链接: https://pan.baidu.com/s/1ZOETQm3K8Lv0EqO9GyTPiw 密码: mvee

DEB包在这里,拿去吧!
云要用
帖子: 4
注册时间: 2018-06-09 17:26
系统: ubuntu18.04
送出感谢: 0
接收感谢: 0

Re: ubuntu18.04打开xmind失败

#9

帖子 云要用 » 2018-06-14 19:39

正文中长长一大段的就是错误的log
poloshiao 写了:
2018-06-09 17-28-01屏幕截图.png
把下面指令 複製 貼進終端機 執行
sudo cat /home/go/下载/xmind/workspace/.metadata/.log
把指令及結果直接 選取/複製 貼上來
头像
Archer123
帖子: 146
注册时间: 2008-05-18 10:16
送出感谢: 2 次
接收感谢: 6 次

Re: ubuntu18.04打开xmind失败(已解决)

#10

帖子 Archer123 » 2018-06-27 17:50

云要用 写了:已按提示敲了命令

代码: 全选

sudo sh setup.sh
装好了字体
但是运行Xmind_amd64下的XMind总是出现错误
2018-06-09 17-28-01屏幕截图.png
---------------------------------------------------------
既然网上有很多教程,在16.04下是安装成功的,我想可能是java运行环境的问题,看到https://www.jianshu.com/p/2a595afe890c是openjdk9是成功的,就想到要改改java

代码: 全选

sudo update-alternatives --config java
有 2 个候选项可用于替换 java (提供 /usr/bin/java)。

选择 路径 优先级 状态
------------------------------------------------------------
* 0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 自动模式
1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 手动模式
2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 手动模式

要维持当前值[*]请按<回车键>,或者键入选择的编号:2
update-alternatives: 使用 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 来在手动模式中提供 /usr/bin/java (java)
2018-06-15 23-55-32屏幕截图.png
最后花了点时间,把它激活成Xmind Pro版,具体的办法 :em09 呵呵,很简单的
2018-06-16 00-31-19屏幕截图.png
pro版才有的导出pdf
2018-06-16 00-33-26屏幕截图.png
---------------------------------------------------------------------
找了好久看到此贴https://www.jianshu.com/p/d3d8afbb8e6e可以达到同样的效果,做到无公害,就不用上面改全局的java环境
修改Xmind_amd64下的xmind.ini
加入两行

代码: 全选

-vm
/usr/lib/jvm/java-8-openjdk-amd64/bin
搞个图标启动

代码: 全选

sudo gedit /usr/share/applications/xmind.desktop

代码: 全选

[Desktop Entry]
Version = 1.0
Encoding=UTF-8
Type=Application
Name=Xmind
Comment=Xmind
Path=/opt/xmind/XMind_amd64
Exec=/opt/xmind/XMind_amd64/XMind
Icon=/opt/xmind/new_branding_old_logo.png
Terminal=false
Categories=Application
StartupWMClass=XMind
请注意我把文件夹搬到/opt下了,照搬的话会出错的,图标ICON是我在网上找的Icon=/opt/xmind/new_branding_old_logo.png,自带的图标隐藏的比较深难找而且特别小


把它激活成Xmind Pro版,具体的办法
求个激活为pro的办法 @云要用
ikt
帖子: 3
注册时间: 2018-05-08 17:38
系统: ubuntu18.04
送出感谢: 1 次
接收感谢: 0

Re: ubuntu18.04打开xmind失败(已解决)

#11

帖子 ikt » 2018-07-03 12:44

本机就openjdk11,改了Xmind.ini,打开还是出错

代码: 全选

!SESSION 2018-07-03 12:40:49.214 -----------------------------------------------
eclipse.buildId=R3.7.7.201801311814
java.version=10.0.1
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=zh_CN
Framework arguments:  -eclipse.keyring @user.home/.xmind/secure_storage_linux
Command-line arguments:  -os linux -ws gtk -arch x86_64 -data ../workspace -eclipse.keyring @user.home/.xmind/secure_storage_linux

!ENTRY org.xmind.cathy 1 0 2018-07-03 12:40:51.477
!MESSAGE Skip unrecognized command line argument: '-eclipse.keyring'

!ENTRY org.xmind.cathy 1 0 2018-07-03 12:40:51.478
!MESSAGE Skip unrecognized command line argument: '@user.home/.xmind/secure_storage_linux'

!ENTRY org.eclipse.osgi.compatibility.state.nl_ko 2 0 2018-07-03 12:40:51.777
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_ko [846]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_zh 2 0 2018-07-03 12:40:51.778
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_zh [850]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_ru 2 0 2018-07-03 12:40:51.778
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_ru [848]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_ja 2 0 2018-07-03 12:40:51.778
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_ja [845]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_de 2 0 2018-07-03 12:40:51.778
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_de [841]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_it 2 0 2018-07-03 12:40:51.778
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_it [844]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_da 2 0 2018-07-03 12:40:51.778
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_da [840]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_fr 2 0 2018-07-03 12:40:51.779
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_fr [843]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_es 2 0 2018-07-03 12:40:51.779
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_es [842]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_pt_BR 2 0 2018-07-03 12:40:51.779
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_pt_BR [847]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_zh_TW 2 0 2018-07-03 12:40:51.779
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_zh_TW [851]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_ar 2 0 2018-07-03 12:40:51.779
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_ar [839]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi.compatibility.state.nl_sl 2 0 2018-07-03 12:40:51.779
!MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_sl [849]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state
  Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state


!ENTRY org.eclipse.osgi 4 0 2018-07-03 12:40:51.780
!MESSAGE 应用程序错误
!STACK 1
org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
	at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386)
	at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:626)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.xmind.cathy.internal.CathyApplication.start(CathyApplication.java:145)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:564)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
	at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
	at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
	... 23 more
Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612
	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
	... 25 more

!ENTRY org.eclipse.e4.ui.workbench 4 0 2018-07-03 12:40:51.809
!MESSAGE FrameworkEvent ERROR
!STACK 0
java.lang.NoClassDefFoundError: javax/annotation/PreDestroy
	at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426)
	at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154)
	at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78)
	at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
	at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74)
	at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:176)
	at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106)
	at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
	at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213)
	at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120)
	at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112)
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156)
	at org.eclipse.osgi.container.Module.publishEvent(Module.java:476)
	at org.eclipse.osgi.container.Module.doStop(Module.java:634)
	at org.eclipse.osgi.container.Module.stop(Module.java:498)
	at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:191)
	at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165)
	at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612
	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
	... 21 more
kuman
帖子: 1
注册时间: 2018-07-18 16:37
系统: ubuntu18.04
送出感谢: 0
接收感谢: 0

Re: ubuntu18.04打开xmind失败(已解决)

#12

帖子 kuman » 2018-07-18 16:41

我的解决方法是,在XMind.ini下面加入
--add-modules=ALL-SYSTEM
然后重新执行 ./XMind就OK了。

我是在这里找到答案的,希望能帮到后面的人。
https://askubuntu.com/questions/1031889 ... rk-anymore
回复

回到 “初学者园地 - Ubuntu 18.04 LTS (Bionic Beaver)”