[digikam] [Bug 420430] Inconsistent behavior of View tab of Metadata dialog in digiKam Configure menu
https://bugs.kde.org/show_bug.cgi?id=420430 Maik Qualmann changed: What|Removed |Added Ever confirmed|0 |1 Version|5.9.0 |7.0.0 CC||metzping...@gmail.com Status|REPORTED|CONFIRMED --- Comment #2 from Maik Qualmann --- I can confirm it here for digiKam-7.0.0-Beta3, depending on the image some hexadecimal metadata are also displayed. I think Exiv2 also maps this metadata, I haven't looked at the code yet. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 341573] kcm-touchpad can`t reset defaults
https://bugs.kde.org/show_bug.cgi?id=341573 nyanpasu64 changed: What|Removed |Added CC||nyanpas...@tuta.io --- Comment #1 from nyanpasu64 --- The "Defaults" button is not enabled when you change any of the widgets... Except changing any option in the final tab "Enable/Disable Touchpad" will enable the "Defaults" button. And if you press that button, all tabs are reset, not just the final tab. Operating System: openSUSE Tumbleweed 20200421 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 Kernel Version: 5.6.4-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 7.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420442] New: Pressing Alt+Tab with no open windows, while window is loading, makes everything disappear
https://bugs.kde.org/show_bug.cgi?id=420442 Bug ID: 420442 Summary: Pressing Alt+Tab with no open windows, while window is loading, makes everything disappear Product: kwin Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: nyanpas...@tuta.io Target Milestone: --- SUMMARY If you press Alt+Tab when no windows are open, and release it after a window opens, all windows and panels disappear. STEPS TO REPRODUCE 1. Launch Firefox. For me, it takes about a second before the window appears. 2. Immediately press Alt+Tab and hold Alt. The window switcher will say "Show Desktop". 3. Once Firefox loads, the window switcher will say "Mozilla Firefox". Release Alt. OBSERVED RESULT Everything but the wallpaper and cursor disappears. If you open another Firefox window using Ctrl+N, it's also invisible. Windows can be interacted with, using keyboard or mouse. EXPECTED RESULT Windows don't become all invisible. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200421 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 Kernel Version: 5.6.4-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 7.6 GiB of RAM ADDITIONAL INFORMATION I think this occurs in both X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420226] Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 416843] The Book Picture I Added Is Not Displayed
https://bugs.kde.org/show_bug.cgi?id=416843 --- 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.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409308] Lag when play this mp4, timeline cursor delay, cannot show background in Titler
https://bugs.kde.org/show_bug.cgi?id=409308 --- 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.
[frameworks-baloo] [Bug 419819] Baloo ranks relevance of results undesirably
https://bugs.kde.org/show_bug.cgi?id=419819 --- 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.
[kmines] [Bug 419839] configuration impossible
https://bugs.kde.org/show_bug.cgi?id=419839 --- 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.
[digikam] [Bug 417737] File operations locked under Windows
https://bugs.kde.org/show_bug.cgi?id=417737 --- Comment #8 from Maik Qualmann --- Git commit 977fee83cf0da275c708908f3ebef5a7cd848f5f by Maik Qualmann. Committed on 23/04/2020 at 04:30. Pushed by mqualmann into branch 'master'. replace QFileSystemWatcher in the LoadingCache interface M +2-2core/libs/database/utils/scan/scancontroller_p.h M +0-5core/libs/fileactionmanager/fileworkeriface.cpp M +43 -116 core/libs/threadimageio/fileio/loadingcache.cpp M +8-47 core/libs/threadimageio/fileio/loadingcache.h M +0-8core/libs/threadimageio/fileio/loadingcacheinterface.cpp M +0-5core/libs/threadimageio/fileio/loadingcacheinterface.h https://invent.kde.org/kde/digikam/commit/977fee83cf0da275c708908f3ebef5a7cd848f5f -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 420441] New: org.kde.kcm1.2 : QML module does not contain information about components contained in plugins.
https://bugs.kde.org/show_bug.cgi?id=420441
Bug ID: 420441
Summary: org.kde.kcm1.2 : QML module does not contain
information about components contained in plugins.
Product: frameworks-kcmutils
Version: 5.69.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: 319513...@outlook.com
Target Milestone: ---
SUMMARY
kde setting -> locale setting -> language -> add language can't work.
When I try add new language from "language", it had nothing happend.
I use "journalctl -xb" found some error :
4月 23 11:14:50 dragon systemsettings5[14280]:
QQmlEngine::setContextForObject(): Object already has a QQmlContext
4月 23 11:14:50 dragon systemsettings5[14280]: kf5.ki18n: "1 instead of 2
arguments to message {无法找到代码为“%2”的语言的翻译文件。...} supplied before conversion."
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39:
TypeError: Cannot read property 'LanguageCode' of null
4月 23 11:14:50 dragon systemsettings5[14280]:
file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43:
TypeError: Cannot read property 'display' of null
4月 23 11:14:50 dragon
[dolphin] [Bug 307505] Double click free space to folder up
https://bugs.kde.org/show_bug.cgi?id=307505 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #12 from Nate Graham --- In fact a patch was already submitted: https://phabricator.kde.org/D20532. There appears to be quite a bit of demand for this feature. Unfortunately the maintainer rejected it on fairly reasonable grounds. He'll need to be convinced to reconsider if the feature is ever to make it into Dolphin. Until then, I'm afraid I need to keep this bug report closed. It can always be re-opened if he reconsiders. No hard feelings, I hope you understand. :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 307505] Double click free space to folder up
https://bugs.kde.org/show_bug.cgi?id=307505 Nate Graham changed: What|Removed |Added URL||https://phabricator.kde.org ||/D20532 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #14 from Nate Graham --- Would you like to submit a patch? See https://community.kde.org/Get_Involved/development -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 420439] item.grabToImage() does not work in a KQuickAddons::ConfigModule
https://bugs.kde.org/show_bug.cgi?id=420439 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #11 from bruce.samha...@samhaber.ca --- Sorry that previous comment was supposed to be 'Now' versus 'not' so Probably worth noting is that with this version of Okular and OpenSuse I am now able to print properly to my Epson XP-810 printer. Now printing multiple pages and duplex. Previously Okular would only print 1 page. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 419355] Unable to log back in after screensaver
https://bugs.kde.org/show_bug.cgi?id=419355 --- Comment #8 from John Bennett --- Is there any way I can troubleshoot this?? Have tried remotely (ssh) using loginctl to unlock the session - does nothing. Can kill the session, etc. Would like to be able to use FerenOS, but currently can't, because the sessions are being locked/losing data. Using KDE/Plasma on opensuse15.1 + tumbleweed, on the same machine (multi-booting Opensuse 15.1/Tumbleweed, FerenOS, and Winblows) and don't have an issue. I occasionally also get the issue where trying to log back in after the screen saver kicks in, it tells me my password is incorrect, and won't let me back in. How can I troubleshoot?? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418630] Cannot select text
https://bugs.kde.org/show_bug.cgi?id=418630 Simon Redman changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Simon Redman --- Hi. Thanks for taking the time to submit this! It's something I have in mind, although I don't yet have a plan for how something like this would be implemented. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420440] plasma desktop can't render title of icon after suspend all the night
https://bugs.kde.org/show_bug.cgi?id=420440 --- Comment #1 from cody.h...@gmail.com --- Created attachment 127783 --> https://bugs.kde.org/attachment.cgi?id=127783=edit the title of icon has not been renderd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420440] New: plasma desktop can't render title of icon after suspend all the night
https://bugs.kde.org/show_bug.cgi?id=420440 Bug ID: 420440 Summary: plasma desktop can't render title of icon after suspend all the night Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: cody.h...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 127782 --> https://bugs.kde.org/attachment.cgi?id=127782=edit the title of icon has not been renderd(but when it being rename,it can show title) SUMMARY STEPS TO REPRODUCE 1. suspend system 2. wait for a while or longer 3. go to plasma decktop OBSERVED RESULT the title of icon has not been renderd EXPECTED RESULT the title of icon has been renderd SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.4.0-26-genneric (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION NVIDIA Driver loaded.(GTX1650) -- 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 Ash changed: What|Removed |Added CC||ashleysom...@gmail.com --- Comment #63 from Ash --- Weighing in here with another "me too". We use Plasma 5 with latest KDE and latest Dolphin on a VM at work. The VM has 8 NFS4 shares permanently mounted. If we leave a Dolphin window open overnight, the memory usage creeps up from approx 500mb used to 32GB (100%) and other applications and services start crashing due to lack of memory. While the memory usage is climbing, the CPU usage also gradually increases from 1% to 100% usage, and stays at 100% usage until I close all open Dolphin windows. On a different VM with no NFS mounts, this problem does not occur. We were having the same problem with Kate, but after disabling the "Filesystem" plugin, the problem no longer occurs with Kate. Note, we do also have Docker installed, others suggested it might be a culprit but I don't think it is related in this case. We disabled the docker daemon overnight one time and the problem with Dolphin still occurred. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420435] [Wayland] Kwin aborts after typing Alt+X into dosemu
https://bugs.kde.org/show_bug.cgi?id=420435 --- Comment #1 from magib...@hotmail.com --- Created attachment 127781 --> https://bugs.kde.org/attachment.cgi?id=127781=edit Output of startplasma-wayland with WAYLAND_DEBUG=1 QT_LOGGING_RULES="kwin_*.debug=true" I can confirm that the GDK_BACKEND=x11 QT_QPA_PLATFORM=xcb environment variables are unrelated to the issue. dosemu is an X11 SDL2 application. When kwin aborts, dosemu receives a SIGHUP: > Thread 6 "dosemu: sdl_r" received signal SIGHUP, Hangup > [Switching to Thread 0x7f395d5f6700 (LWP 1138)] > 0x7f396fb957b4 in do_futex_wait.constprop () >from /usr/lib/libpthread.so.0 > (gdb) thread apply all bt > > Thread 10 (Thread 0x7f395a237700 (LWP 1151)): > #0 0x7f396fb957b4 in do_futex_wait.constprop () at > /usr/lib/libpthread.so.0 > #1 0x7f396fb958a8 in __new_sem_wait_slow.constprop.0 () at > /usr/lib/libpthread.so.0 > #2 0x55ae8ef0c94d in synth_thread () > #3 0x7f396fb8c46f in start_thread () at /usr/lib/libpthread.so.0 > #4 0x7f396f9663d3 in clone () at /usr/lib/libc.so.6 > > Thread 9 (Thread 0x7f395b7fb700 (LWP 1141)): > #0 0x7f396f95bbb6 in ppoll () at /usr/lib/libc.so.6 > #1 0x7f396443a0e3 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 > #2 0x7f396301 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 > #3 0x7f396eec7687 in () at /usr/lib/libSDL2-2.0.so.0 > #4 0x7f396ee0dff6 in () at /usr/lib/libSDL2-2.0.so.0 > #5 0x7f396ee5df4f in () at /usr/lib/libSDL2-2.0.so.0 > #6 0x7f396eeebc9a in () at /usr/lib/libSDL2-2.0.so.0 > #7 0x7f396fb8c46f in start_thread () at /usr/lib/libpthread.so.0 > #8 0x7f396f9663d3 in clone () at /usr/lib/libc.so.6 > > Thread 8 (Thread 0x7f39644bc700 (LWP 1140)): > #0 0x7f396f95bbb6 in ppoll () at /usr/lib/libc.so.6 > #1 0x7f396443a0e3 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 > #2 0x7f396301 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 > #3 0x7f3963b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 > #4 0x7f396eec7990 in () at /usr/lib/libSDL2-2.0.so.0 > #5 0x7f396ee5df4f in () at /usr/lib/libSDL2-2.0.so.0 > #6 0x7f396eeebc9a in () at /usr/lib/libSDL2-2.0.so.0 > #7 0x7f396fb8c46f in start_thread () at /usr/lib/libpthread.so.0 > #8 0x7f396f9663d3 in clone () at /usr/lib/libc.so.6 > > Thread 7 (Thread 0x7f395bffc700 (LWP 1139)): > #0 0x7f396fb957b4 in do_futex_wait.constprop () at > /usr/lib/libpthread.so.0 > #1 0x7f396fb958a8 in __new_sem_wait_slow.constprop.0 () at > /usr/lib/libpthread.so.0 > #2 0x55ae8ee3a81b in render_thread () > #3 0x7f396fb8c46f in start_thread () at /usr/lib/libpthread.so.0 > #4 0x7f396f9663d3 in clone () at /usr/lib/libc.so.6 > > Thread 6 (Thread 0x7f395d5f6700 (LWP 1138)): > #0 0x7f396fb957b4 in do_futex_wait.constprop () at > /usr/lib/libpthread.so.0 > #1 0x7f396fb958a8 in __new_sem_wait_slow.constprop.0 () at > /usr/lib/libpthread.so.0 > #2 0x7f396fbb17fd in render_thread () at /usr/lib/dosemu/libplugin_sdl.so > #3 0x7f396fb8c46f in start_thread () at /usr/lib/libpthread.so.0 > #4 0x7f396f9663d3 in clone () at /usr/lib/libc.so.6 > > Thread 1 (Thread 0x7f396f866280 (LWP 1083)): > #0 0x7f396f22afe0 in FarPtr<_bprm>::~FarPtr() () at > /usr/lib/fdpp/libfdpp.so > #1 0x7f396f8a5537 in __run_exit_handlers () at /usr/lib/libc.so.6 > #2 0x7f396f8a56ee in () at /usr/lib/libc.so.6 > #3 0x7f396eca83f2 in _XDefaultIOError () at /usr/lib/libX11.so.6 > #4 0x7f396eca869e in _XIOError () at /usr/lib/libX11.so.6 > #5 0x7f396eca5db7 in _XEventsQueued () at /usr/lib/libX11.so.6 > #6 0x7f396ec87c3b in XFlush () at /usr/lib/libX11.so.6 > #7 0x7f396eed16ff in () at /usr/lib/libSDL2-2.0.so.0 > #8 0x7f396ee2b5ef in () at /usr/lib/libSDL2-2.0.so.0 > #9 0x55ae8eefbd48 in mouse_client_show_cursor () > #10 0x55ae8eef56b6 in mouse_cursor () > #11 0x55ae8eef75d7 in mouse_int () > #12 0x55ae8ee51b18 in _int33_ () > #13 0x55ae8ee555b4 in dos_helper () > #14 0x55ae8ee5d19b in coopth_thread () > #15 0x55ae8ee801f7 in co_runner () > #16 0x in () Reproducing the issue is not so straightforward. Sometimes I get it the first time I do `edit` > `Alt+X`, sometimes I get it after pressing Alt+X repeatedly, etc. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 luancarvalho changed: What|Removed |Added CC||luancarvalhomartins@gmail.c ||om --- Comment #13 from luancarvalho --- Is there any way I can help? I think this feature would be great. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420438] Cannot Download Stock Prices with AppImage Version of KMyMoney
https://bugs.kde.org/show_bug.cgi?id=420438 --- Comment #1 from Stephen Rynas --- Below is a list of files that Mint 19.3 says are no longer necessary when the repository version of KMyMoney was uninstalled. One or more of those files are needed by the AppImage of KMyMoney. Which ones, I don't know. But for now, I am not unintalling them since I need to download stock prices. The following packages were automatically installed and are no longer required: kinit kio kmymoney-common kpackagetool5 libalkimia5-7 libaqbanking-data libaqbanking35 libaqbanking35-plugins libaqebics0 libaqhbci24 libaqofxconnect7 libaribb24-0 libbasicusageenvironment1 libcddb2 libdbusmenu-qt5-2 libdvbpsi10 libebml4v5 libfam0 libgrantlee-textdocument5 libgroupsock8 libgwengui-cpp0 libgwengui-qt5-0 libgwenhywfar-data libgwenhywfar60 libkchart2 libkf5activities5 libkf5akonadicore-bin libkf5akonadicore5abi1 libkf5akonadiprivate5 libkf5akonadiwidgets5 libkf5archive5 libkf5attica5 libkf5auth-data libkf5auth5 libkf5bookmarks-data libkf5bookmarks5 libkf5codecs-data libkf5codecs5 libkf5completion-data libkf5completion5 libkf5config-data libkf5configcore5 libkf5configgui5 libkf5configwidgets-data libkf5configwidgets5 libkf5contacts-data libkf5contacts5 libkf5coreaddons-data libkf5coreaddons5 libkf5crash5 libkf5dbusaddons-data libkf5dbusaddons5 libkf5declarative-data libkf5declarative5 libkf5doctools5 libkf5emoticons-bin libkf5emoticons-data libkf5emoticons5 libkf5globalaccel-data libkf5globalaccel5 libkf5guiaddons5 libkf5holidays-data libkf5holidays5 libkf5i18n-data libkf5i18n5 libkf5iconthemes-data libkf5iconthemes5 libkf5identitymanagement-data libkf5identitymanagement5abi1 libkf5itemmodels5 libkf5itemviews-data libkf5itemviews5 libkf5jobwidgets-data libkf5jobwidgets5 libkf5kcmutils-data libkf5kcmutils5 libkf5kiocore5 libkf5kiofilewidgets5 libkf5kiontlm5 libkf5kiowidgets5 libkf5notifications-data libkf5notifications5 libkf5package-data libkf5package5 libkf5parts-data libkf5parts5 libkf5pimtextedit-data libkf5pimtextedit5abi2 libkf5quickaddons5 libkf5service-bin libkf5service-data libkf5service5 libkf5solid5 libkf5solid5-data libkf5sonnet5-data libkf5sonnetcore5 libkf5sonnetui5 libkf5syntaxhighlighting-data libkf5syntaxhighlighting5 libkf5textwidgets-data libkf5textwidgets5 libkf5wallet-bin libkf5wallet-data libkf5wallet5 libkf5webkit5 libkf5widgetsaddons-data libkf5widgetsaddons5 libkf5windowsystem-data libkf5windowsystem5 libkf5xmlgui-bin libkf5xmlgui-data libkf5xmlgui5 libktoblzcheck1v5 libkwalletbackend5-5 liblivemedia62 libmatroska6v5 libmicrodns0 libnfs11 libofx7 libopenmpt-modplug1 libosp5 libphonon4qt5-4 libplacebo4 libpolkit-qt5-1-1 libqt5positioning5 libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5quickwidgets5 libqt5script5 libqt5sensors5 libqt5sql5 libqt5texttospeech5 libqt5webchannel5 libqt5webkit5 libqt5x11extras5 libqt5xml5 libresid-builder0c2a libsdl-image1.2 libsidplay2 libssh2-1 libupnp6 libusageenvironment3 libvlc5 libvlccore9 phonon4qt5 phonon4qt5-backend-vlc vlc-data vlc-plugin-base vlc-plugin-video-output -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 420439] New: item.grabToImage() does not work in a KQuickAddons::ConfigModule
https://bugs.kde.org/show_bug.cgi?id=420439
Bug ID: 420439
Summary: item.grabToImage() does not work in a
KQuickAddons::ConfigModule
Product: frameworks-kdeclarative
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: uhh...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
Expected behaviour: item.grabToImage() works as expected.
Actual behaviour: "QML : grabToImage: item's window is not visible"
Example:
---
import QtQuick 2.6
import org.kde.kcm 1.2 as KCM
KCM.ScrollViewKCM {
Rectangle {
id: rect
width: 50
height: 50
color: "red"
MouseArea {
anchors.fill: parent
onClicked: {
rect.grabToImage(function(result) {})
// QML Rectangle: grabToImage: item's window is not visible
}
}
}
}
---
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 420438] New: Cannot Download Stock Prices with AppImage Version of KMyMoney
https://bugs.kde.org/show_bug.cgi?id=420438 Bug ID: 420438 Summary: Cannot Download Stock Prices with AppImage Version of KMyMoney Product: kmymoney Version: 5.0.8 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: rimworldsm...@gmail.com Target Milestone: --- SUMMARY The AppImage version of KMyMoney still requires that certain KyMoney files from the Mint (Ubuntu 18.04) repository be available. When I fully deleted the repository version of KMyMoney, the AppImage version would no longer download stock prices. I had to re-install the repository version to "fix" this issue. Need to incorporate the the stock price module into the AppImage version. Additionally, on launch, the AppImage version periodically crashes with no error message. SOFTWARE/OS VERSIONS Linux Mint 19.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 420437] New: EKOS scheduler instructs Dome to open when weather is still in alert state
https://bugs.kde.org/show_bug.cgi?id=420437 Bug ID: 420437 Summary: EKOS scheduler instructs Dome to open when weather is still in alert state Product: kstars Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: h...@lambermont.dyndns.org Target Milestone: --- SUMMARY EKOS scheduler cannot handle the situation where at first it did image, then it closed down due to bad weather, and from this state with history it cannot start when weather clears up again. Even worse, when the Twilight interval reaches the new evening, scheduler happily instructs the dome to open without noting that the weather is still in alert state. (Luckily the Dome device driver refuses to open due to bad weather). But when the weather later clears up Scheduler does not take action. (It should only then instruct the Dome to open). Here's a log of this case : 2020-04-22T22:25:49 Weather conditions are OK. 2020-04-22T22:03:03 Unparking dome... 2020-04-22T22:03:01 Warning: job 'hd224992' execution overlaps daylight, it will be interrupted at dawn and rescheduled on next night time. 2020-04-22T22:03:00 Scheduler started. 2020-04-22T22:03:00 Scheduler is awake. 2020-04-22T06:15:16 Caution: weather conditions are in the DANGER zone! 2020-04-22T04:43:04 Shutdown complete. So the observatory shut down this morning at 04:43, then just now at 22:03 it said 'Unparking Dome', which the Dome driver refused. At this point weather was still in alert state. Weather state cleared up 22 minutes later but that initiated no action. The Dome Scripting Gateway log : 2020-04-22T22:03:03: [WARNING] Weather is in the danger zone! Cannot unpark dome. STEPS TO REPRODUCE - have weather and twilight boxes checked in the scheduler - use a job that spans multiple nights - let scheduler image - let it close up - let it run to the next evening OBSERVED RESULT - scheduler instructed the dome to open while weather was in alert state - when weather cleared up nothing happened - weather checkbox became greyed out the second evening EXPECTED RESULT - scheduler does not instruct dome to open when weather is in alert state - scheduler continues imaging when weather clears up - weather checkbox is not greyed out halfway a session kstars-bleeding 6:3.4.1+202002231737~ubuntu18.04.1 on Ubuntu 18.04.4 LTS -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420436] New: Modify header section
https://bugs.kde.org/show_bug.cgi?id=420436 Bug ID: 420436 Summary: Modify header section Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: sotadic_rest...@simplelogin.co Target Milestone: --- SUMMARY Kmail already has many options to customize the interface and that's amazing! But there's almost nothing to customize the part where the basic headers of an email are displayed, like sender, recipient, subject, etc. Options to change which items should be displayed, list all headers, see the source of the email, would be very useful. Another necessary modification would be the possibility to move the reply buttons, forward, and other useful ones to that same place. In my opinion it makes more sense that these buttons stay in the header. Currently, they only stay on the top menu and you can move it to one of the sides or keep it "floating". Something like what I tried to do in this image: https://i.imgur.com/etvJlxE.png SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 5.6.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419544] KDE desktop crash when browsing firefox
https://bugs.kde.org/show_bug.cgi?id=419544 Hugo Cesar de Castro Carneiro changed: What|Removed |Added CC||hcesarcas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419544] KDE desktop crash when browsing firefox
https://bugs.kde.org/show_bug.cgi?id=419544 --- Comment #1 from Hugo Cesar de Castro Carneiro --- Created attachment 127780 --> https://bugs.kde.org/attachment.cgi?id=127780=edit New crash information added by DrKonqi plasmashell (5.18.4) using Qt 5.14.2 - What I was doing when the application crashed: Just logged into my session. As soon as it opened, Plasma crashed. I tried to use an Openbox/KDE session. Again, as soon as it opened, Plasma crashed. -- Backtrace (Reduced): #6 0x in () #7 0x7f6287171fa7 in () at /usr/lib/libQt5Quick.so.5 #8 0x7f6287172019 in () at /usr/lib/libQt5Quick.so.5 #9 0x7f6287338a93 in () at /usr/lib/libQt5Quick.so.5 #10 0x7f628096947a in () at /usr/lib/libQt5XcbQpa.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420435] New: [Wayland] Kwin aborts after typing Alt+X into dosemu
https://bugs.kde.org/show_bug.cgi?id=420435 Bug ID: 420435 Summary: [Wayland] Kwin aborts after typing Alt+X into dosemu Product: kwin Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: magib...@hotmail.com Target Milestone: --- SUMMARY Kwin sometimes crashes when typing the Alt+X key combination in dosemu, in a Wayland session. I started the Wayland session with the GDK_BACKEND=x11 and QT_QPA_PLATFORM=xcb environment variables so as to force applications to use Xwayland. I don't know if this is required to reproduce the issue. dosemu seems to be an X11 application as its window has the X11 icon. The crash does not happen every time. I'm not sure yet what needs to be done to always hit this issue. STEPS TO REPRODUCE 1. Start a wayland session, e.g. 'GDK_BACKEND=x11 QT_QPA_PLATFORM=xcb startplasma-wayland' 2. Open a dosemu window, then type 'edit' to get into FreeDOS edit 3. Press the Alt+X key combination. OBSERVED RESULT kwin crashes with the following backtrace: > Thread 1 "kwin_wayland" received signal SIGABRT, Aborted. > 0x7f96f702ece5 in raise () from /usr/lib/libc.so.6 > #0 0x7f96f702ece5 in raise () at /usr/lib/libc.so.6 > #1 0x7f96f701892c in abort () at /usr/lib/libc.so.6 > #2 0x7f96f745a938 in qt_message_fatal (context=..., message= pointer>...) at global/qlogging.cpp:1914 > #3 QMessageLogger::fatal(char const*, ...) const (this=, > msg=) > at global/qlogging.cpp:893 > #4 0x7f96f84f13db in KWin::AbstractClient::transientPlacement(QRect > const&) const () at /usr/lib/libkwin.so.5 > #5 0x7f96f76a6cde in QtPrivate::QSlotObjectBase::call(QObject*, void**) > (a=0x7ffc275811e0, r=0x55bb466002d0, this=0x55bb46f07830) > at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 > #6 doActivate(QObject*, int, void**) (sender=0x55bb46f07340, > signal_index=3, argv=0x7ffc275811e0) > at kernel/qobject.cpp:3870 > #7 0x7f96f81d30a0 in > KWayland::Server::ClientConnection::disconnected(KWayland::Server::ClientConnection*) > () > at /usr/lib/libKF5WaylandServer.so.5 > #8 0x7f96f81e3d0d in > KWayland::Server::ClientConnection::Private::destroyListenerCallback(wl_listener*, > void*) () > at /usr/lib/libKF5WaylandServer.so.5 > #9 0x7f96f4e1de0f in wl_priv_signal_final_emit > (signal=signal@entry=0x55bb46f031b8, data=data@entry=0x55bb46f03150) > at ../wayland-1.18.0/src/wayland-server.c:2157 > #10 0x7f96f4e1e002 in wl_client_destroy (client=0x55bb46f03150) at > ../wayland-1.18.0/src/wayland-server.c:880 > #11 0x7f96f4e1e109 in destroy_client_with_error (reason=, > client=) > at ../wayland-1.18.0/src/wayland-server.c:319 > #12 wl_client_connection_data (fd=, mask=, > data=0x55bb46f03150) > at ../wayland-1.18.0/src/wayland-server.c:342 > #13 0x7f96f4e1ffaa in wl_event_loop_dispatch (loop=0x55bb4664dd60, > timeout=) > at ../wayland-1.18.0/src/event-loop.c:1027 > #14 0x7f96f81e8c70 in KWayland::Server::Display::Private::dispatch() () > at /usr/lib/libKF5WaylandServer.so.5 > #15 0x7f96f76a6cde in QtPrivate::QSlotObjectBase::call(QObject*, void**) > (a=0x7ffc27581640, r=0x55bb4663a3f0, this=0x55bb4664e2b0) > at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 > #16 doActivate(QObject*, int, void**) (sender=0x55bb4664e190, > signal_index=3, argv=0x7ffc27581640) > at kernel/qobject.cpp:3870 > #17 0x7f96f76a130f in QMetaObject::activate(QObject*, QMetaObject const*, > int, void**) > (sender=sender@entry=0x55bb4664e190, m=m@entry=0x7f96f78fd220 > , > local_signal_index=local_signal_index@entry=0, > argv=argv@entry=0x7ffc27581640) at kernel/qobject.cpp:3930 > #18 0x7f96f76aa532 in QSocketNotifier::activated(int, > QSocketNotifier::QPrivateSignal) > (this=this@entry=0x55bb4664e190, _t1=, _t2=...) at > .moc/moc_qsocketnotifier.cpp:141 > #19 0x7f96f76aa882 in QSocketNotifier::event(QEvent*) > (this=0x55bb4664e190, e=0x7ffc27581900) > at kernel/qsocketnotifier.cpp:266 > #20 0x7f96f7a60352 in QApplicationPrivate::notify_helper(QObject*, > QEvent*) > (this=this@entry=0x55bb465d39b0, receiver=receiver@entry=0x55bb4664e190, > e=e@entry=0x7ffc27581900) > at kernel/qapplication.cpp:3685 > #21 0x7f96f7a69829 in QApplication::notify(QObject*, QEvent*) > (this=0x7ffc27581ce0, receiver=0x55bb4664e190, e=0x7ffc27581900) at > kernel/qapplication.cpp:3431 > #22 0x7f96f76714f2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) > (receiver=0x55bb4664e190, event=0x7ffc27581900) at > ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 > #23 0x7f96f76c6b04 in > QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=0x55bb465e2630) > at
[kmail2] [Bug 420434] New: Change only body font size
https://bugs.kde.org/show_bug.cgi?id=420434 Bug ID: 420434 Summary: Change only body font size Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: sotadic_rest...@simplelogin.co Target Milestone: --- SUMMARY Changing the font size of the mail body also changes the header font. OBSERVED RESULT I changed the default font size of kmail because I think the default size is too small (at least on my monitor) but I would like this change to only apply to the message body and not the header. As some email addresses can be very large, or there can be a lot of recipients, this becomes a mess and takes up almost every piece of screen available See this screenshot: https://i.imgur.com/djDh9nt.png EXPECTED RESULT Ideally, it would be possible to edit the font size individually for each of the two separately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 5.6.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381579] add and handle Openpgp header
https://bugs.kde.org/show_bug.cgi?id=381579 Parker changed: What|Removed |Added CC||sotadic_restage@simplelogin ||.co --- Comment #1 from Parker --- Autocrypt does that. It hasn't been implemented in kmail yet. https://bugs.kde.org/show_bug.cgi?id=388036 Maybe this is a duplicate bug? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420433] Clone identity
https://bugs.kde.org/show_bug.cgi?id=420433 Parker changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Parker --- I just realized that this option appears when creating a new identity. sorry -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416181] Allow selecting different locale for each identity / account
https://bugs.kde.org/show_bug.cgi?id=416181 Parker changed: What|Removed |Added CC||sotadic_restage@simplelogin ||.co --- Comment #1 from Parker --- up -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420433] Clone identity
https://bugs.kde.org/show_bug.cgi?id=420433 --- Comment #1 from Parker --- A screenshot of the current options https://i.imgur.com/ReTcDUc.png -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420433] New: Clone identity
https://bugs.kde.org/show_bug.cgi?id=420433 Bug ID: 420433 Summary: Clone identity Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sotadic_rest...@simplelogin.co Target Milestone: --- Kmail already offers some options like modify, delete and rename, but it's still not possible to clone an existing identity. That would be very helpful. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 5.6.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #10 from bruce.samha...@samhaber.ca --- Probably worth noting is that with this version of Okular and OpenSuse I am not able to print properly to my Epson XP-810 printer. Now printing multiple pages and duplex. Previously Okular would only print 1 page. With this driver I can print to the HP Deskjet1120C with 'Document Viewer' called 'XReader 1.6.2' -- You are receiving this mail because: You are watching all bug changes.
[step] [Bug 420432] New: steps - malformed URL
https://bugs.kde.org/show_bug.cgi?id=420432 Bug ID: 420432 Summary: steps - malformed URL Product: step Version: 0.1.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ks.vladi...@gmail.com Reporter: m...@xanum.uam.mx Target Milestone: --- SUMMARY if I try to open tutorial or any examples it returns: "malformed URL" STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-46-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420387] Okular can not open "Okular document archive" files
https://bugs.kde.org/show_bug.cgi?id=420387 --- Comment #5 from shina...@gmail.com --- Yes, sadly it's not intuitive. Now I know and it's not an issue for me anymore. But alone I would never come up with this solution. Sadly I am not a manual reader. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418442] Experiencing 100% cpu usage whenever a notification is present
https://bugs.kde.org/show_bug.cgi?id=418442 --- Comment #3 from jeep7...@gmail.com --- Still experiencing this with 5.18.4. It can be mitigated by turning animation speed to instant. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420387] Okular can not open "Okular document archive" files
https://bugs.kde.org/show_bug.cgi?id=420387 --- Comment #4 from Albert Astals Cid --- Isn't .okular the default suggested extension when saving? Ah, actually i think there was an issue with the Qt/GTK save dialog integration and maybe you don't get that and that's why it's confusing for you. Not really something we can easily fix sadly :/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420430] Inconsistent behavior of View tab of Metadata dialog in digiKam Configure menu
https://bugs.kde.org/show_bug.cgi?id=420430 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Can you reproduce this dysfunction with a more recent digiKam release. Currently we are in 7.0.0-beta3 that you can test using last AppImage Linux Bundle : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #9 from bruce.samha...@samhaber.ca --- Please let me know if these are the correct attachments then I will change to the Gutenprint.ppd and create the error_log file for the other Bug report. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #8 from bruce.samha...@samhaber.ca --- Created attachment 127779 --> https://bugs.kde.org/attachment.cgi?id=127779=edit The attachment requested /var/log/cups/error_log -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 bruce.samha...@samhaber.ca changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Assignee|okular-de...@kde.org|bruce.samha...@samhaber.ca Status|NEEDSINFO |REOPENED --- Comment #7 from bruce.samha...@samhaber.ca --- Created attachment 127778 --> https://bugs.kde.org/attachment.cgi?id=127778=edit The attachment requested /etc/cups/ppd/hpdeskjet1120c.ppd Adding the requested attachments. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420398] Install icon elongated
https://bugs.kde.org/show_bug.cgi?id=420398 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 JanKusanagi changed: What|Removed |Added CC||jan-b...@gmx.co.uk --- Comment #4 from JanKusanagi --- I get a crash that looks mostly like "Thread 1" in the original report, and I can reproduce consistently after a second of launching Yakuake with this simple procedure: - Press the shortcut to show Yakuake. - Right-click somewhere in the "console area" to get the context menu. - Dismiss the context menu by clicking in any other empty area of the "console area". - Press Ctrl+D to exit the Bash shell, which closes the only tab, and crashes Yakuake. Operating System: Mageia 8 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 Yakuake reports itself as "Version 3.0.5+". The "package version" is 20.04.0, same as Konsole. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420431] New: Invalid MimeType "*/*" in `org.kde.kdeconnect_open.desktop`
https://bugs.kde.org/show_bug.cgi?id=420431
Bug ID: 420431
Summary: Invalid MimeType "*/*" in
`org.kde.kdeconnect_open.desktop`
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: orctaro...@gmail.com
Target Milestone: ---
In the desktop file `org.kde.kdeconnect_open.desktop`, the `MimeType` is
`*/*`.
`update-desktop-database` is a tool provided in `desktop-file-utils` that
> updates the database containing a cache of MIME types handled by desktop files
When running `update-desktop-database`, it throws an error saying that
> "*/*" is an invalid MIME type ("*" is an unregistered media type)
This is reported in [Clear
Linux](https://github.com/clearlinux/distribution/issues/1906) and [Arch
Linux](https://bugs.archlinux.org/task/65865)
STEPS TO REPRODUCE
1. Run `update-desktop-database`
OBSERVED RESULT
> "*/*" is an invalid MIME type ("*" is an unregistered media type)
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 419921] Cursor doesn't draw
https://bugs.kde.org/show_bug.cgi?id=419921 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #7 from vanyossi --- Hey, did you try resetting your configuration? I use Krita on mac and its been a long time since cursor glitched. What steps you do to make the cursor change into a looking glass? is a gesture, or using the zoom tool, maybe a shortcut. When the cursor is stuck is it only the cursor shape that is different, meaning, you can paint but the cursor is wrong, or the application menus lock and you can't press anything? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420430] New: Inconsistent behavior of View tab of Metadata dialog in digiKam Configure menu
https://bugs.kde.org/show_bug.cgi?id=420430
Bug ID: 420430
Summary: Inconsistent behavior of View tab of Metadata dialog
in digiKam Configure menu
Product: digikam
Version: 5.9.0
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Setup-Metadata
Assignee: digikam-bugs-n...@kde.org
Reporter: papapanagiot...@hotmail.com
Target Milestone: ---
SUMMARY
Problem in using the View option for Metadata: Besides the desired items
selected by the user, additional items preceding the first selected item appear
in the filtered view list.
STEPS TO REPRODUCE
1. Click Metadata tab of the right sidebar
2. Click EXIF subtab
3. Click the filter icon
4. Click on Settings
5. In the {Embedded Image Information Management} window that opens choose the
{View} tab and then the EXIF Viewer subtab
6. Deactivate all the check boxes by clicking on the Clear button.
7. Scroll down the list to the [Photograph Information] section and tick only
the {ComponentsConfiguration} check box
8. Fimally click the {OK} button (the window closes)
9. In the right sidebar / Metadata tab click the filter icon
10. Click the Custom button and select an image
OBSERVED RESULT
The resultant Metadata list contains the items: {GPS Version ID}, {Color Filter
Array Pattern}, {Color Space}, {Components Configuration}
EXPECTED RESULT
The resultant Metadata list should contain only the item {Components
Configuration}
ADDITIONAL NOTE:
By the way, please notice that in the general list of the {View} tab of the
{Embedded Image Information Management} window there is no check box labeled
“Color Filter Array Pattern”
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-pa] [Bug 420416] Volume Applet Settings allows invalid characters and textbox expands
https://bugs.kde.org/show_bug.cgi?id=420416 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Summary|Volume Applet Settings |Volume Applet Settings |allow invalid characters|allows invalid characters |and textbox expands |and textbox expands CC||n...@kde.org Severity|normal |minor Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420398] Install icon elongated
https://bugs.kde.org/show_bug.cgi?id=420398 Vivek changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Vivek --- (In reply to Maik Qualmann from comment #2) > Here in Windows 10 the logo is absolutely round. Did you activate a scaling > factor under Windows? Your monitor resolution is set correctly or are you > using a scaling in the monitor settings? > > Maik My apologies - Windows was scaling the display to 125%. At 100% the icon is perfectly round. I am marking this as Resolved-> not a bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420406] Images in a Kirigami.Card clip outside of bounds
https://bugs.kde.org/show_bug.cgi?id=420406 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420421] Wish: Store log or notes with configuration
https://bugs.kde.org/show_bug.cgi?id=420421 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- I do this myself, but in a text file. It's a sufficiently niche use case that I'm not sure it makes sense to add a feature to system settings to support it. :) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420424] [enhancement] Provide feedback when unable to mount CryFS vault
https://bugs.kde.org/show_bug.cgi?id=420424 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420226] Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 --- Comment #3 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #2) > I cannot reproduce this issue, i suppose because its random its not that > easy to reproduce. Looking at the log provided I can only tell the crash > ocurred somewhere at KisSelection::pixelSelection() > > Are you generate lldb backtraces? Frankly I don't know how to do that. I tried something like this: > ❯ lldb /Applications/krita.app/Contents/MacOS/krita > (lldb) target create "/Applications/krita.app/Contents/MacOS/krita" > runCurrent executable set to '/Applications/krita.app/Contents/MacOS/krita' > (x86_64). > (lldb) run > error: process exited with status -1 (Error 1) But as you can see it doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420427] Crash in radeonsi_dri.so when opening Team Viewer, copying a flameshot image to clipboard, and when receiving notifications on whatsapp (version with electron)
https://bugs.kde.org/show_bug.cgi?id=420427 Nate Graham changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Summary|crash when openning Team|Crash in radeonsi_dri.so |Viewer, or upon try to copy |when opening Team Viewer, |a flameshot image to|copying a flameshot image |clippboard, and when|to clipboard, and when |receive notifications on|receiving notifications on |whatsapp (version with |whatsapp (version with |electron) |electron) Component|general |generic-crash CC||n...@kde.org --- Comment #1 from Nate Graham --- Hmm, crashing in the graphics drivers. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 --- Comment #7 from Simon Gardet --- big mea culpa sorry. Actually, I find all occurrences of stock_new-window.svg in the Adapta theme (the only one that works and I'm trying to figure out why it doesn't work in the breeze.) It's a symbolic link to window.svg. Also, I'm trying to create a symbolic link new-window.svg -> stock_new-window.svg and window.svg -> stock_new-window.svg in Breeze Icons and it doesn't work So the problem is not the icon names. I'm going to try to find the real problem and I'll tell you what the problem is. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420422] Indian Rupee has new symbol since 7 years,it is ₹
https://bugs.kde.org/show_bug.cgi?id=420422 Thomas Baumgart changed: What|Removed |Added Version Fixed In||5.0.9 Latest Commit||https://commits.kde.org/kmy ||money/27b7a488c4f983525e093 ||8facbb9467a0aaff8e2 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Thomas Baumgart --- Git commit 27b7a488c4f983525e0938facbb9467a0aaff8e2 by Thomas Baumgart. Committed on 22/04/2020 at 16:51. Pushed by tbaumgart into branch '5.0'. Update symbol for Indian Rupee This will use the new symbol in new data files but not update existing files. Currently there's no other way than patching the data file directly to change the symbol. FIXED-IN: 5.0.9 M +1-1kmymoney/mymoney/mymoneyfile.cpp https://commits.kde.org/kmymoney/27b7a488c4f983525e0938facbb9467a0aaff8e2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420342] Transparency colour not saved
https://bugs.kde.org/show_bug.cgi?id=420342 --- Comment #7 from Rudolf --- Rebecca Breu schreef: > https://bugs.kde.org/show_bug.cgi?id=420342 > > Rebecca Breu changed: > > What|Removed |Added > > CC||rebe...@rbreu.de > > --- Comment #6 from Rebecca Breu --- > I still don't know what exactly you are doing, and I can't reproduce > any bugs regarding transparency. > > "Therefor I started to change the background to 'white-transparent'." > > What do you mean by this? The transparency checkerboard of the canvas? > Your layers? Your png export? > > "This figure should have a transparent background and had it through the > whole procedure of making but once saved, the background is white, > transparency gone." > > You should save your images as kra files and only export them to other > file formats once you are done. If you don't export the png with "Store > alpha channel" enabled, then (and only then) you get to pick a colour > at the bottom of the export dialog with which your transparency is > going to be replaced and then, yes, the transparency will be gone in > the exported png. Even if you open that png up again in Krita. > > "And in some occasions a soft grey or white shade appears on > the saved picture which is invisible in Krita." > > My guess is that it's there but not very visible on the white-and-grey > transparency checkerboard, and just a bit that you wanted to erase but > didn't erase completely with the soft eraser because you couldn't see > it. If you are working on black and white pictures, it's probably best > to either change the colour of the transparency checkerboard (Settings > -> Configure Krita -> Display -> Grid Settings -> Transparency > Checkerboard), or to add a solid bright colour layer at the bottom of > your layer stack and toggle the vibisility of that on and off for > checking. And of course toggle visibility off for export. ;) > Thanks very much, Rebecca, I never used kra-format before because I did not understand the necessity of it since I could save in png directly. The problem with 'native' formats is that one cannot publish in them, except for the native Photoshop format psd, which is even known to vector programs. I will experiment in that direction, saving in kra exporting in png. You didn't understand my silly "Therefore I started to change the background to 'white transparent'." I started using Krita seriously in MacOS. There is given a very 'playful' way of changing the background colour and transparency by way of choosing the colour of a 'colouring pencil'. So when the chequered background was to dark for me to see some edge details in the b/w drawing, I chose white in the background and set the transparency to 50%, making sure that I could set the transparency back tot 100% afterwards. In some cases that did not work as perfectly as I had hoped for. I will follow your advice for which I am very thankful and I 'll see what happens. Have a very nice day and keep healthy. Best regards, Rudolf Kahl -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420342] Transparency colour not saved
https://bugs.kde.org/show_bug.cgi?id=420342 --- Comment #8 from Rudolf --- Created attachment 127776 --> https://bugs.kde.org/attachment.cgi?id=127776=edit Krita.png -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420429] Cannot rightclick files in Dolphin without it crashing
https://bugs.kde.org/show_bug.cgi?id=420429 ienjoydigginggra...@gmail.com changed: What|Removed |Added CC||ienjoydigginggraves@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420429] New: Cannot rightclick files in Dolphin without it crashing
https://bugs.kde.org/show_bug.cgi?id=420429 Bug ID: 420429 Summary: Cannot rightclick files in Dolphin without it crashing Product: dolphin Version: 19.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ienjoydigginggra...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 127774 --> https://bugs.kde.org/attachment.cgi?id=127774=edit Text from launching Dolphin from Kobsole My roommate broght to my attention that he could not rightclick a image in a folder and set it as wallpaper, nor get the rightclick menu at all and Dolphin would actually crash. I tested to confirm and also opened a folder of movies and tried to get the rightclick and got the same thing. I honesty do not know what is wrong with his Dolphin since everything else seems to be working without issue. According to him he's had the behavior for a couple of days. Could use some suggestion on what might be the cause. Thanks Manjaro 20.0 Testing Build Addition information: https://forum.manjaro.org/t/issue-with-rightclicking-files-in-dolphin/137609 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420226] Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 vanyossi changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||ghe...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from vanyossi --- I cannot reproduce this issue, i suppose because its random its not that easy to reproduce. Looking at the log provided I can only tell the crash ocurred somewhere at KisSelection::pixelSelection() Are you generate lldb backtraces? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420428] New: nightly build 367/vob exports at 4:3 even when 16:9 in project settings
https://bugs.kde.org/show_bug.cgi?id=420428 Bug ID: 420428 Summary: nightly build 367/vob exports at 4:3 even when 16:9 in project settings Product: kdenlive Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: richard.sutherland...@gmail.com Target Milestone: --- SUMMARY installed nightly build 367 to fix dvd wizard/chapter issue; when exported vob, exporting as 4:3 STEPS TO REPRODUCE 1. render project x/16:9 as vob file in 19.12.3 2. render project x/16:9 as vob file in nightly build 367 3. compare files in DVDStyler; 19.12.3 renders as 16:9; 367 renders as 4:3 OBSERVED RESULT aspect ratio is 4:3 in DVD Styler EXPECTED RESULT aspect ratio is 16;9 in DVD Styler SOFTWARE/OS VERSIONS Windows: 10 macOS: n/a Linux/KDE Plasma: n/a (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION reinstalled 19.12.3 to fix the issue currently. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 --- Comment #6 from Nate Graham --- Yes, Breeze doesn't have stock_new-window.svg. We can create a symlink which will resolve the issue, but it's working around the preferred solution, which is for gnome-calendar to use the correct icon. I'm willing to add that symlink if the gnome-calendar developers refuse to fix the problem correctly on their end, but I would like if it you could try for that first. :) The Breeze icon theme does indeed have all of those weather icons though. I'm seeing them daily in my weather applet. :) So again I think there must be some issue with the GNOME app if it's not using the correct standardized icon names. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 397586] OSD to configure multi-monitor mode is not centered on the screen under Wayland
https://bugs.kde.org/show_bug.cgi?id=397586 Nate Graham changed: What|Removed |Added Version Fixed In||5.19.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420312] Dolphin services not being remove after uninstall
https://bugs.kde.org/show_bug.cgi?id=420312 Nate Graham changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |alex1701c@gmx.net Status|REPORTED|ASSIGNED CC||n...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420312] Dolphin services not being remove after uninstall
https://bugs.kde.org/show_bug.cgi?id=420312 --- Comment #2 from Alex --- https://phabricator.kde.org/D29101 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420427] crash when openning Team Viewer, or upon try to copy a flameshot image to clippboard, and when receive notifications on whatsapp (version with electron)
https://bugs.kde.org/show_bug.cgi?id=420427 phrazão changed: What|Removed |Added CC||phra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420427] New: crash when openning Team Viewer, or upon try to copy a flameshot image to clippboard, and when receive notifications on whatsapp (version with electron)
https://bugs.kde.org/show_bug.cgi?id=420427 Bug ID: 420427 Summary: crash when openning Team Viewer, or upon try to copy a flameshot image to clippboard, and when receive notifications on whatsapp (version with electron) Product: plasmashell Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: phra...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.4) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.3.0-46-generic x86_64 Windowing system: X11 Distribution: Feren OS -- Information about the crash: - What I was doing when the application crashed: this time was when openning Team Viewer, but it also crashes using flameshot or wathsapp. Since this upgrade from FerenOS, i lost completely the stability of the system, essencialy in the KDE... -- Backtrace (Reduced): #6 0x7ff07aeca2c5 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #7 0x7ff0a4f6a3ad in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7ff0a4f6a56b in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7ff0a4f21060 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7ff0a4f25785 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 Possible duplicates by query: bug 41, bug 418316, bug 418084, bug 416926, bug 416905. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420411] digiKam Crash on detect faces 7.0.0 beta3 debug build
https://bugs.kde.org/show_bug.cgi?id=420411 --- Comment #2 from Stefan S --- (In reply to caulier.gilles from comment #1) > >Personal notes: should not be doing work on main thread, that blocks the GUI > >- >can't open digiKam after it starts detecting. > > I don't understand this point : all long process are started in separated > thread under DK. > > Gilles Caulier They are not, at least not all of them, if you look at Thread 0:: CrBrowserMain Dispatch queue: com.apple.main-thread You are doing face detection on the main thread (thread 0) as far as i can see. And there other places in your code where everything is done on the main thread, like here: https://bugs.kde.org/show_bug.cgi?id=420334#c12 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420334] GUI hangs when adding a network folder
https://bugs.kde.org/show_bug.cgi?id=420334 Stefan S changed: What|Removed |Added Assignee|stefan.szeke...@gmail.com |digikam-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420423] HTML font size is affected by view zoom in composer
https://bugs.kde.org/show_bug.cgi?id=420423 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- Sdfsfdfdf sqdqs dqsdqsdqsdqsd q => 1.2em now. so it depends against zoom. it's fixed from long time ago. 5.9.3 is very old :) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 58647] Wrong accelerators specified in Info pages
https://bugs.kde.org/show_bug.cgi?id=58647 Shinjo Park changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #13 from Shinjo Park --- Given that the kdelibs is discontinued, I am going to report a new bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 397586] OSD to configure multi-monitor mode is not centered on the screen under Wayland
https://bugs.kde.org/show_bug.cgi?id=397586 Benjamin Port changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ksc ||reen/b3b45721ee17828d5711ff ||88d5f1777b65c2834a --- Comment #9 from Benjamin Port --- Git commit b3b45721ee17828d5711ff88d5f1777b65c2834a by Benjamin Port. Committed on 22/04/2020 at 15:03. Pushed by bport into branch 'master'. fix(kded): center action OSD on wayland Summary: Currently on Wayland the Action OSD is not centered on the screen. On Wayland we will center it on m_output (laptop, with fallback to primary and then to first one). X behavior is not changed. Reviewers: romangg, davidedmundson Reviewed By: romangg, davidedmundson Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28916 M +9-2kded/osd.cpp M +6-0kded/qml/OsdSelector.qml https://commits.kde.org/kscreen/b3b45721ee17828d5711ff88d5f1777b65c2834a -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414417] current splash screen is not highlighted after I set global theme to breeze dark
https://bugs.kde.org/show_bug.cgi?id=414417 Cyril Rossi changed: What|Removed |Added Version Fixed In||5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418698] Applying Global theme which use a widget style not installed, default still used but config refer to missing style
https://bugs.kde.org/show_bug.cgi?id=418698 Cyril Rossi changed: What|Removed |Added Version Fixed In||5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419552] No style is highlighted when a 3rd-party global theme with breeze style is used
https://bugs.kde.org/show_bug.cgi?id=419552 Cyril Rossi changed: What|Removed |Added Version Fixed In||5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419552] No style is highlighted when a 3rd-party global theme with breeze style is used
https://bugs.kde.org/show_bug.cgi?id=419552 Cyril Rossi changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/17ef374a8cc469a ||9eefc516fc4885cbbce0c0afc Resolution|DUPLICATE |FIXED --- Comment #3 from Cyril Rossi --- Git commit 17ef374a8cc469a9eefc516fc4885cbbce0c0afc by Cyril Rossi. Committed on 22/04/2020 at 14:39. Pushed by crossi into branch 'Plasma/5.18'. KCM LookAndFeel check widgetStyle availability before applying it Summary: Related: bug 418698 * Some Global Theme may refer to breeze widget style with a lower case b, apply the proper name `Breeze` * Some Global Theme use widget style that may not be installed, then don't apply it. Test Plan: * Open KCM LookAndFeel, open GHNS and install Qogir-light theme, then apply it. Open Application Style KCM, if kvantum is not installed, Breeze is highlighted. * Open KCM LookAndFeel, open GHNS and install Aritim-Light, then apply it. Open Application Style KCM, Breeze is highlighted. Reviewers: #plasma, ervin, bport, meven, ngraham Reviewed By: ervin, ngraham Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28662 M +17 -5kcms/lookandfeel/kcm.cpp https://commits.kde.org/plasma-desktop/17ef374a8cc469a9eefc516fc4885cbbce0c0afc -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414417] current splash screen is not highlighted after I set global theme to breeze dark
https://bugs.kde.org/show_bug.cgi?id=414417 Cyril Rossi changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-desktop/dacb3a8bdd206ec ||14a588bb25b37caa48c3b36aa --- Comment #3 from Cyril Rossi --- Git commit dacb3a8bdd206ec14a588bb25b37caa48c3b36aa by Cyril Rossi. Committed on 22/04/2020 at 14:43. Pushed by crossi into branch 'Plasma/5.18'. KCM LookAndFeel check if splash screen is provided before applying it. Summary: * While saving a new global theme, don't set splash screen if none is provided, leave the current one. * KSplash kcfg set default to breeze instead of the current lnf theme which may not contain a splash screen. Test Plan: * Open LookAndFeel KCM, apply Breeze Dark, then open Splash screen KCM, Breeze should be highlighted. * Open splash screen KCM, select none, click on defaults, Breeze should be selected. Reviewers: #plasma, ervin, bport, meven, ngraham Reviewed By: ervin, ngraham Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28656 M +1-4kcms/ksplash/splashscreensettings.kcfg M +4-1kcms/lookandfeel/kcm.cpp https://commits.kde.org/plasma-desktop/dacb3a8bdd206ec14a588bb25b37caa48c3b36aa -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418698] Applying Global theme which use a widget style not installed, default still used but config refer to missing style
https://bugs.kde.org/show_bug.cgi?id=418698 Cyril Rossi changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/17ef374a8cc469a ||9eefc516fc4885cbbce0c0afc --- Comment #3 from Cyril Rossi --- Git commit 17ef374a8cc469a9eefc516fc4885cbbce0c0afc by Cyril Rossi. Committed on 22/04/2020 at 14:39. Pushed by crossi into branch 'Plasma/5.18'. KCM LookAndFeel check widgetStyle availability before applying it Summary: Related: bug 419552 * Some Global Theme may refer to breeze widget style with a lower case b, apply the proper name `Breeze` * Some Global Theme use widget style that may not be installed, then don't apply it. Test Plan: * Open KCM LookAndFeel, open GHNS and install Qogir-light theme, then apply it. Open Application Style KCM, if kvantum is not installed, Breeze is highlighted. * Open KCM LookAndFeel, open GHNS and install Aritim-Light, then apply it. Open Application Style KCM, Breeze is highlighted. Reviewers: #plasma, ervin, bport, meven, ngraham Reviewed By: ervin, ngraham Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28662 M +17 -5kcms/lookandfeel/kcm.cpp https://commits.kde.org/plasma-desktop/17ef374a8cc469a9eefc516fc4885cbbce0c0afc -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 --- Comment #5 from Simon Gardet --- Sorry, I don't speak English very well, I must have misspoken... Actually it's the Breeze theme that doesn't have those icons. I only used the icon theme that worked best with this application to compare with Breeze and I was able to find the name that the breeze icon should have. Maybe there's a better way to find the name that I don't know about... The problem is not in adapta but it is in breeze. Unfortunately if the icon names are not standard anyway I doubt we can fix it. Anyway I've seen several similar cases in GTK CSD applications using Plasma with the Breeze theme. So maybe I'll file a bug report at Gnome. stock_new-window.svg although not standard is not the same as new-window.svg, it seems to be a variant so in my opinion it's certainly a choice, not to have respected the standard, that would come from Gnome for their CSD applications ... I don't know if I was understandable and thank you very much for your answers. And I hope that with these clarifications we can try some things, I remain vigilant to new messages. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420425] Calendar View of Portfolio
https://bugs.kde.org/show_bug.cgi?id=420425 Jack changed: What|Removed |Added Severity|normal |wishlist --- Comment #2 from Jack --- Are you proposing this for the past or the future? (I can imagine both, but the past would perhaps be a new form of report, and the future would likely be based on forecasts.) Are the little icons for each day based on the category? Where would they come from? -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 420426] New: Check and fixup for unused parameters
https://bugs.kde.org/show_bug.cgi?id=420426 Bug ID: 420426 Summary: Check and fixup for unused parameters Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: an...@familiesomers.nl CC: smart...@kde.org Target Milestone: --- There is a check for "non-trivial" unused parameters. I would like to propose a check and a fixup for all unused parameters. Use case: We had a project in which we have a mock object mocking a wide API, with lots of methods and lots of arguments for each of these. Most methods are unimplemented, but they sprayed the compile output with warnings. I commented out all the offending argument names, but it would have been nice to be able to quickly apply a fixup to them instead. Fixup could be either the commenting out, or perhaps inserting a Q_UNUSED() at the top of the implementation. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 419831] KDevelop sometimes hangs on exit
https://bugs.kde.org/show_bug.cgi?id=419831 --- Comment #1 from RJVB --- (drKonqi balks something about private attachments not being allowed when I try to upload the latest report, so here it is manually): Application: kdevelop (5.5.0-25-g0dda64acb3) (Compiled from sources) Qt Version: 5.9.8 Frameworks Version: 5.60.0 Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64 Windowing system: X11 Distribution: Ubuntu 14.04.6 LTS -- Information about the crash: - What I was doing when the application crashed: As the previous time, I quit KDevelop and a deadlock ensued after the languageController was cleaned up. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f42d08f0c80 (LWP 23120))] Thread 7 (Thread 0x7f42976fd700 (LWP 24412)): #0 0x7f42c729537d in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f42bdaeaa7f in g_wakeup_acknowledge (wakeup=0x7f4290002780) at gwakeup.c:210 #2 g_main_context_check (context=0x7f428c000990, max_priority=2147483647, fds=0x7f428c0013c0, n_fds=1) at gmain.c:3686 #3 0x7f42bdaeb7a6 in g_main_context_iterate (context=, block=, dispatch=, self=) at gmain.c:3905 #4 0x7f42bdaeba21 in g_main_context_iteration (context=0x7f428c000990, may_block=1) at gmain.c:3969 #5 0x7f42c80a4b7b in QEventDispatcherGlib::processEvents(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #6 0x7f42c804c5df in QEventLoop::exec(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #7 0x7f42c7e8c7b7 in QThread::exec() () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #8 0x7f42c7e8d946 in QThreadPrivate::start(void*) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #9 0x7f42c4793184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f42c72a403d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f429d9ed700 (LWP 24325)): #0 0x7f42c7296c9d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f42bdaeb761 in g_main_context_poll (priority=0, context=, timeout=, fds=, n_fds=) at gmain.c:4209 #2 g_main_context_iterate (context=, block=, dispatch=, self=) at gmain.c:3903 #3 0x7f42bdaeba21 in g_main_context_iteration (context=0x7f429990, may_block=1) at gmain.c:3969 #4 0x7f42c80a4b7b in QEventDispatcherGlib::processEvents(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #5 0x7f42c804c5df in QEventLoop::exec(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #6 0x7f42c7e8c7b7 in QThread::exec() () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #7 0x7f42c7e8d946 in QThreadPrivate::start(void*) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #8 0x7f42c4793184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f42c72a403d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f429e84e700 (LWP 24248)): #0 0x7f42c7296c9d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f42bdaeb761 in g_main_context_poll (priority=0, context=, timeout=, fds=, n_fds=) at gmain.c:4209 #2 g_main_context_iterate (context=, block=, dispatch=, self=) at gmain.c:3903 #3 0x7f42bdaeba21 in g_main_context_iteration (context=0x7f4298000990, may_block=1) at gmain.c:3969 #4 0x7f42c80a4b7b in QEventDispatcherGlib::processEvents(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #5 0x7f42c804c5df in QEventLoop::exec(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #6 0x7f42c7e8c7b7 in QThread::exec() () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #7 0x7f42cf246a2e in KDevelop::DUChainPrivate::CleanupThread::run (this=0x2cec140) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kf5-kdevelop/kf5-kdevelop-devel/work/kf5-kdevelop-5/kdevplatform/language/duchain/duchain.cpp:331 #8 0x7f42c7e8d946 in QThreadPrivate::start(void*) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #9 0x7f42c4793184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f42c72a403d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f42a014d700 (LWP 23759)): #0 0x7f42c4797404 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f42a0ddcb2b in cnd_wait (cond=, mtx=) at ../mesa-18.3.3/src/../include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=) at ../mesa-18.3.3/src/util/u_queue.c:270 #3 0x7f42a0ddd446 in impl_thrd_routine (p=) at ../mesa-18.3.3/src/../include/c11/threads_posix.h:87 #4 0x7f42c4793184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7f42c72a403d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f42b0b3f700 (LWP 23303)): #0 g_source_iter_next (iter=, source=) at gmain.c:982 #1 g_main_context_prepare (context=0x7f42a4000990,
[kmymoney] [Bug 420425] Calendar View of Portfolio
https://bugs.kde.org/show_bug.cgi?id=420425 --- Comment #1 from Suresh PB --- Created attachment 127773 --> https://bugs.kde.org/attachment.cgi?id=127773=edit Model from another app to give an idea -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 419831] KDevelop sometimes hangs on exit
https://bugs.kde.org/show_bug.cgi?id=419831 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420425] Calendar View of Portfolio
https://bugs.kde.org/show_bug.cgi?id=420425 Suresh PB changed: What|Removed |Added CC||spill...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420425] New: Calendar View of Portfolio
https://bugs.kde.org/show_bug.cgi?id=420425 Bug ID: 420425 Summary: Calendar View of Portfolio Product: kmymoney Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: spill...@gmail.com Target Milestone: --- SUMMARY KMymoney has data to display the daily, weekly, monthly view of summary of account(s) in calendar view. For example a monthly view could display Income/Expenses and Total (ie summary of the transaction) by every day in the view. Similarly, a weekly view would be a great differentiator. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420424] New: [enhancement] Provide feedback when unable to mount CryFS vault
https://bugs.kde.org/show_bug.cgi?id=420424 Bug ID: 420424 Summary: [enhancement] Provide feedback when unable to mount CryFS vault Product: Plasma Vault Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: frap...@gmail.com Target Milestone: --- SUMMARY When cryfs cannot mount a directory, the vault UI will simply not show anything, so the user has no idea what's happening. STEPS TO REPRODUCE 1. Create a test vault and unmount it 2. Remove one of its binary files (eg. rm -rf Test\ Vault.enc/A6D/713C83A158E9483F5385E96AC219E) 3. Try to mount the vault using the plasma vault UI OBSERVED RESULT The UI closes without any feedback, as if the vault was properly mounted, when in fact, it did not mount. Trying to mount it from CLI shows: $ cryfs Test\ Vault.enc/ test CryFS Version 0.9.9 Password: Loading config file (this can take some time)...done [2020-04-22 11:08:13.960] [Log] [error] Could not load blob A6D713C83A158E9483F5385E96AC219E. Is the base directory accessible? [2020-04-22 11:08:13.961] [Log] [error] Crashed: Input/output error EXPECTED RESULT The Plasma Vault UI should at the very least show this error, being very explicit that the vault was unable to be mounted. Ideally, it would be nice to also show some additional information, like: - Full path for the blob (In the example, it would be ~/Test\ Vault.enc/A6D/713C83A158E9483F5385E96AC219E) - Possible suggestions on what the cause could be (incorrect permissions? maybe a conflict resolution by a shared service such as Dropbox? Hardware issues? etc...) SOFTWARE/OS VERSIONS Windows: No macOS: No Linux/KDE Plasma: Yes (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420423] New: HTML font size is affected by view zoom in composer
https://bugs.kde.org/show_bug.cgi?id=420423
Bug ID: 420423
Summary: HTML font size is affected by view zoom in composer
Product: kmail2
Version: 5.9.3
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-b...@kde.org
Reporter: alejandro_a...@yahoo.es
Target Milestone: ---
First of all, i am not sure if this has already been fixed in more modern
versions of kmail (using Debian Stable here).
STEPS TO REPRODUCE
1. Compose an email in HTML mode with, let's say Noto Sans at 11 points of size
2. Make text bigger or smaller for viewing (Ctrl+Mouse scroll wheel, or
Ctrl+{,+})
3. Send message
4. Received message will have a font size proportional to the zoom you used
composing the message
It's also notable that when kmail receives emails composed like this (a CC for
yourself) the size of the text will appear normal so you won't notice but other
people with different emails clients will
In my mind, zoom of the text should be independent of the font size sent in the
HTML. But that's my two cents
OBSERVED RESULT
Example of the HTML code generated by the composer
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Stable 10.3
KDE Plasma Version: 5.14.5.1
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3+dfsg1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 420422] New: Indian Rupee has new symbol since 7 years,it is ₹
https://bugs.kde.org/show_bug.cgi?id=420422 Bug ID: 420422 Summary: Indian Rupee has new symbol since 7 years,it is ₹ Product: kmymoney Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: spill...@gmail.com Target Milestone: --- SUMMARY Indian Rupee has new symbol since 7 years,it is ₹ STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT Please change the symbol of Indian Rupee to ₹ SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION All versions need to change -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 420417] Crash of lokalize when changing to a new item
https://bugs.kde.org/show_bug.cgi?id=420417 --- Comment #1 from Simon Depiets --- That was a one-off right ? I think the project tree segfaults sometimes but I haven't been able to make it reproductible, so I'm very interested if you can. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DOWNSTREAM --- Comment #4 from Nate Graham --- > Okay, I was find !!! His name is stock_new-window.svg Aha! That's not a standard icon name, so it makes sense that we don't have it. This is a bug in the app itself; it should be using the correct standardized icon, which is "window-new" > I use Papirus Icons for the search (I don't know if is very well). Then you'll need to ask the maintainer of that icon theme to add the missing icons. Either way, not our bug. :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420421] New: Wish: Store log or notes with configuration
https://bugs.kde.org/show_bug.cgi?id=420421 Bug ID: 420421 Summary: Wish: Store log or notes with configuration Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: a...@al-williams.com Target Milestone: --- Here's the user story: The other day I was making some changes and thought, "Hmm.. I have compositing set to OpenGL 2 instead of 3. I can't remember if I just tried that to see if it fixed some other problem or if it actually fixed some problem." I knew the change had been long ago and several display drivers ago, so I turned it back on. Within a day I realized my system was crashing and turning it back to Open GL2 fixed that. So what would be a great feature is a field in each module that says "Notes" that gets persisted with the settings. Even just a simple "sticky note" format would be OK although bonus points if it were an accumulated time and date stamped log. The notes could be per module or one for all of systemsettings, it seems like. Either would work. So each module could have at the bottom a text field you could edit along with buttons "save note" and (if you are going to do the log-style) "view notes". >From the view you edit the entire log or erase it. If you just do a sticky note, you don't need the view button or any manipulation, so that would be easier. If you decide to do it for all settings this could be part of the kcmshell window instead of per module, but that would be a big change compared to how it is today, I think. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 420419] Failure to launch an "On Demand SideBar" from "Latte SideBar Button"
https://bugs.kde.org/show_bug.cgi?id=420419 --- Comment #3 from Ali Tajelsir --- (In reply to Michail Vourlakos from comment #1) > You can install SideBar button applet from its repo or wait for an updatefor > it in kde store - I can confirm that it's working after updating the "SideBar Button" to the git version. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402028] Setting shortcut keys to Ctrl+< or Ctrl+> breaks shortcuts for Ctrl+Z & Ctrl+X
https://bugs.kde.org/show_bug.cgi?id=402028 Ben Mayberry changed: What|Removed |Added CC||benmaybe...@live.com --- Comment #4 from Ben Mayberry --- Can confirm is still an issue on: Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-46-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420313] Night color location detection returns the wrong location
https://bugs.kde.org/show_bug.cgi?id=420313 --- Comment #4 from Nate Graham --- No worries! -- You are receiving this mail because: You are watching all bug changes.
