date:20160128

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

2016-01-28 Thread Michael D via KDE Bugzilla

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

Michael D  changed:

   What|Removed |Added

 CC||nortex...@gmail.com

--- Comment #12 from Michael D  ---
Kubuntu 15.10 with backports, Plasma 5.5.3 and Frameworks 15.18.0 is still on
KMail2 5.0.2, Applications 15.08.2. Can I ask which version of Applications 5.1
ships with? Is it in Applications 15.12.1?

I still have the bug, of course.

-- 
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 358658] .desktop files of agents are read in the incorrect encoding

2016-01-28 Thread Alexey Chernov via KDE Bugzilla

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

Alexey Chernov <4er...@gmail.com> changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/akon |http://commits.kde.org/akon
   |adi/1e164ae8d50b38c36159539 |adi/de588dc7fd459449ccc1d29
   |0543ebdeb45231777   |fb30cee1774837140

--- Comment #4 from Alexey Chernov <4er...@gmail.com> ---
Git commit de588dc7fd459449ccc1d29fb30cee1774837140 by Alexey Chernov.
Committed on 28/01/2016 at 12:00.
Pushed by chernov into branch 'Applications/15.12'.

Fix encoding of reading *.desktop files of Akonadi agents

Explicitly set UTF-8 encoding of QSettings when reading *.desktop
files of agents to prevent any encoding issues. Code parts of string
conversion are also removed as now it's done in QSettings internally.
REVIEW: 126911

M  +3-8src/akonadicontrol/agenttype.cpp

http://commits.kde.org/akonadi/de588dc7fd459449ccc1d29fb30cee1774837140

-- 
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 358682] New: Kontact 5

2016-01-28 Thread Ian via KDE Bugzilla

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

Bug ID: 358682
   Summary: Kontact 5
   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: ianse...@yahoo.co.uk

Application: kontact (5.1.1)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-2-default x86_64
Distribution: "openSUSE Tumbleweed (20160117) (x86_64)"

-- Information about the crash:
i had been reconfiguring elements of this new update from kontact to kontact5
such as email layout, knotes, summary up and coming dates then i pressed exit
via the menu

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

Thread 40 (Thread 0x7fc79be38700 (LWP 15628)):
#0  0x7fc7b6f4324d in poll () from /lib64/libc.so.6
#1  0x7fc7b06b8432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fc7b06ba007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fc79df86e29 in QXcbEventReader::run (this=0x1e4bf00) at
qxcbconnection.cpp:1229
#4  0x7fc7b784b94f in QThreadPrivate::start (arg=0x1e4bf00) at
thread/qthread_unix.cpp:331
#5  0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6

Thread 39 (Thread 0x7fc798ec8700 (LWP 15629)):
#0  0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc7b4ae53bb in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fc7b4ae53f9 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6

Thread 38 (Thread 0x7fc74ffd2700 (LWP 15630)):
#0  0x7fc7afabc4d4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fc7afa78cd9 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fc7afa79208 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fc7afa7936c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fc7b7a7052b in QEventDispatcherGlib::processEvents
(this=0x7fc7480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fc7b7a1a63a in QEventLoop::exec (this=this@entry=0x7fc74ffd1cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fc7b7846b1c in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fc7b784b94f in QThreadPrivate::start (arg=0x1f594e0) at
thread/qthread_unix.cpp:331
#8  0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6

Thread 37 (Thread 0x7fc744054700 (LWP 15631)):
#0  0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc74eade133 in cnd_wait (mtx=0x2013950, cond=0x2013978) at
../../../../include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x2013950) at
../../../../src/gallium/auxiliary/os/os_thread.h:259
#3  thread_function (init_data=init_data@entry=0x20138a8) at lp_rast.c:805
#4  0x7fc74eaddfb7 in impl_thrd_routine (p=) at
../../../../include/c11/threads_posix.h:87
#5  0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6

Thread 36 (Thread 0x7fc743853700 (LWP 15632)):
#0  0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc74eade133 in cnd_wait (mtx=0x2013ab8, cond=0x2013ae0) at
../../../../include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x2013ab8) at
../../../../src/gallium/auxiliary/os/os_thread.h:259
#3  thread_function (init_data=init_data@entry=0x2013a10) at lp_rast.c:805
#4  0x7fc74eaddfb7 in impl_thrd_routine (p=) at
../../../../include/c11/threads_posix.h:87
#5  0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6

Thread 35 (Thread 0x7fc74237b700 (LWP 15633)):
#0  0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc7b47f3764 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fc7b4b14441 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7fc741b5b700 (LWP 15634)):
#0  0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc7b47f4793 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fc7b4b14441 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7fc72feff700 (LWP 15636)):
#0

[Akonadi] [Bug 358658] .desktop files of agents are read in the incorrect encoding

