Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB Dongle crash oeserver (core dump) on Linux OpenSUSE 42.3 #47

Open
dominig opened this issue Jul 3, 2019 · 1 comment
Open

USB Dongle crash oeserver (core dump) on Linux OpenSUSE 42.3 #47

dominig opened this issue Jul 3, 2019 · 1 comment

Comments

@dominig
Copy link
Contributor

dominig commented Jul 3, 2019

While I can get (with some hitches) the Dongle to work on OpenSUSE 15.0, I fail systematically under OpenSUSE 42.3 (see Screenshot)
Screenshot_20190703_132613

I did not find any missing lib with ldd with oeserverd.
Dongle is well detected by Linux.
The Journal indicates that oeserverd core dumped. As this is a closed code, I cannot do much.
oeservered works fine when the Dongle is not present and give me access to my chart set which is linked to my finger print.

Any clue how to debug that issue which is specific to that release of OpenSUSE and so linked to the environment ?

---------------- Journalctrl extract core dump --------------
juil. 03 13:25:49 linux-fkwb.suse systemd-coredump[5125]: Failed to generate stack trace: Unwinding not supported for this architecture
juil. 03 13:25:49 linux-fkwb.suse systemd-coredump[5125]: Process 5123 (oeserverd) of user 3204 dumped core.

------------- Journalctrl Dongle detection ------------------
juil. 03 13:34:23 linux-fkwb.suse kernel: usb 1-2: new full-speed USB device number 7 using xhci_hcd
juil. 03 13:34:23 linux-fkwb.suse kernel: usb 1-2: New USB device found, idVendor=1547, idProduct=1000
juil. 03 13:34:23 linux-fkwb.suse kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
juil. 03 13:34:23 linux-fkwb.suse kernel: usb 1-2: Product: SG-Lock USB Key
juil. 03 13:34:23 linux-fkwb.suse kernel: usb 1-2: Manufacturer: SG-Lock
juil. 03 13:34:23 linux-fkwb.suse kernel: hid-generic 0003:1547:1000.0008: hiddev0,hidraw0: USB HID v1.00 Device [SG-Lock SG-Lock USB Key] on usb-0000:00:14.0-2/input0
juil. 03 13:34:23 linux-fkwb.suse mtp-probe[5288]: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2"
juil. 03 13:34:23 linux-fkwb.suse mtp-probe[5288]: bus: 1, device: 7 was not an MTP device

--------------- log without Dongle ------------
3:21:17 CEST: validate_SENC_server
13:21:17 CEST: oesenc_pi: Checking oeserverd utility at {/usr/bin/oeserverd}
13:21:17 CEST: oesenc_pi: starting oeserverd utility: /usr/bin/oeserverd
13:21:18 CEST: oesenc_pi: oeserverd Check OK...LoopCount: 3

------------------- log with Dongle -------------------
13:25:53 CEST: Initializing Chart /home/dominig/CartesOpenCPN/cartes/OeSENC/southerly100-FRatl-2018-22/OC-33-070176.oesenc
13:25:53 CEST: processChartInfo /home/dominig/CartesOpenCPN/cartes/OeSENC/southerly100-FRatl-2018-22/OC-33-070176.oesenc
13:25:53 CEST: validate_SENC_server
13:25:53 CEST: oesenc_pi: Checking oeserverd utility at {}

@leamas
Copy link

leamas commented Feb 24, 2020

We had some problems in the flatpak build related to the libusb version. You might want to check by using the binary from the flatpak/ dir installed in ~/.local/lib or ~/.local/lib/opencpn.

Edit: Although bleeding edge, if oesenc is the only plugin you need you might also want to try the flatpak build. See for example OpenCPN/OpenCPN#1729

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants