[kmail2] [Bug 378439] KMail - search is "one-shot" only

2017-04-04 Thread Burkhard Lueck 
https://bugs.kde.org/show_bug.cgi?id=378439

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 378450] Crashes immediately after launch

2017-04-04 Thread Laurent Montel 
https://bugs.kde.org/show_bug.cgi?id=378450

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
it's a problem with your distro.
Please report this bug to neon.
Regards

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 378450] New: Crashes immediately after launch

2017-04-04 Thread Ryan McCoskrie 
https://bugs.kde.org/show_bug.cgi?id=378450

Bug ID: 378450
   Summary: Crashes immediately after launch
   Product: kmail2
   Version: 5.4.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: w...@ryanmccoskrie.me
  Target Milestone: ---

Kmail is on screen for just long enough to be seen before it suddenly closes
leaving this message on the command line:

> symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5MessageCore.so.5: 
> undefined symbol: _ZNK5KMime5Types7Mailbox13prettyAddressEv

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 378439] New: KMail - search is "one-shot" only

2017-04-04 Thread Don Curtis 
https://bugs.kde.org/show_bug.cgi?id=378439

Bug ID: 378439
   Summary: KMail - search is "one-shot" only
   Product: kmail2
   Version: 5.3.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: search
  Assignee: kdepim-bugs@kde.org
  Reporter: bugrprt21...@online.de
  Target Milestone: ---

openSUSE Leap 42.2 -- plasma5-workspace: 5.8.6-8.1 (LTS)
Linux (x86_64) release 4.4.57-18.3-default
KMail: Version 5.3.0 (QtWebEngine)
  Under:
   - KDE Frameworks 5.26.0
   - Qt 5.6.1 (compiled against 5.6.1)
   - The xcb window system

Provided that, the "Search" folder does not exist, the Tools menu "Find
messages" function ("S") executes as expected.

Subsequent searches do not execute as expected:
 - The result of the initial "Find messages" execution remains unchanged.

If, by means of "right-click" on the Search results folder, the last search
results are cleared (need to first click on other mail folder before the option
to delete changes from "Delete folder" to "Delete search") -- after noticing
the message indicating that, the original searched for and found e-Mails will
remain at their original location, the original e-Mails are no longer displayed
in the original folder view.

Closing down KMail and then restarting it, restores the display of the
"searched for and found" e-Mails in their respective Mail folders and, a new
"Find messages" search can be executed.

--

The URL for the relevant KMail Handbook entry is:

(It doesn't mention that, the Search folder has to be deleted and, that KMail
has to be closed down and then restarted.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kaddressbook] [Bug 378437] New: lost functionality

2017-04-04 Thread Gerry Gavigan 
https://bugs.kde.org/show_bug.cgi?id=378437

Bug ID: 378437
   Summary: lost functionality
   Product: kaddressbook
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: gerrys...@gmail.com
CC: to...@kde.org
  Target Milestone: ---

This is a problem that has arisen since updating an earlier version of
Tumbleweed (probably about a six month gap)

I can open kaddressbook and send an email to an address list (but only TO, not
CC or BCC)

I can open kmail and select addresses from an addresslist one-by-one as BCC,
CC, TO

However, I cannot auto populate one of the three fields (TO, CC, BCC) in kmail
with an address list - which seems a bit fundamental

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 378436] Instance create job emits result too early

2017-04-04 Thread Daniel Vrátil 
https://bugs.kde.org/show_bug.cgi?id=378436

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 378436] New: Instance create job emits result too early

2017-04-04 Thread Andre Heinecke 
https://bugs.kde.org/show_bug.cgi?id=378436

Bug ID: 378436
   Summary: Instance create job emits result too early
   Product: Akonadi
   Version: GIT (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Account Wizard
  Assignee: kdepim-bugs@kde.org
  Reporter: aheine...@intevation.de
  Target Milestone: ---

Created attachment 104869
  --> https://bugs.kde.org/attachment.cgi?id=104869=edit
Hack to fix racyness

The KMail AccountWizard can fail with: "Could not convert value of setting
'AccountIdentity' to required type."

This happens for me in a fairly slow VM (one core, slow disk). But there
happened very reliably.

The reason appears to be that Accountwizard's Resource::instanceCreateResult is
called too early before the resource is fully created. 

Where:
   QDBusInterface iface(QStringLiteral("org.freedesktop.Akonadi.Resource.") +
m_instance.identifier(), QStringLiteral("/Settings"));

isValid but the interface does not provide all Methods. The debug output
surrounding this is:

org.kde.pim.accountwizard: Setting up  "AccountIdentity"  for agent 
"akonadi_imap_resource_12"
org.kde.pim.accountwizard: Did not find D-Bus method:  "setAccountIdentity"
 available methods are:
org.kde.pim.accountwizard: "destroyed(QObject*)"
org.kde.pim.accountwizard: "destroyed()"
org.kde.pim.accountwizard: "objectNameChanged(QString)"
org.kde.pim.accountwizard: "deleteLater()"
org.kde.pim.accountwizard: "_q_reregisterTimers(void*)"
org.kde.pim.accountwizard:
"_q_serviceOwnerChanged(QString,QString,QString)"

Version does not really match. It was with accountwizard 0.2 from the current
KDE Neon devedition gitstable ( 4:16.12.3+p16.04+git20170310.0110-0 ).

Attached Hack fixes the Problem for me but is of course not a real fix as it
just adds a sleep before accessing the resource interface.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 365753] search results are not updated in the search folder (Last Search)

