[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 --- Comment #9 from RaitaroH --- Created attachment 115772 --> https://bugs.kde.org/attachment.cgi?id=115772&action=edit rc file7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 --- Comment #7 from RaitaroH --- Created attachment 115770 --> https://bugs.kde.org/attachment.cgi?id=115770&action=edit rc file5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 --- Comment #6 from RaitaroH --- Created attachment 115769 --> https://bugs.kde.org/attachment.cgi?id=115769&action=edit rc file4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 --- Comment #8 from RaitaroH --- Created attachment 115771 --> https://bugs.kde.org/attachment.cgi?id=115771&action=edit rc file6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 --- Comment #5 from RaitaroH --- Created attachment 115768 --> https://bugs.kde.org/attachment.cgi?id=115768&action=edit rc file3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 --- Comment #3 from RaitaroH --- Created attachment 115766 --> https://bugs.kde.org/attachment.cgi?id=115766&action=edit rc file1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 --- Comment #4 from RaitaroH --- Created attachment 115767 --> https://bugs.kde.org/attachment.cgi?id=115767&action=edit rc file2 -- 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 #9 from Maik Qualmann --- Do I understand correctly that digiKam consumes up to 7G of memory? Do you use face detection and recognition together? Maik -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 --- Comment #15 from Sergey --- Just tried another thing. Removed all the kde/plasma files I was able to find in ~/, ~/.config, ~/.local, ~/.cache. Put my laptop to sleep for whole night. In the morning it's restored properly. The only difference, previously it restored to my logged-in account, now it's kind of password-protected lock screen. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 400059] New: Muon se cierra al intentar cambiar algún icono de la aplicación
https://bugs.kde.org/show_bug.cgi?id=400059 Bug ID: 400059 Summary: Muon se cierra al intentar cambiar algún icono de la aplicación Product: muon Version: 5.8.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: albertocoll...@gmail.com CC: silh...@gmail.com Target Milestone: --- Application: muon (5.8.0) Qt Version: 5.11.1 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: Al cambiar algún icono de la barra de herramientas de Muon, se cierra la aplicación -- Backtrace: Application: Gestor de paquetes Muon (muon), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f704f9f1880 (LWP 1593))] Thread 4 (Thread 0x7f7029d67700 (LWP 1600)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67 #1 0x7f704b634be6 in __GI___poll (fds=0x7f7024004a10, nfds=1, timeout=9302) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0x7f7045f74439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7045f7454c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f704bf7da9b in QEventDispatcherGlib::processEvents (this=0x7f7024000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f704bf21dea in QEventLoop::exec (this=this@entry=0x7f7029d66d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f704bd4cb8a in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7f704bd57aab in QThreadPrivate::start (arg=0x55630c691350) at thread/qthread_unix.cpp:367 #8 0x7f7048b6f6db in start_thread (arg=0x7f7029d67700) at pthread_create.c:463 #9 0x7f704b64188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f703352f700 (LWP 1597)): #0 0x7f704b6300b4 in __GI___libc_read (fd=7, buf=0x7f703352eae0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f7045fb8a00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7045f73f27 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7045f743e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7045f7454c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f704bf7da9b in QEventDispatcherGlib::processEvents (this=0x7f702c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f704bf21dea in QEventLoop::exec (this=this@entry=0x7f703352ecf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7f704bd4cb8a in QThread::exec (this=) at thread/qthread.cpp:525 #8 0x7f704a255e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f704bd57aab in QThreadPrivate::start (arg=0x7f704a4cdd60) at thread/qthread_unix.cpp:367 #10 0x7f7048b6f6db in start_thread (arg=0x7f703352f700) at pthread_create.c:463 #11 0x7f704b64188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f703cd5f700 (LWP 1596)): #0 0x7f704b634bf9 in __GI___poll (fds=0x7f703cd5ec28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7045363747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f704536536a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f703fb5c129 in QXcbEventReader::run (this=0x55630c3f3400) at qxcbconnection.cpp:1388 #4 0x7f704bd57aab in QThreadPrivate::start (arg=0x55630c3f3400) at thread/qthread_unix.cpp:367 #5 0x7f7048b6f6db in start_thread (arg=0x7f703cd5f700) at pthread_create.c:463 #6 0x7f704b64188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f704f9f1880 (LWP 1593)): [KCrash Handler] #6 QString::mid (this=this@entry=0x55630dbd3ac8, position=35, n=n@entry=-1) at tools/qstring.cpp:4769 #7 0x7f704e72c8d9 in sortByFileName (path1=..., path2=...) at ./src/kicondialog.cpp:419 #8 0x7f704e730041 in __gnu_cxx::__ops::_Val_comp_iter::operator()::iterator> (__it=..., __val=..., this=) at /usr/include/c++/7/bits/predefined_ops.h:215 #9 std::__unguarded_linear_insert::iterator, __gnu_cxx::__ops::_Val_comp_iter > (__last=..., __comp=__comp@entry=...) at /usr/include/c++/7/bits/stl_algo.h:1828 #10 0x7f704e72e8be in std::__unguarded_insertion_sort::iterator, __gnu_cxx::__ops::_Iter_comp_iter > (__comp=..., __last=..., __first=...) at /usr/include/c++/7/bits/stl_algo.h:1867 #11 std::__final_insertion_sort::iterator, __gnu_cxx::__ops::_Iter_comp_iter > (__comp=..., __last=..., __first=...) at /usr/include/c++/7/bits/stl_algo.h:1886 #12 std::__sort::iterator, __gnu_cxx::__ops::_I
[kscreenlocker] [Bug 400058] New: kscreenlocker_greet crashes every time
https://bugs.kde.org/show_bug.cgi?id=400058 Bug ID: 400058 Summary: kscreenlocker_greet crashes every time Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: chris.che...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Upgraded neon today, there were plenty of kde related updates, and now kscreenlocker_greet crashes every time the screen is locked and causes a screen that says "loginctl unlock-session #" to unlock to appear. Rebooting, removing kde related cache files under $HOME/.cache/, etc doesn't help. STEPS TO REPRODUCE 1. Upgraded to current neon today 2. Broke OBSERVED RESULT Error screen EXPECTED RESULT Should work SOFTWARE VERSIONS (available in About System) -- THIS TEMPLATE NEEDS TO BE FIXED WHERE IS ABOUT SYETEM? KDE Plasma Version: 5.14.1-0xneon+18.04+bionic+build (various numbers) KDE Frameworks Version: 5.51.0-0xneon+18.04+bionic+build (various numbers) Qt Version: 5.11.2+dfsg-0xneon+18.04+bionic+build (various numbers) ADDITIONAL INFORMATION .xsession-errors shows the following: KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kscreenlocker_greet path = /usr/lib/x86_64-linux-gnu/libexec pid = 10400 KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --immediateLock --graceTime 5000 --ksldfd 38 UnmapNotify: 90177550 UnmapNotify: 90177553 UnmapNotify: 90177555 UnmapNotify: 90177575 CreateNotify: 90177540 Qt: Session management error: networkIdsList argument is NULL CreateNotify: 90177544 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 9004, resource id: 90177575, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 9005, resource id: 90177575, major code: 14 (GetGeometry), minor code: 0 CreateNotify: 90177549 kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" CreateNotify: 90177550 CreateNotify: 90177552 MapNotify: 90177550 kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" CreateNotify: 90177553 MapNotify: 90177553 kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" CreateNotify: 90177555 MapNotify: 90177555 kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" kf5.kpackage: No metadata file in the package, expected it at: "/media/hdd/users/ccheney/Downloads/" Udev
[krunner] [Bug 400057] New: krunner crashes when starting another app
https://bugs.kde.org/show_bug.cgi?id=400057 Bug ID: 400057 Summary: krunner crashes when starting another app Product: krunner Version: 5.14.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: ekzo.t...@gmail.com Target Milestone: --- Application: krunner (5.14.0) Qt Version: 5.11.2 Frameworks Version: 5.50.0 Operating System: Linux 4.18.13-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Krunner crashes on first run after system start when attemptin to run any app. For example, Telegram - on my system it has /opt/Telegram/Telegram -- %u path. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbf55b4b840 (LWP 3980))] Thread 25 (Thread 0x7fbf0dffb700 (LWP 6714)): #0 0x7fbf52c954dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbf5450716b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fbf36145800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fbf36149538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fbf36149592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fbf36149592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7fbf36149592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7fbf36149592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7fbf36149592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7fbf36149592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7fbf36149592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7fbf36149592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7fbf36147689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7fbf545069b7 in () at /usr/lib64/libQt5Core.so.5 #23 0x7fbf52c8f554 in start_thread () at /lib64/libpthread.so.0 #24 0x7fbf53fe2ccf in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fbf0e7fc700 (LWP 6713)): #0 0x7fbf52c954dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbf5450716b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fbf36145800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fbf36149538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fbf36149592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fbf3614490d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fbf36147689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fbf545069b7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fbf52c8f554 in start_thread () at /lib64/libpthread.so.0 #10 0x7fbf53fe2ccf in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fbf0effd700 (LWP 6712)): #0 0x7fbf52c954dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbf5450716b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fbf36145800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWea
[krunner] [Bug 400056] New: krunner crush
https://bugs.kde.org/show_bug.cgi?id=400056 Bug ID: 400056 Summary: krunner crush Product: krunner Version: 5.13.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: webdesig...@meta.ua Target Milestone: --- Application: krunner (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.18.14-200.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: press alt+f2 start typing proagramm name krunner crushes with journal message: KCrash: Attempting to start /usr/bin/krunner from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'krunner' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4d46c46940 (LWP 1745))] Thread 23 (Thread 0x7f4cbf7fe700 (LWP 3214)): #0 0x7f4d516da51c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4d55cde183 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f4d2dae2730 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f4d2dae686c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f4d2dae17c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f4d2dae4751 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f4d55cddb4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f4d516d4594 in start_thread () at /lib64/libpthread.so.0 #8 0x7f4d55013e6f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f4cc7fff700 (LWP 3213)): #0 0x7f4d516da51c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4d55cde183 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f4d2dae2730 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f4d2dae686c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f4d2dae17c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f4d2dae4751 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f4d55cddb4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f4d516d4594 in start_thread () at /lib64/libpthread.so.0 #8 0x7f4d55013e6f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f4cf4ff9700 (LWP 3212)): #0 0x7f4d516da51c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4d55cde183 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f4d2dae2730 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f4d2dae686c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f4d2dae17c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f4d2dae68ca in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f4d2dae17c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7f4d2dae68ca in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7f4d2dae17c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #9 0x7f4d2dae4751 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #10 0x7f4d55cddb4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #11 0x7f4d516d4594 in start_thread () at /lib64/libpthread.so.0 #12 0x7f4d55013e6f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f4cf57fa700 (LWP 3211)): #0 0x7f4d516da51c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so
[korganizer] [Bug 341545] Timezone offset from current timezone seems to be applied twice
https://bugs.kde.org/show_bug.cgi?id=341545 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400055] New: Don't install themes from Internet
https://bugs.kde.org/show_bug.cgi?id=400055 Bug ID: 400055 Summary: Don't install themes from Internet Product: systemsettings Version: 5.14.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: coli...@mail.ru Target Milestone: --- Application: systemsettings5 (5.14.1) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.14-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Don't install themes from Internet The crash can be reproduced every time. -- Backtrace: Application: Параметры системы (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6d4d667cc0 (LWP 6248))] Thread 15 (Thread 0x7f6cf4ff2700 (LWP 6284)): #0 0x7f6d53237c21 in poll () at /usr/lib/libc.so.6 #1 0x7f6d50e3bee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d50e3bfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d5375efe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d5370a8cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d53553eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d5355df65 in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d51aeaa9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d53242b23 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f6cf60c9700 (LWP 6282)): [KCrash Handler] #6 0x7f6d523ccca4 in () at /usr/lib/libQt5Network.so.5 #7 0x7f6d523cb59b in () at /usr/lib/libQt5Network.so.5 #8 0x7f6d53736352 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x7f6d54116e14 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f6d5411e6e1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f6d5370bc39 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f6d5370eccc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #13 0x7f6d5375f9d4 in () at /usr/lib/libQt5Core.so.5 #14 0x7f6d50e3a3cf in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #15 0x7f6d50e3bf89 in () at /usr/lib/libglib-2.0.so.0 #16 0x7f6d50e3bfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #17 0x7f6d5375efc9 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7f6d5370a8cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f6d53553eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #20 0x7f6d5355df65 in () at /usr/lib/libQt5Core.so.5 #21 0x7f6d51aeaa9d in start_thread () at /usr/lib/libpthread.so.0 #22 0x7f6d53242b23 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f6cf6a71700 (LWP 6281)): #0 0x7f6d50dea3a5 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f6d50e3b7b7 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d50e3be06 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d50e3bfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f6d5375efe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d5370a8cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f6d53553eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f6d5355df65 in () at /usr/lib/libQt5Core.so.5 #8 0x7f6d51aeaa9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f6d53242b23 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f6d0984f700 (LWP 6280)): #0 0x7f6d53237c21 in poll () at /usr/lib/libc.so.6 #1 0x7f6d50e3bee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d50e3bfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d5375efe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d5370a8cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d53553eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d5296e859 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f6d5355df65 in () at /usr/lib/libQt5Core.so.5 #8 0x7f6d51aeaa9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f6d53242b23 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f6d0acba700 (LWP 6278)): #0 0x7f6d53237c21 in poll () at /usr/lib/libc.so.6 #1 0x7f6d50e3bee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d50e3bfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d5375efe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x000
[kwin] [Bug 400038] Problems w/KDE Desktop when waking from sleep with proprietary Nvidia Drivers Installed
https://bugs.kde.org/show_bug.cgi?id=400038 Martin Flöser changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Martin Flöser --- *** 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] KWin Seg Fault on Startup
https://bugs.kde.org/show_bug.cgi?id=399499 Martin Flöser changed: What|Removed |Added CC||uavtech2...@gmail.com --- Comment #1 from Martin Flöser --- *** Bug 400038 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400038] Problems w/KDE Desktop when waking from sleep with proprietary Nvidia Drivers Installed
https://bugs.kde.org/show_bug.cgi?id=400038 Martin Flöser changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DUPLICATE |--- --- Comment #2 from Martin Flöser --- @Nate: please don't duplicate a KWin crash to plasma. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 374009] Spectacle's Rectangular Region mode loses keyboard focus after alt-tabbing away or switching to another virtual desktop, making it hard to escape
https://bugs.kde.org/show_bug.cgi?id=374009 --- Comment #32 from Nate Graham --- *** Bug 386629 has been marked as a duplicate of this bug. *** --- Comment #33 from Nate Graham --- *** Bug 379145 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 374009] Spectacle's Rectangular Region mode loses keyboard focus after alt-tabbing away or switching to another virtual desktop, making it hard to escape
https://bugs.kde.org/show_bug.cgi?id=374009 --- Comment #32 from Nate Graham --- *** Bug 386629 has been marked as a duplicate of this bug. *** --- Comment #33 from Nate Graham --- *** Bug 379145 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 386629] Can't exit rectangular region
https://bugs.kde.org/show_bug.cgi?id=386629 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Nate Graham --- After further investigation of Bug 374009, this is indeed a duplicate of it. *** This bug has been marked as a duplicate of bug 374009 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 --- Comment #80 from Martin Flöser --- (In reply to Arash B from comment #79) > What is the problem that makes this solution not applicable? It would break every plasma window such as the application launcher, notifications, etc. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 379145] Rectangular region mode can fail to respond to commands and lock out the system!
https://bugs.kde.org/show_bug.cgi?id=379145 --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 374009 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 395206] Show gui with operations after screenshot done
https://bugs.kde.org/show_bug.cgi?id=395206 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Nate Graham --- > After selecting rect and pressing Enter gui shows up and you choosing save > or copy screenshot That's exactly what it already does. If it's not doing this for you, please attach a screen recording. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 399773] Spectacle does not honor non-png file format preferences when using Save As
https://bugs.kde.org/show_bug.cgi?id=399773 Nate Graham changed: What|Removed |Added CC||kamesh...@yahoo.co.in --- Comment #2 from Nate Graham --- *** Bug 397709 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 296069] Walk Through Desktop layout rendering desktop previews
https://bugs.kde.org/show_bug.cgi?id=296069 Martin Flöser changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from Martin Flöser --- Please don't reopen unrelated bugs. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 397709] cannot save screenshot in eps format. Error while writing file.
https://bugs.kde.org/show_bug.cgi?id=397709 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 399773 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 296071] Drop BoxSwitch effect
https://bugs.kde.org/show_bug.cgi?id=296071 Bug 296071 depends on bug 296069, which changed state. Bug 296069 Summary: Walk Through Desktop layout rendering desktop previews https://bugs.kde.org/show_bug.cgi?id=296069 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 399395] Use the saved file instead of tmp one after it has been saved for exporting
https://bugs.kde.org/show_bug.cgi?id=399395 Nate Graham changed: What|Removed |Added CC||mihael.ver...@gmail.com --- Comment #5 from Nate Graham --- *** Bug 395172 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 395172] Save exported screenshot can fail because such file is located in /tmp
https://bugs.kde.org/show_bug.cgi?id=395172 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 399395 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 374009] Spectacle's Rectangular Region mode loses keyboard focus after alt-tabbing away or switching to another virtual desktop, making it hard to escape
https://bugs.kde.org/show_bug.cgi?id=374009 Nate Graham changed: What|Removed |Added CC||xgd...@msn.com --- Comment #31 from Nate Graham --- *** Bug 398389 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 398389] esc not working sometimes
https://bugs.kde.org/show_bug.cgi?id=398389 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 374009 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 381528] Unable to capture rectangular screenshot
https://bugs.kde.org/show_bug.cgi?id=381528 --- Comment #7 from Ľudovít Lučenič --- Sorry for not responding quick enough. I just checked that Spectacle works if used only with my primary display (laptop). Yes, the mouse activities as described. GPU 1-nVidia GK104M [GeForce GTX 870M] 2-Intel 4th Gen Core Processor Integrated Graphics Controller (driver i915) nvidia-driver 384.130-1 spectacle 16.08.3 - Sorry For Any Inconvenience -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400044] Discover shows distribution name as source of local package (deb/rpm)
https://bugs.kde.org/show_bug.cgi?id=400044 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Yeap, this is not ideal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 --- Comment #2 from RaitaroH --- (In reply to David Edmundson from comment #1) > Please include ~/.config/plasma* configs Well in `plasmarc` I have the walls that appear in `Configure desktop` -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395923] Port FlatpakBackend to use FlatpakTransaction: Installing steam doesn't pull nvidia binaries
https://bugs.kde.org/show_bug.cgi?id=395923 Nate Graham changed: What|Removed |Added Version Fixed In||5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400045] Discover shows no "Category" for deb package
https://bugs.kde.org/show_bug.cgi?id=400045 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/dis ||cover/12fd2c61c14190e4117ed ||b0b00b3476027359927 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.14.2 --- Comment #2 from Nate Graham --- Git commit 12fd2c61c14190e4117edb0b00b3476027359927 by Nate Graham. Committed on 20/10/2018 at 04:06. Pushed by ngraham into branch 'Plasma/5.14'. Only show the category label if the category is available FIXED-IN: 5.14.2 M +3-0discover/qml/ApplicationPage.qml https://commits.kde.org/discover/12fd2c61c14190e4117edb0b00b3476027359927 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 367480] Crash inside Baloo::PostingCodec::decode
https://bugs.kde.org/show_bug.cgi?id=367480 --- Comment #107 from Nate Graham --- *** Bug 400032 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400032] Baloo crashed suddenly
https://bugs.kde.org/show_bug.cgi?id=400032 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 367480 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400038] Problems w/KDE Desktop when waking from sleep with proprietary Nvidia Drivers Installed
https://bugs.kde.org/show_bug.cgi?id=400038 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 364766 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 Nate Graham changed: What|Removed |Added CC||uavtech2...@gmail.com --- Comment #49 from Nate Graham --- *** Bug 400038 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400042] Discover shows download speed while local package (deb/rpm) is installed
https://bugs.kde.org/show_bug.cgi?id=400042 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400045] Discover shows no "Category" for deb package
https://bugs.kde.org/show_bug.cgi?id=400045 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Yeah, if the category isn't available for some reason, we shouldn't show the label at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400047] Plasma shows unnecessary "Examining: finished" notification when I open "Edit applications...." window
https://bugs.kde.org/show_bug.cgi?id=400047 Nate Graham changed: What|Removed |Added Target Milestone|--- |1.0 Product|frameworks-knotifications |plasmashell CC||n...@kde.org, ||plasma-b...@kde.org Version|5.51.0 |master Assignee|kdelibs-b...@kde.org|k...@privat.broulik.de Component|general |Notifications -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400048] [Polish] Add shortcut to display the document 100%
https://bugs.kde.org/show_bug.cgi?id=400048 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400048] [Polish] Add shortcut to display the document 100%
https://bugs.kde.org/show_bug.cgi?id=400048 Nate Graham changed: What|Removed |Added Keywords||junior-jobs, usability -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 400052] Cut-off text at the tops or bottoms of labels on scrollable Plasma views
https://bugs.kde.org/show_bug.cgi?id=400052 Nate Graham changed: What|Removed |Added CC||gr...@student.ethz.ch --- Comment #1 from Nate Graham --- *** Bug 395817 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 400052] Cut-off text at the tops or bottoms of labels on scrollable Plasma views
https://bugs.kde.org/show_bug.cgi?id=400052 Nate Graham changed: What|Removed |Added Assignee|plasma-b...@kde.org |notm...@gmail.com CC||n...@kde.org Summary|The text in the Desktop |Cut-off text at the tops or |Folder Settings window is |bottoms of labels on |cut off.|scrollable Plasma views Product|systemsettings |frameworks-plasma Status|REPORTED|CONFIRMED Component|general |libplasmaquick Version|5.12.7 |unspecified Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 395817] Font antialiasing broken after scrolling
https://bugs.kde.org/show_bug.cgi?id=395817 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Nate Graham --- Duping this to the newer Bug 400052 since the attachment there illustrates the problem more clearly. *** This bug has been marked as a duplicate of bug 400052 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400054] New: DirSelect Dialog saves history in kdeglobals
https://bugs.kde.org/show_bug.cgi?id=400054 Bug ID: 400054 Summary: DirSelect Dialog saves history in kdeglobals Product: dolphin Version: 18.08.2 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mr.shreyan...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Please direct me to correct place if this report doesn't belongs here. KDE currently saves the local item history in $HOME/.config/.kdeglobals file in the [DirSelect Dialog] under "History Items[$e]" key. This field is constantly changing with usage and ideally doesn't belong in $HOME/.config but somewhere in $HOME/.local because of it's nature. I'd like to version control KDE configuration in a git repository but since this file keeps on changing due to this key, I'm unable to commit my configuration. Thank you. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.4 KDE Frameworks Version: 5.49.0 Qt Version: 5.11.1 KDE Plasma on NixOS 18.09 based on commit 09195057114a0a8d112c847a9a8f52957420857d ( https://github.com/NixOS/nixpkgs-channels/tree/09195057114a0a8d112c847a9a8f52957420857d ) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 400053] New: Neon repository throws error in upgrade to Unbutu 18.10 using neon update tool
https://bugs.kde.org/show_bug.cgi?id=400053 Bug ID: 400053 Summary: Neon repository throws error in upgrade to Unbutu 18.10 using neon update tool Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: twil...@phoenix-infosys.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY In trying to update from 18.04 to 18.10 using the update tool on the desktop I get this error when the tool starts to download packages. "E:The repository 'http://archive.neon.kde.org/user cosmic Release' does not have a Release file." It then exits update. STEPS TO REPRODUCE 1. Run Distribution Upgrade 2. 3. OBSERVED RESULT Runs fine until it starts to download new packages then throws error above. EXPECTED RESULT To download new packages and complete the upgrade SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 250355] Volume control with system tray icon does not work when application is minimized or loses focus
https://bugs.kde.org/show_bug.cgi?id=250355 Michael Pyne changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/juk ||/e2012e79359854f0ad73769bd0 ||2f092e44f40cf4 Resolution|--- |FIXED Version Fixed In||18.08.3 --- Comment #3 from Michael Pyne --- Git commit e2012e79359854f0ad73769bd02f092e44f40cf4 by Michael Pyne. Committed on 20/10/2018 at 02:40. Pushed by mpyne into branch 'Applications/18.08'. systray: Make SHIFT+Mousewheel change the volume, not the song. This fixes a bug that recently hit its 8 year anniversary. :( The big issue was that there was no easy way to tell which keyboard modifiers were set for the systray since Qt's event loop didn't actually receive the keyboard events. There's a separate function you can call, queryKeyboardModifiers, which makes a specific query to the desktop, and works even if Qt event loop didn't receive keyboard events. This fixes the bug here, and hopefully for everyone else. In fixing the bug I noticed that we can set out-of-bounds volumes due to lack of checking, so I fixed that too. FIXED-IN:18.08.3 M +5-2playermanager.cpp M +1-1systemtray.cpp https://commits.kde.org/juk/e2012e79359854f0ad73769bd02f092e44f40cf4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400020] Possible dolphinrc corruption after Dolphin's settings being changed for the first time
https://bugs.kde.org/show_bug.cgi?id=400020 --- Comment #6 from Tyson Tan --- Created attachment 115765 --> https://bugs.kde.org/attachment.cgi?id=115765&action=edit ~/.config folder from a freshly installed Manjaro 17.1.12 KDE system Retrieved from command line via Yakuake, right after the system is installed. Nothing else was touched. Not even the notifications. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400020] Possible dolphinrc corruption after Dolphin's settings being changed for the first time
https://bugs.kde.org/show_bug.cgi?id=400020 --- Comment #5 from Tyson Tan --- Created attachment 115764 --> https://bugs.kde.org/attachment.cgi?id=115764&action=edit ~/.config folder from Manjaro 17.1.12 KDE LiveUSB Retrieved from command line via Yakuake, right after it boot into LiveUSB. Nothing else was touched. Not even the notifications. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400020] Possible dolphinrc corruption after Dolphin's settings being changed for the first time
https://bugs.kde.org/show_bug.cgi?id=400020 --- Comment #4 from Tyson Tan --- (In reply to Nate Graham from comment #3) > Is there already a ~/.config/dolphinrc present on a new Manjaro install > *before* you open Dolphin for the first time? No, there is no dolphinrc. I've checked ~/.config with Yakuake without touching anything, both in LiveUSB and the installed system. Strangely enough though -- it somehow has a gwenviewrc but I'm sure I never opened Gwenview. For better investigation, I will attach the content in my ~/.config folders from Manjaro 17.1.12 LiveUSB and the installed system below. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400052] New: The text in the Desktop Folder Settings window is cut off.
https://bugs.kde.org/show_bug.cgi?id=400052 Bug ID: 400052 Summary: The text in the Desktop Folder Settings window is cut off. Product: systemsettings Version: 5.12.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nicholas.h...@protonmail.com Target Milestone: --- Created attachment 115763 --> https://bugs.kde.org/attachment.cgi?id=115763&action=edit Shows how the text is slightly cut off. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400049] Fractional scaling introduces visual artifacts with Kvantum
https://bugs.kde.org/show_bug.cgi?id=400049 --- Comment #4 from Christoph Feck --- Could already be fixed with https://github.com/tsujan/Kvantum/commit/dfffb33dd69d27227e428b486f44301dfab54fce -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400014] After I drag the icon of a favorite app to konsole, cursor changes to hand shaped cursor on mouseover some items in plasma panel
https://bugs.kde.org/show_bug.cgi?id=400014 --- Comment #3 from Patrick Silva --- Also reproducible on neon dev unstable. KDE Plasma: 5.14.80 Qt: 5.11.2 KDE Frameworks: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400049] Fractional scaling introduces visual artifacts with Kvantum
https://bugs.kde.org/show_bug.cgi?id=400049 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #3 from Christoph Feck --- Gwenview is bug 373178. Please report issues for Kvantum style directly to Kvantum developers via https://github.com/tsujan/Kvantum/issues -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399732] double click deb package starts discover with blank install page
https://bugs.kde.org/show_bug.cgi?id=399732 --- Comment #3 from sp --- well, I've tried it now and it works. Must have been the latest set of updates that fixed it. So guess you can close the ticket. for information: -I was using nvida proprietary drivers. -And get the following errors just starting plasma-discover: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/GlobalDrawer.qml:258: TypeError: Cannot read property 'length' of undefined file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/GlobalDrawer.qml:293: TypeError: Cannot read property 'length' of undefined file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/GlobalDrawer.qml:292: TypeError: Cannot read property 'length' of undefined adding empty sources model QStandardItemModel(0x561b8c530eb0) no packages for "com.teamviewer.TeamViewer" no packages for "im.riot.webapp" invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation." invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation." org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" Fwupd Error 9 Failed to find any useful results to report -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400051] New: Always crashes when applying "Audio Wave" to a clip
https://bugs.kde.org/show_bug.cgi?id=400051 Bug ID: 400051 Summary: Always crashes when applying "Audio Wave" to a clip Product: kdenlive Version: git-master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: aspotas...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE Scenario 1: 1. Add a clip to the project 2. Apply effect "Audio Wave" to the clip 3. Start playing in the Clip Monitor -> immediate crash (after less than half a second). ~~~ [aspotashev@glue ~]$ kdenlive libEGL warning: DRI2: failed to authenticate No LADSPA plugins were found! Check your LADSPA_PATH environment variable. qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 10124, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 10178, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 10181, resource id: 96469615, major code: 130 (Unknown), minor code: 3 org.kde.kcoreaddons: Could not lock file: "/home/aspotashev/.local/share/stalefiles/kdenlive/3b5a907be786f4a60eb6e46763de032b.kdenliveqVffile_%2Fhome%2Faspotashev%2FDocumentsIHF91qVf" qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 56737, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 56875, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 56929, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 56932, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 57055, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 57187, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 57327, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 57459, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 57599, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 57731, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 57880, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2109, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2270, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2324, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2327, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2447, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2579, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32089, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32246, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32300, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32303, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32423, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32555, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32695, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32827, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32967, resource id: 96469615, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 33099, resource id: 9646961
[systemsettings] [Bug 399901] Current boot splash is not highlighted
https://bugs.kde.org/show_bug.cgi?id=399901 --- Comment #3 from Patrick Silva --- Created attachment 115762 --> https://bugs.kde.org/attachment.cgi?id=115762&action=edit kcm after theme changing and reboot I configured another theme and rebooted. Now current theme is highlighted. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 400050] New: [Wayland/flatpak] Mouse clicks have no effect in both "Configure Elisa and "Configure shortcuts" windows
https://bugs.kde.org/show_bug.cgi?id=400050 Bug ID: 400050 Summary: [Wayland/flatpak] Mouse clicks have no effect in both "Configure Elisa and "Configure shortcuts" windows Product: elisa Version: 0.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY bug occurs on both Arch Linux and neon dev unstable under Wayland. STEPS TO REPRODUCE 1. open Elisa on Wayland session 2. click hamburger menu aside the volume slider 3. open "Configure Elisa" or "Configure shortcuts" OBSERVED RESULT mouse clicks on any element below the title bar have no effect EXPECTED RESULT mouse clicks work. SOFTWARE VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.14.1 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 ADDITIONAL INFORMATION I installed Elisa via flathub/flatpak. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #20 from ocumo --- Created attachment 115761 --> https://bugs.kde.org/attachment.cgi?id=115761&action=edit Problems with the installation of the flatpak version of krita 4.1.5: Documentation issues and other In the attached file, I am detailing a number of problems faced when installing the current release of krita (4.1.5) using the Flatpak method. This is part of the investigation for the bug in this thread, thus the need to put this here, despite the fact that this opens new problems not directly related to the current bug. The relevance of this report about the Flatpak method, is that the Flatpak is an obvious and valid alternative to the appimages, which this thread show that have catastrophic compatibility issues with a very important, professional class hardware (Wacom Cintiq) that krita and Linux otherwise do support. In this case, Flatpaks can provide at the very least a fallback solution to broken appimages and/or the kritalime PPA has not been updated, among other scenarios in which users prefer/have to use Flatpak in their systems. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400049] Fractional scaling introduces visual artifacts with Kvantum
https://bugs.kde.org/show_bug.cgi?id=400049 --- Comment #2 from Filip F. --- Apparently there is no text corruption in the jpegs, however Gwenview renders images badly with this 1.1 setting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400049] Fractional scaling introduces visual artifacts with Kvantum
https://bugs.kde.org/show_bug.cgi?id=400049 --- Comment #1 from Filip F. --- Created attachment 115760 --> https://bugs.kde.org/attachment.cgi?id=115760&action=edit Blurring is affected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400049] New: Fractional scaling introduces visual artifacts with Kvantum
https://bugs.kde.org/show_bug.cgi?id=400049 Bug ID: 400049 Summary: Fractional scaling introduces visual artifacts with Kvantum Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tyx...@gmail.com Target Milestone: --- Created attachment 115759 --> https://bugs.kde.org/attachment.cgi?id=115759&action=edit Visual artifacts (lines) SUMMARY Using fractional scaling will introduce many visual glitches when used with Kvantum. Mostly there are some 1px lines popping up all over the place, but blurring is also affected. I will attach two screenshots to show you this. There is text corruption in them that wasn't present in real word, I don't know why. STEPS TO REPRODUCE Set up fractional scaling and Kvantum as the widget style (in this case the factor was 1.1 and the theme was Adapta-Nokto) OBSERVED RESULT Visual artifacts everywhere. EXPECTED RESULT No artifacts, just like when not using fractional scaling. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50 Qt Version: 5.11.2 ADDITIONAL INFORMATION My apologies if I've addressed this report to the wrong party. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #19 from ocumo --- I have been testing the flatpak installation of krita 4.1.5 for several minutes. The good news is that the flatpak version does NOT have the crash/hangup issue. Though I need to test more, it clearly is not failing as with the appimage versions, and touch functionality works exactly as with the kritalime PPA version (not perfect, but quite good). This seems to confirm that definitely there is something not well with the appimages 4.x.x, because neither 3.x.x appimages nor kritalime PPA installations, nor flatpak 4.1.5, have any of the reported problems. The bad news is that the installation instructions of flatpak in the https://krita.org/en/download/krita-desktop/ webpage are wrong and incomplete, and even the instructions in https://flathub.org/apps/details/org.kde.krita fail to provide important information. There is, in addition, another issue. I will provide an attachment with these notes and details, in my next post, so please I would really appreciate feedback/comments. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 389768] Add a hidden edit button to the repo lists so people can edit repo URLs, if necessary
https://bugs.kde.org/show_bug.cgi?id=389768 Aleix Pol changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from Aleix Pol --- PackageKit repo editing isn't supported. We could have it for flatpak, and for flatpak one will want the flatpakrepo file anyway. Or it's for super corner-cases because one would have to change the gpg key. So I'd say software-properties is their friend. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400048] New: [Polish] Add shortcut to display the document 100%
https://bugs.kde.org/show_bug.cgi?id=400048 Bug ID: 400048 Summary: [Polish] Add shortcut to display the document 100% Product: okular Version: 1.5.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: fdelgado...@gmail.com Target Milestone: --- Created attachment 115758 --> https://bugs.kde.org/attachment.cgi?id=115758&action=edit keyboard shortcut menu options I have a screen 1366x768 and to see a document, I need always to click on the UI to view the document 100%. It would be quite useful to add a shortcut to activate it from the keyboard. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399370] offline update state stability
https://bugs.kde.org/show_bug.cgi?id=399370 Aleix Pol changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/dis ||cover/26ac7c780fd749d10a149 ||f578649c5dda2e05e5a Resolution|--- |FIXED --- Comment #1 from Aleix Pol --- Git commit 26ac7c780fd749d10a149f578649c5dda2e05e5a by Aleix Pol. Committed on 20/10/2018 at 00:02. Pushed by apol into branch 'master'. pk: don't offer offline updates after they've been downloaded Insist on rebooting instead M +6-0discover/qml/UpdatesPage.qml M +5-0libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp M +12 -0libdiscover/backends/PackageKitBackend/PackageKitNotifier.cpp M +10 -0libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp M +14 -0libdiscover/resources/AbstractBackendUpdater.cpp M +13 -0libdiscover/resources/AbstractBackendUpdater.h M +10 -0libdiscover/resources/ResourcesUpdatesModel.cpp M +3-0libdiscover/resources/ResourcesUpdatesModel.h https://commits.kde.org/discover/26ac7c780fd749d10a149f578649c5dda2e05e5a -- 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 #8 from timo...@zoho.com --- I don't think running out of memory is the issue. I have 8G RAM and 8G swap. I built f8d2d5f66532c3695211f06eb09f967ba1248986 and ran `free` every .5s until the crash (it did crash). The RAM did get close to used up (in the 7Gs) some times, but there was always plenty of swap left. The highest usage I saw was 7G RAM and 3G swap. Memory usage went down towards the end though and at the time of the crash it looked like this: > totalusedfree shared buff/cache > available > Mem:8057628 4580060 197368 178532 3280200 > 2994156 > Swap: 8388604 3202384 5186220 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399732] double click deb package starts discover with blank install page
https://bugs.kde.org/show_bug.cgi?id=399732 Aleix Pol changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Aleix Pol --- Could you try running it from a terminal and see if there's a warning or something we can use to reproduce? I can't. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 400047] New: Plasma shows unnecessary "Examining: finished" notification when I open "Edit applications...." window
https://bugs.kde.org/show_bug.cgi?id=400047 Bug ID: 400047 Summary: Plasma shows unnecessary "Examining: finished" notification when I open "Edit applications" window Product: frameworks-knotifications Version: 5.51.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: bugsefor...@gmx.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 115757 --> https://bugs.kde.org/attachment.cgi?id=115757&action=edit screenshot SUMMARY behavior already noticed on both Arch Linux and neon dev unstable. STEPS TO REPRODUCE 1. open kickoff, right click some entry in "Favorites" tab 2. select "Edit application..." 3. OBSERVED RESULT Plasma shows an unnecessary notification, as you can see in my screenshot. Not always I can reproduce, apparently the notification appears randomly when I follow the steps above. EXPECTED RESULT no notification. SOFTWARE VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.14.1 Qt Version: 5.12.0 beta2 KDE Frameworks Version: 5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400046] New: Making a new tag creates copies of already existing tags
https://bugs.kde.org/show_bug.cgi?id=400046 Bug ID: 400046 Summary: Making a new tag creates copies of already existing tags Product: krita Version: 4.1.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: isa...@live.com Target Milestone: --- Created attachment 115756 --> https://bugs.kde.org/attachment.cgi?id=115756&action=edit A screenshot of the random tag that multiplied. SUMMARY: Making a new tag on the brush presets docker/changing resource bundles makes a copy of a random, already existing tag. STEPS TO REPRODUCE 1.Create a new tag/change resource bundles 2.(optional): add brushes to it OBSERVED RESULT: It can be temporarily fixed by restarting krita, but will happen again if the steps are repeated EXPECTED RESULT: No additional tags being made SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Version (compiled): 5.9.3 Version (loaded): 5.9.3 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 373759] Implement autonumeration back
https://bugs.kde.org/show_bug.cgi?id=373759 Nate Graham changed: What|Removed |Added Version Fixed In||18.12.0 Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/spe ||ctacle/754e1d3a92c13d9327f4 ||dbf3ed9abb08083af7dd Resolution|--- |FIXED --- Comment #3 from Nate Graham --- Git commit 754e1d3a92c13d9327f4dbf3ed9abb08083af7dd by Nate Graham, on behalf of Kyle Utecht. Committed on 19/10/2018 at 22:34. Pushed by ngraham into branch 'master'. Add default file name token for (padded) sequential file numbering Summary: Default file name tokens %d will add an auto-incremented sequential file number when creating file names. Numbering starts with 1. If the save directory has other files present with the same name (excluding extension) but another number in the place of %d, the next number after that of the existing file will be used to create the new file name. The sequential number can be padded with %Nd where N is a number of total digits. If the padded token is used in the default file name, only file names with a number of the padded length or longer will be considered when determining the next sequential number to use in the file name. For example, with the save name like 'Screenshot-%3d' and a save directory with only 'Screenshot-3,' the next generated file name will be 'Screenshot-001' since the existing file's number portion is not at least as long as the padded number length. Related: bug 358641 FIXED-IN: 18.12.0 Reviewers: alexeymin, ngraham Reviewed By: alexeymin, ngraham Subscribers: shubham, ngraham, alexeymin, #spectacle Tags: #spectacle Differential Revision: https://phabricator.kde.org/D16304 M +47 -1src/ExportManager.cpp M +4-2src/Gui/SettingsDialog/SaveOptionsPage.cpp M +3-2src/SpectacleConfig.cpp https://commits.kde.org/spectacle/754e1d3a92c13d9327f4dbf3ed9abb08083af7dd -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 358641] Have Spectacle remember filename
https://bugs.kde.org/show_bug.cgi?id=358641 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/spe ||ctacle/754e1d3a92c13d9327f4 ||dbf3ed9abb08083af7dd Version Fixed In||18.12.0 Resolution|--- |FIXED --- Comment #12 from Nate Graham --- Git commit 754e1d3a92c13d9327f4dbf3ed9abb08083af7dd by Nate Graham, on behalf of Kyle Utecht. Committed on 19/10/2018 at 22:34. Pushed by ngraham into branch 'master'. Add default file name token for (padded) sequential file numbering Summary: Default file name tokens %d will add an auto-incremented sequential file number when creating file names. Numbering starts with 1. If the save directory has other files present with the same name (excluding extension) but another number in the place of %d, the next number after that of the existing file will be used to create the new file name. The sequential number can be padded with %Nd where N is a number of total digits. If the padded token is used in the default file name, only file names with a number of the padded length or longer will be considered when determining the next sequential number to use in the file name. For example, with the save name like 'Screenshot-%3d' and a save directory with only 'Screenshot-3,' the next generated file name will be 'Screenshot-001' since the existing file's number portion is not at least as long as the padded number length. Related: bug 373759 FIXED-IN: 18.12.0 Reviewers: alexeymin, ngraham Reviewed By: alexeymin, ngraham Subscribers: shubham, ngraham, alexeymin, #spectacle Tags: #spectacle Differential Revision: https://phabricator.kde.org/D16304 M +47 -1src/ExportManager.cpp M +4-2src/Gui/SettingsDialog/SaveOptionsPage.cpp M +3-2src/SpectacleConfig.cpp https://commits.kde.org/spectacle/754e1d3a92c13d9327f4dbf3ed9abb08083af7dd -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 399772] Free space is not correctly recalculated when resizing LVM LVs
https://bugs.kde.org/show_bug.cgi?id=399772 Andrius Štikonas changed: What|Removed |Added Latest Commit|https://commits.kde.org/kpm |https://commits.kde.org/kpm |core/3e31ec1431a45029c50507 |core/b06af11357a57bc582e3ee |46012066e1b1101b57 |571053a0bd5f070028 --- Comment #3 from Andrius Štikonas --- Git commit b06af11357a57bc582e3ee571053a0bd5f070028 by Andrius Štikonas. Committed on 19/10/2018 at 18:55. Pushed by stikonas into branch 'master'. Fix free space handling with LVM LVs. The previous commit worked for resizing LVM. However, it is better to do special handling of LVMs in insert/removePreviewPartition. M +12 -1src/ops/operation.cpp M +0-10 src/ops/resizeoperation.cpp https://commits.kde.org/kpmcore/b06af11357a57bc582e3ee571053a0bd5f070028 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400045] New: Discover shows no "Category" for deb package
https://bugs.kde.org/show_bug.cgi?id=400045 Bug ID: 400045 Summary: Discover shows no "Category" for deb package Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 115755 --> https://bugs.kde.org/attachment.cgi?id=115755&action=edit screenshot STEPS TO REPRODUCE 1. open some deb package with discover 2. 3. OBSERVED RESULT Discover shows no "Category". See the screenshot. EXPECTED RESULT Show "Category" correctly. SOFTWARE VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.14.80 Qt Version: 5.11.1 KDE Frameworks Version: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400044] New: Discover shows distribution name as source of local package (deb/rpm)
https://bugs.kde.org/show_bug.cgi?id=400044 Bug ID: 400044 Summary: Discover shows distribution name as source of local package (deb/rpm) Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 115754 --> https://bugs.kde.org/attachment.cgi?id=115754&action=edit screenshot STEPS TO REPRODUCE 1. open some deb/rpm package with discover 2. 3. OBSERVED RESULT "Source:" is the distribution name, see the screenshot. This info makes it appear that the package comes from the distribution repos. Operating System: KDE neon Developer Edition KDE Plasma Version: 5.14.80 Qt Version: 5.11.1 KDE Frameworks Version: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399945] Panel & other desktop functionality hang following network drop if CIFS mounted SMB directory exists
https://bugs.kde.org/show_bug.cgi?id=399945 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #8 from David Edmundson --- > Being that this is a slightly different (although related issue), should I open a new bug report? Yes please. Report it against whichever process is frozen and include a gdb stacktrace of the frozen state. It can always be moved -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399308] Add the ability to display the Close/Min/Max buttons and App name on the global menu
https://bugs.kde.org/show_bug.cgi?id=399308 --- Comment #9 from Michał Dybczak --- AWC seems to be a KDE project now (ut has own bug section) so it's possible it will be taken over sooner or later. I talked with Latte developer and he was interested in it and had ideas on how to integrate AWC with Latte better so if things won't change, someone will take it further. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400042] Discover shows download speed while local package (deb/rpm) is installed
https://bugs.kde.org/show_bug.cgi?id=400042 Patrick Silva changed: What|Removed |Added Summary|do not show download speed |Discover shows download |while local package |speed while local package |(deb/rpm) is installed |(deb/rpm) is installed -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400042] New: do not show download speed while local package (deb/rpm) is installed
https://bugs.kde.org/show_bug.cgi?id=400042 Bug ID: 400042 Summary: do not show download speed while local package (deb/rpm) is installed Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 115753 --> https://bugs.kde.org/attachment.cgi?id=115753&action=edit screenshot STEPS TO REPRODUCE 1. install some deb/rpm package 2. click "tasks" in the side bar while discover installs the package 3. OBSERVED RESULT discover shows "...Installing 0 B/s". See the screenshot. EXPECTED RESULT omit "Installing 0 B/s or replace it with "Installing x %" SOFTWARE VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.14.80 Qt Version: 5.11.1 KDE Frameworks Version: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 400043] New: Korganizer categories are broken; never stay selected, and duplicate themselves
https://bugs.kde.org/show_bug.cgi?id=400043 Bug ID: 400043 Summary: Korganizer categories are broken; never stay selected, and duplicate themselves Product: korganizer Version: 5.9.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: alexandre.bonn...@linuxfr.eu Target Milestone: --- To sum up, I have an old 2012 ics calendar created by Korganizer between 2005 up until the end of 2012, then all hell broke loose and Korganizer categories got broken. I was since then unable to use korganizer as before (ie. with correctly working categories and categories' colors), but I now need to be able to use Korganizer again. The categories problem still exists 6 years after ; basically you cannot create and use a category; it unselect itself when editing the event/task again, and the category keeps duplicating itself when opening the category list. STEPS TO REPRODUCE I tested 3 things; - with my old calendar and current settings, - with my old calendar and a brand new user, - with a new calendar and a new user. In each case, the bug was there. > With my old calendar and current settings Note: my old calendar has 233087 lines and is 6.9MB big. `grep VEVENT calendar.ics|wc -l` lists 11470 events. `grep VTODO calendar.ics|wc -l` lists 17668 tasks. 1. Open Korganizer 2. Double-click an existing event with a 'Work' category to edit it (You know this is a work event since it's color is correctly shown, and the tooltip does show the correct Work category) 3. Select the 'click to add tags' button to open the categories window 4. See that the 'Work' category (or any other categories) are _unselected_ 5. Additionally see that the 'Work' category is currently duplicated 5 times 6. Cry > with my old calendar and a brand new user 1. Create a new user 2. Login with that new user 3. Open the brand new Korganizer 4. Create a new agenda and point it to the existing 6.9MB ics calendar file 5. Wait 1 hour and 45 minutes for akonadi/korganizer to finish 'importing' it (Akonadi/Korganizer can only import 4.63 events/tasks per seconds, on my 12 core cpus, with 32GB of ram, really?! :/) 6. Go into the settings; there are NO categories shown in the color settings (it looks like those are not imported during the...import) 6. Double-click an existing event you KNOW has the 'Work' category to edit it 7. Select the 'click to add tags' button to open the categories window 8. See that the 'Work' category just appeared in that list, but still is _unselected_ 9. Check the categories on another event (ie. 'Fun'), and see that the categories list is now showing two unselected 'Work' and 'Fun' categories. 10. If you edit any Work event and check the categories list, then you can see that the 'Work' category is duplicated 5+ times, but still all are unselected 10. Cry again > with a new calendar and a new user 1. Create a new user 2. Login with that new user 3. Open the brand new Korganizer 4. Create a few new categories : 'Work', 'Fun', 'Soirée', 'Administrative work' 5. Create an event without categories 6. Create an event with the 'Work' category selected 7. Go into the settings to add a specific color to the 'Work' category (ie. blue) 8. Check that in the agenda view, the 2nd event is correctly colored in blue 9. Double-click on that event (with the 'Work' category) to edit it 10. Click the button next to the falsely advertised placeholder 'click to add tags' field, to open the categories window 11. See that the 'Work' category (or any other categories) are _unselected_ 12. See that the 'Work' category is currently duplicated 2 times 13. Close those windows and re-edit the event then show the tag window; the 'Work' category has been duplicated again 14. Try to cry since you have no tears left OBSERVED RESULT Well, in all cases, the categories at utterly broken, even on a new Kde user with a new agenda. (Is there any QA done for Korganizer?) EXPECTED RESULT Categories should : 1. Be listed directly instead of the 'Click here to add tags' placeholder (separated by a comma), currently they are not and I imagine this is related to this bug 2. Be correctly selected in the categories list, and stay selected between edits 3. Accepts accentuated characters in their names without getting duplicated 4. Not be duplicated in the categories list SOFTWARE VERSIONS (info given by kinfocenter) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.49.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION I'm sad, does this help? Let's hope this won't take 6 years again ;P Do you need the original ics file? I tried anonymizing it using https://github.com/collective/plone.app.eventindex/blob/master/anonical.py, but that removes too much information (including the categories). Do you have a script of your own to remove sen
[clazy] [Bug 399853] Request: Provide binary release packages
https://bugs.kde.org/show_bug.cgi?id=399853 Sergio Martins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |smart...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399945] Panel & other desktop functionality hang following network drop if CIFS mounted SMB directory exists
https://bugs.kde.org/show_bug.cgi?id=399945 --- Comment #7 from d...@aninstanceofme.com --- (In reply to Kai Uwe Broulik from comment #5) > I backported the fix to Plasma 5.12 LTS. Unfortunately 5.13 isn't actively > maintained anymore so you would have to ask your distribution to backport > this fix or upgrade to Plasma 5.14, if possible. Okay, I've now tested this after adding the Kubuntu backports PPA to the 18.10 system and upgrading to Plasma 5.14.1 (KDE Frameworks 5.51.0). The issue with the panel is indeed fixed. However, issues to still persist, in terms of access to the paths where the SMB (CIFS) share is mounted. When network is down (or the share becomes unavailable over the network, for whatever reason), not only does the mounted directory become unresponsive, but so does the entire directory path. For example, if the share is mounted at /home/dan/remote_data, then loss of network renders /home and all its subdirectories unresponsive. This applies both to attempts to open directories with Dolphin, and also access those directories with the CLI. Being that this is a slightly different (although related issue), should I open a new bug report? And if so, what would be the most appropriate Product/Component category, since this involves Plasma GUI applications (i.e. Dolphin), network stack, CIFS ... Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 --- Comment #79 from Arash B --- How come you say there's no easy way to fix this when the user can manually restrict a borderless window to the current activity? If this can easily be done manually, then it should be doable programatically. Even if an app opens in a borderless window (and thus the window appears in all Activities), then I can through KDE Plasma’s GUI (manually) make it to only appear in the current Activity. I just have to follow these steps: Press Alt+F3. Click sub-menu Activities. Choose the current activity. My question is if this can immediately be done manually on a borderless window, then why can’t it be done programmatically and automatically by KDE plasma? At least the silly solution to programmatically do the above three steps is available. I.e. KDE plasma is programmed to execute the following steps If a borderless window is created then Execute Alt+F3 (but don’t show the menu on the GUI) Enter sub-menu Activities Select the current Activity What is the problem that makes this solution not applicable? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400036] Wallpaper changing to default release on it's own
https://bugs.kde.org/show_bug.cgi?id=400036 --- Comment #1 from David Edmundson --- Please include ~/.config/plasma* configs -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 400041] New: [wayland] Crashes when opening ttf file with kfontview
https://bugs.kde.org/show_bug.cgi?id=400041 Bug ID: 400041 Summary: [wayland] Crashes when opening ttf file with kfontview Product: kfontview Version: 5.14.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sefa6...@gmail.com Target Milestone: --- Created attachment 115752 --> https://bugs.kde.org/attachment.cgi?id=115752&action=edit stacktrace from gdb SUMMARY When I open any ttf file in kfontview it crashes and does not even show up. STEPS TO REPRODUCE 1. Open ttf file OBSERVED RESULT Crash EXPECTED RESULT Window opening up SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Stacktrace is attached -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 296069] Walk Through Desktop layout rendering desktop previews
https://bugs.kde.org/show_bug.cgi?id=296069 Alexandre Bonneau changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Alexandre Bonneau --- This is still unresolved in 5.13.5-1; there are still no previews shown when switching desktop using the 'slide' effect. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 296071] Drop BoxSwitch effect
https://bugs.kde.org/show_bug.cgi?id=296071 Bug 296071 depends on bug 296069, which changed state. Bug 296069 Summary: Walk Through Desktop layout rendering desktop previews https://bugs.kde.org/show_bug.cgi?id=296069 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 400028] akregator segfaults in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest, thread safety issue
https://bugs.kde.org/show_bug.cgi?id=400028 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de --- Comment #2 from Martin Steigerwald --- Christophe, are you sure this is a duplicate of #371511? This bug is upstream report from Debian bug report of mine: libqt5webengine5: Akregator crashes very often, WebEngine related https://bugs.debian.org/910852 What I see here is that Akregator runs stable with external browser. It just crashes when using Qt Webengine as internal browser. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 367480] Crash inside Baloo::PostingCodec::decode
https://bugs.kde.org/show_bug.cgi?id=367480
--- Comment #106 from hotmusic...@mail.bg ---
(In reply to Don Curtis from comment #105)
> @alx.ku...@gmail.com:
>
> As a workaround until such time as your Distro updates to Frameworks 5.51,
> you can add a symbolic link to this Bash script in
> '~/.config/plasma-workspace/env/':
>
> #!/bin/bash
> #
> # Clean Baloo …
> #
> if [[ -f ~/.local/share/baloo/dateLastCleaned ]]
> then
> declare -i BalooLastDate
> BalooLastDate="$(cat ~/.local/share/baloo/dateLastCleaned)"
> declare -i TwoDaysAgo
> TwoDaysAgo="$(date --date='2 days ago' +%Y%m%d)"
> if (( $BalooLastDate < $TwoDaysAgo ))
> then
> balooctl stop
> rm ~/.local/share/baloo/dateLastCleaned
> find ~/.config/ -maxdepth 1 -iname '*baloo*' -execdir /usr/bin/rm '{}' \;
> find ~/.local/share/baloo/ -iname '*index*' -execdir /usr/bin/rm '{}' \;
> date +%Y%m%d > ~/.local/share/baloo/dateLastCleaned
> fi
> else
> balooctl stop
> find ~/.config/ -maxdepth 1 -iname '*baloo*' -execdir /usr/bin/rm '{}' \;
> find ~/.local/share/baloo/ -iname '*index*' -execdir /usr/bin/rm '{}' \;
> date +%Y%m%d > ~/.local/share/baloo/dateLastCleaned
> fi
> #
Thank you so much! Works perfectly! I placed the script directly into the
folder btw.
--
You are receiving this mail because:
You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Martin Steigerwald changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #9 from Martin Steigerwald --- Reopening, as crash still happens with Qt 5.11.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400040] New: widget crash in wayland session when trying to change the icon
https://bugs.kde.org/show_bug.cgi?id=400040 Bug ID: 400040 Summary: widget crash in wayland session when trying to change the icon Product: plasmashell Version: 5.14.1 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: lordsli...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.1) (Compiled from sources) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.14-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Tried to change Application Dashboard widget in plasma wayland session. It crashed. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4ca6b710c0 (LWP 11922))] Thread 25 (Thread 0x7f4c3a7fc700 (LWP 14174)): #0 0x7f4cac0ebafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4cad1ce71c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f4caedf87ed in () at /usr/lib/libQt5Quick.so.5 #3 0x7f4caedf8a5c in () at /usr/lib/libQt5Quick.so.5 #4 0x7f4cad1cdf65 in () at /usr/lib/libQt5Core.so.5 #5 0x7f4cac0e5a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f4caceb2b23 in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f4c39ffb700 (LWP 14173)): #0 0x7f4cacea7c21 in poll () at /usr/lib/libc.so.6 #1 0x7f4caac07ee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f4caac07fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f4cad3cefe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f4cad37a8cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f4cad1c3eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f4caeaf6859 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f4cad1cdf65 in () at /usr/lib/libQt5Core.so.5 #8 0x7f4cac0e5a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f4caceb2b23 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f4c3b7fe700 (LWP 13600)): #0 0x7f4cac0ebafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4cad1ce71c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f4caedf87ed in () at /usr/lib/libQt5Quick.so.5 #3 0x7f4caedf8a5c in () at /usr/lib/libQt5Quick.so.5 #4 0x7f4cad1cdf65 in () at /usr/lib/libQt5Core.so.5 #5 0x7f4cac0e5a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f4caceb2b23 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f4c40c11700 (LWP 13097)): #0 0x7f4c8a9a699b in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #1 0x7f4c8a9a78fe in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #2 0x7f4c8a9a7cba in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #3 0x7f4c8a9a854a in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #4 0x7f4c8ae0fd18 in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0 #5 0x7f4c8ae0ffef in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #6 0x7f4c8ae10091 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #7 0x7f4c8ae1e5ae in () at /usr/lib/libpulse.so.0 #8 0x7f4c8a9b89fc in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #9 0x7f4cac0e5a9d in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f4caceb2b23 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f4c41412700 (LWP 13077)): #0 0x7f4cac0ebafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4cad1ce71c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f4caedf87ed in () at /usr/lib/libQt5Quick.so.5 #3 0x7f4caedf8a5c in () at /usr/lib/libQt5Quick.so.5 #4 0x7f4cad1cdf65 in () at /usr/lib/libQt5Core.so.5 #5 0x7f4cac0e5a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f4caceb2b23 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f4c42020700 (LWP 12874)): #0 0x7f4cac0ebafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4cad1ce71c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f4c8bd63469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f4c8bd67339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f4c8bd6252d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 --- Comment #14 from Sergey --- Well. after longer delay I still see this bug. -- You are receiving this mail because: You are watching all bug changes.
