[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) segfault when DP screen is going to standby or powered off

2023-03-16 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=467147

--- Comment #5 from David Edmundson  ---
given this is crashing in QtWayland, can you get a hash of the version used?

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

[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) segfault when DP screen is going to standby or powered off

2023-03-16 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=467147

David Edmundson  changed:

   What|Removed |Added

   Keywords||wayland
 CC||k...@davidedmundson.co.uk
   Assignee|kwin-bugs-n...@kde.org  |kdepim-bugs@kde.org
  Component|wayland-generic |general
Product|kwin|kmail2
Version|5.27.3  |unspecified

--- Comment #4 from David Edmundson  ---
Lets not put client-side issues in kwin.

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

[kmail2] [Bug 457435] Krash after idling

2023-03-16 Thread Rob V
https://bugs.kde.org/show_bug.cgi?id=457435

--- Comment #3 from Rob V  ---
Created attachment 157336
  --> https://bugs.kde.org/attachment.cgi?id=157336=edit
New crash information added by DrKonqi

kmail (5.19.2 (21.12.2)) using Qt 5.15.2

Folders in KMail had stopped refreshing with new emails. Then, after minimising
KMail and restoring it, KMail crashed.

-- Backtrace (Reduced):
#4  0x7f111fdaa2c9 in QAction::setText(QString const&) () from
/lib64/libQt5Widgets.so.5
#5  0x7f1128402c5a in KMMainWidget::updateFolderMenu() () from
/lib64/libkmailprivate.so.5
#6  0x7f11283f8e60 in KMMainWidget::setupActions() () from
/lib64/libkmailprivate.so.5
#7  0x7f11283e144a in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*,
KActionCollection*, QExplicitlySharedDataPointer const&) () from
/lib64/libkmailprivate.so.5
#8  0x7f11283a7a4f in KMMainWin::KMMainWin(QWidget*) () from
/lib64/libkmailprivate.so.5

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

[kmail2] [Bug 457435] Krash after idling

2023-03-16 Thread Rob V
https://bugs.kde.org/show_bug.cgi?id=457435

Rob V  changed:

   What|Removed |Added

 CC||rvalk...@protonmail.com

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

