[akregator] [Bug 375701] Akregator crashes on exit command

2017-01-30 Thread Andrea Maria Marconi
https://bugs.kde.org/show_bug.cgi?id=375701

--- Comment #2 from Andrea Maria Marconi  ---
Sorry I couldn't find there was already a bug open.

If you're interested it still in the buggy state so in case you need me
doing anything that can help solving the matter just drop an email.

Regs,

Andrea


On 30/01/2017 21:21, Christoph Feck wrote:
> https://bugs.kde.org/show_bug.cgi?id=375701
>
> Christoph Feck  changed:
>
>What|Removed |Added
> 
>  Resolution|--- |INVALID
>  Status|UNCONFIRMED |RESOLVED
>
> --- Comment #1 from Christoph Feck  ---
> Already reported as bug 375603.
>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 375701] New: Akregator crashes on exit command

2017-01-29 Thread Andrea Maria Marconi
https://bugs.kde.org/show_bug.cgi?id=375701

Bug ID: 375701
   Summary: Akregator crashes on exit command
   Product: akregator
   Version: unspecified
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: am.marc...@gmx.com
  Target Milestone: ---

Application: akregator (4.14.10)
KDE Platform Version: 4.14.21
Qt Version: 4.8.7
Operating System: Linux 4.4.38 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
closing the program by clicking on it's close item on file menu.

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7504d5a7c0 (LWP 1687))]

Thread 4 (Thread 0x7f74d5781700 (LWP 2181)):
#0  0x7f74fe46a36f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f74e6ed4441 in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#2  0x7f74e71d6216 in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#3  0x7f74fe464684 in start_thread () at /lib64/libpthread.so.0
#4  0x7f74fd390efd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f74d6605700 (LWP 2180)):
#0  0x7f74fd38530d in poll () at /lib64/libc.so.6
#1  0x7f74f644a964 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f74f644aa6c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f74fe8390ce in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/qt/lib/libQtCore.so.4
#4  0x7f74fe8095d1 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#5  0x7f74fe8098e5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#6  0x7f74fe702c39 in QThread::exec() () at
/usr/lib64/qt/lib/libQtCore.so.4
#7  0x7f74fe7053bc in  () at /usr/lib64/qt/lib/libQtCore.so.4
#8  0x7f74fe464684 in start_thread () at /lib64/libpthread.so.0
#9  0x7f74fd390efd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f74d7fff700 (LWP 2179)):
#0  0x7f74fe46a36f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f74e71a4d9d in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#2  0x7f74e71a4df9 in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#3  0x7f74fe464684 in start_thread () at /lib64/libpthread.so.0
#4  0x7f74fd390efd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f7504d5a7c0 (LWP 1687)):
[KCrash Handler]
#6  0x7f75002fe3e0 in KXMLGUIFactory::removeClient(KXMLGUIClient*) () at
/usr/lib64/libkdeui.so.5
#7  0x7f74df4219a4 in  () at /usr/lib64/kde4/arkpart.so
#8  0x7f74df421a29 in  () at /usr/lib64/kde4/arkpart.so
#9  0x7f75047847b2 in Akregator::BrowserFrame::Private::~Private() () at
/usr/lib64/libakregatorprivate.so.4
#10 0x7f75047848b9 in Akregator::BrowserFrame::Private::~Private() () at
/usr/lib64/libakregatorprivate.so.4
#11 0x7f750478184b in Akregator::BrowserFrame::~BrowserFrame() () at
/usr/lib64/libakregatorprivate.so.4
#12 0x7f75047818b9 in Akregator::BrowserFrame::~BrowserFrame() () at
/usr/lib64/libakregatorprivate.so.4
#13 0x7f7504780035 in Akregator::FrameManager::slotRemoveFrame(int) () at
/usr/lib64/libakregatorprivate.so.4
#14 0x7f74fe81de30 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4
#15 0x7f74e96c1651 in  () at /usr/lib64/kde4/akregatorpart.so
#16 0x7f74e96a3526 in Akregator::MainWidget::slotOnShutdown() () at
/usr/lib64/kde4/akregatorpart.so
#17 0x7f74e969e7b0 in  () at /usr/lib64/kde4/akregatorpart.so
#18 0x7f74e969edd8 in  () at /usr/lib64/kde4/akregatorpart.so
#19 0x7f74e969f219 in  () at /usr/lib64/kde4/akregatorpart.so
#20 0x7f74fe81de30 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4
#21 0x7f74fe80ef25 in QCoreApplication::exec() () at
/usr/lib64/qt/lib/libQtCore.so.4
#22 0x00407bec in  ()
#23 0x7f74fd2aa7d0 in __libc_start_main () at /lib64/libc.so.6
#24 0x00407e99 in _start ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 375603] New: akgregator crash on close tab