2016-01-28 Thread Alexey Chernov via KDE Bugzilla

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

Alexey Chernov <4er...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/akon
   ||adi/1e164ae8d50b38c36159539
   ||0543ebdeb45231777
 Resolution|--- |FIXED

--- Comment #3 from Alexey Chernov <4er...@gmail.com> ---
Git commit 1e164ae8d50b38c361595390543ebdeb45231777 by Alexey Chernov.
Committed on 28/01/2016 at 11:52.
Pushed by chernov into branch 'master'.

Fix encoding of reading *.desktop files of Akonadi agents

Explicitly set UTF-8 encoding of QSettings when reading *.desktop
files of agents to prevent any encoding issues. Code parts of string
conversion are also removed as now it's done in QSettings internally.
REVIEW: 126911

M  +3-8src/akonadicontrol/agenttype.cpp

http://commits.kde.org/akonadi/1e164ae8d50b38c361595390543ebdeb45231777

-- 
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 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

2016-01-28 Thread Michael D via KDE Bugzilla

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

--- Comment #14 from Michael D  ---
Donovan, you do know you can access the address book by simply clicking the
"Select" button next to the "To/CC/BCC" field and then searching for your
contact that way?

You can also just open kaddressbook, find your contact there, and click their
email address.

It's mildly inconvenient, especially in today's age, but come on, it's not like
it prevents people from working (though it may add up to 3 minutes more to your
work day).

-- 
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 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

2016-01-28 Thread Donovan Hoare via KDE Bugzilla

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

--- Comment #15 from Donovan Hoare  ---
I send 300 emails a day.  And i have 10 support calls a day about it.  My staff
that i FORCE to use linux all day.  (that say cant we use windows)  complain
every day.  Im not a home user.  Im an IT support company.  The main reason i
used kmail is that not even did the last version seach address book.  It also
searched the actual emails.
So yes why dont i just stick with LTS.  Im a qt developer as well and need to
stay current.
There are alotnof other reasons i stay current aswell. 
If you look at my bug reports. I had one about sast time not working.  Someone
didnt fix it for 2 years.  So my calendar entries didnt work properly.  After a
rant it took someone 1 hoir to fix.  I still had to wait 6 months for release.
So 3 mins a day for a normal person is 1 hour for me. 
But thia is not a rant place.  Even though im the one doing it.  Its a please
pretty please fix. And let us know how to test. 






Sent from my Samsung device

 Original message 
From: Michael D via KDE Bugzilla  
Date: 28/01/2016  18:28  (GMT+02:00) 
To: dono...@atstech.co.za 
Subject: [kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows
  recent email addresses but not stored emails in Kaddressbook 

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

--- Comment #14 from Michael D  ---
Donovan, you do know you can access the address book by simply clicking the
"Select" button next to the "To/CC/BCC" field and then searching for your
contact that way?

You can also just open kaddressbook, find your contact there, and click their
email address.

It's mildly inconvenient, especially in today's age, but come on, it's not like
it prevents people from working (though it may add up to 3 minutes more to your
work day).

-- 
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 311633] Kmail2 does not filter by non-ASCII patterns in message body

2016-01-28 Thread via KDE Bugzilla

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

gra...@howlingfrog.com changed:

   What|Removed |Added

 CC||gra...@howlingfrog.com

--- Comment #6 from gra...@howlingfrog.com ---
Bug 345005 sounds similar to this, if not a duplicate.

-- 
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 345005] Filters do not work on the body of the message if the message is in base64

2016-01-28 Thread via KDE Bugzilla

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

gra...@howlingfrog.com changed:

   What|Removed |Added

 CC||gra...@howlingfrog.com

--- Comment #2 from gra...@howlingfrog.com ---
I'm able to replicate this easily.  Most common message that _doesn't_ filter
properly for me and which has a Base64 encoded body, are PayPal payment
notifications.

They used to arrive with:
  Content-Transfer-Encoding: quoted-printable
  Content-Type; text/plain; charset="windows-1252"

and those ones would filter just fine.

The new ones now arrive with:
  Content-Transfer-Encoding: base64
  Content-Type: text/plain; charset=UTF-8

and do *not* match at all with the "Body of Message" filtering rule.

My first guess would be that its trying to match/filter based on the raw
message body, instead of the decoded message body.

-- 
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 358696] New: KF5's kaddressbook crashes when adding a contact that has a birthday

2016-01-28 Thread eric via KDE Bugzilla

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

Bug ID: 358696
   Summary: KF5's kaddressbook crashes when adding a contact that
has a birthday
   Product: Akonadi
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Birthdays Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: pro...@gmx.net

When adding/importing a contact that has a birthday, kaddressbook will crash
immediately and the next times it is started.
This is with Framework-5.18, Akonadi-15.12.1 and Kaddressbook-15.12.1.

