[digikam] [Bug 405980] The area of a "face rectangle" in the picture is different than the face thumbnail.
https://bugs.kde.org/show_bug.cgi?id=405980 --- Comment #2 from Maik Qualmann --- It could also be related to this problem: https://cgit.kde.org/digikam.git/commit/?id=fa288e9e281e28e52eff1b0f77a9bf3b42f598d6 Please use a current digiKam version. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405980] The area of a "face rectangle" in the picture is different than the face thumbnail.
https://bugs.kde.org/show_bug.cgi?id=405980 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Were the wrong-posed facial rectangles detected by the facial engine or were they set manually? The facial engine times clouds or other objects in the image as a face recognizes is quite normal, these must be rejected only. I can not reproduce other problems. Otherwise upload a image with which the problem occurs. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405980] New: The area of a "face rectangle" in the picture is different than the face thumbnail.
https://bugs.kde.org/show_bug.cgi?id=405980 Bug ID: 405980 Summary: The area of a "face rectangle" in the picture is different than the face thumbnail. Product: digikam Version: 6.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY I thought it was the same as Bug #372340, but I think it's a related issue, or maybe a remnant. In this case, the face rectangle in the picture is correctly positioned and frames the person's face correctly. However, the "face thumbnail" shown in the list is from another area of the picture (e.g. a piece of sky). It's likely the same area that was previously framed as a face rectangle in that bug. They all seem to be vertical pictures, so the problem is likely related to how the image is rotated. It only happens in some cases though, and I've narrowed it down to pictures taken with an Iphone SE and a Sony ILCE-5000. These are likely the same pictures which had a problem with the previous bug. I have experienced this issue in digikam-6.1.0-git-20190325T162715 appimage under Ubuntu 18.04 with the default Gnome desktop environment. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405980] The area of a "face rectangle" in the picture is different than the face thumbnail.
https://bugs.kde.org/show_bug.cgi?id=405980 IWBR changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405969] Underscore character not visible on last line of document
https://bugs.kde.org/show_bug.cgi?id=405969 Lothar changed: What|Removed |Added CC||loh@googlemail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Lothar --- *** This bug has been marked as a duplicate of bug 390665 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390665] underscore character not visible with "Bitstream Vera Sans Mono roman" and "dejavu mono" fonts
https://bugs.kde.org/show_bug.cgi?id=390665 Lothar changed: What|Removed |Added CC||bcoo...@gmail.com --- Comment #10 from Lothar --- *** Bug 405969 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 --- Comment #58 from Savor d'Isavano --- (In reply to David Edmundson from comment #57) > link doens't work Sorry, never used vimeo before. Please try this: https://vimeo.com/327057535?activityReferer=1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405949] software is broken
https://bugs.kde.org/show_bug.cgi?id=405949 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 405464] can not speak text selected
https://bugs.kde.org/show_bug.cgi?id=405464 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405949] software is broken
https://bugs.kde.org/show_bug.cgi?id=405949 --- Comment #2 from joey.ca...@gmail.com --- This is what I mean I have attached a video showing me trying to continue to draw as I have been doing and it constantly stops or crashes very laggy what can I do to make my experience with this software more enjoyable On Thu, Mar 28, 2019 at 1:22 AM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=405949 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Latest Commit|i feel as tho i should | >|recive a refund | > Status|REPORTED|NEEDSINFO > Summary|softwear is brokenn |software is broken > Resolution|--- |WAITINGFORINFO > CC||b...@valdyas.org > > --- Comment #1 from Boudewijn Rempt --- > You say "i feel as tho i should recive a refund" in the Latest Commit > field. If > you bought Krita in the Windows Store, see > > https://support.microsoft.com/en-ae/help/10558/microsoft-store-returning-items-bought-for-exchange-refund > -- you did not buy Krita from the Krita project, but from Microsoft. > > As for the problems you have using Krita, it's pretty much impossible to > figure > out what you actually mean from your report. > > Does "does not save properly" mean you can save, but the results are not > what > you're expecting? Or does it mean you cannot save at all? > > Does "currently will not draw" mean it was possible for you to draw? Have > you > perhaps created a small selection and are trying to draw outside the > selection? > Do you have a drawing tablet, and if so, which one? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390221] Discover item in the Favorite area appears duplicately
https://bugs.kde.org/show_bug.cgi?id=390221 --- Comment #15 from tr...@yandex.com --- (In reply to Ivan Čukić from comment #3) > What is the output of the following command? > > echo 'select * from ResourceLink where targettedResource like "%cover%"' | > sqlite3 ~/.local/share/kactivitymanagerd/resources/database Now the output is: :global|org.kde.plasma.favorites.applications|applications:org.kde.discover.desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 --- Comment #47 from tr...@yandex.com --- I can no longer reproduce this on: Plasma 5.15.3 - KF 5.56.0 - Qt 5.12.2 - openSUSE Tumbleweed 20190325. If someone still has this, try: > $ sqlite3 ~/.local/share/kactivitymanagerd/resources/database "DELETE FROM > 'ResourceLink';" (I don't know if it fixes anything though) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390221] Discover item in the Favorite area appears duplicately
https://bugs.kde.org/show_bug.cgi?id=390221 tr...@yandex.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #14 from tr...@yandex.com --- I can no longer reproduce this on: Plasma 5.15.3 - KF 5.56.0 - Qt 5.12.2 - openSUSE Tumbleweed 20190325. If someone still has this, try: > $ sqlite3 ~/.local/share/kactivitymanagerd/resources/database "DELETE FROM > 'ResourceLink';" (I don't know if it fixes anything though) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405979] New: Allow to unmount removable devices in addition to safely remove
https://bugs.kde.org/show_bug.cgi?id=405979 Bug ID: 405979 Summary: Allow to unmount removable devices in addition to safely remove Product: dolphin Version: 18.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: ash...@linuxcomp.ru Target Milestone: --- It is impossible to unmount removable device's partition without removing device. I was experimenting with preparing bootable usb stick, so I constantly needed mount/unmount partitions on usb stick to check bootability with qemu. It is convenient to mount a partition by just clicking to it, but the problem is that when you want to unmount it, you only have Safely Remove action. I do not know how this works internally (probably uses something like eject function of a usb device), but when you use it, device disappears from Dolphin, and next time you want to mount it, you should physically replug usb stick to your pc. Is there a way how I can again "activate" usb stick to be shown in Dolphin without replugging physically? I have noticed that for partitions of internal devices another function is used, which is called Unmount. Can you please implement it also for removable devices? Workaround 1: unmount via terminal. But it becomes uncomfortable. Workaround 2: add a second partition to usb stick and never mount it. When you click Safely Remove on a first partition, then both partitions disappears, but then appears again after a second. Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.4-arch1-1-ARCH -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 QIN Yuhao changed: What|Removed |Added CC||qinq_...@buaa.edu.cn -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405915] Firefox extension installation popup unclickable under kwin
https://bugs.kde.org/show_bug.cgi?id=405915 merilius changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #8 from merilius --- I figured out thanks to help in Arch Linux forum: It depends on window focus settings in kwin. I had focusPolicy = 3, when the firefox dialog was unclickable. The problem disappears when focusPolicy <= 2, i.e. anything else than focus strictly under mouse. PS. Some semantics: in focus settings it says "focus under mouse". Mouse it a physical device, and is not even used by most laptop users. Focus is under _cursor_, a graphical entity. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405978] New: Crash when changing scaling
https://bugs.kde.org/show_bug.cgi?id=405978 Bug ID: 405978 Summary: Crash when changing scaling Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: aleix...@kde.org Target Milestone: --- SUMMARY After disconnecting a display, kwin/kscreen chose the wrong scaling. I changed it to fix it and everything crashed. OBSERVED RESULT #0 0x7f8220d018b8 in () at /usr/lib/libwayland-server.so.0 #1 0x7f8220d01aff in wl_resource_post_error () at /usr/lib/libwayland-server.so.0 #2 0x7f8220d03279 in () at /usr/lib/libwayland-server.so.0 #3 0x7f8220d047f2 in wl_event_loop_dispatch () at /usr/lib/libwayland-server.so.0 #4 0x7f82269705fe in KWayland::Server::Display::Private::dispatch() (this=0x555634153f30) at /home/apol/devel/frameworks/kwayland/src/server/display.cpp:146 #5 0x7f82269763b8 in KWayland::Server::Display::Private::installSocketNotifier()::$_0::operator()() const (this=0x555634137d90) at /home/apol/devel/frameworks/kwayland/src/server/display.cpp:114 #6 0x7f8226976366 in QtPrivate::FunctorCall, QtPrivate::List<>, void, KWayland::Server::Display::Private::installSocketNotifier()::$_0>::call(KWayland::Server::Display::Private::installSocketNotifier()::$_0&, void**) (f=..., arg=0x7fff47c6f1e0) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:146 --Type for more, q to quit, c to continue without paging-- #7 0x7f8226976331 in QtPrivate::Functor::call, void>(KWayland::Server::Display::Private::installSocketNotifier()::$_0&, void*, void**) (f=..., arg=0x7fff47c6f1e0) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:256 #8 0x7f82269762dd in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x555634137d80, r=0x555634142dd0, a=0x7fff47c6f1e0, ret=0x0) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:439 #9 0x7f8224207da8 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=, r=0x555634142dd0, this=0x555634137d80) at ../../include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:394 #10 0x7f8224207da8 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x55563413b050, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff47c6f1e0) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qobject.cpp:3774 #11 0x7f8224208205 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55563413b050, m=m@entry=0x7f82246acc00 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff47c6f1e0) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qobject.cpp:3646 #12 0x7f82242148da in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (this=this@entry=0x55563413b050, _t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:140 #13 0x7f8224214d91 in QSocketNotifier::event(QEvent*) (this=0x55563413b050, e=0x7fff47c6f4f0) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qsocketnotifier.cpp:266 #14 0x7f82251d121d in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x5556341024b0, receiver=receiver@entry=0x55563413b050, e=e@entry=0x7fff47c6f4f0) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3736 #15 0x7f82251d8f9b in QApplication::notify(QObject*, QEvent*) (this=0x7fff47c6fee0, receiver=0x55563413b050, e=0x7fff47c6f4f0) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3093 #16 0x7f82241d4ffb in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55563413b050, event=0x7fff47c6f4f0) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1060 #17 0x7f82241d5256 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1450 #18 0x7f8224234bf1 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=this@entry=0x555634115a20) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:304 #19 0x7f8224235112 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:509 #20 0x7f821b4499e3 in QUnixEventDispatcherQPA::processEvents(QFlags) (this=, flags=...) at /home/apol/devel/frameworks/qt5/qtbase/src/platformsupport/eventdispatchers/qunixeventdispatcher.cpp:63 #21 0x7f82241d2ea7 in QEventLoop::processEvents(QFlags) (this=this@entry=0x7fff47c6f680, flags=..., flags@entry=...) at /usr/include/c++/8.2.1/bits/atomic_base.h:707 #22 0x7f82241d32ff in
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 --- Comment #13 from George L. Emigh --- Tried it again, still refuses to read large emails, back to Thunderbird - sigh View source opens it... Gentoo Qt: 5.12.2 KDE Frameworks: 5.56.0 kf5-config: 1.0 kmail2 5.10.3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405831] Crash with audio clips in Kdenlive Win 19.04beta-git2019
https://bugs.kde.org/show_bug.cgi?id=405831 --- Comment #9 from Justin Irwin --- 1803 build 17134.648 -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 390024] "Compare" button not enabled on the initial dialog even after filling the file names
https://bugs.kde.org/show_bug.cgi?id=390024 --- Comment #13 from Mikle --- ... kompare-18.12.3 and git-version. Not usable. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 390024] "Compare" button not enabled on the initial dialog even after filling the file names
https://bugs.kde.org/show_bug.cgi?id=390024 Mikle changed: What|Removed |Added CC||gramoz...@rocketmail.com --- Comment #12 from Mikle --- This is still present in the last realize: Plasma 5.15.3 Frameworks 5.56(and 5.55) Qt 5.12.2 In dialog "select files" to diff, the "Compare" button is still disabled. In next dialog "Kompare" → "aplication for diff", select any valid aplications not effect. (Meld work fine, diff at console work fine) in console nothing errors. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405971] [Wayland] "Fall apart" effect only should be triggered when a window is closed
https://bugs.kde.org/show_bug.cgi?id=405971 --- Comment #2 from Vlad Zagorodniy --- (In reply to Martin Flöser from comment #1) > On Wayland we don't have window types yet, so it's tricky to get this done. I think isPopupWindow() could be used to filter out popups though not dialogs... :( -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 405977] New: Spectacle snap crashes on startup
https://bugs.kde.org/show_bug.cgi?id=405977 Bug ID: 405977 Summary: Spectacle snap crashes on startup Product: neon Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Snaps Assignee: sit...@kde.org Reporter: blkel...@comcast.net CC: neon-b...@kde.org Target Milestone: --- SUMMARY I tried installing and using the Spectacle snap on Kubuntu 18.04 (I wanted to try the latest version), but it crashes on startup due to a missing library. STEPS TO REPRODUCE 1. $ sudo snap install spectacle 2. $ snap run spectacle OBSERVED RESULT "spectacle: error while loading shared libraries: libxcb-cursor.so.0: cannot open shared object file: No such file or directory" EXPECTED RESULT Launches Spectacle. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION $ snap info spectacle name: spectacle summary: Screenshot capture utility, replaces KSnapshot publisher: KDE✓ contact: https://bugs.kde.org/enter_bug.cgi?product=neon=Snaps license: unset description: | Spectacle captures images of the screen. It can capture the whole screen, a specified region, an individual window, or only part of a window. commands: - spectacle snap-id: tg12Jrs93ndp40AEQnlbuMbtmVJ6ZPpk tracking: stable refresh-date: today at 16:20 CDT channels: stable:18.12.32019-03-26 (12) 299kB - candidate: 18.12.32019-03-26 (12) 299kB - beta: ↑ edge: master+aa9600c 2019-03-26 (11) 180kB - installed: 18.12.3 (12) 299kB - -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405934] "Fall apart" effect does not work with standalone KCMs
https://bugs.kde.org/show_bug.cgi?id=405934 --- Comment #10 from Vlad Zagorodniy --- > No, I don't think it's a race anymore. I added a qDebug statement in FallApartEffect::slotWindowClosed. No windowClosed signal is emitted for the kcm. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 405974] Amarok volume bar requires two wheel scrolls to change at first
https://bugs.kde.org/show_bug.cgi?id=405974 Myriam Schweingruber changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Myriam Schweingruber --- Wich version of Amarok is this about? If you are still running 2.8, please upgrade first. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 405976] New: Filename disappears when switching folders in the copy/move/link dialog
https://bugs.kde.org/show_bug.cgi?id=405976 Bug ID: 405976 Summary: Filename disappears when switching folders in the copy/move/link dialog Product: gwenview Version: 18.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: thomas.sur...@protonmail.com Target Milestone: --- SUMMARY When trying to copy/move/link an image from Gwenview, the 'Name' field in the file dialog, which by default get set to the current file name of the image, will be blanked out if I try to change directory. This only happens if the initial directory does not contain that file to start with, but this is a pretty common case since Gwenview conveniently remembers the last place you copied an image to. STEPS TO REPRODUCE 1. Navigate to a folder with an image 2. Hit F7 to copy that image, select another directory than the current one. 3. Now try to copy again that image (or another image from the current folder), the default name is set to the current image and the default directory to the directory selected in step 2. 4. Try to switch to another directory OBSERVED RESULT The 'Name' field in the dialog box is reset. The file name has to by typed entirely again. EXPECTED RESULT The 'Name' field is unmodified when switching directories. This is maybe be a Qt bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396496] QSQLITE -> MYSQL loses grouping information
https://bugs.kde.org/show_bug.cgi?id=396496 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||6.1.0 --- Comment #4 from Maik Qualmann --- This problem is no longer reproducible, all grouping information is present after migration to MySQL, I close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405564] Upon doubleclicking the application icon for Kdenlive I receive the error 'Cannot find the melt program required for rendering (part of MLT)' suddenly out of the blue. I open t
https://bugs.kde.org/show_bug.cgi?id=405564 --- Comment #18 from Rex Dieter --- Good point, indeed mlt-melt should be searched first to avoid that scenario -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405564] Upon doubleclicking the application icon for Kdenlive I receive the error 'Cannot find the melt program required for rendering (part of MLT)' suddenly out of the blue. I open t
https://bugs.kde.org/show_bug.cgi?id=405564 --- Comment #17 from Christoph Feck --- If there is indeed another binary with the name 'melt', and OSS community thinks this name isn't related to the MLT framework, then maybe the code could check 'mlt-melt' first, then 'melt'. Otherwise, it could still call the wrong binary if both are installed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 385189] Save dialog: Return key only bound to Save button when text field has focus
https://bugs.kde.org/show_bug.cgi?id=385189 Méven Car changed: What|Removed |Added Latest Commit||https://commits.kde.org/kio ||/bea5b68142e4f018a956fd2174 ||152d9a3e0679cf Status|CONFIRMED |RESOLVED Version Fixed In||5.57 Resolution|--- |FIXED --- Comment #10 from Méven Car --- Git commit bea5b68142e4f018a956fd2174152d9a3e0679cf by Méven Car. Committed on 28/03/2019 at 21:34. Pushed by meven into branch 'master'. KFileWidget In saving single file mode an enter/return press on the KDirOperator triggers slotOk Summary: Draw inspiration from inspiration from https://phabricator.kde.org/D12538 for reference. The issue at hand: * the KDirOperator did not signal when it received an enter/return event when it should. * This prevents expected behavior FIXED-IN: 5.57 Test Plan: 1 compile kio and its test kfilewidgettest_saving_gui.cpp 2 launch kfilewidgettest_saving_gui 4 click on an place on the left 5 Hit enter 6 The dialog closes, the filename selected is printed out in the terminal Reviewers: #frameworks, #dolphin, ngraham, dfaure Reviewed By: #dolphin, ngraham, dfaure Subscribers: ngraham, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D19824 M +2-0src/filewidgets/kdiroperator.cpp M +6-0src/filewidgets/kdiroperator.h M +12 -0src/filewidgets/kfilewidget.cpp M +1-0src/filewidgets/kfilewidget.h M +1-0tests/CMakeLists.txt A +58 -0tests/kfilewidgettest_saving_gui.cpp [License: LGPL (v2+)] https://commits.kde.org/kio/bea5b68142e4f018a956fd2174152d9a3e0679cf -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398000] Multi/batch rename fails almost every time
https://bugs.kde.org/show_bug.cgi?id=398000 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||6.1.0 --- Comment #3 from Maik Qualmann --- This problem is no longer reproducible, I close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405564] Upon doubleclicking the application icon for Kdenlive I receive the error 'Cannot find the melt program required for rendering (part of MLT)' suddenly out of the blue. I open t
https://bugs.kde.org/show_bug.cgi?id=405564 --- Comment #16 from Rex Dieter --- Should be fixed by commit, https://cgit.kde.org/kdenlive.git/commit/?id=40ed4ba30ecc34a96a38a7fe768c0dc4e54e8500 I'm verifying now -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389046] Face suggestions disappair each time i confirm one
https://bugs.kde.org/show_bug.cgi?id=389046 --- Comment #7 from Maik Qualmann --- I can not reproduce the problem with the last GIT version of digiKam-6.1.0. It is possible that the problem is resolved. Can you test it please. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 405568] Kmail crashes during startup before any window is displayed
https://bugs.kde.org/show_bug.cgi?id=405568 --- Comment #1 from Andreas --- Workaround: I tried the usual akonadi trickery and also deleting kmail config files, but these things did not help. After finding out that kmail still works for other users, I looked for hints in the strace output and guessed a relationship with "/home/andreas/.local/share/kmail2/autosave/*" Deleting all those files, I am able to start kmail again. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 283678] Distinct session sets per desktop activity
https://bugs.kde.org/show_bug.cgi?id=283678 Aldoo changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Aldoo --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405564] Upon doubleclicking the application icon for Kdenlive I receive the error 'Cannot find the melt program required for rendering (part of MLT)' suddenly out of the blue. I open t
https://bugs.kde.org/show_bug.cgi?id=405564
--- Comment #15 from Rex Dieter ---
FYI, the code in question is in mltconnection.cpp where it hard-codes looking
for "mlt" only:
QString meltPath;
if (qEnvironmentVariableIsSet("MLT_PREFIX"))
meltPath = qgetenv("MLT_PREFIX") + QStringLiteral("/bin/melt") +
exeSuffix;
if (!QFile::exists(meltPath)) {
meltPath = QDir::cleanPath(profilePath +
QStringLiteral("/../../../bin/melt")) + exeSuffix;
}
if (!QFile::exists(meltPath)) {
meltPath = QStandardPaths::findExecutable("melt");
}
KdenliveSettings::setRendererpath(meltPath);
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 405971] [Wayland] "Fall apart" effect only should be triggered when a window is closed
https://bugs.kde.org/show_bug.cgi?id=405971 Martin Flöser changed: What|Removed |Added Flags||Wayland+, X11- -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402123] invalid assembler opcodes for mips32r2
https://bugs.kde.org/show_bug.cgi?id=402123 --- Comment #5 from cote2004-git...@yahoo.com --- (In reply to Petar Jovanovic from comment #4) > cote2004-github, can you check with Valgrind ToT? I have run dc950d964, and also by applying the patch to 3.14.0, and both work like a charm. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405971] [Wayland] "Fall apart" effect only should be triggered when a window is closed
https://bugs.kde.org/show_bug.cgi?id=405971 --- Comment #1 from Martin Flöser --- On Wayland we don't have window types yet, so it's tricky to get this done. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405934] "Fall apart" effect does not work with standalone KCMs
https://bugs.kde.org/show_bug.cgi?id=405934 --- Comment #9 from Martin Flöser --- No, I don't think it's a race anymore. Fall apart only works on normal windows, but the kcm is a dialog. This would be a bug in kcmshell. It doesn't make sense to be a dialog without a transient parent. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 386991] rendering error: Cannot find the melt program required for rendering (part of Mlt)
https://bugs.kde.org/show_bug.cgi?id=386991 Rex Dieter changed: What|Removed |Added Resolution|DOWNSTREAM |DUPLICATE --- Comment #6 from Rex Dieter --- *** This bug has been marked as a duplicate of bug 405564 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405688] Option to move all windows to primary monitor on display change
https://bugs.kde.org/show_bug.cgi?id=405688 Martin Flöser changed: What|Removed |Added Severity|normal |wishlist Component|activities |core Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Martin Flöser --- Please use KWin scripting. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405564] Upon doubleclicking the application icon for Kdenlive I receive the error 'Cannot find the melt program required for rendering (part of MLT)' suddenly out of the blue. I open t
https://bugs.kde.org/show_bug.cgi?id=405564 --- Comment #14 from Rex Dieter --- *** Bug 405953 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405564] Upon doubleclicking the application icon for Kdenlive I receive the error 'Cannot find the melt program required for rendering (part of MLT)' suddenly out of the blue. I open t
https://bugs.kde.org/show_bug.cgi?id=405564 Rex Dieter changed: What|Removed |Added CC||johnand...@posteo.de --- Comment #13 from Rex Dieter --- *** Bug 386991 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405953] fedora 29 kdenlive update no longer finds mlt
https://bugs.kde.org/show_bug.cgi?id=405953 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Rex Dieter --- *** This bug has been marked as a duplicate of bug 405564 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405589] Date taken metadata for video files (start video not used and difference of time)
https://bugs.kde.org/show_bug.cgi?id=405589 Maik Qualmann changed: What|Removed |Added CC||aegor...@gmail.com --- Comment #8 from Maik Qualmann --- *** Bug 401964 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401964] Wrong datestamp video/mp4
https://bugs.kde.org/show_bug.cgi?id=401964 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #8 from Maik Qualmann --- We have a newer bug report because of the same problem. I close this bug, because in the new bug report many example video have been uploaded. Maik *** This bug has been marked as a duplicate of bug 405589 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375375] Various bugs detecting and tagging faces in current 5.4.0 Digikam appimage
https://bugs.kde.org/show_bug.cgi?id=375375 --- Comment #29 from Jens --- Yes agreed. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 405419] Tajikistan Map Update
https://bugs.kde.org/show_bug.cgi?id=405419 --- Comment #14 from Laurent G. --- Good news, I found back my sources of the C plugin, dated from the 2008-06-08 ... Still have little time to check it is still functional. Stay tuned, but patient. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397744] Face recognition not working
https://bugs.kde.org/show_bug.cgi?id=397744 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.1.0 Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Maik Qualmann --- This is not an error, the database has to be trained to get results. I close the bug now. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400140] Digikam crash when exporting on google photos
https://bugs.kde.org/show_bug.cgi?id=400140 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.1.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #29 from Maik Qualmann --- The crash can no longer be reproduced with Exiv2-0.27. I close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402494] Merging down a layer with colourise mask
https://bugs.kde.org/show_bug.cgi?id=402494 Tymond changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kri ||ta/630ce8583cb5a9337aceb2ca ||96f17c2cf1df306e Resolution|--- |FIXED --- Comment #2 from Tymond --- Git commit 630ce8583cb5a9337aceb2ca96f17c2cf1df306e by Agata Cacko. Committed on 28/03/2019 at 20:34. Pushed by tymond into branch 'master'. Disable assert on empty parent in Colorize Mask Before this change, Colorize Mask asserted after flattening or merging with another layer when the image was smaller than 1024px wide and long. After this commit, it shouldn't happen. It was caused by setting the parent dirty just before the parent gets deleted. The request was linked to refreshing area outside the image boundaries; since Colorize Mask didn't and doesn't work outside of the image boundaries, it isn't necessary. NOTE: In case of providing support for Colorize Mask working outside of the canvas boundaries, the decision in this commit might need reevaluation (in case of a need to update the mask there). M +9-1libs/image/lazybrush/kis_colorize_mask.cpp https://commits.kde.org/krita/630ce8583cb5a9337aceb2ca96f17c2cf1df306e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405700] Lensfun supported Camera is missing
https://bugs.kde.org/show_bug.cgi?id=405700 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||6.1.0 --- Comment #15 from Maik Qualmann --- The G9 X is now in the list, I close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375375] Various bugs detecting and tagging faces in current 5.4.0 Digikam appimage
https://bugs.kde.org/show_bug.cgi?id=375375 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||6.1.0 --- Comment #28 from Maik Qualmann --- Point 3 is now also fixed, all possible rotations and flip operations are now possible. It does not matter if you only change the metadata flag or if the image data is rotated. Point 5 is also fixed, with cursor up/down or image up/down it is possible to scroll over images with unknown face rectangles. I close the bug now, other bug reports cover still existing problems. Maik -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405782] "VEX temporary storage exhausted" when attempting to debug slic3r-pe
https://bugs.kde.org/show_bug.cgi?id=405782 Philippe Waroquiers changed: What|Removed |Added CC||jsew...@acm.org -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 377476] kmahjongg crashes during start
https://bugs.kde.org/show_bug.cgi?id=377476 Christian Trippe changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Christian Trippe --- I also can no longer reproduced the issue with kmahjongg-18.12.3 (Version 0.9) KDE Frameworks 5.55.0 Qt 5.12.1 (kompiliert gegen 5.12.1) -> Closing as FIXED -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405975] Crash when changing Mail Folder name in KMail
https://bugs.kde.org/show_bug.cgi?id=405975 Allen Winter changed: What|Removed |Added Attachment #119108|0 |1 is obsolete|| --- Comment #1 from Allen Winter --- Created attachment 119109 --> https://bugs.kde.org/attachment.cgi?id=119109=edit sigsegv backtrace, less cruft -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405975] New: Crash when changing Mail Folder name in KMail
https://bugs.kde.org/show_bug.cgi?id=405975 Bug ID: 405975 Summary: Crash when changing Mail Folder name in KMail Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: win...@kde.org Target Milestone: --- Created attachment 119108 --> https://bugs.kde.org/attachment.cgi?id=119108=edit sigsegv backtrace SUMMARY Got this crash after renaming a folder in KMail STEPS TO REPRODUCE 1. create new subfolder 2. open its properties dialog and change the folder name 3. click ok OBSERVED RESULT see crash bt EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kontact Version 5.10.90 beta1 KDE Frameworks 5.57.0 Qt 5.11.3 (built against 5.11.3) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 405974] New: Amarok volume bar requires two wheel scrolls to change at first
https://bugs.kde.org/show_bug.cgi?id=405974 Bug ID: 405974 Summary: Amarok volume bar requires two wheel scrolls to change at first Product: amarok Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Toolbar Assignee: amarok-bugs-d...@kde.org Reporter: david.cortes.riv...@gmail.com CC: thomas.luebk...@gmail.com Target Milestone: kf5 Steps to reproduce: * Launch amarok. * Click the volume icon. * Use the mouse wheel to change the volume with the volume bar active. Expected behavior: should change it at the first mouse wheel movement. Actual behavior: after amarok is just launched, changes it only after two mouse wheel scrolls. But after the volume has already been changed in an amarok session, any further attempts to change the volume will work with just one mouse wheel scroll. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399314] Tile manager crash with big brushes. [gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=399314 wolthera changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #1 from wolthera --- I haven't been able to reproduce this since the tile manager fixes, so it might in fact be gone. If it returns I'll reopen. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 405973] New: Volume bar in JuK resets to the maximum after closing
https://bugs.kde.org/show_bug.cgi?id=405973 Bug ID: 405973 Summary: Volume bar in JuK resets to the maximum after closing Product: juk Version: 18.08.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: david.cortes.riv...@gmail.com CC: mp...@kde.org Target Milestone: --- Steps to reproduce: * Play some song in JuK * Adjust the volume by clicking the sound icon and dragging the circle (or whatever the plasma theme shows) within that bar. * Close JuK. * Open JuK again. Expected behavior: the volume bar should resume just where it was before closing it. Actual behavior: the volume bar resets to the maximum, but the volume itself is the same as it was before. Trying to change it while listening to a song will however be a PITA as it will first have to go through the maximum volume downwards to the desired volume. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405943] Crash when saving file with vector layer.
https://bugs.kde.org/show_bug.cgi?id=405943 wolthera changed: What|Removed |Added Summary|Crash when saving. |Crash when saving file with ||vector layer. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405943] Crash when saving.
https://bugs.kde.org/show_bug.cgi?id=405943 --- Comment #2 from wolthera --- this seems to be specifically caused by the vector layers... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405972] New: Baloo crashed
https://bugs.kde.org/show_bug.cgi?id=405972 Bug ID: 405972 Summary: Baloo crashed Product: frameworks-baloo Version: 5.45.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: reinhardau...@gmx.at Target Milestone: --- Application: baloo_file (5.45.0) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.48-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: I was burning a DVD when suddenly, Baloo crashed. :-( I had open Google Chrome, too. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f4eb51e8100 (LWP 3829))] Thread 3 (Thread 0x7f4ea9bbe700 (LWP 16006)): [KCrash Handler] #6 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:102 #7 0x7f4eb41dda93 in memcpy (__len=2067, __src=, __dest=) at /usr/include/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f4ea9bbd997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42 #9 0x7f4eb41cef64 in Baloo::PostingDB::get (this=this@entry=0x7f4ea9bbda80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100 #10 0x7f4eb41db180 in Baloo::WriteTransaction::commit (this=0x7f0e9c015ca0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259 #11 0x7f4eb41d44c2 in Baloo::Transaction::commit (this=this@entry=0x7f4ea9bbdb90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262 #12 0x55887b6b96cd in Baloo::NewFileIndexer::run (this=0x55887ccbbdb0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/newfileindexer.cpp:75 #13 0x7f4eb3636372 in QThreadPoolThread::run (this=0x55887c6b68c0) at thread/qthreadpool.cpp:99 #14 0x7f4eb36390ce in QThreadPrivate::start (arg=0x55887c6b68c0) at thread/qthread_unix.cpp:368 #15 0x7f4eb1c22559 in start_thread (arg=0x7f4ea9bbe700) at pthread_create.c:465 #16 0x7f4eb2bdb81f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f4eaa7ca700 (LWP 3834)): #0 0x7f4eb2bd107b in __GI___poll (fds=0x7f4ea4002de0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4eaf279129 in g_main_context_poll (priority=, n_fds=1, fds=0x7f4ea4002de0, timeout=, context=0x7f4ea4000be0) at gmain.c:4169 #2 g_main_context_iterate (context=context@entry=0x7f4ea4000be0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3863 #3 0x7f4eaf27923c in g_main_context_iteration (context=0x7f4ea4000be0, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7f4eb385cc1b in QEventDispatcherGlib::processEvents (this=0x7f4ea4000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4eb380509a in QEventLoop::exec (this=this@entry=0x7f4eaa7c9ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f4eb36344da in QThread::exec (this=this@entry=0x7f4eb4d01d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:515 #7 0x7f4eb4a91985 in QDBusConnectionManager::run (this=0x7f4eb4d01d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f4eb36390ce in QThreadPrivate::start (arg=0x7f4eb4d01d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #9 0x7f4eb1c22559 in start_thread (arg=0x7f4eaa7ca700) at pthread_create.c:465 #10 0x7f4eb2bdb81f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f4eb51e8100 (LWP 3829)): #0 0x7f4eb2bd107b in __GI___poll (fds=0x55887c658f90, nfds=1, timeout=55952) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4eaf279129 in g_main_context_poll (priority=, n_fds=1, fds=0x55887c658f90, timeout=, context=0x55887c652260) at gmain.c:4169 #2 g_main_context_iterate (context=context@entry=0x55887c652260, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3863 #3 0x7f4eaf27923c in g_main_context_iteration (context=0x55887c652260, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7f4eb385cc1b in QEventDispatcherGlib::processEvents (this=0x55887c6518d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4eb380509a in QEventLoop::exec (this=this@entry=0x7ffd736dc830, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f4eb380d9e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1289 #7 0x55887b6b121c in main (argc=, argv=) at
[kwin] [Bug 405619] kwin won't blur flatpak menus
https://bugs.kde.org/show_bug.cgi?id=405619 --- Comment #7 from Mikel Pérez --- (In reply to Vlad Zagorodniy from comment #6) > (In reply to Mikel Pérez from comment #5) > > xprop: error: Can't grab the mouse. > > I work around that by running xprop and then using only keyboard to open a > popup that I would like to test. fantastic thanks!· this is xprop's output of a nonblurred menu in org.kde.konsole flatpak _NET_WM_USER_TIME(CARDINAL) = 401223988 WM_TRANSIENT_FOR(WINDOW): window id # 0x547 _KDE_NET_WM_SHADOW(CARDINAL) = 88080409, 88080411, 88080412, 88080413, 88080414, 88080415, 88080416, 88080417, 8, 18, 28, 18 _NET_WM_ICON_NAME(UTF8_STRING) = _KDE_NET_WM_DESKTOP_FILE(UTF8_STRING) = "org.kde.konsole" _NET_WM_ICON(CARDINAL) = *snipped* XdndAware(ATOM) = BITMAP WM_NAME(STRING) = _NET_WM_NAME(UTF8_STRING) = "Konsole" _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x3e, 0x7e, 0x0, 0x0 _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, _NET_WM_WINDOW_TYPE_POPUP_MENU, _NET_WM_WINDOW_TYPE_NORMAL _XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1 WM_CLIENT_LEADER(WINDOW): window id # 0x549 WM_HINTS(WM_HINTS): Client accepts input or input focus: True window id # of group leader: 0x549 _NET_WM_PID(CARDINAL) = 2 _NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 88080452 WM_CLASS(STRING) = "konsole", "konsole" WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST WM_NORMAL_HINTS(WM_SIZE_HINTS): user specified location: 436, 431 user specified size: 287 by 252 window gravity: Static -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405235] Slow startup and new file scan on low latency networks
https://bugs.kde.org/show_bug.cgi?id=405235 --- Comment #4 from IWBR --- I see. Don't worry about it. It's mostly a network problem. However, as I mentioned, due to the high latency, Digikam thinks the path is not available, although I can browse to that location using Ubuntu's file manager. Btw, checking for the availability of the trash is a smart solution. However, during those periods of "non availability", Digikam freezes the interface and Ubuntu constantly asks me to force close the app (related to bug #389652?). Not even a menu or a picture can be selected, even when Digikam is seemingly doing nothing. I understand if pictures couldn't be opened, but browsing catched thumbnails or opening menus should be possible even if the collection is momentarily non-available (considering the database is stored locally, of course). Maybe I should open a bug just for this issue? Anyway, I understand it's not Digikam's fault that it takes so long to scan new files on a remote location. It's just a bit annoying because the main interface is frozen during that process. Regarding the slow startup, even with new file scan disabled, yep, it can take several minutes even to show the splashscreen and the tray icon, and about 10-12 minutes to show the main interface in my case. Do you think something could be done in this regard? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391298] Kwallet extension save password in binary mode instead text
https://bugs.kde.org/show_bug.cgi?id=391298 --- Comment #2 from Max --- It's very inconvenient that in applications like KWalletManager instead of expected 'Passwords' we got binary blob in weird and undocumented format. It pretty-much defeats the purpose of kwallet as cross-application secure and portable way to store password. I think the priority should be set higher for this bug: extension with bad design is even worse than no extension - it breaks people's expectations and give false hope that some feature is implemented while in reality it isn't. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391298] Kwallet extension save password in binary mode instead text
https://bugs.kde.org/show_bug.cgi?id=391298 Max changed: What|Removed |Added CC||sur...@alumni.ntnu.no -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405971] New: [Wayland] "Fall apart" effect only should be triggered when a window is closed
https://bugs.kde.org/show_bug.cgi?id=405971 Bug ID: 405971 Summary: [Wayland] "Fall apart" effect only should be triggered when a window is closed Product: kwin Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY On Wayland, currently "Fall apart" effect is triggered when menus, context menus, dropdowns and dialogs such to confirm file deletion on Dolphin are closed. STEPS TO REPRODUCE 1. On Wayland session, enable "Fall apart" effect in "Desktop effects" kcm 2. open and close some menu, context menu, dropdown or dialog box EXPECTED RESULT Only trigger "Fall apart" effect when a window is closed, like on X11. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405831] Crash with audio clips in Kdenlive Win 19.04beta-git2019
https://bugs.kde.org/show_bug.cgi?id=405831 --- Comment #8 from emohr --- Which version of Win10 do you have? Type into the search field “winver” and you get i.e: “1803 build 17134” or “1809 build 17763”. Can you insert clips without crash? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pass] [Bug 405970] New: Plasma-pass's icon is too similar to Plasma Vault's
https://bugs.kde.org/show_bug.cgi?id=405970 Bug ID: 405970 Summary: Plasma-pass's icon is too similar to Plasma Vault's Product: plasma-pass Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: dvra...@kde.org Reporter: m...@aidanharris.io Target Milestone: --- Created attachment 119107 --> https://bugs.kde.org/attachment.cgi?id=119107=edit The icons of plasma vault and plasma pass both show on the system tray SUMMARY Looking at the screenshot attached which is Plasma Vault and which is Plasma-Pass? OBSERVED RESULT Both icons look practically the same (they are the same?) so if I didn't know which order the applets were in I wouldn't be able to tell which is which without clicking on them. EXPECTED RESULT It (or Plasma Vault) should use another icon to better differentiate the two ADDITIONAL INFORMATION I'm not sure what icon should be used instead but after looking through many icons I think network-wired-symbolic looks like a good choice (it looks good on the tray and has a key and shield so it's meaning isn't lost either of course it would be used incorrectly because plasma-pass has nothing to do with wired networking...) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405969] New: Underscore character not visible on last line of document
https://bugs.kde.org/show_bug.cgi?id=405969 Bug ID: 405969 Summary: Underscore character not visible on last line of document Product: kate Version: 17.12.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: bcoo...@gmail.com Target Milestone: --- SUMMARY Using the default font the underscore character not visible on last line of document. STEPS TO REPRODUCE 1. Install 17.12.3 on Ubuntu 18.04 using public repo 2. Type the text Hello_There 3. The underscore character is not visible and looks like a space 4. Type a carriage return and type MoreText 5. The underscore character on the first line is now visible OBSERVED RESULT Kate appears to be clipping the display of underscore characters on the last line of documents EXPECTED RESULT Should always be able to see actual characters in the document. Confusing when underscore cannot be distinguished from space. 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.
[Discover] [Bug 405968] New: "Installed (Arch Linux)" is listed twice in "Sources" dropdown
https://bugs.kde.org/show_bug.cgi?id=405968 Bug ID: 405968 Summary: "Installed (Arch Linux)" is listed twice in "Sources" dropdown Product: Discover Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: bugsefor...@gmx.com CC: aleix...@kde.org Target Milestone: --- Created attachment 119106 --> https://bugs.kde.org/attachment.cgi?id=119106=edit screenshot SUMMARY I can't reproduce this bug consistently, apparently it occurs randomly. STEPS TO REPRODUCE 1. install, via Arch repos, an app available from both Arch repos and flathub 2. restart Discover 3. search for the just installed app 4. click on the just installed app listed in the search results 5. click "Sources" dropdown OBSERVED RESULT As we can see in my screenshot, there are two "Installed (Arch Linux)" entries in "Sources" dropdown. EXPECTED RESULT only one "Installed (Arch Linux)" entry SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 405962] Network items overlap or are not drawn
https://bugs.kde.org/show_bug.cgi?id=405962 --- Comment #3 from alex...@gmx.net --- UPDATE TO STEPS TO REPRODUCE 1. Create a host network where you won't assign an IP to your client 2. Try to connect with your client (KDE computer) by DHCP 3. It will endlessly say "Assigning IP" This will give you some time to accomplish the following steps, alternatively connect to any network 4. Select the network which is connecting and has the turning progress circle inside 5. Move your mouse downwards / upwards over other items Voilà! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404622] Discover crashed when closed immediately after opening
https://bugs.kde.org/show_bug.cgi?id=404622 Patrick Silva changed: What|Removed |Added Version|5.15.1 |5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405750] Why is .kde4/share/config/kdeglobals still being created?
https://bugs.kde.org/show_bug.cgi?id=405750 --- Comment #11 from Erik Quaeghebeur --- (In reply to David Edmundson from comment #10) > Why? To avoid clutter in my home directory. Dotfiles/Dotdirs are useful, but if every application just keeps on dumping their stuff there, it's a pain to browse. (Also, some applications like Firefox don't filter out dotfiles in its file save dialog.) The XDG Base Directory Specification that AFAIK KDE as a project intends to support is 7 or more years old and Qt4/KDE4 have been deprecated for 4(?) years now. I guess that at some point this writing out of .kde4/... will cease. I assume that this will be done with deprecation first, where the functionality is still available if explicitly compiled-in or configured, before final removal. So implementing my feature request is essentially preparing for that already. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405967] New: Update notifier does not work as expected when there is update only to a flatpak runtime
https://bugs.kde.org/show_bug.cgi?id=405967 Bug ID: 405967 Summary: Update notifier does not work as expected when there is update only to a flatpak runtime Product: Discover Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updater Assignee: lei...@leinir.dk Reporter: bugsefor...@gmx.com CC: aleix...@kde.org Target Milestone: --- Created attachment 119105 --> https://bugs.kde.org/attachment.cgi?id=119105=edit screenshot SUMMARY See the screenshot please. Update to freedesktop runtime is available, but the update notifier remains hidden in the system tray and its icon is not overlapped by a blue dot. STEPS TO REPRODUCE 1. open discover when there is update only to a flatpak runtime 2. 3. OBSERVED RESULT update notifier remains hidden in the system tray and its icon is not overlapped by a blue dot. EXPECTED RESULT update notificer unhides and it is overlapped by a blue dot. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405750] Why is .kde4/share/config/kdeglobals still being created?
https://bugs.kde.org/show_bug.cgi?id=405750 David Edmundson changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #12 from David Edmundson --- "clutter" is not a compelling reason, so no I would not accept such a patch. As for firefox. Right click -> show hidden files. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405924] ONLY ON RENDERING after a while all trasnitions are misplaced by some seconds...
https://bugs.kde.org/show_bug.cgi?id=405924 --- Comment #3 from emohr --- Which version of Win10 do you have? Type into the search field “winver” and you get i.e: “1803 build 17134” or “1809 build 17763”. I tried to reproduce your problem on Win7 and I don’t have this offset after rendering. But on Win10 it crashes as soon as I load a clip. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405843] kdeconnectd crashes and looses connection with android client after replying to a message.
https://bugs.kde.org/show_bug.cgi?id=405843 Simon changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #3 from Simon --- Glad to hear it! It's not a crash I've seen before, so hopefully this was a one-off. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405750] Why is .kde4/share/config/kdeglobals still being created?
https://bugs.kde.org/show_bug.cgi?id=405750 --- Comment #10 from David Edmundson --- Why? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405966] Show sources more consistently in "Sources" dropdown
https://bugs.kde.org/show_bug.cgi?id=405966 --- Comment #1 from Patrick Silva --- Created attachment 119104 --> https://bugs.kde.org/attachment.cgi?id=119104=edit handbrake is not installed - "community (Arch Linux)" -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405966] New: Show sources more consistently in "Sources" dropdown
https://bugs.kde.org/show_bug.cgi?id=405966 Bug ID: 405966 Summary: Show sources more consistently in "Sources" dropdown Product: Discover Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: bugsefor...@gmx.com CC: aleix...@kde.org Target Milestone: --- Created attachment 119103 --> https://bugs.kde.org/attachment.cgi?id=119103=edit handbrake installed from Arch repos - "Installed (Arch Linux)" When an app is available in both flatpak and distro repos and it only was installed from the distro repos, "Sources" dropdown shows "Installed (Arch Linux)". When the app is not installed or it only was installed via flatpak/flathub, the dropdown shows the repo name, like "community (Arch Linux)". I think this inconsistent because when the app was installed via flatpak/flathub the dropdown does not show "Installed (Flatpak)", it remains "flathub (Flatpak)". See the screenshots please. OBSERVED RESULT inconsistency EXPECTED RESULT show sources more consistently SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405750] Why is .kde4/share/config/kdeglobals still being created?
https://bugs.kde.org/show_bug.cgi?id=405750 --- Comment #9 from Erik Quaeghebeur --- (In reply to David Edmundson from comment #8) > Not really Would you consider changing this bug to a feature request for compile-time or runtime functionality that would allow this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405750] Why is .kde4/share/config/kdeglobals still being created?
https://bugs.kde.org/show_bug.cgi?id=405750 --- Comment #8 from David Edmundson --- Not really -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393332] Switching tabs causes expanded folders to close
https://bugs.kde.org/show_bug.cgi?id=393332 Greg Lepore changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Greg Lepore --- Still happening on Dolphin Version 18.12.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405965] New: Plasma crashes and restart on login
https://bugs.kde.org/show_bug.cgi?id=405965 Bug ID: 405965 Summary: Plasma crashes and restart on login Product: plasmashell Version: 5.12.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: tabaccat...@yahoo.it CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.7) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - Unusual behavior I noticed: Plasma crashes just after Latte dock bar load 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 0x7f1a2de33800 (LWP 22957))] Thread 14 (Thread 0x7f1936a83700 (LWP 23747)): #0 0x7f1a26c9b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564e60eec464) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1a26c9b9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x564e60eec410, cond=0x564e60eec438) at pthread_cond_wait.c:502 #2 0x7f1a26c9b9f3 in __pthread_cond_wait (cond=0x564e60eec438, mutex=0x564e60eec410) at pthread_cond_wait.c:655 #3 0x7f1a27b155ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1a2b89a6a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f1a2b89ab0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f1a27b1417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1a26c956db in start_thread (arg=0x7f1936a83700) at pthread_create.c:463 #8 0x7f1a2740f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f1937484700 (LWP 23653)): #0 0x7f1a26c9b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564e60d7a290) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1a26c9b9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x564e60d7a240, cond=0x564e60d7a268) at pthread_cond_wait.c:502 #2 0x7f1a26c9b9f3 in __pthread_cond_wait (cond=0x564e60d7a268, mutex=0x564e60d7a240) at pthread_cond_wait.c:655 #3 0x7f1a27b155ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1a2b89a6a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f1a2b89ab0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f1a27b1417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1a26c956db in start_thread (arg=0x7f1937484700) at pthread_create.c:463 #8 0x7f1a2740f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f1949586700 (LWP 23527)): #0 0x7f1a27402bf9 in __GI___poll (fds=0x7f1938003ce0, nfds=1, timeout=3435722) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1a21f6c539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1a21f6c64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1a27d4b9bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1a27cf0a1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1a27b0f23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1949c4f747 in KCupsConnection::run() () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f1a27b1417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1a26c956db in start_thread (arg=0x7f1949586700) at pthread_create.c:463 #9 0x7f1a2740f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f196bfff700 (LWP 23447)): #0 0x7f1a26c9b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564e600331f4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1a26c9b9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x564e600331a0, cond=0x564e600331c8) at pthread_cond_wait.c:502 #2 0x7f1a26c9b9f3 in __pthread_cond_wait (cond=0x564e600331c8, mutex=0x564e600331a0) at pthread_cond_wait.c:655 #3 0x7f1a27b155ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1a2b89a6a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f1a2b89ab0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f1a27b1417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1a26c956db in start_thread (arg=0x7f196bfff700) at pthread_create.c:463 #8 0x7f1a2740f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f194bcb0700 (LWP 23445)): #0
[digikam] [Bug 279216] "Resize image" feature is missing some useful options [patch]
https://bugs.kde.org/show_bug.cgi?id=279216 --- Comment #14 from Sambhav Dusad --- Created attachment 119102 --> https://bugs.kde.org/attachment.cgi?id=119102=edit When changing units, previous value should be kept. But I can't access d->wInput->value() OR d->hInput->value() from slotUnitsChanged. And I can access d->resolution->value() from the same slot. Where am I doing wrong? Thanks -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 405964] New: Translation error regarding the disk space used in Dolphin
https://bugs.kde.org/show_bug.cgi?id=405964 Bug ID: 405964 Summary: Translation error regarding the disk space used in Dolphin Product: i18n Version: 15.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: pl Assignee: kdei18n-pl-uw...@lists.sourceforge.net Reporter: rejestra...@pawelpieczyrak.pl Target Milestone: --- POLISH TRANSLATE SUMMARY We właściwościach katalogu w aplikacji Dolphin w sekcji Wykorzystanie urządzenia widnieje informacja o wolnym i zajętym miejscu na dysku. Obecne tłumaczenie wprowadza użytkownika w błąd gdyż zajęte miejsce interpretowane jest jako wolne. OBSERVED RESULT Jak wygląda opis dla mojego dysku, na którym mam zajęte 63 GB: Wykorzystanie urządzenia: 63,0 GiB wolnego z 228,2 Gib (wykorzystano 29%). Sugeruje to, że 63 GiB pozostało wolnego miejsca na dysku podczas gdy tyle miejsca jest zajęte na dysku. EXPECTED RESULT Informacja powinna brzmieć następująco: Wykorzystanie urządzenia: 63 GiB zajętego miejsca z 228,2 GiB (wykorzystano 29%) STEPS TO REPRODUCE 1. Otwórz aplikację Dolphin 2. Wejdź w główny katalog domowy użytkownika, kliknij prawym przyciskiem myszy w puste pole i z rozwijanego menu wybierz Właściwości 3. W nowym oknie kliknij na przycisk Ogólnie i zobacz na samym dole okna napis Wykorzystanie urządzenia SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20190322 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.2-1-default OS Type: 64-bit ENGLISH TRANSLATE SUMMARY In the directory properties in the Dolphin application, the Use of device section shows information about the free and used disk space. The present translation misleads the user because the occupied space is interpreted as free. OBSERVED RESULT What is the description for my drive where I have 63 GB occupied: Device utilization: 63.0 GiB free from 228.2 Gib (29% used). This suggests that 63 GiB has free disk space while so much space is occupied on the disk. EXPECTED RESULT The information should read as follows: Device utilization: 63 GiB occupied space with 228.2 GiB (29% used) STEPS TO REPRODUCE 1. Open the Dolphin application 2. Enter the user's main home directory, right-click in the empty field and select Properties from the drop-down menu 3. In the new window, click on the "General" button and see "Using the device" at the very bottom of the window SOFTWARE / OS VERSIONS Operating System: openSUSE Tumbleweed 20190322 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.2-1-default OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405750] Why is .kde4/share/config/kdeglobals still being created?
https://bugs.kde.org/show_bug.cgi?id=405750 --- Comment #7 from Erik Quaeghebeur --- (In reply to David Edmundson from comment #6) > It's fairly harmless, there's no kde4 deps needed, it's just some config > files. Is there any way to get these under .config instead of under ~? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 331985] [Request] Background settings
https://bugs.kde.org/show_bug.cgi?id=331985 Nick Cross changed: What|Removed |Added CC||k...@goots.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403556] Please add background wallpaper stretching.
https://bugs.kde.org/show_bug.cgi?id=403556 --- Comment #2 from Nick Cross --- Similar to bug 331985 ? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 --- Comment #6 from Will Schmidt --- (In reply to Will Schmidt from comment #4) > So, it looks like the correct value is in the register, we are losing it > somewhere in the cast from float to (raw/hex) on the call to printf. > I'm undecided whether this is simply an improper cast, or if there is > something additionally wrong here. > > tentative patch (attached) while I think on this a bit more... brain-dump update. I've bisected GCC to determine where the behavior changed. looks like the gcc commit referenced here exposed this issue.A sniff test suggests 401827 was also triggered by the same gcc change. commit 93dabbb66cf3e2495c382451f85a0c17c3c326eb (HEAD, refs/bisect/bad) Author: meissner Date: Tue Sep 26 18:04:37 2017 + 2017-09-26 Michael Meissner * config/rs6000/rs6000.md (movsi_from_sf): Adjust code to eliminate doing a 32-bit shift right or vector extract after doing XSCVDPSPN. Use zero_extendsidi2 instead of p8_mfvsrd_4_disf to move the value to the GPRs. (movdi_from_sf_zero_ext): Likewise. (reload_gpr_from_vsxsf): Likewise. (p8_mfvsrd_4_disf): Delete, no longer used. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403556] Please add background wallpaper stretching.
https://bugs.kde.org/show_bug.cgi?id=403556 Nick Cross changed: What|Removed |Added CC||k...@goots.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405494] Problems with Qt's Windows Ink implementation
https://bugs.kde.org/show_bug.cgi?id=405494 Alvin Wong changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-74700 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #57 from David Edmundson --- link doens't work -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 --- Comment #56 from Savor d'Isavano --- Look, I think I have got a reliable way to reproduce the bug. People please take a look and have a try at your end, thank you. Go to System Settings -> Applications -> Default Applications -> Web Browser, change how urls are opened any way you like. Try double-clicking. It should stop working. Take a look at this screencast: https://vimeo.com/user93204887/review/327057535/ba77f5a39c -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 398735] Falkon: Loading Some Pages Freeze Entire Browser
https://bugs.kde.org/show_bug.cgi?id=398735 --- Comment #5 from magib...@hotmail.com --- A simpler website which also suffers from this issue is: https://bit.ly/2FIgvwN I experience accesses to the hard drive each time I change slides in that page. It is then when the reload icon flashes. It seems that the issue can also be avoided by using private browsing. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 342159] Layout preview in settings show random layouts
https://bugs.kde.org/show_bug.cgi?id=342159 Christian Krippendorf changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Christian Krippendorf --- https://commits.kde.org/kmahjongg/837fffbc7e8e95a8a32ca4e3f741117ff877e352 @Albert Registered to phabricator. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405176] unable to add file to internal storage folder
https://bugs.kde.org/show_bug.cgi?id=405176 --- Comment #7 from Philippe ROUBACH --- a kio problem ? -- You are receiving this mail because: You are watching all bug changes.