2017-01-27 Thread Andrea Maria Marconi
https://bugs.kde.org/show_bug.cgi?id=375603

Bug ID: 375603
   Summary: akgregator crash on close tab
   Product: akregator
   Version: unspecified
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: am.marc...@gmx.com
  Target Milestone: ---

Application: akregator (4.14.10)
KDE Platform Version: 4.14.21
Qt Version: 4.8.7
Operating System: Linux 4.4.38 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
I opened up a "see more" tab in akregator from a feed. That "see more" is a
compressed pdf file opened using ark (by itself from akregator). Every time I
try to close this tab (right X icon) akgregator crashes.
I'll keep as it is without trying again to close it for a couple of days in
case of need. Email me at am.marc...@gmx.com if you need more details.

Thanks for the work you're doing anyway!!!

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f100b6cd7c0 (LWP 2295))]

Thread 5 (Thread 0x7f0f8d4c7700 (LWP 2323)):
#0  0x7f1004ddd36f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0fed52383b in WTF::ThreadCondition::timedWait(WTF::Mutex&, double)
() at /usr/lib64/qt/lib/libQtWebKit.so.4
#2  0x7f0fec31455d in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#3  0x7f0fed523216 in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#4  0x7f1004dd7684 in start_thread () at /lib64/libpthread.so.0
#5  0x7f1003d03efd in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f0f97fff700 (LWP 2322)):
#0  0x7f1004ddd36f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0fed221441 in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#2  0x7f0fed523216 in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#3  0x7f1004dd7684 in start_thread () at /lib64/libpthread.so.0
#4  0x7f1003d03efd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f0f9d5ac700 (LWP 2311)):
#0  0x7f1003cf830d in poll () at /lib64/libc.so.6
#1  0x7f0ffcdbd964 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0ffcdbda6c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f10051ac0ce in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/qt/lib/libQtCore.so.4
#4  0x7f100517c5d1 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#5  0x7f100517c8e5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#6  0x7f1005075c39 in QThread::exec() () at
/usr/lib64/qt/lib/libQtCore.so.4
#7  0x7f10050783bc in  () at /usr/lib64/qt/lib/libQtCore.so.4
#8  0x7f1004dd7684 in start_thread () at /lib64/libpthread.so.0
#9  0x7f1003d03efd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f0fde9f5700 (LWP 2310)):
#0  0x7f1004ddd36f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0fed4f1d9d in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#2  0x7f0fed4f1df9 in  () at /usr/lib64/qt/lib/libQtWebKit.so.4
#3  0x7f1004dd7684 in start_thread () at /lib64/libpthread.so.0
#4  0x7f1003d03efd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f100b6cd7c0 (LWP 2295)):
[KCrash Handler]
#6  0x7f1006c713e0 in KXMLGUIFactory::removeClient(KXMLGUIClient*) () at
/usr/lib64/libkdeui.so.5
#7  0x7f0fe48599a4 in  () at /usr/lib64/kde4/arkpart.so
#8  0x7f0fe4859a29 in  () at /usr/lib64/kde4/arkpart.so
#9  0x7f100b0f77b2 in Akregator::BrowserFrame::Private::~Private() () at
/usr/lib64/libakregatorprivate.so.4
#10 0x7f100b0f78b9 in Akregator::BrowserFrame::Private::~Private() () at
/usr/lib64/libakregatorprivate.so.4
#11 0x7f100b0f484b in Akregator::BrowserFrame::~BrowserFrame() () at
/usr/lib64/libakregatorprivate.so.4
#12 0x7f100b0f48b9 in Akregator::BrowserFrame::~BrowserFrame() () at
/usr/lib64/libakregatorprivate.so.4
#13 0x7f100b0f3035 in Akregator::FrameManager::slotRemoveFrame(int) () at
/usr/lib64/libakregatorprivate.so.4
#14 0x7f1005190e30 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4
#15 0x7f0fef9bf651 in  () at /usr/lib64/kde4/akregatorpart.so
#16 0x7f0fef9bea5d in  () at /usr/lib64/kde4/akregatorpart.so
#17 0x7f1005190e30 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4
#18 0x7f1006485532 in QAbstractButton::clicked(bool) () at
/usr/lib64/qt/lib/libQtGui.so.4
#19 0x7f10061dd763 in  () at /usr/lib64/qt/lib/libQtGui.so.4
#20 0x7f10061de954 in  () at /usr/lib64/qt/lib/libQtGui.so.4
#21 0x7f10061dea44 in QAbstractButton::mouseReleaseEve

