[knotes] [Bug 357048] New: knotes 15.12.0 displays contens by black on black and with micro charactiers

[SinClaus via KDE Bugzilla]

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

Bug ID: 357048
   Summary: knotes 15.12.0 displays contens by black on black and
with micro charactiers
   Product: knotes
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: tomsk_interf...@vtomske.ru
CC: myr...@kde.org

After update I see on both boxes (with KDE 4 and KDE 5) black square in place
of my notes.
I can see something only by select area by mouse. All content don't have
reaction about settings.

Reproducible: Always

Steps to Reproduce:
1. Take old installation of Arch
2. Make some notes in a knotes.
3. Update system.

Actual Results:  
Black box.

-- 
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 357064] New: Mail not accessible after migration

[Richard Bos via KDE Bugzilla]

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

Bug ID: 357064
   Summary: Mail not accessible after migration
   Product: Akonadi
   Version: 4.13
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: richard@xs4all.nl

Mail not accessible after migration.  The migration was done after updating
from openSUSE_13.1
to openSUSE_leap

kmail created a new resource called "Local Folders", but the old previous
folders "Kmail folders" were not migrated to the new Local Folders.  Very
frustrating.

After many attempts, using various ways, fortunately having backup arounds, I
started kmail, from the command line.  Kmail finished the migration, spitting
the following line 10 times per second and never stopping:
   Resource id's don't match: "akonadi_maildir_resource_1"
"akonadi_maildir_resource_0"

Looking for this results in this bug report:
   https://bugs.kde.org/show_bug.cgi?id=255104
(Thus that report is still not solved)!  The bugreport points to:
https://forum.kde.org/viewtopic.php?f=215=120777#p308518
Which has the solution.  At the bottom at states:
  https://forum.kde.org/viewtopic.php?f=215=120777#p347175
For me it was sufficient to remove the local trash folder:
rm -rf .local/share/local-mail/trash/

Have this fixed please, because it takes a whole day to work out the problem,
it is frustrating as it looks like old email is no longer accessible, etc.





Reproducible: Always

Steps to Reproduce:
1.  See above
2.
3.

Actual Results:  
Email is no longer accessible!  very bad.

Expected Results:  
Nice smooth migration, and emails always accessible

-- 
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 357066] Konqueror plugin should use standard appearance

[via KDE Bugzilla]

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

--- Comment #1 from danikvas...@gmail.com ---
Version is 5.0.2

-- 
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 357066] New: Konqueror plugin should use standard appearance

[via KDE Bugzilla]

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

Bug ID: 357066
   Summary: Konqueror plugin should use standard appearance
   Product: akregator
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: akregator konqueror plugin
  Assignee: kdepim-bugs@kde.org
  Reporter: danikvas...@gmail.com

The Konqueror plugin uses user color scheme for web content that is retrieved
from RSS feeds, which is hard to use when the theme set is dark.

Reproducible: Always

Steps to Reproduce:
1. Set a dark color scheme KDE-wide
2. Open Akregator
3. Open an RSS feed

-- 
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 357067] New: kmail crashed when configuring appearance

[Richard Bos via KDE Bugzilla]

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

Bug ID: 357067
   Summary: kmail  crashed when configuring appearance
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: richard@xs4all.nl

Application: kmail (4.14.10)
KDE Platform Version: 4.14.10
Qt Version: 4.8.6
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

start kmail
setings
configure kmail
click at appearance
crash

Tried to launch kmail from other users desktops, it always crashed.
While kmail for the other users are not crashing.

