Bug 337758

Please provide the version of KDE you are using. Versions using the XMLRPC interface should not be affected by this issue. Compatibility for older versions of DrKonqi has been removed.

It occurred when reporting the crash in bug report 337756. The reported KDE version there is 4.13.80. When trying to choose the version of drkonqi in this web page, I only could choose between 2.1.5 of unspecified.

At which stage did Dr Konqi fail?

In the windows asking for the login credentials. After filling these in or later filling in doen by KWallet pressing the Login button showed the 410 error message.

Please provide a screenshot of the authentication failed message and prior login page.

Created attachment 87950 [details]
first screenshot

Created attachment 87951 [details]
second screenshot

Created attachment 87952 [details]
third screenshot

Created attachment 87953 [details]
fourth screenshot

Created attachment 87954 [details]
fifth screenshot with 410 error

In screenshot 3 I pressed Aanmelden (Login)

Do you maybe have disabled cookies in konqueror? This looks like login succeeds, but the web engine doesn't remember that you are logged in afterwards, so it could well be a cookie problem.

My standard browser is Firefox.
All cookies are accepted in konqueror, see attached screenshot.

Created attachment 87979 [details]
screenshot of cookies page in konqueror

Application: akonadi_imap_resource (4.13)
KDE Platform Version: 4.13.80
Qt Version: 4.8.6
Operating System: Linux 3.16.0-rc7-2-desktop x86_64
Distribution: "openSUSE 20140807 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I pressed the Restart Application in DrKonqi bug reporting

-- Backtrace:
Application: IMAP-eik van type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
To enable execution of this file add
	add-auto-load-safe-path /usr/lib64/libstdc++.so.6.0.19-gdb.py
line to your configuration file "/home/freek/.gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/home/freek/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"
[KCrash Handler]
#5  0x0000000000450a44 in SessionPool::cancelPasswordRequests (this=<optimized out>) at /usr/src/debug/kdepim-runtime-4.13.80/resources/imap/sessionpool.cpp:71
#6  0x00000000004321f7 in ImapResourceBase::doSetOnline (this=0x178c2c0, online=<optimized out>) at /usr/src/debug/kdepim-runtime-4.13.80/resources/imap/imapresourcebase.cpp:554
#7  0x00007ff77f8ec6b1 in Akonadi::AgentBase::setOnlineInternal (this=0x178c2c0, state=false) at /usr/src/debug/kdepimlibs-4.13.80/akonadi/agentbase.cpp:965
#8  0x000000000042a934 in ImapResourceBase::ImapResourceBase (this=0x178c2c0, id=...) at /usr/src/debug/kdepim-runtime-4.13.80/resources/imap/imapresourcebase.cpp:145
#9  0x000000000041a2a0 in ImapResource::ImapResource (this=0x178c2c0, id=...) at /usr/src/debug/kdepim-runtime-4.13.80/resources/imap/imapresource.cpp:37
#10 0x000000000041a03a in Akonadi::ResourceBase::init<ImapResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/resourcebase.h:184
#11 0x00007ff77b77cb05 in __libc_start_main () from /lib64/libc.so.6
#12 0x0000000000419f14 in _start () at ../sysdeps/x86_64/start.S:122

Sorry, please ignore comment 14, belongs to another bug report.

I have the same issue. It started somewhere with Kubuntu's 4.13.2 packages (in 14.04LTS), and persists with the current 4.13.97 packages from the 14.04 backport PPA.

Log in works fine when requested, but when the time comes to submit a report (and that usually is not immediately after logging in because one has to browse existing reports AND type in one's own report) I get a 401 error telling me I'm not logged in.

Cookie handling hasn't changed: it's always been set to
X only accept cookies from originating server
X automatically accept session cookies
X accept until end of session

and fwiw, a Bugzilla_login_request_cookie shows up in the current kcookiejar (I tried to submit a report earlier this morning).

I've been saving a number of the generated bug reports, but it looks like there's no way to submit them manually (as in without typing in everything once more), or is there?

George, could you please do a whole workflow test? I suspect recent changes in Bugzilla 4.4 may be causing this.

A test instance at https://bugstest.kde.org/ can be used to perform tests.

As seen as I have already typed this out before finding this report I'll add it in.

Okular had crashed and drkonqi had appeared and I proceeded to backtrace and complete the report. However although I managed to log in successfully and fill out all the required information on submitting the report drkonqi reported that it couldn't submit as I was not logged in. The only options from this point were to retry (which failed) or cancel.

(In reply to wintonian from comment #18)
> As seen as I have already typed this out before finding this report I'll add
> it in.
> 
> Okular had crashed and drkonqi had appeared and I proceeded to backtrace and
> complete the report. However although I managed to log in successfully and
> fill out all the required information on submitting the report drkonqi
> reported that it couldn't submit as I was not logged in. The only options
> from this point were to retry (which failed) or cancel.

drkonqi ver. 2.1.5

(In reply to RJVB from comment #16)
> I've been saving a number of the generated bug reports, but it looks like
> there's no way to submit them manually (as in without typing in everything
> once more), or is there?

Ctrl A - select all text.
Ctrl C - copy to clipboard.

When reporting use Ctrl V to paste.

Works for me at least, saves lots of typing.

I had a similar problem.
DrKonqi asked me to login, which I tried to do using the saved password.
I ended up using Chromium to log in see what my password was.
I could auto log in using the password stored in chromium, but not see or change my password.
I ended up resetting my password.

I entered this new password into DrKonqi, and proceeded to file my bug report, when it came time to submit I got this error;
Error sending bug report:/Received unexpected error code 410 from bugzilla. Error message was:
You must log in before using this part of KDE Bugtracking system../
A retry button and a Show contents of this report button.

The retry button simply showed the same message, but with the "Back" button at the bottom greyed out, the Show Contents of this report button worked.
I tried logging in with DrKonqi while both logged in and logged out of bugs.kde.org with Chromium. 
I was unable to copy and paste the error code shown above, I needed to type it out again for this report.

I was reporting on a seg fault on Application: knotify4 (4.13.3)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.13.0-37-generic x86_64
Distribution: Ubuntu 14.04.1 LTS

DrKonqi does not appear to have a version number.

I just had the same problem as comment 16 and comment 18 while trying to submit a report about a crash in Dolphin.

KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-36-generic x86_64
Distribution: Ubuntu 14.04.2 LTS

$ LANG= /usr/lib/kde4/libexec/drkonqi --version
Qt: 4.8.6
KDE Development Platform: 4.14.2
The KDE Crash Handler: 2.1.5

Had the same problem again, appeared to log in OK, but received a 410 error when submitting bug report.
Logged into bugs.kde.org, tried DrKonqi again, still 410 error.
Used the back button to go back and log in, but it says I am already logged in.


Application: knotify4 (4.13.3)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.13.0-52-generic x86_64
Distribution: Ubuntu 14.04.2 LTS

Should be fixed in kde-runtime since late February:
https://bugs.kde.org/show_bug.cgi?id=337742#c62

Created attachment 92752 [details]
attachment-27529-0.html

Thank you.

It might take a little while to filter down through KUbuntu.

Andrew.



On 21 May 2015 at 08:09, RJVB <rjvbertin@gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=337758
>
> --- Comment #24 from RJVB <rjvbertin@gmail.com> ---
> Should be fixed in kde-runtime since late February:
> https://bugs.kde.org/show_bug.cgi?id=337742#c62
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

Apparently solved.