[plasma-nm] [Bug 384410] New: nm-applet fails to connect to APs whose SSID can't be decoded with system locale
https://bugs.kde.org/show_bug.cgi?id=384410 Bug ID: 384410 Summary: nm-applet fails to connect to APs whose SSID can't be decoded with system locale Product: plasma-nm Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: l-softw...@lausen.nl Target Milestone: --- If an AP name cannot be decoded with the system locale (or fallback locale), nm-applet will display gibberish instead of the AP name. Clicking connect will fail to connect to the network. Instead, if the AP name cannot be decoded, the BSSID should be displayed in nm-applet, which would make it possible to still connect to the network. For example, in greater China region some AP names may use the gb18030 encoding, which cannot be decoded with en_US.UTF-8 locale. The user should not be required to switch his system locale to zh_CN.gb18030 locale just to connect to networks for which the AP name cannot be decoded. Secondly, nm-applet should use LC_CTYPE to determine the encoding (and list of fallback encodings [1]) used for decoding AP names. https://bugzilla.gnome.org/show_bug.cgi?id=784415 contains more background information. [1]: https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm-core/nm-utils.c?id=a47153f5b8a114ce1f0d226b33d0ad6d6ec7f150#n76 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 372837] Unplug HDMI cable in sleep mode won't remove external monitor
https://bugs.kde.org/show_bug.cgi?id=372837 --- Comment #4 from Guo Yunhe --- I can understand. Hardware related issues are harder to reproduce. I will try with other computers/cables/monitors. If I have new findings, I will update this report. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384337] performance improvements to VEX register allocator v2 and v3
https://bugs.kde.org/show_bug.cgi?id=384337 --- Comment #9 from Ivo Raisr --- Created attachment 107711 --> https://bugs.kde.org/attachment.cgi?id=107711&action=edit Reorder allocatable registers for AMD64 and X86 archs Reorder allocatable registers for AMD64 and X86 so that the callee saved are listed first. Helper calls always trash all caller saved registers. By listing the callee saved first the register allocator is more likely to pick them and does not need to spill that much before helper calls. If this proves to improve performance (at least somewhat) then the v3 register allocation algorithm needs to be revisited. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 384344] Apply commit from master to speed up 4.8 reports
https://bugs.kde.org/show_bug.cgi?id=384344 Ralf Habacker changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/63e8dc4b7f1f487861911 ||ab78945f1870d695202 Version Fixed In||4.8.1 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Ralf Habacker --- Git commit 63e8dc4b7f1f487861911ab78945f1870d695202 by Ralf Habacker, on behalf of Åukasz WojniÅowicz. Committed on 06/09/2017 at 05:56. Pushed by habacker into branch '4.8'. Speed up KReportChartView::setLineWidth REVIEW: 129830 FIXED-IN:4.8.1 Signed-off-by: Łukasz Wojniłowicz (cherry picked from commit 3b265c4b0f451cf9eccc529e3217553196d224db) M +5-8kmymoney/reports/kreportchartview.cpp https://commits.kde.org/kmymoney/63e8dc4b7f1f487861911ab78945f1870d695202 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 384409] New: Browsing System settings > Workspace theme leads to appl. crash
https://bugs.kde.org/show_bug.cgi?id=384409 Bug ID: 384409 Summary: Browsing System settings > Workspace theme leads to appl. crash Product: systemsettings Version: 5.10.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: joerg.ler...@globalfoundries.com Target Milestone: --- Application: systemsettings5 (5.10.5) Qt Version: 5.7.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.9-300.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: Went to System settings > Workspace theme. Switching through categories there leads to repeatable application crash for me. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9239ca28c0 (LWP 15455))] Thread 6 (Thread 0x7f9203f9b700 (LWP 15467)): #0 0x7f924375bacd in poll () at /lib64/libc.so.6 #1 0x7f923c5ba569 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f923c5ba67c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f9244572e6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f924452360a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f924437b99a in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f9242f349b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f924437fc9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f924084136d in start_thread () at /lib64/libpthread.so.0 #9 0x7f9243767bbf in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9214bcd700 (LWP 15466)): #0 0x7f924375bacd in poll () at /lib64/libc.so.6 #1 0x7f923c5ba569 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f923c5ba67c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f9244572e6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f924452360a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f924437b99a in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f9242f349b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f924437fc9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f924084136d in start_thread () at /lib64/libpthread.so.0 #9 0x7f9243767bbf in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9217aac700 (LWP 15465)): #0 0x7f923c5b9e2c in g_main_context_check () at /lib64/libglib-2.0.so.0 #1 0x7f923c5ba510 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f923c5ba67c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f9244572e6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f924452360a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f924437b99a in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f9242f349b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f924437fc9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f924084136d in start_thread () at /lib64/libpthread.so.0 #9 0x7f9243767bbf in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f9226305700 (LWP 15457)): #0 0x7f924375bacd in poll () at /lib64/libc.so.6 #1 0x7f923c5ba569 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f923c5ba67c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f9244572e6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f924452360a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f924437b99a in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f9244c6ea39 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f924437fc9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f924084136d in start_thread () at /lib64/libpthread.so.0 #9 0x7f9243767bbf in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f922e948700 (LWP 15456)): #0 0x7f924375bacd in poll () at /lib64/libc.so.6 #1 0x7f9240e81c97 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f9240e83a8a in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f923301cba9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f924437fc9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f924084136d in start_thread () at /lib64/libpthread.so.0 #6 0x7f9243767bbf in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f9239ca28c0 (LWP 15455)): [KCrash Handler] #6 0x7f924368d69b in raise () at /lib
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 --- Comment #69 from Arash B --- @Martin Well then we go a step further out; some part of some api/interface (class constructor, public function, etc.) is used by others to signal to KWin that a window element should be created. Calling this api/interface part further leads to the creation a Client class instance, correct? Then add kwinWindowType to this api/interface part but give it a default value of UNKNOWN if the corresponding arg isn't passed on when the api/interface part is called. Then further pass on the value of kwinWindowType to the Client constructor (or Client::manage() which seems to serve instead of a constructor). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384399] Getting dialog asking for "perform also on grouped images?" when no grouped images are selected
https://bugs.kde.org/show_bug.cgi?id=384399 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.8.0 Latest Commit||https://commits.kde.org/dig ||ikam/707edf63bfd0c66d9c63dd ||57e77794b2c3c7d831 --- Comment #2 from Maik Qualmann --- Git commit 707edf63bfd0c66d9c63dd57e77794b2c3c7d831 by Maik Qualmann. Committed on 06/09/2017 at 04:41. Pushed by mqualmann into branch 'master'. fix ask for grouped items when no grouped items selected FIXED-IN: 5.8.0 M +2-1NEWS M +10 -3app/views/digikamview.cpp https://commits.kde.org/digikam/707edf63bfd0c66d9c63dd57e77794b2c3c7d831 -- 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 #68 from Martin Flöser --- Sorry your idea won't work. There is only one place where a Client is created. Client is a KWin internal class. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 376684] Screen brightness can not be changed after external monitor was connected
https://bugs.kde.org/show_bug.cgi?id=376684 Martin Flöser changed: What|Removed |Added Component|multihead |general Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Product|kwin|Powerdevil --- Comment #2 from Martin Flöser --- Yes, you are wrong. KWin is not responsible for screen brightness. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384401] Various recognition algorithm improvements for face detection
https://bugs.kde.org/show_bug.cgi?id=384401 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Faces-Recognition |Faces-Engine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384408] New: PanelView::setBackgroundHints doesn't update enabledBorders (which means it doesn't toggle the shadows)
https://bugs.kde.org/show_bug.cgi?id=384408 Bug ID: 384408 Summary: PanelView::setBackgroundHints doesn't update enabledBorders (which means it doesn't toggle the shadows) Product: plasmashell Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: zrenf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 While fussing with /usr/share/plasma/shells/.../contents/views/Panel.qml, I tried dynamically disabling the blur+shadows on the panel (using a repeating timer). I noticed that while the blur effect went away, the shadows did not. QML: panel.backgroundHints = Plasma.Types.NoBackground C++: https://github.com/KDE/plasma-workspace/blame/master/shell/panelview.cpp setBackgroundHints(Plasma::Types::NoBackground) emit backgroundHintsChanged() connect(this, SIGNAL(backgroundHintsChanged()), this, SLOT(themeChanged())); themeChanged() calls updateMask() but doesn't call updateEnabledBorders(). updateEnabledBorders() is what disables the panel shadow. PanelView::resizeEvent and PanelView::moveEvent call both "update" functions, so You can test this by editing Panel.qml. Note that "panel" == PanelView.cpp. Video: https://streamable.com/cishh I did try resizing the panel, and the shadow did dissappear. However it did not reappear when I resized it again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384401] Various recognition algorithm improvements for face detection
https://bugs.kde.org/show_bug.cgi?id=384401 caulier.gil...@gmail.com changed: What|Removed |Added Component|Faces-Engine|Faces-Recognition -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 344679] Korganizer no alerts no reminders
https://bugs.kde.org/show_bug.cgi?id=344679 David E. Narvaez changed: What|Removed |Added CC||david.narv...@computer.org -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 384407] New: Amarok crashes when closing it
https://bugs.kde.org/show_bug.cgi?id=384407 Bug ID: 384407 Summary: Amarok crashes when closing it Product: amarok Version: 2.8.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: gat...@grrlz.net Target Milestone: 2.9 Application: amarok (2.8.0) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.10.0-33-generic x86_64 Distribution: KDE neon LTS User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: I closed Amarok by Amarok > Quit This occurs ocasionally when I close Amarok The crash can be reproduced sometimes. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". _IO_flush_all_lockp (do_lock=do_lock@entry=0) at genops.c:779 [Current thread is 1 (Thread 0x7fb47fc0a940 (LWP 1724))] Thread 37 (Thread 0x7fb3dbfff700 (LWP 6475)): #0 0x7fb47b42d360 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb474a8e6c1 in () at /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fb474d9e876 in () at /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fb47b4276ba in start_thread (arg=0x7fb3dbfff700) at pthread_create.c:333 #4 0x7fb47c8913dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 36 (Thread 0x7fb3e18c9700 (LWP 1777)): #0 0x7fb47c85630d in nanosleep () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb47c85625a in __sleep (seconds=0) at ../sysdeps/posix/sleep.c:55 #2 0x7fb47ba1adc5 in () at /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7fb47ba1ae49 in () at /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #4 0x7fb47b4276ba in start_thread (arg=0x7fb3e18c9700) at pthread_create.c:333 #5 0x7fb47c8913dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 35 (Thread 0x7fb3e358c700 (LWP 1774)): #0 0x7fb47b42d360 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb474d6c2dd in () at /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fb474d6c339 in () at /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fb47b4276ba in start_thread (arg=0x7fb3e358c700) at pthread_create.c:333 #4 0x7fb47c8913dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 34 (Thread 0x7fb3f97fa700 (LWP 1773)): #0 0x7fb47b42d360 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb47cf513a6 in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x2d6ca5e0) at thread/qwaitcondition_unix.cpp:86 #2 0x7fb47cf513a6 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x2d6ca4e8, mutex=0x2753640, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7fb47a469c9c in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) (this=0x2d6ca4c0, th=0x7fb3ec092270) at /build/kde4libs-_S4zyz/kde4libs-4.14.16/threadweaver/Weaver/WeaverImpl.cpp:370 #4 0x7fb47a46c993 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) (this=0x27538d0, th=0x7fb3ec092270, previous=0x0) at /build/kde4libs-_S4zyz/kde4libs-4.14.16/threadweaver/Weaver/WorkingHardState.cpp:68 #5 0x7fb47a46c9ac in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) (this=0x27538d0, th=0x7fb3ec092270, previous=0x7fb40007f3f0) at /build/kde4libs-_S4zyz/kde4libs-4.14.16/threadweaver/Weaver/WorkingHardState.cpp:71 #6 0x7fb47a46b4ef in ThreadWeaver::Thread::run() (this=0x7fb3ec092270) at /build/kde4libs-_S4zyz/kde4libs-4.14.16/threadweaver/Weaver/Thread.cpp:98 #7 0x7fb47cf50e3c in QThreadPrivate::start(void*) (arg=0x7fb3ec092270) at thread/qthread_unix.cpp:352 #8 0x7fb47b4276ba in start_thread (arg=0x7fb3f97fa700) at pthread_create.c:333 #9 0x7fb47c8913dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 33 (Thread 0x7fb3f9ffb700 (LWP 1772)): #0 0x7fb47b42d360 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb47cf513a6 in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x2d6ca5e0) at thread/qwaitcondition_unix.cpp:86 #2 0x7fb47cf513a6 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x2d6ca4e8, mutex=0x2753640, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7fb47a469c9c in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) (this=0x2d6ca4c0, th=0x7fb3ec0891f0) at /build/kde4libs-_S4zyz/kde4li
[plasmashell] [Bug 384406] New: plasmashell crashed when quitting iceweasel
https://bugs.kde.org/show_bug.cgi?id=384406 Bug ID: 384406 Summary: plasmashell crashed when quitting iceweasel Product: plasmashell Version: 5.8.7 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: arthur.ma...@internode.on.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.7) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.13.0+ x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: chromium and iceweasel were running. I quit chromum first then iceweasel, when plasmashell restarted. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f331e75a100 (LWP 4276))] Thread 22 (Thread 0x7f321dffb700 (LWP 4573)): #0 0x7f3317c3815f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f33188156cb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3260cb5665 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f3260cb96e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #17 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #18 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #19 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #20 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #21 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #22 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #23 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #24 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #25 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #26 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #27 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #28 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #29 0x7f3260cb9742 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #30 0x7f3260cb482d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #31 0x7f3260cb75ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #32 0x7f331881429d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f3317c32494 in start_thre
[plasmashell] [Bug 384405] New: plasma crashed while showing notification
https://bugs.kde.org/show_bug.cgi?id=384405 Bug ID: 384405 Summary: plasma crashed while showing notification Product: plasmashell Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: icze...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.7.1 Frameworks Version: 5.37.0 Operating System: Linux 4.10.0-33-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: The taskbar seemed to crash due to a notification being shown by an application in the tray area. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0838952280 (LWP 2954))] Thread 10 (Thread 0x7f074f0d2700 (LWP 7792)): #0 0x7f0832525d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0826ee6df1 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f0826ed8601 in pa_mainloop_poll () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f0826ed8c9e in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f0826ed8d50 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f0826ee6d39 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f082612b7d8 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #7 0x7f0831ac76da in start_thread (arg=0x7f074f0d2700) at pthread_create.c:456 #8 0x7f0832531d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 9 (Thread 0x7f0756153700 (LWP 8237)): #0 0x7f082d16bcf4 in g_main_context_query () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f082d16c4e8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f082d16c68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0832e480bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0832df1bea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0832c1ff83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0835ae6df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f0832c24c38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0831ac76da in start_thread (arg=0x7f0756153700) at pthread_create.c:456 #9 0x7f0832531d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 8 (Thread 0x7f076adc9700 (LWP 3636)): #0 0x7f083253fdd0 in __libc_disable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:88 #1 0x7f08325218b9 in read () at ../sysdeps/unix/syscall-template.S:84 #2 0x7f082d1b0b30 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f082d16c042 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f082d16c514 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f082d16c68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f0832e480bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0832df1bea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0832c1ff83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f076d2e65c7 in KCupsConnection::run() () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #10 0x7f0832c24c38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0831ac76da in start_thread (arg=0x7f076adc9700) at pthread_create.c:456 #12 0x7f0832531d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 7 (Thread 0x7f077fcd5700 (LWP 3399)): #0 0x7f082d1b1ef4 in g_mutex_unlock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f082d16c10a in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f082d16c5e0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f082d16c68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0832e480bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0832df1bea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0832c1ff83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f083666b4c6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f0832c24c38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f0831ac76da in start_thread (arg=0x7f077fcd5700) at pthread_create.c:456 #10 0x7f0832531d7f in clone () at
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #67 from Leslie Zhai --- Git commit 329c969be1dbc3455d65925bcad32f4df3a5b428 by Leslie Zhai. Committed on 06/09/2017 at 01:54. Pushed by lesliezhai into branch 'master'. Add BD-RE MediaType as Thomas's idea. M +4-2libk3b/jobs/k3biso9660imagewritingjob.cpp M +6-0libk3b/projects/datacd/k3bdatajob.cpp https://commits.kde.org/k3b/329c969be1dbc3455d65925bcad32f4df3a5b428 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 384387] Name-Value maps - not able to add new key
https://bugs.kde.org/show_bug.cgi?id=384387 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 384155 *** -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 384155] Can't add new keys on 17.08, regression to 17.04
https://bugs.kde.org/show_bug.cgi?id=384155 Christoph Feck changed: What|Removed |Added CC||thors...@tfrey.de --- Comment #3 from Christoph Feck --- *** Bug 384387 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 63749] import and export file format issues (usability)
https://bugs.kde.org/show_bug.cgi?id=63749 --- Comment #3 from Rod Lockwood --- Not that I have any hope that anything will be done about this considering it’s been 14 years since the last comment and nothing seems to have been done. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 63749] import and export file format issues (usability)
https://bugs.kde.org/show_bug.cgi?id=63749 Rod Lockwood changed: What|Removed |Added CC||rodlockw...@provide.net --- Comment #2 from Rod Lockwood --- How about making the import file non-proprietary so anyone can use the same type of file no matter which platform they are using Marble on (KDE, QT/Linux, Windows, or Mac). CSV or TSV are simple text files and easy to explain. Once the person knows to use commas or tabs to separate the fields, any text editor can be used to create an import file. It seems to me that would make adding the feature easier since you only have one file format to deal with. Exporting to either CSV or TSV would be good too, since they can be imported into any spreadsheet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 361426] Crash in KIconLoaderPrivate::findCachedPixmapWithPath and KSharedDataCache
https://bugs.kde.org/show_bug.cgi?id=361426 --- Comment #17 from Michael Pyne --- If deleting files were all BleachBit did, that would still be fine. It would make things unnecessarily slower but that's how the existing code clears the cache, it just unlinks the file and lets the kernel do the rest once the shared memory is unmapped. The problem with BleachBit is far more sinister from this POV: it actually mangles the files, filling them with random data, before unlinking them. I can see the appeal, but running it on files in use is a disaster waiting to happen. It's possible that using /dev/shm directly might be workable on the systems we support though, which may at least workaround BleachBit insanity. But I had thought that BleachBit had already removed the KDE cache directory from its default search path? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 337380] When using Selection Tools, make right-click to bring up the content in Menu>Select
https://bugs.kde.org/show_bug.cgi?id=337380 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Scott Petrovic --- Just pushed out some changes that brings up a context menu for the selection tools. There are quite a few to choose from...and easy to modify if we want to change later. https://cgit.kde.org/krita.git/commit/?id=4cbd177ddea85a405b5640c5874119947a1e4e83 https://phabricator.kde.org/D7412 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 384404] Kate and KWrite both crash when editing a Javascript or CSS file
https://bugs.kde.org/show_bug.cgi?id=384404 Omar Plummer changed: What|Removed |Added CC||omarplummer@imergetechnolog ||ies.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383379] Modernize Input Devices section to work with Libinput
https://bugs.kde.org/show_bug.cgi?id=383379 grouchomarx...@gmail.com changed: What|Removed |Added CC||grouchomarx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369867] Widget searching stopped working on Wayland session.
https://bugs.kde.org/show_bug.cgi?id=369867 David Edmundson changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||k...@davidedmundson.co.uk --- Comment #8 from David Edmundson --- Reopening - but it works fine on my system. - XdgB6 - Qt5.9.nearly2 So when you upgrade to this stuff, please can you report back on this. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384348] Please, put a confirmation dialog for canceling operations
https://bugs.kde.org/show_bug.cgi?id=384348 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/par ||titionmanager/feb2e374e496c ||65011e036f2a611fa7cc5b4e940 Status|ASSIGNED|RESOLVED --- Comment #6 from Andrius Štikonas --- Git commit feb2e374e496c65011e036f2a611fa7cc5b4e940 by Andrius Štikonas. Committed on 05/09/2017 at 23:07. Pushed by stikonas into branch 'master'. Fix a crash when clicking cancel in ApplyProgressDialog. M +2-2src/gui/applyprogressdialog.cpp https://commits.kde.org/partitionmanager/feb2e374e496c65011e036f2a611fa7cc5b4e940 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 384404] New: Kate and KWrite both crash when editing a Javascript or CSS file
https://bugs.kde.org/show_bug.cgi?id=384404 Bug ID: 384404 Summary: Kate and KWrite both crash when editing a Javascript or CSS file Product: kate Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: omarplum...@imergetechnologies.com Target Milestone: --- Application: kwrite (17.11.70) (Compiled from sources) Qt Version: 5.8.1 Frameworks Version: 5.38.0 Operating System: Linux 4.11.6-fossa x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: - What I was doing when the application crashed: Open any Javascript or CSS file (Ruby scripts dont seem to trigger the crash) and type a character on the keyboard or press the ENTER key. NOTE: I have only tested this with JS, CSS and Ruby and HTML source files. So far, the crash only happens with JS and CSS files. The crash can be reproduced every time. -- Backtrace: Application: KWrite (kwrite), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbbdd0057c0 (LWP 12136))] Thread 10 (Thread 0x7fbbab736700 (LWP 12146)): #0 0x7fbbd3ff7f9f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbbb7e92963 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fbbb7e92887 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fbbd3ff2434 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbbd70d7b3d in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fbbabf37700 (LWP 12145)): #0 0x7fbbd3ff7f9f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbbb7e92963 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fbbb7e92887 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fbbd3ff2434 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbbd70d7b3d in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fbbac738700 (LWP 12144)): #0 0x7fbbd3ff7f9f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbbb7e92963 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fbbb7e92887 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fbbd3ff2434 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbbd70d7b3d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fbbacf39700 (LWP 12143)): #0 0x7fbbd3ff7f9f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbbb7e92963 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fbbb7e92887 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fbbd3ff2434 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbbd70d7b3d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fbbad73a700 (LWP 12142)): #0 0x7fbbd3ff7f9f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbbb7e92963 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fbbb7e92887 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fbbd3ff2434 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbbd70d7b3d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fbbae142700 (LWP 12141)): #0 0x7fbbd3ff7f9f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbbb7e92963 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fbbb7e92887 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fbbd3ff2434 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbbd70d7b3d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fbbaea8a700 (LWP 12140)): #0 0x7fbbd3ff7f9f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbbb7e92963 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fbbb7e92887 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fbbd3ff2434 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbbd70d7b3d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fbbc0a2a700 (LWP 12138)): #0 0x7fbbd70cacfd in read () from /lib64/libc.so.6 #1 0x7fbbd060ef60 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fbbd05cc3d2 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fbbd05cc8d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fbbd05cca3c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fbbd803bb47 in QEventDispatcherGlib::processEvents (this=0x7fbbbc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fbbd7fafeb8 in QEventLoop::processEvents (this=0x7fbbc0a29d80, flags=...) at kernel/qeventloop.cpp:134 #7 0x7fbbd7fb01ef in QEventLoop::exec (this=0x7fbbc0a29d80, flags=...) at kernel/qeventloop.cpp:212 #8 0x7fbbd7d51859 in QThread::exec (this=0x7fbbdd154dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 skomorokh changed: What|Removed |Added CC||skomor...@harmless.ca -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 360500] Unable to enter the same value in the No. field for more than 1 transaction.
https://bugs.kde.org/show_bug.cgi?id=360500 --- Comment #8 from Ralf Habacker --- (In reply to Jack from comment #7) > Could there be a "do not show this again" at least system-wide see here https://git.reviewboard.kde.org/r/130241/ > but perhaps per account? not thought about how to implement yet. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 229510] upcoming special dates connection to contacts
https://bugs.kde.org/show_bug.cgi?id=229510 Allen Winter changed: What|Removed |Added CC||win...@kde.org Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Allen Winter --- in the current version there is a context menu where you can send mail to the contact or you can view the person's contact info. should be good enough for this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 384284] Display of upcoming special dates not obeying date range
https://bugs.kde.org/show_bug.cgi?id=384284 --- Comment #7 from Allen Winter --- possible fix up for review at https://phabricator.kde.org/D7702 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369867] Widget searching stopped working on Wayland session.
https://bugs.kde.org/show_bug.cgi?id=369867 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com --- Comment #7 from Dr. Chapatin --- This problem can be reproduced on neon dev. Reopen this report please. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 271746] Special dates doesn't update/redraw itself
https://bugs.kde.org/show_bug.cgi?id=271746 Allen Winter changed: What|Removed |Added Platform|Gentoo Packages |Compiled Sources Status|REOPENED|CONFIRMED --- Comment #6 from Allen Winter --- git master, btw -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 271746] Special dates doesn't update/redraw itself
https://bugs.kde.org/show_bug.cgi?id=271746 Allen Winter changed: What|Removed |Added Resolution|UNMAINTAINED|--- CC||win...@kde.org Status|RESOLVED|REOPENED --- Comment #5 from Allen Winter --- confirm this still happens. there is a missing changed() signal from the kcmsdsummary that needs to update the view. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372114] Crash in threaded KWin::X11StandalonePlatform::createOpenGLSafePoint
https://bugs.kde.org/show_bug.cgi?id=372114 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 374559] Add "Width" and "Height" separately to Additional Information -> Images
https://bugs.kde.org/show_bug.cgi?id=374559 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384394] "Free Space Notifier" notifies should warn you about lack of space on root storage partition, not just home directory
https://bugs.kde.org/show_bug.cgi?id=384394 --- Comment #2 from Piotr Mierzwinski --- Or maybe should warn about / and /home or all mounted in local disk. Anyway would be nice if user would be able to configure (by GUI) these limits and alternatively checking disk/partition. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 375713] Kdenlive crashes if GPU processing (Movit library) is enabled
https://bugs.kde.org/show_bug.cgi?id=375713 Premik changed: What|Removed |Added CC||dospa...@centrum.cz --- Comment #2 from Premik --- I'm getting very similar error on Arch Linux. Simply navigating on the timeline back and forth involves a crash usualy in less than one minute giving: > GL error 0x502 (GL_INVALID_OPERATION) at effect_chain.cpp:1987 Application: 17.11.70 (kdenlive-git 17.11.70.r8553.fdbbf2127-1) MLT version 6.5.0 (mlt-git r4507.1504542481.ecb09b14-1) KDE Frameworks 5.36.0 Qt 5.9.1 (built against 5.9.1) movit-git r815.6538edf-1 Althought the stacktrace is slightly different in my case: #0 0x7ff7bdb288c0 in raise () at /usr/lib/libc.so.6 #1 0x7ff7bdb29f72 in abort () at /usr/lib/libc.so.6 #2 0x7ff791eef54b in movit::abort_gl_error(unsigned int, char const*, int) (err=, filename=filename@entry=0x7ff791f5700b "effect_chain.cpp", line=line@entry=1987) at util.cpp:336 #3 0x7ff791efec83 in movit::EffectChain::execute_phase(movit::Phase*, bool, std::map, std::allocator > >*, std::set, std::allocator >*) (this=this@entry=0x7ff71015a440, phase=, phase@entry=0x7ff71015c0b0, last_phase=last_phase@entry=true, output_textures=output_textures@entry=0x7ff764eae5a0, generated_mipmaps=generated_mipmaps@entry=0x7ff764eae570) at effect_chain.cpp:1987 #4 0x7ff791efef6f in movit::EffectChain::render_to_fbo(unsigned int, unsigned int, unsigned int) (this=this@entry=0x7ff71015a440, dest_fbo=2, width=width@entry=1920, height=height@entry=1080) at effect_chain.cpp:1839 #5 0x7ff792180cd5 in GlslManager::render_frame_rgba(movit::EffectChain*, mlt_frame_s*, int, int, unsigned char**) (this=, chain=chain@entry=0x7ff71015a440, frame=frame@entry=0x7ff69d73e110, width=width@entry=1920, height=height@entry=1080, image=image@entry=0x7ff764eae8c8) at filter_glsl_manager.cpp:473 #6 0x7ff792183ba6 in movit_render (image=0x7ff764eae8c8, height=1080, width=1920, output_format=mlt_image_rgb24a, format=0x101b5e26c, frame=0x7ff69d73e110, chain=0x7ff71015a440) at filter_movit_convert.cpp:454 #7 0x7ff792183ba6 in convert_image(mlt_frame, uint8_t**, mlt_image_format*, mlt_image_format) (frame=0x7ff69d73e110, image=0x7ff764eae8c8, format=0x101b5e26c, output_format=mlt_image_rgb24a) at filter_movit_convert.cpp:573 #8 0x7ff7c473f1e3 in mlt_frame_get_image (self=0x7ff69d73e110, buffer=0x7ff764eae8c8, format=0x101b5e26c, width=0x7ff764eaecf4, height=0x7ff764eaecf8, writable=1) at mlt_frame.c:623 #9 0x7ff7c473f182 in mlt_frame_get_image (self=self@entry=0x7ff69d73e110, buffer=buffer@entry=0x7ff764eae8c8, format=format@entry=0x101b5e26c, width=width@entry=0x7ff764eaecf4, height=height@entry=0x7ff764eaecf8, writable=writable@entry=1) at mlt_frame.c:617 #10 0x7ff77c065a1d in get_image(mlt_frame, uint8_t**, mlt_image_format*, int*, int*, int) (a_frame=a_frame@entry=0x7ff712fe91c0, image=image@entry=0x7ff764eaed08, format=format@entry=0x101b5e26c, width=width@entry=0x7ff764eaecf4, height=height@entry=0x7ff764eaecf8, writable=writable@entry=0) at transition_qtblend.cpp:141 #11 0x7ff7c473f182 in mlt_frame_get_image (self=self@entry=0x7ff712fe91c0, buffer=buffer@entry=0x7ff764eaed08, format=format@entry=0x101b5e26c, width=width@entry=0x7ff764eaecf4, height=height@entry=0x7ff764eaecf8, writable=writable@entry=0) at mlt_frame.c:617 #12 0x7ff7c4754e4b in producer_get_image (self=self@entry=0x7ff6cde2d790, buffer=buffer@entry=0x7ff764eaed08, format=format@entry=0x101b5e26c, width=width@entry=0x7ff764eaecf4, height=height@entry=0x7ff764eaecf8, writable=writable@entry=0) at mlt_tractor.c:370 #13 0x7ff7c473f182 in mlt_frame_get_image (self=self@entry=0x7ff6cde2d790, buffer=buffer@entry=0x7ff764eaed08, format=format@entry=0x101b5e26c, width=width@entry=0x7ff764eaecf4, height=height@entry=0x7ff764eaecf8, writable=writable@entry=0) at mlt_frame.c:617 #14 0x7ff77c058be6 in filter_get_image(mlt_frame, uint8_t**, mlt_image_format*, int*, int*, int) (frame=frame@entry=0x7ff6cde2d790, image=image@entry=0x7ff764eaed08, image_format=image_format@entry=0x101b5e26c, width=width@entry=0x7ff764eaecf4, height=height@entry=0x7ff764eaecf8, writable=writable@entry=0) at filter_audiowaveform.cpp:191 #15 0x7ff7c473f182 in mlt_frame_get_image (self=self@entry=0x7ff6cde2d790, buffer=buffer@entry=0x7ff764eaed08, format=format@entry=0x101b5e26c, width=width@entry=0x7ff764eaecf4, height=height@entry=0x7ff764eaecf8, writable=writable@entry=0) at mlt_frame.c:617 #16 0x7ff7c4752308 in consumer_read_ahead_thread (arg=0x10293ff80) at mlt_consumer.c:821 #17 0x00010037c50e in RenderThread::run() (this=0x7ff7280008e0) at /tmp/makepkg/kdenlive-git/src/kdenlive/src/monitor/glwidget.cpp:1282 #18 0x7ff7be5e115b in () at /usr/lib/libQt5Core.so.5 #19 0x7ff7bbbf9049 in start_thread () at /usr/lib/libpthread.so.0 #20 0
[dolphin] [Bug 367614] Devices in left panel are not alphabetically sorted (order change each time Dolphin is opened)
https://bugs.kde.org/show_bug.cgi?id=367614 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376245] Mouse cursor changes size when pointer on Kwin window title bar
https://bugs.kde.org/show_bug.cgi?id=376245 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377014] Kickoff shows pointing_hand cursor over user icon, but click does nothing if user-manager is not installed
https://bugs.kde.org/show_bug.cgi?id=377014 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #66 from Thomas Schmitt --- Hi, > I get lost ... Please tell me to download the commit Excuse my enthusiasm. :)) And forget about the qDebug() proposal of Comment 62 for now. Edit file libk3b/jobs/k3biso9660imagewritingjob.cpp There are two lines (253 and 264) which each say mt = K3b::Device::MEDIA_WRITABLE_DVD; Those match what your qDebug() reported as "wanted": Any kind of DVD. We want to accept any kind of BD, too. So change both lines to mt = K3b::Device::MEDIA_WRITABLE_DVD | K3b::Device::MEDIA_WRITABLE_BD; build K3B and try whether it now accepts your BD-R. (And also lists "BD-R Sequential (SRM)" among the "wanted" media types.) Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377213] Keyboard shortcut of minimize all windows addon does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377213 Dr. Chapatin changed: What|Removed |Added Summary|Keyboard shortcut for |Keyboard shortcut of |minimize all windows addon |minimize all windows addon |does not work under Wayland |does not work under Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382922] KDENLIVE Highly Unstable when using GPU
https://bugs.kde.org/show_bug.cgi?id=382922 Premik changed: What|Removed |Added CC||dospa...@centrum.cz -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372451] mouse cursor is small in titlebar, large elsewhere
https://bugs.kde.org/show_bug.cgi?id=372451 RussianNeuroMancer changed: What|Removed |Added CC||russianneuroman...@ya.ru --- Comment #11 from RussianNeuroMancer --- skierpage, I guess Wayland issue could be separate issue. It's very consistent for me on real hardware and in KVM with Neon Developer Upstable and Kubuntu 17.10. In both cases issue is always reproducible in Wayland session but never in X11 session. However, I not sure if this bugreport is ok for tracking Wayland issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376245] Mouse cursor changes size when pointer on Kwin window title bar
https://bugs.kde.org/show_bug.cgi?id=376245 RussianNeuroMancer changed: What|Removed |Added CC||russianneuroman...@ya.ru -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 377895] "Close Description" button has UI/UX issues; should just be a regular back button
https://bugs.kde.org/show_bug.cgi?id=377895 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381280] Increased CPU usage with Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=381280 Martin Kostolný changed: What|Removed |Added CC||clearmar...@zoho.com --- Comment #14 from Martin Kostolný --- Hi! I know this is resolved dupl. to another bug but I can see some mentions about weather-widget only here. And that it's possibly causing these high CPU problems - I was redirected here from github page of that widget. I was unfortunately unable to replicate this behaviour on my Arch linux with plasma-applet-weather-widget git version. I have Plasma 5.10.5, KF 5.37, Qt 5.9.1, Xorg, Intel graphics with generic modesetting driver. Is this still an issue? Is it specific for weather-widget for anybody? If it is the case, please let's talk here: https://github.com/kotelnik/plasma-applet-weather-widget/issues/54 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 169405] Save icon size per-directory
https://bugs.kde.org/show_bug.cgi?id=169405 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic to work
https://bugs.kde.org/show_bug.cgi?id=378523 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384403] New: Frequent compositing failure with GTX 1070 and associated Xid 31 error
https://bugs.kde.org/show_bug.cgi?id=384403 Bug ID: 384403 Summary: Frequent compositing failure with GTX 1070 and associated Xid 31 error Product: kwin Version: 5.10.5 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mwo...@gmail.com Target Milestone: --- I am experiencing frequent failure of the kwin compositor since I upgraded my video card from a GTX 670 to a GTX 1070. When the failure occurs the compositor fails to restart so I have to restart kwin to get it back. The failure is always accompanied by an NVRM Xid 31 error. I am able to reliably reproduce the problem using Steam by clicking back and forth between Library and Store rapidly. I have a video of the failure along with the logging here: https://www.youtube.com/watch?v=mW6AM1CauNw I found a Manjaro user reporting the exact same errors, using the same version of kwin, and the same GPU here: https://forum.manjaro.org/t/stupid-issue-with-plasmashell/30425 I have been unable to reproduce the issue when I enable the options "Force Composition Pipeline" and "Force Full Composition Pipeline" in nvidia-settings. I am also unable to reproduce it if I set the compositor to XRender backend. I am able to reproduce it with both the OpenGL 2.0 and OpenGL 3.1 backends. I have tried Nvidia driver versions 381.22, 384.59, and 384.69. The behavior is identical. Here is a snippet of my kwin output: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 3071, resource id: 0, major code: 14 (GetGeometry), minor code: 0 QXcbWindow: Unhandled client message: "_NET_CURRENT_DESKTOP" OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2 OpenGL version string: 4.5.0 NVIDIA 384.69 OpenGL shading language version string: 4.50 NVIDIA Driver: NVIDIA Driver version: 384.69 GPU class: Unknown OpenGL version: 4.5 GLSL version: 4.50 X server version: 1.19.3 Linux kernel version: 4.12.10 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_core: OpenGL 2 compositing setup failed kwin_core: Failed to initialize compositing, compositing disabled QXcbConnection: XCB error: 3 (BadWindow), sequence: 34741, resource id: 485, major code: 3 (GetWindowAttributes), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 34742, resource id: 485, major code: 14 (GetGeometry), minor code: 0 And a snippet from my kernel log: [ 9732.672669] NVRM: GPU at PCI::01:00: GPU-ba0bb41c-e9e7-bf70-8f3b-953075a5dd6e [ 9732.672671] NVRM: GPU Board Serial Number: [ 9732.672673] NVRM: Xid (PCI::01:00): 31, Ch 0058, engmask 0101, intr 1000 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #65 from Cristian Aravena Romero --- Hello, I get lost ... Please tell me to download the commit Regards, -- Cristian -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384348] Please, put a confirmation dialog for canceling operations
https://bugs.kde.org/show_bug.cgi?id=384348 --- Comment #5 from Andrius Štikonas --- The first bad commit is dcdffadc3ec2990b8c4dc4ff101dd2b50d7a: Port away from KDialog. This commit is fairly large but most likely the bug is in applyprogressdialog.cpp -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 323349] Cannot add a new directory service
https://bugs.kde.org/show_bug.cgi?id=323349 --- Comment #2 from Christoffer --- (In reply to Christoffer from comment #1) > Will any action be taken on this ticker ... ? > > 2013 was *5 years* ago. And the issue is still relevant. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 323349] Cannot add a new directory service
https://bugs.kde.org/show_bug.cgi?id=323349 --- Comment #1 from Christoffer --- Will any action be taken on this ticker ... ? 2013 was *5 years* ago. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 366238] KMail does not fetch mails from imap.kabelmail.de
https://bugs.kde.org/show_bug.cgi?id=366238 --- Comment #13 from bugs.kde.or...@gcth.net --- Created attachment 107710 --> https://bugs.kde.org/attachment.cgi?id=107710&action=edit kimap logs from test akonadi instance -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365865] Display resolution setting in Display Configuration not obeyed in Wayland Plasma session
https://bugs.kde.org/show_bug.cgi?id=365865 RussianNeuroMancer changed: What|Removed |Added CC||russianneuroman...@ya.ru --- Comment #3 from RussianNeuroMancer --- > Expected. KScreen's wayland backend so far only supports positioning, not > mode-setting. Sebastian, is there any changes? I tested Kubuntu 17.10 in KVM and find that I can't change screen resolution in Plasma Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 323349] Cannot add a new directory service
https://bugs.kde.org/show_bug.cgi?id=323349 Christoffer changed: What|Removed |Added CC||netrav...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 355338] Double-click on a payee do nothing
https://bugs.kde.org/show_bug.cgi?id=355338 Stephane MANKOWSKI changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Stephane MANKOWSKI --- Not reproduce on Skrooge 2.9.0 with Qt 5.9.1. Reopen it if you can reproduce it on this level. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379637] breeze-gtk should draw shadows for client-side-decorated windows
https://bugs.kde.org/show_bug.cgi?id=379637 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384399] Getting dialog asking for "perform also on grouped images?" when no grouped images are selected
https://bugs.kde.org/show_bug.cgi?id=384399 Simon changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||freisi...@gmail.com --- Comment #1 from Simon --- I will have a look at this -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384402] KWin compositing performance anomaly
https://bugs.kde.org/show_bug.cgi?id=384402 --- Comment #1 from network...@rkmail.ru --- Created attachment 107709 --> https://bugs.kde.org/attachment.cgi?id=107709&action=edit KWin support information -- 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 #67 from Cristóvão Sousa --- Hi all, Can't the same mechanism that decides whether windows are placed in current or all desktops be used for activities? On Tue, Sep 5, 2017 at 9:32 PM Arash B wrote: > https://bugs.kde.org/show_bug.cgi?id=274931 > > --- Comment #66 from Arash B --- > But if you agree with this then first we have to establish that list, and > gather input from others on KWins e-mail-list > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #64 from Thomas Schmitt --- Hi, if the change in line 264 does not help, try the same in line 252 ff.: else if( d->isDvdImage ) mt = K3b::Device::MEDIA_WRITABLE_DVD | K3b::Device::MEDIA_WRITABLE_BD; Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384402] New: KWin compositing performance anomaly
https://bugs.kde.org/show_bug.cgi?id=384402 Bug ID: 384402 Summary: KWin compositing performance anomaly Product: kwin Version: 5.8.7 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: network...@rkmail.ru Target Milestone: --- Flags: Wayland?, X11+ I'm experiencing strange performance issues when using KWin + Desktop Effects + VSync (suspending of desktop effects is disabled). I'm not sure how to describe it correctly, but sometimes it looks like the framerate is really low (around 20fps), despite that various framerate counters may show 160+ fps. The worst thing about it, I cannot reliably reproduce it, most of time the picture is nice and smooth, but sometimes the "visual" framerate would drop for a few seconds and then restore. Switching window focus usually restores the performance. I've also noticed it's somehow related to system's uptime, the longer it runs, the higher is chance to hit the problem. But it's not necessary, sometimes it starts just after boot. It's very annoying, especially if you're playing video games, or watching 60fps videos. There is no framerate drops if I disable VSync, enable desktop effects suppression, or use another window manager, so my guess it that frames get dropped somewhere in the composition pipeline. Hardware: AMD RX480 with amdgpu X driver & Mesa OS: openSUSE 42.3 with Plasma 5.8 Currently, I have Mesa-git, but the problem is also reproducible with Mesa 17.1 I'd like to provide more information, but I don't know what you may need. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 384382] Wrong German translation in Settings dialog of App Launcher
https://bugs.kde.org/show_bug.cgi?id=384382 --- Comment #2 from Gregor Mi --- > If the literal german translation "Anwendungsname anzeigen" for "Show > applications by name" is misleading in german, this misleading would apply > for the english term as well, right? "Anwendungsname anzeigen" is at least more correct than using the word "sortieren" (sort). In my view, having only one checkbox for this kind of subtle option makes it hard to have an intuitive description. > Translation should be consistent with Application Launcher +1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382144] Flash icon when it requests attention, instead of displaying little orange line
https://bugs.kde.org/show_bug.cgi?id=382144 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365036] Cantata MPRIS media controls behave fuzzy
https://bugs.kde.org/show_bug.cgi?id=365036 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com --- Comment #3 from Nate Graham --- Did this patch ever get merged? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384401] New: Various recognition algorithm improvements for face detection
https://bugs.kde.org/show_bug.cgi?id=384401
Bug ID: 384401
Summary: Various recognition algorithm improvements for face
detection
Product: digikam
Version: 5.6.0
Platform: Appimage
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Faces-Recognition
Assignee: digikam-bugs-n...@kde.org
Reporter: jens-bugs.kde@spamfreemail.de
Target Milestone: ---
Here are several things I would very much like improved with the current faces
area in Digikam.
1. The face detection (i.e. "this is a face") works reasonably well but fails
miserably for rotated faces (even 90° and 180°). Please make it detect rotated
faces.
2. The faces detection algorithm does not remember that I deleted an area which
it (wrongly) detected as containing a face. If the image is processed again, it
should not offer this area as a face again.
3. The face *regognition* (i.e. "this is Tim") should respect that the same
face cannot appear in an image multiple times (or rather, that this is a rare
corner case that should be excluded, e.g. when handling collages) and make
according suggestions.
4. The face recognition database should update its guesses ("unconfirmed"
faces) automatically whenever I update a face tag, so that when browsing
through the image collection and correcting face tags subsequent very similar
images which previously also had the same (incorrect) face tag are updated
automatically.
Thank you!
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #63 from Thomas Schmitt ---
Hi,
i found a suspect:
https://cgit.kde.org/k3b.git/tree/libk3b/jobs/k3biso9660imagewritingjob.cpp#n232
void K3b::Iso9660ImageWritingJob::startWriting()
{
...
else {
mt = K3b::Device::MEDIA_WRITABLE_DVD;
}
And no MEDIA_WRITABLE_BD !
This would mean it happens only with image writing but not with
Data Composition. A good explanation why K3B can claim BD capability since
years but does not work for Cristian's use case.
The fog rises up.
---
Coarse test proposal:
Add (actually "or") unconditionally K3b::Device::MEDIA_WRITABLE_BD to mt.
else {
mt = K3b::Device::MEDIA_WRITABLE_DVD | K3b::Device::MEDIA_WRITABLE_BD;
}
Does this change appease that nasty "give me a 21.4 GiB medium" window ?
If this works, then Leslie and i have to riddle whether this is the
final solution and thus what this piece of code does. I have some idea
but that would have to be verified.
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are watching all bug changes.
[drkonqi] [Bug 384400] Segmentation Fault on Bug Report
https://bugs.kde.org/show_bug.cgi?id=384400 William changed: What|Removed |Added CC||wibl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 384400] New: Segmentation Fault on Bug Report
https://bugs.kde.org/show_bug.cgi?id=384400 Bug ID: 384400 Summary: Segmentation Fault on Bug Report Product: drkonqi Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: wibl...@gmail.com Target Milestone: --- Created attachment 107707 --> https://bugs.kde.org/attachment.cgi?id=107707&action=edit Call Stack On use of drkonqi the app crashes on receiving a Segmentation Fault (11) signal. Before that signal I was filling a report for a crash. Please find attached the call stack. -- 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 #66 from Arash B --- But if you agree with this then first we have to establish that list, and gather input from others on KWins e-mail-list -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad
https://bugs.kde.org/show_bug.cgi?id=370588 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 363147] Breeze cursors should have more sizes (patch included)
https://bugs.kde.org/show_bug.cgi?id=363147 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- 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 #65 from Arash B --- @Martin Ok then but we should create such a complete list for the purpose introducing logic that allows us to discern different window elements from each other (for instance for the purpose of determining whether if or not a window element should be on all activities). In the end they are all represented by an instance of the class Client, is this correct? I propose that a new instance variable is introduced in the class Client called kdeWindowType. Its value is decided by an enum with as many possible values as there are discernible types of kde window elements (hence why we need that complete list). But the enum also has an extra value called UNKNOWN. By default, every time a Client instance is created kdeWindowType is simply put to UNKNOWN. No further changes are introduced in your repo at the time. This way this change doesn't break KDE or introduce any new bugs at all, because kdeWindowType is only written to, never read. Then I can hunt down all other KDE git repos where instances of your Client class are created, and ask the devs to correctly set the value of kdeWindowType by passing on the correct argument value (determined by the enum) when making the call to create a Client class. And then in the future, determining the type of a window element will just be a getKdeWindowType() call away... This change will take lots of time but solve many of your problems in the future. Things will have to get messy before they get any better... Do you agree with this? All you have to do is to introduce the class instance variable kdeWindowType and the enum. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375505] [Feature request] Start Player music when headphones are connected
https://bugs.kde.org/show_bug.cgi?id=375505 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX CC||pointedst...@zoho.com --- Comment #3 from Nate Graham --- It's an interesting idea, but there are too many guesses that the system would inevitably get wrong for it to ever work acceptably well. And it's not so hard to just turn on your music player manually. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375860] Crash in QTXML Patterns parsing
https://bugs.kde.org/show_bug.cgi?id=375860 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 340368] group indicators are not properly positioned sometimes
https://bugs.kde.org/show_bug.cgi?id=340368 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #5 from Nate Graham --- The grouping icons are now plus signs and they always appear in the right place for me with a vertical Icons-Only Task manager; can anyone still reproduce this with a more recent version of Plasma (5.9.x+)? -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 320961] "Present Windows Effect" as "Group click action" does not work on tabbed windows.
https://bugs.kde.org/show_bug.cgi?id=320961 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||pointedst...@zoho.com --- Comment #2 from Nate Graham --- This is working for me in Plasma 5 (5.9.4, to be precise). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384399] New: Getting dialog asking for "perform also on grouped images?" when no grouped images are selected
https://bugs.kde.org/show_bug.cgi?id=384399 Bug ID: 384399 Summary: Getting dialog asking for "perform also on grouped images?" when no grouped images are selected Product: digikam Version: 5.6.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Albums-Group Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- When there are grouped images in an album and I select some (but NOT the grouped) images for viewing in the virtual lighttable, Digikam asks me if I want to perform this operation also for grouped images. This doesn't make sense. This question should only be asked when grouped images are actually selected for processing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 311423] showfoto crashes during "restore photograph" resize
https://bugs.kde.org/show_bug.cgi?id=311423 caulier.gil...@gmail.com changed: What|Removed |Added Component|showfoto|ImageEditor-Tool-Resize -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370258] No option to bring forward multiple windows of the same program
https://bugs.kde.org/show_bug.cgi?id=370258 --- Comment #16 from Nate Graham --- *** Bug 384398 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384398] For grouped icons, option to bring forward all windows on click instead of Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=384398 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 370258 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384398] New: For grouped icons, option to bring forward all windows on click instead of Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=384398 Bug ID: 384398 Summary: For grouped icons, option to bring forward all windows on click instead of Present Windows effect Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: pointedst...@zoho.com CC: plasma-b...@kde.org Target Milestone: 1.0 Right now, left-clicking on a grouped icon in the Icons-Only Task Manager activates the Present Windows effect. I would like to instead have it bring forward all windows belonging to the application, mimicking the macOS Dock behavior. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354227] kcm_kscreen is too high
https://bugs.kde.org/show_bug.cgi?id=354227 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kcm ||utils/54090d12b3b72a07b57c1 ||7d22b15bd0f80b3c55d --- Comment #32 from Albert Astals Cid --- Git commit 54090d12b3b72a07b57c17d22b15bd0f80b3c55d by Albert Astals Cid, on behalf of Valeriy Malov. Committed on 05/09/2017 at 20:18. Pushed by aacid into branch 'master'. Make KCMultiDialog scrollable Summary: Put KCModuleProxy into a QScrollArea the same way SystemSettings does This should make kcmshell and other users of KCMultiDialog a bit more friendly to small screens However, this assumes that KCMs don't have their own scrollbars (at least sytsemsettings ones don't) and preferably have a size hint (only a few or none actually have; at least kscreen needs patching) Also, reorder headers of the unit Test Plan: doesn't break systemsettings/kcmshell/kmail settings kcmshell kscreen takes some time initializing so it starts very small (patch ready) Reviewers: #frameworks, davidedmundson Reviewed By: davidedmundson Subscribers: davidedmundson, wbauer, broulik Tags: #frameworks Differential Revision: https://phabricator.kde.org/D7487 M +25 -18 src/kcmultidialog.cpp https://commits.kde.org/kcmutils/54090d12b3b72a07b57c17d22b15bd0f80b3c55d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370258] No option to bring forward multiple windows of the same program
https://bugs.kde.org/show_bug.cgi?id=370258 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||pointedst...@zoho.com Ever confirmed|0 |1 --- Comment #15 from Nate Graham --- I would also like this and am also fine with minimized windows' ordering being untracked. It could be as simple as this: - First un-minimize minimized windows, in any order - Then, activate non-minimized windows, in reverse order such that the most-recently-used window winds up on top -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384397] New: Wish: detect / recognize faces option during import (as postprocessing step)
https://bugs.kde.org/show_bug.cgi?id=384397 Bug ID: 384397 Summary: Wish: detect / recognize faces option during import (as postprocessing step) Product: digikam Version: 5.6.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import-PostProcessing Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Currently detecting faces is a separate step which can become tedious since this is usually only done once per image / album and the albums must be selected manually (Digikam does not remember which images/albums it has already processed to skip them). So the easiest way to process all images for faces *once* is to do it directly during import (in the background, after import has been finished). Would it be possible to integrate the faces detection dialog into the import workflow? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384348] Please, put a confirmation dialog for canceling operations
https://bugs.kde.org/show_bug.cgi?id=384348 --- Comment #4 from Andrius Štikonas --- Cancellation works safely in the last kde4 based version 1.1.0 but doesn't work in 1.2.0. So it looks like KF5 porting bug :(. I'll try to bisect it further to see if I can determine which commit caused this. By the way, the dialog is actually shown in kde4 version. What happens here is that as soon as "Cancel" is clicked, KDE Partition Manager grays it out and waits until current operation is completed and then asks whether to cancel the remaining operations. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357264] Icons overlape others widgets on panel
https://bugs.kde.org/show_bug.cgi?id=357264 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Nate Graham --- Haven't been able to reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344123] Colorize entry background based on icon color
https://bugs.kde.org/show_bug.cgi?id=344123 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||pointedst...@zoho.com Resolution|--- |WONTFIX --- Comment #5 from Nate Graham --- Yeah, since now the background color indicated status, I don't think we can implement an average background color purely for aesthetics. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384396] New: Wish: display faces sorted by similarity (pre-grouped) instead of album/time/..
https://bugs.kde.org/show_bug.cgi?id=384396 Bug ID: 384396 Summary: Wish: display faces sorted by similarity (pre-grouped) instead of album/time/.. Product: digikam Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- When detecting faces, there are often a high number of similar images (and identical faces in different images). I would like an option where the newly processed images with "unknown" and "unconfirmed" faces are *already* grouped by face so that confirming a face (or creating a new one) is much quicker. Correcting such a detection can then be achieved by moving a face from one group to the other. Note: I do not want the *images* to be grouped, but the *faces*. This means that images with multiple people on them will of course appear in multiple face groups. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 373791] Crash on exit
https://bugs.kde.org/show_bug.cgi?id=373791 --- Comment #7 from Christoph Feck --- Leszek, what you see is probably bug 378469. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355837] Icons-only task manager: Layout broken if required space exceeds available space
https://bugs.kde.org/show_bug.cgi?id=355837 Nate Graham changed: What|Removed |Added CC||igs...@gmail.com --- Comment #10 from Nate Graham --- *** Bug 364198 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364198] Item missing in icons-only task manager on a resizable panel when widgets unlocked.
https://bugs.kde.org/show_bug.cgi?id=364198 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||pointedst...@zoho.com --- Comment #1 from Nate Graham --- Feels like a duplicate of https://bugs.kde.org/show_bug.cgi?id=355837 *** This bug has been marked as a duplicate of bug 355837 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361030] Show window title in Icon-Only Task Manager Tooltips
https://bugs.kde.org/show_bug.cgi?id=361030 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||pointedst...@zoho.com Resolution|--- |FIXED --- Comment #3 from Nate Graham --- We show the window titles now as of KF 5.31/Plasma 5.94, at least. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383202] System tray icon's context menu isn't updated properly in plasma/x11
https://bugs.kde.org/show_bug.cgi?id=383202 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384348] Please, put a confirmation dialog for canceling operations
https://bugs.kde.org/show_bug.cgi?id=384348 --- Comment #3 from whoisr...@openmailbox.org --- I was moving the LUKS partition when the crash occurred. I tried to reproduce the the bug again by resizing and moving the EFI partition of the disk and cancelling the operation as soon as possible. It destroyed the partition table of the disk (no problem, the data was already lost anyway). I'm using the default installed version of partitionmanager on a live usb of Kubuntu 17.04. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383374] Kate crashed when opening a file in KDE Connect sftp mountpoint
https://bugs.kde.org/show_bug.cgi?id=383374 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 372196 *** -- You are receiving this mail because: You are watching all bug changes.