Reproducible: Always

Steps to Reproduce:
1. Do 'rm -rf akonadi*' in ~/.kde4, ~/.local/share and ~/.config (or create new
user)
2. Let akonadi create a new database
3. Start kaddressbook and create a new contact with a birthday

Actual Results:  
Kaddressbook will immediately crash after the contact is created and it will
crash the next times it is started.

Expected Results:  
No crash.

This crash only happens when the "Birthdays and Anniversaries" calendar is
enabled. This can be checked in korganizer.

Without this calendar, kaddressbook will not crash when adding a new contact
with a birthday... but it will start crashing when this calendar is enabled
later (for example when "Birthdays and Anniversaries" is added as a new
calendar in korganizer).

-- 
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 358696] KF5's kaddressbook crashes when adding a contact that has a birthday

2016-01-28 Thread Laurent Montel via KDE Bugzilla

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
Backtrace 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 345005] Filters do not work on the body of the message if the message is in base64

2016-01-28 Thread via KDE Bugzilla

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

--- Comment #3 from gra...@howlingfrog.com ---
Bug 311633 sounds similar to this, if not a duplicate.

-- 
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 358707] New: KMail doesn't respect crypto options when replying

2016-01-28 Thread Gareth Williams via KDE Bugzilla

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

Bug ID: 358707
   Summary: KMail doesn't respect crypto options when replying
   Product: kmail2
   Version: 4.14.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: gar...@garethwilliams.me.uk

On a system where GPG and S/MIME certificates are installed and KMail is set to
prefer S/MIME, replying to a plain, GPG or S/MIME email causes KMail to attempt
to use GPG.

Checking Options -> Cryptographic Message Format, shows no radio button
selected whereas it should be S/MIME.  When the Send button is sent, KMail asks
for the passphrase to open the GPG key.

Reproducible: Always

Steps to Reproduce:
1. Reply to plain, GPG or S/MIME email
2. Check Options -> Cryptographic Message Format for S/MIME but you'll see no
radio button selected.
3. Click on Send.

Actual Results:  
KMail attempts to send using GPG signature.

Expected Results:  
KMail should send using S/MIME signature.

Creating a new email works as expected - S/MIME is selected in the cryto
message format setting and the mail is signed using S/MIME.

Workaround is to always remember to check Options->Cyptographic Message Fromat
and change it to S/MIME before sending.

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

[kdepimlibs] [Bug 358669] New: File (icons) collision between kdepimlibs/akonadi-contact and oxygen-icons5

2016-01-28 Thread Elias Probst via KDE Bugzilla

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

Bug ID: 358669
   Summary: File (icons) collision between
kdepimlibs/akonadi-contact and oxygen-icons5
   Product: kdepimlibs
   Version: GIT (master)
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: m...@eliasprobst.eu

The '*-mimetypes-x-mail-distribution-list.png' icon is installed by both:
oxygen-icons5 and kdepimlibs/akonadi-contact.

