[kontact] [Bug 454536] Kontact crashes with segmentation fault when marking a recurring task as done

2022-05-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=454536

gjditchfi...@acm.org changed:

   What|Removed |Added

 Ever confirmed|0   |1
  Component|todo|summary
 Status|REPORTED|CONFIRMED

--- Comment #4 from gjditchfi...@acm.org ---
For me, marking a non-recurring to-do complete also
causes a crash.

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

[kontact] [Bug 454536] Kontact crashes with segmentation fault when marking a recurring task as done

2022-05-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=454536

simplyschi...@gmx.net changed:

   What|Removed |Added

Version|5.13.3  |unspecified

--- Comment #3 from simplyschi...@gmx.net ---
(In reply to gjditchfield from comment #2)

Q1: Which version of Kontact are you using?
A1: Kontact 5.10.1 (22.04.1), cf. data uploaded 2022-05-28 15:41:08 UTC when
creating this bug report.
Please note that I have been observing the same problem on my previous openSuse
Leap 15.3, too, but until today never decided to file a bug report.

Q2: Which views does this happen in — the Agenda view, the Month view, ...?
A2: The problem happens in view headed with 'Summary -- Kontact'. Things are
working fine when I switch to view 'To-do List'.

HTH.

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

[kontact] [Bug 454536] Kontact crashes with segmentation fault when marking a recurring task as done

2022-05-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=454536

gjditchfi...@acm.org changed:

   What|Removed |Added

  Component|general |todo
Version|unspecified |5.13.3
 CC||gjditchfi...@acm.org

--- Comment #2 from gjditchfi...@acm.org ---
Which version of Kontact are you using?

Which views does this happen in — the Agenda view, the Month view, ...?

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

[korganizer] [Bug 361242] korganizer fires remainder event every minute when time switch to DST

2022-05-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=361242

gjditchfi...@acm.org changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|REPORTED|RESOLVED
 CC||gjditchfi...@acm.org

--- Comment #1 from gjditchfi...@acm.org ---
As of version 22.04.0 (5.20.0), korgac has been replaced by a new
reminder daemon, kalendarac.  If you have upgraded to that version,
please watch for unreliable reminders and report them as bugs for
product "Reminder Daemon".

For what it's worth, I couldn't reproduce this bug with kalendarac.
- Create contacts with birthdays before, on, and after 2022-03-13
  (recent CST transition).
- Settings > Date & Time: don't set automatically
- pkill kalendarac
- mv ~/.config/kalendaracrc ~
- sudo date -s '2022-03-12 23:57:00.0'
- Log out and back in.  Reminders appeared as expected as time passed.
- sudo date -s '2022-03-13 01:57:00.0'
  No extra reminders appeared as time passed.

-- 
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

2022-05-28 Thread Kishore Gopalakrishnan
https://bugs.kde.org/show_bug.cgi?id=445351

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

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

[kontact] [Bug 454536] Kontact crashes with segmentation fault when marking a recurring task as done

2022-05-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=454536

--- Comment #1 from simplyschi...@gmx.net ---
Update on Information about the crash:
- What I was doing when the application crashed:
I was marking  a (monthly) recurring task as 'Mark To-do Complete' in Kontact.
Bug preproducible 9+ out of 10 times.

Please note that when I tick the same recurring task in 'To-do List',
everything is working as expected: the task is re-schedules for next month.

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

[kontact] [Bug 454536] New: Kontact crashes with segmentation fault when marking a recurring task as done

2022-05-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=454536

Bug ID: 454536
   Summary: Kontact crashes with segmentation fault when marking a
recurring task as done
   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: simplyschi...@gmx.net
  Target Milestone: ---

Application: kontact (5.20.1 (22.04.1))

Qt Version: 5.15.2
Frameworks Version: 5.94.0
Operating System: Linux 5.17.9-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I was marking  a (monthly) recurring task as 'done' in Kontact. Bug
preproducible 9+ out of 10 times.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  std::__atomic_base::load
(__m=std::memory_order_relaxed, this=0x3ff8) at
/usr/include/c++/12/bits/atomic_base.h:818
#5  std::atomic::load
(__m=std::memory_order_relaxed, this=0x3ff8) at
/usr/include/c++/12/atomic:579
#6 
QAtomicOps::loadRelaxed
(_q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#7  QBasicAtomicPointer::loadRelaxed
(this=0x3ff8) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#8  QObjectPrivate::maybeSignalConnected (this=this@entry=0x5601ecc45de0,
signalIndex=signalIndex@entry=15) at kernel/qobject.cpp:482
#9  0x7f0aff412951 in doActivate (sender=0x5601ee93f510,
signal_index=15, argv=0x7ffd691ede80) at kernel/qobject.cpp:3788
#10 0x7f0aff40c0cf in QMetaObject::activate (sender=,
m=m@entry=0x7f0afe90a6e0 ,
local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffd691ede80)
at kernel/qobject.cpp:3946
#11 0x7f0afe8b91c5 in KUrlLabel::rightClickedUrl (this=,
_t1=...) at
/usr/src/debug/kwidgetsaddons-5.94.0-1.1.x86_64/build/src/KF5WidgetsAddons_autogen/include/moc_kurllabel.cpp:418
#12 0x7f0afffc9f48 in QWidget::event (this=this@entry=0x5601ee93f510,
event=event@entry=0x7ffd691ee370) at kernel/qwidget.cpp:9020
#13 0x7f0b0007567e in QFrame::event (this=0x5601ee93f510, e=0x7ffd691ee370)
at widgets/qframe.cpp:550
#14 0x7f0afff8837e in QApplicationPrivate::notify_helper
(this=this@entry=0x5601eb81ded0, receiver=receiver@entry=0x5601ee93f510,
e=e@entry=0x7ffd691ee370) at kernel/qapplication.cpp:3632
#15 0x7f0afff908c2 in QApplication::notify (this=,
receiver=0x5601ee93f510, e=) at kernel/qapplication.cpp:3076
#16 0x7f0aff3db988 in QCoreApplication::notifyInternal2
(receiver=0x5601ee93f510, event=0x7ffd691ee370) at
kernel/qcoreapplication.cpp:1064
#17 0x7f0afff8e9ce in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x5601ee93f510, event=event@entry=0x7ffd691ee370,
alienWidget=, nativeWidget=0x5601ebb2cd40,
buttonDown=buttonDown@entry=0x7f0b004d4330 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
kernel/qapplication.cpp:2614
#18 0x7f0afffe2d68 in QWidgetWindow::handleMouseEvent (this=0x5601ec399a70,
event=0x7ffd691ee620) at kernel/qwidgetwindow.cpp:683
#19 0x7f0afffe62c0 in QWidgetWindow::event (this=0x5601ec399a70,
event=0x7ffd691ee620) at kernel/qwidgetwindow.cpp:300
#20 0x7f0afff8837e in QApplicationPrivate::notify_helper (this=, receiver=0x5601ec399a70, e=0x7ffd691ee620) at
kernel/qapplication.cpp:3632
#21 0x7f0aff3db988 in QCoreApplication::notifyInternal2
(receiver=0x5601ec399a70, event=0x7ffd691ee620) at
kernel/qcoreapplication.cpp:1064
#22 0x7f0aff837a45 in QGuiApplicationPrivate::processMouseEvent
(e=0x5601ee3f31c0) at kernel/qguiapplication.cpp:2282
#23 0x7f0aff80c2ac in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#24 0x7f0aebfae4da in xcbSourceDispatch (source=) at
qxcbeventdispatcher.cpp:105
#25 0x7f0af5cf6da0 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#26 0x7f0af5cf7158 in ?? () from /lib64/libglib-2.0.so.0
#27 0x7f0af5cf71ec in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#28 0x7f0aff4335a6 in QEventDispatcherGlib::processEvents
(this=0x5601eb8fcc00, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x7f0aff3da3fb in QEventLoop::exec (this=this@entry=0x7ffd691ee950,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#30 0x7f0aff3e2566 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#31 0x7f0aff82b3bc in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#32 0x7f0afff882f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#33 0x5601ea3bf03d in main (argc=, argv=) at

[akregator] [Bug 452550] notification dot on system tray icon

2022-05-28 Thread raguse
https://bugs.kde.org/show_bug.cgi?id=452550

raguse  changed:

   What|Removed |Added

 CC||contact...@protonmail.com

--- Comment #1 from raguse  ---
May I join this feature request. 
The current available settings is 'Show unread articles in Taskbar' which only
shows the number of new messages when the application is open. 
The proper or additional settings would be 'Show unread articles in system
tray' which should provide the unread messages as notification dot in system
tray. 
This feature would be great, thanks!

Currently using Akregator version 5.20.1 (22.04.1)

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

[akregator] [Bug 453472] Akregator forbid url

2022-05-28 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=453472

--- Comment #1 from Christophe Giboudeaux  ---
What's the bug exactly? If the wiki card isn't detected, I suppose you have no
network connection?

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