[Skanpage] [Bug 481002] New: Feature request: Introduce an option to automatically turn the backsides of pages 180°
https://bugs.kde.org/show_bug.cgi?id=481002 Bug ID: 481002 Summary: Feature request: Introduce an option to automatically turn the backsides of pages 180° Classification: Applications Product: Skanpage Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: syiad.al-d...@web.de Target Milestone: --- SUMMARY *** When using the automatic document feeder in duplex mode, the backsides of pages are scanned upside-down. It would be nice to have an option that automatically turns them around 180°. *** STEPS TO REPRODUCE 1. Scan pages using automatic document feeder in duplex mode 2. 3. OBSERVED RESULT Backsides of pages are upside-down. They have to be selected in the list on the the left hand side and then turned twice left or right. EXPECTED RESULT Skanpage can be set to automatically turn even pages (i.e. the backsides) 180° after scanning. 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.
[plasma-systemmonitor] [Bug 452763] CPU temperature not working for AMD sensor
https://bugs.kde.org/show_bug.cgi?id=452763 Arjen Hiemstra changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/ksystemstats/-/commit/19 ||cf85eeb1a85c8ef4fc02cd46a61 ||442e4c4e46c Resolution|--- |FIXED --- Comment #25 from Arjen Hiemstra --- Git commit 19cf85eeb1a85c8ef4fc02cd46a61442e4c4e46c by Arjen Hiemstra. Committed on 07/02/2024 at 11:23. Pushed by ahiemstra into branch 'master'. cpu: Also consider "temp1" and "temp2" for AMD temperature sensors Apparently some older CPUs/kernels report Tctl and/or Tdie as "temp1/2" so also check those names. In addition, be a little more verbose if we encounter something that doesn't match what we expect. M +5-4plugins/cpu/linuxcpuplugin.cpp https://invent.kde.org/plasma/ksystemstats/-/commit/19cf85eeb1a85c8ef4fc02cd46a61442e4c4e46c -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 481001] New: Skanpage quits when starting a scan without selecting scanner first.
https://bugs.kde.org/show_bug.cgi?id=481001 Bug ID: 481001 Summary: Skanpage quits when starting a scan without selecting scanner first. Classification: Applications Product: Skanpage Version: 23.08.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: syiad.al-d...@web.de Target Milestone: --- SUMMARY *** Even though the network scanner I want to use is already set from last time I used Skanpage, I have to click on the bottom right button to search for available scanners and (again) select the one I want to use. Otherwise Skanpage just quits when I select "Scan". *** STEPS TO REPRODUCE 1. Start Skanpage. Correct scanner is already shown in bottom right corner. 2. Apply scan mode settings as required 3. Click "Scan" OBSERVED RESULT Skanpage quits EXPECTED RESULT Skanpage scans as per the selected settings SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 23.10 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I have only one scanner that is connected via the network: Epson Stylus Office BX635FWD. However, that scanner shows up twice when I search for available scanners, namely as: - Epson PID 088F (epson2:net:nnn.nnn.n.nnn) - WSD Epson Stylus Office BX635FWD (airscan:w0:Epson Stylus Office BX635FWD) I'm using the former, because it offers more options for the scan settings, like using the ADF. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 474548] Filters do not work in GHNS dialogs
https://bugs.kde.org/show_bug.cgi?id=474548 Patrick Silva changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #11 from Patrick Silva --- This bug persists on neon unstable. Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 480841] Hardware sensors under sensors in system monitor seem to be broken in plasma 6
https://bugs.kde.org/show_bug.cgi?id=480841 Arjen Hiemstra changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/ksystemstats/-/commit/45 ||5ba6364c0323d907d3c99729f4b ||93f0bf50a94 --- Comment #3 from Arjen Hiemstra --- Git commit 455ba6364c0323d907d3c99729f4b93f0bf50a94 by Arjen Hiemstra. Committed on 07/02/2024 at 11:18. Pushed by ahiemstra into branch 'master'. lmsensors: Remove `\x00` from sensor object names Apparently we can end up with `\x00` in sensor object names in certain cases. This then results in path matching failing and sensors not being added properly. So get rid of any such characters in sensor object names. M +6-0plugins/lmsensors/lmsensors.cpp https://invent.kde.org/plasma/ksystemstats/-/commit/455ba6364c0323d907d3c99729f4b93f0bf50a94 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 479573] Horizontal bars don't allow setting data CPU temp range or can't automatically find it
https://bugs.kde.org/show_bug.cgi?id=479573 Arjen Hiemstra changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/libksysguard/-/commit/6b ||3b16c44b642239995ef2d8be0b2 ||872b9aa18e7 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Arjen Hiemstra --- Git commit 6b3b16c44b642239995ef2d8be0b2872b9aa18e7 by Arjen Hiemstra. Committed on 07/02/2024 at 11:17. Pushed by ahiemstra into branch 'master'. faces/horizontalbars: Allow specifying the data range from config In some cases, we may want to display sensors using this face that don't have a proper min/max range. So add the same sort of configuration that we have for other faces so it becomes possible to override the automatic data range with a manually specified one. While at it, port the actual bar implementation from a manual implementation to a ProgressBar with overridden contentItem, as that makes the code a fair bit easier to work with. A +32 -0faces/facepackages/horizontalbars/contents/config/main.xml M +24 -18 faces/facepackages/horizontalbars/contents/ui/Bar.qml A +45 -0faces/facepackages/horizontalbars/contents/ui/Config.qml [License: LGPL(v2.0+)] M +3-1 faces/facepackages/horizontalbars/contents/ui/FullRepresentation.qml https://invent.kde.org/plasma/libksysguard/-/commit/6b3b16c44b642239995ef2d8be0b2872b9aa18e7 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480760] When you in the split mode and want to go back to single mode, when you click the "Close" button, it always close the left window even though the active window is the left windo
https://bugs.kde.org/show_bug.cgi?id=480760
Felix Ernst changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
CC||felixer...@kde.org
--- Comment #1 from Felix Ernst ---
Some users want the "Close" button to close the active view and some want it to
close the inactive view. There is a setting to choose between the two.
In the Dolphin settings ("Configure Dolphin") window look for the checkbox
labeled "Turning off split view closes active pane" and uncheck it. Have fun!
:)
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 480963] Kwin spams QObject::startTimer related warning in systemd journal during user input
https://bugs.kde.org/show_bug.cgi?id=480963 thecooki...@gmail.com changed: What|Removed |Added CC||thecooki...@gmail.com --- Comment #4 from thecooki...@gmail.com --- Had this on my last boot as well. Will try to investigate more if I end up seeing it again as I don't know what triggers it either, unfortunately. That last boot has been on for a while though and the system has been in sleep mode as well. "Feb 06 10:58:33 HOSTNAME kwin_wayland[1383]: QObject::startTimer: Timers cannot have negative intervals" gets reported hundreds of times per second arch, plasma 6 rc2, 3700x+5700xt -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475320] Transition is not smooth when switching tabs
https://bugs.kde.org/show_bug.cgi?id=475320 Patrick Silva changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REPORTED --- Comment #3 from Patrick Silva --- It is still reproducible on both Arch Linux running Plasma 6 RC2 and neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481000] New: Kicker not highlighting selection, neither via keyboard nor hover
https://bugs.kde.org/show_bug.cgi?id=481000 Bug ID: 481000 Summary: Kicker not highlighting selection, neither via keyboard nor hover Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: yao...@protonmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 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. Install Plasma 6.0 RC2 (kde-unstable repository on Arch is my source) 2. Open Kicker 3. Try to use keyboard to navigate Kicker, or hover over items in the menu OBSERVED RESULT Nothing is highlighted in any way. EXPECTED RESULT Items hovered over, or selected with the keyboard, should be highlighted. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I have not yet tried a fresh install of Arch Linux, so this may be an issue of configuration. If you cannot reproduce it I will try a fresh install. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 474336] Horizontal scrollbar appears briefly on bottom when I open a KCM
https://bugs.kde.org/show_bug.cgi?id=474336 --- Comment #6 from Patrick Silva --- KDE Connect is the only affected KCM. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 480999] New: Print page range box too small to show 2 characters
https://bugs.kde.org/show_bug.cgi?id=480999 Bug ID: 480999 Summary: Print page range box too small to show 2 characters Classification: Applications Product: okular Version: 21.12.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: david.campbell...@googlemail.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 print dialogue 2. Open options 3. OBSERVED RESULT Pages from and pages to boxes are only wide enough to show one character. Which is a royal pain when trying to print 20-21 for example. The "pages" dialogue is also sometimes greyed out, and doesn't work when it is showing, instead printing the full range. Although this may be user error, I'm trying "20-21". EXPECTED RESULT View both characters SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Mint Victoria 21.3 (Ubuntu, cinnamon) (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.
[libkgapi] [Bug 468802] 23.04.0: test suite is failing
https://bugs.kde.org/show_bug.cgi?id=468802 --- Comment #3 from Daniel Vrátil --- Hi, I can't reproduce the crashes of the drive-* tests. Can you share a bactrace of one of the segfaulting tests, if you can still reproduce? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 474757] Double "Compress"/"Extract" menu entries in context menu.
https://bugs.kde.org/show_bug.cgi?id=474757 Igor Mironchik changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480881] When going back to Devices or Graphics categories already viewed - they become blank.
https://bugs.kde.org/show_bug.cgi?id=480881 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kinfocenter/-/merge_requests/189 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480998] New: In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 144.
https://bugs.kde.org/show_bug.cgi?id=480998 Bug ID: 480998 Summary: In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 144. Classification: Plasma Product: kwin Version: 5.93.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: plastininiko...@yandex.ru Target Milestone: --- SUMMARY *** In KDE Neon testing external monitor with a capability of 120 ghz displays only 60 when trying to set 144. Right behaviour in windows 11 and fedora 39 gnome. *** STEPS TO REPRODUCE 1. Connect an external monitor to laptop with 120 hz via USB4 type C to the display port 2. Switch refresh rate to 120 hz. OBSERVED RESULT only 60 hz EXPECTED RESULT 120 hz SOFTWARE/OS VERSIONS Windows 11: work macOS: work Linux: Fedora 39 (gnome) work KDE Neon Version: neon-testing-20240206-0538 don't work -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480997] New: Feature request: Create global shortcut to temporarily restrict user inputs (toddler proofing - kiosk)
https://bugs.kde.org/show_bug.cgi?id=480997 Bug ID: 480997 Summary: Feature request: Create global shortcut to temporarily restrict user inputs (toddler proofing - kiosk) Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: funkybom...@gmail.com Target Milestone: --- SUMMARY *** Based on the discussion at: https://discuss.kde.org/t/baby-proofing-the-desktop-control-of-inputs/9673 There are some scenarios where it is useful for a user to be able to temporarily restrict the inputs (mouse, keyboard, trackpad etc) while keeping the desktop unlocked (such as a kiosk usecase). I propose creating an option to give users the ability to create a global shortcut that disables the mouse and ignores all keystrokes (apart from the unlocking shortcut). Once the user gives the correct key combination then all the inputs get restored. A good key combination would be something that would not be easy to replicate by mashing on the keyboard. A good default could be Meta+Scroll Lock. The option should be exposed to the user somewhere in the settings and it should be possible for the user to reassign this functionality to a different shortcut. Any other system shortcuts (global, custom, etc) should probably be unavailable/inactive while this mode is active, in order to not interfere. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480641] fprint GUI setup does not work
https://bugs.kde.org/show_bug.cgi?id=480641 --- Comment #4 from Henning --- I was also able to completely normally register a different finger through the GUI, I think this is just systemsettings reacting because libfprint is not reacting. Now after this seemingly resultless fprintd-delete I open systemsettings again in the user section and it is still showing the entries. I cannot use the fingerprints in pkexec and sudo though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480641] fprint GUI setup does not work
https://bugs.kde.org/show_bug.cgi?id=480641 Henning changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Henning --- >> systemsettings kcm_users qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Cannot open: file:///var/home/kinoite/.face?0 Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Cannot open: file:///var/home/kinoite/.face qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Cannot open: file:///var/home/kinoite/.face qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Cannot open: file:///var/home/kinoite/.face qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Cannot open: file:///var/home/user/.face?0 qt.dbus.integration: QDBusConnection: name 'net.reactivated.Fprint' had owner '' but we thought it was ':1.174' qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Cannot open: file:///var/home/kinoite/.face?0 qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Cannot open: file:///var/home/user/.face?0 qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Cannot open: file:///var/home/kinoite/.face Attempted to set unsupported sample count 40 Attempted to set unsupported sample count 40 # then I had already cancelled the setup because nothing happened. meanwhile fprint-enroll >> fprintd-enroll Using device /net/reactivated/Fprint/Device/0 Enrolling right-index-finger finger. Enroll result: enroll-duplicate # I used that right index finger in the GUI too! >> fprintd-enroll -f right-thumb Using device /net/reactivated/Fprint/Device/0 Enrolling right-thumb finger. Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-completed RESULT This is really strange. The right thumb is now shown as registered in the systemsettings GUI, but the left index finger which gave an error is not shown. This may be a libfprint bug. I also already tried to delete the fingerprint earlier. fprintd-delete * found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors No fingerprints to delete on Synaptics Sensors -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 480996] New: Option to make the folder size dependent on file count instead of file size
https://bugs.kde.org/show_bug.cgi?id=480996 Bug ID: 480996 Summary: Option to make the folder size dependent on file count instead of file size Classification: Applications Product: filelight Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@malplena.net CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY Option to make the folder size dependent on file count instead of file size. It currently sizes each folder according to the total file size. My suggestion is adding an option to size the folders based on the total file count. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 479351] It is not possible to add Sub-ToDos in Kontact ToDo-List
https://bugs.kde.org/show_bug.cgi?id=479351 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||eventviews/-/commit/9388c7e ||c7de461550f4e5439b6802ea6d2 ||bd37b5 --- Comment #3 from Daniel Vrátil --- Git commit 9388c7ec7de461550f4e5439b6802ea6d2bd37b5 by Daniel Vrátil. Committed on 07/02/2024 at 10:25. Pushed by dvratil into branch 'release/24.02'. Fix 'Create sub-todo' action being always disabled Regression introduced while porting away from ETMCalendar. M +1-1src/todo/todoview.cpp https://invent.kde.org/pim/eventviews/-/commit/9388c7ec7de461550f4e5439b6802ea6d2bd37b5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479037] letter spacing increases when highlighting, at the beginning of the highlight
https://bugs.kde.org/show_bug.cgi?id=479037 --- Comment #2 from Henning --- Created attachment 165642 --> https://bugs.kde.org/attachment.cgi?id=165642=edit another video of the spacing bug This doesnt occur when typing random text, but when I enter a command and a long filename, had this with ffmpeg so using this command here. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 473847] To-Do View empty but To-Dos shown in Kontact summary page
https://bugs.kde.org/show_bug.cgi?id=473847 --- Comment #6 from Daniel Vrátil --- If you are using Kontact, there should be a standalone "To-do List" action in the Kontact side-panel that opens the "Todo View" that you would otherwise normally get in standalone KOrganizer toolbar - I'm pretty sure this hasn't changed in the Qt6 build. Or am I misunderstanding the problem? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479037] letter spacing increases when highlighting, at the beginning of the highlight
https://bugs.kde.org/show_bug.cgi?id=479037 --- Comment #1 from Henning --- I could still reproduce this Operating System: Fedora Linux 40 KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 (64-bit) Graphics Platform: offscreen Processors: 8 × AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx Memory: 5.7 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics I will do an update and try again. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 480619] Doesnt detect --user repository until a failed attempt to "add the flathub remote"
https://bugs.kde.org/show_bug.cgi?id=480619 --- Comment #5 from Henning --- and that spello in the first line is not me. I think that is this bug https://bugs.kde.org/show_bug.cgi?id=479037 seems to be a rendering issue in konsole? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480995] In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor
https://bugs.kde.org/show_bug.cgi?id=480995 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480994] switching "extend to left" to "extend to right" makes systray popup appear on the left side of the main screen
https://bugs.kde.org/show_bug.cgi?id=480994 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480993] Monitor quicksettings "extend to left/right" not working
https://bugs.kde.org/show_bug.cgi?id=480993 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480991] Windows resize oddly when 200% scaled monitor hot-replugs itself
https://bugs.kde.org/show_bug.cgi?id=480991 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480992] Kwin (wayland) crashes after idle for about one hour
https://bugs.kde.org/show_bug.cgi?id=480992 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 480619] Doesnt detect --user repository until a failed attempt to "add the flathub remote"
https://bugs.kde.org/show_bug.cgi?id=480619 Henning changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Henning --- 2332 ?00:00:01 DiscoverNotifie This process is still running after closing discover. reproducing: >> flatpak remote-delete --force --user flathub >> pkg-config refresh # discover not opened manually until now >> plasma-discover (through GUI, had no internet connection for some reason, >> didnt show flathub) >> flatpak remote-add --user flathub >> https://dl.flathub.org/repo/flathub.flatpakrepo >> plasma-discover org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false Couldn't get latest commit for [all my flatpak apps listed here] So I assume plasma-discover was not running as I invoked it via Terminal. Closed the process through terminal. Now launched Discover again, flathub (user) is showing up. This is strange, as it should have shown up before. But this is pretty minor, may be possible to close. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 479351] It is not possible to add Sub-ToDos in Kontact ToDo-List
https://bugs.kde.org/show_bug.cgi?id=479351 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/eventviews/-/merge_requests/96 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480994] switching "extend to left" to "extend to right" makes systray popup appear on the left side of the main screen
https://bugs.kde.org/show_bug.cgi?id=480994 --- Comment #2 from Henning --- The external monitor doesnt get any output anymore. I think I enabled "unify outputs" so that every monitor is displaying the same. So 1. log in, dialog pops up, select "extend to left" which is actually right 2. fiddle around, select "unify outputs", from then on the external screen is black 3. extend left right, causes but of applet appearing on the wrong side but still no output 4. "switch to external monitor only" makes both go black I use the monitor daily on Plasma 5, it has somewhat of a bad contact but it works normally. I moved the cable in and out so I exclude a hardware problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480995] New: In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor
https://bugs.kde.org/show_bug.cgi?id=480995 Bug ID: 480995 Summary: In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor Classification: Plasma Product: kwin Version: 5.93.0 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: plastininiko...@yandex.ru Target Milestone: --- SUMMARY *** In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor *** STEPS TO REPRODUCE 1. launch KDE Neon with 165 ghz 2. wait a bit 3. see crush OBSERVED RESULT native monitor is filled with one summary color of desktop wallpapers EXPECTED RESULT Normal monitor behavior SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.93 KDE Neon Version: neon-testing-20240206-0538 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480994] switching "extend to left" to "extend to right" makes systray popup appear on the left side of the main screen
https://bugs.kde.org/show_bug.cgi?id=480994 --- Comment #1 from Henning --- Feb 07 11:23:30 PC kwalletd6[1680]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC kactivitymanagerd[2045]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC kded6[1954]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC polkit-kde-authentication-agent-1[2073]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC konsole[3980]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC plasma-discover[4197]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC DiscoverNotifier[2332]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC baloorunner[2993]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC kdeconnectd[2305]: 2024-02-07T11:23:30 qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC org_kde_powerdevil[2074]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC plasmashell[1999]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC xdg-desktop-portal-kde[2075]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Feb 07 11:23:30 PC plasmashell[1999]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. Feb 07 11:23:30 PC plasmashell[1999]: qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Error decoding: qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml?timestamp=1707300491906: Unsupported image format Feb 07 11:23:30 PC plasmashell[1999]: qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Error decoding: qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml?timestamp=1707300491906: Unsupported image format Feb 07 11:23:30 PC plasmashell[1999]: qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Error decoding: qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml?timestamp=1707300491906: Unsupported image format Feb 07 11:23:30 PC plasmashell[1999]: qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Error decoding: qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml?timestamp=1707300491906: Unsupported image format Feb 07 11:23:30 PC plasmashell[1999]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. Feb 07 11:23:30 PC plasmashell[1999]: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. Feb 07 11:23:32 PC pipewire[1755]: mod.client-node: 0x5606b8529500: unknown peer 0x5606b850cbe0 fd:64 Feb 07 11:23:33 PC pipewire[1755]: mod.client-node: 0x5606b8425fd0: unknown peer 0x5606b850f5f0 fd:41 Feb 07 11:23:33 PC pipewire[1755]: mod.client-node: 0x5606b8304790: unknown peer 0x5606b834b300 fd:64 Feb 07 11:23:33 PC wireplumber[1757]: si-standard-link: in/out items are not valid anymore Feb 07 11:23:33 PC wireplumber[1757]: failed: failed to activate si-standard-link: error:si-standard-link: in/out items are not valid anymore -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480994] New: switching "extend to left" to "extend to right" makes systray popup appear on the left side of the main screen
https://bugs.kde.org/show_bug.cgi?id=480994 Bug ID: 480994 Summary: switching "extend to left" to "extend to right" makes systray popup appear on the left side of the main screen Classification: Plasma Product: kwin Version: 5.92.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- Followup on https://bugs.kde.org/show_bug.cgi?id=480993 I have a laptop with an external monitor over HDMI to my left, so I chose "extend to left" when the dialog automatically appeared. But it extended to the right, so I went to the systray "monitor configuration" applet and enabled "extend to the left". Now the monitor is black, only the main monitor is showing. Then I switched to "extend to the right" and the popup appeared on the other side, just above kickoff, still on the main screen, no changes to the screen layout, monitor still black Feb 07 11:20:20 PC plasmashell[1999]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:60: TypeError: Property 'pressed' of object QQuickMouseArea_QML_143(0x55a1d0f2fc70) is not a function Feb 07 11:20:22 PC plasmashell[1999]: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. Feb 07 11:20:22 PC plasmashell[1999]: kf.windowsystem.wayland: Failed to recreate shadow for PlasmaQuick::AppletPopup(0x55a1d01d8730, name="popupWindow") Feb 07 11:20:28 PC plasmashell[1999]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:60: TypeError: Type error Feb 07 11:20:33 PC plasmashell[1999]: kf.windowsystem.wayland: Failed to recreate shadow for PlasmaQuick::AppletPopup(0x55a1d01d8730, name="popupWindow") Those logs only indicate stuff about the applet, not about the monitor config not doing anything I think. The applet showing on the left when using "extend to the right" and appearing normal when using "extend to the left" is reproducible. Operating System: Fedora Linux 40 KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 (64-bit) Graphics Platform: offscreen Processors: 8 × AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx Memory: 5.7 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480993] New: Monitor quicksettings "extend to left/right" not working
https://bugs.kde.org/show_bug.cgi?id=480993 Bug ID: 480993 Summary: Monitor quicksettings "extend to left/right" not working Classification: Plasma Product: kwin Version: 5.92.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- I have an external monitor to the left of my laptop. I logged in, and it showed the dialog, I selected "extend to the left" and it is actually extended to the right. Then in the quicksettings menu switching to different modes causes lots of trouble, display going back, will report in another issue. Operating System: Fedora Linux 40 KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 (64-bit) Graphics Platform: offscreen Processors: 8 × AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx Memory: 5.7 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480847] Incorrect warning about Chromium proxy settings
https://bugs.kde.org/show_bug.cgi?id=480847 somebody changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from somebody --- I committed the fix. Thanks for the pointer. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 479175] pageStack.push() does not show the pushed page when using QT_QUICK_CONTROLS_MOBILE=1
https://bugs.kde.org/show_bug.cgi?id=479175 --- Comment #3 from b...@mogwai.be --- I got a bit further with debugging this, and it seems that my previous hunch was close. The problem seems to be related to using TapHandler instead of MouseArea. It seems that TapHandler's `onTapped` slot (which pushes a new page) is completely finished before the ColumnView gets to handle the ButtonRelease event. This triggers `setCurrentIndex` while m_mouseDown is still true, so it will not start the animation to slide to the new page. Once the ColumnView gets to process the button release event, it will treat it as a click on the current page instead of the new page, so it will start a new animation to slide to the current page rather than the newly pushed one. In contrast, with MouseArea, the ColumnView first gets to process the ButtonReleases event before MouseArea processes the click. I don't know know the reason of this difference, but could it perhaps be related to this: https://doc.qt.io/qt-6.6/qtquickhandlers-index.html#pointer-grab ? It says that Taphandler gets a first go since it's a child of the item. Next, the item itself (i.e. the delegate) gets a go, which means that it first goes through the childMouseEventFilter which decides whether or not to do anything with the click? So, effectively, it seems like TapHandler will therefore always finish before the filter? NB: As a *workaround*, one could use TapHandler's `onSingleTapped` together with `exclusiveSignals: (TapHandler.SingleTap | TapHandler.DoubleTap)` This ensures that the taphandler will only process the event after the double-click interval has expired, which is apparently long enough for columnview to do its business first. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480992] New: Kwin (wayland) crashes after idle for about one hour
https://bugs.kde.org/show_bug.cgi?id=480992 Bug ID: 480992 Summary: Kwin (wayland) crashes after idle for about one hour Classification: Plasma Product: kwin Version: 5.27.10 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: leandrosansi...@gmail.com Target Milestone: --- Created attachment 165641 --> https://bugs.kde.org/attachment.cgi?id=165641=edit energy settings SUMMARY Kwin_wayland Crashes on no activity. I've noticed that kwin logs to syslog when Kwin tries to put my two screens to sleep. One screen is on a HDMI port and the other on a Display Port. The line I often see on `dmesg` is: ``` [272940.976297] traps: VizCompositorTh[2705470] trap invalid opcode ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] ``` The screens are configured in the KDE settings to go to sleep after 10min. They never go though, instead flickering and finally turning on again. This time though, after leaving the computer doing nothing for about one hour, when I returned, Plasma was on a "reset" state, with no windows open. The screen was unlocked though, so I suspect that the plasma session did not restart (I did not have to unlock it or go back to SDDM). The applications set on autostart did not restart. Upon checking `dmesg`, unfortunately this is the best info I can get: ``` [229252.822425] traps: GlobalQueue[26][2674503] general protection fault ip:7fe76a2c1ddd sp:7fe7015fefd8 error:0 in libQt5Core.so.5.15.12[7fe76a09f000+2dd000] [230033.962062] traps: VizCompositorTh[2567709] trap int3 ip:7fbe4111290d sp:7fbded5fd2d0 error:0 in libcef.so[7fbe37a15000+9aec000] [230644.965366] traps: VizCompositorTh[2556985] trap invalid opcode ip:560a520d6d6e sp:7f2a2c9fe490 error:0 in signal-desktop[560a4d6b2000+7e36000] [230725.867704] traps: VizCompositorTh[2687472] trap invalid opcode ip:560a520d6d6e sp:7f2a2c9fe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] [232955.172067] traps: VizCompositorTh[2682322] trap int3 ip:7fbe4111290d sp:7fbdecbfd090 error:0 in libcef.so[7fbe37a15000+9aec000] [232993.119132] traps: VizCompositorTh[2688239] trap invalid opcode ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] [269637.931822] traps: VizCompositorTh[2549760] trap invalid opcode ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000] [270246.887782] traps: VizCompositorTh[2959470] trap invalid opcode ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000] [272940.976097] traps: VizCompositorTh[2963805] trap invalid opcode ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000] [272940.976297] traps: VizCompositorTh[2705470] trap invalid opcode ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] [272942.646675] traps: VizCompositorTh[2983487] trap invalid opcode ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000] [273551.878088] kwin_wayland[2279]: segfault at 0 ip 7f69ed36939a sp 73e2c930 error 4 in libkwin.so.5.27.10[7f69ed369000+327000] likely on CPU 31 (core 15, socket 0) [273551.878099] Code: 04 25 00 00 00 00 0f 0b 48 8b 04 25 00 00 00 00 0f 0b 8b 04 25 20 00 00 00 0f 0b 90 8b 04 25 20 00 00 00 0f 0b 90 f3 0f 1e fa <48> 8b 04 25 00 00 00 00 0f 0b 31 ff ff 15 14 ed 48 00 0f b7 04 25 [273551.882364] traps: VizCompositorTh[2983700] trap invalid opcode ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] [273585.084529] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [273585.084533] Bluetooth: BNEP filters: protocol multicast [273585.084537] Bluetooth: BNEP socket layer initialized ``` STEPS TO REPRODUCE 1. Configure the screens to switch off after 10min, as in the attached image. 2. let the computer idle. In my case, I left two dolphin windows, each with an embedded terminal (F4) open, doing some work (in my case, computing md5sum of some large files). 3. Go have breakfast and return after about 1 hour. 4. The workspace is empty, with no windows open. All previously running processes were killed. OBSERVED RESULT Plasma workspace empty, no windows open. All previously opened windows were killed. EXPECTED RESULT The screens should've been switched off. Maybe the screens would be locked, asking for authentication to unlock. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.0-0-MANJARO (amd64) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION Kwin Info: ``` KWin Support Information: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath
[kwin] [Bug 480991] New: Windows resize oddly when 200% scaled monitor hot-replugs itself
https://bugs.kde.org/show_bug.cgi?id=480991 Bug ID: 480991 Summary: Windows resize oddly when 200% scaled monitor hot-replugs itself Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kod...@gmail.com Target Milestone: --- SUMMARY *** I have my desktop configured with an LG 24UD58-B 3840x2160@60Hz monitor, set to 200% scaling, either on HDMI or DisplayPort, it will do this on either one. And a Dell P2414H at 1920x1080@60Hz at 100% scaling, over DisplayPort. When my primary monitor is put into DPMS power off state, and successfully turns itself off after displaying the "power save" notice, it does something odd when powering back on. At the instant the operating system powers it back on with DPMS controls, it hot detaches itself from DRM, then needs to be re-attached. This causes a video mode change, possibly causing scaling to temporarily reset to 100% and back to 200% again. This has the effect of causing several of my desktop windows to resize themselves. Wezterm in Wayland mode shrinks to a tiny box. Firefox, in its Wayland mode, maintains its size for the most part. Discord, an Electron app running in Xwayland mode, grows its window frame to 200% of its original size, but the content remains its original size in the top left corner of the window frame, while the rest of the window frame becomes transparent to what's underneath of it, and also becomes transparent to clicking in those empty regions. When resizing this Electron window's frame, or using the Super+Right button resize on a non-transparent region of the window contents, the window contents suddenly grow to the full size of the 200% scaled window frame. I have to shrink this Electron app every time I log back into my desktop, and grow the size of Wezterm to a usable size as well. STEPS TO REPRODUCE 1. Have a 200% scaled monitor that does the above indicated DPMS dance every time it's powered back on, and a 100% scaled monitor to the right of it, which does not do any sort of port resetting when restored to powered on state. 2. Start some of the above mentioned apps, and arrange their windows in a semblance of normalcy. 3. Lock the screen. 4. Press the Escape key to DPMS power off. 5. Wait for the display to fully power off. 6. Move the mouse or press a key to power back on. 7. Unlock the desktop. OBSERVED RESULT Several different apps, depending on GTK+, Qt, Electron, either Xwayland or Wayland native, will be resized oddly, in somewhat consistent ways depending on what type of app it is. EXPECTED RESULT Windows should maintain their original size as they had prior to the video mode change, considering the mode change was same mode to same mode, but maybe had an inconsistent mode in between due to the DPMS power cycling and subsequent DRM mode reset. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux rolling, testing repositories enabled KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION None that I can think of. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 479351] It is not possible to add Sub-ToDos in Kontact ToDo-List
https://bugs.kde.org/show_bug.cgi?id=479351 Daniel Vrátil changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||dvra...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476607] Palette swatch group not saving groups
https://bugs.kde.org/show_bug.cgi?id=476607 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||regression --- Comment #2 from Halla Rempt --- Thank you for the report. I can confirm the issue and that it is a regression. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480542] Appimage looking for PyQt5.QtTest in the wrong place
https://bugs.kde.org/show_bug.cgi?id=480542 Halla Rempt changed: What|Removed |Added Keywords||triaged CC||ha...@valdyas.org --- Comment #2 from Halla Rempt --- I cannot reproduce this, I'm afraid. Running the script in krita's scripter or running it in a system python both work for me. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480704] BIG CRASH AFTER LATEST UPDATE IN TESTING EDITION - 2024-02-01
https://bugs.kde.org/show_bug.cgi?id=480704 Jonathan Riddell changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Jonathan Riddell --- That should also sort the jpegcreatorsettings5.kcfg issue too. Let me know if you have further issues. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480704] BIG CRASH AFTER LATEST UPDATE IN TESTING EDITION - 2024-02-01
https://bugs.kde.org/show_bug.cgi?id=480704 --- Comment #7 from Jonathan Riddell --- Thanks for reporting this valuable information. I've added versioned breaks to kio-extras5 for the files which moved from the old packages there https://invent.kde.org/neon/neon-packaging/kio-extras5/-/commit/48a5773f5ddaa490ac0056048846b8e5ca6b19b6 (Note we have extra QA on User edition which will catch this but for testing edition we are more reliable on helpful testers like you) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480601] Crash when continuous selecting by color label reference includes a transform mask
https://bugs.kde.org/show_bug.cgi?id=480601 Halla Rempt changed: What|Removed |Added OS|All |Microsoft Windows Ever confirmed|0 |1 CC||ha...@valdyas.org Status|REPORTED|CONFIRMED --- Comment #1 from Halla Rempt --- Thank you for the report. I can confirm the issue both with the 5.2.2 appimage and a build from master: krita(38255)/(krita.general) T: [ 0: /home/halla/dev/i-krita//lib/x86_64-linux-gnu/libkritaglobal.so.20(kisBacktrace()+0x48) [0x7fc1fa1de408] 1: /home/halla/dev/i-krita//lib/x86_64-linux-gnu/libkritaimage.so.20(KisMergeLabeledLayersCommand::collectNodes(KisSharedPtr, QList >&, QList&) const+0x99c) [0x7fc1f8ce949c] 2: /home/halla/dev/i-krita//lib/x86_64-linux-gnu/libkritaimage.so.20(KisMergeLabeledLayersCommand::collectNodes(KisSharedPtr, QList >&, QList&) const+0x2b8) [0x7fc1f8ce8db8] 3: /home/halla/dev/i-krita//lib/x86_64-linux-gnu/libkritaimage.so.20(KisMergeLabeledLayersCommand::collectNodes(KisSharedPtr, QList >&, QList&) const+0x2b8) [0x7fc1f8ce8db8] 4: /home/halla/dev/i-krita//lib/x86_64-linux-gnu/libkritaimage.so.20(KisMergeLabeledLayersCommand::mergeLabeledLayers()+0x71) [0x7fc1f8ce9a81] 5: /home/halla/dev/i-krita//lib/x86_64-linux-gnu/libkritaimage.so.20(KisMergeLabeledLayersCommand::redo()+0x14) [0x7fc1f8cec024] 6: /home/halla/dev/i-krita//lib/x86_64-linux-gnu/libkritaimage.so.20(KisStrokeStrategyUndoCommandBased::doStrokeCallback(KisStrokeJobData*)+0x7e) [0x7fc1f8e367de] 7: /home/halla/dev/i-krita//lib/x86_64-linux-gnu/libkritaimage.so.20(+0x212010) [0x7fc1f8c12010] 8: /home/halla/dev/deps/lib/libQt5Core.so.5(+0xd14d2) [0x7fc1f74d14d2] 9: /home/halla/dev/deps/lib/libQt5Core.so.5(+0xce223) [0x7fc1f74ce223] 10: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7fc1f6c94ac3] 11: /lib/x86_64-linux-gnu/libc.so.6(+0x126660) [0x7fc1f6d26660] ] -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475536] Crashes on quick group with both layers selected and a selection
https://bugs.kde.org/show_bug.cgi?id=475536 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #6 from Halla Rempt --- Okay, then we can close the bug: this like a bug in Debian's Qt. Note that Krita 5.1.5 is pretty old by now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480675] I can use the shortcut key "ctrl u" to mask the filter and then overlay the filter mask
https://bugs.kde.org/show_bug.cgi?id=480675 Halla Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||ha...@valdyas.org --- Comment #1 from Halla Rempt --- I'm not sure what you mean: ctrl-u by default opens the HSV/HSL filter dialog. You can create a filter mask from that dialog. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480704] BIG CRASH AFTER LATEST UPDATE IN TESTING EDITION - 2024-02-01
https://bugs.kde.org/show_bug.cgi?id=480704 --- Comment #6 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #5) > The "pkcon update" moves past the thumbnail grid, kwin-addons now but > stumbles on > '/usr/share/config.kcfg/jpegcreatorsettings5.kcfg', which is also in > package kio-extras-data If I repeat the update, I get ... Error while installing package: trying to overwrite '/usr/share/doc/HTML/ca/kioslave5/bzip2/index.cache.bz2', which is also in package kio-extras-data 4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480677] Canvas-only mode and Normal mode remember dockers layout separately, unless restarting Krita
https://bugs.kde.org/show_bug.cgi?id=480677 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org --- Comment #1 from Halla Rempt --- I'm not sure this is actually fixable, because it's tied in with how Qt remembers dockers: through saving the entire window state. Canvas-only mode is a separate window state from normal mode, so it saves the dockers separately. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480699] Sample Screen Color doesn't work in MacOS
https://bugs.kde.org/show_bug.cgi?id=480699 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Halla Rempt --- Sorry, that is not possible: macOS doesn't allow applications to access windows that do not belong to the application. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480705] UI switches between HDR and SDR each time 2-3 seconds passes after mouse cursor stops moving
https://bugs.kde.org/show_bug.cgi?id=480705 Halla Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||ha...@valdyas.org Status|REPORTED|NEEDSINFO --- Comment #1 from Halla Rempt --- It sounds more like a system problem... 10 bit mode is not HDR, though. Please attach the contents of help->system information for bug reports to the report and tell us exactly what hardware you have and how you have enabled "10 bit display mode". Also please tell us what colorspace and channel depth your image uses. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 480990] New: KMail crashes when trying to open .mbox file
https://bugs.kde.org/show_bug.cgi?id=480990 Bug ID: 480990 Summary: KMail crashes when trying to open .mbox file Classification: Applications Product: kmail2 Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rdkr...@gmail.com Target Milestone: --- Application: kmail (5.24.4 (23.08.4)) Qt Version: 5.15.10 Frameworks Version: 5.113.0 Operating System: Linux 6.7.1-060701-generic x86_64 Windowing System: X11 Distribution: Rhino Linux 2023.4 (mainline) DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: what do you want me to input here? I have no idea waht causes this The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted [KCrash Handler] #4 0x702561a9998b in pthread_kill () at /lib/x86_64-linux-gnu/libc.so.6 #5 0x702561a42856 in raise () at /lib/x86_64-linux-gnu/libc.so.6 #6 0x702561a268b7 in abort () at /lib/x86_64-linux-gnu/libc.so.6 #7 0x702561ea5fde in ??? () at /lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x702561ebae5c in ??? () at /lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x702561ea5a29 in std::terminate() () at /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x702561ebb0e8 in __cxa_throw () at /lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x702562290216 in qBadAlloc() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x702562294bad in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x702562338bdc in QByteArray::append(char const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x70256251122e in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x702560339305 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #16 0x70256251122e in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x70256030aad9 in KIO::SlaveInterface::data(QByteArray const&) () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #18 0x70256030d098 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #19 0x70256030b42b in KIO::SlaveInterface::dispatch() () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #20 0x7025603106d1 in KIO::Slave::gotInput() () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #21 0x70256251122e in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7025625046f3 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x70256316bce5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7025624d6558 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7025624d9d7d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x702562533eff in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x70255e1462e5 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x70255e1a45ff in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x70255e144403 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x702562533569 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7025624d4ecb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7025624dd828 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x6219da5171b9 in ??? () #34 0x702561a280d0 in ??? () at /lib/x86_64-linux-gnu/libc.so.6 #35 0x702561a28189 in __libc_start_main () at /lib/x86_64-linux-gnu/libc.so.6 #36 0x6219da5178a5 in ??? () [Inferior 1 (process 55723) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480751] problems with hotkeys
https://bugs.kde.org/show_bug.cgi?id=480751 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Halla Rempt --- Sorry, but you need to be more explicit about what the issue is. The subject talks about hotkeys, the summary about the color changing, so it's not clear what your problem is. It might be better to ask a question on krita-artists.org, where other artists can help you with the way Krita works. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 480766] Yakuake loses focus after split terminal
https://bugs.kde.org/show_bug.cgi?id=480766 --- Comment #2 from Dmitrii Chermnykh --- There are actually 2 kinds of splits now: Splits in Shortcuts in the Konsolepart section that work as expected and show the same headers as in Konsole Splits in Shortcuts in the Yakuake section that don't switch the focus to the new pane and don't display headers, binded by default -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480872] Brush editor doesn't update when editing filter brush settings, in my case changing filter to any other. Poking around unresposive brush editor popup causes krita to crash.
https://bugs.kde.org/show_bug.cgi?id=480872 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Halla Rempt --- Hi, I reproduce this, but only on Windows and MacOS, it doesn't happen on Linux. MacOS doesn't seem to crash. The crash in the attachment happens in the preferences dialog not the brush editor, though, but I get this crash log: krita.exe caused an Access Violation at location 7FFEBF042E39 in module libkritaglobal.dll Reading from location . AddrPC Params 7FFEBF042E39 0049C0EFB340 7FFEBC8FC1AB 4042947AE147AE14 libkritaglobal.dll!KisSignalCompressor::start+0xe9 7FFEBC570CBB 7FFEBC57DE55 00DF021D Qt5Core.dll!doActivate+0x56b 7FFEBC570CBB 7FFEBC5793D0 01EC385DE760 0049C0EFB5C8 Qt5Core.dll!doActivate+0x56b 7FFEBCA83854 0049C0EFB7D0 7FFEBCA82010 7FFEBC758D60 Qt5Widgets.dll!QDoubleSpinBoxPrivate::emitSignals+0x144 7FFEBCA7BE5B 3FF0 3FF0 7FFEBC758935 Qt5Widgets.dll!QAbstractSpinBoxPrivate::setValue+0xfb 7FFEBCA820B2 4029 4058FF5C28F5C28F Qt5Widgets.dll!QDoubleSpinBox::setValue+0x82 7FFEBBAC8872 0049C0EFBCD8 0049C0EFB970 libkritawidgetutils.dll!KisParseSpinBoxPrivate::setValue+0x92 7FFEBBAD1F1F 01090271 0009 012B libkritawidgetutils.dll!KisSliderSpinBoxPrivate::setValue+0x6f 7FFEBBAD6BD6 0049C0EFB7E8 7FFEBBC5A61B 0049C0EFB9A0 libkritawidgetutils.dll!KisSliderSpinBoxPrivate::lineEditMouseReleaseEvent+0x106 7FFEBC53E298 0049C0EFBCD8 0003 0049C0EFB970 Qt5Core.dll!QCoreApplicationPrivate::sendThroughObjectEventFilters+0xf8 7FFEBC8EC58F 0049C0EFB9A0 01EC1E247740 0049C0EFB9A8 Qt5Widgets.dll!QApplicationPrivate::notify_helper+0xef 7FFEBC8EF20A Qt5Widgets.dll!QApplication::notify+0x1bca 7FFEBD677388 00F802C6 3FF0 libkritaui.dll!KisApplication::notify+0xa8 7FFEBC53DFB2 3FF0 Qt5Core.dll!QCoreApplication::notifyInternal2+0x92 7FFEBC8ECE6F 0201 7FFEBA26AA06 0049 Qt5Widgets.dll!QApplicationPrivate::sendMouseEvent+0x36f 7FFEBC943091 7FFF1D161834 7FFEBC846800 Qt5Widgets.dll!QWidgetWindow::handleMouseEvent+0x7d1 7FFEBC941CBC 0049C0EFC1C8 01EC1B6D52A0 0003 Qt5Widgets.dll!QWidgetWindow::event+0xbc 7FFEBC8EC5A3 03A30831 00030320 0200 Qt5Widgets.dll!QApplicationPrivate::notify_helper+0x103 7FFEBC8ED823 3FF0 0049C0EFC1C8 Qt5Widgets.dll!QApplication::notify+0x1e3 7FFEBD677388 01EC1E246C40 7FFEBBC64213 0001 libkritaui.dll!KisApplication::notify+0xa8 7FFEBC53DFB2 76E6908DD713 76E6908DD773 Qt5Core.dll!QCoreApplication::notifyInternal2+0x92 7FFEBBC25FD7 01EC23672670 01EC1E5B8110 7FFEBC40D780 Qt5Gui.dll!QGuiApplicationPrivate::processMouseEvent+0xc07 7FFEBBC0D1EA 01EC1E5B81E0 0024 Qt5Gui.dll!QWindowSystemInterface::sendWindowSystemEvents+0xda 7FFEBC5920FC 01EC35242640 0049C0EFF730 Qt5Core.dll!QEventDispatcherWin32::processEvents+0x5c 7FFEBA2D8A35 0049C0EFF658 7FFEBC389D60 7FFEBC40D780 qwindows.dll!QWindowsGuiEventDispatcher::processEvents+0x15 7FFEBC53B236 01EC0002 01EC0002 01EC237B5B30 Qt5Core.dll!QEventLoop::exec+0x1e6 7FFEBC53E54D 0049C0EFF6F8 7FFE 0049C0EFF6C8 Qt5Core.dll!QCoreApplication::exec+0x6d 7FFEBF1155D9 7FF729D15110 krita.dll!krita_main+0x41a9 7FF729D113D6 krita.exe!__tmainCRTStartup+0x276 7FF729D11156 krita.exe!WinMainCRTStartup+0x16 7FFF1F3B257D KERNEL32.DLL!BaseThreadInitThunk+0x1d 7FFF1F50AA78 ntdll.dll!RtlUserThreadStart+0x28 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 480766] Yakuake loses focus after split terminal
https://bugs.kde.org/show_bug.cgi?id=480766 Dmitrii Chermnykh changed: What|Removed |Added CC||chermnykh2...@gmail.com --- Comment #1 from Dmitrii Chermnykh --- Can confirm In plasma 5 when I've pressed ctrl+shift+) or ctrl+shift+( the focus used to switch to the new pane automatically In plasma 6 rc2 I need to click to switch the focus -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480530] Every time I try to play my animation test from my animation timeline it glitches and shows pieces of two frames cut off in the centre of the drawing at the same time... it even s
https://bugs.kde.org/show_bug.cgi?id=480530 Halla Rempt changed: What|Removed |Added Severity|critical|normal CC||ha...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480971] kwin_wayland random crash in math in KWin::SurfaceItem::refreshRateEstimation
https://bugs.kde.org/show_bug.cgi?id=480971 --- Comment #4 from Dmitrii Chermnykh --- Could the `average` value at https://invent.kde.org/plasma/kwin/-/blob/v5.93.0/src/scene/surfaceitem.cpp?ref_type=tags#L110 also become 0 for the same reason as in the report? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480190] Dolphin QML HTML injection
https://bugs.kde.org/show_bug.cgi?id=480190 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk --- Comment #3 from Jonathan Marten --- Created attachment 165640 --> https://bugs.kde.org/attachment.cgi?id=165640=edit Example screen shot Maybe what the reporter means is that it is possible to inject HTML into the error message displayed when a file or folder does not exist, as shown in the screen shot if Dolphin is started with the command line dolphin "HTML Injection" However, there is no obvious exploit either remotely or by viewing an exploit file name or file contents, so it is not likely to be a securiry risk. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468887] Kate printing formatting problems
https://bugs.kde.org/show_bug.cgi?id=468887 connorpick...@gmail.com changed: What|Removed |Added Platform|Neon|Fedora RPMs Version|23.04.0 |23.08.4 CC||connorpick...@gmail.com --- Comment #2 from connorpick...@gmail.com --- Today I printed a document to PDF and also printed a physical copy. At the bottom of each page, errors were present in both the digital and physical results: page breaks cut through characters, so character ascenders would appear on page 2 while most of the character prints on page 3. Steps to reproduce: 1. print a multiple-page document to file OR physically (i am also using 8.5x11 paper, usa encoding & keyboard) 2. check each bottom line for misprinted characters Observed result: characters are split across a page break, poor readability Expected: Characters should never be split across pages; each line is discretely on its own page. Environment: Fedora Linux 39 KDE Plasma 5.27.10 KDE Frameworks 5.113.10 QT version: 5.15.12 Observed result: -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever
https://bugs.kde.org/show_bug.cgi?id=406917 --- Comment #19 from Rigo Wenning --- Akonadi is unfit for synchronization. If you use nextcloud or any other remote calendar, you risk your data. This is known to me and wasn't fixed since 10 years now and that's why I unfortunately had to abandon KDE-PIM. Since then, no issue whatsoever with my remote calendar. Akonadi is just not usable for production. Too much play and candy, too little serious protocol work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480898] Once an applet is resized to the horizontal max, can' t resize it back
https://bugs.kde.org/show_bug.cgi?id=480898 Marco Martin changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/libplasma/-/commit/c2965 |ma/libplasma/-/commit/cebd2 |a5420366fad66ae3e1d450febb3 |df6b61f03682355cde6c60feb01 |330f879b|792559c3 --- Comment #4 from Marco Martin --- Git commit cebd2df6b61f03682355cde6c60feb01792559c3 by Marco Martin. Committed on 07/02/2024 at 08:40. Pushed by mart into branch 'Plasma/6.0'. Don't let applet popups span the whole screen It's possible to resize some appplets as big as the screen, and in that case the resize borders get disabled as soon as they touch the screen edge, with the possibility to lock the user out from being able to resize the window down again. Limit the maximum size the use can resize the popup to be 95% of the screen size M +17 -1src/plasmaquick/appletpopup.cpp M +1-0src/plasmaquick/appletpopup.h https://invent.kde.org/plasma/libplasma/-/commit/cebd2df6b61f03682355cde6c60feb01792559c3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480898] Once an applet is resized to the horizontal max, can' t resize it back
https://bugs.kde.org/show_bug.cgi?id=480898 Marco Martin changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/libplasma/-/commit/c2965 ||a5420366fad66ae3e1d450febb3 ||330f879b --- Comment #3 from Marco Martin --- Git commit c2965a5420366fad66ae3e1d450febb3330f879b by Marco Martin. Committed on 07/02/2024 at 08:40. Pushed by mart into branch 'master'. Don't let applet popups span the whole screen It's possible to resize some appplets as big as the screen, and in that case the resize borders get disabled as soon as they touch the screen edge, with the possibility to lock the user out from being able to resize the window down again. Limit the maximum size the use can resize the popup to be 95% of the screen size M +17 -1src/plasmaquick/appletpopup.cpp M +1-0src/plasmaquick/appletpopup.h https://invent.kde.org/plasma/libplasma/-/commit/c2965a5420366fad66ae3e1d450febb3330f879b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480312] Plasma crashes in QMimeDataPrivate::retrieveTypedData() when trying to create a Sticky Note with a url dragged from Vivaldi browser
https://bugs.kde.org/show_bug.cgi?id=480312 Akseli Lahtinen changed: What|Removed |Added CC||akse...@akselmo.dev --- Comment #2 from Akseli Lahtinen --- I can't reproduce this crash on my Plasma 6 setup Operating System: Fedora Linux 39 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.0 Kernel Version: 6.7.3-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 477447] Invalid items shown after searching
https://bugs.kde.org/show_bug.cgi?id=477447 Eric Armbruster changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480858] Crash while trying to connect find bluetooth mouse
https://bugs.kde.org/show_bug.cgi?id=480858 Akseli Lahtinen changed: What|Removed |Added CC||akse...@akselmo.dev Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Akseli Lahtinen --- Hi, can you install debug symbols and see if the crash happens again? https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Backtraces -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479934] Incorrect display of blur effect
https://bugs.kde.org/show_bug.cgi?id=479934 --- Comment #12 from Vlad Zahorodnii --- Ack, I can reproduce that. I had background contrast effect disabled :D -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479934] Incorrect display of blur effect
https://bugs.kde.org/show_bug.cgi?id=479934 Bug Janitor Service changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #11 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/5132 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480479] plasmashell spams system logs with errors ( PluginOpenAnimation: Animation is null! and OpenAnimation: Failed to open animation!)
https://bugs.kde.org/show_bug.cgi?id=480479 --- Comment #2 from Silviu C. --- Ah. It seem Doom 2016 is naughty. Linking a bug report: https://github.com/ValveSoftware/Proton/issues/6958 A partial fix may be to use this dll: https://github.com/Riesi/CChromaEditor/releases/tag/EMPTY1.0.0 -- You are receiving this mail because: You are watching all bug changes.
