[frameworks-plasma] [Bug 453830] Plasma unable to detect installed styles
https://bugs.kde.org/show_bug.cgi?id=453830 Rik Mills changed: What|Removed |Added Priority|NOR |VHI Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 453830] Plasma unable to detect installed styles
https://bugs.kde.org/show_bug.cgi?id=453830 Rik Mills changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Rik Mills --- On Kubuntu with 5.94.0, downloaded theme from store.k.o show but system installed themes such as the breeze variants do not. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453866] New: When a brush is assigned to "My favourites" the category still appears in the "Assign to tag" menu
https://bugs.kde.org/show_bug.cgi?id=453866 Bug ID: 453866 Summary: When a brush is assigned to "My favourites" the category still appears in the "Assign to tag" menu Product: krita Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: intu...@protonmail.com Target Milestone: --- SUMMARY *** When a brush is assigned to "My favourites" the category still appears in the "Assign to tag" menu. This can be confusing, because it may prompt one to reassign a brush to my favourites. *** STEPS TO REPRODUCE 1. Open the brush preset docker 2. Right click the brush and assign a random brush to the "My favourites" category 3. Right click the brush again and go to the "assign to tag" menu once again. 4. Notice the category "My favourites" still appears OBSERVED RESULT 4. Notice the category "My favourites" still appears EXPECTED RESULT Just like any other category, the category should disappear from the "Assign to tag" menu if the brush is already assigned to this tag. SOFTWARE/OS VERSIONS Windows: 10 Qt Version: 5.12.12 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 453830] Plasma unable to detect installed styles
https://bugs.kde.org/show_bug.cgi?id=453830 Rik Mills changed: What|Removed |Added CC||rikmi...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 451408] File preview on some locally-mounted drives (NTFS, NFS, SMB) inappropriately use remote preview settings
https://bugs.kde.org/show_bug.cgi?id=451408 --- Comment #30 from Méven Car --- (In reply to Michael Stapelberg from comment #28) > Made an account here just to comment on this issue. > > I was quite surprised when directory previews would no longer show for my > cifs network storage mount. > > Disabling previews by default for this case is fine with me, as long as > there is an option to ignore any limits. > There is one already, Dolphin > configure > Previews > Size limit for network files. It defaults to no files, meaning regardless of a file size no preview will be generated. It applies when you kio to access network mounts aka urls like smb:/ or nfs:/ And until we reverted the change that caused this bug also nfs or smb regular mounts. > My network storage is connected with a 10 Gbit/s link and has plenty of I/O > and CPU capacity, so I really want to make use of file previews on this > “remote” file system in my local network. > Not everyone has a 10Gbit/s link to their mounts, we have to tune things for small capacity. As having things tailored for a lot a resources but not having them is far worse than the opposite. But of course we want to provide the ability to tune things further than our cautious default. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 453835] Some strings in Info Center were not translated into Brazilian Portuguese
https://bugs.kde.org/show_bug.cgi?id=453835 2wxsy5823...@opayq.com changed: What|Removed |Added Product|kinfocenter |i18n Component|general |pt-BR Assignee|plasma-b...@kde.org |kde-i18n-pt...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 453802] Package libjxl
https://bugs.kde.org/show_bug.cgi?id=453802 --- Comment #3 from 2wxsy5823...@opayq.com --- (In reply to charles2000wang from comment #2) > I have libjxl built and installed manually but gwen still can not view the > jxl image. Did you rebuild and install kimageformat-plugins (kimageformats) with libjxl enabled? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 452252] Kate crash on duplicate session
https://bugs.kde.org/show_bug.cgi?id=452252 --- Comment #4 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.
[Skanlite] [Bug 453162] Skanlite crash when scanning one or several selections
https://bugs.kde.org/show_bug.cgi?id=453162 --- 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-pa] [Bug 453865] New: switching audio output device leaves both selected post upgrade to 5.24.5
https://bugs.kde.org/show_bug.cgi?id=453865 Bug ID: 453865 Summary: switching audio output device leaves both selected post upgrade to 5.24.5 Product: plasma-pa Version: 5.24.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: kde.bugtrac...@isfeld.ca CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- Created attachment 148871 --> https://bugs.kde.org/attachment.cgi?id=148871=edit plasma-pa with two audio output devices selected SUMMARY *** switching audio output device leaves both selected post upgrade to 5.24.5 *** STEPS TO REPRODUCE 1. Speakers and USB headphones connected to system, with default audio output device being the speakers 2. open the plasma-pa applet and select the headphones as the new audio output destination 3. note that both audio output destinations are selected (radio buttons filled) OBSERVED RESULT After changing the audio output destination from speakers to headphones, both devices appear to be selected. EXPECTED RESULT After changing the audio output destination from speakers to headphones, the applet should refresh to show that only the headphones are selected as the audio output destination. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.38-1-MANJARO (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I am using Manjaro KDE Plasma, and after the last Manjaro update **KDE Plasma** was updated to **5.24.5**. After applying the update and rebooting, I have an issue in **Audio** applet (**plasma-pa**)where I can swap (once) between my two audio devices (**S/PDIF speakers** => **USB headphones**); however, but both output devices appear selected after the click/swap (see attachment). Once both output devices are selected, switching no longer appears to be possible. My current work around is to unplug/re-plug my USB headset when I want to return to my speakers. And because the swap to headset works via **plasma-pa**, I can swap normally and just ignore the dual-selection. In case it's important to note... I can confirm that only one audio output was really being output to, and seconded this by observing the change in the **KDE System Settings** => **Hardware** => **Audio**. However, if I try switch between my audio devices in **KDE System Settings**, I can replicate the multi-device selection issue... so it's not exclusive to **plasma-pa**. Within **KDE System Settings** I have the advantage of being able to switch between "tabs" (Audio => Multimedia => Audio) to force a refresh to see that really only one device is selected after switching the audio output device there... but I don't know how to force a refresh of **plasma-pa**. Perhaps another way to try explain the issue is that a trigger to refresh **plasma-pa** (and **KDE System Settings**) appears to be missing after a new audio output device is selected (when multiple output devices are available to choose from). In case it's important to note... **pulseaudio** is actually being provided by **pipewire-pulse**. I have been using **pipewire** for a few months now, so that is not new... however, **pipewire** was also updated with the same recent Manjaro update to **pipewire 0.3.51**. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432059] Nvidia Wayland - Yakuake Window Position Is Wrong
https://bugs.kde.org/show_bug.cgi?id=432059 --- Comment #7 from Wyatt Childers --- I should additionally note, I'm on AMD hardware now... so I can't comment as to if there's any remaining nvidia specific issue. I don't see this appear at the top left of the screen, and haven't for a while, but it's still not "in the right spot." -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432059] Nvidia Wayland - Yakuake Window Position Is Wrong
https://bugs.kde.org/show_bug.cgi?id=432059 --- Comment #6 from Wyatt Childers --- (In reply to David Edmundson from comment #4) > I can not reproduce this anymore. It does require some changes in yakuake > which have landed. Given it is window positioning it is unlikely to be > nvidia related. Can you confirm this works with a newer yakuake? Can you give some context as to when those changes "have landed"? What release version are they expected in? I'm running Yakuake 21.12.2 and still see the window appear at centered vertically of my screen, rather than at the top of my screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453864] New: Drawing tablet cursor offsets from actual clicking/hovering position when Global Scaling set to anything other than 100%
https://bugs.kde.org/show_bug.cgi?id=453864 Bug ID: 453864 Summary: Drawing tablet cursor offsets from actual clicking/hovering position when Global Scaling set to anything other than 100% Product: kwin Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- When I set the Global scaling to anything other than 100%, my drawing tablet's cursor is not where the actual clicking/hovering position is. For example, I'm using a Cintiq Pro 24, which is a 4K pen display. When I set the global scaling to 125%, the actual clicking/hovering position of my stylus offsets about 10-20cm lower than the cursor on screen. I began to notice this bug after the lastest KDE/Qt stack update. But I also only changed the global scaling for the firtst time at the same day, so I couldn't be too sure. The bug is affecting all KDE apps and Plasma system apps, including Dolphin, Konsole, Systemsettings and such. It doesn't affect Krita's the official appimage build. Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453844] [Feature Request] Consider exposing more sensors (Encode and Decode) in System Monitor for NVIDIA GPU.
https://bugs.kde.org/show_bug.cgi?id=453844 --- Comment #4 from Samuel --- (In reply to Jack R from comment #3) > (In reply to Samuel from comment #0) > Please change severity to wishlist. I am sorry, but I dont see the option to change Importance from Normal. Is this option hidden somewhere? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 450482] Remote folder previews no longer working after recent update to Plasma 5.24
https://bugs.kde.org/show_bug.cgi?id=450482 --- Comment #18 from AT --- Confirming with arch linux kio 5.94.0-1 resolved issue. Now have thumbnails on files and folders. Yay! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453863] New: Buttons to close the windows not available when filtered
https://bugs.kde.org/show_bug.cgi?id=453863 Bug ID: 453863 Summary: Buttons to close the windows not available when filtered Product: kwin Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: a...@triptech.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. In System Settings > Present Windows > Configure, set Appearance > Provide buttons to close the windows on. 2. Trigger Present Windows Effect (eg CTRL+F10). 3. Type a string to filter to fewer windows (eg "Fir" for Firefox)All windows OBSERVED RESULT A single window (leftmost) is highlighted active and has a close button: all other filtered windows are dimmed and have no close button. No button appears when window is hovered over. The other windows can only be selected, not closed. EXPECTED RESULT All of the filtered windows should display a close button, and be able to close with a single click. This is the case when windows are not filtered, and should be so also when filtered. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.24.4 (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.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #164 from Miguel Guthridge --- Could this be a duplicate of 427861 (https://bugs.kde.org/show_bug.cgi?id=427861)? Now that the crash isn't happening for this one, they appear to be the same issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453862] New: Context menu to remove the widget closes, not allowing to remove the widget
https://bugs.kde.org/show_bug.cgi?id=453862 Bug ID: 453862 Summary: Context menu to remove the widget closes, not allowing to remove the widget Product: plasmashell Version: 5.24.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: andy...@mail.ru Target Milestone: 1.0 Created attachment 148870 --> https://bugs.kde.org/attachment.cgi?id=148870=edit Screencast illustrating the problem. SUMMARY Sometimes, when I try to remove a widget from a panel, the menu disappears as I move the mouse over it. This prevents me from removing the widget. The only workaround I found is to move the widget to the desktop and remove it from there. STEPS TO REPRODUCE 1. Have a widget on a panel. Doesn't really matter what widget it is. 2. Right-click on the panel and Enter Edit Mode. 3. Hover mouse over the widget. A context menu appears with the option to remove the widget. 4. Try to move the mouse over the menu to the remove option. OBSERVED RESULT Sometimes (often) the menu disappears as I move the mouse. See the attached screencast. EXPECTED RESULT The menu should stay open as long as the mouse cursor is over it. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-30-lowlatency (64-bit) Graphics Platform: X11 Processors: 16 × 12th Gen Intel® Core™ i7-12700K Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453784] Add support for Nvidia GPU temps monitoring through nvidia-smi
https://bugs.kde.org/show_bug.cgi?id=453784 Jack R changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Jack R --- (In reply to Lastique from comment #2) > (In reply to Jack R from comment #1) > > This support appears to already exist in System Monitor. > > > > Steps to utilize: > > 1.) Open Plasma System Monitor > > 2.) "Edit Page" (top right) > > 3.) "Add row" or click blue area --> "Add Column" --> Click blue area to > > add a widget > > 4.) Click "Total Sensors" or "Sensors" > > 5.) Click nvidia gpu (probably GPU 0 or 1) > > 6.) Choose "Temperature" or other desired sensor/stat > > > > Please let me know if this isn't working for you > > > > KDE Plasma 5.24.5 Frameworks 5.94 > > Thank you, I found it. > > Though it is located in an unexpected place - all other sensors are in the > Hardware Sensors category, which is where I was looking. Is it possible to > move the sensors in one place? I see what you mean. "Hardware Sensors" is really like the "other" section. That could be a possible feature change, as it is a little confusing. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453784] Add support for Nvidia GPU temps monitoring through nvidia-smi
https://bugs.kde.org/show_bug.cgi?id=453784 Lastique changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Lastique --- (In reply to Jack R from comment #1) > This support appears to already exist in System Monitor. > > Steps to utilize: > 1.) Open Plasma System Monitor > 2.) "Edit Page" (top right) > 3.) "Add row" or click blue area --> "Add Column" --> Click blue area to > add a widget > 4.) Click "Total Sensors" or "Sensors" > 5.) Click nvidia gpu (probably GPU 0 or 1) > 6.) Choose "Temperature" or other desired sensor/stat > > Please let me know if this isn't working for you > > KDE Plasma 5.24.5 Frameworks 5.94 Thank you, I found it. Though it is located in an unexpected place - all other sensors are in the Hardware Sensors category, which is where I was looking. Is it possible to move the sensors in one place? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453480] No image preview for .RW2 files (image/x-panasonic-rw2)
https://bugs.kde.org/show_bug.cgi?id=453480 --- Comment #5 from Andrew --- Today I update to KDE Framework 5.94, but still no thumbnails on RAW images -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453861] New: System settings closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=453861 Bug ID: 453861 Summary: System settings closed unexpectedly Product: systemsettings Version: 5.24.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kevinholgu...@gmail.com Target Milestone: --- Application: systemsettings (5.24.4) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-30-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I updated some fonts The help center crashes too. It opened normal before the update. I updated de mesa drivers, and upgraded everything. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139793478458944) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139793478458944) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139793478458944, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f243971a476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f24397007f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f2439bbeba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f241c385c59 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #11 0x7f241c386d21 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #12 0x55fea5456e78 in ?? () #13 0x55fea545a188 in ?? () #14 0x7f2439e1540e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f243b3976fd in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #16 0x7f243a9f0713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f2439de7e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f2439deaf17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f2439e41a57 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f24379d1d1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f2437a266f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f24379cf3c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f2439e410a8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f2439de674b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f2439deece4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x55fea54511bf in ?? () #27 0x7f2439701d90 in __libc_start_call_main (main=main@entry=0x55fea54506b0, argc=argc@entry=1, argv=argv@entry=0x7ffd3c4b36b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #28 0x7f2439701e40 in __libc_start_main_impl (main=0x55fea54506b0, argc=1, argv=0x7ffd3c4b36b8, init=, fini=, rtld_fini=, stack_end=0x7ffd3c4b36a8) at ../csu/libc-start.c:392 #29 0x55fea5451af5 in ?? () [Inferior 1 (process 3385) detached] Possible duplicates by query: bug 453241, bug 452945, bug 452467, bug 452279, bug 452163. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453844] [Feature Request] Consider exposing more sensors (Encode and Decode) in System Monitor for NVIDIA GPU.
https://bugs.kde.org/show_bug.cgi?id=453844 Jack R changed: What|Removed |Added CC||rubacha.jac...@gmail.com --- Comment #3 from Jack R --- (In reply to Samuel from comment #0) > Created attachment 148862 [details] > Sensors exposed currently in plasma-systemmonitor. > > SUMMARY > Consider exposing more sensors like Encode and Decode sensors for NVIDIA GPU > in Plasma System Monitor. > > OBSERVED RESULT > Currently there are only Memory and Core usage, frequencies and memory size > sensors as shown in the attached image. It would be very helpful to have > Video Encode/Decode sensors in system monitor to have complete monitoring of > NVIDIA GPU in Plasma. > > EXPECTED RESULT > To have more sensors exposed to the user in GPU sensors section like encode, > decode sensors for NVIDIA GPUs. It can be seen from the attached image > showing command-line monitoring of Encoder usage that it is possible to poll > the information using nvidia-smi. > > SOFTWARE/OS VERSIONS > KDE Plasma Version: 5.24.5 > KDE Frameworks Version: 5.93 > Qt Version: 5.15.3 > NVIDIA GeForce GTX 1060 GPU with 510.68 proprietary driver installed. Please change severity to wishlist. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 453788] flatpak (and snap ? ) application desktop entry file not created after installation
https://bugs.kde.org/show_bug.cgi?id=453788 --- Comment #1 from Aleix Pol --- This is flatpak's (or snap's) to do. Also I really cannot reproduce, please be more specific in your bug reports. Explain what you saw and what you expected, instead of what should have been. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453860] [Wayland] Mouse cursor not displayed on Wayland session
https://bugs.kde.org/show_bug.cgi?id=453860 --- Comment #1 from Behzad A --- System Info System:Host: localhost.localdomain Kernel: 5.17.5-1-default x86_64 bits: 64 compiler: gcc v: 12.1.0 Desktop: KDE Plasma 5.24.80 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: openSUSE Tumbleweed 20220513 CPU: Info: Dual Core model: Intel Core2 Duo T6670 bits: 64 type: MCP arch: Penryn rev: A cache: L2: 2 MiB flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 8771 Speed: 1223 MHz min/max: 1200/2201 MHz boost: enabled Core speeds (MHz): 1: 1223 2: 1243 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Sony driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:2a42 Device-2: Ricoh Sony Vaio Integrated Webcam type: USB driver: uvcvideo bus-ID: 3-2:2 chip-ID: 05ca:18b3 Display: x11 server: X.Org 21.1.3 compositor: kwin_x11 driver: loaded: modesetting failed: fbdev,vesa alternate: intel resolution: 1280x800~60Hz s-dpi: 96 OpenGL: renderer: Mesa Mobile Intel GM45 Express (CTG) v: 2.1 Mesa 22.2.0-devel-git-e9e8c649 direct render: Yes -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453860] New: [Wayland] Mouse cursor not displayed on Wayland session
https://bugs.kde.org/show_bug.cgi?id=453860 Bug ID: 453860 Summary: [Wayland] Mouse cursor not displayed on Wayland session Product: kwin Version: git master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: behzad.a...@hotmail.com Target Milestone: --- I now updated to last git version(openSUSE Krypton 22-5-15) and after restart the Mouse cursor disappeared on Wayland session Also related issue https://bugs.kde.org/show_bug.cgi?id=453823 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453859] New: When we enter the user interface, when clicking on the "edit" option, the menu goes completely to the right, and when clicking on another option, it returns to normal.
https://bugs.kde.org/show_bug.cgi?id=453859 Bug ID: 453859 Summary: When we enter the user interface, when clicking on the "edit" option, the menu goes completely to the right, and when clicking on another option, it returns to normal. Product: kdenlive Version: 22.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: m.ro...@outlook.com.br Target Milestone: --- SUMMARY *** When we enter the user interface, when clicking on the "edit" option, the menu goes completely to the right, and when clicking on another option, it returns to normal. *** STEPS TO REPRODUCE 1. Enter the program 2. Click on "edit" option 3. Clicking another option makes it back to normal OBSERVED RESULT When clicking on "edit" the menu moves to the right EXPECTED RESULT When clicking on "edit" the menu should stay in the same place SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.24.4 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453858] New: Dolphin crashed with using eject button after deleted huge files from usb stick
https://bugs.kde.org/show_bug.cgi?id=453858 Bug ID: 453858 Summary: Dolphin crashed with using eject button after deleted huge files from usb stick Product: dolphin Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ose...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.1) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.13.0-41-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Deleted huge size of files then eject external drive with eject button The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 4718] [New LWP 4803] [New LWP 10239] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f342494599f in __GI___poll (fds=0x7ffd13e76ab8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f341fe139c0 (LWP 4688))] Thread 4 (Thread 0x7f3402814700 (LWP 10239)): #0 __GI___libc_read (nbytes=10, buf=0x7f3402813a1e, fd=28) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=28, buf=0x7f3402813a1e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f342237c975 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f342341b416 in pa_mainloop_prepare () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f342341beb4 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f342341bf70 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f342342a11d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f34223ab72c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f342346d609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f3424952133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f34037fe700 (LWP 4803)): #0 0x7f34229f72b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f34229f882b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f34229f929b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f34229f94a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3424f1665b in QEventDispatcherGlib::processEvents (this=0x7f33f4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f3424eba87b in QEventLoop::exec (this=this@entry=0x7f34037fdbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f3424cd4442 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f3424cd5623 in QThreadPrivate::start (arg=0x564128b901b0) at thread/qthread_unix.cpp:331 #8 0x7f342346d609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f3424952133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f341e186700 (LWP 4718)): #0 0x7ffd13fd0a67 in clock_gettime () #1 0x7f34249100b5 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f341e185920) at ../sysdeps/unix/sysv/linux/clock_gettime.c:38 #2 0x7f3424f15f25 in qt_clock_gettime (ts=0x7f341e185920, clock=1) at kernel/qelapsedtimer_unix.cpp:175 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f3424f147bd in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f3410004d50) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f3424f14d99 in QTimerInfoList::timerWait (this=0x7f3410004d50, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f3424f163b6 in timerSourcePrepareHelper (timeout=0x7f341e1859e4, src=) at kernel/qeventdispatcher_glib.cpp:162 #8 timerSourcePrepare (source=, timeout=0x7f341e1859e4) at kernel/qeventdispatcher_glib.cpp:166 #9 0x7f34229f88ef in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f34229f929b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f34229f94a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f3424f1665b in QEventDispatcherGlib::processEvents (this=0x7f341b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7f3424eba87b in QEventLoop::exec (this=this@entry=0x7f341e185bb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #14 0x7f3424cd4442 in QThread::exec (this=) at
[systemsettings] [Bug 453827] Untranslated sentence in the systemsettings
https://bugs.kde.org/show_bug.cgi?id=453827 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||5.95 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 453388] Unable to empty the volume label of FAT32.
https://bugs.kde.org/show_bug.cgi?id=453388 Andrius Štikonas changed: What|Removed |Added Version Fixed In||22.08.0 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 453388] Unable to empty the volume label of FAT32.
https://bugs.kde.org/show_bug.cgi?id=453388 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/syst ||em/kpmcore/commit/fd4a33088 ||79fcf4e59c3f9c199c28c95d044 ||40f5 --- Comment #2 from Andrius Štikonas --- Git commit fd4a3308879fcf4e59c3f9c199c28c95d04440f5 by Andrius Štikonas. Committed on 15/05/2022 at 22:20. Pushed by stikonas into branch 'master'. Allow setting empty FAT label. This breaks compatibility with dosfstools 4.1 M +2-3src/fs/fat12.cpp https://invent.kde.org/system/kpmcore/commit/fd4a3308879fcf4e59c3f9c199c28c95d04440f5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453827] Untranslated sentence in the systemsettings
https://bugs.kde.org/show_bug.cgi?id=453827 Nicolas Fella changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/knewstuff/commit/667 ||327a617fa41ad17e85e34ed3ff2 ||95def5a6e0 --- Comment #1 from Nicolas Fella --- Git commit 667327a617fa41ad17e85e34ed3ff295def5a6e0 by Nicolas Fella. Committed on 15/05/2022 at 16:16. Pushed by nicolasfella into branch 'master'. Add missing translation domain M +1-1src/qtquick/qml/Page.qml https://invent.kde.org/frameworks/knewstuff/commit/667327a617fa41ad17e85e34ed3ff295def5a6e0 -- 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 Andrius Štikonas changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 449770] Mobile-specific Search UI does not go away when you leave Mobile mode
https://bugs.kde.org/show_bug.cgi?id=449770 Matej Starc changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/commit/7226c296 |ma/discover/commit/d87463a5 |03f4cccf4d364f5e9472c3827a4 |94fb5f00e92289b76e623808b80 |440dd |4a5f2 --- Comment #6 from Matej Starc --- Git commit d87463a594fb5f00e92289b76e623808b804a5f2 by Matej Starc. Committed on 15/05/2022 at 14:40. Pushed by apol into branch 'master'. unfocus text field on UI mode change In last commit of fixing mobile search field, I didn't change focus on UI mode change. M +1-1discover/qml/SearchPage.qml https://invent.kde.org/plasma/discover/commit/d87463a594fb5f00e92289b76e623808b804a5f2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #163 from Jacek Wieczorek --- I think Gene might be right. The crash may be just partially covering up the symptoms of this bug by restarting the Plasma automatically. After a couple of attempts more (and perhaps longer periods of screen sleep), I managed to get some missing wallpapers etc., so sadly I can't say that the problem is gone. At least the panel layout seems to be always correct now (probably due to the restarts) I'll be opening a bug report for the crash shortly. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453857] New: malloc() aborts during save
https://bugs.kde.org/show_bug.cgi?id=453857 Bug ID: 453857 Summary: malloc() aborts during save Product: kmymoney Version: 5.1.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: alex.me...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open an existing KMyMoney file 2. Make a change 3. Press the Save button on the toolbar OBSERVED RESULT KMyMoney crashed, and lost the change. EXPECTED RESULT The change was saved to the file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION BACKTRACE malloc(): corrupted top size Thread 1 "kmymoney" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading 0.00 MB source file /usr/src/debug/glibc/nptl/pthread_kill.c 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; gdb$ bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x758563d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x75806838 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x757f0535 in __GI_abort () at abort.c:79 #4 0x7584a45e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7598883e "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #5 0x758600cc in malloc_printerr (str=str@entry=0x759863de "malloc(): corrupted top size") at malloc.c:5664 #6 0x758638dc in _int_malloc (av=av@entry=0x759c6bc0 , bytes=bytes@entry=104) at malloc.c:4373 #7 0x75864358 in __GI___libc_malloc (bytes=bytes@entry=104) at malloc.c:3329 #8 0x75b8537d in operator new(unsigned long) (sz=sz@entry=104) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/new_op.cc:50 #9 0x77311c4b in QDomElementPrivate::setAttribute(QString const&, QString const&) (newValue=..., aname=..., this=0x5a2cf500) at dom/qdom.cpp:3960 #10 QDomElementPrivate::setAttribute(QString const&, QString const&) (this=0x5a2cf500, aname=..., newValue=...) at dom/qdom.cpp:3956 #11 0x7fff8dbbfd01 in () at /usr/lib/qt/plugins/kmymoney/xmlstorage.so #12 0x7fff8dbcd51d in () at /usr/lib/qt/plugins/kmymoney/xmlstorage.so #13 0x7fff8dbcc6aa in () at /usr/lib/qt/plugins/kmymoney/xmlstorage.so #14 0x7fff8dbb89d6 in () at /usr/lib/qt/plugins/kmymoney/xmlstorage.so #15 0x7fff8dbb941b in () at /usr/lib/qt/plugins/kmymoney/xmlstorage.so #16 0x55649911 in () #17 0x760cbc41 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffd0c0, r=, this=0x5615cb10, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate(QObject*, int, void**) (sender=0x5615c910, signal_index=4, argv=0x7fffd0c0) at kernel/qobject.cpp:3886 #19 0x76b81e07 in QAction::triggered(bool) (this=this@entry=0x5615c910, _t1=) at .moc/moc_qaction.cpp:376 #20 0x76b87817 in QAction::activate(QAction::ActionEvent) (this=0x5615c910, event=) at kernel/qaction.cpp:1161 #21 0x76c764ce in QAbstractButtonPrivate::click() (this=0x55ed3020) at widgets/qabstractbutton.cpp:399 #22 0x76c766d0 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) (this=0x55ed3d20, e=0x7fffd650) at widgets/qabstractbutton.cpp:1045 #23 0x76d6894f in QToolButton::mouseReleaseEvent(QMouseEvent*) (this=, e=) at widgets/qtoolbutton.cpp:622 #24 0x76bc5677 in QWidget::event(QEvent*) (this=0x55ed3d20, event=0x7fffd650) at kernel/qwidget.cpp:8659 #25 0x76b8ea7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x559746a0, receiver=receiver@entry=0x55ed3d20, e=e@entry=0x7fffd650) at kernel/qapplication.cpp:3637 #26 0x76b94289 in QApplication::notify(QObject*, QEvent*) (this=, receiver=, e=0x7fffd650) at kernel/qapplication.cpp:3081 #27 0x7609b4a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55ed3d20, event=0x7fffd650) at kernel/qcoreapplication.cpp:1064 #28 0x76b92287 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) (receiver=0x55ed3d20, event=0x7fffd650, alienWidget=, nativeWidget=0x55ece6d0, buttonDown=, lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2619
[frameworks-kservice] [Bug 442011] kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated
https://bugs.kde.org/show_bug.cgi?id=442011 --- Comment #6 from Yosuke Matsumura --- Sorry, it seems my analysis was mistaken and this patch does not fix the "findInCache with a lastModified timestamp of 0 is deprecated" message, but does fix usability of Kinoite when set to UTC timezone. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453160] In the slide manager the pointer is good but it comes with the black background otherwise it's look cool
https://bugs.kde.org/show_bug.cgi?id=453160 sjo...@famseinhorst.nl changed: What|Removed |Added CC||sjo...@famseinhorst.nl Summary|In the slide manage r the |In the slide manager the |pointer is good but it |pointer is good but it |comes with the black|comes with the black |background otherwise it's |background otherwise it's |look cool |look cool --- Comment #1 from sjo...@famseinhorst.nl --- Same here on Arch, BSPWM 0.9.10, xorg-server 21.1.3, kdeconnect 22.04.1. When the Pointer button is held down on my Android phone, the computer screen turns black with only the blue pointer ring and the mouse pointer showing. The blue pointer ring does its animation and moves with the phone, but the feature is useless this way. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 452340] Instant crash on Android
https://bugs.kde.org/show_bug.cgi?id=452340 --- Comment #9 from Albert Astals Cid --- (In reply to Aachman (AarKiMos) from comment #8) > Log says 'failed to find libssl3' but its in the apk. Crashes on android 12 > may be explained with this > https://developer.android.com/about/versions/12/behavior-changes-12#uses- > native-library > TLDR: need to add tag to manifest for each non-NDK > native lib. > Seems to be a simple fix but there might be quite a lot of libs. I don't think that applies here, see the sentence Non-NDK native shared libraries that are provided by silicon vendors or device manufacturers are not accessible by default if the app is targeting Android 12 (API level 31) or higher. We're neither a "silicon vendors or device manufacturers" nor we're targetting "API level 31" -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 453711] PDF form-filling some fields fail or don't print
https://bugs.kde.org/show_bug.cgi?id=453711 --- Comment #5 from Albert Astals Cid --- Wait, why is this bug being CC'ed to 11 people, did you add all those? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 453711] PDF form-filling some fields fail or don't print
https://bugs.kde.org/show_bug.cgi?id=453711 --- Comment #4 from Albert Astals Cid --- (In reply to Bill Dietrich from comment #2) > Please try typing "123-" into Social Security Number field. Ah yes, don't write the - it gets written automatically for you :) But yes, that needs fixing > For check-marks problem: open document, show forms, check box 1B "Normal > Distribution–Roth IRAs", then check box subordinate to that one, "This is a > Qualified Distribution". Save document. Open document again, look at those > two check-boxes. Box 1B "Normal Distribution–Roth IRAs" will be un-checked. Can not reproduce -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 453563] Filter possibility gone
https://bugs.kde.org/show_bug.cgi?id=453563 Stefano Crocco changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/konqueror/commit/7efa0d ||97a98e6786aa80ed58a5a463c5a ||134bf11 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Stefano Crocco --- Git commit 7efa0d97a98e6786aa80ed58a5a463c5a134bf11 by Stefano Crocco. Committed on 15/05/2022 at 12:20. Pushed by dfaure into branch 'master'. Install the dirfilterplugin in the dolphinpart/kpartsplugin directory M +2-1plugins/dirfilter/CMakeLists.txt https://invent.kde.org/network/konqueror/commit/7efa0d97a98e6786aa80ed58a5a463c5a134bf11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 452532] kdesu stopped working in KUbuntu due to sudo's use_pty option
https://bugs.kde.org/show_bug.cgi?id=452532 Ahmad Samir changed: What|Removed |Added Summary|kdesu not working after |kdesu stopped working in |upgrade from kUbuntu 21.10 |KUbuntu due to sudo's |to 22.04|use_pty option -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453856] New: Free space not correctly detected on nested remote mount
https://bugs.kde.org/show_bug.cgi?id=453856 Bug ID: 453856 Summary: Free space not correctly detected on nested remote mount Product: dolphin Version: 21.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ad...@hifiphile.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When multiple remote mount points are mounted on a single mount point using sshfs in a nested way, free space of sub mount points are not detected correctly, free space of root mount point is used for all sub mount points. == Server == Multiple volumes are exported with SFTPGo, with /var/run as the root mount point. > df -h > Filesystem Size Used Avail Use% Mounted on > tmpfs 4G 0 4G1% /var/run > MNT110T1M10T 1% /MNT1 > MNT210T456K 10T 1% /MNT2 == Client == KDE is installed on this system. These volumes are mounted with sshfs. > tree -L 1 /mnt/sftp/ > /mnt/sftp/ > ├── MNT1 > ├── MNT2 "df" can show free spaces of sub mount points correctly: >df -h /mnt/sftp/ >Filesystem Size Used Avail Use% Mounted on >f...@.com: 4G 0 4G0% /mnt/sftp > >df -h /mnt/sftp/MNT1 >Filesystem Size Used Avail Use% Mounted on >f...@.com: 10T1M 10T1% /mnt/sftp STEPS TO REPRODUCE 1. Create a volume on a remote server, for example `mount -t tmpfs tmpfs /mnt/submnt -o size=1g`, expose /mnt with sshfs. 2. On client mount /mnt with sshfs, confirm "df" can show free space of /mnt and /mnt/submnt correctly. 3. Enter /mnt/submnt with Dolphin, free space of /mnt is showed instead of /mnt/submnt, copy file into /mnt/submnt also limited by the free sapce of /mnt OBSERVED RESULT Copy file into sub mount points will fail with "not enough space" if root mount point is not large enough. "Free space" display of bottom bar always show the free space of root mount point even inside a sub mount point. EXPECTED RESULT Free space of current mount point should be used instead of root mount point. Something like `df $PWD` instead of `df /` SOFTWARE/OS VERSIONS Linux/KDE Plasma: 21.12 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364321] UI to switch from JEDEC to SI units
https://bugs.kde.org/show_bug.cgi?id=364321 --- Comment #27 from Nate Graham --- This is what happens to hidden options: the feature they controls bit-rots because it's not being regularly tested. The fact that this is happening is a strong argument to me in favor of exposing it in the UI so more people can use it and the codepaths it enabled get more use. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364321] UI to switch from JEDEC to SI units
https://bugs.kde.org/show_bug.cgi?id=364321 --- Comment #26 from Erik Quaeghebeur --- (In reply to vmelkon from comment #25) > I would much prefer to have a bug free implementation rather than an Option > in the UI. Bug 57240's last comment mentioned that apps that do not respect BinaryUnitDialect should receive a bug report. I've done this now for Dolphin (Bug 453853) and system settings (Bug 453854). I'd like to encourage everyone here to look at their favorite apps and see whether they respect the option or not. If not, please file a bug report for them. You could use my reports for Dolphin and system settings are inspiration/a template. It may be useful to always put Bug 57240 in ‘Depends on’ (just the number suffices) and this bug, Bug 364321, in ‘Blocks’ (toggle advanced fields if needed). That way, we can use this bug to track adherence of apps. (I would say this is a soft block, as the UI implementation need not wait for fixes landing with the apps. If some developer prefers a different organization of all these bugs, go ahead, I do not mind, as long as we can get an overview.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453840] digiKam git build error with ffmpeg 5
https://bugs.kde.org/show_bug.cgi?id=453840 --- Comment #11 from maderios --- I remember now I used a ffmpeg5.patch, that's why i could build digikam git with ffmpeg 5 one month ago I don't know if it works now https://aur.archlinux.org/cgit/aur.git/tree/ffmpeg5.patch?h=digikam-git -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 453855] Cannot get developer information or report bugs due to error: /ui/DeveloperPage.qml:68 Type RatingItem unavailable
https://bugs.kde.org/show_bug.cgi?id=453855 --- Comment #1 from Oded Arbel --- Probably related to this commit: https://invent.kde.org/plasma/drkonqi/-/commit/48f2e7606ad08ff7f4394e793ea9b0cfd82babd2 -- 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 Andrius Štikonas changed: What|Removed |Added Status|REOPENED|RESOLVED Version Fixed In||22.08.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 453855] New: Cannot get developer information or report bugs due to error: /ui/DeveloperPage.qml:68 Type RatingItem unavailable
https://bugs.kde.org/show_bug.cgi?id=453855 Bug ID: 453855 Summary: Cannot get developer information or report bugs due to error: /ui/DeveloperPage.qml:68 Type RatingItem unavailable Product: drkonqi Version: master Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: backtraceparsing Assignee: plasma-b...@kde.org Reporter: o...@geek.co.il Target Milestone: --- Running neon jammy unstable SUMMARY When DrKonqi opens after an application crash, trying to report a bug and clicking "Next" from "What do You Know About the Crash", nothing happens in the UI and in the console the following message is shown: QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:878: Error: Error while loading page: qrc:/ui/DeveloperPage.qml:68 Type RatingItem unavailable qrc:/ui/RatingItem.qml:14 Duplicate property name SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.24.5+p22.04+tunstable+git20220511.0116-0 KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364321] UI to switch from JEDEC to SI units
https://bugs.kde.org/show_bug.cgi?id=364321 Erik Quaeghebeur changed: What|Removed |Added Depends on||453854 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=453854 [Bug 453854] Please follow BinaryUnitDialect, appropriately -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 57240] Display file size in kibibyte, mebibyte... ?
https://bugs.kde.org/show_bug.cgi?id=57240 Erik Quaeghebeur changed: What|Removed |Added Blocks||453854 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=453854 [Bug 453854] Please follow BinaryUnitDialect, appropriately -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453854] New: Please follow BinaryUnitDialect, appropriately
https://bugs.kde.org/show_bug.cgi?id=453854 Bug ID: 453854 Summary: Please follow BinaryUnitDialect, appropriately Product: plasma-systemmonitor Version: 5.24.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: bugs.kde@e3q.eu CC: ahiems...@heimr.nl, plasma-b...@kde.org Depends on: 57240 Blocks: 364321 Target Milestone: --- SUMMARY The system monitor does not seem to follow the BinaryUnitDialect config option. Likely it is just a matter of replacing some function with some higher-level ones, as other apps do the right thing (e.g., Krusader). STEPS TO REPRODUCE 1. Set BinaryUnitDialect=2 in [Locale] section of $KDEHOME/.config/kdeglobals (setting to metric/SI instead of IEC) 2. Start system monitor 3. Look at some of the stats showing OBSERVED RESULT IEC formatting is used everywhere instead of metric EXPECTED RESULT Metric formatting is used everywhere it is appropriate (I think the only place IEC might make sense is for memory size and usage when a preference for metric is expressed) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION The BinaryUnitDialect config option is described in Bug 57240. This option is for now still without a GUI, but Bug 364321 makes it clear this is about to change. So apps like the system monitor should be made ready to follow BinaryUnitDialect. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=57240 [Bug 57240] Display file size in kibibyte, mebibyte... ? https://bugs.kde.org/show_bug.cgi?id=364321 [Bug 364321] UI to switch from JEDEC to SI units -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435414] Enhancement of "Edit Metadata..."
https://bugs.kde.org/show_bug.cgi?id=435414 --- Comment #6 from Maik Qualmann --- This bug report is quite sufficient for problem (2). Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 452532] kdesu not working after upgrade from kUbuntu 21.10 to 22.04
https://bugs.kde.org/show_bug.cgi?id=452532 golgeadam changed: What|Removed |Added Summary|kdesu not working after |kdesu not working after |upgrade from Ubuntu 20.04 |upgrade from kUbuntu 21.10 |to 22.04|to 22.04 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 452532] kdesu not working after upgrade from Ubuntu 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=452532 golgeadam changed: What|Removed |Added CC||golgead...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364321] UI to switch from JEDEC to SI units
https://bugs.kde.org/show_bug.cgi?id=364321 Erik Quaeghebeur changed: What|Removed |Added Depends on||453853 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=453853 [Bug 453853] file size display: please follow BinaryUnitDialect everywhere -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 57240] Display file size in kibibyte, mebibyte... ?
https://bugs.kde.org/show_bug.cgi?id=57240 Erik Quaeghebeur changed: What|Removed |Added Blocks||453853 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=453853 [Bug 453853] file size display: please follow BinaryUnitDialect everywhere -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453853] New: file size display: please follow BinaryUnitDialect everywhere
https://bugs.kde.org/show_bug.cgi?id=453853 Bug ID: 453853 Summary: file size display: please follow BinaryUnitDialect everywhere Product: dolphin Version: 21.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugs.kde@e3q.eu CC: kfm-de...@kde.org Depends on: 57240 Blocks: 364321 Target Milestone: --- SUMMARY Dolphin does not seem to follow the BinaryUnitDialect config option everywhere. Likely it is just a matter of replacing some function with some higher-level ones, as in a few places, Dolphin does do the right thing. STEPS TO REPRODUCE 1. Set BinaryUnitDialect=2 in [Locale] section of $KDEHOME/.config/kdeglobals (setting to metric/SI instead of IEC) 2. Start Dolphin 3. Open some folder with files, select, hover, etc. OBSERVED RESULT Mostly IEC formatting is used instead of metric (metric is used in the status bar when selecting/hovering over a file and also for showing the available disc space) EXPECTED RESULT Metric formatting is used everywhere SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION The BinaryUnitDialect config option is described in Bug 57240. This option is for now still without a GUI, but Bug 364321 makes it clear this is about to change. So apps like Dolphin should be made ready to follow BinaryUnitDialect. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=57240 [Bug 57240] Display file size in kibibyte, mebibyte... ? https://bugs.kde.org/show_bug.cgi?id=364321 [Bug 364321] UI to switch from JEDEC to SI units -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453852] New: ProPhoto RGB gamut MIA
https://bugs.kde.org/show_bug.cgi?id=453852 Bug ID: 453852 Summary: ProPhoto RGB gamut MIA Product: krita Version: 5.0.6 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: major Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: heurihermi...@gmail.com Target Milestone: --- Created attachment 148869 --> https://bugs.kde.org/attachment.cgi?id=148869=edit Profile popup menu in Convert Image Color Space… dialog, showing absence of ProPhoto RGB SUMMARY *** ProPhoto RGB no longer appears as an option when changing color spaces. *** STEPS TO REPRODUCE 1. Open Krita. 2. Open file. 3. Select Convert Image Color Space… 4. Select Profile popup menu. OBSERVED RESULT ProPhoto RGB is not listed. EXPECTED RESULT ProPhoto RGB is listed. SOFTWARE/OS VERSIONS Windows: macOS: Krita 5.0.6, Monterey 12.3.1 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Attempts to follow instructions on https://krita.org/en/get-involved/report-a-bug/ proved impossible because krita-artists will not allow a new registrant to post the description as a possible bug. In addition, an attempt to report this fact proved impossible. -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 453851] New: Flathub package
https://bugs.kde.org/show_bug.cgi?id=453851 Bug ID: 453851 Summary: Flathub package Product: kmplot Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: matth...@mailaender.name Target Milestone: --- Hi, I created https://github.com/flathub/flathub/pull/3153 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 453850] New: Flathub package
https://bugs.kde.org/show_bug.cgi?id=453850 Bug ID: 453850 Summary: Flathub package Product: KBibTeX Version: 0.9.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Compiling/packaging Assignee: fisc...@unix-ag.uni-kl.de Reporter: matth...@mailaender.name Target Milestone: --- Hi, I created https://github.com/flathub/flathub/pull/3152 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453849] New: Dolphin doesn't save last opened directory when shutting down computer
https://bugs.kde.org/show_bug.cgi?id=453849 Bug ID: 453849 Summary: Dolphin doesn't save last opened directory when shutting down computer Product: dolphin Version: 21.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: equ...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When computer is shut down, last opened directories STEPS TO REPRODUCE 1. Open Dolphin. Observe that it restored last opened directories. 2. Navigate to some other directory. 3. Shut down computer without closing Dolphin. 4. Boot up computer. 4. Open Dolphin. OBSERVED RESULT Dolphin opens the same directory as in p. 1 EXPECTED RESULT Dolphin opens the same directory as in p. 2 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Dolphin: 21.12.2 ADDITIONAL INFORMATION I use Plasma with Wayland. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453840] digiKam git build error with ffmpeg 5
https://bugs.kde.org/show_bug.cgi?id=453840 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Digikam git build error |digiKam git build error |with 'digikamwidgets' |with ffmpeg 5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453840] Digikam git build error with 'digikamwidgets'
https://bugs.kde.org/show_bug.cgi?id=453840 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #10 from caulier.gil...@gmail.com --- I'm sure digiKam core (and now QtAV code hosted in digiKam) do not compile with ffmpeg 5. this is your problem... -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 453567] endless reminder notifications
https://bugs.kde.org/show_bug.cgi?id=453567 --- Comment #2 from Martin Koller --- Another detail: the event at 6:00 is a recurring (endless every monday) event. The other event at 9:00 is a single event but even removing the reminder setting completely in that event does not stop kalendarac to keep sending the reminder notification message. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453848] Plasma themes not show in Kcm
https://bugs.kde.org/show_bug.cgi?id=453848 Antonio Rojas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 453830 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 453830] Plasma unable to detect installed styles
https://bugs.kde.org/show_bug.cgi?id=453830 Antonio Rojas changed: What|Removed |Added CC||timofeevsv1...@gmail.com --- Comment #2 from Antonio Rojas --- *** Bug 453848 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 453167] Window close icon does not match icon theme
https://bugs.kde.org/show_bug.cgi?id=453167 --- Comment #4 from Artem Grinev --- (In reply to Nate Graham from comment #3) > Artem, is there anything we can do here? Is this fixed by > https://invent.kde.org/plasma/breeze-gtk/-/merge_requests/56? No, it fixes https://bugs.kde.org/show_bug.cgi?id=449876 for dialogs Technically this particular bug is a Breeze Icons issue which should provide correct default gtk icons. Libadwaita uses them and not our injections of KWin's decorations. So maybe this should be moved there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441910] plasmashell re-reads zoneinfo file many times every second
https://bugs.kde.org/show_bug.cgi?id=441910 --- Comment #6 from V --- (In reply to Nate Graham from comment #5) > Interesting. Cannot reproduce with git master everything KDE on top of > Fedora 36. Are you still using 5.18.6 with openSUSE Leap 15.2? I have upgraded to openSUSE Leap 15.3 however the new distro version still has the same version of KDE. Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 Possibly they make some backports from the current version same as they do with the kernel, still I think that the reason of this bug is an old KDE version. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453848] New: Plasma themes not show in Kcm
https://bugs.kde.org/show_bug.cgi?id=453848 Bug ID: 453848 Summary: Plasma themes not show in Kcm Product: systemsettings Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_style Assignee: plasma-b...@kde.org Reporter: timofeevsv1...@gmail.com CC: zom...@yandex.ru Target Milestone: --- After update Kcm where plasma-desktop themes is empty STEPS TO REPRODUCE 1. Use arch linux 2. Update 3. Open Kcm with plasma themes... and... "No items found" OBSERVED RESULT It is empty EXPECTED RESULT Atleast breeze themes must be shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (Arch) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453847] "Save New Brush Preset" or "Overwrite Brush Preset" causes the current window to lock.
https://bugs.kde.org/show_bug.cgi?id=453847 thalia.adkins.cov...@gmail.com changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453847] New: "Save New Brush Preset" or "Overwrite Brush Preset" causes the current window to lock.
https://bugs.kde.org/show_bug.cgi?id=453847 Bug ID: 453847 Summary: "Save New Brush Preset" or "Overwrite Brush Preset" causes the current window to lock. Product: krita Version: 5.0.6 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: thalia.adkins.cov...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open Krita, either creating a new canvas or opening an existing one. 2. Open the Brush Editor. 3. Select either "Save New Brush Preset" or "Overwrite Brush Preset." OBSERVED RESULT The brush editor window locks and makes all buttons within it unclickable. This is only solved by quitting the program. This is not observed in current builds of Windows versions. EXPECTED RESULT A window usually pops up asking for the name of the new brush to be saved and an icon to be selected for the preset. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications
https://bugs.kde.org/show_bug.cgi?id=451612 --- Comment #22 from Oleksandr Bezushko --- I haven't been able to reproduce this crash for the last 4 days. All windows are configured to be borderless and maximized on my device (by using Window Rules). Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.7-257-tkg-bmq (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.
[kdeplasma-addons] [Bug 453659] Option to display pressure in Pascals
https://bugs.kde.org/show_bug.cgi?id=453659 --- Comment #5 from Nate Graham --- You would file a bug report asking for it. But why would you want milipascals? What's the use case? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 453167] Window close icon does not match icon theme
https://bugs.kde.org/show_bug.cgi?id=453167 Nate Graham changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||agrine...@gmail.com --- Comment #3 from Nate Graham --- Artem, is there anything we can do here? Is this fixed by https://invent.kde.org/plasma/breeze-gtk/-/merge_requests/56? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 449876] Breeze GTK still uses circled closed button by default
https://bugs.kde.org/show_bug.cgi?id=449876 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Nate Graham --- OK, thanks. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 453822] Konqueror reports an undocumented error on a fresh Debian Stable (11.3) install
https://bugs.kde.org/show_bug.cgi?id=453822 --- Comment #3 from Stefano Crocco --- It's not a Debian issue, because after reading your bug report I found out the same happens on my Gentoo system, too (I usually start Konqueror using Krunner, so I never noticed that before). I'll have to investigate why the Application Launcher chooses the wrong program to put in the taskbar. As I know nothing about how the Application Launcher does so, I'll have to ask on the plasma mailing list. In the meanwhile, I've started a merge request (https://invent.kde.org/network/konqueror/-/merge_requests/122) which should fix the symptoms, if not the cause of the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441910] plasmashell re-reads zoneinfo file many times every second
https://bugs.kde.org/show_bug.cgi?id=441910 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #5 from Nate Graham --- Interesting. Cannot reproduce with git master everything KDE on top of Fedora 36. Are you still using 5.18.6 with openSUSE Leap 15.2? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453840] Digikam git build error with 'digikamwidgets'
https://bugs.kde.org/show_bug.cgi?id=453840 --- Comment #9 from maderios --- I forgot to say ffmpeg4.4 is already installed on my system => I have two installed ffmpeg on my system: 5 and 4 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452397] [Wayland] Cannot change resolution in external monitor
https://bugs.kde.org/show_bug.cgi?id=452397 Nate Graham changed: What|Removed |Added Version Fixed In||5.25 Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #15 from Nate Graham --- Thanks for testing! Those seem like other issues. Can you file bug reports for them separately? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450062] Plasma 5.24 + Wayland: When disconnecting 2nd monitor, icon positions get reset
https://bugs.kde.org/show_bug.cgi?id=450062 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Nate Graham --- Not everything has been backported yet. Please re-test with 5.25. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453833] import gradients bundle but gradients don't show, + svg import fails
https://bugs.kde.org/show_bug.cgi?id=453833 Ahab Greybeard changed: What|Removed |Added CC||ha...@valdyas.org --- Comment #2 from Ahab Greybeard --- *** Bug 453624 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453624] svg/stop gradients are always saved as "unnamed.svg"
https://bugs.kde.org/show_bug.cgi?id=453624 Ahab Greybeard changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ahab.greybe...@hotmail.co.u ||k --- Comment #3 from Ahab Greybeard --- There is a closely related bug with a report of additional problems in this area so I'll mark this report as a Duplicate pointing to the more detailed one. *** This bug has been marked as a duplicate of bug 453833 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453840] Digikam git build error with 'digikamwidgets'
https://bugs.kde.org/show_bug.cgi?id=453840 --- Comment #8 from maderios --- I discover last time i built successfully Digikam git was on April 4 2022 At this date, ffmpeg 5.0-5 was already installed on my (updated) system https://github.com/archlinux/svntogit-packages/commits/packages/ffmpeg/trunk So, I think my build error doesn't come from ffmpeg 5 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 453822] Konqueror reports an undocumented error on a fresh Debian Stable (11.3) install
https://bugs.kde.org/show_bug.cgi?id=453822 --- Comment #2 from Alexander Ewering --- (In reply to Stefano Crocco from comment #1) > The problem is not Konqueror itself, as you can see launching Konqueror from > KRunner (Alt-F2) or from the "Internet" section of Application Launcher (K > menu). The behavior you see is caused from the fact that the icon on the > taskbar (as the one in the "Favourite" section of the Application Launcher) > points not to Konqueror itself but to an internal program used by Konqueror > and which isn't supposed to be launched by the user because it requires a > command line argument which can't be given when clicking on an icon. OK thanks, so this should probably be reported to the Debian maintainers? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 453846] Running spectacle under wayland gives a message "Could not take a screenshot. Please report this bug here.
https://bugs.kde.org/show_bug.cgi?id=453846 --- Comment #1 from DaveK --- Spectacle version 21.12.3. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453840] Digikam git build error with 'digikamwidgets'
https://bugs.kde.org/show_bug.cgi?id=453840 --- Comment #7 from Maik Qualmann --- FFmpeg 5 requires major adjustments, I hope Arch Linux still has 4.4.x available. Maik -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453845] dolphin file manager loses nanosecond precision on date and time stamp on copied files and folders
https://bugs.kde.org/show_bug.cgi?id=453845 --- Comment #3 from matthewwilson86...@gmail.com --- (In reply to matthewwilson86.mw from comment #0) > Created attachment 148865 [details] > original sub-folders with nanosecond precision and copied sub-folders with > nanosecond precision lost > > STEPS TO REPRODUCE > 1. Within dolphin file manager select the folder to copy (the folder name in > my case is 'which' - it is a folder used for 'Which?magazine' ralated data > and has sub-folders within it and sub-folders and files within those > sub-folders) > 2. Ctrl-C to copy the folder named 'which' > 3. navigate to the folder where the folder (and sub-folder's and files need > to be copied to) > 4. Ctrl-v to paste > 5. after copying is done, open a terminal window and issue command: > ls -la --time-style=full-iso > > OBSERVED RESULT > > The output in terminal window: > > [j@j-void 211123]$ ls -la --time-style=full-iso > total 24 > drwxr-xr-x 6 j j 4096 2022-03-22 22:43:57.0 +0700 . > drwxr-xr-x 4 j j 4096 2022-03-22 22:43:32.0 +0700 .. > drwxr-xr-x 2 j j 4096 2022-03-22 22:44:21.0 +0700 cancellation > drwxr-xr-x 2 j j 4096 2021-12-02 15:28:02.0 +0700 join > drwxr-xr-x 3 j j 4096 2022-03-22 22:44:21.0 +0700 reviews > drwxr-xr-x 2 j j 4096 2022-03-22 22:44:21.0 +0700 terms > [j@j-void 211123]$ > > EXPECTED RESULT > > [j@j-void 211123]$ ls -la --time-style=full-iso > total 28 > drwxr-xr-x 1 root root 4096 2022-03-22 22:43:57.546506217 +0700 . > drwxr-xr-x 1 root root 4096 2022-03-22 22:43:32.156505366 +0700 .. > -rw--- 1 root root 192 2022-03-22 22:43:57.545506217 +0700 .directory > drwxr-xr-x 1 root root 4096 2022-03-22 22:44:21.119507007 +0700 cancellation > drwxr-xr-x 1 root root 4096 2021-12-02 15:28:02.373914765 +0700 join > drwxr-xr-x 1 root root 4096 2022-03-22 22:44:21.116507007 +0700 reviews > drwxr-xr-x 1 root root 4096 2022-03-22 22:44:21.113507007 +0700 terms > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: void linux 5.15.36_1/xfce 4.16 > (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.
[dolphin] [Bug 453845] dolphin file manager loses nanosecond precision on date and time stamp on copied files and folders
https://bugs.kde.org/show_bug.cgi?id=453845 matthewwilson86...@gmail.com changed: What|Removed |Added Attachment #148865|0 |1 is obsolete|| Attachment #148866|0 |1 is obsolete|| --- Comment #2 from matthewwilson86...@gmail.com --- Created attachment 148868 --> https://bugs.kde.org/attachment.cgi?id=148868=edit original sub-folders with nanosecond precision and copied sub-folders with nanosecond precision lost -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453840] Digikam git build error with 'digikamwidgets'
https://bugs.kde.org/show_bug.cgi?id=453840 --- Comment #6 from maderios --- (In reply to Maik Qualmann from comment #4) > FFmpeg 5 has API changes and is currently not compatible. It also affects > QtAV, that won't work. > > Maik Bad news :( Waiting... :) Thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453840] Digikam git build error with 'digikamwidgets'
https://bugs.kde.org/show_bug.cgi?id=453840 --- Comment #5 from maderios --- Created attachment 148867 --> https://bugs.kde.org/attachment.cgi?id=148867=edit build .txt -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 453846] New: Running spectacle under wayland gives a message "Could not take a screenshot. Please report this bug here.
https://bugs.kde.org/show_bug.cgi?id=453846 Bug ID: 453846 Summary: Running spectacle under wayland gives a message "Could not take a screenshot. Please report this bug here. Product: Spectacle Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: d...@rbdigital.biz CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Start Spectacle from the start menu or the command line. 2. Try to take a screenshot. 3. Receive error message. OBSERVED RESULT Get error message. EXPECTED RESULT Screenshot is taken. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Kernel version : 5.15.0-generic If I start spectacle from the command line, I get an error message and spectacle exits: "QSocketNotifier: Can only be used with threads started with QThread". -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453845] dolphin file manager loses nanosecond precision on date and time stamp on copied files and folders
https://bugs.kde.org/show_bug.cgi?id=453845 --- Comment #1 from matthewwilson86...@gmail.com --- Created attachment 148866 --> https://bugs.kde.org/attachment.cgi?id=148866=edit original sub-folders with nanosecond precision and copied sub-folders with nanosecond precision lost -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453845] dolphin file manager loses nanosecond precision on date and time stamp on copied files and folders
https://bugs.kde.org/show_bug.cgi?id=453845 matthewwilson86...@gmail.com changed: What|Removed |Added CC||matthewwilson86...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453845] New: dolphin file manager loses nanosecond precision on date and time stamp on copied files and folders
https://bugs.kde.org/show_bug.cgi?id=453845 Bug ID: 453845 Summary: dolphin file manager loses nanosecond precision on date and time stamp on copied files and folders Product: dolphin Version: 21.12.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: matthewwilson86...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 148865 --> https://bugs.kde.org/attachment.cgi?id=148865=edit original sub-folders with nanosecond precision and copied sub-folders with nanosecond precision lost STEPS TO REPRODUCE 1. Within dolphin file manager select the folder to copy (the folder name in my case is 'which' - it is a folder used for 'Which?magazine' ralated data and has sub-folders within it and sub-folders and files within those sub-folders) 2. Ctrl-C to copy the folder named 'which' 3. navigate to the folder where the folder (and sub-folder's and files need to be copied to) 4. Ctrl-v to paste 5. after copying is done, open a terminal window and issue command: ls -la --time-style=full-iso OBSERVED RESULT The output in terminal window: [j@j-void 211123]$ ls -la --time-style=full-iso total 24 drwxr-xr-x 6 k k 4096 2022-03-22 22:43:57.0 +0700 . drwxr-xr-x 4 k k 4096 2022-03-22 22:43:32.0 +0700 .. drwxr-xr-x 2 k k 4096 2022-03-22 22:44:21.0 +0700 cancellation drwxr-xr-x 2 k k 4096 2021-12-02 15:28:02.0 +0700 join drwxr-xr-x 3 k k 4096 2022-03-22 22:44:21.0 +0700 reviews drwxr-xr-x 2 k k 4096 2022-03-22 22:44:21.0 +0700 terms [j@j-void 211123]$ EXPECTED RESULT [j@j-void 211123]$ ls -la --time-style=full-iso total 28 drwxr-xr-x 1 root root 4096 2022-03-22 22:43:57.546506217 +0700 . drwxr-xr-x 1 root root 4096 2022-03-22 22:43:32.156505366 +0700 .. -rw--- 1 root root 192 2022-03-22 22:43:57.545506217 +0700 .directory drwxr-xr-x 1 root root 4096 2022-03-22 22:44:21.119507007 +0700 cancellation drwxr-xr-x 1 root root 4096 2021-12-02 15:28:02.373914765 +0700 join drwxr-xr-x 1 root root 4096 2022-03-22 22:44:21.116507007 +0700 reviews drwxr-xr-x 1 root root 4096 2022-03-22 22:44:21.113507007 +0700 terms SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: void linux 5.15.36_1/xfce 4.16 (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.
[plasma-systemmonitor] [Bug 453844] [Feature Request] Consider exposing more sensors (Encode and Decode) in System Monitor for NVIDIA GPU.
https://bugs.kde.org/show_bug.cgi?id=453844 --- Comment #2 from Samuel --- Created attachment 148864 --> https://bugs.kde.org/attachment.cgi?id=148864=edit Polling of Encoder information using nvidia-smi command in console. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450062] Plasma 5.24 + Wayland: When disconnecting 2nd monitor, icon positions get reset
https://bugs.kde.org/show_bug.cgi?id=450062 NIk changed: What|Removed |Added Version|5.24.0 |5.24.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453844] [Feature Request] Consider exposing more sensors (Encode and Decode) in System Monitor for NVIDIA GPU.
https://bugs.kde.org/show_bug.cgi?id=453844 --- Comment #1 from Samuel --- Created attachment 148863 --> https://bugs.kde.org/attachment.cgi?id=148863=edit Information exposed by nvidia-smi -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453844] New: [Feature Request] Consider exposing more sensors (Encode and Decode) in System Monitor for NVIDIA GPU.
https://bugs.kde.org/show_bug.cgi?id=453844 Bug ID: 453844 Summary: [Feature Request] Consider exposing more sensors (Encode and Decode) in System Monitor for NVIDIA GPU. Product: plasma-systemmonitor Version: 5.24.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: samping...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 148862 --> https://bugs.kde.org/attachment.cgi?id=148862=edit Sensors exposed currently in plasma-systemmonitor. SUMMARY Consider exposing more sensors like Encode and Decode sensors for NVIDIA GPU in Plasma System Monitor. OBSERVED RESULT Currently there are only Memory and Core usage, frequencies and memory size sensors as shown in the attached image. It would be very helpful to have Video Encode/Decode sensors in system monitor to have complete monitoring of NVIDIA GPU in Plasma. EXPECTED RESULT To have more sensors exposed to the user in GPU sensors section like encode, decode sensors for NVIDIA GPUs. It can be seen from the attached image showing command-line monitoring of Encoder usage that it is possible to poll the information using nvidia-smi. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93 Qt Version: 5.15.3 NVIDIA GeForce GTX 1060 GPU with 510.68 proprietary driver installed. -- You are receiving this mail because: You are watching all bug changes.
