[trojita] [Bug 396332] New: Segfault when moving a thread when new messages arrive into the same thread

[Jan Kundrát]

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

Bug ID: 396332
   Summary: Segfault when moving a thread when new messages arrive
into the same thread
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Core
  Assignee: trojita-b...@kde.org
  Reporter: j...@kde.org
  Target Milestone: ---

I started dragging a thread and one standalone unthreaded message; I was going
to move them to another mailbox. Another message arrived in the meanwhile. That
message was going to become a part of that existing thread that I was dragging.
Here's a backtrace. There was no assert crash, just a segfault:

(gdb) bt
#0  0x7feb49c2f30d in QSortFilterProxyModel::parent (this=0x27a3790,
child=...) at
/var/tmp/portage/dev-qt/qtcore-5.11./work/qtcore-5.11./src/corelib/itemmodels/qsortfilterproxymodel.cpp:1999
#1  0x004c6273 in Gui::MsgListView::startDrag(QFlags)
()
#2  0x7feb4ab4f24c in QAbstractItemView::mouseMoveEvent(QMouseEvent*) () at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/itemviews/qabstractitemview.cpp:1836
#3  0x7feb4abb8233 in QTreeView::mouseMoveEvent (this=0x26a5b00,
event=0x7ffc030a5a80) at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/itemviews/qtreeview.cpp:1989
#4  0x7feb4a93ec48 in QWidget::event (this=this@entry=0x26a5b00,
event=event@entry=0x7ffc030a5a80) at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/kernel/qwidget.cpp:8916
#5  0x7feb4a9e0b3e in QFrame::event (this=0x26a5b00, e=0x7ffc030a5a80) at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/widgets/qframe.cpp:550
#6  0x7feb4ab4fb9b in QAbstractItemView::viewportEvent
(this=this@entry=0x26a5b00, event=event@entry=0x7ffc030a5a80)
at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/itemviews/qabstractitemview.cpp:1748
#7  0x7feb4abb798b in QTreeView::viewportEvent (this=0x26a5b00,
event=0x7ffc030a5a80) at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/itemviews/qtreeview.cpp:1326
#8  0x7feb49c5375e in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/var/tmp/portage/dev-qt/qtcore-5.11./work/qtcore-5.11./src/corelib/kernel/qcoreapplication.cpp:1174
#9  0x7feb4a900f41 in QApplicationPrivate::notify_helper
(this=this@entry=0x258ff50, receiver=receiver@entry=0x26a61e0,
e=e@entry=0x7ffc030a5a80)
at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/kernel/qapplication.cpp:3721
#10 0x7feb4a9086e7 in QApplication::notify(QObject*, QEvent*) () at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/kernel/qapplication.cpp:3201
#11 0x7feb49c53911 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at
/var/tmp/portage/dev-qt/qtcore-5.11./work/qtcore-5.11./src/corelib/kernel/qcoreapplication.cpp:1048
#12 0x7feb4a907a20 in QCoreApplication::sendEvent (event=,
receiver=) at
../../include/QtCore/../../../qtwidgets-5.11./src/corelib/kernel/qcoreapplication.h:234
#13 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x26a61e0,
event=event@entry=0x7ffc030a5a80, alienWidget=alienWidget@entry=0x26a61e0,
nativeWidget=0x7ffc030a62a0, 
buttonDown=buttonDown@entry=0x7feb4aff2390 ,
lastMouseReceiver=..., spontaneous=true) at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/kernel/qapplication.cpp:2693
#14 0x7feb4a9592f8 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/kernel/qwidgetwindow.cpp:659
#15 0x7feb4a95bc50 in QWidgetWindow::event (this=0x27726f0,
event=0x7ffc030a5e60) at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/kernel/qwidgetwindow.cpp:281
#16 0x7feb4a900f51 in QApplicationPrivate::notify_helper
(this=this@entry=0x258ff50, receiver=receiver@entry=0x27726f0,
e=e@entry=0x7ffc030a5e60)
at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/kernel/qapplication.cpp:3725
#17 0x7feb4a9084a0 in QApplication::notify(QObject*, QEvent*) () at
/var/tmp/portage/dev-qt/qtwidgets-5.11./work/qtwidgets-5.11./src/widgets/kernel/qapplication.cpp:3484
#18 0x7feb49c53911 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at
/var/tmp/portage/dev-qt/qtcore-5.11./work/qtcore-5.11./src/corelib/kernel/qcoreapplication.cpp:1048
#19 0x7feb4a1dca44 in QCoreApplication::sendSpontaneousEvent
(event=0x7ffc030a5e60, receiver=0x27726f0) at
../../include/QtCore/../../../qtgui-5.11./src/corelib/kernel/qcoreapplication.h:237
#20 

[trojita] [Bug 391718] ASSERT: "it != ptrToInternal.constEnd()" in file trojita/src/Imap/Model/ThreadingMsgListModel.cpp, line 1488

[Jan Kundrát]

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

Jan Kundrát  changed:

   What|Removed |Added

Summary|Trojita hangs in infinite   |ASSERT: "it !=
   |loop|ptrToInternal.constEnd()"
   ||in file
   ||trojita/src/Imap/Model/Thre
   ||adingMsgListModel.cpp, line
   ||1488
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Jan Kundrát  ---
(a duplicate bug led me here, so I think that this is a correct report)

1) activate threading
2) open a mailbox
3) perform a search which returns something
4) switch to another mailbox where that search doesn't return anything
5) the threading is still preserved, and trojita assert-crashes:

ASSERT: "it != ptrToInternal.constEnd()" in file
trojita/src/Imap/Model/ThreadingMsgListModel.cpp, line 1488

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 331782] Cannot send a mail with empty subject field

[Jan Kundrát]

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

--- Comment #8 from Jan Kundrát  ---
BTW, I am all for improving the usability of this. The subject field can get
red-highlighted if empty upon a sending attempt, for example. The error dialog
could prompt for subject, or at least move the focus there, etc. Patches
welcome (via Gerrit, please).

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 396114] Allow sending mails without subject

[Jan Kundrát]

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

Jan Kundrát  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Jan Kundrát  ---
Thanks for your feedback. This is actually by design. We are not aware of a use
case for sending e-mails with an empty subject.

Technical reason: It breaks some e-mail threading algorithms.

Opinion: There are certain patterns in e-mail usage which we like and
"encourage" Trojita's users to follow. Writing e-mails with a subject is one of
them. In my opinion, it's a good "etiquette" to provide a very short summary on
what that e-mail is all about. Having usable subjects is something which makes
navigation through thousands of e-mails more doable. Yup, everybody can just
click that dialog away and enter "info" into the subject, but at least there's
a reminder there.

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

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 331782] Cannot send a mail with empty subject field

[Jan Kundrát]

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

Jan Kundrát  changed:

   What|Removed |Added

 CC||tobias.leup...@gmx.de

--- Comment #7 from Jan Kundrát  ---
*** Bug 396114 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 354394] Add $Submitted and $SubmitPending keywords as appropriate

[Jan Kundrát]

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

--- Comment #3 from Jan Kundrát  ---
*** Bug 396112 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 396112] Sent emails are added to the sent folder even if the sending failed

[Jan Kundrát]

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

Jan Kundrát  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Jan Kundrát  ---
Let's track this in the original bug.

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

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 396112] Sent emails are added to the sent folder even if the sending failed

[Jan Kundrát]

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

Jan Kundrát  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Version|unspecified |0.7
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Jan Kundrát  ---
For technical reasons (BURL), it is actually needed to save the mail before it
gets submitted via SMTP. There's a standard for saving a message *and*
indicating that it's still pending submission. We currently do not implement
that (see bug 354394).

(Added v0.7, thanks.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 394664] "hide unread messages": marking threaded messages as read causes the whole thread to disappear

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
patch: https://gerrit.vesnicky.cesnet.cz/r/1003

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 394664] New: "hide unread messages": marking threaded messages as read causes the whole thread to disappear

[Jan Kundrát]

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

Bug ID: 394664
   Summary: "hide unread messages": marking threaded messages as
read causes the whole thread to disappear
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Core
  Assignee: trojita-b...@kde.org
  Reporter: j...@kde.org
  Target Milestone: ---

As reported by caster on IRC:

- activate threading
- activate an option to only show unread messages
- find a thread which is unread except for just one deepest message
- mark it as unread
- boom, an entire thread disappears

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391667] EFAIL: leak of the plaintext of encrypted emails

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

Summary|Security bug|EFAIL: leak of the
   ||plaintext of encrypted
   ||emails

