[digikam] [Bug 412679] Scrolling to a illogical place in the main view
https://bugs.kde.org/show_bug.cgi?id=412679 --- Comment #15 from Maik Qualmann --- disable Menu-> View-> [x] Include Album Sub-Tree Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412067] I get a error message: "Error while opening the database".
https://bugs.kde.org/show_bug.cgi?id=412067 --- Comment #2 from Maik Qualmann --- Could the problem be solved? Without further information, whether a SQLite or MySQL database is used or an output of the debug messages from the terminal we can not help. Maik -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411624] Advanced Switch button has wrong state for preferences popup
https://bugs.kde.org/show_bug.cgi?id=411624 Michail Vourlakos changed: What|Removed |Added Summary|Radio button has wrong |Advanced Switch button has |state for preferences popup |wrong state for preferences ||popup -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412940] Dock background and Rearrange button are not removed when settings panel closed
https://bugs.kde.org/show_bug.cgi?id=412940 --- Comment #6 from Michail Vourlakos --- If you click on the desktop in order for Dock Settings window to lose its focus and close itself, do you have the same issue? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413220] New: Weird connections among selected areas
https://bugs.kde.org/show_bug.cgi?id=413220 Bug ID: 413220 Summary: Weird connections among selected areas Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- Created attachment 123350 --> https://bugs.kde.org/attachment.cgi?id=123350&action=edit file SUMMARY git e444d22 https://forum.kde.org/viewtopic.php?f=288&t=162791 When selecting areas with selection tools, these unexpected lines of marching ants appear. It's not a new behaviour. It also happens with 4.2.7. STEPS TO REPRODUCE 1. Select bunch of areas with selection tools. 2. Adjust zoom level with mouse to see the connection. OBSERVED RESULT Flickery lines appear among selection areas. EXPECTED RESULT No lines. SOFTWARE/OS VERSIONS Windows: Win7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION In the attatched file, it can be seen the most often in zoom level 50, 67. Turns out it does not only happen with contiguous selection tool, and it seems the 'lines' are connected in the order you made the selection areas. I didn't manage to reproduce this with outline selection tool yet. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412679] Scrolling to a illogical place in the main view
https://bugs.kde.org/show_bug.cgi?id=412679 --- Comment #14 from Alexandre Belz --- Hello, Where can I find this setting ? I've looked there without success : - Options/Views/treeview - Misc/Behaviour/Scroll current item to the center of thumb bar has no consequence on my issue/ thanks -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413212] lattedock is unstable on wayland
https://bugs.kde.org/show_bug.cgi?id=413212 --- Comment #1 from Michail Vourlakos --- Crash report? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413126] Filter mask is so heavy
https://bugs.kde.org/show_bug.cgi?id=413126 acc4commissi...@gmail.com changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from acc4commissi...@gmail.com --- Nevermind. I'll just make do with the current way. This is not a critical problem anyway and maybe it can be addressed in another time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413219] systematic crash plasma after update to 5.17
https://bugs.kde.org/show_bug.cgi?id=413219 --- Comment #1 from Dan Joakim Eiworth --- Created attachment 123349 --> https://bugs.kde.org/attachment.cgi?id=123349&action=edit New crash information added by DrKonqi plasmashell (5.17.0) using Qt 5.13.1 - What I was doing when the application crashed: This happens without interaction, last time while playing youtube music for around 2-3h -- Backtrace (Reduced): #6 0x7f0c5b410dc0 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0c5b412a5f in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0c5b413f6a in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f0c5b414351 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f0c5b4144d9 in QSortFilterProxyModel::invalidate() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413219] systematic crash plasma after update to 5.17
https://bugs.kde.org/show_bug.cgi?id=413219 Dan Joakim Eiworth changed: What|Removed |Added CC||joa...@eiworth.net -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 413216] Mosaic tool copies FITS file to job specs, leading to incorrect alignment of mosaic captures
https://bugs.kde.org/show_bug.cgi?id=413216 --- Comment #1 from Jasem Mutlaq --- So the coordinates are used for the initial slew to the target. If a FITS file was specified, then the plate solver would perform the following: 1. Solve the FITS file. 2. Slew the mount to the solution coordinates (center of FITS file). 3. Captures and image to ensure we are at the coords in #2. Does this clears it up for you? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes in slideshow
https://bugs.kde.org/show_bug.cgi?id=413018 --- Comment #24 from akm --- Created attachment 123348 --> https://bugs.kde.org/attachment.cgi?id=123348&action=edit New crash information added by DrKonqi plasmashell (5.17.0) using Qt 5.13.1 PC was running during the night, came back in the morning and found full black screen. kstart plasmashell via yakuake gave me a running desktop back crash is also listed in systemd log Process 2352 (plasmashell) of user 1000 dumped core. Stack trace of thread 2352: #0 0x7f7d2384cd90 n/a (libQt5Core.so.5) #1 0x7f7d2385295a n/a (libQt5Core.so.5) #2 0x7f7c7d02048a n/a (libplasma_wallpaper_imageplugin.so) #3 0x7f7d238a9638 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #4 0x7f7d238a9eea _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #5 0x7f7d24435c62 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #6 0x7f7d2443f1e0 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #7 0x7f7d2387e572 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #8 0x7f7d23881208 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #9 0x7f7d238d5343 n/a (libQt5Core.so.5) #10 0x7f7d21e9f6b3 g_main_context_dispatch (libglib-2.0.so.0) #11 0x7f7d21ea1460 n/a (libglib-2.0.so.0) #12 0x7f7d21ea149f g_main_context_iteration (libglib-2.0.so.0) #13 0x7f7d238d4981 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #14 0x7f7d2387d0db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #15 0x7f7d23884d42 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #16 0x55b34c6dd206 n/a (plasmashell) #17 0x7f7d23264e0b __libc_start_main (libc.so.6) #18 0x55b34c6dd63a _start (plasmashell) -- Backtrace (Reduced): #6 0x7f0451138d90 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f045113e95a in () at /usr/lib64/libQt5Core.so.5 #8 0x7f03f9c1348a in () at /usr/lib64/qt5/qml/org/kde/plasma/wallpapers/image/libplasma_wallpaper_imageplugin.so [...] #10 0x7f0451195eea in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #11 0x7f0451d21c62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes in slideshow
https://bugs.kde.org/show_bug.cgi?id=413018 akm changed: What|Removed |Added CC||alexvk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413219] New: systematic crash plasma after update to 5.17
https://bugs.kde.org/show_bug.cgi?id=413219 Bug ID: 413219 Summary: systematic crash plasma after update to 5.17 Product: plasmashell Version: 5.17.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mixa5...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - Unusual behavior I noticed: Plasma falls at arbitrary points in time, regardless of the tasks I have launched. I noticed this behavior of the working environment after upgrading to version 5.17. On another computer of a similar configuration, but plasma 5.16.5 does not crash. The crash can be reproduced every time. -- 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 0x7f51805f9800 (LWP 1487))] Thread 4 (Thread 0x7f5162da2700 (LWP 1576)): #0 QMutex::unlock (this=this@entry=0x561e348e33a0) at thread/qmutex.cpp:335 #1 0x7f517a66e8ed in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:219 #2 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:213 #3 QThreadData::canWaitLocked (this=0x561e348e3370) at ../../include/QtCore/5.13.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:272 #4 postEventSourcePrepare (s=0x7f51580047a0, timeout=0x7f5162da1bb4) at kernel/qeventdispatcher_glib.cpp:260 #5 0x7f5173c53b28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f5173c544fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f5173c546dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f517a66e9db in QEventDispatcherGlib::processEvents (this=0x7f5158000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #9 0x7f517a60eeaa in QEventLoop::exec (this=this@entry=0x7f5162da1d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #10 0x7f517a42a3ca in QThread::exec (this=) at thread/qthread.cpp:531 #11 0x7f517def8cb5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7f517a42bb72 in QThreadPrivate::start (arg=0x561e349dace0) at thread/qthread_unix.cpp:360 #13 0x7f517735d6db in start_thread (arg=0x7f5162da2700) at pthread_create.c:463 #14 0x7f5179d2888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f5168e67700 (LWP 1538)): #0 0x7f5173c9a664 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5173c53b18 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5173c544fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5173c546dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f517a66e9db in QEventDispatcherGlib::processEvents (this=0x7f515c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f517a60eeaa in QEventLoop::exec (this=this@entry=0x7f5168e66d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f517a42a3ca in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7f517b7220e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f517a42bb72 in QThreadPrivate::start (arg=0x7f517b999d80) at thread/qthread_unix.cpp:360 #9 0x7f517735d6db in start_thread (arg=0x7f5168e67700) at pthread_create.c:463 #10 0x7f5179d2888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f516b050700 (LWP 1494)): #0 0x7f5179d1bbf9 in __GI___poll (fds=0x7f516b04fca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f517f028747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f517f02a36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f516da21f00 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f517a42bb72 in QThreadPrivate::start (arg=0x561e347f43e0) at thread/qthread_unix.cpp:360 #5 0x7f517735d6db in start_thread (arg=0x7f516b050700) at pthread_create.c:463 #6 0x7f5179d2888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f51805f9800 (LWP 1487)): [KCrash Handler] #6 0x7f517a5d7dc0 in QSortFilterProxyModelPrivate::build_source_to_proxy_mapping (proxy_to_source=..., source_to_proxy=..., this=0x561e35113fa0) at itemmodels/qsortfilterproxymodel.cpp:1184 #7 0x7f517a5dc681 in QSortFilterProxyModelPrivate::sort (this=0x561e35113fa0) at itemmodels/qso
[plasmashell] [Bug 370180] Widgets moved to secondary monitor upon reboot
https://bugs.kde.org/show_bug.cgi?id=370180 --- Comment #14 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.
[plasmashell] [Bug 370808] Screen of a 3 monitor setup "slide" on 2 of them
https://bugs.kde.org/show_bug.cgi?id=370808 --- 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.
[plasmashell] [Bug 377561] Panels switched after screen switched off
https://bugs.kde.org/show_bug.cgi?id=377561 --- Comment #13 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.
[plasmashell] [Bug 412093] [plasmashell][plasmashell_process] Multiple repetitive crashes
https://bugs.kde.org/show_bug.cgi?id=412093 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413185] Plasma 5.17 reports crash after login into wayland session
https://bugs.kde.org/show_bug.cgi?id=413185 mitch...@ferguson.geek.nz changed: What|Removed |Added CC||mitch...@ferguson.geek.nz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413185] Plasma 5.17 reports crash after login into wayland session
https://bugs.kde.org/show_bug.cgi?id=413185 --- Comment #1 from mitch...@ferguson.geek.nz --- Created attachment 123347 --> https://bugs.kde.org/attachment.cgi?id=123347&action=edit New crash information added by DrKonqi plasmashell (5.17.0) using Qt 5.13.1 - What I was doing when the application crashed: Login to wayland session - Custom settings of the application: Nvidia PC, using Kwin's EGLStreams support. -- Backtrace (Reduced): #6 0x7f10e5e56a52 in () at /usr/lib/libnvidia-egl-wayland.so.1 #7 0x7f10ecfd6183 in wl_egl_window_destroy () at /usr/lib/libwayland-egl.so.1 #8 0x7f10e657188b in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #9 0x7f10f2728aac in QWindowPrivate::setVisible(bool) () at /usr/lib/libQt5Gui.so.5 #10 0x7f10f2727ed9 in QWindowPrivate::destroy() () at /usr/lib/libQt5Gui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413218] New: Values in Redshift Configuration Popup don't center in boxes right
https://bugs.kde.org/show_bug.cgi?id=413218 Bug ID: 413218 Summary: Values in Redshift Configuration Popup don't center in boxes right Product: plasmashell Version: 5.17.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: dougjsha...@gmail.com Target Milestone: 1.0 Created attachment 123346 --> https://bugs.kde.org/attachment.cgi?id=123346&action=edit Picture of Redshift Control Settings Window SUMMARY The numbers in the text entry box for "Manual Brightness Step" in the Redshift System Tray controller don't fit properly. STEPS TO REPRODUCE 1. right click on Redshift System Tray icon 2. Click on "Configure Redshift Control OBSERVED RESULT Numbers in text entry box for "Manual Brightness Step" is cut off EXPECTED RESULT Numbers should be wholly visible. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.17.0 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 410735] Selected Zone render doesn't render
https://bugs.kde.org/show_bug.cgi?id=410735 MJ Vilches changed: What|Removed |Added Platform|Debian testing |MS Windows OS|Linux |MS Windows Version|19.04.3 |19.08.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 410735] Selected Zone render doesn't render
https://bugs.kde.org/show_bug.cgi?id=410735 MJ Vilches changed: What|Removed |Added CC||mjvilchesf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413207] plasma5 logoff and re-login hangs forever
https://bugs.kde.org/show_bug.cgi?id=413207 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from David Edmundson --- ~/.local/share/sddm/xorg-session.log please As well as what Rex says can you switch to a real VT and run ps -u between sessions -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397006] Keyboard indicator systray item does not handle multiple lock keys properly.
https://bugs.kde.org/show_bug.cgi?id=397006 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399499] Crash in makeInterleavedArrays
https://bugs.kde.org/show_bug.cgi?id=399499 --- Comment #37 from David Edmundson --- Can someone who can reproduce this run QT_LOGGING_RULES="kwin_scene_opengl.debug=true;libkwinglutils.debug=true'" kwin_x11 --replace from a terminal trigger a crash and then paste the whole output here please. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 413217] New: DetailedListView does not refresh when an entry is added to the collection from FetchDialog
https://bugs.kde.org/show_bug.cgi?id=413217 Bug ID: 413217 Summary: DetailedListView does not refresh when an entry is added to the collection from FetchDialog Product: tellico Version: 3.2.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: ro...@periapsis.org Target Milestone: --- SUMMARY The DetailedListView does not refresh (entry is in the list, but never brought into view) when an entry is added to the collection from FetchDialog. As a result EntryEditDialog is never populated with the entry data (setContents is not called). I tracked it down to DetailsListView bug fix 391614 in commit f6d89101ff95cebeb6772f7ecebd084f5b7c6b2f The complete removal of m_selectionChanging and its associated code causes this regression. Reverting this removal fixed the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413153] KWin crashed after my lockscreen crashed
https://bugs.kde.org/show_bug.cgi?id=413153 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 399499 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399499] Crash in makeInterleavedArrays
https://bugs.kde.org/show_bug.cgi?id=399499 --- Comment #36 from David Edmundson --- *** Bug 413153 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399499] Crash in makeInterleavedArrays
https://bugs.kde.org/show_bug.cgi?id=399499 David Edmundson changed: What|Removed |Added CC||mateus.naza...@yahoo.com.br --- Comment #35 from David Edmundson --- *** Bug 413214 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413214] KWin Crashes after computer is suspended
https://bugs.kde.org/show_bug.cgi?id=413214 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 399499 *** -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 413215] typo (home directory is printed where it should not be)
https://bugs.kde.org/show_bug.cgi?id=413215 Benji Dial changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||benji6...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 413169] inefficient-qlist fails on Linux x86 (32bit)
https://bugs.kde.org/show_bug.cgi?id=413169 Sergio Martins changed: What|Removed |Added Latest Commit||https://commits.kde.org/cla ||zy/6b140de078c0dc6f5e6d6732 ||512ad5e454d887d0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Sergio Martins --- Git commit 6b140de078c0dc6f5e6d6732512ad5e454d887d0 by Sergio Martins. Committed on 20/10/2019 at 00:08. Pushed by smartins into branch '1.6'. inefficient-qlist: Fix test on 32-bit platforms The warning is different. A +4-0tests/inefficient-qlist/main.cpp.expected.x86 M +5-1tests/run_tests.py https://commits.kde.org/clazy/6b140de078c0dc6f5e6d6732512ad5e454d887d0 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 413216] New: Mosaic tool copies FITS file to job specs, leading to incorrect alignment of mosaic captures
https://bugs.kde.org/show_bug.cgi?id=413216 Bug ID: 413216 Summary: Mosaic tool copies FITS file to job specs, leading to incorrect alignment of mosaic captures Product: kstars Version: 3.3.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: ja...@talkunafraid.co.uk Target Milestone: --- SUMMARY FITS file setting is propagated to mosaic jobs STEPS TO REPRODUCE 1. Open the Ekos scheduler. Enter target, search, and select a FITS file for the target 2. Create a new job 3. Use the Mosaic tool to generate a bunch of jobs 4. Run the jobs OBSERVED RESULT Plate solving uses the FITS file rather than the coordinates for each mosaic element, meaning that the mosaic produced does not in fact go to the specified coordinates for each job. EXPECTED RESULT FITS file w/ WCS or plate solved should be used as input for the centre of the mosaic for the mosaic tool *or* ignored, rather than written to the job spec for each job. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch, latest (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: N/A ADDITIONAL INFORMATION Default heartnebula-Part9 10 2.50593 62.0176 /home/james/Pictures/scope/2019-10-19/Light/H_Alpha/HeartNebula_Light_H_Alpha_300_secs_2019-10-19T21-36-44_010.fits /home/james/Pictures/scope/2019-10-19/Mosaic/heartnebula-Part9.esq ASAP MinimumAltitude EnforceTwilight Sequence Track Focus Align Guide ... n jobs heartnebula-Part1 10 2.58407 60.8758 /home/james/Pictures/scope/2019-10-19/Light/H_Alpha/HeartNebula_Light_H_Alpha_300_secs_2019-10-19T21-36-44_010.fits /home/james/Pictures/scope/2019-10-19/Mosaic/heartnebula-Part1.esq ASAP MinimumAltitude EnforceTwilight Sequence Track Focus Align Guide 0 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 413215] New: typo (home directory is printed where it should not be)
https://bugs.kde.org/show_bug.cgi?id=413215 Bug ID: 413215 Summary: typo (home directory is printed where it should not be) Product: filelight Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: martin.sandsm...@kde.org Reporter: jensen...@riseup.net Target Milestone: --- Created attachment 123345 --> https://bugs.kde.org/attachment.cgi?id=123345&action=edit picture of the typo filelight version 19.08.2 SUMMARY typo (see attached image). STEPS TO REPRODUCE 1. use filelight in a directory that has a lot of small files, and check the catch-all chunk. OBSERVED RESULT filelight prints my home directory directly before the number of files. EXPECTED RESULT Just print the number of files SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-21-generic OS Type: 64-bit Processors: 4 × AMD FX(tm)-4100 Quad-Core Processor Memory: 21.6 GiB of RAM (1600 MHz DDR3) k o --- --- /= ~ *o --- --==-//&& &~ --\/\|==GPL ~ Thanks for building Free and Open Source software! ~ *o --- --== \\&& &~ --/\/|==GPL k o --- --- \= ~ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413214] New: KWin Crashes after computer is suspended
https://bugs.kde.org/show_bug.cgi?id=413214 Bug ID: 413214 Summary: KWin Crashes after computer is suspended Product: kwin Version: 5.12.9 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mateus.naza...@yahoo.com.br Target Milestone: --- Application: kwin_x11 (5.12.9) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Everytime I suspend/lock using the shortcut (CTRL + ALT + L) or automatically after my setted time, it crashes. I've searched for people with related problems, and it seems like an old bug with NVidia cards that didn't resolve. The icons on the tray bar and the titles of icons in the desktop gets glitchy after these steps. Sometimes, I have problem with resizing windows after this. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a9467ecc0 (LWP 2030))] Thread 5 (Thread 0x7f0a61123700 (LWP 3813)): #0 0x7f0a94003cf6 in __GI_ppoll (fds=0x7f0a54001938, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0a91405651 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0a91406d6e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0a913ae9fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0a911cd23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0a8bb556f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f0a911d217d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0a8d0696db in start_thread (arg=0x7f0a61123700) at pthread_create.c:463 #8 0x7f0a9401088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f0a60922700 (LWP 2170)): #0 0x7f0a8d06f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f0a90606fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0a8d06f9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f0a90606f68, cond=0x7f0a90606f90) at pthread_cond_wait.c:502 #2 0x7f0a8d06f9f3 in __pthread_cond_wait (cond=0x7f0a90606f90, mutex=0x7f0a90606f68) at pthread_cond_wait.c:655 #3 0x7f0a903105f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f0a90310639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f0a8d0696db in start_thread (arg=0x7f0a60922700) at pthread_create.c:463 #6 0x7f0a9401088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0a71c9b700 (LWP 2165)): #0 0x7f0a911d3873 in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f0a91407015 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0a913ae9fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0a911cd23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0a8bb556f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7f0a911d217d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0a8d0696db in start_thread (arg=0x7f0a71c9b700) at pthread_create.c:463 #7 0x7f0a9401088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0a73fff700 (LWP 2125)): #0 0x7f0a94003cf6 in __GI_ppoll (fds=0x7f0a6c00ecc8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0a91405651 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0a91406d6e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0a913ae9fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0a911cd23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0a8aa2ed45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f0a911d217d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0a8d0696db in start_thread (arg=0x7f0a73fff700) at pthread_create.c:463 #8 0x7f0a9401088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f0a9467ecc0 (LWP 2030)): [KCrash Handler] #6 0x7f0a90b7d2af in KWin::WindowQuadList::makeInterleavedArrays(unsigned int, KWin::GLVertex2D*, QMatrix4x4 const&) const
[kscreensaver] [Bug 329076] Unable to unlock, widgets missing
https://bugs.kde.org/show_bug.cgi?id=329076 Wolfgang Bauer changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #16 from Wolfgang Bauer --- (In reply to Arnaud Frézet from comment #15) > i think the issue is not fixed or has reappeared recently. I had the same > issue on KDE Neon 18.04 KDE 5.17. Please file a new bug report then. This one was about KDE4 and has been fixed years ago. The code is not even close to being similar anymore. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 413213] New: Columns have no context menu
https://bugs.kde.org/show_bug.cgi?id=413213 Bug ID: 413213 Summary: Columns have no context menu Product: juk Version: 18.12.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: aspotas...@gmail.com CC: mp...@kde.org Target Milestone: --- SUMMARY Columns have no context menu. The handbook says "You can hide or unhide columns by &RMB; clicking on a column header, and clicking on the name of the column to change". However this is wrong: nothing happens if the click on a column with right mouse button. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412176] Unable to arrange devices in sidebar
https://bugs.kde.org/show_bug.cgi?id=412176 --- Comment #3 from Rajinder Yadav --- I have version 18.12.3, the problem still exist. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413212] New: lattedock is unstable on wayland
https://bugs.kde.org/show_bug.cgi?id=413212 Bug ID: 413212 Summary: lattedock is unstable on wayland Product: lattedock Version: 0.9.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: m...@rainer-finke.de Target Milestone: --- I use lattedock instead of the plasma panel as it decouples the panel from plasmashell and on Wayland my desktop is more stable thanks to this. However lattedock is crashing from time to time, usually it can restart but not always. I'm not sure what exactly is the root cause (sometimes it might be an xwayland application, copying network files or even network changes). But there is no trace back. I've tried to use lattedock from git, but there was no real difference. STEPS TO REPRODUCE 1. Use lattedock on Wayland 2. It will crash after starting some apps OBSERVED RESULT lattedock will crash from time to time EXPECTED RESULT lattedock is not crashing SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.14.0 Kernel Version: 5.3.7-arch1-1-ARCH lattedock 0.9.3 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] With parabolic effect disabled, hover-zoom at 0% AND locked state, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 --- Comment #12 from Michail Vourlakos --- (In reply to andydecleyre from comment #11) > OK I don't understand the intended purpose of the lock button, but surely > the behavior reiterated in Comment 8 Question 4 is not intended, right? What > could possibly be the point of that? > > And can you please answer Question 5 (Comment 9)? You changed the title to > point out that it's possible to have parabolic effect disabled, hover-zoom > at 0%, and "unlock state," whatever that means, but I don't see how that's > possible, if parabolic effect is controlled by the lock button. Comment 7 is the best explanation I can give. For any more questions feel free to investigate the code and provide patches for future versions. The thing is that the implementation is doing exactly what I am thinking as the best approach so this is not a bug. For anyone interested to contribute and improve things, no problem from me. The code in question can be investigated at file, https://github.com/KDE/latte-dock/blob/master/containment/package/contents/ui/applet/AppletItem.qml -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 412719] crash when changing histogram to log scale
https://bugs.kde.org/show_bug.cgi?id=412719 --- Comment #3 from sprinkl...@me.com --- I still cannot change the histogram in the fits view to log scale without kstars crashing please help -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413124] KDE Connect won't connect.
https://bugs.kde.org/show_bug.cgi?id=413124 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413207] plasma5 logoff and re-login hangs forever
https://bugs.kde.org/show_bug.cgi?id=413207 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com --- Comment #1 from Rex Dieter --- I'd encourage you to consider setting KillUserProcesses=yes in /etc/systemd/logind.conf to ensure no lingering processes from your previous session are still running after you logout. This has been a primary cause for the symptom(s) you describe in my experience. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 413211] New: Wired connection default settings are misleading
https://bugs.kde.org/show_bug.cgi?id=413211
Bug ID: 413211
Summary: Wired connection default settings are misleading
Product: plasma-nm
Version: master
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: editor
Assignee: jgrul...@redhat.com
Reporter: dmitriyval...@gmail.com
Target Milestone: ---
SUMMARY
Settings editor applet shows and saves hardcoded default ethernet settings for
connections without negotioation/speed/duplex explicitly saved. It leads to
saving connections with implicit (autonegotiation => auto 1Gb/s Full) as
explicit (no auto negotiation 100Mb/s Half).
STEPS TO REPRODUCE
1. Stop NetworkManager
2. Remove all wired connections in /etc/NetowrkManager/system-connections
(replicates clear distribution installation
3. Start NetowrkManager
4. Ensure you have a wired connections
5. Check connection settings via ethtool
6. Edit anything (e.g. DNS/VPN) in the newly created connection settings
7. Save settings
8. Disconnect and reconnect ethernet (via UI/CLI/physically)
OBSERVED RESULT
Connection become 100 Mb/s Half duplex no auto negotiation
EXPECTED RESULT
Connection stay whatever it was (presumably autonegotiation => auto 1Gb/s Full)
SOFTWARE/OS VERSIONS
Linux: 4.15+ (presumably any)
Distribution: OpenSUSE, Arch, Fedora (presumably any)
KDE Plasma Version: 5.16/5.17 (presumably any)
NetworkManager: 1.18/1.20
Hardware: r8169/e1000e NIC (including qemu and virtualbox) (presumably any)
ADDITIONAL INFORMATION
Bug comes from interpreting {speed: 0, duplex: UnknownDuplex} at
libs/editor/settings/wiredconnectionwidget.cpp:63
(WiredConnectionWidget::loadConfig) as HalfDuplex 100 Mb/s from hardcoded
defaults.
SEVERITY
Note, that ANY change of ANY implicitly created wired connection on ANY stock
system leads to switching from default ethernet settings to rare and unexpected
mode for virtually no reason. This behaviour is obscure and may turn regular
users ot from using Linux/KDE due to slower "Internet"
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 400433] After visiting 'Trash' folder, it is difficult to select 'Preview' mode (remains in 'Thumbnails' mode)
https://bugs.kde.org/show_bug.cgi?id=400433 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||6.4.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/01e007aeef12 ||5ae102e74dc6384bf37142f1fc1 ||b --- Comment #3 from Maik Qualmann --- Git commit 01e007aeef125ae102e74dc6384bf37142f1fc1b by Maik Qualmann. Committed on 19/10/2019 at 21:06. Pushed by mqualmann into branch 'master'. fix preview mode after trash view FIXED-IN: 6.4.0 M +2-1NEWS M +1-0core/app/views/stack/itemiconview.cpp https://invent.kde.org/kde/digikam/commit/01e007aeef125ae102e74dc6384bf37142f1fc1b -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408283] New icons for new Okular annotation toolbar
https://bugs.kde.org/show_bug.cgi?id=408283
Rafael Brandmaier changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest Commit||https://commits.kde.org/bre
||eze-icons/36993fdded8848204
||8a0865a4dcc85a00eeea13a
Version Fixed In||5.64
Resolution|--- |FIXED
--- Comment #14 from Rafael Brandmaier ---
Git commit 36993fdded88482048a0865a4dcc85a00eeea13a by Rafael Brandmaier.
Committed on 19/10/2019 at 21:03.
Pushed by trickyricky into branch 'master'.
Add edit-opacity icons
Summary:
This patch adds edit-opacity icons requested by Okular for D15580.
I'm not quite sure about the naming, and even if the Qt SVG renderer can handle
this transparency. I also considered a style with a checkerboard pattern, which
is the symbol for transparency e.g. in GIMP, but I felt this is not
recognizable enough to most people. If you search for a opacity/transparency
icon, you often find something with two overlapping circles, however I think
that would be too close to our path-intersection etc. icons.
I think this should be the last icon needed for
https://bugs.kde.org/show_bug.cgi?id=408283, so I'm tagging this as closing
that bug.
FIXED-IN: 5.64
Test Plan:
The new `edit-opacity` icons:
{F7624384}
Reviewers: #vdg, ngraham, ndavis
Reviewed By: #vdg, ngraham, ndavis
Subscribers: ndavis, ngraham, kde-frameworks-devel
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D24753
A +5-0icons-dark/actions/16/edit-opacity.svg
A +5-0icons-dark/actions/22/edit-opacity.svg
A +5-0icons/actions/16/edit-opacity.svg
A +5-0icons/actions/22/edit-opacity.svg
https://commits.kde.org/breeze-icons/36993fdded88482048a0865a4dcc85a00eeea13a
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 413210] New: Falkon Browser Bookmarks toolbar shows erratic names
https://bugs.kde.org/show_bug.cgi?id=413210 Bug ID: 413210 Summary: Falkon Browser Bookmarks toolbar shows erratic names Product: Falkon Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kappcl...@yahoo.com Target Milestone: --- SUMMARY Bookmarks toolbar does not show all characters in bookmark STEPS TO REPRODUCE 1. Open Falkon Browser 2. Goto Bookmarks toolbar 3. enter the name of the bookmark - no predictable result of what shows up on Bookmarks toolbar OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 413209] New: Kwin Virtual Desktop Reactivation Delay does not activate when using mouse, edge switching
https://bugs.kde.org/show_bug.cgi?id=413209 Bug ID: 413209 Summary: Kwin Virtual Desktop Reactivation Delay does not activate when using mouse, edge switching Product: frameworks-kwindowsystem Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: danielscan...@hotmail.com Target Milestone: --- SUMMARY It seems that kde has been bugged for a while, and the reactivation delay does not actually do anything when returning to a desktop. I've tried configuring this differently on 3 kde setups, one today on 19.10. All suffer from this issue, even the LTS installs. I keep my compositor speed low, but I've tested that to see if it is an issue. For example: Desktop 1: Time it takes to switch to Desktop 2 on screen edge, 350ms (set in options to 350ms) Desktop 2: Time it takes to switch to Desktop 1 on screen edge, 1ms (set in options to 400ms) When returning from a desk STEPS TO REPRODUCE 1. Enable switch desktop on edge in screen edges 2. Set activation delay to 300ms or 900, or any. 3. Reactivation delay is always set > activation 4. Create a second desktop 5. Switch between them with mouse 6. For a greater effect, turn desktop wrap on. OBSERVED RESULT The mouse will return to your primary desktop instantly after you move to your second one, without the expected reactivation delay. No delay is observed. EXPECTED RESULT You expect to have a reactivation delay so that your cannot flick between desktops so easily. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413208] New: Transform tool deleted parts of drawing
https://bugs.kde.org/show_bug.cgi?id=413208 Bug ID: 413208 Summary: Transform tool deleted parts of drawing Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: mcmarkusthegr...@gmail.com Target Milestone: --- SUMMARY After using the transform tool on a group, one layer got a chunk of it deleted. Krita crashed after saving and upon reopening the file, the layer seemed to be permanently affected. STEPS TO REPRODUCE 1. 3000x3000 canvas , 300ppi 2. Transform tool on group 3. crash OBSERVED RESULT half of the drawing deleted, krita crashes EXPECTED RESULT transform SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] With parabolic effect disabled, hover-zoom at 0% AND locked state, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 --- Comment #11 from andydecle...@gmail.com --- OK I don't understand the intended purpose of the lock button, but surely the behavior reiterated in Comment 8 Question 4 is not intended, right? What could possibly be the point of that? And can you please answer Question 5 (Comment 9)? You changed the title to point out that it's possible to have parabolic effect disabled, hover-zoom at 0%, and "unlock state," whatever that means, but I don't see how that's possible, if parabolic effect is controlled by the lock button. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411181] F4 no longer moves keyboard focus to Konsole panel after it's been opened and closed at least once
https://bugs.kde.org/show_bug.cgi?id=411181 k...@jotomo.de changed: What|Removed |Added CC||k...@jotomo.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413207] plasma5 logoff and re-login hangs forever
https://bugs.kde.org/show_bug.cgi?id=413207 Colin J Thomson changed: What|Removed |Added CC||colin.thom...@g6avk.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391590] Sometimes plasma does not show notifications (from Dolphin and Ark, for example)
https://bugs.kde.org/show_bug.cgi?id=391590 --- Comment #5 from Patrick Silva --- (In reply to Patrick Silva from comment #4) > (In reply to Méven Car from comment #3) > > Does this still occurs ? > > > Plasma does not show a notification from Ark after I compress a 2.2 jpg file > to tar.gz format, but it does after I compress a 5.7 jpg file. > Sorry, I meant 2.2 MiB jpg file and 5.7 MiB jpg file. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400433] After visiting 'Trash' folder, it is difficult to select 'Preview' mode (remains in 'Thumbnails' mode)
https://bugs.kde.org/show_bug.cgi?id=400433 Nicofo changed: What|Removed |Added Version|6.0.0 |6.3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413147] Pictures missing from thumbnail view of album
https://bugs.kde.org/show_bug.cgi?id=413147 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||6.4.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 413198] Changes to GTK Application Style require logout
https://bugs.kde.org/show_bug.cgi?id=413198 --- Comment #2 from Alexander Ewering --- (In reply to Björn Feber from comment #1) > (In reply to Alexander Ewering from comment #0) > > Also, I thought I had understood from the release notes that changes to the > > "Global Theme" should now apply that theme to the GTK Application Style > > settings AUTOMATICALLY as well, which it doesn't seem to do either. > > Only the color scheme. OK. Anyway, the first half of the report is still occuring here... i.e. I have to log out and back in for GTK applications (even newly launched ones) to use the new GTK themes selected in System Settings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413206] File did not save even though in the system info it says it did
https://bugs.kde.org/show_bug.cgi?id=413206 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Boudewijn Rempt --- That is the autosave file, which is hidden by default (since it starts with a dot). You need to enable show hidden files to see it, and rename it to something else. This log line does not show that Conner.jpg was saved. Please check https://docs.krita.org/en/user_manual/autosave.html to learn about autosaving. One other thing: do not use jpeg as your working format, it's lossy. Use .kra files. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413189] Status bar text not correct in Trash view
https://bugs.kde.org/show_bug.cgi?id=413189 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/c8dda138db48 ||ddf1cc4aefd33451fb8ca9513e1 ||a Version Fixed In||6.4.0 Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- Git commit c8dda138db48ddf1cc4aefd33451fb8ca9513e1a by Maik Qualmann. Committed on 19/10/2019 at 19:09. Pushed by mqualmann into branch 'master'. add simple status bar text for the trash view FIXED-IN: 6.4.0 M +2-1NEWS M +5-0core/app/main/digikamapp.cpp M +1-0core/app/main/digikamapp.h M +3-0core/app/main/digikamapp_setup.cpp M +4-0core/app/views/stack/itemiconview.cpp M +1-0core/app/views/stack/itemiconview.h M +26 -0core/app/views/stack/trashview.cpp M +5-0core/app/views/stack/trashview.h https://invent.kde.org/kde/digikam/commit/c8dda138db48ddf1cc4aefd33451fb8ca9513e1a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413157] Warp mode anchor point laggy respond
https://bugs.kde.org/show_bug.cgi?id=413157 --- Comment #2 from grzegorzpedr...@o2.pl --- Thanks ! Hope it wont be difficult to fix -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413207] New: plasma5 logoff and re-login hangs forever
https://bugs.kde.org/show_bug.cgi?id=413207 Bug ID: 413207 Summary: plasma5 logoff and re-login hangs forever Product: plasmashell Version: 5.17.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: slartibar...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Hi, since plasma 5.16.x and 5.17.0 (using zawertun copr repo) on fedora30 i very often encounter problems when leaving (using logout) and re-login to plasma. In 5.16.x i could simply try systemctl restart sddm.service and re-login successfully. Sometimes an additional 'killall -u ' was necessary followed by sddm-restart in a separate root-vterm. The sysmptoms are: sddm accepts your password, then the screen goes black with the rotating spinner and the kde/plasma logo in the middle. Normally, the screen flickers once, then the login succeeds and plasma desktop is available. When it 'hangs', the flicker is missing and the spinner just goes away, the logo is also gone, just the mouse cursor remains on a black screen. No desktop whatsoever, though... Since 5.17.0, all is way quicker - even the error situation :-)) But, here a new 'quality' occurrs: plasma does not even clear the screen, the sddm-login with the breeze background picture is still visible, but the password is greyed out (similar to the 'wrong password' situation, but never returning nor loading your desktop) So, here it helps to (using root-vterm) kill the current Xorg process, killall -u , systemctl restart sddm.service If you're lucky, then, after a new login-try, your desktop appears again. Sometimes though, not immediately, it takes way more time for plasma to 'think this over' and give you access to your desktop... i didn't find anything particularly interesting in dmesg/xorg.log, maybe other logs are giving better info? Any help is appreciated -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpackage] [Bug 350148] plasmashell wants "metadata.desktop" files in slideshow sub-directories for some reason and isn't too shy to mention it 3 times per image
https://bugs.kde.org/show_bug.cgi?id=350148 Alvaro Carroz changed: What|Removed |Added CC||alvaro.car...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpackage] [Bug 396994] plasma shell desktop wallpaper slideshow: log filling up with "No metadata file in the package"
https://bugs.kde.org/show_bug.cgi?id=396994 Alvaro Carroz changed: What|Removed |Added CC||alvaro.car...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413206] New: File did not save even though in the system info it says it did
https://bugs.kde.org/show_bug.cgi?id=413206 Bug ID: 413206 Summary: File did not save even though in the system info it says it did Product: krita Version: 4.2.7.1 Platform: unspecified OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: drobot20...@gmail.com Target Milestone: --- Created attachment 123344 --> https://bugs.kde.org/attachment.cgi?id=123344&action=edit System showing that it had saved My file which I had saved earlier today only around an hour or so ago did not save, when I checked the system information for Krita it showed that at that time it had saved my file is there any way to get my work back or is it just lost forever? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413205] New: Akonadi IMAP resource crashed after login failed
https://bugs.kde.org/show_bug.cgi?id=413205 Bug ID: 413205 Summary: Akonadi IMAP resource crashed after login failed Product: Akonadi Version: 5.12.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_imap_resource (5.12.2) Qt Version: 5.12.5 Frameworks Version: 5.63.0 Operating System: Linux 5.3.6-gentoo-r1 x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: 1. I restarted an Akonadi IMAP resource from AkonadiConsole 2. I saw a dialogue box telling me that authentication failed 3. I got a notification that the Akonadi IMAP resource had crashed -- Backtrace: Application: ProtonMail (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdef8a59ac0 (LWP 1091257))] Thread 19 (Thread 0x7fdeaa70d700 (LWP 1093819)): #0 0x7fdf0cbf23db in poll () at /lib64/libc.so.6 #1 0x7fdf0b19f11e in () at /lib64/libglib-2.0.so.0 #2 0x7fdf0b19f23f in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fdf0d22922b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fde98000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fdf0d1d2a7b in QEventLoop::exec(QFlags) (this=this@entry=0x7fdeaa70cae0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7fdf0d0327e1 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7fdf0d033891 in QThreadPrivate::start(void*) (arg=0x562dcc872550) at thread/qthread_unix.cpp:361 #7 0x7fdf0c1d84ca in start_thread () at /lib64/libpthread.so.0 #8 0x7fdf0cbfe7cf in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fdeab5ef700 (LWP 1093618)): #0 0x7fdf0cbf23db in poll () at /lib64/libc.so.6 #1 0x7fdf0b19f11e in () at /lib64/libglib-2.0.so.0 #2 0x7fdf0b19f23f in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fdf0d22922b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fdea00e2090, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fdf0d1d2a7b in QEventLoop::exec(QFlags) (this=this@entry=0x7fdeab5eeae0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7fdf0d0327e1 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7fdf0d033891 in QThreadPrivate::start(void*) (arg=0x562dcc880c70) at thread/qthread_unix.cpp:361 #7 0x7fdf0c1d84ca in start_thread () at /lib64/libpthread.so.0 #8 0x7fdf0cbfe7cf in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fded0bf9700 (LWP 1091288)): #0 0x7fdf0cbf23db in poll () at /lib64/libc.so.6 #1 0x7fdf0b19f11e in () at /lib64/libglib-2.0.so.0 #2 0x7fdf0b19f23f in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fdf0d22922b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fdea4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fdf0d1d2a7b in QEventLoop::exec(QFlags) (this=this@entry=0x7fded0bf8ae0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7fdf0d0327e1 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7fdf0d033891 in QThreadPrivate::start(void*) (arg=0x562dcc681bc0) at thread/qthread_unix.cpp:361 #7 0x7fdf0c1d84ca in start_thread () at /lib64/libpthread.so.0 #8 0x7fdf0cbfe7cf in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fded13fa700 (LWP 1091287)): #0 0x7fdf0cbf23db in poll () at /lib64/libc.so.6 #1 0x7fdf0b19f11e in () at /lib64/libglib-2.0.so.0 #2 0x7fdf0b19f23f in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fdf0d22922b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fdebb20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fdf0d1d2a7b in QEventLoop::exec(QFlags) (this=this@entry=0x7fded13f9ab0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7fdf0d0327e1 in QThread::exec() (this=this@entry=0x7fdf0e346dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7fdf0e2c0d06 in QDBusConnectionManager::run() (this=0x7fdf0e346dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7fdf0d033891 in QThreadPrivate::start(void*) (arg=0x7fdf0e346dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7f
[dolphin] [Bug 413204] [Possibly kio component][mtp] Dolphin doesn't re-read the state of the same mtp device, after reconnecting the device.
https://bugs.kde.org/show_bug.cgi?id=413204 --- Comment #1 from Jakub Strzelecki --- I have done couple of tests, it just happens randomly on reconnection, there doesn't seem to be any form of a strong pattern. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413204] New: [Possibly kio component][mtp] Dolphin doesn't re-read the state of the same mtp device, after reconnecting the device.
https://bugs.kde.org/show_bug.cgi?id=413204 Bug ID: 413204 Summary: [Possibly kio component][mtp] Dolphin doesn't re-read the state of the same mtp device, after reconnecting the device. Product: dolphin Version: 19.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kuba...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have observed as an end-user that the mtp doesn't work when reconnecting the device, restarting the application is the user-side workaround I use for now. STEPS TO REPRODUCE 1. Open dolphin. 2. Connect mtp device. (mtp mode selected) 3. Do any action. 4. Reconnect mtp device. (mtp mode selected) OBSERVED RESULT The device is there, but contents of the mtp device are empty(no sdcard, no internal storage). I have to restart dolphin to make it work. EXPECTED RESULT The device and it is contents are available without having to restart dolphin. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.3.5 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] With parabolic effect disabled, hover-zoom at 0% AND locked state, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 --- Comment #10 from Michail Vourlakos --- The lock button is used also for that specific case, a second button might would be better to exist for the case but I am not interested adding it, so the lock button is also used for the case I described earlier. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413202] dock settings crash application
https://bugs.kde.org/show_bug.cgi?id=413202 --- Comment #1 from Michail Vourlakos --- 1. Close Latte, and run from command prompt latte-dock --cc 2. The crash still happens 3. Send the crash report from kcrash please -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412152] [Wayland] cannot start session on anything other than proprietary NVIDIA drivers
https://bugs.kde.org/show_bug.cgi?id=412152 --- Comment #20 from alg...@aaathats3as.com --- Well then the missing question is what is up with the people not having an AMD gpu. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413197] Export to Onedrive > Create New Album: improvement when adding album
https://bugs.kde.org/show_bug.cgi?id=413197 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/e5b5f0a478a6 ||1408e4169d789de9e68c43f344a ||b Version Fixed In||6.4.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- Git commit e5b5f0a478a61408e4169d789de9e68c43f344ab by Maik Qualmann. Committed on 19/10/2019 at 17:35. Pushed by mqualmann into branch 'master'. select created album in the OneDrive plugin FIXED-IN: 6.4.0 M +2-1NEWS M +3-3core/dplugins/generic/webservices/onedrive/odwindow.cpp https://invent.kde.org/kde/digikam/commit/e5b5f0a478a61408e4169d789de9e68c43f344ab -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413203] New: Some notifications don't disappear after timeout
https://bugs.kde.org/show_bug.cgi?id=413203 Bug ID: 413203 Summary: Some notifications don't disappear after timeout Product: plasmashell Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: mue...@fribbledom.com CC: plasma-b...@kde.org Target Milestone: 1.0 Some notifications remain visible, even though the timeout has elapsed. Hovering the notification with the mouse restarts the timer (and the vertical progress bar), but the notification won't disappear until I manually dismiss it, clicking the red X-button. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413202] New: dock settings crash application
https://bugs.kde.org/show_bug.cgi?id=413202 Bug ID: 413202 Summary: dock settings crash application Product: lattedock Version: 0.9.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: albertzubkow...@gmail.com Target Milestone: --- SUMMARY Latte crashed few second after opening dock settings STEPS TO REPRODUCE 1. Install Latte 2. Run Latte 3. Open dock settings OBSERVED RESULT Here's the output when running latte-dock --replace --debug in terminal: https://pastebin.com/AS62c7Hr SOFTWARE/OS VERSIONS Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.0.0-31-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 15,5 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export files with more as 4 MB to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 --- Comment #2 from Maik Qualmann --- The OneDrive plugin uses the "Simple item upload" API. File size is 4MB maximum for videos and images. Support for the "Resumable item upload" API requires more work. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export files with more as 4 MB to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 --- Comment #1 from Maik Qualmann --- *** Bug 413199 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export files with more as 4 MB to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Summary|Cannot export "a lot" of|Cannot export files with |pictures to OneDrive|more as 4 MB to OneDrive -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 408981] fails to start without proper Microsoft Visual C++ Redistributable ("missing MSVCR120.dll" error), Windows dependency neither verified nor documented
https://bugs.kde.org/show_bug.cgi?id=408981
Filipus Klutiero changed:
What|Removed |Added
Summary|fails to start without |fails to start without
|proper Microsoft Visual C++ |proper Microsoft Visual C++
|Redistributable ("missing |Redistributable ("missing
|MSVCR120.dll" error), |MSVCR120.dll" error),
|dependency neither verified |Windows dependency neither
|nor documented |verified nor documented
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 413199] Error when exporting a video to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413199 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 413196 *** -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 408981] fails to start without proper Microsoft Visual C++ Redistributable ("missing MSVCR120.dll" error), dependency neither verified nor documented
https://bugs.kde.org/show_bug.cgi?id=408981
Filipus Klutiero changed:
What|Removed |Added
Summary|missing MSVCR120.dll|fails to start without
||proper Microsoft Visual C++
||Redistributable ("missing
||MSVCR120.dll" error),
||dependency neither verified
||nor documented
CC||chea...@gmail.com
--- Comment #4 from Filipus Klutiero ---
I confirm the issue. I also confirm the solution of installing Microsoft Visual
C++ 2013 Redistributable. Even though I have one machine without the 2013
version where Falkon works (it has 2005, 2008, 2010, 2012 and 2015, but
installing both 2012 and 2015 did not suffice). Despite a mistaken article I
found on the Internet, the "12" in the filename does not represent 2012, but
version 12, which is 2013.
Please upgrade this ticket's Importance to either major or grave. As a point of
comparison, Debian policy makes unenforced absolute dependencies grave bugs.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 413199] Error when exporting a video to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413199 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- The OneDrive plugin uses the "Simple item upload" API. File size is 4MB maximum for videos and images. Support for the "Resumable item upload" API requires more work. Maik -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 413198] Changes to GTK Application Style require logout
https://bugs.kde.org/show_bug.cgi?id=413198 Björn Feber changed: What|Removed |Added CC||bfe...@protonmail.com --- Comment #1 from Björn Feber --- (In reply to Alexander Ewering from comment #0) > Also, I thought I had understood from the release notes that changes to the > "Global Theme" should now apply that theme to the GTK Application Style > settings AUTOMATICALLY as well, which it doesn't seem to do either. Only the color scheme. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 413183] confusing Login-screen SDDM in System settings
https://bugs.kde.org/show_bug.cgi?id=413183 Björn Feber changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Björn Feber --- Can confirm. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 413183] confusing Login-screen SDDM in System settings
https://bugs.kde.org/show_bug.cgi?id=413183 Björn Feber changed: What|Removed |Added CC||bfe...@protonmail.com Resolution|UPSTREAM|--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413199] Error when exporting a video to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413199 --- Comment #1 from Maik Qualmann --- Git commit ec7e91b41b547c03666d30c4ad7359db981af196 by Maik Qualmann. Committed on 19/10/2019 at 16:56. Pushed by mqualmann into branch 'master'. add video support up to 4MB M +1-1core/dplugins/generic/webservices/dropbox/dbtalker.cpp M +1-1core/dplugins/generic/webservices/google/gdrive/gdtalker.cpp M +1-1core/dplugins/generic/webservices/google/gphoto/gptalker.cpp M +27 -19 core/dplugins/generic/webservices/onedrive/odtalker.cpp https://invent.kde.org/kde/digikam/commit/ec7e91b41b547c03666d30c4ad7359db981af196 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413087] lockscreen broken when mediacontrols active
https://bugs.kde.org/show_bug.cgi?id=413087 sasori.n...@gmail.com changed: What|Removed |Added CC||sasori.n...@gmail.com --- Comment #1 from sasori.n...@gmail.com --- I'm having the same problem, with a core dump of kscreenlocker at the end (I woke up this morning to find the "Screen locker is broken..." message). Anyway, here are more info and my own conclusions at the end. The following tests were made with plasma 5.16.5 on a Manjaro system with the BreezeDark screen locker and VLC with a media loaded (playing or paused). It does the same with Clementine or other media players. Output of /usr/lib/kscreenlocker_greet --testing /usr/lib/kscreenlocker_greet --testing OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Desktop OpenGL version string: 3.0 Mesa 19.2.1 OpenGL shading language version string: 1.30 Driver: Intel GPU class: Haswell OpenGL version: 3.0 GLSL version: 1.30 Mesa version: 19.2.1 Linux kernel version: 5.3.6 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:59: TypeError: Property 'setAction' of object ScreenLocker::WallpaperIntegration(0x5583239e9090) is not a function file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:59: TypeError: Property 'setAction' of object ScreenLocker::WallpaperIntegration(0x5583239e9090) is not a function Locked at 1571501528 UdevQt: unable to create udev monitor connection Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/SessionManagementScreen.qml:64:5: Unable to assign [undefined] to int file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/ActionButton.qml:33:5: Unable to assign [undefined] to int file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/KeyboardLayoutButton.qml:29:5: Unable to assign [undefined] to int file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/Battery.qml:48:9: Unable to assign [undefined] to double file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/SessionManagementScreen.qml:64:5: Unable to assign [undefined] to int file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/ActionButton.qml:33:5: Unable to assign [undefined] to int file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/KeyboardLayoutButton.qml:29:5: Unable to assign [undefined] to int file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/Battery.qml:48:9: Unable to assign [undefined] to double file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:41:5: Unable to assign [undefined] to int file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:41:5: Unable to assign [undefined] to int QXcbClipboard: SelectionRequest too old QXcbClipboard: SelectionRequest too old QXcbClipboard: SelectionRequest too old QXcbClipboard: SelectionRequest too old QXcbClipboard: SelectionRequest too old QXcbClipboard: SelectionRequest too old file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MediaControls.qml:96:9: QML Image: Binding loop detected for property "sourceSize" # This is repeated a *lot* of times (so much I couldn't copy-paste it all, my computer started to panic) Segmentation fault (core dumped) Output of journalctl -r after the core dump oct. 19 18:12:13 spike-manjaro systemd-coredump[14640]: Process 14618 (kscreenlocker_g) of user 1000 dumped core. Stack trace of thread 14618: #0 0x7f769c8d0330 __vfprintf_internal (libc.so.6) #1 0x7f769c8d3586 buffered_vfprintf (libc.so.6) #2 0x7f769c8d0724 __vfprintf_internal (libc.so.6) #3 0x7f769c8bd19a fprintf (libc.so.6) #4 0x7f769ccd5557 n/a (libQt5Core.so.5) #5 0x7f769ccd1031 n/a (libQt5Core.so.5)
[Akonadi] [Bug 413201] New: Kmail crashes after check email
https://bugs.kde.org/show_bug.cgi?id=413201 Bug ID: 413201 Summary: Kmail crashes after check email Product: Akonadi Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: m...@blobel.com Target Milestone: --- Application: akonadiserver (5.12.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 4.12.14-lp151.28.20-default x86_64 Distribution: openSUSE Leap 15.1 -- Information about the crash: Kmail simply crashes evertime after checking emails. Kmail is simply not workable The crash can be reproduced every time. -- Backtrace (Reduced): #6 _mm_crc32_u64 (__V=, __C=) at /usr/lib64/gcc/x86_64-suse-linux/7/include/smmintrin.h:848 #7 crc32 (ptr=0x7fd2e8027b01, len=, h=) at tools/qhash.cpp:112 #8 0x7fd25c801142 in hash (seed=, len=, p=) at tools/qhash.cpp:223 #9 qHash (key=..., seed=) at tools/qhash.cpp:239 #10 0x55bac81e64db in QHash::findNode (this=this@entry=0x55baca17b758, akey=..., ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:934 Possible duplicates by query: bug 412438, bug 409403, bug 408897, bug 406185, bug 405990. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export "a lot" of pictures to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Platform|Other |Appimage -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] With parabolic effect disabled, hover-zoom at 0% AND locked state, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 --- Comment #9 from andydecle...@gmail.com --- I also see you've changed the title of this issue to change the conditions from two to three, but I don't understand that yet either. 5. What's the difference between "parabolic effect disabled" and "locked state"? I thought the lock icon was precisely the parabolic effect setting. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413050] Breeze style and scaling on Windows
https://bugs.kde.org/show_bug.cgi?id=413050 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #10 from Christoph Cullmann --- I investigated this more and this is plainly a Qt issue: https://bugreports.qt.io/browse/QTBUG-62914 They round up => that messes up the size and makes applications first "too small" and then "too large"... Given for 5.14 one can opt-in, I close this now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413199] Error when exporting a video to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413199 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Platform|Other |Appimage -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] With parabolic effect disabled, hover-zoom at 0% AND locked state, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 --- Comment #8 from andydecle...@gmail.com --- You've marked this as intentional, but I don't understand yet. 1. The lock button tooltip seems to indicate its function is to disable a zooming feature. Is that correct? 2. If a user activates the lock button because they are sure they don't want the items to exhibit any zoom effect, why does that indicate that they want the Task Manager's "Show tooltips" option to be disregarded? 3. If a user activates the lock button because they are sure they don't want the items to exhibit any zoom effect, why does that indicate that they want the Task Manager's "Highlight windows when hovering over tasks" option to be disregarded? 4. If a user activates the lock button because they are sure they don't want the items to exhibit any zoom effect, why does that indicate that they want each Task Manager's entry to be colorized permanently the first time it's clicked? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #198 from Maik Qualmann --- Git commit 27f663c1155498c03c174ce93d7c94e69d77489a by Maik Qualmann. Committed on 19/10/2019 at 16:28. Pushed by mqualmann into branch 'master'. review loading tasks Related: bug 406019 M +42 -37 core/libs/threadimageio/fileio/loadsavetask.cpp M +49 -46 core/libs/threadimageio/preview/previewtask.cpp M +1-1core/libs/threadimageio/thumb/thumbnailcreator_engine.cpp M +41 -40 core/libs/threadimageio/thumb/thumbnailtask.cpp https://invent.kde.org/kde/digikam/commit/27f663c1155498c03c174ce93d7c94e69d77489a -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406019] Corrupted image thumbnail on some pictures
https://bugs.kde.org/show_bug.cgi?id=406019 --- Comment #17 from Maik Qualmann --- Git commit 27f663c1155498c03c174ce93d7c94e69d77489a by Maik Qualmann. Committed on 19/10/2019 at 16:28. Pushed by mqualmann into branch 'master'. review loading tasks Related: bug 399923 M +42 -37 core/libs/threadimageio/fileio/loadsavetask.cpp M +49 -46 core/libs/threadimageio/preview/previewtask.cpp M +1-1core/libs/threadimageio/thumb/thumbnailcreator_engine.cpp M +41 -40 core/libs/threadimageio/thumb/thumbnailtask.cpp https://invent.kde.org/kde/digikam/commit/27f663c1155498c03c174ce93d7c94e69d77489a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412597] rotation performance issue
https://bugs.kde.org/show_bug.cgi?id=412597 --- Comment #10 from til.schmit...@gmx.de --- this might be of interest: i downgraded to krita 4.2.7.1 again and it works better with rotation on this device... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413200] New: No way to show network usage per process
https://bugs.kde.org/show_bug.cgi?id=413200 Bug ID: 413200 Summary: No way to show network usage per process Product: plasmashell Version: 5.17.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: ae@seven.systems Target Milestone: 1.0 Created attachment 123342 --> https://bugs.kde.org/attachment.cgi?id=123342&action=edit Screenshot of columns. No network usage available! >From the release notes, I understood that it should now be possible to show network usage per process. However, in the process table's column list, there is no column for network usage (see screenshot). Please forgive me if I've misunderstood the release notes! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377308] Notifications from disconnected display appear on primary display
https://bugs.kde.org/show_bug.cgi?id=377308 Szymon Łągiewka changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Szymon Łągiewka --- Setting REPORTED the Janitor asked. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 413183] confusing Login-screen SDDM in System settings
https://bugs.kde.org/show_bug.cgi?id=413183 --- Comment #2 from Paul --- Created attachment 123341 --> https://bugs.kde.org/attachment.cgi?id=123341&action=edit exclamation-mark-overlay on breeze icon theme @nate Out of curiosity I just checked on a system using the standard Breeze icon theme (breeze5-icons 5.63.0-1.1) Also appear to have an exclamation mark overlay. Operating System: openSUSE Tumbleweed 20191016 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 I'll add that I'm not using SDDM as my display manager, could that be the reason perhaps for the exclamation mark. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 413192] org-kde-powerde shows incorrect battery percentage
https://bugs.kde.org/show_bug.cgi?id=413192 --- Comment #1 from xpert45...@gmail.com --- It appears to be a upower bug. I ran upower -d after seeing the same bug (the empty battery icon, this time without a restart) and this was the result: Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Samsung SDI model:DELL P8TC727 serial: 57965 power supply: yes updated: Sat 19 Oct 2019 08:40:39 PM PKT (104 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging warning-level: none energy: 0 Wh energy-empty:0 Wh energy-full: 48.84 Wh energy-full-design: 48.84 Wh energy-rate: 0 W percentage: 0% capacity:100% After a minute or two, the battery icon changed to full and I ran upower -d again and got this: Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Samsung SDI model:DELL P8TC727 serial: 57965 power supply: yes updated: Sat 19 Oct 2019 08:42:51 PM PKT (36 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging warning-level: none energy: 47.7633 Wh energy-empty:0 Wh energy-full: 48.84 Wh energy-full-design: 48.84 Wh energy-rate: 1.6095 W voltage: 12.586 V time to full:40.1 minutes percentage: 97% capacity:100% -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 407059] [Installer] Bogus "Falkon is already running" prompt on initial installation, may abort installation
https://bugs.kde.org/show_bug.cgi?id=407059
Filipus Klutiero changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC||chea...@gmail.com
Ever confirmed|0 |1
Summary|[Installer] "Falkon is |[Installer] Bogus "Falkon
|already running", but it is |is already running" prompt
|not |on initial installation,
||may abort installation
--- Comment #1 from Filipus Klutiero ---
This happened to me on both of the Windows 10 installs on which I installed
Falkon.
Additionally:
1. The Yes/No question offers 2 possible answers: "OK" or "Cancel".
2. Choosing Cancel aborts the installation ("Setup was not completed
successfully."). To workaround, one must choose "OK".
This makes for a very bad first impression. Please upgrade this ticket's
Importance to major.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 413199] New: Error when exporting a video to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413199 Bug ID: 413199 Summary: Error when exporting a video to OneDrive Product: digikam Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-OneDrive Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY Exporting videos (mp4 in my case) to Onedrive produces the following error message: Failed to upload photo to OneDrive. Do you want to continue? STEPS TO REPRODUCE 1. Select pictures+videos to export OBSERVED RESULT 1. For each video, the error message occurs (=popup ; as a result, the export of following files is interrupted until the popup is closed) EXPECTED RESULT Video should be exported. If not possible to export videos, at least the error message should not displayed each time ! SOFTWARE/OS VERSIONS Digikam 6.3 Appimage -- You are receiving this mail because: You are watching all bug changes.
