[kontact] [Bug 430790] New: Kontact crashes randomly at start

2020-12-24 Thread Taner
https://bugs.kde.org/show_bug.cgi?id=430790

Bug ID: 430790
   Summary: Kontact crashes randomly at start
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@paclabs.nl
  Target Milestone: ---

Application: kontact (5.16.0 (20.12.0))

Qt Version: 5.15.2
Frameworks Version: 5.77.0
Operating System: Linux 5.9.14-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

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

Quite often when I start Kontact I receive a crash notification on my desktop.
In some cases there is no new window and I need to relaunch Kontact to use it
and in some cases Kontact window still show up after crash notification and I
can use it as normal. It seems like akkregator session is in all cases crashed
and needs to be restored or dismissed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault

[KCrash Handler]
#4  std::__atomic_base::load(std::memory_order) const
(__m=std::memory_order_relaxed, this=Python Exception 
Cannot access memory at address 0x7f940114: 
#5  QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=Python
Exception  Cannot access memory at address
0x7f940114: 
#6  QBasicAtomicInteger::loadRelaxed() const (this=Python Exception  Cannot access memory at address 0x7f940114: 
#7  QtPrivate::RefCount::isShared() const (this=Python Exception  Cannot access memory at address 0x7f940114: 
#8  QList::append(QWidget* const&) (this=0x7f940114,
t=@0x7ffd83189730: 0x5576abfec820) at
../../include/QtCore/../../src/corelib/tools/qlist.h:622
#9  0x7f94fdae0bc0 in QWidget::insertAction(QAction*, QAction*)
(this=this@entry=0x5576abfec820, before=, before@entry=0x0,
action=0x55769b8a7820) at kernel/qwidget.cpp:3129
#10 0x7f94fe2a3f0b in KXMLGUI::ActionList::plug(QWidget*, int) const
(index=, container=0x5576abfec820, this=0x5576b41d9b40) at
/usr/src/debug/kxmlgui-5.77.0-1.1.x86_64/src/kxmlguifactory_p.cpp:32
#11 KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&,
QTypedArrayData::iterator const&)
(mergingIdxIt=, mergingIdxIt=..., state=...,
this=0x5576b45d4630) at
/usr/src/debug/kxmlgui-5.77.0-1.1.x86_64/src/kxmlguifactory_p.cpp:221
#12 KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&)
(this=0x5576b45d4630, state=...) at
/usr/src/debug/kxmlgui-5.77.0-1.1.x86_64/src/kxmlguifactory_p.cpp:191
#13 0x7f94fe2a3f91 in
KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&)
(this=0x55769bb84290, state=...) at
/usr/src/debug/kxmlgui-5.77.0-1.1.x86_64/src/kxmlguifactory_p.cpp:195
#14 0x7f94fe2a3f91 in
KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&)
(this=0x55769ba0, state=...) at
/usr/src/debug/kxmlgui-5.77.0-1.1.x86_64/src/kxmlguifactory_p.cpp:195
#15 0x7f94fe2ab311 in KXMLGUIFactory::plugActionList(KXMLGUIClient*,
QString const&, QList const&) (this=0x5576acad1550,
client=0x5576a5b566b0, name=..., actionList=...) at
/usr/src/debug/kxmlgui-5.77.0-1.1.x86_64/src/kxmlguifactory.cpp:563
#16 0x7f94a0b03d90 in
PimCommon::PluginInterface::initializePluginActions(QString const&,
KXMLGUIClient*) (this=0x7ffd83189a78, prefix=..., guiClient=0x5576a5b566b0) at
/usr/src/debug/pimcommon-20.12.0-1.1.x86_64/src/pimcommonakonadi/genericplugins/plugininterface.cpp:157
#17 0x7f94a14f28e0 in KMMainWidget::initializePluginActions()
(this=0x5576aa829e20) at
/usr/src/debug/kmail-20.12.0-1.1.x86_64/src/kmmainwidget.cpp:4191
#18 0x7f94a168c865 in
KMailPart::guiActivateEvent(KParts::GUIActivateEvent*) (e=,
this=0x5576a5b56680) at
/usr/src/debug/kmail-20.12.0-1.1.x86_64/src/kmail_part.cpp:116
#19 KMailPart::guiActivateEvent(KParts::GUIActivateEvent*)
(this=0x5576a5b56680, e=0x7ffd83189b20) at
/usr/src/debug/kmail-20.12.0-1.1.x86_64/src/kmail_part.cpp:108
#20 0x7f94fcf261ef in QObject::event(QEvent*) (this=0x5576a5b56680,
e=0x7ffd83189ca0) at kernel/qobject.cpp:1336
#21 0x7f94fdaaa50f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5576a5b56680, e=0x7ffd83189ca0) at
kernel/qapplication.cpp:3632
#22 0x7f94fcefa28a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5576a5b56680, event=0x7ffd83189ca0) at
kernel/qcoreapplication.cpp:1063
#23 0x7f94fc6f9f2f in KParts::MainWindow::createGUI(KParts::Part*)
(this=0x5576a5a16e10, part=0x5576a5b56680) at
/usr/src/debug/kparts-5.77.0-1.1.x86_64/src/mainwindow.cpp:108
#24 0x7f94fe32662a in
Kontact::MainWindow::selectPlugin(KontactInterface::Plugin*)
(this=0x5576a5a16e10, plugin=) at
/usr/src/debug/kontact-20.12.0-1.1.x86_64/src/mainwindow.cpp:662
#25 0x7f94fcf308a0 in doActivate(QObject*, int, void**)
(sender=0x557696510cb0, 

[kontact] [Bug 430789] New: Contact group handling needs improvement / sorting

2020-12-24 Thread Axel Braun
https://bugs.kde.org/show_bug.cgi?id=430789

Bug ID: 430789
   Summary: Contact group handling needs improvement / sorting
   Product: kontact
   Version: 5.16.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: contacts
  Assignee: kdepim-bugs@kde.org
  Reporter: axel.br...@gmx.de
  Target Milestone: ---

When working with a contact group, there is no way to search for a single
contact (CRTL-F) or to sort by Name or Email.

This makes managing of large contact lists merely impossible!

Please add a sort and/or search function!
Thank you!

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

[kontact] [Bug 430788] New: Contact groups: 'Name' searches in Email instead of name

2020-12-24 Thread Axel Braun
https://bugs.kde.org/show_bug.cgi?id=430788

Bug ID: 430788
   Summary: Contact groups: 'Name' searches in Email instead of
name
   Product: kontact
   Version: 5.16.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: contacts
  Assignee: kdepim-bugs@kde.org
  Reporter: axel.br...@gmx.de
  Target Milestone: ---

When adding a contact to a contact group, and one enters something in 'Name',
contact proposes an email address. If the name does not by chance match the
mail address, nothing is found.
Example: John Doe 
give no result when entering 'Joe' in 'Name' column. 

Expected result: When entering a Name, contact should search in the names, not
in the emails

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

[kmail2] [Bug 430787] New: When moving an email into a subfolder on KDE Plasma Wayland the context menu does not appear at the target subfolder

2020-12-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=430787

Bug ID: 430787
   Summary: When moving an email into a subfolder on KDE Plasma
Wayland the context menu does not appear at the target
subfolder
   Product: kmail2
   Version: 5.15.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: pug...@yahoo.de
  Target Milestone: ---

SUMMARY
This of course is misleading because of the expression [move|copy] "here" twice
in the options, as they do not match the place they are referring to.

OBSERVED RESULT
On KDE Plasma Wayland: Drag and drop an email into a subfolder. A context menu
appears to choose whether to move here, copy here or cancel. This context menu
appears where the email was located before/where it was clicked to drag it into
the target folder.

EXPECTED RESULT
The menu should appear at the target folder instead, where the mouse button is
released.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.2

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

[Akonadi] [Bug 349696] Akonadi/KF5 hit assert while running in background

2020-12-24 Thread Andreas Cord-Landwehr
https://bugs.kde.org/show_bug.cgi?id=349696

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #4 from Andreas Cord-Landwehr  ---
Thanks for cleaning up the old reports!
Since I did not see this assert over the last few years, let's close it.

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

[kmail2] [Bug 430780] New: With multiple identity, reply doesn't check or use the right one

2020-12-24 Thread Bruno Friedmann
https://bugs.kde.org/show_bug.cgi?id=430780

Bug ID: 430780
   Summary: With multiple identity, reply doesn't check or use the
right one
   Product: kmail2
   Version: 5.15.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-bugs@kde.org
  Reporter: br...@ioda-net.ch
  Target Milestone: ---

SUMMARY
When you have several (for example 2 identities for one account) when you reply
to a message received for identity B, it always use the default.

STEPS TO REPRODUCE
1. Create two identities for one email account, domain A.org and B.org are
aliases and you have 2 email: a...@a.org and b...@b.org both using the same 
account
on your server. a...@a.org is the main default email for that account
2. Write a mail and send it with b...@b.org (selecting this identity in 
composer)
ask your recipient to reply to it.
3. When you receive the reply, you want also to reply. The composer will use
the a...@a.org indentity even if the mail is addressed to b...@b.org

OBSERVED RESULT
The wrong identity is used.

EXPECTED RESULT
If matching use the right identity, when multiple identity exist, by default.


SOFTWARE/OS VERSIONS
Linux 5.9.14-1-default x86_64 GNU/Linux, nvidia: 460.27.04
Qt: 5.15.2, KDE Frameworks: 5.77.0, Plasma: 5.20.4, kmail2 5.15.3 (20.08.3)

ADDITIONAL INFORMATION

Bonus point, if you start your reply and change whatever character in subject
or body, changing identity afterwards will not apply the Signature of the new
choosed identity.

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

[kontact] [Bug 374945] kontact crash after closing

2020-12-24 Thread d-sha
https://bugs.kde.org/show_bug.cgi?id=374945

d-sha  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #4 from d-sha  ---
Hi,

I had completely forgotten about this bug and because of its age i am unable to
test.
I believe it to be fixed or irrelevant to current version

Thanks

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