--- Comment #7 from Jan Kundrát <j...@kde.org> ---
This appears to have gone public now. Technical details are available in the
paper [1]. Trojita is listed as vulnerable (page 20) for two classes of
exfiltration scenarios:

- I3: "CRL requests to a fixed CA URL are performed for valid/trusted S/MIME
signed emails"

- H3, which is about the DNS prefetch control: http://efail.de;>

The I3 is outside of control of Trojita. We are using the libgpgme library for
all crypto operations, including the CRL handling. We do not issue any
cert/CRL/key/... requests directly. Once gpgme is fixed, Trojita will be fixed,
too.

The H3 has been reported in bug 390452, and that's upstream
https://bugreports.qt.io/browse/QTBUG-67068 . Our code has always included
explicit disabling of the DNS prefetch for QtWebKit; unfortunately, due to a
bug in upstream qtwebkit, this does not take any effect. We *could* try to
mitigate the problem by mangling the HTML code, trying to insert an explicit
 element which disables this DNS prefetch. However, these attempts tend
to be error-prone because there are many ways on how to re-enable various
features in HTML renderers.

There are other attacks as well. The user is still presented with a button to
enable remote content when displaying encrypted e-mails. That should probably
be disabled in order to make sure that the plaintext content won't leak by
accident.

[1] https://efail.de/efail-attack-paper.pdf

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 392800] New: ASSERT: "m_root.isValid()" in file src/Cryptography/MessagePart.cpp, line 188

[Jan Kundrát]

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

Bug ID: 392800
   Summary: ASSERT: "m_root.isValid()" in file
src/Cryptography/MessagePart.cpp, line 188
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Cryptography
  Assignee: trojita-b...@kde.org
  Reporter: j...@kde.org
  Target Milestone: ---

This apparently happened during a resume cycle:

(gdb) bt
#0  0x7ff0d62be21b in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x7ff0d62bf8b1 in __GI_abort () at abort.c:89
#2  0x7ff0d701a99e in qt_message_fatal (context=..., message=...)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qlogging.cpp:1690
#3  QMessageLogger::fatal (this=this@entry=0x7fff92d751d0,
msg=msg@entry=0x7ff0d72df038 "ASSERT: \"%s\" in file %s, line %d")
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qlogging.cpp:796
#4  0x7ff0d7014c45 in qt_assert (assertion=, file=, line=)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qglobal.cpp:3077
#5  0x00535e50 in
QtPrivate::QFunctorSlotObject::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
#6  0x7ff0d7246505 in QtPrivate::QSlotObjectBase::call (a=0x7fff92d75370,
r=0x1ea9a10, this=0x303b760)
at
../../include/QtCore/../../../qtcore-5.9./src/corelib/kernel/qobject_impl.h:101
#7  QMetaObject::activate (sender=sender@entry=0x1ab5a00,
signalOffset=, local_signal_index=local_signal_index@entry=10,
argv=argv@entry=0x7fff92d75370)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qobject.cpp:3749
#8  0x7ff0d7246aa5 in QMetaObject::activate (sender=sender@entry=0x1ab5a00,
m=m@entry=0x7ff0d7474540 , 
local_signal_index=local_signal_index@entry=10,
argv=argv@entry=0x7fff92d75370)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qobject.cpp:3628
#9  0x7ff0d71b7ccc in QAbstractItemModel::rowsInserted
(this=this@entry=0x1ab5a00, _t1=..., _t2=1, _t3=11, _t4=...) at
.moc/moc_qabstractitemmodel.cpp:603
#10 0x7ff0d71c102c in QAbstractItemModel::endInsertRows (this=0x1ab5a00)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/itemmodels/qabstractitemmodel.cpp:2709
#11 0x005c18b2 in
Imap::Mailbox::Model::replaceChildMailboxes(Imap::Mailbox::TreeItemMailbox*,
QVector const&) ()
#12 0x005c0f03 in Imap::Mailbox::Model::finalizeList(Imap::Parser*,
Imap::Mailbox::TreeItemMailbox*) ()
#13 0x0061116e in
Imap::Mailbox::ListChildMailboxesTask::handleStateHelper(Imap::Responses::State
const*) ()
#14 0x005bd545 in
Imap::Mailbox::Model::responseReceived(QMap::iterator) ()
#15 0x7ff0d72474da in QObject::event (this=0x1ab5a00, e=)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qobject.cpp:1246
#16 0x7ff0d7b03d54 in QApplicationPrivate::notify_helper (this=, receiver=0x1ab5a00, e=0x26e4d80)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qapplication.cpp:3722
#17 0x7ff0d7b0c4a2 in QApplication::notify (this=0x7fff92d75d90,
receiver=0x1ab5a00, e=0x26e4d80)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qapplication.cpp:3481
#18 0x7ff0d7216078 in QCoreApplication::notifyInternal2
(receiver=0x1ab5a00, event=event@entry=0x26e4d80)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qcoreapplication.cpp:1018
#19 0x7ff0d7219237 in QCoreApplication::sendEvent (event=0x26e4d80,
receiver=)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qcoreapplication.h:233
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x18b87b0)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qcoreapplication.cpp:1678
#21 0x7ff0d721980e in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qcoreapplication.cpp:1532
#22 0x7ff0d7273369 in postEventSourceDispatch (s=0x1917300)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qeventdispatcher_glib.cpp:276
#23 0x7ff0d186c80c in g_main_dispatch (context=0x7ff0c40016f0) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3154
#24 g_main_context_dispatch 

[trojita] [Bug 392522] New: ASSERT: "index.isValid()" in file /home/jkt/work/prog/trojita/src/Composer/ComposerAttachments.cpp, line 448

[Jan Kundrát]

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

Bug ID: 392522
   Summary: ASSERT: "index.isValid()" in file
/home/jkt/work/prog/trojita/src/Composer/ComposerAttac
hments.cpp, line 448
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Message Composer
  Assignee: trojita-b...@kde.org
  Reporter: j...@kde.org
  Target Milestone: ---

1) compose mail
2) attach a part from an IMAP message
3) send, but let an error interrupt sending during APPEND
4) go offline and back online
5) pwned:

#0  0x7f9ece00b21b in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x7f9ece00c8b1 in __GI_abort () at abort.c:89
#2  0x7f9eced6799e in qt_message_fatal (context=..., message=...)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qlogging.cpp:1690
#3  QMessageLogger::fatal (this=this@entry=0x7ffd59e61380,
msg=msg@entry=0x7f9ecf02c038 "ASSERT: \"%s\" in file %s, line %d")
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qlogging.cpp:796
#4  0x7f9eced61c45 in qt_assert (assertion=, file=, line=)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qglobal.cpp:3077
#5  0x0052f81a in Composer::ImapPartAttachmentItem::imapUrl() const ()
#6  0x0052ecc9 in Composer::ImapPartAttachmentItem::caption() const ()
#7  0x00511c38 in Composer::MessageComposer::data(QModelIndex const&,
int) const ()
#8  0x7f9ecfb38a99 in QModelIndex::data (arole=0, this=0x3137c08)
at
../../include/QtCore/../../../qtwidgets-5.9./src/corelib/itemmodels/qabstractitemmodel.h:432
#9  QStyledItemDelegate::initStyleOption (this=0x202ce40,
option=0x7ffd59e615c0, index=...)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/itemviews/qstyleditemdelegate.cpp:345
#10 0x7f9ecfb37a1a in QStyledItemDelegate::sizeHint (this=0x202ce40,
option=..., index=...)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/itemviews/qstyleditemdelegate.cpp:410
#11 0x7f9ecfb52249 in QListViewPrivate::itemSize (this=0x23df890,
option=..., index=...)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/itemviews/qlistview.cpp:1784
#12 0x7f9ecfb5255b in QCommonListViewBase::itemSize (this=0x2fd7410,
idx=..., opt=...)
at
../../include/QtWidgets/5.9.2/QtWidgets/private/../../../../../../qtwidgets-5.9./src/widgets/itemviews/qlistview_p.h:465
#13 QListModeViewBase::indexToListViewItem (this=0x2fd7410, index=...)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/itemviews/qlistview.cpp:2358
#14 0x7f9ecfb552a3 in QListViewPrivate::indexToListViewItem
(this=0x23df890, index=...)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/itemviews/qlistview.cpp:1729
#15 0x7f9ecfb564f8 in QListViewPrivate::rectForIndex (index=...,
this=0x23df890)
at
../../include/QtWidgets/5.9.2/QtWidgets/private/../../../../../../qtwidgets-5.9./src/widgets/itemviews/qlistview_p.h:341
#16 QListView::rectForIndex (this=, index=...)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/itemviews/qlistview.cpp:1223
#17 0x7f9ecfb565b0 in QListView::visualRect (this=,
index=...)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/itemviews/qlistview.cpp:558
#18 0x7f9ecfb52f97 in QListView::paintEvent (this=0x2d5b130, e=)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/itemviews/qlistview.cpp:987
#19 0x7f9ecf89ca60 in QWidget::event (this=this@entry=0x2d5b130,
event=event@entry=0x7ffd59e62090)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qwidget.cpp:9198
#20 0x7f9ecf959891 in QFrame::event (this=0x2d5b130, e=0x7ffd59e62090)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/widgets/qframe.cpp:550
#21 0x7f9ecfb17df3 in QAbstractItemView::viewportEvent (this=0x2d5b130,
event=0x7ffd59e62090)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/itemviews/qabstractitemview.cpp:1748
#22 0x7f9ecef62d26 in
QCoreApplicationPrivate::sendThroughObjectEventFilters
(receiver=receiver@entry=0x1f88b40, event=event@entry=0x7ffd59e62090)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qcoreapplication.cpp:1129
#23 0x7f9ecf850d1a in QApplicationPrivate::notify_helper (this=, receiver=0x1f88b40, e=0x7ffd59e62090)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qapplication.cpp:3718
#24 0x7f9ecf8594a2 in 

[trojita] [Bug 391710] Trojita crash when searching: ASSERT: "it != ptrToInternal.constEnd()" in file src/Imap/Model/ThreadingMsgListModel.cpp, line 1476

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

Summary|Trojita crash when  |Trojita crash when
   |searching   |searching: ASSERT: "it !=
   ||ptrToInternal.constEnd()"
   ||in file
   ||src/Imap/Model/ThreadingMsg
   ||ListModel.cpp, line 1476

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391710] Trojita crash when searching

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 CC||j...@kde.org

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
*** Bug 392182 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 392182] ASSERT: "it != ptrToInternal.constEnd()" in file src/Imap/Model/ThreadingMsgListModel.cpp, line 1476

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
Gah.

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

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 392182] ASSERT: "it != ptrToInternal.constEnd()" in file src/Imap/Model/ThreadingMsgListModel.cpp, line 1476

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
This BT might be incorrect because I rebuilt between capturing the core dump
and invoking `coredumpctl gdb`. But anyway, it looks plausible:

#0  0x7fbf8581421b in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x7fbf858158b1 in __GI_abort () at abort.c:89
#2  0x7fbf8657099e in qt_message_fatal (context=..., message=...)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qlogging.cpp:1690
#3  QMessageLogger::fatal (this=this@entry=0x7ffe913ed2f0,
msg=msg@entry=0x7fbf86835038 "ASSERT: \"%s\" in file %s, line %d")
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qlogging.cpp:796
#4  0x7fbf8656ac45 in qt_assert (assertion=, file=, line=)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qglobal.cpp:3077
#5  0x005ede33 in Imap::Mailbox::ThreadingMsgListModel::applySort() ()
#6  0x005e7869 in
Imap::Mailbox::ThreadingMsgListModel::searchSortPreferenceImplementation(QStringList
const&, Imap::Mailbox::ThreadingMsgListModel::SortCriterium, Qt::SortOrder) ()
#7  0x005e9074 in
Imap::Mailbox::ThreadingMsgListModel::applyThreading(QVector
const&) ()
#8  0x005e3732 in
Imap::Mailbox::ThreadingMsgListModel::wantThreading(Imap::Mailbox::ThreadingMsgListModel::SkipSortSearch)
()
#9  0x0046f450 in Gui::MainWindow::slotThreadMsgList() ()
#10 0x7fbf8679c505 in QtPrivate::QSlotObjectBase::call (a=0x7ffe913ed960,
r=0x7ffe913efaa0, this=0x1787eb0)
at
../../include/QtCore/../../../qtcore-5.9./src/corelib/kernel/qobject_impl.h:101
#11 QMetaObject::activate (sender=sender@entry=0x16bb220,
signalOffset=, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffe913ed960)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qobject.cpp:3749
#12 0x7fbf8679caa5 in QMetaObject::activate (sender=sender@entry=0x16bb220,
m=m@entry=0x7fbf875de880 , 
local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffe913ed960)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qobject.cpp:3628
#13 0x7fbf870513cf in QAction::triggered (this=this@entry=0x16bb220,
_t1=true) at .moc/moc_qaction.cpp:371
#14 0x7fbf87054b3c in QAction::activate (this=this@entry=0x16bb220,
event=event@entry=QAction::Trigger)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qaction.cpp:1163
#15 0x7fbf87219fd2 in QMenuPrivate::activateCausedStack
(this=this@entry=0x1681170, causedStack=..., action=action@entry=0x16bb220, 
action_e=action_e@entry=QAction::Trigger, self=self@entry=true)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/widgets/qmenu.cpp:1324
#16 0x7fbf8722107a in QMenuPrivate::activateAction
(this=this@entry=0x1681170, action=action@entry=0x16bb220,
action_e=action_e@entry=QAction::Trigger, 
self=self@entry=true) at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/widgets/qmenu.cpp:1401
#17 0x7fbf872221fa in QMenu::mouseReleaseEvent (this=,
e=0x7ffe913ee050)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/widgets/qmenu.cpp:2889
#18 0x7fbf870a5a60 in QWidget::event (this=this@entry=0x16b9e20,
event=event@entry=0x7ffe913ee050)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qwidget.cpp:9198
#19 0x7fbf87224693 in QMenu::event (this=0x16b9e20, e=0x7ffe913ee050)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/widgets/qmenu.cpp:3011
#20 0x7fbf87059d54 in QApplicationPrivate::notify_helper (this=, receiver=0x16b9e20, e=0x7ffe913ee050)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qapplication.cpp:3722
#21 0x7fbf87062e2f in QApplication::notify (this=,
receiver=0x16b9e20, e=0x7ffe913ee050)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qapplication.cpp:3198
#22 0x7fbf8676c078 in QCoreApplication::notifyInternal2
(receiver=receiver@entry=0x16b9e20, event=event@entry=0x7ffe913ee050)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qcoreapplication.cpp:1018
#23 0x7fbf870616ee in QCoreApplication::sendEvent (event=,
receiver=)
at
../../include/QtCore/../../../qtwidgets-5.9./src/corelib/kernel/qcoreapplication.h:233
#24 QApplicationPrivate::sendMouse

[trojita] [Bug 392182] New: ASSERT: "it != ptrToInternal.constEnd()" in file src/Imap/Model/ThreadingMsgListModel.cpp, line 1476

[Jan Kundrát]

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

Bug ID: 392182
   Summary: ASSERT: "it != ptrToInternal.constEnd()" in file
src/Imap/Model/ThreadingMsgListModel.cpp, line 1476
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Core
  Assignee: trojita-b...@kde.org
  Reporter: j...@kde.org
  Target Milestone: ---

I got this while switching between mailboxes with threading and searching being
active, or perhaps deactivating one of them, or perhaps changing the search
criteria:

ASSERT: "it != ptrToInternal.constEnd()" in file
src/Imap/Model/ThreadingMsgListModel.cpp, line 1476

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391667] Security bug

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from Jan Kundrát <j...@kde.org> ---
I got a description of the possible bug by an encrypted e-mail -- thanks for
that. Thomas, Caspar, Erik, Stephan, Pali -- if you're interested in it and if
you're OK with keeping it confidential per Damian's terms, please reply here
with your GPG key fingerprint and I'll share the information.

I'm very busy with real life at the time, so please allow for longer responses
than usual.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391382] Trojita with watchFolders=all or watchFolders=subscribed crash

[Jan Kundrát]

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

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
It looks like there's a race between the time the mailboxes get re-created in
response to LIST, and the time CALL_LATER takes effect. I however don't
understand how it's possible that I cannot reproduce this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391727] Trojita crashed when idling in INBOX

[Jan Kundrát]

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

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
Can you please measure this with some heap profiler so that we know where the
leak is?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391710] Trojita crash when searching

[Jan Kundrát]

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

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
This might have something to do with that latest change wihch enabled SORT and
THREAD to co-exist, which is kind of a hack.

Can you please attach a complete IMAP log of this one?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391718] Trojita hangs in infinite loop