[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram

2023-03-16 Thread Ray
https://bugs.kde.org/show_bug.cgi?id=461400

--- Comment #16 from Ray  ---
nmcli connection up id "SSID"
DOES create /org/freedesktop/NetworkManager/ActiveConnection/ - but following a
different number.
Akonadi was looking for /org/freedesktop/NetworkManager/ActiveConnection/4
but nmcli connection up id "SSID" created
/org/freedesktop/NetworkManager/ActiveConnection/6

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

[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram

2023-03-16 Thread Ray
https://bugs.kde.org/show_bug.cgi?id=461400

--- Comment #15 from Ray  ---
org.freedesktop.NetworkManager.sleep-wake no 
It's supposed to be that way - "put NetworkManager to sleep or wake it up
(should only be used by system power management"
But probably system power management doesn't set this state?

Going offline (networkmanager) and online again makes akonadi and kmail think
networkmanager is offline too

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

[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram

2023-03-16 Thread Ray
https://bugs.kde.org/show_bug.cgi?id=461400

--- Comment #14 from Ray  ---
nmcli general permissions


PERMISSIONVALUE 
org.freedesktop.NetworkManager.checkpoint-rollbackauth  
org.freedesktop.NetworkManager.enable-disable-connectivity-check  yes   
org.freedesktop.NetworkManager.enable-disable-network yes   
org.freedesktop.NetworkManager.enable-disable-statistics  yes   
org.freedesktop.NetworkManager.enable-disable-wifiyes   
org.freedesktop.NetworkManager.enable-disable-wimax   yes   
org.freedesktop.NetworkManager.enable-disable-wwanyes   
org.freedesktop.NetworkManager.network-controlyes   
org.freedesktop.NetworkManager.reload auth  
org.freedesktop.NetworkManager.settings.modify.global-dns auth  
org.freedesktop.NetworkManager.settings.modify.hostname   auth  
org.freedesktop.NetworkManager.settings.modify.ownyes   
org.freedesktop.NetworkManager.settings.modify.system yes   
org.freedesktop.NetworkManager.sleep-wake no
org.freedesktop.NetworkManager.wifi.scan  yes   
org.freedesktop.NetworkManager.wifi.share.openyes   
org.freedesktop.NetworkManager.wifi.share.protected   yes   


maybe that's the problem???

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

[kmail2] [Bug 467439] Crash when selecting multiple mails while pressing Ctrl

2023-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=467439

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[korganizer] [Bug 467443] New: Syncing reoccurring events to NextCloud

2023-03-16 Thread MrFrank
https://bugs.kde.org/show_bug.cgi?id=467443

Bug ID: 467443
   Summary: Syncing reoccurring events to NextCloud
Classification: Applications
   Product: korganizer
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: die_adre...@nurfuerspam.de
  Target Milestone: ---

SUMMARY
Changing a reoccurring event is not always synced to NextCloud

STEPS TO REPRODUCE
1. Create an reoccurring event with some days of repetition
2. Sync to NextCloud
3. Add a day exception of the reoccurring event or change the amount of
repetitons
4. Changes are not synced to NextCloud

OBSERVED RESULT
The changes are not synced to NextCloud. Only if more changes are done (eg in
the description) the synchronization is triggered

EXPECTED RESULT
See above

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE 15.4
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[kmail2] [Bug 467436] Crash when moving mails between folders

2023-03-16 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=467436

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
it seems to be a bug in wayland support

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

[kmail2] [Bug 467439] New: Crash when selecting multiple mails while pressing Ctrl

2023-03-16 Thread Thomas Fischer
https://bugs.kde.org/show_bug.cgi?id=467439

Bug ID: 467439
   Summary: Crash when selecting multiple mails while pressing
Ctrl
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: fisc...@unix-ag.uni-kl.de
  Target Milestone: ---

After first filtering mails in the list of mails for a keyword and while
selecting (mouse cursor) several of the found mails while pressing Ctrl, KMail
crashed:

Using Fedora 37, the following program/library versions were used:
KMail 22.12.3
KF5 KMime 22.12.3
Q5 5.15.8
Frameworks 5.103.0

Output on command line up to crash:

kf.notifications: env says KDE is running but SNI unavailable -- check
KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
[New Thread 0x7fff36ffd6c0 (LWP 12933)]
[New Thread 0x7fff367fc6c0 (LWP 12934)]
[New Thread 0x7fff35ffb6c0 (LWP 12935)]
[New Thread 0x7fff357fa6c0 (LWP 12936)]
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
[New Thread 0x7fff1e1bd6c0 (LWP 12942)]
[New Thread 0x7fff1d9bc6c0 (LWP 12943)]
[Detaching after fork from child process 12947]
[Detaching after fork from child process 12949]
[Detaching after fork from child process 12951]
[New Thread 0x7fff0bbff6c0 (LWP 12953)]
[New Thread 0x7fff0abbe6c0 (LWP 12956)]
[New Thread 0x7fff09f2d6c0 (LWP 12957)]
[New Thread 0x7fff0970c6c0 (LWP 12958)]
[New Thread 0x7fff08f0b6c0 (LWP 12959)]
[New Thread 0x7ffef3fff6c0 (LWP 12960)]
[Thread 0x7fff57fff6c0 (LWP 12908) exited]
[Thread 0x7fff767fc6c0 (LWP 12904) exited]
[Thread 0x7fff777fe6c0 (LWP 12902) exited]
[New Thread 0x7fff767fc6c0 (LWP 13009)]
[New Thread 0x7fff777fe6c0 (LWP 13010)]
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x5702e190) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x56e4b8b0) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
[New Thread 0x7fff57fff6c0 (LWP 13019)]
[Detaching after fork from child process 13095]
Recognized the following URL or filename:
"https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606;
Using Firefox executable "/usr/bin/firefox"
[Thread 0x7fff57fff6c0 (LWP 13019) exited]
[New Thread 0x7fff57fff6c0 (LWP 13197)]
[Detaching after fork from child process 13210]
Recognized the following URL or filename:
"https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606;
Using Firefox executable "/usr/bin/firefox"
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the
current topmost grabbing popup,

[kmail2] [Bug 467436] Crash when moving mails between folders

2023-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=467436

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kmail2] [Bug 467436] New: Crash when moving mails between folders

2023-03-16 Thread Thomas Fischer
https://bugs.kde.org/show_bug.cgi?id=467436

Bug ID: 467436
   Summary: Crash when moving mails between folders
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: fisc...@unix-ag.uni-kl.de
  Target Milestone: ---

After observing regular crashes in KMail when moving mails between folders (via
context menu, then "Move to", on mail in list of mails), I ran kmail via gdb
with debuginfod enabled.
Akonadi is no affected by crash, I still get popups on incoming mails even
after KMail had crashed.

Version numbers of concerned programs/libraries:
KMail 22.12.3, Fedora release 1.fc37
QWayand 5.15.8, Fedora release 1.fc37
KF5 KXmlGui 5.103.0, Fedora release 1.fc37

Most recent output in terminal before crash:

qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
kf.notifications: env says KDE is running but SNI unavailable -- check
KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
"Object does not exist at path
“/org/freedesktop/NetworkManager/ActiveConnection/6”"
"Object does not exist at path
“/org/freedesktop/NetworkManager/ActiveConnection/5”"
[Thread 0x7fff75bfb6c0 (LWP 9496) exited]
kf.notifications: env says KDE is running but SNI unavailable -- check
KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
[Thread 0x7fff773fe6c0 (LWP 9633) exited]
[Thread 0x7fff753fa6c0 (LWP 8215) exited]
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x571e7000) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
[New Thread 0x7fff753fa6c0 (LWP 11224)]
[New Thread 0x7fff773fe6c0 (LWP 11225)]
[New Thread 0x7fff75bfb6c0 (LWP 11226)]
[New Thread 0x7ffeecbfc6c0 (LWP 11326)]
[New Thread 0x7ffeebbfa6c0 (LWP 11328)]
[New Thread 0x7ffeec3fb6c0 (LWP 11327)]
[New Thread 0x7ffeeb3f96c0 (LWP 11329)]
[New 

[kmail2] [Bug 390806] kmail sleeping after opening an attachment

2023-03-16 Thread Martin Schnitkemper
https://bugs.kde.org/show_bug.cgi?id=390806

Martin Schnitkemper  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Martin Schnitkemper  ---
The problem has now been fixed and no longer occurs.
[kmail2 5.22.3 (22.12.3) | KDE Plasma version: 5.27.2 | KDE Framework Version:
5.103.0 | Qt version: 5.15.8]

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

[knotes] [Bug 467431] New: Remember Window-Settings on startup

2023-03-16 Thread Enno Hillmer
https://bugs.kde.org/show_bug.cgi?id=467431

Bug ID: 467431
   Summary: Remember Window-Settings on startup
Classification: Applications
   Product: knotes
   Version: 5.15.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: enno.hill...@gmx.de
CC: myr...@kde.org
  Target Milestone: ---

Wouldn't it be nice if kNotes would be able to remember the Window-Settings
like "Always on Top" or "Show on all Desktops" ... on Startup.
Additional it would be nice to activate a KNotes Autostart in it's Settings.
Kind Regards

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

[kmail2] [Bug 465825] mail viewer crashes on this message

2023-03-16 Thread Marc Mezzarobba
https://bugs.kde.org/show_bug.cgi?id=465825

--- Comment #3 from Marc Mezzarobba  ---
Thanks a lot for taking a look!

You mean that the bug is *fixed* in zxing-cpp 2.0, right? (or should I report
it there?)

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

[Akonadi] [Bug 467430] New: Akonadi crash possibly due to dolphin

2023-03-16 Thread David Tonhofer
https://bugs.kde.org/show_bug.cgi?id=467430

Bug ID: 467430
   Summary: Akonadi crash possibly due to dolphin
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: bugh...@gluino.name
  Target Milestone: ---

Application: akonadiserver (5.22.0 (22.12.0))

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.18-100.fc36.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 36 (KDE Plasma)
DrKonqi: 5.27.1 [KCrashBackend]

-- Information about the crash:
I feel this is at least the 3 time I have encountered this crash

What happens:

- I have a large-ish list of ODT LibreOffice Text docucment, the directory
where they reside is open in DOLPHIN 
- Iteratively do:
-- Click on document, opening it.
-- Edit the name of the document in DOLPHIN by prepending a date (_MM_DD_)
found inside the document. Hit RETURN.
-- This rearranges the document list in DOLPHIN of course (as expected, but I
know that renaming documents in DOLPHIN used to be fraught with some
arbitrariness & danger)
-- Do not bother to close thise LibreOffice Writer instance, which accumulates
windows, but that's ok as I can close them all in one click once done.

The crash seems to occur after hitting RETURN upon having renamed a document.

Also, YouTube is playing lofi in the background.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault

[KCrash Handler]
#4  std::default_delete::operator() (__ptr=0x111,
this=) at /usr/include/c++/12/bits/unique_ptr.h:89
#5  std::unique_ptr >::~unique_ptr
(this=, this=) at
/usr/include/c++/12/bits/unique_ptr.h:396
#6  std::__new_allocator >
>::destroy > > (__p=,
this=0x7fff9bf42a28) at /usr/include/c++/12/bits/new_allocator.h:181
#7 
std::allocator_traits > >
>::destroy > > (__p=,
__a=...) at /usr/include/c++/12/bits/alloc_traits.h:535
#8  std::vector >,
std::allocator > > >::_M_erase
(__position=..., this=0x7fff9bf42a28) at
/usr/include/c++/12/bits/vector.tcc:181
#9  std::vector >,
std::allocator > > >::erase (__position=...,
this=0x7fff9bf42a28) at /usr/include/c++/12/bits/stl_vector.h:1530
#10 Akonadi::Server::AkonadiServer::connectionDisconnected
(this=0x7fff9bf429a0) at
/usr/src/debug/kf5-akonadi-server-22.12.0-2.fc36.x86_64/src/server/akonadi.cpp:234
#11 0x7f0e8aec8134 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#12 0x7f0e8ae9d4cb in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#13 0x7f0e8aea0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#14 0x7f0e8aeeeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#15 0x7f0e89b18faf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#16 0x7f0e89b6e2c8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#17 0x7f0e89b16940 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#18 0x7f0e8aeee5fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#19 0x7f0e8ae9bf3a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#20 0x7f0e8aea4002 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#21 0x55fcbd308058 in AkApplicationBase::exec (this=0x7fff9bf42970) at
/usr/src/debug/kf5-akonadi-server-22.12.0-2.fc36.x86_64/src/shared/akapplication.cpp:107
#22 main (argc=, argv=) at
/usr/src/debug/kf5-akonadi-server-22.12.0-2.fc36.x86_64/src/server/main.cpp:65
[Inferior 1 (process 2555) detached]

