[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received

[mike]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=86423 




--- Additional Comments From kde_bug_tracking multiwebinc com  2008-05-29 
21:02 ---
In reply to Marcus Harrison, this bug is about replying to HTML email with the 
same format as what it was received. If I recall correctly, you could display 
HTML e-mails fine, it's when you reply to them that you lose any formatting in 
the main e-mail. KWrite is only a plain text editor and I don't think that 
anyone would be happy with having to write their own HTML tags manually instead 
of just selecting text and clicking a nice "Bold" button. Tables and font 
colors would be an even more difficult thing. I would love to switch to Kmail, 
but until they provide this basic functionality, I'm sticking wtih Thunderbird.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 324807] Sends no UID in UID STORE command

[mike]

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

m...@gaima.co.uk changed:

   What|Removed |Added

 CC||m...@gaima.co.uk

--- Comment #13 from m...@gaima.co.uk ---
(In reply to Randy Simons from comment #12)
> I just made the error to reply an e-mail using KMail, and sure enough, my
> message vanished into thin air after sending. Should I reopen the bug? And
> is there a way to enable logging more permanently?

I'd certainly like to see the bug re-opened, as I'm hit but this repeatedly.
Currently using 4.12.5


Here the message I actually sent is not in the log.


C: A03 SELECT "Sent"
S: * FLAGS ( \Answered \Flagged \Deleted \Seen \Draft $FORWARDED $SENT $ERROR
$REPLIED $SIGNED $ATTACHMENT $ENCRYPTED $INVITATION $QUEUED )
S: * OK Flags permitted. [ PERMANENTFLAGS ( \Answered \Flagged \Deleted \Seen
\Draft $FORWARDED $SENT $ERROR $REPLIED $SIGNED $ATTACHMENT $ENCRYPTED
$INVITATION $QUEUED \* )  ]
S: * 17258 EXISTS
S: * 0 RECENT
S: * OK UIDs valid [ UIDVALIDITY 1138124926  ]
S: * OK Predicted next UID [ UIDNEXT 17892  ]
S: * OK Highest [ HIGHESTMODSEQ 950  ]
S: A03 OK Select completed ( 0.002 secs ) . [ READ-WRITE  ]
C: A04 UID STORE  +FLAGS (\Seen $SENT)
S: A04 BAD Error in IMAP command UID STORE: Invalid uidset

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

[korganizer] [Bug 381166] korganizer crashes on startup, evey time on a Fedora 25 system.

[Mike]

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

--- Comment #6 from Mike  ---
(In reply to Filipus Klutiero from comment #5)
> So you are saying that KOrganizer crashes immediately at startup, but
> Kontact for its part does not, and only crashes when choosing calendar,
> to-do's or journal. Is that correct? If so, issue #388019, which was marked
> as a duplicate, seems different.

Yes, that is what was happening. korganzer crashed and kontacts ran fine. I
have since been able to update to a newer version of korganizer (and the other
KDE tools), and the problem went away.  I don't know what the fix was, but
korganizer runs okay for me now.  Currently using:

korganizer.x86_64   17.12.3-1.fc26 
korganizer-libs.x86_64  17.12.3-1.fc26

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

[korganizer] [Bug 381166] New: korganizer crashes on startup, evey time on a Fedora 25 system.

[Mike]

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

Bug ID: 381166
   Summary: korganizer crashes on startup, evey time on a Fedora
25 system.
   Product: korganizer
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: agendaview (weekview)
  Assignee: kdepim-bugs@kde.org
  Reporter: kdeb...@mikesoffice.com
  Target Milestone: ---

This was an a recently upgraded (crashes since the upgrade) fedora 25 system.
It crashes every time.  If a run kontact and choose calendar, to-do's, or
journal, I get the same crash.

The korganizer rpm info:
korganizer.x86_64   16.12.3-1.fc25 @updates 
korganizer-libs.x86_64  16.12.3-1.fc25
@@commandline

Also the Crash Reporting Assistant comes up on a crash and that is where I got
the backtrace below. But when I get to the dialog for logging into the KDE bug
tracking system, the 'Login' button remains desensitized and I'm unable to
login/use the assistant.


Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff92bd60980 (LWP 28746))]

Thread 6 (Thread 0x7ff913fff700 (LWP 28783)):
#0  0x7ff93f98a879 in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7ff93f945060 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7ff93f94527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7ff9515c66eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7ff95157768a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7ff9513d45e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7ff9513d89ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7ff94eba573a in start_thread () at /lib64/libpthread.so.0
#8  0x7ff9507cbe7f in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7ff918a0b700 (LWP 28778)):
#0  0x7ff9507bff3d in poll () at /lib64/libc.so.6
#1  0x7ff93f945166 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7ff93f94527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7ff9515c66eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7ff95157768a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7ff9513d45e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7ff9513d89ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7ff94eba573a in start_thread () at /lib64/libpthread.so.0
#8  0x7ff9507cbe7f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7ff91920c700 (LWP 28773)):
#0  0x7ff9507bff3d in poll () at /lib64/libc.so.6
#1  0x7ff93f945166 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7ff93f94527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7ff9515c66eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7ff95157768a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7ff9513d45e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7ff95a785fb9 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7ff9513d89ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7ff94eba573a in start_thread () at /lib64/libpthread.so.0
#9  0x7ff9507cbe7f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7ff91120c700 (LWP 28772)):
#0  0x7ff9507bff3d in poll () at /lib64/libc.so.6
#1  0x7ff93f945166 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7ff93f9454f2 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3  0x7ff92f80aa76 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0
#4  0x7ff93f96cb93 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7ff94eba573a in start_thread () at /lib64/libpthread.so.0
#6  0x7ff9507cbe7f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7ff919a0d700 (LWP 28771)):
#0  0x7ff9507bbb0d in read () at /lib64/libc.so.6
#1  0x7ff93f9894d0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7ff93f944c83 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7ff93f945104 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7ff93f94527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7ff93f9452c1 in glib_worker_main () at /lib64/libglib-2.0.so.0
#6  0x7ff93f96cb93 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#7  0x7ff94eba573a in start_thread () at /lib64/libpthread.so.0
#8  0x7ff9507cbe7f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7ff92bd60980 (LWP 28746)):
[KCrash Handler]
#4  0x7ff959a58275 in
EventViews::AgendaView::placeDecorations(QList&,
QDate const&, QWidget*, b

[kleopatra] [Bug 314341] New: Temporary files remain after encrypting

[Mike]

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

Bug ID: 314341
   Summary: Temporary files remain after encrypting
Classification: Unclassified
   Product: kleopatra
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: trawle...@yahoo.com
CC: m...@kde.org

Great program but from time to time the encryption process leaves a temporary
file (or at least I'm assuming that is what they are) which has same name and
size as the encrypted file .. the file has a 6 hex digit extension (e.g.
.gpg.Fu6680 ) each encryption (usually) creates an additional temp file.

I usually delete these files periodically (although they remain open/locked in
Kleopatra whilst its running) and no ill seems to occur .. just a little wary
that there may be information there that weakens security.

Reproducible: Always

Steps to Reproduce:
1.Take a (big file e.g. 4mb)
2.encrypt using personal key (and select delete original option)
3.look in directory of original file (encrypted fiel there also!)
Actual Results:  
Temporary file visible

Expected Results:  
deleted the file completely?

Not sur eif it presents any security weakening

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

[kleopatra] [Bug 314341] Temporary files remain after encrypting

[Mike]

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

Mike  changed:

   What|Removed |Added

   Platform|Ubuntu Packages |MS Windows
 OS|Linux   |MS Windows

-- 
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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]

[mike]

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


m...@urbanmapping.com changed:

   What|Removed |Added

 CC||m...@urbanmapping.com




-- 
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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]

[mike]

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





--- Comment #33 from2010-08-13 02:14:59 ---
Created an attachment (id=50096)
 --> (http://bugs.kde.org/attachment.cgi?id=50096)
New crash information added by DrKonqi

KMail always crashes when filtering messages from an IMAP account. When
applying filter manually, it crashes after going through about 10 or so
messages. When receiving thousands of new messages, it always fails, but seems
to get through 50-100 before it crashes. Doesn't fail on the same message
twice; just applying all filters to one message at a time works fine.

-- 
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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]

[mike]

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





--- Comment #34 from2010-08-16 21:19:58 ---
Created an attachment (id=50629)
 --> (http://bugs.kde.org/attachment.cgi?id=50629)
New crash information added by DrKonqi

Filtering IMAP messages, again. Always fails when applying the filter manually.
Again, < 100 messages to filter, crashes Kmail.

-- 
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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]

[mike]

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





--- Comment #35 from2010-08-16 23:39:53 ---
Created an attachment (id=50633)
 --> (http://bugs.kde.org/attachment.cgi?id=50633)
New crash information added by DrKonqi

Seg fault upon applying all filters manually to less than ten messages. It's
amazing how easy this is to make crash. Just select a few messages, apply all
filters, and there's about a 99% chance Kmail will crash.

-- 
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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]

[mike]

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





--- Comment #36 from2010-08-17 00:56:34 ---
Created an attachment (id=50636)
 --> (http://bugs.kde.org/attachment.cgi?id=50636)
New crash information added by DrKonqi

More crashing on filtering over IMAP. Had selected 3 messages to apply all
filters to when this one happened. Makes using KMail essentially impossible.

-- 
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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]

[mike]

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





--- Comment #37 from2010-08-17 01:41:07 ---
Created an attachment (id=50638)
 --> (http://bugs.kde.org/attachment.cgi?id=50638)
New crash information added by DrKonqi

This crash report may be useful as it occurred while applying all filters to
just one message.
Perhaps less to sort through in this attached report.

-- 
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 151831] IMAP resources broken

[Mike Arthur]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=151831 
mike mikearthur co uk changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
  everconfirmed|0   |1



--- Additional Comments From mike mikearthur co uk  2007-11-27 22:58 ---
Confirmed here too on Debian.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 151831] IMAP resources broken

[Mike Arthur]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=151831 
mike mikearthur co uk changed:

   What|Removed |Added

 CC||mike mikearthur co uk
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 151831] IMAP resources broken

[Mike Arthur]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=151831 




--- Additional Comments From mike mikearthur co uk  2007-11-28 00:10 ---
Confirmed for me too.
I still think this is a bug that needs fixing, this issue should not be in KDE4.

I went from:
[IMAP Resource]
TheIMAPResourceEnabled=true
TheIMAPResourceFolderParent=.360482238.directory/INBOX

to:
[IMAP Resource]
TheIMAPResourceAccount=360482238
TheIMAPResourceEnabled=true
TheIMAPResourceFolderParent=.360482238.directory/INBOX
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 152898] Kmail crashed with signal 6 SIGABRT

[Mike D]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=152898 




--- Additional Comments From llemikebyw aol com  2008-02-17 13:46 ---
Kmail crashes continually with 6 SIGABRT signal when I am trying to read 
messages from AOL IMAP server.

O/S is OpenSUSE 10.3 fully patched (Running on ASRock K7VT4A Pro M/B with 
Athlon XP2000+ cpu).
KDE desktop 3.5.7 Release 72.6.

Only major difference from standard install is VLC MediaPlayer.

This is the error trace...



System configuration startup check disabled.

