[kwin] [Bug 411682] Copy-paste doesn't work in firefox
https://bugs.kde.org/show_bug.cgi?id=411682 cacarry changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #10 from cacarry --- I thought i shouldn't change status -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415460] JFIF files have APP0 marker after SOI where there should be APP1
https://bugs.kde.org/show_bug.cgi?id=415460 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/338776981b62 ||d5e587221577478898816a233d1 ||6 Status|REPORTED|RESOLVED --- Comment #12 from Maik Qualmann --- Git commit 338776981b62d5e587221577478898816a233d16 by Maik Qualmann. Committed on 26/12/2019 at 08:23. Pushed by mqualmann into branch 'master'. set Exif orientation to normal because DImg was loaded aligned FIXED-IN: 7.0.0 M +2-1NEWS M +17 -11 core/dplugins/generic/tools/sendbymail/manager/imageresizejob.cpp https://invent.kde.org/kde/digikam/commit/338776981b62d5e587221577478898816a233d16 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412697] Meta+L keyboard shortcut to lock screen
https://bugs.kde.org/show_bug.cgi?id=412697 --- Comment #4 from Alejandro Moreno Calvo --- Created attachment 124722 --> https://bugs.kde.org/attachment.cgi?id=124722&action=edit Patch without testing -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412697] Meta+L keyboard shortcut to lock screen
https://bugs.kde.org/show_bug.cgi?id=412697 --- Comment #5 from Alejandro Moreno Calvo --- I think I have writen a correct patch. I had the doubt of where to look for the text to put in I18N_NOOP. I have chosen the text by searching in https://l10n.kde.org/stats/gui/stable-kf5/team/es/kde-workspace/, is that correct? Nowadays I haven't a test environment to test this patch. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 415572] New: kdevelop-pg-qt build error on brew (MAC OS) struct hash< QT_PREPEND_NAMESPACE(Class) > 1 error generated
https://bugs.kde.org/show_bug.cgi?id=415572 Bug ID: 415572 Summary: kdevelop-pg-qt build error on brew (MAC OS) struct hash< QT_PREPEND_NAMESPACE(Class) > 1 error generated Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- SUMMARY Trying to install kdevelop on Mac OS Catalina with brew fails, because kdevelop-pg-qt can't be built. STEPS TO REPRODUCE 1. brew install kdevelop OBSERVED RESULT The following link contains the build log. https://gist.github.com/Petross404/65e3026ddcd6d214b7ca7c2741f8402d SOFTWARE/OS VERSIONS macOS: Catalina KDE Frameworks Version: 5.65 Qt Version: 5.14 ADDITIONAL INFORMATION I am using this tap : https://github.com/KDE-mac/homebrew-kde -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 AToMiXhawK changed: What|Removed |Added CC||githinman...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 415573] New: Sign in to Google account fails as app in not verified by Google
https://bugs.kde.org/show_bug.cgi?id=415573 Bug ID: 415573 Summary: Sign in to Google account fails as app in not verified by Google Product: KAccounts Version: 19.12 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-telepathy-b...@kde.org Reporter: githinman...@gmail.com Target Milestone: --- Created attachment 124723 --> https://bugs.kde.org/attachment.cgi?id=124723&action=edit Screenshot SUMMARY STEPS TO REPRODUCE 1. Open Online Accounts Settings, Click Add new Account 2. Select Google 3. Enter username, password, sign in. OBSERVED RESULT Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 --- Comment #7 from Alexandre Belz --- Hi Maik, I'm using the 22th dec 70 beta1 release available here : https://download.kde.org/unstable/digikam/ is there a log file I could open to check myself what went wrong ? or that i could maybe send to you ? Alex -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415568] The "Always use empty screen gap..." option does not work
https://bugs.kde.org/show_bug.cgi?id=415568 --- Comment #1 from Michail Vourlakos --- I reorganized a bit the Behavior options should please check them out again... Some information about option "Always use screen gap from floating...". Latte by default is using all the space from the dock to the screen edge in floating mode. BUT there are cases that this does not occur, for example make a Latte Panel and you will see that the gap behind the Latte panel is a real space which is not be used by Latte. By enabling the option "Always use screen gap from ... " then Latte panels are also using that empty space to the screen edge either for Items activation (when the drag active window from empty areas is NOT enabled) OR to drag/maximize last active window if that option is enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 412071] Multimedia Controls - Spotify Web Client
https://bugs.kde.org/show_bug.cgi?id=412071 Utkarsh Verma changed: What|Removed |Added CC||utkarsh.nav...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415574] New: Plasma blind for root
https://bugs.kde.org/show_bug.cgi?id=415574 Bug ID: 415574 Summary: Plasma blind for root Product: plasmashell Version: 5.17.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: m.hrabov...@post.cz CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.12.6 Frameworks Version: 5.64.0 Operating System: Linux 5.3.15-lp152.1-default x86_64 Distribution: openSUSE Leap 15.2 Alpha -- Information about the crash: - What I was doing when the application crashed: Start plasma as root. Missing start menu and toolbar. If starting as user, it worked. HW Environment VMware Workstation 15. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f01c1dbad80 (LWP 1898))] Thread 8 (Thread 0x7f0182e47700 (LWP 2015)): #0 0x7f01bb42356b in poll () from /lib64/libc.so.6 #1 0x7f01b55091a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f01b55092bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f01bbdb924b in QEventDispatcherGlib::processEvents (this=0x560a267a9330, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f01bbd5a35a in QEventLoop::exec (this=this@entry=0x7f0182e46c70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f01bbb8012a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f0185769c37 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #7 0x7f01bbb818d2 in QThreadPrivate::start (arg=0x560a267e9e30) at thread/qthread_unix.cpp:361 #8 0x7f01b8ce24f9 in start_thread () from /lib64/libpthread.so.0 #9 0x7f01bb42ddbf in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f01986c2700 (LWP 2010)): #0 0x7f01b55080be in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #1 0x7f01b5509065 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f01b55092bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f01bbdb924b in QEventDispatcherGlib::processEvents (this=0x560a24f4e290, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f01bbd5a35a in QEventLoop::exec (this=this@entry=0x7f01986c1c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f01bbb8012a in QThread::exec (this=this@entry=0x560a24d2b540) at thread/qthread.cpp:531 #6 0x7f01bfb5d116 in QQuickPixmapReader::run (this=0x560a24d2b540) at /usr/src/debug/libqt5-qtdeclarative-5.12.6-lp152.1.1.x86_64/src/quick/util/qquickpixmapcache.cpp:953 #7 0x7f01bbb818d2 in QThreadPrivate::start (arg=0x560a24d2b540) at thread/qthread_unix.cpp:361 #8 0x7f01b8ce24f9 in start_thread () from /lib64/libpthread.so.0 #9 0x7f01bb42ddbf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f019e52f700 (LWP 2006)): #0 0x7f01b8ce883d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f01a3f92a4b in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f01a3f928c7 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f01b8ce24f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f01bb42ddbf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f019ed30700 (LWP 2005)): #0 0x7f01b8ce883d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f01a3f92a4b in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f01a3f928c7 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f01b8ce24f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f01bb42ddbf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f01a8159700 (LWP 2001)): #0 0x7f01bb43aff2 in __libc_disable_asynccancel () from /lib64/libc.so.6 #1 0x7f01bb41f07d in read () from /lib64/libc.so.6 #2 0x7f01b554dc80 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f01b5508cb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7f01b5509150 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f01b55092bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7f01bbdb924b in QEventDispatcherGlib::processEvents (this=0x560a24ab0950, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7f01bbd5a35a in QEventLoop::exec (this=this@entry=0x7f01a8158c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #8 0x7f01bbb8012a in QThread::exec (this=this@entry=0x560a24b31470) at thread/qthread.cpp:531 #9 0x7f01bf689bc5 in QQmlThreadPrivate::run (this=0x560a24b31470) at /usr/src/debug/libqt5-qtdeclarative-5.12.6-lp152.1.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:148 #10 0x7f01bbb818d2 in QThreadPrivate::start (arg=0x560a24b31470) at thread/qthread_unix.cpp:361 #11
[digikam] [Bug 366551] Unclear icon-item overlay when associating people to faces
https://bugs.kde.org/show_bug.cgi?id=366551 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Unclear dialog when |Unclear icon-item overlay |associating people to faces |when associating people to ||faces -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414685] imap_resource crash after manual check
https://bugs.kde.org/show_bug.cgi?id=414685 --- Comment #3 from Iyán Méndez Veiga --- Today I realized that my issue only seems to appear when I leave the computer locked. If I don't lock the computer, Kmail keeps working and there is no crush. If I lock it, after a while imap resource crash and I have to close Kmail, do a akonadictl fsck + vacuum + restart, and then open again Kmail. Maybe some issue with akonadi and lockscreen since last release? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 --- Comment #8 from Maik Qualmann --- Download and start DebugView from Microsoft. Start digiKam and do a face search on the image. Post the messages that are available in DebugView. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415559] Standard Face Detection does not work on LowRes pictures
https://bugs.kde.org/show_bug.cgi?id=415559 --- Comment #4 from Maik Qualmann --- Interestingly, the faces are recognized when I split the image. If I debug the incorrectly recognized rectangles, my guess is that the DNN engine can be irritated by the background. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 415576] New: kmail crashes after restarting because no new mail was being fetched
https://bugs.kde.org/show_bug.cgi?id=415576 Bug ID: 415576 Summary: kmail crashes after restarting because no new mail was being fetched Product: kmail2 Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- Application: kmail (5.12.3) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 4.19.86-gentoo x86_64 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: I had just restarted kmail, because it wasn't fetching any new mail. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9996450a40 (LWP 5984))] Thread 23 (Thread 0x7f998611c700 (LWP 31383)): #0 0x7f99a9d5f1bc in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99a296c006 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f99a296c9e3 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f99a296cb61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f99a29246d1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f99a29275a2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f99a2927e64 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f99a296ee8a in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f99a9d583a7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f99ac3f424f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f99617fa700 (LWP 31382)): #0 0x7f99a9d5f1bc in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99a296c006 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f99a296c9e3 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f99a296cb61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f99a29246d1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f99a292793b in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f99a2927e64 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f99a296ee8a in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f99a9d583a7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f99ac3f424f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f99637fe700 (LWP 31380)): #0 0x7f99ac3e3ee0 in read () at /lib64/libc.so.6 #1 0x7f99a939aeff in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f99a935426e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f99a93546e3 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f99a935485f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f99ac9ed36b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f994b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f99ac99853b in QEventLoop::exec(QFlags) (this=this@entry=0x7f99637fdb60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f99ac7fb3b1 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f99ac7fc442 in QThreadPrivate::start(void*) (arg=0x55aa9796dc10) at thread/qthread_unix.cpp:360 #9 0x7f99a9d583a7 in start_thread () at /lib64/libpthread.so.0 #10 0x7f99ac3f424f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f9963fff700 (LWP 31368)): #0 0x7f99a9d5f1bc in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99a296c006 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f99a296c9e3 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f99a296cb61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f99a29246d1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f99a29275a2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f99a2927e64 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f99a296ee8a in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f99a9d583a7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f99ac3f424f in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f9935f51700 (LWP 6794)): #0 0x7f99a9d5ee57 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99a296bf0c in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f99a296c9f0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f99a296cb1f in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f99a29246a6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f99a292793b in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f99a2927ea4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f99a296ee8a in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f99a9d583a7
[kdenlive] [Bug 415575] New: Keyboard input not working
https://bugs.kde.org/show_bug.cgi?id=415575 Bug ID: 415575 Summary: Keyboard input not working Product: kdenlive Version: 19.12.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wanderer...@hotmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open any dialog 2. Attempt to type into a text field or time duration field OBSERVED RESULT Nothing happens EXPECTED RESULT Text should appear or duration time should be updated SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 415577] New: Amarok starts playing automatically after ending Skype call
https://bugs.kde.org/show_bug.cgi?id=415577 Bug ID: 415577 Summary: Amarok starts playing automatically after ending Skype call Product: amarok Version: 2.9.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: kf5 If I have amarok launched, whenever I make a skype call and end it, amarok will start playing the beginning of its playlist automatically. Steps to reproduce: * Launch amarok with some playlist from previous session already in there, don't do anything inside it. Keep the window hidden (so that it's only in the taskbar). * Launch skype. * Make a videocall in skype. * End the videocall. Expected behavior: amarok should not do anything. Actual behavior: amarok starts playing the beginning of its playlist right after the skype call is ended. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 415554] k3b refuses to burn an image it just created
https://bugs.kde.org/show_bug.cgi?id=415554 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- "I can not find source code for this a SourceForge" You mean k3b? https://cgit.kde.org/k3b.git/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415578] New: Compact view no longer respond to vertical scroll but only horizontal scroll
https://bugs.kde.org/show_bug.cgi?id=415578 Bug ID: 415578 Summary: Compact view no longer respond to vertical scroll but only horizontal scroll Product: dolphin Version: 19.12.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: compact mode Assignee: dolphin-bugs-n...@kde.org Reporter: quwenruo.bt...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In compact mode, vertical scroll no longer move the view anymore. Only horizontal scroll can move the view. Unfortunately most mouse doesn't support horizontal scroll. Even for mouse supporting it, like the Sculpt Ergonomic mouse I'm using, it's still super awkward to do horizontal scroll. Please at least provide a way to make compact mode to accept vertical scroll. STEPS TO REPRODUCE 1. Use dolphin to view a directory with many files 2. Switch to compact view mode 3. Use mouse wheel to do vertical scroll OBSERVED RESULT The view is not moved at all. EXPECTED RESULT Vertical scroll should move the view SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Dolphin 19.08.3 works fine. 19.12.0 doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #5 from Duncan <1i5t5.dun...@cox.net> --- FWIW, kwin master as of 054cfc1c8 seems to be /vastly/ improved, altho not /quite/ back to where it was. I'd say 75-80% (aka 3/4 to 4/5) of the original regression performance loss has been regained. I can run all my usual effects now, but still noticed a bit of slow-down until I tweaked configs a bit, adjusting the wobbly-windows config for normal windows and bumping animation speed (workspace behavior, general behavior, animation speed slider) for plasma (autohide panel showing speed, panel plasmoid hover popup morphing speed). It's fast enough now if I was new to plasma I'd never suspect the regression and would just tweak things if the default seemed slow until they worked as I wanted, and it's only that I had it tuned to what I wanted before and it was still slightly too slow with that config that hints at the far greater regression before. (In reply to Roman Gilg from comment #4) > Please check out if this solves the problem for you: > https://phabricator.kde.org/D26216 I take it that's not yet applied to master? Do I still need to try it? And/or would bisecting the commit at which I got most of the performance back still help? (While fiddling with the config I noticed the FPS effect once again. Too bad I didn't think to try enabling it when kwin was lagging out so badly. It'd have been nice to get real numbers, tho of course I still could by pinning the bad commit and rebuilding...) (My regular updates included a gcc-9.2.0 gentoo patch revision early in the update sequence, a mesa update from 19.3.0 to 19.3.1, and an llvm and clang update from 9.0.1-rc3 to 9.0.1 release, of interest given their usage with amdgpu for shader-compiling, etc. While kwin's 00bf75d06 commit did indeed regress something, it's possible that it was only as severe as I was seeing due to a bug in one of the above packages and that updating that package, not a kwin commit since then-head d72e96802, gave me back most of what I saw lost in that regression.) I've a couple more days off due to Christmas, and (if only for my own curiosity) may well do some more rebuild testing to pin down exactly what gave me that performance back, as well as testing D26216, but FWIW it's definitely workable now and as such I'd be OK with closing the bug, even if I didn't get 100% of the pre-regression performance back. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415578] Compact view no longer respond to vertical scroll but only horizontal scroll
https://bugs.kde.org/show_bug.cgi?id=415578 --- Comment #1 from Qu Wenruo --- Reverting to 19.08.3 doesn't solve the problem, so it looks like something wrong in the input stack. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410981] Kickoff does not search if opened with cursor under it
https://bugs.kde.org/show_bug.cgi?id=410981 --- Comment #2 from Tasos Sahanidis --- (In reply to Nate Graham from comment #1) > Fixed in Plasma 5.17 already! I was unable to verify if it was fixed or not, as I had to leave this computer before KDE Neon was updated to 5.17, however I can still reproduce this bug now on a fully updated system, with the exact steps as before. Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Kernel Version: 5.0.9-050009-generic OS Type: 64-bit Processors: 4 × Intel® Core™2 Quad CPU Q6600 @ 2.40GHz Memory: 7,8 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395236] Allow face detection for selected images / albums and automatically during import
https://bugs.kde.org/show_bug.cgi?id=395236 --- Comment #8 from Jens --- Automatic face detection upon import would make my day much easier. Thank you for considering this feature! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415579] New: Could not open the AppStream metadata pool + invalid kns backend +
https://bugs.kde.org/show_bug.cgi?id=415579 Bug ID: 415579 Summary: Could not open the AppStream metadata pool + invalid kns backend + Product: Discover Version: 5.17.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updater Assignee: lei...@leinir.dk Reporter: pubc...@free.fr CC: aleix...@kde.org Target Milestone: --- SUMMARY All is in the title STEPS TO REPRODUCE 1. plasma-discover 2. plasma-discover --listbackends OBSERVED RESULT adding empty sources model QStandardItemModel(0x55665cd7f530) Could not open the AppStream metadata pool "De nombreux composants ont été reconnus comme non valides. Voir la sortie de débogage pour plus de détails." invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation." :7: TypeError: Cannot read property 'contentX' of null file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:188: Error: Cannot assign QObject* to QQuickAction* [carole@localhost ~]$ plasma-discover --backends packagekit-backend [carole@localhost ~]$ plasma-discover adding empty sources model QStandardItemModel(0x565379018900) Could not open the AppStream metadata pool "De nombreux composants ont été reconnus comme non valides. Voir la sortie de débogage pour plus de détails." invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation." -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 415572] kdevelop-pg-qt build error on brew (MAC OS) struct hash< QT_PREPEND_NAMESPACE(Class) > 1 error generated
https://bugs.kde.org/show_bug.cgi?id=415572 Petros changed: What|Removed |Added Platform|Other |Homebrew (macOS) Version|unspecified |5.4.5 OS|Linux |macOS -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415578] Compact view no longer respond to vertical scroll but only horizontal scroll
https://bugs.kde.org/show_bug.cgi?id=415578 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 415546 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415546] Cannot scroll horizontally with mousewheel
https://bugs.kde.org/show_bug.cgi?id=415546 Antonio Rojas changed: What|Removed |Added CC||quwenruo.bt...@gmx.com --- Comment #8 from Antonio Rojas --- *** Bug 415578 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 --- Comment #17 from Yuking --- Plasma works fine while just replacing plasma-workspace-5.17.4 with 5.16.4... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #6 from Roman Gilg --- (In reply to Duncan from comment #5) > FWIW, kwin master as of 054cfc1c8 seems to be /vastly/ improved, altho not > /quite/ back to where it was. I'd say 75-80% (aka 3/4 to 4/5) of the > original regression performance loss has been regained. > > I can run all my usual effects now, but still noticed a bit of slow-down > until I tweaked configs a bit, adjusting the wobbly-windows config for > normal windows and bumping animation speed (workspace behavior, general > behavior, animation speed slider) for plasma (autohide panel showing speed, > panel plasmoid hover popup morphing speed). > > It's fast enough now if I was new to plasma I'd never suspect the regression > and would just tweak things if the default seemed slow until they worked as > I wanted, and it's only that I had it tuned to what I wanted before and it > was still slightly too slow with that config that hints at the far greater > regression before. > > (In reply to Roman Gilg from comment #4) > > Please check out if this solves the problem for you: > > https://phabricator.kde.org/D26216 > > I take it that's not yet applied to master? Do I still need to try it? > And/or would bisecting the commit at which I got most of the performance > back still help? Yea, not yet applied. Would be great if you could try it. I noticed some slow downs as well now after more testing with certain configurations and this patch should help with them. Can you apply it to the top of KWin master? > (While fiddling with the config I noticed the FPS effect once again. Too > bad I didn't think to try enabling it when kwin was lagging out so badly. > It'd have been nice to get real numbers, tho of course I still could by > pinning the bad commit and rebuilding...) The numbers of the FPS effect are not that reliable. Actually currently I test often with: https://www.testufo.com/animation-time-graph https://www.vsynctester.com/ > (My regular updates included a gcc-9.2.0 gentoo patch revision early in the > update sequence, a mesa update from 19.3.0 to 19.3.1, and an llvm and clang > update from 9.0.1-rc3 to 9.0.1 release, of interest given their usage with > amdgpu for shader-compiling, etc. While kwin's 00bf75d06 commit did indeed > regress something, it's possible that it was only as severe as I was seeing > due to a bug in one of the above packages and that updating that package, > not a kwin commit since then-head d72e96802, gave me back most of what I saw > lost in that regression.) > > I've a couple more days off due to Christmas, and (if only for my own > curiosity) may well do some more rebuild testing to pin down exactly what > gave me that performance back, as well as testing D26216, but FWIW it's > definitely workable now and as such I'd be OK with closing the bug, even if > I didn't get 100% of the pre-regression performance back. It's good to hear that it feels better now. Thank you for the feedback. But check out the patch D26216 above if it improves the situation even more. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 415580] New: KTorrent does not save magnets unless properly shut down
https://bugs.kde.org/show_bug.cgi?id=415580 Bug ID: 415580 Summary: KTorrent does not save magnets unless properly shut down Product: ktorrent Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: linus.kardell+kdeb...@gmail.com Target Milestone: --- SUMMARY The magnet link list seems to only save when KTorrent is properly shut down. If KTorrent is killed, or crashes, the magnet link will have not been saved, no matter how long time has passed. STEPS TO REPRODUCE 1. Add a magnet link, or start a download from a magnet link thus removing it 2. Kill KTorrent 3. Restart KTorrent OBSERVED RESULT Magnet link list reset to state before step 1 EXPECTED RESULT Magnet link list should be same as after 1 SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415568] The "Always use empty screen gap..." option does not work
https://bugs.kde.org/show_bug.cgi?id=415568 --- Comment #2 from tr...@yandex.com --- Just an idea, could the dock remove its gap (maybe with an slide animation, something like the autohide effect) when the user maximizes any window? Because when there is a maximized window, the dock with a gap looks kinda ugly and that is wasted space. When there is not any maximized window, it's ok. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519
jochen changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #6 from jochen ---
Yes, it is a strange issue. I do not mind if the ticket gets closed without
solution. Might be a one off issue, dedicated to my installation. Although
there is nothing I can think of what could be that special.
Using AQHBCI_LOGLEVEL=debug ./KMyMoney-5.0.7-3227834-x86_64.AppImage does not
change anything. Console stay empty when trying to update - whether for single
account or all. Of course, other log messages are logged to console.
Given how fast the window with the message ("no transactions imported"; as
attached) appears, I am not prompted for HBCI/bank login and nothing logged to
console, it almost appears to me like that's a dead menu/button. But given it
is working for you, this cannot be true.
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 415581] New: Rendered movie contains many unexpected audio breaks, silent gaps.
https://bugs.kde.org/show_bug.cgi?id=415581 Bug ID: 415581 Summary: Rendered movie contains many unexpected audio breaks, silent gaps. Product: kdenlive Version: 19.12.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: franek.fruwal...@gmail.com Target Milestone: --- Created attachment 124724 --> https://bugs.kde.org/attachment.cgi?id=124724&action=edit Typical movie: MP4 files got from GOPRO6 + MP3 audio. 5994 fps, 2704x1520 SUMMARY STEPS TO REPRODUCE 1. Add mp3 audio to the project bin 2. Place this audio in empty audiotrack 3. Render movie as "mp4 (the dominating format...)" and set quality to maximum 4. Start and finalize rendering OBSERVED RESULT During watching the rendered movie you can observe multiple unexpected silent gaps in audio. EXPECTED RESULT Audio track should be heard without gaps. SOFTWARE/OS VERSIONS Windows: 10 PRO MLT: 19.12.0 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 (built against 5.13.2) ADDITIONAL INFORMATION I have interchanged multiple MP3 file without better result. I have i7 Intel proc with 8 MB of RAM (DELL Inspiron notebook) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415476] ctrl+click on canvas doesn't always disable eraser mode
https://bugs.kde.org/show_bug.cgi?id=415476 --- Comment #4 from Ahab Greybeard --- I've had another look at this. The 4.2.8 appimage now does it most of the time instead of rarely and the Ctrl+double-click no longer makes the eraser mode turn off. With the Dec22 4.3.0 prealpha appimage, it does it all the time. The Ctrl+double-click sometimes (not always) makes the eraser mode turn off. On my laptop running Debian 10, the 4.3.0 prealpha appimage does it most but not all of the time. In all situations, using the eraser now no longer makes the eraser mode turn off after the next Ctrl+click. It's very hard to quantify and examine. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415568] The "Always use empty screen gap..." option does not work
https://bugs.kde.org/show_bug.cgi?id=415568 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Michail Vourlakos --- there is no way to make such animation to play smoothly... and personally I am not interested at all supporting it... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 --- Comment #9 from Alexandre Belz --- Created attachment 124725 --> https://bugs.kde.org/attachment.cgi?id=124725&action=edit DebugView Log file please find enclosed a DebugView log of the "Scan whole collection" triggered from the people view. I will also test the "Scan Face" from a single picture. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415568] The "Always use empty screen gap..." option does not work
https://bugs.kde.org/show_bug.cgi?id=415568 --- Comment #4 from Michail Vourlakos --- in any case, open a feature request to keep track limitations and if this is possible... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415582] New: People Unknown faces does not decrease to zero
https://bugs.kde.org/show_bug.cgi?id=415582 Bug ID: 415582 Summary: People Unknown faces does not decrease to zero Product: digikam Version: 7.0.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- SUMMARY When I identify/confirm a face, the "Unknown" folder does not decrease to zero STEPS TO REPRODUCE 1. Open "People" space 2. Go to unknown people directory 3. Confirm one face OBSERVED RESULT The picture moved to the right "people" directory, but The "Unkown (1)" stays the same. EXPECTED RESULT The "Unkown (1)" should become "Unkown (0)". SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION See attached log file from DebugView. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415582] People Unknown faces does not decrease to zero
https://bugs.kde.org/show_bug.cgi?id=415582 --- Comment #1 from Alexandre Belz --- Created attachment 124726 --> https://bugs.kde.org/attachment.cgi?id=124726&action=edit DebugView Log file -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415582] People Unknown faces does not decrease to zero
https://bugs.kde.org/show_bug.cgi?id=415582 --- Comment #2 from Alexandre Belz --- Same thing from a people folder : if I remove faces, the counter does not decrease : I still see "Harry (2)" zeven if I reject the 2 faces and have no face in that people tag/folder. I would expect to see "Harry (0)" when empty. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414667] Wine systray icons does not respond to clicks with multi monitor
https://bugs.kde.org/show_bug.cgi?id=414667 --- Comment #8 from Eliphas --- Hello! Should it be released in the unstable or testing repos or only when the version changes to 5.18? Tried now on current testing 5.17.4+p18.04+git20191221 and unstable 5.17.4+p18.04+git20191224 with same results. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 --- Comment #10 from Maik Qualmann --- After the log, you started face recognition and not detection. Please do it with a single image. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 415539] Button text "Download New %1" should have ellipsis according to HIG
https://bugs.kde.org/show_bug.cgi?id=415539 Dan Leinir Turthra Jensen changed: What|Removed |Added CC||ad...@leinir.dk Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Dan Leinir Turthra Jensen --- That it most definitely should, good catch :) This is even the sort of thing i try and catch, so i feel all manner of dirty for missing it in code i wrote myself ;) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 --- Comment #11 from Alexandre Belz --- Maik, I confirm that when I click on individual "Scan for face" from "Thumbnails" or "Preview", I do see that faces are correctly detected (empty rectangles). Then how can I trigger the DNN recognition for a single image ? Moreover, from the People / whole collection, I now understand that if I do it in a 3 phases approach, it does work : 1) Detection (= scan for faces on every picture) 2) Tag some faces 3) Recognition (= DNN) will suggest other similar faces This is acceptable although not self-explanatory for non digikam native users. It would be useful to have an option to cumulate both phases ! (= Checkboxes instead of radio buttons) I also noticed that re-launching 3) can bring me new iteratively recognized faces, do you agree ? This must be manually triggered, nothing running in background ? Note that Picasa had the possibility to run this Detection + DNN recognition in a single activation, in background, and - either once (archive folder) - or endlessly (working folder) ... it was so easy to build people database in that mode ! DNN reported new similarities in real time. I just had to confirm/reallocate and after 30 minutes the whole database was rebuilt ! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415583] New: Global Themes with SDDM Themes do not get installed properly if SDDM is not installed
https://bugs.kde.org/show_bug.cgi?id=415583 Bug ID: 415583 Summary: Global Themes with SDDM Themes do not get installed properly if SDDM is not installed Product: systemsettings Version: 5.17.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_lookandfeel Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com Target Milestone: --- SUMMARY Global Themes that have an SDDM theme as part of their pack do not get installed to ~/.local/share/plasma/look-and-feel if SDDM is not installed and /usr/share/SDDM therefore does not exist. STEPS TO REPRODUCE 1. Remove SDDM and any SDDM Themes left over 2. Go into Global Theme -> Get New Global Themes... 3. Install a Global Theme that should pull in an SDDM Theme such as Layan or Sweet OBSERVED RESULT The Global Theme isn't installed to its proper place at all and therefore doesn't appear in Global Theme despite being "Installed" EXPECTED RESULT The Global Theme will be installed to the correct location minus the SDDM theme it provides users with and will be in Global Theme SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Feren OS (KDE neon 5.17.4) (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415584] New: Reorganize setting menus
https://bugs.kde.org/show_bug.cgi?id=415584 Bug ID: 415584 Summary: Reorganize setting menus Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tr...@yandex.com Target Milestone: --- There are some minor things could be improved: 1, Move Layout > Configure > Preferences tab to out of the Layout menu - Because it does not relate to the Layout settings. It's very hidden to be here. Maybe move it to "Edit Latte general settings", something like that, the same level with "Panel Settings" 2, Rename "Layout > Configure..." to "Manage layouts" - It would open the current Settings window, but has only the Layouts tab. 2, Rename "Panel/Dock Settings" to "Edit panel/dock" - This simply follows Plasma style in naming. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 414694] No visible way to show/hide the sidebar in full screen mode
https://bugs.kde.org/show_bug.cgi?id=414694 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/gwe ||nview/db6ca614a41eb880c2eee ||9d34101b17400dd5ca1 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Nate Graham --- Git commit db6ca614a41eb880c2eee9d34101b17400dd5ca1 by Nate Graham, on behalf of Madhav Kanbur. Committed on 26/12/2019 at 15:20. Pushed by ngraham into branch 'master'. Add button to toggle sidebar in fullscreen mode Summary: Previously, there was no way to toggle the sidebar in fullscreen view mode except for the keyboard shortcut F4. This patch adds a button to toggle the sidebar from the fullscreen toolbar. Test Plan: Tested the button in fullscreen (view) mode. Button works as expected, and preserves existing behavior of all other sidebar toggle mechanisms as well. Reviewers: #vdg, #gwenview, ngraham Subscribers: #gwenview Tags: #gwenview Differential Revision: https://phabricator.kde.org/D26230 M +2-0app/fullscreencontent.cpp https://commits.kde.org/gwenview/db6ca614a41eb880c2eee9d34101b17400dd5ca1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415584] Reorganize setting menus
https://bugs.kde.org/show_bug.cgi?id=415584 --- Comment #1 from Michail Vourlakos --- That window is considered a Global Preferences Window, meaning options that alter settings for all docks/panels. As such, I find both tabs sufficient to be in there... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415584] Reorganize setting menus
https://bugs.kde.org/show_bug.cgi?id=415584 --- Comment #2 from tr...@yandex.com --- (In reply to Michail Vourlakos from comment #1) > That window is considered a Global Preferences Window, meaning options that > alter settings for all docks/panels. > > As such, I find both tabs sufficient to be in there... I know both of them are for global settings, I just meant to reorganize them. When you click on Layout > Configure..., do you have a sense that it contains the Preference tab? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415584] Reorganize setting menus
https://bugs.kde.org/show_bug.cgi?id=415584 --- Comment #3 from Michail Vourlakos --- it does but it is not accessed without user interaction -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415546] Cannot scroll horizontally with mousewheel
https://bugs.kde.org/show_bug.cgi?id=415546 --- Comment #9 from Nate Graham --- Does anyone have a Qt bug report handy? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415584] Reorganize setting menus
https://bugs.kde.org/show_bug.cgi?id=415584 --- Comment #4 from tr...@yandex.com --- (In reply to trmdi from comment #2) > (In reply to Michail Vourlakos from comment #1) > > That window is considered a Global Preferences Window, meaning options that > > alter settings for all docks/panels. > > > > As such, I find both tabs sufficient to be in there... > > I know both of them are for global settings, I just meant to reorganize them. > When you click on Layout > Configure..., do you have a sense that it > contains the Preference tab? For example, why does "Autostart" option belong to the Layout > Configure ? Those 2 things are completely unrelated. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412697] Meta+L keyboard shortcut to lock screen
https://bugs.kde.org/show_bug.cgi?id=412697 --- Comment #6 from Nate Graham --- Yep, that's fine. Please feel free to submit your patch using https://phabricator.kde.org. Here is the documentation: https://community.kde.org/Infrastructure/Phabricator -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415584] Reorganize setting menus
https://bugs.kde.org/show_bug.cgi?id=415584 --- Comment #5 from Michail Vourlakos --- Latte Global Preferences tab is hidden because is not used often, having different ways to access it, I consider it normal. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415584] Reorganize setting menus
https://bugs.kde.org/show_bug.cgi?id=415584 --- Comment #6 from tr...@yandex.com --- (In reply to Michail Vourlakos from comment #1) > That window is considered a Global Preferences Window, meaning options that > alter settings for all docks/panels. > > As such, I find both tabs sufficient to be in there... Ok, but I still prefer to move Layout > Configure to the top level and rename it to e.g. "Latte global settings..." Because a Configure insides the Layout give me a feel that it's only used for Configuring Layouts. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406624] dolphin titlebar garbled with baloosearch json query
https://bugs.kde.org/show_bug.cgi?id=406624 Ismael Asensio changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #6 from Ismael Asensio --- Without further information, I'm guessing that this behavior is caused by the option 'Show full path in title bar' being enabled, and so "intended behavior". If that behavior should be changed for certain URL schemes, might be a different matter of discussion. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 414694] No visible way to show/hide the sidebar in full screen mode
https://bugs.kde.org/show_bug.cgi?id=414694 Nate Graham changed: What|Removed |Added Version Fixed In||20.04.0 -- You are receiving this mail because: You are watching all bug changes.
[simon] [Bug 415585] New: After successful install, simon crashes at startup
https://bugs.kde.org/show_bug.cgi?id=415585 Bug ID: 415585 Summary: After successful install, simon crashes at startup Product: simon Version: 0.4.80 Platform: Debian stable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: simon Assignee: kde...@unormal.org Reporter: stephane.lambre...@gmail.com Target Milestone: --- SUMMARY When launched from terminal : QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. and right after KCrash: Application 'simon' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/lambrecht/.kde/socket-tert-port-lambr/kdeinit4__0 Warning: connect() failed: : Aucun fichier ou dossier de ce type KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly Crash report says : Application: Simon (simon), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Inferior 1 (process 19430) detached] EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 10 Buster (4.19.0-6-amd64) KDE Plasma Version: KDE Plasma 5:102 KDE Frameworks Version: 5.54.0-1 Qt Version: (system default) 5.11.3+dfsg1-1+deb10u1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 Rob changed: What|Removed |Added CC||r...@robwu.nl -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415332] Okular does not show the dialogue to let me load a file
https://bugs.kde.org/show_bug.cgi?id=415332 --- Comment #6 from adalbert.hans...@gmx.de --- (In reply to Albert Astals Cid from comment #5) > So maybe you can close this bug, and open a new one with more clear > information of what you did and what is wrong? Why should I close it? The bug is persistent and has nothing to do with Comment2's assumption: In order to exclude any effect of Comment2's assumption, I first uninstalled okular (which was a snap installed version, but since I had used the standard installation before too, I uninstalled that too just to be sure (there was none left): v@v:~$ sudo snap remove okular okular entfernt v@v:~$ sudo apt-get purge okular Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Paket »okular« ist nicht installiert, wird also auch nicht entfernt. 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. v@v:~$ sudo snap install okular okular 19.04.2 aus KDE✓ installiert v@v:~$ okular --version Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed okular 1.7.2 v@v:~$ snap list --all Name Version Rev Aufzeichnung Herausgeber Hinweise core18 20191126 1279 stablecanonical✓ base,deaktiviert core18 20191212 1288 stablecanonical✓ base kde-frameworks-5-core18 5.61.032stablekde✓ - okular 19.04.2 63stablekde✓ - snapd2.42.45643 stablecanonical✓ snapd,deaktiviert snapd2.42.55754 stablecanonical✓ snapd v@v:~$ I expected that after installation that okular --version gives me version 19.04.2. Surprisingly in Hilfe>Über Okular it identifies itself as version 1.7.2, like okular --help does. However snap list all tells about okular 19.04.2! That's strange. The other strange thing is: If I select Datei>Öffnen, no dialogue comes up. I would expect that the file to display would be asked for. However, I can start okular from a terminal window and let it open a pdf file for me like this (however, I see some error messages then) v@v:~$ okular "~/Downloads/gnupg-anleitung-seite-1.pdf" Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed Icon theme "Adwaita" not found. Icon theme "Adwaita" not found. KActivities: FATAL ERROR: Failed to contact the activity manager daemon v@v:~$ (the Icon theme message is also shown if I switch the display theme to Numix). > > At this point i'm not sure what's your setup If you need more information on the setup beyond what is told in my first posting, I'd provide it if you tell me exactly what you are after (e.g. let me issue some command which identifies what you are looking for). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415446] Dissolve goes black
https://bugs.kde.org/show_bug.cgi?id=415446 Adam changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Adam --- Hi, thanks for the comment and indeed, I should have checked newer versions. I have used Ubuntu default installed version (19.08.2), which shows this bug. The version you have pointed to (19.12) needs separate installation but is working correctly! All transform & wipe / dissolve effects are rendered CORRECTLY. I'll change to resolved / fixed. Thank you again and have a great new year. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415439] The Fill Tool is memory overconsumption.
https://bugs.kde.org/show_bug.cgi?id=415439 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #2 from Tymond --- @Ahab the issue with undoing is I believe another bug, even if is related or the reproduction is similar. This bug is related to bug 412560 and maybe bug 414903. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415586] New: Remove online account
https://bugs.kde.org/show_bug.cgi?id=415586 Bug ID: 415586 Summary: Remove online account Product: systemsettings Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andysardin...@gmail.com Target Milestone: --- Created attachment 124727 --> https://bugs.kde.org/attachment.cgi?id=124727&action=edit Settings SUMMARY I have configured a remote account and I am not able to remove it. STEPS TO REPRODUCE 1. Configure a Google Account 2. Try to remove it OBSERVED RESULT I have no options to remove the account. 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.
[plasma-nm] [Bug 395596] [OpenVPN] qt version of network manager gui does not work with openvpn >= 2.4 configuration
https://bugs.kde.org/show_bug.cgi?id=395596 --- Comment #10 from Matthew Woehlke --- Martin, does it work if you import the connection using some other means? See also bug #396530. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 402713] Plasma NetworkManager OpenVPN fails to connect but displays no error, logs: AUTH: Received control message: AUTH_FAILED
https://bugs.kde.org/show_bug.cgi?id=402713 --- Comment #4 from Matthew Woehlke --- Does it work if you import the connection using some other means? See also bug #396530. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399225] OPENVPN does not connect to the network manager
https://bugs.kde.org/show_bug.cgi?id=399225 --- Comment #2 from Matthew Woehlke --- Does it work if you import the connection using some other means? See also bug #396530. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 396530] [RFE][OpenVPN] Use nmcli importer
https://bugs.kde.org/show_bug.cgi?id=396530 Matthew Woehlke changed: What|Removed |Added CC||mwoehlke.fl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 396530] [RFE][OpenVPN] Use nmcli importer
https://bugs.kde.org/show_bug.cgi?id=396530 --- Comment #4 from Matthew Woehlke --- Is anyone working on this? Right now the UX is that plasma+nm+openvpn is broken due to this. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398376] UI problems making face management very hard
https://bugs.kde.org/show_bug.cgi?id=398376 --- Comment #3 from caulier.gil...@gmail.com --- Git commit 05b9a534d89234b7571d5dade8067c490ab896cf by Gilles Caulier. Committed on 26/12/2019 at 17:30. Pushed by cgilles into branch 'master'. Faces Workflow simplication and improvements: remove face scan dialog and embed Face scan settings in People left sidebar. disable settings view while a face job is running. Catch face detector tool complete/cancelled signal to re-enable settings view. By this way, this will prevent to run 2 concurrent face jobs at the same time. Related: bug 412168, bug 380336 M +45 -31 core/app/views/sidebar/leftsidebarwidgets.cpp M +1-0core/app/views/sidebar/leftsidebarwidgets.h M +1-1core/utilities/facemanagement/CMakeLists.txt R +15 -45 core/utilities/facemanagement/widgets/facescanwidget.cpp [from: core/utilities/facemanagement/widgets/facescandialog.cpp - 089% similarity] R +9-11 core/utilities/facemanagement/widgets/facescanwidget.h [from: core/utilities/facemanagement/widgets/facescandialog.h - 079% similarity] R +8-11 core/utilities/facemanagement/widgets/facescanwidget_p.h [from: core/utilities/facemanagement/widgets/facescandialog_p.h - 090% similarity] M +1-1core/utilities/maintenance/facesdetector.cpp M +3-3core/utilities/maintenance/facesdetector.h M +1-0core/utilities/maintenance/maintenancetool.cpp M +11 -3core/utilities/maintenance/maintenancetool.h https://invent.kde.org/kde/digikam/commit/05b9a534d89234b7571d5dade8067c490ab896cf -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412168] Add feedback after scanning for faces
https://bugs.kde.org/show_bug.cgi?id=412168 --- Comment #1 from caulier.gil...@gmail.com --- Git commit 05b9a534d89234b7571d5dade8067c490ab896cf by Gilles Caulier. Committed on 26/12/2019 at 17:30. Pushed by cgilles into branch 'master'. Faces Workflow simplication and improvements: remove face scan dialog and embed Face scan settings in People left sidebar. disable settings view while a face job is running. Catch face detector tool complete/cancelled signal to re-enable settings view. By this way, this will prevent to run 2 concurrent face jobs at the same time. Related: bug 398376, bug 380336 M +45 -31 core/app/views/sidebar/leftsidebarwidgets.cpp M +1-0core/app/views/sidebar/leftsidebarwidgets.h M +1-1core/utilities/facemanagement/CMakeLists.txt R +15 -45 core/utilities/facemanagement/widgets/facescanwidget.cpp [from: core/utilities/facemanagement/widgets/facescandialog.cpp - 089% similarity] R +9-11 core/utilities/facemanagement/widgets/facescanwidget.h [from: core/utilities/facemanagement/widgets/facescandialog.h - 079% similarity] R +8-11 core/utilities/facemanagement/widgets/facescanwidget_p.h [from: core/utilities/facemanagement/widgets/facescandialog_p.h - 090% similarity] M +1-1core/utilities/maintenance/facesdetector.cpp M +3-3core/utilities/maintenance/facesdetector.h M +1-0core/utilities/maintenance/maintenancetool.cpp M +11 -3core/utilities/maintenance/maintenancetool.h https://invent.kde.org/kde/digikam/commit/05b9a534d89234b7571d5dade8067c490ab896cf -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 380336] Suggested improvements of Face Tagging
https://bugs.kde.org/show_bug.cgi?id=380336 --- Comment #6 from caulier.gil...@gmail.com --- Git commit 05b9a534d89234b7571d5dade8067c490ab896cf by Gilles Caulier. Committed on 26/12/2019 at 17:30. Pushed by cgilles into branch 'master'. Faces Workflow simplication and improvements: remove face scan dialog and embed Face scan settings in People left sidebar. disable settings view while a face job is running. Catch face detector tool complete/cancelled signal to re-enable settings view. By this way, this will prevent to run 2 concurrent face jobs at the same time. Related: bug 398376, bug 412168 M +45 -31 core/app/views/sidebar/leftsidebarwidgets.cpp M +1-0core/app/views/sidebar/leftsidebarwidgets.h M +1-1core/utilities/facemanagement/CMakeLists.txt R +15 -45 core/utilities/facemanagement/widgets/facescanwidget.cpp [from: core/utilities/facemanagement/widgets/facescandialog.cpp - 089% similarity] R +9-11 core/utilities/facemanagement/widgets/facescanwidget.h [from: core/utilities/facemanagement/widgets/facescandialog.h - 079% similarity] R +8-11 core/utilities/facemanagement/widgets/facescanwidget_p.h [from: core/utilities/facemanagement/widgets/facescandialog_p.h - 090% similarity] M +1-1core/utilities/maintenance/facesdetector.cpp M +3-3core/utilities/maintenance/facesdetector.h M +1-0core/utilities/maintenance/maintenancetool.cpp M +11 -3core/utilities/maintenance/maintenancetool.h https://invent.kde.org/kde/digikam/commit/05b9a534d89234b7571d5dade8067c490ab896cf -- 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 Summary|Scrollbar set to 'hidden' |Scrollbar set to 'hidden' |reappears sometimes when|reappears when scrolling |zooming then scrolling |twice via touchpad -- 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 #2 from Ferdinand B --- EDIT: the bug doesn't seem to have anything to do with zooming. New reproducing Testcase: STEPS TO REPRODUCE 1. open konsole 2. set scrollbar to 'hidden' 3. get some lines into the scroll buffer (e.g. `yes | head -n100`) 4. scroll a bit (using the touchpad) 5. stop scrolling 6. scroll a bit (using the touchpad) 7. scrollbar appears on the left side of the window -- 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 #3 from Ferdinand B --- Tested different scroll methods: - via Shift+Up, Shift+PgUp -- works as intended - via Mouse Wheel -- works as intended - via Touchṕad Two-Finger scroll -- scrollbar appears unexpectedly -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415332] Okular does not show the dialogue to let me load a file
https://bugs.kde.org/show_bug.cgi?id=415332 Albert Astals Cid changed: What|Removed |Added CC||j...@jriddell.org, ||sit...@kde.org --- Comment #7 from Albert Astals Cid --- I'm not involved in the snap creation nor have access to a snap based system. Adding a few people that may care. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415332] [Snap] Okular does not show the dialogue to let me load a file
https://bugs.kde.org/show_bug.cgi?id=415332 Albert Astals Cid changed: What|Removed |Added Summary|Okular does not show the|[Snap] Okular does not show |dialogue to let me load a |the dialogue to let me load |file|a file -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415586] Remove online account
https://bugs.kde.org/show_bug.cgi?id=415586 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 415267 *** -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 415267] Completely disfunctional dialog in 19.12
https://bugs.kde.org/show_bug.cgi?id=415267 Antonio Rojas changed: What|Removed |Added CC||andysardin...@gmail.com --- Comment #3 from Antonio Rojas --- *** Bug 415586 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 aldo...@gmail.com changed: What|Removed |Added CC||aldo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415587] New: Plasmoid review elements leave popover
https://bugs.kde.org/show_bug.cgi?id=415587 Bug ID: 415587 Summary: Plasmoid review elements leave popover Product: Discover Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: squeakypanca...@disroot.org CC: aleix...@kde.org Target Milestone: --- Created attachment 124728 --> https://bugs.kde.org/attachment.cgi?id=124728&action=edit Plasmoid screenshot SUMMARY Review popover elements for plasmoids do not flex with the popover. STEPS TO REPRODUCE 1. Open discover 2. Select an installed plasmoid 3. Click review 4. Resize discover OBSERVED RESULT Text, input boxes, and buttons will leave the popover if the window is too narrow. EXPECTED RESULT All elements in the popover should stay in the popover like they do for application reviews. 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.
[Discover] [Bug 415587] Plasmoid review elements leave popover
https://bugs.kde.org/show_bug.cgi?id=415587 --- Comment #1 from Squeaky Pancakes --- Created attachment 124729 --> https://bugs.kde.org/attachment.cgi?id=124729&action=edit App screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415310] No thumbnails for bottom screen in pager
https://bugs.kde.org/show_bug.cgi?id=415310 Ian Pilcher changed: What|Removed |Added CC||arequip...@gmail.com --- Comment #3 from Ian Pilcher --- Created attachment 124730 --> https://bugs.kde.org/attachment.cgi?id=124730&action=edit Patch that reverts pager to 5.16.5 version Seeing the same thing (also on Fedora 31). The attached patch, which reverts the pager to the 5.16.5 version, "fixes" the issue. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415214] Error bar stretch too much in a log plot.
https://bugs.kde.org/show_bug.cgi?id=415214 Alexander Semke changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||labplot/commit/9572427432b7 ||9a89d8adc69778aaf55e18ac3c5 ||7 Resolution|--- |FIXED Version Fixed In||2.8 Status|CONFIRMED |RESOLVED --- Comment #2 from Alexander Semke --- Git commit 9572427432b79a89d8adc69778aaf55e18ac3c57 by Alexander Semke. Committed on 26/12/2019 at 19:23. Pushed by asemke into branch 'master'. Better algorithm to draw the error bar caps - don't convert the size of the error bar caps to logical units, determine the anchor points (end points of error bars) and draw the bar caps in scene coordinates relativ to the anchor points. FIXED-IN: 2.8 M +35 -63 src/backend/worksheet/plots/cartesian/XYCurve.cpp https://invent.kde.org/kde/labplot/commit/9572427432b79a89d8adc69778aaf55e18ac3c57 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412697] Meta+L keyboard shortcut to lock screen
https://bugs.kde.org/show_bug.cgi?id=412697 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Nate Graham --- Actually, I completely forgot that I already implemented this earlier in the year: https://phabricator.kde.org/D20178 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415588] New: Global menu is causing Plasma Shell to crash
https://bugs.kde.org/show_bug.cgi?id=415588 Bug ID: 415588 Summary: Global menu is causing Plasma Shell to crash Product: plasmashell Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: techxga...@outlook.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM GPU: GTX 1060 (435.21) -- Information about the crash: Tried to open menus from the global menu. It'll cause Plasma shell to freeze The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fddadad8300 (LWP 8613))] Thread 15 (Thread 0x7fdd5e8a6700 (LWP 8670)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f66787a5c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f66787a570, cond=0x55f66787a598) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f66787a598, mutex=0x55f66787a570) at pthread_cond_wait.c:638 #3 0x7fddb13fedef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fddb13feee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fddb30b57b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fddb30b5a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fddb13f8cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fddb08a0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fddb107b323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fdd5f7fe700 (LWP 8669)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f66716fe84) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f66716fe30, cond=0x55f66716fe58) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f66716fe58, mutex=0x55f66716fe30) at pthread_cond_wait.c:638 #3 0x7fddb13fedef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fddb13feee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fddb30b57b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fddb30b5a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fddb13f8cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fddb08a0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fddb107b323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fdd5700 (LWP 8668)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f667423ed0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f667423e80, cond=0x55f667423ea8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f667423ea8, mutex=0x55f667423e80) at pthread_cond_wait.c:638 #3 0x7fddb13fedef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fddb13feee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fddb30b57b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fddb30b5a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fddb13f8cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fddb08a0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fddb107b323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fdd6d8a5700 (LWP 8667)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f666f0d340) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f666f0d2f0, cond=0x55f666f0d318) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f666f0d318, mutex=0x55f666f0d2f0) at pthread_cond_wait.c:638 #3 0x7fddb13fedef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fddb13feee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fddb30b57b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fddb30b5a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x0
[plasma-pa] [Bug 413332] Per-app raised maximum volume not remembered across reboots
https://bugs.kde.org/show_bug.cgi?id=413332 Nate Graham changed: What|Removed |Added Keywords||usability Status|REOPENED|CONFIRMED Summary|Can't raise the volume more |Per-app raised maximum |than 100% from Audio Volume |volume not remembered |Applet |across reboots -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab
https://bugs.kde.org/show_bug.cgi?id=415286 --- Comment #13 from Roman Gilg --- I tried it out now with https://phabricator.kde.org/D26216 being applied on top of master and alt-tabbing in and out of Dishonored 2 worked without problems for me in the tutorial starting area. System was an AMD RX 5700 XT, MESA (close to) master, Linux kernel 5.4.6. This was independent of me enabling that apps can block compositing or switching on/off compositing mid-game. Could you test if there are still problems for you with the above patch applied? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 413332] Can't raise the volume more than 100% from Audio Volume Applet
https://bugs.kde.org/show_bug.cgi?id=413332 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414679] plymouth-kcm-5.17.3 w/ Qt 5.14.0_beta3: kcm.cpp:54:41: error: no matching function for call to ‘qmlRegisterType()’
https://bugs.kde.org/show_bug.cgi?id=414679 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/ply ||mouth-kcm/92ffa670f0e51ed94 ||9c34fd14c7773a4ad2d0946 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Nate Graham --- Git commit 92ffa670f0e51ed949c34fd14c7773a4ad2d0946 by Nate Graham, on behalf of Peter Levine. Committed on 26/12/2019 at 20:16. Pushed by ngraham into branch 'Plasma/5.17'. Don't use qmlRegisterType with QT-5.14 Summary: Building Plymouth-kcm-5.17.3 against Qt 5.14.0_beta3 fails to build. I don't have much experience with QT/KDE programming but these changes are sufficient to fix the build error on my end. Reviewers: jriddell, #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: zzag, davidedmundson, asturmlechner, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D25624 M +6-0src/kcm.cpp https://commits.kde.org/plymouth-kcm/92ffa670f0e51ed949c34fd14c7773a4ad2d0946 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414679] plymouth-kcm-5.17.3 w/ Qt 5.14.0_beta3: kcm.cpp:54:41: error: no matching function for call to ‘qmlRegisterType()’
https://bugs.kde.org/show_bug.cgi?id=414679 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||5.17.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab
https://bugs.kde.org/show_bug.cgi?id=415286 --- Comment #14 from Roman Gilg --- (In reply to tempel.julian from comment #12) > Forgot to add: The Proton fullscreen application also freezes with KWin's > default settings when executing "kwin_x11 --replace" while the application > is running. This in contrast is still happening to me. But taking away the compositor while the game is running is quite drastic and handling that is probably not been done correctly in Proton in this case (and I don't think it's worth for them to look into fixing that). On another note: I didn't notice any performance difference between having the compositor block compositing and with full compositing still going on while in-game, what would point to the compositing rework being done right. Can you confirm? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415589] New: Se cerró la aplicación "Preferencias del sistema"
https://bugs.kde.org/show_bug.cgi?id=415589 Bug ID: 415589 Summary: Se cerró la aplicación "Preferencias del sistema" Product: systemsettings Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: root_user...@tuta.io Target Milestone: --- Application: systemsettings5 (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Esataba revisando los ajustes del "Estilo de las aplicaciones" cuando la aplicación se cerró inesperadamente. No habían más aplicaciones abiertas en primer plano. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f07b2a88800 (LWP 1974))] Thread 8 (Thread 0x7f0767bfd700 (LWP 1994)): #0 0x7f07adfae0b4 in __GI___libc_read (fd=40, buf=0x7f0767bfcb70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f07a76ac2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f07a76670b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f07a7667570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f07a76676dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f07ae905b9b in QEventDispatcherGlib::processEvents (this=0x7f076b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f07ae8a606a in QEventLoop::exec (this=this@entry=0x7f0767bfcd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f07ae6c13aa in QThread::exec (this=this@entry=0x5648cb343120) at thread/qthread.cpp:531 #8 0x7f07ac464815 in QQmlThreadPrivate::run (this=0x5648cb343120) at qml/ftw/qqmlthread.cpp:152 #9 0x7f07ae6c2b52 in QThreadPrivate::start (arg=0x5648cb343120) at thread/qthread_unix.cpp:360 #10 0x7f07a9a266db in start_thread (arg=0x7f0767bfd700) at pthread_create.c:463 #11 0x7f07adfbf88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f0779317700 (LWP 1992)): #0 0x7f07adfae0b4 in __GI___libc_read (fd=26, buf=0x7f0779316b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f07a76ac2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f07a76670b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f07a7667570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f07a76676dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f07ae905b9b in QEventDispatcherGlib::processEvents (this=0x7f076c0867e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f07ae8a606a in QEventLoop::exec (this=this@entry=0x7f0779316d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f07ae6c13aa in QThread::exec (this=this@entry=0x5648ca21c120) at thread/qthread.cpp:531 #8 0x7f07ac464815 in QQmlThreadPrivate::run (this=0x5648ca21c120) at qml/ftw/qqmlthread.cpp:152 #9 0x7f07ae6c2b52 in QThreadPrivate::start (arg=0x5648ca21c120) at thread/qthread_unix.cpp:360 #10 0x7f07a9a266db in start_thread (arg=0x7f0779317700) at pthread_create.c:463 #11 0x7f07adfbf88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f077c7fb700 (LWP 1982)): #0 0x7f07adfae077 in __GI___libc_read (fd=22, buf=0x7f077c7fab70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f07a76ac2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f07a76670b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f07a7667570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f07a76676dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f07ae905b9b in QEventDispatcherGlib::processEvents (this=0x7f0774000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f07ae8a606a in QEventLoop::exec (this=this@entry=0x7f077c7fad80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f07ae6c13aa in QThread::exec (this=this@entry=0x5648c46cfa30) at thread/qthread.cpp:531 #8 0x7f07ac464815 in QQmlThreadPrivate::run (this=0x5648c46cfa30) at qml/ftw/qqmlthread.cpp:152 #9 0x7f07ae6c2b52 in QThreadPrivate::start (arg=0x5648c46cfa30) at thread/qthread_unix.cpp:360 #10 0x7f07a9a266db in start_thread (arg=0x7f077c7fb700) at pthread_create.c:463 #11 0x7f07adfbf88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f07852cb700 (LWP 1980)): #0 0x
[dolphin] [Bug 414482] Dolphin can't create on network resources
https://bugs.kde.org/show_bug.cgi?id=414482 Nate Graham changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 CC||n...@kde.org --- Comment #6 from Nate Graham --- I can confirm this issue with my Samba share. Can't create, can't paste. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414482] Dolphin can't create on network resources
https://bugs.kde.org/show_bug.cgi?id=414482 Nate Graham changed: What|Removed |Added Severity|normal |major Status|REOPENED|CONFIRMED Priority|NOR |HI Version|unspecified |19.12 Product|dolphin |kio-extras Keywords||regression Component|general |Samba Assignee|dolphin-bugs-n...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414482] Dolphin can't create on network resources
https://bugs.kde.org/show_bug.cgi?id=414482 Nate Graham changed: What|Removed |Added CC||swagfortr...@gmail.com --- Comment #7 from Nate Graham --- *** Bug 375553 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 375553] Can't paste files into a Samba share
https://bugs.kde.org/show_bug.cgi?id=375553 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #5 from Nate Graham --- *** This bug has been marked as a duplicate of bug 414482 *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414482] Dolphin can't create on network resources
https://bugs.kde.org/show_bug.cgi?id=414482 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356768] Resizable splitters are invisible, creating not so nice UI
https://bugs.kde.org/show_bug.cgi?id=356768 Nate Graham changed: What|Removed |Added Summary|Separators are hardly |Resizable splitters are |visible and creates not so |invisible, creating not so |nice UI |nice UI Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356768] Resizable splitters are invisible, creating not so nice UI
https://bugs.kde.org/show_bug.cgi?id=356768 Nate Graham changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #6 from Nate Graham --- *** Bug 415529 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
