[kwin] [Bug 405601] Window is disappearing to lower screen border when moved to second monitor
https://bugs.kde.org/show_bug.cgi?id=405601 --- Comment #10 from lsmod --- With the current stable version of Debian the bug does not exist any more. Betriebssystem: Debian GNU/Linux 11 KDE-Plasma-Version: 5.20.5 KDE-Frameworks-Version: 5.78.0 Qt-Version: 5.15.2 Kernel-Version: 5.10.0-8-amd64 Art des Betriebssystems: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445148] The ordering of encodings is different from other KDE apps in "Select Remote Charset" menu
https://bugs.kde.org/show_bug.cgi?id=445148 qydwhotm...@gmail.com changed: What|Removed |Added Summary|Encodings do not have the |The ordering of encodings |same order as other KDE |is different from other KDE |apps in "Select Remote |apps in "Select Remote |Charset" menu |Charset" menu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445148] Encodings do not have the same order as other KDE apps in "Select Remote Charset" menu
https://bugs.kde.org/show_bug.cgi?id=445148 qydwhotm...@gmail.com changed: What|Removed |Added Summary|Encodings does not have the |Encodings do not have the |same order as other KDE |same order as other KDE |apps in "Select Remote |apps in "Select Remote |Charset" menu |Charset" menu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445148] New: Encodings does not have the same order as other KDE apps in "Select Remote Charset" menu
https://bugs.kde.org/show_bug.cgi?id=445148 Bug ID: 445148 Summary: Encodings does not have the same order as other KDE apps in "Select Remote Charset" menu Product: dolphin Version: 21.08.3 Platform: openSUSE RPMs URL: https://youtu.be/Ay28DUrHOB8 OS: Linux Status: REPORTED Keywords: efficiency Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: qydwhotm...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- "Default" option should be the first. See https://youtu.be/Ay28DUrHOB8 for the complaint. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
https://bugs.kde.org/show_bug.cgi?id=443872 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/75863454a0c1 |ma/kwin/commit/638f5482a854 |6e8713fab5662801fd1d15d4e89 |d4538fa3e58588d8d33d9e93861 |a |8 --- Comment #26 from Zamundaaa --- Git commit 638f5482a854d4538fa3e58588d8d33d9e938618 by Xaver Hugl. Committed on 08/11/2021 at 07:53. Pushed by zamundaaa into branch 'Plasma/5.23'. RenderLoop: restrict repaint scheduling with fullscreen windows With an opaque fullscreen window we can be sure that items under it don't actually require us to repaint. This should yield some small efficiency improvements and resolves stutter with adaptive sync. FIXED-IN: 5.23.3 (cherry picked from commit 75863454a0c16e8713fab5662801fd1d15d4e89a) M +4-4src/item.cpp M +5-5src/renderloop.cpp M +3-3src/renderloop.h M +1-1src/renderloop_p.h https://invent.kde.org/plasma/kwin/commit/638f5482a854d4538fa3e58588d8d33d9e938618 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
https://bugs.kde.org/show_bug.cgi?id=443872 Zamundaaa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.23.3 Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/75863454a0c1 ||6e8713fab5662801fd1d15d4e89 ||a --- Comment #25 from Zamundaaa --- Git commit 75863454a0c16e8713fab5662801fd1d15d4e89a by Xaver Hugl. Committed on 06/11/2021 at 23:41. Pushed by zamundaaa into branch 'master'. RenderLoop: restrict repaint scheduling with fullscreen windows With an opaque fullscreen window we can be sure that items under it don't actually require us to repaint. This should yield some small efficiency improvements and resolves stutter with adaptive sync. FIXED-IN: 5.23.3 M +4-4src/item.cpp M +5-5src/renderloop.cpp M +3-3src/renderloop.h M +1-1src/renderloop_p.h https://invent.kde.org/plasma/kwin/commit/75863454a0c16e8713fab5662801fd1d15d4e89a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397835] Status bar and start menu graphics sometimes becomes garbled
https://bugs.kde.org/show_bug.cgi?id=397835 --- Comment #2 from be...@ammitzboell-consult.dk --- I am no longer using the laptop where I was using nouveau. I still have it, but I will have to run an upgrade on it first. I will try to get that done within the next week or so. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 433313] GPG encryption
https://bugs.kde.org/show_bug.cgi?id=433313 Thomas Baumgart changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Thomas Baumgart --- Updating state -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445032] valgrind/memcheck crash with SIGSEGV when SIGVTALRM timer used and libthr.so associated
https://bugs.kde.org/show_bug.cgi?id=445032 --- Comment #6 from Paul Floyd --- paulf@freebsd:~/scratch/sigreturn $ valgrind ./pthread_sigreturn_clang ==866== Memcheck, a memory error detector ==866== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==866== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==866== Command: ./pthread_sigreturn_clang ==866== ==866== Invalid read of size 4 ==866==at 0x720526B: ??? (in /lib/libthr.so.3) ==866==by 0x72048BD: ??? (in /lib/libthr.so.3) ==866==by 0x381A64F3: ??? (in /usr/local/libexec/valgrind/memcheck-x86-freebsd) ==866==by 0x72B973E: sleep (in /lib/libc.so.7) ==866==by 0x4018F2: main (in /usr/home/paulf/scratch/sigreturn/pthread_sigreturn_clang) ==866== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==866== ==866== ==866== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==866== Access not within mapped region at address 0x0 ==866==at 0x720526B: ??? (in /lib/libthr.so.3) ==866==by 0x72048BD: ??? (in /lib/libthr.so.3) ==866==by 0x381A64F3: ??? (in /usr/local/libexec/valgrind/memcheck-x86-freebsd) ==866==by 0x72B973E: sleep (in /lib/libc.so.7) ==866==by 0x4018F2: main (in /usr/home/paulf/scratch/sigreturn/pthread_sigreturn_clang) ==866== If you believe this happened as a result of a stack ==866== overflow in your program's main thread (unlikely but ==866== possible), you can try to increase the size of the ==866== main thread stack using the --main-stacksize= flag. ==866== The main thread stack size used in this run was 16777216. To get this I changed the ASLR sysctls paulf@freebsd:~/scratch/sigreturn $ sysctl -a | grep -i aslr kern.elf32.aslr.stack_gap: 0 (default is 3) kern.elf32.aslr.honor_sbrk: 1 kern.elf32.aslr.pie_enable: 1 (default is 0) kern.elf32.aslr.enable: 1 (default is 0) vm.aslr_restarts: 0 Are yoiu using ASLR as above? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444399] disInstr(arm64): unhandled instruction 0xC87F2D89
https://bugs.kde.org/show_bug.cgi?id=444399 --- Comment #7 from Julian Seward --- Created attachment 143328 --> https://bugs.kde.org/attachment.cgi?id=143328=edit WIP patch that will possibly get you back on the road. DO NOT LAND. Fixing this is a whole trip because the various IR and arm64 frameworks were not really designed to accommodate it. Anyways, here is a WIP patch. It seems to work for simple tests (in the patch) but is not fully tested. It will not work if you run with `--sim-hints=fallback-llsc` or if the fallback LL/SC implementation is auto-selected, based on your processor, at startup. It applies against the head and also against a vanilla 3.18.1 tarball, although I haven't tested it in the latter case. If anyone wants to test it, and let me know if works, that would be appreciated. I will try to finish it up properly this coming week. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434283] disInstr(arm64): unhandled instruction 0xC87FAB5F (LDAXP and STLXP)
https://bugs.kde.org/show_bug.cgi?id=434283 Julian Seward changed: What|Removed |Added CC||jsew...@acm.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Julian Seward --- I'm going to close this as a dup of bug 444399, where there is, now, a preliminary fix available. *** This bug has been marked as a duplicate of bug 444399 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444399] disInstr(arm64): unhandled instruction 0xC87F2D89
https://bugs.kde.org/show_bug.cgi?id=444399 Julian Seward changed: What|Removed |Added CC||a...@ao2.it --- Comment #6 from Julian Seward --- *** Bug 434283 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 Patrick Kopper changed: What|Removed |Added CC|kopper.patr...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 400784] Implement ShellCheck Linter
https://bugs.kde.org/show_bug.cgi?id=400784 shenlebantongying changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||shenlebantongy...@gmail.com --- Comment #3 from shenlebantongying --- This is already implemented. If u come from Google, enable `project` plugin then click `current project` -> `Code analysis` -> select shellcheck. https://phabricator.kde.org/D17314 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445111] Kickoff does not react to graphics tablet left click anymore
https://bugs.kde.org/show_bug.cgi?id=445111 --- Comment #5 from Tyson Tan --- Thank you guys! :D -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444131] Logging out and in again breaks apps
https://bugs.kde.org/show_bug.cgi?id=444131 David changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from David --- Information is already provided. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444129] CPU usage widget does not show anything for "Text only"
https://bugs.kde.org/show_bug.cgi?id=444129 David changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from David --- Information is already provided. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 443229] python highlights on f-string not work.
https://bugs.kde.org/show_bug.cgi?id=443229 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443239] Krusader crashes when attempting to view 7z file
https://bugs.kde.org/show_bug.cgi?id=443239 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444129] CPU usage widget does not show anything for "Text only"
https://bugs.kde.org/show_bug.cgi?id=444129 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444131] Logging out and in again breaks apps
https://bugs.kde.org/show_bug.cgi?id=444131 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 444030] Messier object labels not displayed
https://bugs.kde.org/show_bug.cgi?id=444030 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 443273] Alignment module not working
https://bugs.kde.org/show_bug.cgi?id=443273 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 433313] GPG encryption
https://bugs.kde.org/show_bug.cgi?id=433313 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445146] 7.3.0 AppImage Randomly Crashes
https://bugs.kde.org/show_bug.cgi?id=445146 --- Comment #3 from caulier.gil...@gmail.com --- The line number is 157 --> it come from startup internal bash script in AppImage. It's not the line of code from binary program. `GLIBC_2.29' not found from 7.4.0 want mean that you linux host is to older to run 7.4.0. This last one is compiled with CentOS 7 like system, where 7.3.0 is compiled with CentOS 6 like. We upgrade binary compatibility to compile AppImage bundle for security reasons. About 7.3.0 crash, yes OpenGL issues is possible. We already seen this kind of problem in the past. OpenGL compatibility is a hell under Linux, especially with Qt/Chromium API used internally in digiKam to render Maps. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 445147] New: Baloo won't content index TMDX
https://bugs.kde.org/show_bug.cgi?id=445147 Bug ID: 445147 Summary: Baloo won't content index TMDX Product: frameworks-baloo Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: noti...@zohomail.com Target Milestone: --- SUMMARY Won't index content of TMDX files from Softmaker's Office Suite, specifically Textmaker, the word processor. I assume the same of the rest of the office suite, such as Presenter and PlanMaker. No doubt, this is because TMDX is a non-standard format, but it is a text format. I reached out to Softmaker, and they said to reach out to you. I know, it's probably a run-around, but could you please look into this? :D STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445146] 7.3.0 AppImage Randomly Crashes
https://bugs.kde.org/show_bug.cgi?id=445146 --- Comment #2 from sh...@shaav.com --- On 7.4.0 I'm getting: digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found Was actually in the process of trying to figure out how to install glibc_2.29... Same crash happens on 7.2.0 and 7.0.0 although in 7.0.0 the line number is 157. If it is helpful, I did find that it reliably crashes when switching to the "People" or "Map" tabs and just before the segmentation fault it reliably gives me: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Which I guess is pointing at a driver issue? I'm using the latest proprietary release for my card: nvidia-driver-470 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 143327] Cursors reset to default system visuals on KDE start
https://bugs.kde.org/show_bug.cgi?id=143327 CataleyaFiennes changed: What|Removed |Added CC||fiennes1...@gmail.com URL||https://yhn678.com Alias||CataleyaFiennes -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 444219] celestine
https://bugs.kde.org/show_bug.cgi?id=444219 --- Comment #3 from CataleyaFiennes --- Comment on attachment 143327 --> https://bugs.kde.org/attachment.cgi?id=143327 Kindly visit my website https://xyp7.com -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 444219] celestine
https://bugs.kde.org/show_bug.cgi?id=444219 --- Comment #2 from CataleyaFiennes --- Created attachment 143327 --> https://bugs.kde.org/attachment.cgi?id=143327=edit Kindly visit my website https://xyp7.com -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 444219] celestine
https://bugs.kde.org/show_bug.cgi?id=444219 CataleyaFiennes changed: What|Removed |Added CC||fiennes1...@gmail.com --- Comment #1 from CataleyaFiennes --- Created attachment 143326 --> https://bugs.kde.org/attachment.cgi?id=143326=edit Kindly visit my website https://yhn678.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445146] 7.3.0 AppImage Randomly Crashes
https://bugs.kde.org/show_bug.cgi?id=445146 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Bundle-AppImage --- Comment #1 from caulier.gil...@gmail.com --- Can you test the 7.4.0 AppImage pre-release build available here : https://files.kde.org/digikam/ To see if problem still here. If yes, use AppImage bundle with "debug" suffix and run it from the console with "debug" option from command line. This will run digikam in gdb. When it crash, enter "bt" to get the backtrace. Post the output here... all is explained in this page : https://www.digikam.org/contribute/ Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445146] New: 7.3.0 AppImage Randomly Crashes
https://bugs.kde.org/show_bug.cgi?id=445146 Bug ID: 445146 Summary: 7.3.0 AppImage Randomly Crashes Product: digikam Version: 7.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: sh...@shaav.com Target Milestone: --- SUMMARY 7.3.0 always crashes with: /tmp/.mount_digiKaylqjnZ/AppRun: line 172: 32379 Segmentation fault digikam $@ 'line 172' is always the same; the number before Segmentation fault varies. I have turned on the debugging messages but there is no consistency. Sometimes it crashes after being open for less than a minute. Sometimes it will function normally for upwards of 20-30min. There's no consistent trigger based on what I'm doing in the moment—it's crashed when it's been sitting idle and I've walked away. STEPS TO REPRODUCE 1. Start ./digiKam-7.3.0-x86-64.appimage 2. Wait. OBSERVED RESULT Segmentation Fault EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Mint 19 Cinnamon ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420763] Add folder context menu when right clicking on location bar element (breadcrumb)
https://bugs.kde.org/show_bug.cgi?id=420763 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- One glaring (for me at least) inconsistency between the breadcrumb context menu and the other folder related ones (both the normal one in the main view and the one in the Places sidebar at least) is that the latter provides options to open the folder in a new window and a new tab, whereas the former only provides an option to open the folder in a new tab, which isn't great when I'd like to see the contents of both folders at once. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445145] celestine
https://bugs.kde.org/show_bug.cgi?id=445145 celestine changed: What|Removed |Added URL||https://xyp7.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445145] New: celestine
https://bugs.kde.org/show_bug.cgi?id=445145 Bug ID: 445145 Summary: celestine Product: Akonadi Version: 5.18.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Account Wizard Assignee: kdepim-b...@kde.org Reporter: celestinebr...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. https://twitter.com/BrokeCelestine 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 224312] MAINTENANCE : needs a database archive/backup/restore facility
https://bugs.kde.org/show_bug.cgi?id=224312 Paul Johnson changed: What|Removed |Added CC||paul.m.w.johnson@protonmail ||.com --- Comment #16 from Paul Johnson --- > "...wouldn't it be possible to > just use mysqldump to export the database?" I can verify that mysqldump does, indeed, produce scripts that can be used for saving and restoring databases used with Digikam. After upgrading to 7.3.0 I lost my databases during setup. (I didn't lose them, I made a mistake in configuring Digikam). I missed the place where you set up the four individual databases and assumed you must use a single database for all of the functionality, so I used mysqldump (against MariaDB) to dump all four databases to scripts, and then used those scripts to load them all into a single new database which Digikam was configured to use. (It was at that time I found out where to set up the four separate databases and found that I didn't have to do this at all.) -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 444219] celestine
https://bugs.kde.org/show_bug.cgi?id=444219 celestine changed: What|Removed |Added CC||celestinebr...@gmail.com Summary|Denisse |celestine -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444243] Notifications disappear below current window on click
https://bugs.kde.org/show_bug.cgi?id=444243 --- Comment #11 from Timothy B --- Plasma 5.23.3 is coming out in a few days. Any updates to this so far? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 445071] Fails to load images that contain a ` character.
https://bugs.kde.org/show_bug.cgi?id=445071
--- Comment #1 from northon_patri...@yahoo.ca ---
More info:
```
QUrl url1{"/tmp/test`test.txt"};
std::cout << url1.toString(QUrl::PreferLocalFile).toStdString() << '\n';
QUrl url2{"file:///tmp/test`test.txt"};
std::cout << url2.toString(QUrl::PreferLocalFile).toStdString() << '\n';
```
will output:
```
/tmp/test%60test.txt
/tmp/test`test.txt
```
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 444519] System Settings crashes in Breeze::BoxShadowRenderer::addShadow() upon opening Window Decoration Module
https://bugs.kde.org/show_bug.cgi?id=444519 --- Comment #6 from ryu.ketsu...@outlook.com --- Has there been any development in fixing this? I know it's not easily replicated but so far it's not allowing me to change anything regarding window decorations. Both Window Manager Settings Module and System Settings itself crash if trying to get open those settings. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 445144] New: KDevelop should have a default launch after importing a project
https://bugs.kde.org/show_bug.cgi?id=445144 Bug ID: 445144 Summary: KDevelop should have a default launch after importing a project Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- By default, after importing a project, no launch exists by default. This means the user needs to add it every time. If a target exists, there should be a launch by default so the user is able to just click Run and it just works, as other IDEs do. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 445143] New: Upon opening a project, the project pane should open automatically
https://bugs.kde.org/show_bug.cgi?id=445143 Bug ID: 445143 Summary: Upon opening a project, the project pane should open automatically Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- When a user opens a development project, no matter the IDE, their purpose is to inspect the project's files first, as far as I know. Also, upon opening a new project, there is no feedback indicating the user actually opened the project other than the automatic build on the lower pane. For both cases, I think having the Project pane open when opening a project makes sense. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361274] Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 kde@grau.net changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #17 from kde@grau.net --- Thank you for your feedback! :-) Well, It hardly took 5 years for this result. Hope your children are doing well in college, your back gets better and you have a nice evening before the next week filled with hard work starts. I'll mark this as resolved, as we cannot reproduce the issue and the devs can spend their time on more actionable issue reports. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361274] Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 --- Comment #16 from PGillespie --- (In reply to kde.org from comment #15) > The menus seem to have changed in the mean time. I cannot reproduce the > issue following the description. > Can you please confirm, that it still persists with KDE 5.23 and provide an > updated list of steps on how to reproduce? Not only have the menus changed, my back hurts, my children are all in college, and I no longer need to run separate instances of Firefox. That functionality is achieved with the Multi-Account Container Add-on. I no longer have the setup that produces this bug. It's an admittedly and exceedingly narrow use-case. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 445142] New: Kirigami SearchField decides for you, that you're done typing into it.
https://bugs.kde.org/show_bug.cgi?id=445142 Bug ID: 445142 Summary: Kirigami SearchField decides for you, that you're done typing into it. Product: frameworks-kirigami Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: 31...@tuta.io Target Milestone: Not decided SUMMARY The search just decides for you, when you're done typing into it. So when you get distracted for a second or need to correct a typo, your search term will often end up missing either a bit at the start or the end. I think that's annoying and the search should instead be more like KRunner, which can also load results as soon as you're typing, but doesn't decide when you're done typing into it. STEPS TO REPRODUCE (in case of pause) 1. Open discover or any get new thing and start typing 2. Pause for a moment, like you have to sneeze or your nose itches, or you forget how the app you're looking for is spelt and glance at your phone 3. Type again OBSERVED RESULT You have searched for whatever you typed at step 3, and lost everything from step 1 EXPECTED RESULT You have entered the whole search term that you were trying to search for STEPS TO REPRODUCE (in case of typo) 1. Open discover or any get new thing and start typing 2. Notice you have made a typo earlier 3. Use the left arrow key to navigate to said typo OBSERVED RESULT The cursor loses its position before you can get to your typo and the next keystroke clears the search field and you end up only searching for the letters you wanted to drop into your misspelled search term. EXPECTED RESULT You get to correct your typo SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 35 (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm sorry guys, I'm a slow typer and I'm clumsy. Issue might be related to 437722, but I'm not sure, so I thought it best to submit this -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445135] “Foreground to background color” in layerstyles
https://bugs.kde.org/show_bug.cgi?id=445135 --- Comment #1 from thetwo <310732...@qq.com> --- Created attachment 143325 --> https://bugs.kde.org/attachment.cgi?id=143325=edit test I tested it again: I created a gradient from foreground to foreground. It is red when it is created. So no matter what color I choose, it is always red in layerstyles -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 445141] New: Battery of bluetooth device not being shown
https://bugs.kde.org/show_bug.cgi?id=445141 Bug ID: 445141 Summary: Battery of bluetooth device not being shown Product: Bluedevil Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: daemon Assignee: now...@gmail.com Reporter: matthewbtjones2...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Enable bluez experimental mode 2. Connect device with battery indicator via bluetooth OBSERVED RESULT Battery level of device is not shown in energy screen of plasma info centre, nor in the battery widget (not sure what this is called). It is shown correctly in the bluetooth widget and with upower -d. EXPECTED RESULT Battery level of device is shown in the energy screen of the plasma info centre and in the battery widget. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Bluez Version: 5.82.1 Bluedevil Version: 5.23.2 Upower Version: 0.99.13.1 ADDITIONAL INFORMATION I think the experimental bluez battery API is being used for battery indicator levels. Not sure if it's relevant, but I'm testing with Sony WH-1000XM4s and I'm using pipewire. Not sure if this is filed under the right component, feel free to let me know if it's not! :) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411968] Kontact crashed after forwarding an email inline with attachment
https://bugs.kde.org/show_bug.cgi?id=411968 Antonio Rojas changed: What|Removed |Added CC||pmanou...@gmail.com --- Comment #5 from Antonio Rojas --- *** Bug 421054 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 421054] Crash (segfault) on email reply
https://bugs.kde.org/show_bug.cgi?id=421054 Antonio Rojas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||aro...@archlinux.org --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 411968 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445140] "No titlebar and frame" Window rule makes applications open in a very tiny window.
https://bugs.kde.org/show_bug.cgi?id=445140 tomasralph2...@gmail.com changed: What|Removed |Added Keywords||wayland --- Comment #1 from tomasralph2...@gmail.com --- I forgot to note that this is a Wayland specific issue. The rule works perfectly fine on X11. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411968] Kontact crashed after forwarding an email inline with attachment
https://bugs.kde.org/show_bug.cgi?id=411968 Antonio Rojas changed: What|Removed |Added CC||manuavazq...@gmail.com --- Comment #4 from Antonio Rojas --- *** Bug 413318 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 413318] Kmail crashes when trying to reply an empty e-mail with a (pdf) file attached
https://bugs.kde.org/show_bug.cgi?id=413318 Antonio Rojas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||aro...@archlinux.org --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 411968 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411968] Kontact crashed after forwarding an email inline with attachment
https://bugs.kde.org/show_bug.cgi?id=411968 Antonio Rojas changed: What|Removed |Added CC||lill...@web.de --- Comment #3 from Antonio Rojas --- *** Bug 421263 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 421263] Mail crashes on reply
https://bugs.kde.org/show_bug.cgi?id=421263 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 411968 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411968] Kontact crashed after forwarding an email inline with attachment
https://bugs.kde.org/show_bug.cgi?id=411968 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #2 from Antonio Rojas --- *** Bug 415167 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 415167] Crash when replying to an email
https://bugs.kde.org/show_bug.cgi?id=415167 Antonio Rojas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 411968 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445140] New: "No titlebar and frame" Window rule makes applications open in a very tiny window.
https://bugs.kde.org/show_bug.cgi?id=445140 Bug ID: 445140 Summary: "No titlebar and frame" Window rule makes applications open in a very tiny window. Product: kwin Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: tomasralph2...@gmail.com CC: isma...@gmail.com Target Milestone: --- SUMMARY If you add the "No titlebar and frame" window rule to any application, it will open in the tiniest possible window. STEPS TO REPRODUCE 1. Add a window rule 2. Match the window class you desire 3. Add "No titlebar and frame" window rule and set it to "yes" 4. Apply 5. Open the program the rule is applying to. OBSERVED RESULT The window does indeed have no borders, but it opens in a very tiny window EXPECTED RESULT The window shouldn't have borders and it should open in the stored window size it previously had SOFTWARE/OS VERSIONS Linux: 5.14.16-arch1-1 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Here are some screenshots: Expected result: https://i.imgur.com/DpUy8jz.jpg Actual result: https://i.imgur.com/MckDDRy.jpg -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 445137] KPM sets flags on GPT partitions with no indication that this is happening and no option to turn it off
https://bugs.kde.org/show_bug.cgi?id=445137 Andrius Štikonas changed: What|Removed |Added URL||https://invent.kde.org/syst ||em/kpmcore/-/merge_requests ||/29 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 445137] KPM sets flags on GPT partitions with no indication that this is happening and no option to turn it off
https://bugs.kde.org/show_bug.cgi?id=445137 Andrius Štikonas changed: What|Removed |Added Latest Commit||f4664671d60ae131921b185d44f ||b264c3eac4d02 Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 445137] KPM sets flags on GPT partitions with no indication that this is happening and no option to turn it off
https://bugs.kde.org/show_bug.cgi?id=445137 Andrius Štikonas changed: What|Removed |Added Version Fixed In||21.12.0 --- Comment #1 from Andrius Štikonas --- I think this was fixed two months ago (so will be in 21.12) https://invent.kde.org/system/kpmcore/-/merge_requests/29 We didn't deliberately set attributes, but that field was not initialized and I guess contains random garbage. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445040] Accent colors should apply different hover and focus colours
https://bugs.kde.org/show_bug.cgi?id=445040
--- Comment #1 from Paul McAuley ---
I worked around this in my own C++ window decoration by doing the following:
if(buttonFocusColor == buttonHoverColor) buttonHoverColor =
ColorTools::getDifferentiatedLessSaturatedColor(buttonHoverColor);
QColor ColorTools::getDifferentiatedLessSaturatedColor( const QColor&
inputColor )
{
int colorHsv[3];
inputColor.getHsv([0], [1], [2]);
if( colorHsv[1] > 125 ) colorHsv[1] -= 80; //decrease saturation if not
already low
else colorHsv[1] += 80; // else increase saturation if very low to
provide differentiation/contrast
QColor outputColor;
outputColor.setHsv(colorHsv[0], colorHsv[1], colorHsv[2]);
return outputColor;
}
I have to still apply this in several other places in the application style
where hover and focus colours are the same, and it would be better if I didn't
have to do this at all.
--
You are receiving this mail because:
You are watching all bug changes.
[Skanpage] [Bug 445139] New: Skanpage coredump
https://bugs.kde.org/show_bug.cgi?id=445139 Bug ID: 445139 Summary: Skanpage coredump Product: Skanpage Version: 1.0.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: hipant...@gmail.com Target Milestone: --- Created attachment 143324 --> https://bugs.kde.org/attachment.cgi?id=143324=edit logs SUMMARY When I start skanpage from Plasma or from the CLI it generates coredump and exits. STEPS TO REPRODUCE 1. Start skanpage via GUI or CLI 2. 3. OBSERVED RESULT Skanpage window closes. In some cases the window doesn't close, the scanner is found and scanning is initiated but only empty pages are produced. Scanning with Skanlite works as expected. EXPECTED RESULT Skanpage shows the scanned content. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: Radeon RX550/550 Series ADDITIONAL INFORMATION In the attachment are the logs from application execution. The important line is 51/52 "Re-raising signal for core dump handling. [2] + 406506 segmentation fault (core dumped) skanpage" The scanner details are available in the scanimage.log The core dump can be downloaded from here: https://drive.google.com/file/d/1SrcdAPSNvNthNGCg5Xifgp8nBHuLt1tQ/view?usp=sharing Please let me know if any further information is needed for debugging. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 445138] New: "Allow resizing maximized windows from window edges" doesn't allow resizing from the right screen edge
https://bugs.kde.org/show_bug.cgi?id=445138 Bug ID: 445138 Summary: "Allow resizing maximized windows from window edges" doesn't allow resizing from the right screen edge Product: Breeze Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: k...@paulmcauley.com CC: kwin-bugs-n...@kde.org Target Milestone: --- 1. Tick "Allow resizing maximized windows from window edges" in Breeze window decoration settings. 2. Maximize a window and try to resize the edges - the top, left and bottom edges resize, but the right edge does not. Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-59.27-preempt (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 445137] New: KPM sets flags on GPT partitions with no indication that this is happening and no option to turn it off
https://bugs.kde.org/show_bug.cgi?id=445137 Bug ID: 445137 Summary: KPM sets flags on GPT partitions with no indication that this is happening and no option to turn it off Product: partitionmanager Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: ilia-k...@gmx.net Target Milestone: --- As the title says, KDE Partition Manager apparently sets several flags on newly created GPT partitions, among them a "Hide from EFI" flag, which made me spend a few hours today trying to figure out why my computer happily boots from a live USB, but doesn't see the EFI system partition I created... gdisk reports this as Attribute flags: 80660003 Going to gdisk's "extra functionality" and accessing the "set attributes" menu lists the flags as 0 (system partition) 1 (hide from EFI) 49 (Undefined bit #49) 50 (Undefined bit #50) 53 (Undefined bit #53) 54 (Undefined bit #54) 63 (do not automount) To my knowledge, KPM is the only tool doing that. Partitions created with gdisk have absolutely no flags set, and while I have not checked gparted explicitly, I have never had problems with unfindable EFI system partitions when I used gparted. Please don't set any flags by default or at least provide an option to turn this behavior off and/or to edit the flags. The live USB that I used to create the EFI system partition was a custom Debian Sid image built a few days ago with KPM 21.08.0, but I've also confirmed this behavior on a newly installed Arch system with KPM 21.08.3. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 340420] Make it easier to find components for common products
https://bugs.kde.org/show_bug.cgi?id=340420 Nate Graham changed: What|Removed |Added CC||d_debn...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 442883] Parent app hangs or crashes when selecting "all" in icon chooser dialog's combobox
https://bugs.kde.org/show_bug.cgi?id=442883 --- Comment #14 from Pawel --- another instance of the hang after saving an ogg file from firefox and double clicking on it: kf.kio.slaves.file: the file doesn't have any xattr QWaylandDataOffer: select() failed QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType text/uri-list kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) libkcups: Renew-Subscription last error: 0 successful-ok QOpenGLTexturePrivate::destroy() called without a current context. Texture has not been destroyed kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) QOpenGLTexturePrivate::destroy() called without a current context. Texture has not been destroyed kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55eefcab90f0) QOpenGLTexturePrivate::destroy() called without a current context. Texture has not been destroyed (firefox:78834): Gdk-WARNING **: 22:50:56.295: Server is missing xdg_foreign support (firefox:78834): Gtk-WARNING **: 22:50:56.295: Failed to export handle, could not set transient for file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/CompactRepresentation.qml:131:13: QML PropertyChanges: Cannot assign to non-existent property "visible" QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection The Wayland connection broke. Did the Wayland compositor die? -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 340420] Make it easier to find components for common products
https://bugs.kde.org/show_bug.cgi?id=340420 Nate Graham changed: What|Removed |Added Summary|Make it easier to file |Make it easier to find |issue reports |components for common ||products CC||n...@kde.org Keywords||usability Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 444972] Login button outside screen
https://bugs.kde.org/show_bug.cgi?id=444972 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 444972] Login button outside screen
https://bugs.kde.org/show_bug.cgi?id=444972 Nate Graham changed: What|Removed |Added Component|templates |general CC||d_debn...@outlook.com, ||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 445136] New: Initial install. Crash while setting theme.
https://bugs.kde.org/show_bug.cgi?id=445136 Bug ID: 445136 Summary: Initial install. Crash while setting theme. Product: kde-cli-tools Version: 5.23.2 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: mlber...@gmail.com Target Milestone: --- Application: kcmshell5 (5.23.2) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-38-generic x86_64 Windowing System: X11 Distribution: Windowsfx 11 DrKonqi: 5.23.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Had just installed OS; was setting up a theme; selected "Dark Willow" (or "Willow Dark" ??). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Segmentation fault [New LWP 2159] [New LWP 2160] [New LWP 2161] [New LWP 2162] [New LWP 2163] [New LWP 2164] [New LWP 2178] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f593096caff in __GI___poll (fds=0x7fff51b0e678, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f592c035980 (LWP 2157))] Thread 8 (Thread 0x7f58fdb99700 (LWP 2178)): #0 0x7f592ee2f363 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f592ee2f4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5930f3a61b in QEventDispatcherGlib::processEvents (this=0x7f58ec000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f5930ede8ab in QEventLoop::exec (this=this@entry=0x7f58fdb98c00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #4 0x7f5930cf82c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #5 0x7f592ff64549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f5930cf945c in QThreadPrivate::start (arg=0x5636c95d3f00) at thread/qthread_unix.cpp:329 #7 0x7f592f841609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f5930979293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f5920cd9700 (LWP 2164)): #0 0x7f593096caff in __GI___poll (fds=0x7f5904004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f592ee2f36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f592ee2f4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5930f3a61b in QEventDispatcherGlib::processEvents (this=0x7f5904000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5930ede8ab in QEventLoop::exec (this=this@entry=0x7f5920cd8c00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f5930cf82c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f592ff64549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f5930cf945c in QThreadPrivate::start (arg=0x5636c7f91e40) at thread/qthread_unix.cpp:329 #8 0x7f592f841609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5930979293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f5921eea700 (LWP 2163)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5636c7e9675c) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5636c7e96708, cond=0x5636c7e96730) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5636c7e96730, mutex=0x5636c7e96708) at pthread_cond_wait.c:638 #3 0x7f5922833e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f5922833a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7f592f841609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f5930979293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f59226eb700 (LWP 2162)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5636c7e96758) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5636c7e96708, cond=0x5636c7e96730) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5636c7e96730, mutex=0x5636c7e96708) at pthread_cond_wait.c:638 #3 0x7f5922833e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f5922833a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7f592f841609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f5930979293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f5928dd8700 (LWP 2161)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5636c7e96758) at
[krita] [Bug 445135] “Foreground to background color” in layerstyles
https://bugs.kde.org/show_bug.cgi?id=445135 Tiar changed: What|Removed |Added Keywords||regression, release_blocker CC||tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444676] Option for auto-generated accent color from current wallpaper
https://bugs.kde.org/show_bug.cgi?id=444676 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 442820] Accent colors don't look as good with Breeze Dark as they do with Breeze Light
https://bugs.kde.org/show_bug.cgi?id=442820 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445040] Accent colors should apply different hover and focus colours
https://bugs.kde.org/show_bug.cgi?id=445040 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445135] New: “Foreground to background color” in layerstyles
https://bugs.kde.org/show_bug.cgi?id=445135 Bug ID: 445135 Summary: “Foreground to background color” in layerstyles Product: krita Version: 5.0.0-beta2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: 310732...@qq.com Target Milestone: --- SUMMARY I turned on the gradient in layerstyles and selected "Foreground to background color". It displays the correct color in the interface. But there is an error on the image. It uses a white to black gradient as a blend. STEPS TO REPRODUCE 1. turn on layerstyles 2. turn on gradients 3. choose Foreground to background color -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 445102] Keybindings are not persistent between sessions
https://bugs.kde.org/show_bug.cgi?id=445102 --- Comment #2 from T.M. Láska --- Hi there, Thanks for getting back to me when you could. When it comes to step 3a: the issue happened within Konqueror: I only attempted to update the keybindings within the Configure Keyboard Shortcuts window in Konqueror and then after clicking apply noticed the keybindings were not registering at all as having changed, restarting the application or not. I tried to change the modifier key on most of the shortcuts. For instance, most of the Mod keys on Konqueror appear to be Control keys whereas I tend to use the Super key as my Mod key, so I went through and edited the keys to reflect that; one clear example was changing access to the Home page from Alt+Home to Super+Home and just not having that register at all. Hopefully this can help a little bit. On 2021-11-07 01:55, Stefano Crocco wrote: > https://bugs.kde.org/show_bug.cgi?id=445102 > > Stefano Crocco changed: > >What|Removed |Added > > CC| > |stefano.cro...@alice.it > > --- Comment #1 from Stefano Crocco --- > In the step 3a, is the keybinding window you need to check the one in > Konqueror > or something else? I'm asking because you didn't explicitly say to > restart > Konqueror before checking that window. > > I can't reproduce this bug on my system. Can you tell me which > shortcuts you > tried to change? Maybe the bug only happens with some shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397745] Meta Key doesn't work after gaming.
https://bugs.kde.org/show_bug.cgi?id=397745 kde@grau.net changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from kde@grau.net --- User cannot reproduce issue due to hw change. Setting to resolved -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445134] Plasma crash when resuming session
https://bugs.kde.org/show_bug.cgi?id=445134 --- Comment #1 from Carlos Castro --- Created attachment 143323 --> https://bugs.kde.org/attachment.cgi?id=143323=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445134] New: Plasma crash when resuming session
https://bugs.kde.org/show_bug.cgi?id=445134 Bug ID: 445134 Summary: Plasma crash when resuming session Product: plasmashell Version: 5.23.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: carlos.r.castr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.2) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-38-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.2 [KCrashBackend] -- Information about the crash: - Unusual behavior I noticed: I have 2 screens, the main one via DisplayPort and an additional one via HDMI, when I lock the screens and re-enter after entering the user password, all the windows get messed up and go to the additional screen and a notification appears indicating that plasma has had an error. It always happens in XORG. The crash can be reproduced every time. -- Backtrace (Reduced): #4 QQuickItemPrivate::addToDirtyList (this=this@entry=0x5616fcda4b70) at items/qquickitem.cpp:6203 #5 0x7f03b908b336 in QQuickItemPrivate::dirty (this=this@entry=0x5616fcda4b70, type=type@entry=QQuickItemPrivate::Size) at items/qquickitem.cpp:6188 #6 0x7f03b908c97b in QQuickItem::setSize (this=0x5616fcda0410, size=...) at items/qquickitem.cpp:7035 #7 0x7f03b907bea9 in QQuickAnchorsPrivate::fillChanged (this=0x5616fcdba650) at items/qquickanchors.cpp:435 #8 0x7f03b90926b4 in QQuickItem::geometryChanged (this=0x5616fc5a9300, newGeometry=..., oldGeometry=...) at items/qquickitem.cpp:3759 The reporter indicates this bug may be a duplicate of or related to bug 363118. Possible duplicates by query: bug 444960, bug 444745, bug 444742, bug 00, bug 423109. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397745] Meta Key doesn't work after gaming.
https://bugs.kde.org/show_bug.cgi?id=397745 --- Comment #7 from Tony --- (In reply to kde.org from comment #6) > This issue report is quite old. Can you please confirm, that it still > persists with Plasma 5.23? I'm sorry, i can't no longer check for this bug on that machine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444175] Wayland: After rotating the screen twice and then opening the system tray, the wallpaper is cut off
https://bugs.kde.org/show_bug.cgi?id=444175 Firlaev-Hans changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Firlaev-Hans --- After the upgrade to Fedora 35 the issue no longer appears even though the Plasma version is still the same (but Frameworks have been upgraded to 5.87) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444969] Digikam often freezes when dropping a tag over another to merge them
https://bugs.kde.org/show_bug.cgi?id=444969 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.4.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #16 from Maik Qualmann --- Thank you for your feedback and for creating the backtraces to localize the problem. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444969] Digikam often freezes when dropping a tag over another to merge them
https://bugs.kde.org/show_bug.cgi?id=444969 --- Comment #15 from MarcP --- I just tried with today's appimage, and also with the latest flatpak, using the same pictures, and the problem seems to have been solved. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445129] Provide an ability to emit dbus signals and react to the method calls, so that other programs could interact with a KWin Script
https://bugs.kde.org/show_bug.cgi?id=445129 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443596] Ability to opt out of minimum window size rule, while the script is loaded
https://bugs.kde.org/show_bug.cgi?id=443596 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424795] Unfocused windows don't get brought forward when activated externally
https://bugs.kde.org/show_bug.cgi?id=424795 Patrick Silva changed: What|Removed |Added CC||egor.kuznetsov...@gmail.com --- Comment #24 from Patrick Silva --- *** Bug 445128 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 445128] Kate Window not raised automaticly on Wayland
https://bugs.kde.org/show_bug.cgi?id=445128 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 424795 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445132] Task switcher has a lag on first activation
https://bugs.kde.org/show_bug.cgi?id=445132 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344882] Thumbs missing after disconnecting external display
https://bugs.kde.org/show_bug.cgi?id=344882 Anders Lund changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 --- Comment #33 from p.w.stockwel...@gmail.com --- On 07/11/2021 19:05, Satyam wrote: > https://bugs.kde.org/show_bug.cgi?id=443410 > > --- Comment #32 from Satyam --- > (In reply to p.w.stockwell01 from comment #31) >> I'm really fed up with doing an update on my system, a system I have spent... > > I certainly have my share of annoyances and frustrations but I don't lose > appreciation and sight of the fact that KDE is a gift by people volunteering > time and hard work. People Volunteer because they want to, or dare I say it because they receive remuneration in the many forms that makes them want to carry on, as do I. Whether it is money, status, gratitude or for a feeling of belonging. It is still the case that removing functionality or performance is a bad idea and trying to use prioritization or resource availability as the reason is short sited as it make it seem like a deliberate decision to do it. To say it doesn't matter to the people who use KDE would be arrogant and I'm sure none of the developers intend to be arrogant. I haven't lost site of what KDE is, I have used KDE for years I have loved promoted and supported it despite the difficulties transitioning from KDE4 to 5. But have you lost site of the importance of your user base and the support you need. Every time this sort of thing happens, like many others, I look for alternatives and evaluate if the retrograde step has let another Graphics User Interface take the lead. Don't take this as a complaint or moaning take it as constructive criticism that may make you take things into account that have not been considered. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425852] When non-default "middle-click to paste sticky note in panel" behavior somehow gets activated, there is no UI to turn it off
https://bugs.kde.org/show_bug.cgi?id=425852 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #27 from Nate Graham --- Hmm, since this bug report wound up being used for something else (sorry about that), let's track your original request with Bug 441668. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 350645] Huge icons in Task Switcher
https://bugs.kde.org/show_bug.cgi?id=350645 Matias L changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #9 from Matias L --- To the best of my knowledge, it doesn't happen anymore :) (honestly, I have migrated from that setup long ago). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 --- Comment #32 from Satyam --- (In reply to p.w.stockwell01 from comment #31) > I'm really fed up with doing an update on my system, a system I have spent... I certainly have my share of annoyances and frustrations but I don't lose appreciation and sight of the fact that KDE is a gift by people volunteering time and hard work. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445032] valgrind/memcheck crash with SIGSEGV when SIGVTALRM timer used and libthr.so associated
https://bugs.kde.org/show_bug.cgi?id=445032 --- Comment #5 from Paul Floyd --- paulf@freebsd:~/scratch/sigreturn $ clang -o pthread_sigreturn_clang -pthread sigreturn.c paulf@freebsd:~/scratch/sigreturn $ valgrind ./pthread_sigreturn_clang ==1910== Memcheck, a memory error detector ==1910== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1910== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==1910== Command: ./pthread_sigreturn_clang ==1910== ==1910== ==1910== HEAP SUMMARY: ==1910== in use at exit: 728 bytes in 2 blocks ==1910== total heap usage: 2 allocs, 0 frees, 728 bytes allocated ==1910== ==1910== LEAK SUMMARY: ==1910==definitely lost: 0 bytes in 0 blocks ==1910==indirectly lost: 0 bytes in 0 blocks ==1910== possibly lost: 0 bytes in 0 blocks ==1910==still reachable: 728 bytes in 2 blocks ==1910== suppressed: 0 bytes in 0 blocks ==1910== Rerun with --leak-check=full to see details of leaked memory ==1910== ==1910== For lists of detected and suppressed errors, rerun with: -s ==1910== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Time to build myself an i386 kernel -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 444849] Make all issues appear in the My Bugs section, independently of the bug status
https://bugs.kde.org/show_bug.cgi?id=444849 --- Comment #7 from D. Debnath --- I think you can significantly simplify the link with this: https://bugs.kde.org/buglist.cgi?email1=ncqm3qdz%40anonaddy.me_to1=1=1=substring=OP=OP=bug_status=reporter=CP=CP=OR_name=Show%20all%20the%20bugs_id=1931964=notequals=equals_based_on=Show%20all%20the%20bugs_format=advanced=UNCONFIRMED=EMAIL_ADDRESS_HERE Essentially, if you want all values of bug_status and all values of resolution, then just don't include them in the link at all. However, I don't have admin permissions on Bugzilla. The admins of Bugzilla will have to look into it. I've added Ben Cooksley to the CC of this bug. Let's see what he says. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445032] valgrind/memcheck crash with SIGSEGV when SIGVTALRM timer used and libthr.so associated
https://bugs.kde.org/show_bug.cgi?id=445032 --- Comment #4 from Paul Floyd --- Looks like we are both using fairly old kit. My VM has CPU: Intel(R) Xeon(R) CPU W3520 @ 2.67GHz (2666.79-MHz 686-class CPU) Origin="GenuineIntel" Id=0x106a5 Family=0x6 Model=0x1a Stepping=5 Features=0x1783fbbf Features2=0x182209 AMD Features=0x800 AMD Features2=0x1 TSC: P-state invariant -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 p.w.stockwel...@gmail.com changed: What|Removed |Added CC||p.w.stockwel...@gmail.com --- Comment #31 from p.w.stockwel...@gmail.com --- I'm really fed up with doing an update on my system, a system I have spent hundreds of hours using and refining to suit my needs to find that once again functionality that I use has been removed or made unusable without any warning prior to the update. KDE is the best full functional configurable Linux desktop, but it is the worst for updates that break things or replace working functionality with something that requires major hardware updating for it to work (Dropping Compiz in favor of clunky slow Plasma) It took months, no years for Plasma to get anywhere near Compiz functionality. The mucking about with login types and the mess that still exist today are just small examples of the continues anoyance. But the one thing Linux users use everyday is the graphic user interface on their screen. It is what sells KDE and Linux to new users, it is what makes the system usable by experienced users. Fundamentally changing it by removing function is both short sited and foolhardy. The only other operating system producer to have been so ridiculously short sighted is Microsoft who to this day have not and may not ever recover the popularity that the windows XP interface had. Microsoft have been able to get away with it because the vast majority of Microsoft end users don't know how to use anything else. Its a level of arrogance that Some haven't survived (Big Blue and the PS2). Please don't be arrogant by assuming people didn't use the cube or by saying you don't have the resources to maintain KDE without taking backward functionality steps and it doesn't matter because other stuff is more important. Nothing is more important than how KDE looks and feels it is after all a graphics user interface. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445032] valgrind/memcheck crash with SIGSEGV when SIGVTALRM timer used and libthr.so associated
https://bugs.kde.org/show_bug.cgi?id=445032 --- Comment #3 from Nick Briggs --- It doesn't fail in a VirtualBox running FreeBSD 13.0 on hardware that reports out as: CPU: Intel(R) Core(TM)2 Duo CPU T9800 @ 2.93GHz (2918.76-MHz 686-class CPU) Origin="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 Features=0x1783fbbf Features2=0x82209 AMD Features2=0x1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 445133] New: Qt Group Box title will only horizontally align center
https://bugs.kde.org/show_bug.cgi?id=445133 Bug ID: 445133 Summary: Qt Group Box title will only horizontally align center Product: Breeze Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: k...@paulmcauley.com CC: noaha...@gmail.com Target Milestone: --- I am trying to align a Qt Group Box title in Qt Designer to the left. However, if you try to horizontally align the Group Box title to the left or the right it still displays in the center. If I change my application style to Fusion this works perfectly, but not in Breeze. Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-59.27-preempt (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
