Version: (using KDE 4.3.4) Compiler: GCC 4.4.2 OS: Linux Installed from: Exherbo Packages I have tried to send crash reports through DrKonqi several times in the last few months and none of them succeeded. DrKonqi always fails to send the report with the same useless message: Error sending the crash report: /Unknown error./ Wherever this message is being generated, it should be substituted to a more adequate message that describes the exact reason why it failed. The current message gives me no clue as to why I can't send crash reports.
DrKonqi catches some common error and put a meaningful description, it also catches some bugzilla errors and use that messages... so "unknown" is really an unknown error. I would prepare a patch so you can provide us more debug information about this. Thanks
Created attachment 38954 [details] Patch to enable more debug output - Apply this patch (kdebase/runtime/drkonqi) - Recompile DrKonqi - Enable the debug output: 1) Run "kdebugdialog" and enable the output of "1410 drkonqi". - Run in Konsole some application and crash it. - Try reporting the bug, the output of drkonqi process should be printed to the shell output. When the "unknown error" message appear, a full info will be printed to the shell. Please copy and paste it here. Thanks
(In reply to comment #2) > - Run in Konsole some application and crash it. > - Try reporting the bug, the output of drkonqi process should be printed to the > shell output. When the "unknown error" message appear, a full info will be > printed to the shell. Please copy and paste it here. Output won't be in konsole, it will be in ~/.xsession-errors, because drkonqi is launched from kdeinit. It is possible to redirect drkonqi's output to a separate file using kdebugdialog, and that is what I would recommend people to do. So, run "kdebugdialog --fullmode", select area "1410 drkonqi" and set the information output to be redirected to a file. After reproducing the crash and the drkonqi bug, attach this file here.
Marking as WAITINGFORINFO
As i can see in the .xsession-errors, it seems a proble with ssl certificate : host in the certificate does not correspond to real domain name. this is what I obtain when trying to send the bug report. drkonqi(12682)/kio (Slave) KIO::Slave::createSlave: createSlave "https" for KUrl("https://bugs.kde.org/post_bug.cgi") drkonqi(12682)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-pascal/drkonqiQ12682.slave-socket" klauncher(3238)/kio (KLauncher) KLauncher::requestSlave: KLauncher: launching new slave "kio_http" with protocol= "https" args= ("https", "local:/tmp/ksocket-pascal/klauncherMT3238.slave-socket", "local:/tmp/ksocket-pascal/drkonqiQ12682.slave-socket") kdeinit4: preparing to launch /usr/lib/kde4/kio_http.so klauncher(3238)/kio (KLauncher) KLauncher::processRequestReturn: "kio_http" (pid 12785) up and running. kio_http(12785)/kio (TCPSlaveBase) KIO::TCPSlaveBase::disconnectFromHost: kio_http(12785)/kssl KSslCertificateManagerPrivate::loadDefaultCaCertificates: Loading 118 CA certificates from ("/usr/share/kde4/apps/kssl/ca-bundle.crt") kio_http(12785)/kssl KTcpSocket::showSslErrors: "Le nom de l'hôte ne correspond à aucun des hôtes valables pour ce certificat" **** ENGLISH : host name does not fit any host names for this certificate*** kio_http(12785)/kssl KIO::TCPSlaveBase::startTLSInternal: Cipher info - advertised SSL protocol version 8 negotiated SSL protocol version 8 authenticationMethod: "RSA" encryptionMethod: "AES" keyExchangeMethod: "DH" name: "DHE-RSA-AES256-SHA" supportedBits: 256 usedBits: 256 kio_http(12785)/kio (kioslave) KIO::SlaveBase::mimeType: "text/html"
@Arthur: do you see related messages on your desktop ? Regards
Does konqueror fail as well when trying to connect to https://bugs.kde.org ? What does it say?
As a matter of fact, it does report those same messages. Here is one of the many occurrences of those messages on my logs: -------------------------------------------------- drkonqi(16300)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-tureba/drkonqis16300.slave-socket" klauncher(3219)/kio (KLauncher) KLauncher::requestSlave: KLauncher: launching new slave "kio_http" with protocol= "https" args= ("https", "local:/tmp/ksocket-tureba/klauncherMT3219.slave-socket", "local:/tmp/ksocket-tureba/drkonqis16300.slave-socket") kdeinit4: preparing to launch /usr/lib/kde4/kio_http.so klauncher(3219)/kio (KLauncher) KLauncher::processRequestReturn: "kio_http" (pid 16633) up and running. kio_http(16633)/kio (TCPSlaveBase) KIO::TCPSlaveBase::disconnectFromHost: kio_http(16633)/kssl KSslCertificateManagerPrivate::loadDefaultCaCertificates: Loading 118 CA certificates from ("/usr/share/apps/kssl/ca-bundle.crt") kio_http(16633)/kssl KTcpSocket::showSslErrors: "The host name did not match any of the valid hosts for this certificate" kio_http(16633)/kssl KIO::TCPSlaveBase::startTLSInternal: Cipher info - advertised SSL protocol version 8 negotiated SSL protocol version 8 authenticationMethod: "RSA" encryptionMethod: "AES" keyExchangeMethod: "DH" name: "DHE-RSA-AES256-SHA" supportedBits: 256 usedBits: 256 -------------------------------------------------- What I think is odd, though, is that it asks for my username and password of bugs.kde.org. It verifies those with the site and only moves forward on the bug reporting wizard after that. That means it connected successfully before failing so misteriously to send the bug report. What is the difference between these two connections it makes? Maybe there lies a clue.
Both "login" and "send bug" requests are using KIO::storedHttpPost with a "https://" address... @Andreas: any hint about this ? Also, should such SSL error pop a KIO::Job error ?
For me the problem lies in : kio_http(16633)/kssl KTcpSocket::showSslErrors: "The host name did not match any of the valid hosts for this certificate" are generic hostnames like *.kde.org legal in certificates CN field ? if yes then why kio_http/kssl issues a warning on "bugs.kde.org" ? konqueror might not issue an error because the user has accepted the certificate permanently upon konqueror first warning. anyway we should never accept invalid certificates by default.
have a look at comment #35 and the current mess in SSL support in bug #162485
*** Bug 228018 has been marked as a duplicate of this bug. ***
Have there been any changes during the last two days? Today, I have been able for the first time to report a bug with DrKonqi (bug #238569).
On Sunday 23 May 2010 04:13:30 walch.martin@web.de wrote: > https://bugs.kde.org/show_bug.cgi?id=217742 > > > > > > --- Comment #13 from <walch martin web de> 2010-05-23 13:13:01 --- > Have there been any changes during the last two days? Today, I have been > able for the first time to report a bug with DrKonqi (bug #238569). I dunno. I know only that for at least the last two weeks (probably more like four), I have been able to report bugs using Dr. Konqui. What a relief!! :) Thanks very much for this.
Failed to report a bug again today. From .xsession-errors: drkonqi(4019)/kio (Scheduler) KIO::SchedulerPrivate::doJob: KIO::SimpleJob(0x1cb3a30) drkonqi(4019)/kio (Slave) KIO::Slave::createSlave: createSlave "https" for KUrl("https://bugs.kde.org/post_bug.cgi") drkonqi(4019)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-eamonn/drkonqiJX4019.slave-socket" klauncher(2433)/kio (KLauncher) KLauncher::requestSlave: KLauncher: launching new slave "kio_http" with protocol= "https" args= ("https", "local:/tmp/ksocket-eamonn/klauncherMT2433.slave-socket", "local:/tmp/ksocket-eamonn/drkonqiJX4019.slave-socket") klauncher(2433)/kio (KLauncher) KLauncher::processRequestReturn: "kio_http" (pid 4791) up and running. kio_http(4791) HTTPProtocol::sendQuery: ============ Sending Header: kio_http(4791) HTTPProtocol::sendQuery: "POST /post_bug.cgi HTTP/1.1" kio_http(4791) HTTPProtocol::sendQuery: "Host: bugs.kde.org" kio_http(4791) HTTPProtocol::sendQuery: "Connection: Keep-Alive" kio_http(4791) HTTPProtocol::sendQuery: "Pragma: no-cache" kio_http(4791) HTTPProtocol::sendQuery: "Cache-control: no-cache" kio_http(4791) HTTPProtocol::sendQuery: "Accept: text/html, image/jpeg;q=0.9, image/png;q=0.9, text/*;q=0.9, image/*;q=0.9, */*;q=0.8" kio_http(4791) HTTPProtocol::sendQuery: "Accept-Encoding: x-gzip, x-deflate, gzip, deflate" kio_http(4791) HTTPProtocol::sendQuery: "Accept-Charset: utf-8, utf-8;q=0.5, *;q=0.5" kio_http(4791) HTTPProtocol::sendQuery: "Accept-Language: en-GB,en-US;q=0.9,en;q=0.8" kio_http(4791) HTTPProtocol::sendQuery: "Content-Type: application/x-www-form-urlencoded" kio_http(4791)/kio (TCPSlaveBase) KIO::TCPSlaveBase::disconnectFromHost: kio_http(4791)/kssl KSslCertificateManagerPrivate::loadDefaultCaCertificates: Loading 123 CA certificates from ("/usr/share/kde4/apps/kssl/ca-bundle.crt") kio_http(4791)/kssl KTcpSocket::showSslErrors: "The host name did not match any of the valid hosts for this certificate" kio_http(4791)/kssl KIO::TCPSlaveBase::startTLSInternal: Cipher info - advertised SSL protocol version 8 negotiated SSL protocol version 8 authenticationMethod: "RSA" encryptionMethod: "AES" keyExchangeMethod: "DH" name: "DHE-RSA-AES256-SHA" supportedBits: 256 usedBits: 256 kio_http(4791) HTTPProtocol::readResponseHeader: ============ Received Status Response: kio_http(4791) HTTPProtocol::readResponseHeader: "HTTP/1.1 200 OK" kio_http(4791)/kio (kioslave) KIO::SlaveBase::mimeType: "text/html" drkonqi(4019)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished: KIO::StoredTransferJob(0x1cb3a30) KIO::Slave(0x1aeed70) Running: KDE Platform Version: 4.4.92 (KDE 4.4.92 (KDE 4.5 RC2)) Qt Version: 4.7.0 Operating System: Linux 2.6.33.6-147.fc13.x86_64 x86_64 Distribution: "Fedora release 13 (Goddard)"