[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471894] New: Offline Updates Does Not Check Polkit Correctly On Remote Systems
https://bugs.kde.org/show_bug.cgi?id=471894 Bug ID: 471894 Summary: Offline Updates Does Not Check Polkit Correctly On Remote Systems Classification: Applications Product: Discover Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Updates (offline) Assignee: plasma-b...@kde.org Reporter: noorez.kas...@gmail.com CC: aleix...@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. Access system remotely via xrdp 2. Set pokit policy to AUTH_ADMIN when refreshing system repositories, triggering offline updates and rebooting system 3. Perform system update via discover app OBSERVED RESULT After updates are downloaded, the screen to initiate a reboot does not appear correctly and instead just refreshes the available update screen EXPECTED RESULT Screen to initiate a reboot and subsequent prompt from polkit to authenticate should appear if the policy allows for it 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.
[kid3] [Bug 471877] does not change the number of digits in the filename from tags
https://bugs.kde.org/show_bug.cgi?id=471877
Urs Fleisch changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED|RESOLVED
--- Comment #1 from Urs Fleisch ---
The import does not change fields which seem to be unchanged, for example only
the case (uppercase/lowercase characters) changed or the numbers are formatted
differently. This is by design and is also the case for the "Tools/Number
Tracks" action. If you want to change track number which are the same but
formatted differently, you have to delete them before importing/renumbering.
You can control the format of the numbers in the file name as is described in
the handbook:
%t %{track.n} Track with field width n (e.g. 001 for %{track.3})
The default is two digits, i.e. %{track} is the same as %{track.2}.
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471892] Konsole crashes when opening a new tab in Windows 11
https://bugs.kde.org/show_bug.cgi?id=471892 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471893] New: Resizing tiled windows (using Super+Arrow) on one virtual desktops affects all other tiled windows across all virtual desktops
https://bugs.kde.org/show_bug.cgi?id=471893 Bug ID: 471893 Summary: Resizing tiled windows (using Super+Arrow) on one virtual desktops affects all other tiled windows across all virtual desktops Classification: Plasma Product: kwin Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quick Tiling Assignee: kwin-bugs-n...@kde.org Reporter: arnav0...@gmail.com Target Milestone: --- SUMMARY So when there are multiple virtual desktops open and in one of the desktops, i do a 50-50 tile using Super+Right and Super+Left and if i resize the split by resizing from the center, then, all other tiled windows on all other desktops also get resized. STEPS TO REPRODUCE 1. Tile a window on one desktop using Super+Right/Left 2. Switch to a different desktop, open and tile another window to the same side 3. Resize one window on one of the two desktops to the left/right OBSERVED RESULT The size of all tiled windows on the same side across all virtual desktops get resized EXPECTED RESULT All virtual desktops should be completely independent, i.e. Resizing tiled windows on one virtual desktop must not affect tiled windows across other virtual desktops SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471892] New: Konsole crashes when opening a new tab in Windows 11
https://bugs.kde.org/show_bug.cgi?id=471892 Bug ID: 471892 Summary: Konsole crashes when opening a new tab in Windows 11 Classification: Applications Product: konsole Version: master Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: os-...@jacraig.com Target Milestone: --- When attempting to open an new tab through any method I've tried (shortcut, menu) or opening a new window from a running instance results in a crash. STEPS TO REPRODUCE 1. Run Konsole 2. Try to open a new tab OBSERVED RESULT crash EXPECTED RESULT no crash, new tab or window opens SOFTWARE/OS VERSIONS Using konsole-master-41-windows-cl-msvc2019-x86_64.exe from binary-factory.kde.org Windows 11 KDE Frameworks Version 5.105.0 Qt Version 5.15.8 ADDITIONAL INFORMATION It works on another computer running Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 470379] Adding icon applet to containment has wrong name/icon
https://bugs.kde.org/show_bug.cgi?id=470379 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470737] Keyboard layout indicator randomly disappears on X11
https://bugs.kde.org/show_bug.cgi?id=470737 --- Comment #19 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.
[Haruna] [Bug 470917] Cannot clear/erase the playlist once created
https://bugs.kde.org/show_bug.cgi?id=470917 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471551] Rendering crashed. Could not update timestamps for skipped samples.
https://bugs.kde.org/show_bug.cgi?id=471551 --- Comment #4 from Jim Henderson --- I run a Windows 10 compter in a virtual machine on my Mac (Host on the Mac is VirtualBox Version 7.0.8 r156879 (Qt5.15.2)). The folder on the Mac where my kdenlive project is located is shared to the client machine, where it appears as drive letter P:. I installed the latest Windows version of kdenlive on the virtual machine (23.04.2) and opened the project file. The program remade the proxy files and I started Rendering to an MP4 file. It ran more slowly than on the Mac, probably because the virtual machine is not given as many resources as the Mac has (eg. memory and processors) but it ran fully to completion without any crash :-) So it seems the problem is in the Mac version of kdenlive, or with how it interacts with the Mac function calls. Still hoping you developers, so generous with your time, can have some ideas for fixing this problem in the Mac version of kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471891] New: Installing an app when Kickoff is open clear the grid
https://bugs.kde.org/show_bug.cgi?id=471891
Bug ID: 471891
Summary: Installing an app when Kickoff is open clear the grid
Classification: Plasma
Product: plasmashell
Version: 5.27.5
Platform: Neon
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: Application Launcher (Kickoff)
Assignee: plasma-b...@kde.org
Reporter: esperluett...@proton.me
CC: mikel5...@gmail.com, noaha...@gmail.com
Target Milestone: 1.0
SUMMARY
When installing a new app (like from "apt") when Kickoff is open, the app grid
becomes empty when the installation is finished.
STEPS TO REPRODUCE
1. (Re-)Install for example Firefox ("apt install -y firefox")
2. Open Kickoff and select "Internet" category before the installation is
finished
OBSERVED RESULT
Once the installation is finished, the applications grid is empty. Changing the
category, or re-opening Kickoff, displays correctly the grid with Firefox
installed.
EXPECTED RESULT
The application grid should be not become empty, and the newly application
should appear in the relevant category without having to change category or to
close then re-open Kickoff.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon Live (20230504-0714)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Graphics: X11 on Neon
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 471890] New: Create new annotation still shows "F6" as shortcut event when changed
https://bugs.kde.org/show_bug.cgi?id=471890
Bug ID: 471890
Summary: Create new annotation still shows "F6" as shortcut
event when changed
Classification: Applications
Product: okular
Version: 23.04.0
Platform: Neon
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: esperluett...@proton.me
Target Milestone: ---
SUMMARY
When changing the shortcut for creating a new annotation (from "F6" by
default), the message in the "Annoations" tab in the left panel is not updated
STEPS TO REPRODUCE
1. Open a file in Okular
2. Select "Annotations" tab in left panel
3. Change shortcut to create a new annotation ("Settings" > "Configure Keyboard
Shortcuts..." > "Okular -> Annotation") to, for this example, "F4"
4. (Optional) Quit and re-open Okular
OBSERVED RESULT
The message still shows "No annotation - To create new annotations press *F6*
or select Tools -> Annotations from the menu."
EXPECTED RESULT
The message should be "No annotation - To create new annotations press *F4* or
select Tools -> Annotations from the menu."
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon Live (20230504-0714)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Graphics: X11 on Neon
Okular Version: 23.04.0
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 471889] Search Results Not Highlighted When Changing Colors in Okular
https://bugs.kde.org/show_bug.cgi?id=471889 gdrjhd changed: What|Removed |Added CC||gdr...@yahooweb.co -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471889] New: Search Results Not Highlighted When Changing Colors in Okular
https://bugs.kde.org/show_bug.cgi?id=471889 Bug ID: 471889 Summary: Search Results Not Highlighted When Changing Colors in Okular Classification: Applications Product: okular Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: gdr...@yahooweb.co Target Milestone: --- Created attachment 160053 --> https://bugs.kde.org/attachment.cgi?id=160053=edit Screenshots 1. Overview: I encountered a bug in Okular where the search results are not highlighted when I change the colors to black and green for improved readability. This issue prevents me from effectively using the search functionality within Okular. 2. Steps to Reproduce: a. Launch Okular on your system. b. Open a PDF document. c. Navigate to the color settings or preferences in Okular. d. Modify the colors to black and green (or any other color combination for improved readability). e. Perform a search within the document using the search feature in Okular. f. Observe that the search results are not highlighted or are not visible. 3. Expected Behavior: When changing the colors for improved readability, the search results should be highlighted properly, allowing users to easily locate the searched keyword(s) within the PDF document. 4. Actual Behavior: After modifying the colors in Okular, the search results are not highlighted, making it difficult to identify the occurrence of the searched keyword(s) within the document. 5. Reproducibility: The issue is consistently reproducible following the provided steps on my system. 6. Screenshots: Please refer to the provided screenshots for a visual demonstration of the issue. 7. Impact: This bug affects users who rely on Okular's search functionality while utilizing customized color schemes for improved accessibility and readability. 8. Workaround: As a temporary workaround, I suggest reverting the color settings to the default or using a different color scheme that does not cause the search results to be hidden. 9. Suggestion: In addition to fixing the issue with search results not being displayed, I propose implementing a feature that allows users to choose the color used to mark search results. This customization would give users more flexibility and control over their reading experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470811] When right-clicking on a desktop widget that s its own menu, append standard context menu actions in a submenu at the end
https://bugs.kde.org/show_bug.cgi?id=470811
--- Comment #2 from esperluett...@proton.me ---
I've tested many widgets, for example "Comic Strip" shows many actions when
right-clicking on it, including the standard "Configure", "Enter Edit Mode"
(and "Show Alternatives" when relevant) and "Remove" at the end, which is
consistent with most other widgets.
Maybe theses actions should be automatically appended on each widget
right-click menu (if not already present), and if the widget provides an empty
menu or no menu (like "Audio Volume" widget when right-clicking outside
sliders), the standard "Configure", ("Show Alternatives"), "Enter Edit Mode"
and "Remove" should be shown.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 471888] New: Unable to update system due to konsole: /etc/xdg/konsolerc already exists in filesystem and conflicts with package update
https://bugs.kde.org/show_bug.cgi?id=471888 Bug ID: 471888 Summary: Unable to update system due to konsole: /etc/xdg/konsolerc already exists in filesystem and conflicts with package update Classification: Applications Product: konsole Version: 22.12.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: codyarnol...@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. Image SDcard with Manjaro ARM for Rpi4 from www.manjaro.org 2. Open Konsole and perform system update 3. "sudo pacman -Syu" or "sudo pacman-mirrors -f 5 && sudo pacman -Syyu" OBSERVED RESULT: :: Synchronizing package databases... core 260.0 KiB 48.2 KiB/s 00:05 [] 100% extra 2.3 MiB 99.3 KiB/s 00:24 [] 100% community 6.7 MiB 128 KiB/s 00:53 [] 100% :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... warning: dependency cycle detected: warning: libcamera-ipa will be installed before its libcamera dependency Packages (425) :: Proceed with installation? [Y/n] y (425/425) checking keys in keyring [] 100% (425/425) checking package integrity [] 100% (425/425) loading package files [] 100% (425/425) checking for file conflicts [] 100% error: failed to commit transaction (conflicting files) konsole: /etc/xdg/konsolerc exists in filesystem Errors occurred, no packages were upgraded. EXPECTED RESULT: Full system update complete SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernal Version: 5.15.92-1-MANJARO-ARM-RPI (64-bit) ADDITIONAL INFORMATION Raspberry Pi 4B Rev. 1.4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470388] Double-clicking a tab to open a new tab
https://bugs.kde.org/show_bug.cgi?id=470388 --- Comment #3 from esperluett...@proton.me --- Thank you :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471132] _NET_FRAME_EXTENTS returns incorrect output on XWAYLAND
https://bugs.kde.org/show_bug.cgi?id=471132 --- Comment #4 from dofficialg...@gmail.com --- Any chance this can be merged into the Plasma/5.27 branch of kwin? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #33 from QwertyChouskie --- Any progress towards a proper fix for this? This completely breaks file transfers when using GSConnect on any somewhat-modern distro. IMHO it's time to drop Android <=7 support if no easy workaround to keep it supported is found. I'm quite confident the number of GSConnect users vastly outweighs the number of Android <= 7 users. For flagship phones, the Samsung Galaxy S7, first released in March 2016, runs Android 8. For budget devices, the Moto G5 series (2017) runs Android 8. You'd have to go back to 2015 flagship phones or 2016 budget phones to find stuff on Android <=7. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 QwertyChouskie changed: What|Removed |Added Component|common |android-application CC||andrew.g.r.hol...@gmail.com ||, ||asdfghrbljz...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 471887] New: Crash when trying to join #grapheneos:grapheneos.org
https://bugs.kde.org/show_bug.cgi?id=471887 Bug ID: 471887 Summary: Crash when trying to join #grapheneos:grapheneos.org Classification: Applications Product: NeoChat Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: k...@egerlach.mozmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: neochat (23.01) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-9-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: I had just added mozilla.org and was Exploring rooms. I saw #grapheneos:grapheneos.org and decided to join that room. When I clicked on it NeoChat crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: NeoChat (neochat), signal: Segmentation fault [KCrash Handler] #4 0x7f9ea54a8460 in QQuickTextDocument::textDocument() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x56384e9e6d61 in ?? () #6 0x56384e9e7b6e in ?? () #7 0x7f9ea30e8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9ea4aea5f2 in Quotient::Connection::newRoom(Quotient::Room*) () from /lib/x86_64-linux-gnu/libQuotient.so.0.6 #9 0x7f9ea4b077f4 in Quotient::Connection::provideRoom(QString const&, Quotient::Omittable) () from /lib/x86_64-linux-gnu/libQuotient.so.0.6 #10 0x7f9ea4b08338 in ?? () from /lib/x86_64-linux-gnu/libQuotient.so.0.6 #11 0x7f9ea30e8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f9ea4aeac02 in Quotient::BaseJob::finished(Quotient::BaseJob*) () from /lib/x86_64-linux-gnu/libQuotient.so.0.6 #13 0x7f9ea4b6e4b3 in Quotient::BaseJob::finishJob() () from /lib/x86_64-linux-gnu/libQuotient.so.0.6 #14 0x7f9ea30e8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f9ea45fe3b8 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7f9ea30dd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f9ea3d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f9ea30b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f9ea30b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f9ea310a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f9ea27337a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f9ea2733a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f9ea2733acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f9ea310984e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f9ea30b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f9ea30b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x56384e8cf2d4 in main () [Inferior 1 (process 88475) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471886] One Or More Monitor Black After Switching With DP KVM
https://bugs.kde.org/show_bug.cgi?id=471886 --- Comment #2 from Kyle Siefring --- This is the kvm switch https://store.level1techs.com/products/14-kvm-switch-dual-monitor-2computer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471886] One Or More Monitor Black After Switching With DP KVM
https://bugs.kde.org/show_bug.cgi?id=471886 Kyle Siefring changed: What|Removed |Added Summary|One Or More Monitor Black |One Or More Monitor Black |After Switching With KVM|After Switching With DP KVM --- Comment #1 from Kyle Siefring --- (In reply to Kyle Siefring from comment #0) > SUMMARY > > m+a+r+y > > STEPS TO REPRODUCE > Switch DP monitors in with kvm switch (needs to be a dumb switch). > > Inserting connectors at approx the same time should work too. > > OBSERVED RESULT > Either 1 or both screen go black. I haven't even switched and had no > monitors effected. Can move mouse in affected screens. > > EXPECTED RESULT > Not that. > > SOFTWARE/OS VERSIONS > Linux: 5.19-1028-lowlatency > KDE Plasma Version: 5.27.6 > KDE Frameworks Version: 5.107.0 > Qt Version: 5.15.10 > Mesa: 23.1.3 > > ADDITIONAL INFORMATION > GPU: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471886] New: One Or More Monitor Black After Switching With KVM
https://bugs.kde.org/show_bug.cgi?id=471886 Bug ID: 471886 Summary: One Or More Monitor Black After Switching With KVM Classification: Plasma Product: kwin Version: 5.27.6 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: kylesiefr...@gmail.com Target Milestone: --- SUMMARY m+a+r+y STEPS TO REPRODUCE Switch DP monitors in with kvm switch (needs to be a dumb switch). Inserting connectors at approx the same time should work too. OBSERVED RESULT Either 1 or both screen go black. I haven't even switched and had no monitors effected. Can move mouse in affected screens. EXPECTED RESULT Not that. SOFTWARE/OS VERSIONS Linux: 5.19-1028-lowlatency KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Mesa: 23.1.3 ADDITIONAL INFORMATION GPU: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471885] New: system-settings crashed when i try to access the Flatpak Permission Settings
https://bugs.kde.org/show_bug.cgi?id=471885 Bug ID: 471885 Summary: system-settings crashed when i try to access the Flatpak Permission Settings Classification: Applications Product: systemsettings Version: 5.27.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: elem...@gmail.com Target Milestone: --- Application: systemsettings (5.27.4) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-24-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: system-settings crashed every time i try to access the Flatpak Permission Settings The crash can be reproduced every time. -- Backtrace: Application: Ρυθμίσεις συστήματος (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f85a523c094 in flatpak_installation_list_installed_refs_by_kind () from /lib/x86_64-linux-gnu/libflatpak.so.0 #5 0x7f85a52d2a09 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_flatpak.so #6 0x7f85a52d3aba in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_flatpak.so #7 0x7f85a52d4b69 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_flatpak.so #8 0x7f85c49b2048 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #9 0x7f85c49152d9 in KCModuleLoader::loadModule(KPluginMetaData const&, QWidget*, QList const&) () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #10 0x7f85c49186cd in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #11 0x7f85c4918cf8 in KCModuleProxy::realModule() const () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #12 0x7f85c58313e8 in ModuleView::updatePageIconHeader(KPageWidgetItem*) () from /lib/x86_64-linux-gnu/libsystemsettingsview.so.3 #13 0x7f85c583495a in ModuleView::addModule(MenuItem*, QStringList const&) () from /lib/x86_64-linux-gnu/libsystemsettingsview.so.3 #14 0x7f85af916dd9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #15 0x7f85af919b31 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #16 0x7f85af91a4cb in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #17 0x7f85c1cd0433 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7f85c1ba9901 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #19 0x7f85c1bab7e0 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7f85c1bc88ad in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7f85c1bcc027 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7f85c1b5d4a6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7f85c1ceae91 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7f85c1c9bb4f in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7f85c1c9d2d8 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7f85c1ccff0f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #27 0x7f85c3ef34f1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f85bf587c91 in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #29 0x7f85bf5a7709 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #30 0x7f85c2262188 in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #31 0x7f85c4b6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7f85c3ebae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f85c22800de in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #34 0x7f85c22817e1 in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #35 0x7f85c434e715 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #36 0x7f85c4b6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #37 0x7f85c3ebae38 in
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471884] New: Windows that opened maximized behave weirdly when dragged
https://bugs.kde.org/show_bug.cgi?id=471884 Bug ID: 471884 Summary: Windows that opened maximized behave weirdly when dragged Classification: Plasma Product: kwin Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: quintenk...@gmail.com Target Milestone: --- SUMMARY Some apps (e.g. Dolphin) behave very oddly when they launch maximized and are then restored by dragging the titlebar. STEPS TO REPRODUCE 1. Open Dolphin, maximize it, close it, and reopen it 2. Observe that Dolphin opens maximized 3. Unmaximize Dolphin by dragging the titlebar 4. Resize Dolphin by its top-left corner OBSERVED RESULT In step 3, Dolphin is positioned with the cursor at the top right. In step 4, Dolphin's bottom-right corner suddenly jumps to the position where you started dragging (the top-left corner of the window). EXPECTED RESULT In step 3 I expect Dolphin to keep the cursor in the same relative position, like when dragging to unmaximize a window that was not initially maximized. In step 4 I expect Dolphin to not jump around. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Probably related to bug 437089 Possibly also related to bug 434116? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Quinten Kock changed: What|Removed |Added CC||quintenk...@gmail.com --- Comment #30 from Quinten Kock --- Just chiming in to say this is still an issue, but only for some applications. For example, Dolphin behaves correctly and even restores to the right size, but System Monitor is affected, as is Elisa. GTK apps seem to handle this correctly on my Plasma Wayland desktop, at least Nautilus and Lutris do, although the latter doesn't remember the size to restore to. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471304] appstream:/ URIs don't open Discover in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=471304 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kservice/-/merge_requests/149 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 471811] Laptop screen auto-dimming
https://bugs.kde.org/show_bug.cgi?id=471811 Zamundaaa changed: What|Removed |Added Flags|Wayland-| Component|general |general CC||m...@ratijas.tk, ||natalie_clar...@yahoo.de, ||xaver.h...@gmail.com Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Version|unspecified |5.27.5 Product|kwin|Powerdevil -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471809] [Wayland] [NVIDIA] Compositing fails under vram exhaustion, nv_gbm_bo_create fails, Failed to allocate NVKMS memory for GEM object
https://bugs.kde.org/show_bug.cgi?id=471809 --- Comment #2 from spr...@redhat.com --- Yeah, it's really weird, I get the titlebar and border, but everything else is invisible for chrome, might be due to it being a GTK application. The start menu just doesn't render anything though -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471127] Support Wikitext extension
https://bugs.kde.org/show_bug.cgi?id=471127 --- Comment #2 from Henning --- thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471809] [Wayland] [NVIDIA] Compositing fails under vram exhaustion, nv_gbm_bo_create fails, Failed to allocate NVKMS memory for GEM object
https://bugs.kde.org/show_bug.cgi?id=471809 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- > Windows/menus/etc work and are visible I don't think that's possible. If an application can't allocate buffers, there's nothing for KWin to show. I'm a bit confused how you get invisible windows though - without new buffers, applications can't resize windows. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 197915] 80-bit floats are not supported on x86 and x86-64
https://bugs.kde.org/show_bug.cgi?id=197915 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471883] Primary screen not working properly
https://bugs.kde.org/show_bug.cgi?id=471883 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.24.6 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.24.6, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471883] New: Primary screen not working properly
https://bugs.kde.org/show_bug.cgi?id=471883 Bug ID: 471883 Summary: Primary screen not working properly Classification: Applications Product: systemsettings Version: 5.24.6 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: socarb...@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 *** When choosing a primary screen, the task bar is set to another screen most of the time, especially if the selected screen is not the internal screen. Sometimes, one of the screen also appear with a black background for some reason. Also, don't know if it's linked, but my computer have more easily slowness issue if my internal screen is OFF, even though that's surprising. I do have particularly large external screen (a 5k, used as two monitors 11:9 and 21:9), and I believe my computer has a hard time managing it so I have to lower the configuration settings to use it, but, weirdly enough, on my kubuntu, if I put the internal screen of my laptop up, at the same time as my two-ish, big screen, it's faster than with my two-ish external screen alone STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: dual boot 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.
[wacomtablet] [Bug 471882] New: Unable to program express keys of "Huion H950P" peripheral
https://bugs.kde.org/show_bug.cgi?id=471882 Bug ID: 471882 Summary: Unable to program express keys of "Huion H950P" peripheral Classification: Plasma Product: wacomtablet Version: 3.2.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: luai.ma...@gmail.com Target Milestone: --- SUMMARY Using the `digimend-dkms-drivers` (v. 10-1) in conjunction with the `wacomtablet-kcm` (v. 3.2.0-5) settings integration I can successfully map the drawing area and pen buttons of my drawing tablet. However when trying to map the express keys (which are seemingly being detected) nothing happens. STEPS TO REPRODUCE 1. Install `digimend-dkms-drivers` from AUR, the `wacomtablet-kcm` integration for access to the GUI within system settings and connect a "Huion H950P" tablet. 2. Use the appropriate settings window to map your express keys. 3. Press the express keys. OBSERVED RESULT The express keys do not behave as requested. EXPECTED RESULT The express keys should produce the mapped key events. SOFTWARE/OS VERSIONS Windows: -- macOS: -- Linux/KDE Plasma: Manjaro Linux (6.1.31-2, 64-bit) (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I know that the express keys were working as they should about half a year ago, however coming back to using the tablet after several months of hiatus, seemingly nothing works (mind that I'm on a rolling release system, so a driver or kernel update may be the culprit here). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471791] Crash in QtWaylandClient::QWaylandXdgSurface::setGrabPopup during quick open
https://bugs.kde.org/show_bug.cgi?id=471791 --- Comment #4 from Christoph Cullmann --- For me it so far happens never. If you can at least get it sometimes to crash, could you try if a singleShot might remove that for you? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 471829] kimageformats 5.107.0 build failure: src/imageformats/psd.cpp:828:23: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-
https://bugs.kde.org/show_bug.cgi?id=471829 --- Comment #3 from Sam James --- planarToChunchyFloat gets called with a quint32. You can't just reinterpret_cast to treat it as a float*. Putting it another way: why would it be okay? This warning appears regardless of -Werror and is enabled by -Wall, the user here is just setting -Werror to find likely miscompilations. GCC warngs by default only for -Wstrict-aliasing=3, where it's extremely confident that aliasing rules were violated (hence the "will break..."). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471881] New: Sending files to Android phone is slow and eventually fails and crashes KDE Connect
https://bugs.kde.org/show_bug.cgi?id=471881 Bug ID: 471881 Summary: Sending files to Android phone is slow and eventually fails and crashes KDE Connect Classification: Applications Product: kdeconnect Version: 23.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: lucianluca...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.04.2) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.3.4-201.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: Happened with both Samsung S23 and Huawei P30. Wireless chipset is Intel AX200 The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7f7c6cd79540 in operator==(QString const&, QString const&) () from /lib64/libQt5Core.so.5 #5 0x7f7c6e6b06dd in Daemon::getDevice(QString const&) () from /lib64/libkdeconnectcore.so.23 #6 0x7f7c6e6a6145 in CompositeUploadJob::emitDescription(QString const&) () from /lib64/libkdeconnectcore.so.23 #7 0x7f7c6e6a92d2 in CompositeUploadJob::startNextSubJob() () from /lib64/libkdeconnectcore.so.23 #8 0x7f7c6cee8461 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7f7c6e2a6fc6 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #10 0x7f7c6e2acbab in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #11 0x7f7c6cee8461 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #12 0x7f7c6ce03afd in QIODevice::close() () from /lib64/libQt5Core.so.5 #13 0x7f7c6cdfa4f3 in QFileDevice::close() () from /lib64/libQt5Core.so.5 #14 0x7f7c6e6a33ce in UploadJob::uploadNextPacket() () from /lib64/libkdeconnectcore.so.23 #15 0x7f7c6cee8461 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7f7c6c59a854 in QSslSocket::encryptedBytesWritten(long long) () from /lib64/libQt5Network.so.5 #17 0x7f7c6c59cd5d in QSslSocketPrivate::_q_bytesWrittenSlot(long long) () from /lib64/libQt5Network.so.5 #18 0x7f7c6cee85e8 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #19 0x7f7c6cdff2c4 in QIODevice::bytesWritten(long long) () from /lib64/libQt5Core.so.5 #20 0x7f7c6c56fd5b in QAbstractSocketPrivate::writeToSocket() () from /lib64/libQt5Network.so.5 #21 0x7f7c6c56abb4 in QAbstractSocketPrivate::flush() () from /lib64/libQt5Network.so.5 #22 0x7f7c6ceded0b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #23 0x7f7c6dbaeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #24 0x7f7c6ceb4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #25 0x7f7c6ceb7635 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #26 0x7f7c6cf06c3f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #27 0x7f7c6b31339c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #28 0x7f7c6b371438 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #29 0x7f7c6b310a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #30 0x7f7c6cf06729 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #31 0x7f7c6ceb2b4b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #32 0x7f7c6cebaddb in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #33 0x560fa081a132 in main () [Inferior 1 (process 8628) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 471829] kimageformats 5.107.0 build failure: src/imageformats/psd.cpp:828:23: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-
https://bugs.kde.org/show_bug.cgi?id=471829 --- Comment #2 from Albert Astals Cid --- (In reply to Albert Astals Cid from comment #1) > Can you prove that's a but instead of you shooting yourself on the feet? but -> bug -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471791] Crash in QtWaylandClient::QWaylandXdgSurface::setGrabPopup during quick open
https://bugs.kde.org/show_bug.cgi?id=471791 --- Comment #3 from Nicolas Fella --- Not reliably. Something like this happens regularly (like 1 in 50 times) opening the quick open thing. Most of the time Kate closes without creating a coredump, I think because it's terminated because of a Wayland protocol error -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 471829] kimageformats 5.107.0 build failure: src/imageformats/psd.cpp:828:23: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-
https://bugs.kde.org/show_bug.cgi?id=471829 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Albert Astals Cid --- Can you prove that's a but instead of you shooting yourself on the feet? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471304] appstream:/ URIs don't open Discover in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=471304 Nicolas Fella changed: What|Removed |Added CC||publiclyvisibleemail@gmail. ||com --- Comment #1 from Nicolas Fella --- *** Bug 471873 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471873] "Get [X application - i.e. Krita...]" in application launcher does nothing, (X11 or Wayland)
https://bugs.kde.org/show_bug.cgi?id=471873 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 471304 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471805] Closing Firefox ESR window preview crashes taskbar
https://bugs.kde.org/show_bug.cgi?id=471805 --- Comment #2 from miracledin...@gmail.com --- Can confirm that this bug does occur for windows of any application, Firefox merely happened to be the first one I noticed it with. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 471851] kde-open with long custom URI opens browser instead of correct application
https://bugs.kde.org/show_bug.cgi?id=471851 --- Comment #1 from egerlach --- I just tried on KDE Neon and got the same result: Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 5.19.0-45-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #23 from Pietro Pizzi --- Created attachment 160052 --> https://bugs.kde.org/attachment.cgi?id=160052=edit The command line output from konqueror This is the output of > QT_LOGGING_RULES="konqueror.debug=true;libkonq.debug=true" konqueror -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 Reid Wiggins changed: What|Removed |Added CC||k...@reidwiggins.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #22 from Pietro Pizzi --- Sorry but it's really hard to say for certain. On Arch I update "all the time" ;) but often doesn't reboot right after. I often use S3 and reboot approximately every other week. One Konqueror window, I mostly use (with ~10 tiles), is always open, the other sessions I open very rarely. And the new Konqueror binary only runs when I start a new konqueror window, which means on reboot (every other week). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Setting to disable when mouse is plugged in is missing when using Libinput driver
https://bugs.kde.org/show_bug.cgi?id=415364 mira.j...@gmail.com changed: What|Removed |Added CC||mira.j...@gmail.com --- Comment #18 from mira.j...@gmail.com --- Any progress on this matter? It does seem like libinput does support disabling devices on mouse plug-in: https://wayland.freedesktop.org/libinput/doc/latest/configuration.html#send-events-mode I've wanted to switch to Wayland for months now, but the fact that this minor, but important feature is still missing is an absolute deal-breaker for me. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471492] Scripts in context menu
https://bugs.kde.org/show_bug.cgi?id=471492 --- Comment #9 from AB --- So the feature already is pretty much already there, but it would need to be more easily accessible. Two simple processes would be needed: A) By simple checkbox in workflow settings adds any workflow available in right-click context menu while file browsing (or to make things easier they could all be available) B) Doing file selection and choosing workflow from context menu would instantly (using already existing feature) i) create queue ii) run selected workflow v) remove queue I for example often need temporary smaller versions of pictures (email attachments etc.) and creating them could still be little easier. And there's many other uses. Especially when dealing with just single files at time manually creating and handling queues seems unnecessary while existing procedure is needed and important in creating workflows, but I would leave current separate worktable mainly for management and prefer quicker alternative for using them if they are needed repeatedly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 Zamundaaa changed: What|Removed |Added CC||bixi...@bixilon.de --- Comment #47 from Zamundaaa --- *** Bug 471832 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471832] One pixel on monitor left out when maximing window on most right screen in 3 screen setup
https://bugs.kde.org/show_bug.cgi?id=471832 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 459373 *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 471869] Add support for libsvtav1 in the ffmpeg version distributed as part of the org.kde.Platform/x86_64/5.15-22.08 runtime
https://bugs.kde.org/show_bug.cgi?id=471869 Aleix Pol changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Aleix Pol --- Our runtime is not really the right place to address this. It could be addressed in two places: - https:// github.com/flathub/org.freedesktop.Platform.ffmpeg < ffmpeg's runtime packaging - digikam's flatpak packaging -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471066] KDE Connect Media control doesn't work anymore after update
https://bugs.kde.org/show_bug.cgi?id=471066 --- Comment #5 from geoangerc...@gmail.com --- (In reply to Albert Vaca from comment #4) > It should be fixed in 1.26.2 yep I can confirm it's fixed!! thanks :) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471066] KDE Connect Media control doesn't work anymore after update
https://bugs.kde.org/show_bug.cgi?id=471066 Albert Vaca changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Albert Vaca --- It should be fixed in 1.26.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467289] In the Raven Shadow: Unable to access top-left corner during gameplay
https://bugs.kde.org/show_bug.cgi?id=467289 myself...@tuta.io changed: What|Removed |Added Version|5.27.2 |5.27.6 --- Comment #4 from myself...@tuta.io --- 7292af3d04a2f692a52564ef16509e3760624e64 is the first bad commit -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 471880] Laptop nearly always completely freezes after removing external display while suspended
https://bugs.kde.org/show_bug.cgi?id=471880
--- Comment #1 from Niisse ---
'kscreen-doctor -o' output without external monitor plugged in:
Output: 1 eDP-1 enabled connected priority 1 Panel Modes: 0:1920x1080@60*!
1:1280x1024@60 2:1024x768@60 3:1280x800@60 4:1920x1080@60 5:1600x900@60
6:1368x768@60 7:1280x720@60 Geometry: 3440,0 1920x1080 Scale: 1 Rotation: 1
Overscan: 0 Vrr: incapable RgbRange: unknown
'kscreen-console' output
START: Requesting Config
Received config. Took 13 milliseconds
Screen:
maxSize: QSize(64000, 64000)
minSize: QSize(0, 0)
currentSize: QSize(1920, 1080)
-
Id: 1
Name: "eDP-1"
Type: "Panel (Laptop)"
Connected: true
Enabled: true
Priority: 1
Rotation: KScreen::Output::None
Pos: QPoint(3440,0)
MMSize: QSize(340, 190)
FollowPreferredMode: false
Size: QSize(1920, 1080)
Scale: 1
Clones: None
Mode: "0"
Preferred Mode: "0"
Preferred modes: ("0")
Modes:
"0""1920x1080@60" QSize(1920, 1080) 60.001
"1""1280x1024@60" QSize(1280, 1024) 59.895
"2""1024x768@60" QSize(1024, 768) 59.92
"3""1280x800@60" QSize(1280, 800) 59.81
"4""1920x1080@60" QSize(1920, 1080) 59.963
"5""1600x900@60" QSize(1600, 900) 59.946
"6""1368x768@60" QSize(1368, 768) 59.882
"7""1280x720@60" QSize(1280, 720) 59.855
EDID Info:
Device ID: "xrandr-BOE"
Name: ""
Vendor: "BOE"
Serial: ""
EISA ID: "NT156FHM-N62"
Hash: "8921c93a2501651b81567b62c19edfac"
Width: 34
Height: 19
Gamma: 2.2
Red: QQuaternion(scalar:1, vector:(0.572266, 0.355469, 0))
Green: QQuaternion(scalar:1, vector:(0.350586, 0.579102, 0))
Blue: QQuaternion(scalar:1, vector:(0.166992, 0.125977, 0))
White: QQuaternion(scalar:1, vector:(0.313477, 0.329102, 0))
--
You are receiving this mail because:
You are watching all bug changes.
[KScreen] [Bug 471880] Laptop nearly always completely freezes after removing external display while suspended
https://bugs.kde.org/show_bug.cgi?id=471880 Niisse changed: What|Removed |Added Summary|Entire laptop nearly always |Laptop nearly always |freezes after removing |completely freezes after |external display while |removing external display |suspended |while suspended -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 471880] New: Entire laptop nearly always freezes after removing external display while suspended
https://bugs.kde.org/show_bug.cgi?id=471880 Bug ID: 471880 Summary: Entire laptop nearly always freezes after removing external display while suspended Classification: Plasma Product: KScreen Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: nisselomme...@gmail.com Target Milestone: --- SUMMARY I have an external HDMI monitor. Whenever I unplug that monitor to take my laptop with me while it is suspended, very often it completely hangs when I wake it from sleep. The screen turns on, and I usually see the unlock screen (but without the login UI), and I can't do anything from here - not even switching to a different TTY. The caps lock light can still be toggled, so I assume it must be the OS and not the complete machine. STEPS TO REPRODUCE 1. Plug in monitor 2. Have various apps open on both displays 3. Suspend laptop 4. Wake laptop from sleep OBSERVED RESULT After about a second, the laptop completely freezes and I'm locked out EXPECTED RESULT The laptop does not freeze and allows me to use it as normal SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230629 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.9-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: VivoBook_ASUSLaptop X515UA_M515UA System Version: 1.0 ADDITIONAL INFORMATION Currently on SDDM version 0.20.0-1.1, although it happened on 0.19 too. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471879] New: Pen Support for KDEConnect
https://bugs.kde.org/show_bug.cgi?id=471879 Bug ID: 471879 Summary: Pen Support for KDEConnect Classification: Applications Product: kdeconnect Version: 23.04.2 Platform: Android OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: daeng...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY I would like to see some kind of Pen support for the Android app. Be it specific S-Pen support for Samsung devices or general support through a fast reachable "Keep-Left-Mouseclick-Down"-Button or a seperate drawing mode. This would make it possible to use any tablet as an remote Drawing Tablet for small scetches. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 471878] New: Digital clock widget doesn't show events with PIM event plugin
https://bugs.kde.org/show_bug.cgi?id=471878 Bug ID: 471878 Summary: Digital clock widget doesn't show events with PIM event plugin Classification: Applications Product: kalendar Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: frankenstein291...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 160051 --> https://bugs.kde.org/attachment.cgi?id=160051=edit In this image i show you how i can configured muy google acount and ativated PIM events plugin I have activated PIM events plugin to show the events in the digital clock widget, but a i can't see its, I have synced muy google account in korganizer an kalendar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471315] Plasmashell crash when clicking on apps in task panel
https://bugs.kde.org/show_bug.cgi?id=471315 Jf changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Jf --- Seems to be something with widgets. I added the same widges, cpu cores and power, and the issue came back. I remove them and it seems to be gone. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470583] Nothing happens after clicking on the update notifier
https://bugs.kde.org/show_bug.cgi?id=470583 Patrick Silva changed: What|Removed |Added CC||publiclyvisibleemail@gmail. ||com --- Comment #11 from Patrick Silva --- *** Bug 471876 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471876] Plasma 6 Wayland - Update applet in bottom (classic) task manager doesn't launch updating
https://bugs.kde.org/show_bug.cgi?id=471876 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 470583 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471347] Windows: Dark Scheme Bug
https://bugs.kde.org/show_bug.cgi?id=471347 aleventuri...@gmail.com changed: What|Removed |Added CC||aleventuri...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458701] Kate cannot edit a system file on nixos
https://bugs.kde.org/show_bug.cgi?id=458701 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- That seems to be a packaging issue, please report that to the nix package repo. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 460923] Allow tabs pulled outside of Kate to open in an new instance of Kate
https://bugs.kde.org/show_bug.cgi?id=460923 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- You can now detach a tab to a new window in the tab button context menu. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471875] Plasma 6 Wayland - (Flathub) Flatseal, (GTK/Gnome 44) fonts not displaying properly, (All GTK? Just Flatpaks? Nvidia issue?)
https://bugs.kde.org/show_bug.cgi?id=471875 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 471877] New: does not change the number of digits in the filename from tags
https://bugs.kde.org/show_bug.cgi?id=471877 Bug ID: 471877 Summary: does not change the number of digits in the filename from tags Classification: Applications Product: kid3 Version: 3.9.x Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: akuma...@gmail.com Target Milestone: --- for example, I have 4 tracks, in the tags it is numbered as 1, 2, 3, 4. but in the file name it goes like 01, 02, 03, 04. in the settings there is an item that seems to change the number of digits in the track number. but it didn't have any effect. it would be nice to be able to choose the numbering format in the file name (1 or 01 or 001). Or at least so that the numbers match the numbers in the tags. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471876] Plasma 6 Wayland - Update applet in bottom (classic) task manager doesn't launch updating
https://bugs.kde.org/show_bug.cgi?id=471876 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
