Bug 278575 - drkonqi crashed after locking up during login to bugs.kde.org
Summary: drkonqi crashed after locking up during login to bugs.kde.org
Status: RESOLVED DUPLICATE of bug 265992
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on: 265992
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-26 19:50 UTC by Dennis Schridde
Modified: 2013-01-19 03:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kcrash report (19.87 KB, text/plain)
2011-07-26 19:50 UTC, Dennis Schridde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Schridde 2011-07-26 19:50:42 UTC
Created attachment 62217 [details]
kcrash report

Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

kmail crashed, which started drkonqi. I tried to report the problem, hence had to login to bugs.kde.org. After clicking the login button drkonqi did not proceed any further. The application did not block entirely, just the username/password field and the login and continue buttons were greyed out and never came back to life. I then closed drkonqi after a few minutes of waiting and pressing the back button and then continuing to the login page. Then drkonqi crashed.

Reproducible: Didn't try

Steps to Reproduce:
drkonqi crashed several times already, but due to the nature of the process I never found a common scheme.


Expected Results:  
drkonqi should not segfault when closing. Further it should not lock up during login.
Comment 1 Christoph Feck 2011-07-27 11:20:11 UTC
Bugzilla does no longer accept bug reports for KMail1, as all bug fixes go into KMail2. That should be somehow reflected in DrKonqi.
Comment 2 George Kiagiadakis 2011-07-27 11:56:00 UTC
The problem is that kwallet did not respond in time. Drkonqi should not use kwallet synchronously. This is bug 265992
Comment 3 Jekyll Wu 2013-01-19 03:51:00 UTC

*** This bug has been marked as a duplicate of bug 265992 ***