[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #84 from Andy Great --- (In reply to Nate Graham from comment #70) > Can everyone testing right now please post the following information: > > 1. Does switching to the Threaded render mode and rebooting fix the problem > for you? > 2. What exact GPU do you have? > 3. What exact version of your graphics drivers (e.g. proprietary NVIDIA > driver, Nouveau, or Mesa) are you using? > 4. How many screens are you using? 1. Yes, it worked. The panel does not freeze anymore. 2. NVIDIA 1650 Ti 3. proprietary NVIDIA 535.104.05-12.1 4. 1 laptop screen, I use Lenovo Legion 5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474073] The icon-only task manager does not open the correct application on Wayland.
https://bugs.kde.org/show_bug.cgi?id=474073 --- Comment #4 from Andy Great --- (In reply to Fushan Wen from comment #3) > > *** This bug has been marked as a duplicate of bug 469016 *** Thanks for the help. It look like the same bug indeed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474073] The icon-only task manager does not open the correct application on Wayland.
https://bugs.kde.org/show_bug.cgi?id=474073 --- Comment #2 from Andy Great --- When this happened, I noticed that the second in my digital clock stop. I un-freezed it by switching between floating panel and back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474073] The icon-only task manager does not open the correct application on Wayland.
https://bugs.kde.org/show_bug.cgi?id=474073 Andy Great changed: What|Removed |Added Summary|Icon only task manager does |The icon-only task manager |not open correct|does not open the correct |application on Wayland |application on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474073] New: Icon only task manager does not open correct application on Wayland
https://bugs.kde.org/show_bug.cgi?id=474073 Bug ID: 474073 Summary: Icon only task manager does not open correct application on Wayland Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: andythe_gr...@pm.me CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 161346 --> https://bugs.kde.org/attachment.cgi?id=161346&action=edit Firefox icons show OBS (screen recording software) being chosen. 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 *** When clicking on applications pinned to the task manager icon on the panel, different applications are opened. This only happened on Wayland, not X11. STEPS TO REPRODUCE 1. Pinned a few applications on the panel 2. After using it for some time, the application on the panel opened an incorrect application. OBSERVED RESULT For example, clicking the Firefox icon would open OBS. EXPECTED RESULT The application icon opens the correct application. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230828 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics Memory: 7.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Driver Version: 535.86.05 Manufacturer: LENOVO Product Name: 82B5 System Version: Lenovo Legion 5 15ARH05 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448746] New: Maintain file selection view when resizing window
https://bugs.kde.org/show_bug.cgi?id=448746 Bug ID: 448746 Summary: Maintain file selection view when resizing window Product: dolphin Version: 21.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: andythe_gr...@pm.me CC: kfm-de...@kde.org Target Milestone: --- Created attachment 145635 --> https://bugs.kde.org/attachment.cgi?id=145635&action=edit lost visual track when resize windows When Dolphin window is resized (eg. from full screen snap to half screen), the current files that is display in "icons view mode" get move so much that the user visually lost track. When I am viewing some photos, I sometime snap dolphin to the side of the screen to open another app to drag the photo into, but I lost track of it immediately. Dolphin Version 21.12.1 Operating System: openSUSE Tumbleweed 20220115 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-2.g9737603-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics Memory: 7.1 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442811] New: Shortcut key for changing keyboard layout does not work when there are 3 layouts.
https://bugs.kde.org/show_bug.cgi?id=442811 Bug ID: 442811 Summary: Shortcut key for changing keyboard layout does not work when there are 3 layouts. Product: systemsettings Version: 5.22.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: andythe_gr...@pm.me CC: butir...@gmail.com Target Milestone: --- SUMMARY When there are 3 keyboard layout (eg. English (US), Thai, Swedish), using change layout shortcut does cycle from Swedish to English (US) STEPS TO REPRODUCE 1. Go to system settings > Input devices > Keyboard 2. Go to layouts tab 3. Add English (US), Thai, Swedish layouts. 4. Set main shortcut to Win+Space > Apply 5. Press Win+Space to change layout starting from English (US). 6. Layout will switch to English (US) > Thai > Swedish but does not go back to English (US). 7. Remove Swedish layout will cycle between English and Thai normally. OBSERVED RESULT Using shortcut will stuck at Swedish layout. EXPECTED RESULT Layout should cycle back from Swedish to English (US). SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210915 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.2-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics Memory: 7.1 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[kuickshow] [Bug 75191] Full screen mode shows black full screen
https://bugs.kde.org/show_bug.cgi?id=75191 --- Comment #15 from Andy Great --- @Jader Your issue most likely are relate to 441904. This one is old report and likely different. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441904] KWin 5.22.5 regression on NVIDIA: Black screen when putting on/taking off full screen a previously maximized window.
https://bugs.kde.org/show_bug.cgi?id=441904 Andy Great changed: What|Removed |Added CC||changoscalien...@gmail.com --- Comment #17 from Andy Great --- *** Bug 442059 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442059] compositor displays a black screen when a maximized windows goes to full screen
https://bugs.kde.org/show_bug.cgi?id=442059 --- Comment #2 from Andy Great --- *** This bug has been marked as a duplicate of bug 441904 *** -- You are receiving this mail because: You are watching all bug changes.
[kuickshow] [Bug 75191] Full screen mode shows black full screen
https://bugs.kde.org/show_bug.cgi?id=75191 Andy Great changed: What|Removed |Added CC||andythe_gr...@pm.me --- Comment #13 from Andy Great --- I can reproduce this. Fullscreened maximized window cause black screen. Work around by making window smaller and fullscreen it. Operating System: openSUSE Tumbleweed 20210915 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.2-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics Memory: 7.1 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA driver 470.63.01 -- You are receiving this mail because: You are watching all bug changes.
[kuickshow] [Bug 75191] Full screen mode shows black full screen
https://bugs.kde.org/show_bug.cgi?id=75191 Andy Great changed: What|Removed |Added CC||changoscalien...@gmail.com --- Comment #12 from Andy Great --- *** Bug 442059 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442059] compositor displays a black screen when a maximized windows goes to full screen
https://bugs.kde.org/show_bug.cgi?id=442059 Andy Great changed: What|Removed |Added Status|REPORTED|RESOLVED CC||andythe_gr...@pm.me Resolution|--- |DUPLICATE --- Comment #1 from Andy Great --- This issue reoccur once again, happen to me too. *** This bug has been marked as a duplicate of bug 75191 *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 426103] Create flatpak package
https://bugs.kde.org/show_bug.cgi?id=426103 Andy Great changed: What|Removed |Added CC||andythe_gr...@pm.me --- Comment #1 from Andy Great --- I found a github repo with kile flatpak here, not sure why they did not submit it. https://github.com/KDE/flatpak-kde-applications -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433096] Line Chart move too far ahead at the beginning and does not read value correctly
https://bugs.kde.org/show_bug.cgi?id=433096 --- Comment #3 from Andy Great --- (In reply to David Redondo from comment #2) > The legend thing was indeed a bug that was fixed. > > The fill behavior of the chart is intentional, it was the other way around > before. Alright, thanks for clarification. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433347] Dolphin may crash when repeatedly opening and closing dialog
https://bugs.kde.org/show_bug.cgi?id=433347 Andy Great changed: What|Removed |Added CC||andythe_gr...@pm.me --- Comment #1 from Andy Great --- Hi, we would need debug symbol for the backtrace to be understandable. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 433376] New: Windows preview on hover does not know correct active application window.
https://bugs.kde.org/show_bug.cgi?id=433376 Bug ID: 433376 Summary: Windows preview on hover does not know correct active application window. Product: Active Window Control Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: andythe_gr...@pm.me CC: plasma-b...@kde.org Target Milestone: --- Created attachment 136008 --> https://bugs.kde.org/attachment.cgi?id=136008&action=edit duplicate preview screenshot SUMMARY When hover over the task manager on the panel to activate windows preview. It display duplicate previews. STEPS TO REPRODUCE 1. Open Firefox with many separate windows. 2. Hover mouse over task manager to preview windows. OBSERVED RESULT It show duplicated previews. EXPECTED RESULT It should show previews for each separate windows of Firefox. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210217 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Same issue report on reddit: https://www.reddit.com/r/kde/comments/lou60a/why_is_plasma_521_showing_the_same_preview_on/ -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433096] Line Chart move too far ahead at the beginning and does not read value correctly
https://bugs.kde.org/show_bug.cgi?id=433096 --- Comment #1 from Andy Great --- Update: Another openSUSE snapshot was released and I update it. The value of sensor legend now correctly display the value. But the line still more in weird way. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432926] Cannot update Flatpak apps and addons installed to system location, rather than user location
https://bugs.kde.org/show_bug.cgi?id=432926 --- Comment #6 from Andy Great --- Created attachment 135911 --> https://bugs.kde.org/attachment.cgi?id=135911&action=edit password twice to finish update -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432926] Cannot update Flatpak apps and addons installed to system location, rather than user location
https://bugs.kde.org/show_bug.cgi?id=432926 --- Comment #5 from Andy Great --- (In reply to Aleix Pol from comment #4) > It's perfectly fine to update system apps. > > sudo should not be necessary to upgrade system-wide flatpak installations > either. Hi, from what I observed on my machine, when I click "update all" the error "Abort due to failure (Flatpak system operation Deploy not allowed for user)" will popup at the same time as password prompt. I have to click "update all" again to finish the update. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 432958] plasma-browser-integration-host crashes repeatedly when started in a Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=432958 --- Comment #6 from Andy Great --- (In reply to tjcater from comment #5) > Created attachment 135905 [details] > coredumpctl info > > Same issue for me > > Used coredumpctl --no-pager and coredumpctl gdb for a backtrace, but I > couldn't find a package related to plasma-browser-integration-debuginfo > > SOFTWARE/OS VERSIONS > Operating System: openSUSE Tumbleweed 20210217 > KDE Plasma Version: 5.21. > KDE Frameworks Version: 5.79.0 > Qt Version: 5.15.2 > Kernel Version: 5.10.16-1-default (64-bit) > Graphics Platform: Wayland > Processors: AMD Ryzen 3600 > Memory: 32GB > Graphics Processor: AMD RX 480 I think you need to enable "openSUSE-Tumbleweed-Debug" repository in YaST software repos. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 407100] Using KDE Plasma 5 shutdown start menu, computer cannot shutdown when Audacious is running, but Audacious close itself instead. Notification "Logout cancelled by 'audacious" a
https://bugs.kde.org/show_bug.cgi?id=407100 Andy Great changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME --- Comment #8 from Andy Great --- not issue anymore -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400895] Missing keys from Thai keyboard layout preview.
https://bugs.kde.org/show_bug.cgi?id=400895 Andy Great changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Andy Great --- somehow fixed in 5.21 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 432958] plasma-browser-integration-host crashes repeatedly when started in a Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=432958 --- Comment #4 from Andy Great --- (In reply to Kai Uwe Broulik from comment #3) > Can't reproduce neither with Firefox nor Chrome neither in native Wayland > nor XWayland mode I could not get gbd to capture the process. I use "gdb -pid 18045" and it say "ptrace: No such process. The program is not being run." Do you know how to make it start logging even if the process does not start or run yet? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433098] New: Segmentation fault when fiddling with compositor settings.
https://bugs.kde.org/show_bug.cgi?id=433098 Bug ID: 433098 Summary: Segmentation fault when fiddling with compositor settings. Product: systemsettings Version: 5.21.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 135777 --> https://bugs.kde.org/attachment.cgi?id=135777&action=edit crash information SUMMARY I login to full wayland session on openSUSE Tumbleweed KDE with latest update. I was changing the Latency setting, when I press apply it crash. I could not reproduce it but I got the crash information. I hope it is useful in some way. Operating System: openSUSE Tumbleweed 20210215 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 432958] plasma-browser-integration-host crashes repeatedly when started in a Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=432958 Andy Great changed: What|Removed |Added CC||andythe_gr...@pm.me --- Comment #2 from Andy Great --- (In reply to Kai Uwe Broulik from comment #1) > Can't do much without a backtrace. There was a bug in 5.21 beta on wayland > which should be fine in the final. Hi, I experience the same issue on openSUSE Tumbleweed KDE. I could not get the backtrace because KDE crash handler said the crash information cannot be generated. Do you know how to do it without KDE crash handler? Operating System: openSUSE Tumbleweed 20210215 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433096] New: Line Chart move too far ahead at the beginning and does not read value correctly
https://bugs.kde.org/show_bug.cgi?id=433096 Bug ID: 433096 Summary: Line Chart move too far ahead at the beginning and does not read value correctly Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andythe_gr...@pm.me CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 135773 --> https://bugs.kde.org/attachment.cgi?id=135773&action=edit video showing line chart of memory usage. SUMMARY Every line chart seems start from the left scrolling to the right. Is this intended feature? (see the attached video) The value of sensor legend stuck at zero until the line reach the right side of the view window. This happen to every type of sensors, CPU, memory, temp, disks, etc. (see video) STEPS TO REPRODUCE 1. Start system monitor. 2. Look at the line chart with legend with number value. OBSERVED RESULT The line chart seems to move too much to the left relative to the viewing windows. Number value stuck at 0.0 until the line chart reach right side, then it read correct value. EXPECTED RESULT I think the line chart should start from the right of the viewing windows, scrolling to the left. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210215 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432926] Cannot update Flatpak apps and addons. Flatpak system operation Deploy not allowed for user
https://bugs.kde.org/show_bug.cgi?id=432926 --- Comment #2 from Andy Great --- (In reply to Nate Graham from comment #1) > Seems like this error comes from Flatpak itself. Does it work if you > manually update using `flatpak update` in a terminal window? It will show the same error if I use "flatpak update". I have to use "sudo flatpak update" to work. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432926] New: Cannot update Flatpak apps and addons. Flatpak system operation Deploy not allowed for user
https://bugs.kde.org/show_bug.cgi?id=432926 Bug ID: 432926 Summary: Cannot update Flatpak apps and addons. Flatpak system operation Deploy not allowed for user Product: Discover Version: 5.20.5 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: andythe_gr...@pm.me CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- Created attachment 135679 --> https://bugs.kde.org/attachment.cgi?id=135679&action=edit screenshot of error SUMMARY I install a lot of flatpak apps, but when I attempts to update it from Discover, it show an error message. Flatpak system operation Deploy not allowed for user STEPS TO REPRODUCE 1. Install some flatpaks apps. 2. Wait for updates and press update all from Discover. 3. Discover will ask for password, but the error will occur before I could type in password. 4. Abort due to failure (Flatpak system operation Deploy not allowed for user) EXPECTED RESULT I think Discover attempts to update Flatpak apps before getting the password, so it got reject. Should wait for password first. 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 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 432703] New: Make CPU label use empty space more efficient
https://bugs.kde.org/show_bug.cgi?id=432703 Bug ID: 432703 Summary: Make CPU label use empty space more efficient Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andythe_gr...@pm.me CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 135539 --> https://bugs.kde.org/attachment.cgi?id=135539&action=edit screenshot showing CPU label 8 x 1 stacking I install system-monitor 5.20.90 on openSUSE Tumbleweed KDE. The CPU percentage label at the bottom does not arrange it self that maximize CPU graph space. For example, as shown in the attached image, when the windows size is too narrow, the label becomes 8 x 1 stacking and when it have enough space it become 1 x 8 stacking. There should be in between to maximize the graph size. Operating System: openSUSE Tumbleweed 20210203 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 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428843] Operating system version is empty for openSUSE Tumbleweed
https://bugs.kde.org/show_bug.cgi?id=428843 Andy Great changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #9 from Andy Great --- I was told that VERSION is commented out because openSUSE Tumbleweed does not have a version. The only thing that was not commented out is VERSION_ID. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421644] Thai font shift upward in application menu
https://bugs.kde.org/show_bug.cgi?id=421644 Andy Great changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Andy Great --- This is likely the fault of the theme, closing. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426827] Latte-dock crash with Segmentation fault (core dumped)
https://bugs.kde.org/show_bug.cgi?id=426827 --- Comment #5 from Andy Great --- (In reply to Samson from comment #1) > I got the similar problem in kubuntu groovy beta. Latte is okay in kubuntu > focal running kernel 5.8.14 > When start up in konsole, it crashed and gave the following message > > KCrash: Attempting to start /usr/bin/latte-dock > KCrash: crashing... crashRecursionCounter = 2 > KCrash: Application Name = latte-dock path = /usr/bin pid = 49048 > KCrash: Arguments: /usr/bin/latte-dock > KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi > > Using ddd and backtrace give the following text. > > Thread 1 "latte-dock" received signal SIGSEGV, Segmentation fault. > 0x555e1fde in ?? () > > > #6 0x55588a9e in _start () > #5 0x755a0cb2 in __libc_start_main (main=0x555870c0, argc=1, > argv=0x7fffdcd8, init=, fini=, > rtld_fini=, stack_end=0x7fffdcc8) at > ../csu/libc-start.c:314 > #4 0x55588363 in ?? () > #3 0x555a18b3 in ?? () > #2 0x555e5c15 in ?? () > #1 0x555e5752 in ?? () > #0 0x555e1fde in ?? () > > I am not a technical guy and have no idea on this bug >From my latest test, it was likely due to "Event Calendar" widgets, try remove it if you have one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421316] Set up wallpapper
https://bugs.kde.org/show_bug.cgi?id=421316 Andy Great changed: What|Removed |Added CC||keithhacks-kde...@yahoo.com --- Comment #3 from Andy Great --- *** Bug 428082 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428082] Plasma reverted my wallpaper to the default, then crashed when I applied desktop settings
https://bugs.kde.org/show_bug.cgi?id=428082 Andy Great changed: What|Removed |Added Resolution|--- |DUPLICATE CC||andythe_gr...@pm.me Status|REPORTED|RESOLVED --- Comment #1 from Andy Great --- Could this be duplicate of 421316? *** This bug has been marked as a duplicate of bug 421316 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428843] Operating system version is empty for openSUSE Tumbleweed
https://bugs.kde.org/show_bug.cgi?id=428843 --- Comment #4 from Andy Great --- I would suggest using VERSION_ID for OS version. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428843] Operating system version is empty for openSUSE Tumbleweed
https://bugs.kde.org/show_bug.cgi?id=428843 --- Comment #3 from Andy Great --- (In reply to Justin Zobel from comment #1) > What are the contents of /etc/os-release and /etc/lsb-release I imagine > it's from one of those. /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20201105" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20201105" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20201105" BUG_REPORT_URL="https://bugs.opensuse.org"; HOME_URL="https://www.opensuse.org/"; DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"; LOGO="distributor-logo" /etc/lsb-release does not exist -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428843] New: Operating system version is empty for openSUSE Tumbleweed
https://bugs.kde.org/show_bug.cgi?id=428843 Bug ID: 428843 Summary: Operating system version is empty for openSUSE Tumbleweed Product: plasma-systemmonitor Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andythe_gr...@pm.me CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 133150 --> https://bugs.kde.org/attachment.cgi?id=133150&action=edit Operating system version is empty I install system monitor from here: https://build.opensuse.org/package/show/KDE:Frameworks5/plasma5-systemmonitor The operating system name and version only show openSUSE Tumbleweed. The operating system version is empty. (see screenshot) It should show openSUSE TW version, something like 20201105. System monitor 1.0 Operating System: openSUSE Tumbleweed 20201105 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.1-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428823] CPU usage y-axis go above 100%
https://bugs.kde.org/show_bug.cgi?id=428823 --- Comment #8 from Andy Great --- (In reply to Arjen Hiemstra from comment #7) > The 800% value is because the chart is stacked so each individual core is > added up. Since each core ranges from 0 to 100% and you have 8 cores you end > up with 800%. We solved this for the process/applications table by having a > way to display values normalized to 100%, we might want to do something > similar here but that's a bit more tricky. > > As to why it is showing only 0%, that one is a bit more odd as the sensors > use the same data source. Does the "CPU" chart on the overview page work > correctly? I get the 800% CPU usage now. I will have to wait until CPU usage is 0% again because I reboot my PC and its fixed, it happen randomly for some reason. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428799] Network name label appear and disappear as line graph progress
https://bugs.kde.org/show_bug.cgi?id=428799 --- Comment #3 from Andy Great --- Created attachment 133143 --> https://bugs.kde.org/attachment.cgi?id=133143&action=edit CPU become CP... -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428799] Network name label appear and disappear as line graph progress
https://bugs.kde.org/show_bug.cgi?id=428799 --- Comment #2 from Andy Great --- This affects CPU as well. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428823] CPU usage y-axis go above 100%
https://bugs.kde.org/show_bug.cgi?id=428823 --- Comment #6 from Andy Great --- (In reply to Justin Zobel from comment #4) > Was this reported twice, here and 428822? Yes, I don't know why it was posted twice. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428823] CPU usage y-axis go above 100%
https://bugs.kde.org/show_bug.cgi?id=428823 --- Comment #3 from Andy Great --- Created attachment 133132 --> https://bugs.kde.org/attachment.cgi?id=133132&action=edit ksysguard show proper CPU usage while system monitor does not. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428823] CPU usage y-axis go above 100%
https://bugs.kde.org/show_bug.cgi?id=428823 --- Comment #2 from Andy Great --- Update: It seems that 800% CPU on y-axis is not an issue, the issue is that the CPU usage is shown as 0%. Try using ksysguard which show CPU usage properly. I upload a new screenshot showing system monitor on the left and ksysguard on the right. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428823] CPU usage y-axis go above 100%
https://bugs.kde.org/show_bug.cgi?id=428823 --- Comment #1 from Andy Great --- Created attachment 133131 --> https://bugs.kde.org/attachment.cgi?id=133131&action=edit CPU usage y-axis go above 100% -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428823] New: CPU usage y-axis go above 100%
https://bugs.kde.org/show_bug.cgi?id=428823 Bug ID: 428823 Summary: CPU usage y-axis go above 100% Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andythe_gr...@pm.me CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- CPU usage y-axis go above 100% STEPS TO REPRODUCE I am not even sure how it get like this, it appears to happen randomly. OBSERVED RESULT CPU usage y-axis go above 100% and went to 800%. This make the CPU usage look flat because it is so small. EXPECTED RESULT The CPU usage should not go above 100% I install system monitor from here: https://build.opensuse.org/package/show/KDE:Frameworks5/plasma5-systemmonitor System monitor 1.0 Operating System: openSUSE Tumbleweed 20201105 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.1-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428822] New: CPU usage y-axis go above 100%
https://bugs.kde.org/show_bug.cgi?id=428822 Bug ID: 428822 Summary: CPU usage y-axis go above 100% Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andythe_gr...@pm.me CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 133130 --> https://bugs.kde.org/attachment.cgi?id=133130&action=edit CPU usage y-axis go above 100% CPU usage y-axis go above 100% STEPS TO REPRODUCE I am not even sure how it get like this, it appears to happen randomly. OBSERVED RESULT CPU usage y-axis go above 100% and went to 800%. This make the CPU usage look flat because it is so small. EXPECTED RESULT The CPU usage should not go above 100% I install system monitor from here: https://build.opensuse.org/package/show/KDE:Frameworks5/plasma5-systemmonitor System monitor 1.0 Operating System: openSUSE Tumbleweed 20201105 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.1-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428799] New: Network name label appear and disappear as line graph progress
https://bugs.kde.org/show_bug.cgi?id=428799 Bug ID: 428799 Summary: Network name label appear and disappear as line graph progress Product: plasma-systemmonitor Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andythe_gr...@pm.me CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 133115 --> https://bugs.kde.org/attachment.cgi?id=133115&action=edit Video showing label appear and disappear. The label for the Network upload and download rate with line graph continues to appear and disappear. (see video) The network name should display all the time. System monitor 1.0 Operating System: openSUSE Tumbleweed 20201105 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.1-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428791] Disk usage does not show (shown as 0)
https://bugs.kde.org/show_bug.cgi?id=428791 --- Comment #5 from Andy Great --- Nevermind, I think it is just the wrong sensor being use. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428791] Disk usage does not show (shown as 0)
https://bugs.kde.org/show_bug.cgi?id=428791 Andy Great changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Andy Great --- Nevermind, I think it is just the wrong sensor being use. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428791] Disk usage does not show (shown as 0)
https://bugs.kde.org/show_bug.cgi?id=428791 --- Comment #2 from Andy Great --- Created attachment 133109 --> https://bugs.kde.org/attachment.cgi?id=133109&action=edit Does not show disk usage. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428791] Disk usage does not show (shown as 0)
https://bugs.kde.org/show_bug.cgi?id=428791 --- Comment #3 from Andy Great --- Created attachment 133110 --> https://bugs.kde.org/attachment.cgi?id=133110&action=edit Does not show disk usage. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428791] New: Disk usage does not show (shown as 0)
https://bugs.kde.org/show_bug.cgi?id=428791 Bug ID: 428791 Summary: Disk usage does not show (shown as 0) Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andythe_gr...@pm.me CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- I use system monitor 5.20 from openSUSE KDE:Frameworks5 repo. https://build.opensuse.org/package/show/KDE:Frameworks5/plasma5-systemmonitor The disk usage is not shown. I use Btrfs if that possibly cause the issue. Operating System: openSUSE Tumbleweed 20201105 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.1-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428791] Disk usage does not show (shown as 0)
https://bugs.kde.org/show_bug.cgi?id=428791 --- Comment #1 from Andy Great --- Created attachment 133108 --> https://bugs.kde.org/attachment.cgi?id=133108&action=edit Does not show disk usage. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426827] New: Latte-dock crash with Segmentation fault (core dumped)
https://bugs.kde.org/show_bug.cgi?id=426827 Bug ID: 426827 Summary: Latte-dock crash with Segmentation fault (core dumped) Product: lattedock Version: git (master) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: andythe_gr...@pm.me Target Milestone: --- I installed master version (2 days ago) of latte-dock by making my own openSUSE repo. https://build.opensuse.org/package/show/home:andythe_great:branches:KDE:Extra/latte-dock-git However, sometime it just crash with no warning. I ran latte-dock with this command. env QV4_FORCE_INTERPRETER=1 latte-dock -d Which when it crash, it show this. ... [Debug : 2:06:23.762762] - "syncGeometry() calculations for edge: Plasma::Types::BottomEdge" [Debug : 2:06:23.762762] - "syncGeometry() ended..." [Warning : 2:06:24.216216] - "KAStatsFavoritesModel::setFavorites is ignored" [Warning : 2:06:24.258258] - "trying to show an empty dialog" [Debug : 2:06:24.265265] - "DOCK VIEW FROM LAYOUT ::: \"Plasma\" - activities: (\"{0}\")" [Debug : 2:06:24.274274] - "immediateSyncGeometry() called..." [Debug : 2:06:24.274274] - "syncGeometry() calculations for screen: \"VGA-1\" _ QRect(0,0 1920x1080)" [Debug : 2:06:24.274274] - "syncGeometry() calculations for edge: Plasma::Types::TopEdge" [Debug : 2:06:24.274274] - "syncGeometry() ended..." [Debug : 2:06:24.384384] - " PLASMA STRUTS MANAGER :: is available..." [Warning : 2:06:24.458458] - "No object for name \"alsa_output.pci-_00_1b.0.analog-stereo.monitor\"" [Debug : 2:06:25.351351] - " PLASMA SCREEN GEOMETRIES, LAST AVAILABLE SCREEN RECTS :: QHash()" [Debug : 2:06:25.351351] - " PLASMA SCREEN GEOMETRIES, SCREEN :: 10 - \"VGA-1\"" [Debug : 2:06:25.354354] - " PLASMA SCREEN GEOMETRIES, AVAILABLE RECT :: \"VGA-1\" : QRect(0,37 1920x1043)" [Debug : 2:06:25.355355] - " PLASMA SCREEN GEOMETRIES, AVAILABLE REGION :: \"VGA-1\" : QRegion(0,37 1920x1043)" [Debug : 2:06:26.654654] - "Loading visibility mode: Latte::Types::DodgeActive on startup..." [Debug : 2:06:27.654654] - " PLASMA SCREEN GEOMETRIES, LAST AVAILABLE SCREEN RECTS :: QHash((\"VGA-1\", QRect(0,37 1920x1043)))" [Debug : 2:06:27.654654] - " PLASMA SCREEN GEOMETRIES, SCREEN :: 10 - \"VGA-1\"" [Debug : 2:06:27.657657] - " PLASMA SCREEN GEOMETRIES, AVAILABLE RECT :: \"VGA-1\" : QRect(0,37 1920x1018)" [Debug : 2:06:27.658658] - " PLASMA SCREEN GEOMETRIES, AVAILABLE REGION :: \"VGA-1\" : QRegion(size=2, bounds=(0,37 1920x1043) - [(0,37 1920x1017), (0,1079 1920x1)])" Segmentation fault (core dumped) Which does not show any useful error. I could not use ddd since it has been removed from openSUSE Tumbleweed. Any suggestion to get more backtrace? Thank you. Operating System: openSUSE Tumbleweed 20200917 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.1 Kernel Version: 5.8.7-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421644] Thai font shift upward in application menu
https://bugs.kde.org/show_bug.cgi?id=421644 Andy Great changed: What|Removed |Added Component|Application Menu (Kicker) |Application Launcher ||(Kickoff) Assignee|h...@kde.org|k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421644] Thai font shift upward in application menu
https://bugs.kde.org/show_bug.cgi?id=421644 Andy Great changed: What|Removed |Added Version|5.18.5 |5.19.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421644] Thai font shift upward in application menu
https://bugs.kde.org/show_bug.cgi?id=421644 --- Comment #2 from Andy Great --- I have add screenshot of more language texts which include Thai, Japanese, Chinese, Lao, Khmer, and Burmese. Only Thai seemingly effects by this visual bug. The latest KDE Plasma on openSUSE Tumbleweed is used. Operating System: openSUSE Tumbleweed 20200917 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.1 Kernel Version: 5.8.7-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421644] Thai font shift upward in application menu
https://bugs.kde.org/show_bug.cgi?id=421644 --- Comment #1 from Andy Great --- Created attachment 131813 --> https://bugs.kde.org/attachment.cgi?id=131813&action=edit Test with more languages -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426409] Panel blur does not work when background size is 100%.
https://bugs.kde.org/show_bug.cgi?id=426409 --- Comment #3 from Andy Great --- (In reply to Michail Vourlakos from comment #2) > v0.9.x is not maintained any more, use git version Will the new version come out soon? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426409] Panel blur does not work when background size is 100%.
https://bugs.kde.org/show_bug.cgi?id=426409 Andy Great changed: What|Removed |Added Summary|Panel blur does not blur|Panel blur does not work |work when background size |when background size is |is 100%.|100%. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426409] Panel blur does not blur work when background size is 100%.
https://bugs.kde.org/show_bug.cgi?id=426409 --- Comment #1 from Andy Great --- This effects both xorg and wayland on KDE Plasma. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426409] New: Panel blur does not blur work when background size is 100%.
https://bugs.kde.org/show_bug.cgi?id=426409 Bug ID: 426409 Summary: Panel blur does not blur work when background size is 100%. Product: lattedock Version: 0.9.11 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 131564 --> https://bugs.kde.org/attachment.cgi?id=131564&action=edit Video showing the bug. SUMMARY When increase the background size to 100% under appearance tab, the blue effect stop working. STEPS TO REPRODUCE Enable blur effect. If the background size is 100% it will not have effect. Decrease background size to 99%, blur will come back. EXPECTED RESULT There should be blur at 100% background size. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200906 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.4-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422767] New: Dolphin segmentation fault when click "Close Session" in terminal panel.
https://bugs.kde.org/show_bug.cgi?id=422767 Bug ID: 422767 Summary: Dolphin segmentation fault when click "Close Session" in terminal panel. Product: dolphin Version: 20.04.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: andythe_gr...@pm.me CC: kfm-de...@kde.org Target Milestone: --- Right click on Dolphin terminal and click Close Session will crash Dolphin. Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f9b585df77e in QListData::size (this=0x555c95f22f30) at ../../include/QtCore/../../src/corelib/tools/qlist.h:1032 #5 QtPrivate::indexOf (from=0, u=@0x7ffdbff16718: 0x555c95f077c0, list=...) at ../../include/QtCore/../../src/corelib/tools/qlist.h:1038 #6 QList::indexOf (from=0, t=@0x7ffdbff16718: 0x555c95f077c0, this=0x555c95f22f30) at ../../include/QtCore/../../src/corelib/tools/qlist.h:1026 #7 QList::removeAll (this=0x555c95f22f30, _t=@0x7ffdbff16718: 0x555c95f077c0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:936 #8 0x7f9b58617a27 in QWidget::removeAction (this=0x555c95f051a0, action=) at kernel/qwidget.cpp:3169 #9 0x7f9b5902f6e9 in KActionCollection::removeAssociatedWidget (this=0x555c95eefdb0, widget=) at /usr/src/debug/kxmlgui-5.70.0-1.2.x86_64/src/kactioncollection.cpp:830 #10 0x7f9b5906308b in KXMLGUIClient::prepareXMLUnplug (this=0x555c95dd6158, w=0x555c95f051a0) at /usr/src/debug/kxmlgui-5.70.0-1.2.x86_64/src/kxmlguiclient.cpp:796 #11 0x7f9b5906e301 in KXMLGUIFactory::removeClient (this=0x555c96287730, client=, client@entry=0x555c95dd6158) at /usr/src/debug/kxmlgui-5.70.0-1.2.x86_64/src/kxmlguifactory.cpp:464 #12 0x7f9b32767096 in Konsole::SessionController::~SessionController (this=, this=) at /usr/src/debug/konsole-20.04.1-1.2.x86_64/src/SessionController.cpp:241 #13 0x7f9b327673d9 in Konsole::SessionController::~SessionController (this=, this=) at /usr/src/debug/konsole-20.04.1-1.2.x86_64/src/SessionController.cpp:243 #14 0x7f9b579fb7ef in QObject::event (this=0x555c95dd6130, e=0x555c96026090) at kernel/qobject.cpp:1301 #15 0x7f9b585e10cf in QApplicationPrivate::notify_helper (this=, receiver=0x555c95dd6130, e=0x555c96026090) at kernel/qapplication.cpp:3671 #16 0x7f9b579cfb0a in QCoreApplication::notifyInternal2 (receiver=0x555c95dd6130, event=0x555c96026090) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #17 0x7f9b579d2531 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x555c957e2770) at kernel/qcoreapplication.cpp:1815 #18 0x7f9b57a278c3 in postEventSourceDispatch (s=0x555c958d5d00) at kernel/qeventdispatcher_glib.cpp:277 #19 0x7f9b558482c7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #20 0x7f9b55848648 in ?? () from /usr/lib64/libglib-2.0.so.0 #21 0x7f9b558486ff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #22 0x7f9b57a26f4f in QEventDispatcherGlib::processEvents (this=0x555c958dc660, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #23 0x7f9b579ce4cb in QEventLoop::exec (this=this@entry=0x7ffdbff16c20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #24 0x7f9b579d6730 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #25 0x7f9b59a97a0b in kdemain (argc=, argv=0x7ffdbff16d70) at /usr/src/debug/dolphin-20.04.1-1.2.x86_64/src/main.cpp:172 #26 0x7f9b598a6cca in __libc_start_main () from /lib64/libc.so.6 #27 0x555c954dd08a in _start () at ../sysdeps/x86_64/start.S:120 [Inferior 1 (process 27973) detached] Operating System: openSUSE Tumbleweed 20200609 KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.14-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 421800] Fitted curve function does not change when changing the curve.
https://bugs.kde.org/show_bug.cgi?id=421800 --- Comment #4 from Andy Great --- Created attachment 128680 --> https://bugs.kde.org/attachment.cgi?id=128680&action=edit Blank rectangle -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 421800] Fitted curve function does not change when changing the curve.
https://bugs.kde.org/show_bug.cgi?id=421800 --- Comment #3 from Andy Great --- But somehow the equation display become blank white rectangle? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 421893] Italic on y-axis is italicize in the wrong direction.
https://bugs.kde.org/show_bug.cgi?id=421893 --- Comment #1 from Andy Great --- Created attachment 128679 --> https://bugs.kde.org/attachment.cgi?id=128679&action=edit Italic effect bug. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 421893] New: Italic on y-axis is italicize in the wrong direction.
https://bugs.kde.org/show_bug.cgi?id=421893 Bug ID: 421893 Summary: Italic on y-axis is italicize in the wrong direction. Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: andythe_gr...@pm.me Target Milestone: --- The italic text on x-axis is wrong, see screenshot. Probably have to rotate the italic effect. Latest labplot nightly build. Operating System: openSUSE Tumbleweed 20200519 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.1 Kernel Version: 5.6.12-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 421800] Fitted curve function does not change when changing the curve.
https://bugs.kde.org/show_bug.cgi?id=421800 --- Comment #1 from Andy Great --- Created attachment 128619 --> https://bugs.kde.org/attachment.cgi?id=128619&action=edit Test file -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 421800] New: Fitted curve function does not change when changing the curve.
https://bugs.kde.org/show_bug.cgi?id=421800 Bug ID: 421800 Summary: Fitted curve function does not change when changing the curve. Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 128618 --> https://bugs.kde.org/attachment.cgi?id=128618&action=edit Screenshot with annotation. The display fit function under "f(x)=" does not change when selecting different curve. Select freundlish fitted curve, change model to power and recalculate fit curve Select Henry's law fitted curve. Select back to freundlish fitted curve, observed that it is now polymonial instead. Labplot nightly build Operating System: openSUSE Tumbleweed 20200511 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.1 Kernel Version: 5.6.11-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421644] New: Thai font shift upward in application menu
https://bugs.kde.org/show_bug.cgi?id=421644 Bug ID: 421644 Summary: Thai font shift upward in application menu Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: andythe_gr...@pm.me CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 128527 --> https://bugs.kde.org/attachment.cgi?id=128527&action=edit Thai words shift upward. When typing Thai language into the menu, the words offset upward a bit. English does not. However, any Thai word will cause all the following English word to shift as well. eg. ไทย Floating words Changing Plasma theme have no effects. Expected Result: All languages shold stay in the center. Operating System: openSUSE Tumbleweed 20200511 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.1 Kernel Version: 5.6.11-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 417288] Zoom and drag in log-log plot is broken.
https://bugs.kde.org/show_bug.cgi?id=417288 --- Comment #3 from Andy Great --- Zoom on log-log plot is now smooth, however if I zoom out too much to like 10^-300 labplot will crash, maybe set a limit to how much uer could zoom out or something. Dragging on log-log plot is still not smooth. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 341817] Only two shortcuts can be configured in KCM
https://bugs.kde.org/show_bug.cgi?id=341817 --- Comment #12 from Andy Great --- The problem gone after reboot, maybe some random glitch. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 341817] Only two shortcuts can be configured in KCM
https://bugs.kde.org/show_bug.cgi?id=341817 Andy Great changed: What|Removed |Added CC||andythe_gr...@pm.me --- Comment #11 from Andy Great --- I upgrade my openSUSE Tumbleweed which upgrade KDE from 5.17 to 5.18 and this same bug come back after doing the work around. Operating System: openSUSE Tumbleweed 20200213 KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.5.2-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413542] Can't UNbind Meta+Space from the global shortcuts
https://bugs.kde.org/show_bug.cgi?id=413542 --- Comment #15 from Andy Great --- I upgrade my openSUSE Tumbleweed which upgrade KDE from 5.17 to 5.18 and this same bug come back after doing the work around. Operating System: openSUSE Tumbleweed 20200213 KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.5.2-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 417288] Zoom and drag in log-log plot is broken.
https://bugs.kde.org/show_bug.cgi?id=417288 --- Comment #1 from Andy Great --- Created attachment 125761 --> https://bugs.kde.org/attachment.cgi?id=125761&action=edit log-log plot file use in video. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 417288] New: Zoom and drag in log-log plot is broken.
https://bugs.kde.org/show_bug.cgi?id=417288 Bug ID: 417288 Summary: Zoom and drag in log-log plot is broken. Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 125760 --> https://bugs.kde.org/attachment.cgi?id=125760&action=edit Video of zooming and draging the plot with minimum success. Trying to zoom or drag a log-log plot will cause the plot to either exaggerated or too little. This seems to effect log-log plot significantly. See log-log plot file and video as example. The labplot was install from my own branch https://build.opensuse.org/package/show/home:andythe_great:branches:openSUSE:Factory/labplot-kf5 Operating System: openSUSE Tumbleweed 20200205 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.4.14-2-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 417283] Font color of axis and title change itself.
https://bugs.kde.org/show_bug.cgi?id=417283 --- Comment #1 from Andy Great --- Created attachment 125757 --> https://bugs.kde.org/attachment.cgi?id=125757&action=edit Example file that the bug was screenshoted. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 417283] New: Font color of axis and title change itself.
https://bugs.kde.org/show_bug.cgi?id=417283 Bug ID: 417283 Summary: Font color of axis and title change itself. Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 125756 --> https://bugs.kde.org/attachment.cgi?id=125756&action=edit Screenshot showing the color difference from the setting. The color of the axis and the title change itself from previously black color. Bug found on master branch. The labplot was install from my own branch https://build.opensuse.org/package/show/home:andythe_great:branches:openSUSE:Factory/labplot-kf5 Operating System: openSUSE Tumbleweed 20200205 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.4.14-2-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415375] [Feature Request] Automatically add fit curve equation to the plot and update them automatically.
https://bugs.kde.org/show_bug.cgi?id=415375 --- Comment #1 from Andy Great --- Also option for R^2 and other goodness of fit would be nice. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415375] New: [Feature Request] Automatically add fit curve equation to the plot and update them automatically.
https://bugs.kde.org/show_bug.cgi?id=415375 Bug ID: 415375 Summary: [Feature Request] Automatically add fit curve equation to the plot and update them automatically. Product: LabPlot2 Version: 2.7.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 124601 --> https://bugs.kde.org/attachment.cgi?id=124601&action=edit Libreoffice can add trend line equation in to the plot automatically. In LibreOffice, there are add trend line equation option. This trend line is the fit curve equation that is display as text on the plot. Currently, the only way to do it on labplot is to write out the trend line equation manually, but it take more time and several jump through hoops, the equation also have to be edit when the line equation change. So I would like to propose a feature that add fit curve equation to the plot and update itself when the equation change. The equation is usually written with y-axis as f(x) and x-axis as x, f(x) = 5x + 3 labplot-kf5-2.7.0-1.3 Operating System: openSUSE Tumbleweed 20191207 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 5.3.12-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415223] Latex text have lower resolution than normal text.
https://bugs.kde.org/show_bug.cgi?id=415223 --- Comment #1 from Andy Great --- Created attachment 124518 --> https://bugs.kde.org/attachment.cgi?id=124518&action=edit Example file demostrating the bug -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415223] New: Latex text have lower resolution than normal text.
https://bugs.kde.org/show_bug.cgi?id=415223 Bug ID: 415223 Summary: Latex text have lower resolution than normal text. Product: LabPlot2 Version: 2.7.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 124517 --> https://bugs.kde.org/attachment.cgi?id=124517&action=edit screenshot showing the difference. Latex have lower resolution than normal text. 1. Add latex text 2. Lower latex resolution is observed. labplot-kf5-2.7.0-1.3 Operating System: openSUSE Tumbleweed 20191207 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 5.3.12-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415214] New: Error bar stretch too much in a log plot.
https://bugs.kde.org/show_bug.cgi?id=415214 Bug ID: 415214 Summary: Error bar stretch too much in a log plot. Product: LabPlot2 Version: 2.7.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 124511 --> https://bugs.kde.org/attachment.cgi?id=124511&action=edit Error bar stretch example file Using a log plot as in the attached file as example, the bar of the error bar stretch too much. labplot-kf5-2.7.0-1.3 Operating System: openSUSE Tumbleweed 20191207 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 5.3.12-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415214] Error bar stretch too much in a log plot.
https://bugs.kde.org/show_bug.cgi?id=415214 --- Comment #1 from Andy Great --- Created attachment 124512 --> https://bugs.kde.org/attachment.cgi?id=124512&action=edit Screenshot of the over stretch error bar. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415211] New: Changing font size in the title or axis will convert subscript and super script to normal text.
https://bugs.kde.org/show_bug.cgi?id=415211 Bug ID: 415211 Summary: Changing font size in the title or axis will convert subscript and super script to normal text. Product: LabPlot2 Version: 2.7.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 124509 --> https://bugs.kde.org/attachment.cgi?id=124509&action=edit Example file for testing bug. Changing font size in the title or axis will convert subscript and super script to normal text. 1. Open the example file. 2. Change the font size of the x-axis or y-axis 3. Subscript and super script become normal text. Expected Result. The text should remain superscript and subscript. labplot-kf5-2.7.0-1.3 Operating System: openSUSE Tumbleweed 20191207 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 5.3.12-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415174] Scaling in labplot change itself when re-opening the file.
https://bugs.kde.org/show_bug.cgi?id=415174 --- Comment #1 from Andy Great --- Created attachment 124490 --> https://bugs.kde.org/attachment.cgi?id=124490&action=edit Another file that have the same problem. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415174] New: Scaling in labplot change itself when re-opening the file.
https://bugs.kde.org/show_bug.cgi?id=415174 Bug ID: 415174 Summary: Scaling in labplot change itself when re-opening the file. Product: LabPlot2 Version: 2.7.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 124489 --> https://bugs.kde.org/attachment.cgi?id=124489&action=edit The file that was effected. 1. Open this labplot file. 2. There are 2 plots in it but with no lines. 3. Select 5% CO2 plot, then hover over the selected plot. 4. Use mouse scroll to change to plot scale randomly. 5. Disable and re-enable the Auto x-range and Auto y-range scaling under General. 6. The lines for both graph should appear. 7. Save the file, close it, then open the same file again. 8. The line is now gone because the scale or position change itself. labplot-kf5-2.7.0-1.3 Operating System: openSUSE Tumbleweed 20191207 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 5.3.12-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413542] Can't UNbind Meta+Space from the global shortcuts
https://bugs.kde.org/show_bug.cgi?id=413542 Andy Great changed: What|Removed |Added CC||andythe_gr...@pm.me --- Comment #8 from Andy Great --- I can confirm this. When I hold down meta + space, KRunner show up (the drop down windows) Which it interfere with my shortcut to change keyboard layout. I check to see if KRunner is using meta+space but in the keyboard setting, KRunner is not set to anything. Operating System: openSUSE Tumbleweed 20191107 KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.8-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 411076] Plasma Theme Explorer does not remember picked color
https://bugs.kde.org/show_bug.cgi?id=411076 --- Comment #1 from Andy Great --- I think I made a mistake, it does not default to black, but instead remember the previous color that was selected before. Like when I change red to blue for the first color, then select color to change, it will choose blue for me. -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 411076] New: Plasma Theme Explorer does not remember picked color
https://bugs.kde.org/show_bug.cgi?id=411076 Bug ID: 411076 Summary: Plasma Theme Explorer does not remember picked color Product: Plasma SDK Version: 5.16.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: andythe_gr...@pm.me CC: antonis.tsiapalio...@kde.org Target Milestone: --- Created attachment 122248 --> https://bugs.kde.org/attachment.cgi?id=122248&action=edit Select purple color to change but get black as default. I install plasma sdk to edit the themes. I select edit color to change the color. But when I click on the color to change it, the color selector default to black instead of that particular color that I was trying to change. The color should remain what it originally was. Operating System: openSUSE Tumbleweed 20190810 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 Kernel Version: 5.2.7-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 407542] New: Latte dock on Wayland does not "dodge active" on any workspace except 1st workspace.
https://bugs.kde.org/show_bug.cgi?id=407542 Bug ID: 407542 Summary: Latte dock on Wayland does not "dodge active" on any workspace except 1st workspace. Product: lattedock Version: 0.8.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: andythe_gr...@pm.me Target Milestone: --- When I login to wayland session, latte dock won't hide when dodge active is set even of there is active window there. This work perfectly in xorg. Latte dock 0.8.8-1.1 Operating System: openSUSE Tumbleweed 20190512 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.13-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM STEPS TO REPRODUCE 1. Login to Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 407100] Using KDE Plasma 5 shutdown start menu, computer cannot shutdown when Audacious is running, but Audacious close itself instead. Notification "Logout cancelled by 'audacious" a
https://bugs.kde.org/show_bug.cgi?id=407100 --- Comment #3 from Andy Great --- Alright I will ask them that. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 407100] New: Using KDE Plasma 5 shutdown start menu, computer cannot shutdown when Audacious is running, but Audacious close itself instead. Notification "Logout cancelled by 'audacio
https://bugs.kde.org/show_bug.cgi?id=407100 Bug ID: 407100 Summary: Using KDE Plasma 5 shutdown start menu, computer cannot shutdown when Audacious is running, but Audacious close itself instead. Notification "Logout cancelled by 'audacious" appeared. Product: ksmserver Version: 5.15.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: andythe_gr...@pm.me Target Milestone: --- SUMMARY KDE report that Audacious (music player) cancelled logout, when trying to shutdown while Audacious is running. STEPS TO REPRODUCE 1. Run Audacious 2. Shutdown from shutdown menu 3. "Logout cancelled by 'audacious' appeared OBSERVED RESULT "Logout cancelled by 'audacious' appeared. Shutdown cancelled. EXPECTED RESULT Shutdown normally Audacious 3.10.1 Operating System: openSUSE Tumbleweed 20190428 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.9-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION I ask Audacious dev about this in https://redmine.audacious-media-player.org/issues/887 They mention that Audacious itself don't cancelled logout. Audacious responds to either SIGTERM or an X11 Delete event by closing itself promptly. I try running dbus-monitor while shutting down, no clue if it help, but there is a message about audacious there. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 407100] Using KDE Plasma 5 shutdown start menu, computer cannot shutdown when Audacious is running, but Audacious close itself instead. Notification "Logout cancelled by 'audacious" a
https://bugs.kde.org/show_bug.cgi?id=407100 --- Comment #1 from Andy Great --- user@linux:~> dbus-monitor signal time=1556585302.265492 sender=org.freedesktop.DBus -> destination=:1.57 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.57" signal time=1556585302.265549 sender=org.freedesktop.DBus -> destination=:1.57 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.57" method call time=1556585305.586283 sender=:1.19 -> destination=org.freedesktop.DBus serial=364 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.kde.ksmserver'" method call time=1556585305.586363 sender=:1.19 -> destination=org.freedesktop.DBus serial=365 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner string "org.kde.ksmserver" method return time=1556585305.586387 sender=org.freedesktop.DBus -> destination=:1.19 serial=77 reply_serial=365 string ":1.11" method call time=1556585305.586624 sender=:1.19 -> destination=org.kde.ksmserver serial=366 path=/KSMServer; interface=org.kde.KSMServerInterface; member=canShutdown method return time=1556585305.598339 sender=:1.11 -> destination=:1.19 serial=82 reply_serial=366 boolean true method call time=1556585305.598666 sender=:1.19 -> destination=org.freedesktop.DBus serial=367 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.kde.ksmserver'" method call time=1556585305.598791 sender=:1.19 -> destination=org.freedesktop.DBus serial=368 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.kde.ksmserver'" method call time=1556585305.598935 sender=:1.19 -> destination=org.freedesktop.DBus serial=369 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner string "org.kde.ksmserver" method return time=1556585305.598960 sender=org.freedesktop.DBus -> destination=:1.19 serial=78 reply_serial=369 string ":1.11" method call time=1556585305.599146 sender=:1.19 -> destination=org.kde.ksmserver serial=370 path=/KSMServer; interface=org.kde.KSMServerInterface; member=canShutdown method return time=1556585305.604453 sender=:1.11 -> destination=:1.19 serial=83 reply_serial=370 boolean true method call time=1556585305.604641 sender=:1.19 -> destination=org.freedesktop.DBus serial=371 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.kde.ksmserver'" method call time=1556585308.996598 sender=:1.19 -> destination=org.freedesktop.DBus serial=372 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.kde.ksmserver'" method call time=1556585308.996671 sender=:1.19 -> destination=org.freedesktop.DBus serial=373 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner string "org.kde.ksmserver" method return time=1556585308.996691 sender=org.freedesktop.DBus -> destination=:1.19 serial=79 reply_serial=373 string ":1.11" method call time=1556585308.996905 sender=:1.19 -> destination=org.kde.ksmserver serial=374 path=/KSMServer; interface=org.kde.KSMServerInterface; member=logout int32 -1 int32 2 int32 -1 method call time=1556585308.996930 sender=:1.19 -> destination=org.freedesktop.DBus serial=375 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.kde.ksmserver'" method call time=1556585308.997711 sender=:1.11 -> destination=org.freedesktop.DBus serial=84 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0=
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Andy Great changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Andy Great --- As of March 18, 2019, the issue disappear, probably was fixed. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 402493] US keyboard layout always come out of no where after reboot.
https://bugs.kde.org/show_bug.cgi?id=402493 Andy Great changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 402493] US keyboard layout always come out of no where after reboot.
https://bugs.kde.org/show_bug.cgi?id=402493 --- Comment #5 from Andy Great --- I have found that by default IBus overrides Xmodmap. Changing IBus settings to use system keyboard layout solved the issue. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 402493] US keyboard layout always come out of no where after reboot.
https://bugs.kde.org/show_bug.cgi?id=402493 --- Comment #4 from Andy Great --- This time deleting .config does not solve the issue as the problem would appear shortly after. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 402493] US keyboard layout always come out of no where after reboot.
https://bugs.kde.org/show_bug.cgi?id=402493 --- Comment #3 from Andy Great --- I would like to open this again as the bug appear in Operating System: openSUSE Tumbleweed 20190226 KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.20.10-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.