[?1034h(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5882950 (LWP 3791)]
[New Thread 0xb3b26b90 (LWP 3795)]
[New Thread 0xb4327b90 (LWP 3794)]
[New Thread 0xb4b28b90 (LWP 3793)]
[New Thread 0xb5329b90 (LWP 3792)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xe410 in __kernel_vsyscall ()
#7  0xb6e188f5 in raise () from /lib/libc.so.6
#8  0xb6e1a1e1 in abort () from /lib/libc.so.6
#9  0xb6fde380 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb6fdbc25 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb6fdbc62 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb6fdc505 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6
#13 0xb7bcaf6f in KMReaderWin::setMsg () from /opt/kde3/lib/libkmailprivate.so
#14 0xb7d424ee in KMMainWidget::slotMsgSelected ()
   from /opt/kde3/lib/libkmailprivate.so
#15 0xb7d54b11 in KMMainWidget::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so
#16 0xb72ab90d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb7b744ce in KMHeaders::selected () from /opt/kde3/lib/libkmailprivate.so
#18 0xb7b7c5eb in KMHeaders::highlightMessage ()
   from /opt/kde3/lib/libkmailprivate.so
#19 0xb7b7c9dc in KMHeaders::highlightMessage ()
   from /opt/kde3/lib/libkmailprivate.so
#20 0xb7b856e7 in KMHeaders::qt_invoke () from /opt/kde3/lib/libkmailprivate.so
#21 0xb72ab90d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb75f2c71 in QListView::currentChanged ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb738b8de in QListView::setCurrentItem ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb738e866 in QListView::contentsMousePressEventEx ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb738f214 in QListView::contentsMousePressEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb5f9b05d in KLis

[Bug 119677] kmail line wraps inserted file

[Mike Frysinger]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=119677 
vapier gentoo org changed:

   What|Removed |Added

 CC||vapier gentoo org



--- Additional Comments From vapier gentoo org  2008-03-01 21:17 ---
sometimes when you insert a file, you *want* it line wrapped ... so the 
behavior cant be completely one or the other

for inserting patches inline, i just turn off line wrapping for the whole 
e-mail (after manually wrapping the lines with the assistance of auto-line 
wrapping)
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 158640] New: clicking "insert file recent" button should act like "insert file"

[Mike Frysinger]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=158640 
   Summary: clicking "insert file recent" button should act like
"insert file"
   Product: kmail
   Version: 1.9.9
  Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs kde org
ReportedBy: vapier gentoo org


Version:   1.9.9 (using KDE 3.5.9)
Installed from:Gentoo Packages
Compiler:  gcc-4.2.3 ppc
OS:Linux

in the e-mail composer, the "insert file recent" toolbar button does nothing 
when you click it.  instead, it should behave just like the "insert file" 
toolbar button.  this way you only need "insert file recent" added to your 
toolbar rather than both.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 158641] New: "Send Queued Messages Via" icon should default to the same as "Send Queued Messages"

[Mike Frysinger]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=158641 
   Summary: "Send Queued Messages Via" icon should default to the
same as "Send Queued Messages"
   Product: kmail
   Version: 1.9.9
  Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs kde org
ReportedBy: vapier gentoo org


Version:   1.9.9 (using KDE 3.5.9)
Installed from:Gentoo Packages
Compiler:  gcc-4.2.3 ppc
OS:Linux

there is no default icon currently for the toolbar button "Send Queued Messages 
Via".  it should have the same default icon as the "Send Queued Messages" 
toolbar button.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 145864] Send Queued Messages function sometimes disabled

[Mike Frysinger]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=145864 




--- Additional Comments From vapier gentoo org  2008-03-01 21:22 ---
i found you can workaround it by going to the outbox, double clicking one of 
the messages (to move it back to the composer), and then hitting the send button
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 158643] New: keyboard shortcuts missing in the "Find Messages" dialog

[Mike Frysinger]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=158643 
   Summary: keyboard shortcuts missing in the "Find Messages" dialog
   Product: kmail
   Version: 1.9.9
  Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs kde org
ReportedBy: vapier gentoo org


Version:   1.9.9 (using KDE 3.5.9)
Installed from:Gentoo Packages
Compiler:  gcc-4.2.3 ppc
OS:Linux

when using the "Find Messages" dialog, i often hit "R" (reply) or "A" (reply 
all) or "CTRL+S" (save) when selecting messages, only to find out none of the 
keyboard shortcuts that are available in the "Message List" pane are available 
in the "Find Messages" dialog.

if none of the shortcuts are conflicting (and i dont think they are), then all 
of the possible shortcuts that are available in the main "Message List" pane 
should be available in the "Find Messages" dialog.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 158644] New: new composer toolbar button "Attach File Recent"

[Mike Frysinger]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=158644 
   Summary: new composer toolbar button "Attach File Recent"
   Product: kmail
   Version: 1.9.9
  Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs kde org
ReportedBy: vapier gentoo org


Version:   1.9.9 (using KDE 3.5.9)
Installed from:Gentoo Packages
Compiler:  gcc-4.2.3 ppc
OS:Linux

there are drop-down variations of many buttons (like Send/Insert File/etc...), 
and i think an "Attach File Recent" would be a nice addition to the composer 
toolbar.  it'd act accordingly:
 - default icon matches "Attach File" default icon
 - clicking the button does the same thing as clicking "Attach File" button
 - holding down the button brings up a drop down list of recently attached files
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 126064] JJ: Account settings dialogs for SMTP/POP3/IMAP should be more similar

[Mike Stoddart]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=126064 
pixellent rogers com changed:

   What|Removed |Added

 CC|pixellent rogers com|
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 55838] messages turn into subject "No Subject" and sender "Unknown" after clicked for viewing

[Mike Jolley]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=55838 




--- Additional Comments From mikejolley sbcglobal net  2008-03-29 23:23 
---
I get this problem every few weeks or so.  I hate deleting the index because I 
lose all my classifications.  I'm thinking of stopping using KMail, and then 
that would in turn make me stop using Kontact since the Palm synch stuff 
doesn't work well either.

I'm using Sidux so I have fairly recent versions of KMail.  I upgrade 
everything every month or so.  I use bogofilter as my spam filter, but if I 
recall, the problem was worse when I used SpamAssassin.  I'm using default 
settings for pretty much everything, POP accounts.

I have a lot of desktops running and I typically don't manually shut programs 
down.  I usually only reboot the computer when I do an upgrade.  The problem 
started happening today after an upgrade I did yesterday.  This might be a 
coincidence.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 55838] messages turn into subject "No Subject" and sender "Unknown" after clicked for viewing

[Mike Jolley]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=55838 




--- Additional Comments From mikejolley sbcglobal net  2008-03-29 23:35 
---
This bug still exists as of 3/29/2008.  It's marked as a duplicate of a bug 
that might be unrelated.

I get this problem every few weeks or so.  I hate deleting the index because I 
lose all my classifications.  I'm thinking of stopping using KMail, and then 
that would in turn make me stop using Kontact since the Palm synch stuff 
doesn't work well either.

I'm using Sidux so I have fairly recent versions of KMail.  I upgrade 
everything every month or so.  I use bogofilter as my spam filter, but if I 
recall, the problem was worse when I used SpamAssassin.  I'm using default 
settings for pretty much everything, POP accounts.

I have a lot of desktops running and I typically don't manually shut programs 
down.  I usually only reboot the computer when I do an upgrade.  The problem 
started happening today after an upgrade I did yesterday.  This might be a 
coincidence.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 158643] Search dialog should have message actions like "reply"

[Mike Frysinger]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=158643 




--- Additional Comments From vapier gentoo org  2008-05-07 18:16 ---
i really have no idea what you're talking about

the purpose is obvious and pretty self explanatory ... after all, they are 
called "shortcuts" for a reason
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 119677] kmail line wraps inserted file

[Mike Frysinger]

http://bugs.kde.org/show_bug.cgi?id=119677





--- Comment #3 from Mike Frysinger   2008-12-11 01:16:05 ---
ive never seen that behavior.  disabling word wrap and then inserting a file
has always worked as expected: the file is not word wrapped.  ive used kde-3.5
and now kde-4.1 without any issues ...


-- 
Configure bugmail: http://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 135717] Deleting many maildir messages very slow

[Mike Frysinger]

http://bugs.kde.org/show_bug.cgi?id=135717


Mike Frysinger vapier gentoo org changed:

   What|Removed |Added

 CC||vap...@gentoo.org




--- Comment #9 from Mike Frysinger   2008-12-27 10:38:55 ---
kmail 1.10.3 (from kde 4.1.3) appears to do the same thing ... ive tweaked the
output to make it a bit more readable, but here's the strace from a delete in a
local maildir

stat(".../.mail/trash/tmp/1230370293.7494.WvV10:2,S", 0x54ad8f8) = -1 ENOENT
lstat(".../.mail/trash/tmp/1230370293.7494.WvV10:2,S", 0x7fff6dea4820) = -1
ENOENT
open(".../.mail/trash/tmp/1230370293.7494.WvV10:2,S",
O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666) = 38
fstat(38, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
write(38, "Delivered-To: vapierfil...@gmail."..., 4096) = 4096
write(38, "de?subject=help>\nList-Subscribe: "..., 2228) = 2228
close(38)   = 0
stat(".../.mail/trash/cur/1230370293.7494.WvV10:2,S", 0x6a3cb78) = -1 ENOENT
lstat(".../.mail/trash/cur/1230370293.7494.WvV10:2,S", 0x7fff6dea48e0) = -1
stat(".../.mail/trash/tmp/1230370293.7494.WvV10:2,S", {st_mode=S_IFREG|0644,
st_size=6324, ...}) = 0
stat(".../.mail/trash/cur/1230370293.7494.WvV10:2,S", 0x6a229e8) = -1 ENOENT
lstat(".../.mail/trash/cur/1230370293.7494.WvV10:2,S", 0x7fff6dea3880) = -1
ENOENT
rename(".../.mail/trash/tmp/1230370293.7494.WvV10:2,S",
".../.mail/trash/cur/1230370293.7494.WvV10:2,S") = 0
unlink(".../.mail/misc projects/cur/1230370293.7494.WvV10") = 0


-- 
Configure bugmail: http://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 135717] Deleting many maildir messages very slow

[Mike Frysinger]

http://bugs.kde.org/show_bug.cgi?id=135717


Mike Frysinger vapier gentoo org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1




--- Comment #10 from Mike Frysinger   2008-12-27 10:39:54 ---
*** This bug has been confirmed by popular vote. ***


-- 
Configure bugmail: http://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 183875] kmail keeps spawning "gpgsm --server" but never kills/reaps them

[Mike Frysinger]

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





--- Comment #2 from Mike Frysinger   2009-07-22 07:13:49 ---
i just noticed that the issue seems to be better with kde-4.2.4 ...

at least on my system, it seems to stabilize at a handful of gpgsm instances
(like 6 of them), although it'd be nice if there werent any duplicate ones at
all

-- 
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 203592] New: kmail crashes after downloading attachment via IMAP

[Mike Spark]

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

   Summary: kmail crashes after downloading attachment via IMAP
   Product: kmail
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: master.swa...@gmail.com


Application that crashed: kmail
Version of the application: 1.12.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-1-686 i686