[Jan Kundrát]

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

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
If this is indeed an infinite loop, there's at least one cycle in the
`threading` map. It would be nice to have access to the raw IMAP log. Without
that log, I cannot really do anything.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 390452] HTML Backchannel in Trojitá Mail Client: DNS Prefetching

[Jan Kundrát]

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

--- Comment #9 from Jan Kundrát <j...@kde.org> ---
Caspar, did you have luck reporting this bug to the Qt upstream?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391667] Security bug

[Jan Kundrát]

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

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
(In reply to Damian Poddebniak from comment #0)
> Hello, I'd like to discuss a security problem, but we don't want to make it
> public right now. Can this issue be set to confidential?

Hi, I don't know how to do that with our Bugzilla instance (and my permission
level). A best course of action is probably mailing me directly (j...@kde.org,
GPG key 94612A6CBDDA8C7F5095BEB31B364DA3AAD4170A).

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391382] Trojita with watchFolders=all or watchFolders=subscribed crash

[Jan Kundrát]

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

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Strange -- I cannot reproduce that. Can you please:

- ensure that you have debugging symbols and that Q_ASSERT are not being
compiled out,
- tell me what your cache settings are,
- tell me the connection method you use,
- specify your version of Qt?

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 373178] Blurry scaling on HiDPI

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 CC|j...@kde.org |

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391239] Don't pass #4: test_Html_formatting on openSUSE Tumbleweed (libpng warning: iCCP: known incorrect sRGB profile)

[Jan Kundrát]

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

--- Comment #5 from Jan Kundrát <j...@kde.org> ---
(In reply to Илья Индиго from comment #3)
> Created attachment 10 [details]
> Screenshot

Yes, that's a breakage of QtWebKit as shipped by your distribution. Please ask
them to have https://github.com/annulen/webkit/issues/511 applied, and if you
see any other bugs, please open a new bugreport for each of them.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 358680] sort order not saved when not threaded

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from Jan Kundrát <j...@kde.org> ---
> (seriously, no one wants to sort new mails to the bottom)

That's incorrect, "people have always wanted that" :).

Anyway, patches which make Trojita remember the search order are welcome.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 391239] Don't pass #4: test_Html_formatting on openSUSE Tumbleweed (libpng warning: iCCP: known incorrect sRGB profile)

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
That means that QtWebKit is broken on Tumbleweed. Please report that against
your distribution, asking them to fix their QtWebKit packaging. The warning
message from libpng doesn't appear to be relevant, though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 390452] HTML Backchannel in Trojitá Mail Client: DNS Prefetching

[Jan Kundrát]

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

--- Comment #8 from Jan Kundrát <j...@kde.org> ---
> Does anyone have a better approach?

Patch QtWebKit and send that patch upstream, please. This is clearly their bug.

> Otherwise the behavior seems intended. You can configure the default 
> behavior, but the webpage has the last word on this.

Which looks like a reasonable behavior for a web browser to my eyes untrained
on today's browsers' safety, but it's definitely a wrong behavior for a
reusable component.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 390452] HTML Backchannel in Trojitá Mail Client: DNS Prefetching

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Hi Jens, thanks a lot for this test. We understand that this is indeed a
problem -- thanks for letting us know.

We're relying on the Qt framework's packaging of WebKit for HTML rendering. Can
you please specify which Qt version and on which platform did you use in this
test? The upstream situation with QtWebKit is, well, complicated, so this is an
important piece of information for us. Please note that there are at least two
implementations of "QtWebKit", one based on the official repositories and the
other based on [1]. Some Linux distributions have switched to using this other
WebKit.

It's documented [2] that DNS prefetching should be disabled by default in the
official (and obsolete) Qt module. I also checked the code in latest upstream's
git, and in there that attribute also defaults to false. We have so far relied
on these effects (and some ad-hoc manual checks which were done at design &
implementation time) to ensure that we don't leak these data. Too bad that it
apparently fails now.

[1] https://github.com/annulen/webkit
[2] http://doc.qt.io/archives/qt-5.5/qwebsettings.html#WebAttribute-enum

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 332914] Threading shows incorrect results when searching is active

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/tro
   ||jita/0c56f64ba16ebe723d96fd
   ||2936e0d613859cf65c
 Status|CONFIRMED   |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 374819] When dragging a collapsed thread, all messages in the thread should be moved

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/tro
   ||jita/c456aa03cddd3c62ff02fe
   ||a2723d5504635a600b
 Status|CONFIRMED   |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 389793] New: ASSERT: "sourceModel()->rowCount()" in file /home/jkt/work/prog/trojita/src/Imap/Model/ThreadingMsgListModel.cpp, line 647

[Jan Kundrát]

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

Bug ID: 389793
   Summary: ASSERT: "sourceModel()->rowCount()" in file
/home/jkt/work/prog/trojita/src/Imap/Model/ThreadingMs
gListModel.cpp, line 647
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Core
  Assignee: trojita-b...@kde.org
  Reporter: j...@kde.org
  Target Milestone: ---

There were some network reconnects. A search was active in a random mailbox.
The msg list went blank, and upon clearing the search condition manually,
Trojita crashed:

Couldn't find out which mailbox is "cesnet.gn3.gn4-jra2-t1" when parsing a
STATUS reply
Couldn't find out which mailbox is "cesnet.project01.CzechLight" when parsing a
STATUS reply
"Current threading invalidated by changed search"
ASSERT: "sourceModel()->rowCount()" in file
/home/jkt/work/prog/trojita/src/Imap/Model/ThreadingMsgListModel.cpp, line 647
Aborted (core dumped)

(gdb) bt
#0  0x7f680fbd221b in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x7f680fbd38b1 in __GI_abort () at abort.c:89
#2  0x7f681092e99e in qt_message_fatal (context=..., message=...) at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qlogging.cpp:1690
#3  QMessageLogger::fatal (this=this@entry=0x7ffe6ea89e20,
msg=msg@entry=0x7f6810bf3038 "ASSERT: \"%s\" in file %s, line %d") at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qlogging.cpp:796
#4  0x7f6810928c45 in qt_assert (assertion=, file=, line=) at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/global/qglobal.cpp:3077
#5  0x005e94f4 in
Imap::Mailbox::ThreadingMsgListModel::askForThreading(unsigned int) ()
#6  0x005edad5 in
Imap::Mailbox::ThreadingMsgListModel::setUserSearchingSortingPreference(QStringList
const&, Imap::Mailbox::ThreadingMsgListModel::SortCriterium, Qt::SortOrder) ()
#7  0x7f6810b5a505 in QtPrivate::QSlotObjectBase::call (a=0x7ffe6ea8a110,
r=0x7ffe6ea8aa00, this=0x128ce40) at
../../include/QtCore/../../../qtcore-5.9./src/corelib/kernel/qobject_impl.h:101
#8  QMetaObject::activate (sender=0x110f900, signalOffset=,
local_signal_index=, argv=0x7ffe6ea8a110) at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qobject.cpp:3749
#9  0x004899f2 in Gui::MessageListWidget::requestingSearch(QStringList
const&) ()
#10 0x004ba1a4 in Gui::MessageListWidget::slotApplySearch() ()
#11 0x7f6810b5a505 in QtPrivate::QSlotObjectBase::call (a=0x7ffe6ea8a280,
r=0x110f900, this=0x122d700) at
../../include/QtCore/../../../qtcore-5.9./src/corelib/kernel/qobject_impl.h:101
#12 QMetaObject::activate (sender=sender@entry=0x122d650,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffe6ea8a280)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qobject.cpp:3749
#13 0x7f6810b5aaa5 in QMetaObject::activate (sender=sender@entry=0x122d650,
m=m@entry=0x7f6810d8a100 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe6ea8a280)
at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qobject.cpp:3628
#14 0x7f6810b68e8f in QTimer::timeout (this=this@entry=0x122d650, _t1=...)
at .moc/moc_qtimer.cpp:201
#15 0x7f6810b69434 in QTimer::timerEvent (this=0x122d650, e=) at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qtimer.cpp:255
#16 0x7f6810b5b49b in QObject::event (this=0x122d650, e=) at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qobject.cpp:1268
#17 0x7f6811417d54 in QApplicationPrivate::notify_helper (this=, receiver=0x122d650, e=0x7ffe6ea8a5b0)
at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qapplication.cpp:3722
#18 0x7f68114204a2 in QApplication::notify (this=0x7ffe6ea8a9f0,
receiver=0x122d650, e=0x7ffe6ea8a5b0) at
/var/tmp/portage/dev-qt/qtwidgets-5.9./work/qtwidgets-5.9./src/widgets/kernel/qapplication.cpp:3481
#19 0x7f6810b2a078 in QCoreApplication::notifyInternal2
(receiver=0x122d650, event=event@entry=0x7ffe6ea8a5b0) at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qcoreapplication.cpp:1018
#20 0x7f6810b85cbd in QCoreApplication::sendEvent (event=0x7ffe6ea8a5b0,
receiver=) at
../../include/QtCore/../../../qtcore-5.9./src/corelib/kernel/qcoreapplication.h:233
#21 QTimerInfoList::activateTimers (this=0x1061cb0) at
/var/tmp/portage/dev-qt/qtcore-5.9./work/qtcore-5.9./src/corelib/kernel/qtimerinfo_unix.cpp:643
#22 0x7f6810b8683f in timerSourceDispatch (source=) at

