[Discover] [Bug 418126] Discover Update All returns error "Internal error Transaction did not go writing phase, but returned no error(0)"
https://bugs.kde.org/show_bug.cgi?id=418126 Nate Graham changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from Nate Graham --- Thanks for the info. :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423344] No way to browse installed packages by category
https://bugs.kde.org/show_bug.cgi?id=423344 --- Comment #5 from Nate Graham --- *way -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423344] No way to browse installed packages by category
https://bugs.kde.org/show_bug.cgi?id=423344 --- Comment #4 from Nate Graham --- I feel the same was as William. :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424691] Thumbnails not showing for face tags
https://bugs.kde.org/show_bug.cgi?id=424691 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/2189f7c ||1bbea606fea9784d37adb344df3 ||c2038a Version Fixed In||7.1.0 Status|CONFIRMED |RESOLVED --- Comment #15 from Maik Qualmann --- Git commit 2189f7c1bbea606fea9784d37adb344df3c2038a by Maik Qualmann. Committed on 01/08/2020 at 05:00. Pushed by mqualmann into branch 'master'. fix SQL query for MySQL in recursive Tags search FIXED-IN: 7.1.0 M +2-3NEWS M +12 -1core/libs/database/item/query/itemquerybuilder.cpp M +2-0core/libs/database/item/query/itemquerybuilder_p.h https://invent.kde.org/graphics/digikam/commit/2189f7c1bbea606fea9784d37adb344df3c2038a -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 423673] Rectangular region - highlighted area doesn't appear
https://bugs.kde.org/show_bug.cgi?id=423673 Bug Janitor Service changed: What|Removed |Added Resolution|FIXED |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 419093] call to Node.mergeDown() exits krita
https://bugs.kde.org/show_bug.cgi?id=419093 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 --- Comment #6 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 423815] Krita crashes when I create or click a frame while animating and also crashes when I make a layer while animating
https://bugs.kde.org/show_bug.cgi?id=423815 Bug Janitor Service changed: What|Removed |Added 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 424841] Secondary pen button if pressed when is put in range of tablet makes it act like an eraser tip
https://bugs.kde.org/show_bug.cgi?id=424841 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.
[systemsettings] [Bug 423604] System Settings doesn't open after installing an icon pack from the repository
https://bugs.kde.org/show_bug.cgi?id=423604 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[systemsettings] [Bug 315626] kcm_mouse (cursortheme): add cursor theme choice to ~/.Xresources
https://bugs.kde.org/show_bug.cgi?id=315626 --- 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.
[kscreenlocker] [Bug 423668] Screen does not always lock allowing user to mistakenly enter password into other applications (while screen is still dimmed)
https://bugs.kde.org/show_bug.cgi?id=423668 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423567] Firefox icon can't be removed from Panel
https://bugs.kde.org/show_bug.cgi?id=423567 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 415150] Save window positions
https://bugs.kde.org/show_bug.cgi?id=415150 --- Comment #13 from Nate Graham --- Yep, and that's where I'm starting here, for sure. I have the common case working and just need to handle the more complicated cases of multiple screens and per-screen positions. I hope to dig into that in the next few days. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 424882] New: The kdevelop crashed if create, rename and save new files
https://bugs.kde.org/show_bug.cgi?id=424882 Bug ID: 424882 Summary: The kdevelop crashed if create, rename and save new files Product: kdevelop Version: 5.5.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: file create Assignee: kdevelop-bugs-n...@kde.org Reporter: flashya...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. click new button in files tools. 2. input some content in the unnamed file; 3. click close tab; 4. choose yes in the close document dialog; 5. input one file anme and click save button; 6. kdevelop will crash OBSERVED RESULT crashed. EXPECTED RESULT no errors. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: ubuntu 20.04.1 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I run the image file. ./KDevelop.AppImage. it is downloaded from kdevelop site. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 --- Comment #7 from 2wxsy5823...@opayq.com --- @aacid FYI: Poppler: 0.90.1 Okular: 20.04.3 Using X11 Screen: 1080p, not hidpi -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399680] Graphical glitch/corruption in certain menus when transparency effect is enabled
https://bugs.kde.org/show_bug.cgi?id=399680 Mathew changed: What|Removed |Added CC||model...@outlook.com.au -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424881] New: Error trying to install neon-user-20200723-1119.iso
https://bugs.kde.org/show_bug.cgi?id=424881 Bug ID: 424881 Summary: Error trying to install neon-user-20200723-1119.iso Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: alejandro.tar...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 130546 --> https://bugs.kde.org/attachment.cgi?id=130546=edit Screenshot of the error SUMMARY I created a live USB using the Startup USB Creator for KDE and I cant boot from it, because a Invalid Magic Number error, already tried with another 3 usb drive with the same results STEPS TO REPRODUCE 1. When try to boot from the USB, the error Invalid Magic Number occurs OBSERVED RESULT Error invalid magic error, image attached EXPECTED RESULT Normal booting into live USB ADDITIONAL INFORMATION Already tried with another 3 usb drive with the same results -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424557] Metadata tags lost/changed
https://bugs.kde.org/show_bug.cgi?id=424557 --- Comment #8 from Jo --- (In reply to caulier.gilles from comment #7) > digiKam 7.0.0 stable release is now published: > > https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ > > We need a fresh feedback on this file using this version. > > Best Regards > > Gilles Caulier Thanks Gilles. I will download and get back to you. Another member of our team had a strange thing happen too - when she opened her images some of them were already tagged - not all, and not all correctly, which seems vaguely similar to my initial problem. Is there some kind of auto-facial recognition that could be at play here? Thanks, Jo -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 424880] New: Button labels disappear from kcalc.
https://bugs.kde.org/show_bug.cgi?id=424880 Bug ID: 424880 Summary: Button labels disappear from kcalc. Product: kcalc Version: 18.04 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: van.sny...@sbcglobal.net Target Milestone: --- SUMMARY Some button labels disappear from kcalc. STEPS TO REPRODUCE 1. Start kcalc, use it, then ignore it for a while 2. Put something on top of it, do some other work 3. Come back later. This time, the Memory save, clear, restore buttons are blank. Other times, other buttons have been blank. OBSERVED RESULT Some button labels have disappeared EXPECTED RESULT Button labels remain SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian 10.4 Buster (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION Sometimes, holding down Ctrl (at least left Ctrl) makes the labels come back. If I hold it down too long, it trips my KVM box to another computer, but that's not your problem. What is "About System" and how do I get at it? Not in kcalc's Help -> About KDE on any tab. Not in the desktop menu. Not in the panel launcher. Not in system settings. Not a file in /etc/. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 424218] Akonadi fails to start for KOrganizer in Linux Mint 20
https://bugs.kde.org/show_bug.cgi?id=424218 --- Comment #4 from m...@bobisevil.com --- Well it seemed to work briefly, then it decided to hang. After a reboot it is back to Akonadi not working. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 424218] Akonadi fails to start for KOrganizer in Linux Mint 20
https://bugs.kde.org/show_bug.cgi?id=424218 --- Comment #3 from m...@bobisevil.com --- Thanks. I had already tried that like five times at the time I posted earlier, without success, and had given up hope and switched to Google Calendar using a backup file. But yes, it seems in the interim an update must have fixed it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424810] Assert crash when selecting quick annotation tool that was added in the config dialog
https://bugs.kde.org/show_bug.cgi?id=424810 --- Comment #5 from Albert Astals Cid --- (In reply to Simone Gaiarin from comment #4) > I wrongly pushed my branch to upstream instead that on my fork and I think > it triggered something here. > > I have removed the branch from upstream and created it on my fork now. > > Hopefully I have not messed up anything. If you push upstream, push under work/ i.e. work/gaiarin/fix_blabla and then triggers are ignored. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424841] Secondary pen button if pressed when is put in range of tablet makes it act like an eraser tip
https://bugs.kde.org/show_bug.cgi?id=424841 --- Comment #3 from tokup...@gmail.com --- (In reply to Tymond from comment #1) > It would be good if you knew what APi your other programs use: Wintab or > Windows Ink. If so, please tell us the name of the program and the API. > > Try to switch Krita to Windows Ink and restart your PC: > https://docs.krita.org/en/contributors_manual/user_support.html#quick- > solutions > > Tbh it's really difficult to investigate issues like that, because between > Krita and your hand holding a stylus there is lots and lots of software and > configuration. It's enough if one of them is misconfigured and puff, it > doesn't work in Krita. Sorry, i didnt realize if i needed to directly reply but i have updated with more info as a comment. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 424878] Kio-extras: FISH component fails to build due to dead/removed code from include.
https://bugs.kde.org/show_bug.cgi?id=424878 Antonio Rojas changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||aro...@archlinux.org --- Comment #3 from Antonio Rojas --- As I've already told you multiple times on irc: this is caused by having /bin in your PATH, which makes cmake use a wrong CMAKE_CURRENT_LIST_DIR. It has absolutely nothing to do with util.h or libutil.h. If you didn't put /bin in PATH yourself, report it to your distro. It shouldn't be there if is it a symlink to /usr/bin -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411790] File layers don't refresh if they are created from the convert context menu in layer stack.
https://bugs.kde.org/show_bug.cgi?id=411790 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/a72eb7495 |hics/krita/commit/1b912acc8 |b66edd923408ed8819b59189028 |14f616772ef17a1a5020af257d4 |9b2f|5d51 --- Comment #9 from Dmitry Kazakov --- Git commit 1b912acc814f616772ef17a1a5020af257d45d51 by Dmitry Kazakov. Committed on 31/07/2020 at 21:39. Pushed by dkazakov into branch 'krita/4.3'. Fix update of file layers created via "Convert to" menu `FileSystemWatcherWrapper` works with absolute paths, but `KisSafeDocumentLoader` works with the original path as it was passed to the layer. We should unify these paths in `KisSafeDocumentLoader::fileChanged()`. The patch also fixes lost connections, when the file is temporary deleted (moved) and its recreation is delayed by something. Previously, FileSystemWatcherWrapper::slotFileChanged could just forget about it. Now it maintains a list of missing files in `m_lostFilesAbsenceCounter` and tries to reconnect to them with 200 ms intervals. PS: The tracked file may be removed/recreated because of QSaveFile functionality. M +5-0libs/global/kis_signal_compressor.cpp M +2-0libs/global/kis_signal_compressor.h M +62 -12 libs/ui/kis_safe_document_loader.cpp https://invent.kde.org/graphics/krita/commit/1b912acc814f616772ef17a1a5020af257d45d51 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424873] If there is just one tag, "Add Tags" menu of the search bar should be closed after we check/uncheck it
https://bugs.kde.org/show_bug.cgi?id=424873 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/41 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420755] Animated scroll transitions should respect global animation speed
https://bugs.kde.org/show_bug.cgi?id=420755 Densetsu no Ero-sennin changed: What|Removed |Added CC||ag+servi...@sologoc.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Matt Fagnani changed: What|Removed |Added Component|general |generic-crash Summary|plasmashell aborted a |plasmashell aborted shortly |shortly after logging in|after logging in with the |with the error The Wayland |error The Wayland |connection experienced a|connection experienced a |fatal error: Invalid|fatal error: Invalid |argument|argument Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] New: plasmashell aborted a shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Bug ID: 424879 Summary: plasmashell aborted a shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument Product: plasmashell Version: 5.19.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.4) Qt Version: 5.14.2 Frameworks Version: 5.72.0 Operating System: Linux 5.8.0-0.rc7.1.fc33.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 33 (KDE Plasma Prerelease) -- Information about the crash: - What I was doing when the application crashed: I logged into Plasma 5.19.4 on Wayland from sddm in Fedora Rawhide with KF 5.72.0, Qt 5.14.2. plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument according to the journal. Jul 31 17:03:00 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for NotificationPopup_QMLTYPE_610_QML_613(0x55cc662a2b20) Jul 31 17:03:00 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for NotificationPopup_QMLTYPE_610_QML_613(0x55cc662a2b20) Jul 31 17:03:00 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for NotificationPopup_QMLTYPE_610_QML_613(0x55cc662a2b20) Jul 31 17:03:00 plasmashell[5493]: trying to show an empty dialog Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: The Wayland connection experienced a fatal error: Invalid argument Jul 31 17:03:05 plasmashell[5998]: org.kde.plasmaquick: Applet preload policy set to 1 - Unusual behavior I noticed: The background went black. plasmashell restarted automatically The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f1fb07d08a4 in __GI_abort () at abort.c:79 #6 0x7f1fb0bf3a7f in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffc97230990, msg=msg@entry=0x7f1f9f338dc8 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893 #8 0x7f1f9f2c8640 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:90 #9 0x7f1f9f2c868e in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55cc641e0470) at qwaylanddisplay.cpp:209 #10 0x7f1fb0debfb0 in doActivate (sender=0x55cc641f5100, signal_index=4, argv=0x7ffc97230a70, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #11 0x7f1fb0de67f8 in QMetaObject::activate (sender=sender@entry=0x55cc641f5100, m=m@entry=0x7f1fb10748a0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #12 0x7f1fb0db9af7 in QAbstractEventDispatcher::awake (this=this@entry=0x55cc641f5100) at .moc/moc_qabstracteventdispatcher.cpp:149 #13 0x7f1fb0e08bac in QEventDispatcherGlib::processEvents (this=0x55cc641f5100, flags=...) at kernel/qeventdispatcher_glib.cpp:430 #14 0x7f1fb0dbb91b in QEventLoop::exec (this=this@entry=0x7ffc97230b90, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #15 0x7f1fb0dc35a6 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #16 0x55cc63509705 in main () [Inferior 1 (process 5493) detached] The reporter
[krita] [Bug 411790] File layers don't refresh if they are created from the convert context menu in layer stack.
https://bugs.kde.org/show_bug.cgi?id=411790 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/a72eb7495 ||b66edd923408ed8819b59189028 ||9b2f Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from Dmitry Kazakov --- Git commit a72eb7495b66edd923408ed8819b591890289b2f by Dmitry Kazakov. Committed on 31/07/2020 at 21:31. Pushed by dkazakov into branch 'master'. Fix update of file layers created via "Convert to" menu `FileSystemWatcherWrapper` works with absolute paths, but `KisSafeDocumentLoader` works with the original path as it was passed to the layer. We should unify these paths in `KisSafeDocumentLoader::fileChanged()`. The patch also fixes lost connections, when the file is temporary deleted (moved) and its recreation is delayed by something. Previously, FileSystemWatcherWrapper::slotFileChanged could just forget about it. Now it maintains a list of missing files in `m_lostFilesAbsenceCounter` and tries to reconnect to them with 200 ms intervals. PS: The tracked file may be removed/recreated because of QSaveFile functionality. M +5-0libs/global/kis_signal_compressor.cpp M +2-0libs/global/kis_signal_compressor.h M +62 -12 libs/ui/kis_safe_document_loader.cpp https://invent.kde.org/graphics/krita/commit/a72eb7495b66edd923408ed8819b591890289b2f -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 424878] Kio-extras: FISH component fails to build due to dead/removed code from include.
https://bugs.kde.org/show_bug.cgi?id=424878 --- Comment #2 from Paul McQuade --- Created attachment 130545 --> https://bugs.kde.org/attachment.cgi?id=130545=edit cmake.log -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424867] Dolphin search doesn't restrict search results "from here"...
https://bugs.kde.org/show_bug.cgi?id=424867 Ismael Asensio changed: What|Removed |Added CC||isma...@gmail.com --- Comment #1 from Ismael Asensio --- I could only reproduce this using non-indexed search (with baloo disabled), and searching on a folder with had a symlink to a different folder outside of its path, as the regular search follows symlinks when going into the folder tree. Is it possible that the subfolder you are searching in contains a symlink to the other directory where the results are shown from? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 424878] Kio-extras: FISH component fails to build due to dead/removed code from include.
https://bugs.kde.org/show_bug.cgi?id=424878 --- Comment #1 from Paul McQuade --- Created attachment 130544 --> https://bugs.kde.org/attachment.cgi?id=130544=edit CMakeOut.log -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 424878] New: Kio-extras: FISH component fails to build due to dead/removed code from include.
https://bugs.kde.org/show_bug.cgi?id=424878 Bug ID: 424878 Summary: Kio-extras: FISH component fails to build due to dead/removed code from include. Product: kio-extras Version: 20.07.80 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: FISH Assignee: plasma-b...@kde.org Reporter: paulmcq...@gmail.com Target Milestone: --- Created attachment 130543 --> https://bugs.kde.org/attachment.cgi?id=130543=edit CMakeError.log SUMMARY Kio-extras fish codebase doesn't compile due to some systems like manjaro Linux. fatal error: util.h: No such file or directory fatal error: libutil.h: No such file or directory Check the attachments above. STEPS TO REPRODUCE 1. Run "kdesrc-build" 2. Crashes at building "Kio-extras" 3. Build Error 2 OBSERVED RESULT Unable to configure kio-extras with CMake! Unable to configure kio-extras with KDE kio-extras didn't build, stopping here. No source update, but the build directory doesn't exist EXPECTED RESULT To build kio-extras SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.9-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GT 705/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424871] Dolphin does not search for files stored in secondary partitions if "Your files" button of the search bar is activated
https://bugs.kde.org/show_bug.cgi?id=424871 Ismael Asensio changed: What|Removed |Added CC||isma...@gmail.com --- Comment #2 from Ismael Asensio --- (In reply to Patrick Silva from comment #1) > Because this issue "From here (username)" and "Your files" buttons are > redundant when the search bar is triggered inside Home. Both make Dolphin to > search for files stored in Home only. When baloo search is enabled, "Your files" will search in all of the indexed folders (although by default this will be only 'Home'), so these two options are slightly different. But for non-indexed search these options are redundant as you well point, as they both search from 'Home' dir. We'll need to think of a possible solution to avoid this confusion. Searching in all of the possible partitions (that is, from '/') doesn't seem viable as it can be quite slow. Users can still explicitly search from root folder for that case. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420710] Shouldn't 'Exif.Image.DateTimeOriginal' be the equivalent of 'XMP Creation date' and 'IPTC Creation date', instead of Exif.Image.DateTime?
https://bugs.kde.org/show_bug.cgi?id=420710 --- Comment #20 from MarcP --- Created attachment 130542 --> https://bugs.kde.org/attachment.cgi?id=130542=edit Table comparing the metadata fields used in main picture managers To summarize the information I gathered when examining the metadata used in major picture managers, I have created a table. Maybe that will clear things up. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420710] Shouldn't 'Exif.Image.DateTimeOriginal' be the equivalent of 'XMP Creation date' and 'IPTC Creation date', instead of Exif.Image.DateTime?
https://bugs.kde.org/show_bug.cgi?id=420710 --- Comment #19 from MarcP --- In any case, according to that conversion table: Exif.Image.DateTime <=> Xmp.xmp.ModifyDate That means that the Exif.Image.DateTime, that is used in digikam as the date for when the "picture was taken" and currently syncs with Xmp.xmp.CreateDate is indeed a "last modification date", and it's used like that in most pictures managers. That field will be overwritten as soon as a picture is edited, so that field should not be used to store permanent data. The other equivalency: Exif.Photo.DateTimeOriginal <=> Xmp.photoshop.DateCreated is a bit weird. But in any case, that speaks against the use of Xmp.xmp.CreateDate in digikam and use Xmp.photoshop.DateCreated instead. Actually, that is the case for Adobe Lightroom, Adobe Photoshop, and ACDSee. However, Xmp.exif.DateTimeOriginal is the preferred field for that information in Picasa, ACDSee, and Shotwell. For some reason, Microsoft Photos just uses the xmp.xmp.createdate field instead, like Digikam (and also Shotwell, but not exclusively). (Oh, and more argument for the use of Exif.Photo.DateTimeOriginal as the main "Date taken" field in Exif, is that most (if not all) cameras store the date in that field, while not using any kind of XMP information. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424691] Thumbnails not showing for face tags
https://bugs.kde.org/show_bug.cgi?id=424691 Maik Qualmann changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #14 from Maik Qualmann --- OK, the problem is now clear to me, also why it occurs and not for me, I fix it. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419289] Krita on master (after RR) cannot save and/or open layers with layer styles
https://bugs.kde.org/show_bug.cgi?id=419289 Tymond changed: What|Removed |Added Component|layer styles|Resource Management --- Comment #8 from Tymond --- Note: situation on master with resource rewrite right now: - Krita can open file with layer styles, it just won't be loaded. - Krita can save file with layer styles, the layer style just won't be saved. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 424876] Number tracks as 1/12 instead of just number and remove leading 0
https://bugs.kde.org/show_bug.cgi?id=424876 --- Comment #1 from Urs Fleisch --- The settings in the dialog which appears when choosing menu "Tools/Number Tracks..." only affect the operation of this dialog, i.e. the numbering of the selected tracks, which is done when closing the dialog by the "OK" button. The option you are looking for is in the settings dialog (menu "Settings/Configure Kid3...") in the tab "Tags/Tag 2". Check "Use track/total number of tracks format" and at the bottom of the same "ID3v2" section, you will find the "Track number digits" option, which has to be set to "1" in order to have "1/12" instead of "01/12". Note that the format is only changed when the value changes, so "01/12" will not automatically be changed to "1/12". For this, you will have to change the value, for example by clearing all track numbers and then renumbering using the function from the "Tools" menu or manually entering a number. -- You are receiving this mail because: You are watching all bug changes.
[basket] [Bug 424877] New: Cannot click save
https://bugs.kde.org/show_bug.cgi?id=424877 Bug ID: 424877 Summary: Cannot click save Product: basket Version: unspecified Platform: Chakra OS: macOS Status: REPORTED Severity: major Priority: NOR Component: general Assignee: niccolo.venera...@gmail.com Reporter: ylva.birgersdot...@gmail.com Target Milestone: --- SUMMARY When trying to save work it will not allow. Save button is disabled. STEPS TO REPRODUCE 1. Create notes 2. Try to save them OBSERVED RESULT Save button is inactivated EXPECTED RESULT Save button should be active and able to save work 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 419289] Krita on master (after RR) cannot save and/or open layers with layer styles
https://bugs.kde.org/show_bug.cgi?id=419289 Tymond changed: What|Removed |Added Summary|krita git db1cc49 was can't |Krita on master (after RR) |save using layer style. |cannot save and/or open ||layers with layer styles -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419289] krita git db1cc49 was can't save using layer style.
https://bugs.kde.org/show_bug.cgi?id=419289 Tymond changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Tymond --- Hi, I checked and all the commits you mentioned that doesn't work are based on master, which means those are development builds. Please don't use them to work. Broken: - db1cc49ba2 (master-only) Thu Mar 26 15:28:35 2020 + Scott Petrovic Change cursor to pointer on up and down arrow for sliderbox input - fc06350be1 (master-only) Sun Mar 22 14:27:19 2020 +0100 Boudewijn Rempt Fix crash when creating an image from the clipboard Working: - 44d8e02 (master and krita/4.3; means it was before resource rewrite merged to master) Sun Mar 15 02:43:21 2020 +0100 l10n daemon script GIT_SILENT made messages (after extraction) - dac91dfbe7 (there is no branch that contains this commit, I believe it's just amyspark's special appimage etc., probably before branching out from master) Sat Feb 15 09:06:31 2020 -0300 L. E. Segovia Use getUIMin/Max in the channel filters too > can't open generate layer style by git db1cc49 You mean it cannot open Fill Layer that you created in the amyspark's special GSOC build? It's not surprising - it wasn't yet released. Only some builds have those abilities. I will change the bug report title to note that it's about the new resource rewrite. Please if you want to use Krita for production, don't use development builds. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420710] Shouldn't 'Exif.Image.DateTimeOriginal' be the equivalent of 'XMP Creation date' and 'IPTC Creation date', instead of Exif.Image.DateTime?
https://bugs.kde.org/show_bug.cgi?id=420710 --- Comment #18 from Maik Qualmann --- As I said, concerns should be brought up to Exiv2, we do not make this assignment. Sidecars are a very special case. We only set "Exif.Photo.DateTimeOriginal", Exiv2 writes "Xmp.photoshop.DateCreated" in the sidecar. The EXIF data is interpreted in the same way backwards (EXIF data does not exist if I only read from sidecars). So you should ignore the EXIF and IPTC metadata when using sidecars, they are not real. Maik -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 424876] New: Number tracks as 1/12 instead of just number and remove leading 0
https://bugs.kde.org/show_bug.cgi?id=424876 Bug ID: 424876 Summary: Number tracks as 1/12 instead of just number and remove leading 0 Product: kid3 Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: just_jee...@yahoo.com Target Milestone: --- SUMMARY I have to manually add /12 (or whatever the total tracks are) in the track number field. I assumed that checking the total number of tracks in the number tracks window would add the total tracks after the track number (i.e. 1/1, 2/12, etc). If this is added it would be nice to also have an option to remove the leading 0 so instead of 01/12 it would be 1/12. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 424849] PLASMASHELL crashed after turning on
https://bugs.kde.org/show_bug.cgi?id=424849 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 326289 *** -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 Christoph Feck changed: What|Removed |Added CC||ruiz.math...@protonmail.com --- Comment #64 from Christoph Feck --- *** Bug 424849 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424691] Thumbnails not showing for face tags
https://bugs.kde.org/show_bug.cgi?id=424691 --- Comment #13 from Maik Qualmann --- Please deactivate View-> Include Tag Sub-Tree Does it work now? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420710] Shouldn't 'Exif.Image.DateTimeOriginal' be the equivalent of 'XMP Creation date' and 'IPTC Creation date', instead of Exif.Image.DateTime?
https://bugs.kde.org/show_bug.cgi?id=420710
--- Comment #17 from Stefan ---
(In reply to MarcP from comment #16)
> Hi. Now that the final 7.0.0 version has been released, can we have a look
> at this report?
>
> I think the samples I provided show that the main tag for saving the date in
> Exif is the Exif.Photo.DateTimeOriginal. To sum up, I believe it should be
> like this:
>
> Exif.Image.DateTime = Xmp.xmp.ModifyDate
> Exif.Photo.DateTimeOriginal = Xmp.xmp.CreateDate
>
> PS: curiously enough, Photoshop is the outlier here, as it's just a photo
> editor not a picture library manager, and just saves the date to xmp and
> iptc.
(Deepl translates)
I interpret the definitions more like this:
Exif.Photo.DateTimeOriginal = Xmp.photoshop.DateCreated
= Exif.Image.DateTime
-> creation date of the displayed image ("what you see")
Exif.Photo.DateTimeDigitized = Xmp.xmp.CreateDate
-> Digitization date (= creation date of the digital image, not the creation
date of the real photo (e.g. the scan image of a negative)
xmp:ModifyDate
-> Date of the last change of the image (?)
xmp:MetadataDate
-> Date of the last change of metadata (?)
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 401446] Crash using multiple transform masks with multiple clone layers
https://bugs.kde.org/show_bug.cgi?id=401446 Tymond changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from Tymond --- There has been changes now. @Larpon could you please check if it happens in the latest Krita (4.3.0)? I couldn't reproduce it - it takes some time updating, but works just fine. Since I cannot reproduce it, there is no backtrace and the assert is too generic to be useful, and there were changes to this part of the code, I don't think there is anything that we can use to fix the bug. I'm gonna change it to NeedsInfo so it will close automatically if there is no new information. If you still experience this crash and can reproduce it, please say so and maybe try to get the backtrace too - https://docs.krita.org/en/reference_manual/sharing_krita_logs.html#crash-log-and-backtrace -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424809] Corners + Rotoscoping = crash
https://bugs.kde.org/show_bug.cgi?id=424809 --- Comment #1 from caetano --- as a side note to anyone looking for a workaround : having the 2 effects separated in 2 clips and using an "Alpha on Top" composition gives the same result while preventing the crash. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 424218] Akonadi fails to start for KOrganizer in Linux Mint 20
https://bugs.kde.org/show_bug.cgi?id=424218 --- Comment #2 from tnpel2...@gmail.com --- I found a fix for the problem. There are five Akondi programs in the software manager for LM20 but only two are installed. I installed the last three and the calendar works. Only a work-around, but it works. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424843] Constantly glitching when just drawing lines or doing dots or anything really. It gets extremely frustrating and time consuming. Also the zoom effect is very glitchy as well
https://bugs.kde.org/show_bug.cgi?id=424843 --- Comment #3 from Tymond --- Please go over to krita-artists.org and write a post there instead, you will get help there. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 424858] An option to display desktop notifications for a feed in Akregator until it is closed by the user
https://bugs.kde.org/show_bug.cgi?id=424858 myndstr...@protonmail.ch changed: What|Removed |Added Summary|An option to display|An option to display |notifications for a feed in |desktop notifications for a |Akregator until it is |feed in Akregator until it |closed by the user |is closed by the user -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424691] Thumbnails not showing for face tags
https://bugs.kde.org/show_bug.cgi?id=424691 --- Comment #12 from LarsE --- Thanks for looking deeper into this. I always used the mySQL mariaDB database, when I started with digikam some time ago. I set up an empty database and let digikam go and index all photos of my collection. So I have no idea, where this structure might come from. What would you suggest to do without loosing information? And what do you think about the issue regarding the digikam@% user required? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423685] Crash in LCMS when certain icc files are present
https://bugs.kde.org/show_bug.cgi?id=423685 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/455 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 424826] Krusader Mint 19.3 root mode login fails
https://bugs.kde.org/show_bug.cgi?id=424826 --- Comment #1 from Gary --- OS = Linux Mint 19.3 Cinnamon x64 bit. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418126] Discover Update All returns error "Internal error Transaction did not go writing phase, but returned no error(0)"
https://bugs.kde.org/show_bug.cgi?id=418126 --- Comment #2 from zeev --- Sorry, I can't test it as I had to reinstall the system since then Thanks for your effort (not related to KDE, Fedora upgraded my kernel and rendered my ZFS unusable) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 424875] New: Dolphin ignoring fstab "x-gvfs-name" since update
https://bugs.kde.org/show_bug.cgi?id=424875
Bug ID: 424875
Summary: Dolphin ignoring fstab "x-gvfs-name" since update
Product: frameworks-solid
Version: 5.72.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: lu...@kde.org
Reporter: david.riv...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
Created attachment 130541
--> https://bugs.kde.org/attachment.cgi?id=130541=edit
Screenshot to illustrate the issue
Hello,
I didn't notice exactly when it happened but Dolphin does not display anymore
the "x-gvfs-name" from fstab since a recent update.
See attachment screenshot.
After some research, I think this is handled by solid.
I found the code of file "src/solid/devices/backends/fstab/fstabdevice.cpp" on
github
https://github.com/KDE/solid/commit/cdbfb3e799c72742163ecf6a6bdf073aeed874c3
It was modified 2 months ago and the part managing GVFS was modified :
for (const QString : gvfsOptions) {
if (option.startsWith(QLatin1String("x-gvfs-name="))) {
QStringRef encoded = option.midRef(12);
- m_description = QUrl::fromPercentEncoding(encoded.toLatin1());
+ m_displayName = QUrl::fromPercentEncoding(encoded.toLatin1());
} else if (option.startsWith(QLatin1String("x-gvfs-icon="))) {
QStringRef encoded = option.midRef(12);
m_iconName = QUrl::fromPercentEncoding(encoded.toLatin1());
}
}
Can you please fix the issue, it's really not nice for NFS share in Dolphin.
Regards,
David
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.72.0
Qt Version: 5.15.0
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 424874] New: Subsequent searches fail if baloo is disabled
https://bugs.kde.org/show_bug.cgi?id=424874 Bug ID: 424874 Summary: Subsequent searches fail if baloo is disabled Product: dolphin Version: 20.07.80 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I can't reproduce this behavior when baloo is enabled. STEPS TO REPRODUCE 1. disable baloo running "balooctl disable" 2. open Dolphin 3. press ctrl+f 4. search for something present in your Home (Dolphin shows the search results as expected) 5. search for another thing present in your Home OBSERVED RESULT second search has no result EXPECTED RESULT search feature should always work when baloo is disabled SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422391] Crash when using "Save Layer/Mask" on a transform mask
https://bugs.kde.org/show_bug.cgi?id=422391 Tymond changed: What|Removed |Added Ever confirmed|0 |1 CC||tamtamy.tym...@gmail.com Severity|normal |crash Status|REPORTED|CONFIRMED --- Comment #1 from Tymond --- Looks like no one ever tried to do it - it's not a regression, it crashed Krita even in Krita 4.1.7. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422750] On canvas HUD color picker (square type) or color history swatches are hard to use due to no buffer area on edges
https://bugs.kde.org/show_bug.cgi?id=422750 --- Comment #2 from Tymond --- Maybe there could be border area around the color selector that when the cursor is there, the color selector fades out a bit to show that it will disappear if you stray away from it too much? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422750] On canvas HUD color picker (square type) or color history swatches are hard to use due to no buffer area on edges
https://bugs.kde.org/show_bug.cgi?id=422750 Tymond changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||tamtamy.tym...@gmail.com Severity|normal |minor --- Comment #1 from Tymond --- I can confirm it closes a bit unexpectedly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424872] I am unable to use the program as there is a lot of lag in my brush strokes and it seems to be spaced out, producing dotted lines as opposed to smooth strokes
https://bugs.kde.org/show_bug.cgi?id=424872 Tymond changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- For tablet driver issues like this it's best to go to user forum like krita-artists.org , since this website bugs.kde.org is development-oriented, not user-oriented. It will probably be fixed if you switch Krita to Windows Ink: https://docs.krita.org/en/contributors_manual/user_support.html#quick-solutions and make sure to restart your PC afterwards. If you still experience issues, please go to krita-artists.org website to ask for help there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384530] If a window doesn't support global menus, closing system settings won't get rid of the menus
https://bugs.kde.org/show_bug.cgi?id=384530 Carson Black changed: What|Removed |Added Status|REPORTED|RESOLVED CC||uhh...@gmail.com Resolution|--- |FIXED --- Comment #6 from Carson Black --- This should be fixed with the port to libtaskmanager. Please reopen if it's not. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424873] New: If there is just one tag, "Add Tags" menu of the search bar should be closed after we check/uncheck it
https://bugs.kde.org/show_bug.cgi?id=424873 Bug ID: 424873 Summary: If there is just one tag, "Add Tags" menu of the search bar should be closed after we check/uncheck it Product: dolphin Version: 20.07.80 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Currently Dolphin keeps the "Add tag" menu open after we check a tag. This behavior is useful when we have several tags so we can select/deselect several tags at once, but it's pointless when there is just one tag. STEPS TO REPRODUCE 1. have just one tag in Dolphin 2. press ctrl+f 3. click on "Add tags" button 4. check/uncheck the tag OBSERVED RESULT Dolphin keeps the "Add tag" menu open after the last step EXPECTED RESULT "Add tag" menu should be closed after the last step SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424872] New: I am unable to use the program as there is a lot of lag in my brush strokes and it seems to be spaced out, producing dotted lines as opposed to smooth strokes
https://bugs.kde.org/show_bug.cgi?id=424872 Bug ID: 424872 Summary: I am unable to use the program as there is a lot of lag in my brush strokes and it seems to be spaced out, producing dotted lines as opposed to smooth strokes Product: krita Version: 4.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: major Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: anonymass...@gmail.com Target Milestone: --- Created attachment 130540 --> https://bugs.kde.org/attachment.cgi?id=130540=edit screenshot of the brush strokes produces SUMMARY STEPS TO REPRODUCE 1. use brush tool 2. 3. OBSERVED RESULT:dotted line EXPECTED RESULT:smooth stroke 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 422486] Session manager window edit buttons should be disabled without a selected session
https://bugs.kde.org/show_bug.cgi?id=422486 Tymond changed: What|Removed |Added Latest Commit||3f3d802f63249196a98cb384299 ||9e281ae0925eb --- Comment #4 from Tymond --- @ Maximilian if you want to resolve a bug inside a commit, you can write > BUG:422486 instead of > CCBUG:422486 (CCBUG only adds a comment, doesn't close the issue). Unless this is not fixed yet - then please reopen and say what is still wrong. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 421288] Unable to delete some categories
https://bugs.kde.org/show_bug.cgi?id=421288 Michael Carpino changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 421288] Unable to delete some categories
https://bugs.kde.org/show_bug.cgi?id=421288 --- Comment #6 from Michael Carpino --- I am closing this issue/bug as it is not a bug because of a recent issue I was following on the KMM Forum that resolves the problem. The categories that I was unable to delete was because I have payees that I defined/assigned as the default category. As soon as I removed the default category for the payee then I am miraculously (sarcasm) able to delete the category. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422486] Session manager window edit buttons should be disabled without a selected session
https://bugs.kde.org/show_bug.cgi?id=422486 Tymond changed: What|Removed |Added Status|REPORTED|RESOLVED CC||tamtamy.tym...@gmail.com Resolution|--- |FIXED --- Comment #3 from Tymond --- I guess the fact that the MR was merged means it's fixed now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422830] Transform Tool - Cage has incorrect default Adjust Granularity values
https://bugs.kde.org/show_bug.cgi?id=422830 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Keywords||triaged --- Comment #1 from Tymond --- This probably needs to be checked in code, I cannot tell if there is any difference between 4/32 and 32/4... And since I can see that sometimes my custom numbers get reset to 16/8 again, I wouldn't be surprised if it ignored user values altogether. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421844] setResolution, setXRes, setYRes, scaleImage not working
https://bugs.kde.org/show_bug.cgi?id=421844 Scott Petrovic changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Scott Petrovic --- Alright. We can close this for now. If something else pops up we can make a new ticket. There has been quite a few fixes happening in the past couple months, so maybe it got fixed with something else. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419093] call to Node.mergeDown() exits krita
https://bugs.kde.org/show_bug.cgi?id=419093 --- Comment #5 from Scott Petrovic --- The point I was trying to make is there is something going on with "children[1]" in your script that is giving it issues. The mergeDown() is working in my script, so there must be some difference with how your script is set up that is giving it issues. There could also be something with the "setChildNodes" that is not being set correctly that is causing the mergeDown to fail. We just need to figure out what causes the situation where it fails. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 424799] Build Error: "Boost_INCLUDE_DIR-NOTFOUND"
https://bugs.kde.org/show_bug.cgi?id=424799 Christophe Giboudeaux changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kactivities-stats/co ||mmit/c8208572abb0d77d76bad6 ||bbba23a0cbd6268251 Status|REPORTED|RESOLVED --- Comment #6 from Christophe Giboudeaux --- Git commit c8208572abb0d77d76bad6bbba23a0cbd6268251 by Christophe Giboudeaux. Committed on 31/07/2020 at 17:34. Pushed by cgiboudeaux into branch 'master'. Ignore BoostConfig.cmake if present The Boost config file when present doesn't provide CMake variables compatible with the ones in FindBoost.cmake. M +1-0CMakeLists.txt M +0-1autotests/CMakeLists.txt M +1-1src/CMakeLists.txt M +0-1tests/model/CMakeLists.txt https://invent.kde.org/frameworks/kactivities-stats/commit/c8208572abb0d77d76bad6bbba23a0cbd6268251 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421844] setResolution, setXRes, setYRes, scaleImage not working
https://bugs.kde.org/show_bug.cgi?id=421844 --- Comment #2 from Manga Tengu --- I'm a bit lost here, I tried it for the nth time and now it works. In between there was OS and Krita upgrades so It's hard for me to tell where it comes from. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 408310] Restarting plasmashell breaks Task Manager keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=408310 --- Comment #6 from Thiago Sueto --- Apparently: killall plasmashell ; plasmashell --replace == not breaks killall plasmashell ; plasmashell == not breaks killall plasmashell ; kstart5 plasmashell == not breaks kquitapp5 plasmashell ; plasmashell --replace == breaks kquitapp5 plasmashell ; plasmashell == breaks kquitapp5 plasmashell ; kstart5 plasmashell == breaks Does plasmashell --replace use kquitapp5 to exit a running instance of plasmashell? If so, it seems likely to me the issue is in kquitapp5 and this would also explain why plasmashell --replace doesn't have this issue when no plasmashell instance is currently running. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424843] Constantly glitching when just drawing lines or doing dots or anything really. It gets extremely frustrating and time consuming. Also the zoom effect is very glitchy as well
https://bugs.kde.org/show_bug.cgi?id=424843 --- Comment #2 from al3x2...@gmail.com --- It’s not user oriented it’s the application it self, sometimes when drawing a straight line, the application will cause the brush to veer of in a complete other direction, or if I’m just doing dot by dot, it’ll lock the brush until I touch the pen to the screen again and it’ll just create a line instead of 2 individual dots. It’s not something i can just look up and fix myself, it’s not the configuration it’s the application glitching out. Sent from my iPhone > On Jul 30, 2020, at 9:00 PM, Tymond wrote: > > https://bugs.kde.org/show_bug.cgi?id=424843 > > Tymond changed: > > What|Removed |Added > > CC||tamtamy.tym...@gmail.com > Resolution|--- |WORKSFORME > Status|REPORTED|RESOLVED > > --- Comment #1 from Tymond --- > Hi, this is way too little information for us to be able to help you, and the > issue you mentioned is unlikely to be a problem in Krita's code because issues > like that can often be fixed or mitigated with different configuration. In any > case, it'd be much better if you could please go to krita-artists.org and ask > for help there. This website here - bugs.kde.org - is strictly > development-oriented, not user support-oriented; while krita-artists.org is > user-oriented and much more user-friendly than here. Someone will help you > investigate the issue and find a remedy. If there is in fact a bug found, and > the user supporter confirms there is a bug, they will help you describe it to > make the bug report helpful for developers. You can read more here for > details: > https://docs.krita.org/en/untranslatable_pages/reporting_bugs.html It's > generally recommended that if you feel like you've found a bug, go to the user > forum and ask about it, because sometimes there is already bug report made, or > maybe it's already fixed, or maybe there are other solutions you could try > first. > > But thanks for taking an active role and trying to report. That's important > for > the community. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422188] Error with palm rejection
https://bugs.kde.org/show_bug.cgi?id=422188 Tymond changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #5 from Tymond --- I will set it up to Upstream since it's not something Krita has a responsibility over. Also you might get better results if you switch Krita to Windows Ink: https://docs.krita.org/en/contributors_manual/user_support.html#quick-solutions - restart your PC afterwards. This setting changes the standard Krita listens to tablet events with. Btw I recently had the same issue on Linux (very annoying :( ). Then I noticed there is a new version of my tablet driver, I installed it and I haven't had issues even since - and there was nothing changed in Krita for that. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424871] Dolphin does not search for files stored in secondary partitions if "Your files" button of the search bar is activated
https://bugs.kde.org/show_bug.cgi?id=424871 --- Comment #1 from Patrick Silva --- Because this issue "From here (username)" and "Your files" buttons are redundant when the search bar is triggered inside Home. Both make Dolphin to search for files stored in Home only. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422188] Error with palm rejection
https://bugs.kde.org/show_bug.cgi?id=422188 Tymond changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||tamtamy.tym...@gmail.com --- Comment #4 from Tymond --- The palm rejection is something that the tablet driver should do, not Krita. You can remove drawing with touch in Krita - in Configure Krita -> General -> Tools -> Enable Touch Painting. If it doesn't fix the issue, you might want to disable touch in your tablet driver, or maybe use a drawing glove (glove helps since it prevents the tablet to find your skin and send events to Krita). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419093] call to Node.mergeDown() exits krita
https://bugs.kde.org/show_bug.cgi?id=419093 --- Comment #4 from Manga Tengu --- There is a lot happening indeed, but the mergeDown() call is the one that triggers the bug as when it's commented everything else works. If there is anything additional I can do please let me know ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424192] Cannot pass a filter configuration to a python Filter
https://bugs.kde.org/show_bug.cgi?id=424192 --- Comment #4 from Scott Petrovic --- We can probably still close this ticket, but I would be interested to know how to set values in the config that are CDATA. For example the halftone filter XML looks like this. true 8 false 45 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422787] Unable to draw or move any drawing tools
https://bugs.kde.org/show_bug.cgi?id=422787 Tymond changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Tymond --- If it started to happen randomly, it means that Krita didn't change but something outside of Krita changed - maybe there was Windows Update or maybe you changed your configuration. Please check following things: - make sure to install Krita 4.3.0 since that's the newest version. If it works, don't do the next step, just say so. - make sure your system is fully updated (the most important thing is to not update the PC partially) and graphics card drivers installed correctly - reset configuration - https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration - remove both `kritadisplayrc` and `kritarc`. If it works, don't do the next step, just say so. - in Configure Krita -> Display change the Rendered to the other one, restart Krita and check. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424192] Cannot pass a filter configuration to a python Filter
https://bugs.kde.org/show_bug.cgi?id=424192
Scott Petrovic changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #3 from Scott Petrovic ---
After looking at another script...I think this does actually work and this bug
might be invalid. Changing the properties and running it again changes the
effect of the filter. This seems to work for me in scripter...
from krita import *
#create document to work with
newDocument = Krita.instance().createDocument(500, 500, "Document name",
"RGBA", "U8", "", 300.0)
Krita.instance().activeWindow().addView(newDocument) # shows it in the
application
# make active node layer opacity 100%
activeNode = newDocument.activeNode()
activeNode.setOpacity(255)
# fill with foreground color that has saturation
Krita.instance().action("fill_selection_foreground_color").trigger();
newDocument.refreshProjection()
# see all available filters
# print(Krita.instance().filters())
randomNoiseFilter = Krita.instance().filter("noise")
config = randomNoiseFilter.configuration()
config.setProperty("level", 100)
config.setProperty("opacity", 99)
randomNoiseFilter.setConfiguration(config)
randomNoiseFilter.apply(activeNode, 0, 0, newDocument.width(),
newDocument.height())
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 424871] New: Dolphin does not search for files stored in secondary partitions if "Your files" button of the search bar is activated
https://bugs.kde.org/show_bug.cgi?id=424871 Bug ID: 424871 Summary: Dolphin does not search for files stored in secondary partitions if "Your files" button of the search bar is activated Product: dolphin Version: 20.07.80 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Currently I use 3 hard disks. sda: root partition, partition of Windows 7 and an ext4 partition to store personal data sdb and sdc: just one ntfs partition to store personal data each Any file stored in any partition mentioned above is mine, but when "Your files" button of the search bar is activated Dolphin only searches for files stored in my Home. This seems confusing to me. STEPS TO REPRODUCE 1. open Dolphin and press ctrl+f 2. activate "Your files" button 3. search for a file stored in a secondary partition OBSERVED RESULT Dolphin does not find your file stored in the secondary partition EXPECTED RESULT When "Your files" button of the search bar is activated, Dolphin should search for files stored in any partition of the system. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419079] Star rating on TIFF images destroys the image
https://bugs.kde.org/show_bug.cgi?id=419079 --- Comment #7 from Dirk --- Dear Gilles, I tested with several hundred changes of ratings on TIFF (and also DNG) files without any problem. Seems to me that the problem is solved :) regards Dirk Am 30.07.2020 um 22:50 schrieb bugzilla_nore...@kde.org: > https://bugs.kde.org/show_bug.cgi?id=419079 > > caulier.gil...@gmail.com changed: > > What|Removed |Added > > CC||caulier.gil...@gmail.com > > --- Comment #6 from caulier.gil...@gmail.com --- > Hi, > > applying start rating will embed information in tiff tags metadata using > Exiv2. > As we update last stable version of Exiv2 in Windows installer, the problem > can > be fixed indirectly. > > I'm waiting your feedback tomorrow evening. > > Gilles Caulier > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422873] Title of the second tab is ambiguous in display settings section of configure Krita
https://bugs.kde.org/show_bug.cgi?id=422873 Tymond changed: What|Removed |Added Ever confirmed|0 |1 CC||tamtamy.tym...@gmail.com Severity|normal |minor Status|REPORTED|CONFIRMED --- Comment #1 from Tymond --- Yes, and maybe let's move the color of the background (and the image background, to make it all in one place) there as well? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423206] Brush cursor rotation flickering when starting to a stroke (using Tilt Direction)
https://bugs.kde.org/show_bug.cgi?id=423206 Tymond changed: What|Removed |Added Summary|Brush cursor rotation |Brush cursor rotation |flickering when starting to |flickering when starting to |a stroke|a stroke (using Tilt ||Direction) CC||tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424638] Crash when using move tool on the transform mask
https://bugs.kde.org/show_bug.cgi?id=424638 Tymond changed: What|Removed |Added CC||emmetoneill@gmail.com --- Comment #4 from Tymond --- *** Bug 423126 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423126] Failed assertion when using Move Tool on Transform Mask.
https://bugs.kde.org/show_bug.cgi?id=423126 Tymond changed: What|Removed |Added Resolution|--- |DUPLICATE CC||tamtamy.tym...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Tymond --- *** This bug has been marked as a duplicate of bug 424638 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423240] Advanced Color selector - slow performance
https://bugs.kde.org/show_bug.cgi?id=423240 Tymond changed: What|Removed |Added Keywords||triaged CC||tamtamy.tym...@gmail.com --- Comment #6 from Tymond --- For the Color Selector Tool (Color Picker), I don't see any lag in Krita 4.3.0 appimage. For the Advanced Color Selector (docker), I also don't see that much lag as @stephen recorded. There is some little lag on dragging inside the rectangle, but it's the same as in Krita 4.1.7. Note: I was checking on Linux. @stephen - are you sure you used the released version? There was some lag recently in some development versions, but it doesn't seem to be present in Krita 4.3.0. If yes, you're sure - then maybe this bug report needs to be checked by someone on Windows. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405194] Python-Plugin Palette Docker doesn't load: KisSwatch not supported
https://bugs.kde.org/show_bug.cgi?id=405194 Scott Petrovic changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO CC||scottpetro...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from Scott Petrovic --- I am going to motion that we close this. The gsoc palette docker is pretty good, and this plugin has not been fixed in over a year. If we need to bring it back for some reason we can make a new ticket. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 415150] Save window positions
https://bugs.kde.org/show_bug.cgi?id=415150 --- Comment #12 from EricCh --- I suspect it's the Main window people are most complaining about. In my case, the upper left corner of the main Kate window is about the middle of my monitor and most of the window is off the bottom and right side of the monitor. Fixing that would be fantastic. Down the road if people want other dialog positions saved/restored, you have the framework avaiable. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424829] Crash when undoing/redoing while using Colorize Mask
https://bugs.kde.org/show_bug.cgi?id=424829 --- Comment #2 from tomtomtomreportin...@gmail.com --- My friend on Debian testing (Bullseye) can reproduce the same crash using the appimage, and I tried Krita 4.3 from the Debian repos and it also produces the same crash, so maybe the crash is Linux/Debian-specific? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419207] Document Krita actions for Python plugins
https://bugs.kde.org/show_bug.cgi?id=419207 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||scottpetro...@gmail.com Ever confirmed|0 |1 --- Comment #3 from Scott Petrovic --- There is a new Krita scripting site in the works that is almost launched. There is an action dictionary where you can search all the actions that are available. I think once that site goes live we can close this ticket. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413088] Changing visibility on multiple layers + calling refreshProjection() is a very slow operation.
https://bugs.kde.org/show_bug.cgi?id=413088 Scott Petrovic changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |NEEDSINFO CC||scottpetro...@gmail.com --- Comment #5 from Scott Petrovic --- Can someone check this out again with the master branch? I made a document at 3000x3000. I made 6 layers and filled them with content. I ran the script above. It took a fraction of a second to toggle the visibility. Maybe something with the node generation was fixed since this was filed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424870] New: Plasma crashes when drag event calendar plasmoid to the desktop
https://bugs.kde.org/show_bug.cgi?id=424870 Bug ID: 424870 Summary: Plasma crashes when drag event calendar plasmoid to the desktop Product: plasmashell Version: 5.12.9 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: theotyf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.9) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 4.15.0-112-generic x86_64 Distribution: Ubuntu 18.04.4 LTS -- Information about the crash: - What I was doing the application crashed: Plasma crashes when drag event calendar plasmoid to the desktop - Unusual behavior I noticed: It crashes every time - Custom settings of the application: no Custom settings. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa1b5e33800 (LWP 1581))] Thread 13 (Thread 0x7fa0b7df2700 (LWP 5116)): #0 0x7fa1a9f59a74 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa1a9f5a4fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa1a9f5a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa1afd3c8ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa1afce190a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa1afb0023a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa1afb0517d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa1aec866db in start_thread (arg=0x7fa0b7df2700) at pthread_create.c:463 #8 0x7fa1af400a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fa0c7a8f700 (LWP 5114)): #0 0x7fffe79e7b62 in clock_gettime () #1 0x7fa1af410056 in __GI___clock_gettime (clock_id=1, tp=0x7fa0c7a8eb10) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7fa1afd3c1c1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa1afd3a9f9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa1afd3afd5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa1afd3c61e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa1a9f59b28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fa1a9f5a4fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fa1a9f5a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fa1afd3c8ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fa1afce190a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fa1afb0023a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fa1afb0517d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fa1aec866db in start_thread (arg=0x7fa0c7a8f700) at pthread_create.c:463 #14 0x7fa1af400a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fa0eebc1700 (LWP 2422)): #0 0x7fffe79e7b62 in clock_gettime () #1 0x7fa1af410056 in __GI___clock_gettime (clock_id=1, tp=0x7fa0eebc0b80) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7fa1afd3c1c1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa1afd3a9f9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa1afd3d005 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa1a9f59fe1 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fa1a9f5a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fa1a9f5a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fa1afd3c8ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa1afce190a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fa1afb0023a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fa1afb0517d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fa1aec866db in start_thread (arg=0x7fa0eebc1700) at pthread_create.c:463 #13 0x7fa1af400a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fa1029e0700 (LWP 1921)): #0 0x7fa1aec8c9f3 in futex_wait_cancelable (private=,
[krita] [Bug 416921] python copy paste selection - Paste issue (not paste action)
https://bugs.kde.org/show_bug.cgi?id=416921 Scott Petrovic changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||scottpetro...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #6 from Scott Petrovic --- This was written a little while ago, but I looked at it briefly. The way the paste() works right now, it requires a selection. When you do the deselect action in your code snippet, you are making it so the paste operation doesn't work. See this code. https://api.kde.org/appscomplete-api/krita-apidocs/libs/libkis/html/Selection_8cpp_source.html#l00177 If there is no selection, the paste isn't going to work. The way it works otherwise is that it will truncate some of your copied content depending on what you put fot he x and y position. My recommendation is probably just not to use the paste(). It is probably better to just use the paste action. You can move it around as needed, then merge down to a below layer if it needs to be on another layer. If there are coding questions like this, we also have a new krita-artists website that you can post questions to (https://krita-artists.org/). There is a good community of developers on there to help with scripting questions like this too. I am going to close this for now. If there is something else that comes up we can make a new ticket. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 424869] New: When a new class or other object is created in the Tree View, the "Edit Properties" dialog should immediately open
https://bugs.kde.org/show_bug.cgi?id=424869 Bug ID: 424869 Summary: When a new class or other object is created in the Tree View, the "Edit Properties" dialog should immediately open Product: umbrello Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: c...@roberthairgrove.com Target Milestone: --- SUMMARY When a new object is added to the Tree View, it must be double-clicked before the new object can be edited. STEPS TO REPRODUCE 1. Right-click on any folder; 2. Choose "New.../Class"; 3. A new object called "new_class" is created, but now I have to do additional clicks in order to change the name, etc. OBSERVED RESULT See above. EXPECTED RESULT The Properties dialog should open automatically so that at least a new name can be set. SOFTWARE/OS VERSIONS Linux Ubuntu 18.04.4 Qt Version: 5.x ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