What I was doing when the application crashed:
I am using gmail via IMAP. When I try to save an attachment, it is being
downloaded, and just after kmail finishes downloading, it crashes. It is not a
constant error, sometimes the file is being saved and everything is OK. Also,
it happens when I try to save quite a big files (~25 MB).

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  DwString::c_str (this=0xa644ff0, msg=0xa3e8088, partSpecifier=...) at
../../mimelib/mimelib/string.h:618
#7  DwMessageComponent::partId (this=0xa644ff0, msg=0xa3e8088,
partSpecifier=...) at ../../mimelib/mimelib/msgcmp.h:259
#8  KMLoadPartsCommand::slotPartRetrieved (this=0xa644ff0, msg=0xa3e8088,
partSpecifier=...) at ../../kmail/kmcommands.cpp:2735
#9  0xb75ce34d in KMLoadPartsCommand::qt_metacall (this=0xa644ff0,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfba2dc8) at
./kmcommands.moc:1858
#10 0xb707ead3 in QMetaObject::activate (sender=0xa5a0b00, from_signal_index=5,
to_signal_index=5, argv=0xbfba2dc8) at kernel/qobject.cpp:3112
#11 0xb707f722 in QMetaObject::activate (sender=0xa5a0b00, m=0xb79f04d0,
local_signal_index=1, argv=0xbfba2dc8) at kernel/qobject.cpp:3186
#12 0xb76233e9 in KMail::FolderJob::messageUpdated (this=0xa5a0b00,
_t1=0xa3e8088, _t2=...) at ./folderjob.moc:106
#13 0xb762fcbb in KMail::ImapJob::slotGetMessageResult (this=0xa5a0b00,
job=0xa6453d8) at ../../kmail/imapjob.cpp:476
#14 0xb763425c in KMail::ImapJob::qt_metacall (this=0xa5a0b00,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfba2f3c) at ./imapjob.moc:82
#15 0xb707ead3 in QMetaObject::activate (sender=0xa6453d8, from_signal_index=7,
to_signal_index=7, argv=0xbfba2f3c) at kernel/qobject.cpp:3112
#16 0xb707f722 in QMetaObject::activate (sender=0xa6453d8, m=0xb7c2efe8,
local_signal_index=3, argv=0xbfba2f3c) at kernel/qobject.cpp:3186
#17 0xb7ad4083 in KJob::result (this=0xa6453d8, _t1=0xa6453d8) at
./kjob.moc:188
#18 0xb7ad4529 in KJob::emitResult (this=0xa6453d8) at
../../kdecore/jobs/kjob.cpp:304
#19 0xb52e89e5 in KIO::SimpleJob::slotFinished (this=0xa6453d8) at
../../kio/kio/job.cpp:477
#20 0xb52e9343 in KIO::TransferJob::slotFinished (this=0xa6453d8) at
../../kio/kio/job.cpp:948
#21 0xb52e58d3 in KIO::TransferJob::qt_metacall (this=0xa6453d8,
_c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfba3178) at ./jobclasses.moc:343
#22 0xb707ead3 in QMetaObject::activate (sender=0xa278e80, from_signal_index=8,
to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112
#23 0xb707f722 in QMetaObject::activate (sender=0xa278e80, m=0xb548fb64,
local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186
#24 0xb53ae6d7 in KIO::SlaveInterface::finished (this=0xa278e80) at
./slaveinterface.moc:165
#25 0xb53b2487 in KIO::SlaveInterface::dispatch (this=0xa278e80, _cmd=104,
rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#26 0xb53aebb7 in KIO::SlaveInterface::dispatch (this=0xa278e80) at
../../kio/kio/slaveinterface.cpp:91
#27 0xb53a0b9d in KIO::Slave::gotInput (this=0xa278e80) at
../../kio/kio/slave.cpp:322
#28 0xb53a3083 in KIO::Slave::qt_metacall (this=0xa278e80,
_c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfba3448) at ./slave.moc:76
#29 0xb707ead3 in QMetaObject::activate (sender=0xa279210, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#30 0xb707f722 in QMetaObject::activate (sender=0xa279210, m=0xb548c4a0,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#31 0xb52ad427 in KIO::Connection::readyRead (this=0xa279210) at
./connection.moc:86
#32 0xb52aed33 in KIO::ConnectionPrivate::dequeue (this=0xa278608) at
../../kio/kio/connection.cpp:82
#33 0xb52af116 in KIO::Connection::qt_metacall (this=0xa279210,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xa671678) at ./connection.moc:73
#34 0xb70782db in QMetaCallEvent::placeMetaCall (this=0xa5b7128,
object=0xa279210) at kernel/qobject.cpp:477
#35 0xb7079db0 in QObject::event (this=0xa279210, e=0xa5b7128) at
kernel/qobject.cpp:1110
#36 0xb66a97d4 in QApplicationPrivate::notify_helper (this=0x9c7d830,
receiver=0xa279210, e=0xa5b7128) at kernel/qapplication.cpp:4056
#37 0xb66b193e in QApplication::notify (this=0xbfba3c78, receiver=0xa279210,
e=0xa5b7128) at kernel/qapplication.cpp:3603
#38 0xb7e0700d in KApplication::notify (this=0xbfba3c78, receiver=0xa279210,
event=0xa5b7128) at ../../kdeui/kernel/kapplication.cpp:302
#39 0xb706996b in QCoreApplication::

[Bug 204020] New: Images in icon view are tiny

[Mike Vaughn]

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

   Summary: Images in icon view are tiny
   Product: kaddressbook
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: NEW
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: contras...@gmail.com
CC: to...@kde.org


Version:(using KDE 4.3.0)
OS:Linux
Installed from:Ubuntu Packages

When using the icon view, the images are so small that they're virtually
useless.

-- 
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 204185] New: kmail crashes on exiting

[Mike Spark]

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

   Summary: kmail crashes on exiting
   Product: kmail
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: master.swa...@gmail.com


Application that crashed: kmail
Version of the application: 1.12.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-1-686 i686

What I was doing when the application crashed:
Sometimes kmail crashes just after exiting. No data is lost, just the crash
window appears.

 -- Backtrace:
Application: KMail (kmail), signal: Aborted
[KCrash Handler]
#6  0xb803e424 in __kernel_vsyscall ()
#7  0xb63853d0 in raise () from /lib/i686/cmov/libc.so.6
#8  0xb6388a85 in abort () from /lib/i686/cmov/libc.so.6
#9  0xb659f27f in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/libstdc++.so.6
#10 0xb659d1b5 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb659d1f2 in std::terminate() () from /usr/lib/libstdc++.so.6
#12 0xb659dea5 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6
#13 0xb76cb064 in KMail::ISubject::notify (this=0x951e4c0) at
../../kmail/isubject.cpp:29
#14 0xb737c7be in KMMessage::updateBodyPart (this=0x951e450, partSpecifier=...,
data=...) at ../../kmail/kmmessage.cpp:3196
#15 0xb769dd4f in KMail::ImapJob::slotGetMessageResult (this=0x9814668,
job=0x97e81e0) at ../../kmail/imapjob.cpp:435
#16 0xb76a225c in KMail::ImapJob::qt_metacall (this=0x9814668,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfa43a0c) at ./imapjob.moc:82
#17 0xb70ecad3 in QMetaObject::activate (sender=0x97e81e0, from_signal_index=7,
to_signal_index=7, argv=0xbfa43a0c) at kernel/qobject.cpp:3112
#18 0xb70ed722 in QMetaObject::activate (sender=0x97e81e0, m=0xb7c9cfe8,
local_signal_index=3, argv=0xbfa43a0c) at kernel/qobject.cpp:3186
#19 0xb7b42083 in KJob::result (this=0x97e81e0, _t1=0x97e81e0) at
./kjob.moc:188
#20 0xb7b42529 in KJob::emitResult (this=0x97e81e0) at
../../kdecore/jobs/kjob.cpp:304
#21 0xb53569e5 in KIO::SimpleJob::slotFinished (this=0x97e81e0) at
../../kio/kio/job.cpp:477
#22 0xb5357343 in KIO::TransferJob::slotFinished (this=0x97e81e0) at
../../kio/kio/job.cpp:948
#23 0xb53538d3 in KIO::TransferJob::qt_metacall (this=0x97e81e0,
_c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfa43c48) at ./jobclasses.moc:343
#24 0xb70ecad3 in QMetaObject::activate (sender=0x96e3b90, from_signal_index=8,
to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112
#25 0xb70ed722 in QMetaObject::activate (sender=0x96e3b90, m=0xb54fdb64,
local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186
#26 0xb541c6d7 in KIO::SlaveInterface::finished (this=0x96e3b90) at
./slaveinterface.moc:165
#27 0xb5420487 in KIO::SlaveInterface::dispatch (this=0x96e3b90, _cmd=104,
rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#28 0xb541cbb7 in KIO::SlaveInterface::dispatch (this=0x96e3b90) at
../../kio/kio/slaveinterface.cpp:91
#29 0xb540eb9d in KIO::Slave::gotInput (this=0x96e3b90) at
../../kio/kio/slave.cpp:322
#30 0xb5411083 in KIO::Slave::qt_metacall (this=0x96e3b90,
_c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfa43f18) at ./slave.moc:76
#31 0xb70ecad3 in QMetaObject::activate (sender=0x980ce48, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#32 0xb70ed722 in QMetaObject::activate (sender=0x980ce48, m=0xb54fa4a0,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#33 0xb531b427 in KIO::Connection::readyRead (this=0x980ce48) at
./connection.moc:86
#34 0xb531cd33 in KIO::ConnectionPrivate::dequeue (this=0x975f410) at
../../kio/kio/connection.cpp:82
#35 0xb531d116 in KIO::Connection::qt_metacall (this=0x980ce48,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x8ea53b8) at ./connection.moc:73
#36 0xb70e62db in QMetaCallEvent::placeMetaCall (this=0x9435d10,
object=0x980ce48) at kernel/qobject.cpp:477
#37 0xb70e7db0 in QObject::event (this=0x980ce48, e=0x9435d10) at
kernel/qobject.cpp:1110
#38 0xb67177d4 in QApplicationPrivate::notify_helper (this=0x8db3a98,
receiver=0x980ce48, e=0x9435d10) at kernel/qapplication.cpp:4056
#39 0xb671f93e in QApplication::notify (this=0xbfa44748, receiver=0x980ce48,
e=0x9435d10) at kernel/qapplication.cpp:3603
#40 0xb7e7500d in KApplication::notify (this=0xbfa44748, receiver=0x980ce48,
event=0x9435d10) at ../../kdeui/kernel/kapplication.cpp:302
#41 0xb70d796b in QCoreApplication::notifyInternal (this=0xbfa44748,
receiver=0x980ce48, event=0x9435d10) at kernel/qcoreapplication.cpp:610
#42 0xb70d85ae in QCoreApplication::sendEvent (receiver=0x0, event_type=0,
data=0x8d8ce60) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#43 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x8d8ce60) at kernel/qcoreapplication.cpp:1247
#44 0xb70d878d in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qc

[Bug 190938] "View Source" does not work on thread starter when thread is collapsed

[Mike Frysinger]

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





--- Comment #4 from Mike Frysinger   2009-08-17 22:45:00 ---
yes, 4.3.0 works for me while 4.2.4 was failing

-- 
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 190938] "View Source" does not work on thread starter when thread is collapsed

[Mike Frysinger]

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


Mike Frysinger  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED




-- 
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 150830] Enterprise headers sit on top of mail text if large desktop font is in use for accessibility reasons

[Mike Cohler]

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





--- Comment #5 from Mike Cohler   2009-08-30 21:31:40 ---
KDE has changed hugely in the intervening period - I think this is fine being
closed.

-- 
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 183875] kmail keeps spawning "gpgsm --server" but never kills/reaps them

[Mike Frysinger]

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





--- Comment #4 from Mike Frysinger   2009-09-03 15:53:49 ---
i dont have any gpgsm instances sticking around with kde-4.3.0, so perhaps
there is interaction with something else non-obvious here ...

-- 
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 212482] New: Make system tray icon ignore messages in spam folders

[Mike Vaughn]

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

   Summary: Make system tray icon ignore messages in spam folders
   Product: kmail
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: unspecified
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: contras...@gmail.com


Version:(using KDE 4.3.2)
Installed from:Ubuntu Packages

It would make the system tray icon a lot more useful if it could be configured
to only show a message count for folders in a user-selected set of folders. For
example, I have three GMail accounts set up on KMail, two of which get a new
spam message on almost every check. I'd like to be able to tell KMail to only
show the message count for my actual inbox folders on the system tray icon,
while disregarding the messages in the spam and trash folders. This would
probably best be implemented via a checkbox-based listview under Settings ->
Configure KMail -> Appearance -> System Tray, where the user could select which
folders' messages should be counted in the system tray icon.

-- 
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 212482] Make system tray icon ignore messages in spam folders

[Mike Vaughn]

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


Mike Vaughn  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||INVALID




--- Comment #2 from Mike Vaughn   2009-10-31 13:18:32 ---
Works perfect, thanks for the quick reply. Sorry for not poking around a bit
more before filing a report.

-- 
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 215376] New: (Wish) Import Contacts Photos

[Mike Welch]

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

   Summary: (Wish) Import Contacts Photos
   Product: kaddressbook
   Version: unspecified
  Platform: openSUSE RPMs
OS/Version: unspecified
Status: NEW
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: michael.a.we...@gmail.com
CC: to...@kde.org


Version:(using KDE 4.3.3)
Installed from:openSUSE RPMs

Would it be possible to import Contact pictures using KIPI plugins?
I'm not a programmer, but I'd love to have the ability to do this as long as it
didn't cause problems or affect performance.

-- 
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 215376] (Wish) Import Contacts Photos

[Mike Welch]

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


Mike Welch  changed:

   What|Removed |Added

 CC||michael.a.we...@gmail.com




-- 
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 212163] Send file on drag 'n drop

[Mike Welch]

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


Mike Welch  changed:

   What|Removed |Added

 CC||michael.a.we...@gmail.com




--- Comment #1 from Mike Welch   2009-11-21 04:13:17 
---
I like it!

-- 
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 217333] New: Kontact/KMail crash upon network disconnection when using IMAP4

[Mike Woźniak]

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

   Summary: Kontact/KMail crash upon network disconnection when
using IMAP4
   Product: kontact
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: miki...@yahoo.co.uk


Application that crashed: kontact
Version of the application: 4.3.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-15-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
When network connection is lost while being connected to an IMAP server,
Kontact/KMail displays error messages, and crashes directly after user discards
those messages.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x07e8709d in KIO::Slave::deref() () from /usr/lib/libkio.so.5
#7  0x07e87c46 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5
#8  0x07e8a033 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) ()
from /usr/lib/libkio.so.5
#9  0x06730263 in QMetaObject::activate(QObject*, int, int, void**) () from
/usr/lib/libQtCore.so.4
#10 0x06730ec2 in QMetaObject::activate(QObject*, QMetaObject const*, int,
void**) () from /usr/lib/libQtCore.so.4
#11 0x07d92057 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5
#12 0x07d93e1e in ?? () from /usr/lib/libkio.so.5
#13 0x07d93f4e in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**)
() from /usr/lib/libkio.so.5
#14 0x06728f0b in QMetaCallEvent::placeMetaCall(QObject*) () from
/usr/lib/libQtCore.so.4
#15 0x0672a5fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x00ab5f54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#17 0x00abd67c in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#18 0x0055a14a in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#19 0x0671a6cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from
/usr/lib/libQtCore.so.4
#20 0x0671b2b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
QThreadData*) () from /usr/lib/libQtCore.so.4
#21 0x0671b47d in QCoreApplication::sendPostedEvents(QObject*, int) () from
/usr/lib/libQtCore.so.4
#22 0x067453ff in ?? () from /usr/lib/libQtCore.so.4
#23 0x04744e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x04748720 in ?? () from /lib/libglib-2.0.so.0
#25 0x04748853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x0674502c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQtCore.so.4
#27 0x00b56be5 in ?? () from /usr/lib/libQtGui.so.4
#28 0x06718c79 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/libQtCore.so.4
#29 0x067190ca in QEventLoop::exec(QFlags) ()
from /usr/lib/libQtCore.so.4
#30 0x00fa2d53 in QDialog::exec() () from /usr/lib/libQtGui.so.4
#31 0x004d4534 in KMessageBox::createKMessageBox(KDialog*, QIcon const&,
QString const&, QStringList const&, QString const&, bool*,
QFlags, QString const&, QMessageBox::Icon) ()
   from /usr/lib/libkdeui.so.5
#32 0x004d591d in KMessageBox::createKMessageBox(KDialog*, QMessageBox::Icon,
QString const&, QStringList const&, QString const&, bool*,
QFlags, QString const&) ()
   from /usr/lib/libkdeui.so.5
#33 0x004d6f59 in KMessageBox::informationListWId(unsigned long, QString
const&, QStringList const&, QString const&, QString const&,
QFlags) () from /usr/lib/libkdeui.so.5
#34 0x004d70d6 in KMessageBox::informationList(QWidget*, QString const&,
QStringList const&, QString const&, QString const&,
QFlags) () from /usr/lib/libkdeui.so.5
#35 0x004d7138 in KMessageBox::information(QWidget*, QString const&, QString
const&, QString const&, QFlags) () from
/usr/lib/libkdeui.so.5
#36 0x04b0c5a0 in ?? () from /usr/lib/libkmailprivate.so.4
#37 0x04b06d73 in ?? () from /usr/lib/libkmailprivate.so.4
#38 0x04b0b6b2 in ?? () from /usr/lib/libkmailprivate.so.4
#39 0x04b0bbab in ?? () from /usr/lib/libkmailprivate.so.4
#40 0x04b1545a in ?? () from /usr/lib/libkmailprivate.so.4
#41 0x06730263 in QMetaObject::activate(QObject*, int, int, void**) () from
/usr/lib/libQtCore.so.4
#42 0x06730ec2 in QMetaObject::activate(QObject*, QMetaObject const*, int,
void**) () from /usr/lib/libQtCore.so.4
#43 0x078ebff3 in KJob::result(KJob*) () from /usr/lib/libkdecore.so.5
#44 0x078ec479 in KJob::emitResult() () from /usr/lib/libkdecore.so.5
#45 0x07dcb7b0 in KIO::SimpleJob::slotFinished() () from /usr/lib/libkio.so.5
#46 0x07dc9553 in KIO::SimpleJob::slotError(int, QString const&) () from
/usr/lib/libkio.so.5
#47 0x07dc969e in KIO::SimpleJob::qt_metacall(QMetaObject::Call, int, void**)
() from /usr/lib/libkio.so.5
#48 0x06730263 in QMetaObject::activate(QObject*, int, int, void**) () from
/usr/lib/libQtCore.so.4
#49 0x06730ec2 in QMetaObject::activate(QObject*,

[Bug 163071] Crash when deleting messages from inbox

[Mike Gager]

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


Mike Gager  changed:

   What|Removed |Added

 CC||tli...@gmail.com




--- Comment #116 from Mike Gager   2009-12-18 05:28:35 ---
Application that crashed: kontact
Version of the application: 4.3.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.27.41-170.2.117.fc10.x86_64 x86_64
Distribution: "Fedora release 10 (Cambridge)"

What I was doing when the application crashed:
It'll do it anytime I delete while a queue of deletes is still processing. 
Current workaround (when I remember) is to make another selection, wait for it
to display the currently selected message, when it gets to it, and then proceed
with the delete.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  QList () at /usr/include/QtCore/qlist.h:111
#6  KMail::FolderJob::msgList (this=0xff8a1b21ff642722) at
/usr/src/debug/kdepim-4.3.3/kmail/folderjob.cpp:120
#7  0x003d72a84735 in KMAcctImap::ignoreJobsForMessage (this=0x198cb70,
msg=0x5042330) at /usr/src/debug/kdepim-4.3.3/kmail/kmacctimap.cpp:215
#8  0x003d72ba3cd7 in KMMoveCommand::execute (this=0x2db1d40) at
/usr/src/debug/kdepim-4.3.3/kmail/kmcommands.cpp:2096
#9  0x003d72b89372 in KMCommand::slotPostTransfer (this=0x2db1d40,
result=KMCommand::OK) at /usr/src/debug/kdepim-4.3.3/kmail/kmcommands.cpp:275
#10 0x003d72b9336e in KMCommand::qt_metacall (this=0x2db1d40,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff7ad2b9d0)
at
/usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:87
#11 0x003d72ba5995 in KMMoveCommand::qt_metacall (this=0x7fff7ad2b580,
_c=4284753698, _id=79546736, _a=0x568a270) at
/usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:1706
#12 0x003d8f358662 in QMetaObject::activate (sender=0x2db1d40,
from_signal_index=, to_signal_index=4, argv=0x568a270) at
kernel/qobject.cpp:3112
#13 0x003d72b8654e in KMCommand::messagesTransfered (this=0x7fff7ad2b580,
_t1=KMCommand::OK) at
/usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:102
#14 0x003d72ba20c8 in KMCommand::transferSelectedMsgs (this=0x2db1d40) at
/usr/src/debug/kdepim-4.3.3/kmail/kmcommands.cpp:369
#15 0x003d72ba22f6 in KMCommand::slotStart (this=0x2db1d40) at
/usr/src/debug/kdepim-4.3.3/kmail/kmcommands.cpp:267
#16 0x003d72b93382 in KMCommand::qt_metacall (this=0x2db1d40,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff7ad2bc30)
at
/usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:86
#17 0x003d72ba5995 in KMMoveCommand::qt_metacall (this=0x7fff7ad2b580,
_c=4284753698, _id=79546736, _a=0x568a270) at
/usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:1706
#18 0x003d8f358662 in QMetaObject::activate (sender=0x2dc8010,
from_signal_index=, to_signal_index=4, argv=0x568a270) at
kernel/qobject.cpp:3112
#19 0x003d8f35e35f in QSingleShotTimer::timerEvent (this=0x2dc8010) at
kernel/qtimer.cpp:298
#20 0x003d8f353473 in QObject::event (this=0x2dc8010, e=0xff8a1b21ff642722)
at kernel/qobject.cpp:1074
#21 0x003d6919001d in QApplicationPrivate::notify_helper (this=0x699c70,
receiver=0x2dc8010, e=0x7fff7ad2c2f0) at kernel/qapplication.cpp:4065
#22 0x003d6919825a in QApplication::notify (this=0x7fff7ad2c640,
receiver=0x2dc8010, e=0x7fff7ad2c2f0) at kernel/qapplication.cpp:4030
#23 0x003d6b81351b in KApplication::notify (this=0x7fff7ad2c640,
receiver=0x2dc8010, event=0x7fff7ad2c2f0) at
/usr/src/debug/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#24 0x003d8f34378c in QCoreApplication::notifyInternal
(this=0x7fff7ad2c640, receiver=0x2dc8010, event=0x7fff7ad2c2f0) at
kernel/qcoreapplication.cpp:610
#25 0x003d8f370859 in QCoreApplication::sendEvent () at
kernel/qcoreapplication.h:213
#26 QTimerInfoList::activateTimers (this=0x695190) at
kernel/qeventdispatcher_unix.cpp:580
#27 0x003d8f36cd5d in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:165
#28 0x003099e377bb in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#29 0x003099e3af8d in ?? () from /lib64/libglib-2.0.so.0
#30 0x003099e3b14b in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#31 0x003d8f36ccbf in QEventDispatcherGlib::processEvents (this=0x66b0f0,
flags=) at kernel/qeventdispatcher_glib.cpp:327
#32 0x003d6922753f in QGuiEventDispatcherGlib::processEvents
(this=0x7fff7ad2b580, flags=) at
kernel/qguieventdispatcher_glib.cpp:202
#33 0x003d8f342022 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149
#34 0x003d8f3423f4 in QEventLoop::exec (this=0x7fff7ad2c5a0, flags=) at
kernel/qeventloop.cpp:201
#35 0x003d8f3446c4 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#36 0x004045f5 in mai