Reported using DrKonqi

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

[kmail2] [Bug 465713] Allow zooming and/or "Open with" of in-place image attachments in HTML message viewer

2023-03-16 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=465713

--- Comment #1 from Laurent Montel  ---
Git commit af19adb109040aabdec36bc8a370314c07922d6d by Laurent Montel.
Committed on 16/03/2023 at 07:14.
Pushed by mlaurent into branch 'master'.

Add "open image" action

M  +2-0src/kmmainwidget.cpp
M  +2-0src/kmreadermainwin.cpp
M  +21   -0src/kmreaderwin.cpp
M  +3-0src/kmreaderwin.h

https://invent.kde.org/pim/kmail/commit/af19adb109040aabdec36bc8a370314c07922d6d

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

[kmail2] [Bug 465825] mail viewer crashes on this message

2023-03-16 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=465825

Laurent Montel  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||mon...@kde.org
 Resolution|--- |FIXED

--- Comment #2 from Laurent Montel  ---
IT doesn't crash here.
It seems a problem with ZXing 2.0,
As a workaround until then, delete or move away
/usr/lib64/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_semantic.so
(path might differ slightly depending on distro/platform). That will disable
the itinerary plugin but not impede KMail's functionality otherwise.

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

[kmail2] [Bug 467360] Preview pane on the right is always unusably small on startup

