[plasmashell] [Bug 407041] New: Desktop Panel "Visibility" Settings Not Available Through Scripting
https://bugs.kde.org/show_bug.cgi?id=407041 Bug ID: 407041 Summary: Desktop Panel "Visibility" Settings Not Available Through Scripting Product: plasmashell Version: 5.15.2 Platform: Other OS: Linux Status: REPORTED Severity: task Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: chaseva...@gmail.com Target Milestone: 1.0 There is no scripting interface to set a panels "Visibility" option. Additionally, if this option (for my test it was [PlasmaViews][Panel 173]panelVisibility in ~/plasmashellrc) is changed in a script or with kwriteconfig5, calling the panel's reloadConfig() method does not reload this option. To me the issue appears to partially stem from this particular option not being saved in the same file and group as other panel options, so I think reloadConfig() does not catch the change. As far as visibility not being scriptable, I'm not surprised it hasn't been caught because it's probably not common, I came across this with a pretty obscure use-case. Anyway, it looks like this other bug is related: https://bugs.kde.org/show_bug.cgi?id=396796 , bug id #396796 In my personal case, I want to toggle between panelVisibility 0 and 3 which are "Always Visible" and "Windows Can Cover." I can get the same functionality I need by going another route, but I think it would be better if I could do it with plasma scripting. To be clear, I would expect that the Panel object in the scripting interface would have a method to change the visibility option. Additionally, if this option gets changed, the reloadConfig() method should reflect the changed option. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406995] Improve the readability of "This effect is not a benchmark" text shown while Show FPS effect is enabled
https://bugs.kde.org/show_bug.cgi?id=406995 Vlad Zagorodniy changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406101] Window "Keep above" overrides "Show Desktop"
https://bugs.kde.org/show_bug.cgi?id=406101 Vlad Zagorodniy changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INTENTIONAL |--- --- Comment #6 from Vlad Zagorodniy --- Well, no. The bug is still there. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407034] Editing an image in the Image editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407034 --- Comment #3 from Maik Qualmann --- Yes that's the cause, you've written in sidecar and now has disabled again. I have to see why the image editor, although disabled, reads from the sidecar. Maik -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 407025] xdg-desktop-portal-kde 5.15.4 segmentation faults in gbm_device_destroy at gbm.c:109 in mesa-libgbm when logging out of Plasma
https://bugs.kde.org/show_bug.cgi?id=407025 Jan Grulich changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/xdg ||-desktop-portal-kde/29609c3 ||eb0a40c37a610f68ec9c9b9d991 ||3b555f --- Comment #1 from Jan Grulich --- Git commit 29609c3eb0a40c37a610f68ec9c9b9d9913b555f by Jan Grulich. Committed on 29/04/2019 at 06:11. Pushed by grulich into branch 'Plasma/5.15'. Destroy gbm_device only when it's initialized M +1-1src/waylandintegration.cpp https://commits.kde.org/xdg-desktop-portal-kde/29609c3eb0a40c37a610f68ec9c9b9d9913b555f -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407034] Editing an image in the Image editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407034 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Problem is not reproduce here. The "video date" can only add the TimeAdjust Tool or the Metadata Editor. Where else is there no code for it. The Image Editor only copies the metadata from the original image. Does a sidecar file exist? Maik -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 406810] Dolphin consumes a lot of CPU when Vault is open for a while
https://bugs.kde.org/show_bug.cgi?id=406810 --- Comment #2 from Ivan Čukić --- Ineresting. What happens if it is a manually created cryfs/encfs drive? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396024] Allow per-site configuration of JavaScript
https://bugs.kde.org/show_bug.cgi?id=396024 --- Comment #5 from The_assassin --- Yes, it is per-tab, but you just could open the new site in new tab, or just click the button before open a new site in same tab. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406535] plasmashell crashing with freebsd, with kill Xorg and sddm again....
https://bugs.kde.org/show_bug.cgi?id=406535 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406043] KWin crashes when switching desktop while a window explodes
https://bugs.kde.org/show_bug.cgi?id=406043 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406533] when the transformation tool is selected you can't see the image/draw until you switch to another tool.
https://bugs.kde.org/show_bug.cgi?id=406533 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 407040] New: Feature Request - Size estimate during resizing
https://bugs.kde.org/show_bug.cgi?id=407040 Bug ID: 407040 Summary: Feature Request - Size estimate during resizing Product: gwenview Version: 18.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: justin.zo...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open image 2. Open resize from the menu 3. OBSERVED RESULT N/A EXPECTED RESULT Add an estimate about how much disk space the image will take up after resize. Many forums and web sites require images to below a certain size to upload and this feature would make this process much eaiser. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Solus 4.0 / Plasma 5.15.4 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383697] [Regression] Document print margins not persistent.
https://bugs.kde.org/show_bug.cgi?id=383697 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389803] Improve Places category show/hide behavior: show/hide when clicking on header
https://bugs.kde.org/show_bug.cgi?id=389803 --- Comment #5 from Nate Graham --- Yep, you're on the right track! Keep in mind that Dolphin does do some custom overlaying on top of that as well. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407039] New: strlen was not found whilst processing symbols from the object with soname: ld-linux-x86-64.so.2
https://bugs.kde.org/show_bug.cgi?id=407039 Bug ID: 407039 Summary: strlen was not found whilst processing symbols from the object with soname: ld-linux-x86-64.so.2 Product: valgrind Version: 3.15 SVN Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: ilya.fo...@mq.edu.au Target Milestone: --- I have an absolutely fresh installation of Ubuntu 19.04 and I compiled valgrind 3.15 from sources: ./autogen.sh ./configure --prefix=/opt/valgrind315/ --enable-only64bit [<= these options do not really matter] make sudo make install Each time I run it, I get the following: $ /opt/valgrind315/bin/valgrind -v ls -l ==16904== Memcheck, a memory error detector ==16904== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==16904== Using Valgrind-3.15.0-608cb11914-20190413 and LibVEX; rerun with -h for copyright info ==16904== Command: ls -l ==16904== --16904-- Valgrind options: --16904---v --16904-- Contents of /proc/version: --16904-- Linux version 5.0.0-13-generic (buildd@lcy01-amd64-020) (gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)) #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 --16904-- --16904-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand --16904-- Page sizes: currently 4096, max supported 4096 --16904-- Valgrind library directory: /opt/valgrind315/lib/valgrind --16904-- Reading syms from /usr/bin/ls --16904--object doesn't have a symbol table --16904-- Reading syms from /usr/lib/x86_64-linux-gnu/ld-2.29.so --16904-- Considering /usr/lib/x86_64-linux-gnu/ld-2.29.so .. --16904-- .. CRC mismatch (computed c34345a7 wanted 87a50cbd) --16904--object doesn't have a symbol table valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. I installed successfully debug symbols for ld: $ nm /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.29.so | grep '\bstr' 000206e0 t strchr 0001d120 t strcmp 00020da0 t strcspn 0001d0d0 t strdup 00020900 t strlen 0001e560 t strncmp 00020aa0 t strnlen 0001b6a0 t strsep I also tried to run with some extra options following, but I got the same result: --allow-mismatched-debuginfo=yes --read-inline-info=yes --extra-debuginfo-path=[different variants] SOFTWARE/OS VERSIONS Linux: Ubuntu 19.04 Compiler: gcc 8.3.0 ADDITIONAL INFORMATION I need to compile my own version of valgrind (the reason is that our software has a huge .bss section, so default repository version of valgrind can not handle it). Before I compiled and ran it with no problems at all (Ubuntu 16.04), and I'm using exactly the same settings now. Valgrind 3.13 drops endless number of Conditional jump or move depends on uninitialised value(s) in /usr/lib/x86_64-linux-gnu/libc-2.29.so -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365254] Usability: Removing Buttons from the window decoration is confusing
https://bugs.kde.org/show_bug.cgi?id=365254 Nate Graham changed: What|Removed |Added Version Fixed In||5.15.0 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||n...@kde.org --- Comment #9 from Nate Graham --- The icon has text that explains it, and now it uses an emblem icon so the meaning is a bit clearer. So I think the original issue is effectively resolved We could still remove the icon of course, but I don't think that's necessary from the perspective of calling this issue fixed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381556] arm64: Handle feature registers access on 4.11 Linux kernel or later
https://bugs.kde.org/show_bug.cgi?id=381556 Jeffrey Walton changed: What|Removed |Added CC||noloa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407034] Editing an image in the Image editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407034 --- Comment #1 from caulier.gil...@gmail.com --- *** Bug 407033 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407033] Editing an image in the Image Editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407033 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 407034 *** -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 407038] New: Muon crashed after install xserver-xorg-input-libinput-hwe-18.04 package on neon dev unstable
https://bugs.kde.org/show_bug.cgi?id=407038 Bug ID: 407038 Summary: Muon crashed after install xserver-xorg-input-libinput-hwe-18.04 package on neon dev unstable Product: muon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: bugsefor...@gmx.com CC: silh...@gmail.com Target Milestone: --- Summary says by itself. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 Application: Gerenciador de pacotes Muon (muon), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe4f0f248c0 (LWP 9897))] Thread 6 (Thread 0x7fe4bdb7f700 (LWP 12191)): #0 0x7fe4ecb0bbf9 in __GI___poll (fds=0x7fe4b8001f60, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe4bc38c481 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fe4bc37de40 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fe4bc37e4d0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fe4bc37e560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fe4bc38c3c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fe4bc12e318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7fe4ea0696db in start_thread (arg=0x7fe4bdb7f700) at pthread_create.c:463 #8 0x7fe4ecb1888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fe4c50d7700 (LWP 9904)): #0 0x7fe4ea06f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x555fc6061178) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x555fc6061128, cond=0x555fc6061150) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x555fc6061150, mutex=0x555fc6061128) at pthread_cond_wait.c:655 #3 0x7fe4c6476dcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fe4c6476af7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fe4ea0696db in start_thread (arg=0x7fe4c50d7700) at pthread_create.c:463 #6 0x7fe4ecb1888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fe4cd76d700 (LWP 9903)): #0 0x7fe4ecb0bbf9 in __GI___poll (fds=0x7fe4c8004a10, nfds=1, timeout=10245) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe4e74aa539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe4e74aa64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe4ed44e15b in QEventDispatcherGlib::processEvents (this=0x7fe4c8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fe4ed3ef64a in QEventLoop::exec (this=this@entry=0x7fe4cd76cce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fe4ed21741a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fe4ed218bc2 in QThreadPrivate::start (arg=0x555fc625c750) at thread/qthread_unix.cpp:361 #7 0x7fe4ea0696db in start_thread (arg=0x7fe4cd76d700) at pthread_create.c:463 #8 0x7fe4ecb1888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fe4d6f10700 (LWP 9900)): #0 0x7fe4e74f0064 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe4e74a9427 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe4e74aa3f5 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe4e74aa64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe4ed44e15b in QEventDispatcherGlib::processEvents (this=0x7fe4db20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7fe4ed3ef64a in QEventLoop::exec (this=this@entry=0x7fe4d6f0fcb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fe4ed21741a in QThread::exec (this=this@entry=0x7fe4eb9bfd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #7 0x7fe4eb748015 in QDBusConnectionManager::run (this=0x7fe4eb9bfd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7fe4ed218bc2 in QThreadPrivate::start (arg=0x7fe4eb9bfd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #9 0x7fe4ea0696db in start_thread (arg=0x7fe4d6f10700) at pthread_create.c:463 #10 0x7fe4ecb1888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fe4dffe0700 (LWP 9899)): #0 0x7fe4ecb0bbf9 in __GI___poll (fds=0x7fe4dffdfbf8, nfds=1, timeout=-1) at ../sysdeps/unix/s
[valgrind] [Bug 406824] Unsupported baseline
https://bugs.kde.org/show_bug.cgi?id=406824 Dapeng changed: What|Removed |Added Version|3.13.0 |3.15 SVN Platform|Fedora RPMs |Compiled Sources --- Comment #1 from Dapeng --- download https://sourceware.org/pub/valgrind/valgrind-3.15.0.tar.bz2 reference README，make and make install. it has same problem，does valgrind not support loongson ? or doesn't support mips64el ? [root@localhost valgrind-3.15.0]# valgrind ls ==2657== Memcheck, a memory error detector ==2657== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==2657== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==2657== Command: ls ==2657== VEX: Err : Unsupported baseline Found: Loongson-baseline Cannot continue. Good-bye vex storage: T total 0 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==2657==at 0x58061BC8: show_sched_status_wrk (m_libcassert.c:388) ==2657==by 0x58061DA0: report_and_quit (m_libcassert.c:459) ==2657==by 0x5806200C: panic (m_libcassert.c:535) ==2657==by 0x5806200C: vgPlain_core_panic_at (m_libcassert.c:540) ==2657==by 0x58062050: vgPlain_core_panic (m_libcassert.c:545) ==2657==by 0x5807F1E8: failure_exit (m_translate.c:751) ==2657==by 0x58191160: vfatal (main_util.c:603) ==2657==by 0x5818B3C0: invalid_hwcaps (main_main.c:1851) ==2657==by 0x5818B97C: check_hwcaps (main_main.c:2068) ==2657==by 0x5818C558: LibVEX_FrontEnd (main_main.c:530) ==2657==by 0x5818CF34: LibVEX_Translate (main_main.c:1185) ==2657==by 0x580822BC: vgPlain_translate (m_translate.c:1813) ==2657==by 0x580D2C50: handle_tt_miss (scheduler.c:1139) ==2657==by 0x580D2C50: vgPlain_scheduler (scheduler.c:1505) ==2657==by 0x5813AE38: thread_wrapper (syswrap-linux.c:103) ==2657==by 0x5813AE38: run_a_thread_NORETURN (syswrap-linux.c:156) sched status: running_tid=1 --2657-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --2657-- si_code=1; Faulting address: 0x148; sp: 0x1002eb7280 valgrind: the 'impossible' happened: Killed by fatal signal host stacktrace: ==2657==at 0x580D4BD8: vgPlain_is_in_syscall (syswrap-main.c:1642) ==2657==by 0x580616CC: print_thread_state (m_libcassert.c:326) ==2657==by 0x580619A4: show_sched_status_wrk (m_libcassert.c:422) ==2657==by 0x58061DA0: report_and_quit (m_libcassert.c:459) ==2657==by 0x5806200C: panic (m_libcassert.c:535) ==2657==by 0x5806200C: vgPlain_core_panic_at (m_libcassert.c:540) ==2657==by 0x58062050: vgPlain_core_panic (m_libcassert.c:545) ==2657==by 0x5807F1E8: failure_exit (m_translate.c:751) ==2657==by 0x58191160: vfatal (main_util.c:603) ==2657==by 0x5818B3C0: invalid_hwcaps (main_main.c:1851) ==2657==by 0x5818B97C: check_hwcaps (main_main.c:2068) ==2657==by 0x5818C558: LibVEX_FrontEnd (main_main.c:530) ==2657==by 0x5818CF34: LibVEX_Translate (main_main.c:1185) ==2657==by 0x580822BC: vgPlain_translate (m_translate.c:1813) ==2657==by 0x580D2C50: handle_tt_miss (scheduler.c:1139) ==2657==by 0x580D2C50: vgPlain_scheduler (scheduler.c:1505) ==2657==by 0x5813AE38: thread_wrapper (syswrap-linux.c:103) ==2657==by 0x5813AE38: run_a_thread_NORETURN (syswrap-linux.c:156) sched status: running_tid=1 Segment error -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396024] Allow per-site configuration of JavaScript
https://bugs.kde.org/show_bug.cgi?id=396024 --- Comment #4 from Christoph Feck --- It doesn't have per-site configuration, so no, it is not useful. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 407037] New: meinproc5 is not honoring Korean naming order (reversed surname/firstname)
https://bugs.kde.org/show_bug.cgi?id=407037 Bug ID: 407037 Summary: meinproc5 is not honoring Korean naming order (reversed surname/firstname) Product: frameworks-kdoctools Version: 5.56.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: k...@peremen.name CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY While I was testing generation of DocBook file and HTML files based on Korean translation for docmessages (not in SVN yet), I found that surname, firstname is not correctly ordered in Korean even if I specified lang="ko" attribute to the tag. Because Korean names in Hangul (FirstnameSurname display) and names in Latin alphabet (Surname Firstname display) can appear on the single document, I think the lang attribute of not only the document but also the individual credit should be honored. Note that order reversing is implemented in DocBook's DSSSL since version 1.59. STEPS TO REPRODUCE 1. Add translator information to ROLES_OF_TRANSLATORS such as: 박신조 Note that lang="ko" attribute. 2. Run scripts/update.xml from l10n-kf5 directory, check whether those attributes are preserved. 3. Run meinproc5 --check index.docbook for the generated docbook and check the generated HTML. OBSERVED RESULT Generated HTML document shows: : 신조 박 EXPECTED RESULT This should be: : 박신조 Note that there is no space between surname and firstname, and surname goes first. While the part is empty, but looks like it is mentioned in TODO. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.56 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 407036] New: Akregator close tab crash
https://bugs.kde.org/show_bug.cgi?id=407036 Bug ID: 407036 Summary: Akregator close tab crash Product: akregator Version: 5.11.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jdhayes.li...@gmail.com Target Milestone: --- Application: akregator (5.11.0) Qt Version: 5.12.0 Frameworks Version: 5.57.0 Operating System: Linux 4.15.0-48-generic x86_64 Distribution: KDE neon Plasma LTS Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I was closing a tab and it crashed, I restarted and tried again and it crashed again. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Illegal instruction Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff75b521bc0 (LWP 7069))] Thread 34 (Thread 0x7ff5fcbf1700 (LWP 7162)): #0 0x7ff757290187 in __GI___libc_write (fd=2, buf=0x7ff5fcbedc40, nbytes=39) at ../sysdeps/unix/sysv/linux/write.c:27 #1 0x7ff75720b1bd in _IO_new_file_write (f=0x7ff75756c680 <_IO_2_1_stderr_>, data=0x7ff5fcbedc40, n=39) at fileops.c:1203 #2 0x7ff75720bb2f in new_do_write (to_do=, data=0x7ff5fcbedc40 "[warn] epoll_wait: Bad file descriptor\n", fp=0x7ff75756c680 <_IO_2_1_stderr_>) at fileops.c:457 #3 0x7ff75720bb2f in _IO_new_file_xsputn (f=0x7ff75756c680 <_IO_2_1_stderr_>, data=, n=39) at fileops.c:1277 #4 0x7ff7571de707 in buffered_vfprintf (s=s@entry=0x7ff75756c680 <_IO_2_1_stderr_>, format=format@entry=0x7ff742eb76a8 "[%s] %s\n", args=args@entry=0x7ff5fcbf0200) at vfprintf.c:2350 #5 0x7ff7571db726 in _IO_vfprintf_internal (s=s@entry=0x7ff75756c680 <_IO_2_1_stderr_>, format=0x7ff742eb76a8 "[%s] %s\n", ap=ap@entry=0x7ff5fcbf0200) at vfprintf.c:1301 #6 0x7ff7572b24c6 in ___fprintf_chk (fp=0x7ff75756c680 <_IO_2_1_stderr_>, flag=1, format=) at fprintf_chk.c:35 #7 0x7ff742e9f9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #8 0x7ff742e9fb44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #9 0x7ff742ea146c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #10 0x7ff742e97114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #11 0x7ff750ca07dd in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7ff750c3749b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7ff750c69d21 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7ff750c9ccd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #15 0x7ff74a91f6db in start_thread (arg=0x7ff5fcbf1700) at pthread_create.c:463 #16 0x7ff7572a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7ff5fd3f2700 (LWP 7161)): #0 0x7ff74a9259f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7ff5fd3f1908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff74a9259f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7ff5fd3f18b8, cond=0x7ff5fd3f18e0) at pthread_cond_wait.c:502 #2 0x7ff74a9259f3 in __pthread_cond_wait (cond=0x7ff5fd3f18e0, mutex=0x7ff5fd3f18b8) at pthread_cond_wait.c:655 #3 0x7ff750c9a0a9 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7ff750c9aae8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7ff750c9ab7f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7ff750c58868 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7ff750c5b387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7ff750c5b9b4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7ff750c9ccd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7ff74a91f6db in start_thread (arg=0x7ff5fd3f2700) at pthread_create.c:463 #11 0x7ff7572a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7ff5fe4f4700 (LWP 7157)): #0 0x7ff74a925ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff5fe4f3710, expected=0, futex_word=0x7ff5fe4f38f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7ff74a925ed9 in __pthread_cond_wait_common (abstime=0x7ff5fe4f37b0, mutex=0x7ff5fe4f38a8, cond=0x7ff5fe4f38d0) at pthread_cond_wait.c:533 #2 0x7ff74a925ed9 in __pthread_cond_timedwait (cond=0x7ff5fe4f38d0, mutex=0x7ff5fe4f38a8, abstime=0x7ff5fe4f37b0) at pthread_cond_wait.c:667 #3 0x7ff750c9a177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7ff750c9aada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7ff750c9abc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7ff750c58851 in () at /usr/lib/x
[wacomtablet] [Bug 407015] wacomtablet FTBFS with gcc9+
https://bugs.kde.org/show_bug.cgi?id=407015 --- Comment #4 from Rex Dieter --- Confirmed patch works as advertised, thanks. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 406997] Headerbar button decorations inconsistent with breeze QT toolbars (and look inferiour, imo)
https://bugs.kde.org/show_bug.cgi?id=406997 Aleix Pol changed: What|Removed |Added Assignee|manutortosa@chakra-project. |scionicspec...@gmail.com |org | Product|kde-gtk-config |Breeze Component|general |gtk theme -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 407032] Sharing via KDE Connect crashes application on Wayland
https://bugs.kde.org/show_bug.cgi?id=407032 --- Comment #4 from Aleix Pol --- This crash is somewhere between QtQuick's scene graph and and your graphics drivers. There's no way we can do anything about it from Purpose. :/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407034] New: Editing an image in the Image editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407034 Bug ID: 407034 Summary: Editing an image in the Image editor adds a XMP video date field. Product: digikam Version: 6.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY Apparently, editing an image using Digikam's Image editor (and saving it as a new version, at least), adds the XMP Video Date field, copying the date from the XMP Creation date. But it depends on the existing metadata, as it not happens in all cases. Check this screen capture: https://i.imgur.com/A2Zu7Wv.gifv I am pretty sure there are other cases where digikam adds the XMP Video Date, but this is the only one I've been able to identify. STEPS TO REPRODUCE 1. Check image in the metadata editor to make sure that the XMP Video date is empty. 2. Use the image editor, and save the image as a new version. 3. Check the metadata of that new image, and observe how the XMP Video date is no longer empty. OBSERVED RESULT Digikam has added a date in the XMP Video Date field. EXPECTED RESULT Metadata should be identical to that of the source picture. SOFTWARE/OS VERSIONS Ubuntu 18.04 with gnome and digikam-6.2.0-git-20190423T140539-qtwebkit-x86-64.appimage -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407035] New: Mass rename sometimes preserves extensions for directories
https://bugs.kde.org/show_bug.cgi?id=407035 Bug ID: 407035 Summary: Mass rename sometimes preserves extensions for directories Product: dolphin Version: 18.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: joe.di...@member.fsf.org CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY When mass renaming with dolphin, if a folder's name ends with a stop then one or two characters, which are both the same, then these characters are preserved in the final folder's name. STEPS TO REPRODUCE 1. Create two folders, test.aa and test2.ab, in an empty folder 2. Select both and right-click -> rename 3. Enter # into the rename pattern box, and 1 as the initial number. OBSERVED RESULT Two folders are created: 1.aa and 2 EXPECTED RESULT The folders should be named 1 and 2 SOFTWARE/OS VERSIONS Fedora 30 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407034] Editing an image in the Image editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407034 IWBR changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407033] New: Editing an image in the Image Editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407033 Bug ID: 407033 Summary: Editing an image in the Image Editor adds a XMP video date field. Product: digikam Version: 6.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY Apparently, editing an image using Digikam's Image editor (and saving it as a new version, at least), adds the XMP Video Date field, copying the date from the XMP Creation date. But it depends on the existing metadata, as it not happens in all cases. Check this screen capture: https://i.imgur.com/A2Zu7Wv.gifv I am pretty sure there are other cases where digikam adds the XMP Video Date, but this is the only one I've been able to identify. STEPS TO REPRODUCE 1. Check image in the metadata editor to make sure that the XMP Video date is empty. 2. Use the image editor, and save the image as a new version. 3. Check the metadata of that new image, and observe how the XMP Video date is no longer empty. OBSERVED RESULT Digikam has added a date in the XMP Video Date field. EXPECTED RESULT Metadata should be identical to that of the source picture. SOFTWARE/OS VERSIONS Ubuntu 18.04 with gnome and digikam-6.2.0-git-20190423T140539-qtwebkit-x86-64.appimage -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 405210] baloo_file_extractor crashes somewhere in KFileMetadata on a specific JPEG file (attached)
https://bugs.kde.org/show_bug.cgi?id=405210 Nate Graham changed: What|Removed |Added Summary|baloofile_extractor crash |baloo_file_extractor ||crashes somewhere in ||KFileMetadata on a specific ||JPEG file (attached) Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #10 from Nate Graham --- Thank you very much for attaching the problematic file! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405930] Shortcut for switching profiles opens a new tab unlike the mouse option
https://bugs.kde.org/show_bug.cgi?id=405930 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #3 from Nate Graham --- Please file a new bug for that request. Thanks! FWIW you can quickly create a new tab by clicking and holding the new tab button in the tab bar and selecting your preferred profile. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388481] No tags appear in tag column in detailed list view
https://bugs.kde.org/show_bug.cgi?id=388481 --- Comment #8 from Clinton --- Yes I still have the issues in 19.04 On Sun, Apr 28, 2019 at 12:52 PM Julian Schraner wrote: > > https://bugs.kde.org/show_bug.cgi?id=388481 > > Julian Schraner changed: > >What|Removed |Added > > Version|17.12.0 |19.04.0 >Platform|Other |Neon Packages > > --- Comment #7 from Julian Schraner --- > Huh, now the issue is also present for me. Maybe I did something wrong when > triaging this for the first time. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 405777] Assigning Tag to a file on the desktop creates a new Tag
https://bugs.kde.org/show_bug.cgi?id=405777 Nate Graham changed: What|Removed |Added Version Fixed In||19.04.1 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406918] Freeze on certain effects (NVidia)
https://bugs.kde.org/show_bug.cgi?id=406918 --- Comment #10 from David Edmundson --- > I can't see that deadlock when breaking in gdb It'll be blocking in the render thread. Thread 0 will be polling on that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407013] Incorrectly parses GPS
https://bugs.kde.org/show_bug.cgi?id=407013 --- Comment #3 from aik --- Rewriting -GPSLatitudeRef=South by exiftool fixed the problem. Weird. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 407032] Sharing via KDE Connect crashes application on Wayland
https://bugs.kde.org/show_bug.cgi?id=407032 --- Comment #3 from Nicolas Fella --- Created attachment 119704 --> https://bugs.kde.org/attachment.cgi?id=119704&action=edit Dolphin output -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 407032] New: Sharing via KDE Connect crashes application on Wayland
https://bugs.kde.org/show_bug.cgi?id=407032 Bug ID: 407032 Summary: Sharing via KDE Connect crashes application on Wayland Product: frameworks-purpose Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: nicolas.fe...@gmx.de Target Milestone: --- STEPS TO REPRODUCE 1. Right-click file in Dolphin 2. Share-> KDE Connect 3. Select device and send OBSERVED RESULT Dolphin crashes SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.4 KDE Frameworks Version: master (28.04.2019) Qt Version: 5.12.3 ADDITIONAL INFORMATION Happens with Spectacle and Falkon as well. -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 407031] korgac immediate crash segfault Disco Dingo
https://bugs.kde.org/show_bug.cgi?id=407031 David Oldford changed: What|Removed |Added Attachment #119699|0 |1 is obsolete|| --- Comment #1 from David Oldford --- Created attachment 119701 --> https://bugs.kde.org/attachment.cgi?id=119701&action=edit better kcrash info When I purged and reinstalled korganizer I forgot to reinstall the korganizer debug info. This kcrash info is with the debug info. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 407032] Sharing via KDE Connect crashes application on Wayland
https://bugs.kde.org/show_bug.cgi?id=407032 --- Comment #2 from Nicolas Fella --- Created attachment 119703 --> https://bugs.kde.org/attachment.cgi?id=119703&action=edit Dolphin BT -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 407032] Sharing via KDE Connect crashes application on Wayland
https://bugs.kde.org/show_bug.cgi?id=407032 --- Comment #1 from Nicolas Fella --- Created attachment 119702 --> https://bugs.kde.org/attachment.cgi?id=119702&action=edit Spectacle BT -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379004] test_duchain-clang fails
https://bugs.kde.org/show_bug.cgi?id=379004 --- Comment #10 from KiloAlphaIndia --- I started the test in an endless loop. It is behaving quite strange. There are two test steps that mostly succeed but sometimes fail. I also got a crash, but the Backtrace is different: #0 0x7f9186b26120 in raise () from /lib64/libc.so.6 #1 0x7f9186b27701 in abort () from /lib64/libc.so.6 #2 0x7f9187825881 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1690 #3 QMessageLogger::fatal (this=this@entry=0x7f918fc8ba80 , msg=msg@entry=0x7f918fa7b4f0 "Received signal %d\n Function time: %dms Total time: %dms") at global/qlogging.cpp:796 #4 0x7f918fa60353 in QTest::FatalSignalHandler::signal (signum=2) at qtestcase.cpp:1416 #5 #6 0x7f9186c4aa87 in __memset_avx2_unaligned_erms () from /lib64/libc.so.6 #7 0x7f918db43e40 in KDevelop::ItemRepository::ItemRepository (this=0x7f910982f010, repositoryName=..., registry=0x23c9c80, repositoryVersion=1, manager=0x0) at ../kdevplatform/serialization/itemrepository.h:1127 #8 0x7f918db43579 in KDevelop::UsesPrivate::UsesPrivate (this=0x7f910982f010) at ../kdevplatform/language/duchain/uses.cpp:119 #9 0x7f918db42890 in KDevelop::Uses::Uses (this=0x7f918e34f328 ) at ../kdevplatform/language/duchain/uses.cpp:126 #10 0x7f918da7759b in KDevelop::DUChainPrivate::DUChainPrivate (this=0x7f918e34f2e0 ) at ../kdevplatform/language/duchain/duchain.cpp:336 #11 0x7f918da72170 in KDevelop::(anonymous namespace)::Q_QGS_sdDUChainPrivate::Holder::Holder (this=0x7f918e34f2e0 ) at ../kdevplatform/language/duchain/duchain.cpp:1186 #12 0x7f918da721e0 in KDevelop::(anonymous namespace)::Q_QGS_sdDUChainPrivate::innerFunction () at ../kdevplatform/language/duchain/duchain.cpp:1186 #13 0x7f918da7616b in QGlobalStatic::operator-> ( this=0x7f918e74eb68 ) at /usr/include/qt5/QtCore/qglobalstatic.h:139 #14 0x7f918da724e4 in KDevelop::DUChain::self () at ../kdevplatform/language/duchain/duchain.cpp:1211 #15 0x7f918da27910 in KDevelop::StaticAssistantsManager::StaticAssistantsManager (this=0x245ddf0, parent=0x259bd60) at ../kdevplatform/language/assistant/staticassistantsmanager.cpp:72 #16 0x7f918f36ffb1 in KDevelop::LanguageController::initialize (this=0x259bd60) at ../kdevplatform/shell/languagecontroller.cpp:146 #17 0x7f918f32740b in KDevelop::CorePrivate::initialize (this=0x21d1e80, mode=KDevelop::Core::Default, session=...) at ../kdevplatform/shell/core.cpp:242 #18 0x7f918fca6880 in KDevelop::TestCore::initializeNonStatic (this=0x21daf60, mode=KDevelop::Core::Default, _session=...) at ../kdevplatform/tests/testcore.cpp:81 #19 0x7f918fca6713 in KDevelop::TestCore::initialize (mode=KDevelop::Core::Default, session=...) at ../kdevplatform/tests/testcore.cpp:55 #20 0x0040de42 in TestDUChain::initTestCase (this=0x7ffd5b8aa840) at ../plugins/clang/tests/test_duchain.cpp:75 #21 0x004400f4 in TestDUChain::qt_static_metacall (_o=0x7ffd5b8aa840, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffd5b8aa520) at plugins/clang/tests/test_duchain-clang_autogen/EWIEGA46WW/moc_test_duchain.cpp:292 #22 0x7f9187a17aa6 in QMetaMethod::invoke (this=this@entry=0x7ffd5b8aa780, object=object@entry=0x7ffd5b8aa840, connectionType=connectionType@entry=Qt::DirectConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp: #23 0x7f918fa67f84 in QMetaMethod::invoke (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., connectionType=Qt::DirectConnection, object=0x7ffd5b8aa840, this=0x7ffd5b8aa780) at ../../include/QtCore/../../src/corelib/kernel/qmetaobject.h:123 #24 QTest::TestMethods::invokeTests (this=this@entry=0x7ffd5b8aa780, testObject=testObject@entry=0x7ffd5b8aa840) at qtestcase.cpp:1363 #25 0x7f918fa685c3 in QTest::qExec (testObject=0x7ffd5b8aa840, argc=, argv=0x7ffd5b8aa968) at qtestcase.cpp:1797 #26 0x0040dc12 in main (argc=1, argv=0x7ffd5b8aa968) at ../plugins/clang/tests/test_duchain.cpp:64 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 Knut Hildebrandt changed: What|Removed |Added CC||knut.hildebra...@gmx.de --- Comment #6 from Knut Hildebrandt --- Created attachment 119700 --> https://bugs.kde.org/attachment.cgi?id=119700&action=edit Dolphins consuming huge amounts of memory and CPU time. Any progress on this. Recently my system is almost stalling during to dolphins memory hunger. Have a look at the attached screenshot. No clue what they are doing what they need all this memory for. I would expect that they just display the file tree. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 --- Comment #19 from Thaodan --- Is there a way to always send auth headers? -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 407031] New: korgac immediate crash segfault Disco Dingo
https://bugs.kde.org/show_bug.cgi?id=407031 Bug ID: 407031 Summary: korgac immediate crash segfault Disco Dingo Product: korgac Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: david_oldf...@hotmail.com Target Milestone: --- Created attachment 119699 --> https://bugs.kde.org/attachment.cgi?id=119699&action=edit kcrash info SUMMARY STEPS TO REPRODUCE 1. login to plasma or start korganizer or run korgac from commandline OBSERVED RESULT korgac crashes with a segmentation fault and drkonqi starts EXPECTED RESULT korgac would run in the background and provide calendar notifications SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.0.0-13-generic / 5.15.4 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION This system is up to date with kubuntu packages for disco dingo and was upgraded from cosmic cuttlefish. The issue has been present since the upgrade. I've tried uninstalling and reinstalling korganizer with no effect, including using apt purge to remove it. console output: korgac KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = korgac path = /usr/bin pid = 24842 KCrash: Arguments: /usr/bin/korgac KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Stopped korgac -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 406997] Headerbar button decorations inconsistent with breeze QT toolbars (and look inferiour, imo)
https://bugs.kde.org/show_bug.cgi?id=406997 maxmustermann1...@web.de changed: What|Removed |Added CC||maxmustermann1...@web.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 Lukasz changed: What|Removed |Added CC|dolo...@outlook.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407030] New: Mass renaming fails to properly handle items which will themselves be renamed
https://bugs.kde.org/show_bug.cgi?id=407030 Bug ID: 407030 Summary: Mass renaming fails to properly handle items which will themselves be renamed Product: dolphin Version: 18.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: joe.di...@member.fsf.org CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY When mass renaming with dolphin, if an file (or folder) is to be renamed to the name of an existing file, if that file is also being renamed, dolphin will still ask to overwrite that file (potentially leaving multiple copies of the same file). STEPS TO REPRODUCE 1. Create two folders, 0 and 1, in an empty folder 2. Select both and right-click -> rename 3. Enter # into the rename pattern box, and 1 as the initial number. OBSERVED RESULT Dolphin will warn that the folder 1 already exists, and ask you if you want to write 0 into 1 or cancel. If you write into, then the directories are merged, then the directory 1 is renamed to 2, leaving you with one directory, 2. EXPECTED RESULT 0 should be renamed to 1, and 1 renamed to 2, but without at any time writing both directories to the same path. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407022] digikam 6.1.0-196.1-x86_64 crash at start
https://bugs.kde.org/show_bug.cgi?id=407022 Maik Qualmann changed: What|Removed |Added CC||wba...@tmo.at --- Comment #3 from Maik Qualmann --- The "packagers" are probably not looking in here. I'll add your namesake. Maik -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 386004] no connection with mariadb (Debian Stretch)
https://bugs.kde.org/show_bug.cgi?id=386004 --- Comment #2 from Francesco Talamona --- In your case "@10.0.0.159"... -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 386004] no connection with mariadb (Debian Stretch)
https://bugs.kde.org/show_bug.cgi?id=386004 Francesco Talamona changed: What|Removed |Added CC||cancellettopu...@gmail.com --- Comment #1 from Francesco Talamona --- I discovered that with MariaDb the suggested command is not sufficient. Instead of: GRANT ALL PRIVILEGES ON amarokdb.* TO amarokuser IDENTIFIED BY 'secret'; it should be: GRANT ALL PRIVILEGES ON amarokdb.* TO amarokuser@localhost IDENTIFIED BY 'secret'; -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407022] digikam 6.1.0-196.1-x86_64 crash at start
https://bugs.kde.org/show_bug.cgi?id=407022 --- Comment #2 from Daniel Bauer --- (In reply to Maik Qualmann from comment #1) > This will most certainly be a package problem. Yes, it looks like that. But it's the first time it happens and I hope to reach the "packager" with this report :-) > Please start digiKam from the console and > post the messages. The only message I get when staring form console is: Speicherzugriffsfehler (Speicherabzug geschrieben) nothing more... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389803] Improve Places category show/hide behavior: show/hide when clicking on header
https://bugs.kde.org/show_bug.cgi?id=389803 Aasif Khan changed: What|Removed |Added CC||aasifk...@gmail.com --- Comment #4 from Aasif Khan --- Hi. I am trying to solve this issue. But I am new to KDE development overall. And looking at the code I think that the code of KFilePlacesModel must be changed because dolphin is using KFilePlacesModel directly for its places panel. Am I headed in the right direction? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406833] add a feature to unlock desktop using fingerprint sensor of phone
https://bugs.kde.org/show_bug.cgi?id=406833 NiO changed: What|Removed |Added CC||arco...@gmail.com --- Comment #1 from NiO --- This is actually a great idea. I'd like to expand on that to not just unlocking the desktop, but authentication in general. For example, it could be used for unlocking KDE vaults or issuing commands as root. There's lots of potential for your idea beyond desktop unlocking. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 406946] Akonadi crashes when sending a large attachment
https://bugs.kde.org/show_bug.cgi?id=406946 --- Comment #2 from Aaron Williams --- Unfortunately, I have been unable to get a backtrace. It is very repeatable. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407029] New: Improve visual stability of ledger - maintain focus on selected transaction
https://bugs.kde.org/show_bug.cgi?id=407029 Bug ID: 407029 Summary: Improve visual stability of ledger - maintain focus on selected transaction Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ostrof...@users.sourceforge.net Target Milestone: --- This is actually similar to bug 296614, which referred to the ledger scrolling to the bottom after merging two transactions. That was fixed by leaving the focus on the next transaction if the action deleted the transaction under focus. However there are other cases where the ledger scrolls to the newest transaction after some action, instead of remaining focused on the previously selected transaction. This always happens at the end of reconciliation, even though I would prefer that focus remain on the last transaction prior to or on the reconciliation date. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406971] Face frames are misaligned on Digikam when face framing was done on Picasa.
https://bugs.kde.org/show_bug.cgi?id=406971 --- Comment #9 from Maik Qualmann --- The problem is clear. Picasa and the the standard is that the face regions are saved to a non-aligned image. The implementation in digiKam has been storing the face regions for the aligned image for years. We will change it, but we need to convert the database and the stored face regions in the users' images. That will be a bigger deal. So you can not currently swap face region images between digiKam and Picasa. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 349625] Entering transaction into ledger creates error message "cannot enter transaction with post date prior to opening date"
https://bugs.kde.org/show_bug.cgi?id=349625 --- Comment #1 from Jack --- The bug you refer to happened due to the user expecting MM-DD dates, but the system was set to DD-MM (or perhaps the other way around) and was closed as "NOT A BUG" Also, since 4.7.2, there have been changes made to avoid this type of error. Unless someone claims this is still a problem, I'm going to close it as fixed, or perhaps UNSUPPORTED. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406154] kmail closes too early
https://bugs.kde.org/show_bug.cgi?id=406154 kwanza.p...@virginmedia.com changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from kwanza.p...@virginmedia.com --- I updated QT to 5.12.3 and KDE apps to 19.04.0 which seems to have fixed the problem. I am not sure which of the two applications was the original culprit. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 407015] wacomtablet FTBFS with gcc9+
https://bugs.kde.org/show_bug.cgi?id=407015 --- Comment #3 from Rex Dieter --- Patch is fine for me, I can test later today. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379004] test_duchain-clang fails
https://bugs.kde.org/show_bug.cgi?id=379004 --- Comment #9 from RJVB --- (In reply to RJVB from comment #8) > I can no longer get the crash myself either on Linux Belay that: it just no longer crashes every time. Try it often enough and I still get the same crash. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407028] New: KDE Connect app fails to send files - Write error, SSL exception in logcat
https://bugs.kde.org/show_bug.cgi?id=407028
Bug ID: 407028
Summary: KDE Connect app fails to send files - Write error, SSL
exception in logcat
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: android-application
Assignee: albertv...@gmail.com
Reporter: arco...@gmail.com
Target Milestone: ---
SUMMARY
Every time I attempt to send a file to my desktop from my phone, I get an error
notification on my phone saying "Failed to send file to me@my-machine".
Everything else in both the desktop and mobile app works fine. I checked
logcat and there is an SSL exception being thrown after attempting to send the
selected files, see below. This is a new problem, read additional info at the
bottom.
Desktop:
* Solus 4
* KDE Connect 1.3.4
Phone:
* OnePlus 6T / stock, unrooted, Android Pie
* KDE Connect 1.12.6
STEPS TO REPRODUCE
1. Pair phone and desktop
2. Send a file
OBSERVED RESULT
Screenshot: https://i.imgur.com/Lo0kh52.jpg
Via logcat:
04-28 14:41:18.357 29693 9584 I KDE/LanLink: Using port 1747
04-28 14:41:18.357 936 3736 D ActivityTrigger: activityResumeTrigger: The
activity in ApplicationInfo{62573a4 org.kde.kdeconnect_tp} is now in focus and
seems to be in full-screen mode
04-28 14:41:18.357 936 3736 E ActivityTrigger: activityResumeTrigger: not
whiteListedorg.kde.kdeconnect_tp/org.kde.kdeconnect.UserInterface.MainActivity/11260
04-28 14:41:18.368 29693 29693 D OnePlusJankManager: Chor uploadMDM
JANK_TYPE_ONCE mViewTitle =
org.kde.kdeconnect_tp/org.kde.kdeconnect.Plugins.SharePlugin.SendFileActivity---
jank level = 1
04-28 14:41:18.369 936 1179 D RestartProcessManager: Update Total Launch
Times :org.kde.kdeconnect_tp
04-28 14:41:18.369 936 1179 D RestartProcessManager: updateSelf :
org.kde.kdeconnect_tp, size : 3
04-28 14:41:18.369 936 1179 D RestartProcessManager: Increase Total Launch
Time : org.kde.kdeconnect_tp, times : 28, index : 2
04-28 14:41:18.369 936 1179 D RestartProcessManager: Last Running Package :
org.kde.kdeconnect_tp , start time 1556480478369
04-28 14:41:18.391 29693 10801 D DecorView: onWindowFocusChangedFromViewRoot
hasFocus: true, DecorView@62bcb36[MainActivity]
04-28 14:41:18.400 29693 7122 E libc: Access denied finding property
"vendor.debug.egl.changepixelformat"
04-28 14:41:18.403 3578 3578 D PhoneStatusBarView: getCompatMode: mode:0
ops:3
04-28 14:41:18.403 3578 3578 I PhoneStatusBarView: isFullAndNotchEnabled()
isFullMode=false pkg=org.kde.kdeconnect_tp isCameraNotchIgnoreSetting=false,
uid=10141
04-28 14:41:18.415 29693 7129 I KDE/LanLinkProvider: Identity package received
from a TCP connection from adam@adam-solus
04-28 14:41:18.415 29693 7129 I KDE/LanLinkProvider: Starting SSL handshake
with adam@adam-solus trusted:true
04-28 14:41:18.418 29693 9584 I KDE/LanLink: Beginning to send payload
04-28 14:41:18.420 29693 7122 E libc: Access denied finding property
"vendor.debug.egl.swapinterval"
04-28 14:41:18.426 29693 9584 W System.err: javax.net.ssl.SSLException: Write
error: ssl=0x740402a108: I/O error during system call, Broken pipe
04-28 14:41:18.426 29693 9584 W System.err:at
com.android.org.conscrypt.NativeCrypto.SSL_write(Native Method)
04-28 14:41:18.426 29693 9584 W System.err:at
com.android.org.conscrypt.NativeSsl.write(NativeSsl.java:414)
04-28 14:41:18.426 29693 9584 W System.err:at
com.android.org.conscrypt.ConscryptFileDescriptorSocket$SSLOutputStream.write(ConscryptFileDescriptorSocket.java:623)
04-28 14:41:18.426 29693 9584 W System.err:at
org.kde.kdeconnect.Backends.LanBackend.LanLink.sendPacketInternal(LanLink.java:207)
04-28 14:41:18.426 29693 9584 W System.err:at
org.kde.kdeconnect.Backends.LanBackend.LanLink.sendPacket(LanLink.java:245)
04-28 14:41:18.426 29693 9584 W System.err:at
org.kde.kdeconnect.Device.sendPacketBlocking(Device.java:676)
04-28 14:41:18.426 29693 9584 W System.err:at
org.kde.kdeconnect.Plugins.SharePlugin.SharePlugin.lambda$queuedSendUriList$1(SharePlugin.java:233)
04-28 14:41:18.426 29693 9584 W System.err:at
org.kde.kdeconnect.Plugins.SharePlugin.-$$Lambda$SharePlugin$nI6DGtB96KsGUO-LKyR05GO3hF4.run(Unknown
Source:6)
04-28 14:41:18.426 29693 9584 W System.err:at
java.lang.Thread.run(Thread.java:764)
04-28 14:41:18.426 29693 9584 E KDE/sendPacket: No device link (of 1
available) could send the package. Packet kdeconnect.share.request to
adam@adam-solus lost!
04-28 14:41:18.426 29693 9584 E SharePlugin: Error sending files
04-28 14:41:18.436 3578 3578 D LightBarController:
onNavigationVisibilityChanged mNavigationLight = false
04-28 14:41:18.446 29693 7122 E libc: Access denied finding property
"vendor.debug.egl.swapinterval"
04-28 14:41:18.455 29693 9303 I LanLink : Socket closed: 155802812. Reason:
End of stream
04-28
[elisa] [Bug 393486] Elisa not picking covers for songs
https://bugs.kde.org/show_bug.cgi?id=393486 --- Comment #12 from sk.griffi...@gmail.com --- > > Support for embedded covers has been added in KFileMetaData but not yet in > Elisa. It is not expected to work yet. Any progress made as to display of embedded covers? I still not getting them on elisa -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 407026] Kmail crashes whenever creating a new mail
https://bugs.kde.org/show_bug.cgi?id=407026 --- Comment #2 from Andreas --- I should have mentioned that, in order to exclude inconsistent settings as cause of the crashes, I deleted all kmail/kmail2 relevant settings I have been able to identify in my home directory, except for the akonadi account settings. This does not change the observed result in any way. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 407027] New: Tellico crashes when adding multiple ebooks to the collection
https://bugs.kde.org/show_bug.cgi?id=407027 Bug ID: 407027 Summary: Tellico crashes when adding multiple ebooks to the collection Product: tellico Version: 3.1.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: phob0s...@gmail.com Target Milestone: --- Application: tellico (3.1.2) Qt Version: 5.11.3 Frameworks Version: 5.55.0 Operating System: Linux 5.0.9-200.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: - What I was doing when the application crashed: selected several (~15) pdf files drag'n'dropped them onto Tellico window selected to merge with the existing collection caught a crash -- Backtrace: Application: Tellico (tellico), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdab4807600 (LWP 21092))] Thread 5 (Thread 0x7fda9db92700 (LWP 21130)): #0 0x7fdab8dd4f54 in read () at /lib64/libc.so.6 #1 0x7fdab4e25355 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7fdab59c5826 in pa_mainloop_prepare () at /lib64/libpulse.so.0 #3 0x7fdab59c6294 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #4 0x7fdab59c6350 in pa_mainloop_run () at /lib64/libpulse.so.0 #5 0x7fdab59d45bd in thread () at /lib64/libpulse.so.0 #6 0x7fdab4e5506c in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #7 0x7fdab84ad58e in start_thread () at /lib64/libpthread.so.0 #8 0x7fdab8de4683 in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fda9f55e700 (LWP 21095)): #0 0x7fdab84b372c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fda9f7b88bb in () at /usr/lib64/dri/i965_dri.so #2 0x7fda9f7b85fb in () at /usr/lib64/dri/i965_dri.so #3 0x7fdab84ad58e in start_thread () at /lib64/libpthread.so.0 #4 0x7fdab8de4683 in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fdaa5f69700 (LWP 21094)): #0 0x7fdab8dd93f1 in poll () at /lib64/libc.so.6 #1 0x7fdab5a903a6 in () at /lib64/libglib-2.0.so.0 #2 0x7fdab5a904d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fdab94865ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fdab9434e0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fdab929ce86 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fdaba9def89 in () at /lib64/libQt5DBus.so.5 #7 0x7fdab92a62fb in () at /lib64/libQt5Core.so.5 #8 0x7fdab84ad58e in start_thread () at /lib64/libpthread.so.0 #9 0x7fdab8de4683 in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fdaa7604700 (LWP 21093)): #0 0x7fdab8dd93f1 in poll () at /lib64/libc.so.6 #1 0x7fdab806039f in () at /lib64/libxcb.so.1 #2 0x7fdab806201a in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fdaa76e4bf9 in () at /lib64/libQt5XcbQpa.so.5 #4 0x7fdab92a62fb in () at /lib64/libQt5Core.so.5 #5 0x7fdab84ad58e in start_thread () at /lib64/libpthread.so.0 #6 0x7fdab8de4683 in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fdab4807600 (LWP 21092)): [KCrash Handler] #6 0x7fdab84afd54 in pthread_mutex_lock () at /lib64/libpthread.so.0 #7 0x7fdabb8666f0 in XMP_AutoMutex::XMP_AutoMutex(pthread_mutex_t*) () at /lib64/libexempi.so.3 #8 0x7fdabb864bd1 in XMP_HomeGrownLock::AcquireForWrite() () at /lib64/libexempi.so.3 #9 0x7fdabb864cf9 in XMP_ReadWriteLock::Acquire(bool) () at /lib64/libexempi.so.3 #10 0x7fdabb865ba9 in XMP_NamespaceTable::Define(char const*, char const*, char const**, unsigned int*) () at /lib64/libexempi.so.3 #11 0x7fdab86da5b4 in () at /lib64/libexpat.so.1 #12 0x7fdab86dd555 in () at /lib64/libexpat.so.1 #13 0x7fdab86e0911 in () at /lib64/libexpat.so.1 #14 0x7fdab86e1780 in () at /lib64/libexpat.so.1 #15 0x7fdab86df1db in () at /lib64/libexpat.so.1 #16 0x7fdab86e0129 in () at /lib64/libexpat.so.1 #17 0x7fdab86e3e9a in XML_ParseBuffer () at /lib64/libexpat.so.1 #18 0x7fdabb86b221 in ExpatAdapter::ParseBuffer(void const*, unsigned long, bool) () at /lib64/libexempi.so.3 #19 0x7fdabb89b0e9 in () at /lib64/libexempi.so.3 #20 0x7fdabb89b89e in XMPMeta::ProcessXMLBuffer(char const*, unsigned int, bool) () at /lib64/libexempi.so.3 #21 0x7fdabb8a097c in XMPMeta::ParseFromBuffer(char const*, unsigned int, unsigned int) () at /lib64/libexempi.so.3 #22 0x7fdabb88ee09 in WXMPMeta_ParseFromBuffer_1 () at /lib64/libexempi.so.3 #23 0x7fdabb8590c0 in TXMPMeta, std::allocator > >::ParseFromBuffer(char const*, unsigned int, unsigned int) () at /lib64/libexempi.so.3 #24 0x7fdabb8da5cb in Scanner_MetaHandler::CacheFileData() () at /lib64
[lattedock] [Bug 406964] Latte dock constantly resizing when nearly out of space
https://bugs.kde.org/show_bug.cgi?id=406964 --- Comment #8 from Michail Vourlakos --- (In reply to sdfjsfjaei-hans from comment #7) > > What do you mean? > > You said I should enable Tasks, but I can't find it in the settings. Maybe > I'm blind. > > Or do you mean the "Add launchers only in the task area" option? Can you show me a screenshot of your Tasks settings? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406506] Wish - Show metadata of files stored on locations non-indexed by baloo in details view mode
https://bugs.kde.org/show_bug.cgi?id=406506 Stefan Brüns changed: What|Removed |Added CC||stefan.bruens@rwth-aachen.d ||e --- Comment #9 from Stefan Brüns --- (In reply to Méven Car from comment #8) > I didn't get that was about the detail view column in the first place. > Thank you for correcting me. Me neither ... @Patrick - next time, please be more specific. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 407026] Kmail crashes whenever creating a new mail
https://bugs.kde.org/show_bug.cgi?id=407026 Andreas changed: What|Removed |Added CC||hoheneg...@web.de --- Comment #1 from Andreas --- Created attachment 119698 --> https://bugs.kde.org/attachment.cgi?id=119698&action=edit Debug trace of kmail for crash during startup (observed when not deleting autosave folder) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 407026] New: Kmail crashes whenever creating a new mail
https://bugs.kde.org/show_bug.cgi?id=407026 Bug ID: 407026 Summary: Kmail crashes whenever creating a new mail Product: kmail2 Version: 5.11.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: hoheneg...@web.de Target Milestone: --- Created attachment 119697 --> https://bugs.kde.org/attachment.cgi?id=119697&action=edit The command line output observed during new mail crash. SUMMARY Kmail crashes when creating a new mail. STEPS TO REPRODUCE Not sure how to reproduce, but I see the issues on two similar KDE neon installations, so I am wondering why nobody else seems to have reported it. The history of the crash is as follows. I experienced a crash of kmail (for whatever reason; In one case I modified the plugin settings trying to enable language tool grammar check). After the crash kmail did not start anymore (crashing each time at start). I figured that I could fix that with rm -r /home/andreas/.local/share/kmail2/autosave After that kmail can be started again without immediate crash. However, clicking the new mail icon (or pressing a shortcut that would also bring up a new composer window) crashes kmail with the trace below. In the second attachment I provide the trace that I get if I do not remove the autosave directory, in which case kmail crashes right at the start. OBSERVED RESULT Kmail crashes leaving the attached output on the command line. The consequence is that it cannot be used anymore to write and send mail. EXPECTED RESULT Kmail shows a new composer window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.15 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef2a5b0bc0 (LWP 20620))] Thread 25 (Thread 0x7fee634e9700 (LWP 20674)): #0 0x7fef1cd89ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fee634e8710, expected=0, futex_word=0x7fee634e88f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fef1cd89ed9 in __pthread_cond_wait_common (abstime=0x7fee634e87b0, mutex=0x7fee634e88a8, cond=0x7fee634e88d0) at pthread_cond_wait.c:533 #2 0x7fef1cd89ed9 in __pthread_cond_timedwait (cond=0x7fee634e88d0, mutex=0x7fee634e88a8, abstime=0x7fee634e87b0) at pthread_cond_wait.c:667 #3 0x7fef11ce9177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fef11ce9ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fef11ce9bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fef11ca7851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fef11caa387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fef11caa974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fef11cebcd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fef1cd836db in start_thread (arg=0x7fee634e9700) at pthread_create.c:463 #11 0x7fef2760688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fee69ac0700 (LWP 20671)): #0 0x7fef1cd899f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fef0d29efb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fef1cd899f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fef0d29ef68, cond=0x7fef0d29ef90) at pthread_cond_wait.c:502 #2 0x7fef1cd899f3 in __pthread_cond_wait (cond=0x7fef0d29ef90, mutex=0x7fef0d29ef68) at pthread_cond_wait.c:655 #3 0x7fef0cfa8844 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fef0cfa8889 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fef1cd836db in start_thread (arg=0x7fee69ac0700) at pthread_create.c:463 #6 0x7fef2760688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fee6a2c1700 (LWP 20666)): #0 0x7fef1cd89ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fee6a2c0710, expected=0, futex_word=0x7fee6a2c08f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fef1cd89ed9 in __pthread_cond_wait_common (abstime=0x7fee6a2c07b0, mutex=0x7fee6a2c08a8, cond=0x7fee6a2c08d0) at pthread_cond_wait.c:533 #2 0x7fef1cd89ed9 in __pthread_cond_timedwait (cond=0x7fee6a2c08d0, mutex=0x7fee6a2c08a8, abstime=0x7fee6a2c07b0) at pthread_cond_wait.c:667 #3 0x7fef11ce9177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fef11ce9ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fef11ce9bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fef11ca7851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEng
[kmymoney] [Bug 407021] Show hidden accounts
https://bugs.kde.org/show_bug.cgi?id=407021 --- Comment #1 from Jack --- I believe the View/Show all accounts will show closed accounts if the Settings/Configure KMyMoney is set to not show closed accounts. If closed accounts are shown, then toggling "Show all accounts" will have no apparent effect. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 407025] New: xdg-desktop-portal-kde 5.15.4 segmentation faults in gbm_device_destroy at gbm.c:109 in mesa-libgbm when logging out of Plasma
https://bugs.kde.org/show_bug.cgi?id=407025
Bug ID: 407025
Summary: xdg-desktop-portal-kde 5.15.4 segmentation faults in
gbm_device_destroy at gbm.c:109 in mesa-libgbm when
logging out of Plasma
Product: xdg-desktop-portal-kde
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: matthew.fagn...@utoronto.ca
Target Milestone: ---
SUMMARY
coredumpctl showed drkonqi aborted 6 times since April 12 which occurred when I
logged out of Plasma 5.15.4 on X 1.20.4 in Fedora 30. These crashes had command
lines like
/usr/libexec/drkonqi --appname xdg-desktop-portal-kde --apppath /usr/libexec
--signal 11 --pid 3710 --startupid 0
coredumpctl debug / gdb had the following on the last crash.
Core was generated by `/usr/libexec/drkonqi --appname xdg-desktop-portal-kde
--apppath /usr/libexec --'.
Program terminated with signal SIGABRT, Aborted.
#0 0xb7f7d85d in __kernel_vsyscall ()
(gdb) bt
#0 0xb7f7d85d in __kernel_vsyscall ()
#1 0xb6071786 in __libc_signal_restore_set (set=0xbf85afac)
at ../sysdeps/unix/sysv/linux/internal-signals.h:84
#2 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
#3 0xb605b37b in __GI_abort () at abort.c:79
#4 0xb6449b84 in qt_message_fatal (context=..., message=...)
at global/qlogging.cpp:1901
#5 QMessageLogger::fatal (this=0xbf85b308, msg=0xb6d95af7 "%s")
at global/qlogging.cpp:887
#6 0xb6a0e153 in init_platform (argv=, argc=@0xbf85b5f0: 11,
platformThemeName=..., platformPluginPath=...,
pluginNamesWithArguments=...)
at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208
#7 QGuiApplicationPrivate::createPlatformIntegration (this=)
at kernel/qguiapplication.cpp:1384
#8 0xb6a0e9cc in QGuiApplicationPrivate::createEventDispatcher
(this=0x1172db0)
at kernel/qguiapplication.cpp:1401
#9 0xb701ca5c in QApplicationPrivate::createEventDispatcher (this=0x1172db0)
at kernel/qapplication.cpp:185
#10 0xb6635df4 in QCoreApplicationPrivate::init (this=)
at kernel/qcoreapplication.cpp:857
#11 0xb6a10219 in QGuiApplicationPrivate::init (this=0x1172db0)
at kernel/qguiapplication.cpp:1430
#12 0xb701ea2e in QApplicationPrivate::init (this=0x1172db0)
at kernel/qapplication.cpp:566
#13 0xb701eae5 in QApplication::QApplication (this=0xbf85b5ac,
argc=@0xbf85b5f0: 11, argv=0xbf85b684, _internal=330753)
at kernel/qapplication.cpp:554
--Type for more, q to quit, c to continue without paging--c
#14 0x0048c585 in main (argc=, argv=0xbf85b684) at
/usr/src/debug/plasma-drkonqi-5.15.4-1.fc30.i386/src/main.cpp:63
I ran /usr/libexec/xdg-desktop-portal-kde & in konsole in Plasma which output
xdp-kde-wayland-integration: Cannot open render node: No such file or
directory
I ran gdb -p 3710 in VT2, where 3710 was xdg-desktop-portal-kde's process ID.
I ran c in gdb. I logged out of Plasma. xdg-desktop-portal-kde segmentation
faulted in gbm_device_destroy at gbm.c:109 in mesa-libgbm-19.0.3-1. The
segmentation fault looked like a null pointer dereference since gbm=0x0 and
gbm.c:109 was gbm->refcount--;
Core was generated by `/usr/libexec/xdg-desktop-portal-kde'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xb7b99b68 in gbm_device_destroy (gbm=0x0) at ../src/gbm/main/gbm.c:109
109gbm->refcount--;
[Current thread is 1 (Thread 0xb2372780 (LWP 3710))]
(gdb) bt full
#0 0xb7b99b68 in gbm_device_destroy (gbm=0x0) at ../src/gbm/main/gbm.c:109
No locals.
#1 0x0055a733 in
WaylandIntegration::WaylandIntegrationPrivate::~WaylandIntegrationPrivate (
this=0x59a2a0 <(anonymous
namespace)::Q_QGS_globalWaylandIntegration::innerFunction()::holder>,
__in_chrg=)
at
/usr/src/debug/xdg-desktop-portal-kde-5.15.4-1.fc30.i386/src/waylandintegration.cpp:186
No locals.
#2 0x0055a79c in (anonymous
namespace)::Q_QGS_globalWaylandIntegration::Holder::~Holder (
this=0x59a2a0 <(anonymous
namespace)::Q_QGS_globalWaylandIntegration::innerFunction()::holder>,
__in_chrg=)
at
/usr/src/debug/xdg-desktop-portal-kde-5.15.4-1.fc30.i386/src/waylandintegration.cpp:48
No locals.
#3 0xb6103038 in __run_exit_handlers (status=0, listp=0xb62753fc
<__exit_funcs>,
run_list_atexit=true, run_dtors=true) at exit.c:108
atfct =
onfct =
cxafct =
f =
new_exitfn_called = 240
cur =
#4 0xb6103167 in __GI_exit (status=0) at exit.c:139
No locals.
#5 0xb60eb8b5 in __libc_start_main (main=0x501710 , argc=1,
--Type for more, q to quit, c to continue without paging--c
argv=0xbff17d14, init=0x563ba0 <__libc_csu_init>, fini=0x563c00
<__libc_csu_fini>, rtld_fini=0xb7fa6c30 <_dl_fini>, stack_end=0xbff17d0c) at
../csu/libc-start.c:342
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -1238937600, 0,
[digikam] [Bug 407022] digikam 6.1.0-196.1-x86_64 crash at start
https://bugs.kde.org/show_bug.cgi?id=407022 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- This will most certainly be a package problem. Which happens more often when the KDE:Extra repository is used. Please start digiKam from the console and post the messages. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407023] KDNLIVE crash. It's go out.
https://bugs.kde.org/show_bug.cgi?id=407023 Karl changed: What|Removed |Added CC||karl...@gmx.de --- Comment #1 from Karl --- Hi Elson, I had a similar Problem lately. After I deleted the Kdenlive-Settings and started Kdenlive new, it worked without crash. In Linux you can find these settings here: ~/.config/kdenliverc : contains the general settings of the application. Delete this and restart kdenlive to reset the application to "factory" Settings. If you run the appimage you might Need to delete another file. I don't know which one though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405912] Add support for adaptive sync (FreeSync) in KWin for Wayland and X sessions
https://bugs.kde.org/show_bug.cgi?id=405912 Rainer Finke changed: What|Removed |Added CC||m...@rainer-finke.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407024] New: Panel texture flickering
https://bugs.kde.org/show_bug.cgi?id=407024 Bug ID: 407024 Summary: Panel texture flickering Product: plasmashell Version: 5.15.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I noticed texture flickering in a few cases. STEPS TO REPRODUCE Scenario 1. 1. Create a horizontal panel with a few application icons. 2. Move the mouse over the icons on the panel. Try moving fast enough so that tooltips with the icon name don't appear. Scenario 2. 1. Invoke logout/reboot/shutdown effect. OBSERVED RESULT Scenario 1. The panel texture is flickering. I can see its opacity vary, as well as contents jitter during the flickering. Scenario 2. The screen dimming effect of the logout/reboot/shutdown animation has flickering opacity. After the animation completion, sometimes the effect darkens the desktop contents more than usual, and then after a fraction of a second (or maybe after I move the mouse) opacity gets restored to usual (which looks like desktop contents become less darkened). While the animation is in progress, the logout/reboot/shutdown icons flicker. EXPECTED RESULT No flickering should happen. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Mesa: 19.0.2 X.org: 1.20.4 ADDITIONAL INFORMATION I'm seeing this on a laptop with Intel Haswell iGPU (i915 driver). I've also seen the problem with logout/reboot/shutdown effect on a different machine, also with Kubuntu 19.04, but with Nvidia GPU (430.09 driver). Not the panel flickering, though. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406964] Latte dock constantly resizing when nearly out of space
https://bugs.kde.org/show_bug.cgi?id=406964 --- Comment #7 from sdfjsfjaei-h...@yahoo.de --- > What do you mean? You said I should enable Tasks, but I can't find it in the settings. Maybe I'm blind. Or do you mean the "Add launchers only in the task area" option? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406971] Face frames are misaligned on Digikam when face framing was done on Picasa.
https://bugs.kde.org/show_bug.cgi?id=406971 --- Comment #8 from Alexandre Belz --- I don't understand your comment Maik, sorry. Anyway, I've found a reason of that bug : the picture was edited in Picasa BUT NOT SAVED BY PICASA. I noticed that the faces position were misaligned AND ROTATED, and this gave me the trick. I went back in Picasa and noticed that modifications done in the past were NOT saved in Picasa. So I guess that the Picasa database was OK, but not applied to the JPG picture itself. Now that the picture is saved, I went back to Digikam 6.1.0 it's better : the faces are now well located... but they are twice more numerous ! * See screen capture : 406971_2019-04-28_1.png * and new JPG saved by Picasa : DSCN6711_saved.JPG -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405436] Some installed apps from discover do not have desktop entry
https://bugs.kde.org/show_bug.cgi?id=405436 Patrick Silva changed: What|Removed |Added CC||da...@thefallenphoenix.net --- Comment #2 from Patrick Silva --- *** Bug 407006 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407006] Snaps not added to Application Launcher
https://bugs.kde.org/show_bug.cgi?id=407006 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 405436 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379004] test_duchain-clang fails
https://bugs.kde.org/show_bug.cgi?id=379004 --- Comment #8 from RJVB --- I have no idea. I can no longer get the crash myself either on Linux, after I corrected something in a local mod (flagged by valgrind) that should be completely unrelated. The whole (top)ducontext structure is a bit of a cardhouse with some known instabilities (like sometimes getting in a closed loop on exit). If I understand the purpose of the ReferencedTopDUContext class correctly it's a kind of proof of that brittleness which can apparently lead to stale references being maintained and used at some point, under certain conditions. FWIW, I do have a patch in place that helps avoid the locking-on-exit issue I mentioned, but a priori that patch shouldn't be the source of my issue (it prints warnings when it takes preventive action and I'm not seeing any of those). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407023] New: KDNLIVE crash. It's go out.
https://bugs.kde.org/show_bug.cgi?id=407023 Bug ID: 407023 Summary: KDNLIVE crash. It's go out. Product: kdenlive Version: 19.04.0 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: epraci...@bol.com.br Target Milestone: --- SUMMARY O KDNLIVE "sai". Ele está funcionando e sai. Crash of KNDLIVE. The KDNLIVE get out. I'm running it and it get out of my screen. I must to run it again. All the time when I'm using it, this hapen. I have tried to reinstall it a lot of time, but again, again, again. Normally when i'm using the "cut" tool. When I "cut", KDNLIVE crash. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/ Mint (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION MLT versão 6.15.0 Bibliotecas FFmpeg -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407022] New: digikam 6.1.0-196.1-x86_64 crash at start
https://bugs.kde.org/show_bug.cgi?id=407022
Bug ID: 407022
Summary: digikam 6.1.0-196.1-x86_64 crash at start
Product: digikam
Version: 6.1.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: digikam-bugs-n...@kde.org
Reporter: li...@daniel-bauer.com
Target Milestone: ---
SUMMARY
since the latest update digikam 6.1.0-196.1-x86_64 from
obs://build.opensuse.org/KDE:Extra produces a segmentation fault immediately at
start ("Speicherzugriffsfehler (Speicherabzug geschrieben)")
STEPS TO REPRODUCE
1. start dikigam from menu or console
2.
3.
OBSERVED RESULT
immediately crashes with segmentation fault
EXPECTED RESULT
start digikam
SOFTWARE/OS VERSIONS
Opensuse Leap 42.3
KDE-Plasma-Version: 5.8.7
KDE-Frameworks-Version: 5.32.0
Qt-Version: 5.6.2
Kernel-Version: 4.4.176-96-default
64bit
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #7 from Nick --- Created attachment 119696 --> https://bugs.kde.org/attachment.cgi?id=119696&action=edit akonadictl_fsck_vacuum_after_NULL-RID_cleanup.txt -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #6 from Nick --- Created attachment 119695 --> https://bugs.kde.org/attachment.cgi?id=119695&action=edit akonadi_kmail_kontact_mariadb_installed_software_levels.txt -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #5 from Nick --- Martin, akonadictl version is 5.7.3 kdepim is at level 17.12.3 The levels of all akonadi/kmail/etc installed software and the reports od akonadictl fsck| vacuum are provided as attachments. After the "remoteId is NULL" cleanup I noticed that all those annoyng messages "wait until ..." are gone . I checked my email at the interner provider server and there are no emails there . The IP tech support told me that with IMAP after an email is received by the client[laptop] it is deleted from the server . So I did not understand why the kmail client was checking remote server . Now it appears that kmail/akonadi tries to solve that NULL remoteId . akonadictl fsck's message ' Item "28761" has no RID.' is wrong . That item with id=28761 HAS an RID but its value is set to NULL . It is very strange/misleading message and the culprit seems to be akonadictl and/or kmail because they do not interpret correctly database/table/record's contents . Thanks, Nick -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 359320] formatDateTime(..., KLocale::FancyShortDate, ... ) should take LC_TIME into account
https://bugs.kde.org/show_bug.cgi?id=359320 p...@gmx.com changed: What|Removed |Added CC||p...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404151] Time Format setting to en_SE results in unrecognized LC_TIME
https://bugs.kde.org/show_bug.cgi?id=404151 p...@gmx.com changed: What|Removed |Added CC||p...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365139] Inconsistent localization of month names in calendar plasmoid
https://bugs.kde.org/show_bug.cgi?id=365139 p...@gmx.com changed: What|Removed |Added CC||p...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 308674] KDE ignores LC_TIME variable
https://bugs.kde.org/show_bug.cgi?id=308674 p...@gmx.com changed: What|Removed |Added CC||p...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 400956] The date/time format of the LC_TIME locale is not regarded
https://bugs.kde.org/show_bug.cgi?id=400956 p...@gmx.com changed: What|Removed |Added CC||p...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 359191] aKregator does not honor LC_TIME / date and time in wrong format
https://bugs.kde.org/show_bug.cgi?id=359191 p...@gmx.com changed: What|Removed |Added CC||p...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344811] Plasma Digital Clock ignores glibc's LC_TIME settings
https://bugs.kde.org/show_bug.cgi?id=344811 p...@gmx.com changed: What|Removed |Added CC||p...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407020] New: When the default font size for epub is changed, links are at the wrong positions
https://bugs.kde.org/show_bug.cgi?id=407020 Bug ID: 407020 Summary: When the default font size for epub is changed, links are at the wrong positions Product: okular Version: 1.7.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EPub backend Assignee: okular-de...@kde.org Reporter: david.hu...@mailbox.org Target Milestone: --- Created attachment 119693 --> https://bugs.kde.org/attachment.cgi?id=119693&action=edit When the default epub font is not Ubuntu 8, links are broken SUMMARY Links in epub documents are at fixed positions, which are only valid with the default font size (Settings -> Configure Backends), which is Ubuntu 8. Even when the font size was changed before the epub was opened, the links are at the wrong position. STEPS TO REPRODUCE 1. Download e. g. https://github.com/paulkoegel/redux-offline-docs/raw/master/redux-documentation-2019-01-04.epub or https://www.freecadweb.org/manual/a-freecad-manual.epub and open in Okular. OBSERVED RESULT Links are where they should be. STEPS TO REPRODUCE 2. Go to Settings -> Configure Backends and change the default epub font size. (E. g. Ubuntu 14) OBSERVED RESULT Links are still at the old position. EXPECTED RESULT Links are where they should be. SOFTWARE/OS VERSIONS: KDE Neon 5.15.4 KDE Frameworks 5.57.0 Qt 5.12.0 Okular 1.7.10, Epub Backend 0.2.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407019] Dolphin crashed while copying files from PC to phone
https://bugs.kde.org/show_bug.cgi?id=407019 Julian Schraner changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||m...@xyquadrat.ch --- Comment #1 from Julian Schraner --- Hello Alexandr, this looks like a problem with the implementation of MTP in Dolphin to me. This implementation has recently been rewritten (for Dolphin 18.12) which brought many improvements to stability and should have fixed crashes similar to yours. Please check if this crash does still happen with Dolphin 18.12 or newer and reopen this report in this case. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407021] New: Show hidden accounts
https://bugs.kde.org/show_bug.cgi?id=407021 Bug ID: 407021 Summary: Show hidden accounts Product: kmymoney Version: 5.0.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: lp.allar...@gmail.com Target Milestone: --- SUMMARY In KMM 5.0.0, Menu entry "Show all Accounts" under View menu does nothing and has no effect (like if no code was associated to it). Showing/hiding closed accounts is done via Preferences > Filter > Do not show closed accounts. STEPS TO REPRODUCE 1. Install KMM 5.0.0 2. GO to accounts page & try menu View>Show all accounts OBSERVED RESULT Menu entry has NO effect EXPECTED RESULT Menu entry should toggle between showing & hiding closed accounts SOFTWARE/OS VERSIONS KDE Frameworks 5.44.0 Qt 5.9.5 (built against 5.9.5) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407020] When the default font size for epub is changed, links are at the wrong positions
https://bugs.kde.org/show_bug.cgi?id=407020 --- Comment #1 from David Hurka --- Created attachment 119694 --> https://bugs.kde.org/attachment.cgi?id=119694&action=edit When the default font size for epub is not changed, links are not broken -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 392133] Huge memory consumption while doing nothing
https://bugs.kde.org/show_bug.cgi?id=392133 PhobosK changed: What|Removed |Added CC||phob...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406855] Feature request: date from filename
https://bugs.kde.org/show_bug.cgi?id=406855 --- Comment #9 from Maik Qualmann --- Git commit b0f560f8982d67dea435f86762340941f58dee2b by Maik Qualmann. Committed on 28/04/2019 at 18:17. Pushed by mqualmann into branch 'master'. add case for date from filename M +2-0core/libs/timeadjust/timeadjustcontainer.cpp https://invent.kde.org/kde/digikam/commit/b0f560f8982d67dea435f86762340941f58dee2b -- You are receiving this mail because: You are watching all bug changes.