[Bug 135717] Deleting many maildir messages very slow

[Mike Frysinger]

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





--- Comment #12 from Mike Frysinger   2009-12-30 03:58:54 ---
are you sure this is a dupe ?  Bug 126793 seems like it's specific to IMAP and
how it hangs.  we've clearly diagnosed the problem here with maildir ... no one
has done that with IMAP.  the IMAP things looks more like a network latency
issue (and ive seen the same thing with IMAP accounts -- unlike my maildir
ones).

-- 
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 222878] kontact process does not exit after closing kontact window in every case

[Mike Vaughn]

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


Mike Vaughn  changed:

   What|Removed |Added

 CC||contras...@gmail.com




--- Comment #3 from Mike Vaughn   2010-01-31 15:54:42 ---
I just wanted to chime in and say I've been experiencing this same problem for
quite some time on Kubuntu, in both the 4.3 and new 4.4 branch. From what I can
tell, it occurs even when there are no lost connections to my IMAP accounts
(assuming there would be some error message informing me of such). It'd be
great to see this fixed soon; Kontact is one of my favorite applications to
show off to new users, but a bug like this presents quite a hurdle for most of
them. :-\

-- 
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 229060] Member information empty in contact groups

[Mike Reiche]

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





--- Comment #2 from Mike Reiche   2010-03-02 12:18:50 ---
Created an attachment (id=41257)
 --> (http://bugs.kde.org/attachment.cgi?id=41257)
4 screenshots that shows the "empty contact information" 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

[Bug 229060] Member information empty in contact groups

[Mike Reiche]

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





--- Comment #3 from Mike Reiche   2010-03-02 12:22:18 ---
This is not a duplicate of my other reported bug 228722.
The difference is, that the group members are available, but not the containing
information. Take a look at the attached screenshots.

It shows an example with a group of 4 members. I dont understand when the name
or emails are empty. It seems to be random. I had a group which was completely
empty.

-- 
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 182169] Option to disable folder panel tooltip

[Mike Frysinger]

http://bugs.kde.org/show_bug.cgi?id=182169





--- Comment #5 from Mike Frysinger   2009-02-06 22:30:11 ---
yep ... i'd also just remind that both tooltip in the folder tree and the
message list in the tabs are affected ... they currently seem to be a bit
independent of each other


-- 
Configure bugmail: http://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 132227] I can't send gpg signed email

[Mike Frysinger]

http://bugs.kde.org/show_bug.cgi?id=132227


Mike Frysinger vapier gentoo org changed:

   What|Removed |Added

 CC||vap...@gentoo.org




--- Comment #5 from Mike Frysinger   2009-02-10 02:39:13 ---
just because the agent is running doesnt mean the active env is sane.  in other
words, a gpg-agent session could be started by your login shell and so all
children inherit the env that points to that session.  if sometime later that
agent is killed and a new one is started, your kmail will still have the old
info.

the same situation might happen with stale env data and gpg-agent wasnt started
properly in the first place, or a different hierarchy.

you can double check this by doing something like:
$ strings /proc/$(pidof kmail)/environ | grep GPG
GPG_AGENT_INFO=/tmp/gpg-D0Refl/S.gpg-agent:30053:1

that second to last number will be the pid:
$ ps up 30053
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
vapier   30053  0.0  0.0  15344   568 ?Ss2008   1:01 gpg-agent
--daemon

if those things dont line up, then try quitting kmail, launching konsole,
checking GPG_AGENT_INFO is correct, then run `kmail` manually.


-- 
Configure bugmail: http://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 187575] New: right clicking in message window resets message list selection

[Mike Frysinger]

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

   Summary: right clicking in message window resets message list
selection
   Product: kmail
   Version: 1.11.1
  Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: vap...@gentoo.org


Version:   1.11.1 (using KDE 4.2.1)
Compiler:  gcc 4.3.3 x86_64
OS:Linux
Installed from:Gentoo Packages

if i select a couple of messages in the message list and then right click in
the message window, the selection in the message list is reset to only the
message i am currently viewing.  i wouldnt expect any mouse behavior like this
in the message window to affect the message list.  it's a pain if you select a
bunch of messages with the intent of deleting but notice a link in one you wish
to d/l before doing so ...

-- 
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 190938] New: "View Source" does not work on thread starter when thread is collapsed

[Mike Frysinger]

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

   Summary: "View Source" does not work on thread starter when
thread is collapsed
   Product: kmail
   Version: 1.11.2
  Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: vap...@gentoo.org


Version:   1.11.2 (using KDE 4.2.2)
Compiler:  gcc 4.3.3 x86_64
OS:Linux
Installed from:Gentoo Packages

with a simple thread like:
a
`-- b
`-- c

if the thread is collapsed at the thread starter ("a") and the "a" e-mail is
selected, then trying to view source on the e-mail "a" does not work (hitting
the V shortcut key).  if it's expanded, then it works fine.

the bug is only observed on the thread starter ... if messages under "b" are
collapsed, viewing the source on the "b" e-mail still works fine.

-- 
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 193066] New: Kontact crashed when I tried to apply new accounts, maybe wallet was involved?

[Mike Stoddart]

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



   Summary: Kontact crashed when I tried to apply new accounts,

maybe wallet was involved?

   Product: kontact

   Version: unspecified

  Platform: SuSE RPMs

OS/Version: Linux

Status: UNCONFIRMED

  Severity: normal

  Priority: NOR

 Component: general

AssignedTo: kdepim-bugs@kde.org

ReportedBy: sto...@gmail.com





Version:(using KDE 4.2.3)

OS:Linux

Installed from:SuSE RPMs



I had finished entering my POP and SMTP accounts and I applied the changes. The

wallet setup appeared so I chose basic and I said, yes store the password in

the wallet twice. At which point Kontact crashed.





This backtrace appears to be of no use.

This is probably because your packages are built in a way which prevents

creation of proper backtraces, or the stack frame was seriously corrupted in

the crash.



[?1034h(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

[Thread debugging using libthread_db enabled]

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

(no debugg

[Bug 193066] Kontact crashed when I tried to apply new accounts, maybe wallet was involved?

[Mike Stoddart]

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





--- Comment #1 from Mike Stoddart   2009-05-18 02:54:56 ---
It may have been related to the POP account settings - when I restarted
Kontact, the POP account was missing but the SMTP account was still there.

-- 
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 33670] add external plugin capability, scripted plugins as well as=

[Mike Frysinger]

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


Mike Frysinger  changed:

   What|Removed |Added

 CC||vap...@gentoo.org




-- 
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 122457] pop mail transfer hangs (sporadic)

[Mike Durian]

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





--- Comment #8 from Mike Durian   2009-07-14 
18:49:37 ---
No, I do not have to kill kio_pop3 anymore.  I do often have to exit kontact
and restart it when things get wedged, but I don't know if that condition is
related to this 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

[Bug 122457] pop mail transfer hangs (sporadic)

[Mike Durian]

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





--- Comment #9 from Mike Durian   2009-07-14 
18:51:31 ---
Sorry, jumped the gun with that last comment.  I'm using imap now, not pop3. 
So, I can't confirm this problem has gone away.

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

[Akonadi] [Bug 427021] Crash when reading mail with Mozilla Thunderbird

[Mike McCarthy]

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

Mike McCarthy  changed:

   What|Removed |Added

 CC||sy...@w1nr.net

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

[Akonadi] [Bug 427021] Crash when reading mail with Mozilla Thunderbird

[Mike McCarthy]

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

--- Comment #2 from Mike McCarthy  ---
Created attachment 132397
  --> https://bugs.kde.org/attachment.cgi?id=132397&action=edit
New crash information added by DrKonqi

akonadiserver (5.14.2 (20.04.2)) using Qt 5.12.7

- What I was doing when the application crashed:

Reading mail with Thuinderbird. OpenSUSE Virtualbox VM running on Windows 10
host.

-- Backtrace (Reduced):
#5  0x56250689222b in QHash::findNode
(this=this@entry=0x562507be6288, akey=..., ahp=ahp@entry=0x0) at
/usr/include/qt5/QtCore/qhash.h:934
#6  0x56250689289a in QHash::remove
(this=this@entry=0x562507be6288, akey=...) at
/usr/include/qt5/QtCore/qhash.h:806
#7  0x56250688f8ef in
Akonadi::Server::ItemRetrievalManager::retrievalJobFinished
(this=0x562507be6250, request=0x7f25c80c5490, errorMsg=...) at
/usr/src/debug/akonadi-server-20.04.2-lp152.2.3.1.x86_64/src/server/storage/itemretrievalmanager.cpp:179
[...]
#9  0x5625068e07e4 in
Akonadi::Server::AbstractItemRetrievalJob::requestCompleted
(this=this@entry=0x7f25c8b40340, _t1=, _t2=...) at
/usr/src/debug/akonadi-server-20.04.2-lp152.2.3.1.x86_64/build/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:135
#10 0x56250689306e in Akonadi::Server::ItemRetrievalJob::callFinished
(this=0x7f25c8b40340, watcher=) at
/usr/src/debug/akonadi-server-20.04.2-lp152.2.3.1.x86_64/src/server/storage/itemretrievaljob.cpp:76

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

[Akonadi] [Bug 421077] Akonadi crashes after almost any boot

[Mike McCarthy]

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

--- Comment #2 from Mike McCarthy  ---
Created attachment 132907
  --> https://bugs.kde.org/attachment.cgi?id=132907&action=edit
New crash information added by DrKonqi

akonadiserver (5.14.2 (20.04.2)) using Qt 5.12.7

- What I was doing when the application crashed:

Just logged in. Running in Virtualbox on Windows 10 host.

-- Backtrace (Reduced):
#4  _mm_crc32_u64 (__V=, __C=) at
/usr/lib64/gcc/x86_64-suse-linux/7/include/smmintrin.h:848
#5  crc32 (ptr=0xfe69d8714ca8, len=, h=)
at tools/qhash.cpp:112
#6  0x7f355bc48914 in hash (seed=, len=,
p=) at tools/qhash.cpp:223
#7  qHash (key=..., seed=) at tools/qhash.cpp:239
#8  0x5650e742f22b in QHash::findNode
(this=this@entry=0x5650e80ae108, akey=..., ahp=ahp@entry=0x0) at
/usr/include/qt5/QtCore/qhash.h:934

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

