SUMMARY Hovering over a link no longer makes the cursor a hand, and clicking on the link doesn't open the link. Right clicking and selecting "Open URL" *does* work. STEPS TO REPRODUCE 1. Get e-mail 2. Hover over link 3. Click OBSERVED RESULT No "hand" cursor, link doesn't open in browser EXPECTED RESULT Cursor turns into a hand, and link opens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon, latest packages (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION
I confirm in Plasma 6.0.1 on Opensuse Tumbleweed
Oddly enough, text converted to links (such as in a non-html message) can simply be clicked. Images/links in an HTML message must be right-clicked.
But even in non-HTML messages, cursor still does not convert to a hand.
I confirm it. I will investigate this problem. Regards
I have this same issue KDE Plasma 6.0.4 Fedora40
There have been a few other reports of the same bug. These attachments are from https://bugs.kde.org/show_bug.cgi?id=483672 and may be useful a mail with links (26.91 KB, application/mbox) https://bugs.kde.org/attachment.cgi?id=167262 another mail with links with no effect (175.22 KB, application/mbox) https://bugs.kde.org/attachment.cgi?id=167374 a sample mbox with both a working and non-working link (915 bytes, message/rfc822) https://bugs.kde.org/attachment.cgi?id=170890
*** Bug 483672 has been marked as a duplicate of this bug. ***
*** Bug 484481 has been marked as a duplicate of this bug. ***
*** Bug 489986 has been marked as a duplicate of this bug. ***
*** Bug 489647 has been marked as a duplicate of this bug. ***
One other problem doesn't seem to be mentioned here: the old behavior opened the link in the background and DID NOT CHANGE FOCUS. Now, no matter how it's done, if a link is opened, focus immediately changes to browser. I suppose there may be an argument for immediately changing focus, but this is a regression from many years of no focus change.
I just noticed this seems to be fixed. KMail 6.2.3 (24.08.3) Cursor turns into a hand when hovering over links. HTML and non-HTML messages. Is that intentional? Or did it get fixed as a result of another change?
I confirm this is resolved in KMail 6.2.3 Unfortunately I don't know which commit or merge request fixed it.
Click on links still cause focus to jump to browser. This never happened before this bug was reported. That is still a regression.
(In reply to Garry Williams from comment #14) > Click on links still cause focus to jump to browser. This never happened > before this bug was reported. That is still a regression. That is a different issue than the one reported in this bug. Please open a new bug report for that issue. Thanks.
This has recurred on Fedora, version 6.4.0, exactly the same symptoms as previously reported. I've also seen similar reports on the kdepim-users mailing list from people running Tumbleweed.
For some mails : clicking has no effect. middle-clicking launch the url. Operating System: openSUSE Tumbleweed 20250515 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.6-1-default (64-bit) Graphics Platform: Wayland
Confirmed on Fedora, middle clicking does what I expect left clicking to do.
Confirmed v6.4.2 on Fedora, middle click and CTRL+click work.
*** Bug 505923 has been marked as a duplicate of this bug. ***
As noted in duplicate bug - If I start Kontact from a terminal I observe "Can not adopt content from a different WebEngineProfile." when I left click on the link.
This seems to be fixed for me now: Operating System: KDE neon User Edition KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.14.0-24-generic (64-bit) Graphics Platform: Wayland
KMail: 6.4.3 (25.04.3) KDE Frameworks: 6.16.0 Qt: Using 6.9.1 and built against 6.9.1 KDE neon User Edition (Xcb) Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.12.10-76061203-generic Some links work, but others do not, so not fully fixed.
I have done some experimenting with troublesome links. No great discoveries. All the links I have found in akregator fail to launch with left click. Links in kmail may or may not launch with left click. Middle click always works. With troublesome links I found if I copy them and use them else where ( like paste into a line on konsole ) a left click will work. Also if I forward the email with the troublesome link, even to the original recipient, I can launch the link with a left click. This suggests that it is the context and not the link itself that is causing the issue. As for the error message ( Can not adopt content from a different WebEngineProfile ) a web search didn't find anything ( i used duckduck ). Duck AI came up with some suggestions. .. GPT-4o mini The error message "Cannot adopt content from a different WebEngineProfile" typically occurs in applications that use web engines, such as those built on Chromium or similar frameworks. This error indicates that there is an attempt to share or transfer content (like cookies, sessions, or other data) between different web engine profiles, which is not allowed due to security and isolation measures. Possible Causes and Solutions 1. Profile Isolation Cause: Each web engine profile is designed to be isolated from others to maintain security and privacy. Solution: Ensure that you are using the same profile for all operations. If you need to share data, consider using a common profile or explicitly managing data transfer. 2. Incorrect Context Usage Cause: The application may be trying to access content from a different context or session. Solution: Check your code to ensure that all content access is happening within the same context. Avoid mixing contexts from different profiles. 3. Session Management Cause: If your application manages multiple sessions, it might inadvertently try to access data from a different session. Solution: Review your session management logic to ensure that sessions are correctly handled and isolated. GPT-4o mini The error message "Cannot adopt content from a different WebEngineProfile" typically occurs in applications that use web engines, such as those built on Chromium or similar frameworks. This error indicates that there is an attempt to share or transfer content (like cookies, sessions, or other data) between different web engine profiles, which is not allowed due to security and isolation measures. Possible Causes and Solutions 1. Profile Isolation Cause: Each web engine profile is designed to be isolated from others to maintain security and privacy. Solution: Ensure that you are using the same profile for all operations. If you need to share data, consider using a common profile or explicitly managing data transfer. 2. Incorrect Context Usage Cause: The application may be trying to access content from a different context or session. Solution: Check your code to ensure that all content access is happening within the same context. Avoid mixing contexts from different profiles. 3. Session Management Cause: If your application manages multiple sessions, it might inadvertently try to access data from a different session. Solution: Review your session management logic to ensure that sessions are correctly handled and isolated.