Might it have something to do with the (kde4) theme?
If so, how do I change it from kde5?

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f5cb1167700 (LWP 16998)):
#0  0x7f5cce58b05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5cca964eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQtWebKit.so.4
#2  0x7f5cca964ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib64/libQtWebKit.so.4
#3  0x7f5cce5870a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5cd5a4104d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f5c6bdd8700 (LWP 16999)):
#0  0x7f5cce58b05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5cca6d7b3d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib64/libQtWebKit.so.4
#2  0x7f5cca98ca06 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib64/libQtWebKit.so.4
#3  0x7f5cce5870a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5cd5a4104d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f5c6b1d7700 (LWP 17002)):
#0  0x7f5cd5a34ced in read () from /lib64/libc.so.6
#1  0x7f5cbdd6df45 in ?? () from /usr/lib64/tls/libnvidia-tls.so.340.93
#2  0x7f5ccd7acb60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f5ccd76b999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f5ccd76bdf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7f5ccd76bf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f5cd710bfde in QEventDispatcherGlib::processEvents
(this=0x7f5c5c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#7  0x7f5cd70ddd4f in QEventLoop::processEvents
(this=this@entry=0x7f5c6b1d6da0, flags=...) at kernel/qeventloop.cpp:149
#8  0x7f5cd70de045 in QEventLoop::exec (this=this@entry=0x7f5c6b1d6da0,
flags=...) at kernel/qeventloop.cpp:204
#9  0x7f5cd6fdb4df in QThread::exec (this=) at
thread/qthread.cpp:538
#10 0x7f5cd6fddbbf in QThreadPrivate::start (arg=0x26876f0) at
thread/qthread_unix.cpp:349
#11 0x7f5cce5870a4 in start_thread () from /lib64/libpthread.so.0
#12 0x7f5cd5a4104d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f5c69c0a700 (LWP 17005)):
#0  0x7f5cce58b05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5cbfe5b86b in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f5cc0157ee0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f5cbfe5b8a9 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f5cce5870a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5cd5a4104d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5cd87ba840 (LWP 16995)):
[KCrash Handler]
#6  data (this=0x8) at ../../src/corelib/tools/qscopedpointer.h:135
#7  qGetPtrHelper (p=...) at
../../src/corelib/global/qglobal.h:2466
#8  d_func (this=0x0) at widgets/qabstractbutton.h:171
#9  QAbstractButton::setChecked (this=0x0, checked=true) at
widgets/qabstractbutton.cpp:738
#10 0x7f5cd82cb7fd in load (this=0x2e11760) at
/usr/src/debug/kdepim-4.14.10/kmail/configuredialog/configuredialog_p.cpp:82
#11 ConfigModuleWithTabs::load (this=0x2d9e050) at
/usr/src/debug/kdepim-4.14.10/kmail/configuredialog/configuredialog_p.cpp:52
#12 0x7f5cd7bd1839 in KCModule::qt_static_metacall (_o=,
_id=, _a=, _c=) at
/usr/src/debug/kdelibs-4.14.10/build/kdeui/kcmodule.moc:65
#13 0x7f5cd70f749e in QObject::event (this=this@entry=0x2d9e050,
e=e@entry=0x2c3d180) at kernel/qobject.cpp:1231
#14 0x7f5cd64c8cab in QWidget::event (this=0x2d9e050, event=0x2c3d180) at
kernel/qwidget.cpp:8859
#15 0x7f5cd647979c in QApplicationPrivate::notify_helper
(this=this@entry=0x1d92470, receiver=receiver@entry=0x2d9e050,

[kmail2] [Bug 356862] KMail crashes on exit

[Martin Schnitkemper via KDE Bugzilla]

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

--- Comment #6 from Martin Schnitkemper  ---
Has already been patched & fixed for Arch users.

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

[knotes] [Bug 354959] Idea: "always on top" function (or did I miss it?)

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #1 from Holger  ---
With focus on a note, KWin can show the system menu via Keyboard shortcut
Alt+F3. Hidden in a submenu is the always on top command. Also there is a
possibility to define window properties for all windows of an application to
automatically become "always on top".

But I admit, I would love a button in the title bar to facilitate access.

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

[knotes] [Bug 357048] knotes 15.12.0 displays contens by black on black and with micro charactiers

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

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

[knotes] [Bug 352011] No notes after KDE login; knotes must be restarted

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #4 from Holger  ---
For me, knotes toggles between 3 situations:
1. no notes at all
2. showing 9 notes (I suspect these are the most recent only)
3. showing all 40 notes actually stored on disk in
~/.local/share/notes/KNotes/new

1 is default after knotes starts up automatically at login
2 can be created via the settings-dialog there is a refresh button for the
inbox maildir folder
3 appeared after disabling, enabling as per comment 1

New notes are saved to the folder as expected and count on top of the 9. The
difference of 31 notes were restored from backup after suffering from bug
357048 (I manually copy and pasted from the black notes, created new ones for
each and deleted the black boxes).

Knotes terminates normally, I if request it via rightclick, but on unlock /
shutdown of Plasma, there is a segfault each time, if KNotes is still around.

-- 
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 357077] New: kmail5 / Kontact5 crashes on startup

[Erick Jimenez via KDE Bugzilla]

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

Bug ID: 357077
   Summary: kmail5 / Kontact5 crashes on startup
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: eric...@yahoo.com.mx