[Akonadi] [Bug 421077] Akonadi crashes after almost any boot

[Mike McCarthy]

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

Mike McCarthy  changed:

   What|Removed |Added

 CC||sy...@w1nr.net

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

[Akonadi] [Bug 443435] New: Kmail crash and repeated offline accessing gmail imap

[Mike Burke]

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

Bug ID: 443435
   Summary: Kmail crash and repeated offline accessing gmail imap
   Product: Akonadi
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: kdepim-bugs@kde.org
  Reporter: geekwork...@gmail.com
  Target Milestone: ---

Application: akonadi_imap_resource (5.18.1 (21.08.1))

Qt Version: 5.15.3
Frameworks Version: 5.86.0
Operating System: Linux 5.11.0-37-generic x86_64
Windowing System: X11
Drkonqi Version: 5.22.5
Distribution: KDE neon User Edition 5.22

-- Information about the crash:
- What I was doing when the application crashed:
The akondi imap resource keeps going offline and reporting segmentation faults
when trying to read mail or click around in Imap folders. Server is Google
Apps/Gmail.

The crash can be reproduced every time.

-- Backtrace:
Application: Work (akonadi_imap_resource), signal: Segmentation fault

[New LWP 3848]
[New LWP 3849]
[New LWP 3850]
[New LWP 3852]
[New LWP 5078]
[New LWP 5632]
[New LWP 6844]
[New LWP 7621]
[New LWP 9306]
[New LWP 10070]
[New LWP 10891]
[New LWP 11840]
[New LWP 12639]
[New LWP 13752]
[New LWP 14679]
[New LWP 15124]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f6c05c28aff in __GI___poll (fds=0x7ffd8f4c0278, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7f6c016089c0 (LWP 3847))]