[kontact] [Bug 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]

2015-01-21 Thread maria
https://bugs.kde.org/show_bug.cgi?id=193514

maria  changed:

   What|Removed |Added

 CC||kamili.ta...@gmail.com

--- Comment #208 from maria  ---
#6  0xb779202c in Kontact::Plugin::identifier (this=0x900806e) at
/usr/include/qt4/QtCore/qstring.h:711
#7  0xb77abff9 in Kontact::MainWindow::activatePluginModule (this=0x9028dc8) at
/build/buildd/kdepim-4.2.90/kontact/src/mainwindow.cpp:300
#8  0xb77ac0a4 in Kontact::MainWindow::setActivePluginModule (this=0x9028dc8,
module=@0xbf81bbd4) at
/build/buildd/kdepim-4.2.90/kontact/src/mainwindow.cpp:278
#9  0x0804ac57 in KontactApp::newInstance (this=0xbf81c738) at
/build/buildd/kdepim-4.2.90/kontact/src/main.cpp:147
#10 0xb6c4b516 in KUniqueApplicationAdaptor::newInstance (this=0x90888e8,
asn_id=@0xa631d18, args=@0x9f49f88) at
/build/buildd/kde4libs-4.2.90/kdeui/kernel/kuniqueapplication.cpp:454
#11 0xb6c4b5be in KUniqueApplicationAdaptor::qt_metacall (this=0x90888e8,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf81be28)
at
/build/buildd/kde4libs-4.2.90/obj-i486-linux-gnu/kdeui/kuniqueapplication_p.moc:75
#12 0xb5c79e2a in QDBusConnectionPrivate::deliverCall (this=0x9010e68,
object=0x90888e8, msg=@0xaef7558, metaTypes=@0xa014d94, slotIdx=4) at
qdbusintegrator.cpp:891
#13 0xb5c7b149 in QDBusConnectionPrivate::activateCall (this=0x9010e68,
object=0x90888e8, flags=337, msg=@0xaef7558) at qdbusintegrator.cpp:803
#14 0xb5c7b5b1 in QDBusConnectionPrivate::activateObject (this=0x9010e68,
node=@0xaef7544, msg=@0xaef7558, pathStartPos=16) at qdbusintegrator.cpp:1375
#15 0xb5c7baaa in QDBusActivateObjectEvent::placeMetaCall (this=0xaef7518) at
qdbusintegrator.cpp:1469
#16 0xb5b72150 in QObject::event (this=0xbf81c738, e=0xaef7518) at
kernel/qobject.cpp:1118
http://www.immobilier-tamansourt.com";> Kech 

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 166475] Distribution lists not saved

2010-06-09 Thread Ferrari Renato Maria
https://bugs.kde.org/show_bug.cgi?id=166475


Ferrari Renato Maria  changed:

   What|Removed |Added

 CC||renatoferr...@tiscali.it




--- Comment #5 from Ferrari Renato Maria   2010-06-10 
08:00:36 ---
Same here with suse factory KDE 4..3.5, also after update completed yesterday.
OS: Linux, openSUSE 11.2
KDE, Kontact and Kaddressbook: 4.3.5
Kmail: 1.12.4

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 206937] SpamBayes function in KMail severely regressed after update to KDE 4.3.1

