[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files
https://bugs.kde.org/show_bug.cgi?id=442010 --- Comment #11 from Kyle Devir --- It's not just Dolphin suffering from this. Apparently, Filelight also suffers the exact same issues... So, probably an issue in KDE Frameworks somehow... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442015] Screen looses content randomly, just black
https://bugs.kde.org/show_bug.cgi?id=442015 Simon Schmeisser changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Simon Schmeisser --- No mouse cursor (or anything for that matter) is visible on the build in screen. Mouse works just fine on external display I checked /sys/class/backlight/intel_backlight/actual_brightness but it doesn't change when the content disappears (and the screen is not pitch black) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442064] the `powermanagement` data engine calling the `UnInhibit` method with incorrect signature
https://bugs.kde.org/show_bug.cgi?id=442064 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1041 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435185] Add shortcuts and sliders for Fade and Scatter in Auto brush mode
https://bugs.kde.org/show_bug.cgi?id=435185 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com --- Comment #3 from tomtomtomreportin...@gmail.com --- https://invent.kde.org/graphics/krita/-/merge_requests/1037 Here's an MR with action shortcuts for Fade and Scatter. After this, sliders for Scatter would likely be simple but Fade sliders might be a bit tricky with their dual-value nature and how their values are baked into the brush definition. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442064] New: the `powermanagement` data engine calling the `UnInhibit` method with incorrect signature
https://bugs.kde.org/show_bug.cgi?id=442064 Bug ID: 442064 Summary: the `powermanagement` data engine calling the `UnInhibit` method with incorrect signature Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DataEngines Assignee: plasma-b...@kde.org Reporter: 7437...@gmail.com Target Milestone: 1.0 SUMMARY I noticed the Battery and Brightness applet always ends up in a confusing state after using its "Inhibit automatic sleep and screen locking" feature. I tracked it down to the `powermanagement` data engine calling the `UnInhibit` method with incorrect signature: - [when un-inhibit sleep](https://invent.kde.org/plasma/plasma-workspace/-/blob/master/dataengines/powermanagement/powermanagementjob.cpp#L107) - [when un-inhibit screen locking](https://invent.kde.org/plasma/plasma-workspace/-/blob/master/dataengines/powermanagement/powermanagementjob.cpp#L126) The correct signature should take an unsigned int: - [`org.freedesktop.PowerManagement.UnInhibit`](https://invent.kde.org/plasma/powerdevil/-/blob/master/daemon/org.freedesktop.PowerManagement.Inhibit.xml#L10) - [`org.freedesktop.ScreenSaver.UnInhibit`](https://invent.kde.org/plasma/powerdevil/-/blob/master/daemon/org.freedesktop.ScreenSaver.xml#L30) STEPS TO REPRODUCE 1. Make sure nothing is inhibiting ``` qdbus --literal org.kde.Solid.PowerManagement.PolicyAgent \ /org/kde/Solid/PowerManagement/PolicyAgent \ org.kde.Solid.PowerManagement.PolicyAgent.ListInhibitions ``` 2. Check the "Inhibit automatic sleep and screen locking" box in the Battery and Brightness applet 3. Wait 5 seconds for the inhibition to engage and verify the list of inhibitions. There should be 2 items. 4. Uncheck the "Inhibit automatic sleep and screen locking" box in the Battery and Brightness applet OBSERVED RESULT Inhibitions are **not** released. And if you toggle the checkbox multiple times, there will be many duplicated items in the list. If you run ``` dbus-monitor "destination=org.freedesktop.PowerManagement.Inhibit" "sender=org.freedesktop.PowerManagement.Inhibit" ``` during step 4, the error reply will be captured (something similar to the following): ``` error time=1630903644.048537 sender=:1.414 -> destination=:1.57 error_name=org.freedesktop.DBus.Error.UnknownMethod reply_serial=7813 string "No such method 'UnInhibit' in interface 'org.freedesktop.PowerManagement.Inhibit' at object path '/org/freedesktop/PowerManagement/Inhibit' (signature 'i')" ``` EXPECTED RESULT Inhibitions are released. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.13-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442063] New: Devices and Applications disappear after a while
https://bugs.kde.org/show_bug.cgi?id=442063 Bug ID: 442063 Summary: Devices and Applications disappear after a while Product: plasma-pa Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: aar...@doofus.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY After some time all applications and devices disappear from the volume control even though sound still works in applications such as Google Chrome. When this happens, there is no way for me to use the volume control in software. Note that I have several audio devices, the built-in audio on my motherboard, HDMI audio in a couple of monitors, and an external USB audio device, which is my primary audio source. The icon shows a mute button when this happens. If I select configure audio devices, no devices are shown. If, however, I go to the audio devices in system settings then all audio devices are shown. Note that pulse audio IS running and audio is also working in KDE apps, i.e. the system bell in a console. Also of note is that when this happens the keyboard volume control also stops working. STEPS TO REPRODUCE 1. Log in to KDE desktop 2. Do some work 3. Volume icon will at some point go mute and audio can no longer be controlled by it. OBSERVED RESULT Icon suddenly shows mute and stops working/ EXPECTED RESULT I expect the applications and the volume control to remain useable. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434447] Kickoff Favourites (and potentially other menus) omit preferred://filemanager
https://bugs.kde.org/show_bug.cgi?id=434447 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[lattedock] [Bug 440657] Restart system after yay -Syu with ASUS 32" Monitor attached (as I mostly have)
https://bugs.kde.org/show_bug.cgi?id=440657 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.
[krita] [Bug 442054] Cache and Resources
https://bugs.kde.org/show_bug.cgi?id=442054 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404594] Plasma crash when opening calendar from panel
https://bugs.kde.org/show_bug.cgi?id=404594 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #8 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 417125] Battery icon does not update on time
https://bugs.kde.org/show_bug.cgi?id=417125 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 413487] Kde battery monitor show the wrong number and it does not update ever
https://bugs.kde.org/show_bug.cgi?id=413487 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.
[plasmashell] [Bug 398567] Keyboard backlight shortcuts are not working anymore ASUS G56JK
https://bugs.kde.org/show_bug.cgi?id=398567 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.
[krita] [Bug 424603] Krita gives blackscreen when I open it. However if i move my mouse , I can see that it passes from some buttons in krita like opening a picture etc.
https://bugs.kde.org/show_bug.cgi?id=424603 --- Comment #8 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.
[krita] [Bug 442054] Cache and Resources
https://bugs.kde.org/show_bug.cgi?id=442054 --- Comment #2 from keyth_qcfx2 --- By design? like on purpose? *visible confusion* that makes no sense. 1. Well for how it is presented on the manual and your explanation have no visible connection beside the fact both related to the resources folder but what it does is totally different. 2. To it self to work properly. Because when I was trying to organize it would randomly read on one end and not on the other. because on the time you set a new resources folder if you don't have all the folders with a file inside you will end up with files in the cache file(previously empty) and others on the resource folder(that had files previously when the change happen). and if you try to rectify it by deleting the new blacklist files so it starts fresh it explains why files disappear while still being inside the folder tree. This makes 2 sets of folders trees with a couple valid on one side and the rest valid on the other side. 3. For any user it looses all value because it only makes sense to have the cache folder and resource folder not to be set to the same location so folders are not dropped at random if by chance some files containing the active valid paths disapears for some reason. As it creates a problem what was said and when to know what is valid at a given point and if you change something the settings may alter completely and may not be possible to set up again without cleaning up folders to then fill them up properly again or you will have to move them back and forth until you get them right. Honestly I felt like I was being trolled and now I can see why... Also within this design that serves no purpose, it is not doing what it should be doing with its own arbitrary set of rules. because my files got duplicated and it would still not read them on the new location. But It can explain why most of the cases of it not being read at one time and read on the other. gawd. Within the trail of thought it working for the objective to make a duplicated system of files for backups is also void because and this is my experience backups should always be done with the application turned off and this is a something I learnt the hard way. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441930] Plasma Wayland won't start
https://bugs.kde.org/show_bug.cgi?id=441930 --- Comment #2 from techxga...@outlook.com --- (In reply to David Edmundson from comment #1) > Please retest Still no good Thread 8 (Thread 0x7f3e0997b700 (LWP 3795)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56250eb9b088) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56250eb9b038, cond=0x56250eb9b060) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56250eb9b060, mutex=0x56250eb9b038) at pthread_cond_wait.c:638 #3 0x7f3e0b34ca4b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3e0b34c64b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3e209c9609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f3e20642293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f3e0b17e700 (LWP 3792)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56250eb9b088) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56250eb9b038, cond=0x56250eb9b060) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56250eb9b060, mutex=0x56250eb9b038) at pthread_cond_wait.c:638 #3 0x7f3e0b34ca4b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3e0b34c64b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3e209c9609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f3e20642293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f3e0a97d700 (LWP 3793)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56250eb9b088) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56250eb9b038, cond=0x56250eb9b060) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56250eb9b060, mutex=0x56250eb9b038) at pthread_cond_wait.c:638 #3 0x7f3e0b34ca4b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3e0b34c64b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3e209c9609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f3e20642293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f3e0a17c700 (LWP 3794)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56250eb9b088) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56250eb9b038, cond=0x56250eb9b060) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56250eb9b060, mutex=0x56250eb9b038) at pthread_cond_wait.c:638 #3 0x7f3e0b34ca4b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3e0b34c64b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3e209c9609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f3e20642293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f3e1aa9c700 (LWP 3789)): #0 0x7f3e20635aff in __GI___poll (fds=0x7f3e140053c0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3e1e84f36e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3e1e84f4a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3e20e26fc2 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3e20dcb26b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3e20be4c22 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3e228aef4b in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f3e20be5dbc in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3e209c9609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f3e20642293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f3e199d7700 (LWP 3791)): #0 0x7f3e20635aff in __GI___poll (fds=0x7f3e10004630, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3e1e84f36e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3e1e84f4a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3e20e26fc2 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3e20dcb26b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3e20be4c22 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3e20be5dbc in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3e209c9609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f3e20642293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f3e1a1d8700 (LWP 3790)): #0 0x7f3e20635aff in __GI___poll (fds=0x7f3e0c005240, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3e1e84f36e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3e1e84f4a3 in g_main_context_iteration () at
[krita] [Bug 442062] New: Add Mutiple Document Mode (Tabbed/Sub-window) chooser in Window menu/Workspace Chooser
https://bugs.kde.org/show_bug.cgi?id=442062 Bug ID: 442062 Summary: Add Mutiple Document Mode (Tabbed/Sub-window) chooser in Window menu/Workspace Chooser Product: krita Version: 5.0.0-beta1 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- One frequent question I got from new users is "how to display more than one document side-by-side". The answer is of course sub-window (A.K.A tile mode). It is often used as a simple trick to view reference image, or copying elements between documents. Krita's Multiple Document Mode option is hidden too deep. It's very difficult for people to find it without knowing it before hand. In real world, artists need to switch between Tabbed/Sub-window quite often, but it's very clumsy to do so in Krita. Other programs like Photoshop integrates this option into Window menu (Consolidate/Tile). I wish Krita will have the same as well. We can even put it in the Workspace chooser button menu, that'll make it even easier to discover. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 441616] Some global shortcuts / hotkeys like Meta+E or PrintScreen do not work when systemd startup is enabled
https://bugs.kde.org/show_bug.cgi?id=441616 Vladimir Yerilov changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 442061] Valgrind: very slow execution under Fedora 34
https://bugs.kde.org/show_bug.cgi?id=442061 Alvaro Kuolas changed: What|Removed |Added CC||kuo...@gmail.com --- Comment #1 from Alvaro Kuolas --- Created attachment 141323 --> https://bugs.kde.org/attachment.cgi?id=141323=edit perf record data Attached is perf record data -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 442061] New: Valgrind: very slow execution under Fedora 34
https://bugs.kde.org/show_bug.cgi?id=442061 Bug ID: 442061 Summary: Valgrind: very slow execution under Fedora 34 Product: valgrind Version: unspecified Platform: Fedora RPMs OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: kuo...@gmail.com Target Milestone: --- SUMMARY I am running valgrind on my PC with dual boot Windows 10 and Fedora 34. Running the same test on Ubuntu 20.04 (under Windows 10 WSL2) valgrind runs in less than a second, but on Fedora 34 is very slow, several minutes slow. On Fedora 34 it looks like the time spent is reading symbols. This is the part that takes most of the time: --23524-- Reading syms from /usr/lib64/libstdc++.so.6.0.29 --23524-- Considering /usr/lib/debug/.build-id/bd/d633ff5da0bba64d19ecf277a9eed7001da127.debug .. --23524-- .. build-id is valid --23524-- Considering /usr/lib/debug/.build-id/bd/../../../../../usr/lib/debug/usr/lib64/../../.dwz/gcc-11.2.1-1.fc34.x86_64 .. --23524-- .. build-id is valid --23524-- Reading syms from /usr/lib64/libm-2.33.so --23524-- Considering /usr/lib/debug/.build-id/c1/784bbe8a93a6e62f74b16105a2076a03b398ac.debug .. --23524-- .. build-id is valid --23524-- Reading syms from /usr/lib64/libgcc_s-11-20210728.so.1 --23524-- Considering /usr/lib/debug/.build-id/46/e10c9ee769c5cfc7cdb638e3ccbc3169c0a949.debug .. --23524-- .. build-id is valid --23524-- Considering /usr/lib/debug/.build-id/46/../../../../../usr/lib/debug/lib64/../.dwz/gcc-11.2.1-1.fc34.x86_64 .. --23524-- .. build-id is valid --23524-- Reading syms from /usr/lib64/libc-2.33.so --23524-- Considering /usr/lib/debug/.build-id/9d/e0f6e78ec16db4c6c167efc6b37466705edeff.debug .. --23524-- .. build-id is valid --23524-- Considering /usr/lib/debug/.build-id/9d/../../../../../usr/lib/debug/lib64/../.dwz/glibc-2.33-20.fc34.x86_64 .. --23524-- .. build-id is valid STEPS TO REPRODUCE 1. Run valgrind on a simple binary OBSERVED RESULT It takes minutes to execute. EXPECTED RESULT It should be instant as the program is very simple like "hello world". SOFTWARE/OS VERSIONS Linux: 5.13.13-200.fc34.x86_64 #1 SMP Thu Aug 26 17:06:39 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ADDITIONAL INFORMATION Using GCC 11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] New: Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 Bug ID: 442060 Summary: Mac OS Trackpad scroll buggy Product: kate Version: 21.08.1 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: axce...@gmail.com Target Milestone: --- Created attachment 141322 --> https://bugs.kde.org/attachment.cgi?id=141322=edit Screen recording of the issue. SUMMARY When you try to scroll using the trackpad on a MacBook Pro it responds erraticaly. Sometimes it tries to scroll back up when you are scrolling down and jumps about or tries to scroll back down when you are scrolling up and jumps around. It's ok if you hover over the overview and scroll, it only seems to be an issue in the main editor screen. STEPS TO REPRODUCE 1. Open any file that requires you to scroll 2. Try and scroll up and down a few times using the inbuilt trackpad 3. OBSERVED RESULT Scrolling is erratic and jumps about. EXPECTED RESULT Smooth scrolling that goes in the correct direction. SOFTWARE/OS VERSIONS macOS: OS X 10.15.7 ADDITIONAL INFORMATION I've attached a screen recording of the issue. I'm trying to scroll back up in the video but it keeps flicking back down until suddenly overshooting right to the very top. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442059] compositor displays a black screen when a maximized windows goes to full screen
https://bugs.kde.org/show_bug.cgi?id=442059 Chango changed: What|Removed |Added Summary|compositor shows a black|compositor displays a black |screen when a maximized |screen when a maximized |windows goes to full screen |windows goes to full screen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442059] New: compositor shows a black screen when a maximized windows goes to full screen
https://bugs.kde.org/show_bug.cgi?id=442059 Bug ID: 442059 Summary: compositor shows a black screen when a maximized windows goes to full screen Product: kwin Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: changoscalien...@gmail.com Target Milestone: --- SUMMARY compositor displays a black screen when a maximized windows goes to full screen. STEPS TO REPRODUCE 1. Open an application, Firefox, VLC or konsole 2. maximize Firefox, VLC or konsole 3. make that window full screen: press F11 on Firefox, on VLC open a video an press F to enter in full screen mode, on konsole right click on window title and navigate menu to full screen option. OBSERVED RESULT screen turns black, no image is displayed, only if the window was maximized before enter in full screen. NOTE: not maximized windows works fine. EXPECTED RESULT A normal fullscreen image of the window no matter the last size of the window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 21.1.20 (available in About System) KDE Plasma Version: 5.225 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Operating System: Manjaro Linux Kernel Version: 5.13.13-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 2 × AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ Memory: 3.8 GiB of RAM Graphics Processor: GeForce 210/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 442047] Labuntu usb running on a brand new computer
https://bugs.kde.org/show_bug.cgi?id=442047 Jan Paul Batrina changed: What|Removed |Added CC||jpmbatrin...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdewebkit] [Bug 442050] Help porting KHTML/KDE WebKit Update to Haiku
https://bugs.kde.org/show_bug.cgi?id=442050 Aaron S changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441930] Plasma Wayland won't start
https://bugs.kde.org/show_bug.cgi?id=441930 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |FIXED --- Comment #1 from David Edmundson --- Please retest -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437709] Crash in KWin::SurfacePixmap::platformTexture
https://bugs.kde.org/show_bug.cgi?id=437709 David Edmundson changed: What|Removed |Added CC||p.r.worr...@gmail.com --- Comment #10 from David Edmundson --- *** Bug 441947 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441947] kwin_wayland crashes when restoring Firefox from task manager
https://bugs.kde.org/show_bug.cgi?id=441947 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 437709 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441947] kwin_wayland crashes when restoring Firefox from task manager
https://bugs.kde.org/show_bug.cgi?id=441947 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Pasting inline Stack trace of thread 90042: #0 0x7f481bbbe254 _ZNK4KWin13SurfacePixmap15platformTextureEv (libkwin.so.5 + 0x236254) #1 0x7f48119721aa n/a (KWinSceneOpenGL.so + 0x221aa) #2 0x55e70036dd07 n/a (kwin_wayland + 0x61d07) #3 0x7f481a27b78e _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2eb78e) #4 0x7f481bb781ac _ZN4KWin5Scene11paintScreenERK7QRegionS3_PS1_S4_PNS_10RenderLoopERK10QMatrix4x4 (libkwin.so.5 + 0x1f01ac) #5 0x7f481196ded9 _ZN4KWin11SceneOpenGL5paintEPNS_14AbstractOutputERK7QRegionRK5QListIPNS_8ToplevelEEPNS_10RenderLoopE (KWinSceneOpenGL.so + 0x1ded9) #6 0x7f481bab2018 _ZN4KWin10Compositor9compositeEPNS_10RenderLoopE (libkwin.so.5 + 0x12a018) #7 0x7f481a27b78e _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2eb78e) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441973] Crashs with Nvidia Proprietary and wayland
https://bugs.kde.org/show_bug.cgi?id=441973 David Edmundson changed: What|Removed |Added Severity|critical|crash Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Crashes need a backtrace to be actionable -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 429770] The password dialog text field highlight on start is overlapped by the loading window
https://bugs.kde.org/show_bug.cgi?id=429770 Bug 429770 depends on bug 424795, which changed state. Bug 424795 Summary: Unfocused windows don't get brought forward when activated externally https://bugs.kde.org/show_bug.cgi?id=424795 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- 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 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #16 from David Edmundson --- This has changed a lot in 5.23. It won't fix everything at once, but leaving this open won't help with that. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442058] New: Floating messages do not refresh their duration if another floating message occurs during expiration
https://bugs.kde.org/show_bug.cgi?id=442058 Bug ID: 442058 Summary: Floating messages do not refresh their duration if another floating message occurs during expiration Product: krita Version: 5.0.0-beta1 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- SUMMARY Floating messages don't seem to refresh their duration if another floating message is called during their expiration. Not a regression. STEPS TO REPRODUCE 1. Zoom in. Observe floating message. 2. Zoom in about half a second later. OBSERVED RESULT The floating message resulting from step 2 barely appears/doesn't appear. EXPECTED RESULT Floating message durations shouldn't be negatively impacted by preceding floating messages. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.12.11 (Appimage) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441823] Menubar dropdowns positioned on wrong place in Wayland when second screen is offsetted
https://bugs.kde.org/show_bug.cgi?id=441823 --- Comment #2 from David Edmundson --- >wouldn't be able to reliably reproduce though. Primary monitor at non 0,0 is the key trigger -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441823] Menubar dropdowns positioned on wrong place in Wayland when second screen is offsetted
https://bugs.kde.org/show_bug.cgi?id=441823 David Edmundson changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442032] dropdowns are missplaced when using wayland plasma
https://bugs.kde.org/show_bug.cgi?id=442032 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- Upstream Qt bug. There's a report already -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442015] Screen looses content randomly, just black
https://bugs.kde.org/show_bug.cgi?id=442015 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Is the cursor visible? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- sub-window or child with a transient parent? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 442057] New: AppImage won't start
https://bugs.kde.org/show_bug.cgi?id=442057 Bug ID: 442057 Summary: AppImage won't start Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: eaglex...@gmail.com Target Milestone: --- SUMMARY I downloaded App Image for build 961, 962 and 963 and when I start them all three build images show Cannot open /proc/self/exe: Permission denied Failed to get fs offset for /proc/self/exe The last image I downloaded that worked is build 955 (did not download and test builds 956-960) STEPS TO REPRODUCE 1. Download App Image builds 961, 962, 963 2. Make App Image executable 3. execute App Image OBSERVED RESULT Console logs show Cannot open /proc/self/exe: Permission denied Failed to get fs offset for /proc/self/exe EXPECTED RESULT Application to run SOFTWARE/OS VERSIONS Linux: Kubuntu 20.04 (Kernel 5.4.0-81-generic) 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.
[plasmashell] [Bug 426464] Transparent Plasma themes are missing transparency in Wayland session with proprietary NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=426464 --- Comment #16 from Mateus --- Only relevant info I could find inside journalctl is that this set of messages appear every time I try to open a plasma panel: Sep 05 19:51:21 mainpc plasmashell[576]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Sep 05 19:51:21 mainpc plasmashell[576]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x5603e60dfa30, name="popupWindow") Sep 05 19:51:21 mainpc plasmashell[576]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x5603e60dfa30, name="popupWindow") Sep 05 19:51:21 mainpc plasmashell[576]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x5603e60dfa30, name="popupWindow") Sep 05 19:51:26 mainpc plasmashell[576]: kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/applications.so" "Failed to extract plugin meta data from '/usr/lib/qt/plugins/kf5/kio/applications.so'" Sep 05 19:51:26 mainpc plasmashell[576]: kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/desktop.so" "Failed to extract plugin meta data from '/usr/lib/qt/plugins/kf5/kio/desktop.so'" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426464] Transparent Plasma themes are missing transparency in Wayland session with proprietary NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=426464 --- Comment #15 from Mateus --- > The plasma panel and kickoff must be using Xwayland by default. Launched a Wayland session and I can confirm this is not the case. `xwininfo` cannot select any plasma panel and `xlsclients` lists firefox only. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 428181] Audacious music player "Open Folder" option no longer working after Plasma 5.20 update
https://bugs.kde.org/show_bug.cgi?id=428181 --- Comment #8 from Jazz --- I've noticed something interesting. I.g. if we have the following dir path: ~/A/B/C/D In case you open D dir (from the "Open Folder" dialogue) and try to click at "Open" - it won't work. But in case you open dir C and JUST SELECT dir D (without opening it), then clicking "Open" works as expected! I could replicate the above behavior whilst running the above Python code as well. Is this the expected behavior? Not very intuitive/user friendly imo. It should work in both cases. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426464] Transparent Plasma themes are missing transparency in Wayland session with proprietary NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=426464 --- Comment #14 from Mateus --- (In reply to Alessandro Astone from comment #13) > This happens on any Xwayland window with transparency. The plasma panel and > kickoff must be using Xwayland by default. This does indeed make sense. I remember seeing some errors related to Xwayland on journalctl. I'll see if I can find them again -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 441857] Online Banking Setup
https://bugs.kde.org/show_bug.cgi?id=441857 --- Comment #14 from Hamdsa --- Sorry I should have added to my description that I was using the manual method to attempt the connection, so basically what you have recommended. I noticed that the default automatic method within KMyMoney for most banks I tried had the message below that it didn't support online banking, which I know was not correct, so I opted for manual connection. The initial entry of the URL's and corresponding KMyMoney message that the bank supports online stmts etc. at least suggest that the URLs are recognized for the connection. I don't recall the successful connection method for Citibank, but at least I can confirm that for both Chase bank and credit cards, it's currently working in GNUcash (using Aquabanking). After the initial call is sent after entering my credentials in KMyMoney, I do get a message in my chase online account profile that I need to authorize the access from desktop software, which means the initial call is successfully reaching Chase. However, after I click on the authorization link within Chase, where it says it's successful and I should be able to access my account info, I still get the message within KMyMoney that no suitable accounts exist, which makes me thing it's the post-MFA flow that is somehow not working, at least for Chase. However, that doesn't explain why it isn't working for other banks like AMEX which doesn't have the similar MFA flow as chase. My AMEX connection is also working within GNUCash, and despite replicating the settings using the manual connection options, it didn't work for me. Someone earlier mentioned that connection to Chase was working for them, but not sure if they were using the windows version like me, or I'm simply missing something here. Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442055] Add ruler parallel to the horizon in 2 point perspective assistant
https://bugs.kde.org/show_bug.cgi?id=442055 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Severity|normal |wishlist --- Comment #1 from Tiar --- Not sure if agree; it's only useful for some cases and it would make using the vanishing point more difficult. Maybe if it was disabled by default, though... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 442056] shortcut stop working
https://bugs.kde.org/show_bug.cgi?id=442056 --- Comment #1 from Rajinder Yadav --- Created attachment 141321 --> https://bugs.kde.org/attachment.cgi?id=141321=edit shortcuts sys setting -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 442056] New: shortcut stop working
https://bugs.kde.org/show_bug.cgi?id=442056 Bug ID: 442056 Summary: shortcut stop working Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY Had application shortcut for "LibreOffice Calc" set to META+ALT+O, no longer works! I have reset it and it still doesn't work. This worked in the past with no issues. My other shortcut seem to be working ok. STEPS TO REPRODUCE 1. open sys setting 2. create shortcut for libreoffice calc 3. set shortcut to meta+alt+o (letter o) OBSERVED RESULT Fails to work EXPECTED RESULT Open app Operating System: openSUSE Tumbleweed 20210902 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.13-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442055] New: Add ruler parallel to the horizon in 2 point perspective assistant
https://bugs.kde.org/show_bug.cgi?id=442055 Bug ID: 442055 Summary: Add ruler parallel to the horizon in 2 point perspective assistant Product: krita Version: 5.0.0-beta1 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: rave...@o2.pl Target Milestone: --- SUMMARY The 5.0 beta two point perspective assistant is already very impressive, however something seems to be missing and it is a ruler that is parallel to the horizon (line connecting the two vanishing points). It would be useful for drawing stuff in open spaces where some areas would necessarily show the horizon without stuff obscuring it and also for drawing utems that are in front of camera and parallel to it, rotated on different angle. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 436235] Elisa crashes when scrolling down in Files mode
https://bugs.kde.org/show_bug.cgi?id=436235 disch.johan...@gmx.de changed: What|Removed |Added CC||disch.johan...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 429910] Settings -> File search: Folder specific configuration list: self-reproducing, irremovable items of '/home/' with 'indexed' value
https://bugs.kde.org/show_bug.cgi?id=429910 pveax changed: What|Removed |Added Version|5.22.2 |5.22.5 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 429910] Settings -> File search: Folder specific configuration list: self-reproducing, irremovable items of '/home/' with 'indexed' value
https://bugs.kde.org/show_bug.cgi?id=429910 --- Comment #12 from pveax --- Sorry for my English. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 442048] KolourPaint critical installation error
https://bugs.kde.org/show_bug.cgi?id=442048 Martin Koller changed: What|Removed |Added CC||kol...@aon.at Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Martin Koller --- I don't understand. What do you mean by "the desktop commands are canceled" ? "when restarting the Pc it is left on a black screen with a check mark" what ist left where ? Screenshot, please. Please provide more details. I do not understand your problem at all. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 441740] Add icon to install
https://bugs.kde.org/show_bug.cgi?id=441740 Nicolas Fella changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/skanlite/commit/1c111a ||82f7d0880777090e300f2fb434f ||bca9776 --- Comment #2 from Nicolas Fella --- Git commit 1c111a82f7d0880777090e300f2fb434fbca9776 by Nicolas Fella. Committed on 05/09/2021 at 20:35. Pushed by nicolasfella into branch 'master'. Install app icon Currently we rely on the 'skanlite' icon being shipped by breeze-icons, which causes trouble when using Skanlite outside of Plasma or from Flatpak. Install the app icon to the hicolor theme to make sure it's always available. The icon file is copied from breeze-icons A +51 -048-apps-org.kde.skanlite.svg M +3-0CMakeLists.txt M +1-1src/org.kde.skanlite.desktop https://invent.kde.org/graphics/skanlite/commit/1c111a82f7d0880777090e300f2fb434fbca9776 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442054] Cache and Resources
https://bugs.kde.org/show_bug.cgi?id=442054 Tiar changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Sorry, but that's by design (well, most of it). In the new system, there is only one folder with resources, and it is built by Krita with default resources. So if you change the path to the resource folder, Krita adds those default resources to the new folder and forgets about the previous resource folder. Krita only checks one folder at the time for resources, so if default resources weren't there, Krita wouldn't know about them. However, do you mean that if you define another resource folder, the keyboard shortcuts etc. files are not recreated there? -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 442039] Make Okular/ODT read-only
https://bugs.kde.org/show_bug.cgi?id=442039 Ben Cooksley changed: What|Removed |Added CC||bcooks...@kde.org --- Comment #1 from Ben Cooksley --- Albert, can you please confirm? Christopher: Please use Sysadmin tickets when requesting changes such as this. Requests made via Bugzilla may not be well tracked and end up being lost. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files
https://bugs.kde.org/show_bug.cgi?id=442010 --- Comment #10 from Antonio Rojas --- kinit was recently removed as a dependency of dolphin, but it is still an undeclared runtime dependency of some frameworks, which may break stuff. Since you have it installed, we can rule it out as the cause for this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441783] kde wayland klipper copies empty string instead of content
https://bugs.kde.org/show_bug.cgi?id=441783 --- Comment #4 from codew...@web.de --- additionally I've tried firefox without XWayland > export MOZ_ENABLE_WAYLAND=1 > firefox -> no issues -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files
https://bugs.kde.org/show_bug.cgi?id=442010 --- Comment #9 from Kyle Devir --- So, yes, kinit is actually installed, so it is, apparently -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442054] New: Cache and Resources
https://bugs.kde.org/show_bug.cgi?id=442054 Bug ID: 442054 Summary: Cache and Resources Product: krita Version: 5.0.0-beta1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: keyth2363...@gmail.com Target Milestone: --- SUMMARY When selecting a resource folder things start to become weird for file management. STEPS TO REPRODUCE 1. Configure Krita > General > Resources > Resource Folder = select a new folder 2. Restart Krita OBSERVED RESULT This will rebuild the folder tree(good) and will rebuild all the default files present in the cache file(bad! it already exists in 2 locations and now it exists in 3). Using Krita over time will duplicate folders on both unecessary work. Not all file types in the Resource folder will be detected When This folder free is rebuilt(cache or resources) there is a bundle folder and no bundles are placed inside on either. Deleting files on the resource folder to only hold my files creates many issues to the point the brush Preset window can become unusable and only detect the brush in index=zero only. Resource Folder Detected Files: Paintool Presets Brushes Gradients Resource Folder Not Detected Files: Keyboard Shortcuts Author File PyKrita Scripts Constantly spawning files in: gamutmasks gradients paint tool presets palettes patterns seexpr_scripts symbols windowlayouts workspaces Bundles (but with bundles placed outside the bundle folder) EXPECTED RESULT Resource folder to add files to Krita but act not as a duplicated folder. 2 locations with resources, Probably Cache for System forced files and installations and Resources with user created files. Detect more resources than just brushes, it rebuilds the whole folder tree but does not accept them all. Files of a given file type inside the correct folder and not outside it after it was created for it. SOFTWARE/OS VERSIONS Windows: 10 Qt Version: 5.12 ADDITIONAL INFORMATION I took a look at the krita manual to try and understand if my idea of what the resource folder was incorrect and it states currently: """ https://docs.krita.org/en/reference_manual/resource_management.html?highlight=resource%20folder Resource Folder The resource folder is considered the primary library. When creating new resources, they will all end up here. You can configure its location in the general preferences. """ This means it is user generated or user installed however this is not what happens. I did not create these files and there they are. I think krita standard files should not be in the cache or resource folder but if it is really needed to edit them and have a safe guard they should be inside the cache location only. Resources sounds to me and is in other software too (called environment though) another folder tree like in the cache location but has only "user files" as explained on the manual. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files
https://bugs.kde.org/show_bug.cgi?id=442010 --- Comment #8 from Kyle Devir --- If kinit is a dependecy, I thought kdesrc-build would have drawn it in as a dependency for Dolphin... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files
https://bugs.kde.org/show_bug.cgi?id=442010 --- Comment #7 from Kyle Devir --- Wait, kinit? -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 441182] Akonadi versions are not up to date
https://bugs.kde.org/show_bug.cgi?id=441182 --- Comment #3 from Christopher Yeleighton --- KAddressBook: does not import URL from iPhone vcf -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files
https://bugs.kde.org/show_bug.cgi?id=442010 --- Comment #6 from Kyle Devir --- @Antonio Yes -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 441824] Share tab of file properties shows never-ending oversized loading animation
https://bugs.kde.org/show_bug.cgi?id=441824 --- Comment #10 from ratijas --- Arch Linux maintainer Antonio Rojas repackaged kdenetwork-filesharing, making samba a hard required dependency instead of an optional one. We still think that spinner should be somehow fixed. What if the package is installed, but application is broken? Or config is so messed up, that samba is failing to start? Either way, UI should somehow handle defective backend instead of displaying gibberish. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 436264] "New Tab" menu item does nothing when only one profile exists
https://bugs.kde.org/show_bug.cgi?id=436264 nsprang...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/konsole/commit/fed1a9 ||d2cf9a9d6f4c0207068b43f7788 ||b8515ea Status|ASSIGNED|RESOLVED --- Comment #5 from nsprang...@gmail.com --- Git commit fed1a9d2cf9a9d6f4c0207068b43f7788b8515ea by Nathan Sprangers. Committed on 05/09/2021 at 19:49. Pushed by ahmadsamir into branch 'master'. Fix missing new-tab menu when only one profile exists Sub-menu will always be displayed in "File>New Tab" and "New Tab" button, even if there is only one profile to display (the built-in default). This fixes not being able to create a new tab from "File>New Tab" menu and long-pressing on the new tab toolbar button. M +16 -39 src/MainWindow.cpp https://invent.kde.org/utilities/konsole/commit/fed1a9d2cf9a9d6f4c0207068b43f7788b8515ea -- You are receiving this mail because: You are watching all bug changes.
[calligragemini] [Bug 442053] New: When opening the application and then make a new document it immeditely crashes on Slackware with KDE 4.14.21
https://bugs.kde.org/show_bug.cgi?id=442053 Bug ID: 442053 Summary: When opening the application and then make a new document it immeditely crashes on Slackware with KDE 4.14.21 Product: calligragemini Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: paulflaher...@hotmail.com Target Milestone: --- Application: calligragemini (2.9.11) KDE Platform Version: 4.14.21 Qt Version: 4.8.7 Operating System: Linux 4.4.14 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: When opening the application and then make a new document it immeditely crashes on Slackware with KDE 4.14.21 The crash can be reproduced every time. -- Backtrace: Application: Calligra Gemini (calligragemini), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6eb6e027c0 (LWP 2286))] Thread 4 (Thread 0x7f6e11ef5700 (LWP 2289)): #0 0x7f6eb03f236f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6e161434d3 in () at /usr/lib64/xorg/modules/dri/swrast_dri.so #2 0x7f6e16143367 in () at /usr/lib64/xorg/modules/dri/swrast_dri.so #3 0x7f6eb03ec684 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6eaf888efd in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f6e126f6700 (LWP 2288)): #0 0x7f6eb03f236f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6e161434d3 in () at /usr/lib64/xorg/modules/dri/swrast_dri.so #2 0x7f6e16143367 in () at /usr/lib64/xorg/modules/dri/swrast_dri.so #3 0x7f6eb03ec684 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6eaf888efd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f6e9791c700 (LWP 2287)): #0 0x7f6eb03f236f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6eaf45c5aa in () at /usr/lib64/qt/lib/libQtScript.so.4 #2 0x7f6eaf45c5d9 in () at /usr/lib64/qt/lib/libQtScript.so.4 #3 0x7f6eb03ec684 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6eaf888efd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f6eb6e027c0 (LWP 2286)): [KCrash Handler] #6 0x7f6eb4f31a38 in KWPageManager::pageNumber(QPointF const&) const () at /usr/lib64/libwordsprivate.so.14 #7 0x7f6eb4f32ca7 in KWPageManager::page(QPointF const&) const () at /usr/lib64/libwordsprivate.so.14 #8 0x7f6e1146c69b in () at /usr/lib64/calligra/imports/org/calligra/CalligraComponents/libcalligraqtquickcomponentsplugin.so #9 0x7f6e11465d98 in () at /usr/lib64/calligra/imports/org/calligra/CalligraComponents/libcalligraqtquickcomponentsplugin.so #10 0x7f6eb68f9bc6 in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #11 0x7f6eb68ff696 in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #12 0x7f6eaf4dab24 in () at /usr/lib64/qt/lib/libQtScript.so.4 #13 0x7f6eaf39fda5 in () at /usr/lib64/qt/lib/libQtScript.so.4 #14 0x7f6e170e6fe0 in () #15 0x7f6e0003 in () #16 0x7f6e0d6403d0 in () #17 0x7f6e0002 in () #18 0x7ffca4fe8ac0 in () #19 0x03541d70 in () #20 0x012bdea0 in () #21 0x7f6eb67f1d50 in QDeclarativeItemPrivate::width() const () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #22 0x012983b0 in () #23 0x7ffca4fe8f50 in () #24 0x7f6e170e6ee8 in () #25 0x7f6e9701f750 in () #26 0x7f6e16c1c3f8 in () #27 0x7f6e97025a88 in () #28 0x7f6eaf75e588 in __bss_start () at /usr/lib64/qt/lib/libQtScript.so.4 #29 0x7f6e97024800 in () #30 0x7f6e16c1c3b0 in () #31 0x7f6e97024800 in () #32 0x7f6eaf75e588 in __bss_start () at /usr/lib64/qt/lib/libQtScript.so.4 #33 0x7f6e16c1c358 in () #34 0x7f6e16c1c3f8 in () #35 0x7f6e9701f738 in () #36 0x7f6eaf35634a in () at /usr/lib64/qt/lib/libQtScript.so.4 #37 0x7f6eaf3f761b in () at /usr/lib64/qt/lib/libQtScript.so.4 #38 0x7f6eaf3c947f in () at /usr/lib64/qt/lib/libQtScript.so.4 #39 0x7f6eaf4b7acf in QScriptValue::call(QScriptValue const&, QList const&) () at /usr/lib64/qt/lib/libQtScript.so.4 #40 0x7f6eb6860ccd in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #41 0x7f6eb686336e in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #42 0x7f6eb686367c in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #43 0x7f6eb68637bb in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #44 0x7f6eb689e7a5 in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #45 0x7f6eb5644f86 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4 #46 0x7f6eb5644e30 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4 #47
[kmymoney] [Bug 442052] New: transaction date vs post date
https://bugs.kde.org/show_bug.cgi?id=442052 Bug ID: 442052 Summary: transaction date vs post date Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Allow for tracking of both transaction date and post date. After some research, it seems that most banks keep track of the post date. However, this make it very difficult for personal financing. Keep in mind the following goals: - I want to track when I made transactions for taxes purposes. Here the date on which I made the purchase or sell, matters most. - I want to keep in sych with my financial institution. Here is one scenario: I make charges to my credit card on the weekend. Most transactions, will post on Monday, not when made. The financial institution does know the transaction date, but their OFX will use the POST date. Statements do show both, transaction date and post date. In KMyMoney, I enter the transaction manually on the day it was made. But now it will not match my banks. Scenario two: Paying my Credit card bill. When I pay my credit card from my checking account, it will reflect that the transaction is pending as of the date I sent it. My Credit card will not receive the money and process it until a few days later. In Double entry accounting, both accounts have to be modified at the same time/date. Should we be using the transaction date(when I sent the payment) or when the transaction posted? Or should we keep track of both. 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 It may be a duplicate or an expansion of this https://bugs.kde.org/show_bug.cgi?id=135198 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442051] Buttons with different heights
https://bugs.kde.org/show_bug.cgi?id=442051 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com --- Comment #1 from tomtomtomreportin...@gmail.com --- Can't reproduce in the appimage nor on my own compilation, maybe Windows-only issue? Changing the interface's width doesn't seem to cause it, nor does having enough bundles to activate a scrollbar. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442051] New: Buttons with different heights
https://bugs.kde.org/show_bug.cgi?id=442051 Bug ID: 442051 Summary: Buttons with different heights Product: krita Version: 5.0.0-beta1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: keyth2363...@gmail.com Target Milestone: --- SUMMARY When using the Manage Resource Libraries from Krita 5 and you active or deactivate the buttons have different sizes. STEPS TO REPRODUCE 1. Open "Manage Resource Libraries" 2. Press activate or deactivate OBSERVED RESULT https://krita-artists.org/uploads/default/original/3X/e/7/e7ec55ad3016987fbf087cc6f51bffa9bd87530e.gif EXPECTED RESULT UI not to flicker by shifting buttons around SOFTWARE/OS VERSIONS Windows: 10 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 343364] keys pressed show as with r_alt modifier
https://bugs.kde.org/show_bug.cgi?id=343364 Martin Zbořil changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #7 from Martin Zbořil --- i opened this bug more than 5 years ago and don't have to use this application anymore (and this experience didn't exactly convince me to bother further) so you can close it if you feel like the info i gave you isn't sufficient... i found another way to test some weirdness in krdc by connecting to a second kde session via krfb session where i set US keyboard while having CZ keyboard on krdc, then i pressed top line of keys (which are in US keyboard as follows: `1234567890-= in CZ they are as: ;+ěščřýžýáíé=´) i get this: +23456ýáíé= (´ doesn't work via krdc/krfb) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdewebkit] [Bug 442050] New: Help porting KHTML/KDE WebKit Update to Haiku
https://bugs.kde.org/show_bug.cgi?id=442050 Bug ID: 442050 Summary: Help porting KHTML/KDE WebKit Update to Haiku Product: frameworks-kdewebkit Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: animor...@protonmail.com Target Milestone: --- SUMMARY Good afternoon: I’m on the promotions team on the Haiku project. We rely pretty heavily on QT and WebKit for much of our software. WebKit1 is integrated pretty tightly into our default OS web browser, WebPositive. We have found that it is a huge challenge porting the latest versions of WebKit onto Haiku, and were hoping for help from the much-larger KDE project. Haiku leans heavily on C++ and has Posix compliance. Haiku is not a *nix. I, personally, and not a programmer, but I can help direct you to others who may be able to answer questions. These include our current WebPositive primary developer, PulkoMandy. We think this holds a lot of value to provide additional variety for the software world in general. SOFTWARE/OS VERSIONS OS: Haiku R1/Beta 3 or Nightly Rolling Release. Haiku-os.org Qt Version: 5.15.2 ADDITIONAL INFORMATION This is a request for assistance in upgrading our systems from a small project to a larger one. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 441112] Errors in KStars star chart
https://bugs.kde.org/show_bug.cgi?id=441112 Jean-Claude changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #15 from Jean-Claude --- This is solved : the planet and stars filez were out-dated for an unknown reason<<< I replaced them and everything worked fine -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 442049] New: reports: click on account to see transactions contributing to the report for the date
https://bugs.kde.org/show_bug.cgi?id=442049 Bug ID: 442049 Summary: reports: click on account to see transactions contributing to the report for the date Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY When looking at a report, the user should be able to drill down to the account(category) transactions at the start of the time range which is set in the report or group date range where the user clicked. Example, a report that shows the accounts balance across three months: if the user clicks on the value for a cross section of an Account and month 1, then the ledge should open for that account at the start for Month 1. This will help when users are looking back at the reports. 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: - Gnome 40.4.0 KDE Frameworks 5.51.0 Qt 5.11.3 (built against 5.11.3) The xcb windowing system ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441956] Qthread with Python broken in Krita 5
https://bugs.kde.org/show_bug.cgi?id=441956 --- Comment #2 from keyth_qcfx2 --- I made the minimal working example. download at: https://github.com/EyeOdin/bug_report_example to use this: 1. install "bug_report_example" as any other plugin docker. 2. open any image bigger than 1000x1000 or so with krita. This will update the display of that image every second without any limitations for this example. 3. press Left Mouse Button on the docker and move the white square with the mouse. 4. using this in 4.4.5 will move the square with no lag and on krita 5 will move the square with rubber banding Notes: 0. This contains the essencial loop of QThread present on Tela. I tryed to make a scripter version but considering I had to create a window to exist, it was not affected by the UI lag nor it had canvas directly available and Krita somehow as it seemed independant I might be wrong though. But because of that I made it into a mini docker as I think this is a composited problem and not a isolate case that happens on every situation with QThread. 1. I know self.update() sucks to cause lag but I made it to write it faster, my original script does not have it but has tons of more stuff that justifies not using it. 2. The original script stops itself from doing a full loop but still has to check what is the image because I cant detect if there was an interaction of the user with Krita to guess "considering the user clicked Krita did he edit the image?" I made that into another proposal to bypass this QThread handycap situation at: https://krita-artists.org/t/python-user-activity-versus-inactivity-timer/28504 However doing this proposal with the current system is so glitchy and prone to crash that is not worth exploring more as it is not a viable solution as I state on the thread. Either way, the usage of QThread bypassed all these crossroads by simply powering through it by managing the workload correctly. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 441881] KSysGuard Crashes When Closing
https://bugs.kde.org/show_bug.cgi?id=441881 tonyw...@rocketmail.com changed: What|Removed |Added Platform|Debian stable |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 442048] New: KolourPaint critical installation error
https://bugs.kde.org/show_bug.cgi?id=442048 Bug ID: 442048 Summary: KolourPaint critical installation error Product: kolourpaint Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: choiva...@gmail.com Target Milestone: --- Hi, I'm a loyal Linux user. I am writing to report a known bug after installing KolourPaint version 21.08.0 from the software center. After installing the desktop commands are canceled and when restarting the Pc it is left on a black screen with a check mark, having to reinstall the operating system completely. I hope I can contribute to solving the problem and at your disposal with any questions. My operating system is Solus Mate 4.3 64 bits kernel 5.13.1. Regards Ivan. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktextwidgets] [Bug 441984] Re implement KPluralHandlingSpinBox
https://bugs.kde.org/show_bug.cgi?id=441984 --- Comment #2 from Safa Alfulaij --- Yes. As you see in the snapshot, Arabic shouldn't use the placeholder in the first three forms. (We write "No books", "One book", "Two books") I also think that some languages change the prefix (if exists) For example: - There is 1 book - There are 5 books -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 442047] New: Labuntu usb running on a brand new computer
https://bugs.kde.org/show_bug.cgi?id=442047 Bug ID: 442047 Summary: Labuntu usb running on a brand new computer Product: Discover Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: yqwwotq...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: yqwwotq...@gmail.com 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.
[kwin] [Bug 442015] Screen looses content randomly, just black
https://bugs.kde.org/show_bug.cgi?id=442015 --- Comment #1 from Simon Schmeisser --- I attached an external monitor, opened the screen settings, toggled the laptop screen off and on and it was completely normal again. Let's see for how long. But this makes me doubt it is an hardware issue (besides that it started with the last update) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442040] Date time original does not always update correctly on maintenance read from image files.
https://bugs.kde.org/show_bug.cgi?id=442040 caulier.gil...@gmail.com changed: What|Removed |Added Platform|Other |Microsoft Windows CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 --- Comment #4 from Manuel Geißer --- Thanks for the help! I'm rather new to KDevelop and haven't unraveled its full capabilities yet. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438703] Missing translations for a few common buttons like OK and Cancel (Kate official builds only)
https://bugs.kde.org/show_bug.cgi?id=438703 --- Comment #13 from Christoph Cullmann --- Started to work on some solution by creating a qt.conf https://invent.kde.org/packaging/craft/-/merge_requests/44 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442046] New: copy-paste from LTR languages bring reversed text
https://bugs.kde.org/show_bug.cgi?id=442046 Bug ID: 442046 Summary: copy-paste from LTR languages bring reversed text Product: okular Version: 21.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: adam.golan...@gmail.com Target Milestone: --- SUMMARY Copying arabic and hebrew text strings from Okular to paste it in another program makes them reversed and garbled. Changing LTR settings doesn't help. I've tested this with Foxit PDF Reader and it worked OK. STEPS TO REPRODUCE 1. select and copy to clipboard arabic or hebrew text in Okular, for example אשר, האיש—אשר לא הלך, בעצת רשעים ال َق ِدي ْ 2. paste it to Libre Office or Google Docs OBSERVED RESULT you're getting something like םיעשר תצעב ,ךלה אל רשא—שיאה ,רשא ر ْ يِ دق َ لا (yeah, in Arabic its really horrible :D) EXPECTED RESULT it should keep correct LTR flow: אשר, האיש—אשר לא הלך, בעצת רשעים ال َق ِدي ْ SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 442045] New: Firefox not able to be "Default Browser after Updates".
https://bugs.kde.org/show_bug.cgi?id=442045 Bug ID: 442045 Summary: Firefox not able to be "Default Browser after Updates". Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: lorenjfi...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- At upgrade/update the file "/usr/share/applications/firefox.desktop" must be modified at the the 1st instance of "Exec=firefox %u" to allow Firefox to become the "Default Browser" The following line is is the patch I add to the 1st instance of "Exec=" Change line "Exec=firefox %u" to "Exec=env --unset=GTK_USE_PORTAL /usr/lib/firefox/firefox %u" -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 441958] Shut Down, Restart, and Log Out actions no longer work
https://bugs.kde.org/show_bug.cgi?id=441958 --- Comment #5 from David Edmundson --- >I don't like when things randomly break and then start working again... If it helps, logs show that it launched /usr/libexec/ksmserver-logout-greeter -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441924] Latte icons move back and forth when launching a new app
https://bugs.kde.org/show_bug.cgi?id=441924 --- Comment #7 from Michail Vourlakos --- Still no idea then, I am considering it pretty minor. Maybe someone else in the future will find something more. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 441958] Shut Down, Restart, and Log Out actions no longer work
https://bugs.kde.org/show_bug.cgi?id=441958 --- Comment #4 from Nate Graham --- Just checked again, it seems to be working now. Still, the fragility of this system worries me a bit. Setup issue though it may be, I don't like when things randomly break and then start working again... -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 441958] Shut Down, Restart, and Log Out actions no longer work
https://bugs.kde.org/show_bug.cgi?id=441958 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from David Edmundson --- Log shows a message gets sent to org.kde.LogoutPrompt There's no reply. That means the binary failed to load (or crashed before it could register the service). Given it's one reporter with DBus activation and we have a pattern of this causing setup issues I'm closing this. Ping me on IM if you can't spot the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441783] kde wayland klipper copies empty string instead of content
https://bugs.kde.org/show_bug.cgi?id=441783 --- Comment #3 from codew...@web.de --- I used the KWin Debug console to test which windows use x11 (x11 client windows) X11 Client windows: - Firefox (issue found) - Signal desktop app (issue found) - Jetbrains Rider (issue found) XWayland Observed behavior: - Copies most of the times 1 entry for the line + one empty entry - Copies sometimes only an empty entry -- Wayland: - Kate (no issues, and also no empty line) - Dolphin (Copying the path the the current dir) (No issues) --- Conclusion: - There seems to be something strange going on when using KWayland (unfortunately used by a lot of applications) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442040] Date time original does not always update correctly on maintenance read from image files.
https://bugs.kde.org/show_bug.cgi?id=442040 --- Comment #3 from Maik Qualmann --- One more word on Flickr. We just pass a title, description and tags to the API. digiKam does not send dates to Flickr. This means that Flickr itself extracts the date from the image metadata. If it is wrong, it is already wrong in your image and therefore it is clear that digiKam recognizes the same date as Flickr. Maik -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441924] Latte icons move back and forth when launching a new app
https://bugs.kde.org/show_bug.cgi?id=441924 --- Comment #6 from David --- (In reply to Michail Vourlakos from comment #5) > I am almost sure this is upstream but I dont have proof. My guess is that > plasma libtaskmanager that is not Latte responsibility when a new window is > added or something it is adding initially at the 0 position and subsequently > moves it at its proper placement. This behavior has been observed in other > cases also. Not so sure about that. If I dowgrade latte to 0.9.11 while keeping libtaskmanager at the same version (5.21.5), I do not experience this issue anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 Nils Fenner changed: What|Removed |Added Version|unspecified |5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] New: KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 Bug ID: 442044 Summary: KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows. Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: nilsfen...@web.de Target Milestone: --- When "show desktop" action is triggered (e.g. by Meta+D shortcut) pcmanfm-qt stays visible in LXQt session. STEPS TO REPRODUCE 1. Start LXQt session (implies: pcmanfm-qt --desktop) 2. Start pcmanfm-qt 3. Call "show desktop" action (e.g. Windows+D) OBSERVED RESULT pcmanfm-qt (file manager) stays visible on screen EXPECTED RESULT pcmanfm-qt (file manager) is hidden like a normal application SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.22.0 (available in About System) KDE Plasma Version: not relevant KDE Frameworks Version: not relevant Qt Version: 5.15.2 (LXQt Version: 0.17) ADDITIONAL INFORMATION When LXQt session starts the first pcmanfm-qt instance implies the flag __NET_WM_WINDOW_TYPE_DESKTOP (aka Qt::WA_X11NetWmWindowTypeDesktop). KWin correctly detects it as a desktop window and does not hide it when "show desktop" action is triggered. However pcmanfm-qt creates subsequent instances through a short-lived process resulting in a child window. KWin now takes the window flags from the parent (desktop window) and the (child) window always stays on screen. For reference see LXQt bug #1411 (https://github.com/lxqt/pcmanfm-qt/issues/1411) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442040] Date time original does not always update correctly on maintenance read from image files.
https://bugs.kde.org/show_bug.cgi?id=442040 --- Comment #2 from Maik Qualmann --- Incidentally, here Bug 416994 is a possible cause, if you use sidecar files, is preferred over the mapping of XMP metadata by Exiv2 other date metadata. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442040] Date time original does not always update correctly on maintenance read from image files.
https://bugs.kde.org/show_bug.cgi?id=442040 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Maik Qualmann --- We have discussed this topic endlessly. With many images of users, which were edited by many different programs and contained the most abundant date metadata. digiKam does not blindly rely on Exif.DateTimeOriginal, it carries out a ranking. Exif.DateTimeOriginal also has a higher priority. Upload a picture that you think digiKam does not determine the correct creation date, then we'll see. Maik -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442042] ksystemstats: GPU plugin reports 0 C temperature with the new libsensors-based plugins
https://bugs.kde.org/show_bug.cgi?id=442042 --- Comment #1 from Luca Beltrame --- Qt is meant to be 5.15.2, not 5.12.5. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442043] New: ksystemstats: NVMe drive temperature is no longer reported (sensor missing)
https://bugs.kde.org/show_bug.cgi?id=442043 Bug ID: 442043 Summary: ksystemstats: NVMe drive temperature is no longer reported (sensor missing) Product: ksysguard Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The new sensor-based plugins in ksystemstats have lost some features, for example the ability to report temperatures from NVMe drives, a regression from the state before these plugins were merged. Sensors report the temperature correctly. STEPS TO REPRODUCE 1. Search for "NVMe" in the sensors of a plasma system monitor applet OBSERVED RESULT No temperature sensor is found EXPECTED RESULT The temperature sensor should be displayed (like it was before the merge) SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest master (available in About System) KDE Plasma Version: latest master KDE Frameworks Version: latest master Qt Version: 5.15.5 + KDE patches ADDITIONAL INFORMATION sensors output: nvme-pci-0100 Adapter: PCI adapter Composite:+36.9°C (low = -273.1°C, high = +83.8°C) -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442042] New: ksystemstats: GPU plugin reports 0 C temperature with the new libsensors-based plugins
https://bugs.kde.org/show_bug.cgi?id=442042 Bug ID: 442042 Summary: ksystemstats: GPU plugin reports 0 C temperature with the new libsensors-based plugins Product: ksysguard Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY After fixing https://bugs.kde.org/show_bug.cgi?id=442023 (see latest comments there), ksystemstats does not report properly the temperature of my GPU anymore. This started happening after the merge of the new plugins based on libsensors. Note that libsensors reports the temperature properly (see below). STEPS TO REPRODUCE 1. Run ksystemstats (with the fix from bug 442023) 2. Check plasma-systemmonitor or the plasma applets for GPU temperatures OBSERVED RESULT "GPU 1 Temperature 0 C" is displayed EXPECTED RESULT The correct temperature (40 C) should be reported SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest master (available in About System) KDE Plasma Version: latest master KDE Frameworks Version: latest master Qt Version: 5.12.5 + KDE patches ADDITIONAL INFORMATION Kernel version: 5.13.13-1-default "sensors" output: amdgpu-pci-0b00 Adapter: PCI adapter vddgfx: 768.00 mV fan1:1438 RPM (min =0 RPM, max = 3500 RPM) edge: +40.0°C (crit = +85.0°C, hyst = -273.1°C) (emerg = +90.0°C) junction: +40.0°C (crit = +105.0°C, hyst = -273.1°C) (emerg = +110.0°C) mem: +42.0°C (crit = +95.0°C, hyst = -273.1°C) (emerg = +100.0°C) power1:6.00 W (cap = 260.00 W) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442041] Okular advertises ODT support
https://bugs.kde.org/show_bug.cgi?id=442041 Christopher Yeleighton changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||80eeec3a -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442041] New: Okular advertises ODT support
https://bugs.kde.org/show_bug.cgi?id=442041 Bug ID: 442041 Summary: Okular advertises ODT support Product: okular Version: 21.08.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ODT backend Assignee: okular-de...@kde.org Reporter: giecr...@stegny.2a.pl Target Milestone: --- SUMMARY Okular wrongly claims it supports opening ODT files. STEPS TO REPRODUCE 1. Tell Discover to display Okular! 2. 3. OBSERVED RESULT Okular is a handler for ODT. EXPECTED RESULT Okular is not a handler for ODT. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed 20210902 (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
