How to Install and Uninstall drkonqi Package on Kali Linux

Last updated: May 05,2024

1. Install "drkonqi" package

Please follow the steps below to install drkonqi on Kali Linux

$ sudo apt update $ sudo apt install drkonqi

2. Uninstall "drkonqi" package

Please follow the step by step instructions below to uninstall drkonqi on Kali Linux:

$ sudo apt remove drkonqi $ sudo apt autoclean && sudo apt autoremove

3. Information about the drkonqi package on Kali Linux

Package: drkonqi
Version: 5.27.10-1
Installed-Size: 3402
Maintainer: Debian Qt/KDE Maintainers
Architecture: amd64
Depends: qml-module-org-kde-syntaxhighlighting, init-system-helpers (>= 1.52), kio, libc6 (>= 2.34), libgcc-s1 (>= 3.0), libkf5configcore5 (>= 5.102.0~), libkf5configgui5 (>= 5.102.0~), libkf5coreaddons5 (>= 5.102.0~), libkf5crash5 (>= 5.102.0~), libkf5i18n5 (>= 5.102.0~), libkf5idletime5 (>= 5.102.0~), libkf5jobwidgets5 (>= 5.102.0~), libkf5kiocore5 (>= 5.102.0~), libkf5kiogui5 (>= 5.102.0~), libkf5notifications5 (>= 5.102.0~), libkf5service-bin, libkf5service5 (>= 5.102.0~), libkf5syntaxhighlighting5 (>= 5.102.0~), libkf5wallet-bin, libkf5wallet5 (>= 5.102.0~), libkf5widgetsaddons5 (>= 5.102.0~), libkf5windowsystem5 (>= 5.102.0~), libkuserfeedbackcore1 (>= 1.0.0), libqt5core5a (>= 5.15.2~), libqt5dbus5 (>= 5.15.2~), libqt5gui5 (>= 5.15.2~) | libqt5gui5-gles (>= 5.15.2~), libqt5network5 (>= 5.15.2~), libqt5qml5 (>= 5.15.2~), libqt5widgets5 (>= 5.15.2~), libstdc++6 (>= 13.1), libsystemd0 (>= 246)
Recommends: systemd-coredump
Size: 547848
SHA256: 743e7bc88fc759392d57b1e2ca1e7a0067cf5b270888a9a32d33b19c73d59cff
SHA1: 8c9b74e9c224739e588b122f36f14dba10e0dae0
MD5sum: 870c3ca4b06d7c8c29835d22aec79c71
Description: Crash handler for Qt applications
Drkonqi shows a dialog for dealing with application crashes.
.
Drkonqi also doesn't technically require a process to actually crash, you
can simply run it manually on any old pid. Do note that in most cases you
only need to define the pid, however not giving certain cmdline options can
change behavior somewhat drastically (e.g. kdeinit vs. notkdeinit behaves
radically different as far as process name detection goes) . Drkonqi has a
number of backends that may be used. Backends are stacked by order of
preference, backends in the directory of the binary are most preferred.
This means that you can dump debuggers/internal/ into your build's bin/
directory and override for example gdb. This essentially allows you to
replace the gdb debugger with a cat of a fixture file to not have to trace
live processes at all.
Description-md5:
Homepage: https://invent.kde.org/plasma/drkonqi
Tag: devel::testing-qa, implemented-in::c++, interface::graphical,
interface::x11, role::program, scope::utility, suite::kde,
uitoolkit::qt, works-with::bugs, works-with::software:running,
x11::application
Section: kde
Priority: optional
Filename: pool/main/d/drkonqi/drkonqi_5.27.10-1_amd64.deb