I have added the toggle button "Activate Proxy" from extra toolbar <khtmlstettings> to konqueror's extra toolbar. But when I start konqueror as webbrowser or switch to the browser profile and click on that toggle button konqueror crashes (independent of the proxy's status). If I first click on the button "HTML settings" (also from extra toolbar <khtmlstettings>), "Activate Proxy" works correctly; it does not matter whether I do something in the "HTML Settings" menu or not, I only have to click on "HTML settings". I am using the hardened profile, konqueror 3.5.5 (kde 3.5.5) and qt-3.3.4-r8. I have compiled konqueror with CFLAGS="-fomit-frame-pointer", the debugger output after the crash is: (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". 0x00002fe3c35ee0b2 in ?? () #0 0x00002fe3c35ee0b2 in ?? () #1 0x00002fe3c35edf50 in ?? () #2 0x00002fe3c02f4b70 in ?? () #3 0x0000000000000000 in ?? () This is the output of emerge --info: Portage 2.1.2_rc2-r5 (hardened/amd64, gcc-3.4.6, glibc-2.3.6-r5, 2.6.18-hardened-r2-monolith x86_64) ================================================================= System uname: 2.6.18-hardened-r2-monolith x86_64 AMD Sempron(tm) Processor 3000+ Gentoo Base System version 1.12.6 Last Sync: Fri, 08 Dec 2006 10:50:01 +0000 ccache version 2.4 [enabled] dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r6 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -fomit-frame-pointer -O2 -pipe " CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=k8 -fomit-frame-pointer -O2 -pipe " DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ " LINGUAS="de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="3dnow X alsa alsa_cards_via82xx amd64 arts bash-completion berkdb bzip2 caps cdr crypt dbus dlloader doc dvd dvdr elibc_glibc examples fbcon gif gpm gtk2 hal hardened input_devices_keyboard input_devices_mouse ipv6 jpeg jpeg2k justify kde kernel_linux linguas_de motif ncurses nls nptl nptlonly offensive ogg opengl pam pdf pic png qt3 readline ruby sdl smartcard spell sse2 ssl symlink tcpd tetex tiff truetype unicode usb userland_GNU userlocales video_cards_vesa video_cards_via vorbis xine xorg zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
*** Bug 157592 has been marked as a duplicate of this bug. ***
*** Bug 157593 has been marked as a duplicate of this bug. ***
See http://www.gentoo.org/proj/en/qa/backtraces.xml and reopen with a useful backtrace.
I have replaced CFLAGS="-fomit-frame-pointer" with "-ggdb", switched my gcc profile from "x86_64-pc-linux-gnu-3.4.6" to "x86_64-pc-linux-gnu-3.4.6-hardenednopie" and reemerged the packages "konqueror-3.5.5" and "konq-plugins-3.5.5". Now the KDE Crashmanager produces the following backtrace: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 54828417001264 (LWP 24520)] 0x000031ddbc36d0b2 in nanosleep () from /lib/libc.so.6 #0 0x000031ddbc36d0b2 in nanosleep () from /lib/libc.so.6 #1 0x000031ddbc36cf50 in sleep () from /lib/libc.so.6 #2 0x000031ddb90ca5ee in KCrash::startDrKonqi () from /usr/kde/3.5/lib64/libkdecore.so.4 #3 0x000031ddb90ca938 in KCrash::defaultCrashHandler () from /usr/kde/3.5/lib64/libkdecore.so.4 #4 0x000031ddbc309440 in killpg () from /lib/libc.so.6 #5 0x0000000000000000 in ?? ()
Is this still a problem with konqueror-3.5.6 and qt-3.3.6?
Yes. Because of Bug #126896 I kept qt-3.3.4-r8 instead of qt-3.3.6. After the above proposal I emerged qt-3.3.6-r5 with x86_64-pc-linux-gnu-3.4.6-hardenednossp as compiler, but I did not reemerge any kde-3.5.6 packages as revdep-rebuild did not recommend it. The problem with konqueror remains. If someone thinks that a reemerge will do the trick, I will try it.
I can reproduce your problem on 3.5.7 without hardened stuff. Actually, it's even known upstream: http://bugs.kde.org/show_bug.cgi?id=110552 If its status changes, please feel free to re-open this to alert us about it. For now, there's not much we can do, sorry.
