[kmail2] [Bug 344270] kmail crashed on restart

2015-03-13 Thread Lastique
https://bugs.kde.org/show_bug.cgi?id=344270

Lastique  changed:

   What|Removed |Added

 CC||andy...@mail.ru

--- Comment #1 from Lastique  ---
Application: kmail (4.14.1)
KDE Platform Version: 4.14.1
Qt Version: 4.8.6
Operating System: Linux 3.16.0-31-generic x86_64
Distribution: Ubuntu 14.10

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

I set to display HTML message bodies for a contact and restarted Kmail. The
crash occurred on restart.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1177301900 (LWP 8153))]

Thread 6 (Thread 0x7f114da4b700 (LWP 8158)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1168f2881d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f1168f28859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f1171eba0a5 in start_thread (arg=0x7f114da4b700) at
pthread_create.c:309
#4  0x7f11745facfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7f110c89e700 (LWP 8159)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1168c6920d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f1168f57fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f1171eba0a5 in start_thread (arg=0x7f110c89e700) at
pthread_create.c:309
#4  0x7f11745facfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f110799e700 (LWP 8160)):
#0  g_mutex_unlock (mutex=0x7f1109a0) at
/build/buildd/glib2.0-2.42.1/./glib/gthread-posix.c:1349
#1  0x7f116c563dfe in g_main_context_iterate
(context=context@entry=0x7f1109a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:3759
#2  0x7f116c563ffc in g_main_context_iteration (context=0x7f1109a0,
may_block=1) at /build/buildd/glib2.0-2.42.1/./glib/gmain.c:3842
#3  0x7f1174f9404e in QEventDispatcherGlib::processEvents
(this=0x7f1108c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f1174f654f1 in QEventLoop::processEvents
(this=this@entry=0x7f110799dce0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f1174f65805 in QEventLoop::exec (this=this@entry=0x7f110799dce0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f1174e63c39 in QThread::exec (this=) at
thread/qthread.cpp:538
#7  0x7f1174e6639f in QThreadPrivate::start (arg=0x1c0e4d0) at
thread/qthread_unix.cpp:349
#8  0x7f1171eba0a5 in start_thread (arg=0x7f110799e700) at
pthread_create.c:309
#9  0x7f11745facfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f1105713700 (LWP 8161)):
#0  0x7f11745f084d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f116c563ee4 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f10f8003210, timeout=-1, context=0x7f10f80009a0) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:4076
#2  g_main_context_iterate (context=context@entry=0x7f10f80009a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:3776
#3  0x7f116c563ffc in g_main_context_iteration (context=0x7f10f80009a0,
may_block=1) at /build/buildd/glib2.0-2.42.1/./glib/gmain.c:3842
#4  0x7f1174f9404e in QEventDispatcherGlib::processEvents
(this=0x7f10f80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x7f1174f654f1 in QEventLoop::processEvents
(this=this@entry=0x7f1105712ca0, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f1174f65805 in QEventLoop::exec (this=this@entry=0x7f1105712ca0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f1174e63c39 in QThread::exec (this=this@entry=0x22acad0) at
thread/qthread.cpp:538
#8  0x7f1174f47033 in QInotifyFileSystemWatcherEngine::run (this=0x22acad0)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7f1174e6639f in QThreadPrivate::start (arg=0x22acad0) at
thread/qthread_unix.cpp:349
#10 0x7f1171eba0a5 in start_thread (arg=0x7f1105713700) at
pthread_create.c:309
#11 0x7f11745facfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f10fee11700 (LWP 8013)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f116030bc8a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f116030bcb9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f1171eba0a5 in start_thread (arg=0x7f10fee11700) at
pthread_create.c:309
#4  0x7f11745facfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f1177301900 (LWP 8153)):
[KCrash Hand

[kmail2] [Bug 345119] New: KMail doesn't show Spam/Ham Buttons

2015-03-13 Thread hotze
https://bugs.kde.org/show_bug.cgi?id=345119

Bug ID: 345119
   Summary: KMail doesn't show Spam/Ham Buttons
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: ho...@openmailbox.org

I try to get Buttons to mark a mail to Spam or No-Spam (Ham).
I put them into the Toolbar (kmmainwin) an it works fine - until i do a restart
of kmail.
After a restart the Buttons ar not shown - but there are still in the
kmmainwin-Toolbar.

It happend every time.

Reproducible: Always

Steps to Reproduce:
1. Put the Buttons in the Toolbar (kmmainwin) - it works
2. Restart kmail
3. No Buttons shown, but still in list.
4. Put them out of the list, restart, put them again in the list  see step
2

Actual Results:  
The Buttons are in the List, but not in the Toolbar

-- 
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 345119] KMail doesn't show Spam/Ham Buttons

2015-03-13 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=345119

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
How did you  add them ?
Could you explain each step please ?

-- 
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 345119] KMail doesn't show Spam/Ham Buttons

2015-03-13 Thread hotze
https://bugs.kde.org/show_bug.cgi?id=345119

--- Comment #2 from ho...@openmailbox.org ---
yes sure
1) Right click on the Toolbar (top Toolbar, with New Message Icon, Print ...)
2) Configure Toolbars
3) That show the Window "Configure Toolbars - Kontact"
On the List are the different Toolbars, i chose Main Toolbar 
Then i put the "Available actions" from the left side to the right side
"Current actions".

Hope it's helpfully

-- 
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 319212] kmail doesn´t show all the mails that are in the folder, while Akonadiconsole does

2015-03-13 Thread Dirk Melcher
https://bugs.kde.org/show_bug.cgi?id=319212

--- Comment #26 from Dirk Melcher  ---
Hallo Till,

thank you for the hint. I don't know if a newer version of kmail ist available 
for OpenSuse 13.1.

Am Donnerstag, 12. März 2015, 21:49:18 schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=319212
> 
> --- Comment #25 from Till Schäfer  ---
> I forgot to mention that my working version is 4.14.6 and akonadi server
> 1.13.
> 
> @Dirk: That 4.11.x version was also affected at my computer. So maybe you
> should update to a newer version.

-- 
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 336417] Akregator crashes when being closed

2015-03-13 Thread Thomas Tanghus
https://bugs.kde.org/show_bug.cgi?id=336417

Thomas Tanghus  changed:

   What|Removed |Added

 CC||tho...@tanghus.net

--- Comment #30 from Thomas Tanghus  ---
(In reply to richardlm from comment #29)
> @diego
> Please see the bug description. This was fixed in Version 4.14.3 (and the
> fix works).
> 
> So please update your software or ask you sysadmin to do so.

I can see the fix is back from January. Any idea when this will hit the Kubuntu
PPA or Kubuntu Backports?

-- 
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 336417] Akregator crashes when being closed

2015-03-13 Thread Thomas Tanghus
https://bugs.kde.org/show_bug.cgi?id=336417

--- Comment #31 from Thomas Tanghus  ---
Besides that: Does Akregator have a maintainer at all? I've been very happy
with it for many years, but now it has just stalled, and the bugs keep piling
up.

My C++/Qt "skills" are pre-millenium change, so I'm afraid I can't take the
torch myself :P

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