Kblogger crashed after hitting on 'auto configure'

Bug #367176 reported by sputnik on 2009-04-26
Affects Status Importance Assigned to Milestone
kblogger (Ubuntu)

Bug Description

  installierte Version: 1.0~alpha3-0ubuntu4 (Kubuntu Jaunty KDE 4.2.2)

While trying to configure kblogger for my blogspot account I failed on the configuration settings.
Hitting the button "auto configure" in the settings dialogue caused the aplication to crash.

This is the backtrace:

The application KBlogger (kblogger) crashed and caused the signal 11 (SIGSEGV)

Anwendung: KBlogger (kblogger), Signal SIGSEGV
[Current thread is 0 (LWP 29257)]

Thread 2 (Thread 0xaf9d5b90 (LWP 29285)):
#0 0xb7f16430 in __kernel_vsyscall ()
#1 0xb56e0412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb5caa344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3 0xb5e9698c in QWaitCondition::wait (this=0x93c9b60, mutex=0x93c9b5c, time=30000) at thread/qwaitcondition_unix.cpp:85
#4 0xb5e8be76 in QThreadPoolThread::run (this=0x93c8fb8) at concurrent/qthreadpool.cpp:140
#5 0xb5e9596e in QThreadPrivate::start (arg=0x93c8fb8) at thread/qthread_unix.cpp:189
#6 0xb56dc4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb5c9b49e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4ede700 (LWP 29257)):
[KCrash Handler]
#6 0x0809624d in _start ()

Jonathan Thomas (echidnaman) wrote :

Since kblogger is at this point very unstable and has not been updated in nearly a year, we have removed it from distribution for future versions of Kubuntu. Unfortunately this means that will no longer be able to provide bugfixes for this package. (Though since its development has been stalled for a year this was unlikely anyways.)

You may with to try "blogilo", KDE's blogging application for KDE 4.4. It will be available in Kubuntu 10.04 to be released this April.

Changed in kblogger (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers