[akregator] [Bug 358716] New: Occasional loss of GUI layout settings after system restart

2016-01-29 Thread Maxim via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358716

Bug ID: 358716
   Summary: Occasional loss of GUI layout settings after system
restart
   Product: akregator
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mmarinche...@yahoo.com

I use Akregator as a resident application (autolaunch at startup). Sometimes
after restarting the system Akregator "forgets" GUI layout settings and I have
to resize controls.

Not critical but annoying...

Reproducible: Sometimes

Steps to Reproduce:
See "Details" section.



openSUSE 13.2 with KDE:Extra repository, Akregator 4.14.9, KDE Platform
4.11.20.

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


[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes

2016-01-29 Thread Laurent Montel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352512

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.2
 Status|CONFIRMED   |RESOLVED

--- Comment #23 from Laurent Montel  ---
I recreate a new widget to inform if we want to restore session (for akregator
5.2).
It's better now. We can or not restore session as previously.

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


[akregator] [Bug 358724] akregator crashes every time when trying to open a tab

2016-01-29 Thread Laurent Montel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358724

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org
 Resolution|--- |FIXED
   Version Fixed In||5.1.2
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Laurent Montel  ---
I disabled it in 5.1.2 it's broken.
you can fix to remove crash info:
rm -rf ~/.local/akregator/crashed

it will not ask you to restore it.
I work on a new method for it in 5.2.
Sorry for the actual bug

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


[akregator] [Bug 358724] New: akregator crashes every time when trying to open a tab

2016-01-29 Thread Con Hennessy via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358724

Bug ID: 358724
   Summary: akregator crashes every time when trying to open a tab
   Product: akregator
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: con.henne...@gmail.com

Application: akregator (5.1.1)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-rc8-1.ge628e30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
On restarting when I selected "Restore session" this crash happens. It can also
be duplicated by "Do not restore" and then selecting any feed.

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7f78647a6700 (LWP 20153)):
#0  0x7f78810ebc1d in poll () at /lib64/libc.so.6
#1  0x7f7877984422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f787798600f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f78664d13c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f78819fa32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f787a1cf0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f78810f404d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f7861e26700 (LWP 20154)):
#0  0x7f78810e7ced in read () at /lib64/libc.so.6
#1  0x7f7879cf3b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7879cb2999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7879cb2df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f7879cb2f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f7881c2cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f7881bd3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f78819f561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f78819fa32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f787a1cf0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f78810f404d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f781dffb700 (LWP 20171)):
#0  0x7f787a1d3408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f78819fb298 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f78819f74e6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f78819fa32f in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f787a1cf0a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f78810f404d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f7885381800 (LWP 20152)):
[KCrash Handler]
#6  0x7f7883f82b42 in KActionCollection::action(QString const&) const () at
/usr/lib64/libKF5XmlGui.so.5
#7  0x7f7862473a81 in  () at /usr/lib64/qt5/plugins/akregatorpart.so
#8  0x7f7862473658 in  () at /usr/lib64/qt5/plugins/akregatorpart.so
#9  0x7f7862485bc4 in
Akregator::ArticleViewer::slotShowSummary(Akregator::TreeNode*) () at
/usr/lib64/qt5/plugins/akregatorpart.so
#10 0x7f78624ac7a3 in
Akregator::MainWidget::slotNodeSelected(Akregator::TreeNode*) () at
/usr/lib64/qt5/plugins/akregatorpart.so
#11 0x7f7881c0573f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#12 0x7f78624c6a1f in  () at /usr/lib64/qt5/plugins/akregatorpart.so
#13 0x7f7862469f3f in  () at /usr/lib64/qt5/plugins/akregatorpart.so
#14 0x7f7881c0573f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#15 0x7f7881b8a8fa in QItemSelectionModel::currentChanged(QModelIndex
const&, QModelIndex const&) () at /usr/lib64/libQt5Core.so.5
#16 0x7f7881b8aace in QItemSelectionModel::setCurrentIndex(QModelIndex
const&, QFlags) () at
/usr/lib64/libQt5Core.so.5
#17 0x7f78834c6bf4 in QAbstractItemView::mousePressEvent(QMouseEvent*) ()
at /usr/lib64/libQt5Widgets.so.5
#18 0x7f788350af0a in QTreeView::mousePressEvent(QMouseEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#19 0x7f78832b83ba in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#20 0x7f78833b243e in QFrame::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#21 0x7f78834cd94b in QAbstractItemView::viewportEvent(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#22 0x7f788350a870 in QTreeView::viewportEvent(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#23 0x7f7881bd60d3 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#24 0x7f7883277e5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#25 0x7f788327d2cb in QApplication::notify(QObject*, QEvent*) () at

[akregator] [Bug 358716] Occasional loss of GUI layout settings after system restart

2016-01-29 Thread Maxim via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358716

--- Comment #4 from Maxim  ---
I've attached sample screenshots: before and after reboot (log off/on
actually).

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


[akregator] [Bug 358716] Occasional loss of GUI layout settings after system restart

2016-01-29 Thread Laurent Montel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358716

