Hi!

At my system (Debian Jessie x64 KDE v.4.14.2), when closing Akregator, appears Dr. Konqi and informs me, that Akregator has crashed.
Seems like there are a couple of related bugs.

How can I disable Dr. Konqi for Akregator (or globally)?
Anyway, reporting bugs for KDE 4, is useless anyway.

TIA!

try:

https://techbase.kde.org/Development/FAQs/Debugging_FAQ

How do I avoid Dr Konqi?

You must set the environment variable KDE_DEBUG (to 1 or whatever you want in fact).

To get Dr Konqi back, unset the KDE_DEBUG environment variable.

Example:
To avoid Dr Konqi: export KDE_DEBUG=1
To see Dr Konqi: unset KDE_DEBUG

Nope!
I tried it from Konsole and I even tried putting it at .bashrc, but didn't work!
G.

after trying it from Konsole did you run the app from within that Konsole tab?

after adding in .bashrc did you restart KDE?

does the variable show when running printenv?

Indeed printenv doesn't show the entry "export KDE_DEBUG=1", no matter if I give it through Konsole or .bashrc!

EDIT:

As a temporary solution, I went to the /usr/lib/kde4/libexec/ directory and changed drkonqi's executable attribute to non-executable.
Maybe renaming it to something else (eg. drkonqi.BAK), is a similar approach.
G.

you using the born bash shell?

Code: Select all

my_account> export KDE_DEBUG=1
 my_account> printenv|grep debug
 KDE_DEBUG=1

Yes, I'm using Bash (the default that comes with Debian).

Giorgos67 wrote:Indeed printenv doesn't show the entry "export KDE_DEBUG=1", no matter if I give it through Konsole or .bashrc!

EDIT:

As a temporary solution, I went to the /usr/lib/kde4/libexec/ directory and changed drkonqi's executable attribute to non-executable.
Maybe renaming it to something else (eg. drkonqi.BAK), is a similar approach.
G.

that will work until its reinstalled during an upgrade

Great!

I changed drkonqi's permission to non-executable.
If a future update changes it, I'll repeat it.

Bye!
G.