[kontact] [Bug 469596] Kontact doesn't start

2023-05-10 Thread Christophe Marin
https://bugs.kde.org/show_bug.cgi?id=469596

Christophe Marin  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Christophe Marin  ---


*** This bug has been marked as a duplicate of bug 469599 ***

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

[neon] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error

2023-05-10 Thread Christophe Marin
https://bugs.kde.org/show_bug.cgi?id=469599

Christophe Marin  changed:

   What|Removed |Added

  Component|general |general
Version|5.23.0  |unspecified
Product|kontact |neon
   Assignee|kdepim-bugs@kde.org |neon-b...@kde.org
 CC||j...@jriddell.org,
   ||neon-b...@kde.org,
   ||sit...@kde.org

--- Comment #7 from Christophe Marin  ---
(In reply to ioo+kde from comment #2)
> I found another error when I try to open it in the journal:
> 
> May 10 15:52:58 host plasmashell[101020]: /usr/bin/kontact: error while
> loading shared libraries: libKF5TextAutoCorrection.so.1: cannot open shared
> object file: No such file or directory
> 
> Perhaps there are files missing from the upgrade? How can I fix this?

Packaging issue

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

[kontact] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error

2023-05-10 Thread Cole
https://bugs.kde.org/show_bug.cgi?id=469599

Cole  changed:

   What|Removed |Added

 CC||cnit...@me.com

--- Comment #6 from Cole  ---
Getting the same issue as the reporter and tried following their debug steps
and get the same outcome. Seems like a bad build, a missing library?

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

[kontact] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469599

--- Comment #5 from ioo+...@posteo.net ---
Multiple user affected:

https://forum.kde.org/posting.php?mode=reply=215=177690

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

[Akonadi] [Bug 469601] New: Absturz Google Groupware

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469601

Bug ID: 469601
   Summary: Absturz Google Groupware
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Google Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: yves.gruenw...@gmx.de
CC: c...@carlschwan.eu, dvra...@kde.org
  Target Milestone: ---

Application: akonadi_google_resource (5.23.0 (23.04.0))

Qt Version: 5.15.9
Frameworks Version: 5.105.0
Operating System: Linux 6.3.1-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
Start TV-Livestream in Google Chrome Browser mit mehreren Fenstern

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Google Groupware (effizienzg...@googlemail.com)
(akonadi_google_resource), signal: Aborted

[KCrash Handler]
#4  0x7ff8ad89490c in __pthread_kill_implementation () from
/lib64/libc.so.6
#5  0x7ff8ad843196 in raise () from /lib64/libc.so.6
#6  0x7ff8ad82b897 in abort () from /lib64/libc.so.6
#7  0x7ff8adebb4e9 in QMessageLogger::fatal(char const*, ...) const () from
/lib64/libQt5Core.so.5
#8  0x7ff8adeba77c in qt_assert_x(char const*, char const*, char const*,
int) () from /lib64/libQt5Core.so.5
#9  0x7ff8afd10fc8 in Akonadi::ResourceBase::retrieveItem(Akonadi::Item
const&, QSet const&) () from /lib64/libKPim5AkonadiAgentBase.so.5
#10 0x7ff8afd2b514 in ?? () from /lib64/libKPim5AkonadiAgentBase.so.5
#11 0x7ff8ae125232 in ?? () from /lib64/libQt5Core.so.5
#12 0x7ff8af7307f5 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib64/libKF5CoreAddons.so.5
#13 0x7ff8af734b9b in ?? () from /lib64/libKF5CoreAddons.so.5
#14 0x7ff8ae118c50 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#15 0x7ff8aeda51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#16 0x7ff8ae0ec978 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7ff8ae0eff71 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#18 0x7ff8ae146713 in ?? () from /lib64/libQt5Core.so.5
#19 0x7ff8ac4698d8 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#20 0x7ff8ac469ce8 in ?? () from /lib64/libglib-2.0.so.0
#21 0x7ff8ac469d7c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#22 0x7ff8ae145f26 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#23 0x7ff8ae0eb40b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#24 0x7ff8ae0f38a0 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#25 0x5599b5603143 in ?? ()
#26 0x7ff8ad82cbb0 in __libc_start_call_main () from /lib64/libc.so.6
#27 0x7ff8ad82cc79 in __libc_start_main_impl () from /lib64/libc.so.6
#28 0x5599b5603785 in ?? ()
[Inferior 1 (process 2942) detached]

Reported using DrKonqi

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

[kontact] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469599

ioo+...@posteo.net changed:

   What|Removed |Added

Version|unspecified |5.23.0

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