Thread 17 (Thread 0x7f6bc4ff9700 (LWP 15124)):
#0  0x7f6c05c28aff in __GI___poll (fds=0x7f6bac010fe0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f6c04fb136e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6c04fb14a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6c062115eb in QEventDispatcherGlib::processEvents
(this=0x7f6bac025580, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f6c061b587b in QEventLoop::exec (this=this@entry=0x7f6bc4ff8be0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f6c05fcf292 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f6c05fd042c in QThreadPrivate::start (arg=0x561082b54690) at
thread/qthread_unix.cpp:329
#7  0x7f6c04e9f609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f6c05c35293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7f6bc7fff700 (LWP 14679)):
#0  0x7f6c04fb0b33 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f6c04fb12e8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6c04fb14a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6c062115eb in QEventDispatcherGlib::processEvents
(this=0x7f6bc0005980, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f6c061b587b in QEventLoop::exec (this=this@entry=0x7f6bc7ffebe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f6c05fcf292 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f6c05fd042c in QThreadPrivate::start (arg=0x56108239f7f0) at
thread/qthread_unix.cpp:329
#7  0x7f6c04e9f609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f6c05c35293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f6bc67fc700 (LWP 13752)):
#0  __GI___libc_read (nbytes=16, buf=0x7f6bc67fb9d0, fd=26) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=26, buf=0x7f6bc67fb9d0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f6c04ff9b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6c04fb0ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6c04fb1312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f6c04fb14a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f6c062115eb in QEventDispatcherGlib::processEvents
(this=0x7f6bb0177030, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f6c061b587b in QEventLoop::exec (this=this@entry=0x7f6bc67fbbe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#8  0x7f6c05fcf292 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#9  0x7f6c05fd042c in QThreadPrivate::start (arg=0x561082798e80) at
thread/qthread_unix.cpp:329
#10 0x7f6c04e9f609 in start_thread (arg=) at
pthread_create.c:477
#11 0x7f6c05c35293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f6be97fa700 (LWP 12639)):
#0  0x7f6c05c28aff in __GI___poll (fds

[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"

[Mike Booth]

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

Mike Booth  changed:

   What|Removed |Added

 CC||mikeboot...@gmail.com

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 459551] New: Oauth2 failure on connecting google groupware

[Mike Benson]

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

Bug ID: 459551
   Summary: Oauth2 failure on connecting google groupware
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Google Resource
  Assignee: dvra...@kde.org
  Reporter: m...@kambe.com.au
CC: kdepim-bugs@kde.org
  Target Milestone: ---

SUMMARY
The Oauth2 process fails trying to access a Google Workspace account

STEPS TO REPRODUCE
1. Go to akonadiconsole
2. On the Agents tab, click "+ Add"
3. Select "Google Groupware" in the presented dialog, and click "OK"
4. Account is "not configured". Click "Configure"
5. A browser tab opens, requesting a Google Account Sign in (in my case, in
firefox).
6. Choose the account
7. A permissions request page appears, choose "Allow"

OBSERVED RESULT
A new web page appears, with the text 
"Something went wrong
Sorry, something went wrong there. Please try again."
Clicking "Next" results in the same page appearing.

EXPECTED RESULT
The auth token is returned to Akonadi googleresource.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux 
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.5
Kernel version 5.19.9 (64 bit)

ADDITIONAL INFORMATION

Note that my gmail imap resource for this google account continues to work, and
Google drive for this account will open in Dolphin (WITHOUT any oauth dialogs)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[korganizer] [Bug 460197] KOrganizer 22.08.1 crashes when trying to create a new event

[Mike Booth]

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

Mike Booth  changed:

   What|Removed |Added

 CC||mikeboot...@gmail.com
   Platform|Archlinux   |Slackware
Version|unspecified |5.21.2

--- Comment #2 from Mike Booth  ---
also the same on Slackware 15. No sync with Google Calendar either

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

[Akonadi] [Bug 421077] Akonadi crashes after almost any boot

[Mike McCarthy]

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

Mike McCarthy  changed:

   What|Removed |Added

 CC||m...@w1nr.net

--- Comment #4 from Mike McCarthy  ---
I do not see this behavior any more since I upgraded to OpenSUSE Leap 15.4
(latest).

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

[kmail2] [Bug 335759] New: kmail crashes on startup due to files in autosave/

[Mike Frysinger]

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

Bug ID: 335759
   Summary: kmail crashes on startup due to files in autosave/
Classification: Unclassified
   Product: kmail2
   Version: 4.13.1
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: vap...@gentoo.org

when writing an e-mail, kmail crashed.  now when i try to start it, it crashes
every time.  i have to delete ~/.kde4/share/apps/kmail2/autosave/ in order to
get it to start up.

Reproducible: Always

Steps to Reproduce:
1. download attached archive
2. unpack it into ~/.kde4/share/apps/kmail2/autosave/
3. start kmail



Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  QTimer::start (this=0x7fff7fff) at kernel/qtimer.cpp:215
#7  0x7f1bcc3d4fd1 in KMComposeWin::slotCloseAttachMissingFile
(this=) at
/var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1/kmail/editor/kmcomposewin.cpp:3524
#8  0x7f1bcc40ebf5 in KMComposeWin::qt_static_metacall (_o=,
_id=, _a=, _c=) at
/var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1_build/kmail/moc_kmcomposewin.cpp:302
#9  0x7f1bc70ff358 in QMetaObject::activate (sender=0x24301a0, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3547
#10 0x7f1bc70ff358 in QMetaObject::activate (sender=sender@entry=0x2431040,
m=m@entry=0x7f1bc2a59020
,
local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at
kernel/qobject.cpp:3547
#11 0x7f1bc279f7b3 in
MessageComposer::AttachmentControllerBase::fileAttached
(this=this@entry=0x2431040) at
/var/tmp/portage/kde-base/kdepim-common-libs-4.13.1/work/kdepim-common-libs-4.13.1_build/messagecomposer/moc_attachmentcontrollerbase.cpp:245
#12 0x7f1bc279f89e in
MessageComposer::AttachmentControllerBase::addAttachment (this=0x2431040,
part=...) at
/var/tmp/portage/kde-base/kdepim-common-libs-4.13.1/work/kdepim-common-libs-4.13.1/messagecomposer/attachment/attachmentcontrollerbase.cpp:813
#13 0x7f1bc27c0a72 in MessageComposer::ComposerViewBase::addAttachmentPart
(this=this@entry=0x2292e50, partToAttach=) at
/var/tmp/portage/kde-base/kdepim-common-libs-4.13.1/work/kdepim-common-libs-4.13.1/messagecomposer/composer/composerviewbase.cpp:1215
#14 0x7f1bc27d084b in MessageComposer::ComposerViewBase::setMessage
(this=0x2292e50, msg=...) at
/var/tmp/portage/kde-base/kdepim-common-libs-4.13.1/work/kdepim-common-libs-4.13.1/messagecomposer/composer/composerviewbase.cpp:176
#15 0x7f1bcc3e3d18 in KMComposeWin::setMessage (this=0x22769d0, newMsg=...,
lastSignState=, lastEncryptState=,
mayAutoSign=, allowDecryption=, isModified=false)
at
/var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1/kmail/editor/kmcomposewin.cpp:1600
#16 0x7f1bcc30d1ed in KMKernel::recoverDeadLetters
(this=this@entry=0x7fffc95de320) at
/var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1/kmail/kmkernel.cpp:1132
#17 0x00402f78 in main (argc=, argv=) at
/var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1/kmail/main.cpp:136

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

[kmail2] [Bug 335759] kmail crashes on startup due to files in autosave/

[Mike Frysinger]

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

--- Comment #1 from Mike Frysinger  ---
Created attachment 86996
  --> https://bugs.kde.org/attachment.cgi?id=86996&action=edit
files in autosave/

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

[Akonadi] [Bug 333514] Maildir items are never expired from Akonadi cache because of Baloo

[Mike Woźniak]

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

Mike Woźniak  changed:

   What|Removed |Added

 CC||rys...@fwioo.pl

--- Comment #9 from Mike Woźniak  ---
Currently I have ~6GiB of e-mail, ~10GiB of Akonadi cache, ~4GiB of Baloo
cache.
 I have *MORE THAN TWICE* as much disk space used for cache as for e-mail
itself. This is absurd.

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

[Akonadi] [Bug 338203] New: Akonadi ignores DAV link changes

[Mike Woźniak]

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

Bug ID: 338203
   Summary: Akonadi ignores DAV link changes
   Product: Akonadi
   Version: 1.12.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: rys...@fwioo.pl

Upon changing the DAV link, Akonadi shows the new link in the GUI, but if there
are events added to the calendar between the last sync and the link change, it
still tries to use the old link (and inevitably fails).

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

[kmail2] [Bug 327122] Kmail keeps on displaying a "NO No item found" message box.

[Mike Frysinger]

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

Mike Frysinger  changed:

   What|Removed |Added

 CC||vap...@gentoo.org

--- Comment #1 from Mike Frysinger  ---
i see this semi-often in Gentoo.  i don't recall the first version i saw it
with, but it's survived upgrades.

current version is 4.13.3.

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

[kmail2] [Bug 340312] New: Attachments are not encrypted when "automatic encryption" is selected

[Mike Schneider]

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

Bug ID: 340312
   Summary: Attachments are not encrypted when "automatic
encryption" is selected
   Product: kmail2
   Version: 4.11.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: mike2.schnei...@gmail.com

When composing a new message, selecting "encrypt message" will cause
attachments to be also encrypted. This is the correct, expected behavior.

However, if encryption is not manually selected and a message comprising
attachments is sent AND the option "automatic encryption" ("Nachrichten
möglichst automatisch verschlüsseln")is selected and the key of the receiver is
known, a pop-up is displayed, asking whether you want to encrypt the mail. This
is also correct.

HOWEVER: if you select yes, kmail will only encrypt the message body, not the
attachments and will send out the unencrypted attachment without asking further
questions.

Expected behaviour: attachments are also encrypted

Reproducible: Always

Steps to Reproduce:
1. In the settings, under security, select "automatic encryption" ("Nachrichten
möglichst automatisch verschlüsseln")
2. Compose a mail to a sender having a known gpg key
3. Attach a file to the message
4. send the massage, when asked whether you want to encrypt the message, select
yes

Actual Results:  
Message body will be encrypted, attachment will be sent in clear , defeating
the purpose of sending encrypted mails

Expected Results:  
Message body ant attachments are encrypted

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

[Akonadi] [Bug 245218] akonadi uses a lot of hard disk space Platform Version 4.5.60 (KDE 4.5.60 (KDE 4.6 >= 20100627)) "release 3"

[Mike Woźniak]

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

Mike Woźniak  changed:

   What|Removed |Added

 CC||rys...@fwioo.pl

--- Comment #6 from Mike Woźniak  ---
Problem still exists here on KDE 4.13.0.

~/.local/share/akonadi$ du -csh *
4,0Kakonadi_control.error
4,0Kcur
1,8Gdb_data
4,0Kdb_misc
2,7Gfile_db_data
4,0Kmysql.conf
4,0Knew
0   socket-lapuntu
4,0Ktmp
4,5Gtotal

Total size of all mailboxes is ~7GiB. Plus, baloo email cache (or whatever it
is) eats up additional 2.5GiB.

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

[kmail2] [Bug 332228] When displaying HTML mails, KMail loads external references before asking the user for permission

[Mike Schneider]

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

Mike Schneider  changed:

   What|Removed |Added

Version|4.11.5  |4.14.4

--- Comment #1 from Mike Schneider  ---
Problem is reproducable with kmail 4.14.4

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

[kmail2] [Bug 300142] Kmail can't render a html signature

[Mike Jones]

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

Mike Jones  changed:

   What|Removed |Added

 CC||dr.mike.jo...@gmail.com

--- Comment #14 from Mike Jones  ---
(In reply to Pierre Maraval from comment #12)
> Same problem on Kubuntu 13.10, Kmail Version 4.11.5.
> 
> Another aspect of this bug (I think) is that Kmail doesn't digitally sign
> the html signature correctly (HTML signature with "inline" images
> (data:image/gif;base64) ).  
> 
> So the sent signed email is invalid, even for other clients which otherwise
> can render html signatures in Kmail-sent mails.

Re Pierre's data:image additional point.

I can confirm that (for kde 4.10.5 and kde 4.13.3) the addition of images via
the  to an html signature causes s/mime signing to record
an incorrect digest.  I notice that when the mail is sent the saved/received
mail has its html image elements converted to https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 300142] Kmail can't render a html signature

[Mike Jones]

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

--- Comment #15 from Mike Jones  ---
(In reply to Mike Jones from comment #14)
> (In reply to Pierre Maraval from comment #12)
> > Same problem on Kubuntu 13.10, Kmail Version 4.11.5.
> > 
> > Another aspect of this bug (I think) is that Kmail doesn't digitally sign
> > the html signature correctly (HTML signature with "inline" images
> > (data:image/gif;base64) ).  
> > 
> > So the sent signed email is invalid, even for other clients which otherwise
> > can render html signatures in Kmail-sent mails.
> 
> Re Pierre's data:image additional point.
> 
> I can confirm that (for kde 4.10.5 and kde 4.13.3) the addition of images
> via the  to an html signature causes s/mime signing to
> record an incorrect digest.  I notice that when the mail is sent the
> saved/received mail has its html image elements converted to  src="cid:...> which are I believe generated on the fly. My best guess is
> that perhaps kmail reformats the html after the digest is calculated
> rendering it void.
> 
> To test this I have created two identity profiles the only difference being
> their name and whether the html signature contains img data block or not. 
> The result is that after signing the email with the images in the signature
> (both saved locally and sent over the wire) result in a red message box and
> "Status: Bad signature"; whereas emails sent without images render in a
> green box and verify correctly.

Additionally Adding a vcard (generated via kmail which inserts \r\n as per spec
IIRC).  There may also be an issue with either kmail or MS exchange (though I
doubt MS would want to remove it's precious carriage return character) 
replacing \r with \n resulting in \n\n substitution for \r\n, and hence voiding
the digest again.

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

[Akonadi] [Bug 348319] Akonadi IMAP crash

[Mike Hammond]

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

--- Comment #2 from Mike Hammond  ---
Created attachment 94188
  --> https://bugs.kde.org/attachment.cgi?id=94188&action=edit
New crash information added by DrKonqi

akonadi_imap_resource (4.14) on KDE Platform 4.14.6 using Qt 4.8.6

- What I was doing when the application crashed:

Nothing related.  I was ssh'd into another machine checking progress of
backups.

-- Backtrace (Reduced):
#6  0x7f879aec2f9d in QByteArray (a=..., this=0x7ffcd479e780) at
/usr/include/qt4/QtCore/qbytearray.h:439
#7  toString (this=0x0) at ../../kimap/message_p.h:42
#8  KIMAP::SearchJob::handleResponse (this=, response=...) at
../../kimap/searchjob.cpp:429
#9  0x7f879aeb3fbb in KIMAP::SessionPrivate::responseReceived
(this=0x1e55b80, response=...) at ../../kimap/session.cpp:300
#10 0x7f879d2d88e1 in QObject::event (this=0x1e55b80, e=) at
kernel/qobject.cpp:1222

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

[Akonadi] [Bug 348319] Akonadi IMAP crash

[Mike Hammond]

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

Mike Hammond  changed:

   What|Removed |Added

 CC||kor...@koranzen.net

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

[kmail2] [Bug 402364] New: Unclear error dialog with actual error message shadowed in background

[Mike Krutov]

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

Bug ID: 402364
   Summary: Unclear error dialog with actual error message
shadowed in background
   Product: kmail2
   Version: 5.9.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: nekoxmach...@gmail.com
  Target Milestone: ---

SUMMARY
Akonadi protocol mismatch results in "The email program encountered a fatal
error and will terminate now" dialog. This dialog blocks actual error message,
displayed in KMail window. 

STEPS TO REPRODUCE
1. Update. Don't restart Akonadi server yet.
2. Restart KMail
3. Observe

OBSERVED RESULT
As described, actual error message isn't vieweable.

EXPECTED RESULT
Dialog should contain erorr message instead of just saying "Fatal error".


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION

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

[kmail2] [Bug 385033] New: Kmail fails to start (unknown condition)

[Mike Goodwin]

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

Bug ID: 385033
   Summary: Kmail fails to start (unknown condition)
   Product: kmail2
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: m...@mgoodwin.net
  Target Milestone: ---

Application: kmail (5.5.1)

Qt Version: 5.7.1
Frameworks Version: 5.36.0
Operating System: Linux 4.12.13-300.fc26.x86_64 x86_64
Distribution: "Fedora release 26 (Twenty Six)"

-- Information about the crash:
This happens when I attempt to start kmail from the application menu, and
immediately a drkonqi window appears.

Using Fedora 26

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f91f7e9d940 (LWP 25117))]

Thread 21 (Thread 0x7f9196ffd700 (LWP 25148)):
#0  0x7f91f96df89c in srb_callback () at
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#1  0x7f91f96e011f in srbchannel_rwloop () at
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#2  0x7f91fb5ca7f8 in pa_mainloop_dispatch () at /lib64/libpulse.so.0
#3  0x7f91fb5cabce in pa_mainloop_iterate () at /lib64/libpulse.so.0
#4  0x7f91fb5cac50 in pa_mainloop_run () at /lib64/libpulse.so.0
#5  0x7f91fb5d8ab9 in thread () at /lib64/libpulse.so.0
#6  0x7f91f96f0078 in internal_thread_func () at
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#7  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#8  0x7f921a328bbf in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f91977fe700 (LWP 25147)):
#0  0x7f921627fe0a in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f920da58172 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f920da1f38e in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#3  0x7f920d9f9fab in
base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f920d9f6828 in base::MessageLoop::RunHandler() () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f920da1326b in base::RunLoop::Run() () at
/lib64/libQt5WebEngineCore.so.5
#6  0x7f920da2af66 in base::Thread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#7  0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#8  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#9  0x7f921a328bbf in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f9197fff700 (LWP 25146)):
#0  0x7f921627f90b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f920e1a7ea0 in cc::SingleThreadTaskGraphRunner::Run() () at
/lib64/libQt5WebEngineCore.so.5
#2  0x7f920da2a9a1 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#5  0x7f921a328bbf in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f91ad7fa700 (LWP 25145)):
#0  0x7f921627f90b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f920da29725 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f920da29c07 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f920da2a9a1 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#6  0x7f921a328bbf in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f91acff9700 (LWP 25144)):
#0  0x7f921627f90b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f920da1f409 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f920da1f437 in base::WaitableEvent::Wait() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f920d9f9f5b in
base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f920d9f6828 in base::MessageLoop::RunHandler() () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f920da1326b in base::RunLoop::Run() () at
/lib64/libQt5WebEngineCore.so.5
#6  0x7f920da2af66 in base::Thread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#7  0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#8  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#9  0x7f921

[akregator] [Bug 329530] Akregator produces multiple and distracting/disturbing certificate errors, including when it is only open in tray.

[Mike Morris]

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

Mike Morris  changed:

   What|Removed |Added

 CC||mikro...@gmail.com

--- Comment #5 from Mike Morris  ---
This looks a lot like the bug I came here to log... Cerificate error
notifications should not IMHO be a modal popup (whatever the korrect term might
be these days) - especially when Akregator is docked in the tray.

More appropriate behaviour would be a systray notification that does not
require user interaction to dismiss.

This is still how it works in 5.2.3, so can we REOPEN this as a bug/enhancement
as I am confirming it for Framework-based Akregator.

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

[korganizer] [Bug 386496] New: Crash closing KOrganizer with todo filter active

[Mike Nix]

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

Bug ID: 386496
   Summary: Crash closing KOrganizer with todo filter active
   Product: korganizer
   Version: unspecified
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kde-a...@wanm.com.au
  Target Milestone: ---

Application: korganizer (4.14.10)
KDE Platform Version: 4.14.36
Qt Version: 4.8.7
Operating System: Linux 4.9.52 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
Closing KOrganizer with a TODO filter active.  The filter hides completed tasks
7 days after completion. (some completed tasks are being hidden, some are not,
and there are un-completed tasks).
The filter works correctly, but if it is active KOrganizer crashes when closed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f368b7e9b70 in QAbstractSlider::maximum() const () at
/usr/lib64/qt/lib/libQtGui.so.4
#7  0x7f368d4ed86d in  () at /usr/lib64/libkdeui.so.5
#8  0x7f368c572e61 in QObject::event(QEvent*) () at
/usr/lib64/qt/lib/libQtCore.so.4
#9  0x7f368b439fac in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtGui.so.4
#10 0x7f368b440d04 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#11 0x7f368d51c0aa in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#12 0x7f368c559ffe in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtCore.so.4
#13 0x7f368c55ce92 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/qt/lib/libQtCore.so.4
#14 0x7f368c58816e in  () at /usr/lib64/qt/lib/libQtCore.so.4
#15 0x7f3681f86467 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#16 0x7f3681f86678 in  () at /usr/lib64/libglib-2.0.so.0
#17 0x7f3681f866fc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#18 0x7f368c5882d6 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/qt/lib/libQtCore.so.4
#19 0x7f368b4dce87 in  () at /usr/lib64/qt/lib/libQtGui.so.4
#20 0x7f368c5586e4 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#21 0x7f368c5589f6 in
QEventLoop::exec(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#22 0x7f368c55e08c in QCoreApplication::exec() () at
/usr/lib64/qt/lib/libQtCore.so.4
#23 0x00408317 in  ()
#24 0x7f368a59302a in __libc_start_main () at /lib64/libc.so.6
#25 0x004087ca in _start ()

Reported using DrKonqi

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

[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Mike Goodwin]

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

Mike Goodwin  changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

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

[kmail2] [Bug 391165] New: [FEATURE REQUEST] markdown support

[Mike Harris]

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

Bug ID: 391165
   Summary: [FEATURE REQUEST] markdown support
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mike.a.har...@outlook.com
  Target Milestone: ---

This is a feature request.

The ability to write in markdown and have it sent formatted as html

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

[kmail2] [Bug 391165] [FEATURE REQUEST] markdown support

[Mike Harris]

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

--- Comment #2 from Mike Harris  ---
The ability to write markdown emails and when sent converted to html.

You can write html in a message but not for something like embedding code into
an email with syntax highlighting like markdown uses `` for code.

Currently the only way to write is either html or rich text.

Adding markdown for composing would be very beneficial.

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

[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28

[Mike Eichler]

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

Mike Eichler  changed:

   What|Removed |Added

Version|4.11.2  |5.7.2
   Platform|Debian unstable |Neon Packages
 CC||m...@mykolab.ch

--- Comment #28 from Mike Eichler  ---
There are  a few articles with that date stuck at the top of article list in
akregator.

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

[kmail2] [Bug 392977] New: Threading from with same subject but different sender shows in wrong thread

[Mike Harris]

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

Bug ID: 392977
   Summary: Threading from with same subject but different sender
shows in wrong thread
   Product: kmail2
   Version: 5.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-bugs@kde.org
  Reporter: mike.a.har...@outlook.com
  Target Milestone: ---

In the inbox if an email has the same subject but different sender it shows in
the thread of the wrong sender.

It should be it's own separate thread not added to the thread of a different
person

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

[kmail2] [Bug 392977] Threading from with same subject but different sender shows in wrong thread

[Mike Harris]

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

--- Comment #1 from Mike Harris  ---
Created attachment 112016
  --> https://bugs.kde.org/attachment.cgi?id=112016&action=edit
These senders are two different email threads that shouldn't be grouped

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

[kmail2] [Bug 393185] New: When user has 2 gmail accounts one using smtp.gmail.com and smtp.googlemail.com and sending from the smtp.googlemail.com it always sends it from the smtp.gmail.com even when

[Mike Harris]

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

Bug ID: 393185
   Summary: When user has 2 gmail accounts one using
smtp.gmail.com and smtp.googlemail.com and sending
from the smtp.googlemail.com it always sends it from
the smtp.gmail.com even when sending from
smtp.googlemail.com
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mike.a.har...@outlook.com
  Target Milestone: ---

Steps to reproduce:
Create 2 gmail accounts
1 account uses the standard imap.gmail.com and smtp.gmail.com
2nd account uses imap.googlemail.com and smtp.googlemail.com

both have separate identities to their respective account.

Send a message using the smtp.googlemail.com 

result: sends from smtp.gmail.com even though everything is listed from the
smtp.googlemail.com account

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

[kmail2] [Bug 393185] When user has 2 gmail accounts one using smtp.gmail.com and smtp.googlemail.com and sending from the smtp.googlemail.com it always sends it from the smtp.gmail.com even when send

[Mike Harris]

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

Mike Harris  changed:

   What|Removed |Added

Summary|When user has 2 gmail   |When user has 2 gmail
   |accounts one using  |accounts one using
   |smtp.gmail.com and  |smtp.gmail.com and
   |smtp.googlemail.com and |smtp.googlemail.com and
   |sending from the|sending from the
   |smtp.googlemail.com it  |smtp.googlemail.com it
   |always sends it from the|always sends it from the
   |smtp.gmail.com even when|smtp.gmail.com even when
   |sending from|sending from
   |smtp.googlemail.com |smtp.googlemail.com email
   ||address

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

[kmail2] [Bug 393185] When user has 2 different gmail accounts one using smtp.gmail.com and smtp.googlemail.com and sending from the smtp.googlemail.com it always sends it from the smtp.gmail.com even

[Mike Harris]

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

Mike Harris  changed:

   What|Removed |Added

Summary|When user has 2 gmail   |When user has 2 different
   |accounts one using  |gmail accounts one using
   |smtp.gmail.com and  |smtp.gmail.com and
   |smtp.googlemail.com and |smtp.googlemail.com and
   |sending from the|sending from the
   |smtp.googlemail.com it  |smtp.googlemail.com it
   |always sends it from the|always sends it from the
   |smtp.gmail.com even when|smtp.gmail.com even when
   |sending from|sending from
   |smtp.googlemail.com email   |smtp.googlemail.com email
   |address |address

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

[Akonadi] [Bug 393328] New: stuck on 100%, email doesn't sync

[Mike Eichler]

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

Bug ID: 393328
   Summary: stuck on 100%, email doesn't sync
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: m...@mykolab.ch
CC: kdepim-bugs@kde.org
  Target Milestone: ---

about once every day, my gmail account stops syncing. Akonadi console shows
"100%" for that resource.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[kmail2] [Bug 393185] When user has 2 different gmail accounts one using smtp.gmail.com and smtp.googlemail.com and sending from the smtp.googlemail.com it always sends it from the smtp.gmail.com even

[Mike Harris]

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

Mike Harris  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

[Mike Pagano]

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

Mike Pagano  changed:

   What|Removed |Added

 CC||mpag...@gentoo.org

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

[Akonadi] [Bug 427021] Crash when reading mail with Mozilla Thunderbird

[Mike McCarthy]

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

--- Comment #1 from Mike McCarthy  ---
Created attachment 131957
  --> https://bugs.kde.org/attachment.cgi?id=131957&action=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[Akonadi] [Bug 427021] New: Crash when reading mail with Mozilla Thunderbird

[Mike McCarthy]

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

Bug ID: 427021
   Summary: Crash when reading mail with Mozilla Thunderbird
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: sy...@w1nr.net
  Target Milestone: ---

Application: akonadiserver (5.14.2 (20.04.2))

Qt Version: 5.12.7
Frameworks Version: 5.71.0
Operating System: Linux 5.3.18-lp152.41-default x86_64
Windowing system: X11
Distribution: "openSUSE Leap 15.2"

-- Information about the crash:
Running openSUSE 15.2 in Virtualbox. Crashes repeatedly when invoking Mozilla
Thunderbird when mailbox contains large number of emails.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  0x7f4a51e359fc in std::__atomic_base::load
(__m=std::memory_order_relaxed, this=0x0) at
/usr/include/c++/7/bits/atomic_base.h:396
#5  QAtomicOps::load (_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
#6  QBasicAtomicInteger::load (this=0x0) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103
[...]
#8  QString::operator= (this=this@entry=0x7f49f08fdf78, other=...) at
tools/qstring.cpp:2417
#9  0x564ed1dac8d5 in
Akonadi::Server::ItemRetrievalManager::retrievalJobFinished
(this=0x564ed3610070, request=0x7f49f08fdf60, errorMsg=...) at
/usr/src/debug/akonadi-server-20.04.2-lp152.2.3.1.x86_64/src/server/storage/itemretrievalmanager.cpp:176


The reporter indicates this bug may be a duplicate of or related to bug 409515.

Possible duplicates by query: bug 425931, bug 425842, bug 425340, bug 425205,
bug 423579.

Reported using DrKonqi

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

[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.

[Mike Goodwin]

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

--- Comment #8 from Mike Goodwin  ---
I still have this bug I just don't login to this bug tracker very often, and I
worked around it so I stopped being annoyed by it. 

If you configure an IDLE account and disable "Interval mail checking" it
basically stops working after it times out, and doesn't reconnect the IDLE
session. 

Thus, I have interval mail checking set at about 20 minutes and that seems to
mostly work ok.

However, My phone using K9 _always_ receives mail instantly via IDLE (because I
can hear the alert) and it takes a substantial amount of time for Kmail to show
the same notification on my computer (both of mine) 

I'm pretty sure most of the time It's just waiting the 20 minutes to check of
I'm between checking intervals, so IDLE is probably doing nothing for me still.

I'd be willing to work with anyone but I'm not sure where else to progress the
bug on my own. I clearly have a configuration and server that is prone to this
issue, but again other clients like K9 work flawlessly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.

[Mike Goodwin]

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

--- Comment #9 from Mike Goodwin  ---
By the way I'm on:

Plasma 5.8.5
kf5 5.29
kdepim 16.08

And will continue to be on the latest of what rdieter is doing with Fedora 25+

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[korganizer] [Bug 379676] New: calendar manager

[Mike Lewis]

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

Bug ID: 379676
   Summary: calendar manager
   Product: korganizer
   Version: 5.1.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: otherviews
  Assignee: kdepim-bugs@kde.org
  Reporter: mle...@wrrc.us
  Target Milestone: ---

Created attachment 105425
  --> https://bugs.kde.org/attachment.cgi?id=105425&action=edit
Screen shot showing calendar manager illegible text.

On Mint v18.1 MATE, text in Calendar Manager is displayed incorrectly, to the
point it is illegible. See example screen-shot with Calendar Manager in lower
left corner of window.

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

[kmail2] [Bug 382204] New: Certain Base64-encoded HTML messages cause composer to hit 100% CPU when attempting to reply

[Mike Ely]

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

Bug ID: 382204
   Summary: Certain Base64-encoded HTML messages cause composer to
hit 100% CPU when attempting to reply
   Product: kmail2
   Version: 4.14.10
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-bugs@kde.org
  Reporter: kdeb...@taupehat.com
  Target Milestone: ---

I'm trying to work out how to clean out confidential information from an
example message while still including one that will cause the bug. In the
meantime, the messages all come from our Veeam Backup and Replication server,
so if anyone has access to one of those it should be easy enough to reproduce
the bug. Just hit "Reply" to any message generated from same.

If anyone has advice on how to submit sufficient data to reproduce this bug
while scrubbing confidential info I'm more than willing to do so.

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