[plasmashell] [Bug 422742] The tooltips in Task Manager disappear if you move the cursor from a not-running application to one which is running
https://bugs.kde.org/show_bug.cgi?id=422742 Bharadwaj Raju changed: What|Removed |Added Version Fixed In||5.22 CC||bharadwaj.raju777@protonmai ||l.com Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/af ||f12784a17d3ffefffac786bc3c3 ||c99dbb217db --- Comment #5 from Bharadwaj Raju --- I think this has been fixed in 5.22 with this merge request? https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/393 Please reopen if it happens on 5.22 again. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 424734] Unnecessary console messages: "Sonnet: Unable to load plugin ...."
https://bugs.kde.org/show_bug.cgi?id=424734 Alexander Lohnau changed: What|Removed |Added CC||alexander.loh...@gmx.de --- Comment #3 from Alexander Lohnau --- >apparently this is a krunner bug. >it is displayed to me as soon as I type anything into krunner after its first >run. That is because then the KRunner plugins are loaded. >In fact, that seems to be the reason the dictionary runner doesn't work for me. Why do you think so? Have you checked the KRunner settings for the dictionary runner to make sure you have typed the right Trigger Word? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395396] Highlight effect keeps empty window after application closes
https://bugs.kde.org/show_bug.cgi?id=395396 Bharadwaj Raju changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||bharadwaj.raju777@protonmai ||l.com --- Comment #5 from Bharadwaj Raju --- Can't replicate on Plasma 5.22 with new behaviour of highlighting only on tooltip hover, not icon hover. Highlight effect is cancelled, and focus correctly transfers back (probably since the cursor isn't on the panel anymore). Please reopen if problem persists on Plasma 5.22. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436647] Overwriting a gpg-encrypted file results in a zero byte file
https://bugs.kde.org/show_bug.cgi?id=436647 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi |ce/kmymoney/commit/39785a3d |ce/kmymoney/commit/646c4cb8 |80c56dc6e53f301d76c41bcc8ca |10a960699b1b659d72bef248992 |048c6 |f4e40 --- Comment #3 from Thomas Baumgart --- Git commit 646c4cb810a960699b1b659d72bef248992f4e40 by Thomas Baumgart. Committed on 12/05/2021 at 06:54. Pushed by tbaumgart into branch 'master'. Solve problems with usage of QTemporaryFile on MS-Windows A call to QTemporaryFile::close() may not close the file but only rewind the file pointer to the beginning allwing faster re-open. This causes problems on MS-Windows filesystems, as one cannot e.g. rename the temporary file in this case because it is still kept open from the perspective of the filesystem. Only destroying the object really closes the file on the filesystem. This change makes sure, that the QTemporaryFile object only lives as long as it is needed and closed immediately after by destroying the object. FIXED-IN: 5.1.2 (cherry picked from commit 39785a3d80c56dc6e53f301d76c41bcc8ca048c6) M +18 -10 kmymoney/plugins/xml/xmlstorage.cpp https://invent.kde.org/office/kmymoney/commit/646c4cb810a960699b1b659d72bef248992f4e40 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429312] Icons disapearing form icon-only task manager unless Caps Lock is enabled
https://bugs.kde.org/show_bug.cgi?id=429312 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #2 from Bharadwaj Raju --- So it's the indicator causing the task manager size to change enough that it brings Inkscape icon to the front row. Try Configure > Maximum rows > set to 1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429215] Highlight windows on hover effect does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=429215 Bharadwaj Raju changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||bharadwaj.raju777@protonmai ||l.com --- Comment #6 from Bharadwaj Raju --- *** This bug has been marked as a duplicate of bug 433134 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433134] Cannot highlight task when hovering in Wayland
https://bugs.kde.org/show_bug.cgi?id=433134 Bharadwaj Raju changed: What|Removed |Added CC||groszdaniel...@gmail.com --- Comment #3 from Bharadwaj Raju --- *** Bug 429215 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436757] Tooltip sometimes disappears
https://bugs.kde.org/show_bug.cgi?id=436757 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #4 from Bharadwaj Raju --- Possible duplicate of #434657 (fixed)? The steps to reproduce that bug were: Hover over a pinned app, see the tooltip, then move mouse away from panel. now move mouse onto an open window thing, and the tooltip reliably disappears. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436647] Overwriting a gpg-encrypted file results in a zero byte file
https://bugs.kde.org/show_bug.cgi?id=436647 Thomas Baumgart changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.1.2 Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/commit/39785a3d ||80c56dc6e53f301d76c41bcc8ca ||048c6 Status|REPORTED|RESOLVED --- Comment #2 from Thomas Baumgart --- Git commit 39785a3d80c56dc6e53f301d76c41bcc8ca048c6 by Thomas Baumgart. Committed on 12/05/2021 at 06:33. Pushed by tbaumgart into branch '5.1'. Solve problems with usage of QTemporaryFile on MS-Windows A call to QTemporaryFile::close() may not close the file but only rewind the file pointer to the beginning allwing faster re-open. This causes problems on MS-Windows filesystems, as one cannot e.g. rename the temporary file in this case because it is still kept open from the perspective of the filesystem. Only destroying the object really closes the file on the filesystem. This change makes sure, that the QTemporaryFile object only lives as long as it is needed and closed immediately after by destroying the object. FIXED-IN: 5.1.2 M +18 -10 kmymoney/plugins/xml/xmlstorage.cpp https://invent.kde.org/office/kmymoney/commit/39785a3d80c56dc6e53f301d76c41bcc8ca048c6 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 426400] Fix KF5 issues on Windows
https://bugs.kde.org/show_bug.cgi?id=426400 Bug 426400 depends on bug 436647, which changed state. Bug 436647 Summary: Overwriting a gpg-encrypted file results in a zero byte file https://bugs.kde.org/show_bug.cgi?id=436647 What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436956] New: Multiple images copy paste issues
https://bugs.kde.org/show_bug.cgi?id=436956 Bug ID: 436956 Summary: Multiple images copy paste issues Product: plasmashell Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: michal.zubkow...@gmail.com Target Milestone: 1.0 SUMMARY Copy paste of images is working in strange way. Very often I cannot paste images between the apps, or I must do it twice (first time doesn't paste anything). I know already from another bug report that Gimp related cases are Gimp fault, but Libre Office, Firefox, Edge, Chrome are also broken? I've never seen such issues in other desktop environments. I suspect it's something related to copy paste between GTK -> QT apps. Could you please help me to provide enough information for You to solve it to create reproducible case? My tries are: STEPS TO REPRODUCE 1. Run "spectacle -rbc", try to paste in Firefox or Edge in any webapp, sometimes it's working sometimes path is pasted or nothing. 2. Open Gimp, copy image try to paste in LibreOffice, sometimes contents of image is pasted. 3. When copying image from Dolphin in browser only image path is pasted sometimes in browser window. On second try it's working. OBSERVED RESULT Images are not copied, or only paths are pasted, or file content is pasted. Worst thing it occurs randomly and sometimes it's working. EXPECTED RESULT It should paste image. SOFTWARE/OS VERSIONS KDE Neon: 21.04 (but problems was also in previous versions) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436953] Feature request: keyboard shortcut for "assign pick label then advance image" as one action
https://bugs.kde.org/show_bug.cgi?id=436953 --- Comment #7 from caulier.gil...@gmail.com --- Krita recording macro architecture : https://community.kde.org/Krita/Recording_System Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372496] Support tmux control mode
https://bugs.kde.org/show_bug.cgi?id=372496 --- Comment #3 from Murz --- Konsole now already have feature to split view (the tab contents) into parts horizontally and vertically, like tmux, so seems integration is possible. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436953] Feature request: keyboard shortcut for "assign pick label then advance image" as one action
https://bugs.kde.org/show_bug.cgi?id=436953 --- Comment #6 from caulier.gil...@gmail.com --- See bug https://bugs.kde.org/show_bug.cgi?id=119399 for macro recorder... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436953] Feature request: keyboard shortcut for "assign pick label then advance image" as one action
https://bugs.kde.org/show_bug.cgi?id=436953 --- Comment #5 from caulier.gil...@gmail.com --- About Macro recorder, we have another and older entry in bugzilla. Typically, Krita has this kind of tool available since a long time, so stable and work as well. This is the way to experiment and look for a DK solution. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436953] Feature request: keyboard shortcut for "assign pick label then advance image" as one action
https://bugs.kde.org/show_bug.cgi?id=436953 --- Comment #4 from K D Murray --- @Maik: agreed, a generalised macro system for digikam would be fantastic. A perhaps more easily achieved goal would be generalising this to all metadata assignments: picks, ratings, colours, etc. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436953] Feature request: keyboard shortcut for "assign pick label then advance image" as one action
https://bugs.kde.org/show_bug.cgi?id=436953 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- I would understand the function as a kind of macro recorder for key shortcuts. An implementation only for this user use case makes no sense. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436955] New: SYSTEM CRASHED
https://bugs.kde.org/show_bug.cgi?id=436955 Bug ID: 436955 Summary: SYSTEM CRASHED Product: systemsettings Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: achhaabhi...@gmail.com Target Milestone: --- Application: systemsettings5 (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.11.18-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I was trying to change the theme and the application crashed The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7fe9d01250d0 in ?? () #5 0x7feace416ed7 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #6 0x7feace4033e9 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #7 0x7feace41f783 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #8 0x7feacbde1c04 in ffi_call_unix64 () from /lib64/libffi.so.6 #9 0x7feacbde1107 in ffi_call () from /lib64/libffi.so.6 #10 0x7feace370d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #11 0x7feace37142b in dispatch_event.isra () from /lib64/libwayland-client.so.0 #12 0x7feace37161c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #13 0x7feace3fb5ef in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #14 0x7fead07884fd in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7fead07a478b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7fead07569b2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7fead075e544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #18 0x5630ed838d4c in main () [Inferior 1 (process 4316) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430862] Kde5init crashes in ThumbnailProtocol::get() every time I take a screenshot or start the computer
https://bugs.kde.org/show_bug.cgi?id=430862 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added CC||1i5t5.dun...@cox.net --- Comment #91 from Duncan <1i5t5.dun...@cox.net> --- (In reply to vindicator from comment #19) > I'm curious why the other posts (specifically older) "has been marked as a > duplicate of this bug" Bug is resolved/fixed (and my curiosity upon seeing it referenced in the git logs is why I'm here) but I don't see that this question was ever answered. So here's my (explicitly unofficial as I'm just another bugfiler, here and elsewhere) attempt at an answer... There are (at least) two general bug-duplicate policies that can be employed by devs choosing which bugs to mark as duplicates. Some products or bug installations use one, some the other, and others may default to the first but choose the second given a strong enough reason on an individual bug basis. 1) Chronological order policy. Newer bugs are always duplicates of the oldest, original bug. This could be argued to be the most "correct", but often has the practical issue described/solved by the more pragmatic policy below. Still it's the most reasonable default in the absence of a solid reason to override and is thus favored where such priority-overrides are less common. In my experience distros commonly have this policy, probably because of their function as accumulators/packagers of software from various upstream sources. 2) Pragmatic "most useful information" policy. The "original" bug is defined as the one with the most useful information already posted to it at the time of the duplicate marking, regardless of which one was actually filed first. In my experience this policy is more common on upstream original software source providers, I'd suggest due to reasoning below, but extended to the more general case (that is, not always will the most informative bug-filing be the one with the commit-ID attached). Especially where (semi-)automated crash-report filing is used (as it is with some kde components and apps, with the user's consent of course), the often-automated chronologically first bugs may have very little additional information, while a bug filed later, sometimes only because its author took the time to collect and add additional information, has more practically useful information in terms of actually fixing the bug. A recent bug I filed where earlier bugs were marked duplicates of mine is a good example. For kde I run live-git versions built myself (using the gentoo/kde project's build scripts so it's pretty automated) and I normally update once or twice a week. I found a regression that wasn't there before my last update, so I checked the git logs to see what changed and then bisected the problem down to an individual commit. When I filed the bug it had the git commit ID that triggered the problem in the subject line. There was other information in the bug as well but honestly the commit ID was probably the most helpful and the reason earlier bugs were marked dupes of mine. But bisecting to an individual commit is a non-trivial amount of work and takes time. By the time I did that there were other bugs reporting the problem. But despite not being first, my bug was (presumably) considered to have more useful info attached, as I said, likely the commit ID alone was enough, so other bugs, including some filed earlier, were declared duplicates of mine. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 436719] Thumbnails wont rebuild
https://bugs.kde.org/show_bug.cgi?id=436719 --- Comment #8 from isenh...@yahoo.co.uk --- Sorry, can't do that now as it is all working but I can say that the thumbnail index file had loads of thumbnails in the list (all correct as far as I could see) but only a handful of thumbnails were produced and only one was correct. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436953] Feature request: keyboard shortcut for "assign pick label then advance image" as one action
https://bugs.kde.org/show_bug.cgi?id=436953 --- Comment #2 from K D Murray --- With current settings, pressing 1 would assign rejected to all selected images, and + would deselect the selection and select the image after the last selected image. I assume the same would happen with the hypothetical feature I describe below? That's certainly what I'd assume should happen. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 436954] New: Plasma Version detection broken and unreliable
https://bugs.kde.org/show_bug.cgi?id=436954 Bug ID: 436954 Summary: Plasma Version detection broken and unreliable Product: kinfocenter Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Information Assignee: plasma-b...@kde.org Reporter: skierp...@gmail.com CC: sit...@kde.org Target Milestone: --- SUMMARY In Fedora 34, System Information doesn't show KDE Plasma Version. STEPS TO REPRODUCE 1. Run `kinfocenter` from a terminal, or start "system information" from Application Launcher. OBSERVED RESULT There's no KDE Plasma Version (even though this bug template calls for it). EXPECTED RESULT KDE Plasma Version used to appear. One workaround is run `plasmashell --version` in a terminal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System)← or not 😉 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 on Wayland ADDITIONAL INFORMATION https://invent.kde.org/plasma/kinfocenter/-/blob/master/Modules/about-distro/src/PlasmaEntry.cpp is trying to get the Plasma version by reading the value of X-KDE-PluginInfo-Version from xsessions/plasma.desktop. But https://invent.kde.org/plasma/plasma-workspace/-/tree/master/login-sessions now installs /usr/share/wayland-sessions/plasma.desktop and /usr/share/xsessions/plasmax11.desktop, so this lookup fails. I guess the code could look for wayland-sessions/plasma.desktop if the XDG_SESSION_TYPE environment variable == "wayland", otherwise xsessions/plasmax11.desktop. As the code comments, this is an unreliable way to detect the Plasma version: > // Since Plasma version detection isn't based on a library query it can fail > // in weird cases; instead of admitting defeat we simply hide everything :P kinfocenter doesn't seem to link in any plasma library that it could query for a version. For comparison, Gnome installs /usr/share/gnome/gnome-version.xml, 'a data file that exports the "GNOME" version to the Settings Details panel.' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435618] Plasmashell crashes in QSGSoftwareInternalImageNode::pixmap() when clicking a widget in the system notification area
https://bugs.kde.org/show_bug.cgi?id=435618 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-gstreamer] [Bug 435576] Crash when resume from nonstandard resume
https://bugs.kde.org/show_bug.cgi?id=435576 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 436118] "Software not from a trusted source" prompt does not tell which package is the suspect one
https://bugs.kde.org/show_bug.cgi?id=436118 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436222] Crush kinit5
https://bugs.kde.org/show_bug.cgi?id=436222 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[knetwalk] [Bug 200726] impossible to deactivate sound
https://bugs.kde.org/show_bug.cgi?id=200726 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436953] Feature request: keyboard shortcut for "assign pick label then advance image" as one action
https://bugs.kde.org/show_bug.cgi?id=436953 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Hum, what we can do if multiple selection is done in this case, especially in icon-view ? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 191086] wish: read-only calendars should not cause reminder alarms to fire (or this capability should be configurable on a calendar by calendar basis)
https://bugs.kde.org/show_bug.cgi?id=191086 Chris Kerr changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED CC||chris.k...@mykolab.ch --- Comment #2 from Chris Kerr --- (In reply to gjditchfield from comment #1) > The Folder Properties dialog of each calendar now has a "Block reminders > locally" option on the General tab. Does that satisfy this wish? Yes. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436953] New: Feature request: keyboard shortcut for "assign pick label then advance image" as one action
https://bugs.kde.org/show_bug.cgi?id=436953 Bug ID: 436953 Summary: Feature request: keyboard shortcut for "assign pick label then advance image" as one action Product: digikam Version: 7.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability-Keyboard Assignee: digikam-bugs-n...@kde.org Reporter: f...@kdmurray.id.au Target Milestone: --- SUMMARY To facilitate rating large numbers of images, I have the three pick label states mapped to my numeric keypad: 1 -> rejected, 2 -> pending, 3-> accepted. I also have the + and - of my numeric keypad mapped to next/previous image. This way, I can press 1 then + to reject an image, 2 then + to mark images for further consideration. This is a workable system, however other tools I've used allow mapping "rate then move on" as a single keypress (in the above example, pressing 1 would assign rejected label and move to the next image). Would this be difficult to support in Digikam? My QT is a bit rusty, but is there a way to trigger multiple slots (slotAssignPickLabel() and then slotNextItem()) from one key combination? STEPS TO REPRODUCE n/a OBSERVED RESULT n/a EXPECTED RESULT n/a SOFTWARE/OS VERSIONS Linux 7.2.0-rc AppImage ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436285] can't get past grub boot after offline update on thinkpad
https://bugs.kde.org/show_bug.cgi?id=436285 --- Comment #9 from kinghat --- i removed all of my older kernels to test my theory about there not being enough room for more kernels during the update process, and somehow leaving my /boot dir empty, was partially confirmed with the recent 5.8.0-53-generic update. the update went fine 🤷♂️ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436952] Missing Animation Dockers due to MacOS CMake Changes
https://bugs.kde.org/show_bug.cgi?id=436952 --- Comment #1 from Eoin O'Neill --- Sorry, I accidentally said `SHARED` to `MODULE` in the original post, but it was actually changed the other way around in commit f862034e93a62fd2538fde0efece9310e99abbf2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436952] New: Missing Animation Dockers due to MacOS CMake Changes
https://bugs.kde.org/show_bug.cgi?id=436952 Bug ID: 436952 Summary: Missing Animation Dockers due to MacOS CMake Changes Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: eoinoneill1...@gmail.com Target Milestone: --- SUMMARY Since commit f862034e93a62fd2538fde0efece9310e99abbf2 (found via Bisect), the animation dockers are not properly included in Krita builds (Not selectable, missing from animation workspace.) Something about changing the libraries from `SHARED` to `MODULE` has caused this regression on my Linux system. I only noticed this because I was debugging a resource system safe assert that was preventing me from opening files. I tried clearing my install and database, which worked, but I was missing the animation dockers that were previously there due to linking. STEPS TO REPRODUCE 1. Clear your install folder, build folder, and various config folders. 2. Run Cmake, Build Krita fresh, Launch Krita 3. Select the `Animation` workspace, or try manually adding the dockers via the docker view menu. SOFTWARE/OS VERSIONS OS: Manjaro 21.0.4 Ornara Kernel: x86_64 Linux 5.10.34-1-MANJARO Uptime: 1h 27m Packages: 1676 Shell: bash 5.1.4 Resolution: 3120x1920 WM: sway GTK Theme: -theme [GTK3] Disk: 1.2T / 3.8T (32%) CPU: Intel Core i7-4770K @ 8x 3.9GHz [42.0°C] GPU: Radeon RX 590 Series (POLARIS10, DRM 3.40.0, 5.10.34-1-MANJARO, LLVM 11.1.0) RAM: 2942MiB / 11916MiB ADDITIONAL INFORMATION It's also worth checking whether this affects the docker / appimage bundle. So far, I've observed this issue on both Manjaro and Fedora systems. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 436951] New: in bug template, "About System" is renamed and may not provide KDE Plasma Version.
https://bugs.kde.org/show_bug.cgi?id=436951
Bug ID: 436951
Summary: in bug template, "About System" is renamed and may not
provide KDE Plasma Version.
Product: bugs.kde.org
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: templates
Assignee: sysad...@kde.org
Reporter: skierp...@gmail.com
CC: she...@kde.org
Target Milestone: ---
SUMMARY
The guide for getting versions in the template for filing KDE bugs doesn't
match Plasma desktop.
STEPS TO REPRODUCE
1. Enter a new bug, choose a product such as bugs.kde.org
OBSERVED RESULT
The bugzilla template includes
> SOFTWARE/OS VERSIONS
> Windows:
> macOS:
> Linux/KDE Plasma:
> (available in About System)
> KDE Plasma Version:
> KDE Frameworks Version:
> Qt Version:
but
a) it's not called "About System", it's called "System Information." Entering
"About system" in the Plasma application launcher works, but it's a little
confusing.
b) In Fedora 34, System Information does not display the KDE Plasma Version.
Instead I run `plasmashell --version` in a terminal window.
EXPECTED RESULT
Better verbiage. Change to say something like "(available in System
Information)", I'm not sure how to get Plasma version.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2 Wayland
ADDITIONAL INFORMATION
https://invent.kde.org/plasma/kinfocenter/-/blob/master/Modules/about-distro/src/PlasmaEntry.cpp
suggests that it's trying to get the Plasma version from
xessions/plasma.desktop, but comments
> // Since Plasma version detection isn't based on a library query it can fail
(I have /usr/share/wayland-sessions/plasma.desktop and
/usr/share/xsessions/plasmax11.desktop ; I'll file a separate bug.)
Does this part of the bug template make sense for Windows and macOS users? Even
without System Settings, they can still provide KDE versions; most KDE apps
provide it in Help > About {KDE Appname} > Libraries. Or are the three lines
intended to get the user to indicate which O.S. she is using, in which case
collapse them to one question:
> SOFTWARE/OS VERSIONS
> Which O.S. (Windows/macOS/Linux) and version are you running? :
> The following are shown in System Information or a KDE application's Help >
> About {Appname} > Libraries.
> KDE Plasma Version:
> KDE Frameworks Version:
> Qt Version:
Would it help to ask Linux users for Graphics Platform (wayland or X11) that my
System Information shows?
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 436946] Settings not permanent
https://bugs.kde.org/show_bug.cgi?id=436946 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.3.0 Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from caulier.gil...@gmail.com --- same for me. Tested on my 3 Linux configurations with last stable 7.2.0 or current pre-release 7.3.0. You can use the Linux AppImage than we provide officially or the pre-release here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435170] Option to bring all of an app's windows to the front when one window is switched to
https://bugs.kde.org/show_bug.cgi?id=435170 --- Comment #3 from RedBearAK --- There is another desktop environment that has the ability to have both "Switch windows" and "Switch applications" active at the same time on different keyboard shortcuts. It is possible that some users would have a use case where they would want to have application-centric task switching on one workspace, and window-centric task switching on a different workspace. It would be sad if KDE couldn't do the same thing. So the ideal way to implement the fix for this feature request would actually be to allow the user to designate one keyboard shortcut that activates "window switching", where each window is treated as a separate entity, and a different keyboard shortcut that activates "application switching", where application windows are treated as a linked group. The two different modes on this other desktop environment each have their own task switcher dialog that comes up. The "Only one window per application" option that currently exists should only apply to the "application switching" mode of the task switcher dialog. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 205104] Complex filtering for tasks in Calendar / Task view
https://bugs.kde.org/show_bug.cgi?id=205104 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from gjditchfi...@acm.org --- KOrganizer 5.17.0 lets you 1) filter by priorities 2) sort by dates 3) filter by summary contents Is that adequate? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 436950] New: Konsole --tabs-from-file command behavior is opaque and hard to debug
https://bugs.kde.org/show_bug.cgi?id=436950 Bug ID: 436950 Summary: Konsole --tabs-from-file command behavior is opaque and hard to debug Product: konsole Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: skierp...@gmail.com Target Milestone: --- SUMMARY I've been fighting konsole --tabs-from-file for an hour just trying to make it run some commands in a tab that sticks around. STEPS TO REPRODUCE 1. Add the following to ~/konsole_tabs file: title: Echo %d : %n;; command: echo 123456 title: Echo background;; command: echo Did anything happen & title: Cat;; command: cat - title: Bad;; command: badprogramname 2. Run `konsole --tabs-from-file ~/konsole_tabs 3. Run `konsole --hold --tabs-from-file ~/konsole_tabs OBSERVED RESULT The echo command completes; but without --hold the tab goes away. The echo background tab goes away; with --hold you get a red error message > Warning: Could not find 'echo Did anything happen &',... The cat command echoes input, but when you press Ctrl-D, the tab goes away. The bad tab helpfully tells you in red > Warning: Could not find 'badprogramname', starting (your shell)... In the terminal where you ran this, konsole displays > [18::30:59.234] unknown: "Could not find binary: " "" > [18::30:59.301] unknown: "Could not find binary: " "badprogramname" EXPECTED RESULT This need not be so prone to error and confusion. (A) The number one thing that would help is to change https://docs.kde.org/stable5/en/konsole/konsole/command-line-options.html to say "Use the --hold command-line option with --tabs-from-file, it can help debug any problems." (B) The next thing is for the documentation to explain how the heck > command: a command to run actually works. Is "command" interpreted by a shell? (No, I think). Can it have arguments (yes, I think). Are any environment variables available? (I don't know). Can you have more than one command? (I don't think so.) Is it possible to have more than one command? (I Googled for hours and tried dozens of command lines). Can you have the shell stick around, remaining interactive? (I don't think so, though surely this is a common desire!) (C) The console output should be much more helpful. Instead of: > [18::36:1.771] unknown: "Could not find binary: " "" It should say something more useful, like konsole --tabs-from-file option had problem with tab titled "Echo sleep" executing command `echo Did anything happen &`, error is 'Could not find binary " "'. (D) It should be easier to have the tab run one or more commands and then become a normal interactive shell, either by modifying Konsole's behavior or documenting how to do this. The behavior when you ask Konsole to run `badprogramname` and it tells you it had a problem then runs your shell seems generally useful; in the case of success it could print a similar message in green then run your shell. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version:5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Wayland ADDITIONAL INFORMATION Examples of the hair-pulling this causes: * https://forum.kde.org/viewtopic.php?f=227&t=152305 * https://forum.kde.org/viewtopic.php?f=227&t=160124 * https://stackoverflow.com/questions/32779281/how-to-launch-a-kde-konsole-with-multiple-tabs-running-various-progs Konsole is demonstrably difficult to automate, but thanks for a great terminal program! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 202788] Non-time-associated event is not shown
https://bugs.kde.org/show_bug.cgi?id=202788 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||gjditchfi...@acm.org --- Comment #1 from gjditchfi...@acm.org --- I can't reproduce the "event not shown" part of this bug wit 5.17.0, and the "new event" part is a duplicate. *** This bug has been marked as a duplicate of bug 146564 *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 146564] [Wishlist] All Day area New Event function
https://bugs.kde.org/show_bug.cgi?id=146564 gjditchfi...@acm.org changed: What|Removed |Added CC||andr...@pietzowski.de --- Comment #1 from gjditchfi...@acm.org --- *** Bug 202788 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 200002] Please add "All Events" view
https://bugs.kde.org/show_bug.cgi?id=22 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||gjditchfi...@acm.org --- Comment #1 from gjditchfi...@acm.org --- *** This bug has been marked as a duplicate of bug 195542 *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 195542] View all events and to-do (no filtering on date)
https://bugs.kde.org/show_bug.cgi?id=195542 gjditchfi...@acm.org changed: What|Removed |Added CC||kde-2011...@dotancohen.com --- Comment #3 from gjditchfi...@acm.org --- *** Bug 22 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 436949] New: AltGr is disabled under Lokalize. Cannot enter letters, symbols otherwise available with AltGr + key
https://bugs.kde.org/show_bug.cgi?id=436949 Bug ID: 436949 Summary: AltGr is disabled under Lokalize. Cannot enter letters, symbols otherwise available with AltGr + key Product: lokalize Version: 21.04.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: bozid...@yahoo.com CC: sha...@ukr.net Target Milestone: --- SUMMARY AltGr key on Windows is disabled bz Lokaliye STEPS TO REPRODUCE 1. Change keyboard layout to HR language 2. Press AltGr + any key 3. nothing is inserted, like AltGr does not exisist OBSERVED RESULT Cannot entered letters which in other apps is possible EXPECTED RESULT To use AltGr like in any other apps 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.
[korganizer] [Bug 191086] wish: read-only calendars should not cause reminder alarms to fire (or this capability should be configurable on a calendar by calendar basis)
https://bugs.kde.org/show_bug.cgi?id=191086 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from gjditchfi...@acm.org --- The Folder Properties dialog of each calendar now has a "Block reminders locally" option on the General tab. Does that satisfy this wish? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436725] 5.0.0-prealpha does not produce a log_encode.log file
https://bugs.kde.org/show_bug.cgi?id=436725 --- Comment #4 from Eoin O'Neill --- Hey Ahab Greybeard, This change has to do with the unification of multiple FFMPEG wrappers. We currently have a discussion around the FFMPEG wrapper and it's future on phabricator ( https://phabricator.kde.org/T14331 ) which encompasses some of the discussion around using the temp folder, what to do with temporary files, and more. Currently, the plan is to always store the log file in the system temporary folder and to only move (really, copy) the log file into the destination folder (where the video file was going to save) if we determine that FFMPEG ran into an error, which the new C++ wrapper is better at determining. Before, the log file was always saved into the target directory regardless of success or failure, which created a lot of garbage and unused data for the artists IMO. Additionally, with the increased scope of parts that use FFMPEG within Krita, it would be nice to have a unified place for us to ask users to check if they want to know how ffmpeg ran for their given task. With that in mind, we're still in the planning and discussion phase, with more changes planned beyond 5.0's release. Please, if you have any specific requests regarding animation / ffmpeg / log file production, please give us your thoughts on the phabricator page so that we can have a single place to track discussion around this topic. Additionally, since KnowZero has also been helping with FFMPEG features and frontend changes, it will also help him to see artist and user feedback on some of the more recent changes to the FFMPEG wrapper as well. I'm going to leave this open and assigned. For 5.0's immediate release, I will at least make sure that FFMPEG will reliably place error files where videos were supposed to go when errors occur and triple check that all of the FFMPEG operations produce a log file in the temp folder as they should. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436820] certificate not found
https://bugs.kde.org/show_bug.cgi?id=436820 --- Comment #8 from Gabriel Memmert --- Oh, that's very true. I didn't find good changes yet. Nevertheless two sugestions: * Poppler will try to use the following -> Poppler will try to use one of the following * adding: You can check which cert store is used via the entry in the 'PDF Backend Configuration' section of the 'Configure Backends...' dialog. I would appreciate if there were instructions on how to properly (or easiest) add a certificate. I am not sure whether this would be helpfull to many people. What is the usual setup procedure to enable the signing documents? Is it something that is always preconfigured in your organisation? After reading on [ArchWiki - nss](https://wiki.archlinux.org/index.php/Network_Security_Services) and [MDN NSS](https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Tools) I got to these two instructions that worked for me (manjaro kde, firefox installed, .p12 and .pfx certificates): VERSION A: 1. Go to the 'PDF Backend Configuration' section of the 'Configure Backends...' dialog. Find the certificate store that okular uses by default (right now one can *not* mark or copy from this field!) and in the following commands please substitute 'cert/store' with the found path. One example would be `/home/myuser/.mozilla/firefox/abcdef12.default-release` 2. Add the certificate via `pk12util -d sql:cert/store -i /path/to/cert/filename.p12`. You can see the certificate added in `certutil -d sql:cert/store -L`. You can check the certificate for signing messages via `certutil -d sql:cert/store -V -u S -n "certificate-name"` you need to look for `certificate-name` in the output of the previous command. This output is acceptable: `certutil: certificate is invalid: Peer's certificate issuer has been marked as not trusted by the user.` 3. restart okular, now everything should be working. The certificate should be listed in the 'PDF Backend Configuration' section. VERSION B: 1. Add the certificate via `pk12util -d sql:$HOME/.pki/nssdb -i /path/to/cert/filename.p12`. You can see the certificate added in `certutil -d sql:$HOME/.pki/nssdb -L`. You can check the certificate for signing messages via `certutil -d sql:$HOME/.pki/nssdb -V -u S -n "certificate-name"` you need to look for `certificate-name` in the output of the previous command. This output is acceptable: `certutil: certificate is invalid: Peer's certificate issuer has been marked as not trusted by the user.` 2. Go to the 'PDF Backend Configuration' section of the 'Configure Backends...' dialog. Set the certificate store to custom and set the path to `$HOME/.pki/nssdb` 3. restart okular, now everything should be working. The certificate should be listed in the 'PDF Backend Configuration' section. Questions: * Do I need `sql:` in the commands? * Is the environment variable the same in okular and shell? * Should one do something about this invalid certificate message? * ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436607] KDe crashed when close the vlc window
https://bugs.kde.org/show_bug.cgi?id=436607 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- We're missing debug symbols here: #11 0x7fde04031025 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436948] Kwin uses 1.5GiB of ram(and 87Megs of shared mem)
https://bugs.kde.org/show_bug.cgi?id=436948 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- There are many types of "ram" used, some harmless some not. Please include a full screenshot from ksysguard/plasma-sytemmonitor. Then if things look like a leak please collect a trace with heaptrack -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged on a Wayland session after I've switched from main
https://bugs.kde.org/show_bug.cgi?id=421700
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #16 from David Edmundson ---
It still doesn't make any sense.
We're iterating through
```
const auto screens = qGuiApp->screens();
for (QScreen *screen : screens) {
... screen->name()
and yet end up with screen being dangling.
There's only two ways this could happen.
1) The QPA is feeding us garbage
2) someone is starting a nested event loop somewhere whilst we're in
"addOutput" and this is removing a screen, whilst we iterate over the copy of
the list
I checked for the latter, but found nothing. Potentially that's applet
dependent, it only takes one to be doing something wrong.
This needs investigation from someone who can reproduce it reliably before we
can do anything.
If someone can reproduce locally and can install debug symbols let me know and
I'll suggest some gdb commands.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 domy...@gmail.com changed: What|Removed |Added CC||domy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436816] If a shortcut component is deleted while being viewed, its name sometimes becomes unreadable
https://bugs.kde.org/show_bug.cgi?id=436816 --- Comment #3 from Nate Graham --- Git commit a73ce76190d2ba08bf3c0f492e9f06a67beeceac by Nate Graham. Committed on 11/05/2021 at 22:56. Pushed by ngraham into branch 'master'. Add new fadeContent property to BasicListItem This new property can be used to make the main content of a BasicListitem have a disabled or de-emphasized look while preserving full opacity for any leading or trailing items. M +15 -3src/controls/BasicListItem.qml https://invent.kde.org/frameworks/kirigami/commit/a73ce76190d2ba08bf3c0f492e9f06a67beeceac -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436948] New: Kwin uses 1.5GiB of ram(and 87Megs of shared mem)
https://bugs.kde.org/show_bug.cgi?id=436948 Bug ID: 436948 Summary: Kwin uses 1.5GiB of ram(and 87Megs of shared mem) Product: kwin Version: 5.20.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: kuba...@yahoo.com Target Milestone: --- SUMMARY I have a 13 hour uptime. STEPS TO REPRODUCE 1.Use a computer. gtx 1060, closed source drivers nvidia-dkms, linux-zen OBSERVED RESULT Every kde component seems to use a "healthy" amount of ram. But it seems like kwin_x11, got a bit chunky. EXPECTED RESULT I don't have to call kwin_x11 --replace every now and then, this brings it down to 200-110MiB(grows if one uses certain features etc. not everything needs to be aggressively garbage collected at all times, but 1.5GiB is excessive for 4 windows open[konsole, firefox, ksysguard, hexchat], 2 empty workspaces(out of 3))+99MiB. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.12.2-zen2-1-zen KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436086] PNG image in CBZ wrapper does not display correctly (but PNG itself does)
https://bugs.kde.org/show_bug.cgi?id=436086 Albert Astals Cid changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414785] Notifications cause system lag
https://bugs.kde.org/show_bug.cgi?id=414785 --- Comment #4 from Lapineige --- I have this issue again for a few days. KDE : 5.19.5. Nvidia drivers : 450.119.03. I did not have the changes in usr/share/X11/xorg.conf.d/10-nvidia.conf adviced in the reddit topic. I don't know if it was intentional (not done last time), something I forgot, and some file overwritten by a driver update or so. I did them. Let's hope this will solve the issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 424734] Unnecessary console messages: "Sonnet: Unable to load plugin ...."
https://bugs.kde.org/show_bug.cgi?id=424734 Podagric changed: What|Removed |Added CC||kde.podag...@slmail.me --- Comment #2 from Podagric --- apparently this is a krunner bug. it is displayed to me as soon as I type anything into krunner after its first run. If the dictionary and spell check runners are disabled, these messages are not displayed. In fact, that seems to be the reason the dictionary runner doesn't work for me. The spelling checker works perfectly. In addition, although the log reports that the files exist, it is possible to find them in the folder. $ ls /usr/lib/qt/plugins/kf5/sonnet/ sonnet_aspell.so sonnet_hspell.so sonnet_hunspell.so sonnet_voikko.so -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436947] New: There is a delay to update task manager on switching between virtual desktops while an app plays audio
https://bugs.kde.org/show_bug.cgi?id=436947 Bug ID: 436947 Summary: There is a delay to update task manager on switching between virtual desktops while an app plays audio Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 138349 --> https://bugs.kde.org/attachment.cgi?id=138349&action=edit screen recording SUMMARY Please watch the attached screen recording showing the delay to update task manager that occurs when I switch between virtual desktops while an app plays audio. This delay stops when I close the audio player. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 370397] Support coloring/tinting of tabs
https://bugs.kde.org/show_bug.cgi?id=370397 --- Comment #4 from Eyal Rozenberg --- In those screenshot, I see a colored line under the tab. That's not sufficient, it should be possible to color the whole tab. The line is not noticeable enough. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385329] Klipper preview does not display character before newline.
https://bugs.kde.org/show_bug.cgi?id=385329 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #6 from Patrick Silva --- I have just noticed this bug on neon unstable. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433166] Plasma slows to a crawl with low CPU usage after certain system setting changes
https://bugs.kde.org/show_bug.cgi?id=433166 twinshadows...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED --- Comment #13 from twinshadows...@gmail.com --- Yes. https://drive.google.com/file/d/1zpPQ52ka1kBkTDe867bmO389BttJ5tT0/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 370397] Support coloring/tinting of tabs
https://bugs.kde.org/show_bug.cgi?id=370397 --- Comment #3 from Podagric --- > I'm not using the latest KDE right now, so I can't verify this being the > case. But I won't object if someone verifies it and closes the bug. here's an example of what is possible in version 21.04 https://i.imgur.com/iJO83L1.png https://i.imgur.com/6SipIqY.png -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436932] Provide a better placeholder message when no app-backends are available
https://bugs.kde.org/show_bug.cgi?id=436932 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396791] Theme cache doesn't invalidate on output scale changes
https://bugs.kde.org/show_bug.cgi?id=396791 Nate Graham changed: What|Removed |Added CC||war...@gmx.de --- Comment #4 from Nate Graham --- *** Bug 436918 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436918] Corners of input fields appear pixelated at higher DPI
https://bugs.kde.org/show_bug.cgi?id=436918 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Component|Theme - Breeze |general Resolution|WAITINGFORINFO |DUPLICATE Assignee|visual-des...@kde.org |k...@davidedmundson.co.uk --- Comment #3 from Nate Graham --- AH, Then this is Bug 396791. *** This bug has been marked as a duplicate of bug 396791 *** -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 436885] High RAM consumption
https://bugs.kde.org/show_bug.cgi?id=436885 --- Comment #3 from Elisha Daugherty Podagric --- I understand. Thank you for the explanation! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436926] Primary screen picking from SDDM is extremely unreliable
https://bugs.kde.org/show_bug.cgi?id=436926 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- So you're saying that which screen is the primary one actually changes depending on your cursor position when you log in or resume from sleep? Can you confirm that the primary screen setting in System Settings > Display & Monitor > Display Configuration is actually changing? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419438] [feature] - "cycle through minimized + minimize all" actions for tasks
https://bugs.kde.org/show_bug.cgi?id=419438 Max Grävendieck changed: What|Removed |Added CC||mgraevendi...@outlook.de --- Comment #5 from Max Grävendieck --- (In reply to Michail Vourlakos from comment #4) > (In reply to Peter from comment #3) Last used is shown or all of them are unminimized? Yes, just like this -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 436719] Thumbnails wont rebuild
https://bugs.kde.org/show_bug.cgi?id=436719 --- Comment #7 from Johannes Zarl-Zierl --- Sorry, I meant to run it inside a console window. I should have mentioned this. You'll get some output like this: Thumbnail cache directory: /data/images/.thumbnails/ Thumbnail index file version: 5 Maximum supported thumbnailindex file version: 5 Thumbnail storage dimensions: 452 pixels Number of thumbnails: 33 674 The number of thumnails should ideally match the number of images in your database, as shown in the lower right corner of the kphotoalbum window. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 390700] Unable to convert Fujifilm RAF RAW to DNG
https://bugs.kde.org/show_bug.cgi?id=390700 --- Comment #18 from Maik Qualmann --- Git commit e4dee8b223a2ce81e8d70af37472dcc83f4e4c11 by Maik Qualmann. Committed on 11/05/2021 at 20:37. Pushed by mqualmann into branch 'master'. add Fuji X-Trans sensor identify Colors not yet correct. M +17 -6core/libs/dngwriter/dngwriter_convert.cpp M +1-0core/libs/dngwriter/dngwriter_p.h https://invent.kde.org/graphics/digikam/commit/e4dee8b223a2ce81e8d70af37472dcc83f4e4c11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436946] Settings not permanent
https://bugs.kde.org/show_bug.cgi?id=436946 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The problem cannot be reproduced in digiKam-7.3.0. Maik -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 370397] Support coloring/tinting of tabs
https://bugs.kde.org/show_bug.cgi?id=370397 --- Comment #2 from Eyal Rozenberg --- (In reply to Podagric from comment #1) > it is now possible to do so. > could you close this bug? I'm not using the latest KDE right now, so I can't verify this being the case. But I won't object if someone verifies it and closes the bug. > and this is a duplicate of the bug > https://bugs.kde.org/show_bug.cgi?id=278699 Well, only partly, but it merits a different bug anyway. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436946] Settings not permanent
https://bugs.kde.org/show_bug.cgi?id=436946 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Setup-Views CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436946] New: Settings not permanent
https://bugs.kde.org/show_bug.cgi?id=436946 Bug ID: 436946 Summary: Settings not permanent Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: kurti.goe...@gmail.com Target Milestone: --- If I select a different (bold) font in "Settings"/"Digikam setup"/"Appearance"/"Application font", then afterwards this selected font is visible in Digikam. After quitting Digikam and then restarting Digikam, this setting is gone and the original font is displayed. Linux/KDE Plasma: Linux Mint (x86_64) release 5.4.0-73-generic KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436682] Desktop windows shrink or disappear if an output is unplugged
https://bugs.kde.org/show_bug.cgi?id=436682 Vlad Zahorodnii changed: What|Removed |Added URL|https://github.com/qt/qtway |https://codereview.qt-proje |land/commit/14d066c61025e54 |ct.org/c/qt/qtwayland/+/334 |8227ccd8d655e80ffa31fa15e |532 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436682] Desktop windows shrink or disappear if an output is unplugged
https://bugs.kde.org/show_bug.cgi?id=436682 Vlad Zahorodnii changed: What|Removed |Added URL||https://github.com/qt/qtway ||land/commit/14d066c61025e54 ||8227ccd8d655e80ffa31fa15e Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Vlad Zahorodnii --- This is a bug in buffer size tracking in wayland-egl client buffer integration. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436832] Fade in/out not working on rendered output
https://bugs.kde.org/show_bug.cgi?id=436832 Herr Irrtum changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436832] Fade in/out not working on rendered output
https://bugs.kde.org/show_bug.cgi?id=436832 --- Comment #5 from Herr Irrtum --- Solved! I am sorry for having wasted your valuable time! Won't happen again! (In reply to Vincent PINON from comment #4) > your latest log shows mlt-7, but Kdenlive 21.04 is not updated and targets > mlt-6 (which should be co-installable?). We do have a MLT7 branch for > Kdenlive, but it misses features that have been ported to new API. Ah! Thanks Vincent. This is an Arch Linux issue. ``` melt --version melt 7.0.0 Copyright (C) 2002-2021 Meltytech, LLC ``` But kdenlive still reports Melt 6 in it's about dialog. Arch has a separate melt package (which happens to be v.7) and for some reason I had installed it. There is also a "mlt6" package - and it's melt6 binary renders my example just fine! So Vincenct was on point here. Again sorry. And thanks for helping anyway! -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 436885] High RAM consumption
https://bugs.kde.org/show_bug.cgi?id=436885 --- Comment #2 from george fb --- > does haruna not share the mpv process with other programs? Do you mean like smplayer where you have an mpv process started by smplayer? If yes than that's because smplayer uses window embedding https://github.com/mpv-player/mpv-examples/tree/master/libmpv#native-window-embedding while Haruna uses render API https://github.com/mpv-player/mpv-examples/tree/master/libmpv#render-api So when looking at smplayer memory usage you should count mpv's memory too. And if you count the total memory, shared + not-shared, the difference will also be smaller. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 390700] Unable to convert Fujifilm RAF RAW to DNG
https://bugs.kde.org/show_bug.cgi?id=390700 --- Comment #17 from Maik Qualmann --- The 45 degree rotation is a Fuji specialty from SuperCCD, the image is recorded that way with older cameras. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436832] Fade in/out not working on rendered output
https://bugs.kde.org/show_bug.cgi?id=436832 --- Comment #4 from Vincent PINON --- your latest log shows mlt-7, but Kdenlive 21.04 is not updated and targets mlt-6 (which should be co-installable?). We do have a MLT7 branch for Kdenlive, but it misses features that have been ported to new API. But this is not the problem here as melt fails alone. And your initial report show mlt libraries 6.26.1... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430661] Two keyboard layout indicators are showing in the system tray
https://bugs.kde.org/show_bug.cgi?id=430661 --- Comment #21 from Andrey --- Git commit a845e67aba7232a2561b3388ba84db6a60b7cfdc by Andrey Butirsky. Committed on 11/05/2021 at 19:05. Pushed by butirsky into branch 'master'. [kcms/keyboard] Drop legacy keyboard indicator A new applet was created that speaks DBus. Having the old settings is a very confusing user experience. It is also a lot of now obsoleted code. M +0-3kcms/keyboard/CMakeLists.txt M +8-8kcms/keyboard/bindings.cpp M +1-1kcms/keyboard/bindings.h M +0-132 kcms/keyboard/flags.cpp M +0-29 kcms/keyboard/flags.h M +10 -50 kcms/keyboard/kcm_keyboard.ui M +4-28 kcms/keyboard/kcm_keyboard_widget.cpp M +1-8kcms/keyboard/kcm_view_models.cpp M +0-30 kcms/keyboard/keyboard_config.cpp M +0-19 kcms/keyboard/keyboard_config.h M +2-27 kcms/keyboard/keyboard_daemon.cpp M +0-3kcms/keyboard/keyboard_daemon.h D +0-123 kcms/keyboard/layout_tray_icon.cpp D +0-63 kcms/keyboard/layout_tray_icon.h D +0-136 kcms/keyboard/layouts_menu.cpp D +0-56 kcms/keyboard/layouts_menu.h M +1-1kcms/keyboard/tests/CMakeLists.txt https://invent.kde.org/plasma/plasma-desktop/commit/a845e67aba7232a2561b3388ba84db6a60b7cfdc -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 436945] New: Request for icon for Tokodon
https://bugs.kde.org/show_bug.cgi?id=436945 Bug ID: 436945 Summary: Request for icon for Tokodon Product: Breeze Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: c...@carlschwan.eu CC: kain...@gmail.com Target Milestone: --- SUMMARY Hi, it would be nice if someone could create an icon for Tokodon, a KDE client for Mastodon. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 430339] Clipboard gets two entries (one truncated) when KRDC client is connected to a VNC server (Krfb)
https://bugs.kde.org/show_bug.cgi?id=430339 Philipp Maierhöfer changed: What|Removed |Added CC||maiphi.pub...@gmx.net --- Comment #1 from Philipp Maierhöfer --- I can confirm this (on Tumbleweed and neon-user-20210506-0945 using X) and I'm in particular affected by the copy&paste problem. Copying a file in Dolphin and pasting it opens the "filename for clipboard content" dialogue (client to client copy not involving the server). Entering a file name creates a text file with the URL of the copied file instead of the file itself. Yes, there are two entries in Klipper: the file and its URL. But choosing the file explicitly doesn't work either, the URL always stays in the first place. Not only KDE applications are affected, but also e.g. LibreOffice (formulas can't be pasted anymore). And umlauts are pasted with the wrong encoding. I'm connecting to a Raspberry Pi 4 running Ubuntu 21.04 and Kfrb via VNC. Client keyboard layout is en_US, server de_DE. Other than in https://bugs.kde.org/show_bug.cgi?id=327311 and https://bugs.kde.org/show_bug.cgi?id=420177, the keyboard layout on the client is not changed when the connection is established. As soon as KRDC is disconnected, everything is back to normal. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436944] New: Krita Crashes when using tablet
https://bugs.kde.org/show_bug.cgi?id=436944 Bug ID: 436944 Summary: Krita Crashes when using tablet Product: krita Version: 4.4.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Tablets (tablet issues are only very rarely bugs in Krita!) Assignee: krita-bugs-n...@kde.org Reporter: karmagr...@gmail.com Target Milestone: --- SUMMARY Basically, using Krita with a pen makes it crash randomly. It is not the tablet, the tablet works fine, but it will crash with absolutely no warning and will give no information in the bug log, which you can see here. SESSION: 11 May 2021 11:31:21 -0700. Executing C:\Program Files (x86)\Steam\steamapps\common\Krita\krita\bin\krita.exe Krita Version: 4.4.3, Qt version compiled: 5.12.9, loaded: 5.12.9. Process ID: 16120 -- -- -- -- -- -- -- -- 11 May 2021 11:31:21 -0700: Style: fusion. Available styles: windowsvista, Windows, Fusion 11 May 2021 11:31:55 -0700: Created image "Unnamed", 1000 * 750 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 There isn't anything else here, it just stopped working. It happens randomly with no specific time. I'm sure tablet users send reports like this all the time, but this is not my tablets problem. Krita likes to crash randomly with tablets, this only happens with tablets, and it seems to happen more if I use the pressure function more. STEPS TO REPRODUCE 1. Use a tablet 2. 3. OBSERVED RESULT Crashes when I use a tablet EXPECTED RESULT Not crash when I use a tablet SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436786] Application loads, but crashes when trying to use a Huion H420 tablet to draw. Mouse drawing works, just whenever any tablet input is sensed, the whole application crashes The tab
https://bugs.kde.org/show_bug.cgi?id=436786 Karma changed: What|Removed |Added CC||karmagr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 390700] Unable to convert Fujifilm RAF RAW to DNG
https://bugs.kde.org/show_bug.cgi?id=390700 --- Comment #16 from Maik Qualmann --- Hi Gilles, Your test sample is from a Fuji S3Pro. But the Mosaic6x6 should be for the newer X-Trans sensors from Fuji, all cameras with an X in their name as X-T20 e.g. With a test sample of the X-T20, I still have a Bayer-Mosaic error. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430661] Two keyboard layout indicators are showing in the system tray
https://bugs.kde.org/show_bug.cgi?id=430661 --- Comment #20 from Andrey --- Git commit 718c1872f66a7ab82bc19b13d0dda218b1858181 by Andrey Butirsky. Committed on 11/05/2021 at 18:54. Pushed by butirsky into branch 'master'. feat: [Keyboard Layout applet] add spare layouts support For now, X11 only To support spare layouts in new Keyboard Layouts applet via existing DBus API, they are appended to the main ones and passed to the applet alongside in a row. When spare layout selected in applet's context menu, layout swapping logic takes place - the spare layout activates and placed in last position of the main layouts loop, preempting previous layout there in current keymap. That way the actual keymap can be dynamically modified from the menu, without reconfiguring in KCM. No DBus API/applet changes are needed currently. M +21 -2kcms/keyboard/keyboard_daemon.cpp https://invent.kde.org/plasma/plasma-desktop/commit/718c1872f66a7ab82bc19b13d0dda218b1858181 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 374638] Keyboard Shortcut to open search result in default search engine
https://bugs.kde.org/show_bug.cgi?id=374638 Alexander Lohnau changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436832] Fade in/out not working on rendered output
https://bugs.kde.org/show_bug.cgi?id=436832 --- Comment #3 from Herr Irrtum --- When preparing my melt test I started from scratch with two images. The bug does not occur when fading images! So. Important to reproduce this bug: *You have to use video clips.* Melt did produce exactly the same wrong result. Here's the output for what it's worth. ``` $ LC_ALL=C melt bugreport.mlt mlt_repository_init: failed to dlopen /usr/lib/mlt-7/libmltsdl.so (/usr/lib/mlt-7/libmltsdl.so: undefined symbol: XGetWindowAttributes) mlt_repository_init: failed to dlopen /usr/lib/mlt-7/libmltrtaudio.so (librtaudio.so.6: cannot open shared object file: No such file or directory) +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ |1=-10| |2= -5| |3= -2| |4= -1| |5= 0| |6= 1| |7= 2| |8= 5| |9= 10| +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ | H = back 1 minute, L = forward 1 minute | | h = previous frame, l = next frame | | g = start of clip, j = next clip, k = previous clip | |0 = restart, q = quit, space = play | +-+ [mp4 @ 0x7f850c200f40] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 0x7f850c200f40] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 0x7f850c200f40] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [mp4 @ 0x7f850c200f40] Encoder did not produce proper pts, making some up. Current Position:937 ``` -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436943] New: Monitor de Sistema no se ejecuta
https://bugs.kde.org/show_bug.cgi?id=436943 Bug ID: 436943 Summary: Monitor de Sistema no se ejecuta Product: plasma-systemmonitor Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: kirschcob...@riseup.net CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.4.0-73-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: Tras iniciar el sistema y llamar al Monitor de sistema, aparece una notificacion donde me indica que se ha presentado un error con el monitor del sistema. The crash can be reproduced every time. -- Backtrace: Application: Monitor del sistema (plasma-systemmonitor), signal: Segmentation fault [New LWP 1519] [New LWP 1520] [New LWP 1521] [New LWP 1529] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x55604c9bfc00) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7f81c99f8340 (LWP 1518))] Thread 5 (Thread 0x7f81a700 (LWP 1529)): [KCrash Handler] #4 _mesa_remove_dead_code_global (prog=prog@entry=0x7f81a4b1d090, mem_ctx=mem_ctx@entry=0x7f81a4b1d090) at ../src/mesa/program/prog_optimize.c:281 #5 0x7f81badbe574 in _mesa_optimize_program (program=program@entry=0x7f81a4b1d090, mem_ctx=mem_ctx@entry=0x7f81a4b1d090) at ../src/mesa/program/prog_optimize.c:1324 #6 0x7f81badbcd9c in get_mesa_program (shader=, shader_program=, ctx=) at ../src/mesa/program/ir_to_mesa.cpp:2957 #7 _mesa_ir_link_shader (ctx=, prog=) at ../src/mesa/program/ir_to_mesa.cpp:3046 #8 0x7f81badbd071 in _mesa_glsl_link_shader (ctx=ctx@entry=0x55604ba91910, prog=prog@entry=0x7f81a400a5f0) at ../src/mesa/program/ir_to_mesa.cpp:3117 #9 0x7f81bacc5ee2 in link_program (no_error=, shProg=, ctx=) at ../src/mesa/main/shaderapi.c:1311 #10 link_program_error (shProg=0x7f81a400a5f0, ctx=0x55604ba91910) at ../src/mesa/main/shaderapi.c:1419 #11 link_program_error (ctx=0x55604ba91910, shProg=0x7f81a400a5f0) at ../src/mesa/main/shaderapi.c:1417 #12 0x7f81cdade067 in QOpenGLShaderProgram::link() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f81c37c83ed in QSGDefaultRenderContext::compileShader(QSGMaterialShader*, QSGMaterial*, char const*, char const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f81c3762c8d in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7f81c376ee0e in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f81c3774a45 in QSGBatchRenderer::Renderer::renderBatches() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7f81c3774f9a in QSGBatchRenderer::Renderer::render() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7f81c3758b54 in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f81c3759023 in QSGRenderer::renderScene(unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f81c37c7c77 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7f81c3835509 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #22 0x7f81c37d57b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #23 0x7f81c37d9c47 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7f81cd0debec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f81cca52609 in start_thread (arg=) at pthread_create.c:477 #26 0x7f81ccd60293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f81c1a2a700 (LWP 1521)): #0 0x7f81cbc5a8ed in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f81cbc5c345 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f81cbc5dcbf in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f81cbc5e312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f81cbc5e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f81cd31effb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f81cd2c31eb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f81cd0dda52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f81ce993fa9 in ?? () from /lib/x86_64-
[korganizer] [Bug 436448] Can't see ok button in iCal creation dialog
https://bugs.kde.org/show_bug.cgi?id=436448 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |kdepim-runtime/commit/e3599 |kdepim-runtime/commit/d2390 |4dd41f61c28277769e63729f144 |ef45dcd2800ee6721a56b039331 |81ef5a80|fc512839 Resolution|--- |FIXED --- Comment #5 from gjditchfi...@acm.org --- Git commit d2390ef45dcd2800ee6721a56b039331fc512839 by Glen Ditchfield. Committed on 11/05/2021 at 18:44. Pushed by gditchfield into branch 'release/21.04'. Adjust the size of the iCal Calendar File properties dialog The dialog is too narrow and too tall: 390x1000, despite the geometry declaration in the UI file. Replacing the QTextEdit widgits with QLabels (like the other property dialogs) and setting a minimum size helps. Related: bug 435871 M +38 -39 resources/shared/singlefileresource/singlefileresourceconfigwidget_desktop.ui https://invent.kde.org/pim/kdepim-runtime/commit/d2390ef45dcd2800ee6721a56b039331fc512839 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 435871] KOrganizer's calendar settings dialog is too small by default
https://bugs.kde.org/show_bug.cgi?id=435871 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |kdepim-runtime/commit/e3599 |kdepim-runtime/commit/d2390 |4dd41f61c28277769e63729f144 |ef45dcd2800ee6721a56b039331 |81ef5a80|fc512839 --- Comment #2 from gjditchfi...@acm.org --- Git commit d2390ef45dcd2800ee6721a56b039331fc512839 by Glen Ditchfield. Committed on 11/05/2021 at 18:44. Pushed by gditchfield into branch 'release/21.04'. Adjust the size of the iCal Calendar File properties dialog The dialog is too narrow and too tall: 390x1000, despite the geometry declaration in the UI file. Replacing the QTextEdit widgits with QLabels (like the other property dialogs) and setting a minimum size helps. Related: bug 436448 M +38 -39 resources/shared/singlefileresource/singlefileresourceconfigwidget_desktop.ui https://invent.kde.org/pim/kdepim-runtime/commit/d2390ef45dcd2800ee6721a56b039331fc512839 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436918] Corners of input fields appear pixelated at higher DPI
https://bugs.kde.org/show_bug.cgi?id=436918 --- Comment #2 from Frank Steinmetzger --- I did try Wayland on the device, but it’s been some while ago and I went back to X11. I cleared the cache and now those corners are smth. 👍 I also have this glitch on another device which I think never had Wayland installed. I will try the cache method there later. I can’t remember ever having seen the shadow glitches from the ticket you linked. I would have noticed that very quickly. :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436942] New: Stretched (or compressed) audio track timeline visualization does not match audio
https://bugs.kde.org/show_bug.cgi?id=436942 Bug ID: 436942 Summary: Stretched (or compressed) audio track timeline visualization does not match audio Product: kdenlive Version: git-master Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. Import an audio or AV track 2. stretch it using Ctrl+Mouse with our without keeping the pitch OBSERVED RESULT The audio visualization in the track is not compressed or stretched, but cropped. This means that it does not match the audio at any given time any more. EXPECTED RESULT The audio visualization should match the audio and thus be compressed or stretched as well. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 20.04 with all updates applied KDE Plasma Version: KDE Frameworks Version: 5.21.4 Qt Version: ADDITIONAL INFORMATION Using Kdenlive Nightly 20.07.70. This also occured with Kdenlive 21.04. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436910] AdjustTimeDate changes the value of the LastModified field only during the calculation.
https://bugs.kde.org/show_bug.cgi?id=436910 --- Comment #5 from Maik Qualmann --- Git commit 047d78ab45b3edef87f5f843ac11b3d67355e6a4 by Maik Qualmann. Committed on 11/05/2021 at 18:40. Pushed by mqualmann into branch 'master'. try to fix file time under Windows M +1-14 core/libs/threadimageio/engine/dfileoperations.cpp https://invent.kde.org/graphics/digikam/commit/047d78ab45b3edef87f5f843ac11b3d67355e6a4 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436870] Document Catalog OpenAction not respected
https://bugs.kde.org/show_bug.cgi?id=436870 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432137] Generated window class match doesn't match
https://bugs.kde.org/show_bug.cgi?id=432137 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 436897] Use the END and HOME keys to jump through the results
https://bugs.kde.org/show_bug.cgi?id=436897 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org Keywords||usability Severity|normal |wishlist --- Comment #6 from Nate Graham --- +1 for using home and end to navigate the results list. Keep in mind that these keys are also used for text navigation, so they would have to only do this when the text field is not focused. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436899] System Settings crashes when closed
https://bugs.kde.org/show_bug.cgi?id=436899 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Nate Graham --- > systemsettings5 (5.5.5) > Distribution: Ubuntu 16.04.7 LTS You are using software that is five years old and is out of support. I strongly suggest upgrading. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436901] Wayland session Plasma crash bug on reboot
https://bugs.kde.org/show_bug.cgi?id=436901 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 421700 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged on a Wayland session after I've switched from main
https://bugs.kde.org/show_bug.cgi?id=421700 Nate Graham changed: What|Removed |Added CC||philip0muldo...@gmail.com --- Comment #15 from Nate Graham --- *** Bug 436901 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