[kontact] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469599

--- Comment #4 from ioo+...@posteo.net ---
I tried to reinstall kontact:

sudo-apt-get install --reinstll Kontact. 

"(Reading database ... 463542 files and directories currently installed.)
Preparing to unpack
.../kontact_4%3a23.04.0-0xneon+22.04+jammy+release+build24_amd64.deb ...
Unpacking kontact (4:23.04.0-0xneon+22.04+jammy+release+build24) over
(4:23.04.0-0xneon+22.04+jammy+release+build24) ...
Setting up kontact (4:23.04.0-0xneon+22.04+jammy+release+build24) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ..."

it reinstalled it sucessfully however I am still getting the same error about
the missing library. It appears this Kontact is broken in this version. Email
is pretty essential. Is there any way to downgrade or otherwise get access to
my email?

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

[kontact] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469599

--- Comment #3 from ioo+...@posteo.net ---
Doing a search for this library (sudo apt search libkf5textautocorrection)

libkf5textautocorrection1/jammy,now 1.3.1-0xneon+22.04+jammy+release+build15
amd64 [installed,automatic]
  Text processing library from KDE - auto correction features

libkf5textautocorrection1-dbgsym/jammy 1.3.1-0xneon+22.04+jammy+release+build15
amd64
  debug symbols for libkf5textautocorrection1

however the file does not exist on the hard drive:

search for "libKF5TextAutoCorrection.*"

does not show me any results. This is confusing, is the file there or not?

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

[kontact] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469599

ioo+...@posteo.net changed:

   What|Removed |Added

Summary|Kontact and Kmail broken|Kontact and Kmail broken
   |after upgrade to KDE|after upgrade to KDE
   |5.27.5, app is still there  |5.27.5, app is still there
   |but will not open "Failed   |but will not open "Failed
   |to register new cgroup, |to register new cgroup,
   |does Process does not   |Process does not exist"
   |exist"  |error

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

[kontact] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, does Process does not exist"

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469599

--- Comment #2 from ioo+...@posteo.net ---
I found another error when I try to open it in the journal:

May 10 15:52:58 host plasmashell[101020]: /usr/bin/kontact: error while loading
shared libraries: libKF5TextAutoCorrection.so.1: cannot open shared object
file: No such file or directory

Perhaps there are files missing from the upgrade? How can I fix this?

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

[kontact] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, does Process does not exist"

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469599

ioo+...@posteo.net changed:

   What|Removed |Added

Summary|Kontact and Kmail broken|Kontact and Kmail broken
   |after upgrade to KDE 5.27.5 |after upgrade to KDE
   ||5.27.5, app is still there
   ||but will not open "Failed
   ||to register new cgroup,
   ||does Process does not
   ||exist"

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

[kontact] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469599

--- Comment #1 from ioo+...@posteo.net ---
I wish to add the following information:

KDE Plasma 5.27.5
KDE Framework Version 5.105.0
Qt version 5.15.9

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

[kontact] [Bug 469599] New: Kontact and Kmail broken after upgrade to KDE 5.27.5

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469599

Bug ID: 469599
   Summary: Kontact and Kmail broken after upgrade to KDE 5.27.5
Classification: Applications
   Product: kontact
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ioo+...@posteo.net
  Target Milestone: ---

SUMMARY
***
I just upgraded from KDE 5.27.4 to KDE 5.27.5 and Kontact is now gone. The icon
is still in my start menu but when I click on it nothing happens.

I see in the journal log this message:
[code]
May 10 15:40:34 host plasmashell[2808]: kf.kio.gui: Failed to register new
cgroup: "app-org.kde.kontact-ca9cd8afcc1e4256bd90d768c5cac2c0.scope"
"org.freedesktop.DBus.Error.UnixProcessIdUnknown" "Process with ID 40407 does
not exist."
May 10 15:40:34 host plasmashell[2808]: kf.kio.gui: "The command
 could not be found."
[/code]

Does anyone have any idea what this means? What can I do to get my email back
working again?

If I try to open just the kmail app I get this unhelpful message:
[code]
May 10 15:42:51 host systemd[2214]: Failed to start KMail - Mail Client.
[/code]

Help!!
***


STEPS TO REPRODUCE
1. Upgrade to KDE 5.27.5 from 5.27.4 using Discover
2. No errors, upgrade seemed to work
3. Open Kontact

OBSERVED RESULT
1. Nothing happens, see error log in journal.


EXPECTED RESULT
1. Kontact will open.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kontact] [Bug 469596] New: Kontact doesn't start

2023-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469596

Bug ID: 469596
   Summary: Kontact doesn't start
