[akregator] [Bug 405947] New: Can not bind Numpad Enter to an action

[bugzilla_noreply]

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

Bug ID: 405947
   Summary: Can not bind Numpad Enter to an action
   Product: akregator
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: pawel.vese...@gmail.com
  Target Milestone: ---

SUMMARY

Version 5.10.2
Fedora 29 distro

STEPS TO REPRODUCE
1. Open Settings->Configure Shortcuts
2. Try to configure an action to open on KPEnter (I wanted it to open the
article in a browser)

OBSERVED RESULT
Upon pressing KPEnter for input, it shows "Numpad Enter, + ...", expecting some
next key to be pressed, as if it's a modifier. No other bindings exist for
KPEnter.

EXPECTED RESULT
Binding to KPEnter should work as normal as for any other key.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 28
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.55
Qt Version: 5.11.3

ADDITIONAL INFORMATION

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

[kmail2] [Bug 380171] KMail crash on first start

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #8 from Daniel Vrátil  ---
I think this is a race condition in the initial setup: the race could be that
on first start the Maildir resource (that backs the "Local folders") starts
discovering what folders exist in ~/.local/share/mail and starts creating them
in Akonadi and at the same time KMail realizes there's no Inbox, Outbox etc. in
Local Folders and starts creating them.

At some point they clash as they both attempt to create the same collection -
one of them wins and one of them fails with the SQL error - if KMail is the one
who loses, it aborts the initial job and triggers the "fatal error" dialog.

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

[kmail2] [Bug 380171] KMail crash on first start

[Rik Mills]

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

--- Comment #7 from Rik Mills  ---
Creating the ~/.config/specialmailcollectionsrc file with its default content
of:

[SpecialCollections]
DefaultResourceId=akonadi_maildir_resource_0

prior to 1st launch prevents the crash, but I don't know if that would
adversely affect the running of Kmail after that.

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

[kmail2] [Bug 380171] KMail crash on first start

[Rik Mills]

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

--- Comment #6 from Rik Mills  ---
Ubuntu Bug: https://bugs.launchpad.net/kmail/+bug/1821868

Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861960

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

[Akonadi] [Bug 405922] New: Very frequent akonadi crash

[Piotr Belniak]

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

Bug ID: 405922
   Summary: Very frequent akonadi crash
   Product: Akonadi
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: beln...@gmail.com
  Target Milestone: ---

Application: akonadiserver (5.10.3)

Qt Version: 5.12.0
Frameworks Version: 5.56.0
Operating System: Linux 4.18.0-16-generic x86_64
Distribution: KDE neon User Edition 5.15

-- Information about the crash:
I can't reproduce it, but it happens few (10 - 20) times a day - since latest
KDE frameworks update.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f60f4f59800 (LWP 12676))]

Thread 16 (Thread 0x7f60397fa700 (LWP 13068)):
#0  0x7f60f2bdabf9 in __GI___poll (fds=0x7f601c003ce0, nfds=1,
timeout=85481) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f60efd7b539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f60efd7b64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f60f373515b in QEventDispatcherGlib::processEvents
(this=0x7f601c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f60f36d664a in QEventLoop::exec (this=this@entry=0x7f60397f99a0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x564e71b5db41 in Akonadi::Server::Connection::handleIncomingData
(this=0x564e73581ee0) at ./src/server/connection.cpp:212
#6  0x7f60f3714d04 in QtPrivate::QSlotObjectBase::call (a=0x7f60397f9a10,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#7  QSingleShotTimer::timerEvent (this=0x7f601c005a10) at kernel/qtimer.cpp:318
#8  0x7f60f370894b in QObject::event (this=0x7f601c005a10, e=) at kernel/qobject.cpp:1271
#9  0x7f60f36d8311 in doNotify (event=0x7f60397f9b50,
receiver=0x7f601c005a10) at kernel/qcoreapplication.cpp:1151
#10 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1137
#11 QCoreApplication::notifyInternal2 (receiver=0x7f601c005a10,
event=0x7f60397f9b50) at kernel/qcoreapplication.cpp:1061
#12 0x7f60f37345a9 in QTimerInfoList::activateTimers (this=0x7f601c005120)
at kernel/qtimerinfo_unix.cpp:643
#13 0x7f60f3734d71 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:182
#14 0x7f60efd7b387 in g_main_context_dispatch () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7f60efd7b5c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7f60efd7b64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7f60f373513f in QEventDispatcherGlib::processEvents
(this=0x7f601c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#18 0x7f60f36d664a in QEventLoop::exec (this=this@entry=0x7f60397f9da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#19 0x7f60f34fe41a in QThread::exec (this=) at
thread/qthread.cpp:531
#20 0x7f60f34ffbc2 in QThreadPrivate::start (arg=0x7f606c047fd0) at
thread/qthread_unix.cpp:361
#21 0x7f60f17386db in start_thread (arg=0x7f60397fa700) at
pthread_create.c:463
#22 0x7f60f2be788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f6039ffb700 (LWP 12924)):
#0  0x7f60f2bdabf9 in __GI___poll (fds=0x7f6028003ce0, nfds=1,
timeout=2481) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f60efd7b539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f60efd7b64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f60f373515b in QEventDispatcherGlib::processEvents
(this=0x7f6028000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f60f36d664a in QEventLoop::exec (this=this@entry=0x7f6039ffa9a0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x564e71b5db41 in Akonadi::Server::Connection::handleIncomingData
(this=0x564e735fccd0) at ./src/server/connection.cpp:212
#6  0x7f60f3714d04 in QtPrivate::QSlotObjectBase::call (a=0x7f6039ffaa10,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#7  QSingleShotTimer::timerEvent (this=0x7f6028005a10) at kernel/qtimer.cpp:318
#8  0x7f60f370894b in QObject::event (this=0x7f6028005a10, e=) at kernel/qobject.cpp:1271
#9  0x7f60f36d8311 in doNotify (event=0x7f6039ffab50,
receiver=0x7f6028005a10) at kernel/qcoreapplication.cpp:1151
#10 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1137
#11 QCoreApplication::notifyInternal2 (receiver=0x7f6028005a10,
event=0x7f6039ffab50) at kernel/qcoreapplication.cpp:1061
#12