[dolphin] [Bug 415377] Connection from Dolphin to Samsung Note 2 via USB [debug on phone turned on] crashes
https://bugs.kde.org/show_bug.cgi?id=415377 --- Comment #3 from Christoph Feck --- > 16.04 is still maintained. It is maintained by Ubuntu, so if you need bug fixes for this version, please report this issue to Ubuntu maintainers. > Thumb drive is a separate segment. Any suggestions. It is possible to mount individual directories on separate partitions. Please ask in Ubuntu or general Linux forums for help. This bug tracker is not a help forum. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 411487] kcm-wacomtablet is providing incorrect default settings, causing choppy, wobbly lines and inability to click
https://bugs.kde.org/show_bug.cgi?id=411487 --- Comment #3 from Shawn Rutledge --- I didn't really notice lines being choppy though, but maybe something is different on my system. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 411487] kcm-wacomtablet is providing incorrect default settings, causing choppy, wobbly lines and inability to click
https://bugs.kde.org/show_bug.cgi?id=411487 Shawn Rutledge changed: What|Removed |Added Summary|kcm-wacomtablet is |kcm-wacomtablet is |providing incorrect default |providing incorrect default |settings, causing choppy, |settings, causing choppy, |wobbly lines|wobbly lines and inability ||to click -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 411487] kcm-wacomtablet is providing incorrect default settings, causing choppy, wobbly lines
https://bugs.kde.org/show_bug.cgi?id=411487 Shawn Rutledge changed: What|Removed |Added CC||s...@ecloud.org --- Comment #2 from Shawn Rutledge --- I was just trying the Wacoms on KDE Neon (I managed to reproduce https://bugreports.qt.io/browse/QTBUG-77826 there). What I noticed is that even more of the defaults were not sane: as soon as I installed kcm-wacomtablet, I couldn't click with the stylus anymore. It took me a while to realize that it had unmapped all the buttons, and I had to set that up again manually (map stylus tip to left click, one button to right click and another to middle click). This issue is also mentioned here, by the way: https://wiki.manjaro.org/index.php?title=Wacom_Tablet_And_Pen#KDE_Plasma_5_2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415377] Connection from Dolphin to Samsung Note 2 via USB [debug on phone turned on] crashes
https://bugs.kde.org/show_bug.cgi?id=415377 --- Comment #2 from Michael --- (In reply to Nate Graham from comment #1) > Hi Michael, > You're using software that is almost four years old. I'm afraid we cannot > offer support for such old software, and many or even most of the bugs you > are experiencing have been fixed since then. In particular, MTP support was > completely written for better reliability recently. Consider upgrading. > Kubuntu 19.10 is quite nice, and 20.04 will be released in a few months as > an LTS release. @ Nate Graham: My Comment: 16.04 is still maintained. So. Would move to newer Linux but cannot. Insufficient root partition room. Need 12 gig more (working space??). Would like to use thumb drive for temporary added root space but when mounted, is not part of partition. Thumb drive is a separate segment. Any suggestions. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 415422] New: LibreOffice Calc BASIC Editor crash in KDE desktops in Spins when resize Watches Panel and Call Stack Panel
https://bugs.kde.org/show_bug.cgi?id=415422 Bug ID: 415422 Summary: LibreOffice Calc BASIC Editor crash in KDE desktops in Spins when resize Watches Panel and Call Stack Panel Product: kde Version: unspecified Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: nuk...@gmail.com Target Milestone: --- SUMMARY Please see > https://bugs.documentfoundation.org/show_bug.cgi?id=127642 STEPS TO REPRODUCE 1. Open LibreOffice Calc 2. Tools > Macros > Organize Macros > LibreOffice BASIC > New > Create 'Module1' > OK 3. Resize Watches Panel and Call Stack Panel by moving downwards to the bottom of the Editor's screen. OBSERVED RESULT LibreOffice Editor and Calc crashed. (In GNOME by default it doesn't crash.) EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31 KDE Desktop Spins (available in About System) KDE Plasma Version: plasmashell 5.17.4 KDE Frameworks Version: kf5-config --version Qt Version: Qt: 5.12.5 KDE Frameworks: 5.64.0 kf5-config: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 375909] Breeze SDDM wallpaper was reset in KDE Neon 5.9 update
https://bugs.kde.org/show_bug.cgi?id=375909 --- Comment #6 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.
[KScreen] [Bug 414256] rotating screen breaks session kscreen
https://bugs.kde.org/show_bug.cgi?id=414256 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 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 413950] Undo Expand Canvas crashes Krita
https://bugs.kde.org/show_bug.cgi?id=413950 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |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.
[Breeze] [Bug 365690] kaccessibleapp icon
https://bugs.kde.org/show_bug.cgi?id=365690 --- 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.
[kdelibs] [Bug 183252] Empty "Default Browser" launches fill x client limit and freezes kde.
https://bugs.kde.org/show_bug.cgi?id=183252 --- Comment #9 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.
[kdelibs] [Bug 328881] kbookmarkmanager creates empty .tbcache file
https://bugs.kde.org/show_bug.cgi?id=328881 --- Comment #4 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 414359] chrome + ripcord + nvidia + kwin crash
https://bugs.kde.org/show_bug.cgi?id=414359 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[plasmashell] [Bug 413934] High CPU usage when switching wallpaper as slideshow
https://bugs.kde.org/show_bug.cgi?id=413934 --- 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.
[Breeze] [Bug 339638] Upgrade 5.0 -> 5.1 oxygen icons being used from cache
https://bugs.kde.org/show_bug.cgi?id=339638 --- Comment #5 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.
[Breeze] [Bug 370569] kde4breeze.upd ignores system distributor values from XDG_CONFIG_DIRS/kdeglobals
https://bugs.kde.org/show_bug.cgi?id=370569 --- 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.
[apper] [Bug 337941] Software name coloumn does not resize
https://bugs.kde.org/show_bug.cgi?id=337941 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415212] Dolphin crashed when renaming folder
https://bugs.kde.org/show_bug.cgi?id=415212 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 414227 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 414227] Dolphin crashes in KFileMetaData::UserMetaData::queryAttributes() when retrieving metadata from dangling symlink
https://bugs.kde.org/show_bug.cgi?id=414227 Nate Graham changed: What|Removed |Added CC||govers...@gmail.com --- Comment #8 from Nate Graham --- *** Bug 415212 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 414227] Dolphin crashes in KFileMetaData::UserMetaData::queryAttributes() when retrieving metadata from dangling symlink
https://bugs.kde.org/show_bug.cgi?id=414227 Nate Graham changed: What|Removed |Added CC||s...@gmx.eu --- Comment #7 from Nate Graham --- *** Bug 415418 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415418] Dolphin crashes when clicking on a dangling symbolic link
https://bugs.kde.org/show_bug.cgi?id=415418 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 414227 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #3 from Andrew Udvare --- Created attachment 124635 --> https://bugs.kde.org/attachment.cgi?id=124635=edit New user screenshot This is from a new user account with minimal customisation, 1.5x scale enabled, 144 DPI force enabled (because that is what System Settings does automatically). The left is Kate and the right KPatience. KPatience correctly shows its menus while Kate remains too large. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 411811] QPushButton and QLineEdit have different height
https://bugs.kde.org/show_bug.cgi?id=411811 Noah Davis changed: What|Removed |Added CC||noaha...@gmail.com --- Comment #3 from Noah Davis --- It seems like only buttons with text have this problem. If a button only has an icon, then it is the same size as a QLineEdit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #2 from Andrew Udvare --- Created attachment 124634 --> https://bugs.kde.org/attachment.cgi?id=124634=edit Konsole displaying incorrectly Konsole claims this is point size 9 but it definitely is not when compared to my browser or LibreOffice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #1 from Andrew Udvare --- Created attachment 124633 --> https://bugs.kde.org/attachment.cgi?id=124633=edit System Settings rendering correctly -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] New: [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 Bug ID: 415421 Summary: [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole Product: plasmashell Version: master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: audv...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 124632 --> https://bugs.kde.org/attachment.cgi?id=124632=edit Dolphin vs a Gtk+ app rendering SUMMARY Certain apps are rendering font sizes too large in comparison to others. This applies to: * Dolphin * Kate * KWrite * Konsole The font sizes are about 25% larger than expected. System Settings and just about every other app I have including Chromium run at the correct size. I am attaching screenshots for reference. The first is a Gtk+ app vs Dolphin, where the Gtk+ app is showing the correct scale. The second is System Settings which is rendering correctly with the current settings. STEPS TO REPRODUCE 1. Set scale factor to 1.5 2. Log out and log back in 3. Run Kate OBSERVED RESULT Kate is running with correct size icons (I think) but a 25% larger font than expected. EXPECTED RESULT Kate should have normal size fonts as other apps (like System Settings) do. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Gentoo, 5.17.4 (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Recently updated to latest versions available of Qt, Plasma, etc on Gentoo Portage. This was not happening in a prior version. I do not have forced font DPI enabled nor a DPI setting in ~/.Xresources. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415420] New: cjk input of apt install and flatpak (appimage)
https://bugs.kde.org/show_bug.cgi?id=415420 Bug ID: 415420 Summary: cjk input of apt install and flatpak (appimage) Product: kdenlive Version: Appimage - Refactoring Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gsh...@gmail.com Target Milestone: --- apt install kdenlive enables cjk input. It is Good. but However, flatpak and appimage do not support cjk input. This is likely due to apparmor blocking access ??? I want Flatpak or appimage supports cjk input. Can apply for either? Thank you for reading it. Merry Christmas Happy end of the year. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413084] Background of decoration buttons is not rendered correctly
https://bugs.kde.org/show_bug.cgi?id=413084 Christoph Feck changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Christoph Feck --- To further investigate this issue, KDE developers need the information requested in comment 1 and comment 2. If you can provide it, or need help with finding that information, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408253] Plasma Panel Starts Flashing (Randomly?) after update from OpenSUSE 15.0 to 15.1
https://bugs.kde.org/show_bug.cgi?id=408253 Christoph Feck changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #11 from Christoph Feck --- To further investigate this issue, KDE developers need the information requested in comment 9. If you can provide it, or need help with finding that information, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415419] New: kwin_x11/intel : screen flickers, large parts are black, sometimes show stale content
https://bugs.kde.org/show_bug.cgi?id=415419 Bug ID: 415419 Summary: kwin_x11/intel : screen flickers, large parts are black, sometimes show stale content Product: kwin Version: 5.14.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: stefan.schwar...@gmx.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. log in / kde desktop OBSERVED RESULT see description, always reproducible EXPECTED RESULT well, what a compositing window manager should do... SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.3.0-3-amd64 #1 SMP Debian 5.3.15-1 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.62 (?) Qt Version: 5.12.5 ADDITIONAL INFORMATION Intel CPU with integrated graphics, nvidia optimus, nouveau blacklisted, no nvidia-drivers installed (more info below) The following is basically a quote from debbugs (#deb943585, 27 Oct 2019): Right after login I get flickering black rectangles on the screen, which may cover up to 90% of its area. Windows mostly remain black or their content suddenly becomes visible, the task bar remains black and I see other residuals of the kde splash screen where windows should be drawn or the background wallpaper be restored. Swithing to a VT; all seems ok, kwin, the desktop and applications are running. So far, my only clue as to what may be going on is a workaroud I found: if I start a terminal via keyboard shortcut and issue blindly DRI_PRIME=1 kwin_x11 --replace then afterwards things behave mostly normally (Sometimes window content is still not correctly updated). I just picked this line up from older bug reports against kwin on the net without understanding what it does. This is the output of kwin following this command in the hope that it helps OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL version string: 4.5 (Core Profile) Mesa 19.2.1 OpenGL shading language version string: 4.50 Driver: Intel GPU class: Unknown OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 19.2.1 X server version: 1.20.4 Linux kernel version: 5.3 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE (tainted module is vmware kernel stuff (patched Workstation 14)) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415418] New: Dolphin crashes when clicking on a dangling symbolic link
https://bugs.kde.org/show_bug.cgi?id=415418 Bug ID: 415418 Summary: Dolphin crashes when clicking on a dangling symbolic link Product: dolphin Version: 19.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: s...@gmx.eu CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (19.12.0) Qt Version: 5.13.1 Frameworks Version: 5.64.0 Operating System: Linux 5.3.12-1-default x86_64 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: Mouse click on the directory list entry of a symbolic link where the source directory was renamed outside of Dolphin. - Custom settings of the application: openSUSE Tumbleweed with all updates applied. An old symbolic link, like created with "ln -s source_dir mydir", in the home directory, like "/home/tux/mydir". The name of the " source_dir" has been manually changed outside of Dolphin; without updating the the symbolic link entry in the home directory. Other info: The "source_dir" is located on another disk partition, formatted with btrfs. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57dab2af80 (LWP 4014))] Thread 6 (Thread 0x7f57c6ae5700 (LWP 4019)): #0 0x7f57dfa8fbdf in poll () from /lib64/libc.so.6 #1 0x7f57db74f27e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f57db74f39f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f57dd90d98b in QEventDispatcherGlib::processEvents (this=0x7f57bc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f57dd8b60cb in QEventLoop::exec (this=this@entry=0x7f57c6ae4da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f57dd6ee021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f57dd6ef1a2 in QThreadPrivate::start (arg=0x564d13b467a0) at thread/qthread_unix.cpp:360 #7 0x7f57dc15af2a in start_thread () from /lib64/libpthread.so.0 #8 0x7f57dfa9a4af in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f57d0c9c700 (LWP 4018)): #0 0x7f57dc1616a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f57d22af515 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f57d2292897 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f57dc15af2a in start_thread () from /lib64/libpthread.so.0 #4 0x7f57dfa9a4af in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f57d149d700 (LWP 4017)): #0 0x7f57dc1616a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f57d22af515 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f57d2292897 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f57dc15af2a in start_thread () from /lib64/libpthread.so.0 #4 0x7f57dfa9a4af in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f57d3e88700 (LWP 4016)): #0 0x7f57db74bf18 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f57db74d4fc in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f57db74e743 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x7f57db74f1ab in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f57db74f39f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f57dd90d98b in QEventDispatcherGlib::processEvents (this=0x7f57cc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f57dd8b60cb in QEventLoop::exec (this=this@entry=0x7f57d3e87d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f57dd6ee021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f57ddb964f6 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f57dd6ef1a2 in QThreadPrivate::start (arg=0x7f57ddc18d80) at thread/qthread_unix.cpp:360 #10 0x7f57dc15af2a in start_thread () from /lib64/libpthread.so.0 #11 0x7f57dfa9a4af in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f57d8a54700 (LWP 4015)): #0 0x7f57dfa8fbdf in poll () from /lib64/libc.so.6 #1 0x7f57dc128742 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f57dc1293fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f57d8c5ef90 in QXcbEventQueue::run (this=0x564d1329eb80) at qxcbeventqueue.cpp:228 #4 0x7f57dd6ef1a2 in QThreadPrivate::start (arg=0x564d1329eb80) at thread/qthread_unix.cpp:360 #5 0x7f57dc15af2a in start_thread () from /lib64/libpthread.so.0 #6 0x7f57dfa9a4af in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f57dab2af80 (LWP 4014)): [KCrash Handler] #6 QByteArray::QByteArray
[valgrind] [Bug 415382] vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2 0x79 0x13 0x14 0x1A 0xC5 0xF9 0x6E 0xE9
https://bugs.kde.org/show_bug.cgi?id=415382 --- Comment #4 from Tom Hughes --- *** This bug has been marked as a duplicate of bug 356715 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356715] vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2 0x7D 0x13 0x4 0x4A 0xC5 0xFC
https://bugs.kde.org/show_bug.cgi?id=356715 --- Comment #5 from Tom Hughes --- This is VCVTPH2PS and is fixed in the 3.15.0 release. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398870] Please add support for instruction vcvtps2ph
https://bugs.kde.org/show_bug.cgi?id=398870 Tom Hughes changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||t...@compton.nu --- Comment #2 from Tom Hughes --- This was fixed in the 3.15.0 release. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356715] vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2 0x7D 0x13 0x4 0x4A 0xC5 0xFC
https://bugs.kde.org/show_bug.cgi?id=356715 Tom Hughes changed: What|Removed |Added CC||the.true.nathan.mills@gmail ||.com --- Comment #6 from Tom Hughes --- *** Bug 415382 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398870] Please add support for instruction vcvtps2ph
https://bugs.kde.org/show_bug.cgi?id=398870 Tom Hughes changed: What|Removed |Added CC||the.true.nathan.mills@gmail ||.com --- Comment #1 from Tom Hughes --- *** Bug 415382 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 415382] vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2 0x79 0x13 0x14 0x1A 0xC5 0xF9 0x6E 0xE9
https://bugs.kde.org/show_bug.cgi?id=415382 Tom Hughes changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Tom Hughes --- This is already fixed in 3.15.0 by the looks of it. *** This bug has been marked as a duplicate of bug 398870 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 415382] vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2 0x79 0x13 0x14 0x1A 0xC5 0xF9 0x6E 0xE9
https://bugs.kde.org/show_bug.cgi?id=415382 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #2 from Tom Hughes --- I believe this is vcvtph2ps (opcode 0x0f 0x38 0x13 with 0x66 prefix). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408217] Switching profile does not execute the custom command
https://bugs.kde.org/show_bug.cgi?id=408217 --- Comment #11 from Darin McBride --- I can confirm the old behaviour has been restored - if you're on a distro that's not carrying KDE apps 19.08.3+ (maybe earlier), then you'll have to wait until the distro makes available the upgrade. (Which is why these regressions are so painful - it can take a long time for some distros, especially the LTS releases, to get the fixes.) However, I thank the developers for fixing it. It's really appreciated and helpful. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415417] New: Task won't activate until raise animation completes, if hidden
https://bugs.kde.org/show_bug.cgi?id=415417 Bug ID: 415417 Summary: Task won't activate until raise animation completes, if hidden Product: lattedock Version: git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: k...@lasath.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Assign global shortcut to Activate Entry 1 2. Set dock to auto-hide, or ensure that it's hidden in some way 3. Press the shortcut OBSERVED RESULT A (half second or so) delay between keypress and task activating. The dock has to rise first. EXPECTED RESULT The task activates as soon as the shortcut is triggered. SOFTWARE/OS VERSIONS All of them, I think ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401272] Plasmashell freezes randomly
https://bugs.kde.org/show_bug.cgi?id=401272 --- Comment #9 from stefan.schwar...@gmx.net --- Created attachment 124631 --> https://bugs.kde.org/attachment.cgi?id=124631=edit stack trace of plasmashell (panel with display frozen) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 415416] New: CPU was maxed and the computer was running hot
https://bugs.kde.org/show_bug.cgi?id=415416 Bug ID: 415416 Summary: CPU was maxed and the computer was running hot Product: frameworks-baloo Version: 5.64.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: barry.furni...@gmail.com Target Milestone: --- Application: baloo_file (5.64.0) Qt Version: 5.12.5 Frameworks Version: 5.64.0 Operating System: Linux 5.3.15-300.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: The CPU was maxed out on my laptop and the fan was running high. The computer was hot. Nothing else was running on the laptop. The laptop was locked up, so I powered it off. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f27d1d7d800 (LWP 2153))] Thread 3 (Thread 0x7ee7b700 (LWP 3346)): [KCrash Handler] #6 0x7f27d5491625 in raise () from /lib64/libc.so.6 #7 0x7f27d547a8d9 in abort () from /lib64/libc.so.6 #8 0x7f27d44e0db3 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x7f27d44d59c5 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x7f27d44d6c56 in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x7f27d44d6e93 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x7f27d44d8aec in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0 #13 0x7f27d44dbbfd in mdb_cursor_put () from /lib64/liblmdb.so.0.0.0 #14 0x7f27d44dea9b in mdb_put () from /lib64/liblmdb.so.0.0.0 #15 0x7f27d5f9ef6d in Baloo::DocumentTimeDB::put(unsigned long long, Baloo::DocumentTimeDB::TimeInfo const&) () from /lib64/libKF5BalooEngine.so.5 #16 0x7f27d5fc4f93 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags) () from /lib64/libKF5BalooEngine.so.5 #17 0x7f27d5fb8246 in Baloo::Transaction::replaceDocument(Baloo::Document const&, QFlags) () from /lib64/libKF5BalooEngine.so.5 #18 0x56488749745c in Baloo::UnindexedFileIndexer::run() () #19 0x7f27d5a1eacb in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #20 0x7f27d5a1b4f6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #21 0x7f27d45474e2 in start_thread () from /lib64/libpthread.so.0 #22 0x7f27d5556693 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f27c4d97700 (LWP 2164)): #0 0x7f27d554ba6f in poll () from /lib64/libc.so.6 #1 0x7f27d3dd079e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f27d3dd08d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f27d5c17da3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f27d5bc1cfb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f27d5a1a3a5 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f27d5febf4a in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f27d5a1b4f6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f27d45474e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f27d5556693 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f27d1d7d800 (LWP 2153)): #0 0x7f27d554ba6f in poll () from /lib64/libc.so.6 #1 0x7f27d3dd079e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f27d3dd08d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f27d5c17da3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f27d5bc1cfb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f27d5bc9a26 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #6 0x564887485009 in main () [Inferior 1 (process 2153) detached] Possible duplicates by query: bug 412847, bug 410494, bug 410134. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 415415] Renaming tag groups can produce tags with id=0
https://bugs.kde.org/show_bug.cgi?id=415415 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Johannes Zarl-Zierl --- The root cause for this bug was fixed by commit 059b6934: https://cgit.kde.org/kphotoalbum.git/commit/?id=059b6934fad3876ae8b2d1cfd8fc25e72698a584 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 415415] Renaming tag groups can produce tags with id=0
https://bugs.kde.org/show_bug.cgi?id=415415 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||059b6934 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 415415] New: Renaming tag groups can produce tags with id=0
https://bugs.kde.org/show_bug.cgi?id=415415 Bug ID: 415415 Summary: Renaming tag groups can produce tags with id=0 Product: kphotoalbum Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: XML backend Assignee: kpab...@willden.org Reporter: johan...@zarl-zierl.at Target Milestone: --- SUMMARY Renaming tag groups can produce tags with id=0, which is a problem not just because most code assumes that id != 0, but because it can lead to losing tag data. Especially, if more than one tag gets assigned the id=0 due to this bug, an automatic recovery is not possible. STEPS TO REPRODUCE 1. Create a new tag group under under an existing tag group. For example, with the demo database, create a tag group named "dk" under Places->Denmark. 2. Rename said tag group. 3. Save. The new group will have ID 0, accompanied by this message: kphotoalbum.XMLDB: Member "dk1" in group "Places" -> "Denmark" has no id! Note that renaming an existing tag group, or creating one at top level (e. g. under Places) does not trigger this. The bug was at least present since mid 2017. Note: - Thanks to Robert Krawitz for discovering bug and fixing the cause of it! - This bug report was created after the fact for documentation purposes. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415319] Appimage version Run Issue
https://bugs.kde.org/show_bug.cgi?id=415319 --- Comment #2 from Lani Rani --- Wow~ Yes! rm -r kdenlive-appimagerc and Okay, run. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401272] Plasmashell freezes randomly
https://bugs.kde.org/show_bug.cgi?id=401272 --- Comment #8 from Rex Dieter --- Do, gdb "bt thread apply all" next time, to get all threads, not just the first one -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 415387] Application icon is not installed
https://bugs.kde.org/show_bug.cgi?id=415387 Alexander Potashev changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kti ||metracker/4c4027d6bcc6050f1 ||9e96d6322bf5fed357ca3a6 --- Comment #2 from Alexander Potashev --- Git commit 4c4027d6bcc6050f19e96d6322bf5fed357ca3a6 by Alexander Potashev. Committed on 20/12/2019 at 23:22. Pushed by aspotashev into branch 'master'. Install application icon M +14 -0icons/CMakeLists.txt https://commits.kde.org/ktimetracker/4c4027d6bcc6050f19e96d6322bf5fed357ca3a6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401272] Plasmashell freezes randomly
https://bugs.kde.org/show_bug.cgi?id=401272 stefan.schwar...@gmx.net changed: What|Removed |Added CC||stefan.schwar...@gmx.net --- Comment #7 from stefan.schwar...@gmx.net --- I may have the same or a similar issue (debian-testing, plasma 5.14.5, Intel graphics, nvidia blacklisted) which appeared at the same time as an update about a month ago which also broke kwin_x11. The panel display only freezes at random points while e.g. I can still click on its components and get a reaction. However, of course, state changes are not reflected in the panel any longer as the display remains frozen. I have never observed it unfreeze, even after hours. Kill/restart will get things back to normal. I can attach gdb and get a stack trace - maybe it helps: Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f56fcb96d0f in __GI___poll (fds=0x55ad02e099b0, nfds=14, timeout=27846) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. (gdb) where #0 0x7f56fcb96d0f in __GI___poll (fds=0x55ad02e099b0, nfds=14, timeout=27846) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f56fb08109e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f56fb0811bf in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f56fd1127f1 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f56fd0bb71b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f56fd0c31c2 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x55acf72f9235 in () #7 0x7f56fcacdbbb in __libc_start_main (main= 0x55acf72f8720, argc=1, argv=0x7ffcbdd75548, init=, fini=, rtld_fini=, stack_end=0x7ffcbdd75538) at ../csu/libc-start.c:308 #8 0x55acf72f96ba in _start () (gdb) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408217] Switching profile does not execute the custom command
https://bugs.kde.org/show_bug.cgi?id=408217 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415414] New: KWrite asks twice to cancel closing file deleted by another program
https://bugs.kde.org/show_bug.cgi?id=415414 Bug ID: 415414 Summary: KWrite asks twice to cancel closing file deleted by another program Product: kate Version: 19.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: groszdaniel...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open a file in KWrite. 2. Modify it, without saving. 3. Delete the file on the disk. 4. Switch back to KWrite. It warns you that the file was deleted by another program, with the options "Close File", "Save As" and "Ignore". 5. Click "Close File". 6. In the dialog "Do you want to save your changes or discard them?", click "Cancel". OBSERVED RESULT The same "Do you want to save your changes or discard them?" dialog pops up again, and you have to click Cancel a second time. Then it doesn't happen again. EXPECTED RESULT It gets the message the first time. SOFTWARE/OS VERSIONS OS: openSUSE Tubleweed 20191216 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396151] Edit option disappeared from the context menu/regression (?)
https://bugs.kde.org/show_bug.cgi?id=396151 stefan.schwar...@gmx.net changed: What|Removed |Added Version|5.7.3 |5.12.3 --- Comment #3 from stefan.schwar...@gmx.net --- It seems somebody heard our prayers. In kontact 5.12.3 my sore right mouse button brought back both an Edit As New feature in the context menu. I could also right click on the message header to copy email adresses and such Thanks a lot - this is greatly appreciated! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411131] kmail crashed when scrolling in the viewer window
https://bugs.kde.org/show_bug.cgi?id=411131 stefan.schwar...@gmx.net changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from stefan.schwar...@gmx.net --- cannot be reproduced any more in kontact 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 388726] kmail crashes for addresses containing unusual characters
https://bugs.kde.org/show_bug.cgi?id=388726 --- Comment #5 from stefan.schwar...@gmx.net --- sorry, the last comment is incomplete: I meant to say that the behavior concerning umlauts is still observable in kontact 5.12.3 (framework 5.62.0, Qt 5.12.5), though it does not crash kmail any longer. Entering, e.g. 'Schön', followed by ENTER, in the To: address field, of an otherwise empty message causes the editor to place an apparently random number of additional addresses from some internal resource (recent addresses? ..) in To: fields. My suspicion is that this has something to do with utf-8 representation of the addressee name not being compatible with some internal calculation (string length, whatever?). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415413] New: Appimage version crash selecting "Download New Render Profile..."
https://bugs.kde.org/show_bug.cgi?id=415413 Bug ID: 415413 Summary: Appimage version crash selecting "Download New Render Profile..." Product: kdenlive Version: Appimage - Refactoring Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: d...@live.it Target Milestone: --- SUMMARY Appimage version crash selecting "Download New Render Profile..." STEPS TO REPRODUCE 1. Open "render" window. 2. Choose "Render project" tab. 3. Click on "Download New Render Profile...". OBSERVED RESULT Kdenlive close itself. EXPECTED RESULT SOFTWARE/OS VERSIONS On MX-Linux 19_x64 patito feo (Linux (x86_64) release 4.19.0-6-amd64) ADDITIONAL INFORMATION "Launch bug report wizard" button dont't work. Clicking on button nothing happen. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 415382] vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2 0x79 0x13 0x14 0x1A 0xC5 0xF9 0x6E 0xE9
https://bugs.kde.org/show_bug.cgi?id=415382 --- Comment #1 from Nathan Mills --- I forgot to mention I'm using VcXsrv 1.20.5.1 in "One large window" mode as the X server. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415411] No support for check forms with split protocol
https://bugs.kde.org/show_bug.cgi?id=415411 --- Comment #4 from Ralf Habacker --- Git commit 3ed3238d0cbd5f1cf8f51e8adfd4c779448c5585 by Ralf Habacker. Committed on 20/12/2019 at 22:08. Pushed by habacker into branch '4.8'. printcheck plugin: Always replace $MEMO1|2 to avoid being replaced by the value of $MEMO. M +2-4kmymoney/plugins/printcheck/printcheck.cpp https://commits.kde.org/kmymoney/3ed3238d0cbd5f1cf8f51e8adfd4c779448c5585 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 388726] kmail crashes for addresses containing unusual characters
https://bugs.kde.org/show_bug.cgi?id=388726 --- Comment #4 from stefan.schwar...@gmx.net --- still the same state in 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 406530] Elisa-git music playback stutters
https://bugs.kde.org/show_bug.cgi?id=406530 --- Comment #4 from Matthieu Gallien --- (In reply to Öyvind Saether from comment #3) > elisa-git will stutter on playback if it is compiled with the VLC backend > and a networked Pulseaudio setup is used. It can be worked around > compile-time by simply not having libblc installed - which makes Elisa "fall > back" to QtMultimedia - which seems to work just fine. > > VLC has the exact same problem if it's playing to a local PulseAudio > instance which has a remote sink on another machine as output. It's 100% > reproducible in both elisa (when compiled with libvlc) and VLC. > > This bug can simply be closed if Rainer Finke is using a similar setup and > Elisa is/was compiled against libvlc. Thanks a lot for the information. Did you already reported it to VLC project ? -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 415387] Application icon is not installed
https://bugs.kde.org/show_bug.cgi?id=415387 --- Comment #1 from Alexander Potashev --- Thanks! Will skip 5.0.0 and publish 5.0.1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413431] Clicking on notification's close button triggers the default action in addition to closing it
https://bugs.kde.org/show_bug.cgi?id=413431 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Kai Uwe Broulik --- https://cgit.kde.org/plasma-workspace.git/commit/?id=5d6aa75daf9977b1883ec760bccb9ee35420d477 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 406530] Elisa-git music playback stutters
https://bugs.kde.org/show_bug.cgi?id=406530 Öyvind Saether changed: What|Removed |Added CC||oyvi...@everdot.org --- Comment #3 from Öyvind Saether --- elisa-git will stutter on playback if it is compiled with the VLC backend and a networked Pulseaudio setup is used. It can be worked around compile-time by simply not having libblc installed - which makes Elisa "fall back" to QtMultimedia - which seems to work just fine. VLC has the exact same problem if it's playing to a local PulseAudio instance which has a remote sink on another machine as output. It's 100% reproducible in both elisa (when compiled with libvlc) and VLC. This bug can simply be closed if Rainer Finke is using a similar setup and Elisa is/was compiled against libvlc. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 415302] Cantor crashing (qalculate backend)
https://bugs.kde.org/show_bug.cgi?id=415302 Tim Richardson changed: What|Removed |Added CC||t...@tim-richardson.net -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408460] kdenlive-19.04.3-x86_64.appimage During rendering, internal paths are assumed to be relative to current working directory instead of project file location causing blank white
https://bugs.kde.org/show_bug.cgi?id=408460 Robert changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Robert --- I just tested this bug out again using the following steps and it appears to be fixed in version kdenlive-19.12.0a-x86_64.appimage: mkdir /tmp/test1 cd /tmp/test1 wget http://mirrors.ocf.berkeley.edu/kde-applicationdata/kdenlive/release/kdenlive-19.12.0a-x86_64.appimage md5sum -c <(echo "1d12febea853500fb1e0f1adeeea4f32 kdenlive-19.12.0a-x86_64.appimage") chmod u+x kdenlive-19.12.0a-x86_64.appimage mkdir project1 cd project1 wget "http://www.robertelder.ca/Screencast 2019-06-08 13:53:57.mp4" /tmp/test1/kdenlive-19.12.0a-x86_64.appimage # Now create a project, add the clip 'Screencast 2019-06-08 13:53:57.mp4' to timeline. Render to output file '/tmp/good.mp4'. # Save project as /tmp/test1/project1/proj.kdenlive # Exit program. # Check /tmp/test1/project1/proj.kdenlive and note that the project file uses relative paths for the video file (which is probably the right way to do it). cd /tmp/test1/ mkdir otherdir cd otherdir /tmp/test1/kdenlive-19.12.0a-x86_64.appimage /tmp/test1/project1/proj.kdenlive # Render project to output file '/tmp/bad.mp4'. md5sum /tmp/good.mp4 /tmp/bad.mp4 # Result was this: #680621ef3f9a421cda66072bb7af3ca7 /tmp/good.mp4 #680621ef3f9a421cda66072bb7af3ca7 /tmp/bad.mp4 Both files work correctly and no blank white output is observed. Bug appears to be fixed in kdenlive-19.12.0a-x86_64.appimage. Updating bug to resolved. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 415267] Completely disfunctional dialog in 19.12
https://bugs.kde.org/show_bug.cgi?id=415267 Nate Graham changed: What|Removed |Added CC||n...@kde.org Severity|normal |critical Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 410174] kdenlive-19.04.3-x86_64.appimage Speed Effect is broken
https://bugs.kde.org/show_bug.cgi?id=410174 Robert changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Robert --- I just tested this bug out again using the following steps and it appears to be fixed in version kdenlive-19.12.0a-x86_64.appimage: mkdir /tmp/speed cd /tmp/speed wget http://mirrors.ocf.berkeley.edu/kde-applicationdata/kdenlive/release/kdenlive-19.12.0a-x86_64.appimage md5sum -c <(echo "1d12febea853500fb1e0f1adeeea4f32 kdenlive-19.12.0a-x86_64.appimage") chmod u+x kdenlive-19.12.0a-x86_64.appimage wget "http://www.robertelder.ca/Screencast 2019-06-08 13:53:57.mp4" /tmp/speed/kdenlive-19.12.0a-x86_64.appimage # Now add the clip 'Screencast 2019-06-08 13:53:57.mp4' to timeline. Right-click on clip and select change speed. Change speed to 200 using right-click method. Then render project to /tmp/speed/untitled.mp4 Also tested with re-naming the clip to ren:der.mp4 and adding that to the project. Renders just fine in both cases. I now consider this bug fixed since I no longer see any issues with my test case. I am going to go ahead and mark this bug as resolved (let me know if you'd rather update the bug statuses yourselves). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415327] endless loop during file dialodue
https://bugs.kde.org/show_bug.cgi?id=415327 --- Comment #2 from Manfred --- Am 20.12.19 um 18:17 schrieb emohr: > https://bugs.kde.org/show_bug.cgi?id=415327 > > emohr changed: > > What|Removed |Added > >Flags||timeline_corruption+ > CC||fritzib...@gmx.net > > --- Comment #1 from emohr --- > Thank you for reporting. > Please try with the current Kdenlive AppImage version 19.12.0a to see if there > are any packaging issues https://files.kde.org/kdenlive/release/ > > If the problem/issue doesn't occur when using the AppImage, then it's your > configuration or packaging. > The problem does not occur with the AppImage file. Removing kdenlive and reinstalling it on Lubuntu was no fix. There was an error message of GTK complaining on a missing parent for the dialogue. I will further on use the proposed Kdenlive AppImage version 19.12.0. Thank you -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 415302] Cantor crashing (qalculate backend)
https://bugs.kde.org/show_bug.cgi?id=415302 --- Comment #1 from Nikita Sirgienko --- I have reproduced crash only with Qalculate. Octave, Maxima and others works as expected. Could you please add crashlog with Octave backend for example? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 --- Comment #4 from Roger Larsson --- Created attachment 124629 --> https://bugs.kde.org/attachment.cgi?id=124629=edit zypp log Not seen the problem (nor rebooted since 2019-11-13 update), together with replacing CPU (disks are the same, still no external GPU) something (HW or SW) has fixed the issue! Old CPU: Intel Core i5-2500K RAM: 2*16GB + 2*8GB = 24GB DDR3 MB: ASUS P8H67-M New CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz RAM: 4*16G = 32GB DDR3 MB: ASUS H97M-PLUS Do not remember if the Power unit got replaced too, probably. Inherited the components from my children... -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 408370] Applet stuck in connecting status even though connected
https://bugs.kde.org/show_bug.cgi?id=408370 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409392] NetworkManager widget freezes on connection issues blocking all Plasma
https://bugs.kde.org/show_bug.cgi?id=409392 Alexander Potashev changed: What|Removed |Added CC||kdeb...@fratti.ch -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409400] The list of networks gets updated while the cursor is over it
https://bugs.kde.org/show_bug.cgi?id=409400 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409392] NetworkManager widget freezes on connection issues blocking all Plasma
https://bugs.kde.org/show_bug.cgi?id=409392 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com --- Comment #2 from Alexander Potashev --- *** Bug 410859 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410859] plasmashell hangs for multiple seconds while nmcli is also slow to respond
https://bugs.kde.org/show_bug.cgi?id=410859 Alexander Potashev changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Alexander Potashev --- *** This bug has been marked as a duplicate of bug 409392 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 415412] New: ActionToolbar "more" menu visible when empty
https://bugs.kde.org/show_bug.cgi?id=415412 Bug ID: 415412 Summary: ActionToolbar "more" menu visible when empty Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: nicolas.fe...@gmx.de Target Milestone: Not decided Created attachment 124628 --> https://bugs.kde.org/attachment.cgi?id=124628=edit code example SUMMARY When I set 'visible: false' in one of the actions inside an ActionToolbar the action is correctly not displayed, but now the overflow menu is always visible although empty. See attached code example -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 --- Comment #38 from NSLW --- (In reply to przem.formela from comment #36) > > According to https://www.usertesting.com/blog/gestalt-principles/ > > "The human brain is wired to see structure, logic, and patterns. It helps us > > make sense of the world. In the 1920s a group of German psychologists > > developed theories around how people perceive the world around them, called > > Gestalt principles." > > I think we might be over-stretching scope of gestalt principles which are > > about structure, logic, and patterns. I'm not sure if Luigi meant that > > specifically or in general, so I think we might slightly went off-topic > > here. Nevertheless thank you for your explanation. > > [...] > > "The principle of similarity states that when things appear to be similar to > > each other, we group them together. And we also tend to think they have the > > same function." > Isn't this exactly the case, though? I'm not sure after reading "Examples of the similarity principle" on https://www.usertesting.com/blog/gestalt-principles/ Could you tell me why did you originally think that I ignored the rule of similarity? > On every other OS you can encounter > windows with up to three buttons: OK, Cancel, Apply. Person using Android, > Windows, Mac expects there to be these three buttons, named consistently > across all platforms. Because that's the pattern they know or, well, at > least I do. Further explanation in the next point. I get impression that you're using all those systems and have certain certain expectations and preferences to them. I used or worked in them as well. For me translation of word "cancel" wasn't the key to master those OS's. Nothing which I remembered from Windows has helped me to get around on MacOS. Waste bin on Android is not by default on my "desktop" and god knows how to add it there. Would you mind telling me why do you put such pressure on "cancel" being translated in the same way if Android, MacOS, and Windows have many basic quirks and features so different? For example, don't you want MacOS minimize/maximize/close buttons which are on the left side of window title bar to be on the right side like "in all other OS's" as well? > I know what both of these do. But I don't **read** button text, I **look** > at it. That's even one of principles of quick text reading, if I remember > correctly. > I'm not in a research mood to point to specific papers but I'm pretty sure > that's what people do most of the time, when interacting with UI elements as > well. > So, in this case, user doesn't read three buttons: "OK, Anuluj, Zastosuj". > They see "Button with OK, Button with A..j, button with Z...j". When we > switch from "Anuluj" to "Zaniechaj", we end up with two buttons having > "Z..j", thus disabling the ability to quickly estabilishing function of the > button with a glance and extending the time it takes to actually choose the > desired button. I'm not sure why have you replaced inside letters with dots. That conflicts with my need to see shape of a word or its upper/lower part to guess what's the word is. Is covering inside letters a method that allows you to read words faster? > > > The way you approach actual feedback given to you isn't community- > > > nor improvement-oriented. > > > > I presume that you don't see this change as making anything valuable to you. > > In our devel list I wrote: > > "My motivation is to promote the use of Polish language and enhance its > > quality > > in software." > > Don't you see it as improvement of Polish wording in software? > I'm sorry, but I really don't. "OK" is not a polish word. "Kontynuuj" isn't. > "Menu" isn't. I don't see a point in having well-known "Anuluj" replaced > with a word, which is "more Polish" by some standards I really don't > understand. You mention many outside words for which native replacements would be difficult to find. It's not difficult to find native replacement for "anuluj". It's why I think that word is redundant in our language and instead of helping Polish, it takes its distinctiveness. I looked at other languages in KDE to see if "OK" is spread only in Polish and found that it's spread all over the world :) There are some exceptions though: 1) In Ukrainian OK is translated as "Гаразд" which I believe means "dobrze" 2) In Spanish OK is translated as "Aceptar" 3) In Catalan OK is translated as "D'acord" which I believe means "zgoda" By that example, I would like you to see that even such popular and understandable word as OK has been replaced by local words. I think, that "D'acord" gives a special feeling that one uses Catalan. > I'm sorry, I didn't want to make you feel disrespected. It just seems to me > that in this case, Polish language and community might be at odds and your > work will benefit either of those, but not both. I find that paragraph well said. It makes me sad though because I expected that every Pole would like to have more
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 --- Comment #37 from NSLW --- (In reply to r.rozne from comment #34) > > You used Polish translation in KDE before the change to "Zaniechaj" and > > after the change > > you tried (struggled) to use it? > > No, I had never used KDE *in Polish* before the change occurred is what I > meant. I had only tried KDE in English before. OK, I get that you've switched to Polish after the change to "Zaniechaj". I'm curious what this word has to do with your switch. Was the word a trigger for you or was it by sheer accident? > I'm a person learned in both > linguistics and computers, so I didn't have any problems. But here's the > thing, I, like you, am a learned person. In my experience, the typical user > gets confused a *lot* when presented with different wording than they've > been seeing for years (Windows, Android, modern Apple platforms). I reckon you adapted fast to the change. Do you feel concerned about how fast other users may adapt considering that they're not as confident in computer skills as you? In my experience, every user gets confused with anything new, e.g. switch from Windows to Linux is confusing in itself. Some learned users, like you, may get it fast and some may get it slow. I think, actions that don't confuse user are bug-fixes. Any other change is considered confusing. That way there would be no space for improvement because no way for a change. > In this scenario, neither the expert, nor the user are even aware they're > running KDE. The user is agitated and puts pressure on the "so-called > expert" to solve their problem at all costs. The expert may assume things > because of that. I suggest we drop considering this example, because to me "cancel" button doesn't play key role in it and I believe it is rare. > Well, on paper it hasn't. However, some people don't know the formal > definition of "Anuluj". I don't have a real-life example for that, but I do > have one for the word "Edycja" (Edit). My grandmother was recently confused > by this word, because she was used to seeing it in a web app, where clicking > it opened a separate screen that showed more details about something than > could be seen normally, in addition to making them editable. So, she told, > she thought it means something like "show more details". Then, she > encountered it in a situation, where tapping the "Edytuj" button didn't show > more stuff, leaving her tapping over and over, looking for more stuff. > Encountering the same word in a different place, where the *apparent effect* > (to them) is different, may leave them confused. > Likewise, users may not associate "Anuluj" and "Zaniechaj" with the same > concept. Is Microsoft to blame for this? First, I don't want to blame anyone (or encourage such actions) for anything and in this particular case Microsoft for translating "cancel" as "anuluj". Second, You told us your grandmother case. It seems to me, she felt confused because she expected some consistency in the use of word "Edycja", right? Third, I have issues following your third thought after your first though. There seems to be no connection to me between them. When I read "associating [word] with concept" I see the word as being jargon because it has to be associated with a concept and I want to avoid using jargon words in translations. I see that you're concerned if the user will catch that "anuluj" and "zaniechaj" means the same concept. In English KDE there are "Settings" , "Configuration", "Options" that from function point of view mean the same to me, nevertheless three words are used. It seems to me that users adapted to it. > Given that the Start button hasn't been labeled since Vista, I think the > average user calls any button in the bottom-left corner of the screen a > "Start" button. Even then, there's the resort of "the button in the > bottom-left corner" (and if that fails, try the upper-left and the > upper-right - that can happen on Windows, too). Not so much with our > "Anuluj" button, given that different OS' put "OK" and "Anuluj" in different > order. You're right. Start button is no more. Someday the change must have happened though and I believe it was confusing. > > MacOS was translated since 1986. > Huh, that's the first time I've heard of this… Have you ever seen it? Where? > Only other trace I've found was an archived Allegro listing. I think I would > enjoy seeing it. The real machine? No. I've seen their dictionary from 1992. https://aresluna.org/attached/terminology/glossaries/mac > Try running a JavaScript that uses window.confirm(). > Or closing a window with multiple tabs open. > I'm not talking about Open/Save/Print dialogs here, they should and are > properly integrated. You're stating the fact that other software uses dominant Windows standard. > In this case, I would argue that the language isn't "changing", it "has > changed" already. 20 years of continuous usage is quite enough. Yes, it changed
[plasma-nm] [Bug 410859] plasmashell hangs for multiple seconds while nmcli is also slow to respond
https://bugs.kde.org/show_bug.cgi?id=410859 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #3 from Nicolas Frattaroli --- I can confirm this bug, the way I can reproduce it specifically is to use stubby as a local DNS resolver. 1. Install stubby and configure it 2. Set DNS resolver to 127.0.0.1 3. Switch from one wifi to the other 4. The entirety of plasmashell will now freeze as NetworkManager waits for a dns response to time out Note that restarting stubby unfreezes plasmashell and NetworkManager prematurely (i.e. before the timeout happens) The general problem here appears to be threefold, 1. plasmashell lets itself get blocked by applets, 2. plasma-nm lets itself get blocked by NetworkManager, 3. NetworkManager is not good. Ideally plasmashell would not freeze if a widget freezes, and even more ideally plasma-nm won't freeze if NetworkManager decides to pointlessly block. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415411] No support for check forms with split protocol
https://bugs.kde.org/show_bug.cgi?id=415411 --- Comment #3 from Ralf Habacker --- Git commit 8674a3c6471b6c5427910b6773273dcb1490c0f6 by Ralf Habacker. Committed on 20/12/2019 at 19:23. Pushed by habacker into branch '4.8'. print check plugin: Add supported fields to check_all_fields.html template M +12 -0kmymoney/plugins/printcheck/check_all_fields.html https://commits.kde.org/kmymoney/8674a3c6471b6c5427910b6773273dcb1490c0f6 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415411] No support for check forms with split protocol
https://bugs.kde.org/show_bug.cgi?id=415411 --- Comment #1 from Ralf Habacker --- Git commit 9ae5d7c17654dc57b396571ddd630305674ff3a2 by Ralf Habacker. Committed on 20/12/2019 at 19:22. Pushed by habacker into branch '4.8'. printcheck: avoid incorrect replacement of split values Template parameters for split values are now replaced in descending order. If we replace the template parameter 'SPLITVALUE1' before 'SPLITVALUE10', the latter is erroneously overwritten with the value from the former, followed by '0'. M +2-2kmymoney/plugins/printcheck/printcheck.cpp https://commits.kde.org/kmymoney/9ae5d7c17654dc57b396571ddd630305674ff3a2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415411] No support for check forms with split protocol
https://bugs.kde.org/show_bug.cgi?id=415411 Ralf Habacker changed: What|Removed |Added Version Fixed In|4.8.5 |4.8.5,5.0.7 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415188] No support for printing sepa bank transfer forms
https://bugs.kde.org/show_bug.cgi?id=415188 --- Comment #4 from Ralf Habacker --- Git commit 3c7c1bcdaf6e462a5d29f06e0f8df8d1eba06193 by Ralf Habacker. Committed on 20/12/2019 at 19:18. Pushed by habacker into branch '4.8'. printcheck plugin: In check_all_fields.html show template variables with leading '$' M +27 -27 kmymoney/plugins/printcheck/check_all_fields.html https://commits.kde.org/kmymoney/3c7c1bcdaf6e462a5d29f06e0f8df8d1eba06193 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415411] No support for check forms with split protocol
https://bugs.kde.org/show_bug.cgi?id=415411 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kmy ||money/d12a2e01a35a44e584fae ||3e3ef1dd545af74d34a Version Fixed In||4.8.5 --- Comment #2 from Ralf Habacker --- Git commit d12a2e01a35a44e584fae3e3ef1dd545af74d34a by Ralf Habacker, on behalf of Phil Hopkins. Committed on 20/12/2019 at 19:21. Pushed by habacker into branch '4.8'. Adding additional variable to check printing When using check forms that contain a log for record keeping it is needed to print out all of the splits associated with a transaction when printing a check. This cannot be done since the split variables are not present in the check printing plugin. This patch will add the variables SplitAccountName and SplitValue for up to 10 splits within a transaction. The check template will then be able to access the split variables and print them when printing a check. Differential Revision: https://phabricator.kde.org/D23369 FIXED-IN:4.8.5,5.0.7 M +18 -0kmymoney/plugins/printcheck/printcheck.cpp https://commits.kde.org/kmymoney/d12a2e01a35a44e584fae3e3ef1dd545af74d34a --- Comment #1 from Ralf Habacker --- Git commit 9ae5d7c17654dc57b396571ddd630305674ff3a2 by Ralf Habacker. Committed on 20/12/2019 at 19:22. Pushed by habacker into branch '4.8'. printcheck: avoid incorrect replacement of split values Template parameters for split values are now replaced in descending order. If we replace the template parameter 'SPLITVALUE1' before 'SPLITVALUE10', the latter is erroneously overwritten with the value from the former, followed by '0'. M +2-2kmymoney/plugins/printcheck/printcheck.cpp https://commits.kde.org/kmymoney/9ae5d7c17654dc57b396571ddd630305674ff3a2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415188] No support for printing sepa bank transfer forms
https://bugs.kde.org/show_bug.cgi?id=415188 --- Comment #5 from Ralf Habacker --- Git commit 27d54970e572f90e423e7a0fd640d7701033947b by Ralf Habacker. Committed on 20/12/2019 at 19:19. Pushed by habacker into branch '4.8'. printcheck plugin: Support for printing individual lines from the transaction note This supports additional template fields $MEMO1 and $MEMO2, which use the first and second line from the memo field. M +2-0kmymoney/plugins/printcheck/check_all_fields.html M +7-1kmymoney/plugins/printcheck/printcheck.cpp M +4-3kmymoney/plugins/printcheck/sepa.html https://commits.kde.org/kmymoney/27d54970e572f90e423e7a0fd640d7701033947b --- Comment #4 from Ralf Habacker --- Git commit 3c7c1bcdaf6e462a5d29f06e0f8df8d1eba06193 by Ralf Habacker. Committed on 20/12/2019 at 19:18. Pushed by habacker into branch '4.8'. printcheck plugin: In check_all_fields.html show template variables with leading '$' M +27 -27 kmymoney/plugins/printcheck/check_all_fields.html https://commits.kde.org/kmymoney/3c7c1bcdaf6e462a5d29f06e0f8df8d1eba06193 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415402] QIF Import - unclear guidance produces unusable file
https://bugs.kde.org/show_bug.cgi?id=415402 --- Comment #2 from Jack --- Also, if you have any particular suggestions for improving the manual, you can post them to the forum or mailing list. I am aware that when experienced users write instructions, we often miss things that can cause a problem for a new user. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415411] New: No support for check forms with split protocol
https://bugs.kde.org/show_bug.cgi?id=415411 Bug ID: 415411 Summary: No support for check forms with split protocol Product: kmymoney Version: 4.8.4 Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: exporter Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- Phil Hopkins wrote: When using check forms that contain a log for record keeping it is needed to print out all of the splits associated with a transaction when printing a check. This cannot be done since the split variables are not present in the check printing plugin. STEPS TO REPRODUCE 1. inspect https://cgit.kde.org/kmymoney.git/tree/kmymoney/plugins/checkprinting/checkprinting.cpp?h=5.0=5f5848ba2b3a2148aa402fe87d8c41ba1ebdb329#n172 OBSERVED RESULT There are not template attributes for the mentioned split attributes EXPECTED RESULT The mentioned split attributes should be replaces ADDITIONAL INFORMATION It would be nice to have a template showing all available fields. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 415270] Ark can't handle rar archives that contain files with square brackets (that is, "[" and "]") in the name
https://bugs.kde.org/show_bug.cgi?id=415270 --- Comment #1 from loca...@tutanota.com --- It's disappointing that Ark has not not been fully functional for the last ten years or so. The last time it was working correctly for me was in KDE 3.5, after that it was mostly broken. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415402] QIF Import - unclear guidance produces unusable file
https://bugs.kde.org/show_bug.cgi?id=415402 Thomas Baumgart changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Thomas Baumgart --- Please don't use the bug tracker for user questions and a single entry for multiple questions. Your questions are better suited for the forum (https://forum.kde.org/viewforum.php?f=69) or mailing list (https://mail.kde.org/mailman/listinfo/kmymoney). Did you consult the manual regarding QIF import at https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.impexp.qifimp.html I leave this entry open to keep it as a wish list item to improve the QIF import in a future version. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 412327] Plugin library 'kde_grantlee_plugin' not found
https://bugs.kde.org/show_bug.cgi?id=412327 --- Comment #10 from Thomas McNicholas --- (In reply to Antonio Rojas from comment #9) > The ArchLinux issue was a packaging problem which has nothing to do with > this. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 412327] Plugin library 'kde_grantlee_plugin' not found
https://bugs.kde.org/show_bug.cgi?id=412327 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Platform|unspecified |Neon Packages --- Comment #9 from Antonio Rojas --- The ArchLinux issue was a packaging problem which has nothing to do with this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414672] Crash in uninitialized transform tool
https://bugs.kde.org/show_bug.cgi?id=414672 Tymond changed: What|Removed |Added CC||pedroreis...@protonmail.com --- Comment #14 from Tymond --- *** Bug 415388 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415388] Crash on Resize, then cancel
https://bugs.kde.org/show_bug.cgi?id=415388 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Tymond --- *** This bug has been marked as a duplicate of bug 414672 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 415410] New: bad display of string values containing Unicode supplemental characters
https://bugs.kde.org/show_bug.cgi?id=415410
Bug ID: 415410
Summary: bad display of string values containing Unicode
supplemental characters
Product: kdevelop
Version: 5.4.2
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: CPP Debugger
Assignee: kdevelop-bugs-n...@kde.org
Reporter: andy.henin...@gmail.com
CC: niko.s...@gmail.com
Target Milestone: ---
SUMMARY
The C++ debugger display of string values is garbled when the string contains
Unicode supplemental characters, that is, character code points > 64k
STEPS TO REPRODUCE
1. Debug the following test program. The emoji is Unicode U+1F60E.
=
#include
int main() {
const char *cs8 {"Hello, Worldβ.\n"};
const char16_t *cs16 {u"Hello, Worldβ.\n"};
const char32_t *cs32 {U"Hello, Worldβ.\n"};
std::cout << cs8 << std::endl;
}
==
2. Put a break point on the std::cout line.
3. Examine the local variables in the variables debug window
OBSERVED RESULT
cs8 0x4d9ca0 "Hello, Worldβ�\237\230\216.\n"
cs16 0x4d9ce0 u"Hello, Worldβ�\237\230\216.\n"
cs32 0x4d9d40 U"Hello, Worldβ�\237\230\216.\n"
EXPECTED RESULT
cs8 0x4d9ca0 "Hello, Worldβ.\n"
cs16 0x4d9ce0 u"Hello, Worldβ.\n"
cs32 0x4d9d40 U"Hello, Worldβ.\n"
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 19.10
(available in About System)
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4
ADDITIONAL INFORMATION
Raw gdb, run from the command line, works correctly.
(gdb) b 8
Breakpoint 1 at 0x11d6: file suppl.cpp, line 8.
(gdb) r
Starting program: /home/andy/icprogs/a.out
Breakpoint 1, main () at suppl.cpp:8
8 std::cout << cs8 << std::endl;
(gdb) p cs8
$1 = 0x6009 "Hello, Worldβ.\n"
(gdb) p cs16
$2 = 0x6020 u"Hello, Worldβ.\n"
(gdb) p cs32
$3 = 0x6048 U"Hello, Worldβ.\n"
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 415409] False detection of a matching investment cash dividend transaction
https://bugs.kde.org/show_bug.cgi?id=415409 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/c17568b8c82b59ad72b07 |money/6ed6175828ac1b027d112 |d2db4ab7181757b4bfe |0eb7fabd3e1d239e5c9 --- Comment #2 from Thomas Baumgart --- Git commit 6ed6175828ac1b027d1120eb7fabd3e1d239e5c9 by Thomas Baumgart. Committed on 20/12/2019 at 18:00. Pushed by tbaumgart into branch 'master'. Assign bankid to correct split The bankid used to detect duplicate transactions was assigned to the wrong split (the one that identifies the category). This change places the bankid in the split that references the investment account. FIXED-IN: 5.0.8 (cherry picked from commit c17568b8c82b59ad72b07d2db4ab7181757b4bfe) M +22 -20 kmymoney/converter/mymoneystatementreader.cpp https://commits.kde.org/kmymoney/6ed6175828ac1b027d1120eb7fabd3e1d239e5c9 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415409] False detection of a matching investment cash dividend transaction
https://bugs.kde.org/show_bug.cgi?id=415409 Thomas Baumgart changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/c17568b8c82b59ad72b07 ||d2db4ab7181757b4bfe Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.0.8 --- Comment #1 from Thomas Baumgart --- Git commit c17568b8c82b59ad72b07d2db4ab7181757b4bfe by Thomas Baumgart. Committed on 20/12/2019 at 17:59. Pushed by tbaumgart into branch '5.0'. Assign bankid to correct split The bankid used to detect duplicate transactions was assigned to the wrong split (the one that identifies the category). This change places the bankid in the split that references the investment account. FIXED-IN: 5.0.8 M +22 -20 kmymoney/converter/mymoneystatementreader.cpp https://commits.kde.org/kmymoney/c17568b8c82b59ad72b07d2db4ab7181757b4bfe -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415409] New: False detection of a matching investment cash dividend transaction
https://bugs.kde.org/show_bug.cgi?id=415409 Bug ID: 415409 Summary: False detection of a matching investment cash dividend transaction Product: kmymoney Version: 5.0.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: onlinebanking Assignee: kmymoney-de...@kde.org Reporter: tbaumg...@kde.org Target Milestone: --- SUMMARY Importing two cash dividend transactions that reference different investment accounts but have the same amount are treated as the same transaction and matched. STEPS TO REPRODUCE 1. Import an OFX cash dividend transaction into the corresponding account 2. Import an OFX cash dividend transaction with the same amount into a different account OBSERVED RESULT Second transaction is matched with the first EXPECTED RESULT Two transactions in different accounts are shown -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"
https://bugs.kde.org/show_bug.cgi?id=414631 Julian changed: What|Removed |Added Attachment #124627|Crash report / backtrace on |Crash report / backtrace on description|KDE Neon Developer Edition |KDE Neon Developer Edition |incl debug symbols for | |libQt5Core | --- Comment #6 from Julian --- Comment on attachment 124627 --> https://bugs.kde.org/attachment.cgi?id=124627 Crash report / backtrace on KDE Neon Developer Edition incl debug symbols for libQt5Core Gvenview version: 20.03.70 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414076] emacs (GUI) does not start (Undefined color: "WINDOW_FOREGROUND")
https://bugs.kde.org/show_bug.cgi?id=414076 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Nate Graham --- Thanks, looks like this is not a Breeze GTK bug then. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"
https://bugs.kde.org/show_bug.cgi?id=414631 Julian changed: What|Removed |Added Attachment #124626|0 |1 is obsolete|| --- Comment #5 from Julian --- Created attachment 124627 --> https://bugs.kde.org/attachment.cgi?id=124627=edit Crash report / backtrace on KDE Neon Developer Edition incl debug symbols for libQt5Core -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415214] Error bar stretch too much in a log plot.
https://bugs.kde.org/show_bug.cgi?id=415214 Alexander Semke changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
