[okular] [Bug 410723] Freehand annotation jagged lines with stylus
https://bugs.kde.org/show_bug.cgi?id=410723 --- Comment #12 from Logan --- I managed to get the bug to reproduce on Ubuntu 18.04.3 with Okular(v1.8.1) on a separate machine with the same drawing tablet. I initially installed Okular with "sudo snap install Okular" to get the latest version and experienced the same bug. I was trying to install and use Okular on a computer that didn't have this error and decided to try to install an older version on the same machine (Ubuntu 18.04.3). I used "sudo apt install Okular" and it installed Okular(v1.3.3) and I did NOT experience the same bug! This was good news for me but I have no clue why it was happening. I uninstalled the snap version(v1.8.1) on my main computer(Ubuntu 19.04) and installed the apt version(v1.6.3). Obviously, the apt packages are maintained by the Ubuntu Developers (you can check with "apt show okular")and because my OS is on a later version, some of the packages are more updated as well. Okular happens to be one of them. On my main computer(Ubuntu 19.04), I experience the same annotation bug with Okular(v1.6.3). This leads me to believe that this bug occurs on Okular versions 1.6.3 and later. The bug may still occur on a number of earlier versions before Okular(v1.6.3) but I think that it would work fine with Okular(v1.3.3) if I were able to run it on Ubuntu (19.04). I tried to install Okular(v1.3.3) with "sudo apt install okular=1.3.3" but I received an error: "E: Version '1.3.3' for 'okular' was not found" meaning for whatever reason, version 1.3.3 was not available. There may be a way to install version 1.3.3 some other way but I don't quite know how to navigate Okular's website to install the older version. If I discover a way to install Okular(v1.3.3), I will report what happens. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408283] New icons for new Okular annotation toolbar
https://bugs.kde.org/show_bug.cgi?id=408283 --- Comment #10 from Simone Gaiarin --- Great, we have the first new icon! Thanks I realized that two more icons are needed. - Line width icon (see attachments "Okular line width menu" for where it will be used and "Line width icon" for how I imagine the icon more or less) - Opacity icon (see attachment "Okular opacity menu" for where it will be used) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408283] New icons for new Okular annotation toolbar
https://bugs.kde.org/show_bug.cgi?id=408283 --- Comment #9 from Simone Gaiarin --- Created attachment 122899 --> https://bugs.kde.org/attachment.cgi?id=122899=edit Line width icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408283] New icons for new Okular annotation toolbar
https://bugs.kde.org/show_bug.cgi?id=408283 Simone Gaiarin changed: What|Removed |Added Attachment #122897|0 |1 is obsolete|| --- Comment #8 from Simone Gaiarin --- Created attachment 122898 --> https://bugs.kde.org/attachment.cgi?id=122898=edit Okular opacity menu -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408283] New icons for new Okular annotation toolbar
https://bugs.kde.org/show_bug.cgi?id=408283 --- Comment #7 from Simone Gaiarin --- Created attachment 122897 --> https://bugs.kde.org/attachment.cgi?id=122897=edit Okular opacity menu -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408283] New icons for new Okular annotation toolbar
https://bugs.kde.org/show_bug.cgi?id=408283 --- Comment #6 from Simone Gaiarin --- Created attachment 122896 --> https://bugs.kde.org/attachment.cgi?id=122896=edit Okular line width menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412389] New: Random plasma crash
https://bugs.kde.org/show_bug.cgi?id=412389 Bug ID: 412389 Summary: Random plasma crash Product: plasmashell Version: 5.16.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@mva.name CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.4) (Compiled from sources) Qt Version: 5.12.4 Frameworks Version: 5.61.0 Operating System: Linux 5.2.10 x86_64 Distribution: "Gentoo GNU/Linux" -- Information about the crash: - What I was doing when the application crashed: Nothing related to plasma at all. Crash happened when I called `vim` as `vim ~/.password-store/Chrome/.gpg-id` in Yakuake. Well, I though, it can be related to plasma-pass plasmoid, but no, plasma doesn't crash again in the same situation. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81d525d880 (LWP 676553))] Thread 16 (Thread 0x7f81ba6cf700 (LWP 946624)): #0 0x7f81dae43f85 in pthread_cond_wait () at /lib64/libpthread.so.0 #1 0x7f81dbd7cd73 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f81dbd7cdf9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f81ddaa4d49 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #4 0x7f81ddaa4fed in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #5 0x7f81dbd77752 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #6 0x7f81dae3d42a in start_thread () at /lib64/libpthread.so.0 #7 0x7f81dba1043f in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f818772d700 (LWP 381622)): #0 0x7f81dae43f85 in pthread_cond_wait () at /lib64/libpthread.so.0 #1 0x7f81dbd7cd73 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f81dbd7cdf9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f81ddaa4d49 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #4 0x7f81ddaa4fed in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #5 0x7f81dbd77752 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #6 0x7f81dae3d42a in start_thread () at /lib64/libpthread.so.0 #7 0x7f81dba1043f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f81a91f2700 (LWP 512576)): #0 0x7f81dae43f85 in pthread_cond_wait () at /lib64/libpthread.so.0 #1 0x7f81dbd7cd73 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f81dbd7cdf9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f81ddaa4d49 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #4 0x7f81ddaa4fed in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #5 0x7f81dbd77752 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #6 0x7f81dae3d42a in start_thread () at /lib64/libpthread.so.0 #7 0x7f81dba1043f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f8192de0700 (LWP 512575)): #0 0x7f81dba04473 in poll () at /lib64/libc.so.6 #1 0x7f81d8a54142 in poll_func () at /usr/lib64/libpulse.so.0 #2 0x7f81d8a45909 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f81d8a45f8f in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f81d8a46040 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f81d8a54089 in thread () at /usr/lib64/libpulse.so.0 #6 0x7f81d5ee8688 in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #7 0x7f81dae3d42a in start_thread () at /lib64/libpthread.so.0 #8 0x7f81dba1043f in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f81a87ae700 (LWP 482618)): #0 0x7f81dae43f85 in pthread_cond_wait () at /lib64/libpthread.so.0 #1 0x7f81dbd7cd73 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f81dbd7cdf9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f81ddaa4d49 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #4 0x7f81ddaa4fed in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #5 0x7f81dbd77752 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #6 0x7f81dae3d42a in start_thread () at /lib64/libpthread.so.0 #7 0x7f81dba1043f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f813766e700 (LWP 477336)): #0 0x7f81dae43f85 in pthread_cond_wait () at /lib64/libpthread.so.0 #1
[krita] [Bug 412364] Audio doesn't play (OSX)
https://bugs.kde.org/show_bug.cgi?id=412364 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 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.
[krita] [Bug 411390] After image inversion, krita is crashed.
https://bugs.kde.org/show_bug.cgi?id=411390 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412278] Assertion failure when trying to open a specific kra document
https://bugs.kde.org/show_bug.cgi?id=412278 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- 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.
[krita] [Bug 408089] The window is semi-transparent when using opengl instead of angle
https://bugs.kde.org/show_bug.cgi?id=408089 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #16 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411754] Dolphin crash when opening pdf file with Okular
https://bugs.kde.org/show_bug.cgi?id=411754 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411718] Dolphin shows the wrong file type for Python
https://bugs.kde.org/show_bug.cgi?id=411718 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412211] Night Color Always On using Auto or Location
https://bugs.kde.org/show_bug.cgi?id=412211 --- Comment #18 from Samantha --- Icon theme "gnome" not found. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2) OpenGL version string: 4.5 (Core Profile) Mesa 19.1.7 OpenGL shading language version string: 4.50 Driver: Intel GPU class: Unknown OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 19.1.7 X server version: 1.20.5 Linux kernel version: 5.2.14 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_colorcorrection: Received new location (lat: 49.00, lng: -122.00) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412365] Reset Rotation visible on welcome page, clicking causes sefgault
https://bugs.kde.org/show_bug.cgi?id=412365 Ahab Greybeard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- I can confirm this for the #634 Sep 26 4.3.0-prealpha (git 3330d7e) appimage. It is not present in the previous nightly build. When I open a file or create a new file, the button stays and is then moved to be to the right of the selection indicator button and it does wwork to reset rotation. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406955] Switching profile does not update KONSOLE_PROFILE_NAME environment variable
https://bugs.kde.org/show_bug.cgi?id=406955 Kurt Hindenburg changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||konsole/commit/9e3a30fdca20 ||78e04bee2315ebd2adf678a8126 ||3 --- Comment #7 from Kurt Hindenburg --- Git commit 9e3a30fdca2078e04bee2315ebd2adf678a81263 by Kurt Hindenburg. Committed on 27/09/2019 at 02:24. Pushed by hindenburg into branch 'master'. Remove env variable KONSOLE_PROFILE_NAME env variables can not be changed after process creation so this causes this variable to be wrong after profile switching. Use the dbus method profile to determine name. qdbus $KONSOLE_DBUS_SERVICE $KONSOLE_DBUS_SESSION profile M +0-1src/SessionManager.cpp https://invent.kde.org/kde/konsole/commit/9e3a30fdca2078e04bee2315ebd2adf678a81263 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406955] Switching profile does not update KONSOLE_PROFILE_NAME environment variable
https://bugs.kde.org/show_bug.cgi?id=406955 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon |konsole/commit/9e3a30fdca20 |sole/9e3a30fdca2078e04bee23 |78e04bee2315ebd2adf678a8126 |15ebd2adf678a81263 |3 | --- Comment #8 from Kurt Hindenburg --- Git commit 9e3a30fdca2078e04bee2315ebd2adf678a81263 by Kurt Hindenburg. Committed on 27/09/2019 at 02:24. Pushed by scmsync into branch 'master'. Remove env variable KONSOLE_PROFILE_NAME env variables can not be changed after process creation so this causes this variable to be wrong after profile switching. Use the dbus method profile to determine name. qdbus $KONSOLE_DBUS_SERVICE $KONSOLE_DBUS_SESSION profile M +0-1src/SessionManager.cpp https://commits.kde.org/konsole/9e3a30fdca2078e04bee2315ebd2adf678a81263 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412278] Assertion failure when trying to open a specific kra document
https://bugs.kde.org/show_bug.cgi?id=412278 --- Comment #3 from Andrei Alexeyev --- Created attachment 122895 --> https://bugs.kde.org/attachment.cgi?id=122895=edit Stack trace (v4.3.0-prealpha-451-g9894a20269) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412278] Assertion failure when trying to open a specific kra document
https://bugs.kde.org/show_bug.cgi?id=412278 --- Comment #2 from Andrei Alexeyev --- I've built Krita from master the other day (v4.3.0-prealpha-451-g9894a20269), and unfortunately the crash still persists. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406955] Switching profile does not update KONSOLE_PROFILE_NAME environment variable
https://bugs.kde.org/show_bug.cgi?id=406955 --- Comment #5 from Kurt Hindenburg --- Git commit 05f5663a90106ee8ddcff024c9b30b2b8f1e0f4f by Kurt Hindenburg. Committed on 27/09/2019 at 02:12. Pushed by hindenburg into branch 'master'. Add dbus profile() to return profile name of current session Instead of relying on env variable KONSOLE_PROFILE_NAME, which is invalid upon switching profiles, use a dbus method profile(). qdbus $KONSOLE_DBUS_SERVICE $KONSOLE_DBUS_SESSION profile M +4-0src/Session.cpp M +5-0src/Session.h https://invent.kde.org/kde/konsole/commit/05f5663a90106ee8ddcff024c9b30b2b8f1e0f4f -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406955] Switching profile does not update KONSOLE_PROFILE_NAME environment variable
https://bugs.kde.org/show_bug.cgi?id=406955 --- Comment #6 from Kurt Hindenburg --- Git commit 05f5663a90106ee8ddcff024c9b30b2b8f1e0f4f by Kurt Hindenburg. Committed on 27/09/2019 at 02:12. Pushed by scmsync into branch 'master'. Add dbus profile() to return profile name of current session Instead of relying on env variable KONSOLE_PROFILE_NAME, which is invalid upon switching profiles, use a dbus method profile(). qdbus $KONSOLE_DBUS_SERVICE $KONSOLE_DBUS_SESSION profile M +4-0src/Session.cpp M +5-0src/Session.h https://commits.kde.org/konsole/05f5663a90106ee8ddcff024c9b30b2b8f1e0f4f -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 408797] kinit crashes when I close Dolphin while it shows the content of an audio CD
https://bugs.kde.org/show_bug.cgi?id=408797 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kio ||/2c379fecccbf5e2c0b20a93c84 ||3c009f2f597318 --- Comment #14 from David Faure --- Git commit 2c379fecccbf5e2c0b20a93c843c009f2f597318 by David Faure. Committed on 27/09/2019 at 00:56. Pushed by dfaure into branch 'master'. Fix crash on exit in kio_file Summary: All QTextCodec are deleted by QCoreGlobalData on exit, so they must be allocated on the heap. Before Qt 5.12, it is even not allowed to delete them. Reviewers: cfeck, dfaure, broulik Reviewed By: dfaure Subscribers: aacid, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D24150 M +2-1src/ioslaves/file/file.cpp https://commits.kde.org/kio/2c379fecccbf5e2c0b20a93c843c009f2f597318 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412295] Assert on font settings
https://bugs.kde.org/show_bug.cgi?id=412295 --- Comment #1 from Kurt Hindenburg --- It looks like you compiled Qt yourself - I would guess a Qt bug? #10 0x7f141590dc13 in qt_assert_x (where=0x7f14166d6fe0 "QFont::setWeight", what=0x7f14166d6fc0 "Weight must be between 0 and 99", file=0x7f14166d6e38 "/home/david/projects/qt5/qtbase/src/gui/text/qfont.cpp", line=1097) at /home/david/projects/qt5/qtbase/src/corelib/global/qglobal.cpp:3310 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412388] Freeze whenever editing existing text
https://bugs.kde.org/show_bug.cgi?id=412388 --- Comment #1 from Andrew --- Created attachment 122894 --> https://bugs.kde.org/attachment.cgi?id=122894=edit system info -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412388] New: Freeze whenever editing existing text
https://bugs.kde.org/show_bug.cgi?id=412388 Bug ID: 412388 Summary: Freeze whenever editing existing text Product: krita Version: 4.2.6 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: ct5h...@gmail.com Target Milestone: --- Created attachment 122893 --> https://bugs.kde.org/attachment.cgi?id=122893=edit .kra I'm having issues editing text in attached SUMMARY Whenever I edit an existing text to add (what appears to be) too many lines of text, Krita becomes unresponsive/freezes. It doesn't crash so I've been unable to get a crashlog. STEPS TO REPRODUCE 1. Edit existing text box inside the layer I've titled "Text body" to contain 9 separate lines of text. (3 lines are already present, copying and pasting them to take up 9 lines reproduced the freeze.) OBSERVED RESULT Non-Responsive / Frozen EXPECTED RESULT Updated text and no freeze. SOFTWARE/OS VERSIONS Windows: 10 (Home) 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.
[neon] [Bug 412387] New: The snap app does not respect the global theme
https://bugs.kde.org/show_bug.cgi?id=412387 Bug ID: 412387 Summary: The snap app does not respect the global theme Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: neon-b...@kde.org Reporter: newmrde...@gmail.com CC: neon-b...@kde.org Target Milestone: --- SUMMARY Setting Breeze Dark global theme doesn't affect the Okular snap app. 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.
[krita] [Bug 412364] Audio doesn't play (OSX)
https://bugs.kde.org/show_bug.cgi?id=412364 --- Comment #2 from Scott Petrovic --- They said they were going to come back on later to maybe provide more info. What type of information would be helpful for diagnosing this? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 412386] New: Krunner crashed when selecten open window
https://bugs.kde.org/show_bug.cgi?id=412386 Bug ID: 412386 Summary: Krunner crashed when selecten open window Product: krunner Version: 5.16.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: szymon.ug...@hotmail.com Target Milestone: --- Application: krunner (5.16.90) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.1-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I was reading website in Firefox and my song in spotify changed so I opened krunner and searched for spotify then selected spotify under open windows section. After selecting entry in krunner from `windows` section, nothing happens, then after about 5 secs notification appears that says that krunner crashed. The crash can be reproduced every time. -- Backtrace (Reduced): #6 0x7f4fa3d8e8bb in KWindowInfo::KWindowInfo(KWindowInfo const&) () at /usr/lib/libKF5WindowSystem.so.5 #7 0x7f4f9751088f in () at /usr/lib/qt/plugins/krunner_windows.so #8 0x7f4f8ee1b0f1 in Plasma::RunnerContext::run(Plasma::QueryMatch const&) () at /usr/lib/libKF5Runner.so.5 #9 0x7f4f8ee207a7 in Plasma::RunnerManager::run(Plasma::QueryMatch const&) () at /usr/lib/libKF5Runner.so.5 #10 0x7f4f8ee8e173 in () at /usr/lib/libmilou.so.5 The reporter indicates this bug may be a duplicate of or related to bug 412109. Possible duplicates by query: bug 412381, bug 412300, bug 412296, bug 412218, bug 412123. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 400725] Select application should not run first app from multiple choice
https://bugs.kde.org/show_bug.cgi?id=400725 --- Comment #7 from Ahmad Samir --- Ah, OK, I see your point now. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 412172] garbled display of multiple toolbars in DrKonqi
https://bugs.kde.org/show_bug.cgi?id=412172 --- Comment #2 from skierpage --- (In reply to Harald Sitter from comment #1) > Please file a bug report with your distribution for further investigation. Done, https://bugzilla.redhat.com/show_bug.cgi?id=1756150 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 412385] New: Focus lost when editing tab name
https://bugs.kde.org/show_bug.cgi?id=412385 Bug ID: 412385 Summary: Focus lost when editing tab name Product: yakuake Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: sgmo...@kde.org Target Milestone: --- Package: yakuake Version: 19.08.0-1 Severity: normal Dear Maintainer, since the update to yakuake 19.08, when I rename a tab, the focus is lost. Steps to reproduce: 1. Open Yakuake. Observe: typing inserts characters into the shell. 2. Press the shortcut to rename a tab. By default, that is Ctrl+Alt+S. I mapped it to Shift+F2, and reproduced the problem with either setting. Double-clicking the tab name works as well. 3. Press Enter to submit the new tab name (this is sufficient to demonstrate. In a realistic example, one likely wants to actually change the name.) 4. Type a character, e.g. x Expected (and previous) behavior: the character got typed into the shell. Current behavior: The focus is on some other element; typing does nothing. Workaround: Press Shift+Tab after renaming. Alternative workaround: Click into the terminal window after renaming. This is not a good experience, especially if you rename your tabs quite often, as I do. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yakuake depends on: ii kio5.54.1-1 ii konsole-kpart 4:19.08.0-1 ii libc6 2.28-10 ii libkf5archive5 5.54.0-1 ii libkf5configcore5 5.54.0-2 ii libkf5configgui5 5.54.0-2 ii libkf5configwidgets5 5.54.0-1 ii libkf5coreaddons5 5.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons5 5.54.0-1 ii libkf5globalaccel-bin 5.54.0-1 ii libkf5globalaccel5 5.54.0-1 ii libkf5i18n55.54.0-1 ii libkf5iconthemes5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5newstuff55.54.0-2 ii libkf5newstuffcore55.54.0-2 ii libkf5notifications5 5.54.0-1 ii libkf5notifyconfig55.54.0-1 ii libkf5parts5 5.54.0-1 ii libkf5service-bin 5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5waylandclient5 4:5.54.0-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem55.54.0-1 ii libkf5xmlgui5 5.54.0-1 ii libqt5core5a 5.11.3+dfsg1-4 ii libqt5dbus55.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5widgets5 5.11.3+dfsg1-4 ii libqt5x11extras5 5.11.3-2 ii libstdc++6 9.2.1-6 ii libx11-6 2:1.6.7-1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412374] KRA (Krita) files thumbnails not rendered
https://bugs.kde.org/show_bug.cgi?id=412374 --- Comment #5 from Rafael Linux User --- OpenSUSE 15.1 (not rolling release) https://fromsmash.com/JyilSKoV_0-c0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412374] KRA (Krita) files thumbnails not rendered
https://bugs.kde.org/show_bug.cgi?id=412374 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #4 from Maik Qualmann --- KRA files work here under openSUSE Tumbleweed and the current developer version without problems. The KRA files are processed by the QImage loader. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412384] New: insufficient installation documentation
https://bugs.kde.org/show_bug.cgi?id=412384 Bug ID: 412384 Summary: insufficient installation documentation Product: kmymoney Version: unspecified Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: documentation Assignee: kmymoney-de...@kde.org Reporter: steve.61...@gmail.com Target Milestone: --- SUMMARY no information is provided to find A) a compiled version of kMyMoney for the Mac; or B) simple complete instructions on how to compile your software for a non-Unix programmer. STEPS TO REPRODUCE 1. goto kmymoney.org. On the right click DOWNLOAD, find pc versions. Wonder WTF. 2. hit back arrow. select MACOS under preview versions. Wonder WTF? 3. ht back arrow. click on 4.7.2 for your Mac under macport. Download macports. Find no documentation on what it is or how to use it: all documentation assumes you already know. 4. find another site that has a tar file to download (sourceforge). Download and decompress files. Wonder why you have to do all this work, when the pc version downloads and runs, just like a normal program, not a f...g project. 5. read the README files. discover they too are written for unix programmers. open Terminal. type in a few of the commands. get "program not found". Quit in frustration. OBSERVED RESULT find a sludge of files, none of which run as kMyMoney. EXPECTED RESULT Find a usable alternative to Quicken. SOFTWARE/OS VERSIONS Windows: macOS: 10.14.6 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.
[digikam] [Bug 412374] KRA (Krita) files thumbnails not rendered
https://bugs.kde.org/show_bug.cgi?id=412374 Rafael Linux User changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #3 from Rafael Linux User --- (In reply to caulier.gilles from comment #1) > The KRA file are at least visible in icon view with a default icon ? Yes, that is, icon is visible cause you included KRA in default mime types on latest versions of Digikam (thanks for that and for add SVG too). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 399388] IncludeRules breaks dynamic RegExpr matching
https://bugs.kde.org/show_bug.cgi?id=399388 Jonathan Poelen changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/syn ||tax-highlighting/d6b1e02ad4 ||da168755df693bca379937ce618 ||f13 Resolution|--- |FIXED --- Comment #1 from Jonathan Poelen --- Git commit d6b1e02ad4da168755df693bca379937ce618f13 by Jonathan Poelen. Committed on 26/09/2019 at 21:03. Pushed by jpoelen into branch 'master'. Fix skipOffset with dynamic RegExpr Summary: The pattern used depends on the previous contexts so skipOffset cannot be computed with a dynamic regex. Reviewers: #framework_syntax_highlighting, dhaumann, cullmann Reviewed By: #framework_syntax_highlighting, cullmann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D24179 A +2-0autotests/folding/d399388_dynamic_RegExpr.dyInclRl.fold A +9-0autotests/html/d399388_dynamic_RegExpr.dyInclRl.html A +2-0autotests/input/d399388_dynamic_RegExpr.dyInclRl A +40 -0autotests/input/syntax/d399388_dynamic_RegExpr.xml A +2-0autotests/reference/d399388_dynamic_RegExpr.dyInclRl.ref M +3-1src/lib/rule.cpp https://commits.kde.org/syntax-highlighting/d6b1e02ad4da168755df693bca379937ce618f13 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412383] Krita No Global menu and Crash when closed
https://bugs.kde.org/show_bug.cgi?id=412383 --- Comment #2 from Boudewijn Rempt --- To be more exact: the crash on closing krita is a bug in Qt 5.13, the issue with the global menu is an issue with the distribution. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412383] Krita No Global menu and Crash when closed
https://bugs.kde.org/show_bug.cgi?id=412383 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Boudewijn Rempt --- Please complain to the distribution; this is something we just cannot fix because it's all downstream. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412383] New: Krita No Global menu and Crash when closed
https://bugs.kde.org/show_bug.cgi?id=412383 Bug ID: 412383 Summary: Krita No Global menu and Crash when closed Product: krita Version: 4.2.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: dandyoctav...@gmail.com Target Milestone: --- Created attachment 122891 --> https://bugs.kde.org/attachment.cgi?id=122891=edit Krita reported crashed when close SUMMARY When running Krita, Global Menu Dissapear. then, closed Krita dr konqi says "Krita Crashed" STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Manjaro Linux 18.1.0 (Kernel 5.1.21-1) (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412313] Duplicate entries on the Project View
https://bugs.kde.org/show_bug.cgi?id=412313 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- Is this some project with sub-modules? Then this should be fixed with: Author: Christoph Cullmann 2019-04-07 13:42:02 Committer: Christoph Cullmann 2019-04-08 06:57:10 Parent: ae04ae91e886d035a4b081b4471421d5a1abf00b ([kateproject] Gracefully exit when analyzer is not finished) Child: 36b9beaa605fd8ba9f27680d53ab4304f10838ac (improve comment) Branches: master, remotes/origin/Applications/19.04, remotes/origin/Applications/19.08, remotes/origin/expose-show-plugin-config-page, remotes/origin/external-tools-toolbar, remotes/origin/fix-dual-screen-hidpi, remotes/origin/lsp, remotes/origin/master, remotes/origin/remove-deprecated-plugins, remotes/origin/revive-externaltools-plugin Follows: v19.03.90 Precedes: v19.04.0 fix handling of sub modules in git rely on ls-files --recurse-submodules, there since end of 2016 Summary: before this fix, submodules lead to duplicate files in the file tree for a project Test Plan: test e.g. https://github.com/christoph-cullmann/cullmann.io without patch: duplicated files, missing sub-modules with patch: no duplicates + sub-module files are there Subscribers: kwrite-devel Tags: #kate Differential Revision: https://phabricator.kde.org/D20343 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412358] lsp client messages from ui file are not extracted
https://bugs.kde.org/show_bug.cgi?id=412358 Christoph Cullmann changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kat |kate/commit/0853456192e9cda |e/0853456192e9cda7a8234301b |7a8234301b96c34c609a4fd11 |96c34c609a4fd11 --- Comment #3 from Christoph Cullmann --- Git commit 0853456192e9cda7a8234301b96c34c609a4fd11 by Christoph Cullmann. Committed on 26/09/2019 at 20:35. Pushed by scmsync into branch 'master'. fix message extraction M +1-1addons/lspclient/Messages.sh https://commits.kde.org/kate/0853456192e9cda7a8234301b96c34c609a4fd11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412358] lsp client messages from ui file are not extracted
https://bugs.kde.org/show_bug.cgi?id=412358 Christoph Cullmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||kate/commit/0853456192e9cda ||7a8234301b96c34c609a4fd11 Status|ASSIGNED|RESOLVED --- Comment #2 from Christoph Cullmann --- Git commit 0853456192e9cda7a8234301b96c34c609a4fd11 by Christoph Cullmann. Committed on 26/09/2019 at 20:35. Pushed by cullmann into branch 'master'. fix message extraction M +1-1addons/lspclient/Messages.sh https://invent.kde.org/kde/kate/commit/0853456192e9cda7a8234301b96c34c609a4fd11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412358] lsp client messages from ui file are not extracted
https://bugs.kde.org/show_bug.cgi?id=412358 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- Thanks for patch! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412382] New: Kwin Crash when minimized window with Magic Lamp effects
https://bugs.kde.org/show_bug.cgi?id=412382 Bug ID: 412382 Summary: Kwin Crash when minimized window with Magic Lamp effects Product: kwin Version: 5.16.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: dandyoctav...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.4) Qt Version: 5.13.0 Frameworks Version: 5.61.0 Operating System: Linux 5.1.21-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Minimize a window and move to corner (desktop grid) then showing popup from dr konqi and says "kwin is crashed" - Custom settings of the application: When kwin using magic lamp effect minimize The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fce0db5cd00 (LWP 1165))] Thread 9 (Thread 0x7fce05308700 (LWP 4616)): #0 0x7fce15d63415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fce147685a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fce14768692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fce1341b7bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fce1341ba6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7fce14762520 in () at /usr/lib/libQt5Core.so.5 #6 0x7fce15d5d57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fce15e760e3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fcdf6c10700 (LWP 4615)): #0 0x7fce15e6b756 in ppoll () at /usr/lib/libc.so.6 #1 0x7fce14983913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fce14984fa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fce1492e5ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fce147612f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fce130838f9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fce14762520 in () at /usr/lib/libQt5Core.so.5 #7 0x7fce15d5d57f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fce15e760e3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fce06dee700 (LWP 1456)): #0 0x7fce15e6b756 in ppoll () at /usr/lib/libc.so.6 #1 0x7fce14983913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fce14984fa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fce1492e5ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fce147612f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fce130838f9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fce14762520 in () at /usr/lib/libQt5Core.so.5 #7 0x7fce15d5d57f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fce15e760e3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fcdf640f700 (LWP 1342)): #0 0x7fce15d63415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fce141eaedc in () at /usr/lib/libQt5Script.so.5 #2 0x7fce141eaef9 in () at /usr/lib/libQt5Script.so.5 #3 0x7fce15d5d57f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fce15e760e3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fcdf7411700 (LWP 1292)): #0 0x7fce15d63415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcdf757bf8c in () at /usr/lib/dri/i965_dri.so #2 0x7fcdf757bb88 in () at /usr/lib/dri/i965_dri.so #3 0x7fce15d5d57f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fce15e760e3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fce06549700 (LWP 1285)): #0 0x7fce15e6b756 in ppoll () at /usr/lib/libc.so.6 #1 0x7fce14983913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fce14984fa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fce1492e5ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fce147612f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fce130838f9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fce14762520 in () at /usr/lib/libQt5Core.so.5 #7 0x7fce15d5d57f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fce15e760e3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fce07fff700 (LWP 1180)): #0 0x7fce15e6b756 in ppoll () at /usr/lib/libc.so.6 #1 0x7fce14983913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fce14984fa3 in
[kate] [Bug 412351] Kate fills 100% of tmpfs /tmp folder
https://bugs.kde.org/show_bug.cgi?id=412351 --- Comment #8 from Christoph Cullmann --- Hmm, have you ctags installed? (e.g. is there some ctags binary in the path) Could you try if some "ctags" process is running during that fill-up phase? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412351] Kate fills 100% of tmpfs /tmp folder
https://bugs.kde.org/show_bug.cgi?id=412351 --- Comment #7 from Clara --- (In reply to Christoph Cullmann from comment #6) > Ok, no problem ;=) Thanks! :D > Can you check that the project plugin is really off? Per default it is on. > > It might try to create some large ctags file or such stuff if it detects > some project. D'oh sorry, I didn't realized it was on per default. Disabling it seems to fix the issue. I will post back if it reappears. I started using Git a few weeks ago and I also used Subversion for a long time so maybe the issue is related. Thank you again :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409957] Adjust the size of kickoff settings window to unhide the tip on bottom
https://bugs.kde.org/show_bug.cgi?id=409957
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest Commit||https://commits.kde.org/pla
||sma-desktop/184f2a8274dc387
||86a0ca3cb22f49e1a2d688aae
Resolution|--- |FIXED
Version Fixed In||5.17.0
--- Comment #2 from Nate Graham ---
Git commit 184f2a8274dc38786a0ca3cb22f49e1a2d688aae by Nate Graham.
Committed on 26/09/2019 at 20:18.
Pushed by ngraham into branch 'Plasma/5.17'.
[applets/kickoff] Improve appearance of draggable button grid in settings
window
Summary:
The button grid was not centered, the content inside the buttons was not
centered, the
vertical spacing was too high on top and too low on bottom, and the explanatory
text
got cut off.
This patch solves all those problems.
Big thanks to @davidedmundson for his help getting this merge-ready.
FIXED-IN: 5.17.0
Test Plan:
Before: {F7247447, size=full}
After: {F7247446, size=full}
Reviewers: #vdg, #plasma, davidedmundson, GB_2, hein
Reviewed By: #vdg, #plasma, davidedmundson, GB_2
Subscribers: hein, GB_2, davidedmundson, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D23158
M +13 -10 applets/kickoff/package/contents/ui/ConfigButtons.qml
M +5-6applets/kickoff/package/contents/ui/ConfigGeneral.qml
M +20 -19
applets/kickoff/package/contents/ui/KickoffConfigurationButton.qml
https://commits.kde.org/plasma-desktop/184f2a8274dc38786a0ca3cb22f49e1a2d688aae
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 411510] No Label Selection doesn't filter out colored layers label
https://bugs.kde.org/show_bug.cgi?id=411510 Tymond changed: What|Removed |Added Severity|normal |wishlist Assignee|tamtamy.tym...@gmail.com|krita-bugs-n...@kde.org --- Comment #12 from Tymond --- It is possible to set colors to both transparency and filter masks. If you start by setting a color for a parent layer, it will set it to all the children, which is consistent with group layers behaviour. It is possible to change it in the child too, though. (Marking as wishlist importance (as a wish to add the depth option) and unassigning myself.) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412381] New: KMyMoney Import CSV
https://bugs.kde.org/show_bug.cgi?id=412381 Bug ID: 412381 Summary: KMyMoney Import CSV Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ppelita...@gmail.com Target Milestone: --- Application: kmymoney (5.0.7) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: If I start importing from a csv file and then go back and choose another or even the same file the application crashes after a couple of "Next Next"... The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f207de7c980 (LWP 4985))] Thread 7 (Thread 0x7f1feef88700 (LWP 5012)): #0 0x7f2075f370b4 in __GI___libc_read (fd=27, buf=0x7f1feef87a5e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f1ff3b55021 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f1ff3dd3a2e in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f1ff3dd44a0 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f1ff3dd4560 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f1ff3de23c9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f1ff3b84318 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f206daa16db in start_thread (arg=0x7f1feef88700) at pthread_create.c:463 #8 0x7f2075f4888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f1ffb9ff700 (LWP 4991)): #0 0x7f2075f370b4 in __GI___libc_read (fd=18, buf=0x7f1ffb9fea10, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f206bb612d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f206bb1c0b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f206bb1c570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f206bb1c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2076e34dcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2076dd603a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2076bfd4ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2076bfec72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f206daa16db in start_thread (arg=0x7f1ffb9ff700) at pthread_create.c:463 #10 0x7f2075f4888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f20013ff700 (LWP 4990)): #0 0x7f2075f370b4 in __GI___libc_read (fd=11, buf=0x7f20013fea10, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f206bb612d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f206bb1c0b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f206bb1c570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f206bb1c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2076e34dcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2076dd603a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2076bfd4ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2076bfec72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f206daa16db in start_thread (arg=0x7f20013ff700) at pthread_create.c:463 #10 0x7f2075f4888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f205a3fc700 (LWP 4988)): #0 0x7f2075f3bbf9 in __GI___poll (fds=0x7f204c0136c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f206bb1c5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f206bb1c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2076e34dcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2076dd603a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2076bfd4ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f20772a3015 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f2076bfec72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f206daa16db in start_thread (arg=0x7f205a3fc700) at
[frameworks-kparts] [Bug 412380] New: Files of type application can no longer be embedded in kpart/konqueror
https://bugs.kde.org/show_bug.cgi?id=412380 Bug ID: 412380 Summary: Files of type application can no longer be embedded in kpart/konqueror Product: frameworks-kparts Version: 5.62.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: eseb...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 122890 --> https://bugs.kde.org/attachment.cgi?id=122890=edit Screenshot STEPS TO REPRODUCE 1. Click a file of type application (javascript, json) OBSERVED RESULT The file is opened with kate not with katepart. EXPECTED RESULT The file is opened/embedded with kdepart/konqueror. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION I assume something has changed in frameworks, it was fine with 5.61. Opening in a terminal: $ konqueror /home/test.json I get a popup window with the message: "Do you really want to execute 'file:///home/test.json'?" -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412379] New: When a menu is selected, the pop-up menu is blank
https://bugs.kde.org/show_bug.cgi?id=412379 Bug ID: 412379 Summary: When a menu is selected, the pop-up menu is blank Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: jim_ander...@jjajava.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. bring up konsole 2. In the konsole toolbar, select 'File', 'Edit', 'View', or any of the items and the menu drops down 3. OBSERVED RESULT When a menu item is selected, the menu pops up a rectangular black box that is blank. I suspect the font and the background are both defaulting or being set to the same color. EXPECTED RESULT I expect the normal menu to be readable. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Bunsenlabs Linux: Helium - 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3 Qt Version: 5 (I think) ADDITIONAL INFORMATION konsole version 16.12.0 I suspect that this is a configuration problem. I have been running Konsole on older versions of Bunsenlabs linux for years and never had a problem. Is there a way to set the menu font manually? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412376] Toolbar Text Position never Under Icons
https://bugs.kde.org/show_bug.cgi?id=412376 --- Comment #3 from Andrius Štikonas --- That should be easy to fix. It's just specified in a text file in XML format: https://invent.kde.org/kde/partitionmanager/blob/master/src/gui/partitionmanagerui.rc Do you want to try to fix it? Alternatively, a new bug can be opened. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412270] Keep active layer name when merging
https://bugs.kde.org/show_bug.cgi?id=412270 David REVOY changed: What|Removed |Added CC||i...@davidrevoy.com --- Comment #3 from David REVOY --- Hi Stepan, Yes, this is the type of situation where sometime one want to keep the name of the layer of the top while merging down. I think it is fair to tell it happens to everyone more or less rarely. That being said; the default behavior "to merge down" is more logic: the layer on the top get merged on the one of the bottom on a compositing point of view. So it is most likely reasonable to let the layer of the bottom dictate most of the properties of the result, including name. I'll give here two workflow where the merge down works well for default: You have layer "Pencil", you create a temp layer on the top to create set of lines you can move freely and rotate on a "Layer 12" type of autogenerated layer name, then you merge down to bake this changes and it auto-inherit the "Pencil" name. Same with painting and paint over, or photo bashing over a "texture" layer and then merging all down into it. I read your issue and the example are really specific; in my opinion they can be solved at creation of the stack with starting with properly named groups: then you can base color, ink, post-fx any body parts and keep the name of the groups during the full process while adding layer up or down. That's why all in all, I wouldn't even advice an option. I hope you'll understan d. -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 412325] calligraplan doesn't load translations from calligraplanlibs.mo
https://bugs.kde.org/show_bug.cgi?id=412325 --- Comment #3 from Christoph Feck --- Thanks Burkhard! I knew it was a simple fix, but investigating it requires knowledge about the i18n stuff only you got :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412364] Audio doesn't play (OSX)
https://bugs.kde.org/show_bug.cgi?id=412364 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from vanyossi --- this is happening on some macOS systems, but I need to know more about those systemsa s in my setup it works ok in 4.2.6, it might be a ill audio file. I tested with mp3 and FLAC and both worked ok. Do you happen to know more info? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412378] Latte crash in middle of auto-hide
https://bugs.kde.org/show_bug.cgi?id=412378 --- Comment #1 from Michail Vourlakos --- This crash points to applet code and plasma libraries and more specific when an applet is removed or when you switch layouts. 1. Have you tried the Latte Default layout and check if it crashes? 2. You can also check that this crash is not related to specific applet and not Latte fault -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412351] Kate fills 100% of tmpfs /tmp folder
https://bugs.kde.org/show_bug.cgi?id=412351 --- Comment #6 from Christoph Cullmann --- Ok, no problem ;=) Can you check that the project plugin is really off? Per default it is on. It might try to create some large ctags file or such stuff if it detects some project. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412378] New: Latte crash in middle of auto-hide
https://bugs.kde.org/show_bug.cgi?id=412378 Bug ID: 412378 Summary: Latte crash in middle of auto-hide Product: lattedock Version: 0.9.2 Platform: Gentoo Packages URL: https://bugs.kde.org/show_bug.cgi?id=412216#c6 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: halo...@gmail.com Target Milestone: --- Created attachment 122889 --> https://bugs.kde.org/attachment.cgi?id=122889=edit KCrash output Latte sometimes crashes, seemingly at random. It is always in the middle of hiding when it crashes, but I, as I am currently, cannot predict when it will crash. --- Operating System: Gentoo Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 Kernel Version: 5.3.1-gentoo OS Type: 64-bit Processors: 2 × AMD A9-9410 RADEON R5, 5 COMPUTE CORES 2C+3G Memory: 7,2 GiB of RAM --- sandy@sandys-pavilion:~$ latte-dock --cc Cache directory found and cleared... ^CKCrash: Attempting to start /usr/bin/latte-dock directly KCrash: Application 'latte-dock' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi directly Cache directory found and cleared... [1]+ Stopped latte-dock --cc --- ^C is ctrl+c. I used that to stop it after I saw that Latte was fully loaded and working. I did not want to have one of my Konsole tabs taken up by Latte. --- Here are the GCC flags from my make.conf in case anybody needs them: "-O3 -march=bdver4 -pipe -pthread -fira-hoist-pressure -fira-loop-pressure -fbranch-target-load-optimize -fweb -fgraphite-identity -floop-nest-optimize -fdevirtualize-at-ltrans -fipa-pta -fno-semantic-interposition -flto=2 -fuse-linker-plugin -fuse-ld=bfd -Wall -Wextra" -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412351] Kate fills 100% of tmpfs /tmp folder
https://bugs.kde.org/show_bug.cgi?id=412351 --- Comment #5 from Clara --- Sorry for the over-posting (first time reporting a bug here) but my last message was wrong, opening any file after removing all Kate related files in my home brings this bug back so it remains the same. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #197 from timo...@zoho.com --- Sorry for the delay. The test is still running. One thing I can say for sure is that with 04179402304ee8d9d813d5761dabf3ea8c769048 the performance has degraded a lot. It takes up to 10G of ram at times (4G on average) and after over 10h of running I'm now at 17%. Is that to be expected? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412376] Toolbar Text Position never Under Icons
https://bugs.kde.org/show_bug.cgi?id=412376 --- Comment #2 from Sete --- You're right. I've changed settings for all 3 of them and it worked. On the other hand, it doesn't make any sense to have 3 toolbars for this application. Thanks a lot! On Thu, 26 Sep 2019 at 21:05, Andrius Štikonas wrote: > https://bugs.kde.org/show_bug.cgi?id=412376 > > Andrius Štikonas changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > Resolution|--- |WORKSFORME > > --- Comment #1 from Andrius Štikonas --- > It works for me. Note that KDE Partition manager has 3 toolbars (I don't > know > why, this was probably before I joined the project), so you need to change > settings for all 3 of them. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412376] Toolbar Text Position never Under Icons
https://bugs.kde.org/show_bug.cgi?id=412376 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Andrius Štikonas --- It works for me. Note that KDE Partition manager has 3 toolbars (I don't know why, this was probably before I joined the project), so you need to change settings for all 3 of them. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412351] Kate fills 100% of tmpfs /tmp folder
https://bugs.kde.org/show_bug.cgi?id=412351 --- Comment #4 from Clara --- (In reply to Christoph Cullmann from comment #3) > Project plugin on? No, sorry. But I tried moving ~/.config/kate* and ~/.local/share/kate to a backup folder and the bug disappeared and restoring that files back does not bring the bug back so I am now unable to reproduce it in order to identify what was the problem, sorry :( Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412346] Personal settings not being saved
https://bugs.kde.org/show_bug.cgi?id=412346 --- Comment #3 from cor --- Created attachment 122887 --> https://bugs.kde.org/attachment.cgi?id=122887=edit after edit -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412216] Latte dock crahs
https://bugs.kde.org/show_bug.cgi?id=412216 --- Comment #7 from Sandi (Sandy) Vujaković --- (In reply to Michail Vourlakos from comment #6) > this crash has nothing to do with the first crash report. Please open a > different issue Oh... Sorry! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412346] Personal settings not being saved
https://bugs.kde.org/show_bug.cgi?id=412346 --- Comment #2 from cor --- Created attachment 122886 --> https://bugs.kde.org/attachment.cgi?id=122886=edit before editing -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4
https://bugs.kde.org/show_bug.cgi?id=412366 Ralf Habacker changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/beca6d92002eabc52ebd1 ||da52d6edf4c06c9c22c Status|REPORTED|RESOLVED Version Fixed In||4.8.5 Resolution|--- |FIXED --- Comment #6 from Ralf Habacker --- Git commit beca6d92002eabc52ebd1da52d6edf4c06c9c22c by Ralf Habacker. Committed on 26/09/2019 at 18:52. Pushed by habacker into branch '4.8'. Fix 'Print to File (PDF) broken on KDE4 in 4.8.4 on Slackware' Using the KHtmlView quick print support does not work if a user does not select the default system printer in kmymoney. FIXED-IN:4.8.5 M +1-1kmymoney/views/kreportsview.cpp https://commits.kde.org/kmymoney/beca6d92002eabc52ebd1da52d6edf4c06c9c22c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410341] Exif checkboxes ‘Fired’, ‘Function’ and ‘Red-eye remove’ all act as *one* checkbox
https://bugs.kde.org/show_bug.cgi?id=410341 --- Comment #2 from Tymond --- Relevant files: plugins/extensions/metadataeditor/kis_entry_editor.cpp plugins/extensions/metadataeditor/kis_metadata_editor.cpp plugins/extensions/metadataeditor/editors/exif.ui krita/data/metadata/schemas/exif.schema The most relevant functions are void KisEntryEditor::valueChanged() and KisMetaDataEditor::KisMetaDataEditor(QWidget* parent, KisMetaData::Store* originalStore) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4
https://bugs.kde.org/show_bug.cgi?id=412366 --- Comment #5 from Ralf Habacker --- (In reply to Ralf Habacker from comment #4) > At > https://build.opensuse.org/package/show/windows:mingw:win32/mingw32-kdelibs4 > there is a tarball for 4.14.60 and several patches I collected in the past. Most patches are intended for cross compiling windows packages. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4
https://bugs.kde.org/show_bug.cgi?id=412366 --- Comment #4 from Ralf Habacker --- (In reply to Erich from comment #2) > Hi Ralf, > > I will try your patch. > > Are there any concerns with updating KDE_VERSION_RELEASE to 65? The patch > file increases it from 60 to 65, whereas Slackware has it at 38. I assume > I'll be missing additional functionality that was added along the way? Mostly fixes > Where can I find these additional patches to kdelibs? At https://build.opensuse.org/package/show/windows:mingw:win32/mingw32-kdelibs4 there is a tarball for 4.14.60 and several patches I collected in the past. To be find kdelibs4 with method print(QPrinter* printer, bool quick) I raised the kdelibs patch level to 65. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412351] Kate fills 100% of tmpfs /tmp folder
https://bugs.kde.org/show_bug.cgi?id=412351 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #3 from Christoph Cullmann --- Project plugin on? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410341] Exif checkboxes ‘Fired’, ‘Function’ and ‘Red-eye remove’ all act as *one* checkbox
https://bugs.kde.org/show_bug.cgi?id=410341 Tymond changed: What|Removed |Added Assignee|tamtamy.tym...@gmail.com|krita-bugs-n...@kde.org Status|ASSIGNED|CONFIRMED --- Comment #1 from Tymond --- Related: bug 396669 It looks like metadata are kind of broken anyway. I could "fix this" by making it behave independently, but... I can't test if it breaks anything, because most of the code in metadata is either broken or wrong. The reason why all those checkboxes behave as one is that they are all distinguished as "exif:Flash" instead of "exif:Flash:Fired" etc. because exif:Flash, differently from all other fields in exif: scheme, is a structure (which means it contains other fields inside). The code looks like someone knew about it, but later forgot or at least forgot to check it in practice. The second/main reason is that all updates in one widget are propagated to all other widgets using the name of the property as the only thing that differentiate between what should get the notification and what shouldn't. All checkboxes has a property called "checked", which is why when one changes its "checked" status, they all change it too. Looks like the main reason for all those trouble is not separating the model and the view enough. I'm gonna unassign myself now. This bug depends on untangling the metadata code and fixing other bugs. It shouldn't be very difficult, but it will take some time, especially because half of the information is in .ui files and schemes. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4
https://bugs.kde.org/show_bug.cgi?id=412366 --- Comment #3 from Ralf Habacker --- (In reply to Erich from comment #0) > What I believe is the cause of the problem: > The net result of patches: > 5f4f90e83565647f3579660e4c5d9ac447547a02 Fix 'Printer settings are not saved' > 15ac7d472af41fc503dc5209643cfc8b392b0089 Add print support for report charts > Changes the "print" command from > m_part->view()->print() > to > q->m_part->view()->print(true); > when KDE_IS_VERSION(4, 14, 65) is false (which is the case for me). /** * Prints the HTML document. * @param quick if true, fully automated printing, without print dialog */ void print( bool quick = false ); > From what I can tell from reading the docs (I am not a KDE developer), this > changes the "print" command from "print by asking the user how to print" to > "print using the default settings". Unfortunately, those "default settings" > are not what KMyMoney asked about in the code immediately preceding the > "print" command, they must be the system-wide defaults. Thanks for reporting this hidden issue. > My minimally-invasive patch simply changes the print command back to what it > used to be, with the net effect that the print dialog appears twice when > printing a report. This could be fixed with the patch from attachment 122884. > I also developed a small patch which restores Print to File (PDF) > functionality for me, but the print dialog appears twice (I did expect that > to happen when I tried out the patch). So it is not a proper patch. which is required as fallback to avoid this issue, if the mentioned patch is not applied to kdelibs4. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4
https://bugs.kde.org/show_bug.cgi?id=412366 --- Comment #2 from Erich --- Hi Ralf, I will try your patch. Are there any concerns with updating KDE_VERSION_RELEASE to 65? The patch file increases it from 60 to 65, whereas Slackware has it at 38. I assume I'll be missing additional functionality that was added along the way? Where can I find these additional patches to kdelibs? I was under the impression that 4.14.38 was the last release of kdelibs. Erich -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412351] Kate fills 100% of tmpfs /tmp folder
https://bugs.kde.org/show_bug.cgi?id=412351 --- Comment #2 from Clara --- (In reply to Dominik Haumann from comment #1) > Do you open any file? No, I don't open any files. I open and empty Kate and it begins to drain /tmp instantly > Is it a session that you restore? No, it's a clean session > Do you open remote files? No -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412351] Kate fills 100% of tmpfs /tmp folder
https://bugs.kde.org/show_bug.cgi?id=412351 --- Comment #1 from Dominik Haumann --- Do you open any file? Is it a session that you restore? Do you open remote files? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 412377] New: SIGILL on cache flushes on arm64
https://bugs.kde.org/show_bug.cgi?id=412377 Bug ID: 412377 Summary: SIGILL on cache flushes on arm64 Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: kilob...@angband.pl Target Milestone: --- Created attachment 122885 --> https://bugs.kde.org/attachment.cgi?id=122885=edit patch to avoid SIGILL; doesn't implement cachegrind information SUMMARY Cache flush opcodes dc cvac, cvap, cvadp, civac cause valgrind to SIGILL, despite cvac and civac being in the arch baseline (the other two, cvap and cvadp, were added in 8.2 and 8.5 ISAs respectively). The only flush instruction that works is cvau. STEPS TO REPRODUCE 1. compile a program that includes "dc cvac" 2. test that it works on real hardware 3. run it under valgrind OBSERVED RESULT SIGILL EXPECTED RESULT On any arm64 machine, instructions other than dc cvap, cvadp should work. Valgrind doesn't need to ban opcodes from newer processors by itself, thus there's little point in banning cvap cvadp either. ADDITIONAL INFORMATION The function of those opcodes: * dc cvau makes icache same as dcache (ie, flushes L1 to L2) * dc cvac flushes all cache levels to real memory (L1-L3 to DRAM) * dc cvap flushes to system-defined "point of persistence" -- which might be memory controller or even no operation at all * dc cvadp flushes to actual medium the persistent memory is backed with (3DXpoint on Intel DCPMM, flash on HPE/IBM NVDIMM-N) * dc civac does cvac then evicts the cacheline from L1-L3 Here's a working but incomplete patch that has been applied in Debian (https://bugs.debian.org/930708); I see that valgrind doesn't use Phabricator thus I'm not sure what's the appropriate place for patch submissions. This patch stops the SIGILL, allowing use of tools like memcheck, drd or helgrind. It does not pass appropriate information to cachegrind -- I don't know its representation of cache levels well enough. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4
https://bugs.kde.org/show_bug.cgi?id=412366 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #1 from Ralf Habacker --- Created attachment 122884 --> https://bugs.kde.org/attachment.cgi?id=122884=edit Patch for kdelibs to support requested print operation On Windows builds the appended patch add related support to kdelibs. This need to be applied to Slackware's kdelibs4 package. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412374] KRA (Krita) files thumbnails not rendered
https://bugs.kde.org/show_bug.cgi?id=412374 caulier.gil...@gmail.com changed: What|Removed |Added Component|Thumbs-Album|Thumbs-IconView -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412374] KRA (Krita) files thumbnails not rendered
https://bugs.kde.org/show_bug.cgi?id=412374 --- Comment #2 from caulier.gil...@gmail.com --- Here KRA are not generated but ORA are fine in digiKam. I just generated both file with Krita. Look like Dolphin do not generate thumbnails for KRA and ORA... https://imgur.com/ZVmAIUz Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412370] [KCM]Add "enable-compositing" toggle to the top and move "enable at startup" setting to the bottom
https://bugs.kde.org/show_bug.cgi?id=412370 mthw0 changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #2 from mthw0 --- This KCM doesn't seem to have a specific task created for it. Could you add it, so I can comment there? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412376] New: Toolbar Text Position never Under Icons
https://bugs.kde.org/show_bug.cgi?id=412376 Bug ID: 412376 Summary: Toolbar Text Position never Under Icons Product: partitionmanager Version: 3.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: jolug...@gmail.com Target Milestone: --- SUMMARY The text position of the icons in the toolbar is always the same: Alongside STEPS TO REPRODUCE 1. Clic with secondary mouse button over the Toolbar to show the Context Menu 2. Clic on "Text Position" 3. Clic on "Text Under Icons" OBSERVED RESULT Text Alongside Icons EXPECTED RESULT Text Under Icons SOFTWARE/OS VERSIONS KDE Partition Manager: 3.3.1 Linux/KDE Plasma: Manjaro KDE KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel Version: 5.2.11-1-MANJARO ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412374] KRA (Krita) files thumbnails not rendered
https://bugs.kde.org/show_bug.cgi?id=412374 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- The KRA file are at least visible in icon view with a default icon ? If not please add KRA in album type mime item supported. Look in Setup/Views/Type-Mimes section of DK configuration dialog. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412375] pressure sensitivity of the pen doesn't work in krita
https://bugs.kde.org/show_bug.cgi?id=412375 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |NOT A BUG CC||b...@valdyas.org Status|REPORTED|RESOLVED --- Comment #1 from Boudewijn Rempt --- I'm sorry, but this is always a matter your local system setup. Krita works with Huion out of the box; please try to reset Krita's settings (https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration) or Huion's driver settings (you will have to figure that out yourself) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412372] Image editor view is expanded to 100% and shows only partial amount of picture
https://bugs.kde.org/show_bug.cgi?id=412372 --- Comment #6 from henk.deb...@telfort.nl --- Thank you very much that is a quick reply. Cheers, H (In reply to caulier.gilles from comment #1) > Already reported, and already fixed with next 6.4.0 release. > > Pre-PKG package can be tested here : > > https://files.kde.org/digikam/ > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412370] [KCM]Add "enable-compositing" toggle to the top and move "enable at startup" setting to the bottom
https://bugs.kde.org/show_bug.cgi?id=412370 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |NOT A BUG --- Comment #1 from David Edmundson --- This isn't really a bug, but more design input. We are interested in redesigning all our KCMs across plasma from the ground up doing things properly. So that things don't get split, can you find the relevant thread on https://phabricator.kde.org/tag/plasma_kcm_redesign/ and add your input there. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412375] New: pressure sensitivity of the pen doesn't work in krita
https://bugs.kde.org/show_bug.cgi?id=412375 Bug ID: 412375 Summary: pressure sensitivity of the pen doesn't work in krita Product: krita Version: 4.2.6 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Shape Assignee: krita-bugs-n...@kde.org Reporter: jo-...@gmx.de Target Milestone: --- SUMMARY pressure sensitivity of the pen doeen't work in krita (huion) even after resetting and deinstall. 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.
[digikam] [Bug 412374] New: KRA (Krita) files thumbnails not rendered
https://bugs.kde.org/show_bug.cgi?id=412374 Bug ID: 412374 Summary: KRA (Krita) files thumbnails not rendered Product: digikam Version: 6.3.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-Album Assignee: digikam-bugs-n...@kde.org Reporter: rafael.linux.u...@gmail.com Target Milestone: --- SUMMARY Digikam 6.3 doesn't show .KRA thumbnails. Dolphin and Krusader does. STEPS TO REPRODUCE 1. Create a KRA (Krita) image and save it in a folder that Digikam manages 2. Launch Digikam and open the previous folder OBSERVED RESULT Digikam shows no thumbnails for KRA files EXPECTED RESULT To show/render the KRA file thumbnail SOFTWARE/OS VERSIONS OpenSUSE 15.0 and 15.1 KDE Frameworks 5.45.0 Qt 5.9.4 (compilado con 5.9.4) El sistema de ventanas xcb ADDITIONAL INFORMATION Please, fix it -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412372] Image editor view is expanded to 100% and shows only partial amount of picture
https://bugs.kde.org/show_bug.cgi?id=412372 --- Comment #5 from henk.deb...@telfort.nl --- Created attachment 122883 --> https://bugs.kde.org/attachment.cgi?id=122883=edit Normal background view after opening preferences version 6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358932] [WACOM] Pen pressure sensitivity won't work even after reinstalling program, configuring, and resetting defaults
https://bugs.kde.org/show_bug.cgi?id=358932 jo-...@gmx.de changed: What|Removed |Added Version|2.9.10 |4.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358932] [WACOM] Pen pressure sensitivity won't work even after reinstalling program, configuring, and resetting defaults
https://bugs.kde.org/show_bug.cgi?id=358932 jo-...@gmx.de changed: What|Removed |Added CC||jo-...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412372] Image editor view is expanded to 100% and shows only partial amount of picture
https://bugs.kde.org/show_bug.cgi?id=412372 --- Comment #4 from henk.deb...@telfort.nl --- Created attachment 122882 --> https://bugs.kde.org/attachment.cgi?id=122882=edit Exploded background view after opening preferences version 6.3.0 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412373] New: Formatting drives messes with my trackpad
https://bugs.kde.org/show_bug.cgi?id=412373 Bug ID: 412373 Summary: Formatting drives messes with my trackpad Product: partitionmanager Version: 4.0.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: jplx...@gmail.com Target Milestone: --- SUMMARY KDE Partitionmanager seems to somehow mess with my trackpad driver (synaptics). When I tell it to apply changes, my mouse pointer becomes much slower for a while, like it's switching to a different driver. * I did not find anything suspicious in dmesg * It doesn't matter if it's an internal or USB drive STEPS TO REPRODUCE 1. Create a new partition layout 2. Click "Apply" OBSERVED RESULT The behaviour of my trackpad changes EXPECTED RESULT Partitioning drives shouldn influence the trackpad. They've got nothing to do with each other. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412372] Image editor view is expanded to 100% and shows only partial amount of picture
https://bugs.kde.org/show_bug.cgi?id=412372 --- Comment #3 from henk.deb...@telfort.nl --- Created attachment 122881 --> https://bugs.kde.org/attachment.cgi?id=122881=edit normal editing view in version 6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 213940] Dolphin doesn't show previews for Krita's .kra files
https://bugs.kde.org/show_bug.cgi?id=213940 --- Comment #11 from Boudewijn Rempt --- No problem :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412372] Image editor view is expanded to 100% and shows only partial amount of picture
https://bugs.kde.org/show_bug.cgi?id=412372 --- Comment #2 from henk.deb...@telfort.nl --- Created attachment 122880 --> https://bugs.kde.org/attachment.cgi?id=122880=edit Exploded editing view after opening editor -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412372] Image editor view is expanded to 100% and shows only partial amount of picture
https://bugs.kde.org/show_bug.cgi?id=412372 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED CC||caulier.gil...@gmail.com Version Fixed In||6.4.0 Status|REPORTED|RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- Already reported, and already fixed with next 6.4.0 release. Pre-PKG package can be tested here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412372] New: Image editor view is expanded to 100% and shows only partial amount of picture
https://bugs.kde.org/show_bug.cgi?id=412372 Bug ID: 412372 Summary: Image editor view is expanded to 100% and shows only partial amount of picture Product: digikam Version: 6.3.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: major Priority: NOR Component: ImageEditor Assignee: digikam-bugs-n...@kde.org Reporter: henk.deb...@telfort.nl Target Milestone: --- SUMMARY When opening the image editor from the opening screen, the view expands immediately to 100% and the image left hand top corner is displayed only. This cannot be undone. This renders the program unusable. My system is iMac (Retina 4K, 21.5", 2017), 8GB, Radeon Pro 560 4GB. This problem started originally in version 6.2.0 but then only with specific editing tools (like white balance or BCG). Now it happens directly when opening the editor. It is absent in version 6.1.0. Also in version 6.3.0, the background view of the standard screen expands to 100% when opening the preferences window from the menu. This preferences window remains visible in normal view, but again, this cannot be undone. This was not a problem in version 6.2.0 nor version 6.1.0. The program must be terminated to restore normal view. I have removed the program and reinstalled version 6.1.0. STEPS TO REPRODUCE 1. Open Digikam 2. Select image from any folder 3. Click image editor OBSERVED RESULT Exploded view which cannot be used for editing EXPECTED RESULT Normal view which can be used for editing and can be zoomed in any particular size. SOFTWARE/OS VERSIONS Windows: macOS: 10.14.6 Mojave 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.
[krita] [Bug 213940] Dolphin doesn't show previews for Krita's .kra files
https://bugs.kde.org/show_bug.cgi?id=213940 --- Comment #10 from Rafael Linux User --- My fault While I was typing the subject here, this bug appeared, but I didn't notice that this old bug (opened by me years ago) was refered to Krita, cause I opened it for Digikam, so I press "Send" without taking into account it was for Krita. My apologies Krita es AWESOME!! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 rjurado changed: What|Removed |Added CC||rjurad...@gmail.com --- Comment #110 from rjurado --- (In reply to Robbert van der Helm from comment #105) > While not ideal, I've managed to work around this by launching Konsole > without DPI scaling and then reexporting the environment variable for > applications launched from within the shell. This gets rid of the horizontal > line artifacts without interfering with other applications. > > To do this I changed konsole.desktop's `Exec` line from `konsole` to > `_QT_SCREEN_SCALE_FACTORS="$QT_SCREEN_SCALE_FACTORS" > QT_SCREEN_SCALE_FACTORS="" konsole` and I've added the following to my shell > config: > > # fish > set -xg QT_SCREEN_SCALE_FACTORS $_QT_SCREEN_SCALE_FACTORS > # bash > export QT_SCREEN_SCALE_FACTORS=$_QT_SCREEN_SCALE_FACTORS This works !! -- You are receiving this mail because: You are watching all bug changes.
