[korganizer] [Bug 476642] Wrong calculation in week recurrence after 15 iterations

2024-01-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476642

pi...@gmx.de changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

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

[korganizer] [Bug 476642] Wrong calculation in week recurrence after 15 iterations

2024-01-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=476642

--- Comment #11 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kmail2] [Bug 444108] kmail dragging mail to sidebar starts scrolling fast in wayland sessions

2024-01-04 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=444108

Kamil Dudka  changed:

   What|Removed |Added

 CC||kdu...@redhat.com

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

[kmail2] [Bug 440874] Folder list scrolls up when trying to drag message into folder

2024-01-04 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=440874

Kamil Dudka  changed:

   What|Removed |Added

 CC||kdu...@redhat.com

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

[Akonadi] [Bug 357819] Korganizer doesn't send calendar events to Google account

2024-01-04 Thread KDamian
https://bugs.kde.org/show_bug.cgi?id=357819

KDamian  changed:

   What|Removed |Added

 CC||damik...@gmail.com

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

[kontact] [Bug 479395] New: Crash on trying to re-open draft from local folder

2024-01-04 Thread Martin Riethmayer
https://bugs.kde.org/show_bug.cgi?id=479395

Bug ID: 479395
   Summary: Crash on trying to re-open draft from local folder
Classification: Applications
   Product: kontact
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: rip...@freakmail.de
  Target Milestone: ---

Application: kontact (5.24.3 (23.08.3))

Qt Version: 5.15.11
Frameworks Version: 5.112.0
Operating System: Linux 6.6.2-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
When trying to re-open a draft from a local folder after sending failed, KMail
/ Kontact crashed. The draft was still available and would open at the next
start, so no data was lost.

This happened multiple times until I finally managed to have the correct SMTP
configured (which is really, really, really not intuitive if you have multiple
accounts configured...).

I could not reproduce this by simply making a draft and re-opening it.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  doActivate (sender=0x56271f1aa780, signal_index=4,
argv=0x7ffc5a33ffc0) at kernel/qobject.h:132
#5  0x7ff48eb1e0af in QMetaObject::activate
(sender=sender@entry=0x56271f1aa780, m=,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc5a33ffc0)
at kernel/qobject.cpp:3985
#6  0x7ff3f47c0e4c in KMCommand::completed (_t1=0x56271f1aa780,
this=0x56271f1aa780) at
/usr/src/debug/kmail-23.08.3/build/src/kmailprivate_autogen/EWIEGA46WW/moc_kmcommands.cpp:201
#7  KMCommand::slotPostTransfer (this=0x56271f1aa780, result=KMCommand::OK) at
/usr/src/debug/kmail-23.08.3/src/kmcommands.cpp:263
#8  0x7ff48eb25442 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5a3400f0,
r=0x56271f1aa780, this=0x562720700f50) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9  doActivate (sender=0x56271f1aa780, signal_index=3,
argv=0x7ffc5a3400f0) at kernel/qobject.cpp:3925
#10 0x7ff48eb1e0af in QMetaObject::activate
(sender=sender@entry=0x56271f1aa780, m=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc5a3400f0)
at kernel/qobject.cpp:3985
#11 0x7ff3f47c1a9a in KMCommand::messagesTransfered (_t1=KMCommand::OK,
this=0x56271f1aa780) at
/usr/src/debug/kmail-23.08.3/build/src/kmailprivate_autogen/EWIEGA46WW/moc_kmcommands.cpp:194
#12 KMCommand::slotJobFinished (this=0x56271f1aa780) at
/usr/src/debug/kmail-23.08.3/src/kmcommands.cpp:368
#13 0x7ff48eb25442 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5a340220,
r=0x56271f1aa780, this=0x56271c077a10) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate (sender=0x56271ea666a0, signal_index=6,
argv=0x7ffc5a340220) at kernel/qobject.cpp:3925
#15 0x7ff48fdad115 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib64/libKF5CoreAddons.so.5
#16 0x7ff48fdb141b in ?? () from /lib64/libKF5CoreAddons.so.5
#17 0x7ff48eb18f50 in QObject::event (this=0x56271ea666a0,
e=0x56271e738970) at kernel/qobject.cpp:1347
#18 0x7ff48f7a519e in QApplicationPrivate::notify_helper (this=, receiver=0x56271ea666a0, e=0x56271e738970) at
kernel/qapplication.cpp:3640
#19 0x7ff48eaed198 in QCoreApplication::notifyInternal2
(receiver=0x56271ea666a0, event=0x56271e738970) at
kernel/qcoreapplication.cpp:1064
#20 0x7ff48eaed35e in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462
#21 0x7ff48eaf0791 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x56271bbb5ae0) at
kernel/qcoreapplication.cpp:1821
#22 0x7ff48eaf0cd8 in QCoreApplication::sendPostedEvents
(receiver=, event_type=) at
kernel/qcoreapplication.cpp:1680
#23 0x7ff48eb468c3 in postEventSourceDispatch (s=0x56271bbf9cf0) at
kernel/qeventdispatcher_glib.cpp:277
#24 0x7ff485513f30 in ?? () from /lib64/libglib-2.0.so.0
#25 0x7ff485515b58 in ?? () from /lib64/libglib-2.0.so.0
#26 0x7ff48551620c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#27 0x7ff48eb460d6 in QEventDispatcherGlib::processEvents
(this=0x56271bba2e70, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x7ff48eaebc2b in QEventLoop::exec (this=this@entry=0x7ffc5a340610,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#29 0x7ff48eaf40c0 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#30 0x56271a9a7fd3 in main (argc=, argv=) at
/usr/src/debug/kontact-23.08.3/src/main.cpp:216
[Inferior 1 (process 29314) detached]

Reported using DrKonqi

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

[akregator] [Bug 445351] Akregator always wants to recover the session on boot

2024-01-04 Thread Jan Wesselink
https://bugs.kde.org/show_bug.cgi?id=445351

Jan Wesselink  changed:

   What|Removed |Added

   Platform|Arch Linux  |Debian stable
Version|5.18.3  |5.22.3
 CC||wessel...@gmail.com

--- Comment #6 from Jan Wesselink  ---
Same thing here while using wayland on desktop HP prodesk 400 g5.
Akregator opens screen to restore last session, is wasnt shutdown properly it
says.

When starting with x11 it doenst give any problems.

akregator 5.22.3 (22.12.3) 
debian 12 stable KDE

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

[Akonadi] [Bug 479342] Akonadi server crashed.

2024-01-04 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=479342

--- Comment #2 from Attila  ---
Hi, I apologise for the duplicates. It was not my intention to create
duplicates over and over again. It is a bug in DrKonqi. When I press the
"submit" button, I see the spinning wheel. There is no confirmation that the
bug report has been sent.
So I took a step back and pressed the "submit" button again.

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