[trojita] [Bug 334091] Add support for bouncing (redirecting) messages

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

  Latest Commit||38b8822884868c35c6d768558a2
   ||8788c7fddbbcb
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Jan Kundrát <j...@kde.org> ---
Thanks. Feel free to submit a patch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 359437] Keyboard shortcut to move a mail to a specified folder (e.g. to a "Archived" folder)

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||456365e020b95dc4673e898745d
   ||eb67cd567edb0

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
Right; this wasn't closed because the commit author apparently doesn't have a
Bugzilla account.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 378555] Add HTTPS/SSL support to trojita.flaska.net website

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Sorry for a late response. Yes, you're right, it would be nice. I'll handle
this when I reimage that VM.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 323725] Systray aborts session management

[Jan Kundrát]

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

--- Comment #5 from Jan Kundrát <j...@kde.org> ---
> Jan, what do you think about the patch proposed in comment #1? I as the
> maintainter of the trojita package in Fedora tend to add this patch instead
> of disabling the systray icon by default (for an autostart option in session
> settings).

That patch does not work; please do not apply it.

Yes, the bug is still there. Once we have something which fixes this issue
properly, this bugreport will be marked as solved :).

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 353150] Pressing Alt+E in composer results in message being send when kwidgetsaddons are active

[Jan Kundrát]

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

--- Comment #4 from Jan Kundrát <j...@kde.org> ---
Git commit 9847606f232d01dd1ac6120579f2f2e90ea9bb1e by Jan Kundrát, on behalf
of Roland Pallai.
Committed on 02/11/2017 at 19:20.
Pushed by gerrit into branch 'master'.

Do not add ampersands on address completion

Using qaction->data() instead of text() because the latter may (and will)
be tampered by Qt (with ampersands).
Change-Id: I61f9917d4079c05e0c477a02675c401beb19bf4d

M  +3-3src/Gui/ComposeWidget.cpp

https://commits.kde.org/trojita/9847606f232d01dd1ac6120579f2f2e90ea9bb1e

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 386452] Win32 devbuild setup comes with Qt 5.6 but Qt5WebKit.dll is from 5.5.1 causing "Entry Point Not Found"

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from Jan Kundrát <j...@kde.org> ---
OK, thanks. I checked the build nodes and discovered that there has been no
update to EPEL7's mingw32-qt5-qtwebkit package for almost two years :(. That's
bad. The good thing is that it's still being maintained in Fedora branches, at
least.

There are several options on what we might do:

a) Discontinue Windows builds.
b) Pester Fedora to update the EPEL7 packages of mingw-qt5-*, update our VMs
once this is done.
c) Add more build VMs, this time running a newer Fedora which provides newer
QtWebkit.
d) Use our own Qt and build it via mingw.

I definitely don't have time for d) or c), sorry.

One can monitor progress for b) at
https://bugzilla.redhat.com/show_bug.cgi?id=1341993 (I actually forgot that I
reported that one).

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 386457] Haiku supporting patchset

[Jan Kundrát]

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

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
https://techbase.kde.org/Development/Gerrit

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 386457] Haiku supporting patchset

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Can you please submit these patches via Gerrit?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 386452] Win32 devbuild setup comes with Qt 5.6 but Qt5WebKit.dll is from 5.5.1 causing "Entry Point Not Found"

[Jan Kundrát]

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

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
Just to clarify -- is this about binaries downloaded from
http://ci-logs.kde.flaska.net/binaries/trojita/win32/ , or something differen?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 386353] Crash on startup, related to Util::Css::warningBorder

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 CC||zmiz...@extrowerk.com

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
*** Bug 386351 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 386351] Trojita crashes at start on Haiku

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REOPENED|RESOLVED

--- Comment #3 from Jan Kundrát <j...@kde.org> ---


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

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 386351] Trojita crashes at start on Haiku

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|DOWNSTREAM  |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
Sorry, I got confused by the crash log and the patch-observation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 386351] Trojita crashes at start on Haiku

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Sorry, we cannot help with platform-specific issues. If I were you, I would
start with writing a simple Qt app which exercises the QApplication/QTranslator
combination. If that doesn't work, then you will know that it is a Qt bug, and
that you should bring this to the Haiku/Qt maintainers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 336186] ComposeWidget fails with e-mails that contain @ in the human readable name

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
URL||https://gerrit.vesnicky.ces
   ||net.cz/r/904

--- Comment #4 from Jan Kundrát <j...@kde.org> ---
Indeed, thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 378684] Incorrect page width for plain text messages

[Jan Kundrát]

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

--- Comment #9 from Jan Kundrát <j...@kde.org> ---
(In reply to Jesper Schmitz Mouridsen from comment #8)
> initial fix of  the plain text issue, uses webwngine. WIP.

Cool! Thanks, yes, adding a QWebEngine backend to be used as an alternative to
the legacy QWebKit backend is definitely a way to go. Please make that at least
buildtime-configurable, though, and submit these patches via Gerrit. See
https://techbase.kde.org/Development/Gerrit for a small howto.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 344606] Can't directly open attached PDF files in Adobe Reader

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/tro
   ||jita/4cecef196024ffb31fc6d9
   ||38ea616d17834c2d6b

--- Comment #11 from Jan Kundrát <j...@kde.org> ---
Git commit 4cecef196024ffb31fc6d938ea616d17834c2d6b by Jan Kundrát.
Committed on 10/09/2017 at 14:38.
Pushed by gerrit into branch 'master'.

Do not auto remove direct-opened attachments

Previously, Trojita tried to wait for a while and remove the temporary
file on disk 10 seconds after the application has been launched. That
was a possible race, and worse, some applications attempt to be smart
and detect this file removal and somehow handle that. An example is
Gwenview which auto-switches to a next file in the directory. Another
example is Ark which won't let you extract/preview additional files from
the archive once the downloaded file has been removed.

It's 2017, and it seems that we can now mostly rely on a system behaving
"sanely" and cleaning /tmp automatically. That's probably better than a
random ad-hoc timeout of 10 seconds which we used to have in Trojita.

Another bonus is that this fixes an interoperability problem with Adobe
Reader on Windows. That app complained when the file to be openened was
locked by another application -- Trojita in this case.
Related: bug 316981
Change-Id: Ic150c6d2976ac1a414a6b34a41008aed104c7098

M  +2-5src/Gui/AttachmentView.cpp

https://commits.kde.org/trojita/4cecef196024ffb31fc6d938ea616d17834c2d6b

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 316981] Gwenview automatically switches to a next file in a directory when the original file gets deleted

[Jan Kundrát]

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

--- Comment #8 from Jan Kundrát <j...@kde.org> ---
Git commit 4cecef196024ffb31fc6d938ea616d17834c2d6b by Jan Kundrát.
Committed on 10/09/2017 at 14:38.
Pushed by gerrit into branch 'master'.

Do not auto remove direct-opened attachments

Previously, Trojita tried to wait for a while and remove the temporary
file on disk 10 seconds after the application has been launched. That
was a possible race, and worse, some applications attempt to be smart
and detect this file removal and somehow handle that. An example is
Gwenview which auto-switches to a next file in the directory. Another
example is Ark which won't let you extract/preview additional files from
the archive once the downloaded file has been removed.

It's 2017, and it seems that we can now mostly rely on a system behaving
"sanely" and cleaning /tmp automatically. That's probably better than a
random ad-hoc timeout of 10 seconds which we used to have in Trojita.

Another bonus is that this fixes an interoperability problem with Adobe
Reader on Windows. That app complained when the file to be openened was
locked by another application -- Trojita in this case.
Related: bug 344606
Change-Id: Ic150c6d2976ac1a414a6b34a41008aed104c7098