Classification: Applications
   Product: kontact
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: damian@posteo.de
  Target Milestone: ---

SUMMARY
***
Kontact doesn't start.
***


STEPS TO REPRODUCE
1. trying to start kontact from K-menu, from command line


OBSERVED RESULT:
kontact: error while loading shared libraries: libKF5TextAutoCorrection.so.1:
cannot open shared object file: No such file or directory




SOFTWARE/OS VERSIONS


Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.19.9

ADDITIONAL INFORMATION
occurs after plasma update today

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

[kmail2] [Bug 469589] New: KMail segfaults when trying to send an encrypted and signed E-Mail

2023-05-10 Thread sudden6
https://bugs.kde.org/show_bug.cgi?id=469589

Bug ID: 469589
   Summary: KMail segfaults when trying to send an encrypted and
signed E-Mail
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sudd...@gmx.at
  Target Milestone: ---

Application: kmail (5.23.0 (23.04.0))

Qt Version: 5.15.9
Frameworks Version: 5.105.0
Operating System: Linux 6.2.12-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
When trying to send and encrypted and signed E-Mail, KMail crashes with a
segfault and the attached backtrace.

I have not used that functionality in a long time, so it's hard to tell when it
broke. Last time I know it was working was still with XServer instead of
Wayland though.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x7f7ebd92645b in  () at /lib64/libQt5WaylandClient.so.5
#5  0x7f7ebde1d8d2 in  () at /lib64/libffi.so.8
#6  0x7f7ebde1a24f in  () at /lib64/libffi.so.8
#7  0x7f7ebde1ce96 in ffi_call () at /lib64/libffi.so.8
#8  0x7f7ebdedda23 in  () at /lib64/libwayland-client.so.0
#9  0x7f7ebdede203 in  () at /lib64/libwayland-client.so.0
#10 0x7f7ebdede494 in wl_display_dispatch_queue_pending () at
/lib64/libwayland-client.so.0
#11 0x7f7ebd926a12 in QtWaylandClient::QWaylandDisplay::flushRequests() ()
at /lib64/libQt5WaylandClient.so.5
#12 0x7f7ec4718c50 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#13 0x7f7ec53a51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#14 0x7f7ec46ec978 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#15 0x7f7ec46eff71 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#16 0x7f7ec4746713 in  () at /lib64/libQt5Core.so.5
#17 0x7f7ec052b8d8 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#18 0x7f7ec052bce8 in  () at /lib64/libglib-2.0.so.0
#19 0x7f7ec052bd7c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#20 0x7f7ec4745f26 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#21 0x7f7ec46eb40b in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#22 0x7f7ec55acfe7 in QDialog::exec() () at /lib64/libQt5Widgets.so.5
#23 0x7f7ec2148c8a in KMessageBox::createKMessageBox(QDialog*,
QDialogButtonBox*, QIcon const&, QString const&, QStringList const&, QString
const&, bool*, QFlags, QString const&, QMessageBox::Icon)
() at /lib64/libKF5WidgetsAddons.so.5
#24 0x7f7ec2149382 in KMessageBox::createKMessageBox(QDialog*,
QDialogButtonBox*, QMessageBox::Icon, QString const&, QStringList const&,
QString const&, bool*, QFlags, QString const&) () at
/lib64/libKF5WidgetsAddons.so.5
#25 0x7f7ec214a887 in  () at /lib64/libKF5WidgetsAddons.so.5
#26 0x7f7ec214aa67 in KMessageBox::warningContinueCancelList(QWidget*,
QString const&, QStringList const&, QString const&, KGuiItem const&, KGuiItem
const&, QString const&, QFlags) () at
/lib64/libKF5WidgetsAddons.so.5
#27 0x7f7ec214ab0a in KMessageBox::warningContinueCancel(QWidget*, QString
const&, QString const&, KGuiItem const&, KGuiItem const&, QString const&,
QFlags) () at /lib64/libKF5WidgetsAddons.so.5
#28 0x7f7ec39352b8 in  () at /lib64/libKPim5MessageComposer.so.5
#29 0x7f7ec3942673 in Kleo::KeyResolver::getEncryptionKeys(QString const&,
bool) const () at /lib64/libKPim5MessageComposer.so.5
#30 0x7f7ec393923b in Kleo::KeyResolver::resolveEncryptionKeys(bool, bool&)
() at /lib64/libKPim5MessageComposer.so.5
#31 0x7f7ec393a538 in Kleo::KeyResolver::resolveAllKeys(bool&, bool&) () at
/lib64/libKPim5MessageComposer.so.5
#32 0x7f7ec3927dfe in
MessageComposer::ComposerViewBase::generateCryptoMessages(bool&) () at
/lib64/libKPim5MessageComposer.so.5
#33 0x7f7ec3928dc7 in
MessageComposer::ComposerViewBase::slotEmailAddressResolved(KJob*) () at
/lib64/libKPim5MessageComposer.so.5
#34 0x7f7ec4725232 in  () at /lib64/libQt5Core.so.5
#35 0x7f7ec59a97f5 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/lib64/libKF5CoreAddons.so.5
#36 0x7f7ec59adb9b in  () at /lib64/libKF5CoreAddons.so.5
#37 0x7f7ec3916900 in MessageComposer::EmailAddressResolveJob::start() ()
at /lib64/libKPim5MessageComposer.so.5
#38 0x7f7ec392686c in MessageComposer::ComposerViewBase::readyForSending()
() at /lib64/libKPim5MessageComposer.so.5
#39 0x7f7ec3926c0e in
MessageComposer::ComposerViewBase::send(MessageComposer::MessageSender::SendMethod,

[akregator] [Bug 469332] crashed when clicking on report link

2023-05-10 Thread Christopher Yeleighton
https://bugs.kde.org/show_bug.cgi?id=469332

--- Comment #1 from Christopher Yeleighton  ---
Created attachment 158834
  --> https://bugs.kde.org/attachment.cgi?id=158834=edit
New crash information added by DrKonqi

kontact (5.23.0 (23.04.0)) using Qt 5.15.9

I told Akgregator to follow a hyperlink in a feed article.  Kontact crashed.

-- Backtrace (Reduced):
#4  content::WebContentsImpl::CreateNewWindow () at
../../3rdparty/chromium/content/browser/web_contents/web_contents_impl.cc:3771
#5  0x7f6e483a4280 in
content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr,
base::OnceCallback)>) () at
../../3rdparty/chromium/content/browser/renderer_host/render_frame_host_impl.cc:5077
#6  0x7f6e446445ca in
content::mojom::FrameHostStubDispatch::AcceptWithResponder () at
gen/content/common/frame.mojom.cc:7074
#7  0x7f6e4837bead in
content::mojom::FrameHostStub
>::AcceptWithResponder () at gen/content/common/frame.mojom.h:1025
#8 
content::mojom::FrameHostStub
>::AcceptWithResponder () at gen/content/common/frame.mojom.h:1020

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

