Hello,
unfortunately rekonq crashes quite often here, but so far never Dr. Konqi / the crashreporter showed up.

What do I have to do to enable this?
Thanks.

Can you check to see if Rekonq is being run with the argument "--nocrashhandler"?

No, rekonq is not started "--nocrashhandler".
But I noticed now, that after rekonq crashes, for a very short time systemd-coredump process shows up. Can it be that systemd interferes with the crashhandler?

Your system could have environment variables set which cause the system to prefer generating a core dump rather than invoking a crash handler. Please check the output of "env" for such variables.

Hmm, I fail to see anything related:

Code: Select all

XDG_VTNR=7
SSH_AGENT_PID=346
XDG_SESSION_ID=1
KDE_MULTIHEAD=false
DM_CONTROL=/var/run/xdmctl
GPG_AGENT_INFO=/tmp/gpg-AmPLf1/S.gpg-agent:343:1
SHELL=/bin/bash
TERM=xterm
HISTSIZE=10000
XDM_MANAGED=method=classic
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/richard/.gtkrc-2.0:/home/richard/.kde4/share/config/gtkrc-2.0
KONSOLE_DBUS_SERVICE=:1.54
KONSOLE_PROFILE_NAME=Shell
GS_LIB=/home/richard/.fonts
GTK_RC_FILES=/etc/gtk/gtkrc:/home/richard/.gtkrc:/home/richard/.kde4/share/config/gtkrc
WINDOWID=69206043
SHELL_SESSION_ID=b1430fd41e364000b54b9421590e77b9
KDE_FULL_SESSION=true
HISTFILESIZE=10000
USER=richard
SSH_AUTH_SOCK=/tmp/ssh-KpvtDCjkdXP5/agent.345
SESSION_MANAGER=local/kray:@/tmp/.ICE-unix/405,unix/kray:/tmp/.ICE-unix/405
MOZ_PLUGIN_PATH=/usr/lib/mozilla/plugins:/extra/usr/lib/mozilla/plugins
DESKTOP_SESSION=default
MAIL=/var/spool/mail/richard
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/core_perl
LC_MESSAGES=en_US
PWD=/home/richard
EDITOR=vim
KDE_SESSION_UID=1000
LANG=en_US
KONSOLE_DBUS_SESSION=/Sessions/1
HISTCONTROL=ignoreboth
HOME=/home/richard
COLORFGBG=15;0
XDG_SEAT=seat0
SHLVL=2
KDE_SESSION_VERSION=4
LANGUAGE=
XCURSOR_THEME=Oxygen_White
LOGNAME=richard
VISUAL=vim
XDG_DATA_DIRS=/usr/share:/usr/share:/usr/local/share
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-5wPnVOYoYE,guid=c96e3c4752559280984833b85314e0ce
WINDOWPATH=7
PROFILEHOME=
XDG_RUNTIME_DIR=/run/user/1000
DISPLAY=:0
QT_PLUGIN_PATH=/home/richard/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/
XDG_CURRENT_DESKTOP=KDE
_=/usr/bin/env

BTW: I deavtivated the systemd-coredump, but still...

Which version of Rekonq do you use?

bcooksley wrote:Which version of Rekonq do you use?

Its's rekonq
Version 2.4.2

I can't see anything in the sources which would indicate the crash handler is being disabled.
Can you try launching it from a terminal, and post the output once it has crashed?

I suspect it may be a stack recursion crash - which can't be caught so the crash handler doesn't get launched.

bcooksley wrote:I can't see anything in the sources which would indicate the crash handler is being disabled.
Can you try launching it from a terminal, and post the output once it has crashed?

I suspect it may be a stack recursion crash - which can't be caught so the crash handler doesn't get launched.

Yeah, you may be right about this one, because when I crash rekonq there is no output at all in the console - its just gone.

Also apparently I had now a different crash in rekonq, because the crashreporter (finally) showed up.


So it lookes like there is no error in rekonq nor crahsreporter, but it was (is) due to the nature of the crash...

If it is a stack recursion crash, then you should see the message "Segmentation fault" when it crashes.
If you want to investigate that issue further, i'd suggest running Rekonq within a debugger, although this will limit it's performance significantly.