--- Comment #5 from Laurent Montel  ---
Ok splitter size ok

-- 
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 355743] akonadiconsole shows now enties in the 'Browser' tab

2016-01-29 Thread Daniel Vrátil via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355743

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

-- 
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 358116] messageviewer leaks temporary files with mail parts in it

2016-01-29 Thread Sandro Knauß via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358116

--- Comment #6 from Sandro Knauß  ---
Well I can reproduce this behaviour with a simple testcase.  This one fails:
QString path;
{
NodeHelper helper;
path = helper.createTempDir(QStringLiteral("foo"));
QVERIFY(QDir(path).exists());
}
QEventLoop loop;
QTimer::singleShot(0, , ::quit);
loop.exec();
QVERIFY(!QDir(path).exists());

if I change the singleShot to something like 11000 (11secs) if passes.

The problem here is that if the NodeHelper instance is deleted the tempfiles
are deleted also only 10secs after the application and not directly with the
deletion of NodeHelper. I see no need to wait 10secs when the object is already
deleted.

NodeHelper::~NodeHelper()
{
//Don't delete it it will delete in class with a deleteLater;
if (mAttachmentFilesDir) {
mAttachmentFilesDir->removeTempFiles();
mAttachmentFilesDir = 0;
}
}

void AttachmentTemporaryFilesDirs::removeTempFiles()
{
QTimer::singleShot(d->mDelayRemoveAll, this,
::slotRemoveTempFiles);
}

^^ d->mDelayRemoveAll is 10secs.

-- 
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 358116] messageviewer leaks temporary files with mail parts in it

2016-01-29 Thread Sandro Knauß via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358116

--- Comment #7 from Sandro Knauß  ---
I've created a patch that should improve the situation:
https://phabricator.kde.org/D883

Still we have no handling, if the application crashes, but we now delete the
temp dirs directly, if the object is deleted. It would be great to test it in
the wild.

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


[akregator] [Bug 358716] Occasional loss of GUI layout settings after system restart

2016-01-29 Thread Maxim via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358716

--- Comment #3 from Maxim  ---
Created attachment 96899
  --> https://bugs.kde.org/attachment.cgi?id=96899=edit
After

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


[akregator] [Bug 358716] Occasional loss of GUI layout settings after system restart

2016-01-29 Thread Maxim via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358716

--- Comment #2 from Maxim  ---
Created attachment 96898
  --> https://bugs.kde.org/attachment.cgi?id=96898=edit
Before

-- 
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 354056] Deleted emails stay, but greyed out

2016-01-29 Thread Dmitry Roshchin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354056

Dmitry Roshchin  changed:

   What|Removed |Added

 CC||dmi...@roshchin.org

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


[akregator] [Bug 358716] Occasional loss of GUI layout settings after system restart

2016-01-29 Thread Laurent Montel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358716

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
Which layout settings is "forgetting" ?
view layout ?
Size ?
etc.

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


[kontact] [Bug 358742] New: Kontact (Akregator) crashed after clicking "more" on a feed

2016-01-29 Thread Ian Borg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358742

Bug ID: 358742
   Summary: Kontact (Akregator) crashed after clicking "more" on a
feed
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bor...@gmail.com

Application: kontact (4.14.9)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-29-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
Was reading a feed in the Kontact (Akregator) window. Clicked on "more" to read
more of the feed, which switched me to Firefox. As I read the feed in the
firefox browser I noticed that Kontact had closed and the crash Reporting
Assistant was up on the screen.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3af4812800 (LWP 1630))]

Thread 45 (Thread 0x7f3ad7316700 (LWP 1637)):
#0  0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3aef5bc686 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f3aef5bc6b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3af1d9f08d in clone () at /lib64/libc.so.6

Thread 44 (Thread 0x7f3a96a13700 (LWP 1653)):
#0  0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3aef32ee7d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f3aef5e41e6 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3af1d9f08d in clone () at /lib64/libc.so.6

Thread 43 (Thread 0x7f3a7f156700 (LWP 1781)):
#0  0x7f3af1d96c5d in poll () at /lib64/libc.so.6
#1  0x7f3aeb846be4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3aeb846cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3af25190de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f3af24eae6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f3af24eb165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f3af23e80bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f3af23ea79f in  () at /usr/lib64/libQtCore.so.4
#8  0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3af1d9f08d in clone () at /lib64/libc.so.6

Thread 42 (Thread 0x7f3a777fe700 (LWP 7340)):
#0  0x7f3af1d96c5d in poll () at /lib64/libc.so.6
#1  0x7f3aeb846be4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3aeb846f0a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#3  0x7f3a58ae8946 in  () at /usr/lib64/libgio-2.0.so.0
#4  0x7f3aeb86bb85 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f3af1d9f08d in clone () at /lib64/libc.so.6

Thread 41 (Thread 0x7f3a77fff700 (LWP 7341)):
#0  0x7f3aeb8464ae in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f3aeb846b52 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3aeb846cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3aeb846d29 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f3aeb86bb85 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f3af1d9f08d in clone () at /lib64/libc.so.6

Thread 40 (Thread 0x7f3a51479700 (LWP 7344)):
#0  0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3a514e0d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f3a514e1819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3af1d9f08d in clone () at /lib64/libc.so.6

Thread 39 (Thread 0x7f3a50c78700 (LWP 7345)):
#0  0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3a514e0d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f3a514e1819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3af1d9f08d in clone () at /lib64/libc.so.6

Thread 38 (Thread 0x7f3a50477700 (LWP 7346)):
#0  0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3a514e0d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f3a514e1819 in  () at

[kontact] [Bug 353482] Akonadi will not load in PMI files.

2016-01-29 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353482

bu...@gmx.at changed:

   What|Removed |Added

 CC||bu...@gmx.at

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


[kontact] [Bug 353482] Akonadi will not load in PMI files.

2016-01-29 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353482

--- Comment #11 from bu...@gmx.at ---
Created attachment 96904
  --> https://bugs.kde.org/attachment.cgi?id=96904=edit
New crash information added by DrKonqi

kaddressbook (5.0.2) using Qt 5.5.1

- What I was doing when the application crashed:

I just opened the application. I have one Google contact account configured.

-- Backtrace (Reduced):
#7  0xb54d226a in Akonadi::Tag::operator= (this=0xbffd4df4, other=...) at
../../../../akonadi/src/core/tag.cpp:80
#8  0xb54d23cf in Akonadi::Tag::Tag (this=0xbffd4df4, other=...) at
../../../../akonadi/src/core/tag.cpp:72
#9  0xb5571537 in Akonadi::TagModelPrivate::tagForIndex (this=0x91d0b80,
index=...) at ../../../../akonadi/src/core/models/tagmodel_p.cpp:105
#10 0xb557032c in Akonadi::TagModel::data (this=0x91d1cd0, index=..., role=258)
at ../../../../akonadi/src/core/models/tagmodel.cpp:91
#11 0xb7626145 in CategorySelectWidgetPrivate::slotTagsInserted
(this=0x91cdd80, parent=..., start=0, end=0) at
../../kaddressbook/categoryselectwidget.cpp:173

-- 
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 358760] New: Sending Message Failed -- Could not compose message: No such file or directory

2016-01-29 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358760

Bug ID: 358760
   Summary: Sending Message Failed -- Could not compose message:
No such file or directory
   Product: kmail2
   Version: 5.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kokotokos...@yopmail.fr

When trying to send a signed (and/or encrypted) message, it fails with the
above error.

I even tried sending to one of my other accounts, so the PGP certificates have
ultimate trust, but no, it just refuses to send.

Looks suspiciously like this https://bugs.kde.org/show_bug.cgi?id=284274 one,
and this one from KMail1 https://bugs.kde.org/show_bug.cgi?id=44699

This thing might be possibly related?
https://bugs.kde.org/show_bug.cgi?id=356950

I'll go Major on this, as I have to resort to Thunderbird to send signed email,
and my professional emails are all signed.


Reproducible: Always

-- 
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 358757] New: Incorrect encoding in Followup Reminder Messages... dialog

2016-01-29 Thread André Marcelo Alvarenga via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358757

Bug ID: 358757
   Summary: Incorrect encoding in Followup Reminder Messages...
dialog
   Product: kmail2
   Version: 5.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: alvare...@kde.org

See screenshot.

File -> Followup Reminder Messages...

Tested with pt_BR translations.


Reproducible: Always

-- 
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 358757] Incorrect encoding in Followup Reminder Messages... dialog

2016-01-29 Thread André Marcelo Alvarenga via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358757

--- Comment #1 from André Marcelo Alvarenga  ---
Created attachment 96912
  --> https://bugs.kde.org/attachment.cgi?id=96912=edit
Screenshot

-- 
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 340540] Folder Archive does not archive on Archive selection

2016-01-29 Thread Michael Mikowski via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=340540

Michael Mikowski  changed:

   What|Removed |Added

 CC||z_mikow...@yahoo.com

--- Comment #4 from Michael Mikowski  ---
Confirmed here as well.  Archiving a folder fails for every folder I try on
both active and disabled IMAP accounts.  It doesn't work for Local folders
either.

I too am trying to archive an imap account (Exchange 2008 server - not my
choice :P ) that did NOT have "download messages for offline use" set but is
now defunct.  I want to store whatever information I currently have into an
archive.  Is there any way to do this?  

Interestingly, I was able to copy a second account (Gmail server) with the
exact same settings to a backup folder without difficulty by selecting the
account "folder", e.g. "Gmail", right-clicking, and then selecting  -> Copy
folder to  and then selecting a local backup folder.  When I try that with
the (Exchange) IMAP account, it silently fails.

v5.02 Using:
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

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


[kontact] [Bug 358754] New: Another mailer was found on system. Do you want to import data from it?

2016-01-29 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358754

Bug ID: 358754
   Summary: Another mailer was found on system. Do you want to
import data from it?
   Product: kontact
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kokotokos...@yopmail.fr

Great to know. But *WHICH* other mailer? It wouldn't hurt to say, would it?


Reproducible: Always

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