[digikam] [Bug 453275] Renaming files is not folder aware, even with folder aware option
https://bugs.kde.org/show_bug.cgi?id=453275 --- Comment #3 from Maik Qualmann --- Maybe I'm misunderstanding you and you want to use the folder date to rename. This function is currently not available. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453275] Renaming files is not folder aware, even with folder aware option
https://bugs.kde.org/show_bug.cgi?id=453275 --- Comment #2 from Maik Qualmann --- Correction, rename is F2. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397310] DigiKam file renaming issue
https://bugs.kde.org/show_bug.cgi?id=397310 --- Comment #5 from Maik Qualmann --- Correction, rename is F2. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453275] Renaming files is not folder aware, even with folder aware option
https://bugs.kde.org/show_bug.cgi?id=453275 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Renaming in the import dialog is still limited at the moment. Rename the images later with the "Rename" (F3) function. You have to activate the metadata in the camera settings of digiKam under Behavior (makes the connection slower) so that e.g. creating folders by date works correctly. Maik -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453252] 'Append newline to file on save' moves cursor on save
https://bugs.kde.org/show_bug.cgi?id=453252 Christoph Cullmann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/commit/a ||1b91bacd3b919c41c68b3aed795 ||77d2408e9564 Resolution|--- |FIXED --- Comment #2 from Christoph Cullmann --- Git commit a1b91bacd3b919c41c68b3aed79577d2408e9564 by Christoph Cullmann. Committed on 02/05/2022 at 05:34. Pushed by cullmann into branch 'master'. avoid cursor move on insert of line at EOF on save M +16 -0src/document/katedocument.cpp https://invent.kde.org/frameworks/ktexteditor/commit/a1b91bacd3b919c41c68b3aed79577d2408e9564 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 389052] Desired connections run away just before clicking the "connect" button or entering password
https://bugs.kde.org/show_bug.cgi?id=389052 Cajus Pollmeier changed: What|Removed |Added CC||k...@cajus.naasa.net --- Comment #27 from Cajus Pollmeier --- If you're in a place with dozens of SSIDs around, it is not possible to connect to the correct one using the applet, as the list is re-arranged all the time, and you've no chance to enter the password at that speed. As stated by others before, this can quickly become a security issue, as the password field keeps open, but suddenly belongs to the wrong entry - of whatever type. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 453278] Baloo doesn't reindex files after they have been moved or renamed - manually reindexing is necessary...
https://bugs.kde.org/show_bug.cgi?id=453278 tagwer...@innerjoin.org changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||tagwer...@innerjoin.org --- Comment #3 from tagwer...@innerjoin.org --- Does Bug 392793 describe this? (and https://bugs.kde.org/show_bug.cgi?id=392793#c3?) I think I still run into the issue if renaming a parent folder (or sometimes have trouble, not every time) and if I've renamed the parent folder, anything I then do in it is not picked up. I don't think the patches discussed in 392793 caught all the instances and didn't make it into production. A "balooctl check" works to get baloo back "up to date" (in the case of renames) B.T.W. I think you see the difference between TAG- and TA prefixes if you have a multi-word or hierarchical tag, cf tagging with "Parent/Child" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 453281] New: When muted notifications are unmuted after a set time the notification sound stays muted if the unmuting happens at login
https://bugs.kde.org/show_bug.cgi?id=453281 Bug ID: 453281 Summary: When muted notifications are unmuted after a set time the notification sound stays muted if the unmuting happens at login Product: frameworks-knotifications Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Whenever I set my notifications to "silent until such time" the sound stays muted if i log out and log in only after the time when the notifications should be unmuted STEPS TO REPRODUCE 1. mute your notifications for some set time, i.e. "until tomorrow" 2. take note of the actual time when the notifications should unmute, i.e. 6:00am 3. logoff 4. stay away from that account until **after** the time from 2., then log in again OBSERVED RESULT After logging in, notifications are unmuted but the sound for notifications, for example the "pop" sound from kmix when you change volume, is **not** EXPECTED RESULT I expect **all** notifications to be unmuted, including sound SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220428 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION Workaround: manually mute and then unmute notifications Fun fact: this can easily lead to believing that sound has stopped working, triggering some longish bug search o.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #151 from Henrik Hudson --- (In reply to naumenko.dmitriy from comment #150) > (In reply to wget from comment #149) > > From my side, I can confirm the related problems have been fixed in the > > latest 5.24 dot releases. However, to make this happens, I had to reset the > > KDE related conf (and I took the initiative to reset all the KDE apps conf > > too, in order to start clean, since I was using the same install since 2018 > > already). I assume there was some leftovers from previous 5.x versions > > making KWin or related to misbehave. > > ``` > > #!/usr/bin/env bash > > cd ~/ > > rm -rv .kde > > rm -rv .cache/plasmashell* > > rm -rv .cache/org.kde.dirmodel-qml.kcache > > rm -rv .cache/kioexec/ .cache/krunner/ .cache/ksycoca5* > > rm -rv .cache/krunnerbookmarkrunnervirefoxdbfile.sqlite > > rm -rv .config/plasma* > > rm -rv .config/kde* > > cd .local/ > > rm -rv kate/ kded5/ klipper/ knewstuff3/ kscreen/ konsole/ kwalletd/ > > ksysguard/ kmail2/ kcookiejar/ kactivitymanagerd/ > > cd share/ > > rm -rv dolphin kate kcookiejar kded5 keyrings klipper kmail2 knewstuff3 > > konsole kscreen ksysguard kwalletd kxmlgui5 plasma_engine_comic plasma > > plasma_notes org.kde.gwenview > > cd ~/.config/ > > rm -rv akonadi* KDE kconf_updaterc baloo* dolphinrc drkonqirc gwenviewrc > > kmail2rc k*rc katemetainfos > > ``` > > [src.](https://forum.manjaro.org/t/how-reset-all-kde-settings/21518/3) > > My KDE daily driver machine is a DELL Inspiron 5579 with i7-8550U and Intel > > UHD 620 as "graphic" card. > > Unfortunately, this did not work for me. I've gone as far as reinstalling > all of Plasma to no avail. Yeah, I completely rebuilt / re-installed 2 systems with Arch 3 or so weeks ago. They're both AMD GPUs and plugged into the same 2 monitors. The one with HDMI connections has the problems described here. The DP port does not. It seems something (plasma, X, etc...???) doesn't wait long enough to see if the screen is still there when coming out of monitor "off" mode and then moves everything to "one" screen. I don't put my systems to sleep, just the monitors. This exact problem didn't start for me until the last 6 months or so (also Arch based) and it's been pretty consistent. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452159] krita crashed and proceeded to glitch whenever i try to zoom in or out- as in it's taking really really long to move around
https://bugs.kde.org/show_bug.cgi?id=452159 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451950] Crash while loading Custom Latte Dock Theme
https://bugs.kde.org/show_bug.cgi?id=451950 --- Comment #2 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 watching all bug changes.
[lattedock] [Bug 451492] [wayland / multimonitor] editing dock/panel causes latte to crash
https://bugs.kde.org/show_bug.cgi?id=451492 --- Comment #4 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 watching all bug changes.
[lattedock] [Bug 451490] [startup] latte docks dodge void at boot
https://bugs.kde.org/show_bug.cgi?id=451490 --- Comment #2 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 watching all bug changes.
[lattedock] [Bug 429529] dock resizes if contents are too long and never resize back
https://bugs.kde.org/show_bug.cgi?id=429529 --- Comment #2 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 watching all bug changes.
[kwin] [Bug 453070] [Wayland] Night Color not working on Wayland session
https://bugs.kde.org/show_bug.cgi?id=453070 Robert Britton changed: What|Removed |Added CC||britto...@protonmail.com --- Comment #3 from Robert Britton --- I can third this issue. Like Behzad -- Night Color works just fine on X11, but it's completely broken on Wayland. I'm on Arch with a fully up-to-date system as of today 5/1. I can't say whether or not this happened before the current version of Plasma I'm on was released into Arch repositories; I've only started trying to use Wayland in the past week. Night Color doesn't work whatsoever for me on Wayland. It doesn't matter what activation time you set it to or what temperature you set it to adjust to, it just doesn't work. It's as if it doesn't exist. The Night Color widget can be toggled on or off, and it displays changes as such, but nothing happens. I AM NOT A DEVELOPER but from my troubleshooting I think this might have to do with the way monitor names are detected and tracked in Wayland versus X11. The other major issue with Wayland I've been having is that on my current user account, existing since January and whatever version of Plasma was available on Arch then, any changes I make to display settings don't get saved, either resolution or refresh rate. This means I have to re-set my monitor to output at 144 Hz every single time I start a Wayland session. I've tested pretty extensively with a test user I made this weekend, and that user doesn't have the settings-not-being-saved issue, but it does also have a broken Night Color. I use a single monitor with DVI. I think these two issues may possibly be related somehow. System info: Operating System: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz Memory: 15.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 running proprietary driver version 510.60.02 I'd be happy to provide more info if needed -- config files, etc. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 --- Comment #27 from Alexander Lohnau --- I will makeq a mockup before implementing the UI where I will consult the VDG and add it as an attachment to this bug report. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 Alexander Lohnau changed: What|Removed |Added Assignee|k...@privat.broulik.de |alexander.loh...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 453280] New: kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 Bug ID: 453280 Summary: kded5 leaks X-Window connections: Maximum number of clients reached Product: frameworks-kded Version: 5.91.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: rocketra...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I started receiving the error "Maximum number of clients reached" when trying to open new X-based programs. Upon investigation, I saw that `kded5` was using 146 connections -- the next highest program was using 8 [1]. Restarting kded5 solved the problem. [1] I used the script found here to identify this: https://unix.stackexchange.com/a/700637/11249 STEPS TO REPRODUCE 1. Leave desktop running for a few days/weeks, until X reports "Maximum number of clients reached" when trying to start a new window. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.20-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen Threadripper 1950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 590 Series ADDITIONAL INFORMATION It appears I'm not the only one experiencing this probem. See also: https://unix.stackexchange.com/questions/700366/kded-taking-up-x-client-connections -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] When a device connects, it is positioned too far down for a moment, causing it to overlap the separator line
https://bugs.kde.org/show_bug.cgi?id=438610 --- Comment #19 from Nate Graham --- Ah, the problem is that Logic.conectedDevicesCount() is imperative, and not a property. So when that changes, the UI code doesn't get notified and updated itself as it should. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications
https://bugs.kde.org/show_bug.cgi?id=451612 --- Comment #11 from wodenc...@gmail.com --- Created attachment 148507 --> https://bugs.kde.org/attachment.cgi?id=148507=edit New crash information added by DrKonqi kwin_x11 (5.24.4) using Qt 5.15.3 - What I was doing when the application crashed: I hit alt tab and immediately kwin crashed. I installed all the debug symbols, I see this bug has already been reported but the backtrace I am including is complete (no ??) and the main report appears to not be complete. I hope this helps. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139807870436672) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139807870436672) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139807870436672, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f279318a476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f27931707f3 in __GI_abort () at ./stdlib/abort.c:79 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications
https://bugs.kde.org/show_bug.cgi?id=451612 wodenc...@gmail.com changed: What|Removed |Added CC||wodenc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453279] New: Krita Epub not downloading from manual website
https://bugs.kde.org/show_bug.cgi?id=453279 Bug ID: 453279 Summary: Krita Epub not downloading from manual website Product: krita Version: unspecified Platform: Android OS: All Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: austinman...@gmail.com Target Milestone: --- Created attachment 148506 --> https://bugs.kde.org/attachment.cgi?id=148506=edit Krazy characters SUMMARY Hello I am on my tab s7 and I was attempting to download the epub manual. This was on both the android tablet and android phone the attachment below shows what happens STEPS TO REPRODUCE 1. Go to the official website 2. Download the epub from the manual link 3. Watch the crazy characters load in OBSERVED RESULT What appears to be a broken link EXPECTED RESULT A download prompt for the epub version SOFTWARE/OS VERSIONS Android at the latest update ADDITIONAL INFORMATION Was reproducible on both samsung internet and chrome -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 453278] Baloo doesn't reindex files after they have been moved or renamed - manually reindexing is necessary...
https://bugs.kde.org/show_bug.cgi?id=453278 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453247] Paste into Active Layer and Paste at Cursor paste at the wrong locations
https://bugs.kde.org/show_bug.cgi?id=453247 tomtomtomreportin...@gmail.com changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 453278] Baloo doesn't reindex files after they have been moved or renamed - manually reindexing is necessary...
https://bugs.kde.org/show_bug.cgi?id=453278 --- Comment #2 from piedro --- Baloo stops working after initial indexing - this also doesn't index new files added later. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 karl...@gmail.com changed: What|Removed |Added CC||karl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 453278] Baloo doesn't reindex files after they have been moved or renamed - manually reindexing is necessary...
https://bugs.kde.org/show_bug.cgi?id=453278 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #1 from piedro --- After changing a folder name or moving a folder "balooctl status" stays idle - shouldn'T it start working right away? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 453278] New: Baloo doesn't reindex files after they have been moved or renamed - manually reindexing is necessary...
https://bugs.kde.org/show_bug.cgi?id=453278
Bug ID: 453278
Summary: Baloo doesn't reindex files after they have been moved
or renamed - manually reindexing is necessary...
Product: frameworks-baloo
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: piedro.kul...@gmail.com
Target Milestone: ---
SUMMARY
on my system baloo only searches the documents and music folder. Tagging,
content and file name search works initially. But when I work with the files -
renaming them, moving some in subfolders or renaming the containing folder
they disappear from the index.
STEPS TO REPRODUCE
1. index a file in a subfolder in Documents ("recent_path", "recent_file_name")
2. rename the subfolder or the file or both ("current_path",
"current_file_name")
3. search for the content or the file name of the current file in the current
folder
OBSERVED RESULT
Absurd: the search can't find the file name nor the content of the file in the
current folder - though it is right there in the dolphin window if you do not
search for it (navigate > current folder > content: this one current file!)
EXPECTED RESULT
To find the only file in the current folder by it's name within the current
folder...
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch linux 5.17.5-arch1-1, fully updated
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
the current file's index can be shown with
"balooshow -x /current_path/current_file_name"
but the file index information output still contains the old file path
"/recent_path/recent_file_name"!
So my guess is that after renaming a file the index isn't updated - baloo
sleeps on the job. It doesn't matter to wait a while or reboot - only
reindexing does the job to update the files index information to include the
correct path and file name.
On a curious note: Is it normal that some tags are shown as "TAG-tagname1" and
others as "TAtagname2" or is this a hint that something with the indexing
isn't right anyway?
--
You are receiving this mail because:
You are watching all bug changes.
[kstars] [Bug 453239] Get segmentation fault (core dumped) when starting Kstars on Kubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453239 --- Comment #8 from Otto --- I added the PPA in a couple machines (Kubuntu and Lubuntu 22.04). That fixed the problem. Best Regards. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 453277] New: The Kwin scripting tutorial misses crucial info
https://bugs.kde.org/show_bug.cgi?id=453277 Bug ID: 453277 Summary: The Kwin scripting tutorial misses crucial info Product: docs Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Missing Content Assignee: kde-doc-engl...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- At: https://develop.kde.org/docs/extend/plasma/kwin/ Missing info: https://forum.kde.org/viewtopic.php?f=305=163749=454755#p454755 https://askubuntu.com/a/1406027/19033 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453276] [Wayland] icons on dolphin stutter when being dragged in window
https://bugs.kde.org/show_bug.cgi?id=453276 ptgarl...@protonmail.com changed: What|Removed |Added CC||ptgarl...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453276] New: [Wayland] icons on dolphin stutter when being dragged in window
https://bugs.kde.org/show_bug.cgi?id=453276 Bug ID: 453276 Summary: [Wayland] icons on dolphin stutter when being dragged in window Product: dolphin Version: 22.04.0 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: ptgarl...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** After opening dolphin, When I click on a file or directory and drag it across the screen it stutters and pops around the mouse until it leaves the Dolphin window. After it leaves the Dolphin window, the icon is able to smoothly be dragged across the screen. *** STEPS TO REPRODUCE 1. Open Dolphin 2. Go to any directory and click-and-drag the icon 3. drag in dolphin to notice stuttering and out of dolphin to notice smooth. OBSERVED RESULT Icon stutters across the dolphin window EXPECTED RESULT Icon should smoothly be drug across the window SOFTWARE/OS VERSIONS Distribution: Garuda Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares
https://bugs.kde.org/show_bug.cgi?id=452924 --- Comment #7 from piedro --- So I do not think it's only about reading the files metadata - moving the file to the network share and back loses the metadata! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares
https://bugs.kde.org/show_bug.cgi?id=452924 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #6 from piedro --- Same here - I think it is due to extended attributes not correctly assigned. I thought this is happening because my network file server (Synology NAS) might not support xattr data. But I experimented quite a lot and it turns out the server does. I checked the xattr state of files I copied to the server and it turns out they are there. Copying the files in dolphin to the network share and then moving the file back results in a loss of all file tags which are, as I understand saved as extended file attributes. Here's parts of my post on reddit: - Hi! As I understand the KDE file tags that can be applied by dolphin get written into the extended attributes of the tagged files. So that's fine and works most of the times... But it seems that dolphin loses the ability to read or assign tags in any mounted network folder - though the network server uses btrfs as well and the shares (I tried nfs and cifs/samba mounting) should support unix attributes. So do I need additional mount options to make KDE tags "stick" in network shares? I do not seem to have the same problem with local mounts Anyone? Thanks! Cheers, p. p.s.: Btw... - the context menu in dolphin still shows the "Add tag" entry - but adding tags in the mounted folders doesn't do anything... p. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453275] New: Renaming files is not folder aware, even with folder aware option
https://bugs.kde.org/show_bug.cgi?id=453275 Bug ID: 453275 Summary: Renaming files is not folder aware, even with folder aware option Product: digikam Version: 7.6.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: AdvancedRename-file Assignee: digikam-bugs-n...@kde.org Reporter: jader...@msn.com Target Milestone: --- SUMMARY I have not done file renaming in digiKam yet. All of the file renaming has happened outside of digiKam. I would like to use digiKam going forward, but I am running into errors. STEPS TO REPRODUCE 1. Have a pre-existing name schema. For pictures of my cat in 2022 it is Bella 22 ##. 2. Import a new picture 3. Select the picture. 4. In the rename dialog enter Bella 22 ##[f] (or Bella [date:yy] ##[f]) OBSERVED RESULT The dialog will say that the new name is Bella 22 01. EXPECTED RESULT The dialog to say that the new name is Bella 22 07 (the directory already contains Bella 22 01 - Bella 22 06). 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 watching all bug changes.
[krita] [Bug 446376] Improperly escaped description field may bork documentinfo.xml in .kra files
https://bugs.kde.org/show_bug.cgi?id=446376 --- Comment #1 from Nagy Tibor --- The name field in the predefinedimage XMLs are also affected by this. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 453274] New: [openconnect] Add the possiblity to edit the useragent of a VPN connection for openconnect
https://bugs.kde.org/show_bug.cgi?id=453274 Bug ID: 453274 Summary: [openconnect] Add the possiblity to edit the useragent of a VPN connection for openconnect Product: plasma-nm Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: earen...@toleressea.fr Target Milestone: --- SUMMARY It could be usefull to allow to edit the useragent of an openconnect VPN connection. I have a working tree with the last version of openconnect (minimum version 9.0) because I need the function openconnect_set_useragent added in the last version. ADDITIONAL INFORMATION You can found a commit that add this feature here: https://invent.kde.org/earendilfr/plasma-nm/-/commit/fef77307bcf272702d445327524bbd317d0c514f I have no idea if it's possible to submit directly a "merge request" though the gitlab portal of KDE... -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Couldn't write accent mark
https://bugs.kde.org/show_bug.cgi?id=410876 juan changed: What|Removed |Added CC||oscar.fernandez.pujol@gmail ||.com --- Comment #5 from juan --- *** Bug 436830 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 436830] In Catalan language can't insert some characters
https://bugs.kde.org/show_bug.cgi?id=436830 juan changed: What|Removed |Added Resolution|--- |DUPLICATE CC||jumase+fo...@disroot.org Status|REPORTED|RESOLVED --- Comment #1 from juan --- This seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=410876 *** This bug has been marked as a duplicate of bug 410876 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450911] Very soon or later i always suddenly loose control over the touchpad
https://bugs.kde.org/show_bug.cgi?id=450911 --- Comment #12 from PK --- Too bad... still a crash! But things seem better... -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Couldn't write accent mark
https://bugs.kde.org/show_bug.cgi?id=410876 juan changed: What|Removed |Added CC||fcojpe...@gmail.com --- Comment #4 from juan --- *** Bug 439933 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 439933] I cannot type words with a Spanish accent like á
https://bugs.kde.org/show_bug.cgi?id=439933 juan changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||jumase+fo...@disroot.org --- Comment #1 from juan --- This seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=410876 *** This bug has been marked as a duplicate of bug 410876 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453161] touching certain places of my touch screen makes tap-to-click crash
https://bugs.kde.org/show_bug.cgi?id=453161 --- Comment #2 from PK --- Too bad... still a crash! But things seem better... -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Couldn't write accent mark
https://bugs.kde.org/show_bug.cgi?id=410876 juan changed: What|Removed |Added CC||jumase+fo...@disroot.org --- Comment #3 from juan --- I confirm this behaviour on version 20.12.0 from Debian stable repositories. In the hope that this could be solved in latest version (22.04.0), I tried the flatpak one; unfortunately it still happens on that version. As mentioned on bugreport https://bugs.kde.org/show_bug.cgi?id=419137 , all dead keys don't work —accute and grave accents (ú, ù), circumflex (û), diaeresis (ü). I mean this doesn't seem to be related to a specific keyboard layout, not even to an specific language. I've tried with spanish dvorak and qwerty, but none of them worked as expected. There are also reports with Catalan (https://bugs.kde.org/show_bug.cgi?id=436830) and French (https://bugs.kde.org/show_bug.cgi?id=419137) layouts that suggest this is about dead keys in general. I've read about something related to QT libraries but I don't know how to test that, and also the reference (https://bugs.kde.org/show_bug.cgi?id=118862) is quite old. I'm usin XFCE, I don't know if that has anything to do. However, I use kmail, appimage of kdenlive, akgregator, and all of them recognize dead keys properly. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453273] New: KScreen 2 behavior when I close my laptop lid should be configurable in the control center
https://bugs.kde.org/show_bug.cgi?id=453273 Bug ID: 453273 Summary: KScreen 2 behavior when I close my laptop lid should be configurable in the control center Product: KScreen Version: 5.24.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kde_bugrepor...@snkmail.com Target Milestone: --- SUMMARY *** When I add a second display and configure power settings to do nothing, KScreen2 moves all windows to the second monitor and crashes both desktops when I close my laptop lid. *** After adding an external monitor as a second display in Display Manager, setting the laptop lid action under Power Management settings to "Do nothing" and checking "Even when external monitor is connected" STEPS TO REPRODUCE 1. Install Kubuntu on a laptop 2. Acquire and connect an external monitor 3. Go to Control Center -> Power Management, ensure "Button events handling" is checked, and select "Do nothing" for "When laptop lid closed", and optionally click "Even when an external monitor is connected" 4. Edit /etc/systemd/logind.conf, and set HandleLidSwitch=ignore 5. Restart. 6. Login and open some windows. 7. Close your laptop lid. OBSERVED RESULT The external screen blacks out and restarts, and all windows jump over to the external screen. When I open my laptop, the windows don't jump back; I have to either kill them and restart them (conky) or drag them back. Additionally plasma desktop seems to crash and restart on both screens. EXPECTED RESULT Nothing at all should happen, since I never defined that I want windows to move to the external monitor. I recognize the added value of having windows move to the external monitor - this would be useful if I was using the monitor instead of my laptop monitor. However, for my use case, this is not helpful. This behavior would be explicitly configurable in KDE Control Center, so people who want windows to jump to the external monitor could do that, and people who don't could configure it differently. I should not need to disable KScreen2 and use arandr; that's not something a beginner user would even know how to do. SOFTWARE/OS VERSIONS OS: Linux Linux Distro: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Additional Info: I'm using Xorg -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453272] New: External tools: forward slash in name causing all tools to disapear
https://bugs.kde.org/show_bug.cgi?id=453272 Bug ID: 453272 Summary: External tools: forward slash in name causing all tools to disapear Product: kate Version: 22.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: witchhunter...@protonmail.com Target Milestone: --- SUMMARY In External tools settings, adding new tool named with forward slash character creates new folder in ~/.config/kate/externaltools. Upon restart all default tools in before mentioned folder are gone. STEPS TO REPRODUCE 1. Configure Kate > External tools > Add tool 2. Create new tool which name contains / character 3. Restart Kate OBSERVED RESULT All default tools are deleted including newly added one, or at best case newly added tool is not in the list. EXPECTED RESULT New tool should be added. SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition, VM KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-40-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450911] Very soon or later i always suddenly loose control over the touchpad
https://bugs.kde.org/show_bug.cgi?id=450911 --- Comment #11 from PK --- All my troubles seem to have gone... Of all the possible solutions I tried the last one actually worked! I found it here https://askubuntu.com/questions/965856/kworker-blocked-for-more-than-120-seconds-ubuntu-17-10/1363359#1363359 "The solution was for me to switch the whole KWin compositing from OpenGL / GLX to OpenGL ES / EGL. For this, the corresponding config file must be edited." I really not have so much a clue what that means but it works 100%! The result is impressive. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453161] touching certain places of my touch screen makes tap-to-click crash
https://bugs.kde.org/show_bug.cgi?id=453161 --- Comment #1 from PK --- All my troubles seem to have gone... Of all the possible solutions I tried the last one actually worked! I found it here https://askubuntu.com/questions/965856/kworker-blocked-for-more-than-120-seconds-ubuntu-17-10/1363359#1363359 "The solution was for me to switch the whole KWin compositing from OpenGL / GLX to OpenGL ES / EGL. For this, the corresponding config file must be edited." I really not have so much a clue what that means but it works 100%! The result is impressive. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452915] invert scroll direction shows as enabled but is not actually working upon rebooting when using bluetooth mouse
https://bugs.kde.org/show_bug.cgi?id=452915 i...@gmx.net changed: What|Removed |Added CC||i...@gmx.net --- Comment #1 from i...@gmx.net --- I have this identical behaviour after upgrading to Kubuntu 22.04, Plasma 5.24.4. KDE Framework 5.92.0 Hardware: Bluetooth Mouse, Lenovo Laptop 530 Yoga Problem: Invert Scroll setting is lost after Logout or Restart. Scrolling is no longer inverted. Workaround: Switch off the setting, click Apply, Switch ON setting again. Apply. Then it is working. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 452252] Kate crash on duplicate session
https://bugs.kde.org/show_bug.cgi?id=452252 --- Comment #3 from André Hübert Johansen --- Attempted duplicating a sessions in Kate 21.12.2 (Fedora), no crash. Seem to remember I had no saved session at the time; this time I attempted duplicating a saved session. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453271] New: Certain methods of mouse movement break canvas input usage, for example by using xdotool
https://bugs.kde.org/show_bug.cgi?id=453271 Bug ID: 453271 Summary: Certain methods of mouse movement break canvas input usage, for example by using xdotool Product: krita Version: 5.0.6 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- SUMMARY In Krita 5.0.5 and 5.0.6, using xdotool (https://manpages.ubuntu.com/manpages/trusty/man1/xdotool.1.html) to move the mouse will break canvas input usage, until the dockers/menus are interacted with or alt-tab is used. It's possible this is related to other cases of canvas input breakage, for example as described in https://old.reddit.com/r/krita/comments/ufw4x3/krita_506_shift_space_and_mouse_right_click/ , especially as this breakage does NOT occur in Krita 5.0.2. STEPS TO REPRODUCE 0. Install xdotool 1. Create an executable bash script with the following code: #!/bin/bash # requires xdotool package xdotool mousemove 1080 700 2. Bind the executable script to a DE shortcut. 3. Move Krita to the right half of your screen. 4. While cursor is over Krita, execute the script using the DE shortcut. 5. Attempt to use any canvas input shortcut. OBSERVED RESULT Nothing happens. EXPECTED RESULT Canvas input shortcuts should still be usable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.12.12 (appimage) -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 453270] New: Have different import sources (Amazon, Discogs, Musicbrainz, etc.) parse metadata from provided URLs
https://bugs.kde.org/show_bug.cgi?id=453270 Bug ID: 453270 Summary: Have different import sources (Amazon, Discogs, Musicbrainz, etc.) parse metadata from provided URLs Product: kid3 Version: 3.9.x Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: intergalacti...@protonmail.ch Target Milestone: --- Created attachment 148505 --> https://bugs.kde.org/attachment.cgi?id=148505=edit Image showing reduced identification between editions Rather than File > Import Musicbrainz Release / Discogs, where you input artist and release name, make possible to provide a URL and have the metadata parsed. For example tag files by providing a URL such as: https://musicbrainz.org/release/c69d328a-5ea0-4b08-a4f7-93e6ac196563 or: https://www.discogs.com/release/1048226-Electric-Six-Se%C3%B1or-Smoke Reason: Research from Discogs/Musicbrainz may be already open in browser; faster to transport URL into kid3 than looking up information again within the program. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453269] Screen display offset from desktop after boot and login until resolution is changed and switched back
https://bugs.kde.org/show_bug.cgi?id=453269 bartek...@gmail.com changed: What|Removed |Added CC||bartek...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453269] New: Screen display offset from desktop after boot and login until resolution is changed and switched back
https://bugs.kde.org/show_bug.cgi?id=453269 Bug ID: 453269 Summary: Screen display offset from desktop after boot and login until resolution is changed and switched back Product: plasmashell Version: 5.24.4 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bartek...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY This is a problem I have on my system for some time, where the first login after boot has mismatched desktop and display area, making interaction with the desktop very difficult. STEPS TO REPRODUCE 1. I have no idea how to reproduce it outside of my PC. For me it happens every time after the first login after reboot. OBSERVED RESULT Mismatched desktop and display area. This video shows what happens: https://www.youtube.com/watch?v=uyDL2vtc9jo EXPECTED RESULT Desktop interaction should work normally. SOFTWARE/OS VERSIONS Linux, debian testing KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION If that's relevant, I'm using proprietary nvidia drivers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440399] Focus between UI elements and canvas doesn't switch fast enough, often leading to clashing functionality of hotkeys
https://bugs.kde.org/show_bug.cgi?id=440399 --- Comment #2 from tomtomtomreportin...@gmail.com --- Another case: Change opacity of a layer, then immediately attempt to rotate the canvas with a canvas input bound to a number. This will result in both the canvas rotating AND digits being added to the opacity value. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 230129] Cannot connect without running krfb in KDE4
https://bugs.kde.org/show_bug.cgi?id=230129 Ömer Fadıl USTA changed: What|Removed |Added CC||omeru...@gmail.com --- Comment #2 from Ömer Fadıl USTA --- Hello Pal , sorry to disturb you with this ancient bug (11 years old ), just wantted to learn if this bug still exist in current version of KDE Plasma/Gears ? I want to close bug reports which even doest exist with current versions. I am waiting your reponse to close this bug report -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450482] Remote folder previews no longer working after recent update to Plasma 5.24
https://bugs.kde.org/show_bug.cgi?id=450482 --- Comment #11 from public.paul.meier+...@gmail.com --- Problem persists in current KDE Neon Unstable Edition KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453268] New: KWin's Wayland session limits framerate when borderless in XWayland applications.
https://bugs.kde.org/show_bug.cgi?id=453268 Bug ID: 453268 Summary: KWin's Wayland session limits framerate when borderless in XWayland applications. Product: kwin Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: nexustc...@gmail.com Target Milestone: --- On KWin's Wayland session, the framerate inside XWayland applications gets limited to the monitor's refresh rate when either setting the window to become fullscreen or removing its borders through the context menu. This can be seen with glxgears. STEPS TO REPRODUCE 1. Run "env vblank_mode=0 __GL_SYNC_TO_VBLANK=0 glxgears" 2. Remove the window borders with the context menu (Alt-F3->More Actions->No border). OBSERVED RESULT The framerate is uncapped until the window borders get removed, then it drops to the monitor refresh rate. EXPECTED RESULT Uncapped framerate SOFTWARE/OS VERSIONS OS: openSUSE Tumbleweed Linux Kernel: 5.17.4-1 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I also tested Mutter and wlroots (Wayfire) to reproduce the issue there, both through a standalone wayland session and nested inside KWin itself, but both work as expected. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453076] Kate crashes on closed
https://bugs.kde.org/show_bug.cgi?id=453076 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/kate/commit/6fe4aecde ||5f62828e5bb3e11640524955747 ||01dd Resolution|--- |FIXED --- Comment #1 from Christoph Cullmann --- Git commit 6fe4aecde5f62828e5bb3e1164052495574701dd by Christoph Cullmann. Committed on 01/05/2022 at 18:28. Pushed by cullmann into branch 'master'. ensure app adaptor survives long enough the document deletion signals will otherwise access already destructed objects M +1-1apps/lib/kateapp.cpp M +5-4apps/lib/kateapp.h https://invent.kde.org/utilities/kate/commit/6fe4aecde5f62828e5bb3e1164052495574701dd -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 450475] Crash when adding notes
https://bugs.kde.org/show_bug.cgi?id=450475 Alexander changed: What|Removed |Added CC||cookie...@web.de --- Comment #2 from Alexander --- Still crashing: KDE Plasma 5.24.5. Is anybody taking notice of this? Well, except me... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453218] Restore split views sharing tabs globally from 18.12.3
https://bugs.kde.org/show_bug.cgi?id=453218 --- Comment #5 from tcanabr...@kde.org --- I’ll keep this open, if any other Konsole dev want to try to revive this (without removing the current approach), I’ll be happy to review the code. On Sun, 1 May 2022 at 19:52 wrote: > https://bugs.kde.org/show_bug.cgi?id=453218 > > --- Comment #4 from twojstaryzdomu+...@gmail.com --- > > You do not consider, a lot of people did and we had a pile of bugs opened > > for that. > It was designed that way and that works for me. To throw the old design > out of > the window and replace it with a worse (from a session management > perspective) > is not an improvement. > > > You can still manage two views independently and use tabs independently: > > create two Konsole windows, and open tabs on them. > That's no solution, two separate windows cannot be managed simultaneously > without switching back and forth between them. > > I doubt tue old style will get back, but we can work with compromises: a > > way to mirror tabs, I won’t implement it as I find a waste of my time. If > > you have time to implement this, I can help you start and review the > code. > > Why do you think I'm opening this as a bug, not fixing it myself? And in > any > case I wouldn't want to touch the existing code, which isn't how I would > tabs > in views. This code is beyond my abilities. > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453218] Restore split views sharing tabs globally from 18.12.3
https://bugs.kde.org/show_bug.cgi?id=453218 --- Comment #4 from twojstaryzdomu+...@gmail.com --- > You do not consider, a lot of people did and we had a pile of bugs opened > for that. It was designed that way and that works for me. To throw the old design out of the window and replace it with a worse (from a session management perspective) is not an improvement. > You can still manage two views independently and use tabs independently: > create two Konsole windows, and open tabs on them. That's no solution, two separate windows cannot be managed simultaneously without switching back and forth between them. > I doubt tue old style will get back, but we can work with compromises: a > way to mirror tabs, I won’t implement it as I find a waste of my time. If > you have time to implement this, I can help you start and review the code. Why do you think I'm opening this as a bug, not fixing it myself? And in any case I wouldn't want to touch the existing code, which isn't how I would tabs in views. This code is beyond my abilities. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 452978] URL parsing broken if URL includes port number (or address is IPv6)
https://bugs.kde.org/show_bug.cgi?id=452978 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #3 from Ahmad Samir --- I think 7 and 8 aren't that common (and it would complicate the regular expression used even more), so we can hopefully skip those ones. I've tried my hand at implementing rfc3986 (thanks for the link :)) at https://invent.kde.org/utilities/konsole/-/merge_requests/646 not 100% compliant, but close enough. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 452252] Kate crash on duplicate session
https://bugs.kde.org/show_bug.cgi?id=452252 Christoph Cullmann changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Christoph Cullmann --- Sorry, can not reproduce. Could you try the current 22.04 version? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453252] 'Append newline to file on save' moves cursor on save
https://bugs.kde.org/show_bug.cgi?id=453252 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453252] 'Append newline to file on save' moves cursor on save
https://bugs.kde.org/show_bug.cgi?id=453252 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/360 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452958] akonadi's mysql locked with an extraneous SELECT query after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=452958 --- Comment #3 from Ricardo J. Barberis --- Workaroud: right after resuming, restart akonadi. I tried that fot several days and it seems to work so far. Maybe it could be scripted? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453266] Flipping the pen no longer erases
https://bugs.kde.org/show_bug.cgi?id=453266 Alvin Wong changed: What|Removed |Added CC||al...@alvinhc.com --- Comment #1 from Alvin Wong --- Have you tried switching to an eraser brush preset after flipping to the eraser tip? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Carlo changed: What|Removed |Added CC||cirlo...@msn.com --- Comment #28 from Carlo --- (In reply to Ivan Čukić from comment #8) > The reason this is not in the UI is that I don't find the use-case of > syncing with other computers via a public cloud service a particularly > secure practice. I am very new to the subject, but I'd be interested if you could explain a little further. What is that you don't like about using public Cloud service + CryFS (or w/e), exactly? Is it about the fact that you don't trust Cloud services in general? Is it because, perhaps, this use case could corrupt the files/folder in case of an internet connection loss? Is there something else I don't see -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 418044] Muon crashes during uninstallation
https://bugs.kde.org/show_bug.cgi?id=418044 Maxim Egorushkin changed: What|Removed |Added CC||maxim.yegorush...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 418044] Muon crashes during uninstallation
https://bugs.kde.org/show_bug.cgi?id=418044 --- Comment #1 from Maxim Egorushkin --- Created attachment 148503 --> https://bugs.kde.org/attachment.cgi?id=148503=edit New crash information added by DrKonqi muon (5.8.0) using Qt 5.15.3 I experience the same crash when purging or uninstalling. -- Backtrace (Reduced): #4 0x7f0dde7c125f in QApt::Backend::package (this=this@entry=0x55ab1e47ba80, name=...) at /usr/include/apt-pkg/string_view.h:39 #5 0x7f0dde7c3f04 in QApt::Backend::search (this=0x55ab1e47ba80, searchString=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:91 #6 0x55ab1cc11f52 in PackageProxyModel::search (this=0x55ab1e2032d0, searchText=...) at ./src/PackageModel/PackageProxyModel.cpp:71 #7 0x55ab1cc16ace in PackageWidget::startSearch (this=0x55ab1e167380) at ./src/PackageModel/PackageWidget.cpp:409 #8 PackageWidget::startSearch (this=0x55ab1e167380) at ./src/PackageModel/PackageWidget.cpp:406 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453267] New: Trying to add new Filter Layer crashes program (Android)
https://bugs.kde.org/show_bug.cgi?id=453267 Bug ID: 453267 Summary: Trying to add new Filter Layer crashes program (Android) Product: krita Version: 5.0.6 Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: rh...@tutanota.com Target Milestone: --- Created attachment 148502 --> https://bugs.kde.org/attachment.cgi?id=148502=edit Krita Log STEPS TO REPRODUCE 1. Open Krita 2. Open any document or create a new one 3. Add a new filter mask to any layer/Edit the proprieties of a palettize filter layer OBSERVED RESULT Program freezes until i close it EXPECTED RESULT The filter layer setting menu opens up SOFTWARE/OS VERSIONS Device: Samsung Galaxy Tab S7+ OS: Android 12 (One UI 4.1) Qt Version: 5.12.12 I have attached the krita log, but i don't know how to get a backtrace on Android ADDITIONAL INFORMATION I've tested a document with a layer with all the filter layers added to it, and opened the proprieties of each one (where possible) to see which type of filter layer makes the program crash, and only the "Palettize" filter makes the program crash as described above. My guess is that when i try to add in a new filter layer, it tries to open the pallettize filter menu, and just crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453266] Flipping the pen no longer erases
https://bugs.kde.org/show_bug.cgi?id=453266 Joseph Nosie changed: What|Removed |Added CC||joeno...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453266] New: Flipping the pen no longer erases
https://bugs.kde.org/show_bug.cgi?id=453266 Bug ID: 453266 Summary: Flipping the pen no longer erases Product: krita Version: 5.0.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tablets (tablet issues are only very rarely bugs in Krita!) Assignee: krita-bugs-n...@kde.org Reporter: joeno...@protonmail.com Target Milestone: --- Created attachment 148501 --> https://bugs.kde.org/attachment.cgi?id=148501=edit Log of drawing a line with the pen tip, then the eraser tip SUMMARY Using a wacom CTH-460, flipping the pen no longer erases. STEPS TO REPRODUCE 1. Draw using the pen 2. Flip the pen over to erase OBSERVED RESULT The pen draws using the same settings. EXPECTED RESULT The pen erases when using the eraser end. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Silverblue 35, Linux 5.17.4-200.fc35.x86_64 (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The issue also occurs on the 5.0.0 and 5.0.6 appimage, but using the 4.4.8 appimage did not have this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450582] Some change between 5.24.0 and 5.24.1 broke windows shade/shutter feature
https://bugs.kde.org/show_bug.cgi?id=450582 Steven R. changed: What|Removed |Added CC||stevenrosensh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376859] Tag Shortcut Key Combination Conflict Dialog Always Appears
https://bugs.kde.org/show_bug.cgi?id=376859 --- Comment #22 from Staffan --- (In reply to Maik Qualmann from comment #21) > Neither F1 nor F10 is assigned to the manual in the digiKam default > settings. This is probably an automatic assignment in your desktop operating > system. > > Maik That does indeed seem to be the case. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 453265] New: No way to acknowledge user abort
https://bugs.kde.org/show_bug.cgi?id=453265 Bug ID: 453265 Summary: No way to acknowledge user abort Product: kcolorchooser Version: 22.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: witchhunter...@protonmail.com Target Milestone: --- SUMMARY Run from terminal: kcolorchooser --color '#11' --print User can press OK, Cancel, Esc or X on titlebar to exit the app. Kcolorchooser will always return exit code zero. Now, if the user changes the color and press e.g. Cancel, changed color will still be printed to output, so there is no way to know for certain whether a user has aborted the app. OBSERVED RESULT No information is provided to know for certain whether a user has aborted the app. EXPECTED RESULT There should be the way to know for certain whether a user has aborted the app. SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition, VM KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-40-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439659] Overlapping characters in titles rendered incorrectly
https://bugs.kde.org/show_bug.cgi?id=439659 phylor+kdeb...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from phylor+kdeb...@gmail.com --- Tested in 22.04.0 and can no longer reproduce. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376859] Tag Shortcut Key Combination Conflict Dialog Always Appears
https://bugs.kde.org/show_bug.cgi?id=376859 --- Comment #21 from Maik Qualmann --- Neither F1 nor F10 is assigned to the manual in the digiKam default settings. This is probably an automatic assignment in your desktop operating system. Maik -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 453239] Get segmentation fault (core dumped) when starting Kstars on Kubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453239 --- Comment #7 from Rik Mills --- Tracking bug for fixing this in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/kstars/+bug/1971091 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453029] Changing subtitle duration is erratic
https://bugs.kde.org/show_bug.cgi?id=453029 --- Comment #4 from johnnyou1...@gmail.com --- Created attachment 148500 --> https://bugs.kde.org/attachment.cgi?id=148500=edit Video demonstrating erratic behavior -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453029] Changing subtitle duration is erratic
https://bugs.kde.org/show_bug.cgi?id=453029 --- Comment #3 from johnnyou1...@gmail.com --- Created attachment 148499 --> https://bugs.kde.org/attachment.cgi?id=148499=edit Saved .srt -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453029] Changing subtitle duration is erratic
https://bugs.kde.org/show_bug.cgi?id=453029 --- Comment #2 from johnnyou1...@gmail.com --- Created attachment 148498 --> https://bugs.kde.org/attachment.cgi?id=148498=edit Saved file -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 453264] New: Could not connect to search (Could not connect to host www.googleapis.com: SSL negotiation failed.)
https://bugs.kde.org/show_bug.cgi?id=453264 Bug ID: 453264 Summary: Could not connect to search (Could not connect to host www.googleapis.com: SSL negotiation failed.) Product: tellico Version: 3.4.4 Platform: Homebrew (macOS) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: jacques.lebour...@obspm.fr Target Milestone: --- I just installe tellico through HomeBrew on a brand new Mac (OS 12.3.1), and could not use the search engine. I receive this error message: Could not connect to host www.googleapis.com: SSL negotiation failed. I have no idea what to do (sorry). STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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 watching all bug changes.
[digikam] [Bug 376859] Tag Shortcut Key Combination Conflict Dialog Always Appears
https://bugs.kde.org/show_bug.cgi?id=376859 --- Comment #20 from Staffan --- (In reply to Staffan from comment #18) > I have the same, or at least a similar, problem using digiKam 7.6. It was > also present in 7.4 and 7.5 but I didn't report it then, assuming that it > would be fixed in the next version. > > I had assigned the F1 key to 'Pick label "Rejected"' which was reported to > be in conflict with 'digiKam Handbook'. When removing the assignment, > digiKam starts up without displaying the error messages. However, the F1 key > does not seem to do anything. Under 'Help', I see that the 'Online Handbook' > (is that the same as the 'digiKam Handbook'?) is assigned to F10 and this > key (F10) does indeed bring up 'Revision 7.0' of the handbook. But the > disputed F1 key does nothing (that I can see) and I haven't been able to > determine that it is actually assigned to the handbook, i.e. I haven't found > the place where that assignment is done. > > I have a screendump named digiKam_bug_376859.png which I'll try to attach. I might add that I'm using the digiKam-7.6.0-x86-64.appimage on Linux; currently Linux Mint 20.3 (previous versions 7.5 and 7.4 on Linux Mint 20.2). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 dakkudu...@tozya.com changed: What|Removed |Added CC||dakkudu...@tozya.com --- Comment #64 from dakkudu...@tozya.com --- *** Bug 453245 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453245] Touchpad settings override mouse settings
https://bugs.kde.org/show_bug.cgi?id=453245 dakkudu...@tozya.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from dakkudu...@tozya.com --- After more testing, the issue doesn't only happen on startup. And it seems like it doesn't take the trackpad setting, like I though, but just resetted to the default cursor speed, that happen to be the same as my trackpad settings. *** This bug has been marked as a duplicate of bug 435113 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376859] Tag Shortcut Key Combination Conflict Dialog Always Appears
https://bugs.kde.org/show_bug.cgi?id=376859 Staffan changed: What|Removed |Added Attachment #140006|0 |1 is obsolete|| --- Comment #19 from Staffan --- Created attachment 148497 --> https://bugs.kde.org/attachment.cgi?id=148497=edit The bug is still present in digiKam 7.6 I had assigned the F1 key to 'Pick label "Rejected"' which was reported to be in conflict with 'digiKam Handbook'. When removing the assignment, digiKam starts up without displaying the error messages. However, the F1 key does not seem to do anything as far as I can see. Under 'Help', I see that the 'Online Handbook' (is that the same as the 'digiKam Handbook'?) is assigned to F10 and this key (F10) does indeed bring up 'Revision 7.0' of the handbook. But the disputed F1 key does nothing... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376859] Tag Shortcut Key Combination Conflict Dialog Always Appears
https://bugs.kde.org/show_bug.cgi?id=376859 Staffan changed: What|Removed |Added CC||staf...@sgsresa.se --- Comment #18 from Staffan --- I have the same, or at least a similar, problem using digiKam 7.6. It was also present in 7.4 and 7.5 but I didn't report it then, assuming that it would be fixed in the next version. I had assigned the F1 key to 'Pick label "Rejected"' which was reported to be in conflict with 'digiKam Handbook'. When removing the assignment, digiKam starts up without displaying the error messages. However, the F1 key does not seem to do anything. Under 'Help', I see that the 'Online Handbook' (is that the same as the 'digiKam Handbook'?) is assigned to F10 and this key (F10) does indeed bring up 'Revision 7.0' of the handbook. But the disputed F1 key does nothing (that I can see) and I haven't been able to determine that it is actually assigned to the handbook, i.e. I haven't found the place where that assignment is done. I have a screendump named digiKam_bug_376859.png which I'll try to attach. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453218] Restore split views sharing tabs globally from 18.12.3
https://bugs.kde.org/show_bug.cgi?id=453218 --- Comment #3 from tcanabr...@kde.org --- You do not consider, a lot of people did and we had a pile of bugs opened for that. You can still manage two views independently and use tabs independently: create two Konsole windows, and open tabs on them. I doubt tue old style will get back, but we can work with compromises: a way to mirror tabs, I won’t implement it as I find a waste of my time. If you have time to implement this, I can help you start and review the code. Best, Tomaz On Sun, 1 May 2022 at 11:10 wrote: > https://bugs.kde.org/show_bug.cgi?id=453218 > > --- Comment #2 from twojstaryzdomu+...@gmail.com --- > I do not consider it a particular bug to be unable to split horizontally > and > vertically at the same time when it is possible to retain share tabs per > all > split view. That design worked nicely. The most common use case for this > mode > would be to display X horizontal or X vertical tabs, since the tab bar in > each > split view takes up some space. I'd say horizontal would be more common > due to > the way how tabs are presented. This mode does not necessarily require > splits > beyond horizontal or vertical, whichever is picked first. > > The idea that there should be one tabbar with tabs selecting different > split > views is based on a false premise a user wants / needs a browser style > tab. The > old design has its merit in quickly being able to display the tabs that are > needed without any hassle. The new design is unwieldy in that it requires > split > views to be isolated to a particular tab, making it impossible to manage > console sessions and them sessions around with ease. > > Whoever came up with the old design got it right. Then came changes to make > konsole mimic a browser-like tab managed interface, with tabs first, views > second and broke the sensible design. > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452726] 100% cpu usage of kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=452726 --- Comment #3 from kt47uo5u...@protonmail.com --- Any ideas? Because I can't work with multi user logged in as the cpu and fan usage is really high then. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452657] [kwin_wayland] 100% cpu usage after user switching
https://bugs.kde.org/show_bug.cgi?id=452657 --- Comment #4 from kt47uo5u...@protonmail.com --- Any ideas? Because I can't work with multi user logged in as the cpu and fan usage is really high then. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443706] Crash in WindowShadowTile::~WindowShadowTile()
https://bugs.kde.org/show_bug.cgi?id=443706 Jacob Chodubski changed: What|Removed |Added CC||jchodub...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443706] Crash in WindowShadowTile::~WindowShadowTile()
https://bugs.kde.org/show_bug.cgi?id=443706 --- Comment #16 from Jacob Chodubski --- Created attachment 148495 --> https://bugs.kde.org/attachment.cgi?id=148495=edit New crash information added by DrKonqi plasmashell (5.24.4) using Qt 5.15.3 - What I was doing when the application crashed: I restarted plasmashell using script i have bound to hotkey. Script: kquitapp5 plasmashell || killall plasmashell && kstart5 plasmashell - Unusual behavior I noticed: Before the crash plasmashell was bugged after plugging in external monitor. Plasmashell restarted normally, but DrKonqi icon appeared. - Custom settings of the application: I have moved panel to left side of the screen and set it's width to 80 pixels. -- Backtrace (Reduced): #6 0x7f3c24534383 in wl_map_insert_at (data=, i=306, flags=1, map=) at ../wayland-1.20.0/src/wayland-util.c:249 #7 proxy_destroy (proxy=0x562f0a73da50) at ../wayland-1.20.0/src/wayland-client.c:503 #8 0x7f3c24535d3b in wl_proxy_destroy_caller_locks (proxy=0x562f0a73da50) at ../wayland-1.20.0/src/wayland-client.c:523 #9 wl_proxy_marshal_array_flags (proxy=proxy@entry=0x562f0a73da50, opcode=opcode@entry=0, interface=interface@entry=0x0, version=version@entry=1, flags=flags@entry=1, args=args@entry=0x7ffdd9036ae0) at ../wayland-1.20.0/src/wayland-client.c:861 #10 0x7f3c24536830 in wl_proxy_marshal_flags (proxy=0x562f0a73da50, opcode=0, interface=0x0, version=1, flags=1) at ../wayland-1.20.0/src/wayland-client.c:784 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 453228] Column "Name" is sorted alphabetically, not alphanumerically with no options to change it
https://bugs.kde.org/show_bug.cgi?id=453228 --- Comment #2 from hasez...@gmail.com --- (In reply to Patrick Silva from comment #1) > > *** This bug has been marked as a duplicate of bug 387969 *** thanks, but i am sure i have searched for this before creating the issue, but had not found a related issue -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453153] Project plugin does not list externally created files
https://bugs.kde.org/show_bug.cgi?id=453153 --- Comment #5 from Lothar --- > It does seems I am asking too much of the plugin I don't know, I don't like it in this form either. But my ideas for changes are unpopular. To your request: It would logical fit when there would be an "action" (button/menu) to import/add new files to some project. Then would the plugin know it need an update and could also trigger "stage new stuff". But, yes, just keep in mind you need to reload manually is a working compromise. Um, that reminds me, there was some other patch. When you open your new add stuff and save it, it appear then as "untracked". So, half way solved, I guess. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453263] [Wayland] Minimizing the last opened window makes Plasma hang
https://bugs.kde.org/show_bug.cgi?id=453263 --- Comment #1 from Corentin Fleury --- Created attachment 148494 --> https://bugs.kde.org/attachment.cgi?id=148494=edit video exemple of the situation -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453263] [Wayland] Minimizing the last opened window makes Plasma hang
https://bugs.kde.org/show_bug.cgi?id=453263 Corentin Fleury changed: What|Removed |Added Summary|[Wayland] Minimzing the |[Wayland] Minimizing the |last opened window makes|last opened window makes |Plasma hang |Plasma hang -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453263] New: [Wayland] Minimzing the last opened window makes Plasma hang
https://bugs.kde.org/show_bug.cgi?id=453263 Bug ID: 453263 Summary: [Wayland] Minimzing the last opened window makes Plasma hang Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: fleury.coren...@outlook.fr Target Milestone: 1.0 Created attachment 148493 --> https://bugs.kde.org/attachment.cgi?id=148493=edit log with QWayland and Plasma error SUMMARY *** As the title explains, on Wayland, when minimizing the last non minimized window, plasma hangs for a second before you can use any applet. *** STEPS TO REPRODUCE 1. Open any application 2. If it's the last one not minimized, try to minimize it OBSERVED RESULT Plasma hangs for a second EXPECTED RESULT Should not hang SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 35 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450750] Plasma Wayland Crashes when Login
https://bugs.kde.org/show_bug.cgi?id=450750 --- Comment #8 from HFarmer --- Created attachment 148492 --> https://bugs.kde.org/attachment.cgi?id=148492=edit Terminal input and crash report -- You are receiving this mail because: You are watching all bug changes.