2009-09-13 Thread Maria Niku
https://bugs.kde.org/show_bug.cgi?id=206937





--- Comment #7 from Maria Niku   2009-09-13 11:11:12 ---
I now managed to fix my other problem and was able to test the changes to the
spam controls. Everything works now. Thank you again.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 207210] KMail crashes when accessing the folders of an email account

2009-09-12 Thread Maria Niku
https://bugs.kde.org/show_bug.cgi?id=207210





--- Comment #2 from Maria Niku   2009-09-12 22:22:09 ---
Apologies. Here the error messages directly:

1. Error message:

Unable to Enter Folder
This means that an attempt to enter (in other words, to open) the requested
folder imaps://(address):993/;TYPE=LIST was rejected.
Details of the request:
URL: (unknown)
Date and time: Saturday 12 September 2009 22:44
Additional information: imaps://(address):993/;TYPE=LIST
Possible causes:
Your access permissions may be inadequate to perform the requested operation on
this resource.
The file may be in use (and thus locked) by another user or application.
Possible solutions:
Check your access permissions on this resource.
Check to make sure that no other application or user is using the file or has
locked the file.
Contact your appropriate computer support system, whether the system
administrator, or technical support group for further assistance.

2. Crash report:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f467f1e6820 (LWP 3154))]

Thread 2 (Thread 0x7f4669642910 (LWP 3187)):
#0  0x003e3520b57d in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x003bb4a5ace2 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQtCore.so.4
#2  0x003bb4a50e22 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x003bb4a59cd5 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x003e3520686a in start_thread () from /lib64/libpthread.so.0
#5  0x003e346de3bd in clone () from /lib64/libc.so.6
#6  0x in ?? ()

Thread 1 (Thread 0x7f467f1e6820 (LWP 3154)):
[KCrash Handler]
#5  0x00380f59ee08 in KIO::Slave::deref() () from /usr/lib64/libkio.so.5
#6  0x00380f59f7f9 in KIO::Slave::gotInput() () from /usr/lib64/libkio.so.5
#7  0x00380f5a18fc in KIO::Slave::qt_metacall(QMetaObject::Call, int,
void**) () from /usr/lib64/libkio.so.5
#8  0x003bb4b54fdc in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQtCore.so.4
#9  0x00380f4baf57 in ?? () from /usr/lib64/libkio.so.5
#10 0x00380f4bb06d in KIO::Connection::qt_metacall(QMetaObject::Call, int,
void**) () from /usr/lib64/libkio.so.5
#11 0x003bb4b4f309 in QObject::event(QEvent*) () from
/usr/lib64/libQtCore.so.4
#12 0x003cf5d8ee2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQtGui.so.4
#13 0x003cf5d95e5e in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQtGui.so.4
#14 0x00380ea11b56 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libkdeui.so.5
#15 0x003bb4b3fcbc in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQtCore.so.4
#16 0x003bb4b408c8 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#17 0x003bb4b68743 in ?? () from /usr/lib64/libQtCore.so.4
#18 0x003bb3e3790e in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#19 0x003bb3e3b0e8 in ?? () from /lib64/libglib-2.0.so.0
#20 0x003bb3e3b20a in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#21 0x003bb4b683b6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQtCore.so.4
#22 0x003cf5e21b8e in ?? () from /usr/lib64/libQtGui.so.4
#23 0x003bb4b3e5f2 in
QEventLoop::processEvents(QFlags) () from
/usr/lib64/libQtCore.so.4
#24 0x003bb4b3e9c4 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQtCore.so.4
#25 0x003bb4b40b79 in QCoreApplication::exec() () from
/usr/lib64/libQtCore.so.4
#26 0x00403d17 in _start ()

3. Relevant parts of .xsession-errors

QThreadStorage: Thread 0x20556f0 exited after QThreadStorage 2147483638
destroyed
kdeinit4: preparing to launch /usr/bin/kontact
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib64/kde4/kio_imap4.so
(3132)/ kdemain: IMAP4::kdemain
kdeinit4: preparing to launch /usr/lib64/kde4/kio_imap4.so
(3133)/ kdemain: IMAP4::kdemain
kdeinit4: preparing to launch /usr/lib64/kde4/kio_imap4.so
(3134)/ kdemain: IMAP4::kdemain
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
*** KMail got signal 11