Application: kmail (5.1)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20151124) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Allways crash every time q¿when starting. I restar akonadi and crash too.

The crash can be reproduced every time.

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

Thread 22 (Thread 0x7fd79e2eb700 (LWP 14138)):
#0  0x7fd7c1b1124d in poll () from /lib64/libc.so.6
#1  0x7fd7b4f3d432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fd7b4f3f007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fd7a0644e29 in QXcbEventReader::run (this=0x1cdcc90) at
qxcbconnection.cpp:1229
#4  0x7fd7c241994f in QThreadPrivate::start (arg=0x1cdcc90) at
thread/qthread_unix.cpp:331
#5  0x7fd7b83554a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fd7c1b19bdd in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7fd7975ef700 (LWP 14139)):
#0  0x7fd7b835dcfc in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x7fd7b8357bb2 in pthread_mutex_lock () from /lib64/libpthread.so.0
#2  0x7fd7b6e5ce90 in ?? () from /usr/lib64/libGL.so.1
#3  0x7fd7b6e6041e in ?? () from /usr/lib64/libGL.so.1
#4  0x7fd7b6e6081b in ?? () from /usr/lib64/libGL.so.1
#5  0x7fd7ac066fc0 in ?? () from /usr/lib64/tls/libnvidia-tls.so.340.96
#6  0x7fd7b7e7a210 in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7fd7b7e37d94 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#8  0x7fd7b7e38208 in ?? () from /usr/lib64/libglib-2.0.so.0
#9  0x7fd7b7e3836c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#10 0x7fd7c263e52b in QEventDispatcherGlib::processEvents
(this=0x7fd798e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#11 0x7fd7c25e863a in QEventLoop::exec (this=this@entry=0x7fd7975eec90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#12 0x7fd7c2414b1c in QThread::exec (this=) at
thread/qthread.cpp:503
#13 0x7fd7c241994f in QThreadPrivate::start (arg=0x1dd5f00) at
thread/qthread_unix.cpp:331
#14 0x7fd7b83554a4 in start_thread () from /lib64/libpthread.so.0
#15 0x7fd7c1b19bdd in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7fd796dee700 (LWP 14140)):
#0  0x7fd7b835dcfc in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x7fd7b8357bb2 in pthread_mutex_lock () from /lib64/libpthread.so.0
#2  0x7fd7b6e5ce90 in ?? () from /usr/lib64/libGL.so.1
#3  0x7fd7b6e6041e in ?? () from /usr/lib64/libGL.so.1
#4  0x7fd7b6e60878 in ?? () from /usr/lib64/libGL.so.1
#5  0x7fd7ac066fd1 in ?? () from /usr/lib64/tls/libnvidia-tls.so.340.96
#6  0x7fd7b7e7a210 in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7fd7b7e37d94 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#8  0x7fd7b7e38208 in ?? () from /usr/lib64/libglib-2.0.so.0
#9  0x7fd7b7e3836c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#10 0x7fd7c263e52b in QEventDispatcherGlib::processEvents
(this=0x7fd7880008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#11 0x7fd7c25e863a in QEventLoop::exec (this=this@entry=0x7fd796dedc90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#12 0x7fd7c2414b1c in QThread::exec (this=) at
thread/qthread.cpp:503
#13 0x7fd7c241994f in QThreadPrivate::start (arg=0x1e03900) at
thread/qthread_unix.cpp:331
#14 0x7fd7b83554a4 in start_thread () from /lib64/libpthread.so.0
#15 0x7fd7c1b19bdd in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fd7965ed700 (LWP 14142)):
#0  0x7fd7b835dd9a in __lll_unlock_wake () from /lib64/libpthread.so.0
#1  0x7fd7b8359121 in __pthread_mutex_unlock_usercnt () from
/lib64/libpthread.so.0
#2  0x7fd7b6e5cb69 in ?? () from /usr/lib64/libGL.so.1
#3  0x7fd7b6e6081b in ?? () from /usr/lib64/libGL.so.1
#4  0x7fd7ac066fc0 in ?? () from /usr/lib64/tls/libnvidia-tls.so.340.96
#5  0x7fd7b7e7a210 in ?? () from /usr/lib64/libglib-2.0.so.0
#6  0x7fd7b7e37d94 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#7  0x7fd7b7e38208 in ?? () from /usr/lib64/libglib-2.0.so.0
#8  0x7fd7b7e3836c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#9  0x7fd7c263e52b in QEventDispatcherGlib::processEvents
(this=0x7fd78c0008e0, flags=...) at 

[kmail2] [Bug 357074] New: add window role to main KMail window

[Andrew Gaydenko via KDE Bugzilla]

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

Bug ID: 357074
   Summary: add window role to main KMail window
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: a...@gaydenko.com

To be able to set advanced behavior to the main KMail window we need to get a
way to filter the window from others KMail-related ones. I guess, adding window
role is the way.

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 356862] KMail crashes on exit

[Freddie Chopin via KDE Bugzilla]

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

--- Comment #7 from Freddie Chopin  ---
Thanks for the heads up - I updated the system and it indeed works fine with
the patches Arch maintainers applied.

-- 
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 357060] New: Import of Thunderbird mails doesn't work

