[frameworks-kio] [Bug 410381] Opening links should open a new tab in a visible browser
https://bugs.kde.org/show_bug.cgi?id=410381 --- Comment #11 from Ahmad Samir --- If someone stumbles upon this report, here's a better version of my puny script that uses window ID instead of relying on title (if you have two firefox windows with the same title on two different virtual desktops, it's playing a toss-up): #!/bin/bash # get the current virtual desktop number currDesktopNum=$(wmctrl -d | grep -F "*" | cut -d' ' -f1) # get the win id of any firefox window, if any exists, on the current desktop ffWinID=$(wmctrl -l | grep Mozilla\ Firefox | grep -F " "$currDesktopNum" " | head -n1 | perl -p -e 's!([\S]+).+!$1!') # if the win id isn't empty, i.e. there's a firefox window on this desktop, raise that window # then call firefox --new-tab; otherwise call firefox --new-window if [ ! -z "$ffWinID" ]; then wmctrl -i -a "$ffWinID" /usr/bin/firefox --new-tab "$@" else /usr/bin/firefox --new-window "$@" fi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420387] Okular can not open "Okular document archive" files
https://bugs.kde.org/show_bug.cgi?id=420387 Yuri Chornoivan changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||yurc...@ukr.net Resolution|WAITINGFORINFO |NOT A BUG --- Comment #3 from Yuri Chornoivan --- (In reply to shinanqu from comment #2) > Oh it works! Great! Thank you. > > But still, I think it's a bug or a missing feature. Most often I open epub > files and then I just save it on the same filename, or change the prefix. > But I would never come up with the idea to call the suffix .okular. There is > no information I am supposed to do so. >From Okular official handbook: Okular has the "document archiving" feature. This is an Okular-specific format for carrying the document plus various metadata related to it (currently only annotations). You can save a "document archive" from the open document by choosing File → Save As and selecting Okular document archive in the Filter selector. Documents saved this way will get .okular as their filename extension. To open an Okular document archive, just open it with Okular as it would be e.g. a PDF document. https://docs.kde.org/trunk5/en/kdegraphics/okular/annotations.html -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417628] Exclude filter in find/replace files dialog doesn't seem to work
https://bugs.kde.org/show_bug.cgi?id=417628 Mattia Basaglia changed: What|Removed |Added CC||mattia.basag...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420342] Transparency colour not saved
https://bugs.kde.org/show_bug.cgi?id=420342 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #6 from Rebecca Breu --- I still don't know what exactly you are doing, and I can't reproduce any bugs regarding transparency. "Therefor I started to change the background to 'white-transparent'." What do you mean by this? The transparency checkerboard of the canvas? Your layers? Your png export? "This figure should have a transparent background and had it through the whole procedure of making but once saved, the background is white, transparency gone." You should save your images as kra files and only export them to other file formats once you are done. If you don't export the png with "Store alpha channel" enabled, then (and only then) you get to pick a colour at the bottom of the export dialog with which your transparency is going to be replaced and then, yes, the transparency will be gone in the exported png. Even if you open that png up again in Krita. "And in some occasions a soft grey or white shade appears on the saved picture which is invisible in Krita." My guess is that it's there but not very visible on the white-and-grey transparency checkerboard, and just a bit that you wanted to erase but didn't erase completely with the soft eraser because you couldn't see it. If you are working on black and white pictures, it's probably best to either change the colour of the transparency checkerboard (Settings -> Configure Krita -> Display -> Grid Settings -> Transparency Checkerboard), or to add a solid bright colour layer at the bottom of your layer stack and toggle the vibisility of that on and off for checking. And of course toggle visibility off for export. ;) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406403] Tags within Split transaction not reporting correctly
https://bugs.kde.org/show_bug.cgi?id=406403 --- Comment #9 from Ralf Habacker --- (In reply to Ralf Habacker from comment #8) > As can be seen from comment 5, a corresponding patch for 4.8 has been > provided to the best of our knowledge. However, it is currently impossible > to say whether this will not affect other reports. There are two reasons for this: 1. due to the large number of report settings and the many enhancements and adjustments that have been made, the implementation of reports is in a state where adjustments and bug fixes are very susceptible to create hidden interference with other report types and variants, which may lead to deviations or missing results. Since the core of financial applications is the "correct" (in the sense of defined rules) processing and presentation of figures, errors in reports have a huge impact and reduce the reliability and usability of the application. 2. In addition, there are currently no comprehensive tests that allow a developer to quickly determine whether a change to the report implementation will cause unwanted interference. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420324] Unable to load featured apps or check for updates due to spurious network connectivity error
https://bugs.kde.org/show_bug.cgi?id=420324 Fabian Vogt changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||fab...@ritter-vogt.de Resolution|--- |DOWNSTREAM --- Comment #3 from Fabian Vogt --- The root cause is that the main Tumbleweed repo is currently missing the "appdata" file with the appstream info (already being investigated). This causes discover to create a search files transaction for all appstream lookups, which is for some reason slowing it down significantly, although it doesn't actually return any results. Discover just shows the network connectivity error if there are no items on the "featured" page. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420198] Clipboard sync stopped work after 1.14 update
https://bugs.kde.org/show_bug.cgi?id=420198 lubimov.maxim+...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from lubimov.maxim+...@gmail.com --- Works for me in 1.14.2. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418257] App not starting on Android
https://bugs.kde.org/show_bug.cgi?id=418257 --- Comment #8 from Petra Viola Beck --- Also, I've tried all of those signed APKs, all of them failed to install. I didn't check the logs, why. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418257] App not starting on Android
https://bugs.kde.org/show_bug.cgi?id=418257 --- Comment #7 from Petra Viola Beck --- Reinstall doesn't fix it, I'm using the latest working version, which is git 4e672a5 for me. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399324] Scrolling changes sliders, list widgets, and numeric fields, causing unintentional changes to controls on scrollable views
https://bugs.kde.org/show_bug.cgi?id=399324 Karl Szmutny changed: What|Removed |Added CC||sha...@privy.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420410] New: Plasma crashes after second log in, sessions lost after switching user.
https://bugs.kde.org/show_bug.cgi?id=420410 Bug ID: 420410 Summary: Plasma crashes after second log in, sessions lost after switching user. Product: plasmashell Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mineden230...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.4) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.4.6-arch3-1 x86_64 Windowing system: X11 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Plasma crashes after second log in, sessions lost after switching user. When I click on switch user I go to SDDM screen. When I log in another user and then in mine, my session lost. When I log in my user Plasma crashes. The crash can be reproduced every time. -- Backtrace: Application: Плазма (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f081b251840 (LWP 6429))] Thread 7 (Thread 0x7f07f1ff8700 (LWP 6977)): #0 0x7f081ed1ecf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f081f8deac4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f081f8deba2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f08216405cb in () at /usr/lib/libQt5Quick.so.5 #4 0x7f082164085b in () at /usr/lib/libQt5Quick.so.5 #5 0x7f081f8d8dd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7f081ed1846f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f081f55f3d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f07fd9a0700 (LWP 6682)): #0 0x7f081ed1ecf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f081f8deac4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f081f8deba2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f08216405cb in () at /usr/lib/libQt5Quick.so.5 #4 0x7f082164085b in () at /usr/lib/libQt5Quick.so.5 #5 0x7f081f8d8dd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7f081ed1846f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f081f55f3d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f0806109700 (LWP 6568)): #0 0x7f081dd9a4e4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f081dde9bda in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f081ddeb448 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f081ddeb571 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f081fb0c8ac in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f081fab305c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f081f8d7c62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f082157aefb in () at /usr/lib/libQt5Quick.so.5 #8 0x7f081f8d8dd6 in () at /usr/lib/libQt5Core.so.5 #9 0x7f081ed1846f in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f081f55f3d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f0806931700 (LWP 6562)): #0 0x7f081ed1ecf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f081f8deac4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f081f8deba2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f08216405cb in () at /usr/lib/libQt5Quick.so.5 #4 0x7f082164085b in () at /usr/lib/libQt5Quick.so.5 #5 0x7f081f8d8dd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7f081ed1846f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f081f55f3d3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f0813fff700 (LWP 6506)): #0 0x7f081f554abf in poll () at /usr/lib/libc.so.6 #1 0x7f081ddeb4a0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f081ddeb571 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f081fb0c8ac in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f081fab305c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f081f8d7c62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f08212db389 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f081f8d8dd6 in () at /usr/lib/libQt5Core.so.5 #8 0x7f081ed1846f in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f081f55f3d3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f0819541700 (LWP 6473)): #0 0x7f081f5504fc in read () at /usr/lib/libc.so.6 #1 0x7f081dd9a8c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f081d
[frameworks-kirigami] [Bug 420404] Kirigami.Card is pixel misaligned
https://bugs.kde.org/show_bug.cgi?id=420404 Arjen Hiemstra changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Arjen Hiemstra --- *** This bug has been marked as a duplicate of bug 420286 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420286] ShadowedRectangle is not pixel aligned
https://bugs.kde.org/show_bug.cgi?id=420286 Arjen Hiemstra changed: What|Removed |Added CC||uhh...@gmail.com --- Comment #4 from Arjen Hiemstra --- *** Bug 420404 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 419935] Template HTML file is lacking doctype, has not very useful meta tag
https://bugs.kde.org/show_bug.cgi?id=419935 gszymas...@short.pl changed: What|Removed |Added Assignee|fa...@kde.org |gszymas...@short.pl -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420407] Crash in systemsetting
https://bugs.kde.org/show_bug.cgi?id=420407 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 419118 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419118] System settings crash while opening translucency config
https://bugs.kde.org/show_bug.cgi?id=419118 David Edmundson changed: What|Removed |Added CC||angschm...@gmail.com --- Comment #11 from David Edmundson --- *** Bug 420407 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405573] "Touch Screen" KCM sets action to "Present windows - Current desktop" despite I select "Present windows - All desktops"
https://bugs.kde.org/show_bug.cgi?id=405573 Cyril Rossi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/01314f8e9a7315e35e0169c8f ||b99899d09a9692f --- Comment #7 from Cyril Rossi --- Git commit 01314f8e9a7315e35e0169c8fb99899d09a9692f by Cyril Rossi. Committed on 22/04/2020 at 09:09. Pushed by crossi into branch 'master'. KCM KWinTouchScreen port to KConfigXT Summary: Also manage KCModule states (isSaveNeeded and isDefaults) Test Plan: * exec kcmshell5 kwintouchscreen * In an edge, select action Present windows - All desktops, then apply * close and reopen * Should display action Present windows - All desktops in the previously selected edge. * Do same test with Present windows - current desktop Reviewers: #kwin, ervin, bport, meven, zzag Reviewed By: #kwin, ervin, meven, zzag Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D27862 M +3-1kcmkwin/kwinscreenedges/CMakeLists.txt A +217 -0kcmkwin/kwinscreenedges/kwinscreenedge.cpp [License: GPL (v2)] A +83 -0kcmkwin/kwinscreenedges/kwinscreenedge.h [License: GPL (v2)] A +45 -0kcmkwin/kwinscreenedges/kwintouchscreenedgeconfigform.cpp [License: GPL (v2)] A +52 -0kcmkwin/kwinscreenedges/kwintouchscreenedgeconfigform.h [License: GPL (v2)] A +14 -0kcmkwin/kwinscreenedges/kwintouchscreenscriptsettings.kcfg A +7-0kcmkwin/kwinscreenedges/kwintouchscreenscriptsettings.kcfgc A +56 -0kcmkwin/kwinscreenedges/kwintouchscreensettings.kcfg A +7-0kcmkwin/kwinscreenedges/kwintouchscreensettings.kcfgc M +157 -283 kcmkwin/kwinscreenedges/touch.cpp M +18 -24 kcmkwin/kwinscreenedges/touch.h M +2-2kcmkwin/kwinscreenedges/touch.ui https://commits.kde.org/kwin/01314f8e9a7315e35e0169c8fb99899d09a9692f -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420411] New: digiKam Crash on detect faces 7.0.0 beta3 debug build
https://bugs.kde.org/show_bug.cgi?id=420411 Bug ID: 420411 Summary: digiKam Crash on detect faces 7.0.0 beta3 debug build Product: digikam Version: 7.0.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: stefan.szeke...@gmail.com Target Milestone: --- SUMMARY When scanning for faces, digiKam instantly crashes STEPS TO REPRODUCE 1. connect network drive with photos under /Volumes/photos 2. go to people tab 3. select scan again and merge results, Detect Faces, search in: Whole albums collection, work on all processors, face accuracy 85% 4. Scan collection for faces OBSERVED RESULT Crash 50% reproduction rate EXPECTED RESULT no crash Process: digikam [76962] Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam Identifier:digikam Version: 7.0.0 (7.0.0-beta3) Code Type: X86-64 (Native) Parent Process:??? [1] Responsible: digikam [76962] User ID: 501 Date/Time: 2020-04-22 12:16:11.662 +0300 OS Version:Mac OS X 10.14.5 (18F132) Report Version:12 Bridge OS Version: 3.0 (14Y901) Anonymous UUID:640A05BC-CE71-FC62-2810-57378A7673CE Sleep/Wake UUID: 63D298DB-2A41-4C53-A8B2-4A0DF4E9047A Time Awake Since Boot: 40 seconds Time Since Wake: 5600 seconds System Integrity Protection: disabled Crashed Thread:32 Thread (pooled) Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0038 Exception Note:EXC_CORPSE_NOTIFY Termination Signal:Segmentation fault: 11 Termination Reason:Namespace SIGNAL, Code 0xb Terminating Process: exc handler [76962] VM Regions Near 0x38: --> __TEXT 000106219000-000106227000 [ 56K] r-x/r-x SM=COW /opt/digikam/*/digikam.app/Contents/MacOS/digikam Thread 0:: CrBrowserMain Dispatch queue: com.apple.main-thread 0 libsystem_malloc.dylib 0x7fff59b5329e nanov2_allocate_from_block + 282 1 libsystem_malloc.dylib 0x7fff59b52a61 nanov2_allocate + 130 2 libsystem_malloc.dylib 0x7fff59b5298e nanov2_malloc + 56 3 libsystem_malloc.dylib 0x7fff59b45dfd malloc_zone_malloc + 103 4 libsystem_malloc.dylib 0x7fff59b45d79 malloc + 24 5 libc++abi.dylib 0x7fff56c1a378 operator new(unsigned long) + 40 6 org.qt-project.QtCore 0x00010ab4cd16 QObject::QObject(QObject*) + 34 7 libdigikamcore.7.0.0.dylib 0x000107df6d1d Digikam::WorkerObject::WorkerObject() + 29 8 libdigikamgui.7.0.0.dylib 0x00010676c180 Digikam::DetectionWorker::DetectionWorker(Digikam::FacePipeline::Private*) + 32 9 libdigikamgui.7.0.0.dylib 0x00010676c1ed Digikam::DetectionWorker::DetectionWorker(Digikam::FacePipeline::Private*) + 29 10 libdigikamgui.7.0.0.dylib 0x0001067564b4 Digikam::FacePipeline::plugParallelFaceDetectors() + 196 11 libdigikamgui.7.0.0.dylib 0x00010660f4c4 Digikam::FacesDetector::FacesDetector(Digikam::FaceScanSettings const&, Digikam::ProgressItem*) + 1220 12 libdigikamgui.7.0.0.dylib 0x0001066100a5 Digikam::FacesDetector::FacesDetector(Digikam::FaceScanSettings const&, Digikam::ProgressItem*) + 37 13 libdigikamgui.7.0.0.dylib 0x000106372953 Digikam::PeopleSideBarWidget::slotScanForFaces() + 131 14 libdigikamgui.7.0.0.dylib 0x00010624de54 Digikam::PeopleSideBarWidget::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 164 15 org.qt-project.QtCore 0x00010ab524bc 0x10a9fe000 + 1393852 16 org.qt-project.QtWidgets0x00010a289c35 0x10a1dd000 + 707637 17 org.qt-project.QtWidgets0x00010a28a467 QAbstractButton::mousePressEvent(QMouseEvent*) + 93 18 org.qt-project.QtWidgets0x00010a21151a QWidget::event(QEvent*) + 1714 19 org.qt-project.QtWidgets0x00010a1e9ab6 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 218 20 org.qt-project.QtWidgets0x00010a1ebee7 QApplication::notify(QObject*, QEvent*) + 6019 21 org.qt-project.QtCore 0x00010ab33774 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 138 22 org.qt-project.QtWidgets0x00010a1ea1dd QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) + 701 23 org.qt-project.QtWidgets0x00010a2246ef 0x10a1dd000 + 292591 24 org.qt-project.QtWidgets0x00010a223b1f 0x10a1dd000 + 289567 25 org.qt-project.QtWidgets0x00010a1e9ab6 QApplicationPrivate::notify_helper(QObje
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 --- Comment #2 from Simon Gardet --- (In reply to Nate Graham from comment #1) > Could you find out what that icon's name is? Yes, like with Gnome (its curious...) and breeze icons in Plasma don't display, I use Papirus Icons for the search (I don't know if is very well). On my screenshot, The weather icons doesn't display and I hadn't noticed. the icons are: weather-clear-night.svg weather-clear.svg weather-clouds-night.svg weather-clouds.svg weather-few-clouds-night.svg weather-few-clouds.svg weather-fog.svg weather-freezing-rain.svg weather-none-available.svg weather-overcast.svg weather-severe-alert.svg weather-showers-scattered.svg weather-showers.svg weather-snow-rain.svg weather-snow-scattered.svg weather-snow.svg weather-storm.svg weather-windy.svg for the icon in the panel I'll try to find it and I reply you. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 420412] New: System Load Properties Cancel button saves
https://bugs.kde.org/show_bug.cgi?id=420412 Bug ID: 420412 Summary: System Load Properties Cancel button saves Product: ksysguard Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.h...@tuta.io CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open KSysGuard 2. Go to the System Load tab 3. Right click a graph 4. Change Title or something else 5. Click Cancel OBSERVED RESULT Changes get saved EXPECTED RESULT Changes get discarded SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 420412] System Load Properties Cancel button saves
https://bugs.kde.org/show_bug.cgi?id=420412 --- Comment #1 from Nico --- Created attachment 127770 --> https://bugs.kde.org/attachment.cgi?id=127770&action=edit Screen recording showing the behaviour -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420411] digiKam Crash on detect faces 7.0.0 beta3 debug build
https://bugs.kde.org/show_bug.cgi?id=420411 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- >Personal notes: should not be doing work on main thread, that blocks the GUI - >>can't open digiKam after it starts detecting. I don't understand this point : all long process are started in separated thread under DK. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 --- Comment #3 from Simon Gardet --- Okay, I was find !!! His name is stock_new-window.svg -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 Simon Gardet changed: What|Removed |Added CC||gardet.si...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358071] Kmail adds wrong contacts to e-mail when using contact groups
https://bugs.kde.org/show_bug.cgi?id=358071 --- Comment #4 from Robert Spillner --- I dug into this bug a little by myself and found out that in order to resolve contact group names into mail addresses kmail does a search via akonadi. When using *spaces* in the contact group names with similar words in both contact group names this search will have multiple results. So if you have two list, say foo bar foo crowbar, and you use "foo crowbar" as recipient the akonadi search query will return "foo bar" and "foo crowbar" since "foo" is in both of them. KMail apparently chooses the first result of the result list, which is "foo bar". As a workaround, if you rename your contact lists to foorbar foocrowbar this will not happen. Unfortunately, KMail does not allow "_" in the names. I guess that there should be a better input validation and masking of the search word in kmail when quering for a contact group. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420413] New: Hotkeys show as duplicate and glitches out
https://bugs.kde.org/show_bug.cgi?id=420413 Bug ID: 420413 Summary: Hotkeys show as duplicate and glitches out Product: systemsettings Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: nicolas.h...@tuta.io CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open System Settings and go to Global Shortcuts 2. Click on the plus and add Konsole 3. Set Launch Konsole to CTRL+Alt+T 4. Click Apply 5. Click on the plus and add another Application 6. Set Launch XYZ to the same keybinding 7. Click reassign 8. Click Default radio button 9. Go back to Konsole OBSERVED RESULT After Step 7 it glitches out and if you click the radio button Default it automatically applies. Also if you go back to Konsole the it is still set to the keybinding. EXPECTED RESULT After Step 7 it should behave normally and if you click the radio button Default it should not apply. Also if you go back to Konsole the it should be set to None SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION I'm sorry if this is not reproducible on your end because it may depend on any settings I made. If you need any files from me you can contact me. Screen Recording showing the behavior (because it was too large for an attachment): https://streamable.com/2xyos0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 420414] New: What I was doing when the application crashed
https://bugs.kde.org/show_bug.cgi?id=420414 Bug ID: 420414 Summary: What I was doing when the application crashed Product: Akonadi Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: christian.holzm...@t-online.de Target Milestone: --- Application: akonadiserver (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-46-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: reboot after successfull upgrade to "eoan ermine" per "do-release-upgrade" -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=16, buf=0x7ffdf3f1ba20, fd=3) at ../sysdeps/unix/sysv/linux/read.c:26 [Current thread is 1 (Thread 0x7f1f5ce46d40 (LWP 2692))] Thread 30 (Thread 0x7f1ef77fe700 (LWP 2736)): #0 0x7f1f5f61cc3d in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1f5f5d0235 in g_main_context_query () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1f5f5d0a28 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1f5f5d0be3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1f60c31653 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1f60bd85cb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x55c74fd1b69e in ?? () #7 0x7f1f60c12696 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1f60c05de5 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f1f60bd9a07 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f1f60c30990 in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f1f60c3126c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1f5f5d08bd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f1f5f5d0b40 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f1f5f5d0be3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f1f60c31635 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f1f60bd85cb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f1f60a11a45 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f1f60a12c92 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f1f5fdbb669 in start_thread (arg=) at pthread_create.c:479 #20 0x7f1f6067d323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f1ef7fff700 (LWP 2732)): #0 __GI___libc_read (nbytes=16, buf=0x7f1ef7ffe710, fd=110) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=110, buf=0x7f1ef7ffe710, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f1f5f61870f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1f5f5d05fe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1f5f5d0a52 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1f5f5d0be3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f1f60c31653 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1f60bd85cb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x55c74fd1b69e in ?? () #9 0x7f1f60c12696 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f1f60c05de5 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f1f60bd9a07 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1f60c30990 in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f1f60c3126c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f1f5f5d08bd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f1f5f5d0b40 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f1f5f5d0be3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f1f60c31635 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f1f60bd85cb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f1f60a11a45 in QThread::exec() () from /usr/lib/x86_64-lin
[plasmashell] [Bug 418767] Plasma crashes repeatedly
https://bugs.kde.org/show_bug.cgi?id=418767 --- Comment #10 from Pavel Florian --- The Opensuse Thumbleweed 20200417 is generally stabil and this bug is performed only by occasionally GUI frozening for few seconds and by unwanted logouts in first three runs of my computer after software upgrade. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420415] New: kde connect three point menu not closing
https://bugs.kde.org/show_bug.cgi?id=420415 Bug ID: 420415 Summary: kde connect three point menu not closing Product: kdeconnect Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: gaertnerjonat...@gmail.com Target Milestone: --- Created attachment 127771 --> https://bugs.kde.org/attachment.cgi?id=127771&action=edit I mean this part of the desktop SUMMARY If i open the kde connect column in the notification bar and open the three point menu i can not close the menu without choosing one option STEPS TO REPRODUCE 1. Update to the newest version (kubuntu with 20.04 LTS) 2. click on the kde connect icon 3. open three point menu OBSERVED RESULT I can not close the menu without choosing an option. Even when im opening other notifications or the wifi or the music icon EXPECTED RESULT I can close the menu by clicking a second time on the three point symbol SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 420416] New: Volume Applet Settings allow invalid characters and textbox expands
https://bugs.kde.org/show_bug.cgi?id=420416 Bug ID: 420416 Summary: Volume Applet Settings allow invalid characters and textbox expands Product: plasma-pa Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: nicolas.h...@tuta.io CC: plasma-b...@kde.org Target Milestone: --- Created attachment 127772 --> https://bugs.kde.org/attachment.cgi?id=127772&action=edit Screen recording showing the behavior SUMMARY STEPS TO REPRODUCE 1. Right click the plasmoid and click on Configure Audio Volume 2. Enter any letter in the textboxes for "Maximum volume" or "Volume step" OBSERVED RESULT You can enter letter and unlimited characters which results in the textbox expanding EXPECTED RESULT Only numbers are allowed and it is limited to 3 digits as the maximum is 150. It should have a fixed width SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 420417] New: Crash of lokalize when changing to a new item
https://bugs.kde.org/show_bug.cgi?id=420417 Bug ID: 420417 Summary: Crash of lokalize when changing to a new item Product: lokalize Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: freekdekru...@kde.nl CC: sha...@ukr.net Target Milestone: --- Application: lokalize (19.12.3) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.4-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I finished editing of an item and pressed ++ to change to the next item to be editted. -- Backtrace: Application: Lokalize (lokalize), 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 0x7fe7de608840 (LWP 4130))] Thread 11 (Thread 0x7fe7be80b700 (LWP 4145)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x3484a94) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x3484a40, cond=0x3484a68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x3484a68, mutex=0x3484a40) at pthread_cond_wait.c:638 #3 0x7fe7e07ee1db in QWaitConditionPrivate::wait (deadline=..., this=0x3484a40) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x12c4aa8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fe7e07ee299 in QWaitCondition::wait (this=this@entry=0x3098520, mutex=mutex@entry=0x12c4aa8, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #6 0x7fe7e07eb9db in QThreadPoolThread::run (this=0x3098510) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:270 #7 0x7fe7e07e8698 in QThreadPrivate::start (arg=0x3098510) at thread/qthread_unix.cpp:342 #8 0x7fe7dfac2efa in start_thread (arg=) at pthread_create.c:477 #9 0x7fe7e25a03bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fe7c8a2b700 (LWP 4141)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x30c2d68) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x30c2d18, cond=0x30c2d40) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x30c2d40, mutex=0x30c2d18) at pthread_cond_wait.c:638 #3 0x7fe7cb4d72db in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7fe7cb4d6a97 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7fe7dfac2efa in start_thread (arg=) at pthread_create.c:477 #6 0x7fe7e25a03bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fe7c922c700 (LWP 4140)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x30c2d68) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x30c2d18, cond=0x30c2d40) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x30c2d40, mutex=0x30c2d18) at pthread_cond_wait.c:638 #3 0x7fe7cb4d72db in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7fe7cb4d6a97 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7fe7dfac2efa in start_thread (arg=) at pthread_create.c:477 #6 0x7fe7e25a03bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fe7c9a2d700 (LWP 4139)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x30c2d68) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x30c2d18, cond=0x30c2d40) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x30c2d40, mutex=0x30c2d18) at pthread_cond_wait.c:638 #3 0x7fe7cb4d72db in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7fe7cb4d6a97 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7fe7dfac2efa in start_thread (arg=) at pthread_create.c:477 #6 0x7fe7e25a03bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fe7ca22e700 (LWP 4138)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x30c2d68) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x30c2d18, cond=0x30c2d40) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x30c2d40, mutex=0x30c2d18) at pthread_cond_wait.c:638 #3 0x7fe7cb4d72db in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7fe7cb4d6a97 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7fe7dfac2efa in start_thread (arg=) at pthread_create.c:477 #6 0x7fe7e25a03bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fe7caa2f700 (LWP 4137)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x32090a4) at ../sysdeps/nptl/futex-internal.h:183
[plasmashell] [Bug 420418] New: Global menu disappesrs when application moved to second monitor
https://bugs.kde.org/show_bug.cgi?id=420418 Bug ID: 420418 Summary: Global menu disappesrs when application moved to second monitor Product: plasmashell Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: hema_pra...@hotmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Global menu disappears when an application moved to second monitor, though application still have focus and active. I use Kde neon 5.18.4. I have global menu. when I move an active application, the global menu disappears from panel, though application is still active and i am using the application. STEPS TO REPRODUCE 1. place global menu widget in panel (in my case, I have top panel) 2. open any application on primary screen (application menu is visible in panel) 3. move the application to second monitor and keep it active and keep using OBSERVED RESULT The application's menu disappears from panel. EXPECTED RESULT The application menu shall be visible. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kde neon 5.18 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420352] Logo for Alligator Feed Reader
https://bugs.kde.org/show_bug.cgi?id=420352 Tobias Fella changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/bre ||eze-icons/9f5f2a06066236291 ||9e987c8085fb96fa95209ed --- Comment #1 from Tobias Fella --- Git commit 9f5f2a060662362919e987c8085fb96fa95209ed by Tobias Fella, on behalf of Mathis Brüchert. Committed on 22/04/2020 at 13:31. Pushed by tfella into branch 'master'. add alligator icon Summary: FEATURE: 420352 Reviewers: tfella, #vdg, ndavis Reviewed By: tfella, #vdg, ndavis Subscribers: ognarb, ngraham, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D29070 A +59 -0icons-dark/apps/48/alligator.svg A +59 -0icons/apps/48/alligator.svg https://commits.kde.org/breeze-icons/9f5f2a060662362919e987c8085fb96fa95209ed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420418] Global menu disappesrs when application moved to second monitor
https://bugs.kde.org/show_bug.cgi?id=420418 prasad changed: What|Removed |Added CC||hema_pra...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420418] Global menu disappesrs when application moved to second monitor
https://bugs.kde.org/show_bug.cgi?id=420418 --- Comment #1 from prasad --- The issue also happens if any application on second monitor becomes active. when an application on second monitor gets clicked and becomes active, global menu in panel disappears. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 405963] Firefox HTML5 player does not retain app volume setting when forwarded
https://bugs.kde.org/show_bug.cgi?id=405963 --- Comment #2 from Patrick Silva --- Still reproducible with Firefox 75. Operating system: Arch Linux KDE Plasma: 5.18.4 KDE Frameworks: 5.69.0 Qt: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 405963] Firefox HTML5 player does not retain app volume setting when forwarded
https://bugs.kde.org/show_bug.cgi?id=405963 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #3 from Kai Uwe Broulik --- Firefox seems to revoke the stream right away when seeking and then opens it again. It does have module-stream-restore.id = "sink-input-by-application-name:Firefox" so I am not sure if this is a Firefox bug, a pulseaudio bug, or a bug on our side. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420312] Dolphin services not being remove after uninstall
https://bugs.kde.org/show_bug.cgi?id=420312 Alex changed: What|Removed |Added CC||alex1701c@gmx.net --- Comment #1 from Alex --- Hello, I can reproduce the issue and will do my best to write a patch. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 420419] New: Failure to launch an "On Demand SideBar" from "Latte SideBar Button"
https://bugs.kde.org/show_bug.cgi?id=420419 Bug ID: 420419 Summary: Failure to launch an "On Demand SideBar" from "Latte SideBar Button" Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: library Assignee: mvourla...@gmail.com Reporter: alitajel...@gmail.com Target Milestone: --- SUMMARY - Can't launch an "On Demand SideBar" from "Latte SideBar Button" STEPS TO REPRODUCE - Try to launch an "On Demand SideBar" from "Latte SideBar Button" OBSERVED RESULT - Failure to launch with the following error: ``` Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.latte.sidebarbutton/contents/ui/main.qml:99:5: Type Icons.GeneralIcon unavailable file:///usr/share/plasma/plasmoids/org.kde.latte.sidebarbutton/contents/ui/icons/GeneralIcon.qml:43:9: Type LatteIcon unavailable file:///usr/share/plasma/plasmoids/org.kde.latte.sidebarbutton/contents/ui/icons/LatteIcon.qml:24:1: Latte.IconItem is not a type ``` EXPECTED RESULT - Launch an "On Demand SideBar" SOFTWARE/OS VERSIONS Linux: EndeavourOS KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION - I was using the master branch version packaged by [Archlinux CN Repository](https://github.com/archlinuxcn/repo/tree/master/archlinuxcn/latte-dock-git). So, to exclude a packaging issue I installed the [github version](https://github.com/KDE/latte-dock.git), but with the same results. - Downgrading to `latte-dock-git 0.9.11.r0.gff490a41-5` solves the issue. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420380] Folder with files disappear
https://bugs.kde.org/show_bug.cgi?id=420380 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Ivan Čukić --- Should be fixed for the next release Plasma 5.18.5 or 5.19 when they get out. Please reopen if it persists after update. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 420420] New: Unexpected and repeated crash
https://bugs.kde.org/show_bug.cgi?id=420420 Bug ID: 420420 Summary: Unexpected and repeated crash Product: kolourpaint Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: chiacheng...@gmail.com Target Milestone: --- Application: kolourpaint (19.04.3) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-46-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: edited a png file (screenshot) closed it and reopen the same file throught File-Recent Documents and it crashed. The crash can be reproduced every time. -- Backtrace: Application: KolourPaint (kolourpaint), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2accd4e840 (LWP 5967))] Thread 4 (Thread 0x7f2abbfff700 (LWP 5970)): #0 0x7f2acf9632c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x5618203a38f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f2acf9632c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5618203a38a8, cond=0x5618203a38d0) at pthread_cond_wait.c:508 #2 0x7f2acf9632c6 in __pthread_cond_wait (cond=0x5618203a38d0, mutex=0x5618203a38a8) at pthread_cond_wait.c:638 #3 0x7f2ac0b82aab in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f2ac0b826cb in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f2acf95c669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f2ad0787323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2acad88700 (LWP 5969)): #0 0x7ffd5987b901 in clock_gettime () #1 0x7f2ad079512b in __GI___clock_gettime (clock_id=1, tp=0x7f2acad87aa0) at ../sysdeps/unix/sysv/linux/clock_gettime.c:33 #2 0x7f2ad0e71f15 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f2ad0e707bd in QTimerInfoList::updateCurrentTime() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2ad0e70d99 in QTimerInfoList::timerWait(timespec&) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2ad0e723a6 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2acf03a02f in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f2acf03a9db in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f2acf03abe3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f2ad0e72653 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2ad0e195cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2ad0c52a45 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2acfc97efa in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #13 0x7f2ad0c53c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2acf95c669 in start_thread (arg=) at pthread_create.c:479 #15 0x7f2ad0787323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2acc444700 (LWP 5968)): #0 0x7f2ad077ac2f in __GI___poll (fds=0x7f2acc443c68, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2ad02b9917 in () at /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2ad02bb53a in xcb_wait_for_event () at /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2accc06288 in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f2ad0c53c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2acf95c669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f2ad0787323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2accd4e840 (LWP 5967)): [KCrash Handler] #6 0x7f2ad0d704bf in QUrl::QUrl(QUrl const&) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2ad214e7a3 in KRecentFilesAction::addUrl(QUrl const&, QString const&) () at /lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #8 0x56181f5f24a9 in () #9 0x56181f5f642f in () #10 0x56181f5f6662 in () #11 0x7f2ad0e46558 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2ad214d366 in KRecentFilesAction::urlSelected(QUrl const&) () at /lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #13 0x7f2ad214dccd in () at /lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #14 0x7f2ad214e155 in () at /lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #15 0x7f2ad0e463f8 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f2ad2049543 in KSelectAction::triggered(QAction*) () at /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #17 0x7f2ad204aba3 in KSelectAction::actionTriggered(Q
[frameworks-kirigami] [Bug 420405] Performance regression with Kirigami.Card
https://bugs.kde.org/show_bug.cgi?id=420405 Arjen Hiemstra changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Arjen Hiemstra --- I'm going to need more information here. I just profiled it and on my machine creating 100 cards without actions takes a total of ~500 ms. Individual cards take ~1.5ms to create, of which most time is spent creating ActionToolBar. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420406] Images in a Kirigami.Card clip outside of bounds
https://bugs.kde.org/show_bug.cgi?id=420406 --- Comment #1 from Arjen Hiemstra --- Fixed with https://phabricator.kde.org/D29092 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420286] ShadowedRectangle is not pixel aligned
https://bugs.kde.org/show_bug.cgi?id=420286 --- Comment #5 from Arjen Hiemstra --- I did some further tweaking in https://phabricator.kde.org/D29092 . This still has some slightly haloing around certain edges, which unfortunately is pretty much unavoidable with the rendering techniques involved without sacrificing any antialiasing for the corners. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 420419] Failure to launch an "On Demand SideBar" from "Latte SideBar Button"
https://bugs.kde.org/show_bug.cgi?id=420419 --- Comment #1 from Michail Vourlakos --- You can install SideBar button applet from its repo or wait for an updatefor it in kde store -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 389964] KRunner window behind keep-above windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=389964 --- Comment #6 from Patrick Silva --- This bug persists on Neon unstable. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 420419] Failure to launch an "On Demand SideBar" from "Latte SideBar Button"
https://bugs.kde.org/show_bug.cgi?id=420419 --- Comment #2 from Ali Tajelsir --- (In reply to Michail Vourlakos from comment #1) > You can install SideBar button applet from its repo or wait for an updatefor > it in kde store - I'll and report back -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415872] kwin_wayland random segfault libQt5Qml.so.5.14.0[7fe09a171000+307000]
https://bugs.kde.org/show_bug.cgi?id=415872 --- Comment #7 from Tom B --- Is there anything else I can provide to help this become resolved? This is a very annoying issue that happens several times a day and on wayland halts the entire session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415872] kwin_wayland random segfault libQt5Qml.so.5.14.0[7fe09a171000+307000]
https://bugs.kde.org/show_bug.cgi?id=415872 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #8 from David Edmundson --- >Is there anything else I can provide to help this become resolved? Super explicit steps to reliably reproduce. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420313] Night color location detection returns the wrong location
https://bugs.kde.org/show_bug.cgi?id=420313 --- Comment #4 from Nate Graham --- No worries! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402028] Setting shortcut keys to Ctrl+< or Ctrl+> breaks shortcuts for Ctrl+Z & Ctrl+X
https://bugs.kde.org/show_bug.cgi?id=402028 Ben Mayberry changed: What|Removed |Added CC||benmaybe...@live.com --- Comment #4 from Ben Mayberry --- Can confirm is still an issue on: Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-46-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 420419] Failure to launch an "On Demand SideBar" from "Latte SideBar Button"
https://bugs.kde.org/show_bug.cgi?id=420419 --- Comment #3 from Ali Tajelsir --- (In reply to Michail Vourlakos from comment #1) > You can install SideBar button applet from its repo or wait for an updatefor > it in kde store - I can confirm that it's working after updating the "SideBar Button" to the git version. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420421] New: Wish: Store log or notes with configuration
https://bugs.kde.org/show_bug.cgi?id=420421 Bug ID: 420421 Summary: Wish: Store log or notes with configuration Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: a...@al-williams.com Target Milestone: --- Here's the user story: The other day I was making some changes and thought, "Hmm.. I have compositing set to OpenGL 2 instead of 3. I can't remember if I just tried that to see if it fixed some other problem or if it actually fixed some problem." I knew the change had been long ago and several display drivers ago, so I turned it back on. Within a day I realized my system was crashing and turning it back to Open GL2 fixed that. So what would be a great feature is a field in each module that says "Notes" that gets persisted with the settings. Even just a simple "sticky note" format would be OK although bonus points if it were an accumulated time and date stamped log. The notes could be per module or one for all of systemsettings, it seems like. Either would work. So each module could have at the bottom a text field you could edit along with buttons "save note" and (if you are going to do the log-style) "view notes". >From the view you edit the entire log or erase it. If you just do a sticky note, you don't need the view button or any manipulation, so that would be easier. If you decide to do it for all settings this could be part of the kcmshell window instead of per module, but that would be a big change compared to how it is today, I think. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DOWNSTREAM --- Comment #4 from Nate Graham --- > Okay, I was find !!! His name is stock_new-window.svg Aha! That's not a standard icon name, so it makes sense that we don't have it. This is a bug in the app itself; it should be using the correct standardized icon, which is "window-new" > I use Papirus Icons for the search (I don't know if is very well). Then you'll need to ask the maintainer of that icon theme to add the missing icons. Either way, not our bug. :) -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 420417] Crash of lokalize when changing to a new item
https://bugs.kde.org/show_bug.cgi?id=420417 --- Comment #1 from Simon Depiets --- That was a one-off right ? I think the project tree segfaults sometimes but I haven't been able to make it reproductible, so I'm very interested if you can. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420422] New: Indian Rupee has new symbol since 7 years,it is ₹
https://bugs.kde.org/show_bug.cgi?id=420422 Bug ID: 420422 Summary: Indian Rupee has new symbol since 7 years,it is ₹ Product: kmymoney Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: spill...@gmail.com Target Milestone: --- SUMMARY Indian Rupee has new symbol since 7 years,it is ₹ STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT Please change the symbol of Indian Rupee to ₹ SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION All versions need to change -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420423] New: HTML font size is affected by view zoom in composer
https://bugs.kde.org/show_bug.cgi?id=420423
Bug ID: 420423
Summary: HTML font size is affected by view zoom in composer
Product: kmail2
Version: 5.9.3
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-b...@kde.org
Reporter: alejandro_a...@yahoo.es
Target Milestone: ---
First of all, i am not sure if this has already been fixed in more modern
versions of kmail (using Debian Stable here).
STEPS TO REPRODUCE
1. Compose an email in HTML mode with, let's say Noto Sans at 11 points of size
2. Make text bigger or smaller for viewing (Ctrl+Mouse scroll wheel, or
Ctrl+{,+})
3. Send message
4. Received message will have a font size proportional to the zoom you used
composing the message
It's also notable that when kmail receives emails composed like this (a CC for
yourself) the size of the text will appear normal so you won't notice but other
people with different emails clients will
In my mind, zoom of the text should be independent of the font size sent in the
HTML. But that's my two cents
OBSERVED RESULT
Example of the HTML code generated by the composer
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Stable 10.3
KDE Plasma Version: 5.14.5.1
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3+dfsg1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[Plasma Vault] [Bug 420424] New: [enhancement] Provide feedback when unable to mount CryFS vault
https://bugs.kde.org/show_bug.cgi?id=420424 Bug ID: 420424 Summary: [enhancement] Provide feedback when unable to mount CryFS vault Product: Plasma Vault Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: frap...@gmail.com Target Milestone: --- SUMMARY When cryfs cannot mount a directory, the vault UI will simply not show anything, so the user has no idea what's happening. STEPS TO REPRODUCE 1. Create a test vault and unmount it 2. Remove one of its binary files (eg. rm -rf Test\ Vault.enc/A6D/713C83A158E9483F5385E96AC219E) 3. Try to mount the vault using the plasma vault UI OBSERVED RESULT The UI closes without any feedback, as if the vault was properly mounted, when in fact, it did not mount. Trying to mount it from CLI shows: $ cryfs Test\ Vault.enc/ test CryFS Version 0.9.9 Password: Loading config file (this can take some time)...done [2020-04-22 11:08:13.960] [Log] [error] Could not load blob A6D713C83A158E9483F5385E96AC219E. Is the base directory accessible? [2020-04-22 11:08:13.961] [Log] [error] Crashed: Input/output error EXPECTED RESULT The Plasma Vault UI should at the very least show this error, being very explicit that the vault was unable to be mounted. Ideally, it would be nice to also show some additional information, like: - Full path for the blob (In the example, it would be ~/Test\ Vault.enc/A6D/713C83A158E9483F5385E96AC219E) - Possible suggestions on what the cause could be (incorrect permissions? maybe a conflict resolution by a shared service such as Dropbox? Hardware issues? etc...) SOFTWARE/OS VERSIONS Windows: No macOS: No Linux/KDE Plasma: Yes (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420425] New: Calendar View of Portfolio
https://bugs.kde.org/show_bug.cgi?id=420425 Bug ID: 420425 Summary: Calendar View of Portfolio Product: kmymoney Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: spill...@gmail.com Target Milestone: --- SUMMARY KMymoney has data to display the daily, weekly, monthly view of summary of account(s) in calendar view. For example a monthly view could display Income/Expenses and Total (ie summary of the transaction) by every day in the view. Similarly, a weekly view would be a great differentiator. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420425] Calendar View of Portfolio
https://bugs.kde.org/show_bug.cgi?id=420425 Suresh PB changed: What|Removed |Added CC||spill...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 419831] KDevelop sometimes hangs on exit
https://bugs.kde.org/show_bug.cgi?id=419831 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420425] Calendar View of Portfolio
https://bugs.kde.org/show_bug.cgi?id=420425 --- Comment #1 from Suresh PB --- Created attachment 127773 --> https://bugs.kde.org/attachment.cgi?id=127773&action=edit Model from another app to give an idea -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 419831] KDevelop sometimes hangs on exit
https://bugs.kde.org/show_bug.cgi?id=419831 --- Comment #1 from RJVB --- (drKonqi balks something about private attachments not being allowed when I try to upload the latest report, so here it is manually): Application: kdevelop (5.5.0-25-g0dda64acb3) (Compiled from sources) Qt Version: 5.9.8 Frameworks Version: 5.60.0 Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64 Windowing system: X11 Distribution: Ubuntu 14.04.6 LTS -- Information about the crash: - What I was doing when the application crashed: As the previous time, I quit KDevelop and a deadlock ensued after the languageController was cleaned up. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f42d08f0c80 (LWP 23120))] Thread 7 (Thread 0x7f42976fd700 (LWP 24412)): #0 0x7f42c729537d in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f42bdaeaa7f in g_wakeup_acknowledge (wakeup=0x7f4290002780) at gwakeup.c:210 #2 g_main_context_check (context=0x7f428c000990, max_priority=2147483647, fds=0x7f428c0013c0, n_fds=1) at gmain.c:3686 #3 0x7f42bdaeb7a6 in g_main_context_iterate (context=, block=, dispatch=, self=) at gmain.c:3905 #4 0x7f42bdaeba21 in g_main_context_iteration (context=0x7f428c000990, may_block=1) at gmain.c:3969 #5 0x7f42c80a4b7b in QEventDispatcherGlib::processEvents(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #6 0x7f42c804c5df in QEventLoop::exec(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #7 0x7f42c7e8c7b7 in QThread::exec() () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #8 0x7f42c7e8d946 in QThreadPrivate::start(void*) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #9 0x7f42c4793184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f42c72a403d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f429d9ed700 (LWP 24325)): #0 0x7f42c7296c9d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f42bdaeb761 in g_main_context_poll (priority=0, context=, timeout=, fds=, n_fds=) at gmain.c:4209 #2 g_main_context_iterate (context=, block=, dispatch=, self=) at gmain.c:3903 #3 0x7f42bdaeba21 in g_main_context_iteration (context=0x7f429990, may_block=1) at gmain.c:3969 #4 0x7f42c80a4b7b in QEventDispatcherGlib::processEvents(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #5 0x7f42c804c5df in QEventLoop::exec(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #6 0x7f42c7e8c7b7 in QThread::exec() () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #7 0x7f42c7e8d946 in QThreadPrivate::start(void*) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #8 0x7f42c4793184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f42c72a403d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f429e84e700 (LWP 24248)): #0 0x7f42c7296c9d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f42bdaeb761 in g_main_context_poll (priority=0, context=, timeout=, fds=, n_fds=) at gmain.c:4209 #2 g_main_context_iterate (context=, block=, dispatch=, self=) at gmain.c:3903 #3 0x7f42bdaeba21 in g_main_context_iteration (context=0x7f4298000990, may_block=1) at gmain.c:3969 #4 0x7f42c80a4b7b in QEventDispatcherGlib::processEvents(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #5 0x7f42c804c5df in QEventLoop::exec(QFlags) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #6 0x7f42c7e8c7b7 in QThread::exec() () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #7 0x7f42cf246a2e in KDevelop::DUChainPrivate::CleanupThread::run (this=0x2cec140) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kf5-kdevelop/kf5-kdevelop-devel/work/kf5-kdevelop-5/kdevplatform/language/duchain/duchain.cpp:331 #8 0x7f42c7e8d946 in QThreadPrivate::start(void*) () from /opt/local/libexec/qt512/lib/libQt5Core.so.5 #9 0x7f42c4793184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f42c72a403d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f42a014d700 (LWP 23759)): #0 0x7f42c4797404 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f42a0ddcb2b in cnd_wait (cond=, mtx=) at ../mesa-18.3.3/src/../include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=) at ../mesa-18.3.3/src/util/u_queue.c:270 #3 0x7f42a0ddd446 in impl_thrd_routine (p=) at ../mesa-18.3.3/src/../include/c11/threads_posix.h:87 #4 0x7f42c4793184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7f42c72a403d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f42b0b3f700 (LWP 23303)): #0 g_source_iter_next (iter=, source=) at gmain.c:982 #1 g_main_context_prepare (context=0x7f42a4000990, priority=0x7f42b0
[clazy] [Bug 420426] New: Check and fixup for unused parameters
https://bugs.kde.org/show_bug.cgi?id=420426 Bug ID: 420426 Summary: Check and fixup for unused parameters Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: an...@familiesomers.nl CC: smart...@kde.org Target Milestone: --- There is a check for "non-trivial" unused parameters. I would like to propose a check and a fixup for all unused parameters. Use case: We had a project in which we have a mock object mocking a wide API, with lots of methods and lots of arguments for each of these. Most methods are unimplemented, but they sprayed the compile output with warnings. I commented out all the offending argument names, but it would have been nice to be able to quickly apply a fixup to them instead. Fixup could be either the commenting out, or perhaps inserting a Q_UNUSED() at the top of the implementation. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420425] Calendar View of Portfolio
https://bugs.kde.org/show_bug.cgi?id=420425 Jack changed: What|Removed |Added Severity|normal |wishlist --- Comment #2 from Jack --- Are you proposing this for the past or the future? (I can imagine both, but the past would perhaps be a new form of report, and the future would likely be based on forecasts.) Are the little icons for each day based on the category? Where would they come from? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 --- Comment #5 from Simon Gardet --- Sorry, I don't speak English very well, I must have misspoken... Actually it's the Breeze theme that doesn't have those icons. I only used the icon theme that worked best with this application to compare with Breeze and I was able to find the name that the breeze icon should have. Maybe there's a better way to find the name that I don't know about... The problem is not in adapta but it is in breeze. Unfortunately if the icon names are not standard anyway I doubt we can fix it. Anyway I've seen several similar cases in GTK CSD applications using Plasma with the Breeze theme. So maybe I'll file a bug report at Gnome. stock_new-window.svg although not standard is not the same as new-window.svg, it seems to be a variant so in my opinion it's certainly a choice, not to have respected the standard, that would come from Gnome for their CSD applications ... I don't know if I was understandable and thank you very much for your answers. And I hope that with these clarifications we can try some things, I remain vigilant to new messages. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418698] Applying Global theme which use a widget style not installed, default still used but config refer to missing style
https://bugs.kde.org/show_bug.cgi?id=418698 Cyril Rossi changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/17ef374a8cc469a ||9eefc516fc4885cbbce0c0afc --- Comment #3 from Cyril Rossi --- Git commit 17ef374a8cc469a9eefc516fc4885cbbce0c0afc by Cyril Rossi. Committed on 22/04/2020 at 14:39. Pushed by crossi into branch 'Plasma/5.18'. KCM LookAndFeel check widgetStyle availability before applying it Summary: Related: bug 419552 * Some Global Theme may refer to breeze widget style with a lower case b, apply the proper name `Breeze` * Some Global Theme use widget style that may not be installed, then don't apply it. Test Plan: * Open KCM LookAndFeel, open GHNS and install Qogir-light theme, then apply it. Open Application Style KCM, if kvantum is not installed, Breeze is highlighted. * Open KCM LookAndFeel, open GHNS and install Aritim-Light, then apply it. Open Application Style KCM, Breeze is highlighted. Reviewers: #plasma, ervin, bport, meven, ngraham Reviewed By: ervin, ngraham Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28662 M +17 -5kcms/lookandfeel/kcm.cpp https://commits.kde.org/plasma-desktop/17ef374a8cc469a9eefc516fc4885cbbce0c0afc -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414417] current splash screen is not highlighted after I set global theme to breeze dark
https://bugs.kde.org/show_bug.cgi?id=414417 Cyril Rossi changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-desktop/dacb3a8bdd206ec ||14a588bb25b37caa48c3b36aa --- Comment #3 from Cyril Rossi --- Git commit dacb3a8bdd206ec14a588bb25b37caa48c3b36aa by Cyril Rossi. Committed on 22/04/2020 at 14:43. Pushed by crossi into branch 'Plasma/5.18'. KCM LookAndFeel check if splash screen is provided before applying it. Summary: * While saving a new global theme, don't set splash screen if none is provided, leave the current one. * KSplash kcfg set default to breeze instead of the current lnf theme which may not contain a splash screen. Test Plan: * Open LookAndFeel KCM, apply Breeze Dark, then open Splash screen KCM, Breeze should be highlighted. * Open splash screen KCM, select none, click on defaults, Breeze should be selected. Reviewers: #plasma, ervin, bport, meven, ngraham Reviewed By: ervin, ngraham Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28656 M +1-4kcms/ksplash/splashscreensettings.kcfg M +4-1kcms/lookandfeel/kcm.cpp https://commits.kde.org/plasma-desktop/dacb3a8bdd206ec14a588bb25b37caa48c3b36aa -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419552] No style is highlighted when a 3rd-party global theme with breeze style is used
https://bugs.kde.org/show_bug.cgi?id=419552 Cyril Rossi changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/17ef374a8cc469a ||9eefc516fc4885cbbce0c0afc Resolution|DUPLICATE |FIXED --- Comment #3 from Cyril Rossi --- Git commit 17ef374a8cc469a9eefc516fc4885cbbce0c0afc by Cyril Rossi. Committed on 22/04/2020 at 14:39. Pushed by crossi into branch 'Plasma/5.18'. KCM LookAndFeel check widgetStyle availability before applying it Summary: Related: bug 418698 * Some Global Theme may refer to breeze widget style with a lower case b, apply the proper name `Breeze` * Some Global Theme use widget style that may not be installed, then don't apply it. Test Plan: * Open KCM LookAndFeel, open GHNS and install Qogir-light theme, then apply it. Open Application Style KCM, if kvantum is not installed, Breeze is highlighted. * Open KCM LookAndFeel, open GHNS and install Aritim-Light, then apply it. Open Application Style KCM, Breeze is highlighted. Reviewers: #plasma, ervin, bport, meven, ngraham Reviewed By: ervin, ngraham Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28662 M +17 -5kcms/lookandfeel/kcm.cpp https://commits.kde.org/plasma-desktop/17ef374a8cc469a9eefc516fc4885cbbce0c0afc -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418698] Applying Global theme which use a widget style not installed, default still used but config refer to missing style
https://bugs.kde.org/show_bug.cgi?id=418698 Cyril Rossi changed: What|Removed |Added Version Fixed In||5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419552] No style is highlighted when a 3rd-party global theme with breeze style is used
https://bugs.kde.org/show_bug.cgi?id=419552 Cyril Rossi changed: What|Removed |Added Version Fixed In||5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414417] current splash screen is not highlighted after I set global theme to breeze dark
https://bugs.kde.org/show_bug.cgi?id=414417 Cyril Rossi changed: What|Removed |Added Version Fixed In||5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 397586] OSD to configure multi-monitor mode is not centered on the screen under Wayland
https://bugs.kde.org/show_bug.cgi?id=397586 Benjamin Port changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ksc ||reen/b3b45721ee17828d5711ff ||88d5f1777b65c2834a --- Comment #9 from Benjamin Port --- Git commit b3b45721ee17828d5711ff88d5f1777b65c2834a by Benjamin Port. Committed on 22/04/2020 at 15:03. Pushed by bport into branch 'master'. fix(kded): center action OSD on wayland Summary: Currently on Wayland the Action OSD is not centered on the screen. On Wayland we will center it on m_output (laptop, with fallback to primary and then to first one). X behavior is not changed. Reviewers: romangg, davidedmundson Reviewed By: romangg, davidedmundson Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28916 M +9-2kded/osd.cpp M +6-0kded/qml/OsdSelector.qml https://commits.kde.org/kscreen/b3b45721ee17828d5711ff88d5f1777b65c2834a -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 58647] Wrong accelerators specified in Info pages
https://bugs.kde.org/show_bug.cgi?id=58647 Shinjo Park changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #13 from Shinjo Park --- Given that the kdelibs is discontinued, I am going to report a new bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420423] HTML font size is affected by view zoom in composer
https://bugs.kde.org/show_bug.cgi?id=420423 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- Sdfsfdfdf sqdqs dqsdqsdqsdqsd q => 1.2em now. so it depends against zoom. it's fixed from long time ago. 5.9.3 is very old :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420334] GUI hangs when adding a network folder
https://bugs.kde.org/show_bug.cgi?id=420334 Stefan S changed: What|Removed |Added Assignee|stefan.szeke...@gmail.com |digikam-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420411] digiKam Crash on detect faces 7.0.0 beta3 debug build
https://bugs.kde.org/show_bug.cgi?id=420411 --- Comment #2 from Stefan S --- (In reply to caulier.gilles from comment #1) > >Personal notes: should not be doing work on main thread, that blocks the GUI > >- >can't open digiKam after it starts detecting. > > I don't understand this point : all long process are started in separated > thread under DK. > > Gilles Caulier They are not, at least not all of them, if you look at Thread 0:: CrBrowserMain Dispatch queue: com.apple.main-thread You are doing face detection on the main thread (thread 0) as far as i can see. And there other places in your code where everything is done on the main thread, like here: https://bugs.kde.org/show_bug.cgi?id=420334#c12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420427] New: crash when openning Team Viewer, or upon try to copy a flameshot image to clippboard, and when receive notifications on whatsapp (version with electron)
https://bugs.kde.org/show_bug.cgi?id=420427 Bug ID: 420427 Summary: crash when openning Team Viewer, or upon try to copy a flameshot image to clippboard, and when receive notifications on whatsapp (version with electron) Product: plasmashell Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: phra...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.4) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.3.0-46-generic x86_64 Windowing system: X11 Distribution: Feren OS -- Information about the crash: - What I was doing when the application crashed: this time was when openning Team Viewer, but it also crashes using flameshot or wathsapp. Since this upgrade from FerenOS, i lost completely the stability of the system, essencialy in the KDE... -- Backtrace (Reduced): #6 0x7ff07aeca2c5 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #7 0x7ff0a4f6a3ad in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7ff0a4f6a56b in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7ff0a4f21060 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7ff0a4f25785 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 Possible duplicates by query: bug 41, bug 418316, bug 418084, bug 416926, bug 416905. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420427] crash when openning Team Viewer, or upon try to copy a flameshot image to clippboard, and when receive notifications on whatsapp (version with electron)
https://bugs.kde.org/show_bug.cgi?id=420427 phrazão changed: What|Removed |Added CC||phra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420312] Dolphin services not being remove after uninstall
https://bugs.kde.org/show_bug.cgi?id=420312 --- Comment #2 from Alex --- https://phabricator.kde.org/D29101 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420312] Dolphin services not being remove after uninstall
https://bugs.kde.org/show_bug.cgi?id=420312 Nate Graham changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |alex1701c@gmx.net Status|REPORTED|ASSIGNED CC||n...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 397586] OSD to configure multi-monitor mode is not centered on the screen under Wayland
https://bugs.kde.org/show_bug.cgi?id=397586 Nate Graham changed: What|Removed |Added Version Fixed In||5.19.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 --- Comment #6 from Nate Graham --- Yes, Breeze doesn't have stock_new-window.svg. We can create a symlink which will resolve the issue, but it's working around the preferred solution, which is for gnome-calendar to use the correct icon. I'm willing to add that symlink if the gnome-calendar developers refuse to fix the problem correctly on their end, but I would like if it you could try for that first. :) The Breeze icon theme does indeed have all of those weather icons though. I'm seeing them daily in my weather applet. :) So again I think there must be some issue with the GNOME app if it's not using the correct standardized icon names. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420428] New: nightly build 367/vob exports at 4:3 even when 16:9 in project settings
https://bugs.kde.org/show_bug.cgi?id=420428 Bug ID: 420428 Summary: nightly build 367/vob exports at 4:3 even when 16:9 in project settings Product: kdenlive Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: richard.sutherland...@gmail.com Target Milestone: --- SUMMARY installed nightly build 367 to fix dvd wizard/chapter issue; when exported vob, exporting as 4:3 STEPS TO REPRODUCE 1. render project x/16:9 as vob file in 19.12.3 2. render project x/16:9 as vob file in nightly build 367 3. compare files in DVDStyler; 19.12.3 renders as 16:9; 367 renders as 4:3 OBSERVED RESULT aspect ratio is 4:3 in DVD Styler EXPECTED RESULT aspect ratio is 16;9 in DVD Styler SOFTWARE/OS VERSIONS Windows: 10 macOS: n/a Linux/KDE Plasma: n/a (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION reinstalled 19.12.3 to fix the issue currently. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420226] Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 vanyossi changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||ghe...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from vanyossi --- I cannot reproduce this issue, i suppose because its random its not that easy to reproduce. Looking at the log provided I can only tell the crash ocurred somewhere at KisSelection::pixelSelection() Are you generate lldb backtraces? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420429] New: Cannot rightclick files in Dolphin without it crashing
https://bugs.kde.org/show_bug.cgi?id=420429 Bug ID: 420429 Summary: Cannot rightclick files in Dolphin without it crashing Product: dolphin Version: 19.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ienjoydigginggra...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 127774 --> https://bugs.kde.org/attachment.cgi?id=127774&action=edit Text from launching Dolphin from Kobsole My roommate broght to my attention that he could not rightclick a image in a folder and set it as wallpaper, nor get the rightclick menu at all and Dolphin would actually crash. I tested to confirm and also opened a folder of movies and tried to get the rightclick and got the same thing. I honesty do not know what is wrong with his Dolphin since everything else seems to be working without issue. According to him he's had the behavior for a couple of days. Could use some suggestion on what might be the cause. Thanks Manjaro 20.0 Testing Build Addition information: https://forum.manjaro.org/t/issue-with-rightclicking-files-in-dolphin/137609 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420429] Cannot rightclick files in Dolphin without it crashing
https://bugs.kde.org/show_bug.cgi?id=420429 ienjoydigginggra...@gmail.com changed: What|Removed |Added CC||ienjoydigginggraves@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420342] Transparency colour not saved
https://bugs.kde.org/show_bug.cgi?id=420342 --- Comment #8 from Rudolf --- Created attachment 127776 --> https://bugs.kde.org/attachment.cgi?id=127776&action=edit Krita.png -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420422] Indian Rupee has new symbol since 7 years,it is ₹
https://bugs.kde.org/show_bug.cgi?id=420422 Thomas Baumgart changed: What|Removed |Added Version Fixed In||5.0.9 Latest Commit||https://commits.kde.org/kmy ||money/27b7a488c4f983525e093 ||8facbb9467a0aaff8e2 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Thomas Baumgart --- Git commit 27b7a488c4f983525e0938facbb9467a0aaff8e2 by Thomas Baumgart. Committed on 22/04/2020 at 16:51. Pushed by tbaumgart into branch '5.0'. Update symbol for Indian Rupee This will use the new symbol in new data files but not update existing files. Currently there's no other way than patching the data file directly to change the symbol. FIXED-IN: 5.0.9 M +1-1kmymoney/mymoney/mymoneyfile.cpp https://commits.kde.org/kmymoney/27b7a488c4f983525e0938facbb9467a0aaff8e2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420342] Transparency colour not saved
https://bugs.kde.org/show_bug.cgi?id=420342 --- Comment #7 from Rudolf --- Rebecca Breu schreef: > https://bugs.kde.org/show_bug.cgi?id=420342 > > Rebecca Breu changed: > > What|Removed |Added > > CC||rebe...@rbreu.de > > --- Comment #6 from Rebecca Breu --- > I still don't know what exactly you are doing, and I can't reproduce > any bugs regarding transparency. > > "Therefor I started to change the background to 'white-transparent'." > > What do you mean by this? The transparency checkerboard of the canvas? > Your layers? Your png export? > > "This figure should have a transparent background and had it through the > whole procedure of making but once saved, the background is white, > transparency gone." > > You should save your images as kra files and only export them to other > file formats once you are done. If you don't export the png with "Store > alpha channel" enabled, then (and only then) you get to pick a colour > at the bottom of the export dialog with which your transparency is > going to be replaced and then, yes, the transparency will be gone in > the exported png. Even if you open that png up again in Krita. > > "And in some occasions a soft grey or white shade appears on > the saved picture which is invisible in Krita." > > My guess is that it's there but not very visible on the white-and-grey > transparency checkerboard, and just a bit that you wanted to erase but > didn't erase completely with the soft eraser because you couldn't see > it. If you are working on black and white pictures, it's probably best > to either change the colour of the transparency checkerboard (Settings > -> Configure Krita -> Display -> Grid Settings -> Transparency > Checkerboard), or to add a solid bright colour layer at the bottom of > your layer stack and toggle the vibisility of that on and off for > checking. And of course toggle visibility off for export. ;) > Thanks very much, Rebecca, I never used kra-format before because I did not understand the necessity of it since I could save in png directly. The problem with 'native' formats is that one cannot publish in them, except for the native Photoshop format psd, which is even known to vector programs. I will experiment in that direction, saving in kra exporting in png. You didn't understand my silly "Therefore I started to change the background to 'white transparent'." I started using Krita seriously in MacOS. There is given a very 'playful' way of changing the background colour and transparency by way of choosing the colour of a 'colouring pencil'. So when the chequered background was to dark for me to see some edge details in the b/w drawing, I chose white in the background and set the transparency to 50%, making sure that I could set the transparency back tot 100% afterwards. In some cases that did not work as perfectly as I had hoped for. I will follow your advice for which I am very thankful and I 'll see what happens. Have a very nice day and keep healthy. Best regards, Rudolf Kahl -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420388] some icons do not appear in GTK applications
https://bugs.kde.org/show_bug.cgi?id=420388 --- Comment #7 from Simon Gardet --- big mea culpa sorry. Actually, I find all occurrences of stock_new-window.svg in the Adapta theme (the only one that works and I'm trying to figure out why it doesn't work in the breeze.) It's a symbolic link to window.svg. Also, I'm trying to create a symbolic link new-window.svg -> stock_new-window.svg and window.svg -> stock_new-window.svg in Breeze Icons and it doesn't work So the problem is not the icon names. I'm going to try to find the real problem and I'll tell you what the problem is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420427] Crash in radeonsi_dri.so when opening Team Viewer, copying a flameshot image to clipboard, and when receiving notifications on whatsapp (version with electron)
https://bugs.kde.org/show_bug.cgi?id=420427 Nate Graham changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Summary|crash when openning Team|Crash in radeonsi_dri.so |Viewer, or upon try to copy |when opening Team Viewer, |a flameshot image to|copying a flameshot image |clippboard, and when|to clipboard, and when |receive notifications on|receiving notifications on |whatsapp (version with |whatsapp (version with |electron) |electron) Component|general |generic-crash CC||n...@kde.org --- Comment #1 from Nate Graham --- Hmm, crashing in the graphics drivers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420226] Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 --- Comment #3 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #2) > I cannot reproduce this issue, i suppose because its random its not that > easy to reproduce. Looking at the log provided I can only tell the crash > ocurred somewhere at KisSelection::pixelSelection() > > Are you generate lldb backtraces? Frankly I don't know how to do that. I tried something like this: > ❯ lldb /Applications/krita.app/Contents/MacOS/krita > (lldb) target create "/Applications/krita.app/Contents/MacOS/krita" > runCurrent executable set to '/Applications/krita.app/Contents/MacOS/krita' > (x86_64). > (lldb) run > error: process exited with status -1 (Error 1) But as you can see it doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420424] [enhancement] Provide feedback when unable to mount CryFS vault
https://bugs.kde.org/show_bug.cgi?id=420424 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420421] Wish: Store log or notes with configuration
https://bugs.kde.org/show_bug.cgi?id=420421 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- I do this myself, but in a text file. It's a sufficiently niche use case that I'm not sure it makes sense to add a feature to system settings to support it. :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420406] Images in a Kirigami.Card clip outside of bounds
https://bugs.kde.org/show_bug.cgi?id=420406 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420398] Install icon elongated
https://bugs.kde.org/show_bug.cgi?id=420398 Vivek changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Vivek --- (In reply to Maik Qualmann from comment #2) > Here in Windows 10 the logo is absolutely round. Did you activate a scaling > factor under Windows? Your monitor resolution is set correctly or are you > using a scaling in the monitor settings? > > Maik My apologies - Windows was scaling the display to 125%. At 100% the icon is perfectly round. I am marking this as Resolved-> not a bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 420416] Volume Applet Settings allows invalid characters and textbox expands
https://bugs.kde.org/show_bug.cgi?id=420416 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Summary|Volume Applet Settings |Volume Applet Settings |allow invalid characters|allows invalid characters |and textbox expands |and textbox expands CC||n...@kde.org Severity|normal |minor Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420430] New: Inconsistent behavior of View tab of Metadata dialog in digiKam Configure menu
https://bugs.kde.org/show_bug.cgi?id=420430
Bug ID: 420430
Summary: Inconsistent behavior of View tab of Metadata dialog
in digiKam Configure menu
Product: digikam
Version: 5.9.0
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Setup-Metadata
Assignee: digikam-bugs-n...@kde.org
Reporter: papapanagiot...@hotmail.com
Target Milestone: ---
SUMMARY
Problem in using the View option for Metadata: Besides the desired items
selected by the user, additional items preceding the first selected item appear
in the filtered view list.
STEPS TO REPRODUCE
1. Click Metadata tab of the right sidebar
2. Click EXIF subtab
3. Click the filter icon
4. Click on Settings
5. In the {Embedded Image Information Management} window that opens choose the
{View} tab and then the EXIF Viewer subtab
6. Deactivate all the check boxes by clicking on the Clear button.
7. Scroll down the list to the [Photograph Information] section and tick only
the {ComponentsConfiguration} check box
8. Fimally click the {OK} button (the window closes)
9. In the right sidebar / Metadata tab click the filter icon
10. Click the Custom button and select an image
OBSERVED RESULT
The resultant Metadata list contains the items: {GPS Version ID}, {Color Filter
Array Pattern}, {Color Space}, {Components Configuration}
EXPECTED RESULT
The resultant Metadata list should contain only the item {Components
Configuration}
ADDITIONAL NOTE:
By the way, please notice that in the general list of the {View} tab of the
{Embedded Image Information Management} window there is no check box labeled
“Color Filter Array Pattern”
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 419921] Cursor doesn't draw
https://bugs.kde.org/show_bug.cgi?id=419921 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #7 from vanyossi --- Hey, did you try resetting your configuration? I use Krita on mac and its been a long time since cursor glitched. What steps you do to make the cursor change into a looking glass? is a gesture, or using the zoom tool, maybe a shortcut. When the cursor is stuck is it only the cursor shape that is different, meaning, you can paint but the cursor is wrong, or the application menus lock and you can't press anything? -- You are receiving this mail because: You are watching all bug changes.
