Arch Linux User Repository

I released a new packaged version of 2.1.3.c that should provide a workaround to the problems reported below.

Use /usr/share/fakturama2/startup_script to start Fakturama (instead of the binary)

Hello so far there seems to be no solution on the manufacturer's side the question arises whether it can be due to eclipse. Anyone have an idea how to check that thanks

@steadfasterX: Thanks! I had the problems with runnings instances in the past. That was solved, but you are right, this could be a problem! For reference: https://www.fakturama.info/community/postid/11264/

@gregorK: can you try to kill all fakturama processes prior to starting it (however a reboot of your machine should do this too ...)

For reference our current problem: https://www.fakturama.info/community/hilfe-bei-installation-und-bedienung/fakturama-unter-ubuntu-lunar-lobster/

FYI: There is also a desktop file performing a clean start! I will post a cross reference there too... No need to discuss this multiple times...

@Helloagain:

ya as said.. digging in the dark here.. I just remembered that I had start issues in the past and got an advice to add that setting in the Fakturama.ini. Can't rem exactly the error but the -vm flag solved it for me at that time so I thought that might help here, too.

java.net.BindException: Die Adresse wird bereits verwendet (Bind failed)

^^ that is likely the root cause. at least that prevents me from starting Fakturama a second time. so as long as that is not solved it won't start for sure. the -clean flag might solve that one though. and no that error is new and was not there in the users previous logs..

atm it works for me but well I am on Manjaro so dunno what else might be different here

@steadfasterX:

It seems to me as this is the same error as before and seems to be rooted somewhere in eclipse. At least you can find that error on the internet on eclipse-based applications.

@steadfasterX: Did you encounter that problem on your machine too? Did the flag in Fakturama.ini solve it for you?

ah well.. sorry just digging in the dark here and I am too scared to rebuild it. it works here atm so I don't wanna touch it lol.

so here is my ini, I have the -vm thingy directly after the startup one though (wasnt on my PC yesterday when I wrote that). this is how mine looks like:

-startup
plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar
-vm
/usr/lib/jvm/java-11-openjdk/bin
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.400.v20211117-0650
-vmargs
-DREFRESH_BUNDLES=false
-Dorg.eclipse.e4.ui.css.dynamic=true
--add-modules=ALL-SYSTEM
-DLiquibaseHubMode=off

Try it with that maybe first.

.. but it seems since you added that the behavior changed no? I mean you get now:

java.net.BindException: Die Adresse wird bereits verwendet (Bind failed)

which likely points to the fact that either a Fakturama process is still open or due to the previous tests didn't closed successfully. I can re-produce that error when trying to open Fakturama twice so one of these might be true on yours.

The following is without any warranties and please please please: do a backup of all your Fakturama folders before. It might not be needed and it might not do anything but well try this:

$> Fakturama -clean -consoleLog

If that still does not work I would suggest to ask with this console log in the Fakturama forum for help...

Puh Sorry will not work my Fakturama.ini

-startup
plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.400.v20211117-0650
-vm
/usr/lib/jvm/java-11-openjdk/bin
-vmargs
-DREFRESH_BUNDLES=false
-Dorg.eclipse.e4.ui.css.dynamic=true
--add-modules=ALL-SYSTEM
-DLiquibaseHubMode=off

Consolen output

[gregor@compi fakturama2]$ Fakturama 
WARNING: Extender - Refreshing disabled - entities in bundle com.sebulli.fakturama.model may not be woven
März 22, 2023 8:27:32 NACHM. javax.money.spi.Bootstrap init
INFORMATION: Money Bootstrap: new ServiceProvider set: org.javamoney.osgi.OsgiServiceProvider
[Server@2dac2e1b]: Initiating startup sequence...
[Server@2dac2e1b]: [Thread[HSQLDB Server @2dac2e1b,5,main]]: run()/openServerSocket(): 
java.net.BindException: Die Adresse wird bereits verwendet (Bind failed)
    at java.base/java.net.PlainSocketImpl.socketBind(Native Method)
    at java.base/java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:452)
    at java.base/java.net.ServerSocket.bind(ServerSocket.java:395)
    at java.base/java.net.ServerSocket.<init>(ServerSocket.java:257)
    at java.base/java.net.ServerSocket.<init>(ServerSocket.java:149)
    at org.hsqldb.server.HsqlSocketFactory.createServerSocket(Unknown Source)
    at org.hsqldb.server.Server.openServerSocket(Unknown Source)
    at org.hsqldb.server.Server.run(Unknown Source)
    at org.hsqldb.server.Server$ServerThread.run(Unknown Source)