[wodenhof via KDE Bugzilla]

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

Bug ID: 357060
   Summary: Import of Thunderbird mails doesn't work
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: woden...@web.de

When I start the import, I first select mozilla/thunderbird  then choose a
target-folder (why does it have to be a new one when the import software
creates its own anyhow below the new one?). 

Subsequently at all source folders in the .thunderbird folder (in my case
/jwy92t9m.default) are treated as mail folders -- but they are not. In my case
they are abook.mab,  crashes, ImapMail,  pluginreg.dat, storage.sdb,
addons.json ... and some 40 more, which are not mails. The subfolders with the
mails which are there too, are found but can't be opened.

If this is no bug, better i.e. more succinct instructions in the relevant popup
might help, at least I couldn't find the correct handling.

-- 
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 357061] New: Kmail5 crashes on shutdown

[wodenhof via KDE Bugzilla]

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

Bug ID: 357061
   Summary: Kmail5 crashes on shutdown
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: woden...@web.de

Application: kmail (5.1)

Qt Version: 5.5.0
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I clicked on the "X" in the upper right corner or used  + q.

The crash can be reproduced every time.

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

Thread 13 (Thread 0x7f0c5f125700 (LWP 12950)):
#0  0x7f0c80956c1d in poll () from /lib64/libc.so.6
#1  0x7f0c73e2f422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f0c73e3100f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f0c60e4fc29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f0c8126455f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f0c771060a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f0c8095f04d in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f0c5cfee700 (LWP 12951)):
#0  0x7f0c80952ced in read () from /lib64/libc.so.6
#1  0x7f0c76c2ab60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f0c76be in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f0c76be9df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f0c76be9f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f0c81495a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f0c8143ca63 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f0c8125f84a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f0c8126455f in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f0c771060a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f0c8095f04d in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f0c40f6e700 (LWP 12967)):
#0  0x7f0c7710a05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0c71c864a3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f0c71c864c9 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f0c771060a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0c8095f04d in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f0becf8d700 (LWP 12968)):
#0  0x7f0c7710a05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0c379f9ff3 in ?? () from /usr/lib64/dri/radeonsi_dri.so
#2  0x7f0c379f9777 in ?? () from /usr/lib64/dri/radeonsi_dri.so
#3  0x7f0c771060a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0c8095f04d in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f0bdbdf8700 (LWP 12978)):
#0  0x7f0c7710a05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0c719924cd in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f0c71cb4da1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f0c771060a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0c8095f04d in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f0bdb5f7700 (LWP 12979)):
#0  0x7f0c7710a05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0c719934a3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f0c71cb4da1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f0c771060a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0c8095f04d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f0bdadf6700 (LWP 12980)):
#0  0x7f0c7710a05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0c719934a3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f0c71cb4da1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f0c771060a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0c8095f04d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f0bda5f5700 (LWP 12981)):
#0  0x7f0c7710a05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0c719934a3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f0c71cb4da1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f0c771060a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0c8095f04d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f0bd9df4700 (LWP 12982)):
#0  0x7f0c7710a05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0c719934a3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f0c71cb4da1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f0c771060a4 in start_thread 

[kmail2] [Bug 357086] New: Maximum Number of connections error break imap ressource

[sederic via KDE Bugzilla]

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

Bug ID: 357086
   Summary: Maximum Number of connections error break imap
ressource
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sebastian.end...@online.de

I have one imap account which often breaks and showing up this dialogue:

"""
The server for account "$Account" refused the supplied username and password.
Do you want to go to the settings, have another attempt at logging in, or do
nothing?

Login failed, server replied: A03 NO Maximum number of connections from
user+IP exceeded ( mail_max_userip_connections=10 ) [ UNAVAILABLE  ]
"""

