[Bug 215002] kmail crass when I delete an attachment

2009-11-19 Thread Iacopo
https://bugs.kde.org/show_bug.cgi?id=215002





--- Comment #2 from Iacopo iacopo controgeografie net  2009-11-19 10:10:41 ---
It's similar, but not the same. Kmail does not crash when I'm deleting a 
message (in this case it works perfectly) but when I'm deleting an attachment 
from a message.

I hope this is helpful.

Iacopo

-- 
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 215002] New: kmail crass when I delete an attachment

2009-11-17 Thread Iacopo
https://bugs.kde.org/show_bug.cgi?id=215002

   Summary: kmail crass when I delete an attachment
   Product: kmail
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: iac...@controgeografie.net


Application that crashed: kmail
Version of the application: 1.12.1
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-2-686 i686
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
I right click on the attachment and select the command delete and kmail crash
immediately. The message is in a local folder. My versioni is 1.12.1 on a
laptop with Debian squeeze and kde 4.3.2

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0x74736547 in ?? ()
#7  0xb747ba0b in KMReaderWin::displayMessage (this=0x899f478) at
../../kmail/kmreaderwin.cpp:1605
#8  0xb747bc20 in KMReaderWin::updateReaderWin (this=0x887b710) at
../../kmail/kmreaderwin.cpp:1545
#9  0xb7488647 in KMReaderWin::qt_metacall (this=0x887b710,
_c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfbf3168) at
./kmreaderwin.moc:168
#10 0xb70f4303 in QMetaObject::activate (sender=0x887b768, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#11 0xb70f4f42 in QMetaObject::activate (sender=0x887b768, m=0xb71d0d84,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#12 0xb712fb37 in QTimer::timeout (this=0x887b768) at
.moc/release-shared/moc_qtimer.cpp:128
#13 0xb70fa65e in QTimer::timerEvent (this=0x887b768, e=0xbfbf35ec) at
kernel/qtimer.cpp:261
#14 0xb70ef39f in QObject::event (this=0x887b768, e=0xbfbf35ec) at
kernel/qobject.cpp:1074
#15 0xb671ea94 in QApplicationPrivate::notify_helper (this=0x866e130,
receiver=0x887b768, e=0xbfbf35ec) at kernel/qapplication.cpp:4065
#16 0xb6726bee in QApplication::notify (this=0xbfbf3908, receiver=0x887b768,
e=0xbfbf35ec) at kernel/qapplication.cpp:3605
#17 0xb7e840fd in KApplication::notify (this=0xbfbf3908, receiver=0x887b768,
event=0xbfbf35ec) at ../../kdeui/kernel/kapplication.cpp:302
#18 0xb70df1eb in QCoreApplication::notifyInternal (this=0xbfbf3908,
receiver=0x887b768, event=0xbfbf35ec) at kernel/qcoreapplication.cpp:610
#19 0xb710de21 in QCoreApplication::sendEvent (this=0x8670e34) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 QTimerInfoList::activateTimers (this=0x8670e34) at
kernel/qeventdispatcher_unix.cpp:580
#21 0xb710a317 in timerSourceDispatch (source=0x8670e70) at
kernel/qeventdispatcher_glib.cpp:184
#22 idleTimerSourceDispatch (source=0x8670e70) at
kernel/qeventdispatcher_glib.cpp:231
#23 0xb4822e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0xb4826623 in ?? () from /lib/libglib-2.0.so.0
#25 0xb48267a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0xb710a041 in QEventDispatcherGlib::processEvents (this=0x86478d0,
flags=...) at kernel/qeventdispatcher_glib.cpp:407
#27 0xb67be305 in QGuiEventDispatcherGlib::processEvents (this=0x86478d0,
flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#28 0xb70dd83a in QEventLoop::processEvents (this=0xbfbf3810, flags=...) at
kernel/qeventloop.cpp:149
#29 0xb70ddc82 in QEventLoop::exec (this=0xbfbf3810, flags=...) at
kernel/qeventloop.cpp:201
#30 0xb70e00d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0xb671e917 in QApplication::exec () at kernel/qapplication.cpp:3525
#32 0x0804a6d0 in main (argc=0, argv=0x0) at ../../kmail/main.cpp:146

Reported using DrKonqi

-- 
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 193454] New: Error signing and verifying gpg/Smime email

2009-05-21 Thread Iacopo
https://bugs.kde.org/show_bug.cgi?id=193454

   Summary: Error signing and verifying gpg/Smime email
   Product: kmail
   Version: unspecified
  Platform: Debian testing
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: avv...@spalletti.it


Version:(using KDE 4.2.2)
OS:Linux
Installed from:Debian testing/unstable Packages

Since upgrading to Kmail in KDE 4 i couldn't sign and verify email anymore.
Signing works randomly during any kmail (kontact, in fact) session, and i got
or General Error
message upon signing or No key has been configured for this identity message
(actual message
is longer, and i have it in italian, so it maybe not the exact translation).
Sign verify fails with the Not enough information to validate the sign
(again, it's a
translation from the actual italian message).
Upon opening identity configuration an error message box appears: An error has
occurred while retrieving keys from the backend. General error (translation
from italian).
Same error if i create an new user and generate a new keypair.
In KDE 3.5 kmail it's ok.

-- 
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