dkopp crashed with SIGABRT in beroot()

[belphegor54]

ne s'ouvre pas

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: dkopp 6.5-1build1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 16 13:00:05 2018
ExecutablePath: /usr/bin/dkopp
InstallationDate: Installed on 2018-04-15 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: /usr/bin/dkopp
ProcEnviron:
 LANGUAGE=fr_CA:fr
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: dkopp
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x55fcd85f3d30, argc=1, argv=0x7ffcced65408, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcced653f8) at ../csu/libc-start.c:310
 ?? ()
Title: dkopp crashed with SIGABRT in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 beroot (argc=0, argv=0x7ffcced65410) at zfuncs.cc:486
 main (argc=<optimized out>, argv=<optimized out>) at dkopp-6.5.cc:344

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Caleb McKay (caleb-9)]

Seeing the same errors. This app was updated by the developer and source posted on his/her website. See https://kornelix.net/downloads/downloads.html. Everything about this package is out of date, including the link to the developer's website. I download the source and built my own .deb and installed. Can confirm the updated version works fine on Ubuntu 19.04.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Caleb McKay (caleb-9)]

So this bug has been open since 2018. There is a readily available fix, but the Debian maintainer has shown no interest in updating this package to anything that resembles a recent release. I love this software, but frankly this package should be just dropped altogether since Debian seems uninterested in maintaining it.