M  +2-5src/Gui/AttachmentView.cpp

https://commits.kde.org/trojita/4cecef196024ffb31fc6d938ea616d17834c2d6b

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 316981] Gwenview automatically switches to a next file in a directory when the original file gets deleted

[Jan Kundrát]

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

--- Comment #6 from Jan Kundrát <j...@kde.org> ---
> In modern systems, /tmp is
> just a directory in /, not a tiny mount that's prone to filling up, as was
> true in daye of yore.

Actually, it's the systemd's default configuration to mount a tmpfs at /tmp.
Systemd doesn't specify any size, which means that it's going to use the
kernel's default, which is total_RAM * 0.5.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 344606] Can't directly open attached PDF files in Adobe Reader

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

URL|https://gerrit.vesnicky.ces |https://gerrit.vesnicky.ces
   |net.cz/r/#/c/407/   |net.cz/r/943

--- Comment #10 from Jan Kundrát <j...@kde.org> ---
There's a patch which implements this at [1]. An example installer lives at
[2].

[1] https://gerrit.vesnicky.cesnet.cz/r/943
[2]
http://ci-logs.kde.flaska.net/binaries/trojita/win32/check/Trojita-Setup-945-a621aef9ce924861bfe9f0faf5536dda.exe

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 316981] Gwenview automatically switches to a next file in a directory when the original file gets deleted

[Jan Kundrát]

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

--- Comment #4 from Jan Kundrát <j...@kde.org> ---
> /tmp exists for precisely the reason they are using it: to hold temporary 
> files. No need to perform manual cleaning. The system takes care of that.

This appears to be the root of your argument. As an app developer (I'm actually
Trojita's maintainer), I would be very happy to rely on that, but I'm not sure
that we're already there today. Is that something that the rest of KDE
effectively already relies upon? If so, then the matter is settled.

I see that systemd ships with a default of 10 days lifetime for stuff under
/tmp; this appears to be preserved on RHEL7 as well. That's good. However,
Gentoo decided to patch this away [1] in fall 2015 and as such, they do not
clean /tmp at all.

[1] https://bugs.gentoo.org/show_bug.cgi?id=490676

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 316981] Gwenview automatically switches to a next file in a directory when the original file gets deleted

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |---

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
(In reply to Nate Graham from comment #1)
> What would you rather it do? Continue showing a file that no longer exists?

Yes. I tried to explain my reasons and the use case behind this situation.
While the file is gone, it doesn't mean that one suddenly loses the possibility
to show its content which is already being shown. I'm also fine if some
features are disabled -- I can imagine that one won't be able to zoom, for
example. However, navigating to a different file is confusing in the scenario I
described in my original submission, four and half years ago.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 378684] Incorrect page width for plain text messages

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|UPSTREAM|---
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 368859] Use newer upstream gpgme to get rid of kf5-gpgmepp

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 379632] Let the user to change fixed font

[Jan Kundrát]

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

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Sorry for a late reply. I thought that Qt follows your "platform preferences".
It's a bummer if it is really hardcoded on Windows.

Anyway, patches welcome.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 383822] Address Book accesses first 100 records only.

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
I cannot reproduce this -- I've created an address book with more than one
hundred records, and I can access those around index #100 just fine.

How do these inaccessible contacts look like? Please re-open when you add more
details. If possible, please attach or private-mail your ~/.abook/addressbook
to me. You can probably perform some basic anonymization via `sed -e
's/^name=.*/name=XXX/' -e 's/^email=.*/email=YYY/' ~/.abook/addressbook`.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 383131] Invalid QRESYNC parameters when selecting INBOX a second time

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
Hi Matthieu, thanks for going through the trouble of debugging this paroblem
and providing a patch. Sorry for a late response, I've been on a month-long
holiday recently. I won't merge this patch as-is for a bunch of reasons.

First of all, I believe that this issue was reported to the Dovecot upstream
and fixed in 2010 [1] in all of their by-then maintained branches. Is there any
chance of asking your IMAP service provider to upgrade their Dovecot? I find it
a little bit worrying that this fix has not made it through whatever
distribution/upgrading channels that they are using. I realize that there's
only a small chance of success here, but it never hurts to ask.

We do not generally carry fixes for stuff like this which has been fixed
upstream for ages. Also, as the rest of the thread at [1] suggests, this might
need a range of 1 to (2^32)-1 in order to also catch all UIDs that we haven't
seen before (please check the RFC7162 if it's correct). That's one more special
case which needs to be unit-tested properly. Right now, I do not think that
this is something worth the extra effort, but please do comment if you
disagree.

As a quick fix, you can add "QRESYNC" to the list of blacklisted IMAP
capabilities. This effectively reverts to a CONDSTORE-level functionality which
is still better than plain RFC3501-like SELECT.

Perhaps we need to add some extra-careful infrastructure which automatically
enables quirks like this one in case of buggy servers...

[1] https://dovecot.org/list/dovecot/2010-August/052025.html

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 382160] Cannot edit name of contacts

[Jan Kundrát]

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

--- Comment #4 from Jan Kundrát <j...@kde.org> ---
(In reply to Thomas Lübking from comment #2)
> Putting a ton of lineedits there makes the thing look terribly crowded (and
> it's rather meant to be looked at)

My problem with this approach is that Trojita is "different" than any other app
that I use.

I'm not so unhappy about it as to change the code, but I still think that the
discoverability is kinda limited. Yup, the [markings] help in case the data
have not been filed and are empty, but that's not all, IMHO.

> How would you feel about altering the look of only the focused label? Like
> passing it a solid background and poosibly a frame?

Sounds good I think, patches welcome.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 382160] Cannot edit name of contacts

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/tro
   ||jita/a96e5e0b5516a8f548d893
   ||dd221b08dca33b2255
 Resolution|--- |FIXED

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
Git commit a96e5e0b5516a8f548d893dd221b08dca33b2255 by Jan Kundrát, on behalf
of Thomas Lübking.
Committed on 14/07/2017 at 17:51.
Pushed by gerrit into branch 'master'.

change contact name on list edit
Change-Id: Ibd5d4aa5a4f8d7dd3068fc1a142e1bdeac01cf2d

M  +3-0src/Plugins/AbookAddressbook/be-contacts.cpp

https://commits.kde.org/trojita/a96e5e0b5516a8f548d893dd221b08dca33b2255

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 382160] Cannot edit name of contacts

[Jan Kundrát]

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

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Patches welcome. I'm quite surprised that this widget allows editing. I've
always used the main widget at the right for changing the contact details (and
I'm always annoyed that they are not using default QLineEdit UI because the
current version probably doesn't look like an editable thing to the user).

Anyway, the easiest fix is probably to ensure that the EditRole is missing from
the list model.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381280] Increased CPU usage with Qt 5.9

[Jan Kundrát]

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

--- Comment #6 from Jan Kundrát <j...@kde.org> ---
> I'm seeing this as well, do you happen to use SlideShow for the desktop
> background?

Nope, my background is a static image.

On the other hand, right now I'm not getting that high CPU usage at this
moment. I haven't made any changes to plasma config files; I'm using the same
set of applets, the same everything. So it seems that the reproducibility is a
bit random :(.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 381461] Two overlapping QMessageBox instances causes KWin to lock up

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 CC||j...@kde.org,
   ||thomas.luebk...@gmail.com
Summary|hard lockup after   |Two overlapping QMessageBox
   |ParseError  |instances causes KWin to
   ||lock up
 Status|REOPENED|CONFIRMED
Product|trojita |kwin
   Assignee|trojita-b...@kde.org|kwin-bugs-n...@kde.org
  Component|IMAP|general
Version|git |git master

--- Comment #11 from Jan Kundrát <j...@kde.org> ---
Run the attached test case, observe that KWin stops being responsive.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 381461] hard lockup after ParseError

[Jan Kundrát]

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

--- Comment #10 from Jan Kundrát <j...@kde.org> ---
Created attachment 106212
  --> https://bugs.kde.org/attachment.cgi?id=106212=edit
kwin supportinfo for jkt

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 381461] hard lockup after ParseError

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Attachment #106201|0   |1
is obsolete||
 Attachment #106208|0   |1
is obsolete||

--- Comment #8 from Jan Kundrát <j...@kde.org> ---
Created attachment 106211
  --> https://bugs.kde.org/attachment.cgi?id=106211=edit
testcase-twodialogs.cpp

