[digikam] [Bug 408265] The stacked images tool appears to be non-functional
https://bugs.kde.org/show_bug.cgi?id=408265 Maik Qualmann changed: What|Removed |Added Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406237] PDFs get an added margin when printing
https://bugs.kde.org/show_bug.cgi?id=406237 Michael Weghorn changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #14 from Michael Weghorn --- (In reply to Matthew Trescott from comment #13) > I've opened separate bug reports. > > https://bugs.kde.org/show_bug.cgi?id=408270 > https://bugs.kde.org/show_bug.cgi?id=408271 > https://bugs.kde.org/show_bug.cgi?id=408272 > https://bugs.kde.org/show_bug.cgi?id=408273 Thanks! Closing this one then. *** This bug has been marked as a duplicate of bug 408270 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408272] The default scaling method should be "Fit to Full Page"
https://bugs.kde.org/show_bug.cgi?id=408272 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408271] Print-to-PDF defaults to A4 regardless of locale or original document size
https://bugs.kde.org/show_bug.cgi?id=408271 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #6 from Michael Weghorn --- *** Bug 406237 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408273] Scaling mode "Print original size" is confusing
https://bugs.kde.org/show_bug.cgi?id=408273 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 407014] side bar of desktop settings window has unnecessary horizontal scroll bar
https://bugs.kde.org/show_bug.cgi?id=407014 Kai Uwe Broulik changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 407014] side bar of desktop settings window has unnecessary horizontal scroll bar
https://bugs.kde.org/show_bug.cgi?id=407014 Kai Uwe Broulik changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #10 from Kai Uwe Broulik --- Yup, observed the same -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368366] Wish - Render .mlt files as a clip job, and add resulting rendered file to project
https://bugs.kde.org/show_bug.cgi?id=368366 Evert Vorster changed: What|Removed |Added Version|unspecified |19.04.1 --- Comment #3 from Evert Vorster --- This wish is still here. It would be super-awesome to be able to render an .mlt file at the project settings and add it to the project bin. Right now, that requires opening another project, dragging the .mlt file into it, rendering it, and then adding the output back into the first project. So tedious. Conceptually this would be really easy to do as a clip job in the project bin. As we all know, mlt files have issues. They are CPU intensive to display, and cause their own class of bugs in kdenlive. In my mind there is not much difference between rendering a clip once and using that, and rendering it every time you want to look at it, apart from the CPU used. If you want to be purist about it, one can use a lossless profile for in-project renders... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408274] New: Printscreen shortcut stopped working after update to 5.15
https://bugs.kde.org/show_bug.cgi?id=408274 Bug ID: 408274 Summary: Printscreen shortcut stopped working after update to 5.15 Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: triffid.hun...@gmail.com Target Milestone: --- Created attachment 120546 --> https://bugs.kde.org/attachment.cgi?id=120546&action=edit screenshot of settings window (two panes) plus demonstration that shell script works as expected when actually invoked I have printscreen bound to a shell script which used to work great, but after updating kde/plasma recently it no longer works - the script simply never gets run. The mapping is still listed in systemsettings -> workspace -> shortcuts -> custom shortcuts, however nothing happens when I press printscreen. I tried setting it to other combinations (eg shift+print, ctrl+alt+J), none worked - even if I was asked to reassign it from another action (eg examples -> type hello) that previously worked! I tried assigning other commands (krita, gimp, logger -t shortcut works), also with no effect. Thus, it appears that Command/URL global shortcuts have somehow been broken in this update. Please let me know any debugging steps that may be useful, I miss my conveniently organised screenshots! Linux/KDE Plasma: Linux 5.1.3 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 318193] wish: behaviour of the akregator systray icon consitent with the other like kmail and chokoq for example
https://bugs.kde.org/show_bug.cgi?id=318193 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Laurent Montel --- it works here. I close it -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369657] XMP subject matter code can be added twice
https://bugs.kde.org/show_bug.cgi?id=369657 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||6.2.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/d6a94becc2f9 ||7a5514d6f7c02583c4f0fb18eb5 ||7 --- Comment #2 from Maik Qualmann --- Git commit d6a94becc2f97a5514d6f7c02583c4f0fb18eb57 by Maik Qualmann. Committed on 04/06/2019 at 06:06. Pushed by mqualmann into branch 'master'. fix handling with subject matter code FIXED-IN: 6.2.0 M +2-1NEWS M +3-1 core/dplugins/generic/metadata/metadataedit/iptc/iptcsubjects.cpp M +3-1core/dplugins/generic/metadata/metadataedit/xmp/xmpsubjects.cpp M +3-1core/libs/template/subjectedit.cpp M +9-2core/libs/widgets/metadata/subjectwidget.cpp M +2-0core/libs/widgets/metadata/subjectwidget.h https://invent.kde.org/kde/digikam/commit/d6a94becc2f97a5514d6f7c02583c4f0fb18eb57 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 374653] System tray icon empty when there are unread feeds
https://bugs.kde.org/show_bug.cgi?id=374653 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Laurent Montel --- it seems fixed here. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 --- Comment #16 from Jean-Baptiste Mardelle --- Thanks again for the detailed bug report and attached project. In fact, when switching compositing to "none" and back to another mode, track compositing was not enabled for the lowest track. This went undetected since most projects have an audio track as lowest track so the bug was not triggered. This is now fixed. I also now made a change to save track compositing mode in the project (before it always reverted to high resolution each time you opened the project. The problem should now be fixed, and you can test today's automated AppImage build for confirmation - the build will happen in approximately 7 hours - check that it was built on the 4th of june on emohr's link in comment 9. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 Jean-Baptiste Mardelle changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |kdenlive/commit/e71e7609b5b |kdenlive/commit/c9358290cea |47a461f9863307f1a4a0df30d14 |048020486285844a03f617e1d06 |11 |4b Status|REOPENED|RESOLVED --- Comment #15 from Jean-Baptiste Mardelle --- Git commit c9358290cea048020486285844a03f617e1d064b by Jean-Baptiste Mardelle. Committed on 04/06/2019 at 05:46. Pushed by mardelle into branch 'Applications/19.04'. Save track compositing mode in project to restore it on load Fix compositing broken for first track if we have a video only project after switching compositing mode M +6-0src/project/projectmanager.cpp M +2-1src/timeline2/view/timelinecontroller.cpp https://invent.kde.org/kde/kdenlive/commit/c9358290cea048020486285844a03f617e1d064b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408265] The stacked images tool appears to be non-functional
https://bugs.kde.org/show_bug.cgi?id=408265 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||metzping...@gmail.com Version Fixed In||6.2.0 --- Comment #3 from Maik Qualmann --- This message is the cause, the problem is already solved in the pre-release of digiKam-6.2.0. QObject::disconnect: No such signal DigikamGenericExpoBlendingPlugin::ExpoBlendingThread::finished(Digikam::ExpoBlendingActionData) https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #94 from Rob --- For now if you want to get it working, since this is proving to be more difficult than I first thought. The following commands will install homebrew, python3, Astropy, and numpy to your system. The final command will delete my broken internal python. Just type the commands into a terminal. Plate solving in Kstars should work as expected. I would still like to resolve this. I don't want users to have to do all this if possible. /usr/bin/ruby -e "$(curl -fsSL raw.githubusercontent.com/Homebrew/install/master/install )" brew install python3 ln -s /usr/local/bin/python3 /usr/local/bin/python ln -s /usr/local/bin/pip3 /usr/local/bin/pip pip install astropy rm -r /Applications/kstars.app/Contents/MacOS/python/* Thanks, Rob -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406311] KWin crash at boot-time
https://bugs.kde.org/show_bug.cgi?id=406311 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393336] Brush rotation using tablet pen's rotation capped at 180 degrees.
https://bugs.kde.org/show_bug.cgi?id=393336 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 --- Comment #95 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.
[kate] [Bug 372226] Some sessions stay in full screen on cinnamon
https://bugs.kde.org/show_bug.cgi?id=372226 --- 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.
[lattedock] [Bug 408266] Grab the active window not possible
https://bugs.kde.org/show_bug.cgi?id=408266 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Michail Vourlakos --- You need to enable that option from Behavior page -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 407918] Does not find music on other ext4 partition even when added to search paths
https://bugs.kde.org/show_bug.cgi?id=407918 Joseph Nosie changed: What|Removed |Added CC||joeno...@protonmail.com --- Comment #10 from Joseph Nosie --- Created attachment 120545 --> https://bugs.kde.org/attachment.cgi?id=120545&action=edit STDOUT with logging enabled I can also reproduce this with the Elisa nightly flatpak. I have verified that Elisa has been given filesystem permission for the mount point of the partition. If an album exists in both ~/Music and the mount, the album shows up twice in the album listing, but one of them (the one from the mount) is empty. Also, other flatpak apps can access the mount point when given the permissions. (I have a steam library on the same drive.) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406237] PDFs get an added margin when printing
https://bugs.kde.org/show_bug.cgi?id=406237 --- Comment #13 from Matthew Trescott --- I've opened separate bug reports. https://bugs.kde.org/show_bug.cgi?id=408270 https://bugs.kde.org/show_bug.cgi?id=408271 https://bugs.kde.org/show_bug.cgi?id=408272 https://bugs.kde.org/show_bug.cgi?id=408273 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408273] New: Scaling mode "Print original size" is confusing
https://bugs.kde.org/show_bug.cgi?id=408273 Bug ID: 408273 Summary: Scaling mode "Print original size" is confusing Product: okular Version: 1.7.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: matthewtresc...@gmail.com Target Milestone: --- Created attachment 120544 --> https://bugs.kde.org/attachment.cgi?id=120544&action=edit Sample PDF for testing Split from https://bugs.kde.org/show_bug.cgi?id=406237 SUMMARY When selecting "Print original size" as the scaling setting, the document is shifted down and left, rather than being cropped. STEPS TO REPRODUCE 1. Open any PDF (such as the one attached) 2. Open the Print menu, choose a paper size smaller than the one of the original document, and select "Print original size" as the scaling mode. 3. Click "Print." OBSERVED RESULT The document's contents are shifted down and left to fit the printer's margins. EXPECTED RESULT The document's contents are overlayed with a blank margin prior to being sent tot the print driver. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION The current system for this kind of printing may even have problems for RTL languages (I do not know since I have not tested this). I think a simpler, more elegant solution would be to replace this scaling mode with one called "Crop to fit printable area." This new scaling mode would add blank margins to the PDF before sending it to the print driver, rather than allowing the printer to figure out that it can't print part of the document. I'm not sure how useful that would be in practice compared to the "Fit to full page" scale mode. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408271] Print-to-PDF defaults to A4 regardless of locale or original document size
https://bugs.kde.org/show_bug.cgi?id=408271 --- Comment #1 from Matthew Trescott --- Note: split from https://bugs.kde.org/show_bug.cgi?id=406237 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408272] The default scaling method should be "Fit to Full Page"
https://bugs.kde.org/show_bug.cgi?id=408272 --- Comment #1 from Matthew Trescott --- Note: split from https://bugs.kde.org/show_bug.cgi?id=406237 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408272] New: The default scaling method should be "Fit to Full Page"
https://bugs.kde.org/show_bug.cgi?id=408272 Bug ID: 408272 Summary: The default scaling method should be "Fit to Full Page" Product: okular Version: 1.7.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: matthewtresc...@gmail.com Target Milestone: --- When printing, "fit to printable area" is the default scaling setting. However, most PDF documents have margins built-in and so do not need the extra margins added by this setting. "Fit to full page" should be the default. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408271] New: Print-to-PDF defaults to A4 regardless of locale or original document size
https://bugs.kde.org/show_bug.cgi?id=408271 Bug ID: 408271 Summary: Print-to-PDF defaults to A4 regardless of locale or original document size Product: okular Version: 1.7.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: matthewtresc...@gmail.com Target Milestone: --- Created attachment 120543 --> https://bugs.kde.org/attachment.cgi?id=120543&action=edit Sample document for testing SUMMARY The title pretty much says it all. Personally, I feel that since Okular aims to be a viewer for many more types of files other than PDF (EPUB, ODF, etc.) it should be able to act as a one-to-one converter to PDF. For example, you should be able to open an PostScript file with many different page sizes and use Okular's Print-to-PDF function to create an identical PDF, with the page sizes preserved. However, I can also understand the reasoning behind the current default setting. It also makes sense that using Print-to-PDF would force the document to fit into a consistent, standard paper size. If this remains the default, however, the default paper size should be dependent on locale (en_US should have Letter for example). STEPS TO REPRODUCE 1. Open the attached PDF. 2. Go to File > Print and select Print to PDF. 3. Hit "Print" and observe the output. OBSERVED RESULT The Letter-size document produces an A4-size PDF. EXPECTED RESULT The PDF produced via Print-to-PDF is Letter-sized for either of the following reasons: 1. The original document was Letter-sized, and the original document's page size(s) are preserved, OR 2. Letter is the default paper size for my locale (en_US). SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #5 from Matthew Trescott --- Also note that this bug is unaffected by the scaling settings available when "Force rasterization" is selected. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #4 from Matthew Trescott --- Note that this doesn't occur with other software like LibreOffice, so I don't think it's a problem with CUPS or the PPD. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #3 from Matthew Trescott --- Created attachment 120542 --> https://bugs.kde.org/attachment.cgi?id=120542&action=edit Output from /var/spool/cups -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407221] Random KWin hang on VirtualDesktop RefCount
https://bugs.kde.org/show_bug.cgi?id=407221 --- Comment #6 from David Gow --- Okay, it seems that I spoke too soon: I just got the hang again. I have better debug symbols now, so here's an updated (example) stacktrace. As before, it appears to be an infinite loop in KWin::Placement::placeSmart(): #0 0x7f9e7d2211d4 in KWin::Client::metaObject() const (this=) at /home/david/kde/build/kwin/kwin_autogen/EWIEGA46WW/moc_client.cpp:264 #1 0x7f9e7c1dab69 in QMetaObject::cast(QObject const*) const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9e7d0d9c4d in qobject_cast(QObject*) (object=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:499 #3 0x7f9e7d0d9c4d in KWin::Placement::placeSmart(KWin::AbstractClient*, QRect const&, KWin::Placement::Policy) (this=, c=c@entry=0x5623225705c0, area=...) at /home/david/kde/src/kwin/placement.cpp:243 #4 0x7f9e7d0db9d8 in KWin::Placement::place(KWin::AbstractClient*, QRect&, KWin::Placement::Policy, KWin::Placement::Policy) (this=, c=0x5623225705c0, area=..., policy=, nextPlacement=) at /home/david/kde/src/kwin/placement.cpp:106 #5 0x7f9e7d1ca38d in KWin::ShellClient::placeIn(QRect&) (this=this@entry=0x5623225705c0, area=...) at /home/david/kde/src/kwin/placement.h:107 #6 0x7f9e7d1ca849 in KWin::ShellClient::finishInit() (this=0x5623225705c0) at /home/david/kde/src/kwin/shell_client.cpp:378 #7 0x7f9e7c1fb563 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9e77e0381e in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #9 0x7f9e77e031ef in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #10 0x7f9e79bc88fd in () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #11 0x7f9e79bc5379 in () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #12 0x7f9e79bc6942 in wl_event_loop_dispatch () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #13 0x7f9e7cd083ae in KWayland::Server::Display::Private::dispatch() (this=) at /home/david/kde/src/kwayland/src/server/display.cpp:147 #14 0x7f9e7c1fb563 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f9e7c206bd9 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f9e7c206f21 in QSocketNotifier::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f9e7c5e8551 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f9e7c5ef930 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f9e7c1d18e9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f9e7c76 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f9e7c222587 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f9e74cac65d in QUnixEventDispatcherQPA::processEvents(QFlags) () at /home/david/kde/usr/lib/x86_64-linux-gnu/plugins/platforms/KWinQpaPlugin.so #23 0x7f9e7c1d05bb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f9e7c1d85e2 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x56231f48c25e in main(int, char**) (argc=, argv=) at /home/david/kde/src/kwin/main_wayland.cpp:676 Sorry for the spam — let me know if there's anything more I should be looking at. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #2 from Matthew Trescott --- Created attachment 120541 --> https://bugs.kde.org/attachment.cgi?id=120541&action=edit Sample PDF used This is the sample PDF I printed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #1 from Matthew Trescott --- Created attachment 120540 --> https://bugs.kde.org/attachment.cgi?id=120540&action=edit The PPD for my printer This is the PPD for the printer I use. It is a Samsung C1860FW laser printer. The PPD is from /usr/share/foomatic/db/source/PPD/Samsung -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407118] Keyboard navigation broken
https://bugs.kde.org/show_bug.cgi?id=407118 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407118] Keyboard navigation broken
https://bugs.kde.org/show_bug.cgi?id=407118 Nate Graham changed: What|Removed |Added Keywords||regression, usability -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] New: Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 Bug ID: 408270 Summary: Okular always prints in A4 on physical printers, even when Letter is the default Product: okular Version: 1.7.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: matthewtresc...@gmail.com Target Milestone: --- Split from https://bugs.kde.org/show_bug.cgi?id=406237 I turned off WiFi temporarily so CUPS would hold my print job (it's a network printer), then printed my Letter-size PDF. I double-checked the printer properties in Okular to make sure that it was set to Letter (Letter is the default for the print queue so the paper size was already correctly set). However, when I opened the corresponding PostScript document in /var/spool/cups, it had the distinctive sqrt(2) side ratio of A-size paper. This confirms the results I had when I permitted the print jobs to go through previously and discovered this bug---I just didn't want to waste paper this time. Attachments are coming shortly. System: Arch Linux (fairly up-to-date) CUPS 2.2.11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407221] Random KWin hang on VirtualDesktop RefCount
https://bugs.kde.org/show_bug.cgi?id=407221 --- Comment #5 from David Gow --- I've tried to reproduce this on the latest KWin git (c62650394) over the last few days, and haven't been able to, so maybe it's fixed. I'd certainly have expected it to show up by now if it were still happening, though my environment for git KWin is slightly different (started from a VT instead of SDDM). So… maybe fixed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408227] Setting Caps Lock as Compose doesn't disable Caps Lock functionality
https://bugs.kde.org/show_bug.cgi?id=408227
--- Comment #4 from David Gow ---
Thanks for pointing me to kxkbrc — I'm unable to reproduce the issue after
deleting it, unless I add multiple keyboard layouts. If there are multiple
layouts configured, I can reproduce the issue — deleting them fixes it.
For example, creating a US English ("us") and Japanese ("jp") keyboard layout,
allows me to reproduce the issue from within the us layout. Disabling the
"Configure Layouts" checkbox doesn't fix the issue by itself, the layouts seem
to have to be deleted.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 408227] Setting Caps Lock as Compose doesn't disable Caps Lock functionality
https://bugs.kde.org/show_bug.cgi?id=408227 --- Comment #3 from David Gow --- Created attachment 120539 --> https://bugs.kde.org/attachment.cgi?id=120539&action=edit kxkbrc which reproduces the problem This is a kxkbrc which reproduces the problem. Having multiple keyboard layouts seems to be a prerequisite — I'm unable to reproduce the issue from a clean kxkbrc by just following the instructions in the original report. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407118] Keyboard navigation broken
https://bugs.kde.org/show_bug.cgi?id=407118 Chris Holland changed: What|Removed |Added CC||zrenf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408268] On "Yiynova or tablet screen" disconnect -> Krita popup windows show on wrong screen
https://bugs.kde.org/show_bug.cgi?id=408268 --- Comment #1 from Bollebib --- This has been a longstanding issue,its not recent -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408268] On "Yiynova or tablet screen" disconnect -> Krita popup windows show on wrong screen
https://bugs.kde.org/show_bug.cgi?id=408268 Bollebib changed: What|Removed |Added Summary|On Yiynova/tablet screen|On "Yiynova or tablet |Disconnect Krita popup |screen" disconnect -> Krita |windows show on wrong |popup windows show on wrong |screen |screen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408269] New: Applications launch in the wrong monitor sometimes.
https://bugs.kde.org/show_bug.cgi?id=408269 Bug ID: 408269 Summary: Applications launch in the wrong monitor sometimes. Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: manuelcha...@gmail.com Target Milestone: --- (I'm not sure if this is the right component, I had no idea where to put this) STEPS TO REPRODUCE 1. Have 2 monitors 2. Click on a icon only task in the taskbar of the first monitor to launch an application OBSERVED RESULT Sometimes it starts the applications in the second monitor. EXPECTED RESULT It should always start in the monitor where it was launched. Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-20-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4690K CPU @ 3.50GHz Memory: 15,6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402446] Konsole Column Count is Incorrect
https://bugs.kde.org/show_bug.cgi?id=402446 Oleg Girko changed: What|Removed |Added CC||ol+...@infoserver.ru -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408268] On Yiynova/tablet screen Disconnect Krita popup windows show on wrong screen
https://bugs.kde.org/show_bug.cgi?id=408268 Bollebib changed: What|Removed |Added OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408268] New: On Yiynova/tablet screen Disconnect Krita popup windows show on wrong screen
https://bugs.kde.org/show_bug.cgi?id=408268 Bug ID: 408268 Summary: On Yiynova/tablet screen Disconnect Krita popup windows show on wrong screen Product: krita Version: 4.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- When krita is open when Yiynova Disconnects (maybe any screen tablet)The popu windows for rightclicking on ,for example, layers show on the wrong screen You need to restart krita to get the correct popups back It would be good to not waste time to have krita be able tobe able to reset the correct window in such a case when i'm streaming and this happens i lose 3-5 m setting up again -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379339] My Krita keeps crashing
https://bugs.kde.org/show_bug.cgi?id=379339 Samuel Barber changed: What|Removed |Added CC||sambarber0...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 408267] New: Input field labels missing in installer
https://bugs.kde.org/show_bug.cgi?id=408267 Bug ID: 408267 Summary: Input field labels missing in installer Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: mue...@fribbledom.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 120538 --> https://bugs.kde.org/attachment.cgi?id=120538&action=edit Missing labels in installer SUMMARY When trying to install Neon on an encrypted LVM, two unlabeled input fields are showing up. I assume I'm supposed to enter the encryption password here, but I really don't know. See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 359662] Terminal Rows are miscalculated if Menu Bar is turned off
https://bugs.kde.org/show_bug.cgi?id=359662 Oleg Girko changed: What|Removed |Added CC||ol+...@infoserver.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408250] Progress not display for transfer status in notifications
https://bugs.kde.org/show_bug.cgi?id=408250 --- Comment #11 from Nate Graham --- Wait a minute, what version of KDE Plasma are you using> Not OpenSUSE, but Plasma itself. You can find this in the Info Center app. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408266] New: Grab the active window not possible
https://bugs.kde.org/show_bug.cgi?id=408266 Bug ID: 408266 Summary: Grab the active window not possible Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: aligatortur...@gmail.com Target Milestone: --- SUMMARY I just installed latte-dock from git on opensuse tumbleweed and I am unable to use latte's empty space to grab the active window. No errors whatsoever during installation. 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.
[kscreenlocker] [Bug 346741] bring back "auto-lock screen on login" option from KDM/Plasma 4
https://bugs.kde.org/show_bug.cgi?id=346741 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408250] Progress not display for transfer status in notifications
https://bugs.kde.org/show_bug.cgi?id=408250 --- Comment #10 from Юрий --- Created attachment 120537 --> https://bugs.kde.org/attachment.cgi?id=120537&action=edit new dbus log with openSUSE Leap 15.1 update system 15.0 => 15.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408265] The stacked images tool appears to be non-functional
https://bugs.kde.org/show_bug.cgi?id=408265 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Plugin-Generic-ExpoBlending CC||caulier.gil...@gmail.com Platform|Windows CE |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408251] Preview does not work with title clips
https://bugs.kde.org/show_bug.cgi?id=408251 RafaMar changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from RafaMar --- This problem is resolved in kdenlive-19.04.2-e782377-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408265] The stacked images tool appears to be non-functional
https://bugs.kde.org/show_bug.cgi?id=408265 James M. Orr changed: What|Removed |Added Attachment #120535|0 |1 is obsolete|| --- Comment #2 from James M. Orr --- Created attachment 120536 --> https://bugs.kde.org/attachment.cgi?id=120536&action=edit console report on stacked image operation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408265] The stacked images tool appears to be non-functional
https://bugs.kde.org/show_bug.cgi?id=408265 --- Comment #1 from James M. Orr --- Created attachment 120535 --> https://bugs.kde.org/attachment.cgi?id=120535&action=edit Console re -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408265] New: The stacked images tool appears to be non-functional
https://bugs.kde.org/show_bug.cgi?id=408265 Bug ID: 408265 Summary: The stacked images tool appears to be non-functional Product: digikam Version: 6.1.0 Platform: Windows CE OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: jorr1...@earthlink.net Target Milestone: --- SUMMARY I am copying slides, and am making three CR2 images at EV 0, 1.5, and 3. I have been using Aurora HDR 2019 in batch mode. It is fast and easy. I decided to try the stacked images tool in DigiKam. The opening window shows align_image_stack as version 2019.0.0; it shows enfuse as version 4.3 (this is confusing because the enfuse/enblend web site only has version 4.2). I selected 3 CR2 images as a test. I made sure that I highlighted them in the stacked images window. It has now been 20 minutes and the Pre-processing Bracketed Images indicates that the process in under progress, and tells me this can take a while. This long is wrong. I wonder what is going on. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Operating System Windows 10 Professional (x64) Version 1803 (build 17134.765) Install Language: English (United States) System Locale: English (United States) Installed: 2/21/2019 11:48:09 AM Servicing Branch: Current Branch (CB) Boot Mode: Legacy BIOS in UEFI (Secure Boot not supported) System Model CyberPowerPC C SERIES Enclosure Type: Desktop Processor a 3.70 gigahertz Intel Core i7-8700K 384 kilobyte primary memory cache 1536 kilobyte secondary memory cache 12288 kilobyte tertiary memory cache 64-bit ready Multi-core (6 total) Hyper-threaded (12 total) Main Circuit Board b Board: ASRock Z370 SLI Xtreme Serial Number: M80-B1003800527 Bus Clock: 100 megahertz UEFI: American Megatrends Inc. P1.30 11/27/2017 Drives 3479.98 Gigabytes Usable Hard Drive Capacity 2966.51 Gigabytes Hard Drive Free Space ASUS DRW-24F1ST d [Optical drive] hp DVD-RAM GH40L [Optical drive] ADATA SU650 [Hard drive] (480.10 GB) -- drive 0, s/n AA0287, rev Q1124A0, SMART Status: Healthy Generic- Compact Flash USB Device [Hard drive] -- drive 4 Generic- MS/MS-Pro USB Device [Hard drive] -- drive 6 Generic- SD/MMC USB Device [Hard drive] -- drive 3 Generic- SM/xD-Picture USB Device [Hard drive] -- drive 5 TOSHIBA DT01ACA300 [Hard drive] (3000.59 GB) -- drive 2, s/n 38RJ5KJAS, rev MX6OABB0, SMART Status: Healthy TOSHIBA DT01ACA300 [Hard drive] (3000.59 GB) -- drive 1, s/n 38RJ5MLAS, rev MX6OABB0, SMART Status: Healthy Memory Modules c,d 16318 Megabytes Usable Installed Memory Slot 'ChannelA-DIMM0' is Empty Slot 'ChannelA-DIMM1' has 8192 MB (serial number 1B9E) Slot 'ChannelB-DIMM0' is Empty Slot 'ChannelB-DIMM1' has 8192 MB (serial number 4476) Local Drive Volumes c: (NTFS on drive 0) * 479.53 GB 355.38 GB free d: (NTFS on drive 2)3000.46 GB 2611.13 GB free * Operating System is installed on c: Network Drives None detected ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 408264] New: Notification area is shown just once (Wayland)
https://bugs.kde.org/show_bug.cgi?id=408264 Bug ID: 408264 Summary: Notification area is shown just once (Wayland) Product: frameworks-knotifications Version: 5.58.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: m...@rainer-finke.de CC: kdelibs-b...@kde.org Target Milestone: --- If notifications are shown once on Plasma Wayland, they cannot be viewed again. Sometimes the hole notification area will not show any information anymore and becomes inaccessible, but e.g. the calendar will be shown without any issues. This worked OK previously with the old notification system, so this seems like a regression. STEPS TO REPRODUCE 1. Copy a big file and paste it to another folder 2. Hide the popup notification or minimize it OBSERVED RESULT You cannot view the notification area again even if it must be there. EXPECTED RESULT Show the notification area on Wayland. SOFTWARE/OS VERSIONS KDE Plasma: 5.15.90 KDE Frameworks Version: 5.58 Qt Version: 5.13 beta4 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 408263] Pop up window: buttons aren't complete
https://bugs.kde.org/show_bug.cgi?id=408263 Christoph Feck changed: What|Removed |Added Product|Active Window Control |korganizer Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO Component|General |general Assignee|zrenf...@gmail.com |kdepim-b...@kde.org --- Comment #1 from Christoph Feck --- Which version of Mint is this? When KOrganizer version? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 Christoph Feck changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 --- Comment #9 from Christoph Feck --- *** Bug 408218 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 408218] Crash when entering ~./Fonts in Dolphin
https://bugs.kde.org/show_bug.cgi?id=408218 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Christoph Feck --- Indeed. *** This bug has been marked as a duplicate of bug 401031 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Editable Selection Outlines
https://bugs.kde.org/show_bug.cgi?id=408149 Leo changed: What|Removed |Added Summary|Selection Transformation|Editable Selection Outlines |not available via Selection | |Tool. | --- Comment #14 from Leo --- Yes, exactly the selection made, the outline, not the content. I see now that the selection outline can be moved, by hovering over it. Thus what I am suggesting is when hovering over the corners of the outline, that would enable resizing of the selection. Take a look at how GIMP handles resizing of the selection outlines. And before you say it, yes, I know, this is Krita and not GIMP. Editable selections outlines would be a very handy feature. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 408263] New: Pop up window: buttons aren't complete
https://bugs.kde.org/show_bug.cgi?id=408263 Bug ID: 408263 Summary: Pop up window: buttons aren't complete Product: Active Window Control Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: t.er...@web.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 120534 --> https://bugs.kde.org/attachment.cgi?id=120534&action=edit Buttons are never complete. SUMMARY STEPS TO REPRODUCE 1. Set a date in the window 2. And delete it 3. Pop up appears with uncomplete button. 4. This happens with all popup buttons! OBSERVED RESULT Buttons are not fully visual EXPECTED RESULT See photo SOFTWARE/OS VERSIONS Linux mint Tara on a LENOVO Yoga 920 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408262] New: Dolphin crashed when copying files between tabs
https://bugs.kde.org/show_bug.cgi?id=408262 Bug ID: 408262 Summary: Dolphin crashed when copying files between tabs Product: dolphin Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pedron.alexan...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.18.0-20-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Dolphin crashed when copying files between tabs. I was just doing that. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f662814d6c0 (LWP 10266))] Thread 4 (Thread 0x7f65b700 (LWP 925)): #0 0x7f661ca9c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b8e4a0d170) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b8e4a0d120, cond=0x55b8e4a0d148) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b8e4a0d148, mutex=0x55b8e4a0d120) at pthread_cond_wait.c:655 #3 0x7f66219a759b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f662199fc0b in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f65fd19880c in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so #6 0x7f66219a616d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f661ca966db in start_thread (arg=0x7f65b700) at pthread_create.c:463 #8 0x7f66279d688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f65fecd0700 (LWP 10271)): #0 0x7f661a96a664 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f661a9234b7 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f661a924485 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f661a9246dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6621bdd90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6621b829ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f66219a122a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f66219a616d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f661ca966db in start_thread (arg=0x7f65fecd0700) at pthread_create.c:463 #9 0x7f66279d688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f660a6dd700 (LWP 10270)): #0 0x7f661a96a664 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f661a9245be in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f661a9246dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6621bdd90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6621b829ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f66219a122a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f662205ad45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f66219a616d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f661ca966db in start_thread (arg=0x7f660a6dd700) at pthread_create.c:463 #9 0x7f66279d688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f662814d6c0 (LWP 10266)): [KCrash Handler] #6 __GI___libc_free (mem=0x1) at malloc.c:3103 #7 0x7f6621bb0aed in QObjectPrivate::Connection::~Connection() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6621bb5722 in QObjectPrivate::cleanConnectionLists() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f6621bb5837 in QObjectPrivate::addConnection(int, QObjectPrivate::Connection*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6621bb7774 in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f6621bb7b22 in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f6625f32fc2 in ?? () from /usr/lib/x86_64-linu
[digikam] [Bug 408261] In Metadata editor, "Ok" and "Apply" buttons should save changes for all tabs, not just the active one.
https://bugs.kde.org/show_bug.cgi?id=408261 --- Comment #2 from IWBR --- Thanks Maik! -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 268496] All sent messages get lost, from the inclusion of some URL, until chat window is closed
https://bugs.kde.org/show_bug.cgi?id=268496 --- Comment #5 from Thomas McNicholas --- As far as Bonjour/Zeroconf with Kopete is concerned message transfer works again but file transfer is still broken. The use of Pidgin, Gajim etc. confirms that Avahi is set up correctly since I'm able to communicate and transfer files over the network without error. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 --- Comment #13 from Mauro Carvalho Chehab --- (In reply to awf_ul from comment #11) > confirmed many times that the dvb5zap would start "Record to file 'mpeg.ts' > started", but dump no mpeg.ts file. > > After maybe 20-30 tries, and an overnight time delay, dvb5zap actually > recorded an mpeg.ts file, and at that time kaffeine began to work normally > across many stations. > > After shutting down the app, it would black screen again, dvb5zap created > empty mpeg.ts files again. Same after power cycle. > > It appears to me that for some reason the board (KWorld ATSC110) is not > always initializing properly. > > My system is very stable in all regards, voltages good, though an outside > chance a bad tuner board? If you're having problems with dvbv5-zap too, then indeed it is a hardware problem. There are some alternatives: 1) bad antenna/antenna cabling. Usually PC devices require a stronger/better signal than normal TV sets. So, even if you have a good signal at TV, you may not have a good enough signal for those cheap USB sticks; 2) it could indeed be a broken USB stick that it is starting to fail; 3) If you're using hardware like Raspberry Pi, it could be power problem at USB. There are known problems with USB hardware on some RPi devices that cause the device to restart multiple times. Also, you need very strong power supply, in order to give enough power to RPi3 and still have at least 500 mW for the USB stick, without dropping voltage. The dvbv5-zap has a monitoring mode (-m). It runs the device on "all-pid" mode (just like -P) and checks if there are broken frames, counting them. I suggest you to run it for some time on this mode and see what happens. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 --- Comment #14 from RafaMar --- (In reply to emohr from comment #9) Only note that when you go from none to high quality in the section that there is no transition is still giving an erroneous view and solves restarting the application. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 --- Comment #13 from RafaMar --- Sorry I duplicated a comment -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 --- Comment #12 from RafaMar --- Comment on attachment 120533 --> https://bugs.kde.org/attachment.cgi?id=120533 Test track composer With this version that you indicate to me it goes well when I already have the assembly with the transition of composing and transforming inserted, but if I do not have the transition inserted when I change from none to high quality it is still only visible V1. I feel that I do not know programming and little else I can contribute ... I am an audiovisual technician and I develop well as a computer user, but programming for me is a mystery :-) I attached a project file so you can see what happens with the different composition modes beyond the transitions. Thank you very much for your good work. P.S. I have seen that the problem of the preview is resuleta in this version, so I will indicate it in the bug in which I quoted this. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 --- Comment #11 from RafaMar --- (In reply to emohr from comment #9) With this version that you indicate to me it goes well when I already have the assembly with the transition of composing and transforming inserted, but if I do not have the transition inserted when I change from none to high quality it is still only visible V1. I feel that I do not know programming and little else I can contribute ... I am an audiovisual technician and I develop well as a computer user, but programming for me is a mystery :-) I attached a project file so you can see what happens with the different composition modes beyond the transitions. Thank you very much for your good work. P.S. I have seen that the problem of the preview is resuleta in this version, so I will indicate it in the bug in which I quoted this. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 --- Comment #10 from RafaMar --- Created attachment 120533 --> https://bugs.kde.org/attachment.cgi?id=120533&action=edit Test track composer -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June
https://bugs.kde.org/show_bug.cgi?id=408240 Alexander Semke changed: What|Removed |Added CC||alexander.se...@web.de --- Comment #7 from Alexander Semke --- do you clean your build folder when switching between the different commits? Can you please do make clean and try again with the current master? -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June
https://bugs.kde.org/show_bug.cgi?id=408240 --- Comment #6 from Nikita Sirgienko --- (In reply to vialav from comment #4) > > If the signals and cmake use proper system qt, that will means, what your > > qt broken from June 1, for example, by update. > > That could also mean the difference from Qt on your system and mine. I doubt > you use Qt v5.9.5. $ LANG=en_EN.UTF-8 dpkg -l qt5-default Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===- ii qt5-default:amd64 5.9.5+dfsg-0ubu amd64 Qt 5 development defaults package Also i had checked my qdialogbuttonbox.h and qdialogbuttonbox.h from source via diff and there aren't differents. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407252] Random freezes of Plasma 5
https://bugs.kde.org/show_bug.cgi?id=407252 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #11 from Christoph Feck --- Thanks for the update; changing status. If possible, please also add the bug report from the Mesa/Intel bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load
https://bugs.kde.org/show_bug.cgi?id=322060 --- Comment #158 from Stephan Karacson --- I believe it works now without tripleBuffer quite well on kwin 5.15.5 on Gentoo-GNU/Linux, just to dump a version number here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408261] In Metadata editor, "Ok" and "Apply" buttons should save changes for all tabs, not just the active one.
https://bugs.kde.org/show_bug.cgi?id=408261 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/83445b12286d ||a6e1611efefe17469193fad1132 ||0 Version Fixed In||6.2.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- Git commit 83445b12286da6e1611efefe17469193fad11320 by Maik Qualmann. Committed on 03/06/2019 at 19:43. Pushed by mqualmann into branch 'master'. fix applying the metadata on all tabs FIXED-IN: 6.2.0 M +2-1NEWS M +7-3 core/dplugins/generic/metadata/metadataedit/exif/exifeditwidget.cpp M +7-3 core/dplugins/generic/metadata/metadataedit/iptc/iptceditwidget.cpp M +8-3 core/dplugins/generic/metadata/metadataedit/xmp/xmpeditwidget.cpp https://invent.kde.org/kde/digikam/commit/83445b12286da6e1611efefe17469193fad11320 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 407454] konqueror crash on shutdown
https://bugs.kde.org/show_bug.cgi?id=407454 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 emohr changed: What|Removed |Added Flags||timeline_corruption+ --- Comment #9 from emohr --- @RafAMar Please try with tomorrows Kdenlive_Nightly_Appimage https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ And apply Jean-Baptiste Mardelle comment #7 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June
https://bugs.kde.org/show_bug.cgi?id=408240 --- Comment #5 from vialav --- …then run git checkout $your_version and git log -p $the_file_in_question # down to Qt v5.9.5 Those were my thougts, if it is about a subtle particular change in API. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June
https://bugs.kde.org/show_bug.cgi?id=408240 --- Comment #4 from vialav --- > If the signals and cmake use proper system qt, that will means, what your qt > broken from June 1, for example, by update. That could also mean the difference from Qt on your system and mine. I doubt you use Qt v5.9.5. You may find the full set of headers packaged in Ubuntu on: https://packages.ubuntu.com/src:qtbase-opensource-src and trace the changes by cloning: git://code.qt.io/qt/qtbase.git -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 --- Comment #12 from awf_ul --- https://gofile.io/?c=tlNZN2 - a bit short as it caught me off guard when it began to finally record. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 --- Comment #8 from RafaMar --- (In reply to Jean-Baptiste Mardelle from comment #7) Thank you very much -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408258] Program crashes when opening project
https://bugs.kde.org/show_bug.cgi?id=408258 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #1 from emohr --- Please upload your project file here for testing. Try with the Windows_Nightly_Build: https://binary-factory.kde.org/job/Kdenlive_Nightly_mingw64/lastSuccessfulBuild/artifact/ it could be that this problem is fixed already. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 --- Comment #11 from awf_ul --- confirmed many times that the dvb5zap would start "Record to file 'mpeg.ts' started", but dump no mpeg.ts file. After maybe 20-30 tries, and an overnight time delay, dvb5zap actually recorded an mpeg.ts file, and at that time kaffeine began to work normally across many stations. After shutting down the app, it would black screen again, dvb5zap created empty mpeg.ts files again. Same after power cycle. It appears to me that for some reason the board (KWorld ATSC110) is not always initializing properly. My system is very stable in all regards, voltages good, though an outside chance a bad tuner board? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408260] selection, brush, reset krita
https://bugs.kde.org/show_bug.cgi?id=408260 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #1 from vanyossi --- Hi, please report only one issue for each bug report. With 4 different things its impossible to work with them properly. Pick one, edit and make new bug reports for the other 3. - Selection: it's not clear how you are doing the selections, please elaborate more on the process you follow. I don't get issues with editing selection and move since the move action is not activated if a selection modifier is active. - The gap is indeed quite large to allow easy manipulation of guides. Once you are finished editing guides it is best to "lock guides" - Weird, but it might be realted to the resource manager bugs. I get no issue like that. - could be. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408261] In Metadata editor, "Ok" and "Apply" buttons should save changes for all tabs, not just the active one.
https://bugs.kde.org/show_bug.cgi?id=408261 IWBR changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408261] New: In Metadata editor, "Ok" and "Apply" buttons should save changes for all tabs, not just the active one.
https://bugs.kde.org/show_bug.cgi?id=408261 Bug ID: 408261 Summary: In Metadata editor, "Ok" and "Apply" buttons should save changes for all tabs, not just the active one. Product: digikam Version: 6.2.0 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Metadata-Editor Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY When using the metadata editor, there are three tabs: Edit EXIF, IPTC, and XMP. If any changes are made in several tabs and the Ok or Apply buttons are used, only those changes in the current/active tab will be saved. Right now, you have to click "Apply" before changing to another tab, otherwise the edits are lost. I personally think the "Ok" and "Apply" buttons should save changes made in the three tabs. STEPS TO REPRODUCE 1. Open metadata editor 2. Do some changes on one tab (e.g. change EXIF's Original date and time) 3. Move to another tab (e.g. XMP) 4. Click "Apply" 5. Go back to the previous tab. OBSERVED RESULT Changes in the previous tab have been lost (not applied). EXPECTED RESULT Changes should have been applied even if that tab did not have the focus. SOFTWARE/OS VERSIONS Ubuntu 18.04 with Gnome and digikam-6.2.0-git-20190522T104638-qtwebkit-x86-64.appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #13 from vanyossi --- this wish is confusing I think tweaking the selection made, not the content selected, is what I understand is wished upon. we already have some form of this, as we can move the selection outline by hovering the selection decoration. However for resizing and editing the selection outline it is not as straightforward as moving the outline is. For this you need to enter an editing mode in vector tools which in case you are using global selection mask, looses the layer you were coming from. On the other hand, If the wish is about also transforming the content selected, then I agree with scotty completely. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408240] The Qt buttons no longer work (Qt signals problem) after the code change from 1 June
https://bugs.kde.org/show_bug.cgi?id=408240 --- Comment #3 from vialav --- (For being slow and late I'm sorry, starting from Monday I have much less time for reporting.) There were no doubts that it it the system-wide Qt installation, so to confirm: $ pwd /home/cantor/cantor-19.07.70+git20190603 $ cat $(find -type f -name CMakeCache.txt) | grep Qt5 | grep _DIR Qt5Concurrent_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5Concurrent Qt5Core_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5Core Qt5DBus_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5DBus Qt5Gui_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5Gui Qt5Network_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5Network Qt5PrintSupport_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5PrintSupport Qt5Svg_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5Svg Qt5Test_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5Test Qt5Widgets_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets Qt5XmlPatterns_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5XmlPatterns Qt5Xml_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5Xml Qt5_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5 $ cat $(find -type f -name CMakeCache.txt) | grep QMAKE_EXECUTABLE QMAKE_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/qmake $ locate qdialogbuttonbox.h | grep qt5 /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialogbuttonbox.h /usr/share/qt5/doc/qtwidgets/qdialogbuttonbox.html $ dpkg -S /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialogbuttonbox.h qtbase5-dev:amd64: /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialogbuttonbox.h $ dpkg -l qtbase5-dev … ||/ Name Version Architecture Description +++-=-===--= ii qtbase5-dev:amd64 5.9.5+dfsg-0ubuntu2 amd64Qt 5 base development files $ cat /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialogbuttonbox.h | grep -e rejected -e accepted void accepted(); void rejected(); $ cd /usr/include/x86_64-linux-gnu/qt5/QtWidgets && grep -rnw -e rejected -e accepted 5.9.5/QtWidgets/private/qabstractitemview_p.h:171:// Drag enter event shall always be accepted, if mime type and action match. 5.9.5/QtWidgets/private/qwidgetlinecontrol_p.h:545:void accepted(); qdialog.h:89:void accepted(); qdialog.h:90:void rejected(); qdialogbuttonbox.h:147:void accepted(); qdialogbuttonbox.h:149:void rejected(); -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408260] New: selection, brush, reset krita
https://bugs.kde.org/show_bug.cgi?id=408260 Bug ID: 408260 Summary: selection, brush, reset krita Product: krita Version: 4.2.0-beta Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: laurinchen-...@web.de Target Milestone: --- Created attachment 120532 --> https://bugs.kde.org/attachment.cgi?id=120532&action=edit sensitivity brush to move tool SUMMARY: Since the update to krita 4.2 I've got some issues with the program and I thought I should report them to you. First of all I love the new addition you did, where I can see if I'm adding or substracting something to my selection. But the option to move your selection while you're selecting something is rather inconvenient. If you're too close to the line you're going to shift your selection. while working on smaller areas it happens a lot and I had to adjust my selection everytime to it's original place. The same problem goes with the guidelines you can drag from the left and upper side of your toolbars. if you're working "near" the line it's switchs from pen to move tool. And the gap where it starts to switch is rather large. Another issue, but that's something I also had with the previous version, is renaming and adding an icon to a new created brush/stamp. I followed the tutorial from David Revoy (deevad). But after creating my brush the names and icons got all mixed up with the ones I already had. And I have something I would wish for in Krita: a button or option where you can reset krita to it's default settings including resetting roaming/ app data. As I mentioned before, I had problems to create a brush and during the process it delet an existing brush which I wanted to get back. To do that I had to insert the desired brush into the file "app data". I took me a while to get to that point, so I'm suggesting to add an easier way to do that. Thanks for taking your time to read this. Best regards -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408235] Crop effect not rendering like in project
https://bugs.kde.org/show_bug.cgi?id=408235 Rafael Linux User changed: What|Removed |Added Summary|Crop not rendering like in |Crop effect not rendering |project |like in project -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 --- Comment #86 from plasmapeleng --- Created attachment 120531 --> https://bugs.kde.org/attachment.cgi?id=120531&action=edit baloo_file_extractor log crash I've finished one project and deleted the detritus. Log out / Log in. Crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407252] Random freezes of Plasma 5
https://bugs.kde.org/show_bug.cgi?id=407252 --- Comment #10 from imagina...@mailbox.org --- After a week of normally intense use and without freezes or other problems I'm sure now that it really *was* an unfortunate driver issue as described in my last post. So as far as I'm concerned, you may close this report. Should freezes reoccur, I would re-open it. Thanks for your time! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 --- Comment #7 from Jean-Baptiste Mardelle --- Well, it doesn't fix problem in existing projects. So you need to edit the composition between track V1 and V2, and set the compositing track to V1, then back to "Automatic" and it should work as expected after that. An automatic detection of these cases might be nice I agree, if I find time I will try to add it and warn user on project opening. -- You are receiving this mail because: You are watching all bug changes.
