[dolphin] [Bug 417067] Dolphin permissions error
https://bugs.kde.org/show_bug.cgi?id=417067 maxim changed: What|Removed |Added CC|ma...@disroot.org | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 417076] Timeline time scale is not correctly modified when loading or creating project with non-default frame rate
https://bugs.kde.org/show_bug.cgi?id=417076 Jean-Baptiste Mardelle changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #1 from Jean-Baptiste Mardelle --- Thanks for reporting and yes sorry stupid mistake on my side. Should be fixed now, please test -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396537] "Removable devices" kcm should not show Snap mount points
https://bugs.kde.org/show_bug.cgi?id=396537 Méven Car changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/5eb5c9ab7d7eb9c ||d5713e2648abd3fd69ff90230 Version Fixed In||5.18 Resolution|--- |FIXED --- Comment #5 from Méven Car --- Git commit 5eb5c9ab7d7eb9cd5713e2648abd3fd69ff90230 by Méven Car. Committed on 03/02/2020 at 07:39. Pushed by meven into branch 'master'. Solid-device-automounter/kcm: Hide ignored Solid::StorageAccess Summary: FIXED-IN: 5.18 Reviewers: #plasma, broulik, ngraham, ervin Reviewed By: ervin Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D27019 M +10 -4solid-device-automounter/kcm/DeviceModel.cpp https://commits.kde.org/plasma-desktop/5eb5c9ab7d7eb9cd5713e2648abd3fd69ff90230 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417067] Dolphin permissions error
https://bugs.kde.org/show_bug.cgi?id=417067 maxim changed: What|Removed |Added CC||ma...@disroot.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417088] AppImage with QWebEngine does not start
https://bugs.kde.org/show_bug.cgi?id=417088 Maik Qualmann changed: What|Removed |Added Platform|Manjaro |Appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417088] AppImage with QWebEngine does not start
https://bugs.kde.org/show_bug.cgi?id=417088 Maik Qualmann changed: What|Removed |Added Summary|Digikam does not start |AppImage with QWebEngine ||does not start -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417088] Digikam does not start
https://bugs.kde.org/show_bug.cgi?id=417088 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The AppImage is currently using the QWebEngine. This requires a functioning OpenGL support. Which graphics card and drivers do you use? Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375292] Wallpaper changes when mirrored screen is connected
https://bugs.kde.org/show_bug.cgi?id=375292 --- Comment #2 from Salvo "LtWorf" Tomaselli --- No -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 69530] we need to implement precise exception handling
https://bugs.kde.org/show_bug.cgi?id=69530 Tom Hughes changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- CC||t...@compton.nu --- Comment #11 from Tom Hughes --- Undoing KDE robot brain damage. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #3 from Jan Grulich --- It would be nice if you can bisect, because I didn't see such issue here. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 417055] BusyIndicator stresses CPU
https://bugs.kde.org/show_bug.cgi?id=417055 Rinigus changed: What|Removed |Added CC||rinigus@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 417035] Maliit extension for KDE Flatpak Runtime
https://bugs.kde.org/show_bug.cgi?id=417035 Rinigus changed: What|Removed |Added CC||rinigus@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417088] New: Digikam does not start
https://bugs.kde.org/show_bug.cgi?id=417088 Bug ID: 417088 Summary: Digikam does not start Product: digikam Version: 7.0.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: r...@gmx.de Target Milestone: --- SUMMARY digikam-7.0.0-beta3-20200130T131559-x86-64-debug.appimage STEPS TO REPRODUCE 1. every execution -> no start EXPECTED RESULT no start Operating System: Manjaro Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 4.19.99-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7,7 GiB ADDITIONAL INFORMATION Only the appimage does not start. Version 6.4 starts normaly. This is the bug report: ./digikam-7.0.0-beta3-20200130T131559-x86-64-debug.appimage -debug -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 /tmp/.mount_digikaKdjM64/AppRun: Zeile 16: arch: Kommando nicht gefunden. -- Preloading shared libs: unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) unknown: Could not initialize GLX /tmp/.mount_digikaKdjM64/AppRun: Zeile 155: 30422 Abgebrochen (Speicherabzug geschrieben) digikam $@ -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417015] plasmashell crashes in primaryConnectionTypeChanged() after restarting NetworkManager
https://bugs.kde.org/show_bug.cgi?id=417015 --- Comment #5 from Jan Grulich --- Here you go: https://cgit.kde.org/plasma-nm.git/commit/?id=70c5d48f320baf8c84b06fdfe79349104c6b8b4e -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417087] New: Launching chrome will not have indicator
https://bugs.kde.org/show_bug.cgi?id=417087 Bug ID: 417087 Summary: Launching chrome will not have indicator Product: systemsettings Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: proje@outlook.com CC: plasma-b...@kde.org Target Milestone: --- Launching chrome will not have indicator STEPS TO REPRODUCE 1. Set "Global Shortcuts > Application Launchers > Launch Google Chrome > Launch Google Chrome" to "Meta+W" (or any combination) 2. Do the key combination 3. Chrome will launch but without that jumping icon indicator OBSERVED RESULT Chrome will launch but without that jumping icon indicator EXPECTED RESULT Maybe for the first time it to show a jumping icon indicator, so user can understand that its launching. I am not sure about the second or so on times because they are pretty quick. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Pop!_OS 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 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 416100] "Browse Device" causes enegma to open the mounted folder
https://bugs.kde.org/show_bug.cgi?id=416100 tuxutku changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from tuxutku --- After changing default file browser from kde system settings, issue has been resolved, it was set to engrampa somehow -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417086] New: Crash after getting many notifications.
https://bugs.kde.org/show_bug.cgi?id=417086 Bug ID: 417086 Summary: Crash after getting many notifications. Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jodr...@live.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.80) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.4.16-xanmod9 x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was trying to set up a tft server to do a network install, so i was fiddling a lot with Network-Manager. I had Network-Manager setup to share my ethernet as "Shared with other computers" something went wrong and i got lots of notifications about it, some point after i got the crash pop up. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc1cd313800 (LWP 1625))] Thread 22 (Thread 0x7fc15b01f700 (LWP 1768)): #0 0x7fc1cc011588 in () at /usr/lib64/libQt5Core.so.5 #1 0x7fc1cc00fe89 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #2 0x7fc1cc0123c5 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fc1ca571d59 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc1ca572292 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fc1ca57240f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fc1cc011c6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fc1cbfb9bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fc1cbde462e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7fc15b88fe48 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #10 0x7fc1cbde56f8 in () at /usr/lib64/libQt5Core.so.5 #11 0x7fc1cb298f2a in start_thread () at /lib64/libpthread.so.0 #12 0x7fc1ce2e738f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7fc16b3b7700 (LWP 1760)): #0 0x7fc1ce2dcabf in poll () at /lib64/libc.so.6 #1 0x7fc1ca5722ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc1ca57240f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc1cc011c6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc1cbfb9bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc1cbde462e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc1cda680e6 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7fc1cbde56f8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc1cb298f2a in start_thread () at /lib64/libpthread.so.0 #9 0x7fc1ce2e738f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7fc181ffb700 (LWP 1759)): #0 0x7fc1cb29f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc1b7096c2b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fc1b7096b07 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fc1cb298f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7fc1ce2e738f in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7fc1827fc700 (LWP 1757)): #0 0x7fc1cb29f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc1b7096c2b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fc1b7096b07 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fc1cb298f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7fc1ce2e738f in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fc182ffd700 (LWP 1756)): #0 0x7fc1cb29f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc1b7096c2b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fc1b7096b07 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fc1cb298f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7fc1ce2e738f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fc1837fe700 (LWP 1755)): #0 0x7fc1cb29f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc1b7096c2b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fc1b7096b07 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fc1cb298f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7fc1ce2e738f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fc183fff700 (LWP 1754)): #0 0x7fc1cb29f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc1b7096c2b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fc1b7096b07 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fc1cb298f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7fc1ce2e738f in clone () at /lib64/libc.so.6 Thread
[plasma-nm] [Bug 414762] mousearea onClicked dialog popup opens in wrong place unless window is minimized and reopened
https://bugs.kde.org/show_bug.cgi?id=414762 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #13 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 69530] we need to implement precise exception handling
https://bugs.kde.org/show_bug.cgi?id=69530 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #10 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417058] Krita is crashing at start windows 7 64x SP1
https://bugs.kde.org/show_bug.cgi?id=417058 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415860] Not updating currencies online
https://bugs.kde.org/show_bug.cgi?id=415860 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 411691] Only happens in Opensuse 15.1 in most games the cards will only autodrop a few, and then it stops., often crashes when Yukon is selected
https://bugs.kde.org/show_bug.cgi?id=411691 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #13 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 409951] Missing component KDev::Tests required for Umbrello
https://bugs.kde.org/show_bug.cgi?id=409951 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 377548] lokalize gives wrong spelling errors after colon :
https://bugs.kde.org/show_bug.cgi?id=377548 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416076] Can't open or save projects
https://bugs.kde.org/show_bug.cgi?id=416076 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369080] Git master:2016-09-19:Project profile management issues, and idea for massive display speed improvement
https://bugs.kde.org/show_bug.cgi?id=369080
Evert Vorster changed:
What|Removed |Added
Ever confirmed|1 |0
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #10 from Evert Vorster ---
Hi there!
I am getting a build error when trying to build the master branch of kdenlive:
---snip-
[ 3%] Building C object
src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/mediactrl.c.o
/data/OS/aur/kdenlive-testing-git/src/kdenlive/src/lib/external/media_ctrl/mediactrl.c:
In function 'find_first_device':
/data/OS/aur/kdenlive-testing-git/src/kdenlive/src/lib/external/media_ctrl/mediactrl.c:355:5:
error: 'for' loop initial declarations are only allowed in C99 or C11 mode
355 | for (int i = 0; i < 32; i++) {
| ^~~
/data/OS/aur/kdenlive-testing-git/src/kdenlive/src/lib/external/media_ctrl/mediactrl.c:355:5:
note: use option '-std=c99', '-std=gnu99', '-std=c11' or '-std=gnu11' to
compile your code
make[2]: ***
[src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/build.make:76:
src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/mediactrl.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:2267:
src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
Error making: kdenlive-testing-git
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 417060] Crash occurs after I click close window button
https://bugs.kde.org/show_bug.cgi?id=417060 --- Comment #2 from Gilbert Row --- (In reply to Ahab Greybeard from comment #1) > Is this with the 4.2.8 appimage? If not, can you try it to see if that works? Hello. Thanks for your reply. Currently, an rpm version from Tumbleweed's repos installed on my machine. I've downloaded the appimage version, and it works just fine (does not crash) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398153] Apparent false positive of uninitialised values in libjpeg-turbo
https://bugs.kde.org/show_bug.cgi?id=398153 --- Comment #4 from n...@deditus.de --- Created attachment 125639 --> https://bugs.kde.org/attachment.cgi?id=125639=edit Another image reproducing the problem I've uploaded another (all-black) image reproducing the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[KTechLab] [Bug 417085] New: ktechlab-0.40.1 fails to build with gcc10
https://bugs.kde.org/show_bug.cgi?id=417085 Bug ID: 417085 Summary: ktechlab-0.40.1 fails to build with gcc10 Product: KTechLab Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: zoltan.pad...@gmail.com Reporter: rosset.fil...@gmail.com CC: jul...@svg4all.de Target Milestone: --- ktechlab-0.40.1 fails to build with gcc10 /builddir/build/BUILD/ktechlab-0.40.1/src/gui/contexthelp.h:14:10: fatal error: ui_contexthelpwidget.h: No such file or directory14 | #include Full logs here: https://kojipkgs.fedoraproject.org//work/tasks/9925/41319925/build.log -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398153] Apparent false positive of uninitialised values in libjpeg-turbo
https://bugs.kde.org/show_bug.cgi?id=398153 --- Comment #3 from n...@deditus.de --- Created attachment 125638 --> https://bugs.kde.org/attachment.cgi?id=125638=edit square8x8.jpg - example input Copying the example input from the linked dropbox into an issue tracker for longevity. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 417084] New: I would like to paste HEX codes.
https://bugs.kde.org/show_bug.cgi?id=417084 Bug ID: 417084 Summary: I would like to paste HEX codes. Product: okteta Version: 0.26.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kosse...@kde.org Reporter: aalexand...@gmail.com Target Milestone: --- I have a string with hex codes, like "FF 00 AA BB" etc, and I would like to just copy paste it to populate a file. For now, if I paste it, they are put as symbols, not hex codes. Or I just couldn't find how to paste them right. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 264936] vectorization might lead to 'false positives'
https://bugs.kde.org/show_bug.cgi?id=264936 n...@deditus.de changed: What|Removed |Added CC||n...@deditus.de -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 417083] New: Crash when unplugging second monitor in Wayland
https://bugs.kde.org/show_bug.cgi?id=417083 Bug ID: 417083 Summary: Crash when unplugging second monitor in Wayland Product: Powerdevil Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ck_min...@hotmail.com Target Milestone: --- Application: org_kde_powerdevil (2.0.0) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.14-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I am unplugging my HDMI cable before the crash happen. And prior to that, I did put my laptop to sleep. -- Backtrace: Application: KDE Power Management System (org_kde_powerdevil), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc8e4ec8c80 (LWP 2868))] Thread 7 (Thread 0x7fc8c7e53700 (LWP 18642)): #0 0x7fc8e880b4ec in read () at /lib64/libc.so.6 #1 0x7fc8cbfa40f1 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-13.0.so #2 0x7fc8e0081a0e in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0 #3 0x7fc8e00824b0 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7fc8e0082570 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7fc8e0090439 in () at /usr/lib64/libpulse.so.0 #6 0x7fc8cbfd1c78 in () at /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7fc8e6910f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7fc8e881a38f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fc8e08da700 (LWP 2949)): #0 0x7fc8e880b4ec in read () at /lib64/libc.so.6 #1 0x7fc8e5e081df in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc8e5dc0e47 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc8e5dc1292 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc8e5dc140f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fc8e749fbdb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fc8e7447d5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fc8e727363e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fc8e7274708 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fc8e6910f2a in start_thread () at /lib64/libpthread.so.0 #10 0x7fc8e881a38f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc8e10db700 (LWP 2948)): #0 0x7fc8e880fabf in poll () at /lib64/libc.so.6 #1 0x7fc8e5dc12ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc8e5dc140f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc8e749fbdb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc8e7447d5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc8e727363e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc8e7274708 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fc8e6910f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7fc8e881a38f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fc8e1baa700 (LWP 2912)): #0 0x7fc8e880b4ec in read () at /lib64/libc.so.6 #1 0x7fc8e5e081df in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc8e5dc0e47 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc8e5dc1292 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc8e5dc1653 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #5 0x7fc8e257ec96 in () at /usr/lib64/libgio-2.0.so.0 #6 0x7fc8e5dea18e in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fc8e6910f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7fc8e881a38f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fc8e23ab700 (LWP 2911)): #0 0x7fc8e5dbdf99 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7fc8e5dbf5d4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc8e5dc0c5f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc8e5dc1292 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc8e5dc140f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fc8e5dc1461 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7fc8e5dea18e in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fc8e6910f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7fc8e881a38f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fc8e2efc700 (LWP 2902)): #0 0x7fc8e5dbf4e7 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7fc8e5dc0c5f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc8e5dc1292 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc8e5dc140f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc8e749fbdb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5
[plasmashell] [Bug 417082] Files on desktop can open multiple context menus at once on Wayland
https://bugs.kde.org/show_bug.cgi?id=417082 --- Comment #1 from Ash --- Created attachment 125637 --> https://bugs.kde.org/attachment.cgi?id=125637=edit Screenshot showing context menu with window decorations after clicking with a focused window -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417082] New: Files on desktop can open multiple context menus at once on Wayland
https://bugs.kde.org/show_bug.cgi?id=417082 Bug ID: 417082 Summary: Files on desktop can open multiple context menus at once on Wayland Product: plasmashell Version: 5.17.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: a...@heyquark.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 125636 --> https://bugs.kde.org/attachment.cgi?id=125636=edit Screenshot showing multiple context menus open after right-clicking on desktop icon SUMMARY On Wayland, when right-clicking files on the desktop to open a context menu, multiple context menus appear, with only the topmost one responding to interaction. If a window has focus, the first menu appears in the top-left with window decorations (similar to https://bugs.kde.org/show_bug.cgi?id=387597 ). I suspect these are both the same underlying issue, so I'm reporting them together - happy to change that! STEPS TO REPRODUCE 1. Have some files in ~/Desktop, and have the desktop layout set to "Folder View" 2. With all applications minimised or unfocused, right-click on a desktop icon 3. Right-click on a still-exposed part of the icon (or another icon entirely) 4. Right-click on an empty portion of the desktop or focus a window to dismiss any context menus. 5. With a window focused, right-click on a desktop icon OBSERVED RESULT With no focused windows: Multiple context menus appear, overlapping. Only the topmost/most recent one can be interacted with. Actions that would usually close a context menu (left-clicking on the desktop or icons) are ineffective, and choosing an item in the menu only dismisses one at a time. With a focused window: The window loses focus, and a context menu appears in the top-left corner with window decorations, like in https://bugs.kde.org/show_bug.cgi?id=387597 . Further context menus can be opened by right-clicking icons, but these do not appear with window decorations. EXPECTED RESULT The second right-click anywhere on the desktop or icons closes the active context menu, instead of opening another one - this is the behaviour of empty desktop space. In the case where the menu opens with window decorations, it should instead appear at the position of the mouse, without decorations. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon User 5.17 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 Also reproduced on Linux/KDE Plasma: Arch Linux (rolling, up to date 2020-02-03) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Left-clicking on the desktop while one of these rouge context menus is open causes a "Delete" option to appear under "Move to Wastebin". Since a file isn't selected in this state, I'm not really game to see what it does. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416226] Logging in/out and restarting with external monitor as primary makes whole desktop act as secondary screen instead of primary
https://bugs.kde.org/show_bug.cgi?id=416226 --- Comment #3 from Jan Keith Darunday --- (In reply to Nate Graham from comment #2) > Any chance you could try this again in the Plasma 5.18 beta? See > https://www.reddit.com/r/kde/comments/epkjlo/ > plasma_518_lts_beta_more_convenient_and_with_long/fejwivz/ > ?utm_source=share_medium=web2x Hi, I just tried this with Plasma 5.17.90 with my existing user and with a newly-created user, the same issue occurs. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 394227] [x86] False negative "uninitialised value" report due to not recognizing simd registers clear by pcmp*
https://bugs.kde.org/show_bug.cgi?id=394227 --- Comment #5 from n...@deditus.de --- Also related: https://bugs.kde.org/show_bug.cgi?id=398153 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398153] Apparent false positive of uninitialised values in libjpeg-turbo
https://bugs.kde.org/show_bug.cgi?id=398153 --- Comment #2 from n...@deditus.de --- Related: https://bugs.kde.org/show_bug.cgi?id=394227 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 394227] [x86] False negative "uninitialised value" report due to not recognizing simd registers clear by pcmp*
https://bugs.kde.org/show_bug.cgi?id=394227 --- Comment #4 from n...@deditus.de --- The specific case of `pcmpeqw xmm0, xmm0` is claimed to be fixed in issue https://bugs.kde.org/show_bug.cgi?id=290006. Yet, there are still issues with valgrind on libjpeg-turbo (see https://github.com/libjpeg-turbo/libjpeg-turbo/issues/277#issuecomment-581198382), suggesting that either the fix is incomplete or that other instructions are involved. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 394227] [x86] False negative "uninitialised value" report due to not recognizing simd registers clear by pcmp*
https://bugs.kde.org/show_bug.cgi?id=394227 n...@deditus.de changed: What|Removed |Added CC||n...@deditus.de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398153] Apparent false positive of uninitialised values in libjpeg-turbo
https://bugs.kde.org/show_bug.cgi?id=398153 n...@deditus.de changed: What|Removed |Added CC||n...@deditus.de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 290006] memcheck doesn't mark %xmm as initialized after "pcmpeqw %xmm %xmm"
https://bugs.kde.org/show_bug.cgi?id=290006 n...@deditus.de changed: What|Removed |Added CC||n...@deditus.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413762] GTK2 themes are not working at all and the previews aren't working either for only gtk2
https://bugs.kde.org/show_bug.cgi?id=413762 --- Comment #12 from b2.t...@gmx.com --- The problem for me was that the file "~/.gtkrc-2.0-kde4" was not updated after changing the theme in the setting panel. Maybe check if this was the problem for you too. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 417039] Elisa doesnt recognize some files regardless of name and format
https://bugs.kde.org/show_bug.cgi?id=417039 --- Comment #2 from qik0...@gmail.com --- (In reply to Alexander Stippich from comment #1) > Do these files have their title tagged in their metadata? Some of them, doesnt seem to affect it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417081] Weather widget selects the first city result no matter what you choose.
https://bugs.kde.org/show_bug.cgi?id=417081 Doug B changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Doug B --- Oh, wait. I think you guys fixed this super recently! https://pointieststick.com/2020/02/01/this-week-in-kde-plasma-5-18-is-nigh/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417081] New: Weather widget selects the first city result no matter what you choose.
https://bugs.kde.org/show_bug.cgi?id=417081 Bug ID: 417081 Summary: Weather widget selects the first city result no matter what you choose. Product: plasmashell Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: w...@dougie.io Target Milestone: 1.0 Created attachment 125635 --> https://bugs.kde.org/attachment.cgi?id=125635=edit KDE Weather bug SUMMARY Let's say you search for your city of "Somewhereville" in KDE's Weather Report system tray. You'll be presented with search results. Let's say these are the cities you are shown. - Somewhereville, Earth - Somewhereville, Mars - Somewhereville, Pluto You select the Pluto derivative and press ok. However you will notice that the report still selects the first option. "Somewhereville, Earth" Check out the wemb video for a demo. STEPS TO REPRODUCE 1. Right click weather icon in system tray, click "Configure Weather Report". 2. Click the Choose button, select Wetter.com, and search a location like "Kansas". 3. Select any result other than the first item in the list. OBSERVED RESULT Despite what you select, the first item in the selection list is chosen. EXPECTED RESULT The selected location to be chosen. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-29-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-9300H CPU @ 2.40GHz Memory: 7.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417057] Synched SDDM theme struck to a previous colourscheme
https://bugs.kde.org/show_bug.cgi?id=417057 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com --- Comment #2 from Filip Fila --- I thought we've been deleting the cache when resetting the settings but turns out I was wrong. Made a patch: https://phabricator.kde.org/D27113 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 417080] New: Add support for huge pages
https://bugs.kde.org/show_bug.cgi?id=417080 Bug ID: 417080 Summary: Add support for huge pages Product: ksysguard Version: 5.16.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andy...@mail.ru Target Milestone: --- Created attachment 125634 --> https://bugs.kde.org/attachment.cgi?id=125634=edit Example of a /proc//status file with huge pages Currently, the Memory column for a process in KSysGuard does not include memory allocated in anonymous huge pages. There seems to be no way to see how much RAM, including huge pages, the process is using. Note that Virtual Size does not work as it includes all mapped address space of the process, not necessarily the amount of RAM used. Since huge pages cannot be swapped out to a page file (as of the time of this writing and to my knowledge), it seems reasonable to include them into the Memory column value. If not, at least a separate column would be useful. For an example, I'm attaching /proc//status of an ffmpeg process, which uses huge pages for most of its allocations (through a custom memory allocator). For this process, KSysGuard shows 64300 K in its Memory column, while there is actually 1606 MiB more allocated in huge pages. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 290742] kmix is crashing after multiple volume changes
https://bugs.kde.org/show_bug.cgi?id=290742 jahira8...@gmail.com changed: What|Removed |Added CC||jahira8...@gmail.com Attachment #70717|0 |1 is patch|| Attachment #70717|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 416354] button to close GHNS window without label
https://bugs.kde.org/show_bug.cgi?id=416354 qrest changed: What|Removed |Added CC||qr...@protonmail.com --- Comment #3 from qrest --- Created attachment 125633 --> https://bugs.kde.org/attachment.cgi?id=125633=edit Same on KDE neon testing -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 416275] Activating Application Menu Bar Removes Windows Controls in Firefox
https://bugs.kde.org/show_bug.cgi?id=416275 --- Comment #5 from qrest --- Updated my system today and the window controls appear now as they should. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 417079] New: Device name is missing
https://bugs.kde.org/show_bug.cgi?id=417079 Bug ID: 417079 Summary: Device name is missing Product: plasma-pa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: christo...@krop.fr CC: plasma-b...@kde.org Target Milestone: --- Created attachment 125632 --> https://bugs.kde.org/attachment.cgi?id=125632=edit new tray menu Using master. With the recent change, the device name are not informative. See the attached screenshot. "Analog output" and "Line Out" is not informative if you don't know which card provides them. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 417079] Device name is missing
https://bugs.kde.org/show_bug.cgi?id=417079 Christophe Giboudeaux changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #10 from andydecle...@gmail.com --- (In reply to Michail Vourlakos from comment #9) > I won't add any option for this. On the other hand if the Needs Attention > never stops then this is a bug, and I would need steps to reproduce because > in my system works just fine, after 8.5 secs the in question dock becomes > hidden again. Ok, if you have already tried the originally posted reproduction steps exactly and it didn't reproduce the problem, I will upload a configuration and layout when I'm back at a computer. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 417078] Updates not working
https://bugs.kde.org/show_bug.cgi?id=417078 --- Comment #1 from benji.ma...@gmail.com --- Created attachment 125631 --> https://bugs.kde.org/attachment.cgi?id=125631=edit screenshot just before error message appears -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 417078] Updates not working
https://bugs.kde.org/show_bug.cgi?id=417078 benji.ma...@gmail.com changed: What|Removed |Added CC||benji.ma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 417078] New: Updates not working
https://bugs.kde.org/show_bug.cgi?id=417078 Bug ID: 417078 Summary: Updates not working Product: Discover Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: benji.ma...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 125630 --> https://bugs.kde.org/attachment.cgi?id=125630=edit screen of window with error message SUMMARY In Discover, Updates tab lists several packages that need to be updated. Whether updating all or each package individually, the update fails with message "Aborted due to failure". STEPS TO REPRODUCE 1. Software center > Updates > 2. Update all, OR 3. Update selected OBSERVED RESULT Error message appears "Aborted due to failure" EXPECTED RESULT Package should update SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 417077] Single Click not working/available.
https://bugs.kde.org/show_bug.cgi?id=417077 --- Comment #1 from Yichao Yu --- You need to be much more specific about what you are talking about. A few points to consider. 1. QtCurve is a theme/style. While it is not completely unrelated to clicking, it is not itself something that you click. Reporting that you have to double click on QtCurve doesn't really make that much sense. 2. I'm 99.9% sure you don't have to "double click on everything". As in, I'm sure single click does something in some cases. It may just not be what you want it to do. 3. In any case, you should mention what program(s) you are talking about and what you are trying to do. I just looked at my system setting for input device/mouse. It doesn't seem to have the single click/double click setting that used to be there for at least KDE4. It's not a setting I need but if that's the option you are talking about you have reported it to the wrong component. I'm too lazy to figure out what would be the right component but `systemsettings` would be a good start. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417060] Crash occurs after I click close window button
https://bugs.kde.org/show_bug.cgi?id=417060 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- Is this with the 4.2.8 appimage? If not, can you try it to see if that works? -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 417077] New: Single Click not working/available.
https://bugs.kde.org/show_bug.cgi?id=417077 Bug ID: 417077 Summary: Single Click not working/available. Product: QtCurve Version: 1.9 Platform: Debian stable OS: Linux Status: REPORTED Severity: task Priority: NOR Component: qt5 Assignee: yyc1...@gmail.com Reporter: xenoida...@gmail.com CC: h...@kde.org Target Milestone: --- Having to Double Click on everything is noisy and annoying! KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416894] krita full screen in wrong monitor
https://bugs.kde.org/show_bug.cgi?id=416894 Boudewijn Rempt changed: What|Removed |Added Platform|Windows CE |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416893] zooming with windows ink in windows 10 is broken
https://bugs.kde.org/show_bug.cgi?id=416893 Boudewijn Rempt changed: What|Removed |Added Platform|Windows CE |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 417076] New: Timeline time scale is not correctly modified when loading or creating project with non-default frame rate
https://bugs.kde.org/show_bug.cgi?id=417076 Bug ID: 417076 Summary: Timeline time scale is not correctly modified when loading or creating project with non-default frame rate Product: kdenlive Version: git-master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: alridd...@googlemail.com Target Milestone: --- Created attachment 125629 --> https://bugs.kde.org/attachment.cgi?id=125629=edit Screenshot showing a 25fps project, but the timeline scale has 50fps. SUMMARY The default project profile for my kdenlive config has 50fps. When I create a New project with a profile of 25fps, or load a 25fps project from disc, the time scale at the top of the timeline is not correctly updated for the new project, and still shows 50fps. By binary search of the recent commits, I have found this this issue was introduced in the following commit: f9491a9e39830ff02f1da94d80f09c015fc3 "Attempt to fix crash after profile change" STEPS TO REPRODUCE 1. Load kdenlive with its default configuration. (e.g. 50fps) 2. Create a new empty project with a different fps (e.g. 25fps) 3. Manually set the timeline cursor to a non-zero position on the timeline. OBSERVED RESULT The numerical cursor position below the monitor does not match the position on the timeline scale, and the numbers on the timeline scale have the incorrect number of frames per second. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 31, Linux 5.4.12 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION The attached screenshot is a new empty 25fps project created after kdenlive was started with 50fps in the default profile. The highlighted title shows the correct project profile fps, and the indicator below the project monitor shows the correct position for the cursor of 00:05:00. The highlighted cursor position on the timeline scale shows it is incorrectly at 00:02:25, and also that the scale has 50 frames per second. i.e. The position of the cursor is the correct number of frames from the start, but the wrong number of seconds. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417075] pwritev(vector[...]) suppression ignored
https://bugs.kde.org/show_bug.cgi?id=417075 --- Comment #1 from Leonid Yuriev --- Actual memcheck version information: ==151028== Memcheck, a memory error detector ==151028== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==151028== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info $ dnf list valgrind Last metadata expiration check: 0:01:18 ago on Mon Feb 3 00:01:22 2020. Installed Packages valgrind.x86_641:3.15.0-11.fc31 @fedora -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417061] Startup Brush only making Dots
https://bugs.kde.org/show_bug.cgi?id=417061 Ahab Greybeard changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||ahab.greybe...@hotmail.co.u ||k Resolution|--- |WAITINGFORINFO --- Comment #1 from Ahab Greybeard --- When you say 'Startup Brush'. do you mean the first brush you choose? What about other brushes? Is this true for any brush? What about the brush called b)_Basic-1? Which tablet are you using? Can you read this and see if it helps you to fix or understand the problem: https://docs.krita.org/en/user_manual/drawing_tablets.html?highlight=tablet#where-it-can-go-wrong-windows Can you post the system information from Help -> Show system information ? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417075] New: pwritev(vector[...]) suppression ignored
https://bugs.kde.org/show_bug.cgi?id=417075
Bug ID: 417075
Summary: pwritev(vector[...]) suppression ignored
Product: valgrind
Version: 3.15 SVN
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: l...@yuriev.ru
Target Milestone: ---
SUMMARY
memcheck 3.13 (ubuntu) works fine, but memcheck 3.15 (fedora 31) don't handle
suppression for pwritev syscall.
STEPS TO REPRODUCE
1. git clone https://github.com/leo-yuriev/libmdbx.git
2. make -C libmdbx memcheck
3. cat libmdbx/valgrind-*.log | less
OBSERVED RESULT
Error report:
==149931== Syscall param pwritev(vector[0]) points to uninitialised byte(s)
==149931==at 0x4D2F5CD: pwritev (in /usr/lib64/libc-2.30.so)
==149931==by 0x486B47D: mdbx_pwritev (osal.c:790)
==149931==by 0x486910E: mdbx_flush_iov (core.c:7507)
==149931==by 0x486910E: mdbx_page_flush (core.c:7566)
EXPECTED RESULT
Suppression works as expected.
SOFTWARE/OS VERSIONS
$ lsb_release -a
LSB Version::core-4.1-amd64:core-4.1-noarch
Distributor ID: Fedora
Description:Fedora release 31 (Thirty One)
Release:31
Codename: ThirtyOne
ADDITIONAL INFORMATION
Suppression:
{
pwrite-page-flush
Memcheck:Param
pwritev(vector[...])
fun:pwritev
...
fun:mdbx_page_flush
}
https://raw.githubusercontent.com/leo-yuriev/libmdbx/master/test/valgrind_suppress.txt
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-pa] [Bug 417074] Broken applet UI with long device names
https://bugs.kde.org/show_bug.cgi?id=417074 Christophe Giboudeaux changed: What|Removed |Added CC||gv...@protonmail.com, ||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 417074] New: Broken applet UI with long device names
https://bugs.kde.org/show_bug.cgi?id=417074 Bug ID: 417074 Summary: Broken applet UI with long device names Product: plasma-pa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: christo...@krop.fr CC: plasma-b...@kde.org Target Milestone: --- Created attachment 125628 --> https://bugs.kde.org/attachment.cgi?id=125628=edit plasma-pa with long device name Using master. Check the screenshot. The UI is broken when a device name doesn't fit the tray window width. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #9 from Michail Vourlakos --- I won't add any option for this. On the other hand if the Needs Attention never stops then this is a bug, and I would need steps to reproduce because in my system works just fine, after 8.5 secs the in question dock becomes hidden again. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 --- Comment #2 from Allan Sandfeld --- Note I am using Qt 5.14.1 if that makes any difference -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 --- Comment #1 from Allan Sandfeld --- Reverting to the v5.17.5 git tag, solved the issue for me. If you want me too I could probably bisect which commit caused the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 Allan Sandfeld changed: What|Removed |Added Version|5.17.5 |5.17.90 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] New: plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 Bug ID: 417073 Summary: plasma-nm prevents most other systray applets Product: plasma-nm Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: k...@carewolf.com Target Milestone: --- With the lastest update of plasma I found most of the systray icons absent from the systray. I traced it down to plasma-nm, and uninstalling the plasma-nm applet restores the rest of the applet. During launch or relaunch of plasmashell, all the systray apps an be seen shortly before plasma-nm starts and nukes the rest. Unfortunately there is nothing in the log that suggest what is going on. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415508] Scrollbar set to 'hidden' reappears when scrolling twice via touchpad
https://bugs.kde.org/show_bug.cgi?id=415508 --- Comment #9 from Ferdinand B --- Added phabricator revision for this patch: https://phabricator.kde.org/D27110 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #8 from andydecle...@gmail.com --- (In reply to Michail Vourlakos from comment #1) > The > fact that an application has set that flag it means that wants the > attention. Further, the current behavior can *obscure* the window that wants attention, as is demonstrated in the originally attached video. This bugzilla instance fails at properly sharing the attachment, but if you download it, you can see the video, which is not "corrupt" as bugzilla claims. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 415241] Trouble opening an MTP device
https://bugs.kde.org/show_bug.cgi?id=415241 Said Bakr changed: What|Removed |Added CC||said@gmail.com --- Comment #1 from Said Bakr --- I have another issues with connecting my computer operated by Kubuntu 18.04 to my Android device, Redmi Note7, while the process is not smooth. The file manager able to access files on the device, but trying to browse files using the open file dialog of any application such as web browsers e.g. Firefox, Vivaldi, etc. is not succeeded. I posted a question on Ask Ubuntu that describes the issue at the following URL: https://askubuntu.com/questions/1207350/could-not-able-to-find-android-device-photo-through-applications-open-file -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 384515] [ksysguardd]: Internal buffer too small to read '/proc/cpuinfo'
https://bugs.kde.org/show_bug.cgi?id=384515 Benjamin Xiao changed: What|Removed |Added CC||ben.r.x...@gmail.com Platform|openSUSE RPMs |unspecified --- Comment #5 from Benjamin Xiao --- This happens on Arch Linux as well with the latest KDE packages. No info is shown in the System Load Plasma widget and 'Internal buffer too small to read '/proc/cpuinfo' is shown in journalctl. This didn't used to happen on my Ryzen 1800x but is now happening on my Ryzen 3900x. The increase in the number of cores is probably making /proc/cpuinfo pretty big. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415508] Scrollbar set to 'hidden' reappears when scrolling twice via touchpad
https://bugs.kde.org/show_bug.cgi?id=415508 --- Comment #8 from Ferdinand B --- Created attachment 125627 --> https://bugs.kde.org/attachment.cgi?id=125627=edit QScrollBar diff between 5.13.2 and 5.14.0 I also attached a diff showing what changed in QScrollBar from Qt 5.13.2 to 5.14.0, which is what I suspect caused this bug to appear. I have tested latest konsole master with 5.13.2, 5.14.0, and 5.14.1, and the bug appears in both 5.14.0 and 5.14.1, but not in 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415508] Scrollbar set to 'hidden' reappears when scrolling twice via touchpad
https://bugs.kde.org/show_bug.cgi?id=415508 Ferdinand B changed: What|Removed |Added CC||theferdi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415508] Scrollbar set to 'hidden' reappears when scrolling twice via touchpad
https://bugs.kde.org/show_bug.cgi?id=415508 --- Comment #7 from Ferdinand B --- Created attachment 125626 --> https://bugs.kde.org/attachment.cgi?id=125626=edit Workaround Patch I attached a patch that works around the issue by reapplying the scrollbar state (_scrollBar->setHidden(true)) every time an event is propagated to the scroll bar. It's not beautiful, but it works, and should be a NOP in cases where this bug does not occur. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 417072] New: Kontact crashes again for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=417072 Bug ID: 417072 Summary: Kontact crashes again for no apparent reason Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-29-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I was away from machine, when I returned kontacht had crashed. I couldn't find out wether it is a duplicate from bug 416307 and/or bug 415997 The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x in () #7 0x7f997ad3e8ea in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f997ad3e9fa in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f997ad3ea29 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f997d1b5779 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 Possible duplicates by query: bug 416986, bug 416900, bug 416816, bug 416730, bug 416721. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 417072] Kontact crashes again for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=417072 --- Comment #1 from Andreas Hencke --- Created attachment 125625 --> https://bugs.kde.org/attachment.cgi?id=125625=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 172615] Gimp 2.6 utility windows do not stay on top of the main window
https://bugs.kde.org/show_bug.cgi?id=172615 David Edmundson changed: What|Removed |Added Status|REOPENED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #30 from David Edmundson --- If you can explain where we explicitly break the spec I will reopen this. Thomas above explains that we don't. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 417071] Akonadi is constantly writing to disk.
https://bugs.kde.org/show_bug.cgi?id=417071 Hakan Bayindir changed: What|Removed |Added CC||ha...@bayindir.org -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 417070] KRunner makes excessive writes during searching.
https://bugs.kde.org/show_bug.cgi?id=417070 Hakan Bayindir changed: What|Removed |Added CC||ha...@bayindir.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 417071] New: Akonadi is constantly writing to disk.
https://bugs.kde.org/show_bug.cgi?id=417071 Bug ID: 417071 Summary: Akonadi is constantly writing to disk. Product: Akonadi Version: 5.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ha...@bayindir.org Target Milestone: --- Created attachment 125624 --> https://bugs.kde.org/attachment.cgi?id=125624=edit One day of iotop statistics, running in cumulative mode, sorted by disk write. SUMMARY Akonadi is constantly writing to disk and creating a lot of cumulative disk I/O after some time. STEPS TO REPRODUCE 1. Run akonadi. 2. Leave it turned on for the day. 3. Enable indexer for better results. OBSERVED RESULT ~3.5GB written to the disk after 10 hours of operation. EXPECTED RESULT A milder disk write pattern. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Testing. (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION KMail is also managing a single IMAP account via Akonadi. Continually writing small amounts of data wears SSDs pretty fast. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 417070] New: KRunner makes excessive writes during searching.
https://bugs.kde.org/show_bug.cgi?id=417070 Bug ID: 417070 Summary: KRunner makes excessive writes during searching. Product: krunner Version: 5.14.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: ha...@bayindir.org Target Milestone: --- Created attachment 125623 --> https://bugs.kde.org/attachment.cgi?id=125623=edit One day of iotop statistics, running in cumulative mode, sorted by disk write. SUMMARY KRunner can write ~2.2GB of data to disk in a couple of searches. STEPS TO REPRODUCE 1. Call KRunner with its shortcut. 2. Write something. OBSERVED RESULT KRunner makes a lot of disk calls and writes a lot of data, genrally to .cache folder. This wears down SSD disks pretty fast. EXPECTED RESULT A more milder disk access pattern (mostly reads, much less write) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Testing. (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION System I/O is monitored via fatrace and iotop. When running fatrace with -cC krunner --filter=CWD in the home directory of the user, the effects of triggering a search is becomes very visible. Keeping iotop open for a single day in accumulation mode and ordered by disk write reveals pretty shocking write statistics for a couple of KDE processes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417038] Fails to start session after logging out if there is any process of this user
https://bugs.kde.org/show_bug.cgi?id=417038 --- Comment #3 from Pyroman --- (In reply to Pyroman from comment #2) > After kill -u $USER s/kill/pkill/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417038] Fails to start session after logging out if there is any process of this user
https://bugs.kde.org/show_bug.cgi?id=417038 --- Comment #2 from Pyroman --- (In reply to David Edmundson from comment #1) > Can I have a "ps aux" after you've logged out. > > Something is dangling, and you've explicitly turned off the part that cleans > up. After logging out: https://pastebin.com/XxwnwfS0 After logging in failure: https://pastebin.com/xKsD9qWM After kill -u $USER: https://pastebin.com/SdWuPMAB (still cannot log in, have to logout from TTY2) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 --- Comment #26 from Alexander Kernozhitsky --- Finally, after some hours of debugging and reading the logs I reached the reason of this bug. It's triggered when: - KDirWatch uses inotify as a backend - the watched directory contains a symlink as one of its parent. For example, /d is a symlink to /media/data, and our current directory in Dolphin is something like /d/1/2/3 - the directory is added and then removed: $ while true ; do mkdir abc ; sleep 1 ; rmdir abc ; sleep 1 ; done The problem is that inotify_add_watch reuses the file descriptor if the directory is already watched. When the directory and the another path to it with a symlink (e. g. /d/1/2/3 and /media/data/1/2/3) are watched, inotify API still reuses the file descriptor. But KDirWatch intrinsically considers these path different, so uses different entries for them. The mapping between file descriptors and names is kept in QHash m_inotify_wd_to_entry, so the previous entry here is overwritten. Moreover, when one of these path stops being watched, the file descriptor is freed and the map entry is removed, so the other path doesn't receive events. I don't know how to fix this in a simple way (maybe use canonical paths inside KDirWatch?) Also note that it's the only one scenario in which the file system updates are not delivered, there may be other ways to break it and the separate reasons why this happens. Any missing update in KDirWatch can be the reason. As I stated in the previous message, KDirWatch can use other methods as default (FAM, inotify, QFSWatch and Stat). FAM seems to affect performance. Stat will poll the filesystem each 0.5 seconds, which is not the most efficient way. I don't know anything about QFSWatch and why it's not use as a default. Some comments in the code suggest that it lacks some functionality. As I workaround, I set the environment variable: KDIRWATCH_METHOD=QFSWatch -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412272] Gyroscope/accelerometer support in presenter or control plugin
https://bugs.kde.org/show_bug.cgi?id=412272 daniel-other+kde...@dadosch.de changed: What|Removed |Added CC||daniel-other+kdebug@dadosch ||.de --- Comment #1 from daniel-other+kde...@dadosch.de --- In the presenter plugin, this is currently implemented. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 417026] Battery monitor in system tray with missing translation
https://bugs.kde.org/show_bug.cgi?id=417026 --- Comment #3 from Burkhard Lück --- Kapazität wird schon für die Nennkapazität eines neuen Akkus als Übersetzung benutzt, mit State_of_health wird aktuelle Kapazität als Prozenzwert der Nennkapazität bezeichnet. Vielleicht Kapazitätsminderung o. ä. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 403500] Add a "laser pointer" in presentation mode
https://bugs.kde.org/show_bug.cgi?id=403500 daniel-other+kde...@dadosch.de changed: What|Removed |Added Status|REPORTED|RESOLVED CC||daniel-other+kdebug@dadosch ||.de Resolution|--- |FIXED --- Comment #2 from daniel-other+kde...@dadosch.de --- This has been added in 38caa1831f3425a9cf1cf3f037297bd4b066364a https://github.com/KDE/kdeconnect-android/commit/38caa1831f3425a9cf1cf3f037297bd4b066364a -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417069] New: tab of a samba share has the "unknown" icon
https://bugs.kde.org/show_bug.cgi?id=417069 Bug ID: 417069 Summary: tab of a samba share has the "unknown" icon Product: dolphin Version: 19.12.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. open Dolphin 2. open a samba share in a new tab 3. OBSERVED RESULT as we can see in the attached screenshot, the tab of the samba share has the "unknown" icon. EXPECTED RESULT I'm not sure. Maybe a folder icon, or an specific icon to represent a samba share and other kinds of remote locations. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417069] tab of a samba share has the "unknown" icon
https://bugs.kde.org/show_bug.cgi?id=417069 --- Comment #1 from Patrick Silva --- Created attachment 125622 --> https://bugs.kde.org/attachment.cgi?id=125622=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417068] Clipboard does not stay pinned when it should
https://bugs.kde.org/show_bug.cgi?id=417068 Matt Parry changed: What|Removed |Added Keywords||usability --- Comment #1 from Matt Parry --- I think that this is a new regression as I have used the clipboard in older versions of Kubuntu and it does not do this -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 398651] Drop down to select an user account is vertically bigger than normal
https://bugs.kde.org/show_bug.cgi?id=398651 --- Comment #9 from Patrick Silva --- Created attachment 125621 --> https://bugs.kde.org/attachment.cgi?id=125621=edit Gnome Disks asking for password on Plasma 5.18 beta Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417068] New: Clipboard does not stay pinned when it should
https://bugs.kde.org/show_bug.cgi?id=417068 Bug ID: 417068 Summary: Clipboard does not stay pinned when it should Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: mattparry...@gmail.com Target Milestone: 1.0 Created attachment 125620 --> https://bugs.kde.org/attachment.cgi?id=125620=edit video showing the clipboard not staying pinned and switching to 'Status and Notifictions SUMMARY 2 Usability issues, First issue I have pinned the clipboard to the desktop so that I have easy access to three items that I need to paste multi times into a spreadsheet chart, however rather than staying 'pinned' on the clipboard, it keeps bouncing back to the 'Status and Notifications' menu and I have to click back into the clipboard. This add unnecessary step into copying and pasting. Secondary, when highlighting the text that needs to be replaced, without asking it to 'copy' to the clipboard, it is automatically copying to the clipboard pushing my saved clipboards down the list, causing me to have to delete STEPS TO REPRODUCE 1. Pin Clipboard to the desktop on the top of my worksheet 2. Copy my values to the clipboard. 3. Values that I want to be replaced are automatically copied to the clipboard - this should not happen 4 - I select my value and the clipboard changes to status and notifications - it should stay as clipboard OBSERVED RESULT - info is copied to the clipboard without me selecting 'copy' resulting in me having to delete the content - Clipboard when pinned should stay as clipboard and not change to 'status and notifications' - In my attached video Only '20' 'AL' 'AW' should be in the clipboard. - In the video, I keep having to press on the clipboard when it should stay pinned EXPECTED RESULT - Dont copy data I've not specifically asked my system to copy - Dont close the clipboard window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 (available in About System) KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417064] Import menu has no option to acquire images from scanner
https://bugs.kde.org/show_bug.cgi?id=417064 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Platform|Compiled Sources|MS Windows --- Comment #1 from caulier.gil...@gmail.com --- Windows version do not have the scanner plugin compiled for the moment. In fact it do not compile about libksane library under windows... Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387230] plasmashell information window starts minimized
https://bugs.kde.org/show_bug.cgi?id=387230 --- Comment #6 from Gordon Lack --- Similarly no longer an issue in Kubuntu 19.10 (plasma 5.16.5) -- You are receiving this mail because: You are watching all bug changes.