[Server@2dac2e1b]: Initiating shutdown sequence...
[Server@2dac2e1b]: Shutdown sequence completed in 1 ms.
[Server@2dac2e1b]: 2023-03-22 19:27:32.994 SHUTDOWN : System.exit() was not called
[Server@2dac2e1b]: Initiating startup sequence...
[Server@2dac2e1b]: Server socket opened successfully in 0 ms.
[Server@2dac2e1b]: Database [index=0, id=0, db=file:/home/gregor/Arbeit/fakturama/Database/Database, alias=fakdbneu] opened successfully in 192 ms.
[Server@2dac2e1b]: Startup sequence completed in 201 ms.
[Server@2dac2e1b]: 2023-03-22 19:27:33.283 HSQLDB server 2.6.0 is online on port 9002
[Server@2dac2e1b]: To close normally, connect and execute SHUTDOWN SQL
[Server@2dac2e1b]: From command line, use [Ctrl]+[C] to abort abruptly
März 22, 2023 8:27:33 NACHM. liquibase.servicelocator
INFORMATION: Cannot load service: liquibase.license.LicenseService: Provider liquibase.license.pro.DaticalTrueLicenseService could not be instantiated
März 22, 2023 8:27:33 NACHM. liquibase.database
INFORMATION: Set default schema name to PUBLIC
März 22, 2023 8:27:33 NACHM. liquibase.lockservice
INFORMATION: Changelog-Protokoll erfolgreich gesperrt.
März 22, 2023 8:27:34 NACHM. liquibase.changelog
INFORMATION: Reading from PUBLIC.DATABASECHANGELOG
März 22, 2023 8:27:34 NACHM. liquibase.lockservice
INFORMATION: Successfully released change log lock
März 22, 2023 8:27:34 NACHM. liquibase.database
WARNUNG: Failed to restore the auto commit to true
[EL Info]: 2023-03-22 20:27:34.396--ServerSession(1438924435)--EclipseLink, version: Eclipse Persistence Services - 2.7.10.v20211216-fe64cd39c3
SWT WebKitGDBus: error creating DBus server Fehler beim Binden an Adresse (GUnixSocketAddress): Datei oder Verzeichnis nicht gefunden
SWT WebKit: error initializing DBus server, dBusServer == 0

(Fakturama:39849): GLib-GIO-<span style="color:#A347BA">CRITICAL</span> **: <span style="color:#12488B">20:27:35.259</span>: g_dbus_server_get_client_address: assertion 'G_IS_DBUS_SERVER (server)' failed
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fc12163ed16, pid=39849, tid=39850
#
# JRE version: OpenJDK Runtime Environment (11.0.18+10) (build 11.0.18+10)
# Java VM: OpenJDK 64-Bit Server VM (11.0.18+10, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [libswt-gtk-4950r5.so+0x3ed16]  Java_org_eclipse_swt_internal_C_strlen+0xf
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /usr/share/fakturama2/core.39849)
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid39849.log
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
[gregor@compi fakturama2]$ 

Ah well sorry,I wasn't really clear. Pls try that:

-startup
plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.400.v20211117-0650
-vm
/usr/lib/jvm/java-11-openjdk/bin
-vmargs
-DREFRESH_BUNDLES=false
-Dorg.eclipse.e4.ui.css.dynamic=true
--add-modules=ALL-SYSTEM
-DLiquibaseHubMode=off

Ok add in Fakturama.ini -vm /usr/lib/jvm/java-11-openjdk/bin and install jdk11-openjdk switsch to java 11 after start this happens

[gregor@compi fakturama2]$ Fakturama Unrecognized option: -vm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.

pls try to add this (obviously needs java 11 in that path):

-vm
/usr/lib/jvm/java-11-openjdk/bin

and yes a new line after -vm ;)