Erik, running this locks up kwin for me as well. I'm on the git master of all
of KF5 and all of plasma as of last week or two, with Qt from 5.9 git. Does it
cause the same lockup for you as well?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 381461] hard lockup after ParseError

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|NEEDSINFO   |REOPENED
 Resolution|WAITINGFORINFO  |---

--- Comment #7 from Jan Kundrát <j...@kde.org> ---
This is interesting :).

I looked at the code that opens these dialog boxes. Both of them in the end
call a helper like this:

  auto box = new QMessageBox(icon, title, message, QMessageBox::Ok, );
  box->open();

And I'm able to reproduce this :(.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 381461] hard lockup after ParseError

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
(In reply to Erik Quaeghebeur from comment #0)
> * 22 FETCH (FLAGS (\Seen $X-ME-Annot-2 werk [EXPUNGED]) UID 2006 MODSEQ
> (673451))
> 
>  ^ here

Yes, this was a server-side bug. I don't think that making our parser more
relaxed in this context would be reasonable.

> I don't know whether Trojita is supposed to be able to deal with this, but
> after retriggering the issue by re-opening the mailbox with the offending
> message a couple of times, Trojita locks up the window manager hard.

If a window manager locks up, it's a bug in the window manager, not in Trojita.
I would love to improve Trojita in order to ensure that it doesn't do crazy
things that might crash some WMs, but I don't know what crazy thing it was
doing.

Maybe you ended up with an endless reconnect loop with plenty of dialog windows
on top of each other? That should not happen, and as far as I can tell, it
doesn't happen for me. Reporting IMAP errors is just a simple QMessageBox. I
get an error (from e.g. reconnects or network errors) every now and then, and
my WM survives just fine. Either way, without knowing what your WM dislikes and
how to reproduce this, I cannot fix it, sorry.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381280] Increased CPU usage with Qt 5.9

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
(In reply to Jan Kundrát from comment #0)
> Initially everything works well. After I dock the machine and kscreen
> switches to an external screen (which happens to be bigger in resolution),
> both plasmashell and kwin_x11 put increased load on the CPUs.

I have one external screen at work (Dell U2711, 2560x1440) and another one
(Dell U3014, 2560x1600) at home. This only happens on the work one; I can
switch freely at home and there's no issue there. This is on the exact same
laptop with the same model of the dock.

An interesting point about my home screen is that kscreen is configured to
switch to it automatically, but it actually doesn't make that switch when I
dock. I have to either run `xrandr` with no options, or to power-cycle that
external screen. After doing any of these two options, kscreen switches the
output as expected. I'm not sure if it's related in any way. Either way,
plasmashell's and kwin_x11's CPU consumption is always fine with this
not-auto-switching screen.

Also confirming because there's more people hitting this than just me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 381353] New qt5-webkit breaks viewer layout

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
This looks like a duplicate of bug #378684. There's also an upstream bugreport
at https://github.com/annulen/webkit/issues/511 .

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

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 378684] Incorrect page width for plain text messages

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
*** Bug 381353 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381280] New: Increased CPU usage with Qt 5.9

[Jan Kundrát]

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

Bug ID: 381280
   Summary: Increased CPU usage with Qt 5.9
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: j...@kde.org
CC: bhus...@gmail.com, mgraess...@kde.org,
plasma-b...@kde.org
  Target Milestone: 1.0

I'm seeing increased CPU usage from both kwin_x11 and plasmashell after I
updated "everything" after several months of no updates. Now both kwin_x11 and
plasmashell consume >20% of CPU time according to htop, and the cooling fan
spin on an idle system.

I'm on Gentoo Linux with kernel 4.9.31, xorg-server-1.19.3, xorg-x11-7.4-r2,
mesa 17.1.1, Qt 5.9 from git (last week's), kf5 and plasma-* from git master as
of last week. I'm using KMS with an integrated Intel Skylake GPU (i5-6300U,
Thinkpad T460s).

Initially everything works well. After I dock the machine and kscreen switches
to an external screen (which happens to be bigger in resolution), both
plasmashell and kwin_x11 put increased load on the CPUs. Stuff gets fixed when
I log out and log back in while docked. When I un-dock and re-dock after that
(and the screen switches), the increased CPU load is back there.

I tried looking into `perf top` for both kwin_x11 and plasmashell, but I don't
see anything that is suspicious to my untrained eyes.

I've heard some rumors on IRC about Qt sending expose events that it should not
be sending. I have no clue whether the bug is in Plasma, Qt, Mesa or somewehere
else. I know that it is not in the kernel because I see the same behavior on
4.9.18 that I used to run before. However, because I'm seeing this high load in
plasma apps, I'm reporting the bug here.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 381199] Broken brightness control with kernel module (ex. nvidia-bl)

[Jan Kundrát]

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

--- Comment #5 from Jan Kundrát <j...@kde.org> ---
Just FYI and as a random data point, my T460s with intel_backlight which once
again has a type = raw contains "enabled" in its device/enabled property.
Despite that, I was too hitting this bug.

However, it's possible that I might have always logged in with this laptop
docked while I was debugging this. If that's the case, SDDM shows output on the
laptop's internal screen as well as on some external one. kscreen switches the
internal output off because that's what I want to have.

It's possible that there was a race between kscreen switching and powerdevil
deciding to ignore stuff. Thanks bshah for fixing this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 373374] Test failures with gnupg-2.1.16

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #5 from Jan Kundrát <j...@kde.org> ---
This appears to work as of Gentoo's gnupg-2.1.20-r1.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 321382] Discovery of new arrivals

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 CC||i...@ilya.pp.ua

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
*** Bug 380306 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 380306] Missing any notification support (sound, desktop, tray icon) about new message.

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
> 1 Need popup desktop Notification about new message with sound.

Yup, we're aware of that, but we didn't have the time to implement it yet.
That's bug 321382.

Contributions are welcome -- we're very happy to accept patches.

> 2 Tray icon must changed and/or show quantity new messages.

The tray icon shows the number of unread messages in INBOX. That's been
implemented several years ago.

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

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 379692] UnknownMessageIndex: Got FETCH that is out of bounds

[Jan Kundrát]

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

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
This looks like a bug in the server.

Here's the relevant part of the log:

14:08:35.66612  <<<  * 918 EXISTS
14:08:35.66612  <<<  * 379 RECENT
14:08:35.66612  <<<  y9 OK Completed (0.002 sec)
14:08:35.67712  >>>  y11 UID FETCH 918:* (FLAGS)
14:08:35.75912  <<<  * THREAD [...]
14:08:35.76012  <<<  y10 OK Completed (918 msgs in 0.033 secs)

At this point, the server let us know that there's 918 messages in total, their
MSNs are ( by definition) 1-918. So far, so good.

14:08:35.91312  <<<  * 918 FETCH (FLAGS (\Recent $X-ME-Annot-2) UID 918)

This one was also reasonable -- the server let us know about an update of the
last message's flags. That is nice.

14:08:35.91312  <<<  * 919 FETCH (FLAGS (\Recent $X-ME-Annot-2) UID 919)
14:08:35.91312  <<<  * 919 EXISTS

But here's the bug -- the IMAP server sent a FETCH FLAGS about a message with
MSN 919, but it didn't let us know that there was an arrival before. EXISTS
must be sent prior to FETCH.

14:08:35.91312  <<<  * 380 RECENT
14:08:35.91312  <<<  y11 OK Completed (0.001 sec)

I've notified a friend who works for FastMail about this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 377416] Got FETCH that is out of bounds

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
We've moved this discussion to private mail in order to send unredacted logs. I
*think* that our conclusion was that Zimbra was broken. Please reopen if
there's something to fix in Trojita.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 379566] Address Book should be stored under $XDG_DATA_HOME

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
Closing as per comment #1

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 379158] introduce advanced IMAP server options

[Jan Kundrát]

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

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
> Thunderbird has advanced options for IMAP servers:

Actually, these are largely work-arounds for legacy or misconfigured IMAP 
servers. The mere fact that something in TB is available as a GUI option 
doesn't mean that it's needed. Which one of these prevents you from doing 
something in Trojita?

> IMAP server directory [text]

That's a poor man's NAMESPACE. It might have been relevant around 2000 with 
uw-imapd, but not anymore, IMHO.

> show only subscribed folders [boolean]

Trojita supports that just fine (although you'll need LSUB on the server 
side).

> server supports folders that contain sub-folders and messages [boolean]

There's no need to have that checkbox in the settings; Trojita handles it 
implicitly.

> three namespaces: personal
> namespace [text], public (shared) [text], other users [text], 
> and allow server
> to override these namespaces [boolean].