Their location in the repositories:
oxygen-icons5/*x*/mimetypes/x-mail-distribution-list.png
kdepimlibs/akonadi-contact/src/icons/*-mimetypes-x-mail-distribution-list.png

Result when trying to install akonadi-contact on Gentoo from git master:
 * 
 * Detected file collision(s):
 * 
 *  /usr/share/icons/oxygen/128x128/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/16x16/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/48x48/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/22x22/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/256x256/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/32x32/mimetypes/x-mail-distribution-list.png
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * kde-frameworks/oxygen-icons-:5::kde
 *  /usr/share/icons/oxygen/128x128/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/16x16/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/22x22/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/256x256/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/32x32/mimetypes/x-mail-distribution-list.png
 *  /usr/share/icons/oxygen/48x48/mimetypes/x-mail-distribution-list.png

-- 
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 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

2016-01-28 Thread piedro via KDE Bugzilla

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

--- Comment #11 from piedro  ---
This is Kmail 5.1.1 btw.

-- 
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 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

2016-01-28 Thread Donovan Hoare via KDE Bugzilla

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

--- Comment #13 from Donovan Hoare  ---
I think we will have to suffer until 16.04 is released. Ive switched to gnome
and thunderbird. this is such a big bug. everyone and i mean every linux user
uses email and to not be able to email an address-book contact from the to
line... Really ppl

They have "Fixed" the problem but no one can test it. so if the fix didn’t work
16.04 is out of use aswell.

And linus torvald wanders why we cant get the desktop. Its because users cant
wait this long for this.
Perhaps the admin, for us "stupid" users can explain how we can get the fix now
rather than say it will be there eventually.

Ha ve an awesome day. sorry for the rant but over 6 months i cant work

-- 
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 358679] New: kmail5 crash on reload

2016-01-28 Thread Ian via KDE Bugzilla

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

Bug ID: 358679
   Summary: kmail5 crash on reload
   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: ianse...@yahoo.co.uk

Application: kmail (5.1.1)

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

-- Information about the crash:
I had been using newly installed kmail5, i change config to empty trash on
exit, saved it, exited via File menu.  It crashed on reloading.  i relaoded to
check teh trash was beiung emptied

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

Thread 11 (Thread 0x7fd18b675700 (LWP 32055)):
#0  0x7fd1ad8e024d in poll () from /lib64/libc.so.6
#1  0x7fd1a0916432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fd1a0918007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fd18d39de29 in QXcbEventReader::run (this=0x1067450) at
qxcbconnection.cpp:1229
#4  0x7fd1ae1e894f in QThreadPrivate::start (arg=0x1067450) at
thread/qthread_unix.cpp:331
#5  0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7fd18936d700 (LWP 32068)):
#0  0x7fd1ad8e024d in poll () from /lib64/libc.so.6
#1  0x7fd1a375b264 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd1a375b36c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd1ae40d52b in QEventDispatcherGlib::processEvents
(this=0x7fd17c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fd1ae3b763a in QEventLoop::exec (this=this@entry=0x7fd18936cc90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fd1ae1e3b1c in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fd1ae1e894f in QThreadPrivate::start (arg=0x10ea510) at
thread/qthread_unix.cpp:331
#7  0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7fd16d30f700 (LWP 32091)):
#0  0x7fd1a3c7e07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd19e7813bb in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fd19e7813f9 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7fd114a0d700 (LWP 32099)):
#0  0x7fd1a3c7e07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd19e48f764 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fd19e7b0441 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7fd107fff700 (LWP 32100)):
#0  0x7fd1a3c7e07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd19e490793 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fd19e7b0441 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fd10519e700 (LWP 32122)):
#0  0x7fd1a379e4b9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fd1a375a2d0 in g_main_context_acquire () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fd1a375b135 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fd1a375b36c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fd1ae40d52b in QEventDispatcherGlib::processEvents
(this=0x7fd0f8007400, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fd1ae3b763a in QEventLoop::exec (this=this@entry=0x7fd10519dc90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fd1ae1e3b1c in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fd1ae1e894f in QThreadPrivate::start (arg=0x1716540) at
thread/qthread_unix.cpp:331
#8  0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fd10599f700 (LWP 32124)):
#0  0x7ffe801ce999 in ?? ()
#1  0x7ffe801cecc5 in clock_gettime ()
#2  0x7fd1ad8f57d6 in clock_gettime () from /lib64/libc.so.6
#3  0x7fd1ae2941a6 in qt_clock_gettime (ts=0x7fd10599ea40, clock=) at tools/qelapsedtimer_unix.cpp:105
#4  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#5  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#6  0x7fd1ae40b0e9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x1559cc0) at

[kmail2] [Bug 358679] kmail5 crash on reload

2016-01-28 Thread Ian via KDE Bugzilla

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

--- Comment #1 from Ian  ---
kmail5 does actually load even though it gives this message.  it seems to load
okay if you logout but if you try to reload kmail5 in the same session it gives
the error.  if i unset the empty trash on exit, it doesn't seem to give this
error.  it might be that the error is happening trying to empty the trash.

-- 
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 358679] kmail5 crash on reload

2016-01-28 Thread Ian via KDE Bugzilla

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

--- Comment #2 from Ian  ---
It doesn't empty the trash on exit even when set.  It also says its kmail2 on
the prompt for kwallet access and the bug reporter also logs it as kmail2 even
though the help menu says Version 5.1.1 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

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[Akonadi] [Bug 358658] .desktop files of agents are read in the incorrect encoding

[kontact] [Bug 358682] New: Kontact 5

[Akonadi] [Bug 358658] .desktop files of agents are read in the incorrect encoding

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[Akonadi] [Bug 311633] Kmail2 does not filter by non-ASCII patterns in message body

[kmail2] [Bug 345005] Filters do not work on the body of the message if the message is in base64

[Akonadi] [Bug 358696] New: KF5's kaddressbook crashes when adding a contact that has a birthday

[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday

[kmail2] [Bug 345005] Filters do not work on the body of the message if the message is in base64

[kmail2] [Bug 358707] New: KMail doesn't respect crypto options when replying

[kdepimlibs] [Bug 358669] New: File (icons) collision between kdepimlibs/akonadi-contact and oxygen-icons5

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[kmail2] [Bug 358679] New: kmail5 crash on reload

[kmail2] [Bug 358679] kmail5 crash on reload

[kmail2] [Bug 358679] kmail5 crash on reload

18 matches

Site Navigation

Mail list logo

Footer information