[kdevelop] [Bug 391897] lldb debugger "setting set takes more arguments"
https://bugs.kde.org/show_bug.cgi?id=391897 Kevin Funkchanged: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||velop/63819c741f7263d754f17 ||d8dfa60caa198e751a7 Version Fixed In||5.2.2 --- Comment #5 from Kevin Funk --- FYI: commit 63819c741f7263d754f17d8dfa60caa198e751a7 (HEAD -> 5.2, origin/5.2) Author: Peifeng Yu <7437...@gmail.com> Date: Tue Mar 20 14:39:22 2018 -0400 lldb: don't issue command when there's no env variables to set, fix Bug 391897 Summary: LLDB becomes stricter about the `settings set target.env-vars` command. Now it doens't allow empty arguments. This causes a warning when start debugging session in KDevelop. https://bugs.kde.org/show_bug.cgi?id=391897 Test Plan: - Created a new project with an empty environment variable profile - Start debugging with lldb - No warnings Reviewers: apol, #kdevelop Reviewed By: apol, #kdevelop Subscribers: kdevelop-devel Differential Revision: https://phabricator.kde.org/D11524 (cherry picked from commit 3fd20921df6a9d69c54bfc1add86f42185652148) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 188192] Checkboard in the browse window
https://bugs.kde.org/show_bug.cgi?id=188192 Huonchanged: What|Removed |Added CC||h...@plonq.org --- Comment #4 from Huon --- We'd need to do something about the filenames of the thumbnails. Quite hard to read text on a checkerboard background. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392143] [regression] ”Save attachments…” is not offered anymore if multiple messages are selected
https://bugs.kde.org/show_bug.cgi?id=392143 Burkhard Lueckchanged: What|Removed |Added CC||lu...@hube-lueck.de --- Comment #1 from Burkhard Lueck --- Ubuntu 17.10 kmail2 5.5.3 KDE Frameworks 5.43.0 Qt 5.9.1 Selecting multiple messages in the messagelist I have the option ”Save attachments…” in the context menu. Please provide infos about your system and version of kmail + frameworks -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 392153] Cursor won't go from a screen to another if there is blank space in the middle
https://bugs.kde.org/show_bug.cgi?id=392153 Martin Flöserchanged: What|Removed |Added Product|kwin|KScreen Version|git master |git Component|platform-wayland|common CC||mgraess...@kde.org Assignee|kwin-bugs-n...@kde.org |se...@kde.org --- Comment #1 from Martin Flöser --- That setup is not allowed by KWin. Kscreen should ensure that all screens are adjacent. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391548] Drag and drop to desktop fails
https://bugs.kde.org/show_bug.cgi?id=391548 Tonychanged: What|Removed |Added CC||jodr...@live.com --- Comment #2 from Tony --- Created attachment 111551 --> https://bugs.kde.org/attachment.cgi?id=111551=edit If you refer to this It is working as intended. If you want a "direct" drag/drop as in Windows, please make a request here in the bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392163] New: Crash when opening Flatpak
https://bugs.kde.org/show_bug.cgi?id=392163 Bug ID: 392163 Summary: Crash when opening Flatpak Product: Discover Version: 5.12.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: f.alexander.wi...@gmail.com Target Milestone: --- Application: plasma-discover (5.12.2) Qt Version: 5.9.4 Frameworks Version: 5.44.0 Operating System: Linux 4.15.6-300.fc27.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Double clicked on a Flatpak bundle in Dolphin. Tried it with Octave.flatpak built from these sources: https://github.com/flathub/org.octave.Octave/tree/fed0fb5b2573bab3e69722466ab9b595e45ef9fe and Flare.flatpak build from these sources: https://github.com/flathub/org.flarerpg.Flare The crash can be reproduced every time. -- Backtrace: Application: Entdecken (plasma-discover), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f364454e8c0 (LWP 7981))] Thread 12 (Thread 0x7f35c6ffd700 (LWP 8099)): #0 0x7f3636fdb34f in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #1 0x7f3636fdbdcb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f3636fdbfac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f363f225c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f363f1d396a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f363f0248ca in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f363f028de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f363bf7550b in start_thread () from /lib64/libpthread.so.0 #8 0x7f363e3da16f in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f35c67fc700 (LWP 8098)): #0 0x7f363e3cb738 in read () from /lib64/libc.so.6 #1 0x7f36370200a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f3636fdb9a8 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f3636fdbe40 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f3636fdbfac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f363f225c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f363f1d396a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f363f0248ca in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f363f028de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f363bf7550b in start_thread () from /lib64/libpthread.so.0 #10 0x7f363e3da16f in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f35f099d700 (LWP 8065)): #0 0x7f363f2257a5 in socketNotifierSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #1 0x7f3636fdb3f9 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f3636fdbdcb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f3636fdbfac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f363f225c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f363f1d396a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f363f0248ca in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f363f028de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f363bf7550b in start_thread () from /lib64/libpthread.so.0 #9 0x7f363e3da16f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f35c7fff700 (LWP 8000)): #0 0x7f363e3cfc6b in poll () from /lib64/libc.so.6 #1 0x7f3636fdbe99 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f3636fdc232 in g_main_loop_run () from /lib64/libglib-2.0.so.0 #3 0x7f35f7894b56 in gdbus_shared_thread_func () from /lib64/libgio-2.0.so.0 #4 0x7f3637003486 in g_thread_proxy () from /lib64/libglib-2.0.so.0 #5 0x7f363bf7550b in start_thread () from /lib64/libpthread.so.0 #6 0x7f363e3da16f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f35e8ff9700 (LWP 7999)): #0 0x7f363e3cb738 in read () from /lib64/libc.so.6 #1 0x7f36370200a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f3636fdb9a8 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f3636fdbe40 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f3636fdbfac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f3636fdbff1 in glib_worker_main () from /lib64/libglib-2.0.so.0 #6 0x7f3637003486 in g_thread_proxy () from /lib64/libglib-2.0.so.0 #7 0x7f363bf7550b in start_thread () from /lib64/libpthread.so.0 #8
[Breeze] [Bug 390550] Can't resize windows due to no borders
https://bugs.kde.org/show_bug.cgi?id=390550 --- Comment #2 from scionicspec...@gmail.com --- We've been trying to find the best way around this while preserving client-side decorations for a long time now. So long as GTK's CSD implementation relies on undocumented behavior in Mutter-like compositors, it looks like the only long-term solution will be to force KWin's server-side decorations on these applications. This should be negotiated properly in the Wayland session, but for X11 we will have to make some sort of script to force SSDs, something which was possible in the past but might require us to name each specific GTK CSD application in recent versions of GTK. Just letting everyone know the situation and why we can't get normal invisible resize areas around GTK's CSD windows. Other CSD-using applications appear to work, however, just not with GTK. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388804] [Request] Actions service menu for images: "Set as wallpaper"
https://bugs.kde.org/show_bug.cgi?id=388804 Tonychanged: What|Removed |Added Summary|Actions service menu for|[Request] Actions service |images: "Set as wallpaper" |menu for images: "Set as ||wallpaper" CC||jodr...@live.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392098] Display Bug - Icon missing
https://bugs.kde.org/show_bug.cgi?id=392098 --- Comment #2 from Tony--- Created attachment 111550 --> https://bugs.kde.org/attachment.cgi?id=111550=edit Confirmed? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392098] Display Bug - Icon missing
https://bugs.kde.org/show_bug.cgi?id=392098 Tonychanged: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- Can confirm this one on Opensuse Tumbleweed. Seems more like a packaging issue to me, i am not expert though. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371574] Dolphin crashes after Konsole-button related operations
https://bugs.kde.org/show_bug.cgi?id=371574 Tonychanged: What|Removed |Added CC||notux...@gmail.com --- Comment #4 from Tony --- *** Bug 391888 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391888] Dolphin crashed after closing it's window
https://bugs.kde.org/show_bug.cgi?id=391888 Tonychanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||jodr...@live.com Resolution|--- |DUPLICATE --- Comment #1 from Tony --- *** This bug has been marked as a duplicate of bug 371574 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 383101] Baloo crashed out of nowhere
https://bugs.kde.org/show_bug.cgi?id=383101 --- Comment #3 from Tony--- *** Bug 383334 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 383334] Baloo daemon crash
https://bugs.kde.org/show_bug.cgi?id=383334 Tonychanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Tony --- *** This bug has been marked as a duplicate of bug 383101 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392162] Floating point exception when using speficic selection and applying blur efect
https://bugs.kde.org/show_bug.cgi?id=392162 --- Comment #1 from Petr Nehez--- The report above is from version 4.0.0.51 beta build from AUR but I get the same exception when I install 3.3.3 from Manjaro's repository. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392162] New: Floating point exception when using speficic selection and applying blur efect
https://bugs.kde.org/show_bug.cgi?id=392162 Bug ID: 392162 Summary: Floating point exception when using speficic selection and applying blur efect Product: krita Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: petr.ne...@gmail.com Target Milestone: --- Application: Krita (krita), signal: Floating point exception Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f3ea06800 (LWP 13808))] Thread 12 (Thread 0x7f1ed7fff700 (LWP 13876)): #0 0x7f1f352bc6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbaee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3bcb6db1 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 11 (Thread 0x7f1eed9b1700 (LWP 13874)): [KCrash Handler] #6 0x7f1f090e9d8d in ?? () from /usr/lib/kritaplugins/kritaextensioncolorsfilters.so #7 0x7f1f3e194902 in KisFilterStrokeStrategy::doStrokeCallback(KisStrokeJobData*) () from /usr/lib/libkritaui.so.16 #8 0x7f1f394fd33c in ?? () from /usr/lib/libkritaimage.so.16 #9 0x7f1f3bcb6b22 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #11 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #12 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 10 (Thread 0x7f1eef0f4700 (LWP 13873)): #0 0x7f1f352bc6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbaee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3bcb6db1 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f1eed1b0700 (LWP 13872)): #0 0x7f1f352bc6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbaee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3bcb6db1 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f1eec9af700 (LWP 13871)): #0 0x7f1f352bc6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbaee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3bcb6db1 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f1eef8f5700 (LWP 13821)): #0 0x7f1f352bc3bd in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbb02c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3ce45586 in ?? () from /usr/lib/libQt5Widgets.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f1ef00f6700 (LWP 13820)): #0 0x7f1f33769b94 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f1f337229f2 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f1f33722f96 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f1f3372310e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f1f3bf03314 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f1f3bea53db in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f1f3bcb47ae in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f1f2223250b in ?? () from /usr/lib/libQt5Quick.so.5 #8 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f1f01027700 (LWP 13819)): #0 0x7f1f33769b94 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f1f33722fad in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1f3372310e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f1f3bf03314 in
[systemsettings] [Bug 391162] Not Asking to Save settings on change
https://bugs.kde.org/show_bug.cgi?id=391162 Dr. Chapatinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Dr. Chapatin --- *** This bug has been marked as a duplicate of bug 392160 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392160] No prompt when switching with unsaved changes
https://bugs.kde.org/show_bug.cgi?id=392160 Dr. Chapatinchanged: What|Removed |Added CC||rizzite...@kde.org --- Comment #1 from Dr. Chapatin --- *** Bug 391162 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392161] New: Default pixel grid start showing too early during zooming
https://bugs.kde.org/show_bug.cgi?id=392161 Bug ID: 392161 Summary: Default pixel grid start showing too early during zooming Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: tyson...@mail.com Target Milestone: --- krita-4.1.0-pre-alpha-cc28a62-x86_64 The current default threshold for pixel grid start showing is 800%. However, after working intensively for a pixel art style game for more than a year now, I came to the conclusion that 800% is way too early. 800% is a sweet spot where I zoom out to see the whole design while each pixel is still big enough to be painted precisely. But the grid gets in the way here so I found myself changing this value every time after reinstalling an OS. >From my experience, a value of 2400% is more appropriate. Since new users don't know where, or even if they can change this value at all, I suggest we change the default value to 2400% for better first impression and less fuss. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389967] systemsettings5 crashes on launch
https://bugs.kde.org/show_bug.cgi?id=389967 rfe.gribovs...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from rfe.gribovs...@gmail.com --- After one of updates it works fine. Works on plasma version 5.12.3, framework 5.44.0, qt 5.10.0. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360464] settings crash when filtered by "window"
https://bugs.kde.org/show_bug.cgi?id=360464 David Edmundsonchanged: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346850] configurator login screen (SDDM) did not start.
https://bugs.kde.org/show_bug.cgi?id=346850 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from David Edmundson --- Crash is in Qt and it's a really old Qt, please reopen if it's still a problem -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 266518] systemsettings as root crashed
https://bugs.kde.org/show_bug.cgi?id=266518 David Edmundsonchanged: What|Removed |Added Resolution|--- |UNMAINTAINED CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391252] Baloo unable to find files in hidden folders
https://bugs.kde.org/show_bug.cgi?id=391252 Nate Grahamchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373735] System Settings is closed
https://bugs.kde.org/show_bug.cgi?id=373735 David Edmundsonchanged: What|Removed |Added Resolution|--- |UPSTREAM CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Edmundson --- Haven't seen another report of this, and the crash is upstream in Qt. Please reopen if you still have an issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364524] kcmshell5 kcm_sddm dumps core everytime it is executed
https://bugs.kde.org/show_bug.cgi?id=364524 David Edmundsonchanged: What|Removed |Added Status|CONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 352554] Apps crash on exit
https://bugs.kde.org/show_bug.cgi?id=352554 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Crash is in Qt, and that Qt listed is really old. Please reopen if you still have this issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 387444] Crash when removing shortcuts group
https://bugs.kde.org/show_bug.cgi?id=387444 David Edmundsonchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389967] systemsettings5 crashes on launch
https://bugs.kde.org/show_bug.cgi?id=389967 David Edmundsonchanged: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- >Related to/duplicate of bug 383828. I'm not sure it is, there's no object being shared between two engines, and the trace is a bit different. Do you still have the crash on launch? If you can run it in valgrind that would be very useful. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392160] New: No prompt when switching with unsaved changes
https://bugs.kde.org/show_bug.cgi?id=392160 Bug ID: 392160 Summary: No prompt when switching with unsaved changes Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: k...@davidedmundson.co.uk Target Milestone: --- In icon mode: Open a module, click on a different module or click "all settings" you get a dialog "the settings of the current modeule have changed blah blah" In the sidebar view: change to a different module. Nothing happens Could be a sign of a much bigger bug (leaking KCMs) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390005] crash during search
https://bugs.kde.org/show_bug.cgi?id=390005 David Edmundsonchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391651] [Wayland] Crash when I click "Choose" button
https://bugs.kde.org/show_bug.cgi?id=391651 Dr. Chapatinchanged: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #2 from Dr. Chapatin --- I'm using Wayland session on neon dev unstable right now. Stll crashing. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344801] Plasma 5 kcminit5 often crashes on login
https://bugs.kde.org/show_bug.cgi?id=344801 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |WORKSFORME --- Comment #1 from David Edmundson --- Crash is in Qt, the Qt listed is really old. I don't think there's much we can do. Please reopen if it's still an issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340605] kcmshell4 crash when closing with authorisation dialog open
https://bugs.kde.org/show_bug.cgi?id=340605 David Edmundsonchanged: What|Removed |Added Resolution|--- |UNMAINTAINED CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Plasma 4 is unmaintained for bugs, hopefully this was fixed in the meantime. Closing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392159] New: Term splitting interprets protocol part of URLs as property
https://bugs.kde.org/show_bug.cgi?id=392159 Bug ID: 392159 Summary: Term splitting interprets protocol part of URLs as property Product: frameworks-baloo Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: stefan.bru...@rwth-aachen.de Target Milestone: --- The query parser splits every term containing e.g. : or =, interpreting the parts infront and after the separator as property and value. This has two implications: - Typing into krunner e.g. "firefox http://www.kde.org; is interpreted as searching for the property "http". This creates a log of debug output: 'baloorunner[...]: Property "http" not found" - Searching for "http://www.kde.org; returns no result, even if it should. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391651] [Wayland] Crash when I click "Choose" button
https://bugs.kde.org/show_bug.cgi?id=391651 David Edmundsonchanged: What|Removed |Added Resolution|--- |WORKSFORME CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- There are no version numbers here, but I can see QtWayland has changed a lot since this was reported. closestShellSurfaceWindow has moved 200 lines I think this is something I fixed. Please repoen if not -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 --- Comment #8 from Jesse--- I just, accidentally, changed the version of this bug. I meant to edit the bug I reported but I had two tabs opened and edited this by mistake. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392158] New cursor KCM: buttons/dropdown appear in wrong position or become unvailable when the window is resized
https://bugs.kde.org/show_bug.cgi?id=392158 --- Comment #1 from Dr. Chapatin--- youtube link because file size limit here https://www.youtube.com/watch?v=7eJpsiP1vmU -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 Jessechanged: What|Removed |Added CC||jesse...@gmail.com Version|5.11.1 |5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392158] New: New cursor KCM: buttons/dropdown appear in wrong position or become unvailable when the window is resized
https://bugs.kde.org/show_bug.cgi?id=392158 Bug ID: 392158 Summary: New cursor KCM: buttons/dropdown appear in wrong position or become unvailable when the window is resized Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Watch my screencast and observe the position of the drop down and buttons on bottom of the window. After to maximize the window, drop down and buttons appear centered (wrong position) After to unmaximize the window, drop down is cut off and the buttons are unvailable. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 391462] Accent free search
https://bugs.kde.org/show_bug.cgi?id=391462 Stefan Brünschanged: What|Removed |Added CC||stefan.bruens@rwth-aachen.d ||e --- Comment #1 from Stefan Brüns --- Can you please provide the output of the command: balooshow -x -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 281232] Samba configuration
https://bugs.kde.org/show_bug.cgi?id=281232 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |UNMAINTAINED --- Comment #2 from David Edmundson --- Plasma 4 is closed for crash fixes, closing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 276981] Crash while adding custom shortcut.
https://bugs.kde.org/show_bug.cgi?id=276981 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||k...@davidedmundson.co.uk --- Comment #9 from David Edmundson --- Plasma 4 is closed for crash fixes, closing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 297481] Switching from the mouse to the joystick settings caused it to crash
https://bugs.kde.org/show_bug.cgi?id=297481 David Edmundsonchanged: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Plasma 4 is closed for crash fixes, closing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 310071] Settings crash when adding a custom key shortcut
https://bugs.kde.org/show_bug.cgi?id=310071 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Plasma 4 is closed for crash fixes, closing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 288300] Systemsettings crashed on Windows if you change the style under details & comit it, always
https://bugs.kde.org/show_bug.cgi?id=288300 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Both Plasma4 and Plasma on windows are unmaintained for crash fixes, closing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 286383] crash by update
https://bugs.kde.org/show_bug.cgi?id=286383 David Edmundsonchanged: What|Removed |Added Resolution|--- |UNMAINTAINED CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED --- Comment #15 from David Edmundson --- Plasma 4 is unmaintained for crash fixes, closing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 305061] Crash during configuring displays in systemsettings
https://bugs.kde.org/show_bug.cgi?id=305061 --- Comment #8 from David Edmundson--- Still relevant in 5, see final linked report -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391252] Baloo unable to find files in hidden folders
https://bugs.kde.org/show_bug.cgi?id=391252 Stefan Brünschanged: What|Removed |Added CC||stefan.bruens@rwth-aachen.d ||e --- Comment #7 from Stefan Brüns --- Regarding files not found in hidden directories: This is a design decision. Baloo is meant to help finding files the user has created or received from another person (this includes downloading files from the internet). Configuration files and the like are clearly not in this scope. Many users are not even aware of hidden files/directories, and these are not shown by default in e.g. dolphin. IMHO it would be quite awkward if these files showed up during a search. Files in hidden directories are only useful for power users/developers, which are typically capable of using e.g. find and grep. These configuration files are also typically in plain text format, so searching with grep works, while formats like ODF, PDF, ... do not store text as plain text, these documents are exemplary for the baloo scope. Regarding the "log.txt" file, please file another bug report. This neither matches the bug description (which has a number of implications: hard to find when searching for it, bad reference/description when the bug has been confirmed and fixed, ...) and does not obey the "One bug per bug report". This may sound somewhat discouraging, but rest assured that bugs like the second are definitely a concern for past as well as current developers. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 305061] Crash during configuring displays in systemsettings
https://bugs.kde.org/show_bug.cgi?id=305061 David Edmundsonchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392157] System Settings crash on applying hotkey change
https://bugs.kde.org/show_bug.cgi?id=392157 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |UNMAINTAINED --- Comment #1 from David Edmundson --- >/kde-workspace-4.11.2 Plasma 4 is unmtained for bugfixes, sorry -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392012] Duplicated global menu when using mnemonics in undecorated windows
https://bugs.kde.org/show_bug.cgi?id=392012 Jessechanged: What|Removed |Added Target Milestone|--- |1.0 Assignee|plasma-b...@kde.org |k...@privat.broulik.de CC||plasma-b...@kde.org Product|kded-appmenu|plasmashell Component|menu popup |Global Menu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392157] New: System Settings crash on applying hotkey change
https://bugs.kde.org/show_bug.cgi?id=392157 Bug ID: 392157 Summary: System Settings crash on applying hotkey change Product: systemsettings Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mdi...@golem2.net Target Milestone: --- Application: systemsettings (4.11.22) KDE Platform Version: 4.14.33 Qt Version: 4.8.6 Operating System: Linux 4.4.114-42-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: System settings, Personalized hotkeys, Browser, Conditions, Active window: Webbrowsers, Edit..., Window simple: Firefox, Edit, modify regular expression, OK, OK, Apply -> crash -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x0021 in ?? () #7 0x7fae3d215ad6 in qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/QtCore/qalgorithms.h:322 #8 qDeleteAll (c=...) at /usr/include/QtCore/qalgorithms.h:330 #9 ConditionsWidget::copyToObject (this=0x1d2e970) at /usr/src/debug/kde-workspace-4.11.22/khotkeys/kcm_hotkeys/conditions/conditions_widget.cpp:177 #10 0x7fae3d216d0d in HotkeysWidgetBase::apply (this=0x1e1ca60) at /usr/src/debug/kde-workspace-4.11.22/khotkeys/kcm_hotkeys/hotkeys_widget_base.cpp:46 #11 0x7fae3d201d30 in KCMHotkeysPrivate::save (this=0x1dd58e0) at /usr/src/debug/kde-workspace-4.11.22/khotkeys/kcm_hotkeys/kcm_hotkeys.cpp:363 #12 0x7fae3d20256d in KCMHotkeys::save (this=0x1c36140) at /usr/src/debug/kde-workspace-4.11.22/khotkeys/kcm_hotkeys/kcm_hotkeys.cpp:271 #13 0x7fae5b6e38a7 in KCModuleProxy::save (this=) at /usr/src/debug/kdelibs-4.14.33/kutils/kcmoduleproxy.cpp:280 #14 0x7fae5b90ff43 in ModuleView::moduleSave (this=, module=) at /usr/src/debug/kde-workspace-4.11.22/systemsettings/core/ModuleView.cpp:289 #15 0x7fae5b9118da in ModuleView::qt_static_metacall (_o=, _id=, _a=0x7fff2bfaee70, _c=) at /usr/src/debug/kde-workspace-4.11.22/build/systemsettings/core/ModuleView.moc:71 #16 0x7fae599120ea in QMetaObject::activate (sender=sender@entry=0x1ac0ce0, m=m@entry=0x7fae5b0521e0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff2bfaee70) at kernel/qobject.cpp:3576 #17 0x7fae5abce372 in QAbstractButton::clicked (this=this@entry=0x1ac0ce0, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219 #18 0x7fae5a932723 in QAbstractButtonPrivate::emitClicked (this=this@entry=0x1ad4fe0) at widgets/qabstractbutton.cpp:548 #19 0x7fae5a933893 in QAbstractButtonPrivate::click (this=this@entry=0x1ad4fe0) at widgets/qabstractbutton.cpp:541 #20 0x7fae5a93397c in QAbstractButton::mouseReleaseEvent (this=0x1ac0ce0, e=0x7fff2bfaf360) at widgets/qabstractbutton.cpp:1123 #21 0x7fae5a5d4bba in QWidget::event (this=0x1ac0ce0, event=0x7fff2bfaf360) at kernel/qwidget.cpp:8389 #22 0x7fae5a5856fc in QApplicationPrivate::notify_helper (this=this@entry=0x1643400, receiver=receiver@entry=0x1ac0ce0, e=e@entry=0x7fff2bfaf360) at kernel/qapplication.cpp:4565 #23 0x7fae5a58bd7a in QApplication::notify (this=this@entry=0x7fff2bfafba0, receiver=receiver@entry=0x1ac0ce0, e=e@entry=0x7fff2bfaf360) at kernel/qapplication.cpp:4108 #24 0x7fae5b29ce9a in KApplication::notify (this=0x7fff2bfafba0, receiver=0x1ac0ce0, event=0x7fff2bfaf360) at /usr/src/debug/kdelibs-4.14.33/kdeui/kernel/kapplication.cpp:311 #25 0x7fae598fe17d in QCoreApplication::notifyInternal (this=0x7fff2bfafba0, receiver=receiver@entry=0x1ac0ce0, event=event@entry=0x7fff2bfaf360) at kernel/qcoreapplication.cpp:953 #26 0x7fae5a58b573 in QCoreApplication::sendEvent (event=, receiver=) at ../../src/corelib/kernel/qcoreapplication.h:231 #27 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x1ac0ce0, event=event@entry=0x7fff2bfaf360, alienWidget=alienWidget@entry=0x1ac0ce0, nativeWidget=nativeWidget@entry=0x17c6650, buttonDown=buttonDown@entry=0x7fae5b064258 , lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3173 #28 0x7fae5a5fcc4b in QETWidget::translateMouseEvent (this=this@entry=0x17c6650, event=event@entry=0x7fff2bfaf6d0) at kernel/qapplication_x11.cpp:4530 #29 0x7fae5a5fb6bc in QApplication::x11ProcessEvent (this=0x7fff2bfafba0, event=event@entry=0x7fff2bfaf6d0) at kernel/qapplication_x11.cpp:3653 #30 0x7fae5a622552 in x11EventSourceDispatch (s=0x16436d0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #31 0x7fae520ed134 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #32 0x7fae520ed388 in ?? () from /usr/lib64/libglib-2.0.so.0 #33
[krunner] [Bug 391250] Plasha crashed when opening Virtualbox by Application Menu
https://bugs.kde.org/show_bug.cgi?id=391250 Christoph Feckchanged: What|Removed |Added Component|general |filesearch Product|plasmashell |krunner Target Milestone|1.0 |--- Assignee|k...@davidedmundson.co.uk|baloo-bugs-n...@kde.org Severity|normal |crash --- Comment #1 from Christoph Feck --- Crash is either in the runner, in solid, or caused by memory corruption anywhere. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 392156] New: Konqueror does not start when I click "show in folder" on google-chrome
https://bugs.kde.org/show_bug.cgi?id=392156 Bug ID: 392156 Summary: Konqueror does not start when I click "show in folder" on google-chrome Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: marcelo.jime...@gmail.com Target Milestone: --- Application: kdeinit5 (5.0.97) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.15.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was trying to open konqueror in the directory where I downloaded a PDF document, but Konqueror did not start when I click "show in folder" on google-chrome. -- Backtrace: Application: Konqueror (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 28return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7f560b7548c0 (LWP 6712))] Thread 3 (Thread 0x7f55df5f8700 (LWP 6715)): #0 0x7f5609830d9f in __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67 #1 0x7f5609819166 in __GI___poll (fds=0x7f55d80049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0x7f5605d05109 in g_idle_add () at /usr/lib64/libglib-2.0.so.0 #3 0x7f55d8001e80 in () #4 0x000105d2203d in () #5 0x7fff in () #6 0xb9e490d9c162ff00 in () #7 0x0005 in () #8 0x7f55d8000bf0 in () #9 0x0001 in () #10 0x0004 in () #11 0x7f55d8000b20 in () #12 0x in () Thread 2 (Thread 0x7f55f2506700 (LWP 6714)): #0 0x7f5609814bf4 in __GI___libc_read (fd=8, buf=0x7f55f2505ad0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f5605d49420 in g_unix_fd_add_full () at /usr/lib64/libglib-2.0.so.0 #2 0x7f55e4000bf0 in () #3 0x7f55e4000bf0 in () #4 0x7f55e4000bf0 in () #5 0xb9e490d9c162ff00 in () #6 0x in () Thread 1 (Thread 0x7f560b7548c0 (LWP 6712)): [KCrash Handler] #6 0xb716 in () #7 0x7f55d3231901 in () at /usr/lib64/libgobject-2.0.so.0 #8 0x7f560b5aa40a in call_init (l=, argc=argc@entry=5, argv=argv@entry=0x7ffc90c54e08, env=env@entry=0x5625d5d0cda0) at dl-init.c:72 #9 0x7f560b5aa516 in call_init (env=0x5625d5d0cda0, argv=0x7ffc90c54e08, argc=5, l=) at dl-init.c:118 #10 0x7f560b5aa516 in _dl_init (main_map=main_map@entry=0x5625d646f680, argc=5, argv=0x7ffc90c54e08, env=0x5625d5d0cda0) at dl-init.c:119 #11 0x7f560b5ae67f in dl_open_worker (a=a@entry=0x7ffc90c52420) at dl-open.c:511 #12 0x7f560985fe5f in __GI__dl_catch_exception (exception=exception@entry=0x7ffc90c52400, operate=operate@entry=0x7f560b5ae2c0 , args=args@entry=0x7ffc90c52420) at dl-error-skeleton.c:196 #13 0x7f560b5adf1a in _dl_open (file=0x5625d6402338 "/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so", mode=-2147479551, caller_dlopen=0x7f5609d7324c, nsid=, argc=5, argv=, env=0x5625d5d0cda0) at dl-open.c:594 #14 0x7f5608d06f96 in dlopen_doit (a=a@entry=0x7ffc90c52650) at dlopen.c:66 #15 0x7f560985fe5f in __GI__dl_catch_exception (exception=exception@entry=0x7ffc90c525f0, operate=operate@entry=0x7f5608d06f40 , args=args@entry=0x7ffc90c52650) at dl-error-skeleton.c:196 #16 0x7f560985feef in __GI__dl_catch_error (objname=objname@entry=0x5625d5c75ae0, errstring=errstring@entry=0x5625d5c75ae8, mallocedp=mallocedp@entry=0x5625d5c75ad8, operate=operate@entry=0x7f5608d06f40 , args=args@entry=0x7ffc90c52650) at dl-error-skeleton.c:215 #17 0x7f5608d07685 in _dlerror_run (operate=operate@entry=0x7f5608d06f40 , args=args@entry=0x7ffc90c52650) at dlerror.c:162 #18 0x7f5608d07051 in __dlopen (file=, mode=) at dlopen.c:87 #19 0x7f5609d7324c in () at /usr/lib64/libQt5Core.so.5 #20 0x7f5609d6ca75 in () at /usr/lib64/libQt5Core.so.5 #21 0x7f55fbe01052 in () at /usr/lib64/libphonon4qt5.so.4 #22 0x7f55fbe02c2c in () at /usr/lib64/libphonon4qt5.so.4 #23 0x7f55fbe030ae in () at /usr/lib64/libphonon4qt5.so.4 #24 0x7f55fbe03a2c in Phonon::Factory::backend(bool) () at /usr/lib64/libphonon4qt5.so.4 #25 0x7f55fbe03fb3 in () at /usr/lib64/libphonon4qt5.so.4 #26 0x7f55fbdf9331 in () at /usr/lib64/libphonon4qt5.so.4 #27 0x7f55fbdf6820 in () at /usr/lib64/libphonon4qt5.so.4 #28 0x7f55fc4f729a in () at /usr/lib64/libKF5Notifications.so.5 #29 0x7f55fc4d1b51 in () at /usr/lib64/libKF5Notifications.so.5 #30 0x7f55fc4ce764 in KNotification::sendEvent() () at /usr/lib64/libKF5Notifications.so.5 #31 0x7f5609da5c52 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #32 0x7f560843001c in
[systemsettings] [Bug 392155] New cursor KCM: Theme preview shows bigger cursors under Wayland
https://bugs.kde.org/show_bug.cgi?id=392155 Dr. Chapatinchanged: What|Removed |Added Summary|New cursor KCM: Theme |New cursor KCM: Theme |preview shos bigger cursors |preview shows bigger |under Wayland |cursors under Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392155] New cursor KCM: Theme preview shos bigger cursors under Wayland
https://bugs.kde.org/show_bug.cgi?id=392155 --- Comment #1 from Dr. Chapatin--- Created attachment 111549 --> https://bugs.kde.org/attachment.cgi?id=111549=edit cursor kcm under Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392155] New: New cursor KCM: Theme preview shos bigger cursors under Wayland
https://bugs.kde.org/show_bug.cgi?id=392155 Bug ID: 392155 Summary: New cursor KCM: Theme preview shos bigger cursors under Wayland Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 111548 --> https://bugs.kde.org/attachment.cgi?id=111548=edit cursor kcm under X11 Compare screenshots taken under X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 392154] New: Atadenoise frame count is broken
https://bugs.kde.org/show_bug.cgi?id=392154 Bug ID: 392154 Summary: Atadenoise frame count is broken Product: kdenlive Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: sund...@iki.fi Target Milestone: --- In the Atadenoise filter the av.s frame count parameter can only be 5. If set to anything else the result is not denoised properly. Sometimes the beginning of the video gets included twice. Steps to reproduce: 1. Add the Atadenoise filter to a noisy clip. 2. Set Atadenoise's av.s value to, say, 6. 3. Render. Expected results: 6 frame averaging denoising. Actual results: No denoising. Possibly starting with a duplicate section of the beginning of the clip. Kdenlive: 18.03.70 MLT: 6.7.0 Kubuntu: 18.04 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392153] New: Cursor won't go from a screen to another if there is blank space in the middle
https://bugs.kde.org/show_bug.cgi?id=392153 Bug ID: 392153 Summary: Cursor won't go from a screen to another if there is blank space in the middle Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: aleix...@kde.org Target Milestone: --- Created attachment 111547 --> https://bugs.kde.org/attachment.cgi?id=111547=edit Impossible love story I can't move my cursor from the laptop screen to system settings. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 392152] New: Broken display set up recovery
https://bugs.kde.org/show_bug.cgi?id=392152 Bug ID: 392152 Summary: Broken display set up recovery Product: KScreen Version: 1.0.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kded Assignee: se...@kde.org Reporter: aleix...@kde.org Target Milestone: --- Screens were placed far apart and the cursor won't travel from a screen to another. I never chose to have it this way, so it's probably a bug when figuring out the position of the screens. In case it helps, I usually extend vertically. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392151] New cursor KCM: Breeze theme is duplicated when a new theme is installed
https://bugs.kde.org/show_bug.cgi?id=392151 --- Comment #1 from Dr. Chapatin--- Created attachment 111546 --> https://bugs.kde.org/attachment.cgi?id=111546=edit demonstration -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392151] New: New cursor KCM: Breeze theme is duplicated when a new theme is installed
https://bugs.kde.org/show_bug.cgi?id=392151 Bug ID: 392151 Summary: New cursor KCM: Breeze theme is duplicated when a new theme is installed Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Watch my screencast recorded on neon dev unstable please. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391910] New kcm to configure cursor theme has large space in the sides
https://bugs.kde.org/show_bug.cgi?id=391910 --- Comment #1 from Dr. Chapatin--- Created attachment 111545 --> https://bugs.kde.org/attachment.cgi?id=111545=edit unmaximized system settings > cursor kcm Situation is worst when the window is unmaximized. -- You are receiving this mail because: You are watching all bug changes.
[KReport] [Bug 390199] Please make sdc.py work also with (or switch it to) Python 3
https://bugs.kde.org/show_bug.cgi?id=390199 Jarosław Staniekchanged: What|Removed |Added Latest Commit||https://commits.kde.org/kre ||port/f57a3a36f08b444bf4249a ||3286798a94469d2184 Version Fixed In||3.1.0 -- You are receiving this mail because: You are watching all bug changes.
[KReport] [Bug 390199] Please make sdc.py work also with (or switch it to) Python 3
https://bugs.kde.org/show_bug.cgi?id=390199 Jarosław Staniekchanged: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[KDb] [Bug 390198] Please make sdc.py work also with (or switch it to) Python 3
https://bugs.kde.org/show_bug.cgi?id=390198 Jarosław Staniekchanged: What|Removed |Added Latest Commit|https://commits.kde.org/kre |https://cgit.kde.org/kdb.gi |port/f57a3a36f08b444bf4249a |t/commit/?h=3.1=7e5633c3 |3286798a94469d2184 |6316cd8cf180eae982c5bc4574b ||b62bf -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 362647] Can't search with Chinese characters
https://bugs.kde.org/show_bug.cgi?id=362647 --- Comment #8 from GuHua--- Stefan, thanks for the suggestion of writting test cases. Yes, searching in character level (grapheme, if I understand this word correctly) is far better than nothing. To what I know (as a native Chinese speaker), many (or even most) Chinese people are happy enough if the software can deal with things in character level. Actually, using a dictionary is still not enough for Chinese -- it often happens that three (or more) character can be split in two different ways and they both make sense without context. A simple example of this scenario could be "化學生": both "化學" (chemistry) and "學生" (student) make sense (moreover, sometimes "化學生" also makes sense, meaning "a student whose major is in chemistry"), so context is the only way we can tell how to correctly split them (e.g. "教化學生" will most likely be split into "教化" [enlighten/teach] and "學生" [student]). Correctly handling of Chinese words requires more sophisticated Natural Language Processing techniques (e.g. using machine learning), and I think that would be far beyond today's baloo (or maybe even any search / index engines). (I have studied machine learning and natural language processing during my masters, so it should be safe for me to say that today's NLP technique [for Chinese word-splitting] is not yet good enough to be used in production [compared with character level and judged in a user's sense, i.e. false positive is better than false negative].) Classical Chinese (this is a style of composing sentences and ways of understanding characters / words, not like the different between "Traditional Chinese" and "Simplified Chinese") makes the situation more difficult. Almost all historical texts (e.g. history recordings / books / poems) (there are quite a LOT) are written in Classical Chinese, and nowadays Chinese people still study Classical Chinese and read those things (though we usually don't write in Classical Chinese). Even humans may still need some effort to read a piece of text written in Classical Chinese (but Classical Chinese is very very consise, that's one of the reasons it exists). However, in Classical Chinese, characters "are" words in many cases. Splitting by characters is a very good choice. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 377038] Spectacle crashes when the option "Rectangular Region" is selected.
https://bugs.kde.org/show_bug.cgi?id=377038 Christoph Feckchanged: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Christoph Feck --- No response, changing status. If you have new information, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[KReport] [Bug 390199] Please make sdc.py work also with (or switch it to) Python 3
https://bugs.kde.org/show_bug.cgi?id=390199 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Christoph Feck --- No response, assuming it was. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371875] Plasma 5 Desktop shows Black bar on Second screen in ultra-wide UW-UXGA (2560x1080) resolution
https://bugs.kde.org/show_bug.cgi?id=371875 David Edmundsonchanged: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #11 from David Edmundson --- please can you run kquitapp5 plasmashell QSG_INFO=1 plasmashell and paste the output here -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 Sebastian Schraderchanged: What|Removed |Added CC||sebastian.schrader@ossmail. ||de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392134] SIGSEGV While Scanning Faces
https://bugs.kde.org/show_bug.cgi?id=392134 --- Comment #6 from nroycea+...@gmail.com --- with debug: * ... digikam.general: Check for finish: 51 packages, 0 infos to filter, hasFinished() false Thread 1673 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff087f0700 (LWP 23667)] 0x00329e92d3c8 in operator==(QString const&, QString const&) () from /tmp/.mount_digikajZHvp3/usr/lib/libQt5Core.so.5 (gdb) bt #0 0x00329e92d3c8 in operator==(QString const&, QString const&) () from /tmp/.mount_digikajZHvp3/usr/lib/libQt5Core.so.5 #1 0x76696895 in Digikam::LoadingDescription::equalsIgnoreReducedVersion (this=, other=...) at /b/dktemp/digikam-v5.8.0/core/libs/threadimageio/loadingdescription.cpp:295 #2 0x766a2f3b in Digikam::SharedLoadingTask::notifyNewLoadingProcess (this=0x3fa5290, process=, description=...) at /b/dktemp/digikam-v5.8.0/core/libs/threadimageio/loadsavetask.cpp:421 #3 0x766994a0 in Digikam::LoadingCache::notifyNewLoadingProcess (this=this@entry=0x7d68a0, process=process@entry=0x4661358, description=...) at /b/dktemp/digikam-v5.8.0/core/libs/threadimageio/loadingcache.cpp:243 #4 0x766a5dd7 in Digikam::PreviewLoadingTask::execute (this=0x4661160) at /b/dktemp/digikam-v5.8.0/core/libs/threadimageio/previewtask.cpp:162 #5 0x76690892 in Digikam::LoadSaveThread::run (this=0x463c9a0) at /b/dktemp/digikam-v5.8.0/core/libs/threadimageio/loadsavethread.cpp:133 #6 0x766ce87e in Digikam::DynamicThread::DynamicThreadPriv::run (this=0x463dbd0) at /b/dktemp/digikam-v5.8.0/core/libs/threads/dynamicthread.cpp:183 #7 0x00329e8ab8bd in ?? () from /tmp/.mount_digikajZHvp3/usr/lib/libQt5Core.so.5 #8 0x00329e8ae9ba in ?? () from /tmp/.mount_digikajZHvp3/usr/lib/libQt5Core.so.5 #9 0x75d9108c in start_thread () from /usr/lib/libpthread.so.0 #10 0x7fffed8b3e7f in clone () from /usr/lib/libc.so.6 (gdb) thread apply all backtrace Thread 2000 (Thread 0x7fff097fa700 (LWP 24343)): #0 0x7fffed8a997b in poll () from /usr/lib/libc.so.6 #1 0x7fffecebeff3 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fffecebf10e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00329eadc9a7 in QEventDispatcherGlib::processEvents(QFlags) () from /tmp/.mount_digikajZHvp3/usr/lib/libQt5Core.so.5 #4 0x00329ea8b35a in QEventLoop::exec(QFlags) () from /tmp/.mount_digikajZHvp3/usr/lib/libQt5Core.so.5 #5 0x766cccec in Digikam::WorkerObjectRunnable::run (this=0x3ec7a70) at /b/dktemp/digikam-v5.8.0/core/libs/threads/threadmanager.cpp:192 #6 0x00329e8ab8bd in ?? () from /tmp/.mount_digikajZHvp3/usr/lib/libQt5Core.so.5 #7 0x00329e8ae9ba in ?? () from /tmp/.mount_digikajZHvp3/usr/lib/libQt5Core.so.5 #8 0x75d9108c in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fffed8b3e7f in clone () from /usr/lib/libc.so.6 Thread 1683 (Thread 0x7fff0affd700 (LWP 23684)): #0 0x75d9a988 in read () from /usr/lib/libpthread.so.0 #1 0x7fffe859fb52 in ?? () from /tmp/.mount_digikajZHvp3/usr/plugins/sqldrivers/libqsqlite.so #2 0x7fffe85a13a3 in ?? () from /tmp/.mount_digikajZHvp3/usr/plugins/sqldrivers/libqsqlite.so #3 0x7fffe85e1ca5 in ?? () from /tmp/.mount_digikajZHvp3/usr/plugins/sqldrivers/libqsqlite.so #4 0x7fffe85e2b37 in ?? () from /tmp/.mount_digikajZHvp3/usr/plugins/sqldrivers/libqsqlite.so #5 0x7fffe85e994b in ?? () from /tmp/.mount_digikajZHvp3/usr/plugins/sqldrivers/libqsqlite.so #6 0x7fffe86099ab in ?? () from /tmp/.mount_digikajZHvp3/usr/plugins/sqldrivers/libqsqlite.so #7 0x7fffe8612867 in ?? () from /tmp/.mount_digikajZHvp3/usr/plugins/sqldrivers/libqsqlite.so #8 0x7fffe8594825 in ?? () from /tmp/.mount_digikajZHvp3/usr/plugins/sqldrivers/libqsqlite.so #9 0x7fffe8595a43 in ?? () from /tmp/.mount_digikajZHvp3/usr/plugins/sqldrivers/libqsqlite.so #10 0x0032a68119b2 in QSqlQuery::exec() () from /tmp/.mount_digikajZHvp3/usr/lib/libQt5Sql.so.5 #11 0x764664e8 in Digikam::BdEngineBackend::exec (this=0x766470, query=...) at /b/dktemp/digikam-v5.8.0/core/libs/database/engine/dbenginebackend.cpp:1432 #12 0x76466c0c in Digikam::BdEngineBackend::execQuery
[plasmashell] [Bug 371875] Plasma 5 Desktop shows Black bar on Second screen in ultra-wide UW-UXGA (2560x1080) resolution
https://bugs.kde.org/show_bug.cgi?id=371875 --- Comment #10 from GHPS--- Created attachment 111544 --> https://bugs.kde.org/attachment.cgi?id=111544=edit Kubuntu 18.04 Screenshot after Boot into Live system with black bar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371875] Plasma 5 Desktop shows Black bar on Second screen in ultra-wide UW-UXGA (2560x1080) resolution
https://bugs.kde.org/show_bug.cgi?id=371875 --- Comment #9 from GHPS--- I've just tested the upcoming version of Kubuntu 18.04 with Plasma 5.12.3 and Qt 5.94. The daily build shows no changes concerning the black bar on the desktop. Chances are high that this annoying bug will find it's way into the next LTS version... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 391861] Massif Assertion 'n_ips >= 1 && n_ips <= VG_(clo_backtrace_size)'
https://bugs.kde.org/show_bug.cgi?id=391861 --- Comment #4 from Philippe Waroquiers--- fixed (or rather bypassed) in commit 4c9bd311660bf4c1f9228519223214b6a50935ec -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 391861] Massif Assertion 'n_ips >= 1 && n_ips <= VG_(clo_backtrace_size)'
https://bugs.kde.org/show_bug.cgi?id=391861 Philippe Waroquierschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 259678] Partitionmanager should not require root privileges to start.
https://bugs.kde.org/show_bug.cgi?id=259678 --- Comment #21 from Michael D--- Nice! -- You are receiving this mail because: You are watching all bug changes.
[kwebkitpart] [Bug 382641] Build kwebkitpart as module
https://bugs.kde.org/show_bug.cgi?id=382641 Rex Dieterchanged: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392134] SIGSEGV While Scanning Faces
https://bugs.kde.org/show_bug.cgi?id=392134 Maik Qualmannchanged: What|Removed |Added CC||metzping...@gmail.com --- Comment #5 from Maik Qualmann --- The AppImage has a built-in GDB, use the "debug" option. Can you post the result? Maik -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 346445] Crash on exit after opening GIF animation
https://bugs.kde.org/show_bug.cgi?id=346445 Henrik Fehlauerchanged: What|Removed |Added Resolution|--- |UPSTREAM CC||rk...@lab12.net Status|UNCONFIRMED |RESOLVED --- Comment #17 from Henrik Fehlauer --- This GIF somehow made it into my collection of test images, and I never experienced a crash in the last months. Backtrace looks a bit like it might have been a problem in Qt. No more duplicates since a while too, so therefore let's close the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392150] New: Discover Constantly Crashing on NEON OS
https://bugs.kde.org/show_bug.cgi?id=392150 Bug ID: 392150 Summary: Discover Constantly Crashing on NEON OS Product: Discover Version: 5.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: pinstriped...@yahoo.com Target Milestone: --- Every time I go to update after initial installation of the OS, Discover CRASHES!! Reboot and try again... Same thing. I had to update the system using Apt-Get, but the Updates icon in the panel still says there are updates and so I click on it and BAM... CRASH!! Everything else seems to be working fine on my DELL Optiplex 760 desktop and my HP 14" Pavilion laptop. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 390550] Can't resize windows due to no borders
https://bugs.kde.org/show_bug.cgi?id=390550 Dr. Chapatinchanged: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 259678] Partitionmanager should not require root privileges to start.
https://bugs.kde.org/show_bug.cgi?id=259678 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #20 from Andrius Štikonas --- The GUI of KDE Partition Manager can now run as unprivileged user. So far code is still in kauth branches of kpmcore and partitionmanager but it's getting to the state where testing and reviews would be useful. Especially, security review of the helper would be appreciated as it is used quite differently from normal KAuth helper. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 392149] New: Option to not recalibrate PHD2 when starting guiding from scheduler
https://bugs.kde.org/show_bug.cgi?id=392149 Bug ID: 392149 Summary: Option to not recalibrate PHD2 when starting guiding from scheduler Product: kstars Version: git Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jarno.paana...@gmail.com Target Milestone: --- Currently Ekos always clears calibration from PHD2 when starting guiding which is both annoying and detrimental when you already have a good calibration done and fixed setup. I commented out this part from the source myself, but it would be nice to have it as an option. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 331864] Merge Tags with same name when moving to same hierarchy level
https://bugs.kde.org/show_bug.cgi?id=331864 Maik Qualmannchanged: What|Removed |Added CC||metzping...@gmail.com --- Comment #5 from Maik Qualmann --- Note: Like renaming or moving tags, this is a pure database operation. The merging the tags also updates the face regions. The metadata must still be e.g. with the maintenance tool into the images are written. For the automatic update we have another bug report. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382115] Rendering artifacts on desktop Icon Text after resume from suspend.
https://bugs.kde.org/show_bug.cgi?id=382115 Layne Parlorchanged: What|Removed |Added CC||laynepar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 347302] reassign name to face
https://bugs.kde.org/show_bug.cgi?id=347302 Maik Qualmannchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||6.0.0 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dig ||ikam/7c7d9c8d6aafb2cb6fa65f ||9015c1f2cf03426e5c --- Comment #4 from Maik Qualmann --- Git commit 7c7d9c8d6aafb2cb6fa65f9015c1f2cf03426e5c by Maik Qualmann. Committed on 21/03/2018 at 20:41. Pushed by mqualmann into branch 'master'. implement merge tags function by drag and drop Related: bug 331864 FIXED-IN: 6.0.0 M +3-3NEWS M +60 -3core/libs/album/albummanager.cpp https://commits.kde.org/digikam/7c7d9c8d6aafb2cb6fa65f9015c1f2cf03426e5c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 331864] Merge Tags with same name when moving to same hierarchy level
https://bugs.kde.org/show_bug.cgi?id=331864 Maik Qualmannchanged: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/7c7d9c8d6aafb2cb6fa65f ||9015c1f2cf03426e5c Status|CONFIRMED |RESOLVED Version Fixed In||6.0.0 Resolution|--- |FIXED --- Comment #4 from Maik Qualmann --- Git commit 7c7d9c8d6aafb2cb6fa65f9015c1f2cf03426e5c by Maik Qualmann. Committed on 21/03/2018 at 20:41. Pushed by mqualmann into branch 'master'. implement merge tags function by drag and drop Related: bug 347302 FIXED-IN: 6.0.0 M +3-3NEWS M +60 -3core/libs/album/albummanager.cpp https://commits.kde.org/digikam/7c7d9c8d6aafb2cb6fa65f9015c1f2cf03426e5c -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 391464] KDEConnect does not browse my external SD correctly
https://bugs.kde.org/show_bug.cgi?id=391464 pchanged: What|Removed |Added CC||peter.mueller_1...@yahoo.co ||m --- Comment #3 from p --- I have the same issue on an S8. If you give me a hint where in the Android code this part is executed I could try to debug the code a little bit. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343938] Konsole handles dead keys and Compose incorrectly
https://bugs.kde.org/show_bug.cgi?id=343938 --- Comment #7 from f...@windfisch.org --- Created attachment 111543 --> https://bugs.kde.org/attachment.cgi?id=111543=edit xev excerpt from pressing -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343938] Konsole handles dead keys and Compose incorrectly
https://bugs.kde.org/show_bug.cgi?id=343938 --- Comment #6 from f...@windfisch.org --- I don't have ibus installed on any of my systems; also, I just checked with the `xev` tool: upon pressing , it produces the attached log. Most importantly, it features: ... KeyPress event, serial 33, synthetic NO, window 0x2e1, root 0x4e8, subw 0x0, time 22618620, (214,139), root:(218,867), state 0x0, keycode 44 (keysym 0x6a, j), same_screen YES, XLookupString gives 1 bytes: (6a) "j" XmbLookupString gives 1 bytes: (6a) "j" XFilterEvent returns: True KeyPress event, serial 33, synthetic NO, window 0x2e1, root 0x4e8, subw 0x0, time 22618620, (214,139), root:(218,867), state 0x0, keycode 0 (keysym 0x10003b8, U03B8), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 2 bytes: (ce b8) "θ" XFilterEvent returns: False ... Which suggests to me that any X11 application should "just work". What could cause this issue here, shouldn't it work fine without ibus installed, too? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 380269] [PATCH] No multithreading in macOS Sierra (10.12)
https://bugs.kde.org/show_bug.cgi?id=380269 Manodeep Sinhachanged: What|Removed |Added CC||manod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 392148] New: No connection for a MicroTouch focuser
https://bugs.kde.org/show_bug.cgi?id=392148 Bug ID: 392148 Summary: No connection for a MicroTouch focuser Product: kstars Version: 2.9.3 Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jcjes...@free.fr Target Milestone: --- Created attachment 111542 --> https://bugs.kde.org/attachment.cgi?id=111542=edit MicroTouch focuser I followed the "StellarMate Tutorials - Part 4" to assign permanent designations to my serial-to-USB adapters (scope Celestron GPS + dome MaxDome II) and my MicroTouch focuser. I only succeeded to map the focuser, not the scope and the dome. However, now, I cannot connect my focuser directly to KStars anymore. I checked that the baud rate was correct (19200). My setup works because I can connect the scope, the dome and the focuser to TheSkyX. I started a de novo installation of KStars (I trashed the app KStars and the folder /Application Support/kstars) : but the problem was still present and I couldn't connect the focuser (see the attached screenshot). Do you have any idea ? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391897] lldb debugger "setting set takes more arguments"
https://bugs.kde.org/show_bug.cgi?id=391897 Aetf <7437...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391778] FreeRDP second Full-Screen Monitor is hidden
https://bugs.kde.org/show_bug.cgi?id=391778 --- Comment #21 from Robert Cheramy--- Thank you very much Martin for your help! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343938] Konsole handles dead keys and Compose incorrectly
https://bugs.kde.org/show_bug.cgi?id=343938 Egmont Koblingerchanged: What|Removed |Added CC||egm...@gmail.com --- Comment #5 from Egmont Koblinger --- (In reply to flo from comment #4) > 1. xmodmap -e 'keycode 94 = dead_greek' > 2. in konsole, press your dead_greek key, then press j Works correctly for me (produces θ) in konsole 17.12.3, under Unity 7 desktop environment on Ubuntu Bionic beta. So it probably depends on some lower level setting or software component, maybe ibus??? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392064] New text tool doesn't use the SVG property for RTL text
https://bugs.kde.org/show_bug.cgi?id=392064 --- Comment #5 from Safa Alfulaij--- Thanks a lot Dmitry! I was wondering why we don't use just http://doc.qt.io/qt-5/qstring.html#isRightToLeft... Or even http://doc.qt.io/qt-5/qtextblock.html#textDirection :) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 392147] New: Properly handle ELF files
https://bugs.kde.org/show_bug.cgi?id=392147 Bug ID: 392147 Summary: Properly handle ELF files Product: kde Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: i...@gassmann.io Target Milestone: --- It shouldn't be necessary for the end-user to modify the permission of an AppImage file to execute it. It's not an intuitive use case. AppImage being an ELF file. Quoting: " Desktop environments should ask the user whether to set the executable bit and then run the application when the user double-clicks on an ELF file that doesn't have the executable bit set. ... It should ask "do you want to mark this application as executable and launch it?". " More information: https://github.com/AppImage/AppImageKit/issues/374 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, mdir_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 Matthias Bruggerchanged: What|Removed |Added Assignee|matthias@gmail.com |jsew...@acm.org -- You are receiving this mail because: You are watching all bug changes.