[plasmashell] [Bug 449800] Battery & Brightness widget, no more displayed
https://bugs.kde.org/show_bug.cgi?id=449800 Philippe ROUBACH changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Philippe ROUBACH --- Fixed by executing "plasmashell --replace" Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449993] New: Font and icon rendering in Electron apps (I think?) is blurry in Plasma only, on WQHD screens
https://bugs.kde.org/show_bug.cgi?id=449993 Bug ID: 449993 Summary: Font and icon rendering in Electron apps (I think?) is blurry in Plasma only, on WQHD screens Product: kwin Version: 5.23.5 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: gustoh...@gmail.com Target Milestone: --- SUMMARY Pretty much the summary. The "I think?" is because it seems to happen in web-based apps, I'm not sure what's what but I think it's an electron thing. This is all happening on my new laptop fedora 35, using wayland. The reason I'm posting this on the KDE sub tho is because all these apps are fine on GNOME from my testing, but act up in Plasma. I think it's something to do with how Plasma handles scaling, since this new device has a 1440p screen, and I've never had this before on 1080p and 768p screens, plus when I set the scaling in plasma to 100% nothing is blurred, but everything is zoomed out so it's not too ideal. I'd appreciate all the help I could get on this since this device is essential for work and school. STEPS TO REPRODUCE 1. Install any electron-based app, whether through flatpak or the package manager 2. Open it, in plasma, using wayland OBSERVED RESULT The fonts and icons are blurry EXPECTED RESULT The fonts and icons are not blurry SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 35, Plasma 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449348] Unable to launch recently used apps from "history" and "frequently used" tabs
https://bugs.kde.org/show_bug.cgi?id=449348
--- Comment #9 from Oleg Solovyov ---
in RecentUsageModel::trigger:
if (!mimeType.isEmpty()) { // mimeType == " ", isEmpty() == false
I don't think it's what we want
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 405235] Slow startup and new file scan on low latency networks
https://bugs.kde.org/show_bug.cgi?id=405235 --- Comment #44 from Maik Qualmann --- I understand you correctly that the change from an album takes 3 minutes after the start? This is a database operation, in principle there is no loss of time. You must have very, very slow access to your database. Since there are no error messages in the log, the behavior cannot be explained, check the rights as Gilles already recommends. Maik -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 449992] dropdown menu and folder path text overflowing in android version
https://bugs.kde.org/show_bug.cgi?id=449992 thomas.ramsa...@gmx.de changed: What|Removed |Added OS|Other |Android 10.x Platform|Other |Android -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 439490] Ambiguous Shortcuts -- There are two actions (Open Command Bar, Add Images ...) that want to use the same shortcut (Ctrl+Alt+I). This is most probably a bug.
https://bugs.kde.org/show_bug.cgi?id=439490 Marcos Dione changed: What|Removed |Added CC||mdi...@grulic.org.ar --- Comment #4 from Marcos Dione --- Weird, I just came to report this same thing and the initial search "digikam two actions one shortcut" returned nothing relevant https://bugs.kde.org/buglist.cgi?quicksearch=digikam%20two%20actions%20one%20shortcut&list_id=1977148, but once I started writing the report, the interface correctly suggested this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 449968] [Feature Request] Dynamic / Virtual Albums
https://bugs.kde.org/show_bug.cgi?id=449968 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #6 from Maik Qualmann --- Let's be realistic, if a virtual album doesn't build on something that already exists like tags, labels or search, it has to be completely reprogrammed. The database must be expanded, etc. This cannot be implemented "quickly". As a workaround, you can create a physical album in which you can manage images via symlinks. With the local export tool it is possible to create symlinks. You can specify your folder within your collection as a destination. After refreshing your folder with STR+F5 you will see the symlink images. You can even assign your own tags or labels to the symlinks within the database. You should only deactivate the writing of the metadata, otherwise the original images will be changed. Manual sorting of the symlink images is also possible. Maik -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 449992] New: dropdown menu and folder path text overflowing in android version
https://bugs.kde.org/show_bug.cgi?id=449992 Bug ID: 449992 Summary: dropdown menu and folder path text overflowing in android version Product: Elisa Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: thomas.ramsa...@gmx.de Target Milestone: --- Created attachment 146569 --> https://bugs.kde.org/attachment.cgi?id=146569&action=edit screenshot of behaviour SUMMARY The text of some dropdown menus in the settings are out of display bounds. STEPS TO REPRODUCE 1. Open Elisa 2. Go to settings OBSERVED RESULT Not all text of dropdown menus and the specified folder path can be read. EXPECTED RESULT See all relevant text of dropdown menus and folder path A scrolling mechanism (also for the specified folder path) or line wraping should be implemented. SOFTWARE/OS VERSIONS Android: LineageOS 17 ADDITIONAL INFORMATION Elisa version is 21.07.70, installed from f-droid. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435190] plasmashell crash on Wayland when opening Thunderbird blog entry
https://bugs.kde.org/show_bug.cgi?id=435190 pyro4h...@gmail.com changed: What|Removed |Added Version|5.21.4 |5.24.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435190] plasmashell crash on Wayland when opening Thunderbird blog entry
https://bugs.kde.org/show_bug.cgi?id=435190 pyro4h...@gmail.com changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #8 from pyro4h...@gmail.com --- Plasmashell still crashes for me on Arch Linux with the 5.24 update, when opening the earlier mentioned blogpost. It also crashed hard on a random Signal-desktop notification and even crashed instantly when restarting with 'kstart5 plasmashell' -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422336] kmail: the access and reading of the received messages is often very slow
https://bugs.kde.org/show_bug.cgi?id=422336 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416704] Port digiKam to Qt6 and KF6 API.
https://bugs.kde.org/show_bug.cgi?id=416704 --- Comment #149 from caulier.gil...@gmail.com --- Git commit 273229de47a4724ae51ce3c2268ac96c1b637b4b by Gilles Caulier. Committed on 11/02/2022 at 07:07. Pushed by cgilles into branch 'gsoc21-qt6-port'. Qt6 port++ M +1-1core/dplugins/generic/webservices/inaturalist/inatwindow.cpp M +2-2core/dplugins/generic/webservices/mediawiki/mediawikiwidget.cpp M +4-2core/dplugins/generic/webservices/piwigo/piwigologindlg.h M +1-2core/dplugins/generic/webservices/piwigo/piwigotalker.h M +1-2core/dplugins/generic/webservices/piwigo/piwigowindow.h https://invent.kde.org/graphics/digikam/commit/273229de47a4724ae51ce3c2268ac96c1b637b4b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416704] Port digiKam to Qt6 and KF6 API.
https://bugs.kde.org/show_bug.cgi?id=416704 --- Comment #148 from caulier.gil...@gmail.com --- It still 3 plugins which d o not compile yet : - expoblending (QtConcurrent::run problems with volatile args) - flickr (O2 API port required) - twitter (O2 API port required) Gilles -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 449991] New: On Wayland session, Bookmarks menu (BookMan II) opens on the other side of the window, then it should
https://bugs.kde.org/show_bug.cgi?id=449991 Bug ID: 449991 Summary: On Wayland session, Bookmarks menu (BookMan II) opens on the other side of the window, then it should Product: krusader Version: 2.7.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: ond...@krsko.sk CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 146568 --> https://bugs.kde.org/attachment.cgi?id=146568&action=edit I clicked on the right panel's BookMan icon, menu appears on the left side. SUMMARY On Wayland session, Bookmarks menu (BookMan II) opens on the other side of the window, then it should. STEPS TO REPRODUCE 0. Use Wayland session 1. click on BookMan II icon or press Ctrl-D 2. Bookmarks are shown on the other side OBSERVED RESULT - Bookmarks are shown on the other side EXPECTED RESULT - Bookmarks should be shown next to the icon SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-28-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-11370H @ 3.30GHz Memory: 31,1 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416704] Port digiKam to Qt6 and KF6 API.
https://bugs.kde.org/show_bug.cgi?id=416704 --- Comment #147 from caulier.gil...@gmail.com --- Git commit 55cdf0399ed6bf12e4f2aad19725824143b0a429 by Gilles Caulier. Committed on 11/02/2022 at 07:04. Pushed by cgilles into branch 'gsoc21-qt6-port'. Qt6 port++ M +2-2core/dplugins/generic/webservices/smugmug/smugwindow.cpp https://invent.kde.org/graphics/digikam/commit/55cdf0399ed6bf12e4f2aad19725824143b0a429 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 442309] KDE neon (Live from USB) changes clock under Windows 10
https://bugs.kde.org/show_bug.cgi?id=442309 --- Comment #4 from BOF --- Today I noticed a problem that I noticed before: When you run the live system and it changes the clock, the Windows 10 clock will auto update, but this takes some time and will also only work if you connected to the internet. The problem I had: I thought the clock was accurate (on Windows 10) and trusted it (because I didn't kept this bug in mind). I was working on the PC and wondered why today I was doing the same things, yet had so much more time than usual. This was followed by a huge _Oh sh!t_ moment when I took a look at my phone's clock. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449983] I cannot use the app because it keeps exiting it whenever I choose a different brush
https://bugs.kde.org/show_bug.cgi?id=449983 Alvin Wong changed: What|Removed |Added CC||al...@alvinhc.com --- Comment #3 from Alvin Wong --- (In reply to Tiar from comment #2) > 3. And please tell me why your Krita is installed in this location: > C:\Program > Files\WindowsApps\49800KritaProject.Krita_5.0.2.0_x64__n3kgb906j1zjg\krita - > how did you install it? That's the Microsoft Store package. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449987] krita suffer a fatal error and doesnt let me use the app anymore
https://bugs.kde.org/show_bug.cgi?id=449987 Alvin Wong changed: What|Removed |Added CC||al...@alvinhc.com --- Comment #1 from Alvin Wong --- Hi, other Steam applications probably has nothing to do with this. Reinstalling does not reset the settings of Krita so that wouldn't help. Do you remember where exactly did you move the resources (I assume you changed the resource location)? Please follow these steps to check the Krita configuration file: 1. Open Notepad 2. Inside Notepad, select "File -> Open" from the menu 3. In the filename, input "%localappdata%\kritarc" (without quotes) 4. Find the two lines starting with "ResourceCacheDbDirectory=" and "ResourceDirectory=" 5. Note these two lines and reply to this bug report with them so we can see what was happening. To fix your Krita configuration, you can just remove these two lines and save the file. This should cause Krita to use the default resource location. (Please close the file before launching Krita.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] Pointer speed resets after restart
https://bugs.kde.org/show_bug.cgi?id=435113 mayur.k.she...@gmail.com changed: What|Removed |Added CC||mayur.k.she...@gmail.com --- Comment #9 from mayur.k.she...@gmail.com --- Facing the same issue. Started after updating KDE Plasma to 5.24.0. Operating System: EndeavourOS KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-arch1-g14-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 9 5900HS with Radeon Graphics Memory: 15.1 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416704] Port digiKam to Qt6 and KF6 API.
https://bugs.kde.org/show_bug.cgi?id=416704 --- Comment #146 from caulier.gil...@gmail.com --- Git commit 2931793921419694fdab6aea7b17e26c0fe1c8da by Gilles Caulier. Committed on 11/02/2022 at 06:34. Pushed by cgilles into branch 'gsoc21-qt6-port'. Qt6 port++ M +20 -3core/CMakeLists.txt M +1-1core/dplugins/generic/tools/jalbum/CMakeLists.txt M +1-0core/dplugins/generic/tools/mediaserver/CMakeLists.txt M +5-2 core/dplugins/generic/tools/mediaserver/server/dmediaservermngr.cpp M +7-4core/dplugins/generic/tools/mjpegstream/mjpegserver_p.cpp M +6-3core/dplugins/generic/tools/mjpegstream/mjpegservermngr.cpp M +4-0core/dplugins/generic/tools/panorama/wizard/panopreviewpage.cpp M +7-2core/dplugins/generic/tools/panorama/wizard/panopreviewpage.h M +5-1core/dplugins/generic/view/glviewer/CMakeLists.txt M +8-1core/dplugins/generic/view/presentation/CMakeLists.txt https://invent.kde.org/graphics/digikam/commit/2931793921419694fdab6aea7b17e26c0fe1c8da -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449913] Text aliasing doesn't work properly/looks ugly in the overview
https://bugs.kde.org/show_bug.cgi?id=449913 Berengal changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Berengal --- Yes, I use wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429211] [X11] Digital clock/whole panel sometimes stops updating until there is user interaction with Plasma
https://bugs.kde.org/show_bug.cgi?id=429211 David Chmelik changed: What|Removed |Added CC||dchme...@gmail.com --- Comment #34 from David Chmelik --- It's NOT originally a Wayland bug but has been happening since KDE Plasma 4 started, and into Plasma 5. The panel used to stay frozen for as long as a half-hour or hour until I maybe killed plasmashell or KDE. Sometimes it worked to restart/fork plasmashell in a screen session in a xterm. Now it might still sort of work except your minimized system tray programs won't reappear there, only on taskbar (and some in background, have to kill them) which will no longer be in the order you moved programs to. This bug for the last 10 or 12+ years is why I initially switched back to KDE3.5 for a few major versions of Slackware until KDE3.5 stopped working, then tried to switch to TDE KDE3.5 fork and simpler (less power-hungry, even though I don't use many effects) desktop environments and still will try to switch. I still love KDE and will report bugs, but I haven't seen the panel freeze bug ever stop. Sometimes at the same time, some/most/all other things stop responding too. People suggested turn off indexing, which I did, which didn't improve situation. If I leave KDE on for days the panel is probably bound to stop responding. One thing that did seem to exacerbate it is if I start 10 or 15+ GUI programs immediately on starting KDE, which sometimes permanently slowed it down. If I start one program then another after a minute or two or after disc activity died down (though my OS is on SSD, /home is on HDD) and continue in that fashion, usually it doesn't slow down. The thing is, even if I start 15+ programs at once, it might just be 10% CPU resources of my 32 threads is even being used, so the parallel processing might need to improve (unless that situation is only a HDD access problem.) Hardware was asked about, and when this happened I'm using up to AMD Radeon 6900 XT. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 David Chmelik changed: What|Removed |Added CC||dchme...@gmail.com --- Comment #35 from David Chmelik --- It's NOT originally a Wayland bug but has been happening since KDE Plasma 4 started, and into Plasma 5. The panel used to stay frozen for as long as a half-hour or hour until I maybe killed plasmashell or KDE. Sometimes it worked to restart/fork plasmashell in a screen session in a xterm. Now it might still sort of work except your minimized system tray programs won't reappear there, only on taskbar (and some in background, have to kill them) which will no longer be in the order you moved programs to. This bug for the last 10 or 12+ years is why I initially switched back to KDE3.5 for a few major versions of Slackware until KDE3.5 stopped working, then tried to switch to TDE KDE3.5 fork and simpler (less power-hungry, even though I don't use many effects) desktop environments and still will try to switch. I still love KDE and will report bugs, but I haven't seen the panel freeze bug ever stop. Sometimes at the same time, some/most/all other things stop responding too. People suggested turn off indexing, which I did, which didn't improve situation. If I leave KDE on for days the panel is probably bound to stop responding. One thing that did seem to exacerbate it is if I start 10 or 15+ GUI programs immediately on starting KDE, which sometimes permanently slowed it down. If I start one program then another after a minute or two or after disc activity died down (though my OS is on SSD, /home is on HDD) and continue in that fashion, usually it doesn't slow down. The thing is, even if I start 15+ programs at once, it might just be 10% CPU resources of my 32 threads is even being used, so the parallel processing might need to improve (unless that situation is only a HDD access problem.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449990] New: Boot Splash screen settings
https://bugs.kde.org/show_bug.cgi?id=449990
Bug ID: 449990
Summary: Boot Splash screen settings
Product: systemsettings
Version: 5.24.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: marokanski.ka...@gmail.com
Target Milestone: ---
Application: systemsettings (5.24.0)
Qt Version: 5.15.3
Frameworks Version: 5.90.0
Operating System: Linux 5.15.0-18-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.0 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Chamging the boot Splash Screen theme when the System settings window hung up
and after a while it crashed=
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Системни настройки (systemsettings), signal: Segmentation fault
[New LWP 2829]
[New LWP 2830]
[New LWP 2832]
[New LWP 2836]
[New LWP 2843]
[New LWP 2844]
[New LWP 2861]
[New LWP 2862]
[New LWP 2878]
[New LWP 2880]
[New LWP 2888]
[New LWP 2889]
[New LWP 3906]
[New LWP 3907]
[New LWP 10859]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f5386396acf in __GI___poll (fds=0x7ffcea9c4af8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="onClicked",file="/usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml",fullname="/usr/share/kpackage/genericqml/org.kde.systemset".
-
(beware that frames may have been optimized out)
[Current thread is 1 (Thread 0x7f5381ad49c0 (LWP 2813))]
Thread 16 (Thread 0x7f531b0ff700 (LWP 10859)):
#0 0x7f5340f5852d in pa_fdsem_before_poll () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#1 0x7f5340f70387 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#2 0x7f5340fd4ba3 in pa_mainloop_dispatch () from
/lib/x86_64-linux-gnu/libpulse.so.0
#3 0x7f5340fd4ed2 in pa_mainloop_iterate () from
/lib/x86_64-linux-gnu/libpulse.so.0
#4 0x7f5340fd4f70 in pa_mainloop_run () from
/lib/x86_64-linux-gnu/libpulse.so.0
#5 0x7f5340fe311d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#6 0x7f5340f7f72c in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#7 0x7f5384da5609 in start_thread (arg=) at
pthread_create.c:477
#8 0x7f53863a3263 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 15 (Thread 0x7f5361222700 (LWP 3907)):
#0 __GI___libc_read (nbytes=16, buf=0x7f5361221b10, fd=36) at
../sysdeps/unix/sysv/linux/read.c:26
#1 __GI___libc_read (fd=36, buf=0x7f5361221b10, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2 0x7f538442fb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f53843e6ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7f53843e7312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7f53843e76f3 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x7f53401c5f8a in ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
#7 0x7f5384410ad1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7f5384da5609 in start_thread (arg=) at
pthread_create.c:477
#9 0x7f53863a3263 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 14 (Thread 0x7f535219a700 (LWP 3906)):
#0 0x7f53844344dd in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x7f53843e748e in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f53843e74f1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f5384410ad1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7f5384da5609 in start_thread (arg=) at
pthread_create.c:477
#5 0x7f53863a3263 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 13 (Thread 0x7f5341d47700 (LWP 2889)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x555eacbddaf0) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x555eacbddaa0,
cond=0x555eacbddac8) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x555eacbddac8, mutex=0x555eacbddaa0) at
pthread_cond_wait.c:647
#3 0x7f536e4385eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x7f536e4381eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5 0x7f5384da5609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f53863a3263 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 12 (Thread 0x7f5342598700 (LWP 2888)):
#0 futex_wait_cancelable
[kdemultimedia] [Bug 444064] ffmpegthumbs causes Dolphin to "hang" when viewing properties / details of video file on network share (CIFS/SMB)
https://bugs.kde.org/show_bug.cgi?id=444064 flan_suse changed: What|Removed |Added Version|unspecified |21.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 444064] ffmpegthumbs causes Dolphin to "hang" when viewing properties / details of video file on network share (CIFS/SMB)
https://bugs.kde.org/show_bug.cgi?id=444064 --- Comment #3 from flan_suse --- UPDATE: Removing the package "ffmpegthumbs" fixes the issue, but I don't consider this "resolved", since it means I lose out on video thumbnail previews in Dolphin. This is why I believe the underlying cause has to do with ffmpegthumbs + network folder. -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 444064] ffmpegthumbs causes Dolphin to "hang" when viewing properties / details of video file on network share (CIFS/SMB)
https://bugs.kde.org/show_bug.cgi?id=444064 --- Comment #2 from flan_suse --- This continues to happen with an updated system: Operating System: Manjaro Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics The issue is as described in the bug report. :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449989] New: Overview effect shows several instances of application if it is placed between displays
https://bugs.kde.org/show_bug.cgi?id=449989 Bug ID: 449989 Summary: Overview effect shows several instances of application if it is placed between displays Product: plasmashell Version: 5.23.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: indecisiveautoma...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Placing a window between displays (horizontally or vertically) will cause the window to appear on each display it appears between. For example, if it is placed between two displays horizontally, it will appear in the overview effect on both. If it is placed between four displays, it will appear four times. This occurs no matter the display orientation. This is purely a visual glitch, clicking on any of the instances of the application will focus it correctly. STEPS TO REPRODUCE 1. Place a window between two or more displays 2. Activate the Overview effect OBSERVED RESULT The window appears on the Overview effect for all displays that it overlaps. EXPECTED RESULT Overview effect only appears on one display, perhaps the display it was most recently focused on, or the display that contains most of the window? But I'm not sure how that would work in the case of a setup with vertical and horizontal displays. I'm not sure what the most intuitive solution would be here, apologies. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.8-arch1-1 (64bit) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Only tested on Wayland, unsure if this affects X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411662] plasmashell segmentation fault in QV4::CompiledData::CompilationUnit::destroy() after configuring the task manager to set the Show tooltips to off in Plasma 5.16.4 on Waylan
https://bugs.kde.org/show_bug.cgi?id=411662 --- Comment #6 from Matt Fagnani --- (In reply to Nate Graham from comment #3) > Can't reproduce with current git master. Can anyone who was affected check > again with at least Plasma 5.23? Git master or the Plasma 5.24 beta > (released tomorrow) would be even better. :) I set Show tooltips to off and on from Configure Task Manager several times in a Fedora 35 KDE Plasma installation with Plasma 5.23.5, KF 5.90.0, Qt 5.15.2. Plasmashell didn't crash. I didn't get emails for comments 3-4. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 447112] Very low framerate (fps) in kamoso
https://bugs.kde.org/show_bug.cgi?id=447112 Celeste changed: What|Removed |Added CC||coelacant...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438255] Taskbar panel missing (wayland session)
https://bugs.kde.org/show_bug.cgi?id=438255 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 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 441234] [Wayland] Moving panel objects causes Plasma to crash in QGuiApplicationPrivate::createPlatformIntegration()
https://bugs.kde.org/show_bug.cgi?id=441234 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #7 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 398396] Preappearance of larger submenu if switching from smaller submenu into larger one in Kicker on Wayland
https://bugs.kde.org/show_bug.cgi?id=398396 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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 413638] Wayland session with GDM is broken
https://bugs.kde.org/show_bug.cgi?id=413638 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 391647] Titlebar application menu crashes on wayland
https://bugs.kde.org/show_bug.cgi?id=391647 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 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 411662] plasmashell segmentation fault in QV4::CompiledData::CompilationUnit::destroy() after configuring the task manager to set the Show tooltips to off in Plasma 5.16.4 on Waylan
https://bugs.kde.org/show_bug.cgi?id=411662 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[systemsettings] [Bug 447764] Configure Firewall crashed while viewing connections
https://bugs.kde.org/show_bug.cgi?id=447764 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447617] Add option to allow .desktop files to be seen with their Desktop Entry Name in any folder
https://bugs.kde.org/show_bug.cgi?id=447617 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445245] Kickoff takes too long to open
https://bugs.kde.org/show_bug.cgi?id=445245 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-attica] [Bug 447279] System Settings crashes when searching for themes gets interrupted
https://bugs.kde.org/show_bug.cgi?id=447279 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- 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 446053] Several times switch of user session type between wayland and x11 leads to crash of plasmashell
https://bugs.kde.org/show_bug.cgi?id=446053 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445310] Kickoff ignores hover events generated by a stylus if it's opened by touch for the first time
https://bugs.kde.org/show_bug.cgi?id=445310 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 438688] Add Widgets sidebar pushes virtual keyboard to the right in Wayland
https://bugs.kde.org/show_bug.cgi?id=438688 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442078] Wayland session crash when clicking icon in taskbar
https://bugs.kde.org/show_bug.cgi?id=442078 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #11 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 441365] Plasma crashed on Wayland when I tried to remove an empty entry from Clipboard applet by clicking on "Remove from history" button repeatedly
https://bugs.kde.org/show_bug.cgi?id=441365 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[plasmashell] [Bug 441440] [Wayland] plasmashell high CPU usage
https://bugs.kde.org/show_bug.cgi?id=441440 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME 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.
[plasmashell] [Bug 435190] plasmashell crash on Wayland when opening Thunderbird blog entry
https://bugs.kde.org/show_bug.cgi?id=435190 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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 435220] Cannot paste text copied from firefox outside firefox in wayland session
https://bugs.kde.org/show_bug.cgi?id=435220 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #13 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.
[kwin] [Bug 436022] kwin_wayland crashes when mounting an external USD harddrive
https://bugs.kde.org/show_bug.cgi?id=436022 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #15 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 418677] Plasma with Wayland crashes in PlasmaQuick::Dialog::Dialog(QQuickItem*) trying to change compositing settings
https://bugs.kde.org/show_bug.cgi?id=418677 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[kstars] [Bug 449221] Current traking is poor. Two weeks ago it was perfect
https://bugs.kde.org/show_bug.cgi?id=449221 --- 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.
[plasmashell] [Bug 389599] global menu crashes in wayland
https://bugs.kde.org/show_bug.cgi?id=389599 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 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.
[krita] [Bug 449000] Mouse wheel rotates canvas and stops working after importing image
https://bugs.kde.org/show_bug.cgi?id=449000 --- 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.
[plasma-systemmonitor] [Bug 448580] show wrong character
https://bugs.kde.org/show_bug.cgi?id=448580 --- 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.
[plasmashell] [Bug 446075] several crashes
https://bugs.kde.org/show_bug.cgi?id=446075 --- Comment #13 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448518] Lattedock crashes when starting other programs
https://bugs.kde.org/show_bug.cgi?id=448518 --- 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.
[kwin] [Bug 419333] [Wayland] Titlebar of a window turns black
https://bugs.kde.org/show_bug.cgi?id=419333 --- Comment #6 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.
[frameworks-ktexteditor] [Bug 365903] Search does not highlight search string occurrences that are part of a word
https://bugs.kde.org/show_bug.cgi?id=365903 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 hugh changed: What|Removed |Added OS|Other |Linux Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] New: No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 Bug ID: 449988 Summary: No Border Window Action Toggle Continually Shrinks the Window Size Product: kwin Version: 5.24.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: hugh.ga...@tutamail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open a window in Plasma 5.24 (X11) 2. Toggle No Border window action 3. Togger No Border again 4. Togger No Border again 5. Togger No Border again OBSERVED RESULT The window will repeatedly shrink with each toggle. When the titlebar and border is toggled off the window contents are not repainted in the existing window area. The titlebar is simply removed and new window size now becomes the existing window area. The window shrinks by the size of the titlebar and border each toggle. EXPECTED RESULT Prior to 5.24 toggling the no border setting did not alter the window size. It remained exactly the same size. SOFTWARE/OS VERSIONS Linux Distro : Arch KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445251] Ever since upgrading to 5.23, wobbly windows, alt-tab preview, clicking on grouped icons to show them all, (and other stuff) crash and stop working
https://bugs.kde.org/show_bug.cgi?id=445251 eliyahushap...@gmail.com changed: What|Removed |Added Summary|Every since upgrading to|Ever since upgrading to |5.23, wobbly windows, |5.23, wobbly windows, |alt-tab preview, clicking |alt-tab preview, clicking |on grouped icons to show|on grouped icons to show |them all, (and other stuff) |them all, (and other stuff) |crash and stop working |crash and stop working -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 449968] [Feature Request] Dynamic / Virtual Albums
https://bugs.kde.org/show_bug.cgi?id=449968 Ty Mayn changed: What|Removed |Added CC||tyrus.m...@gmail.com --- Comment #5 from Ty Mayn --- I see Dynamic/Virtual Album as a way of improving digikam use . Such a virtual album should be able to be loaded into the MainView window where thumbnails act as the symlinks for actions such as copy or hand off to modules like Slideshow The Dynamic album is a persistent collection that can be named and saved without creating moving or duplicating files into any OS directory. If the tagging engine is used to name and persist the collection , then the tagging should be hidden from the standard TagManager and filter tools. Dynamic album is disposable so that deletion does not delete the files that the collection represents NO file should have to be moved to a new folder on the OS in order to join a collection NO file should have to be duplicated/copy/pastes to be processed into some location to join a persistent collection Dynamic Album acts as in Input to load into any digikam module: Slideshow,Presentation,Mass Tagging, or FilterActions Dynamic Album acts as an Output so that it can be converted to a plain text list of Path+Filename (obviously only useful on a workstation which has that file/folder pattern) Since each major OS has symlinks there should be a way to export Dynamic Album to a collections of symlinks . Declare a buffer folder into which the Dynamic album symlinks can be placed, once there then the user can move these symlinks, in part or in whole, anywhere on the filesystem (without carrying the baggage of the files) Sorting: Dynamic albums should have a tool for arbitrary manual sorting of the collection. The sort engine should be able to begin with a typical sort from the OS (date etc) Wish that the manual sorting could be a visual drag/drop among the thumbnails in the MainViewer Look at the primitive way to sort files for slideshow by win10 explorer by Prefix Renaming: http://wordpress.jmcgowan.com/wp/how-to-control-the-order-of-slides-in-a-slideshow-on-windows-10/ These thoughts are from a nonprogrammer user perspective , so thanks to any programmer who arbitrates the needs and the places in code to be affected. Ty Mayn -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 448072] Context Menu is overlapping text with shortcuts in RTL mode and Arabic Interface
https://bugs.kde.org/show_bug.cgi?id=448072 Safa Alfulaij changed: What|Removed |Added CC||safa1996alful...@gmail.com Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Safa Alfulaij --- Upstream bug: https://bugreports.qt.io/browse/QTBUG-43478 Please add more information if you can to reopen the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449987] New: krita suffer a fatal error and doesnt let me use the app anymore
https://bugs.kde.org/show_bug.cgi?id=449987 Bug ID: 449987 Summary: krita suffer a fatal error and doesnt let me use the app anymore Product: krita Version: 5.0.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: leonardolara...@gmail.com Target Milestone: --- Created attachment 146567 --> https://bugs.kde.org/attachment.cgi?id=146567&action=edit error message I was testing the pen pressure on the tablet and the app, and I was also moving where the resources were stored, I passed them to data (they were on windows) I have krita on steam and I was using another steam application (I don't know if this is relevant, the app was dead by daylight), once I finished playing, I wanted to enter the app but an error message appeared, I managed to enter the app using a file I was working on, uninstall the app and reinstall it and when I wanted to enter by both ways I could not. i tried to install krita from the website and the same message appear STEPS TO REPRODUCE 1. open another steam app 2. open krita (steam version) 3. move the storage and pen pressure 4. close both apps 5. done, the error will appear, now you can only enter the app using an old file 6. uninstall and reinstall krita 7. i can no longer use or enter krita OBSERVED RESULT error message EXPECTED RESULT be able to still using krita SOFTWARE/OS VERSIONS Windows: 5.0.2 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.
[frameworks-kirigami] [Bug 449884] Text looks cut off and buggy when scrolling using trackpad or mouse
https://bugs.kde.org/show_bug.cgi?id=449884 --- Comment #11 from Noah Davis --- The ideal fix would be to fix the text elements in Qt so that they don't glitch out when given fractional positions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 449884] Text looks cut off and buggy when scrolling using trackpad or mouse
https://bugs.kde.org/show_bug.cgi?id=449884 --- Comment #10 from Noah Davis --- Actually, isn't there already a solution built into Flickable? Set `pixelAligned: true`. That's technically the correct thing to do. It's not going to work that well with fractional scale factors though. Even if we made a built-in workaround in Kirigami WheelHandler, I'm not sure we'd be able to do much about fractional scale factors. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 449968] [Feature Request] Dynamic / Virtual Albums
https://bugs.kde.org/show_bug.cgi?id=449968 --- Comment #4 from johan.kemn...@gmail.com --- That's true - seems the way to maintain that would be to just have another node in the main view: - Folders --> physical directories - Albums --> collections of images that could be anywhere - Tags - Labels ... that would allow users to follow whichever workflow they're more comfortable with. E.g.: if you like putting your files into different directories by date, location, whatever, you might have: Trip to Someplace\Week1, ..\Week2, ..\ThisPlace, ..\ThatThing etc. Maybe you want a view that contains images from all of those subfolders. "Include Album Sub-Tree" gives you ALL of the subfolder images; depending on how you organize may or may not be what you want in the "Album" (the way I think of an album, anyway). You can get there with tagging / custom search, just feels less intuitive to me. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)
https://bugs.kde.org/show_bug.cgi?id=449774 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #28 from Nate Graham --- I'm sorry we wouldn't help you. :( -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449966] [Feature Request] cargo clippy code analysis
https://bugs.kde.org/show_bug.cgi?id=449966 --- Comment #4 from infrandomn...@gmail.com --- (In reply to Christoph Cullmann from comment #3) > Sounds like some good fit, yes. > > Are you interested in contributing a patch for this? > > This is handled in kate.git/addons/project/tools Sure ! I'd be glad to try and do this -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 449884] Text looks cut off and buggy when scrolling using trackpad or mouse
https://bugs.kde.org/show_bug.cgi?id=449884 --- Comment #9 from Noah Davis --- We should probably round the contentX and contentY position changes in Kirigami WheelHandler. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443060] Feature request: sequential screenshots (configurable)
https://bugs.kde.org/show_bug.cgi?id=443060 --- Comment #13 from John B --- Just as I submitted the above comment I realized I needed to edit it. Doh! 1. I've been going back and forth between this bug and the other one and forgot to take out the bit about automatic saving. Having a checkbox right there in the main window might be a little more intuitive, but I did find that setting in the configuration dialogs. So, thanks for that, talk about fast turnaround time! :) 2. It occurs to me that "I definitely feel like this is a different issue that should also be addressed" is kinda ambiguously-worded. What I meant was, I definitely feel like _this_ issue, bug #443060, stands on its own and should be addressed as such...while acknowledging that I _personally_ may not need this bug if the feature request from #449986 gets implemented. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443060] Feature request: sequential screenshots (configurable)
https://bugs.kde.org/show_bug.cgi?id=443060 John B changed: What|Removed |Added CC||john+kde_...@daaave.org --- Comment #12 from John B --- I'd like to request this feature as well; there are workarounds (of varying effectiveness), but it seems like something that could really benefit from just officially being supported. For example, the comment before this suggests an interesting workaround that _almost_ does the trick, but not quite. I want to capture a particular window with multiple sequential screenshots, but when I use this workaround the following happens: 1. I set the capture mode to "Active Window", activate the window, and hit PrtScr. Spectacle successfully captures the window. 2. I press Return (after manually navigating the active button around to the "Save" button, which is a bit non-intuitive but perhaps not a deal-breaker) and Spectacle successfully saves the screenshot. So far, so good. 3. PLOT TWIST: When I saved the screenshot, Spectacle itself became the active window; when I hit PrtScr again, I get a picture of the Spectacle window. My best thought for a UI to enable this while creating the smallest amount of new UI possible (I know we're in Apple mode here 'cause the window doesn't even have a proper Close/Quit button :P) is to add a checkbox below the current ones (below "Quit after manual Save or Copy" in my version) that says something like "Immediately save to default location on capture". Although, I suppose at that point you've still got to deal with having Spectacle become the active window when you click in it or press PrtScr. As an aside, I've created a feature request to capture a specific window by its properties; I definitely feel like this is a different issue that should also be addressed, but adding that functionality should solve for my particular use case. Here's the link, in case anybody else is interested: https://bugs.kde.org/show_bug.cgi?id=449986 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 449986] New: New capture mode: Window by properties
https://bugs.kde.org/show_bug.cgi?id=449986 Bug ID: 449986 Summary: New capture mode: Window by properties Product: Spectacle Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: john+kde_...@daaave.org CC: k...@david-redondo.de Target Milestone: --- Created attachment 146566 --> https://bugs.kde.org/attachment.cgi?id=146566&action=edit Hall of mirrors effect when spamming the PrtScr button It would be nice to be able to screenshot a specific window by its properties, so that you can target a particular window even if it's not active or under the cursor. One particular use case that would benefit from this is taking rapid, sequential screenshots as described in https://bugs.kde.org/show_bug.cgi?id=443060 I'm not sure what the best UI/workflow for this would be, but I'm envisioning something like: 1. Select "Window (by properties)" from the "Area" drop-down. 2. When you select that option, a picker like the one you get in the "Window Rules" part of System Settings when you click "Detect Window Properties" shows up and you click the window you want. 3. A dialog (again, similar to what you get when setting up window rules in System Settings) comes up that lets you pick which properties you want to apply to the filter. 4. When you click "Take a New Screenshot", Spectacle will screenshot the first window it finds that matches the properties. 5. The window properties will be saved for subsequent screenshots, using the same logic Spectacle currently uses to save the rectangular region information. There seems to be some reference to this at the end of the comment history for https://bugs.kde.org/show_bug.cgi?id=411290 but I'm not sure enough to call this a duplicate (plus, that bug's main focus is something else anyway). In other news, I just discovered the "Autosave the image to the default location" setting, but even with that enabled I can't just set "Active Window" and spam the PrtScr button 'cause as soon as I press it, Spectacle raises itself and then starts taking screenshots of itself instead. On a side note, I've included a screenshot (taken by Spectacle) that shows what happens when you do this with a delay configured, for the amusement of the peanut gallery. Although, you can also see the effect of having a little bit more transparent border added on each pass. I did rename the file because the fractal filenames were getting a little out of control (you'll see what I mean along the bottom). I'm honestly not sure if this is a bug or just Spectacle's doing what it's told and my not expecting the result I got from the instructions I gave. :) SOFTWARE/OS VERSIONS OS Version: Kubuntu 20.04 (all packages are the stock versions that come with this Kubuntu release) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449983] I cannot use the app because it keeps exiting it whenever I choose a different brush
https://bugs.kde.org/show_bug.cgi?id=449983 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Tiar --- Hi @Dylan, you were supposed to add the log file to bug 449977, not create a new bug report... please next time make sure you add your comment and your log files to this place: https://bugs.kde.org/show_bug.cgi?id=449983 (best way: just visit that link and then add comments and files - there is a little "Add an attachment" button below bug report information). 1. Can you please tell me whether Krita only always crash when you create the canvas? 2. And could you please also attach the file that you can find if you put this text into the file browser: %LOCALAPPDATA%\kritacrash.log 3. And please tell me why your Krita is installed in this location: C:\Program Files\WindowsApps\49800KritaProject.Krita_5.0.2.0_x64__n3kgb906j1zjg\krita - how did you install it? 4. You can try going (without creating an image) to Settings -> Configure Krita -> Display -> and change the Renderer from ANGLE/DirectX to OpenGL or the other way around, close and reopen Krita and see if it works then. If not, disable Canvas Acceleration and then close and open Krita and check if it works. And tell me if it helped or not. 5. You can reinstall krita, but it won't help in this case. You could reset the configuration though. Instruction: https://docs.krita.org/en/KritaFAQ.html?highlight=configuration#resetting-krita-configuration - Make sure to remove the 'kritadisplayrc' file as well. Remember that it will reset your configuration to default values. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 416848] Add 'paste from clipboard' to import image to view
https://bugs.kde.org/show_bug.cgi?id=416848 DeKay changed: What|Removed |Added CC||dekaymail+...@gmail.com --- Comment #2 from DeKay --- Another vote for this type of feature. irFanView on Windows allows this. Control-V to paste an image previously copied to the clipboard into an empty window and you're done. From there you can zoom the image, edit it, save it, etc. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 449985] Drop Shadows on the lock screen are inconsistent between light and dark mode.
https://bugs.kde.org/show_bug.cgi?id=449985 hellosway changed: What|Removed |Added CC||hellos...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 449985] Drop Shadows on the lock screen are inconsistent between light and dark mode.
https://bugs.kde.org/show_bug.cgi?id=449985 --- Comment #2 from hellosway --- Created attachment 146565 --> https://bugs.kde.org/attachment.cgi?id=146565&action=edit light mode screenshot. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 449985] Drop Shadows on the lock screen are inconsistent between light and dark mode.
https://bugs.kde.org/show_bug.cgi?id=449985 --- Comment #1 from hellosway --- Created attachment 146564 --> https://bugs.kde.org/attachment.cgi?id=146564&action=edit dark mode screenshot. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449983] I cannot use the app because it keeps exiting it whenever I choose a different brush
https://bugs.kde.org/show_bug.cgi?id=449983 --- Comment #1 from Tiar --- *** Bug 449977 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 449985] New: Drop Shadows on the lock screen are inconsistent between light and dark mode.
https://bugs.kde.org/show_bug.cgi?id=449985 Bug ID: 449985 Summary: Drop Shadows on the lock screen are inconsistent between light and dark mode. Product: Breeze Version: 5.24.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hellos...@protonmail.com Target Milestone: --- Drop Shadows on the lock screen are inconsistent between light and dark mode. STEPS TO REPRODUCE 1. Open systemsettings and click "dark". 2. Lock your screen. 3. Wait until password prompt disappears. 4. Observer the drop shadow on date and time text 5. Unlock screen and open systemsettings. Then click "light". 6. Lock your screen. 7. Wait until password prompt disappears. 8. Observer the drop shadow on date and time text again OBSERVED RESULT The drop shadow in the dark theme is much stronger EXPECTED RESULT Both drop shadows are the same SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Occurs with Xorg and Wayland. I am using the default "Breeze" theme. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449977] It keeps closing out of the app whenever I choose a different brush, and a couple days ago it wasn’t saving any of the files
https://bugs.kde.org/show_bug.cgi?id=449977 Tiar changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #3 from Tiar --- *** This bug has been marked as a duplicate of bug 449983 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446461] Latte Dock layouts appearing all at once in overview
https://bugs.kde.org/show_bug.cgi?id=446461 Tomas changed: What|Removed |Added CC||eurog...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446460] Plasma Overview shows all panels and docks even when they are not in the current activity
https://bugs.kde.org/show_bug.cgi?id=446460 Tomas changed: What|Removed |Added CC||eurog...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449977] It keeps closing out of the app whenever I choose a different brush, and a couple days ago it wasn’t saving any of the files
https://bugs.kde.org/show_bug.cgi?id=449977 --- Comment #2 from Dylan --- Isn’t there just a way where I could just restart Krita? I do t get why this is happening because I have no tabs open and plenty storage left Sent from my iPhone > On Feb 10, 2022, at 3:44 PM, Tiar wrote: > > https://bugs.kde.org/show_bug.cgi?id=449977 > > Tiar changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > CC||tamtamy.tym...@gmail.com > > --- Comment #1 from Tiar --- > Please attach the content of Help -> Show Krita log for bug reports, and Help > -> Show system information for bug reports. (You'll need to save them both to > file, then attach one file after the other to the bug report). > > Please also say whether you downloaded Krita from the website or did you get > it > from any of the stores (and if from the store, which one was it). > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 449984] New: Plasma 5.24.0 NetworkManager not working with kdewallet
https://bugs.kde.org/show_bug.cgi?id=449984 Bug ID: 449984 Summary: Plasma 5.24.0 NetworkManager not working with kdewallet Product: plasma-nm Version: 5.24.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: tniag...@gmail.com Target Milestone: --- SUMMARY Since an upgrade to 5.24 network connections that use secrets (WiFi, VPN) will not connect. STEPS TO REPRODUCE Attempt to connect to a WiFi or VPN connection. OBSERVED RESULT The connection stops with "needs authorisation" showing in the applet. They connection never works. EXPECTED RESULT Connection succeeds. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.24 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Kernel 5.13.0-28 Wayland ADDITIONAL INFORMATION Affects both 'applet' and 'editor'. I could get a WiFi up using "nmcli --ask connection up ", which prompted for the password. That doesn't work for the VPN connections. SystemSettings/Connections don't show the secrets either, just empty fields instead of the circle characters. Maybe 30sec later, it produces Notifications: "Failed to get secrets for " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449983] New: I cannot use the app because it keeps exiting it whenever I choose a different brush
https://bugs.kde.org/show_bug.cgi?id=449983 Bug ID: 449983 Summary: I cannot use the app because it keeps exiting it whenever I choose a different brush Product: krita Version: 5.0.2 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: dylanthe...@gmail.com Target Milestone: --- Created attachment 146563 --> https://bugs.kde.org/attachment.cgi?id=146563&action=edit This is just showing my log in info to krita of me trying to use the app, but it keeps logging me off of it SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: surface pro 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)
https://bugs.kde.org/show_bug.cgi?id=449774 --- Comment #27 from Katie Marie Nelson --- Look I'm not going to bother! I explained to you in vivid detail and even took pictures at your request. I also provided additional clues to what else might have caused the issue. Delete the issue or do what ever. On 2/10/22 11:15, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=449774 > > --- Comment #26 from Nate Graham --- > I am still having a hard time understanding the issue. Can you please answer > one question at a time and not also provide a ton of other information or a > narration of what you're doing? And please don't quote every reply as it > causes > each comment to be huge. > > Can you please write a simple step-by-step description of how you can > reproduce > the problem? No need to start all the way back with "I installed such-and-such > OS"; that part is implicit. :) Just start with what app you launched. > -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449947] Single click to open files/folders does not work using MATE desktop
https://bugs.kde.org/show_bug.cgi?id=449947 --- Comment #3 from Nicolas Fella --- Dolphin on Mate reading settings from another desktop that happens to be installed would be quite odd, and most Mate users don't have Plasma installed anyway. The single/double click behavior in Dolphin is controlled by a flag in the Qt PlatformTheme. The platformtheme provided by Plasma reads the setting set by systemsettings. What happens on Mate depends on what platformtheme is used there -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443971] Present windows effect in desktop grid is missing its animations
https://bugs.kde.org/show_bug.cgi?id=443971 --- Comment #15 from bastimeyer...@gmail.com --- The current diff from MR 1998 does not fix the issue: https://invent.kde.org/plasma/kwin/-/commit/af185b23f77587d437dad381a01b4d75a7e7c422.patch I've already mentioned that I tried fixing it, and this was one of my attempts. What this does fix is the zoom-out (open grid) and move-windows animation, but the zoom-in (close grid) animation is still broken which is probably caused by the new callback of the `finish()` method, as I described earlier. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449978] Touchpad settings cannot be changed
https://bugs.kde.org/show_bug.cgi?id=449978 --- Comment #6 from Nicolas Fella --- Thank you, it helped me check what I wanted to check. Let's continue the conversation in https://bugs.kde.org/show_bug.cgi?id=449843 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 414533] cannot install obs studio via Spectacle
https://bugs.kde.org/show_bug.cgi?id=414533 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449982] New: Gradient effect applied to left and right window borders
https://bugs.kde.org/show_bug.cgi?id=449982 Bug ID: 449982 Summary: Gradient effect applied to left and right window borders Product: kwin Version: 5.24.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: scribe.awo...@gmail.com Target Milestone: --- Created attachment 146562 --> https://bugs.kde.org/attachment.cgi?id=146562&action=edit A screenshot of the graphical bug on display. SUMMARY When using many Aurorae themes, a vertical gradient is applied to the left and right window borders. This is most apparent on VinceLiuice's Graphite theme and its derivatives due to the thick, contrasting outlines it uses, though this is also present in other themes, like eliverlara's Nordic theme. Notably this seems to happen in themes where the bottom corners have a different shape than the top corners. Some observations across different themes: - When the border size is set to normal or larger, both the left and right borders are affected on Graphite and Graphite-Round - When the size is set to Tiny, neither side border is affected on the round variations on Graphite, but the right border is still affected on normal Graphite STEPS TO REPRODUCE 1. Apply certain Aurorae themes (most apparent with VinceLiuice's Graphite themes, but also subtly present on eliverlara's Nordic theme) 2. Open Qt program. OBSERVED RESULT The side window decorations have a gradient effect applied to them EXPECTED RESULT The side window decorations should look identical to how they look in the .svg file. SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed 20220207 (available in About System) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Screen resolution is 1366x768. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443971] Present windows effect in desktop grid is missing its animations
https://bugs.kde.org/show_bug.cgi?id=443971 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #14 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/1998 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449976] Can't open okular document archive saved from a directory of images
https://bugs.kde.org/show_bug.cgi?id=449976 --- Comment #3 from dirtyice --- Oh yes, sorry, now that I re-read my original bugreport, I noticed that the wall of text is under observed result and the expected result comes logically after steps to reproduce, it's only physically after observed result, but that's not what I exactly had on mind when written the report. So TL;DR, my problem is that it can't load the file it created, everything else is additional information. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449976] Can't open okular document archive saved from a directory of images
https://bugs.kde.org/show_bug.cgi?id=449976 --- Comment #2 from dirtyice --- (In reply to Albert Astals Cid from comment #1) > I mean, you asked it to do that, so I'm not sure why you're suddently > surprised that the application did what you said. Hmm, what do you mean? We have two things going on. First I wanted to quit, and save the changes before I quit. Not necessarily a bug, it's just a bit weird that okular asks to reload the document, when it's going to quit right after it. But my main problem is that I can't load the document it saved at all. I didn't ask okular to create an unopenable file. > Anyhow, you defenitely triggered an unexpected path, sadly folders of images > is not something the code accounts for, my suggestion is that one shouldn't > be able to annotate when opening folders of images, just when opening > individual files. Couldn't it be made to work somehow? I mean, back when okular automatically saved annotations in a separate file into ~/.local/share/okular/docdata, this worked IIRC. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447705] Flickering in Wayland session when returning from standby
https://bugs.kde.org/show_bug.cgi?id=447705 Aleix Pol changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #9 from Aleix Pol --- I see this on dmesg, it could be related. [10956.771516] [drm] Fence fallback timer expired on ring sdma0 [10957.315506] [drm] Fence fallback timer expired on ring sdma0 [10957.827495] [drm] Fence fallback timer expired on ring sdma0 [10958.339484] [drm] Fence fallback timer expired on ring sdma0 [10958.851473] [drm] Fence fallback timer expired on ring sdma0 [10959.363464] [drm] Fence fallback timer expired on ring sdma0 [10959.540717] [drm] UVD initialized successfully. [10959.868009] OOM killer enabled. [10959.868014] Restarting tasks ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449951] Low framerate (35 fps) when display scale is set to 125% on Wayland
https://bugs.kde.org/show_bug.cgi?id=449951 Dave Oxley changed: What|Removed |Added CC||d...@daveoxley.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449981] New: Plasmashell crash, basically out of the blue
https://bugs.kde.org/show_bug.cgi?id=449981
Bug ID: 449981
Summary: Plasmashell crash, basically out of the blue
Product: plasmashell
Version: 5.24.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: nik.kaise...@googlemail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.24.0)
Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.16.5-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.0 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I had my VM up and running, but this very error happened before too, even
without doing anything. The only program open was Firefox then, and the second
time (this report) virt-manager. 5.24 seems a bit .. unstable.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fd0f1cfcb95 in std::__atomic_base::load
(__m=std::memory_order_relaxed, this=) at
/usr/include/c++/11/bits/atomic_base.h:481
#7 QAtomicOps::loadRelaxed (_q_value=...) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:239
#8 QBasicAtomicInteger::loadRelaxed (this=) at
/usr/include/qt5/QtCore/qbasicatomic.h:107
#9 QtPrivate::RefCount::isShared (this=) at
/usr/include/qt5/QtCore/qrefcount.h:101
#10 QVector::isDetached (this=0x55fb07c89930) at
/usr/include/qt5/QtCore/qvector.h:113
#11 QVector::detach (this=0x55fb07c89930) at
/usr/include/qt5/QtCore/qvector.h:399
#12 QVector::begin (this=0x55fb07c89930) at
/usr/include/qt5/QtCore/qvector.h:210
#13 QQuickWindowPrivate::queryPointerEventInstance
(this=this@entry=0x55fb07c89790, device=0x31,
eventType=eventType@entry=QEvent::None) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickwindow.cpp:2498
#14 0x7fd0f1cfcd14 in QQuickWindow::mouseGrabberItem (this=)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickwindow.cpp:1735
#15 0x7fd0f1cff49b in QQuickWindowPrivate::removeGrabber
(this=0x55fb08699540, grabber=grabber@entry=0x55fb04f45430,
mouse=mouse@entry=true, touch=touch@entry=true) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickwindow.cpp:1001
#16 0x7fd0f1cdf002 in QQuickItemPrivate::setEffectiveVisibleRecur
(this=0x55fb04fa2f00, newEffectiveVisible=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickitem.cpp:6067
#17 0x7fd0f1cdf037 in QQuickItemPrivate::setEffectiveVisibleRecur
(this=this@entry=0x55fb04c90150, newEffectiveVisible=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickitem.cpp:6072
#18 0x7fd0f1cdf153 in QQuickItemPrivate::setVisible (this=0x55fb04c90150,
visible=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickitem.cpp:5975
#19 0x7fd0f1cec59b in QQuickItem::qt_metacall
(this=this@entry=0x55fb04cf52e0, _c=_c@entry=QMetaObject::WriteProperty,
_id=11, _a=_a@entry=0x7ffc242b4c40) at .moc/moc_qquickitem.cpp:1048
#20 0x7fd0f24d18a6 in PlasmaQuick::AppletQuickItem::qt_metacall
(this=this@entry=0x55fb04cf52e0, _c=_c@entry=QMetaObject::WriteProperty,
_id=, _a=_a@entry=0x7ffc242b4c40) at
/usr/src/debug/plasma-framework-5.90.0-1.1.x86_64/build/src/plasmaquick/KF5PlasmaQuick_autogen/include/moc_appletquickitem.cpp:364
#21 0x7fd0e064fc76 in AppletInterface::qt_metacall (this=0x55fb04cf52e0,
_c=QMetaObject::WriteProperty, _id=, _a=0x7ffc242b4c40) at
/usr/src/debug/plasma-framework-5.90.0-1.1.x86_64/build/src/scriptengines/qml/plasma_appletscript_declarative_autogen/include/moc_appletinterface.cpp:850
#22 0x7fd0e065e226 in ContainmentInterface::qt_metacall
(this=0x55fb04cf52e0, _c=QMetaObject::WriteProperty, _id=,
_a=0x7ffc242b4c40) at
/usr/src/debug/plasma-framework-5.90.0-1.1.x86_64/build/src/scriptengines/qml/plasma_appletscript_declarative_autogen/include/moc_containmentinterface.cpp:453
#23 0x7fd0f17bce1f in QQmlPropertyData::writeProperty (flags=...,
value=, target=, this=) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:379
#24 QQmlPropertyPrivate::write (object=object@entry=0x55fb04cf52e0,
property=..., value=..., context=, flags=..., flags@entry=...)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/qml/qqmlproperty.cpp:1292
#25 0x7fd0f16e31f1 in QV4::QObjectWrapper::setProperty
(engine=0x55fb04c5ad60, object=0x55fb04cf52e0, property=0x7fd0a40a0ae8,
value=...) at /usr/include/qt5/QtCore/qflags.h:120
#26 0x7fd0f16e3a62 in QV4::QObjectWrapper::setQmlProperty (value=...,
revisionMode=QV4:
[plasmashell] [Bug 449918] plasma-workspace-5.24.0 sets Xft.dpi to 0 in Xresources
https://bugs.kde.org/show_bug.cgi?id=449918 he...@freedesk.net changed: What|Removed |Added CC||he...@freedesk.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449978] Touchpad settings cannot be changed
https://bugs.kde.org/show_bug.cgi?id=449978 --- Comment #5 from eoinlan...@gmail.com --- (In reply to Nicolas Fella from comment #2) > Could you please make a screenshot of the touchpad settings UI? Two screenshots added, one before and one after changing the "Inverted Scroll" setting. -- You are receiving this mail because: You are watching all bug changes.
