[Akonadi] [Bug 451448] New: Akonadi Serverprocess dies after login

2022-03-13 Thread Bruno Schrade 
https://bugs.kde.org/show_bug.cgi?id=451448

Bug ID: 451448
   Summary: Akonadi Serverprocess dies after login
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@schwarzwald-software.de
  Target Milestone: ---

Application: akonadiserver (5.14.2 (20.04.2))

Qt Version: 5.12.7
Frameworks Version: 5.76.0
Operating System: Linux 5.3.18-150300.59.54-default x86_64
Windowing system: X11
Distribution: "openSUSE Leap 15.3"

-- Information about the crash:
- What I was doing when the application crashed:
Logging in. Akonadi server crashes most of the time. When it does not it will
when i try to use kmail.

- Custom settings of the application:
KMail has 5 POP3 accounts configured.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
[KCrash Handler]
#4  0x5624771adcc3 in QVector::isEmpty
(this=) at /usr/include/qt5/QtCore/qvector.h:89
#5  Akonadi::Server::Query::Condition::isEmpty (this=this@entry=0x56247722c9b8
) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/query.cpp:54
#6  0x5624771b04ff in Akonadi::Server::QueryBuilder::buildWhereCondition
(this=this@entry=0x7fe5637fcee0, query=query@entry=0x7fe5637fcd98, cond=...) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/querybuilder.cpp:506
#7  0x5624771b0589 in Akonadi::Server::QueryBuilder::buildWhereCondition
(this=this@entry=0x7fe5637fcee0, query=query@entry=0x7fe5637fcd98, cond=...) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/querybuilder.cpp:511
#8  0x5624771b0589 in Akonadi::Server::QueryBuilder::buildWhereCondition
(this=this@entry=0x7fe5637fcee0, query=query@entry=0x7fe5637fcd98, cond=...) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/querybuilder.cpp:511
#9  0x5624771b0589 in Akonadi::Server::QueryBuilder::buildWhereCondition
(this=this@entry=0x7fe5637fcee0, query=query@entry=0x7fe5637fcd98, cond=...) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/querybuilder.cpp:511
#10 0x5624771b0589 in Akonadi::Server::QueryBuilder::buildWhereCondition
(this=this@entry=0x7fe5637fcee0, query=query@entry=0x7fe5637fcd98, cond=...) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/querybuilder.cpp:511
#11 0x5624771b3344 in Akonadi::Server::QueryBuilder::buildQuery
(this=this@entry=0x7fe5637fcee0, statement=statement@entry=0x7fe5637fcd98) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/querybuilder.cpp:310
#12 0x5624771b3d04 in Akonadi::Server::QueryBuilder::exec
(this=this@entry=0x7fe5637fcee0) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/querybuilder.cpp:354
#13 0x56247709f176 in Akonadi::Server::ItemFetchHelper::buildItemQuery
(this=this@entry=0x7fe5637fd650) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/handler/itemfetchhelper.cpp:194
#14 0x5624770a1c15 in
Akonadi::Server::ItemFetchHelper::fetchItems(std::function&&) (this=this@entry=0x7fe5637fd650,
itemCallback=...) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/handler/itemfetchhelper.cpp:386
#15 0x56247709d1e0 in Akonadi::Server::ItemFetchHandler::parseStream
(this=0x7fe5540154a0) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/handler/itemfetchhandler.cpp:50
#16 0x562477068cbe in Akonadi::Server::Connection::parseStream
(this=this@entry=0x562478566440, cmd=...) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/connection.cpp:183
#17 0x56247706c110 in Akonadi::Server::Connectionoperator()
(__closure=0x7fe5637fd8a0) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/connection.cpp:274
#18
Akonadi::Server::DbDeadlockCatcher::callFunc&>
(recursionCounter=0, func=..., this=0x7fe5637fd830) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/dbdeadlockcatcher.h:47
#19
Akonadi::Server::DbDeadlockCatcher::DbDeadlockCatcher
> (func=..., this=0x7fe5637fd830) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/dbdeadlockcatcher.h:40
#20 Akonadi::Server::Connection::handleIncomingData (this=0x562478566440) at
/usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/connection.cpp:274
#21 0x7fe592885e84 in QtPrivate::QSlotObjectBase::call (a=0x7fe5637fd910,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#22 QSingleShotTimer::timerEvent (this=0x7fe554006270) at kernel/qtimer.cpp:318
#23 0x7fe592879a1b in QObject::event (this=0x7fe554006270, e=) at kern

[frameworks-kholidays] [Bug 445324] Winter solstice inappropriately listed as a holiday

2022-03-13 Thread Bug Janitor Service 
https://bugs.kde.org/show_bug.cgi?id=445324

--- Comment #9 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kholidays/-/merge_requests/38

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

[korganizer] [Bug 451459] New: Korganizer displays wrong start/end times for recurrences over DST boundary and created in UTC

2022-03-13 Thread Tusooa Zhu 
https://bugs.kde.org/show_bug.cgi?id=451459

Bug ID: 451459
   Summary: Korganizer displays wrong start/end times for
recurrences over DST boundary and created in UTC
   Product: korganizer
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: agendaview (weekview)
  Assignee: kdepim-bugs@kde.org
  Reporter: tus...@kazv.moe
  Target Milestone: ---

Created attachment 147472
  --> https://bugs.kde.org/attachment.cgi?id=147472&action=edit
the KOrganizer window that demonstrates this bug

SUMMARY
If I create a recurring event in UTC and it goes past a DST boundary,
korganizer will use the tz offset at the first instance of that event as the
displayed start/end time for *all* recurrences of that event.

STEPS TO REPRODUCE
1. Switch system timezone to America/Toronto
2. Create an event that starts at 2022-02-26 5:00 PM and ends at 2022-02-26
5:00 PM with *timezone set to UTC*, and repeats every week
3. Take a look at the Feb 26 instance and Mar 19 instance in Agenda/Week view

OBSERVED RESULT
In 3, the block of the Mar 19 instance is aligned with "1pm-2pm," but the start
and end time on the block is "12:00 P.M. - 1:00 P.M." Clicking on the event and
the details docker on the left sidebar says "Time: 12:00 P.M. - 1:00 P.M."

EXPECTED RESULT
In 3, the block of the Mar 19 instance is aligned with "1pm-2pm," the start and
end time on the block should be "1:00 P.M. - 2:00 P.M." Clicking on the event
and the details docker on the left sidebar should say "Time: 1:00 P.M. - 2:00
P.M."

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux 5.16.12-gentoo-x86_64
(available in About System)
KDE Plasma Version: 5.24.3 
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[korganizer] [Bug 436372] Cannot synchronize with my Nextcloud carddav/caldav

2022-03-13 Thread Bug Janitor Service 
https://bugs.kde.org/show_bug.cgi?id=436372

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #13 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kio/-/merge_requests/784

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