[plasmashell] [Bug 373010] New: Folder View does not accept touchscreen input
https://bugs.kde.org/show_bug.cgi?id=373010 Bug ID: 373010 Summary: Folder View does not accept touchscreen input Product: plasmashell Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: doublejiniti...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I am using Manjaro 16.10 with Plasma 5.8.4 and a Wacom touchscreen. The Folder View plasmoid does not accept touchscreen input, regardless of how it is configured, while other plasmoids work as expected. Steps to reproduce: 1. Add a Folder View plasmoid anywhere on the desktop or in a panel. 2. Attempt to select or open an item using a touchscreen. Actual Results: The plasmoid does not register a click or display hover feedback. Expected Results: The plasmoid responds to the touchscreen the same as it would with a mouse or touchpad. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489286] Since Plasma 6.1, the icons in systray for gtk2 applications do not work on Wayland after the first click
https://bugs.kde.org/show_bug.cgi?id=489286 Jacob changed: What|Removed |Added CC||xsoadxx...@gmail.com --- Comment #9 from Jacob --- having this problem as well with 'hexchat' arch linux with kde 6.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 Jacob changed: What|Removed |Added CC||ja...@jacobwinski.com --- Comment #11 from Jacob --- Created attachment 166841 --> https://bugs.kde.org/attachment.cgi?id=166841&action=edit notification settings w/ the notification popup in wrong position I am also having this issue ever since upgrading to 6.0.1. I upgraded from 5.27.10 right into 6.0.1 on Arch. I did not have any testing or beta packages of Plasma 6 installed. Prior to Plasma 6, notifications were always right next to the system tray, bottom right side of the screen. No matter what notification position setting I choose, I always get the center / middle-bottom notification popup position. Attached screenshot showing send-notify, notification settings and the notification popup together. Xorg 21.1.11 Plasma 6.0.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449166] Dragging items in Dolphin makes them look shaky
https://bugs.kde.org/show_bug.cgi?id=449166 Jacob changed: What|Removed |Added CC||jacobmobsla...@gmail.com --- Comment #17 from Jacob --- I have found that if i move the file over the tabs bar area (must have at least 1 tab open), not the tabs themselves and back to the file area it stops and the cursor stays as "drag and drop" instead of flickering and jittering between "dragging hand" and "drag and drop". Also I have found that dragging a file from the places panel to the file area can cause it to hand for a little bit. This happens on both of my systems; desktop and laptop, both on Wayland with mesa, laptop is a fresh arch install. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Jacob changed: What|Removed |Added CC||jacobmobsla...@gmail.com --- Comment #82 from Jacob --- I have the same problem here always the left most monitor moving to the rightmost screen and if it doesn't move sometimes the rightmost screen will flicker in and out of existence in the middle of my 2 other screens, but that may have been fixed because it was rare and I haven't seen it in a while. My panels haven't moved since the 5.24 release, just the wallpaper. I also noticed that when this happens if I right click and open "Configure desktop and wallpaper" it will sometimes open the settings for the leftmost screen and the rightmost screen simultaneously on top of each other and they will only maximize to the resolution of the rightmost screen, which is 1080x1920, the leftmost screen is 2k so this is very apparent. System: Arch KDE: 5.24.5 KDE Framworks: 5.93.0 Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452207] New: Remove space in all tracks stops working for no reason
https://bugs.kde.org/show_bug.cgi?id=452207
Bug ID: 452207
Summary: Remove space in all tracks stops working for no reason
Product: kdenlive
Version: 21.12.1
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: jtrib...@gmail.com
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. User program for a while
2. eventually the "Remove space in all tracks" feature will not work.
3.
OBSERVED RESULT
Error at bottom of page
EXPECTED RESULT
to remove space in all tracks.
would also be nice if there was a, {i} in the error message that could give
details why the action could not be performed
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.
[kdenlive] [Bug 452229] New: After project crashed after reloading my project all my clips about half way though have the sound bit flat lined
https://bugs.kde.org/show_bug.cgi?id=452229 Bug ID: 452229 Summary: After project crashed after reloading my project all my clips about half way though have the sound bit flat lined Product: kdenlive Version: 21.12.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: jtrib...@gmail.com Target Milestone: --- Created attachment 147935 --> https://bugs.kde.org/attachment.cgi?id=147935&action=edit Screeb shot showing the issue SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I was messing with Time Remap then the project completely dissappeared and a new project named untitled was shown. i loaded my previous project and found that now all my clips about half way though have the sound bit flat lined. the auto is still there as normal but it is now shown flat. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 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.
[kdenlive] [Bug 452229] After project crashed i reloadedmy project to find that all of my clips about half way through have the sound wave flat lined
https://bugs.kde.org/show_bug.cgi?id=452229 Jacob changed: What|Removed |Added Summary|After project crashed after |After project crashed i |reloading my project all my |reloadedmy project to find |clips about half way though |that all of my clips about |have the sound bit flat |half way through have the |lined |sound wave flat lined -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452229] After project crashed i reloadedmy project to find that all of my clips about half way through have the sound wave flat lined
https://bugs.kde.org/show_bug.cgi?id=452229 --- Comment #1 from Jacob --- Upon further review i checked all my saved video project files they all have this flat sound bite. these were save before the crash. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452229] After project crashed i reloaded my project to find that all of my clips about half way through have the sound wave flat lined
https://bugs.kde.org/show_bug.cgi?id=452229 Jacob changed: What|Removed |Added Summary|After project crashed i |After project crashed i |reloadedmy project to find |reloaded my project to find |that all of my clips about |that all of my clips about |half way through have the |half way through have the |sound wave flat lined |sound wave flat lined -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452229] After project crashed i reloaded my project to find that all of my clips about half way through have the sound wave flat lined
https://bugs.kde.org/show_bug.cgi?id=452229 --- Comment #2 from Jacob --- I have found a workaround for the issue. in the project Bin if reload all the video the audio thumb nail sound wave is now correct. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452971] New: rendering crahsed
https://bugs.kde.org/show_bug.cgi?id=452971 Bug ID: 452971 Summary: rendering crahsed Product: kdenlive Version: 21.12.1 Platform: Microsoft Windows OS: Android 10.x Status: REPORTED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: jtrib...@gmail.com Target Milestone: --- SUMMARY *** Rendering crahsed everytime. i reload the program and video no errors on loading project. *** Kdenlive: 21.12.1 MLT: 7.3.0 Qt: 5.15.2 (built against 5.15.2 x86_64-little_endian-llp64) Frameworks: 5.89.0 System: Windows 10 Version 2009 Kernel: winnt 10.0.19044 CPU: x86_64 Windowing System: windows Movit (GPU): disabled Track Compositing: frei0r.cairoblend Rendering of C:/Users/Jtribb76/Documents/BOAT/TwinsSail/SeaLite_Repair/SeaLiteRepair.mp4 crashed [h264 @ 11216bc0] Missing reference picture, default is 0 [h264 @ 11216bc0] decode_slice_header error [h264 @ 1121c700] Missing reference picture, default is 0 [h264 @ 1121c700] decode_slice_header error [h264 @ 1121bdc0] Missing reference picture, default is 0 [h264 @ 1121bdc0] decode_slice_header error [h264 @ 1121cb80] Missing reference picture, default is 65558 [h264 @ 0c005740] Missing reference picture, default is 2147483647 Current Frame: 2274, percentage: 3 [h264 @ 35ade980] Missing reference picture, default is 0 [h264 @ 35ade980] decode_slice_header error [h264 @ 35adb2c0] Missing reference picture, default is 0 [h264 @ 35adb2c0] decode_slice_header error [h264 @ 35ae1bc0] Missing reference picture, default is 0 [h264 @ 35ae1bc0] decode_slice_header error [h264 @ 35ae0980] Missing reference picture, default is 65562 [h264 @ 35ade980] Missing reference picture, default is 2147483647 Current Frame: 4654, percentage: 7 [swscaler @ 2b0db980] Warning: data is not aligned! This can lead to a speed loss Current Frame: 8263, percentage: 12 [h264 @ 95631840] Missing reference picture, default is 0 [h264 @ 95631840] decode_slice_header error [h264 @ 359dbc00] Missing reference picture, default is 65548 [h264 @ 8ec54e80] Missing reference picture, default is 0 [h264 @ 8ec54e80] decode_slice_header error [h264 @ 8ec520c0] Missing reference picture, default is 65554 [h264 @ 8ec54e80] Missing reference picture, default is 2147483647 Current Frame: 12433, percentage: 19 [h264 @ 359dc9c0] Missing reference picture, default is 2147483647 Current Frame: 14041, percentage: 22 [h264 @ 8ec786c0] Missing reference picture, default is 2147483647 [h264 @ 8ec786c0] Missing reference picture, default is 2147483647 [h264 @ 8ec78fc0] Missing reference picture, default is 2147483647 [h264 @ 8ec78fc0] Missing reference picture, default is 2147483647 [h264 @ 117b5ac0] Missing reference picture, default is 2147483647 Current Frame: 15022, percentage: 23 [h264 @ 1140b840] Missing reference picture, default is 2147483647 Current Frame: 15723, percentage: 24 [h264 @ 3619b540] Missing reference picture, default is 2147483647 [h264 @ 3619b540] Missing reference picture, default is 2147483647 [h264 @ 36199e80] Missing reference picture, default is 2147483647 [h264 @ 36199e80] Missing reference picture, default is 2147483647 [h264 @ 3619ac40] Missing reference picture, default is 2147483647 Current Frame: 18851, percentage: 29 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT rendering crashed EXPECTED RESULT completed video SOFTWARE/OS VERSIONS Windows: 10 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.
[kdenlive] [Bug 453074] New: Zoomed portion in video and blank after rendering
https://bugs.kde.org/show_bug.cgi?id=453074 Bug ID: 453074 Summary: Zoomed portion in video and blank after rendering Product: kdenlive Version: 21.12.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: jtrib...@gmail.com Target Milestone: --- SUMMARY *** I select a portion of video to zoom. i work through the whole project and review no missing video and zoom works. save and reopen project again no issues with zoom in video. after rendering the portion of the video where the zoom effect is at the video is blank. the audio is still there without issues. this happens every single time. *** STEPS TO REPRODUCE 1. add zoom effect to video 2. complete project 3. Render video OBSERVED RESULT No video so only a black screen is seen. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 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.
[kdenlive] [Bug 452971] rendering crahsed
https://bugs.kde.org/show_bug.cgi?id=452971 --- Comment #2 from Jacob --- my project has no cell phone photos. but i did find a solution to this problem. simply rendering the video outside of my project folder, like the decktop, solved the issues. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453074] Zoomed portion in video and blank after rendering
https://bugs.kde.org/show_bug.cgi?id=453074 --- Comment #2 from Jacob --- Thanks for reaching out, I was playing around with rendering options and found a solution with forcing interlaced scanning. turning off Parallel processes did not solve the issue. not sure what you mean with rendering with CPU though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] Enable Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=356446 Jacob changed: What|Removed |Added CC||ja...@jacobwinski.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #205 from Jacob --- Guys, I think you are making this issue more complicated than it has to be. Yes, we might not be able to fix the "architecture" — my skill level is certainly below that. But, it is actually fairly easy to fix using a simple script, as I proposed some ~2 years back. How? Once the resolution is set, and has remained for a few seconds, you record the entire Desktop layout. E.g.: 1. Record the Desktop Layout for the current monitor and resolution combination, either automatically or on-demand via clicking a "save" button 2. When the monitor and resolution combination changes, do nothing if the combination is not found in backups 3. When a previously known combination is used, restore the Desktop Layout from a backup 4. Detect changes to the Desktop layout. Every change may require deleting all backed up combinations; alternatively, user should manually save a backup by clicking a "save" button Again, you could probably create a simple .sh script for this. I already made one, but I have not used it since, so do not know if it still works. - Jacob On Tue, Oct 19, 2021 at 1:09 PM Nick Stefanov wrote: > https://bugs.kde.org/show_bug.cgi?id=360478 > > --- Comment #204 from Nick Stefanov --- > (In reply to postix from comment #200) > > (In reply to Nick Stefanov from comment #199) > > > Bharadwaj Raju, I don't know why, I replace the file with yours, it's a > > > simple task, but it's not working... > > > > Here's how I did it: > > > > ``` > > wget "https://bugsfiles.kde.org/attachment.cgi?id=142613"; -o > > "~/Downloads/FolderViewLayer.qml" > > > > sudo mv > > /usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/ > > FolderViewLayer.qml > > /usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/ > > FolderViewLayer.qml.bak > > > > sudo cp ~/Downloads/FolderViewLayer.qml > > /usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/ > > FolderViewLayer.qml > > > > plasmashell --replace > > ``` > > Thanks, I do it the same way > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> changed: What|Removed |Added CC||05e42f84-6281-4bcb-8159-d43 ||2d71ae...@anonaddy.me --- Comment #2 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- I'm also experiencing this bug, and the slow down seems very similar to the slow down in bug 428903, I don't know maybe they're connected somehow. SOFTWARE/OS VERSIONS kdeconnect 20.12.2 Operating System: openSUSE Tumbleweed 20210210 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.12-1-default OS Type: 64-bit Graphics Processor: Mesa DRI Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 --- Comment #3 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- Furthermore, if I go to the system tray > Configure System Tray > Entries > KDE Connect, and set it to disabled, the shutdown/logout time seems to be normal again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #85 from Jacob --- It seems to be fixed for me. I get scrollbars on the Desktop now, but that is much better IMO. On Sun, Sep 20, 2020 at 3:35 PM Mircea Kitsune wrote: > https://bugs.kde.org/show_bug.cgi?id=360478 > > --- Comment #84 from Mircea Kitsune > --- > I wonder if this is fixed now? With the latest version of KDE / Plasma, > after a > game temporarily changed my resolution and rearranged my widgets, the > widgets > went back to their proper positions once I set the desktop resolution back. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425852] Middle-clicking on the panel should not create a sticky note in the panel
https://bugs.kde.org/show_bug.cgi?id=425852 Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> changed: What|Removed |Added CC||05e42f84-6281-4bcb-8159-d43 ||2d71ae...@anonaddy.me --- Comment #19 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- I think this might be related to Manjaro/Arch, see the following discussion: https://archived.forum.manjaro.org/t/notifications-on-plasma-desktop-panels/148102/13 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=390830 Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> changed: What|Removed |Added CC||05e42f84-6281-4bcb-8159-d43 ||2d71ae...@anonaddy.me --- Comment #6 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- Baloo indexing is not the only thing: the names of the folders within vaults can be seen at /home/user/.local/share/dolphin/view_properties/local/home/user/..., when the vault is closed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427985] New: Folders' names and folder structure in plasma vault can be accessed when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=427985 Bug ID: 427985 Summary: Folders' names and folder structure in plasma vault can be accessed when the vault is closed Product: dolphin Version: 20.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: 05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Folders' names and folder structure in plasma vault can be accessed when the vault is closed at /home/user/.local/share/dolphin/view_properties/local/home/user/ It happens when the view properties of the folder is changed. STEPS TO REPRODUCE 1. set dolphin to remember display style for each folder 2. open a vault with folders 3. change the view properties of a folder in the vault 4. close the vault OBSERVED RESULT the name of the folder within the vault can be seen at /home/user/.local/share/dolphin/view_properties/local/home/user/... (location of the mount point of your vault) EXPECTED RESULT the name of the folder within the vault cannot be seen at /home/user/.local/share/dolphin/view_properties/local/home/user/... (location of the mount point of your vault) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Kernel Version: 5.4.67-1-MANJARO KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=390830 --- Comment #8 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- (In reply to Nate Graham from comment #7) > Hmm, that is very bad too. However that's a separate issue in Dolphin > unrelated to this particular issue in Baloo. Can you file a new bug report > for that? Thanks! Done https://bugs.kde.org/show_bug.cgi?id=427985 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 428903] New: Kwallet causes system shutdown to hang for about 8 seconds
https://bugs.kde.org/show_bug.cgi?id=428903 Bug ID: 428903 Summary: Kwallet causes system shutdown to hang for about 8 seconds Product: kwalletmanager Version: 20.08 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: 05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me Target Milestone: --- SUMMARY Kwallet causes shutdown to hang for 8-10 seconds before system shuts down under certain conditions STEPS TO REPRODUCE 1. have kwallet enabled with the default settings 2. enable 'show manager in system tray' in KDE wallet preferences 3. log out and log in to make sure that the Wallet Manager is shown in the system tray 4. shutdown/reboot your system from GUI OBSERVED RESULT shutdown hangs for about 8 seconds before it shuts down properly EXPECTED RESULT system shuts properly without a hang (like when the abovementioned setting is not enabled) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION if I perform 'shutdown -r now' in the terminal, the system shuts down as expected regardless the kwallet preferences -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 428903] Kwallet causes system shutdown to hang for about 8 seconds
https://bugs.kde.org/show_bug.cgi?id=428903 --- Comment #3 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- Removing 'Launch Manager=true' from .config/kwalletrc seems to just disable the 'show manager in system tray' setting in KDE wallet preferences, which I know that solves the issue. My problem is, if that setting is enabled (like I wrote in my bug description), the logout process still does not start instantly. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 284331] Plasma destop crash when trying to apply colour change
https://bugs.kde.org/show_bug.cgi?id=284331 jacob changed: What|Removed |Added CC||turneja...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 449505] New: discovery crashes
https://bugs.kde.org/show_bug.cgi?id=449505 Bug ID: 449505 Summary: discovery crashes Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: aleix...@kde.org Reporter: jacob.kammi...@me.com Target Milestone: --- Created attachment 146177 --> https://bugs.kde.org/attachment.cgi?id=146177&action=edit Kcrash report SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. When desktop left overnight selecting the update notifier the next morning causes a crash 2. Restart the notifier also results in a crash. 3. Trying to log out of the session results in a crash of the logout functionality. 4. Only way to resolves is opening a terminal and shutdown -4 now OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425777] Missing metadata in certain columns in details view mode
https://bugs.kde.org/show_bug.cgi?id=425777 --- Comment #2 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- (In reply to Nicolas Fella from comment #1) > Do you have Baloo enabled? I think yes, output of 'balooctl status' in terminal: Baloo File Indexer is running Indexer state: Idle Total files indexed: 6 167 Files waiting for content indexing: 0 Files failed to index: 0 Current size of index is 9,97 MiB -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425777] Missing metadata in certain columns in details view mode
https://bugs.kde.org/show_bug.cgi?id=425777 --- Comment #4 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- input: [...@... test]$ balooshow IMG_20180813_121043.jpg output: 3545967949316866 66306 825610 IMG_20180813_121043.jpg [/home/.../Pictures/test/IMG_20180813_121043.jpg] Mtime: 1552470148 2019-03-13T10:42:28 Ctime: 1598354047 2020-08-25T13:14:07 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425777] Missing metadata in certain columns in details view mode
https://bugs.kde.org/show_bug.cgi?id=425777 --- Comment #6 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- So I enabled 'Also index file content' and restarted baloo, and now the output of 'balooshow' of the image file shows all the metadata. However, my problem now is that Dolphin, in the 'Date photographed' column shows the 'Image Date Time' data from the balooshow output, and not the 'Original Date Time' data. It is problematic for me, because whenever I edit an image file, the 'Image Date Time' data changes to the date of the modification. I think it would be better if Dolphin used the 'Original Date Time' data in the 'Date photographed' column. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425777] Missing metadata in certain columns in details view mode
https://bugs.kde.org/show_bug.cgi?id=425777 --- Comment #7 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- Created attachment 131193 --> https://bugs.kde.org/attachment.cgi?id=131193&action=edit example2 -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 437571] New: Segfalut when attaching to binary (Ubuntu 20.04 docker)
https://bugs.kde.org/show_bug.cgi?id=437571
Bug ID: 437571
Summary: Segfalut when attaching to binary (Ubuntu 20.04
docker)
Product: Heaptrack
Version: 1.1.0
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: m...@milianw.de
Reporter: domaga...@gmail.com
Target Milestone: ---
I'm getting the Segfault when running heaptrack with attach mode (heaptrack -p)
on programs compiled inside docker container (ubuntu 20.04 clang-10, heaptrack
1.1.80 and 1.2.80). I've tested it on pre-compiled programs, such as nano, and
it works fine, so I'm guessing I'm doing something wrong.
Even as simple program as this will fail:
int main(int argc, char** argv)
{
while(1){
int* a = new int(10);
delete a;
}
return 0;
}
I've tried to debug the issue (see ADDITIONAL INFORMATION below) but wasn't
able to fix the issue.
STEPS TO REPRODUCE
Not sure whether it's related to my docker container or how I compile things,
but anything that I compile and try to run heaptrack on it, will fail.
OBSERVED RESULT
heaptrack output will be written to "//heaptrack.a.out.17470.gz"
injecting heaptrack into application via GDB, this might take some time...
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(heaptrack_inject) will be abandoned.
When the function is done executing, GDB will silently stop.
heaptrack stats:
allocations:0
leaked allocations: 0
temporary allocations: 0
injection finished
removing heaptrack injection via GDB, this might take some time...
ptrace: No such process.
No symbol table is loaded. Use the "file" command.
The program is not being run.
Heaptrack finished! Now run the following to investigate the data:
heaptrack --analyze "//heaptrack.a.out.17470.gz"
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Docker image: Ubuntu 20.04
Compiler: clang-10 or gcc-9.3
heaptrack 1.1.80 and 1.2.80
ADDITIONAL INFORMATION
I've tried to debug where exactly it segfaults and it seems that it fails
during call to heaptrack_inject, on this line:
libheaptrack.cpp:317
s_data = new LockedData(out, stopCallback);
and then inside:
heaptrack_inject.cpp:94
static void* hook(size_t size) noexcept
Let me know if you need any other information.
--
You are receiving this mail because:
You are watching all bug changes.
[Heaptrack] [Bug 437571] Segfalut when attaching to binary (Ubuntu 20.04 docker)
https://bugs.kde.org/show_bug.cgi?id=437571
--- Comment #2 from Jacob ---
Hello Milian, thank you for replying.
It seems to be reproducable with following docker image:
--
FROM ubuntu:latest
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install -y heaptrack gdb clang-11
--
1. docker run --cap-add=SYS_PTRACE --security-opt seccomp=unconfined
2. Create file test.cc with following content:
---
int main(int argc, char** argv)
{
while(1){
int* a = new int(10);
delete a;
}
return 0;
}
---
3. Build it 'clang++-11 test.cc -o test'
4. Start it and get its PID
5. Attach heaptrack using the PID 'heaptrack -d -p PID'
6. Heaptrack output:
heaptrack output will be written to "//heaptrack.test.1481.gz"
injecting heaptrack into application via GDB, this might take some time...
Attaching to process 1162
Reading symbols from /test...
(No debugging symbols found in /test)
Reading symbols from /lib/x86_64-linux-gnu/libstdc++.so.6...
(No debugging symbols found in /lib/x86_64-linux-gnu/libstdc++.so.6)
Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...
Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libm-2.31.so...
Reading symbols from /lib/x86_64-linux-gnu/libgcc_s.so.1...
(No debugging symbols found in /lib/x86_64-linux-gnu/libgcc_s.so.1)
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...
Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libc-2.31.so...
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in /lib64/ld-linux-x86-64.so.2)
__GI___libc_malloc (bytes=4) at malloc.c:2940
2940malloc.c: No such file or directory.
Symbols already loaded for /lib/x86_64-linux-gnu/libc.so.6
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Symbols already loaded for /usr/lib/heaptrack/libheaptrack_inject.so
Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(heaptrack_inject) will be abandoned.
When the function is done executing, GDB will silently stop.
(gdb) bt
#0 0x in ?? ()
#1 0x7f50eb626049 in
std::thread::_M_start_thread(std::unique_ptr >, void (*)()) () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#2 0x7f50eb1e66ff in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so
#3 0x7f50eb1e7ffe in heaptrack_init () from
/usr/lib/heaptrack/libheaptrack_inject.so
#4 0x7f50eb1e53f2 in heaptrack_inject () from
/usr/lib/heaptrack/libheaptrack_inject.so
#5
#6 __GI___libc_malloc (bytes=4) at malloc.c:2940
#7 0x7f50eb5f9c29 in operator new(unsigned long) () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#8 0x00401160 in main ()
(gdb)
--
You are receiving this mail because:
You are watching all bug changes.
[Heaptrack] [Bug 437571] Segfalut when attaching to binary (Ubuntu 20.04 docker)
https://bugs.kde.org/show_bug.cgi?id=437571 --- Comment #3 from Jacob --- Oh ok, it seems that for this example adding -pthread solves the issue. I will see whether it was also the case in my previous testings. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 437571] Segfalut when attaching to binary (Ubuntu 20.04 docker)
https://bugs.kde.org/show_bug.cgi?id=437571 --- Comment #4 from Jacob --- Sadly it doesn't help with my initial test. I will try to isolate the issue (my guess is that some libs that I'm linking with, could be somehow causing the issue) heaptrack output will be written to "/vt/heaptrack.memory_checker.31540.gz" injecting heaptrack into application via GDB, this might take some time... Attaching to process 31464 Reading symbols from /build/vt/tests/memory_checker... (No debugging symbols found in /build/vt/tests/memory_checker) Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2... Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libdl-2.31.so... Reading symbols from /lib/x86_64-linux-gnu/libz.so.1... (No debugging symbols found in /lib/x86_64-linux-gnu/libz.so.1) Reading symbols from /usr/local/lib/libmpicxx.so.12... (No debugging symbols found in /usr/local/lib/libmpicxx.so.12) Reading symbols from /usr/local/lib/libmpi.so.12... (No debugging symbols found in /usr/local/lib/libmpi.so.12) Reading symbols from /lib/x86_64-linux-gnu/libstdc++.so.6... (No debugging symbols found in /lib/x86_64-linux-gnu/libstdc++.so.6) Reading symbols from /lib/x86_64-linux-gnu/libm.so.6... Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libm-2.31.so... Reading symbols from /lib/x86_64-linux-gnu/libgcc_s.so.1... (No debugging symbols found in /lib/x86_64-linux-gnu/libgcc_s.so.1) Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0... --Type for more, q to quit, c to continue without paging-- Reading symbols from /usr/lib/debug/.build-id/e5/4761f7b554d0fcc1562959665d93dffbebdaf0.debug... [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Reading symbols from /lib/x86_64-linux-gnu/libc.so.6... Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libc-2.31.so... Reading symbols from /lib64/ld-linux-x86-64.so.2... (No debugging symbols found in /lib64/ld-linux-x86-64.so.2) Reading symbols from /lib/x86_64-linux-gnu/librt.so.1... Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/librt-2.31.so... 0x005fddd0 in main () Symbols already loaded for /lib/x86_64-linux-gnu/libc.so.6 Symbols already loaded for /usr/lib/heaptrack/libheaptrack_inject.so Program received signal SIGSEGV, Segmentation fault. 0x7f423d9bfe76 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so The program being debugged was signaled while in a function called from GDB. GDB remains in the frame where the signal was received. To change this behavior use "set unwindonsignal on". Evaluation of the expression containing the function (heaptrack_inject) will be abandoned. When the function is done executing, GDB will silently stop. (gdb) bt #0 0x7f423d9bfe76 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #1 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #2 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #3 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #4 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #5 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #6 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #7 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #8 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #9 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #10 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #11 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #12 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #13 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #14 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #15 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #16 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #17 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #18 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #19 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #20 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #21 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #22 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #23 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #24 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #25 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #26 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so #27 0x7f423d9bfe83 in ?? () from /usr/lib/heaptrack/libheapt
[Discover] [Bug 409195] New: Discover crashes on launch (invalid kns backend)
https://bugs.kde.org/show_bug.cgi?id=409195 Bug ID: 409195 Summary: Discover crashes on launch (invalid kns backend) Product: Discover Version: 5.16.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PackageKit Assignee: lei...@leinir.dk Reporter: dustr...@protonmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 121147 --> https://bugs.kde.org/attachment.cgi?id=121147&action=edit terminal printout SUMMARY Whenever Discover is launched it crashes. When launched from Konsole, I am hit with the error: invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation." STEPS TO REPRODUCE 1. Launch Discover 2. Wait for it to crash 3. Launch from Konsole: ~> plasma-discover OBSERVED RESULT Icon theme "gnome" not found. Icon theme "ubuntu-mono-dark" not found. Icon theme "Mint-X" not found. Icon theme "elementary" not found. Icon theme "gnome" not found. Icon theme "gnome" not found. Icon theme "ubuntu-mono-dark" not found. Icon theme "Mint-X" not found. Icon theme "elementary" not found. Icon theme "gnome" not found. file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:62: TypeError: Cannot read property 'selectedText' of null file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:70: TypeError: Cannot read property 'selectedText' of null file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:78: TypeError: Cannot read property 'canPaste' of null invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation." adding empty sources model QStandardItemModel(0x55695ba58850) Segmentation fault (core dumped) EXPECTED RESULT Discover launches SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20190623 KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION I've included a pdf printout of my Konsole -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409195] Discover crashes on launch (invalid kns backend)
https://bugs.kde.org/show_bug.cgi?id=409195 --- Comment #3 from Jacob --- Sorry for the delay. This is my first go around with KDE Plasma so I've been reading a lot of documentation. Unfortunately, I do not have drkonqi crash handler working on my system (not sure if openSUSE disables this in favor of their own crash handler) but was able to get some more detailed information within the crash logs openSUSE has provided. When attempting to run Discover from the terminal with root privilege, I get the following printout: ~>sudo plasma-discover qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. error: XDG_RUNTIME_DIR not set in the environment. Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aborted In the warn log built in to openSUSE: 2019-06-27T17:00:07.285213-07:00 linux-71jo plasmashell[2054]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:347: Unable to assign [undefined] to int 2019-06-27T17:00:07.286416-07:00 linux-71jo plasmashell[2054]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:375: TypeError: Type error 2019-06-27T17:00:07.298193-07:00 linux-71jo plasmashell[2054]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:347: Unable to assign [undefined] to int 2019-06-27T17:00:07.298433-07:00 linux-71jo plasmashell[2054]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:375: TypeError: Type error 2019-06-27T17:00:07.342155-07:00 linux-71jo plasmashell[2054]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:347: Unable to assign [undefined] to int 2019-06-27T17:00:07.342540-07:00 linux-71jo plasmashell[2054]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:375: TypeError: Type error 2019-06-27T17:00:07.360158-07:00 linux-71jo plasmashell[2054]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:347: Unable to assign [undefined] to int 2019-06-27T17:00:07.360448-07:00 linux-71jo plasmashell[2054]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:375: TypeError: Type error 2019-06-27T17:00:08.016838-07:00 linux-71jo kwin_x11[2044]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5803, resource id: 94371863, major code: 15 (QueryTree), minor code: 0 2019-06-27T17:00:08.019993-07:00 linux-71jo kwin_x11[2044]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5808, resource id: 94371863, major code: 18 (ChangeProperty), minor code: 0 Hope this helps -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409195] Discover crashes on launch (invalid kns backend)
https://bugs.kde.org/show_bug.cgi?id=409195 --- Comment #5 from Jacob --- Created attachment 121197 --> https://bugs.kde.org/attachment.cgi?id=121197&action=edit Crash report Okay so I've had some developments on my end. After changing my window manager from default to plasma5, I was able to get Discover "working". The unfortunate part is that Discover is unable to update the repos; it's essentially useless in this state. I was however able to get the crash report working. This happened after disabling some repos. Not exactly sure whats happening but I feel like the repos are messing with Discover. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 Jacob changed: What|Removed |Added CC||jacobsea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #43 from Jacob --- (In reply to funkybomber from comment #41) > Thanks for the submission @Andrii Arendariuk, this is a simple, elegant > solution. Kudos! > > I took the liberty to run a couple more tests with your code in terminal, > and realised how easy it is to actually use your code to create multiple > backup files, in order to preserve icon positions per resolution (if that's > what we want - and we should). > For example, I used this command when I was in 1920x1080: > cp -f ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/plasma1920x1080.bak > > Then I changed resolution to 800x600, and I rearranged some of the desktop > icons to new places so that I would feel more comfortable while working in > this resolution. > Then I used this command (while still in 800x600) to preserve the icon > positions for this state as well: > cp -f ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/plasma800x600.bak > > Then I changed resolution back to 1920x1080 and run the command: > konsole -e killall plasmashell && cp -f ~/plasma1920x1080.bak > ~/.config/plasma-org.kde.plasma.desktop-appletsrc && plasmashell & > > which sure enough restored all my icons in the appropriate places. > > Just for the heck of it, I also run the command: > konsole -e killall plasmashell && cp -f ~/plasma800x600.bak > ~/.config/plasma-org.kde.plasma.desktop-appletsrc && plasmashell & > > which just placed the icons in the "800x600" pattern while I was still in > the 1920x1080 resolution. But that was just me playing at this point. > > The only thing remaining is someone with programming experience to make the > script run automatically when there is a resolution change. > To function properly this script should get as parameters both the "old" and > "new" resolution and then call "backup" for the "old" resolution and > "restore" (if a relevant file for this resolution exists) for the "new" > resolution. > > Obviously I'm biased because I desperately want to see a resolution to this > issue, but let's discuss: > > What are the downsides to this solution exactly? I spent several hours trying to make the resolution change idea work only to eventually give up (at least for now). What I tested out was to simply detect a "resolution change" from within a .sh script. This can actually be done. However, the problem is that when a program or game changes the resolution (temporarily?), it does not seem to actually change the desktop resolution, even though it seems that way visually. I tested this with Diablo 2 in Wine. While the game is running, the reported resolution, when requested from a .sh script, will be unchanged. Hence, we can not easily detect this. However, we could probably parse the configuration file and do a simple search and replace whenever it is corrupted. I also tried simply comparing the md5sums of the configuration and backup files, but this does not work very well at all. It seems like other things also change the configuration file, and those changes will be overwritten every time we restore from a backup automatically. Hence, a search and replace is probably best. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #44 from Jacob --- Okay, I found another command that helped me detect resolution changes. Now I got a working script to restore the relevant section in the configuration file automatically, without overwriting the entire file. It has build in logging for debugging, and should also take a backup of your full file, before modifying it. I almost lost my file 1 time, since I was working on the script without making a backup first. Doh! I could use some help getting the literal string replacement to work in bash, I had to do it in PHP, since escaping the relevant characters proved to be very difficult. The scripts can be found here: https://github.com/jacobkri/kde-containment-guard -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer
https://bugs.kde.org/show_bug.cgi?id=353240 Jacob changed: What|Removed |Added CC||doublejiniti...@gmail.com --- Comment #8 from Jacob --- Same for me on Manjaro, 132 font DPI with KOrganizer 5.4.1 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 375467] New: Cantor hangs at "Initializing Session" when choosing Sage backend
0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0090\r\nâ\u0094\u0082
SageMath version 7.5, Release Date: 2017-01-11
â\u0094\u0082\r\nâ\u0094\u0082 Type \"notebook()\" for the browser-based
notebook interface.â\u0094\u0082\r\nâ\u0094\u0082 Type \"help()\" for
help.
â\u0094\u0082\r\nâ\u0094\u0094â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0080â\u0094\u0098\r\n\u001B]0;IPython:
home/jj\u0007\u001B[?1l\u001B[6n\u001B[?2004h\u001B[?25l\u001B[?7l\u001B[0m\r\u001B[0m\u001B[J\r\u001B[0m\u001B[?12l\u001B[?25h\u001B[?25l\r\u001B[0m\u001B[J\r\u001B[J\u001B[?7h\u001B[0m\u001B[?12l\u001B[?25h\u001B[?2004l\u001B[?1l\u001B[6n\u001B[?2004h\u001B[?25l\u001B[?7l\u001B[0m\r\u001B[0m\u001B[J\r\u001B[0m\u001B[?12l\u001B[?25h\u001B[?25l\r\u001B[0m\u001B[?12l\u001B[?25h"
found version: ("7.5", "7", "5")
using the current set of commands
QObject::disconnect: Unexpected null parameter
Shortcut for action "format_text_bold" "&Bold" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action "format_text_italic" "&Italic" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action "format_text_underline" "&Underline" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action "format_text_strikeout" "&Strike Out" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action "evaluate_current" "Evaluate Entry" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action "insert_command_entry" "Insert Command Entry" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action "remove_current" "Remove current Entry" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action "show_completion" "Show Completion" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
updating panels
adding panel for "Help"
logout
SAGE_TMP_ROOT = /home/jj/.sage/temp/jacob-Thinkpad
Starting sage-cleaner with PID 23997
Checking PIDs [23833]
Process 23833 is no longer running, so we clean up
Deleting /home/jj/.sage/temp/jacob-Thinkpad/23833
Checking PIDs []
cleanup() #2 took 0.00s
Checking PIDs []
cleanup() #3 took 0.00s
Checking PIDs []
cleanup() #4 took 0.00s
Checking PIDs []
cleanup() #5 took 0.00s
Checking PIDs []
cleanup() #6 took 0.00s
Checking PIDs []
cleanup() #7 took 0.00s
Checking PIDs []
cleanup() #8 took 0.00s
Checking PIDs []
cleanup() #9 took 0.00s
Checking PIDs []
cleanup() #10 took 0.00s
sage-cleaner is finished
Removing pidfile and logfile
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 394686] New: System settings "Display and Monitor" crashes
https://bugs.kde.org/show_bug.cgi?id=394686 Bug ID: 394686 Summary: System settings "Display and Monitor" crashes Product: systemsettings Version: 5.12.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jacob.donof...@gmail.com Target Milestone: --- Application: systemsettings5 (5.12.5) Qt Version: 5.10.0 Frameworks Version: 5.46.0 Operating System: Linux 4.13.0-43-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: Clikcing on "Display and Monitor" from the systemsetting5 application. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4e97186900 (LWP 8869))] Thread 4 (Thread 0x7f4e654ae700 (LWP 8874)): #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7f4e8f11fe42 in __GI___pthread_mutex_lock (mutex=0x7f4e8ea9f9d0) at ../nptl/pthread_mutex_lock.c:115 #2 0x7f4e8e819e4c in ?? () from /usr/lib/nvidia-384/libGL.so.1 #3 0x7f4e8e81ed81 in ?? () from /usr/lib/nvidia-384/libGL.so.1 #4 0x7f4e8e81f298 in ?? () from /usr/lib/nvidia-384/libGL.so.1 #5 0x7f4e8ae58102 in ?? () from /usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111 #6 0x7f4e8cb746f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f4e8cb30e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f4e8cb31330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f4e8cb3149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f4e935cb5db in QEventDispatcherGlib::processEvents (this=0x7f4e68e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #11 0x7f4e9357265a in QEventLoop::exec (this=this@entry=0x7f4e654adca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #12 0x7f4e93392554 in QThread::exec (this=) at thread/qthread.cpp:522 #13 0x7f4e90ecca35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7f4e933976eb in QThreadPrivate::start (arg=0x1780a80) at thread/qthread_unix.cpp:376 #15 0x7f4e8f11d6ba in start_thread (arg=0x7f4e654ae700) at pthread_create.c:333 #16 0x7f4e92ca441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f4e6e11a700 (LWP 8873)): #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7f4e8f11fe42 in __GI___pthread_mutex_lock (mutex=0x7f4e8ea9f9d0) at ../nptl/pthread_mutex_lock.c:115 #2 0x7f4e8e819e4c in ?? () from /usr/lib/nvidia-384/libGL.so.1 #3 0x7f4e8e81ed81 in ?? () from /usr/lib/nvidia-384/libGL.so.1 #4 0x7f4e8e81f298 in ?? () from /usr/lib/nvidia-384/libGL.so.1 #5 0x7f4e8ae58102 in ?? () from /usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111 #6 0x7f4e8cb746f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f4e8cb30e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f4e8cb31330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f4e8cb3149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f4e935cb5db in QEventDispatcherGlib::processEvents (this=0x7f4e680008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #11 0x7f4e9357265a in QEventLoop::exec (this=this@entry=0x7f4e6e119ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #12 0x7f4e93392554 in QThread::exec (this=) at thread/qthread.cpp:522 #13 0x7f4e90ecca35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7f4e933976eb in QThreadPrivate::start (arg=0x16727c0) at thread/qthread_unix.cpp:376 #15 0x7f4e8f11d6ba in start_thread (arg=0x7f4e6e11a700) at pthread_create.c:333 #16 0x7f4e92ca441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f4e79869700 (LWP 8871)): #0 0x7f4e8f1214ee in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7f4e8ea9f9d0) at pthread_mutex_unlock.c:55 #1 __GI___pthread_mutex_unlock (mutex=0x7f4e8ea9f9d0) at pthread_mutex_unlock.c:314 #2 0x7f4e8e819b65 in ?? () from /usr/lib/nvidia-384/libGL.so.1 #3 0x7f4e8e81f23b in ?? () from /usr/lib/nvidia-384/libGL.so.1 #4 0x7f4e8ae580f1 in ?? () from /usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111 #5 0x7f4e8cb746f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f4e8cb30e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f4e8cb31330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f4e8cb3149c in g_main_context_iteration () from /lib/x86_64-linux
[Powerdevil] [Bug 374483] New: Powerdevil KCM is too tall for my screen
https://bugs.kde.org/show_bug.cgi?id=374483 Bug ID: 374483 Summary: Powerdevil KCM is too tall for my screen Product: Powerdevil Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: doublejiniti...@gmail.com Target Milestone: --- Created attachment 103161 --> https://bugs.kde.org/attachment.cgi?id=103161&action=edit KCM opened through systemtray applet When opening the Energy Saving settings page through the Battery & Brightness system tray applet, the window is taller than my screen (900px) and is not capable of being resized. Opening Energy Saving through the full system settings interface is resizeable and has a scrollbar, and therefore doesn't have this issue. I am using Plasma 5.8.5 with the Breeze widget and kwin theme. Steps to reproduce: - Set the screen vertical resolution to 900px or less - Right click on 'Battery & Brightness' in the systemtray, and choose 'Configure power saving...' -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 497956] New: Can't change theme pernamently.
https://bugs.kde.org/show_bug.cgi?id=497956 Bug ID: 497956 Summary: Can't change theme pernamently. Classification: Plasma Product: plasma-mobile Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-mobile-bugs-n...@kde.org Reporter: kubaszek10puch...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Can't change theme pernamently. STEPS TO REPRODUCE 1. Change theme to anything but not org.kde.breeze.mobile 2. Log out 3. Log in 4. Open settings 5. Check which theme is used right now OBSERVED RESULT The theme has only been changed for the current session After restarting, Plasma-mobile uses org.kde.breeze.mobile EXPECTED RESULT Change the theme to org.kde.breeze dark.desktop in the current session, changes the theme permanently SOFTWARE/OS VERSIONS Linux/KDE Plasma: plasma-mobile(AUR) KDE Plasma Version: latest KDE Frameworks Version: Don't know how to check Qt Version: 5.15.16 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 499438] New: keyboad major 24.12.1 ubuntu linux
https://bugs.kde.org/show_bug.cgi?id=499438 Bug ID: 499438 Summary: keyboad major 24.12.1 ubuntu linux Classification: Applications Product: konsole Version: 24.12.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: ninnose...@icloud.com Target Milestone: --- EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 501413] New: Find / Replace not working with regular expression
https://bugs.kde.org/show_bug.cgi?id=501413 Bug ID: 501413 Summary: Find / Replace not working with regular expression Classification: Applications Product: kate Version: 24.12.3 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: chase63...@gmail.com Target Milestone: --- SUMMARY When entering certain regular expressions in Search / Replace, the Replace function does not work. STEPS TO REPRODUCE 1. Enter the following into a new text file: Phrase A: Words Phrase A: Words Phrase A: Words Phrase B: Words Phrase B: Words Phrase A: Words Phrase A: Words Phrase B: Words Phrase A: Words Phrase A: Words 2. Open Search window on bottom 3. Enable Regular Expressions and Expand Results 4. Enter the following in Search: `(?<=Phrase A: ).*[\r\n]+\KPhrase A: ` 5. This PCRE Regular Expression finds and selects a specified phrase at the beginning of sentences, **only if** it is preceded by a sentence that also contains the phrase. The first sentence containing the phrase is **not** selected. So in this example, it finds `Phrase A: ` in lines 2, 3, 7, and 10. 6. Enter any text for replacement, or leave blank for deletion. Click the "Replace" button. OBSERVED RESULT It cycles through the results but has no effect. Nothing is replaced. EXPECTED RESULT Highlighted found results should be replaced by whatever is entered in "Replace" field. SOFTWARE/OS VERSIONS Windows: 10 Professional 2004 ADDITIONAL INFORMATION >From what I checked so far, this behavior exists as far back as 2022 (v22.08.1) and is still present in the latest nightly builds. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 501413] Find / Replace not working with regular expression
https://bugs.kde.org/show_bug.cgi?id=501413 --- Comment #1 from Jacob --- This is my first time posting here so I noticed markdown doesn't work here, so make sure to leave the ` out, i.e., regular expression entered should be: (?<=Phrase A: ).*[\r\n]+\KPhrase A: Make sure to leave a space at the end of the line after A: -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502032] New: Keystrokes not registering in X11-based context menus within Wayland session
https://bugs.kde.org/show_bug.cgi?id=502032 Bug ID: 502032 Summary: Keystrokes not registering in X11-based context menus within Wayland session Classification: Plasma Product: kwin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jakemorgan...@outlook.com Target Milestone: --- Summary: Keystrokes not registering in X11-based context menus within Wayland session Description: When running Unreal Engine 5.5 (X11-based application) on Arch Linux under KDE Plasma Wayland session, keystrokes are not being registered in context menus within the editor (such as the blueprint graph right-click menu). I have identified the issue to be related to Wayland’s handling of legacy X11 apps. Currently, the only working solution (from within a wayland session) that I have been able to find is to enable the "Allow legacy X11 apps to read keystrokes typed in all apps" setting in KDE Plasma's "Legacy X11 App Support" options and set it to "Always". However, this workaround significantly reduces security by allowing all legacy X11 applications to potentially intercept sensitive keyboard inputs. I am not sure how many other applications this issue impacts but, depending on the application, it is likely that this issue could happen in other X11 applications since this issue seems to be related to Wayland’s handling of legacy X11 apps and not an issue with the Unreal Editor. Steps to Reproduce: Launch KDE Plasma under Wayland. Download Unreal Engine binaries and run Unreal Engine 5.5 (via XWayland). Open a blueprint graph within Unreal Engine. Right-click to open the context menu and attempt to type to filter/search. Observed Behavior: Keystrokes are ignored; no input is registered. Expected Behavior: Keystrokes should be correctly registered within the X11-based application's context menu without compromising system security. System Information: KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Operating System: Arch Linux 6.13.8-arch1-1 (64-bit) Graphics Hardware and Drivers: NVIDIA GeForce RTX 4070 Driver Version: 570.133.07 Workaround (with security concerns): Enabling the setting: "Allow legacy X11 apps to read keystrokes typed in all apps" = Always Request: A safer and more secure solution or workaround that allows keystrokes in X11 applications without compromising overall system security. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 343427] kcm_sddm : Allow keyboard layout selection
https://bugs.kde.org/show_bug.cgi?id=343427 --- Comment #9 from Florian Jacob --- This is still an issue. While the default theme of sddm now has a keyboard layout chooser since November 2015, the breeze theme, which is developed as part of plasma and not of sddm, still lacks one in plasma workspace 5.8.3. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 444832] Panel can auto show underneath yakuake, but will not auto hide
https://bugs.kde.org/show_bug.cgi?id=444832 Jacob Birkett changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||spikes...@outlook.com --- Comment #1 from Jacob Birkett --- I am having the exact same issue. Took me a while to figure out that Yakuake was the culprit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455164] New: Can't highlight icons across multiple dispays in desktop Folder Views
https://bugs.kde.org/show_bug.cgi?id=455164 Bug ID: 455164 Summary: Can't highlight icons across multiple dispays in desktop Folder Views Product: plasmashell Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: jacobryan...@gmail.com CC: h...@kde.org Target Milestone: 1.0 Flags: Usability+ SUMMARY When two displays are assigned Folder View layouts the user is unable to highlight icons across both displays. STEPS TO REPRODUCE 1. Observing this bug requires multiple displays 2. Set two or more displays to Folder View layouts 3. Try to highlight across the displays by dragging the mouse across both screens with left click pressed. OBSERVED RESULT The highlight box ends at the edge of the display where the highlight was created EXPECTED RESULT The user should be able to highlight icons across multiple displays to create a more cohesive desktop experience. Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.18.3-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 1400 Quad-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466955] New: Discover crashes on startup
https://bugs.kde.org/show_bug.cgi?id=466955
Bug ID: 466955
Summary: Discover crashes on startup
Classification: Applications
Product: Discover
Version: 5.27.2
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: discover
Assignee: plasma-b...@kde.org
Reporter: jacob.sk...@pm.me
CC: aleix...@kde.org
Target Milestone: ---
Application: plasma-discover (5.27.2)
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.2.2-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.2 [KCrashBackend]
-- Information about the crash:
My discover application is crashing on startup where it seems to get stuck in a
refresh loop for a second before the process dies
The crash can be reproduced every time.
-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 doActivate(QObject*, int, void**) (sender=0x55996fdbd950,
signal_index=3, argv=0x7ffc7bdd3860) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:132
#7 0x7ff42e7429d7 in
ResultsStream::resourcesFound(QVector const&)
(this=, _t1=...) at
/usr/src/debug/discover/build/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResourcesBackend.cpp:159
#8 0x7ff3df975523 in operator() (__closure=) at
/usr/src/debug/discover/discover-5.27.2/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:1595
#9 QtPrivate::FunctorCall, QtPrivate::List<>, void,
FlatpakBackend::search(const AbstractResourcesBackend::Filters&)::
>::call (arg=, f=) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#10 QtPrivate::Functor, 0>::call,
void> (arg=, f=) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#11 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443
#12 0x7ff42c6b1bb0 in QObject::event(QEvent*) (this=0x55996cd53f70,
e=0x7ff3b4094080) at kernel/qobject.cpp:1347
#13 0x7ff42e178b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55996cd53f70, e=0x7ff3b4094080) at
kernel/qapplication.cpp:3640
#14 0x7ff42c68df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55996cd53f70, event=0x7ff3b4094080) at
kernel/qcoreapplication.cpp:1064
#15 0x7ff42c68dfb3 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=) at
kernel/qcoreapplication.cpp:1462
#16 0x7ff42c68ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55996c6efe10) at
kernel/qcoreapplication.cpp:1821
#17 0x7ff42c6d4e88 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55996c7407b0) at kernel/qeventdispatcher_glib.cpp:277
#18 0x7ff42af1682b in g_main_dispatch (context=0x7ff420005010) at
../glib/glib/gmain.c:3454
#19 g_main_context_dispatch (context=0x7ff420005010) at
../glib/glib/gmain.c:4172
#20 0x7ff42af6dcc9 in g_main_context_iterate.constprop.0
(context=0x7ff420005010, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4248
#21 0x7ff42af150e2 in g_main_context_iteration (context=0x7ff420005010,
may_block=1) at ../glib/glib/gmain.c:4313
#22 0x7ff42c6d8c6c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55996c71eea0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#23 0x7ff42c6866ec in
QEventLoop::exec(QFlags) (this=0x7ffc7bdd3d70,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x7ff42c691219 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#25 0x7ff42cb39fe2 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1870
#26 0x7ff42e176f2a in QApplication::exec() () at
kernel/qapplication.cpp:2832
#27 0x55996c113947 in main(int, char**) (argc=,
argv=) at
/usr/src/debug/discover/discover-5.27.2/discover/main.cpp:224
[Inferior 1 (process 416528) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 467740] New: After saving, move waveform/thumbnail cache instead of regenerating
https://bugs.kde.org/show_bug.cgi?id=467740 Bug ID: 467740 Summary: After saving, move waveform/thumbnail cache instead of regenerating Classification: Applications Product: kdenlive Version: 22.12.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: ja...@nerdonthestreet.com Target Milestone: --- SUMMARY Kdenlive discards and re-generates data such as audio waveforms if the project is saved to a new location. This can often mean waiting for waveforms to generate twice when starting a new project (once before saving for the first time, and once after.) STEPS TO REPRODUCE 1. Open Kdenlive 2. Drag a video into the Project Bin 3. Drag the video to the Timeline 4. Wait for some waveforms to appear 5. Save the new project to a non-default directory (e.g. if the project has its own directory where the footage is stored, save it there) OBSERVED RESULT Kdenlive notifies the user: "The location of the project file changed. You selected to use the location of the project file to save temporary files. This will move all temporary files from /old/directory to /new/directory, the project file will then be reloaded" After this, all audio waveforms are gone and the loading bar under the clip in the Project Bin restarts from zero to generate them again. EXPECTED RESULT The already-generated waveform thumbnails should be moved (as the dialog indicates) and generating should not start over from zero. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.7-arch1-1 (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 418605] Improve handling of network-based music collection
https://bugs.kde.org/show_bug.cgi?id=418605 --- Comment #9 from Jacob Kauffmann --- (In reply to Nate Graham from comment #7) > *** Bug 457782 has been marked as a duplicate of this bug. *** Nate, please see my previous comment-- you incorrectly marked #457782 as a duplicate and you are conflating various hard bugs and UX wishlist items in combining all of these into a single thread. Can you please respond to this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467182] Cannot pan zoom area to certain locations when using KWin Zoom plugin with certain multi-monitor configurations
https://bugs.kde.org/show_bug.cgi?id=467182 jacob ham changed: What|Removed |Added CC||jacobryan...@gmail.com --- Comment #1 from jacob ham --- This phenomenon happens because of an unfortunate reaction between the zoom desktop effect and the way that multimonitor is implemented. Plasma is not the only desktop to have it; I noticed the same thing on Windows (7 and 10, though I imagine it still exists today) as well. When displays have a vertical physical offset Kwin renders black boxes corresponding to those offsets to make the whole frame a rectangle. These boxes also define the bounds for where the mouse can move the zoomed frame, because they lay beyond what would normally be usable screen space it would not normally make sense to allow the mouse or windows to move into these unseen spaces. Because the mouse can't move into the boxes and the Zoom effect scales the whole frame, trying to the displayed zoom region up to the lower monitor's top does suggest seemingly inaccessible areas. It is actually possible to access that screen portion, however: 1. Move the cursor to the uppermost offset screen region and push the zoom area to the top of the screen. 2. Move the cursor back down (without moving the zoomed region) and push the region back towards the lower display. 3. Eventually, when you cross the virtual screen boundary that corresponds to the where the displays meet horizontally in the frame you'll see a black box occupy the topmost portion of your lower display. Below the box is the top of your lower screen, and you can push the zoom frame over the area you couldn't see before. Alternatively, switching to proportional or centered mouse tracking lets you see all areas of the frame like you describe iun the expected behaviour section without doing the annoying maneuver outlined above. Writing the above made me wonder why us blind users don't have a window manager that just creates an infinite plane that we can push around the viewport of, since zoom and magnification challenges the notion of physical display boundaries. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 470685] New: Parser hangs on Template Literals/strings and Arrow functions
https://bugs.kde.org/show_bug.cgi?id=470685 Bug ID: 470685 Summary: Parser hangs on Template Literals/strings and Arrow functions Classification: Applications Product: kdevelop Version: 5.11.230401 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: QML/JavaScript Assignee: kdevelop-bugs-n...@kde.org Reporter: jelg...@gmail.com Target Milestone: --- Created attachment 159486 --> https://bugs.kde.org/attachment.cgi?id=159486&action=edit arrow function in a qml file SUMMARY *** When parsing qml files the parser throws unexpected token on arrow functions and template literals/strings then will stop updating after changes are made both of these are well supported in javascript for a long time *** STEPS TO REPRODUCE 1. Open a qml file with an arrow function or template literals (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals) 2. wait for parser to finish 3. Unexpected token `>' will appear next to arrow functions Unexpected token `' will appear next to template literals 4. Hover functions; the "where is this declared" box doesn't work for the file, neither does highlighting 5. Parser will sometimes stop working kdevelop is restarted OBSERVED RESULT arrow functions and template string will show as errors and highlighting will fail EXPECTED RESULT file parses normally, and is fully highlighted SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.3.5.zen2-1 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419745] WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client
https://bugs.kde.org/show_bug.cgi?id=419745 Jacob S. changed: What|Removed |Added CC||jakieschneide...@gmail.com --- Comment #4 from Jacob S. --- I'm experiencing similar symptoms although mine are more general. When specifying hotspot SSID, as long as the password is blank, my devices connect, but once the password is set, it seems to reject the device outright immediately. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 469045] New: Kalendar crashes after saving an all-day event
https://bugs.kde.org/show_bug.cgi?id=469045
Bug ID: 469045
Summary: Kalendar crashes after saving an all-day event
Classification: Applications
Product: kalendar
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: claudio.cam...@kde.org
Reporter: st.ja...@web.de
CC: c...@carlschwan.eu
Target Milestone: ---
Application: kalendar (23.04.0)
Qt Version: 5.15.9
Frameworks Version: 5.105.0
Operating System: Linux 6.2.12-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 5.27.4 [KCrashBackend]
-- Information about the crash:
Creating a new all-day event in Kalendar, saving it, reopening it, and saving
it again causes Kalendar to crash.
I am using a calendar from my self-hosted Nextcloud instance.
The crash can be reproduced every time.
-- Backtrace:
Application: Kalendar (kalendar), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fdf9a1a1250 in std::__atomic_base::operator--() (this=0x0,
this=) at /usr/include/c++/12.2.1/bits/atomic_base.h:393
#7 QAtomicOps::deref(std::atomic&) (_q_value=, _q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:289
#8 QBasicAtomicInteger::deref() (this=0x0, this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:119
#9 QDateTime::Data::operator=(QDateTime::Data const&) (other=...,
this=0x55b870345228) at time/qdatetime.cpp:3411
#10 QDateTime::operator=(QDateTime const&) (this=this@entry=0x55b870345228,
other=...) at time/qdatetime.cpp:3791
#11 0x55b867c4886e in
IncidenceOccurrenceModel::Occurrence::operator=(IncidenceOccurrenceModel::Occurrence
const&) (this=0x55b870345228) at
/usr/src/debug/kalendar/kalendar-23.04.0/src/models/incidenceoccurrencemodel.h:89
#12 QVector::replace(int,
IncidenceOccurrenceModel::Occurrence const&) (t=..., i=,
this=0x55b869868660) at /usr/include/qt/QtCore/qvector.h:491
#13 IncidenceOccurrenceModel::slotSourceDataChanged(QModelIndex const&,
QModelIndex const&) (this=0x55b8698685f0, upperLeft=..., bottomRight=) at
/usr/src/debug/kalendar/kalendar-23.04.0/src/models/incidenceoccurrencemodel.cpp:227
#14 0x7fdf9a2beb41 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff209f6350, r=, this=0x55b86986c6d0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#15 doActivate(QObject*, int, void**) (sender=0x55b868395500,
signal_index=3, argv=0x7fff209f6350) at kernel/qobject.cpp:3923
#16 0x7fdf9a246c41 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=, _t1=, _t2=, _t3=) at
.moc/moc_qabstractitemmodel.cpp:557
#17 0x7fdf9a26d316 in
QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=0x55b8683696a0,
source_top_left=, source_bottom_right=,
roles=...) at itemmodels/qsortfilterproxymodel.cpp:1539
#18 0x7fdf9a2becf0 in doActivate(QObject*, int, void**)
(sender=0x55b868388a60, signal_index=3, argv=0x7fff209f6640) at
kernel/qobject.cpp:3935
#19 0x7fdf9a246c41 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=, _t1=, _t2=, _t3=) at
.moc/moc_qabstractitemmodel.cpp:557
#20 0x7fdf9a26d316 in
QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=0x55b86838a7a0,
source_top_left=, source_bottom_right=,
roles=...) at itemmodels/qsortfilterproxymodel.cpp:1539
#21 0x7fdf9a2becf0 in doActivate(QObject*, int, void**)
(sender=0x55b868388f60, signal_index=3, argv=0x7fff209f6930) at
kernel/qobject.cpp:3935
#22 0x7fdf9a246c41 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=, _t1=, _t2=, _t3=) at
.moc/moc_qabstractitemmodel.cpp:557
#23 0x7fdf9a26d316 in
QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=0x55b868389920,
source_top_left=, source_bottom_right=,
roles=...) at itemmodels/qsortfilterproxymodel.cpp:1539
#24 0x7fdf9a2becf0 in doActivate(QObject*, int, void**)
(sender=0x55b8683855e0, signal_index=3, argv=0x7fff209f6c20) at
kernel/qobject.cpp:3935
#25 0x7fdf9a246c41 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=, _t1=, _t2=, _t3=) at
.moc/moc_qabstractitemmodel.cpp:557
#26 0x7fdf9c58969b in
KSelectionProxyModelPrivate::sourceDataChanged(QModelIndex const&, QModelIndex
const&) (this=0x55b8683888b0, topLeft=..., bottomRight=...) at
/usr/src/debug/kitemmodels/kitemmodels-5.105.0/src/core/kselectionproxymodel.cpp:734
#27 0x7fdf9a2beb41 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff209f6e80, r=, this=0x55b8683893b0
[akregator] [Bug 461344] Akregator Crashes when clicking a link
https://bugs.kde.org/show_bug.cgi?id=461344 Jacob Gibson changed: What|Removed |Added CC||crazygu...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 461344] Akregator Crashes when clicking a link
https://bugs.kde.org/show_bug.cgi?id=461344 --- Comment #2 from Jacob Gibson --- Created attachment 158949 --> https://bugs.kde.org/attachment.cgi?id=158949&action=edit New crash information added by DrKonqi akregator (5.23.1 (23.04.1)) using Qt 5.15.9 Akrregator crashes when clicking links or images. -- Backtrace (Reduced): #5 0x7f9ed113f656 in content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, content::mojom::CreateNewWindowParams const&, bool, bool, content::SessionStorageNamespace*) () at ../../3rdparty/chromium/content/browser/web_contents/web_contents_impl.cc:3771 #6 0x7f9ed0fa4260 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr, base::OnceCallback)>) () at ../../3rdparty/chromium/content/browser/renderer_host/render_frame_host_impl.cc:5077 #7 0x7f9ecd2445aa in content::mojom::FrameHostStubDispatch::AcceptWithResponder(content::mojom::FrameHost*, mojo::Message*, std::unique_ptr >) () at gen/content/common/frame.mojom.cc:7074 #8 0x7f9ed0f7be8d in content::mojom::FrameHostStub >::AcceptWithResponder(mojo::Message*, std::unique_ptr >) () at gen/content/common/frame.mojom.h:1025 #9 content::mojom::FrameHostStub >::AcceptWithResponder(mojo::Message*, std::unique_ptr >) () at gen/content/common/frame.mojom.h:1020 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 460636] New: Talk to techies to know- why is Outlook stuck on loading profile
https://bugs.kde.org/show_bug.cgi?id=460636 Bug ID: 460636 Summary: Talk to techies to know- why is Outlook stuck on loading profile Classification: Applications Product: apper Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: jacobhudson8...@gmail.com Target Milestone: --- Is your Outlook account got stuck and not loading? How to fix if there’s the issue with Outlook stuck on loading profile? There are many users who don’t know how to fix this if they’re using it for the first time. It’s always better to seek expert help from professionals. In such a situation, dial the helpline number to seek help. With this helpline number, it’s easy to speak to technical professionals and get your problems solved. You can also read the blogs that are available on the website to know more. https://www.digihubexpert.com/email/outlook-stuck-on-loading-profile/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478849] New: Dolphin in administrator mode sometimes hangs/freezes until OOM kills it
https://bugs.kde.org/show_bug.cgi?id=478849 Bug ID: 478849 Summary: Dolphin in administrator mode sometimes hangs/freezes until OOM kills it Classification: Applications Product: dolphin Version: 23.08.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jacobwga...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Sometimes, when browsing a directory with dolphin after using the "Open as Administrator" option to view root-owned folders, the dolphin window will freeze and become unresponsive. After a short while, the window is killed. This happened while I was browsing the /boot directory. I saw this in journalctl both times it happened: >Dec 21 11:15:48 kernel: >oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/app-dolphin-d404b4650d8948828d743209543602cd.scope,task=dolphin,pid=7430,uid=1000 >Dec 21 11:15:48 kernel: Out of memory: Killed process 7430 >(dolphin) total-vm:22055596kB, anon-rss:13076652kB, file-rss:67080kB, >shmem-rss:2016kB, UID:1000 pgtables:37908kB oom_score_adj:200 >Dec 21 11:15:48 systemd[1758]: >app-dolphin-d404b4650d8948828d743209543602cd.scope: A process of this unit has >been killed by the OOM killer. >Dec 21 11:15:49 systemd[1758]: >app-dolphin-d404b4650d8948828d743209543602cd.scope: Failed with result >'oom-kill'. >Dec 21 11:15:49 systemd[1758]: >app-dolphin-d404b4650d8948828d743209543602cd.scope: Consumed 24.493s CPU time. I had this happen twice very quickly, and then when I went to repro it a third time to gather more information I couldn't get it to happen, so it's not 100% consistent. STEPS TO REPRODUCE 1. Navigate to /boot in dolphin 2. Right-click and select "Open as Administrator" 3. Enter password 4. Browse the directory and subdirectories. Click on files. Interact with the window. OBSERVED RESULT Sometimes, the window will freeze and no longer respond to input. Eventually, it will be killed. EXPECTED RESULT Expected that the window will not freeze when browsing the directory. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.8_tkg_eevdf (64-bit) Graphics Platform: X11 Processors: 28 × Intel® Core™ i7-14700KF Memory: 15.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2 Manufacturer: Alienware Product Name: Alienware Aurora R16 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476469] Kate crashes when clicking on first "Welcome" widget after creating a new session
https://bugs.kde.org/show_bug.cgi?id=476469 Stefan Jacob changed: What|Removed |Added CC||st.ja...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476469] Kate crashes when clicking on first "Welcome" widget after creating a new session
https://bugs.kde.org/show_bug.cgi?id=476469 --- Comment #4 from Stefan Jacob --- Created attachment 165818 --> https://bugs.kde.org/attachment.cgi?id=165818&action=edit New crash information added by DrKonqi kate (23.08.4) using Qt 5.15.12 Kate crashes when a text document is open and "Welcome" is clicked in the document selection under open controls. -- Backtrace (Reduced): #4 0x749693e4a0ed in ??? () at /usr/lib/qt/plugins/ktexteditor/katefiletreeplugin.so #5 0x7496a02d0e27 in ??? () at /usr/lib/libQt5Core.so.5 #6 0x7496a11e356a in QAbstractItemView::clicked(QModelIndex const&) () at /usr/lib/libQt5Widgets.so.5 #7 0x7496a11de7d5 in QAbstractItemView::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #8 0x7496a0faf1a1 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 481690] New: Crash upon editing message
https://bugs.kde.org/show_bug.cgi?id=481690 Bug ID: 481690 Summary: Crash upon editing message Classification: Applications Product: NeoChat Version: 23.08.5 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: jchodub...@protonmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: neochat (23.08.5) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.5-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Application sometime crashes when we try to edit message. The edited message contained a quote (starting with > symbol markdown). Crash happens as soon as we click edit button. Does not matter if in group or in private chat. The crash can be reproduced sometimes. -- Backtrace: Application: NeoChat (neochat), signal: Segmentation fault [KCrash Handler] #4 0x5d7c9f22b546 in ??? () #5 0x5d7c9f2397c3 in ??? () #6 0x78a1b27747f9 in ??? () at /usr/lib/libQt5Qml.so.5 #7 0x78a1b2775f13 in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () at /usr/lib/libQt5Qml.so.5 #8 0x78a1b278ff1e in ??? () at /usr/lib/libQt5Qml.so.5 #9 0x78a1b2793d24 in ??? () at /usr/lib/libQt5Qml.so.5 #10 0x78a1b2737120 in ??? () at /usr/lib/libQt5Qml.so.5 #11 0x78a1b2777ba3 in ??? () at /usr/lib/libQt5Qml.so.5 #12 0x78a1b0ac8e27 in ??? () at /usr/lib/libQt5Core.so.5 #13 0x5d7c9f239ec3 in ??? () #14 0x78a1b2776d18 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #15 0x78a1b2777156 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #16 0x78a1b27772b7 in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt5Qml.so.5 #17 0x78a1b27501f3 in QV4::Object::virtualResolveLookupSetter(QV4::Object*, QV4::ExecutionEngine*, QV4::Lookup*, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #18 0x78a1b27900c3 in ??? () at /usr/lib/libQt5Qml.so.5 #19 0x78a1b2793d24 in ??? () at /usr/lib/libQt5Qml.so.5 #20 0x78a1b273731a in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5 #21 0x78a1b289856d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5 #22 0x78a1b284f641 in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5 #23 0x78a1b284fd2c in ??? () at /usr/lib/libQt5Qml.so.5 #24 0x78a1b287cf15 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #25 0x78a1b0ac8710 in ??? () at /usr/lib/libQt5Core.so.5 #26 0x78a1b2837405 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib/libQt5Qml.so.5 #27 0x78a1b287cff4 in ??? () at /usr/lib/libQt5Qml.so.5 #28 0x78a1b277dfb6 in ??? () at /usr/lib/libQt5Qml.so.5 #29 0x78a1b277ffe6 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib/libQt5Qml.so.5 #30 0x78a1b2790367 in ??? () at /usr/lib/libQt5Qml.so.5 #31 0x78a1b2793d24 in ??? () at /usr/lib/libQt5Qml.so.5 #32 0x78a1b273731a in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5 #33 0x78a1b289856d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5 #34 0x78a1b284f641 in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5 #35 0x78a1b284fd2c in ??? () at /usr/lib/libQt5Qml.so.5 #36 0x78a1b287cf15 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #37 0x78a1b0ac8710 in ??? () at /usr/lib/libQt5Core.so.5 #38 0x78a1b010ae27 in QQuickAction::triggered(QObject*) () at /usr/lib/libQt5QuickTemplates2.so.5 #39 0x78a1b010d850 in ??? () at /usr/lib/libQt5QuickTemplates2.so.5 #40 0x78a1b010db80 in QQuickAbstractButtonPrivate::trigger() () at /usr/lib/libQt5QuickTemplates2.so.5 #41 0x78a1b0110b5a in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () at /usr/lib/libQt5QuickTemplates2.so.5 #42 0x78a1b012bdd9 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5QuickTemplates2.so.5 #43 0x78a1b2e40411 in QQuickItem::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #44 0x78a1b17578ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #45
[Discover] [Bug 482095] New: Specific search terms causes discover to crash
https://bugs.kde.org/show_bug.cgi?id=482095 Bug ID: 482095 Summary: Specific search terms causes discover to crash Classification: Applications Product: Discover Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jacobosborne...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Specific search terms causes discover to crash. STEPS TO REPRODUCE 1. Open discover 2. Type free Into the search box 3. Press enter OBSERVED RESULT Discover crashes EXPECTED RESULT Search terms shouldn't cause discover to crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.5.0-21-generic (64-bit) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486056] New: "2 pass" checkbox greyed out, needs to be added manually in text settings
https://bugs.kde.org/show_bug.cgi?id=486056 Bug ID: 486056 Summary: "2 pass" checkbox greyed out, needs to be added manually in text settings Classification: Applications Product: kdenlive Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ja...@nerdonthestreet.com Target Milestone: --- SUMMARY The "2 pass" checkbox is never selectable for formats such as H264 and H265 where it should theoretically be available depending on the rate control setting. STEPS TO REPRODUCE 1. Create a render preset for the libx264 codec with "CBR - Constant Bitrate" or "Average Bitrate" rate control. OBSERVED RESULT 2. Observe the "2 Pass" checkbox is greyed out in the main render dialog. 3. Edit the preset again, add "passes=2" to the "Additional Parameters:" box in the "Other" tab, and observe that the checkbox becomes checked (and is no longer greyed out). EXPECTED RESULT The "2 Pass" checkbox should be selectable in cases where it's possible to use it. Checking or un-checking the box should add/remove the text parameter; it shouldn't be necessary to manually change the text parameter in order to control the checkbox. Given the number of questions I've seen about this checkbox on places like the /r/Linux and /r/Kdenlive subreddits, it might be useful to also include a tooltip broadly explaining when it is/isn't available when the checkbox is greyed out for an actual reason. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.8.7-arch1-1 / Plasma 6.0.4 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I don't think this is a very recent regression, but I don't have time to bisect right now. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478849] Dolphin in administrator mode sometimes hangs/freezes until OOM kills it
https://bugs.kde.org/show_bug.cgi?id=478849 --- Comment #4 from Jacob White --- I happened upon this bug report, which looks like it may have been the same issue (now that I know the kio-admin plugin provides the context menu option): https://bugs.kde.org/show_bug.cgi?id=474909 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487256] New: Crash on launch when opening an image with very large media files in the same directory
https://bugs.kde.org/show_bug.cgi?id=487256 Bug ID: 487256 Summary: Crash on launch when opening an image with very large media files in the same directory Classification: Applications Product: gwenview Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ja...@nerdonthestreet.com Target Milestone: --- SUMMARY If I have a folder structure like this: - Project Folder - 200GB ProRes video file - 6MB PNG file Attempting to open the PNG file results in Gwenview freezing before the file has finished the fade-in animation, then crashing. If I delete the 200GB ProRes video file (or move it to a different directory), then the PNG file opens successfully. STEPS TO REPRODUCE 1. Put a very large media file in the same directory as an image. 2. Attempt to open the image. OBSERVED RESULT Gwenview crashes on launch. EXPECTED RESULT Gwenview displays the image. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.9.1-arch1-1 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I don't think this is a recent regression. I've long had certain "broken" folders where Gwenview was unable to open images; I've never managed to determine an exact cause until now. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487256] Crash on launch when opening an image with very large media files in the same directory
https://bugs.kde.org/show_bug.cgi?id=487256 --- Comment #1 from Jacob Kauffmann --- Created attachment 169634 --> https://bugs.kde.org/attachment.cgi?id=169634&action=edit Full backtrace from crash I think this is a full backtrace from one of the crashes. Based on the behavior and the backtrace, I assume the issue has something to do with Gwenview attempting to thumbnail the massive video file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487289] New: plasmashell on Wayland crashes when more than ~100 windows are open
https://bugs.kde.org/show_bug.cgi?id=487289 Bug ID: 487289 Summary: plasmashell on Wayland crashes when more than ~100 windows are open Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: ja...@nerdonthestreet.com Target Milestone: 1.0 SUMMARY When running on Wayland, plasmashell has a maximum number of windows that it can handle-- around 100. When more than this number is opened, plasmashell crashes. It can be restarted once the number of windows goes back down, but not while the number remains the same. (See the attached video.) STEPS TO REPRODUCE 1. Start a KDE Wayland session 2. Open 100 windows, then a few more OBSERVED RESULT plasmashell crashes. EXPECTED RESULT plasmashell continues to run. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This is happening on KDE Neon and Arch Linux (both currently with 6.0.4). The specific application does not matter. I recreated this in Neon with both Firefox and Kate, and most of my windows on Arch are typically Brave. The hardware also does not matter. I recreated this in Neon on VirtualBox, and in Arch on physical hardware (AMD CPU + NVIDIA GPU). When I'm teetering on the edge of the maximum window limit, opening the Notifications applet in the bottom panel is also able to count as a "window" and cause plasmashell to crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487289] plasmashell on Wayland crashes when more than ~100 windows are open
https://bugs.kde.org/show_bug.cgi?id=487289 --- Comment #1 from Jacob Kauffmann --- The video (~1 minute) is too large to attach. Here's a link instead: https://www.dropbox.com/scl/fi/ybenhbnf563428nr165gm/kde-plasma-100-windows.webm?rlkey=9hbuk02e2v89s0cvm5dbcex60&e=1&st=rtyscexo&dl=0 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 Jacob Kauffmann changed: What|Removed |Added CC||ja...@nerdonthestreet.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487289] plasmashell on Wayland crashes when more than ~100 windows are open
https://bugs.kde.org/show_bug.cgi?id=487289 --- Comment #2 from Jacob Kauffmann --- I can't seem to get gdb to give me any significant output for either plasmashell or kwin_wayland when this occurs (just threads exiting/starting, and output that shows up normally before the issue happens). Give that plasmashell's only output when the issue occurs is "The Wayland connection broke. Did the Wayland compositor die?", and that message doesn't come from plasmashell or kwin's codebase (I think it comes from Qt?), I'm not sure where to even start when it comes to debugging this. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 422507] Grouping of multi-disk albums
https://bugs.kde.org/show_bug.cgi?id=422507 Jacob Kauffmann changed: What|Removed |Added CC||ja...@nerdonthestreet.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 446041] New: Clicking screencast tray icon should not stop recording
https://bugs.kde.org/show_bug.cgi?id=446041 Bug ID: 446041 Summary: Clicking screencast tray icon should not stop recording Product: xdg-desktop-portal-kde Version: 5.23.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: jchodub...@protonmail.com Target Milestone: --- While recording screen on wayland there is a tray icon named *Recording screen "name_of_screen"* . Clicking it stops screensharing. This is very unexpected for 2 reasons: - Most of other icons in tray upon click invoke either a window with more options or open an applet. No action is done immediately. - Only way user would know clicking it will stop screensharing is by hovering over with a mouse and seeing tooltip. The most expected behavior would be opening an applet which contains a button "Stop recording". It could also contain additional information such as: what is being recorded (window or full screen), how long since recording has started, what application is recording. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445214] OpenTimelinIO Export/Import Fails: OTIO kdenlive/mlt adapter is out of date?
https://bugs.kde.org/show_bug.cgi?id=445214 Jacob Kauffmann changed: What|Removed |Added CC||ja...@nerdonthestreet.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 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&action=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.
[kwin] [Bug 400461] Cursor doesn't change or fails to revert to pointer while using zoom effect (Firefox and Thunderbird)
https://bugs.kde.org/show_bug.cgi?id=400461 jacob ham changed: What|Removed |Added CC||jacobryan...@gmail.com Version|5.14.2 |5.24.5 --- Comment #11 from jacob ham --- I encounter this bug with all applications running under XWayland (Firefox with XWayland backend, Steam, and Discord). Some can be run with Wayland backends. Operating System: Arch Linux KDE Plasma Version: 5.24.5 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 × AMD Ryzen 5 1400 Quad-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 422507] Grouping of multi-disk albums in Playlist
https://bugs.kde.org/show_bug.cgi?id=422507 --- Comment #13 from Jacob Kauffmann --- (In reply to Nate Graham from comment #12) > This works in the Album view now, but it still needs to be done for the > Plsylist. This does not work in the Album view, testing with Elisa 22.04. I have an album split between two directories, with all tracks having the same Album and Album Artist tags, and they are still displayed in Elisa's album view as two separate albums. I've tried setting the disc number tags to 1/2, 2/2 and 1, 2. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457782] New: Music folder resets if not reachable
https://bugs.kde.org/show_bug.cgi?id=457782 Bug ID: 457782 Summary: Music folder resets if not reachable Product: Elisa Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: ja...@nerdonthestreet.com Target Milestone: --- SUMMARY I keep my music folder on a NAS that I mount manually when I boot my desktop computer. Sometimes, I forget to mount the NAS, and when I open Elisa, my music folder resets from the NAS mount directory to the default (~/Music). This indexes several thousand files that I don't want in my library, and causes me to have to re-configure my desired music folder after mounting the NAS. While automatically mounting the NAS may be one obvious workaround to this, the issue would also affect the NAS or network connection going down temporarily; if I happen to launch Elisa during one of those events, I wouldn't want my music folder reset either. STEPS TO REPRODUCE 1. Configure the music directory 2. Unmount or otherwise remove access to the music directory 3. Launch Elisa OBSERVED RESULT The music directory resets to ~/Music. EXPECTED RESULT The previously-configured music directory should remain configured. If it doesn't exist, I might expect the music collection to show up as empty, and/or an error message that one of the music folders can't be found could be displayed. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 418605] Improve handling of network-based music collection
https://bugs.kde.org/show_bug.cgi?id=418605 --- Comment #8 from Jacob Kauffmann --- I would argue this is a bug report and not a feature request if #457782 is a duplicate of this. Configuration should not be getting changed out from under me, whether the folder is reachable or not. I also don't see how this is specific to network-based locations at all. I mount via SSHFS, which is a FUSE filesystem and shouldn't need handling any differently from other FUSE filesystems. Additionally, I can replicate this with a USB external hard drive (simply configuring a folder on the drive and then launching with the drive unplugged.) One other thing, I see "importing ### tracks" every time I launch Elisa even with only the default ~/Music folder configured. So #457782 was not a duplicate of what was initially being described here, and what was initially being described here also had nothing to do with networking. Nate, would we be able to re-open and un-mark #457782 as duplicate, and rename #418605 to be more specific about re-scanning on every startup (and remove the network reference)? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 452847] Add more options when saving as webP
https://bugs.kde.org/show_bug.cgi?id=452847 Jacob Kauffmann changed: What|Removed |Added CC||ja...@nerdonthestreet.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423745] Add the ability to delete inhibitions from the applet
https://bugs.kde.org/show_bug.cgi?id=423745 Jacob Kauffmann changed: What|Removed |Added CC||ja...@nerdonthestreet.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441148] New: Always full GPU usage display in System Monitor Sensor widget
https://bugs.kde.org/show_bug.cgi?id=441148 Bug ID: 441148 Summary: Always full GPU usage display in System Monitor Sensor widget Product: plasmashell Version: 5.22.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: cmp...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 140826 --> https://bugs.kde.org/attachment.cgi?id=140826&action=edit Screenshot of the widget SUMMARY The "All GPU Usage" bar in the "System Monitor Sensor" widget always displays full usage even the number is correct. OBSERVED RESULT See attached image. EXPECTED RESULT The bar should be consistent with the usage number. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.22 (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I'm not sure whether it's related to my computer specifically. I just updated my CPU to Ryzen 5700G. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376120] Repackage fcitx-frontend-qt5
https://bugs.kde.org/show_bug.cgi?id=376120 Jacob Zhong changed: What|Removed |Added Status|RESOLVED|REOPENED CC||cmp...@gmail.com Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from Jacob Zhong --- Hi, I found this issue happens again on the latest KDE Neon. The error message is ``` Investigating (0) fcitx5-frontend-qt5:amd64 < none -> 0.0~git20200118.2e38c95-1build3 @un puN Ib > Broken fcitx5-frontend-qt5:amd64 Depends on qtbase-abi-5-12-8:amd64 < none @un H > Considering libqt5core5a:amd64 3773 as a solution to fcitx5-frontend-qt5:amd64 Done ``` I guess it's the same issue and could you help to repackage it? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441742] New: Accessibility Features in Response window are missing
https://bugs.kde.org/show_bug.cgi?id=441742 Bug ID: 441742 Summary: Accessibility Features in Response window are missing Product: kdeconnect Version: 1.10 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: jakieschneide...@gmail.com Target Milestone: --- SUMMARY When responding to a message through the KDEConnect service, the message field is missing many critical accessibility features, such as keyboard navigation. STEPS TO REPRODUCE 1. Respond to a message received from the android device through Connect 2. Use navigation keys such as `tab` or `enter` OBSERVED RESULT Keys used appear as characters. EXPECTED RESULT `tab` or `enter` key presses should in some way allow keyboard-navigation. Perhaps `shift`+`` would type that character. SOFTWARE/OS VERSIONS Windows: Windows 10 21H1 macOS: Linux/KDE Plasma: KUbuntu 21.04 - Plasma 5.12 ADDITIONAL INFORMATION General Accessibility features are missing, however the example outlined above is most impactful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440534] New: On Wayland, dragging items over windows immediately makes those windows focused
https://bugs.kde.org/show_bug.cgi?id=440534 Bug ID: 440534 Summary: On Wayland, dragging items over windows immediately makes those windows focused Product: plasmashell Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jacobwga...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Dragging items such as files, folders, etc. over windows will immediately focus those windows on Wayland. This is extremely annoying with large or fullscreen windows. Dragging items from one place to another is impossible if the destination is not next to the source and is also not next to its entry in the task manager bar. On X11, dragging over windows doesn't focus them, so this problem is avoided. This looks like the right category for this issue. My apologies if it isn't. STEPS TO REPRODUCE 1. Open a window (for example, Firefox) in fullscreen. 2. Open two Dolphin windows, and move them to the top left and top right corners of the screen, leaving a gap between them. 3. Attempt to drag a file or folder from one Dolphin window to the other. OBSERVED RESULT The moment the cursor is over the Firefox window, Firefox becomes focused, hiding the destination Dolphin window. EXPECTED RESULT The Firefox window should not become focused in this case, or should at least not become focused immediately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel Version: 5.13.6-200.fc34.x86_64 Graphics Processor: Mesa Intel UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440534] On Wayland, dragging items over windows immediately makes those windows focused
https://bugs.kde.org/show_bug.cgi?id=440534 --- Comment #2 from Jacob White --- It's truly immediate for me. I don't think the screen is rendered once before the focus switch happens. My monitor is running at 144hz, but I also tested at 60hz and experienced the same behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 438396] Rapid changes of audio streams crashes panel
https://bugs.kde.org/show_bug.cgi?id=438396 --- Comment #2 from Jacob Chodubski --- So far I've been able to get following backtrace. Is this enough or do I need to install additional debugging symbols (if yes for which files)? Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. 0x7fbf74689c10 in QObjectPrivate::maybeSignalConnected(unsigned int) const () from /usr/lib/libQt5Core.so.5 (gdb) bt #0 0x7fbf74689c10 in QObjectPrivate::maybeSignalConnected(unsigned int) const () at /usr/lib/libQt5Core.so.5 #1 0x7fbf74696f50 in () at /usr/lib/libQt5Core.so.5 #2 0x7fbf10144d03 in () at /usr/lib/qt/qml/org/kde/plasma/private/volume/libplasma-volume-declarative.so #3 0x7fbf1009dcb2 in () at /usr/lib/libpulse.so.0 #4 0x7fbf03e033bd in () at /usr/lib/pulseaudio/libpulsecommon-14.2.so #5 0x7fbf03e04bbf in () at /usr/lib/pulseaudio/libpulsecommon-14.2.so #6 0x7fbf100e265e in () at /usr/lib/libpulse-mainloop-glib.so.0 #7 0x7fbf7297502c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #8 0x7fbf729c8b59 in () at /usr/lib/libglib-2.0.so.0 #9 0x7fbf72972781 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #10 0x7fbf746b8c36 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7fbf7465e97c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #12 0x7fbf74666ee4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #13 0x5617ba0a820b in () #14 0x7fbf73feab25 in __libc_start_main () at /usr/lib/libc.so.6 #15 0x5617ba0a833e in () -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 438396] Rapid changes of audio streams crashes panel
https://bugs.kde.org/show_bug.cgi?id=438396 --- Comment #3 from Jacob Chodubski --- Here is the same with qt5-base-debug installed. For additional symbols I would need to compile plasma myself if I understand ArchWiki correctly. Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. 0x7ff77901af72 in QQmlData::isSignalConnected(QAbstractDeclarativeData*, QObject const*, int) () from /usr/lib/libQt5Qml.so.5 (gdb) bt #0 0x7ff77901af72 in QQmlData::isSignalConnected(QAbstractDeclarativeData*, QObject const*, int) () at /usr/lib/libQt5Qml.so.5 #1 0x7ff777aaeef7 in QObjectPrivate::isDeclarativeSignalConnected(unsigned int) const (signal_index=3, this=) at kernel/qobject_p.h:426 #2 doActivate(QObject*, int, void**) (sender=0x55e8696ce9d0, signal_index=3, argv=0x0) at kernel/qobject.cpp:3775 #3 0x7ff70f55cd03 in () at /usr/lib/qt/qml/org/kde/plasma/private/volume/libplasma-volume-declarative.so #4 0x7ff70f4b5cb2 in () at /usr/lib/libpulse.so.0 #5 0x7ff70f24c3bd in () at /usr/lib/pulseaudio/libpulsecommon-14.2.so #6 0x7ff70f24dbbf in () at /usr/lib/pulseaudio/libpulsecommon-14.2.so #7 0x7ff70f4fa65e in () at /usr/lib/libpulse-mainloop-glib.so.0 #8 0x7ff775d8d02c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #9 0x7ff775de0b59 in () at /usr/lib/libglib-2.0.so.0 #10 0x7ff775d8a781 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #11 0x7ff777ad0c36 in QEventDispatcherGlib::processEvents(QFlags) (this=0x55e865852b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #12 0x7ff777a7697c in QEventLoop::exec(QFlags) (this=this@entry=0x7fffbc4addc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #13 0x7ff777a7eee4 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #14 0x55e86430120b in () #15 0x7ff777402b25 in __libc_start_main () at /usr/lib/libc.so.6 #16 0x55e86430133e in () -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 438396] Rapid changes of audio streams crashes panel
https://bugs.kde.org/show_bug.cgi?id=438396 Jacob Chodubski changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429377] Wayland: zoom effect reverting to proportional mouse-tracking
https://bugs.kde.org/show_bug.cgi?id=429377 jacob ham changed: What|Removed |Added CC||jacobryan...@gmail.com --- Comment #5 from jacob ham --- (In reply to Duncan from comment #4) > A comment on another bug made me aware of the wayland/X flags, use 'em. I know this is an old bug but do you remember which bug it was that you read? Or do you know what flags you're using to fix this weird zoom behavior? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435403] New: Can't scroll while moving cursor in Chromium
https://bugs.kde.org/show_bug.cgi?id=435403 Bug ID: 435403 Summary: Can't scroll while moving cursor in Chromium Product: kwin Version: 5.21.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: ja...@nerdonthestreet.com Target Milestone: --- SUMMARY In Chromium-based browsers (including Chromium, Brave, and Vivaldi), scrolling with the scrollbar on an external mouse only works while the mouse cursor is not being moved. In other words, if I'm moving the mouse at all, I cannot scroll at the same time. If I'm already scrolling and I start to move the mouse, scrolling stops. STEPS TO REPRODUCE 1. Open Chromium and navigate to a long page 2. Start moving the mouse 3. Attempt to scroll while still moving the mouse OBSERVED RESULT As long as the mouse is moving, scrolling does not occur. EXPECTED RESULT I should be able to scroll while moving the mouse in Chromium-based apps the same as in all other apps. SOFTWARE/OS VERSIONS Linux: 5.10.27-1-lts KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION - I've confirmed the issue happens in a brand new user account. - I've confirmed the issue does not happen in a GNOME/Mutter Wayland session. - This issue has never occurred in Plasma/KWin on X11. - I'm using AMD graphics, the OpenGL 3.1 compositor, and libinput 1.17.1. - The issue occurs whether I launch the session from SDDM or GDM. - The issue does not occur with Falkon or Firefox. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435403] Can't scroll while moving cursor in Chromium
https://bugs.kde.org/show_bug.cgi?id=435403 --- Comment #2 from Jacob Kauffmann --- > So this is only happening in a Plasma Wayland session? Correct. It happens in Plasma Wayland, it does not happen in GNOME Wayland or Plasma X11. Please let me know what other info I can provide. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435980] New: libhandy viewswitcher styling is broken
https://bugs.kde.org/show_bug.cgi?id=435980 Bug ID: 435980 Summary: libhandy viewswitcher styling is broken Product: Breeze Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: ja...@nerdonthestreet.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY While the theme includes some styling meant to be applied to the libhandy viewswitcher widget, it is currently not being applied, likely because the CSS selectors changed in libhandy version 1.0. STEPS TO REPRODUCE 1. Open an application that makes use of a libhandy viewswitcher with libhandy version 1.0 or above. OBSERVED RESULT https://invent.kde.org/plasma/breeze-gtk/uploads/1ab28e96f3a359a01514c1481d7803b3/demo-before.gif EXPECTED RESULT https://invent.kde.org/plasma/breeze-gtk/uploads/78eb208be70bd48e3117fe1acbe8f4fb/demo-after.gif SOFTWARE/OS VERSIONS Linux: 5.10.28-1-lts KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This merge request uses an incorrect coding style, but demonstrates which CSS selectors can be used to successfully style the widget: https://invent.kde.org/plasma/breeze-gtk/-/merge_requests/18 -- You are receiving this mail because: You are watching all bug changes.