That's again NAMESPACE. I agree that it would be nice if Trojita offered 
user-visible bits for these, but what do you need them for? Do you have an 
account which actually doesn't publish these mailboxes via a single LIST 
hierarchy?

> For configuring GMail well the server
> directory can be set to "[Google Mail]" (with brackets, without 
> quotes) for a
> much improved display, as the standard GMail labels on shown at 
> the same level as the inbox.

Yes, this is a server-side choice whether various folders are listed as 
children of INBOX or at the same level. I don't think that it warrants an 
extra UI override to tweak the visual representation here, frankly. Does 
that one extra level which is nonetheless automatically expanded bother you 
that much?

> Other IMAP servers also introduce unnecessary nesting

Yes, I'm sure that there are servers which introduce extra nesting. At my 
former workplace, we also used to have one in place. However, that was 
prior to 2006 IIRC. Are you *still* stuck with one of them today?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 321387] Option for switching to next message after deleting one

[Jan Kundrát]

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

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
Git commit 7179c38fbff9c5e881112e381731bdc29b0530d5 by Jan Kundrát, on behalf
of Roland Pallai.
Committed on 21/04/2017 at 20:05.
Pushed by gerrit into branch 'master'.

Move cursor to the next message after current one disappears

A big inconvience for keyboard usability if the cursor forgets last
position when the current message disappeared from message list. It
also prevents next/previous message actions to function.
This patch using an unobtrusive approach to this problem, moves the
cursor to the next message but does not activate it. The user can
activate with return key or can navigate towards. This way it does not
interfere with automatic read marking nor habits of users.
Related: bug 360091
Change-Id: Ic823c2c9d0bba9de65d01fb0e72b91093f233f7e

M  +66   -0src/Gui/MsgListView.cpp
M  +6-0src/Gui/MsgListView.h

https://commits.kde.org/trojita/7179c38fbff9c5e881112e381731bdc29b0530d5

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 360091] MessageWidget should reset when the current message disappears

[Jan Kundrát]

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

--- Comment #4 from Jan Kundrát <j...@kde.org> ---
Git commit 7179c38fbff9c5e881112e381731bdc29b0530d5 by Jan Kundrát, on behalf
of Roland Pallai.
Committed on 21/04/2017 at 20:05.
Pushed by gerrit into branch 'master'.

Move cursor to the next message after current one disappears

A big inconvience for keyboard usability if the cursor forgets last
position when the current message disappeared from message list. It
also prevents next/previous message actions to function.
This patch using an unobtrusive approach to this problem, moves the
cursor to the next message but does not activate it. The user can
activate with return key or can navigate towards. This way it does not
interfere with automatic read marking nor habits of users.
Related: bug 321387
Change-Id: Ic823c2c9d0bba9de65d01fb0e72b91093f233f7e

M  +66   -0src/Gui/MsgListView.cpp
M  +6-0src/Gui/MsgListView.h

https://commits.kde.org/trojita/7179c38fbff9c5e881112e381731bdc29b0530d5

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 358485] CardDAV support

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 CC||bronsonmath...@gmail.com

--- Comment #4 from Jan Kundrát <j...@kde.org> ---
*** Bug 379001 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 379001] support contact sync with gmail

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jan Kundrát <j...@kde.org> ---


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

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 321374] Multiple accounts

[Jan Kundrát]

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

--- Comment #5 from Jan Kundrát <j...@kde.org> ---
As a partial workaround, Trojita has the --profile command-line option. It's
been available since v0.4.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 379000] support for multiple email/gmail accounts

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Jan Kundrát <j...@kde.org> ---


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

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 321374] Multiple accounts

[Jan Kundrát]

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

--- Comment #4 from Jan Kundrát <j...@kde.org> ---
*** Bug 379000 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 378684] Incorrect page width for plain text messages

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Yeah, it's likely a regression in their unofficial port of a new upstream
webkit to Qt. As far as I can tell, Gentoo doesn't really ship that fork in
their official repositories. Please report this to the forked QtWebKit
upstream, we cannot really fix their regressions.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 369556] Change "Development" link on website

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/tro
   ||jita/18539e6b1cfd7c9b4410c5
   ||813ce48e7470c18085
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
Git commit 18539e6b1cfd7c9b4410c5813ce48e7470c18085 by Jan Kundrát.
Committed on 04/04/2017 at 09:39.
Pushed by gerrit into branch 'master'.

www: Do not link to the ancient Redmine

Our website was still linking to my private Redmine which has been
deprecated for a fair amount of time. Let's link to Gerrit for patch
review and to KDE's Bugzilla for bugreports.

Thanks to Daniel Aleksandersen (ctOS on IRC) for reminding me about this.
Change-Id: I220af6c7789c5296bce7cd14759019bffc261867

M  +2-2www/download.html
M  +2-2www/index.html
M  +2-2www/screenshots.html
M  +1-0www/welcome.html

https://commits.kde.org/trojita/18539e6b1cfd7c9b4410c5813ce48e7470c18085

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 377734] Failed to Send Mail: Append failed

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
menu -> IMAP -> Settings -> SMTP -> Sent Folder Name

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 378055] Depends on libmimetic0 but needs libmimetic0v5

[Jan Kundrát]

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

--- Comment #4 from Jan Kundrát <j...@kde.org> ---
(In reply to Michael Tunnell from comment #3)
> @Jan would there be any chance for Trojita to set up a PPA to solve the
> Ubuntu support?

Anyone is free to set up and maintain their own PPAs. Given that I do not use
Ubuntu and that the OBS actually gets the job done, I do not plan on investing
my time to provide an Ubuntu-specific solution.

> If Trojita has git somewhere it's actually possible to mirror git commits to
> Launchpad so that updates are rather seamless. I have used this git
> mirroring feature before and it works pretty well.

Feel free to setup whatever repos you need, then. You can find Trojita's git
URL on the project's homepage :).

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 378055] Depends on libmimetic0 but needs libmimetic0v5

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Jan Kundrát <j...@kde.org> ---
Several factors are involved here:

- https://wiki.debian.org/GCC5 introduced an extra package suffix to cope with
the changed ABI required by GCC's STL which became incompatible with C++11

- While Debian has mimetic in its regular repositories, that is not the case
with Ubuntu. Ubuntu only has this in Universe. However, OBS doesn't allow
access to Ubuntu Universe packages, so we have to build Mimetic ourselves.

- Our bundled Mimetic package must remain compatible with Debian Jessie at
least until (some time after) Stretch will have been released (and made
available via OBS).

If you have experience with Debian packaging, handling the GCC 5 C++11 ABI
change, and can provide a patch/request on OBS which handles this while still
preserving compatibility with current Debian, patches are welcome.

Can you perhaps in the meanwhile give priority to the OBS version of Mimetic?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 358680] sort order not saved when not threaded

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 CC||szg0...@freemail.hu

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
*** Bug 378149 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 378149] Trojitá forgets e-mail sorting after restart

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Jan Kundrát <j...@kde.org> ---


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

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 378150] Need to change the INBOX column order and column width

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
You can reorder these columns and change their widths by simply dragging the
header with a mouse.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 377734] Failed to Send Mail: Append failed

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |INVALID
   Severity|critical|normal
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Specify a mailbox that exists in your settings and the message will go away. We
don't do autodetection yet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 360091] MessageWidget should reset when the current message disappears

[Jan Kundrát]

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

--- Comment #3 from Jan Kundrát <j...@kde.org> ---
> This behavior is unintuitive.

Agreed.

> If you need access to a message which is no
> longer in the "active folder list" then it would make sense to require
> navigation to the location of that message (i.e. trash).

That also makes sense. Note that this message might very well be gone for once
and not available at all (once it gets expunged from its mailbox).

> This state also prevents the next/previous actions (shortcuts and menu
> items) from functioning.

That's bad, but at least there's https://gerrit.vesnicky.cesnet.cz/r/896 for
that.

> The question is, what to you do if you don't display the message anymore?
> Does the MessageWidget collapse? Does it show the next message? If it shows
> the message, do you mark that message as read?
> 
> My desired behavior is to show the next message and give me an option of
> marking it as read (but not automatically marking it as read).

What you mean by "give me an option of marking it as read"? Do you mean just
moving to the next message as usual without starting the timer which marks it
as read, and still allowing all operations such as replying, deleting, or
marking as read by an appropriate button/shortcut?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 377382] Unable to log in -- IMAP alert

[Jan Kundrát]

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

Jan Kundrát <j...@kde.org> changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

-- 
You are receiving this mail because:
You are watching all bug changes.