[Bug 206937] SpamBayes function in KMail severely regressed after update to KDE 4.3.1

2009-09-12 Thread Maria Niku
https://bugs.kde.org/show_bug.cgi?id=206937





--- Comment #6 from Maria Niku   2009-09-12 22:07:45 ---
I am very glad if this problem can be sorted out so easily, many thanks for
checking it. 

Unfortunately, a new problem has now emerged which prevents me from testing
this. I have sent a bug report for it since ther was a crash involved:

https://bugs.kde.org/show_bug.cgi?id=207210

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 207210] New: KMail crashes when accessing the folders of an email account

2009-09-12 Thread Maria Niku
https://bugs.kde.org/show_bug.cgi?id=207210

   Summary: KMail crashes when accessing the folders of an email
account
   Product: kmail
   Version: 1.12.1
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: mr.wi...@gmail.com


Version:   1.12.1 (using KDE 4.3.1)
OS:Linux
Installed from:Fedora RPMs

When trying to open the folders of an IMAP email account I have set up in
KMail, there is an error message and then KMail crashes. This is a new problem,
found in the evening (CET) of September 12th. It was not there in the morning
of the same day. Nothing in the email account or other settings has changed
between morning and evening, and the mail account is accessible without
problems in Thunderbird- The other two email accounts (gmail, IMAP) I have set
in KMail are not producing problems.

Error message: http://pastebin.com/m6f9dfa73

Crash report: http://pastebin.com/m2385eaee

Relevant part of .xsession-errors: http://pastebin.com/m575aa4fb

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 206937] SpamBayes function in KMail severely regressed after update to KDE 4.3.1

2009-09-11 Thread Maria Niku
https://bugs.kde.org/show_bug.cgi?id=206937





--- Comment #4 from Maria Niku   2009-09-11 23:33:47 ---
I attached two email messages that were marked as spam. 

Here the spam filters in kmailrc

http://pastebin.com/m628728e4

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 206937] SpamBayes function in KMail severely regressed after update to KDE 4.3.1

2009-09-11 Thread Maria Niku
https://bugs.kde.org/show_bug.cgi?id=206937





--- Comment #3 from Maria Niku   2009-09-11 23:33:02 ---
Created an attachment (id=36880)
 --> (http://bugs.kde.org/attachment.cgi?id=36880)
Attached email message 2

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 206937] SpamBayes function in KMail severely regressed after update to KDE 4.3.1

2009-09-11 Thread Maria Niku
https://bugs.kde.org/show_bug.cgi?id=206937





--- Comment #2 from Maria Niku   2009-09-11 23:32:27 ---
Created an attachment (id=36879)
 --> (http://bugs.kde.org/attachment.cgi?id=36879)
Attached email message

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 206937] New: SpamBayes function in KMail severely regressed after update to KDE 4.3.1

2009-09-09 Thread Maria Niku
https://bugs.kde.org/show_bug.cgi?id=206937

   Summary: SpamBayes function in KMail severely regressed after
update to KDE 4.3.1
   Product: kmail
   Version: 1.12.1
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: mr.wi...@gmail.com


Version:   1.12.1 (using KDE 4.3.1)
OS:Linux
Installed from:Fedora RPMs

After the update from 4.3.0 to 4.3.1 yesterday, I deleted all spam filters and
re-ran the anti-spam wizard. I did not change the given settings: emails marked
as spam and those marked as probable spam are moved to specified, separate
folders.

Prior to the update, SpamBayes was functioning well: there were some mistakes,
as is to be expected, but it learned from those quickly. Now, out of the 70-100
emails that have arrived since the update, EVERY SINGLE one has been marked as
either spam or probable spam. Having manually marked all of those emails as not
spam, there has been no visible change.

There are no errors related to KMail or SpamBayes in .xsession-errors. I posted
about this in the KDE Community forums and was adviced by an admin to report a
bug.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs