[kwin] [Bug 465432] Middle click with three-fingers touch on touchpad is lost randomly after using 4-fingers swipe gesture
https://bugs.kde.org/show_bug.cgi?id=465432 --- Comment #4 from Alexandre Hen --- Hello ! Thank you vive.linux. It happened today on Opensuse Tumbleweed 240407, on my P14s AMD Gen1 : I lost the three fingers to middle click after using the four fingers swipe gesture. Using a 4 fingers swipe again resolved the issue. Thank you ! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465432] Middle click with three-fingers touch on touchpad is lost randomly after using 4-fingers swipe gesture
https://bugs.kde.org/show_bug.cgi?id=465432 Alexandre Hen changed: What|Removed |Added Version|5.26.90 |6.0.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465432] Middle click with three-fingers touch on touchpad is lost randomly after using 4-fingers swipe gesture
https://bugs.kde.org/show_bug.cgi?id=465432 Alexandre Hen changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482937] New: Dolphin crashes when ejecting unmounted cdrom via physical button
https://bugs.kde.org/show_bug.cgi?id=482937 Bug ID: 482937 Summary: Dolphin crashes when ejecting unmounted cdrom via physical button Classification: Applications Product: dolphin Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: a...@lab.underwares.org CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (24.02.0) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.5.0-25-generic x86_64 Windowing System: Wayland Distribution: KDE neon 6.0 DrKonqi: 6.0.0 [KCrashBackend] -- Information about the crash: I was dumping old CDs off of a usb dvd drive to images, for archival purposes. After finishing the raw dump via command line tools (which just reads the block device), and then copying the resultant image files to storage via Dolphin over cifs kio, I briefly checked that the media had not been mounted (it hadn't) and pressed the physical eject button on the drive to get my disc back. Dolphin immediately crashed with the following stack trace. I can reproduce this somewhat reliably, as it does not systematically occurs, but reoccurs the majority of the time. I in fact did it just now by reinserting the physical media, starting dolphin, waiting for everything to settle (not mounting anything) and just hitting the eject button. If it helps, since Dolphin helpfully reads the disk labels and presents them in the side bar for easy mounting, the media was an Apple HFS disk. I am unsure of how much this helps, but here is the disk layout and properties: --- /dev/sr0 Block device, size 647.7 MiB (679211008 bytes) CD-ROM, 1 track, CDDB disk ID 02114501 Track 1: Data track, 647.7 MiB (679211008 bytes) Apple partition map, 3 entries Partition 1: 31.50 KiB (32256 bytes, 63 sectors from 1) Type "Apple_partition_map" Partition 2: 647.4 MiB (678871040 bytes, 1325920 sectors from 64) Type "Apple_HFS" HFS Plus file system Volume size 647.4 MiB (678871040 bytes, 165740 blocks of 4 KiB) Volume name "Microsoft Office 2004" Partition 3: 8 KiB (8192 bytes, 16 sectors from 1325984) Type "Apple_Free" Blank disk/medium The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=137239995239104) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=137239995239104) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=137239995239104, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7cd1b1e42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7cd1b1e287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7cd1b2adb017 in qAbort () at ./src/corelib/global/qglobal.cpp:161 #10 0x7cd1b2ad64e5 in qt_message_fatal (message=..., context=...) at ./src/corelib/global/qlogging.cpp:2003 #11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=, ap=ap@entry=0x7fff43e57e40) at ./src/corelib/global/qlogging.cpp:378 #12 0x7cd1b2adba43 in QMessageLogger::fatal (this=, msg=) at ./src/corelib/global/qlogging.cpp:901 #13 0x7cd1b2aa9c94 in qt_assert (assertion=assertion@entry=0x7cd1b49fcbd8 "dev->backendObject() != nullptr", file=file@entry=0x7cd1b49fcba8 "./src/solid/devices/frontend/devicemanager.cpp", line=line@entry=234) at ./src/corelib/global/qassert.cpp:68 #14 0x7cd1b49746dd in Solid::DeviceManagerPrivate::_k_deviceRemoved (udi=..., this=) at ./src/solid/devices/frontend/devicemanager.cpp:234 #15 Solid::DeviceManagerPrivate::qt_static_metacall (_o=0x622d3f223c90, _c=, _id=, _a=) at ./obj-x86_64-linux-gnu/src/solid/KF6Solid_autogen/include/moc_devicemanager_p.cpp:139 #16 0x7cd1b2a2baab in doActivate (sender=0x622d3f20ac20, signal_index=4, argv=0x7fff43e580f0) at ./src/corelib/kernel/qobject.cpp:4051 #17 0x7cd1b498eb99 in Solid::Ifaces::DeviceManager::deviceRemoved (this=, _t1=...) at ./obj-x86_64-linux-gnu/src/solid/KF6Solid_autogen/include/moc_devicemanager.cpp:189 #18 0x7cd1b49b9855 in Solid::Backends::UDisks2::Manager::slotInterfacesRemoved (interfaces=..., object_path=..., this=) at ./src/solid/devices/backends/udisks2/udisksmanager.cpp:249 #19 Solid::Backends::UDisks2::Manager::qt_static_metacall (_o=, _c=, _id=, _a=) at ./obj-x86_64-linux-gnu/src/solid/KF6Solid_autogen/include/moc_udisksmanager.cpp:161 #20 0x7cd1b2a2baab in doActivate (sender=0x622d3f20ac38, signal_index=4, argv=0x7fff43e583a0) at ./src/corelib/kernel/qobject.cpp:4051 #21 0x7cd1b49d1371 in OrgFreedesktopDBusObjectManagerInterface::InterfacesRemoved (_t2=..., _t1=..., this=) at
[kwin] [Bug 482388] Keyboard shortcuts using numpad not working
https://bugs.kde.org/show_bug.cgi?id=482388 --- Comment #6 from Alexandre BARBIER --- (In reply to Nicolas Fella from comment #5) > Ok, then it's expected that the numpad key does not trigger it. > > What should and does happen for me (using Fedora 40) is that it shows > "Meta+Num++" and the numpad key triggers the shortcut Hello, I wanted to try it again, just to be sure, I ran Fedora 40 from a live USB (the exact same as yesterday), didn't update anything since then, but when I tried it today it worked just fine (exactly how you described it, the UI said "Meta+Num++" and the shortcut worked), I have no idea what changed between yesterday and today, I'm sorry for this bug report that isn't really useful, and I thank you for your answers. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 482416] New: Incorrect french translation of "Highlighting" in Konsole
https://bugs.kde.org/show_bug.cgi?id=482416 Bug ID: 482416 Summary: Incorrect french translation of "Highlighting" in Konsole Classification: Translations Product: i18n Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: fr Assignee: kde-francoph...@kde.org Reporter: a...@lab.underwares.org Target Milestone: --- SUMMARY In Konsole under profile settings -> scrolling, the options to display the light blue bar to identify newly drawn lines has an incorrect and confusing translation. It reads "Coloration syntaxique : Réaliser une coloration syntaxique dans les lignes allant être affichées". This unfortunately refers to Syntax Highlighting, which is absolutely not what this setting is about. Consistent with the rest of the translation for Konsole where "highlight" is used, I would suggest instead: "Mise en évidence : Mettre en évidence les nouvelles lignes de l'affichage" This conveys "highlight" as in "to bring attention to" instead of syntax highlighting. STEPS TO REPRODUCE 1. Open Konsole 2. Modifier le profil actuel -> Barre de défilement 3. See weird last option at the bottom OBSERVED RESULT User is confused, unsure of what this does EXPECTED RESULT User understands that this controls the highlighting widget on the left hand side of the window. SOFTWARE/OS VERSIONS KDE Neon 6.0 KDE Frameworks: 6.0 QT: 6.6.2 Konsole package: 4:24.02.0-0xneon+22.04+jammy+release+build35 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482388] Keyboard shortcuts using numpad not working
https://bugs.kde.org/show_bug.cgi?id=482388 --- Comment #4 from Alexandre BARBIER --- (In reply to Nicolas Fella from comment #3) > When you enter the shortcut, what does the UI say? "Meta++" or "Meta+Num++"? It shows Meta++ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482388] Keyboard shortcuts using numpad not working
https://bugs.kde.org/show_bug.cgi?id=482388 --- Comment #2 from Alexandre BARBIER --- (In reply to Nicolas Fella from comment #1) > I looks like you are reporting the inverse of > https://bugs.kde.org/show_bug.cgi?id=446389 > > We fixed shortcuts to differentiate between numpad and non-numpad keys, but > you seem to want them to behave the same? Nl(In reply to Nicolas Fella from comment #1) > I looks like you are reporting the inverse of > https://bugs.kde.org/show_bug.cgi?id=446389 > > We fixed shortcuts to differentiate between numpad and non-numpad keys, but > you seem to want them to behave the same? No not really, my issue is that, even if when I want to add a new shortcut I press the key on the numpad (in this example I press Meta + Numpad+ to add the shortcut then apply the changes), the shortcut doesn't work afterward with the numpad key -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482388] New: Keyboard shortcuts using numpad not working
https://bugs.kde.org/show_bug.cgi?id=482388 Bug ID: 482388 Summary: Keyboard shortcuts using numpad not working Classification: Plasma Product: kwin Version: 6.0.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: alexbarbier0...@gmail.com Target Milestone: --- SUMMARY When I try using the shortcut for zoom (Meta++) it doesn't work with the '+' key of the numpad but works with the '+' key that isn't on the numpad. I tried adding a new shorcut with other keys from the numpad and the same issue appears. STEPS TO REPRODUCE 1. Open settings 2. Go to Keyboard -> Shortcut 3. Search for Zoom 4. In Kwin -> Zoom In 3. Add a shorcut using the numpad (for example Meta++) (This issue is not exclusive to this shortcut) 4. Try using the shortcut OBSERVED RESULT Nothing happens EXPECTED RESULT The shortcut should be activated SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.8.0/Plasma 6.0.0 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION The shortcut worked just fine on Plasma 5.27 -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 481699] New: Plan crashes when trying to open a 2013 plan file in 2024
https://bugs.kde.org/show_bug.cgi?id=481699 Bug ID: 481699 Summary: Plan crashes when trying to open a 2013 plan file in 2024 Classification: Applications Product: calligraplan Version: 3.3.0 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dag.ander...@kdemail.net Reporter: alexandre.bonn...@linuxfr.eu Target Milestone: --- Application: calligraplan (3.3.0) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.6.15-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Install a brand new calligraplan 1:3.3.0-2 on Debian Trixie (testing). Try to open a plan created with calligraplan in 2013. The app crashes. I can post the plan file privately if needed. The crash can be reproduced every time. -- Backtrace: Application: Plan (calligraplan), signal: Aborted PID: 1535014 (calligraplan) UID: 1000 (acid) GID: 1000 (acid) Signal: 6 (ABRT) Timestamp: Thu 2024-02-22 11:16:56 -10 (19s ago) Command Line: /usr/bin/calligraplan Executable: /usr/bin/calligraplan Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fcalligraplan-fd39862436104c94a70d52b7fa363493.scope Unit: user@1000.service User Unit: app-\x2fusr\x2fbin\x2fcalligraplan-fd39862436104c94a70d52b7fa363493.scope Slice: user-1000.slice Owner UID: 1000 (acid) Boot ID: b404ca645c734eb78f2a5abe64506c34 Machine ID: 80bf05fa6a4f4e26a066dd73d081fa2b Hostname: AciD Storage: /var/lib/systemd/coredump/core.calligraplan.1000.b404ca645c734eb78f2a5abe64506c34.1535014.170863661600.zst (present) Size on Disk: 4.9M Message: Process 1535014 (calligraplan) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-255.3-2.amd64 Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2.amd64 Module libudev.so.1 from deb systemd-255.3-2.amd64 Stack trace of thread 1535014: #0 0x7fb5d55c416c n/a (libc.so.6 + 0x8a16c) #1 0x7fb5d5576472 raise (libc.so.6 + 0x3c472) #2 0x7fb5d2c0d84d _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x584d) #3 0x7fb5d5576510 n/a (libc.so.6 + 0x3c510) #4 0x7fb5d55c416c n/a (libc.so.6 + 0x8a16c) #5 0x7fb5d5576472 raise (libc.so.6 + 0x3c472) #6 0x7fb5d55604b2 abort (libc.so.6 + 0x264b2) #7 0x7fb5d55603d5 n/a (libc.so.6 + 0x263d5) #8 0x7fb5d556f3a2 __assert_fail (libc.so.6 + 0x353a2) #9 0x7fb5b40624dc _ZN6KGantt12DateTimeGrid11setDayWidthEd (libKGantt.so.2 + 0x5a4dc) #10 0x7fb5b4386959 _ZN6KPlato13GanttViewBase11loadContextERK12KoXmlElement (libplanui.so.18 + 0x186959) #11 0x7fb5b439250a n/a (libplanui.so.18 + 0x19250a) #12 0x7fb5c59be9e3 _ZN6KPlato4View11createViewsEv (libplanprivate.so.18 + 0xa69e3) #13 0x7fb5c59beb35 _ZN6KPlato4View13initiateViewsEv (libplanprivate.so.18 + 0xa6b35) #14 0x7fb5d48f9940 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2f9940) #15 0x7fb5d4d62f32 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f32) #16 0x7fb5d54d3897 _ZN13KoApplication6notifyEP7QObjectP6QEvent (libplanmain.so.18 + 0x3b897) #17 0x7fb5d48cc748 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2cc748) #18 0x7fb5d48cfe51 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2cfe51) #19 0x7fb5d4928697 n/a (libQt5Core.so.5 + 0x328697) #20 0x7fb5d29111f4 n/a (libglib-2.0.so.0 + 0x571f4) #21 0x7fb5d2914317 n/a (libglib-2.0.so.0 + 0x5a317) #22 0x7fb5d2914930 g_main_context_iteration (libglib-2.0.so.0 + 0x5a930) #23 0x7fb5d4927d4a _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x327d4a) #24 0x7fb5d48cb0fb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2cb0fb) #25 0x7fb5d48d38a4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2d38a4) #26 0x7fb5d571f19e kdemain (libkdeinit5_calligraplan.so + 0x319e) #27 0x7fb5d55616ca n/a (libc.so.6 + 0x276ca) #28 0x7fb5d5561785 __libc_start_main (libc.so.6 + 0x27785)
[Bluedevil] [Bug 420238] Bluetooth toggle overrides airplane mode
https://bugs.kde.org/show_bug.cgi?id=420238 --- Comment #2 from Alexandre CATTEAU --- Coming back to this issue today, I believe my point was on consistency: You should not be able to disable Airplane mode by toggling something it forbids (like Wi-Fi). If we consider that Bluetooth should not be forbidden by Airplane mode, fine by me. But then I would support de-correlating those entirely and not reproduce the Android behavior mentioned above. So I suggest removing Bluetooth disablement when enabling Airplane mode. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 --- Comment #12 from Alexandre Bonneau --- It's always weird when a bug is closed as duplicate of a more recent one, specially when there was more comments on the former, just saying. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476573] Preview - Picture is shifted upward
https://bugs.kde.org/show_bug.cgi?id=476573 --- Comment #8 from Alexandre Belz --- Thank you Maik, that was the issue indeed. Not easy to detect it myself ! (and I don't remind having undocked by purpose). Many thanks again. BR. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476573] Preview - Picture is shifted upward
https://bugs.kde.org/show_bug.cgi?id=476573 --- Comment #7 from Alexandre Belz --- Thank you Maik, tha -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476573] Preview - Picture is shifted upward
https://bugs.kde.org/show_bug.cgi?id=476573 --- Comment #4 from Alexandre Belz --- Created attachment 162912 --> https://bugs.kde.org/attachment.cgi?id=162912=edit Previewed_JPG_picture -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476573] Preview - Picture is shifted upward
https://bugs.kde.org/show_bug.cgi?id=476573 --- Comment #3 from Alexandre Belz --- Created attachment 162910 --> https://bugs.kde.org/attachment.cgi?id=162910=edit Screen Capture Fit to screen -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476573] Preview - Picture is shifted upward
https://bugs.kde.org/show_bug.cgi?id=476573 --- Comment #2 from Alexandre Belz --- Hello @Maik, Thank you for your fast answer & assistance. My pictures are JPG, the one displayed is attached . On my previous screen capture I zoomed out just to show you that the picture is actually centered in the middle of the Preview area EXCLUDING the top horizontal thumbnail bar, while it should be centered on the remaining space, below. Default viewing mode is indeed "fit to screen". If I click on the "fit to screen" button, nothing changes, it remains in the same mode. Find attached screen capture showing the "fit to screen" display. You'll note that the top part of the picture (top yellow labelled bottle) disappears !) Note that now that I have the issue, all albums/pictures are displayed shifted in that bad centered position. Do you advise me to uninstall/reinstall ? Best regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476573] New: Preview - Picture is shifted upward
https://bugs.kde.org/show_bug.cgi?id=476573 Bug ID: 476573 Summary: Preview - Picture is shifted upward Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- Created attachment 162876 --> https://bugs.kde.org/attachment.cgi?id=162876=edit ScreenCapture of the bug SUMMARY *** In Preview mode, picture is displayed too high. The top comes then masked. *** STEPS TO REPRODUCE 1. Open preview mode 2. Fit to Screen 3. Move to different pictures, album. Change to 100% / revert to "fit to screen". OBSERVED RESULT The Previewed pictured is not centered anymore. Changing 100% / "Fit to screen". Zoomed out view shows that the picture is not centered, as if the top horizontal browsing thumbnails was not taken into consideration for the centering. See attached screen capture. EXPECTED RESULT * Picture should be centered * "Fit to screen" should display all the picture. SOFTWARE/OS VERSIONS Windows: 10 Family ; 19045.3570 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475321] System settings does not show subgroup if window is big and wants to show all groups
https://bugs.kde.org/show_bug.cgi?id=475321 --- Comment #1 from Alexandre Pereira --- Aditional info: terminal output of systemsettings and selecting a group: ``` systemsettings qrc:/kcm/kcm_lookandfeel/main.qml:142:9: QML StackView: Binding loop detected for property "implicitHeight" qml: Page SubCategoryPage_QMLTYPE_88(0x559b95495ed0) is already in the PageRow qml: Pushed pages do not confront the rules. Please check the documentation. push (file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:223) onActiveSubCategoryRowChanged (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:175) expression for onClicked (qrc:/qt/qml/org/kde/systemsettings/CategoriesPage.qml:192) ``` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475321] New: System settings does not show subgroup if window is big and wants to show all groups
https://bugs.kde.org/show_bug.cgi?id=475321 Bug ID: 475321 Summary: System settings does not show subgroup if window is big and wants to show all groups Classification: Applications Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pereira.a...@gmail.com Target Milestone: --- Created attachment 162144 --> https://bugs.kde.org/attachment.cgi?id=162144=edit subgroup is missing SUMMARY *** When the systemsettings window is original big, in that when entering a section with a subgroup, the subgroup isnt visible. This happens when supposedly, the "root group" and the "subgroup" are both visible. The windows needs to be resized vertically (changing height) for the subgroup to appear. *** STEPS TO REPRODUCE 1. Open systemsettings window and make it big 2. Open a group with subgroups 3. Subgroup is not visible OBSERVED RESULT Subgroup is not visible EXPECTED RESULT Subgroup to be visible SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION After adjusting the height of the window, the subgroup becomes visible (although tiny). After that, switching to other items with subgroups works. Screenshots of group before adjusting the window height -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475068] New: Kicker menu gets behind autohide panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=475068 Bug ID: 475068 Summary: Kicker menu gets behind autohide panel on Wayland Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: alexandre.catt...@gmail.com Target Milestone: 1.0 Created attachment 161981 --> https://bugs.kde.org/attachment.cgi?id=161981=edit Illustration of the issue On Plasma Wayland session, with panel set to "Auto Hide", Application Menu (Kicker) menus get behind the panel instead of covering it (as they correctly do on X11). STEPS TO REPRODUCE 1. Start a Plasma Wayland session 2. Add Application Menu to panel 3. Set panel to "Auto Hide" OBSERVED RESULT Menus go behind panel (see attachment) EXPECTED RESULT Menus should cover the panel SOFTWARE/OS VERSIONS KDE Plasma from Arch Linux: KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475066] New: No longer possible to choose default action for Logout Screen
https://bugs.kde.org/show_bug.cgi?id=475066 Bug ID: 475066 Summary: No longer possible to choose default action for Logout Screen Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: alexandre.catt...@gmail.com Target Milestone: 1.0 In System Settings' Desktop Session module, it is no longer possible (don't know from which Plasma version exactly) to choose the default action (log out, shut down, restart ...) for Logout Screen. Has the setting been moved? SOFTWARE/OS VERSIONS KDE Plasma from Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kalzium] [Bug 473096] Molecues editor Crash every time when I clicked it.
https://bugs.kde.org/show_bug.cgi?id=473096 Alexandre Bonneau changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||alexandre.bonneau@linuxfr.e ||u --- Comment #2 from Alexandre Bonneau --- *** This bug has been marked as a duplicate of bug 457191 *** -- You are receiving this mail because: You are watching all bug changes.
[kalzium] [Bug 457191] Kalzium crashes after clicking the Molecular Editor button
https://bugs.kde.org/show_bug.cgi?id=457191 Alexandre Bonneau changed: What|Removed |Added CC||en...@outlook.com --- Comment #6 from Alexandre Bonneau --- *** Bug 473096 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474187] New: After locking the screen HDMI monitor stays black with no wallpaper and no context menu, but windows can be dragged to it
https://bugs.kde.org/show_bug.cgi?id=474187 Bug ID: 474187 Summary: After locking the screen HDMI monitor stays black with no wallpaper and no context menu, but windows can be dragged to it Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alexan...@ecog.io CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY I currently have the following specs and the issue. Step to reproduce are the same i.e.: STEPS TO REPRODUCE 1. Boot with more than one external monitor one in USB C and one over HDMI 2. Lock the computer, let it go into sleep 3. Wake up and unlock OBSERVED RESULT Current setup is the following: - eDP-1 (disabled) - DP-1 (main, does not get disturbed) - HDMI-A-1 (second, gets into black background with no context menu and shadows other virtual desktop windows as background if I have windows drag onto it) EXPECTED RESULT The monitor over HDMI does not got black and retains its background along with normal usage. SOFTWARE/OS VERSIONS: Operating System: Manjaro Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.12-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 38,0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20YG006GGE System Version: ThinkPad E15 Gen 3 ADDITIONAL INFORMATION The screen goes black and disrupts windows that have been put into it. These windows often go to the other screen that has not been affected. I often have only one window left on the zombie screen but I cannot say for that this happens all the time. It also disrupts bismuth in the way that windows get untitled when moved to the main screen after the cold restart. When I proceed to move windows back and then change virtual desktops I can see these windows as background, although glitching. Let me know if you needs logs or any other information. Also let me know if I should open this as a new issue -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 474169] New: Add an option for better managing unfinished tasks which have a passed due date
https://bugs.kde.org/show_bug.cgi?id=474169 Bug ID: 474169 Summary: Add an option for better managing unfinished tasks which have a passed due date Classification: Applications Product: korganizer Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: agendaview (weekview) Assignee: kdepim-b...@kde.org Reporter: alexandre.bonn...@linuxfr.eu Target Milestone: --- Currently, the incomplete tasks that have a passed due date are moved at the top of the weekview as soon as you 'force' an update of that weekview (i.e. going to next week and back). The positioning of the tasks are their due date is _critically important_ if you want to be able to organize your days. Therefore, moving the unfinished task to the current day is not good. Now, since it's still not possible to select multiple tasks and move them in one go, it means that if you fail to complete a bunch of tasks during the previous days, all those unfinished tasks will be stacked at the top of the current day, and if there are many: - it can be very difficult and sometimes impossible to select one in particular to be able to move it to another day in the future - it's impossible to get an overview of which tasks were failed when in the previous days, since they have been moved to the current day, whatever was their due date To circumvent this annoying behavior, it would be great to have an option: - To keep this existing behavior (since it's has been like this for 17+ years) - To keep the unfinished tasks at their due date/time place in the agenda view, but color them in a specific way (without removing their tag color) and/or add a very visible 'Due date passed'-icon. Perhaps here make the tasks background hashed with a variation of the tag color?, or change the task opacity to 60%? Which ever is best design-wise and that insure legibility. The goal of this being to be able to get a clear view of what was missed, and what needs to be rescheduled, and with an added benefit of being able to select those tasks more easily. Also in the future when we'll be able to select and move multiple tasks in one go, it'll greatly help. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 474168] New: Display the Sequence number in the task/event detail pane
https://bugs.kde.org/show_bug.cgi?id=474168 Bug ID: 474168 Summary: Display the Sequence number in the task/event detail pane Classification: Applications Product: korganizer Version: 5.22.3 Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: otherviews Assignee: kdepim-b...@kde.org Reporter: alexandre.bonn...@linuxfr.eu Target Milestone: --- In the .ics files, each VTODO, VEVENT and VJOURNAL have a SEQUENCE information, which translate to the number of editions this particular element has seen. It would be useful to show that number at the bottom of the Task/Event detail pane after the 'Creation date', in italic, like `Revision: 12`. Example in the .ics file: ``` SEQUENCE:12 ``` Example of display in Korganizer detail pane: ``` [icon] Create a feature requests for Korganizer Agenda: Calendar in Nextcloud Starting date: Friday 28th april 2023 18:30:00 -10 Due date: Monday 4th of September 2023 14:30:00 -10 Duration: 128 days 20 hours Description: This a task description... ...that can span multiple lines ..and paragraphs. Tags: Computing, Misc Pourcentage done : 0 % Creation date: Monday 27th March 2023 08:30:04 -10 Revision: 12 ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 473991] New: Templates in .local/share/templates don't override /usr/share/templates
https://bugs.kde.org/show_bug.cgi?id=473991 Bug ID: 473991 Summary: Templates in .local/share/templates don't override /usr/share/templates Classification: Frameworks and Libraries Product: frameworks-kio Version: 5.107.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: contribute.2f...@simplelogin.co CC: kdelibs-b...@kde.org Target Milestone: --- I was trying to override the libreoffice templates that my distro provides with local ones that I modified (so they won't get overwritten on updates) but this doesn't seem to work. Also it seems that KDE detects that a template is the same by having the same URL field in the .desktop file. Which means if they have the same relative URL they'll be treated as the same template. A workaround for now is to remove libreoffice-plasma package so that there are no templates in /usr/share/templates -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442826] After cold boot one of multiple monitors stays black with no wallpaper and no context menu, but windows can be dragged to it
https://bugs.kde.org/show_bug.cgi?id=442826 Alexandre changed: What|Removed |Added CC||alexan...@ecog.io Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #10 from Alexandre --- The issue persists after plasma 5.27.7. I currently have the following specs and the issue. Step to reproduce are the same i.e.: 1. Boot with more than one external monitor 2. Lock the computer, let it go into sleep 3. Wake up and unlock Current setup is the following (and __may differ__ from the original bug post): - eDP-1 (disabled) - DP-1 (main, does not get disturbed) - HDMI-A-1 (second, gets into zombie mode i.e. black background and shadows other virtual desktop windows as background if I have windows drag onto it) The specs for my system are: Operating System: Manjaro Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.12-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 38,0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20YG006GGE System Version: ThinkPad E15 Gen 3 Additional information: The screen goes black and disrupts windows that have been put into it. These windows often go to the other screen that has not been affected. I often have only one window left on the zombie screen but I cannot say for that this happens all the time. It also disrupts bismuth in the way that windows get untitled when moved to the main screen after the cold restart. When I proceed to move windows back and then change virtual desktops I can see these windows as background, although glitching. Let me know if you needs logs or any other information. Also let me know if I should open this as a new issue -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 472817] New: Stockfish engine: "thinks forever"
https://bugs.kde.org/show_bug.cgi?id=472817 Bug ID: 472817 Summary: Stockfish engine: "thinks forever" Classification: Applications Product: knights Version: 2.6.22123 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: alexnc@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 160631 --> https://bugs.kde.org/attachment.cgi?id=160631=edit Stockfish output sample, collected from Knights "chat" console SUMMARY *** The client does not pick Stockfish's answers. The game simply doesn't go on. *** STEPS TO REPRODUCE 1. Create a new game, selecting Stockfish as the player with black OBSERVED RESULT After the first move from white, the console shows Stockfish's output, but a move on board is never done. EXPECTED RESULT Black answers to this first white move. SOFTWARE/OS VERSIONS 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.
[digikam] [Bug 415599] Add date to help DNN face recognition for baby/kid/adult distinction
https://bugs.kde.org/show_bug.cgi?id=415599 --- Comment #6 from Alexandre Belz --- Hi Craig, I agree with you, haircut would probably not be a good metadata parameter. Nevertheless, we as humans can use this as a complement to distinginuish two people having the same skull. Let's take the example of real twins. If at some date (Let's say between 2005 and 2010) Jane had long hair and Mary had cut them short, a human can know that. An good NN could progressively learn, converge, and finally do better suggestions based on this. And if from 2010 to 2015 they had the opposite haircut, NN could use the "date taken" to correlate better and suggest better. The advantage with a NN is that, provided it have access to more (meta)data it can progressively learn (but it's a bit of magic/black box) the differences, it can build a better estimation model. Let's take another example: if both sisters have same haircut, and Mary only plays the piano and Jane plays the guitar, a human will be able to distinguish the two when they play at band, even if they look the same. An ideal NN should be able to learn that also. But the learning process might be long for the NN. Finally, if Jane lives in London and Mary in Paris, the GPS coordinates could help making a guess. After all, a NN is just that : making stastistical guesses. And objective metadata are more reliable and easy to learn for a "young" NN. So back to my initial topic, i think that "date taken" and probably "location" would be great to be added to the NN. Of course, it's not on Digikam shoulders, but more on DNN research team. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415599] Add date to help DNN face recognition for baby/kid/adult distinction
https://bugs.kde.org/show_bug.cgi?id=415599 --- Comment #4 from Alexandre Belz --- Hi guys, i'm working in a company that is now using A.I. and many parameters seem to be potentially added to the "big data" in which the -customized- AI engine works and determine statistical results. More than ever, i do believe that adding *additionnal metadata* such as "date taken" to au updated DNN module (or any other picture oriented AI) should (must?) help to improve the quality of the estimation model, and thus, the face recognition. In other words, as a face is not static, and will, fore sure, evolve with years, how does the AI enginee manages this evolution ? The above comments would deserve to be sent to the DNN team, i think, and recommend. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472220] New: Renaming an album leads to an error if Digikam is working on it
https://bugs.kde.org/show_bug.cgi?id=472220 Bug ID: 472220 Summary: Renaming an album leads to an error if Digikam is working on it Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Albums-TreeView Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- Created attachment 160265 --> https://bugs.kde.org/attachment.cgi?id=160265=edit Screen capture SUMMARY *** Renaming an album may lead to an error if Digikam is working on it (typically after an import process) This is related to https://bugs.kde.org/show_bug.cgi?id=412678 but know I think I understand why. *** STEPS TO REPRODUCE 1. From the album view (left tree) 2. Choose an album, and refresh it (F5) 2. Do not wait and immediately try to rename the folder/album (Maj+F2). OBSERVED RESULT 3. An error message appears EXPECTED RESULT 3. folder/Album should be renamed as desired. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION The error messages seems to appear if the bottom right progress bar is not 100%. If I wait the progress bar to finish, I don't see the error message, and the folder is correctly renamed. I wonder if Digikam is certainly accessing some files, maybe even writing some sidecar files or database entries. It may be dangerous to rename this folder while a process is running, and this is maybe why digikam rises an error. I suggest digikam to write a better message, such as "a process is running, please wait before renaming". Or maybe cue it so that it's done when possible. "a process is running, renaming will be performed asap". -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470199] Latte dock crash
https://bugs.kde.org/show_bug.cgi?id=470199 --- Comment #1 from Alexandre Oliveira --- Created attachment 160062 --> https://bugs.kde.org/attachment.cgi?id=160062=edit New crash information added by DrKonqi latte-dock (0.10.8) using Qt 5.15.10 I just opened the start menu (OnzeMenu) and latte-dock crashed. -- Backtrace (Reduced): #6 0x7fa8461014dc in QQmlData::wasDeleted(QObject const*) (object=0x560467a6fac0) at ../../include/QtQml/5.15.10/QtQml/private/../../../../../../qtdeclarative/src/qml/qml/qqmldata_p.h:338 #7 QV4::QObjectWrapper::wrap(QV4::ExecutionEngine*, QObject*) (engine=0x560466fc2b10, object=0x560467a6fac0) at ../../include/QtQml/5.15.10/QtQml/private/../../../../../../qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper_p.h:213 #8 0x7fa84617416a in loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (v4=0x560466fc2b10, object=0x5604680d3de0, property=...) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:205 #9 0x7fa8461752fd in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) (property=0x7ffe2c11c090, hasProperty=0x7ffe2c11c088, revisionMode=QV4::QObjectWrapper::CheckRevision, name=0x7fa811dc1850, object=0x5604680d3de0, qmlContext=0x5604680d39b0, engine=0x560466fc2b10) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:388 #10 QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) (engine=0x560466fc2b10, qmlContext=0x5604680d39b0, object=0x5604680d3de0, name=0x7fa811dc1850, revisionMode=QV4::QObjectWrapper::CheckRevision, hasProperty=0x7ffe2c11c088, property=0x7ffe2c11c090) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:358 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470199] Latte dock crash
https://bugs.kde.org/show_bug.cgi?id=470199 Alexandre Oliveira changed: What|Removed |Added CC||rockyt...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439680] Signature border issue
https://bugs.kde.org/show_bug.cgi?id=439680 --- Comment #8 from Alexandre ZANNI --- I have been having the issue for a long time. I currently have KMail Version 5.23.2 (23.04.2) on ArchLinux, KDE Frameworks Version 5.106.0, Qt Version 5.15.9 (built against 5.15.9). My signature displayed in Firefox https://bugs.kde.org/attachment.cgi?id=159649 My signature displayed in the Signature Editor https://bugsfiles.kde.org/attachment.cgi?id=159650 My signature displayed in the Mail Compositor https://bugsfiles.kde.org/attachment.cgi?id=159651 Signature source code https://bugsfiles.kde.org/attachment.cgi?id=159652 My signature displayed in the sent folder or as received by others https://bugs.kde.org/attachment.cgi?id=159653 Source code of the email as sent by KMail https://bugsfiles.kde.org/attachment.cgi?id=159654 It seems that Kmail totally modify the inline style of the signature instead of letting it untouched. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439680] Signature border issue
https://bugs.kde.org/show_bug.cgi?id=439680 --- Comment #7 from Alexandre ZANNI --- Created attachment 159654 --> https://bugs.kde.org/attachment.cgi?id=159654=edit Source code of the email as sent by KMail -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439680] Signature border issue
https://bugs.kde.org/show_bug.cgi?id=439680 --- Comment #6 from Alexandre ZANNI --- Created attachment 159653 --> https://bugs.kde.org/attachment.cgi?id=159653=edit My signature displayed in the sent folder or as received by others -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439680] Signature border issue
https://bugs.kde.org/show_bug.cgi?id=439680 Alexandre ZANNI changed: What|Removed |Added Attachment #159652|Sinature source code|Signature source code description|| -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439680] Signature border issue
https://bugs.kde.org/show_bug.cgi?id=439680 --- Comment #5 from Alexandre ZANNI --- Created attachment 159652 --> https://bugs.kde.org/attachment.cgi?id=159652=edit Sinature source code All borders are none or zero -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439680] Signature border issue
https://bugs.kde.org/show_bug.cgi?id=439680 --- Comment #4 from Alexandre ZANNI --- Created attachment 159651 --> https://bugs.kde.org/attachment.cgi?id=159651=edit My signature displayed in the Mail Compositor -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439680] Signature border issue
https://bugs.kde.org/show_bug.cgi?id=439680 --- Comment #3 from Alexandre ZANNI --- Created attachment 159650 --> https://bugs.kde.org/attachment.cgi?id=159650=edit My signature displayed in the Signature Editor -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439680] Signature border issue
https://bugs.kde.org/show_bug.cgi?id=439680 Alexandre ZANNI changed: What|Removed |Added CC||alexan...@acceis.fr --- Comment #2 from Alexandre ZANNI --- Created attachment 159649 --> https://bugs.kde.org/attachment.cgi?id=159649=edit My signature displayed in Firefox -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446188] Dedicated "Faces" section added to the Image Properties tab from the Right Sidebar.
https://bugs.kde.org/show_bug.cgi?id=446188 --- Comment #7 from Alexandre Belz --- Ok, that's indeed better now. Thank you ! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 468440] Global Application shortcuts are slower than they could be
https://bugs.kde.org/show_bug.cgi?id=468440 --- Comment #4 from Alexandre Pereira --- "so I think it's fair to say that there's no "global shortcuts are slow" bug in plasma after all." Well, after your tip on using Meta+1, Meta+2 to launch apps, I started using that, and it "seems faster" than "global application shortcuts" even on Gentoo and Arch. I say "seem faster" because timing kstart here gives around 70~80ms delay, so its hard to measure it really. So at the end this will improve things :) Thanks for reports this bug and fixing nixos side and Thanks KDE devs for improving KDE all the time! :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 468440] Global Application shortcuts are slower than they could be
https://bugs.kde.org/show_bug.cgi?id=468440 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458574] Denied access to save an opened file on Windows
https://bugs.kde.org/show_bug.cgi?id=458574 Alexandre Valença Alves Barbosa changed: What|Removed |Added CC||bar.barb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466693] New: Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=466693 Bug ID: 466693 Summary: Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog. Classification: Applications Product: Discover Version: 5.27.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: plasma-b...@kde.org Reporter: a...@viatis.com CC: aleix...@kde.org, eli...@gmail.com, n...@kde.org Depends on: 419055 Target Milestone: --- +++ This bug was initially created as a clone of Bug #419055 +++ SUMMARY Even when the user sets a lower frequency of automatic updates (e.g. weekly) in the Software Sources dialog, Discover nevertheless checks for updates daily. This means that effectively the user has no control over automatic update frequency. STEPS TO REPRODUCE 1. In Discover, click on "Sources" -> "Software Sources". Provide the password if required. 2. In the "Software Sources" dialog that opens, click on "Updates". Make sure the "Check for updates" checkbox is checked, and choose a frequency other than "Daily" (e.g. "Weekly") in the corresponding dropdown. Click on "Close". OBSERVED RESULT Update notifications appear in the notifications area multiple times a week, presumably on every startup if updates are available. EXPECTED RESULT Update notifications appear at most once a week. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.1-arch1-1 (64-bit) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION SUMMARY Even when the user sets a lower frequency of automatic updates (e.g. weekly) in the Software Sources dialog, Discover nevertheless checks for updates daily. This means that effectively the user has no control over automatic update frequency. STEPS TO REPRODUCE 1. In Discover, click on "Sources" -> "Software Sources". Provide the password if required. 2. In the "Software Sources" dialog that opens, click on "Updates". Make sure the "Check for updates" checkbox is checked, and choose a frequency other than "Daily" (e.g. "Weekly") in the corresponding dropdown. Click on "Close". OBSERVED RESULT Update notifications appear in the notifications area multiple times a week. EXPECTED RESULT Update notifications appear at most once a week. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.10 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION This is a follow up to bug 401810 (Phabricator patch D17375) and bug 337752. Unfortunately, it appears that the issue wasn't resolved (at least not on my system). My analysis shows that Discover's PackageKitNotifier attempts to check the frequency set in software-properties by running "apt-config dump" and looking for the "Apt::Periodic::Update-Package-Lists" property in its output. However, on my system the property name starts with uppercase "APT" rather than "Apt", and ends with a semicolon. Therefore PackageKitNotifier fails to find the correct property value, and falls back to the default of a daily check. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=419055 [Bug 419055] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419055] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=419055 Alexandre changed: What|Removed |Added Blocks||466693 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=466693 [Bug 466693] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466131] Flatpak icons missing in system tray
https://bugs.kde.org/show_bug.cgi?id=466131 Alexandre changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Alexandre --- Apparently it was a conflict between SOME Flatpak apps and the latest Plasma update. Anyway, I was able to solve the most annoying missing tray icon (SynologyDrive) by downloading it elsewhere. As of today, other Flatpaks seem to work correctly. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 466131] New: Flatpak icons missing in system tray
https://bugs.kde.org/show_bug.cgi?id=466131 Bug ID: 466131 Summary: Flatpak icons missing in system tray Classification: Plasma Product: kdeplasma-addons Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: a...@viatis.com Target Milestone: --- SUMMARY All running Flatpak apps (whether autostarted or not) are missing their icon in the system tray since plasma update 5.27. STEPS TO REPRODUCE 1. Launch any Flatpak app, check if icon is showing in the tray OBSERVED RESULT No icon is shown in plasma system tray. In the "entries" menu, no Flatpak apps appear either. Other programs (i.e. installed via pacman) work as expected. EXPECTED RESULT System tray icon should show normally for Flatpak apps like the ones of any other programs. SOFTWARE/OS VERSIONS Linux: 6.1.12-arch1-1 (64-bit) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Reinstalling apps and/or switching from X11 to Wayland does not change anything. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 389766] Weather widget does not show the temperature beside or over the icon in the Plasma panel when I use wetter.com provider
https://bugs.kde.org/show_bug.cgi?id=389766 Alexandre changed: What|Removed |Added CC||a...@viatis.com --- Comment #8 from Alexandre --- (In reply to Patrick Silva from comment #7) > Currently there are options the show the temperature beside or over the > widget icon if the widget is placed on Plasma panel. > None works with wetter.com provider. > > Operating System: KDE neon Unstable Edition > KDE Plasma Version: 5.27.80 > KDE Frameworks Version: 5.104.0 > Qt Version: 5.15.8 > Graphics Platform: Wayland Same by me. I do not recall if these options were available before Plasma 5.27 but the temperature showed correctly in the panel. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465432] Middle click with three-fingers touch on touchpad is lost randomly after using 4-fingers swipe gesture
https://bugs.kde.org/show_bug.cgi?id=465432 Alexandre Hen changed: What|Removed |Added Summary|Middle click with |Middle click with |three-fingers touch on |three-fingers touch on |touchpad is lost randomly |touchpad is lost randomly |after using 4-fingers swipe |after using 4-fingers swipe |gesture or Meta+W |gesture -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465432] Middle click with three-fingers touch on touchpad is lost randomly after using 4-fingers swipe gesture or Meta+W
https://bugs.kde.org/show_bug.cgi?id=465432 --- Comment #1 from Alexandre Hen --- Created attachment 156033 --> https://bugs.kde.org/attachment.cgi?id=156033=edit cat /proc/bus/input/devices -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465432] New: Middle click with three-fingers touch on touchpad is lost randomly after using 4-fingers swipe gesture or Meta+W
https://bugs.kde.org/show_bug.cgi?id=465432 Bug ID: 465432 Summary: Middle click with three-fingers touch on touchpad is lost randomly after using 4-fingers swipe gesture or Meta+W Classification: Plasma Product: kwin Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: alexan...@eskulap.fr Target Milestone: --- Created attachment 156032 --> https://bugs.kde.org/attachment.cgi?id=156032=edit Configuration SUMMARY I lose three-fingers click from the touchpad for Middle-Click after using the 4 fingers gesture or Meta+W. It is especially visible in the tabs bar of Firefox for closing or opening tabs. Instead, and after multiple attempts of three-fingers touch, it shows, sometimes, the context menu instead (what I get usually with a two-fingers touch on my touchpad). It is not systematic after every gestures... Important note : it does not seem happen with Meta+W. Firefox is configured to have his titlebar disabled. I set plasma to have a right click with a two-fingers touch and a middle click with a three-fingers touch. I'm on Fedora Kinoite 37 Beta on Wayland. STEPS TO REPRODUCE 1. Use the gesture "4-fingers swipe" up or down, multiple times in a row. 2. After each #1, try to open or close a tab in Firefox, or paste a text that you copied in KWrite, by using a three-fingers touch on your touchpad OBSERVED RESULT After a few tries, the context menu is showing (a two-fingers action usually) instead of having the action associated with a three-fingers touch. You can have the usual behaviour by triggering a new #1, then #2. 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.
[krita] [Bug 464484] New: TGA files not saved correctly
https://bugs.kde.org/show_bug.cgi?id=464484 Bug ID: 464484 Summary: TGA files not saved correctly Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: alexandre.prokoud...@gmail.com Target Milestone: --- Krita saves 8-bit RGBA TGA files in a way that appears to be wrong. GIMP reports this upon an attempt to open such a file: Unhandled sub-format in '/home/alex/Pictures/test.tga' (type = 2, bpp = 32, alpha = 4) (related bug report: https://gitlab.gnome.org/GNOME/gimp/-/issues/9067) >From #krita: Lynx3d: "Bits 3-0 - number of attribute bits associated with each pixel. (...) For Targa 32, it should be 8." so it seems wrong indeed that's what krita does: s << quint8(hasAlpha ? 0x24 : 0x20); // top left image (0x20) + 8 bit alpha (0x4): -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 463479] I'm missing a "move album to..." menu and shortcut
https://bugs.kde.org/show_bug.cgi?id=463479 --- Comment #1 from Alexandre Belz --- To me more realistic, folders are : D:\Pictures\1. Coarse selection D:\Pictures\2. Ask to my wife D:\Pictures\3. Picture correction D:\Pictures\4. Facetag D:\Pictures\5. GeoTag D:\Pictures\6. Good to archive -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 463479] New: I'm missing a "move album to..." menu and shortcut
https://bugs.kde.org/show_bug.cgi?id=463479 Bug ID: 463479 Summary: I'm missing a "move album to..." menu and shortcut Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Albums-MainView Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- SUMMARY *** As I use Digikam as a workflow manager, I need to move Album from one parent Folders to another one . The current Drag/Drop capability is OK when you have few folders, but when you need to scroll down > 30 folders, it becomes a pain. Moreover, when you are in mobility, with a laptop, using the trackpad to drag/drop is a pain. For instance, I would like to be able to easily move an Album "2022-12 Xmas with family" from the step-folders below 1. Coarse selection 2. Ask to my wife 3. Picture correction 4. Facetag 5. GeoTag 6. Good to archive *** STEPS TO REPRODUCE 1. in the left panel, Select an Album (not a picture) 2. Right Click OBSERVED RESULT There is no "Move To..." option for albums in the contextual Album menu. EXPECTED RESULT in the contextual Album menu, - Intermediate, Step 1: I would like to see the "Move To..." option, opening the same "Move To..." GUI than for an individual picture. But here, the whole album would be moved. Shortcut (Ctrl+M) same so than for individual picture. - Final target, Step 2: I would like to see a "Move to Predefined Folders" option, with a child dropdown list of predefined destination folders (defined in Parameters). This action would become powerful if we can use programmable Shortcuts. For instance : Ctrl+M+1 = move the last selected item (Album or Picture) to preset folder #1 SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION Don't hesitate to ask me more informations. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 415933] Fonts of gtk3 apps installed via flatpak are not antialiased on Wayland
https://bugs.kde.org/show_bug.cgi?id=415933 Alexandre Pereira changed: What|Removed |Added Resolution|DOWNSTREAM |FIXED CC||pereira.a...@gmail.com --- Comment #8 from Alexandre Pereira --- > For what it's worth, it still happens to me even with xdg-desktop-portal-gtk > installed, so I guess it is just a real downstream issue. I just had this issue, and installed xdg-desktop-portal-gtk, and it seemed it didn't work, but after restarting systemctl --user xdg-desktop-portal it works ( if one does not restart it, it doesn't work ). Hope it helps ! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462816] Keyboard shortcuts stop responding when focused on a Chromium application
https://bugs.kde.org/show_bug.cgi?id=462816 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com --- Comment #1 from Alexandre Pereira --- some context, this is due to: https://github.com/chromium/chromium/commit/ac0160a4ae8b8432a2041992415ceb1c1b0597e0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462845] The default button changed to Cancel at permanent delete
https://bugs.kde.org/show_bug.cgi?id=462845 --- Comment #16 from Alexandre --- (In reply to Felix Ernst from comment #14) > I agree! We should have kept the old behaviour unless there was a big > discussion about this. The thing is: This never was an intentional change! > > (In reply to Nick Stefanov from comment #11) > > Some people think KDE Plasma is a testing pilot or a hobby. No, it's my full > > time work horse and now my workflow is broken. I'm pissed off from such > > "improvements". Let's focus on fixing bugs, not such "improvements", KDE > > needs this badly. > (In reply to Peter Tselios from comment #13) > > First, I honestly believe that developers spend their energy to non-useful > > "improvements". They spend time to "improve" non-broken things, then they > > spend more time to revert them. > > I am sure you will be glad to hear then that this behaviour change happened > as a side-effect of fixing https://bugs.kde.org/show_bug.cgi?id=431351. Your > assumptions about this being an ill-conceived attempt of improving something > that didn't need improving is therefore wrong. Your annoyance is also > misplaced: We simply don't have enough volunteers or money to make sure that > such things never happen. > > Now let's get back to solving the problem instead of venting. Glad to read this. Thank you for your work! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462845] The default button changed to Cancel at permanent delete
https://bugs.kde.org/show_bug.cgi?id=462845 Alexandre changed: What|Removed |Added CC||a...@viatis.com --- Comment #10 from Alexandre --- I don't why this change was made. The user already makes an implicit confirmation by pressing the shift key. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462448] New: Switching Virtual Desktops with Ctrl+Alt+MouseWheel seems inverted
https://bugs.kde.org/show_bug.cgi?id=462448 Bug ID: 462448 Summary: Switching Virtual Desktops with Ctrl+Alt+MouseWheel seems inverted Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pereira.a...@gmail.com Target Milestone: --- SUMMARY Switching virtual desktops using Ctrl+Alt+MouseWheel seems inverted in the direction of just using the mouse wheel on the desktop. In my case, doing Ctrl+Alt+MouseWheel Up switches a virtual desktop down, and Ctrl+Alt+MouseWheel Down, switches a virtual desktop up. ( I have virtual desktops in a vertical layout ) The opposite happens when just using the mouse wheel and scrolling when the desktop is focused. Using the mouse setting on the mouse kcm, of inverted scrolling, the opposite from above happens, and the behaviour of the two ways of switching virtual desktop are still different. STEPS TO REPRODUCE 1. Add some virtual desktops 2. Switch between them using Ctrl+Alt+MouseWheel 3. OBSERVED RESULT The Virtual Desktops switch in an inverted manner, like if it was a gesture movement, not a mouse wheel on a desktop. EXPECTED RESULT The Virtual Desktops to switch down when the mouse wheel is scrolled down, and up when scrolled up on the mouse wheel. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Using git version of plasma, and using kwin wayland. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462366] The currency conversion rate for EUR/XPF is wrong
https://bugs.kde.org/show_bug.cgi?id=462366 Alexandre Bonneau changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from Alexandre Bonneau --- Ok, my bad, it seems I have entered the 1000/8,38 ratio in both EUR -> XPF and XPF -> EUR ratio. This is fixed now. Thanks for the hint. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462366] New: The currency conversion rate for EUR/XPF is wrong
https://bugs.kde.org/show_bug.cgi?id=462366 Bug ID: 462366 Summary: The currency conversion rate for EUR/XPF is wrong Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: alexandre.bonn...@linuxfr.eu Target Milestone: --- SUMMARY The currency conversion rate for EUR/XPF is wrong, leading to hugely wrong dashboards and reports STEPS TO REPRODUCE 1. You have an account with the total amount 680.056 XPF 2. In the value calculated in Euro is calculated to 81.152.267,14 € (this is wrong) The fixed ratio between EUR and XPF is equal to 1000/8,38 ~= 119,3317422. OBSERVED RESULT & EXPECTED RESULT When you have 680.056 XPF, you should do 680.056 / 119,33 ~= 5.698,86928€. Currently Kmymoney does the inverse using 680.056 * 119,33 = 81.152.267,14 €. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 400043] Korganizer categories are broken; never stay selected, and duplicate themselves
https://bugs.kde.org/show_bug.cgi?id=400043 Alexandre Bonneau changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Alexandre Bonneau --- Also in Korganizer 5.21.3. The categories are still a pain to use; they still get duplicated, they still are un-sorted, they still 'sometimes' decide to forget the color they were assigned to, and they still aren't coherent between Korganizer and say, Kmail. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 460260] On a multi screen setup on Wayland, KDE app windows do not remember the size they had if the primary monitor is not the leftmost one.
https://bugs.kde.org/show_bug.cgi?id=460260 Alexandre Hen changed: What|Removed |Added CC||alexan...@eskulap.fr --- Comment #4 from Alexandre Hen --- Hello, It is also affecting me. I have two monitors and the primary one is on the right. If I switch my primary on the left one, the windows size are remembered. My configuration : Fedora 37 Kinoite on Wayland - up to date version 221117 Nvidia RTX 2080 with driver 520.56.06 Left monitor : Dell U2515H 1440p @ 60hz Right monitor : AG271QG 1440p @ 144Hz Ryzen 3900X RAM 32Go 3466Mhz Thank you. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 374779] Categories should be hierarchically organized
https://bugs.kde.org/show_bug.cgi?id=374779 Alexandre Bonneau changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Alexandre Bonneau --- Yes, this is still a valid feature request. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458574] Denied access to save an opened file on Windows
https://bugs.kde.org/show_bug.cgi?id=458574 --- Comment #16 from Alexandre --- Serious? Well anyway the problem has been solved. Updates are usually made to the store library. They arrive and update the application. Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows De: Albert Astals Cid Enviado: Friday, September 9, 2022 1:04:42 PM Para: alexandre.arr...@outlook.com Assunto: [okular] [Bug 458574] Denied access to save an opened file on Windows https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D458574data=05%7C01%7C%7Ca091eb4e7295467b01cb08da927d0560%7C84df9e7fe9f640afb435%7C1%7C0%7C637983362900028178%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=T%2BqbELH5sGShc5NqI4%2BIT9YeqWpy01AqBzc2isiTXQ8%3Dreserved=0 --- Comment #15 from Albert Astals Cid --- > I uninstalled Okular with Revo Uninstaller and installed it again. The > result was that it stopped giving the problem. No, what happened is that you got the new version. -- You are receiving this mail because: You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458574] Denied access to save an opened file on Windows
https://bugs.kde.org/show_bug.cgi?id=458574 --- Comment #14 from Alexandre --- Dear Albert. Informing me, what I did. I uninstalled Okular with Revo Uninstaller and installed it again. The result was that it stopped giving the problem. Very good! Anyway if i give the problem again I'll contact you. If you have a good update that's newer, we'll wait in the Microsoft store. Thank you very much for your attention and return. Alexander Arraes Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows De: Albert Astals Cid Enviado: Friday, September 9, 2022 10:49:40 AM Para: alexandre.arr...@outlook.com Assunto: [okular] [Bug 458574] Denied access to save an opened file on Windows https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D458574data=05%7C01%7C%7Cf9574c6f8c354b77f91108da926a25b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637983281840170388%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=DKbjofPWv7FiMiAUvJK0r9K%2Fbe3B5DU%2FFBe3BtqwyAs%3Dreserved=0 --- Comment #12 from Albert Astals Cid --- > How can I repair it? I have the Microsoft Store version and I have no > programming skills. Be patient. Wait for the fixed version to appear as an update in the Microsoft Store, should be today, tomorrow. -- You are receiving this mail because: You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458574] Denied access to save an opened file on Windows
https://bugs.kde.org/show_bug.cgi?id=458574 --- Comment #13 from Alexandre --- Good morning, Albert. exactly my Okular comes from the Microsoft store. It's been working fine ever since. But this problem came up. From what I understand you will do an update in the same Microsoft store. I'm waiting for you. Thank you. Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows De: Albert Astals Cid<mailto:bugzilla_nore...@kde.org> Enviado:sexta-feira, 9 de setembro de 2022 10:49 Para: alexandre.arr...@outlook.com<mailto:alexandre.arr...@outlook.com> Assunto: [okular] [Bug 458574] Denied access to save an opened file on Windows https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D458574data=05%7C01%7C%7Cf9574c6f8c354b77f91108da926a25b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637983281840170388%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=DKbjofPWv7FiMiAUvJK0r9K%2Fbe3B5DU%2FFBe3BtqwyAs%3Dreserved=0 --- Comment #12 from Albert Astals Cid --- > How can I repair it? I have the Microsoft Store version and I have no > programming skills. Be patient. Wait for the fixed version to appear as an update in the Microsoft Store, should be today, tomorrow. -- You are receiving this mail because: You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458899] Prezados o Okular estava funcionando maravilha, mas hoje ele não está salvado as alterações que faço no arquivo pdf. Está dando uma menssagem assim: O arquivo não pôde ser salvo
https://bugs.kde.org/show_bug.cgi?id=458899 --- Comment #1 from Alexandre --- Estava salvando normalmente e começou a dar esse erro. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458899] New: Prezados o Okular estava funcionando maravilha, mas hoje ele não está salvado as alterações que faço no arquivo pdf. Está dando uma menssagem assim: O arquivo não pôde ser
https://bugs.kde.org/show_bug.cgi?id=458899 Bug ID: 458899 Summary: Prezados o Okular estava funcionando maravilha, mas hoje ele não está salvado as alterações que faço no arquivo pdf. Está dando uma menssagem assim: O arquivo não pôde ser salvo em 'file:///C:/Us agem de que acesso negado para salvar nesse endereço Product: okular Version: 22.08.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: task Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: alexandre.arr...@outlook.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. 2. 3. prezados o okular não está salvando as alterações que faço do documento pdf ao sair dele está dando a seguinte mensagem: O arquivo não pôde ser salvo em 'file:///C:/Users/alexa/OneDrive/Documentos/Okular/Seja Feliz para Sempre - Um Curso da Bíblia para Você - Incompleto.pdf'. Erro: 'Acesso negado para C:/Users/alexa/OneDrive/Documentos/Okular/Seja Feliz para Sempre - Um Curso da Bíblia para Você - Incompleto.pdf.'. Tente salvá-lo em outro local. 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.
[kactivitymanagerd] [Bug 441680] The default activity can be removed
https://bugs.kde.org/show_bug.cgi?id=441680 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com --- Comment #1 from Alexandre Pereira --- Hi, I tried reproducing this bug report in a new KDE Neon: neon-developer-20220808-1852.iso. I tried setting up a user on X11, with creating a new activity and immediately deleting the "original one". Nothing bad happened. I tried again with a new user, do the same on Wayland. I also tried with another new user, to add some widgets to the desktop first, and then create a new one and delete the original. Nothing bad happened. Can you try it on a VM (or in any other way) with a recent KDE ? Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 --- Comment #19 from Alexandre Pereira --- > That’s the big misunderstanding here and probably why this bug report was > closed so overhasty: The code is deceptive in this case. There was something > altered somewhere else, making the values run faster or whatnot, I don’t > know. But 5.25 speeds were definitely extremely accelerated. You will see it > in comparison to an older release. I am really starting to think that the speeds in 5.25 became faster because of the AnimationDurationFactor (the speed slider) got moved into kdeglobals instead of kwinrc. I didn't notice any speed up from 5.24 to 5.25 ( and since I have been running git version for years now, I would have noticed it just as I noticed this change ). See bug which was just "recently" fixed: https://bugs.kde.org/show_bug.cgi?id=431259 By the way ... was the bug report closed overhasty? I thought it was closed because of the commit. Anyway i guess I reported my findings (I will test a live neon iso on the weekend), maybe let more users check it out on the 5.26 release and see if they like it. maybe I am the odd one here, using the present windows effect too much. Thanks for your time ! :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 --- Comment #16 from Alexandre Pereira --- Hi, > Alexandre, may I ask how you have perceived the speed of the old > implementation of Present Windows (pre-Overview) until Plasma 5.24? The previous speed of Present Windows were fine, and it was when I switched to it as an alt tab replacement. I also checked the code: https://invent.kde.org/plasma/kwin/-/blob/v5.23.0/src/effects/presentwindows/presentwindows.cpp#L164 > Could you test with a live CD? In my perception, this new values are just a > touch slower than the old, 300 ms feels just a bit closer to my eye. But like > my whole bug report and the Reddit thread with dozens of upvotes found, 200 > ms is definitely way too fast. I will test a live iso later on. Like I said on my previous comment, I use the 1 tick slider speed anim to the left, which makes ALL animations smooth and consistent. Overview seems smooth, but now noticeable slow, and others super fast. Also, the speed can be related to the bug I mentioned on the previous commit, when it was changed from kwinrc to kdeglobals, and the speed was reset (making it faster to those that had a slower speed factor on kwinrc. I am speculating here, could be, probably isn't). > If you have used it like an Alt + Tab replacement, maybe look into the Alt + > Tab window switcher settings, there is a grid layout you can chose. hum... I actually prefer the present windows/overview effect to the grid layout, but I know the effect you mention, since I use the small grid as alt tab. I just don't like alt tab as much as I prefer to see all windows scaled on the screen. > Present Windows, Overview and the actual Grid should have another speed with > more elegance, signaling also your current window positions. That’s how this > effect series worked since Plasma 4, Compiz and on their origins in OS X. > Plasma 5.25’s speeds just were a shortsighted fault of the reimplemetation. I don't think 5.25's speeds are faster. Looking at the code, they are slower. But in my mind, some effects shouldn't have more "elegance" than others, they all should have elegance (especially no frame skipping). That is why, again, I used the 1.4 factor, which would probably put the timings around 300ms from the 200ms (and with it, all the effects were buttery smooth). Maybe 300ms is a good middle ground, if you also feel it is a touch slower. But as to how it should be, that isn't for me to say, nor I am part of the VDG nor a "usability expert". If the goal is to have some effects fast and some slow, and I am the only one with an issue to it, then nevermind, I will adapt to it some way. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 --- Comment #14 from Alexandre Pereira --- > Interesting, I wonder if another factor is at play or causing the scaling to > be wrong in cases. On my system and liveCD tests, the merged changes to > duration and easing cause the WindowHeap transitions to match every other > effect, when they didn't before. Even the old duration of 300ms is too quick. Its strange, here it was "on par" with other effects, which I then used a 1.4 animation factor ( one tick just to the left of default ). > I just spun up a new local user with no config, tried plus and minus 2 ticks > on the global Animation Speed slider, and compared the Overview and Desktop > Grid against the open/close Window Animations (Fade, Glide, Scale) and > Minimize effects, they still match up for me and look very consistent. Even > extremes on the scale match up, and i'm honestly wondering why the scale is > so large as the center 5 ticks are the most distinct. Yes, i agree, the extreme values are way ... extreme :) If Nate has no issue, I could supply a patch to make it less "extreme" and more granular. Its extremely weird, because the other effects are all around 150ms~200ms. even old present windows. And here is very very noticeable. > Could something in config be overriding the duration and throwing things off > on some environments but not all? For instance, I removed this line in my > config a year or so ago (around 5.23 release when things regressed) to fix > the issue in the title: https://bbs.archlinux.org/viewtopic.php?id=263845. > It makes me wonder if a similar thing is occurring with the Windowheap > effects for some users, possibly even the systems that 400ms look good on > (liveCD though..) I've also tested the durations with a 60hz laptop while on > a trip this last week, to rule out higher refresh displays being an edge case. I can try a kde neon live cd in the weekend or earlier if I can. But that setting is correct here. I tend to keep an eye on it, because there was a bug that used to reset it, which David Edmundson fixed. ( he also fixed other bugs, like this one: https://invent.kde.org/plasma/kwin/-/commit/0bb3eb2baf5b0a4c0aacbe23bf55c47c0a2c39fd ). Just to clear one possible issue, you are also using kde git version, correct? Also as a workaround, the slide/glide effect allow to specify the duration. Overriding it to 400 makes it more similar in timings to the overview/present windows now. So something weird is happening here... I don't know if its not my system at fault, but I checked the kwinrc variable (it should NOT have one) and the kdeglobals one (which can actually be a custom number if one edits it manually). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com --- Comment #12 from Alexandre Pereira --- Hi, This is just a matter of taste/opinion, i guess... but as a heavy present windows/overview user, this is now way too slow. As using present windows as almost an alt+tab replacement, its now ... weird ... Worse, i guess, is that it feels completely disconnected with other animation speeds: window opening, closing, fading, minimizing, plasma popups sliding. for example: * sliding popups is 150ms * slide (open/close) is 200ms and glide is 160ms * fade is 150 ms The issue with 400 for me, is that is completely set apart from the rest of kde's animations, making me unable to control it (set it faster, makes everything super fast... make everything "normal speed", present windows/ overview seem super slow ) Could a middle ground be achieved on this ? Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368872] Plasmashell panel when put on the middle edge of a multi screen setup does not stay below
https://bugs.kde.org/show_bug.cgi?id=368872 Alexandre Pereira changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #3 from Alexandre Pereira --- I can now replicate reliably: It needs to be a "multi screen setup". Panel is on secondary screen (on the right, in wayland), and have 2 windows for example: Putting the window above panel , and changing windows while on the same monitor, it works well. But as soon as I change to the other monitor and pass the mouse through the desktop, it puts the panel on top. Strangely this does not happen if the mouse does not "travel above the desktop" while moving the cursor to the other monitor. (even if it does not focus the desktop, it stills raises the panel) Mouse "activation policy" doesn't change anything (either click to focus or follows mouse does the same) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453603] Window spanning multiple screens temporarily disappear when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=453603 Alexandre Pereira changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Alexandre Pereira --- seems fixed with: https://invent.kde.org/plasma/kwin/-/commit/df1938b8af46a1d033264afc9851b48d33c8632f Thank you very much -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 420237] Airplane mode cannot be toggled without Wi-Fi adapter
https://bugs.kde.org/show_bug.cgi?id=420237 Alexandre CATTEAU changed: What|Removed |Added Version|5.20.3 |5.25.2 --- Comment #2 from Alexandre CATTEAU --- Still present on: Arch Linux KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 455283] plasma-pa 5.25.0 applet hides virtual devices by default
https://bugs.kde.org/show_bug.cgi?id=455283 Alexandre CATTEAU changed: What|Removed |Added CC||alexandre.catt...@gmail.com --- Comment #5 from Alexandre CATTEAU --- Just to add another use case where virtual devices are useful in applet: I use pulseaudio-dlna to add virtual audio devices corresponding to DLNA renderers (or "players") on local network. It allows for example to punctually move an audio source to an output device in another room. And doing so with the drag'n'drop feature of the applet is just perfect. ;) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 135939] need custom font for list of feeds
https://bugs.kde.org/show_bug.cgi?id=135939 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com --- Comment #5 from Alexandre Pereira --- This would be really great if it could be done. Something simple as allowing the font size on the articles list. It would be awesome if something like in kmail and its "emails list" (where you can select a theme between classic/smart/smart with toggle or custom) but as something simple, allowing to change the fonts. In my use case, as I mostly want to quickly read the title between lots of items and only really read a few that interest me, bigger fonts would be really great. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356752] Weird animation when resizing activity pager widget in panel
https://bugs.kde.org/show_bug.cgi?id=356752 Alexandre Pereira changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from Alexandre Pereira --- (In reply to Nate Graham from comment #3) > A lot has changed since this bug was filed. Is it still reproducible for you > in Plasma 5.24 (the latest LTS version) or 5.25 (the latest version, period)? Indeed ... sorry this escaped my attention, as I did a workaround for this to not happen. I was not able to trigger this anymore, seems fixed! ( hope you don't mind changing directly to resolved/fixed ) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447840] Overview: option to make it show all desktops like GNOME's Activities Overview
https://bugs.kde.org/show_bug.cgi?id=447840 --- Comment #10 from Alexandre Pereira --- (In reply to Nate Graham from comment #9) > Video is fine! Many sorries for failing to do the Video! Btw... easy way to describe the issue: Currently overview lets switch virtual desktop by using the "previous/next virtual desktop". Just let mouse wheel do the same ! So mouse wheel would do the same as the keyboard shortcuts. ( I think mouse wheel could also switch virtual desktops even if mouse on top of windows ) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453545] Konsole resets font size after disconnecting from SSH session
https://bugs.kde.org/show_bug.cgi?id=453545 Alexandre Sicard changed: What|Removed |Added CC||bugs@chezmandre.net --- Comment #2 from Alexandre Sicard --- I am seeing something very similar here, the behaviour is a bit weird and seems related to Konsole profiles. I have the "Default" (read-only) profile, a profile named "Terminal" I don't use much which has some customization, and a third one also named "Terminal" which is my default. Upon disconnecting from most SSH hosts (even if I interrupt the session before entering the password), Konsole switches to the older "Terminal" profile. For some other hosts, it happens upon login instead, before prompting for the password. If I rename my default profile to "Terminal 2", the behaviour changes a bit. For hosts where it happened upon quitting SSH, the problem stops happening. For hosts where it happened upon login, it still happens but reverts back to the correct profile upon logout. KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.14.5 OpenSSH version: 9.0p1 (also tested on 8.6p1) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 454015] New: kio slaves crash if trash is a symlink
https://bugs.kde.org/show_bug.cgi?id=454015
Bug ID: 454015
Summary: kio slaves crash if trash is a symlink
Product: frameworks-kio
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Trash
Assignee: fa...@kde.org
Reporter: pereira.a...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
I use a symlink to another drive as my ~/.local/share/Trash folder.
when not using a symlink, it works fine, but with a symlink, the kio slave
crashes, with the following output in the terminal:
ASSERT: "info.origPath[0] == QLatin1Char('/')" in file
/home/main-builder/pkgwork/src/kio/src/ioslaves/trash/trashimpl.cpp, line 784
27 -- exe=/usr/lib/kf5/kioslave5
18 -- appname=kioslave5
21 -- apppath=/usr/lib/kf5
9 -- signal=6
11 -- pid=450601
12 -- startupid=0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kioslave5 path = /usr/lib/kf5 pid = 450601
KCrash: Arguments: /usr/lib/kf5/kioslave5 trash
local:/run/user/1500/dolphinsyBafu.2.slave-socket
kf.kio.core: "The process for the trash protocol died unexpectedly."
thanks !
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 453603] Window spanning multiple screens temporarily disappear when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=453603 Alexandre Pereira changed: What|Removed |Added Summary|Window spanning multiple|Window spanning multiple |screens slighly disappear |screens temporarily |when switching virtual |disappear when switching |desktops|virtual desktops -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453479] Window spanning multiple screens appears in each screen's Overview effect
https://bugs.kde.org/show_bug.cgi?id=453479 Alexandre Pereira changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453603 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453603] New: Window spanning multiple screens slighly disappear when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=453603 Bug ID: 453603 Summary: Window spanning multiple screens slighly disappear when switching virtual desktops Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: pereira.a...@gmail.com Target Milestone: --- Testing with a window that is half in one monitor and half in another (2 monitors side by side). When switching virtual desktops vertically, the window gets cut in half ( only shows part of the window in one monitor. the rest of the window then just magically reappears after the animation ). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453479] Window in both monitors in multiple monitor setups
https://bugs.kde.org/show_bug.cgi?id=453479 --- Comment #1 from Alexandre Pereira --- Created attachment 148618 --> https://bugs.kde.org/attachment.cgi?id=148618=edit window in middle on overview -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453479] New: Window in both monitors in multiple monitor setups
https://bugs.kde.org/show_bug.cgi?id=453479 Bug ID: 453479 Summary: Window in both monitors in multiple monitor setups Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pereira.a...@gmail.com Target Milestone: --- Created attachment 148617 --> https://bugs.kde.org/attachment.cgi?id=148617=edit window in middle Tested on wayland, haven't tested on X11, but in a multiple monitor setup, if I put a window across both monitors ( ex: half of the window is in one monitor and half in another ) and press an effect like overview, the window gets duplicated in the effect. Also, when switching virtual desktops vertically, the window gets cutted in half ( only shows part of the window in one monitor. the rest of the window then just magicly reappears after the animation ). Sorry for doing the example with screenshots, but I am having troubles with obs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442643] Overview is empty with non-mirrored multi-screen setup on X11
https://bugs.kde.org/show_bug.cgi?id=442643 --- Comment #7 from Alexandre Pereira --- Nate: bug https://bugs.kde.org/show_bug.cgi?id=447833 isn't a duplicate of this. bug: https://bugs.kde.org/show_bug.cgi?id=447833 is about the animation when selecting another virtual desktop when using 2 monitors! ( I just retested on master, and its still there ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453110] folderview to linked activity files does not work
https://bugs.kde.org/show_bug.cgi?id=453110 --- Comment #2 from Alexandre Pereira --- btw I noticed that if I use kf5 git and plasma git, but kde-gear stable version ( especially dolphin and kio/kio-extras ), the bug doesn't happen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453182] New: Latest commit brakes appmenu (global menu) in git version
https://bugs.kde.org/show_bug.cgi?id=453182 Bug ID: 453182 Summary: Latest commit brakes appmenu (global menu) in git version Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: plasma-b...@kde.org Reporter: pereira.a...@gmail.com CC: k...@privat.broulik.de, mvourla...@gmail.com Target Milestone: 1.0 using the git version of kde with this commit: https://invent.kde.org/plasma/plasma-workspace/-/commit/2e056ed6e563f5f0fd7975186db8238adb20b6cf breaks appmenu. The appmenu appears, but clicking on the menu does not make any "submenu appear", except search. In the logs, it appears: plasmashell[71423]: file:///usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/ui/main.qml:117: TypeError: Cannot read property 'visible' of null when compiling plasma-workspace git version with that commit reverted, appmenu works again. thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453110] New: folderview to linked activity files does not work
https://bugs.kde.org/show_bug.cgi?id=453110 Bug ID: 453110 Summary: folderview to linked activity files does not work Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: pereira.a...@gmail.com CC: h...@kde.org Target Milestone: 1.0 SUMMARY Using the stable version of plasma, I have several folder views in various activities that show the files linked with current activity. When switching to the git version of plasma, these folder views show empty. When reverting back to stable version, the files reappear. STEPS TO REPRODUCE 1. add a folder view to the desktop 2. set it to show "files linked to current activity" 3. link a file to current activity through dolphin OBSERVED RESULT the folder view does not show anything EXPECTED RESULT it should appear in the folder view of that activity -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375372] Ability to choose activity to pin apps while they are not running
https://bugs.kde.org/show_bug.cgi?id=375372 --- Comment #9 from Alexandre Pereira --- indeed, just tested it! really cool! thanks for updating this bug report! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 442736] wayland system hangs on lock session
https://bugs.kde.org/show_bug.cgi?id=442736 Alexandre Cavalheiro changed: What|Removed |Added CC||alexandre.cssi...@gmail.com --- Comment #5 from Alexandre Cavalheiro --- (In reply to Alexander Fieroch from comment #4) > After switching to an Nvidia graphic card, the locking works as expected. > There must be a problem in combination with the AMD driver... It must be, because I personally have this issue and I am running an AMD GPU, I also have problems on the lock screen through the default key-bind when I am using wayland, the screen just jitters and takes a while to receive any input. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 451795] New: KRunner not opening in the monitor the cursor is in (XWayland)
https://bugs.kde.org/show_bug.cgi?id=451795 Bug ID: 451795 Summary: KRunner not opening in the monitor the cursor is in (XWayland) Product: krunner Version: 5.24.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: alexandre.cssi...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Whenever I invoke KRunner using the default key-bind (Alt + Space) it opens in my secondary monitor, even if the cursor isn't located in it, while in X11 it opens in whatever monitor my cursor is located. I must note that even if I make it my primary monitor the behaviour is the same, my "primary" monitor is using a DisplayPort while my secondary is using an HDMI port; for the sake of simplicity I'll call the one using the HDMI port as my "secondary" monitor. STEPS TO REPRODUCE 1. Open KRunner OBSERVED RESULT KRunner opens, but in the secondary monitor. EXPECTED RESULT For KRunner to open in the monitor where the cursor is located. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.15 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446118] Update button on installed global theme makes System Settings crash
https://bugs.kde.org/show_bug.cgi?id=446118 --- Comment #3 from Alexandre Leduc --- (In reply to Nate Graham from comment #2) > > I don't have the technical chops to compile libraries with debug symbols on > > Manjaro, sorry. > Can you at least attach an unsymbolicated backtrace, then? At least with > that, there is a chance we can figure out what went wrong and fix it. > Without it, there is no chance. I just tried it again on 5.24.2 and it now works perfectly, so you can close the bug. Thanks. -- You are receiving this mail because: You are watching all bug changes.