2017-04-04 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=365753

alessandro.ma...@unimi.it changed:

   What|Removed |Added

 CC||alessandro.ma...@unimi.it

--- Comment #5 from alessandro.ma...@unimi.it ---
I confirm: I get this bug too.

Mint18.1 + neon repo
KMail 5.4.3
KDE Frameworks 5.32.0
Qt 5.7.1

Corresponding collection in mysql db has still the same "queryString" field
value.
Empty queryString value does nothing.
Delete collection in DB or research in Kmail let search work again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 378429] Kontact Welcome screen - visit the web site - Signal: Segmentation fault (11)

2017-04-04 Thread Don Curtis 
https://bugs.kde.org/show_bug.cgi?id=378429

Don Curtis  changed:

   What|Removed |Added

Version|unspecified |5.3.0

--- Comment #1 from Don Curtis  ---
Set the Kontact version in the Bug Report header.
plasma5-workspace version: 5.8.6-8.1 (LTS)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 378429] New: Kontact Welcome screen - visit the web site - Signal: Segmentation fault (11)

2017-04-04 Thread Don Curtis 
https://bugs.kde.org/show_bug.cgi?id=378429

Bug ID: 378429
   Summary: Kontact Welcome screen - visit the web site - Signal:
Segmentation fault (11)
   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: bugrprt21...@online.de
  Target Milestone: ---

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.57-18.3-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
On the welcome screen, clicked the link to the Kontact web site URL.

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

Thread 38 (Thread 0x7f9337d1d700 (LWP 8010)):
#0  0x7f9490495458 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9487ac50c2 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f9487ad2b06 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f9487ad2cf6 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f9487acca2e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f9490490734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f94945a9d3d in clone () at /lib64/libc.so.6

Thread 37 (Thread 0x7f933851e700 (LWP 8009)):
#0  0x7f9490495458 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9487ac50c2 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f9487ad2b06 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f9487ad2cf6 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f9487acca2e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f9490490734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f94945a9d3d in clone () at /lib64/libc.so.6

Thread 36 (Thread 0x7f9338d1f700 (LWP 8008)):
#0  0x7f9490495458 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9487ac50c2 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f9487ad2b06 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f9487ad2cf6 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f9487acca2e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f9490490734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f94945a9d3d in clone () at /lib64/libc.so.6

Thread 35 (Thread 0x7f933a7e7700 (LWP 8007)):
#0  0x7f9490495458 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9487ac50c2 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f9487ad2b06 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f9487ad2cf6 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f9487acca2e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f9490490734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f94945a9d3d in clone () at /lib64/libc.so.6

Thread 34 (Thread 0x7f9344faf700 (LWP 7864)):
#0  0x7f94945a149d in poll () at /lib64/libc.so.6
#1  0x7f948f844314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f948f84442c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f94950d232b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x3b1d1a0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f949507ffdb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f9344faee10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7f9494ebaf1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7f9494ebf9e9 in QThreadPrivate::start(void*) (arg=0x3b255e0) at
thread/qthread_unix.cpp:341
#7  0x7f9490490734 in start_thread () at /lib64/libpthread.so.0
#8  0x7f94945a9d3d in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7f9347077700 (LWP 7858)):
#0  0x7f948f8857b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f948f844205 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f948f84442c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f94950d232b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f933c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f949507ffdb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f9347076e10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7f9494ebaf1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7f9494ebf9e9 in QThreadPrivate::start(void*) (arg=0x389d9a0) at
thread/qthread_unix.cpp:341
#7  0x7f9490490734 in start_thread () at /lib64/libpthread.so.0
#8  0x7f94945a9d3d in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f9355114700 (LWP 7838)):
#0  0x7f94904950af in

[kmail2] [Bug 376589] Layout destroyed after clicking link with HiDPI

2017-04-04 Thread David Faure 
https://bugs.kde.org/show_bug.cgi?id=376589

--- Comment #4 from David Faure  ---
Note: if `kcmshell5 componentchooser` says the webbrowser is firefox, the bug
doesn't happen.
If OTOH it says "based on the contents of the URL" (i.e. KMail uses KIO), then
the bug happens.

That's a workaround for now, and an indication that something in KIO is
triggering it.

-- 
You are receiving this mail because:
You are the assignee for the bug.