When hitting "Try again" I will be asked for my password (which is correct) and
then this dialogue comes again.
I also can go to "Account settings" but I think everything is correct there.
When hitting "Cancel" I can see a notification:

"Ressource $Account is broken"

Reproducible: Sometimes



Expected Results:  
Kmail should limit the count of connections to one server when it receives this
answer from server.

-- 
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 357031] Messages reappear or duplicate on moving or deleting in kmail version 15.12

[Wolfgang Mader via KDE Bugzilla]

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

--- Comment #1 from Wolfgang Mader  ---
The protocol used is imap4 over ssl.

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

[Akonadi] [Bug 357031] New: Messages reappear or duplicate on moving or deleting in kmail version 15.12

[Wolfgang Mader via KDE Bugzilla]

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

Bug ID: 357031
   Summary: Messages reappear or duplicate on moving or deleting
in kmail version 15.12
   Product: Akonadi
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: wolfgang_ma...@brain-frog.de
CC: kdepim-bugs@kde.org, vkra...@kde.org

I experienced the described issue for all akonadi/kmail versions which are
ported to frameworks.

The system I am using is Arch with the following (relevant) packages installed
- plasma-desktop: 5.5.1
- plasma-framework: 5.17
- framework components 5.17
- kde applications: 15.12, including kmail and akonadi

Moreover, as a dependency of digikam, the following kde 4 stuff is there
- kdebase-runtime: 15.12
- kdebase-lib: 15.12
- kdepimlibs4: 4.14.10
- libkipi4: 15.08
- libakonadi-qt4: 1.13.0
- libbaloo4: 4.14.3

I configure two generic imap resource in kmail. The first points to the mail
server of my 
university, the second to the one of my web provider. I do not know what imap
server they are 
running, but likely they are running different software. Thus, I guess, the
issue is not with the 
server but with the client side. I do not configure anything special like
server side subscription 
or sieve script.

On initial population of the mailboxes, everything seem fine. All messages are
there and readable. 
The trouble starts as soon as I start to move around mails manually or via
kmail filters or delete 
messages. Say, I move a message from the Inbox to the Private folder. The
message disappears in the 
Inbox and seems to be moved to Privat. However, the message is not really
moved. I is still in the 
Inbox and reappears the next time kmail refreshes the Inbox. The mail is grayed
in the 
Inbox (everything is good with the messages in Private). In the Inboxr, I can
not click on it, move 
or delete it. It just sits there, grayed out, not touchable. Now, using the web
interface of 
my universities mail system, the mail is marked as deleted in the Inbox, but
still there. At least, 
using the web interface, I can select the massage and delete it for real. Then,
also in kmail, the 
message disappears. Unfortunately, I can not properly name the state of the
deleted message in 
"imap"-terms.

On top of this issue, moved messages start to appear in the target folder
multiple times. There is 
always one instance of the message which is clickable and good, but with time,
multiple grayed out
versions start to accumulate. They seem to be in the same state as the moved
one in the source 
folder.

If there is any more information I can provide, do not hesitate to drop me a
mail.

Reproducible: Always

Steps to Reproduce:
1. Create a Imap resource in framework based kmail
2. Move or delete messages
3. Refresh mailbox and observe grayed out, uncklickable messages

Actual Results:  
Messages are not moved or deleted from mailbox.

Expected Results:  
Messages should be moved or deleted from mailbox.

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

[Akonadi] [Bug 325224] CalDav doesn't read server items

[Metko via KDE Bugzilla]

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

Metko  changed:

   What|Removed |Added

 CC||metkome...@gmail.com

--- Comment #37 from Metko  ---
I'm observing the behavior described in the original bugreport with Owncloud
(8.1) as a CalDAV source: Creating events in KOrganizer shows them in
KOrganizer and the Owncloud calendar (so writing the akonadi resource works),
but events created in the Owncloud calendar are not propagated back to
KOrganizer (reading doesn't work). On opensuse 13.2 and KOrganizer 4.14 there
was an error message popping up every 5 mins saying there was an error reading
from the CalDAV resource, but now on Leap42.1 with KF5 there's not even a
message, and reading still doesn't work.
What makes KOrganizer now really problematic is that when I export the calendar
from Owncloud to an .ics file, KOrganizer doesn't show it either. There's no
problem reported during the import, but it simply doesn't show any events
thereafter.
The whole setup worked with older versions of Owncloud; therefore, it may be
that something changed in the way it sends data via CalDAV. But since so many
other people report problems here with other CalDAV sources, there may be a bug
in the read-function of KOrganizer's DAV groupware ressource as well.
CardDAV-communication with my Owncloud server works without any problems.

-- 
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 357031] Messages reappear or duplicate on moving or deleting in kmail version 15.12