[akregator] [Bug 469332] crashed when clicking on report link

2023-05-10 Thread Christopher Yeleighton
https://bugs.kde.org/show_bug.cgi?id=469332

Christopher Yeleighton  changed:

   What|Removed |Added

 CC||giecr...@stegny.2a.pl

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

[knotes] [Bug 469578] notes should have a lock to avoid unintentional edits

2023-05-10 Thread Miguel Rozsas
https://bugs.kde.org/show_bug.cgi?id=469578

--- Comment #2 from Miguel Rozsas  ---
I don't have this option.
I don't understand...knotes does not have a title bar...?!?!?!
Anyway, right clicking on a note only shows options to change the note's
color or remove it.

Operating System: openSUSE Tumbleweed 20230413
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 6.2.10-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Manufacturer: ASUS

Em qua., 10 de mai. de 2023 às 11:58, Laurent Montel <
bugzilla_nore...@kde.org> escreveu:

> https://bugs.kde.org/show_bug.cgi?id=469578
>
> Laurent Montel  changed:
>
>What|Removed |Added
>
> 
>  CC||mon...@kde.org
>
> --- Comment #1 from Laurent Montel  ---
> We have it.
> Right click on title bar => lock
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[knotes] [Bug 469578] notes should have a lock to avoid unintentional edits

2023-05-10 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=469578

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
We have it.
Right click on title bar => lock

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

[knotes] [Bug 469578] New: notes should have a lock to avoid unintentional edits

2023-05-10 Thread Miguel Rozsas
https://bugs.kde.org/show_bug.cgi?id=469578

Bug ID: 469578
   Summary: notes should have a lock to avoid unintentional edits
Classification: Applications
   Product: knotes
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mig...@rozsas.eng.br
CC: myr...@kde.org
  Target Milestone: ---

Whishlist SUMMARY

Notes are good to hold information you want to be available right there, right
now.
Frequently this information needs to be copied to another place where it is
needed.
The problem is when we select a text on a note to copy it, the note enter in
edit mode and a single keyboard stroke is enough to erase that information.
I wish you could select a text on a note and the note remains in a read-only
mode to avoid accidental alteration of selected text.

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