https://bugs.kde.org/show_bug.cgi?id=419646
--- Comment #11 from Harald Sitter ---
It'd be lovely if you could test that fix.
I can't actually reproduce the problem on my end. I've verified that indeed
it's automatic cookie injection that makes your cookie end up in the requests
and the commit d
https://bugs.kde.org/show_bug.cgi?id=419646
Harald Sitter changed:
What|Removed |Added
Version Fixed In||5.18.5
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=419646
Harald Sitter changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=419646
--- Comment #8 from Martin Koller ---
Created attachment 127641
--> https://bugs.kde.org/attachment.cgi?id=127641&action=edit
logfile
new logfile attached. Shows a HTTP 400 "Bad request" error
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=419646
--- Comment #7 from Harald Sitter ---
:(
You can try putting KDE_FORK_SLAVES=1 into /etc/environment and logging out and
in again. That should make drkonqi fork() directly and ideally then make the
debug output appear.
Should that not work I presume y
https://bugs.kde.org/show_bug.cgi?id=419646
--- Comment #6 from Martin Koller ---
That does not help either. The only additional output is:
Apr 16 11:04:22 lapi drkonqi[10500]: kf5.kio.core:
"/usr/lib64/qt5/plugins/kf5/kio/audiocd.so" supports protocols ("audiocd")
Apr 16 11:04:22 lapi drkonqi[1
https://bugs.kde.org/show_bug.cgi?id=419646
--- Comment #5 from Harald Sitter ---
Well, that I thought would be more useful :|
Please also add kf5.kio.*=true to qtlogging.ini and try again. Note that the
output will likely contain plaintext passwords now, you'll want to replace them
before attac
https://bugs.kde.org/show_bug.cgi?id=419646
--- Comment #4 from Martin Koller ---
Created attachment 127583
--> https://bugs.kde.org/attachment.cgi?id=127583&action=edit
logs
logs from a crash I forced by kill -4 of a kwrite instance
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=419646
--- Comment #3 from Harald Sitter ---
on opensuse I'm fairly confident output goes to journald and I'm also fairly
confident that debug message are compiled-in.
if you find out where your drkonqi binary lives you can probably also try to
run it manuall
https://bugs.kde.org/show_bug.cgi?id=419646
--- Comment #2 from Martin Koller ---
Operating System: openSUSE Tumbleweed 20200411
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Kernel Version: 5.6.2-1-default
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6300U CPU @
https://bugs.kde.org/show_bug.cgi?id=419646
Harald Sitter changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=419646
Nate Graham changed:
What|Removed |Added
Product|frameworks-kcrash |drkonqi
CC|
12 matches
Mail list logo