[Wolfgang Mader via KDE Bugzilla]

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

Wolfgang Mader  changed:

   What|Removed |Added

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

--- Comment #2 from Wolfgang Mader  ---


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

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

[kmail] [Bug 95064] Duplicates messages in imap folder after filtering

[Wolfgang Mader via KDE Bugzilla]

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

Wolfgang Mader  changed:

   What|Removed |Added

 CC||Wolfgang_Mader@brain-frog.d
   ||e

--- Comment #91 from Wolfgang Mader  ---
*** Bug 357031 has been marked as a duplicate of this 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

[kmail] [Bug 95064] Duplicates messages in imap folder after filtering

[Wolfgang Mader via KDE Bugzilla]

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

--- Comment #92 from Wolfgang Mader  ---
I filed https://bugs.kde.org/show_bug.cgi?id=357031 and after seeing this one
marked is as douplicate.

By the way, what does status "RESOLVED UNMAINTAINED" mean?

-- 
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 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||yyc1...@gmail.com

--- Comment #13 from Christoph Feck  ---
*** Bug 356978 has been marked as a duplicate of this 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 356978] Clicking any article cause all articles to be set to read when only unread articles are shown.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[kmail] [Bug 95064] Duplicates messages in imap folder after filtering

[Graeme Hewson via KDE Bugzilla]

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

--- Comment #93 from Graeme Hewson  ---
See comment 87. This bug report was filed against Kmail version 1, which is
unmaintained, so it's been closed. "UNRESOLVED UNMAINTAINED" would be more
accurate. :-(

I suggest you find a more recent report for the problem (there are several),
e.g., bug 283682. Note this was filed against Akonadi, which is the component
which does the filtering.

-- 
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 357069] New: KMail5 Crashes on exit

[via KDE Bugzilla]

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

Bug ID: 357069
   Summary: KMail5 Crashes on exit
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: a.skemb...@gmail.com

Application: kmail (5.1)

Qt Version: 5.5.0
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

Closed KMail5's window, right clicked on tray icon, clicked quit.

The crash can be reproduced every time.

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

Thread 14 (Thread 0x7fa645816700 (LWP 4397)):
#0  0x7fa6670a6c1d in poll () at /lib64/libc.so.6
#1  0x7fa65a574422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fa65a57600f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fa647540c29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fa6679b455f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fa65d84c0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fa6670af04d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fa63f5ef700 (LWP 4402)):
#0  0x7fa6670a6c1d in poll () at /lib64/libc.so.6
#1  0x7fa65d32fe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fa65d32ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa667be5a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fa667b8ca63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa6679af84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fa6679b455f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fa65d84c0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fa6670af04d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fa62d561700 (LWP 4431)):
#0  0x7fa65d85005f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa6583cb4a3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fa6583cb4c9 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fa65d84c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fa6670af04d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fa5e57a0700 (LWP 4434)):
#0  0x7fa65d85005f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa5ec228ff3 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7fa5ec228777 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7fa65d84c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fa6670af04d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fa5e1e0c700 (LWP 4440)):
#0  0x7fa65d85005f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa6580d74cd in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fa6583f9da1 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fa65d84c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fa6670af04d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fa5e160b700 (LWP 4441)):
#0  0x7fa65d85005f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa6580d84a3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fa6583f9da1 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fa65d84c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fa6670af04d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fa5e0e0a700 (LWP 4442)):
#0  0x7fa65d85005f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa6580d84a3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fa6583f9da1 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fa65d84c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fa6670af04d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fa5dbfff700 (LWP 4443)):
#0  0x7fa65d85005f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa6580d84a3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fa6583f9da1 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fa65d84c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fa6670af04d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fa5db7fe700 (LWP )):
#0  0x7fa65d85005f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa6580d84a3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fa6583f9da1 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fa65d84c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fa6670af04d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fa5daffd700 (LWP 4445)):
#0  0x7fa65d85005f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa6580d84a3 in  () at /usr/lib64/libQt5WebKit.so.5
#2