[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections
https://bugs.kde.org/show_bug.cgi?id=350521 Denis Nelubin changed: What|Removed |Added CC||dnelu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 470194] New: Coverflow in picturezoom
https://bugs.kde.org/show_bug.cgi?id=470194 Bug ID: 470194 Summary: Coverflow in picturezoom Classification: Applications Product: kasts Version: 23.04.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: hans.ten...@posteo.de Target Milestone: --- SUMMARY *** Is it possible to show the coverflow in the picturezoom automaticaly too, perhaps with a own option in the settings? At the moment you have reopen the picturezoom, when there is a new coverpicture. Some podcasts use this feature with realy many pictures, somtime in short time and than you have to reopen and reopen and reopen ... the picturezoom. *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- 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.
[valgrind] [Bug 470121] Can't run callgrind_control with valgrind 3.21.0 because of perl errors
https://bugs.kde.org/show_bug.cgi?id=470121 Paul Floyd changed: What|Removed |Added Assignee|josef.weidendor...@gmx.de |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 470193] New: Kinfocenter inconsistently respecting chosen monospace font
https://bugs.kde.org/show_bug.cgi?id=470193 Bug ID: 470193 Summary: Kinfocenter inconsistently respecting chosen monospace font Classification: Applications Product: kinfocenter Version: 5.27.4 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: leonardogilr...@gmail.com CC: sit...@kde.org Target Milestone: --- SUMMARY I have chosen another font other than the default for monospace. If I go into Devices > Firmware Security, I see my chosen font. If instead go into Devices > CPU I see the default font from KDE. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 5.15.0-70-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470192] New: Okular shows the RTL text in correct view but reads it from left to right
https://bugs.kde.org/show_bug.cgi?id=470192 Bug ID: 470192 Summary: Okular shows the RTL text in correct view but reads it from left to right Classification: Applications Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: mh.firouz...@gmail.com Target Milestone: --- Created attachment 159218 --> https://bugs.kde.org/attachment.cgi?id=159218=edit Okular successful result to find RTL text in reversed char order Hi there, It's a major bug in Okular PDF reader app, when I want to search for a word in RTL language if I type the word in reverse order of characters it will find it but if I type the word as the correct way in RTL version, it can not find it! The same problem with copy/paste text from Okular, an RTL text in correct view copied from Okular and pasted to another app will be in reversed character order too! It seems that Okular it self will read any text from left to right even if the text is in a RTL language; it's not clear for me how Okular shows the RTL text in a good format but reads it from left to right!! I don't know how apps are figuring out BiDi of a text, but if a text contains `U+202E` so it probably is a RTL text. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456987] Open with... not working in AppImage
https://bugs.kde.org/show_bug.cgi?id=456987 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|7.8.0 | Status|REOPENED|CONFIRMED Version|8.0.0 |8.1.0 --- Comment #23 from caulier.gil...@gmail.com --- I just tested with 8.1.0 AppImage pre-release, and open with still empty under Kubuntu 22.04. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 225807] Add icon-view customization options from setup dialog into main menu
https://bugs.kde.org/show_bug.cgi?id=225807 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.1.0 Resolution|--- |INTENTIONAL Status|CONFIRMED |RESOLVED -- 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.
[drkonqi] [Bug 470190] Dr. Konqi doesn't always show up when plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=470190 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.
[digikam] [Bug 466893] Hidden elements in the Pick Label and Color Label locations
https://bugs.kde.org/show_bug.cgi?id=466893 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |INTENTIONAL Version Fixed In||8.1.0 Status|REPORTED|RESOLVED --- Comment #6 from caulier.gil...@gmail.com --- Closed as intentional following Maik comment #5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470191] New: Crash in Configure Desktop and Wallpaper when Latte Dock is installed
https://bugs.kde.org/show_bug.cgi?id=470191 Bug ID: 470191 Summary: Crash in Configure Desktop and Wallpaper when Latte Dock is installed Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: tildear...@protonmail.com Target Milestone: 1.0 SUMMARY plasmashell will crash if plasma_containmentactions_lattecontextmenu.so loads by going to Configure Desktop and Wallpaper... > Mouse Actions. I don't know whether to report it as a plasmashell bug or a latte-dock one, so I reported it as plasmashell. May not reproduce all the time. Backtrace: ``` (gdb) backtrace #0 0x7fff7fc93b42 in () at /usr/lib/qt/plugins/plasma_containmentactions_lattecontextmenu.so #1 0x7fff7fc9624b in () at /usr/lib/qt/plugins/plasma_containmentactions_lattecontextmenu.so #2 0x75cecfe7 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffda20, r=, this=0x58e39a80, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #3 doActivate(QObject*, int, void**) (sender=0x55f5cc60, signal_index=13, argv=0x7fffda20) at kernel/qobject.cpp:3923 #4 0x77ca72e7 in Plasma::Applet::userConfiguringChanged(bool) (this=, _t1=, _t1@entry=false) at /usr/src/debug/plasma-framework/build/src/plasma/KF5Plasma_autogen/include/moc_applet.cpp:598 #5 0x77ca85c9 in Plasma::Applet::setUserConfiguring(bool) (this=, configuring=configuring@entry=false) at /usr/src/debug/plasma-framework/plasma-framework-5.106.0/src/plasma/applet.cpp:585 #6 0x77f5dd51 in PlasmaQuick::ConfigView::~ConfigView() (this=0x5a1877a0, this=) at /usr/src/debug/plasma-framework/plasma-framework-5.106.0/src/plasmaquick/configview.cpp:284 #7 0x5558422a in ContainmentConfigView::~ContainmentConfigView() (this=0x5a1877a0, this=) at /usr/src/debug/plasma-workspace/plasma-workspace-5.27.5/shell/containmentconfigview.cpp:62 #8 ContainmentConfigView::~ContainmentConfigView() (this=0x5a1877a0, this=) at /usr/src/debug/plasma-workspace/plasma-workspace-5.27.5/shell/containmentconfigview.cpp:62 #9 0x75cdf65e in QObject::event(QEvent*) (this=0x5a1877a0, e=0x58bab1e0) at kernel/qobject.cpp:1334 #10 0x7693593f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x75cb7b18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5a1877a0, event=0x58bab1e0) at kernel/qcoreapplication.cpp:1064 #12 0x75cbca7b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x5562fa70) at kernel/qcoreapplication.cpp:1821 #13 0x75d03088 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55707410) at kernel/qeventdispatcher_glib.cpp:277 #14 0x7470c53b in g_main_dispatch (context=0x7fffe8000ee0) at ../glib/glib/gmain.c:3460 #15 g_main_context_dispatch (context=0x7fffe8000ee0) at ../glib/glib/gmain.c:4200 #16 0x74769219 in g_main_context_iterate.constprop.0 (context=0x7fffe8000ee0, block=1, dispatch=1, self=) at ../glib/glib/gmain.c:4276 #17 0x7470b1a2 in g_main_context_iteration (context=0x7fffe8000ee0, may_block=1) at ../glib/glib/gmain.c:4343 #18 0x75d06f0c in QEventDispatcherGlib::processEvents(QFlags) (this=0x5570f800, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #19 0x75cb6824 in QEventLoop::exec(QFlags) (this=this@entry=0x7fffdeb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #20 0x75cb7cc3 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #21 0x5557816c in main(int, char**) (argc=, argv=) at /usr/src/debug/plasma-workspace/plasma-workspace-5.27.5/shell/main.cpp:235 ``` STEPS TO REPRODUCE 1. Install Latte Dock 0.10.9. 2. Right click on desktop and select Configure Desktop and Wallpaper. 3. Go to Mouse Actions. 4. Change (or add) one of the actions. Set the action to Standard Latte Menu. When this happens, plasma_containmentactions_lattecontextmenu.so will be loaded into memory. 5. Click OK. plasmashell will crash. OBSERVED RESULT Crash. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.107.62.realtime1-2-rt-lts (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 470190] Dr. Konqi doesn't always show up when plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=470190 tildearrow changed: What|Removed |Added Summary|Dr. Konqi doesn't show up |Dr. Konqi doesn't always |at all when plasmashell |show up when plasmashell |crashes |crashes -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457272] Incorrect UI Element Padding under KDE with Breeze Theme at 1.5 scale
https://bugs.kde.org/show_bug.cgi?id=457272 --- Comment #13 from caulier.gil...@gmail.com --- Freddie, The Linux AppImage 8.1.0 pre-release includes Breeze Widget style module which will improve certainly the way to render widget in digiKam. Please test with the bundle available here : https://files.kde.org/digikam/ How to run digiKam AppImage : https://docs.digikam.org/en/getting_started/installation.html#digikam-on-linux The Breeze widget style must be selected in Setup/Misc/Appearence tab : https://docs.digikam.org/en/setup_application/miscs_settings.html#appearance-settings Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 470190] New: Dr. Konqi doesn't show up at all when plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=470190 Bug ID: 470190 Summary: Dr. Konqi doesn't show up at all when plasmashell crashes Classification: Applications Product: drkonqi Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tildear...@protonmail.com Target Milestone: --- SUMMARY Like https://bugs.kde.org/show_bug.cgi?id=409961 but happens on X11 too. STEPS TO REPRODUCE 1. Crash plasmashell 2. Wait 3. OBSERVED RESULT Nothing. plasmashell restarts and Dr. Konqi never appears. Not even in the tray. EXPECTED RESULT Dr. Konqi appears. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: 5.15.107.62.realtime1-2-rt-lts (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Graphics Platform: X11 ADDITIONAL INFORMATION This might be caused by the fact that plasmashell isn't present when Dr. Konqi tries to show up in the tray but shouldn't Dr. Konqi just pop up if it can't find the tray (because plasmashell is gone)? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 302559] Add overlay to Preview Mode to edit properties as Labels and Tags.
https://bugs.kde.org/show_bug.cgi?id=302559 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Add overlay to edit |Add overlay to Preview Mode |properties as Labels and|to edit properties as |Tags|Labels and Tags. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 138704] Show selected camera focus points (AF) as graphical overlay of preview canvas.
https://bugs.kde.org/show_bug.cgi?id=138704 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Show selected camera focus |Show selected camera focus |points (AF) as graphical|points (AF) as graphical |overlay of preview canvas |overlay of preview canvas. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 138704] Show selected camera focus points (AF) as graphical overlay of preview canvas
https://bugs.kde.org/show_bug.cgi?id=138704 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Show selected camera focus |Show selected camera focus |points (AF) as graphical|points (AF) as graphical |overlay of editor/preview |overlay of preview canvas |canvas | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 138704] Show selected camera focus points (AF) as graphical overlay of editor/preview canvas
https://bugs.kde.org/show_bug.cgi?id=138704 caulier.gil...@gmail.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||8.1.0 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 404794] Gwenview crashes when opening a very specific picture
https://bugs.kde.org/show_bug.cgi?id=404794 tildearrow changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #8 from tildearrow --- Apologies for the extremely long delay! Gwenview 23.04.1... no longer crashes when opening the picture. Image is still improperly displayed though... -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443398] Spectacle exits without taking screenshot, upon-relaunch is in 'select rectangle' mode.
https://bugs.kde.org/show_bug.cgi?id=443398 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 466805] kalendar fails to start
https://bugs.kde.org/show_bug.cgi?id=466805 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 464564] Steam deck connecting to display port does not identify monitor resolution correctly
https://bugs.kde.org/show_bug.cgi?id=464564 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.
[frameworks-baloo] [Bug 433783] baloo_file_extractor keeps crashing on Wayland
https://bugs.kde.org/show_bug.cgi?id=433783 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[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 470189] New: One of two screens randomly goes white and blank after wake up
https://bugs.kde.org/show_bug.cgi?id=470189 Bug ID: 470189 Summary: One of two screens randomly goes white and blank after wake up Classification: Plasma Product: kwin Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: cuihao@gmail.com Target Milestone: --- Created attachment 159217 --> https://bugs.kde.org/attachment.cgi?id=159217=edit The right screen turns white SUMMARY I connect two monitors to my PC. Recently, after I wake up the monitors from power saving, the right one of them (which is set to non-primary) sometimes goes white and blank. Only mouse cursor is visible. Please see the attachment for picture. When I move the cursor, it still interacts with windows on that screen. I can notice changes of cursor shapes, and even pull windows out from that screen. Turning off+on / Unplugging+Plugging the screen doesn't fix. "killall -9 kwin_wayland" fixes the screen at the cost of losing all windows. STEPS TO REPRODUCE 1. Let the screens sleep. 2. Wake them up. OBSERVED RESULT The right one of the two screens sometimes becomes white. EXPECTED RESULT Both screens are usable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.3-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Graphics: Device-1: NVIDIA TU117 [GeForce GTX 1650] driver: nvidia v: 530.41.03 Device-2: AMD Raphael driver: amdgpu v: kernel Device-3: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1 compositor: kwin_wayland driver: X: loaded: modesetting dri: radeonsi gpu: nvidia,amdgpu resolution: 1: 1920x1080 2: 1920x1080 API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon Graphics (gfx1036 LLVM 15.0.7 DRM 3.52 6.3.3-arch1-1) The two screens are both connected to the integrated AMD GPU. The left one is connected to the DisplayPort, the right one to the HDMI port. -- 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.
[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.
[digikam] [Bug 415845] configurable "open with" menu under Windows
https://bugs.kde.org/show_bug.cgi?id=415845 davidkace...@gmail.com changed: What|Removed |Added CC||davidkace...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470188] New: Add mouse/touchpad safety measures
https://bugs.kde.org/show_bug.cgi?id=470188 Bug ID: 470188 Summary: Add mouse/touchpad safety measures Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: tempqd...@mailinator.com CC: natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Currently if you disable the touchpad on a laptop and click apply, you are left with no pointer control and have to suddenly improvise and quickly learn to use the keyboard navigation to re-enable it, which is not very straightforward (I just tried it out with no prior experience and it was pretty challenging). Adding a "keep/revert" timer popup, like when changing display settings, could be a nice user safety feature. This could also help if you set your pointer speed way too high (or low) and consequently have difficulty hitting the buttons and moving the sliders to lower it back down. The touchpad settings have a spinbox to control the pointer speed in addition to the slider bar, but the mouse settings seem to lack one. The spinbox is helpful because, rather than slamming the bar to its edges with a speedy pointer, you can spend a few minutes positioning your mouse just right and then just click repeatedly until the speed is lowered back down (or type it in), then spend a few more minutes positioning your mouse over the Apply button. OS: openSUSE Tumbleweed, latest snapshot -- 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 470187] New: Clarify wording of mouse/touchpad acceleration settings
https://bugs.kde.org/show_bug.cgi?id=470187 Bug ID: 470187 Summary: Clarify wording of mouse/touchpad acceleration settings Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: tempqd...@mailinator.com CC: natalie_clar...@yahoo.de Target Milestone: --- SUMMARY The wording of "flat" and "adaptive" (and "acceleration profile" itself) seems unclear and perhaps overly technical. Plus, the word "adaptive" nowadays sounds more like it will learn from how you use the mouse and adapt itself over time, in a machine-learning sense. Or, it sounds like perhaps it will adapt based on the context your pointer is in, i.e. different applications will have different pointer behavior. What it really means is that there is simply acceleration. Calling it a "profile" and having the radio buttons with two options below the pointer speed bar also makes it seem like the choice will determine how the speed bar behaves. To me, "adaptive profile" seems like the bar will set how adaptive the acceleration is (which is not how it works, I don't think), especially in the touchpad settings where the bar is labeled "pointer acceleration" (should be labeled speed, I assume). I might suggest a simple toggle switch, "Acceleration: on/off". The hover (or perhaps an [i]) tooltip wording here (seemingly only in touchpad settings, by the way) would be trickier with only one on/off choice. In general the distinction between speed (velocity) and acceleration of the pointer is muddy when the user is constantly changing the pointer's speed themselves by moving their real-life mouse/finger at different speeds. So, maybe a better term than "acceleration" is possible here, like "boost" or "thrust" or something? OS: openSUSE Tumbleweed, latest snapshot -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 470184] Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11
https://bugs.kde.org/show_bug.cgi?id=470184 Felix Miata changed: What|Removed |Added CC||mrma...@earthlink.net -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 470186] New: Marble Bad satellite imagery
https://bugs.kde.org/show_bug.cgi?id=470186 Bug ID: 470186 Summary: Marble Bad satellite imagery Classification: Applications Product: marble Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: omg.qk...@aleeas.com Target Milestone: --- SUMMARY Marble's preloaded NASA satellite imagery is not high quality and cannot be used to look at any precise details. Sentinel images allow you to get closer, but are still not detailed and do not seem to work for most of the world. I went to Marble's website to review documentation on adding new maps, and found it to be next to nonexistent. I found this page https://marble.kde.org/maps-4.5.php and tried to download the MapQuest satellite images in hopes of better quality, but all download links result in 404 errors. There are no instructions on how to utilize satellite images from another source besides those you provide. How can usable satellite data be loaded? STEPS TO REPRODUCE 1. Run Marble 2. Open any pre-provided satellite view 3. Zoom in to try and look at buildings, roads, etc. OBSERVED RESULT Blurry images and restricted zoom EXPECTED RESULT Clear images and full zoom SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470096] Line.svg drawn inconsistently in Networks compared to Kickoff
https://bugs.kde.org/show_bug.cgi?id=470096 --- Comment #2 from doncb...@gmail.com --- Created attachment 159216 --> https://bugs.kde.org/attachment.cgi?id=159216=edit Line.svg in Kickoff vs Networks using Colloid Theme Sorry about that Nate, you should be able to reproduce it with the Colloid Light or Colloid Dark plasma themes, which are available for download on the store. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470185] New: Maximized windows not covering entire screen in some circumstances
https://bugs.kde.org/show_bug.cgi?id=470185 Bug ID: 470185 Summary: Maximized windows not covering entire screen in some circumstances Classification: Plasma Product: kwin Version: 5.27.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: 09_strays_fli...@icloud.com Target Milestone: --- Created attachment 159215 --> https://bugs.kde.org/attachment.cgi?id=159215=edit Screen shot demonstrating the issue. Look at the bottom row of pixels. It is a web page in Firefox, "behind" Dolphin. STEPS TO REPRODUCE 1. 4K display, 200% DPI scaling. 2. Bottom panel set to "auto hide". 3. Launch Dolphin application and maximize the window. OBSERVED RESULT Dolphin covers the entire screen... minus the bottom row of pixels. (See screen shot, attached.) EXPECTED RESULT Dolphin should cover the entire screen. Note that snapping a window to the left or right half of the screen (i.e. Super+left arrow) does result in it covering that bottom row of pixelsproperly. Also, this issue appears to be specific to Qt applications? Dolphin, Kate, Konsole, and VLC will leave a row of pixels at the bottom. Firefox, Thunderbird, Visual Studio Code and Google Earth do not. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 426540] plasma-nm icon vanishes sometimes after wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=426540 --- Comment #13 from Joshua J. Kugler --- I am running KDE Neon these days. Currently at Plasma 5.27. I have not seen the network icon disappear since I started using it. Just FYI. :) -- 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 403563] Memory leak in plasma desktop (plasmashell)
https://bugs.kde.org/show_bug.cgi?id=403563 --- Comment #18 from Jonathan Wakely --- Well that didn't help: top - 00:29:30 up 8:52, 6 users, load average: 3.24, 2.35, 2.20 Tasks: 412 total, 2 running, 410 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.9 us, 7.7 sy, 0.0 ni, 26.6 id, 63.3 wa, 0.3 hi, 0.3 si, 0.0 st MiB Mem : 64229.3 total,380.3 free, 63408.5 used,440.5 buff/cache MiB Swap: 69618.0 total, 22149.9 free, 47468.1 used.141.8 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 76 root 20 0 0 0 0 R 38.5 0.0 22:44.61 kswapd0 114347 root 20 0 25.4g 39608 25700 S 7.6 0.1 1:32.63 Xorg 114631 jwakely 20 0 1515740 20804 15968 S 2.7 0.0 0:04.83 kded5 3092 jwakely9 -11 473512 12616 8144 S 2.3 0.0 0:02.24 wireplumber 114634 jwakely 20 0 1323284 53276 44564 D 2.3 0.1 1:02.43 kwin_x11 115789 jwakely 20 0 3071832 86556 30860 S 2.0 0.1 3:54.37 Isolated Web Co 115756 jwakely 20 0 3063488 87384 30896 S 1.7 0.1 3:52.92 Isolated Web Co 118895 jwakely 20 0 100.4g 54.9g 33756 D 1.7 87.5 30:56.40 plasmashell It's about 4 hours since I restarted plasmashell (then left the system idle), and it's reached 100gb and the system is performing badly due to swapping. I'll try software rendering tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 470184] Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11
https://bugs.kde.org/show_bug.cgi?id=470184 --- Comment #2 from Steve --- There is more detail in a discussion on LQ here: https://www.linuxquestions.org/questions/showthread.php?p=6432534=1#post6432534 -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 470184] Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11
https://bugs.kde.org/show_bug.cgi?id=470184 --- Comment #1 from Steve --- There is a discussion with more detail on LQ here: https://www.linuxquestions.org/questions/showthread.php?p=6432534=1#post6432534 -- 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 #29 from Brian --- No, as far as I can tell, the situation is still unchanged -- sshd-core is still stuck at the obsolete version 0.14.0, carrying only "ssh-rsa" support: https://invent.kde.org/network/kdeconnect-android/-/blob/master/build.gradle. Any desktop apps that don't/can't enable support for this algorithm, will fail to establish SFTP/mount sessions with the Android app. As mentioned earlier, we need to get the sshd-core version bumped up to the most recent as possible (likely 2.9.2 or greater) and confirm that it resolves this standing issue of SSH negotiation, while retaining support for Android <= 7 if relevant and possible. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 469617] MPRIS receivers/controllers are ignoring playback rate to extrapolate current play position
https://bugs.kde.org/show_bug.cgi?id=469617 --- Comment #3 from Andy Holmes --- Fair enough, I don't do a lot of podcasting so I hadn't considered that. In that case I would suggest a slightly simplified way of communicating this, in the form of a triplet like `[rate, min, max]`. If the field is missing (older clients), it can be assumed `[1.0, 1.0, 1.0]`. The min/max would be required since if this is a useful feature, we will certainly want to be able to control it as well. If the value is, or falls back to `[1.0, 1.0, 1.0]` we can assume it's unsupported or not controllable and hide any UI in remote controls. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 470184] New: Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11
https://bugs.kde.org/show_bug.cgi?id=470184 Bug ID: 470184 Summary: Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11 Classification: Plasma Product: Active Window Control Version: unspecified Platform: Slackware OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: ste...@gmail.com CC: plasma-b...@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. Switching secondary monitor out temporarily from a port-replicator switch while keeping primary desktop active. 2. Switch back in secondary monitor/desktop 3. OBSERVED RESULT Wallpaper and Desktop menu are disabled (inactive). Right-click on secondary desktop does not invoke menu. The wallpaper that was set will disappear and turn to a black background. EXPECTED RESULT Wallpaper and Desktop menu should become active after a second or two of refresh time. This errant behavior does not happen on other Desktops such as XFCE and Plasma Full Wayland mode - as well as Windows OS. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Slackware64 (Current)/23.04 & 5.105 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9_20230412 ADDITIONAL INFORMATION As mentioned this is not an issue in Plasma5 full Wayland mode nor XFCE/X11. Secondary Desktop wallpaper and menu will resume/refresh after a second or two once monitor is reconnected through HDMI port replicator switch in those DE's. I have 4 computers that share the secondary monitor with a common mouse and keyboard. The brand of switch is xtremPro and is a model 4x1 USB HDMI KVM Switch 4K2K. If I use the xrandr binary in a script to temporarily switch the secondary monitor resolution I can get the secondary desktop to refresh. Below is the script: #!/bin/bash xrandr --output DP-2-2 --mode 1600x900 xrandr --output DP-2-2 --mode 1920x1080 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468950] Doesn't pair with Windows at all, doesn't even see it
https://bugs.kde.org/show_bug.cgi?id=468950 --- Comment #3 from mailinglist...@gmail.com --- iOS 15.0 iPhone 13 mini -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468950] Doesn't pair with Windows at all, doesn't even see it
https://bugs.kde.org/show_bug.cgi?id=468950 --- Comment #2 from mailinglist...@gmail.com --- Created attachment 159214 --> https://bugs.kde.org/attachment.cgi?id=159214=edit video behaviour of iOS in slow motion video behaviour of iOS in slow motion PLEASE FIX the app is completely useless!!! 郎 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470131] From Spectacle, Libreoffice, Firefox, ... copied image has replace-mimetype, broken
https://bugs.kde.org/show_bug.cgi?id=470131 Henning changed: What|Removed |Added Summary|Spectacle and other sources |From Spectacle, |copied image has wrong |Libreoffice, Firefox, ... |Mimetype|copied image has ||replace-mimetype, broken -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470131] Spectacle and other sources copied image has wrong Mimetype
https://bugs.kde.org/show_bug.cgi?id=470131 --- Comment #3 from Henning --- https://cloud.uol.de/s/ojt6eTLL4DdxeT2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470183] Feature request: Do not collapse annotation list when deleting an annotation
https://bugs.kde.org/show_bug.cgi?id=470183 Bug Janitor Service changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470182] Feature Request: Double click on pop-up note in annotations panel to open pop up note
https://bugs.kde.org/show_bug.cgi?id=470182 Bug Janitor Service changed: What|Removed |Added Severity|normal |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|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 470061] KWin crash on unhide autohide panel
https://bugs.kde.org/show_bug.cgi?id=470061 Holger changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #2 from Holger --- Yes, Dim Inactive effect is in effect ;) though I definitely didn't use audacity for some weeks. Anyway, here is another backtrace registered in coredumpctl ... it also happened on unhiding the panel (but this time for the highlight window effect - similar symptom, but totally different stacktrace): (gdb) bt #0 __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at ./nptl/pthread_sigmask.c:43 #1 0x7f278e23c6ad in __GI___sigprocmask (how=, set=, oset=) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x7f27913f1fcf in KCrash::setCrashHandler (handler=handler@entry=0x0) at ./src/kcrash.cpp:414 #3 0x7f27913f44fb in KCrash::defaultCrashHandler (sig=11) at ./src/kcrash.cpp:625 #4 #5 0x563153dc9e99 in KWin::isHighlightWindow (window=0x563155ea2290) at /usr/src/kwin-4:5.27.4-0ubuntu1/src/effects/highlightwindow/highlightwindow.cpp:57 #6 KWin::HighlightWindowEffect::finishHighlighting (this=this@entry=0x563156acc200) at /usr/src/kwin-4:5.27.4-0ubuntu1/src/effects/highlightwindow/highlightwindow.cpp:178 #7 0x563153dcb168 in KWin::HighlightWindowEffect::highlightWindows (windows=..., this=0x563156acc200) at /usr/src/kwin-4:5.27.4-0ubuntu1/src/effects/highlightwindow/highlightwindow.cpp:198 #8 KWin::HighlightWindowEffect::highlightWindows (windows=..., this=0x563156acc200) at /usr/src/kwin-4:5.27.4-0ubuntu1/src/effects/highlightwindow/highlightwindow.cpp:71 #9 KWin::HighlightWindowEffect::qt_static_metacall (_o=0x563156acc200, _c=, _id=, _a=) at /usr/src/kwin-4:5.27.4-0ubuntu1/obj-x86_64-linux-gnu/src/effects/highlightwindow/kwin4_effect_highlightwindow_autogen/EWIEGA46WW/moc_highlightwindow.cpp:105 #10 0x563153dcb243 in KWin::HighlightWindowEffect::qt_metacall (this=0x563156acc200, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x7ffcd0a0c2b0) at /usr/src/kwin-4:5.27.4-0ubuntu1/obj-x86_64-linux-gnu/src/effects/highlightwindow/kwin4_effect_highlightwindow_autogen/EWIEGA46WW/moc_highlightwindow.cpp:182 #11 0x7f278e8fa22b in QDBusConnectionPrivate::deliverCall ( this=this@entry=0x7f27680013f0, object=object@entry=0x563156acc200, msg=..., metaTypes=..., slotIdx=) at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:189 #12 0x7f278e8fdf86 in QDBusConnectionPrivate::activateCall ( this=this@entry=0x7f27680013f0, object=0x563156acc200, flags=240, msg=...) at qdbusintegrator.cpp:911 #13 0x7f278e8fe55e in QDBusConnectionPrivate::activateCall (msg=..., flags=, object=, this=0x7f27680013f0) at qdbusintegrator.cpp:853 #14 QDBusConnectionPrivate::activateObject (this=0x7f27680013f0, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1521 #15 0x7f278e9009fc in QDBusActivateObjectEvent::placeMetaCall (this=0x56315641cdb0) at qdbusintegrator.cpp:1617 #16 0x7f278f6e7de0 in QObject::event (this=0x563156acc200, e=0x56315641cdb0) at kernel/qobject.cpp:1347 #17 0x7f278eb6bf92 in QApplicationPrivate::notify_helper (this=, receiver=0x563156acc200, e=0x56315641cdb0) at kernel/qapplication.cpp:3640 #18 0x7f278f6bae38 in QCoreApplication::notifyInternal2 (receiver=0x563156acc200, event=0x56315641cdb0) at kernel/qcoreapplication.cpp:1064 #19 0x7f278f6bb012 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 --Type for more, q to quit, c to continue without paging--c #20 0x7f278f6bdea1 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5631556e6580) at kernel/qcoreapplication.cpp:1821 #21 0x7f278f6be32c in QCoreApplication::sendPostedEvents (receiver=, event_type=) at kernel/qcoreapplication.cpp:1680 #22 0x7f278f7157b7 in postEventSourceDispatch (s=0x5631557d2740) at kernel/qeventdispatcher_glib.cpp:277 #23 0x7f278ce6149d in g_main_dispatch (context=0x7f2784000ee0) at ../../../glib/gmain.c:3460 #24 g_main_context_dispatch (context=0x7f2784000ee0) at ../../../glib/gmain.c:4200 #25 0x7f278cebc178 in g_main_context_iterate.constprop.0 (context=0x7f2784000ee0, block=, dispatch=1, self=) at ../../../glib/gmain.c:4276 #26 0x7f278ce601b0 in g_main_context_iteration (context=0x7f2784000ee0, may_block=1) at ../../../glib/gmain.c:4343 #27 0x7f278f714e7a in QEventDispatcherGlib::processEvents (this=0x5631557e43c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f278f6b97cb in QEventLoop::exec (this=this@entry=0x7ffcd0a0c870, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7f278f6c1c1a in QCoreApplication::exec () at
[plasmashell] [Bug 470131] Spectacle and other sources copied image has wrong Mimetype
https://bugs.kde.org/show_bug.cgi?id=470131 Henning changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Henning --- What I am doing: 1. Get an image somewhere. It actually doesnt matter. Examples: taking a spectacle screenshot (set to autocopy to clipboard), copy an image from libreoffice flatpak, copy an image from firefox. 2. Try to paste the image to dolphin. The image has this named mimetype, which breaks it. Even naming it ".png" doesnt help, its broken completely. I can make a video but I dont think this is nessecary -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469908] Kwin crashes in std::default_delete on applying rules
https://bugs.kde.org/show_bug.cgi?id=469908 --- Comment #4 from Holger --- Hihi ... you're right - my harddrive is not that big, it has to be 720 MiB not GB ;-) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 --- Comment #8 from Andrei Rybak --- Jose, thank you for the insight. I will try disabling the MAC randomization on the phone and see if it helps. What is very surprising, however, if it is indeed the root cause, is that KDE Connect itself doesn't seem to be confused by the MAC address randomization. Regardless of the MAC address, KDE Connect seems to be able to keep track of the "trusted" status of the phone and of all the settings of plugins (e.g. the commands in "Run commands"). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470183] New: Feature request: Do not collapse annotation list when deleting an annotation
https://bugs.kde.org/show_bug.cgi?id=470183 Bug ID: 470183 Summary: Feature request: Do not collapse annotation list when deleting an annotation Classification: Applications Product: okular Version: unspecified Platform: Archlinux OS: Other Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: nat...@upchur.ch Target Milestone: --- Currently, when deleting an annotation via right click > delete in the annotations sidebar, the list of annotations collapses. If you have a large number of annotations in a document, particularly from several authors, this makes it tedious to delete annotations repeatedly, as you might if you were going through an annotated proof, adjusting the source document note by note, and deleting each as you go along to track what you've completed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470182] New: Feature Request: Double click on pop-up note in annotations panel to open pop up note
https://bugs.kde.org/show_bug.cgi?id=470182 Bug ID: 470182 Summary: Feature Request: Double click on pop-up note in annotations panel to open pop up note Classification: Applications Product: okular Version: unspecified Platform: Archlinux OS: Other Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: nat...@upchur.ch Target Milestone: --- Basically, I just think it would be nice if pop-up notes opened when you double-clicked them in the annotations sidebar. -- 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 453385] KSplash segfaults in SplashWindow::setStage() after sleep or lock
https://bugs.kde.org/show_bug.cgi?id=453385 --- Comment #6 from aron...@gmail.com --- (In reply to aronkvh from comment #5) > I haven't seen *ksplash crash lately, so might be resolved? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453385] KSplash segfaults in SplashWindow::setStage() after sleep or lock
https://bugs.kde.org/show_bug.cgi?id=453385 --- Comment #5 from aron...@gmail.com --- I haven't seen kcrash crash lately, so might be resolved? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470181] Keyboard shortcuts to move windows don't behave as expected in multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=470181 p...@paulschweigert.com changed: What|Removed |Added CC||p...@paulschweigert.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470181] New: Keyboard shortcuts to move windows don't behave as expected in multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=470181 Bug ID: 470181 Summary: Keyboard shortcuts to move windows don't behave as expected in multi-monitor setup Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: generic-multiscreen Assignee: plasma-b...@kde.org Reporter: p...@paulschweigert.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY After upgrading to v5.27, using keyboard shortcuts to move windows between monitors is broken in some instances STEPS TO REPRODUCE I have three monitors arranged horizontally: A B C The built-in screen of my laptop is set as a replica of monitor B, while A and C rotated 90d clockwise (in case that matters). All monitors have the same resolution and refresh rate. Meta+Left / Meta+Right are set to Quick Tile Window to the Left / Right. After the upgrade to KDE 5.27, moving a window from Monitor B to Monitor C using Meta+Right no longer works (the window alternates between the left and right side of Monitor B). I _can_ drag the window from B to C using the mouse. Prior to the 5.27 upgrade, Meta+Right was able to move a window from Monitor B to Monitor C. It appears the issue may be related to the fact that the built-in screen is set as a replica of Monitor B; if I make the built-in a replica of None, then I am able to move a window from B to C as before. OBSERVED RESULT (covered in previous section) EXPECTED RESULT The Meta+Right keyboard shortcut would move a window across all monitors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 470148] Bond connection should offer MTU setting like wired Ethernet
https://bugs.kde.org/show_bug.cgi?id=470148 --- Comment #1 from Jean-Marc Liotier --- For proof of backend functionality I gave an 'ip' command, but should have mentioned a 'nmcli' command instead - so here it is: ''nmcli connection modify bond0 802-3-ethernet.mtu 9000' -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470050] Dolphin does not restore folders when opened through session restore
https://bugs.kde.org/show_bug.cgi?id=470050 --- Comment #7 from mlchatnoir...@gmail.com --- (In reply to mlchatnoir666 from comment #6) > I am currently experiencing the same bug. > > If it can help, I see the default home folder when I open dolphin manually > (clicking on the app) and when my computer opens dolphin on start, BUT I see > the saved state when another app opens dolphin. Not sure why the behavior is > different depending on the case as seen in https://bugs.kde.org/show_bug.cgi?id=469656 , the bug doesn't happen if you open dolphin with the shortcut (default Meta+E in Plasma). I'm just reposting for others since it's a valid workaround -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468035] Crash when try to save a PDF document
https://bugs.kde.org/show_bug.cgi?id=468035 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #2 from Albert Astals Cid --- I don't think any of the devs has a mac machine available so this is not going to be fixed "very fast". -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470172] The application is closing itself when trying to change general and annotation configurations
https://bugs.kde.org/show_bug.cgi?id=470172 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Works fine here. Just opening the configure okular crashes? Or you do something else? Where did you install okular from? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470174] 40 Characters Annotation consuming 20MB
https://bugs.kde.org/show_bug.cgi?id=470174 Albert Astals Cid changed: What|Removed |Added Severity|grave |normal CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470090] [Wayland][Nvidia?] Ksplashqml, plasma and systemsettings crash on login
https://bugs.kde.org/show_bug.cgi?id=470090 --- Comment #13 from Syfer Polski --- apt info plasma-workspace Package: plasma-workspace Version: 4:5.24.7-0ubuntu0.1 Priority: optional Section: universe/kde Origin: Ubuntu Maintainer: Kubuntu Developers Original-Maintainer: Debian Qt/KDE Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug I'll try to get the backtrace tomorrow -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470050] Dolphin does not restore folders when opened through session restore
https://bugs.kde.org/show_bug.cgi?id=470050 mlchatnoir...@gmail.com changed: What|Removed |Added CC||mlchatnoir...@gmail.com --- Comment #6 from mlchatnoir...@gmail.com --- I am currently experiencing the same bug. If it can help, I see the default home folder when I open dolphin manually (clicking on the app) and when my computer opens dolphin on start, BUT I see the saved state when another app opens dolphin. Not sure why the behavior is different depending on the case -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357170] plasmashell loaded longer than ksplash
https://bugs.kde.org/show_bug.cgi?id=357170 Nate Graham changed: What|Removed |Added Product|ksplash |plasmashell Component|general |Splash Screens Target Milestone|--- |1.0 Version|unspecified |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446515] KSplash keeps loading for 50 seconds in background
https://bugs.kde.org/show_bug.cgi?id=446515 Nate Graham changed: What|Removed |Added Version|5.23.4 |5.27.5 Component|general |Splash Screens Target Milestone|--- |1.0 Product|ksplash |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 259029] SVG support for background images
https://bugs.kde.org/show_bug.cgi?id=259029 Nate Graham changed: What|Removed |Added Version|unspecified |5.27.5 Component|general |Splash Screens Target Milestone|--- |1.0 Product|ksplash |plasmashell -- 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 368942] Splash screen spinner should fade out instead of pause when fading into desktop
https://bugs.kde.org/show_bug.cgi?id=368942 Nate Graham changed: What|Removed |Added Target Milestone|--- |1.0 Component|general |Splash Screens Product|ksplash |plasmashell Version|5.27.4 |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355250] Configurable splash screen wallpaper apart from changing the entire splash screen theme
https://bugs.kde.org/show_bug.cgi?id=355250 Nate Graham changed: What|Removed |Added Product|ksplash |plasmashell Component|general |Splash Screens Target Milestone|--- |1.0 Version|5.4.3 |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470036] Cursor is shown over Splash screen when using Wayland session
https://bugs.kde.org/show_bug.cgi?id=470036 Nate Graham changed: What|Removed |Added Version|5.27.4 |5.27.5 Product|ksplash |plasmashell Component|general |Splash Screens Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453385] KSplash segfaults in SplashWindow::setStage() after sleep or lock
https://bugs.kde.org/show_bug.cgi?id=453385 Nate Graham changed: What|Removed |Added Version|5.25.0 |5.27.5 Target Milestone|--- |1.0 Component|general |Splash Screens Product|ksplash |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 255126] KSplash should be able to share SDDM's background image
https://bugs.kde.org/show_bug.cgi?id=255126 Nate Graham changed: What|Removed |Added Target Milestone|--- |1.0 Component|general |Splash Screens Product|ksplash |plasmashell Version|unspecified |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449472] Splash animation isn't seamless on X11
https://bugs.kde.org/show_bug.cgi?id=449472 Nate Graham changed: What|Removed |Added Version|5.23.5 |5.27.5 Target Milestone|--- |1.0 Component|general |Splash Screens Product|ksplash |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437639] Stop showing KSplash only after all desktop components are loaded
https://bugs.kde.org/show_bug.cgi?id=437639 Nate Graham changed: What|Removed |Added Version|unspecified |5.27.5 Product|ksplash |plasmashell Component|general |Splash Screens Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463195] Plasma gets stuck at splash screen if I switch TTY at startup and then back
https://bugs.kde.org/show_bug.cgi?id=463195 Nate Graham changed: What|Removed |Added Version|5.26.4 |5.27.5 Target Milestone|--- |1.0 Component|general |Splash Screens Product|ksplash |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)
https://bugs.kde.org/show_bug.cgi?id=403563 Jonathan Wakely changed: What|Removed |Added CC||zi...@kayari.org --- Comment #17 from Jonathan Wakely --- Created attachment 159213 --> https://bugs.kde.org/attachment.cgi?id=159213=edit Settings an KWin support info For the past few weeks plasmashell (version plasma-workspace-x11-5.27.4.1-1.fc37.x86_64 from fedora RPMs) has been growing to tens of gigabytes while idle and getting killed by the oomkiller. I've attached my ~/config/plasma*rc and the kwin support info as requested above. I've tried setting the Render loop to basic and will see if that changes anything. -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 470180] New: Screens go black after manual suspend
https://bugs.kde.org/show_bug.cgi?id=470180 Bug ID: 470180 Summary: Screens go black after manual suspend Classification: Plasma Product: plasma-wayland-protocols Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gome...@hotmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 159212 --> https://bugs.kde.org/attachment.cgi?id=159212=edit Screenshot - screen configuration SUMMARY When returning from "suspend", the monitors do not turn on or return with low resolution (640x480). Wayland does not allow changing resolution (attachment). I have two HP V206hz monitors that have a maximum resolution of 1600x900x60hz and are connected to a Radeon RX 6600 via cable (displayport > DVI). 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. Manually suspend the computer. 2. Wait for the suspension process to finish (front panel LED flashes). 3. Press any key to wake up the computer. OBSERVED RESULT Screens go black after manual suspend. One of the screens returns with 640x480 resolution after returning from automatic suspend (when automatic splint shutdown is not active). If the screen turns off automatically (before automatic suspend) the monitor video returns with adequate resolution (1600x900) EXPECTED RESULT Screens turn on after computer resumes from sleep. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OS: Kubuntu 22.04.2 LTS x86_64 Kernel: 5.19.0-42-generic KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION To view any content, you must force restart with the power button or remove and reinsert the monitor cable. I installed the amd package for the gpu but the problem remained. https://www.amd.com/en/support/graphics/amd-radeon-6000-series/amd-radeon-6600-series/amd-radeon-rx-6600 -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369435] Splash screen does not disappear on primary monitor
https://bugs.kde.org/show_bug.cgi?id=369435 --- Comment #3 from Nate Graham --- Yay, thanks for following up so ridiculously quickly! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455240] Activity-specific panels
https://bugs.kde.org/show_bug.cgi?id=455240 Clay Weber changed: What|Removed |Added CC||c...@claydoh.com -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369435] Splash screen does not disappear on primary monitor
https://bugs.kde.org/show_bug.cgi?id=369435 Rolf Eike Beer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Rolf Eike Beer --- I have not seen this for a long while, so hopefully done. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 436140] Splash screen not correctly aligned with custom multiple monitor setup in X11
https://bugs.kde.org/show_bug.cgi?id=436140 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Keywords||multiscreen Status|REPORTED|NEEDSINFO --- Comment #2 from Nate Graham --- Thank you for the bug report. Unfortunately we were not able to get to it yet, and the way multi-monitor support is handled has changed a lot over the years. Can we ask you to please check if this is still an issue with Plasma 5.27? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369435] Splash screen does not disappear on primary monitor
https://bugs.kde.org/show_bug.cgi?id=369435 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO Keywords||multiscreen --- Comment #1 from Nate Graham --- Thank you for the bug report. Unfortunately we were not able to get to it yet, and the way multi-monitor support is handled has changed a lot over the years. Can we ask you to please check if this is still an issue with Plasma 5.27? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 422904] [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=422904 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #9 from Nate Graham --- Awesome, thanks. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369592] KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML
https://bugs.kde.org/show_bug.cgi?id=369592 Nate Graham changed: What|Removed |Added Resolution|--- |MOVED Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #2 from Nate Graham --- The fact that you need to create a whole custom splash screen to persist your edits is currently intentional, and this is the way it works for any themable UI elements. That said, I agree that it's not ideal and seems fairly heavyweight for the simple case of just wanting to change the background; see Bug 355250. I've proposed some changes to the infrastructure here that would support this; see https://invent.kde.org/plasma/plasma-desktop/-/issues/93. Let's follow up there. -- You are receiving this mail because: You are watching all bug changes.