2023-03-16 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=467360

--- Comment #2 from Laurent Montel  ---
First time is small but after that I expand it and close kmail/reopen it it's
ok. Size is restored.

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

[kmail2] [Bug 467360] Preview pane on the right is always unusably small on startup

2023-03-16 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=467360

Laurent Montel  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||mon...@kde.org
 Ever confirmed|0   |1

--- Comment #1 from Laurent Montel  ---
I confirm it. I will work on it.

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

[kmail2] [Bug 467291] Switching Folder List layout causes messages in message list to disappear

2023-03-16 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=467291

Laurent Montel  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.23.0
  Latest Commit||https://invent.kde.org/pim/
   ||kmail/commit/b269da73b1e5c6
   ||d6182ef189a5be959c2e64d826

--- Comment #2 from Laurent Montel  ---
Git commit b269da73b1e5c6d6182ef189a5be959c2e64d826 by Laurent Montel.
Committed on 16/03/2023 at 06:16.
Pushed by mlaurent into branch 'release/23.04'.

Fix bug 467291:  Switching Folder List layout causes messages in message list
to disappear
FIXED-IN: 5.23.0

M  +1-0src/kmmainwidget.cpp

https://invent.kde.org/pim/kmail/commit/b269da73b1e5c6d6182ef189a5be959c2e64d826

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

[kmail2] [Bug 467291] Switching Folder List layout causes messages in message list to disappear

2023-03-16 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=467291

Laurent Montel  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
I confirm it

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