[kwin] [Bug 436813] "Present Windows" animation laggy on Wayland
https://bugs.kde.org/show_bug.cgi?id=436813 smit changed: What|Removed |Added CC||smit1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436813] New: "Present Windows" animation laggy on Wayland
https://bugs.kde.org/show_bug.cgi?id=436813 Bug ID: 436813 Summary: "Present Windows" animation laggy on Wayland Product: kwin Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: smit1...@gmail.com Target Milestone: --- SUMMARY On wayland "Present Windows" animation is laggy. Its not that bad but noticeable compared to how smooth it is on xorg. I tried setting all Latency options in Compositor settings but still no change. other animations like wobbly windows seems to work fine. On x11 session, running GPU heavy task in background and bunch of windows open, its still smooth compared to Wayland. This problem did not occur when I tested 5.21.0. But I'm now on 5.21.5 and did not checked wayland in between so cant say which version this bug affects from. STEPS TO REPRODUCE 1. Log into Wayland session. 2. Open more than 10 windows 3. toggle "Present Windows" OBSERVED RESULT laggy Animation EXPECTED RESULT smooth animation as x11 SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.5 Qt Version: 5.15.2+kde+r192-1 ADDITIONAL INFORMATION CPU: Intel i7-8565U (8) @ 4.600GHz iGPU: Intel UHD Graphics 620 dGPU: Radeon 520 Mobile (muxless, uses iGPU to render) tested on both GPUs by setting DRI_PRIME before `startplasma-wayland` command and getting same result -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 436812] New: Event not shown in KOrganizer, when my mail address is in in the ATTENDEE list
https://bugs.kde.org/show_bug.cgi?id=436812 Bug ID: 436812 Summary: Event not shown in KOrganizer, when my mail address is in in the ATTENDEE list Product: korganizer Version: 5.15.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-b...@kde.org Reporter: michael.hael...@online.de Target Milestone: --- Created attachment 138264 --> https://bugs.kde.org/attachment.cgi?id=138264&action=edit the two .ics files SUMMARY When I import an .ics event, it is not shown in KOrganizer, although 'successfully imported' STEPS TO REPRODUCE 1. Import 'englert.ics'. The reaction is 'successfully imported'. The event is not visible 2. Delete the ATTENDEE part with my mail address manually in the .ics file, resulting in 'englert.kurz.ics' 3. Import 'englert.kurz.ics'. The event is visible. OBSERVED RESULT With me as participant the event is not shown in KOrganizer. But the event is visible e.g. in Thunderbird Calendar, Nextcloud Calendar and in my smartphone Calendar, which all are synchronized with KOrganizer via Nextcloud/caldav. If I delete me as participant manually in the .ics file, the event is shown in KOrganizer (and again in all other synchronized calendars) EXPECTED RESULT Event should be visible also in KOrganizer SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I add the two .ics files zipped. 'englert.kurz.ics' is *after* import. Before I just deleted the lines from 'ATTENDEE;' to 'michael.hael...@munichways.com' -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436811] New: Closing dolphin while KNS3 window is loading crashes it.
https://bugs.kde.org/show_bug.cgi?id=436811 Bug ID: 436811 Summary: Closing dolphin while KNS3 window is loading crashes it. Product: dolphin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jodr...@live.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.07.70) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.0-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.21.80 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Installing new services. To trigger do : Open dolphin. Go to preferences > context menus > "Download New Services". As soon as the services window opens close dolphin then close the services window by hitting the "x" on the top right. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f0b857e729a in KNS3::QtQuickDialogWrapper::exec() () at /usr/lib64/libKF5NewStuff.so.5 #5 0x7f0b857c77fd in KNS3::Button::showDialog() () at /usr/lib64/libKF5NewStuff.so.5 #6 0x7f0b83aaec17 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffdd37a6040, r=0x56507e923c00, this=0x56507e924510) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate(QObject*, int, void**) (sender=0x56507e923c00, signal_index=9, argv=argv@entry=0x7ffdd37a6040) at kernel/qobject.cpp:3886 #8 0x7f0b83aa7f60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x56507e923c00, m=m@entry=0x7f0b84c214e0, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffdd37a6040) at kernel/qobject.cpp:3946 #9 0x7f0b847f56a2 in QAbstractButton::clicked(bool) (this=this@entry=0x56507e923c00, _t1=) at .moc/moc_qabstractbutton.cpp:308 #10 0x7f0b847f591a in QAbstractButtonPrivate::emitClicked() (this=0x56507e923eb0) at widgets/qabstractbutton.cpp:415 #11 0x7f0b847f7970 in QAbstractButtonPrivate::click() (this=0x56507e923eb0) at widgets/qabstractbutton.cpp:408 #12 0x7f0b847f7b91 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) (this=0x56507e923c00, e=0x7ffdd37a65c0) at widgets/qabstractbutton.cpp:1044 #13 0x7f0b84743b4e in QWidget::event(QEvent*) (this=0x56507e923c00, event=0x7ffdd37a65c0) at kernel/qwidget.cpp:9019 #14 0x7f0b84701aff in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x56507d912a00, receiver=receiver@entry=0x56507e923c00, e=e@entry=0x7ffdd37a65c0) at kernel/qapplication.cpp:3632 #15 0x7f0b847090cb in QApplication::notify(QObject*, QEvent*) (this=0x7ffdd37a62f0, receiver=0x56507e923c00, e=0x7ffdd37a65c0) at kernel/qapplication.cpp:3076 #16 0x7f0b83a7813a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x56507e923c00, event=0x7ffdd37a65c0) at kernel/qcoreapplication.cpp:1063 #17 0x7f0b84708103 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) (receiver=receiver@entry=0x56507e923c00, event=event@entry=0x7ffdd37a65c0, alienWidget=alienWidget@entry=0x56507e923c00, nativeWidget=0x56507e5a3520, buttonDown=, lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614 #18 0x7f0b8475d0dc in QWidgetWindow::handleMouseEvent(QMouseEvent*) (this=0x56507e95e050, event=0x7ffdd37a6880) at kernel/qwidgetwindow.cpp:683 #19 0x7f0b84760505 in QWidgetWindow::event(QEvent*) (this=0x56507e95e050, event=0x7ffdd37a6880) at kernel/qwidgetwindow.cpp:300 #20 0x7f0b84701aff in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x56507e95e050, e=0x7ffdd37a6880) at kernel/qapplication.cpp:3632 #21 0x7f0b83a7813a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x56507e95e050, event=0x7ffdd37a6880) at kernel/qcoreapplication.cpp:1063 #22 0x7f0b83facff3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) (e=0x56507e95e2b0) at kernel/qguiapplication.cpp:2282 #23 0x7f0b83f82c5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) (flags=...) at kernel/qwindowsysteminterface.cpp:1169 #24 0x7f0b810d6240 in userEventSourceDispatch(GSource*, GSourceFunc, gpointer) (source=source@entry=0x56507d91b8e0) at qeventdispatcher_glib.cpp:74 #25 0x7f0b815f78b7 in g_main_dispatch (context=0x56507d96a030) at ../glib/gmain.c:3337 #26 g_main_context_dispatch (context=0x56507d96a030) at ../glib/gmain.c:4055 #27 0x7f0b815f7c38 in g_main_context_iterate (context=context@entry=0x56507d96a030, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain
[systemsettings] [Bug 436784] mask/umast - lost option ssuspend
https://bugs.kde.org/show_bug.cgi?id=436784 --- Comment #2 from Mattai --- When the system is running normally it is a desktop. At certain times it is necessary to block sleep. Bareos and LTO work. Maybe plasma has some mechanism that will allow the script to switch energy saving mechanisms? W dniu 09.05.2021 o 01:31, David Edmundson pisze: > https://bugs.kde.org/show_bug.cgi?id=436784 > > David Edmundson changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||k...@davidedmundson.co.uk > > --- Comment #1 from David Edmundson --- > Why would one do that? > > Plasma queries. qdbus --system org.freedesktop.login1 /org/freedesktop/login1 > org.freedesktop.login1.Manager.CanSuspend > > once at startup and caches that value. Please confirm you think there is > actually a Plasma issue. > -- You are receiving this mail because: You are watching all bug changes.
[sweeper] [Bug 436810] New: KDEInit could not launch '/usr/bin/sweeper
https://bugs.kde.org/show_bug.cgi?id=436810 Bug ID: 436810 Summary: KDEInit could not launch '/usr/bin/sweeper Product: sweeper Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: iamarg...@zohomail.in Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: MX-19.4_KDE_x64 patito feo November 11 2020 , Linux 10(buster) (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.13 ADDITIONAL INFORMATION KDEInit could not launch '/usr/bin/sweeper -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436809] New: Changing "Window placement" crashes systemsettings.
https://bugs.kde.org/show_bug.cgi?id=436809 Bug ID: 436809 Summary: Changing "Window placement" crashes systemsettings. Product: systemsettings Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jodr...@live.com Target Milestone: --- Application: systemsettings5 (5.21.80) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.0-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.21.80 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Systemsettings > window management > window behavior > advanced. Here i changed the window placement from the default "Minimal Overlapping" to "Centered", systemsettings crashed after i hit apply. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x55a497208220 in QArrayData::shared_null () #5 0x7ff5a954d7e3 in QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x55a499703e30, registry=0x55a49757bba0, id=45, interface=..., version=1) at global/qwaylandclientextension.cpp:67 #6 0x7ff5a95364b2 in QtWaylandClient::QWaylandDisplay::registry_global (this=, id=45, interface=..., version=1) at qwaylanddisplay.cpp:397 #7 0x7ff5a9556ba6 in QtWayland::wl_registry::handle_global (data=0x55a49757f7f0, object=, name=45, interface=0x55a498cb0c60 "org_kde_kwin_blur_manager", version=1) at qwayland-wayland.cpp:94 #8 0x7ff5a8b4042d in ffi_call_unix64 () at ../src/x86/unix64.S:106 #9 0x7ff5a8b3c4f9 in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=) at ../src/x86/ffi64.c:669 #10 0x7ff5a94ac8fe in wl_closure_invoke (closure=closure@entry=0x55a498cb0b80, target=, target@entry=0x55a49757bba0, opcode=opcode@entry=0, data=, flags=) at src/connection.c:1018 #11 0x7ff5a94acfcb in dispatch_event (display=display@entry=0x55a49757fd20, queue=, queue=) at src/wayland-client.c:1452 #12 0x7ff5a94ad19c in dispatch_queue (queue=0x55a49757fdf0, display=0x55a49757fd20) at src/wayland-client.c:1598 #13 wl_display_dispatch_queue_pending (display=0x55a49757fd20, queue=0x55a49757fdf0) at src/wayland-client.c:1840 #14 0x7ff5a94ad1ec in wl_display_dispatch_pending (display=) at src/wayland-client.c:1903 #15 0x7ff5a9535df3 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55a49757f7e0) at qwaylanddisplay.cpp:222 #16 0x7ff5abcf6c50 in doActivate (sender=0x55a4975ec5a0, signal_index=3, argv=argv@entry=0x7ffdddce1eb0) at kernel/qobject.cpp:3898 #17 0x7ff5abceff60 in QMetaObject::activate (sender=sender@entry=0x55a4975ec5a0, m=m@entry=0x7ff5abfa5a60 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdddce1eb0) at kernel/qobject.cpp:3946 #18 0x7ff5abcfa0bf in QSocketNotifier::activated (this=this@entry=0x55a4975ec5a0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #19 0x7ff5abcfa8bb in QSocketNotifier::event (this=0x55a4975ec5a0, e=0x7ffdddce1fc0) at kernel/qsocketnotifier.cpp:302 #20 0x7ff5ac978aff in QApplicationPrivate::notify_helper (this=, receiver=0x55a4975ec5a0, e=0x7ffdddce1fc0) at kernel/qapplication.cpp:3632 #21 0x7ff5abcc013a in QCoreApplication::notifyInternal2 (receiver=0x55a4975ec5a0, event=0x7ffdddce1fc0) at kernel/qcoreapplication.cpp:1063 #22 0x7ff5abd188f5 in socketNotifierSourceDispatch (source=source@entry=0x55a49757da60) at kernel/qeventdispatcher_glib.cpp:107 #23 0x7ff5a97d38b7 in g_main_dispatch (context=0x55a4975cc2e0) at ../glib/gmain.c:3337 #24 g_main_context_dispatch (context=0x55a4975cc2e0) at ../glib/gmain.c:4055 #25 0x7ff5a97d3c38 in g_main_context_iterate (context=context@entry=0x55a4975cc2e0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #26 0x7ff5a97d3cef in g_main_context_iteration (context=0x55a4975cc2e0, may_block=may_block@entry=1) at ../glib/gmain.c:4196 #27 0x7ff5abd17d30 in QEventDispatcherGlib::processEvents (this=0x55a4975ec2e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7ff5abcbeb7b in QEventLoop::exec (this=this@entry=0x7ffdddce21d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7ff5abcc6db0 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x7ff5ac217a9c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #31 0x7ff5ac978a75 in QApplication::exec () at kernel/qapplication.cpp:2824 #32 0x55a4971f60da in main (argc=, argv=0x7ffdddce22f0) at /usr/src/debug/systemsettings5-5.21.80git.20210507T231548~1c7b26f0-ku.36.1.x86_64/app/main.cpp:208 [Inferior 1 (process 24544) detached] Possible duplicates by quer
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #418 from Dngrsone --- THe desktop wallpaper /might/ be hidden. But for me it is usually not. I have four Virtual desktops, each with its own set of shortcuts and widgets. Unfortunately, FIrefox, for some reason will always show the same icon, regardless, so when I am switching VIrtual desktops, I can't tell immediately /which/ FIrefox profile/instance is open on that desktop. It is faster to identify a wallpaper instead of looking at the patter of tiny shortcut icons. If I have different wallpapers, I immediately know "this is my photo editing desktop" or "this is my writing desktop". Is it stupid? Maybe to you. Is it extra work? It isn't work for me, though it would be nice if things worked out of the box instead of me having to do elaborate semi-effective workarounds for something that used to work just fine. What would be really nice if Desktop Cube worked for the virtual desktops too. Yes, it's so 1990's to have a process-burning graphic toy, but just like I prefer roses in my front yard, I like playing with the fancy toy. On Sat, May 8, 2021 at 12:58 PM leftcrane wrote: > https://bugs.kde.org/show_bug.cgi?id=341143 > > --- Comment #410 from leftcrane --- > > The background is a visual clue for where you are. > > It's a bad visual cue for the following reasons: > > - the desktop wallpaper might be hidden entirely by the windows. > - you have to manage wallpapers for each desktop - that's very a very time > consuming way of getting a "visual cue" > - you have to remember which desktop background symbolizes which desktop. > > I don't see the rationale at all here. The visual cue should provided by a > panel plasmoid. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 435543] In create dc in AS1 error is is coming
https://bugs.kde.org/show_bug.cgi?id=435543 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419575] Effects menu labels not aligned/messed up
https://bugs.kde.org/show_bug.cgi?id=419575 --- Comment #12 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 436119] Possible memory leak
https://bugs.kde.org/show_bug.cgi?id=436119 --- 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.
[lattedock] [Bug 435769] Latte-dock won't show up on Gnome 40
https://bugs.kde.org/show_bug.cgi?id=435769 --- Comment #7 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.
[kdenlive] [Bug 420821] Rendered video stalls while playing on Android
https://bugs.kde.org/show_bug.cgi?id=420821 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416418] The effect selection list can only be operated with the cursor and cannot be moved to the full top and last
https://bugs.kde.org/show_bug.cgi?id=416418 --- 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.
[Discover] [Bug 409389] Discover not updating
https://bugs.kde.org/show_bug.cgi?id=409389 --- 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 407033] Image Editor adds a XMP video tags.
https://bugs.kde.org/show_bug.cgi?id=407033 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Editing an image in the |Image Editor adds a XMP |Image Editor adds a XMP |video tags. |video date field. | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407033] Editing an image in the Image Editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407033 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.3.0 Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/10cdfe4 ||a5aedb3c38303fba8d3d8f1e72d ||6e2ead Resolution|DUPLICATE |FIXED --- Comment #3 from caulier.gil...@gmail.com --- Git commit 10cdfe4a5aedb3c38303fba8d3d8f1e72d6e2ead by Gilles Caulier. Committed on 09/05/2021 at 03:55. Pushed by cgilles into branch 'master'. Do not add Xmp video date-time stamp tags on non video files Related: bug 407034 FIXED-IN: 7.3.0 M +12 -4core/libs/metadataengine/engine/metaengine_item.cpp M +1-0core/libs/metadataengine/engine/metaengine_p.h https://invent.kde.org/graphics/digikam/commit/10cdfe4a5aedb3c38303fba8d3d8f1e72d6e2ead -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407034] Editing an image in the Image editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407034 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/10cdfe4 ||a5aedb3c38303fba8d3d8f1e72d ||6e2ead Status|REPORTED|RESOLVED Version Fixed In||7.3.0 --- Comment #13 from caulier.gil...@gmail.com --- Git commit 10cdfe4a5aedb3c38303fba8d3d8f1e72d6e2ead by Gilles Caulier. Committed on 09/05/2021 at 03:55. Pushed by cgilles into branch 'master'. Do not add Xmp video date-time stamp tags on non video files Related: bug 407033 FIXED-IN: 7.3.0 M +12 -4core/libs/metadataengine/engine/metaengine_item.cpp M +1-0core/libs/metadataengine/engine/metaengine_p.h https://invent.kde.org/graphics/digikam/commit/10cdfe4a5aedb3c38303fba8d3d8f1e72d6e2ead -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 158556] Manual hiding of panel
https://bugs.kde.org/show_bug.cgi?id=158556 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407034] Editing an image in the Image editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407034 --- Comment #12 from caulier.gil...@gmail.com --- Elementary : https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/metadataengine/engine/metaengine.cpp#L258 Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422755] Memory leak in plasmashell on opening activity manager sidebar repeatedly
https://bugs.kde.org/show_bug.cgi?id=422755 Alex changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Alex --- In Plasma 5.21.4, Qt 5.15.2, Frameworks 5.80, on a Wayland session in Fedora 34, I can successfully reproduce this leak with that bash script. Maybe this is a Qt bug, not sure, but since it does occur, I'll mark it as confirmed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407034] Editing an image in the Image editor adds a XMP video date field.
https://bugs.kde.org/show_bug.cgi?id=407034 --- Comment #11 from caulier.gil...@gmail.com --- Maik, I can reproduce the problem with an unit test. I written a DMetadata method to list changes to perform of file before to apply. This list Exif, Iptc and Xmp tags modified. https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/metadataengine/engine/metaengine.cpp#L258 The unit test load a file and call DMetadata::setImageDateTime() with current date. Finaly i list changes without to apply. https://invent.kde.org/graphics/digikam/-/blob/master/core/tests/metadataengine/dmetadatadiff_cli.cpp Look the result with a simple JPEG image: [gilles@localhost metadataengine]$ exiv2 -pa M104.jpg Exif.Image.ImageDescription Ascii 14 IDL TIFF file Exif.Image.Orientation Short 1 haut, gauche Exif.Image.XResolution Rational1 600 Exif.Image.YResolution Rational1 600 Exif.Image.ResolutionUnitShort 1 Pouce Exif.Image.Software Ascii 20 Adobe Photoshop 7.0 Exif.Image.DateTime Ascii 20 2003:09:25 17:30:51 Exif.Image.ExifTag Long1 180 Exif.Photo.ColorSpaceShort 1 Non calibré Exif.Photo.PixelXDimension Long1 11472 Exif.Photo.PixelYDimension Long1 6429 Exif.Thumbnail.Compression Short 1 JPEG (ancienne version) Exif.Thumbnail.XResolution Rational1 72 Exif.Thumbnail.YResolution Rational1 72 Exif.Thumbnail.ResolutionUnitShort 1 Pouce Exif.Thumbnail.JPEGInterchangeFormat Long1 318 Exif.Thumbnail.JPEGInterchangeFormatLength Long1 12385 Iptc.Application2.RecordVersion Short 1 2 Iptc.Application2.CaptionString 13 IDL TIFF file Xmp.xmpMM.DocumentID XmpText58 adobe:docid:photoshop:85e8fa57-a0f3-11d7-aea6-e74f76773090 Xmp.xmpMM.InstanceID XmpText41 uuid:af6d5080-ef91-11d7-96ef-9036d9cb0c44 Xmp.dc.description LangAlt 1 lang="x-default" IDL TIFF file ./dmetadatadiff_cli M104.jpg digikam.metaengine: Loading metadata with "Exiv2" backend from "M104.jpg" digikam.metaengine: List of changes to perform on: "M104.jpg" digikam.metaengine: New Exif tag Exif.Photo.DateTimeOriginal with value 2021:05:09 05:35:42 digikam.metaengine: New Exif tag Exif.Photo.DateTimeDigitized with value 2021:05:09 05:35:42 digikam.metaengine: New Iptc tag Iptc.Application2.DateCreated with value 2021-05-09 digikam.metaengine: New Iptc tag Iptc.Application2.TimeCreated with value 05:35:42+00:00 digikam.metaengine: New Iptc tag Iptc.Application2.DigitizationDate with value 2021-05-09 digikam.metaengine: New Iptc tag Iptc.Application2.DigitizationTime with value 05:35:42+00:00 digikam.metaengine: New Xmp tag Xmp.exif.DateTimeOriginal with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.photoshop.DateCreated with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.tiff.DateTime with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.xmp.CreateDate with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.xmp.MetadataDate with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.xmp.ModifyDate with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.video.DateTimeOriginal with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.video.DateUTC with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.video.ModificationDate with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.exif.DateTimeDigitized with value 2021-05-09T05:35:42 digikam.metaengine: New Xmp tag Xmp.video.DateTimeDigitized with value 2021-05-09T05:35:42 Look like XMP includes new video time stamp tags... Gilles -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436808] New: Okular crashes when closing it.
https://bugs.kde.org/show_bug.cgi?id=436808 Bug ID: 436808 Summary: Okular crashes when closing it. Product: okular Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jodr...@live.com Target Milestone: --- Application: okular (21.07.70) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.0-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.21.80 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Had a pdf file open in Okular, close it. No need to have a file open to trigger the crash though, just open and close okular to trigger the crash. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7efc114fd5e0 in QList::removeAll (this=0x55f435c18ea0, _t=@0x7ffdaa75cae0: 0x55f435f9acf0) at /usr/include/qt5/QtCore/qlist.h:948 #5 0x7efc114fd6d8 in KSelectActionPrivate::comboBoxDeleted (object=, this=) at /usr/src/debug/kwidgetsaddons-5.82.0git.20210508T124256~5c768976-ku.11.1.x86_64/src/kselectaction.cpp:471 #6 operator() (obj=, __closure=) at /usr/src/debug/kwidgetsaddons-5.82.0git.20210508T124256~5c768976-ku.11.1.x86_64/src/kselectaction.cpp:583 #7 QtPrivate::FunctorCall, QtPrivate::List, void, KSelectAction::createWidget(QWidget*):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #8 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #9 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl (which=, r=, ret=, a=, this_=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #10 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:436 #11 0x7efc101ccc17 in QtPrivate::QSlotObjectBase::call (a=0x7ffdaa75cbf0, r=0x55f435c097a0, this=0x55f435fc6a30) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x55f435f9acf0, signal_index=0, argv=argv@entry=0x7ffdaa75cbf0) at kernel/qobject.cpp:3886 #13 0x7efc101c5f60 in QMetaObject::activate (sender=sender@entry=0x55f435f9acf0, m=m@entry=0x7efc10472a00 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdaa75cbf0) at kernel/qobject.cpp:3946 #14 0x7efc101c600f in QObject::destroyed (this=this@entry=0x55f435f9acf0, _t1=, _t1@entry=0x55f435f9acf0) at .moc/moc_qobject.cpp:219 #15 0x7efc10e2a533 in QWidget::~QWidget (this=0x55f435f9acf0, __in_chrg=) at kernel/qwidget.cpp:1497 #16 0x7efc10ef1da9 in QComboBox::~QComboBox (this=0x55f435f9acf0, __in_chrg=) at widgets/qcombobox.cpp:1512 #17 0x7efc10e31ad7 in qDeleteAll::const_iterator> (end=..., begin=...) at ../../include/QtCore/../../src/corelib/tools/qalgorithms.h:320 #18 qDeleteAll > (c=...) at ../../include/QtCore/../../src/corelib/tools/qalgorithms.h:328 #19 QWidgetAction::~QWidgetAction (this=0x55f435c097a0, __in_chrg=) at kernel/qwidgetaction.cpp:126 #20 0x7efc114fec19 in KSelectAction::~KSelectAction (this=, this=) at /usr/src/debug/kwidgetsaddons-5.82.0git.20210508T124256~5c768976-ku.11.1.x86_64/src/kselectaction.cpp:81 #21 0x7efc101c00ae in QObjectPrivate::deleteChildren (this=this@entry=0x55f435b48560) at kernel/qobject.cpp:2104 #22 0x7efc10e2a276 in QWidget::~QWidget (this=0x55f435b48500, __in_chrg=) at kernel/qwidget.cpp:1522 #23 0x7efc09992169 in PageView::~PageView (this=, this=) at /usr/src/debug/okular-21.07.70git.20210507T234046~34b8c1e72-ku.13.1.x86_64/part/pageview.cpp:530 #24 0x7efc101c00ae in QObjectPrivate::deleteChildren (this=this@entry=0x55f435b0e990) at kernel/qobject.cpp:2104 #25 0x7efc10e2a276 in QWidget::~QWidget (this=0x55f435b0e100, __in_chrg=) at kernel/qwidget.cpp:1522 #26 0x7efc10e2a5c9 in QWidget::~QWidget (this=0x55f435b0e100, __in_chrg=) at kernel/qwidget.cpp:1546 #27 0x7efc101c00ae in QObjectPrivate::deleteChildren (this=this@entry=0x55f435953850) at kernel/qobject.cpp:2104 #28 0x7efc10e2a276 in QWidget::~QWidget (this=0x55f43591e7e0, __in_chrg=) at kernel/qwidget.cpp:1522 #29 0x7efc10f9ecb9 in QSplitter::~QSplitter (this=0x55f43591e7e0, __in_chrg=) at widgets/qsplitter.cpp:979 #30 0x7efc101c00ae in QObjectPrivate::deleteChildren (this=this@entry=0x55f4359504b0) at kernel/qobject.cpp:2104 #31 0x7efc10e2a276 in QWidget::~QWidget (this=0x55f43591c8e0, __in_chrg=) at kernel/qwidget.cpp:1522 #32 0x7efc099c7ea9 in Sidebar::~Sidebar (this=, this=) at /usr/src/debug/okular-21.07.70git.20210507T234046~34b8c1e72-ku.13.1.x86_64/part/sidebar.cpp:88 #33 0x7efc101c00ae in QObjectPr
[plasma-systemmonitor] [Bug 436807] New: Getting a crash pop-up after closing System Monitor sometimes
https://bugs.kde.org/show_bug.cgi?id=436807 Bug ID: 436807 Summary: Getting a crash pop-up after closing System Monitor sometimes Product: plasma-systemmonitor Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: domy...@gmail.com 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.11.18-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: If I open System Monitor to check statuses and want to close it, I'm getting a crash pop-up after closing System Monitor. This is happening sometimes, maybe 1 of 10 cases. The crash can be reproduced sometimes. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x7f7e0a1fd06f in QQuickItem::setVisible(bool) () from /lib64/libQt5Quick.so.5 #5 0x7f7e0311586a in ToolBarLayoutDelegate::ensureItemVisibility() () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #6 0x7f7e1cafd4b0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7f7e0a1ff8cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib64/libQt5Quick.so.5 #8 0x7f7e0a203119 in QQuickItem::setParentItem(QQuickItem*) () from /lib64/libQt5Quick.so.5 #9 0x7f7e0a1f7a5a in QQuickItem::~QQuickItem() () from /lib64/libQt5Quick.so.5 #10 0x7f7e02b6b242 in QQmlPrivate::QQmlElement::~QQmlElement() () from /usr/lib64/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #11 0x7f7e031165fa in ToolBarLayoutDelegate::~ToolBarLayoutDelegate() () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #12 0x7f7e0311669a in std::_Hashtable > >, std::allocator > > >, std::__detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_erase(unsigned long, std::__detail::_Hash_node_base*, std::__detail::_Hash_node > >, false>*) () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #13 0x7f7e03116a40 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #14 0x7f7e1cafd4b0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7f7e1caf7aa3 in QObject::destroyed(QObject*) () from /lib64/libQt5Core.so.5 #16 0x7f7e1cafa10a in QObject::~QObject() () from /lib64/libQt5Core.so.5 #17 0x7f7e02b6c89f in QQmlPrivate::QQmlElement::~QQmlElement() () from /usr/lib64/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #18 0x7f7e1caf3eda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #19 0x7f7e1cafa184 in QObject::~QObject() () from /lib64/libQt5Core.so.5 #20 0x7f7e000fb9d9 in QQmlPrivate::QQmlElement::~QQmlElement() () from /usr/lib64/qt5/qml/org/kde/ksysguard/faces/libFacesPlugin.so #21 0x7f7e1caf3eda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #22 0x7f7e1cafa184 in QObject::~QObject() () from /lib64/libQt5Core.so.5 #23 0x7f7e02fcffdd in KSysGuard::SensorFaceController::~SensorFaceController() () from /lib64/libKSysGuardSensorFaces.so.1 #24 0x7f7e1caf3eda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #25 0x7f7e1cafa184 in QObject::~QObject() () from /lib64/libQt5Core.so.5 #26 0x562f558a3999 in main () [Inferior 1 (process 10640) detached] Possible duplicates by query: bug 435427, bug 432084, bug 431077, bug 429973, bug 429504. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 436806] New: Screen locked looping notification sound
https://bugs.kde.org/show_bug.cgi?id=436806 Bug ID: 436806 Summary: Screen locked looping notification sound Product: frameworks-knotifications Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: metal...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY If I configure a notification sound for the Screen Saver's "Screen locked" event, putting the system to sleep sometimes behaves as expected: it plays the sound once, followed by the system going to sleep. Other times, it starts looping/repeating the sound continuously until the system goes to sleep. When this looping/repeating sound is 'stuck' it can be very loud, with no way to stop it, until the system finishes going to sleep. STEPS TO REPRODUCE 1. System Settings->Notifications->Configure->Screen Saver->Configure Events->Screen locked->Play a sound. I chose /usr/share/sounds/Oxygen-Im-Highlight-Msg.ogg, but I assume any short/loud sound would suffice. 2. Put the system to sleep 3. If the behavior is as expected (sound plays once), try waking up the system & trying again. The bug is sporadic (it may happen i.e. 1 out of 4 times when putting the system to sleep). OBSERVED RESULT Sometimes the sound plays once, as expected. Other times, the sound gets stuck in a buggy-sounding loop, that continues repeating until the system finishes going to sleep (usually a second or two, but can be as long as 10 seconds). EXPECTED RESULT The sound should only play once, not get stuck in a repeating loop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.5 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.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 Matti Klock changed: What|Removed |Added CC|matti-kdeb...@twonth.com| -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 428665] subscribing and syncing to remote dynamic ics web calendar not possible
https://bugs.kde.org/show_bug.cgi?id=428665 --- Comment #5 from je-vv@e.email --- (In reply to James Cain from comment #4) > As mentioned, on the second tab of the folder properties dialogue, one can > specify the update interval. It remains to be seem on my system if this is > working, however I can confirm that manually updating the folder DOES work. > Not ideal, but perhaps a workable solution in the interim until this bug > gets fixed / closed. I've tried both, adding an ical file, and adding an ical directory. In both cases, after created, and looking at its folder properties, on the 2nd tab, called "Retrieval", it's "Synchronize when selecting this folder" is ALWAYS un-selected and grayed out (not possible to select it), and its "Automatically synchronize after" is ALWAYS with NEVER selection, and also grayed out (not possible to change selection). So no, that is not working unfortunately. Moreover, as mentioned before, there should be an option to add a remote ics/ical calendar, and to be able to keep it synchronized automatically. That doesn't exist at all, one can add the URL to the file or the directory calendars, but those are clearly meant for local to the computer calendars... What saddens me the most, is that it seems devs don't care about this functionality. Korganizer has years being available, and it's really sad this is still unsupported, :( I don't even remember Thunderbird not supporting this ever, and even icsdroid (icsx5) is there for Android supporting this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435747] Truncated panel button tooltip
https://bugs.kde.org/show_bug.cgi?id=435747 --- Comment #2 from Dan Dascalescu --- Still seeing this in 5.21.5 / Qt 5.15.2. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 --- Comment #1 from Pozsgay Máté --- Might be related to: https://invent.kde.org/multimedia/kdenlive/-/issues/1053 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #417 from leftcrane --- Windows is better, objectively, because it has a fully featured virtual desktop switcher. Now that WOULD be useful to have on KDE, as opposed to wasting resources on confusing gimmicks like per-desktop wallpapers. Sometimes removing features makes sense. Only adding features and options, especially when you have a million options already, is unsustainable. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436805] New: Add clip to project option is ignored in video stabilize window
https://bugs.kde.org/show_bug.cgi?id=436805 Bug ID: 436805 Summary: Add clip to project option is ignored in video stabilize window Product: kdenlive Version: 21.04.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY "Add clip to project" option is ignored in video stabilizer dialog. STEPS TO REPRODUCE 1. Import a clip 2. Open the stabilize video window 3. Uncheck the "Add clip to project" checkbox OBSERVED RESULT After the stabilization is completed the stabilized mlt is added to project bin EXPECTED RESULT The mlt shouldn't added to project if the corresponding checkbox is not checked. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04.2 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #30 from Mircea Kitsune --- (In reply to Tomasz Paweł Gajc from comment #29) I hear Plasma 5.22 comes with some improvements for Wayland. No idea if that includes this issue, perhaps let us know if you notice a difference after its update. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] New: Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 Bug ID: 436804 Summary: Proxy clips are not properly generated from stabilized vidoes Product: kdenlive Version: 21.04.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY Multiple issues of proxy clips generated from stabilized clips. STEPS TO REPRODUCE 1. Import a clip 2. Stabilize the clip 3. Add the stabilized mlt to the clip bin (or let the kdenlive do it for you) 4. Generate a proxy clip from the stabilized clip OBSERVED RESULT The proxy clip is generated, however the quality is much worst than expected, blank strips are added to te top and bottom, and the length of the proxy clip is also incorrect (about the double of the original). EXPECTED RESULT The proxy clip shouldn't have the two black strips, this might improve the quality as well, the length of the proxy clip should be the same as the original. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04.2 KDE Plasma Version: KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 435869] Logout cancelled by ... without asking.
https://bugs.kde.org/show_bug.cgi?id=435869 --- Comment #12 from leftcrane --- Not sure what resolved downstream means here. The bug hasn't been resolved anywhere, downstream or upstream. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436803] New: Weird flickering when list of apps is refreshed
https://bugs.kde.org/show_bug.cgi?id=436803 Bug ID: 436803 Summary: Weird flickering when list of apps is refreshed Product: plasma-systemmonitor Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: med.medin.2...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 138262 --> https://bugs.kde.org/attachment.cgi?id=138262&action=edit Weird flickering when list of apps is refreshed This happens only when I select an element in the list of apps, See attached video for more info. NB : this problem is not present with KSysguard. Operating System: Manjaro Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.4.112-1-MANJARO OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 435869] Logout cancelled by ... without asking.
https://bugs.kde.org/show_bug.cgi?id=435869 --- Comment #11 from leftcrane --- Can the decision of whether to cancel the logout be at least given to the user? Here's a sensible dialog for this situation, and that's how OTHER platforms handle it: > "App so and so is preventing logout, What do you want to do? > [Retry - (timer)] [Abort logout] That will fix the problem in a safe way. Allowing programs to "cancel" logout at will is actually the most dangerous approach in practice, because it encourages technically illiterate or frustrated users to solve the problem with a hard shutdown. If the software won't comply, they power button will, so that's what the user will do. I'd appreciate if this bug were reopened. Allowing random apps to cancel logout is unheard of on other platforms, and for good reason. It would be a considered a major bug on Windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392185] Informational tooltips are shifting a little bit to the left/top side when hovering over task in left/top sided Panel one more time
https://bugs.kde.org/show_bug.cgi?id=392185 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Nate Graham --- It must have been, since I'm using a left panel and haven't seen it in years. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 436374] KDE Connect run command plugin on windows problems with quote
https://bugs.kde.org/show_bug.cgi?id=436374 --- Comment #1 from brute4s99 --- Thanks for reporting the bug. I just pushed a patch to fix this. It's available at https://invent.kde.org/network/kdeconnect-kde/commit/3b7d51dc804a075af7eef26f9b415f05187c66b4 The nightly build doesn't work right now, but if you want to test if it works fine for you now, go ahead and install the package made on my machine hosted here : https://baadal.my.to/s/BPBZ6NRNig9HrQR Alternatively, ping me on @PiyushAggarwal on Telegram. I'll keep you in the loop and let you know when the nightly is good again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435528] Specific filename for clip prevented editing the clip without warning
https://bugs.kde.org/show_bug.cgi?id=435528 --- Comment #4 from gerrytre...@gmail.com --- The problem seems to be the question mark. That's what I experienced today. It wouldn't even let me delete the clip I had -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436802] Kdenlive master, and 21.04 crash when trying to run stabilize video
https://bugs.kde.org/show_bug.cgi?id=436802 --- Comment #2 from Lance Rissman --- This is the windbg output from 20.12.3 that is working. // Fetching effect: "vidstab" Asset "vidstab" found in the repository. Description: "Stabilize Video (for wiggly/rolling video) (vidstab)" XML parsing of "vidstab" . found 16 parameters QLocale: Default value is QVariant(double, 8) parsed: "8" = = SET EFFECT PARAM: "accuracy" = 8 QLocale: Default value is QVariant(double, 4) parsed: "4" = = SET EFFECT PARAM: "shakiness" = 4 QLocale: Default value is QVariant(double, 6) parsed: "6" = = SET EFFECT PARAM: "stepsize" = 6 QLocale: Default value is QVariant(double, 0.3) parsed: "0.3" = = SET EFFECT PARAM: "mincontrast" = 0.3 QLocale: Default value is QVariant(double, 10) parsed: "10" = = SET EFFECT PARAM: "smoothing" = 10 QLocale: Default value is QVariant(double, -1) parsed: "-1" = = SET EFFECT PARAM: "maxshift" = -1 QLocale: Default value is QVariant(double, -1) parsed: "-1" = = SET EFFECT PARAM: "maxangle" = -1 QLocale: Default value is QVariant(QString, "0") parsed: "0" = = SET EFFECT PARAM: "crop" = 0 QLocale: Default value is QVariant(double, 0) parsed: "0" = = SET EFFECT PARAM: "zoom" = 0 QLocale: Default value is QVariant(double, 1) parsed: "1" = = SET EFFECT PARAM: "optzoom" = 1 QLocale: Default value is QVariant(double, 0.25) parsed: "0.25" = = SET EFFECT PARAM: "zoomspeed" = 0.25 QLocale: Default value is QVariant(double, 0.8) parsed: "0.8" = = SET EFFECT PARAM: "sharpen" = 0.8 QLocale: Default value is QVariant(double, 0) parsed: "0" = = SET EFFECT PARAM: "show" = 0 QLocale: Default value is QVariant(double, 0) parsed: "0" = = SET EFFECT PARAM: "tripod" = 0 WARNING: Unknown type : "fixed" WARNING: Unknown type : "fixed" QLocale: Default value is QVariant(double, 1) parsed: "1" = = SET EFFECT PARAM: "reload" = 1 WARNING: Unknown type : "fixed" WARNING: Unknown type : "fixed" QLocale: Default value is QVariant(double, 0) parsed: "0" = = SET EFFECT PARAM: "analyse" = 0 END parsing of "vidstab" . Number of found parameters 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 QLocale: Could not load double parameter "" = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 QLocale: Could not load double parameter "" = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 QLocale: Could not load double parameter "" = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 QLocale: Could not load double parameter "" = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 QLocale: Could not load double parameter "" = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 QLocale: Could not load double parameter "" = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 QLocale: Could not load double parameter "" = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0x0)) 14 = Requested rowCount QModelIndex(-1,-1,0x0,QObject(0
[systemsettings] [Bug 433827] QWidgets-based KCMs are missing their titles when activated as default item in category
https://bugs.kde.org/show_bug.cgi?id=433827 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- Should be fixed by: https://invent.kde.org/plasma/systemsettings/-/commit/8b261e7ca6242c7fe541fa3813d89e6c245a7be3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436784] mask/umast - lost option ssuspend
https://bugs.kde.org/show_bug.cgi?id=436784 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Why would one do that? Plasma queries. qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanSuspend once at startup and caches that value. Please confirm you think there is actually a Plasma issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436802] Kdenlive master, and 21.04 crash when trying to run stabilize video
https://bugs.kde.org/show_bug.cgi?id=436802 --- Comment #1 from Lance Rissman --- Ran windbg and this is the lines related to the crash: // Fetching effect: "vidstab" (2158.1ad4): Unknown exception - code 20474343 (first chance) (2158.1ad4): Unknown exception - code 20474343 (first chance) QEventDispatcherWin32::wakeUp: Failed to post a message (Invalid window handle.) -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 435851] Fix the layout of the Plasma overview page
https://bugs.kde.org/show_bug.cgi?id=435851 Ricardo J. Barberis changed: What|Removed |Added CC||ricardo.barbe...@gmail.com --- Comment #1 from Ricardo J. Barberis --- This also happens in Opera 76 beta and Falkon 3.1.0, but only for "System Tray" and "Notifications", "Discover" looks fine. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 436798] kaffeine-2.0.18 w/ KF5WindowSystem built without <=5.62 deprecated API: src/main.cpp:183:32: error: cannot convert ‘QPointer’ to ‘QWindow*’
https://bugs.kde.org/show_bug.cgi?id=436798 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/multimedia/kaffeine/-/merge_requests/2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #9 from David Edmundson --- There is a possibility this is fixed by: https://codereview.qt-project.org/c/qt/qtwayland/+/347774 If we were hitting this it would have the symptoms listed. Lets assume it's a fix until we hear otherwise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #416 from abrah...@acm.org --- This argument has been going on for six years!! Sad to say, the developers brought it on themselves by removing a feature that many users liked and relied on heavily. I was one of them. Unless the development team has new members, I'm afraid we're stuck with this. It's like the Catholics and the Protestants in the Middle Ages! An interesting alternative is the virtual desktops of Windows 10. The way that's designed is quite different from both the old KDE and the current KDE. I haven't decided which one I prefer. I definitely dislike activities, though, and never use them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399499] KWin crashes in makeInterleavedArrays
https://bugs.kde.org/show_bug.cgi?id=399499 David Edmundson changed: What|Removed |Added Priority|VHI |NOR -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 David Edmundson changed: What|Removed |Added Priority|VHI |NOR -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422786] Global Menu requires refocus to display properly
https://bugs.kde.org/show_bug.cgi?id=422786 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #45 from David Edmundson --- Can't reproduce any issues. Please attach a log of running `dbus-monitor --pcap ` and focussing the inkscape window As well as output from plasmashell --replace and/or verified steps that work from a clean VM image. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update
https://bugs.kde.org/show_bug.cgi?id=407058 David Edmundson changed: What|Removed |Added Priority|VHI |NOR CC||k...@davidedmundson.co.uk Keywords|regression | --- Comment #43 from David Edmundson --- This bug seems to be a mix of two things. It not working in wayland, which was to be expected at the time And it not working in X11 which were describing user setup issues. Neither are very high regressions. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436738] docdata duplicated each time pdf is edited
https://bugs.kde.org/show_bug.cgi?id=436738 --- Comment #7 from David Hurka --- This is the content of my 13572671.pgfplots.pdf.xml : (If formatting doesn’t break here) [...] So it is not just (filesize,filename), but actually stores the full file path. When I overwrite one instance of (filesize,path), that means that there can’t be another instance of (filesize,path) somewhere in the system. Except when the user actively restores an old version of the file. Is the url attribute ignored when docdata files for an opened document are searched? In that case it is true that there may be another file which fits this docdata file. The workflow originally addressed by this bug report was that Okular automatically reloads the document, and so actively creates these duplicates. Now we are talking a bit more general. Should we split this into two bug reports? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 433364] [systemd startup] Can't unlock session with loginctl
https://bugs.kde.org/show_bug.cgi?id=433364 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/35 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436802] New: Kdenlive master, and 21.04 crash when trying to run stabilize video
https://bugs.kde.org/show_bug.cgi?id=436802 Bug ID: 436802 Summary: Kdenlive master, and 21.04 crash when trying to run stabilize video Product: kdenlive Version: git-master Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: lriss...@probus.ca Target Milestone: --- SUMMARY Program crash when selecting "stabilize video" on a clip, STEPS TO REPRODUCE 1. Start kdenlive 2. Add a video clip to the project bin 3. Right-click on video clip, choose clip jobs->stabilize (vidstab) Re-produceable with master complied using craft Re-produceable with 21.04 Works on 20.12.03 OBSERVED RESULT Kdenlive will hang and eventually Windows will ask if you want to close the program. EXPECTED RESULT Dialog for stabilization will appear and work. SOFTWARE/OS VERSIONS Windows: Windows 10 Pro KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436801] New: Transitions and wipe not rendering in export
https://bugs.kde.org/show_bug.cgi?id=436801 Bug ID: 436801 Summary: Transitions and wipe not rendering in export Product: kdenlive Version: 21.04.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: tra...@destinationgreatlakes.us Target Milestone: --- SUMMARY When previewing a video timeline wipes between clips and fade in and out on both audio and video clips work as expected. When the video is rendered, the finished video file does not have the wipes, or fades. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.12.2-153-tkg-bmq-zen2 Kernel (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436066] Per-app color schemes
https://bugs.kde.org/show_bug.cgi?id=436066 --- Comment #6 from leftcrane --- I think it's actually more logical than cluttering up the application interface with dozens of color schemes. If you could specify the color scheme at launch in the environment variable, you could manage it via kmenueditor for all applications. Still think this is a bad idea? I think it'd be a major UI improvement - the only question is the difficulty of implementation. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436066] Per-app color schemes
https://bugs.kde.org/show_bug.cgi?id=436066 --- Comment #5 from leftcrane --- It's not a UI issue. It's about the ability to launch qt applications with a custom color scheme (just as you can launch them with a custom theme), via an environment variable. GTK has this functionality, via variants. It could look like this "QT_QPA_PLATFORMTHEME=Breeze:ColorScheme [application]" As for the UI, there is a perfectly logical place for stuff like titlebar color or app "theme:color" - the much neglected kde menu editor. (Currently, the titlebar color can be set via a combination of color scheme editor and window rule, which is a prohibitively convoluted UI solution.) -- You are receiving this mail because: You are watching all bug changes.
[calligracommon] [Bug 436800] New: Huge sidebars waste too much space, make multitasking impractical. Suggestion to move the tools into the toolbar and menus.
https://bugs.kde.org/show_bug.cgi?id=436800 Bug ID: 436800 Summary: Huge sidebars waste too much space, make multitasking impractical. Suggestion to move the tools into the toolbar and menus. Product: calligracommon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: usability Assignee: calligra-bugs-n...@kde.org Reporter: leftcr...@tutanota.com Target Milestone: --- This is a general UI problem that affects the entire suite. The sidebars take up anywhere from a quarter to a third of the window area on normal screens. This means you can't tile a calligra window with anything else and expect to be able to see the content. The worst thing is that most of the space in the sidebars is completely empty. Most of the tools are tiny buttons that could fit into a two-row toolbar - the gargantuan sidebars give them five times the space they actually require. I've never seen software where whitespace crowds out content to this degree. I would urge Calligra developers to adopt the kind of interface seen on other office suites and move the tools out of the sidebars. Maybe just put them all in the menubar, at least for starters, so users have at least some alternative to the sidebars. It's sad to see such an impressive project completely crippled - at least for me, though I suspect I'm not the only one - by one strange UI decision. Otherwise, a native office suite like Calligra could be a great asset for the desktop as a whole. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #415 from leftcrane --- Then hire a developer who will do whatever you without any questions. There are no hired hands here. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436710] Playing of Flash-free ("plain") Rich Media annotations
https://bugs.kde.org/show_bug.cgi?id=436710 --- Comment #6 from Michal Vlasák --- (In reply to Albert Astals Cid from comment #3) > > It seems that I can't create new merge request normally. > > You're going to need to be a bit more verbose on what's the problem you're > having ;) Sorry for being unclear. I don't see the button normally used for creating merge requests. I thought it was intentionally limited only to orginization members. (The difference between poppler/okular repositories is visible in files attached above). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436710] Playing of Flash-free ("plain") Rich Media annotations
https://bugs.kde.org/show_bug.cgi?id=436710 --- Comment #5 from Michal Vlasák --- Created attachment 138261 --> https://bugs.kde.org/attachment.cgi?id=138261&action=edit okular merge requests -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436710] Playing of Flash-free ("plain") Rich Media annotations
https://bugs.kde.org/show_bug.cgi?id=436710 --- Comment #4 from Michal Vlasák --- Created attachment 138260 --> https://bugs.kde.org/attachment.cgi?id=138260&action=edit poppler merge requests -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436758] Question to date-format of import images
https://bugs.kde.org/show_bug.cgi?id=436758 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||7.3.0 Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/1329f9c ||a2bd353793487b88b1a0629820f ||41ff32 --- Comment #1 from Maik Qualmann --- Git commit 1329f9ca2bd353793487b88b1a0629820f41ff32 by Maik Qualmann. Committed on 08/05/2021 at 21:32. Pushed by mqualmann into branch 'master'. check if auto create date albums are activated FIXED-IN: 7.3.0 M +2-2NEWS M +2-1core/utilities/import/main/importui.cpp https://invent.kde.org/graphics/digikam/commit/1329f9ca2bd353793487b88b1a0629820f41ff32 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 436799] New: Ability to search attachments
https://bugs.kde.org/show_bug.cgi?id=436799 Bug ID: 436799 Summary: Ability to search attachments Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: leftcr...@tutanota.com Target Milestone: --- This is one thing I miss from Gmail. KDE has an indexer but it won't index or search attachments in Kmail. If it could be integrated into Kmail, this would be one of the most useful applications of baloo. I have lots of emails that are easily identifiable only by attachments. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 436798] New: kaffeine-2.0.18 w/ KF5WindowSystem built without <=5.62 deprecated API: src/main.cpp:183:32: error: cannot convert ‘QPointer’ to ‘QWindow*’
https://bugs.kde.org/show_bug.cgi?id=436798 Bug ID: 436798 Summary: kaffeine-2.0.18 w/ KF5WindowSystem built without <=5.62 deprecated API: src/main.cpp:183:32: error: cannot convert ‘QPointer’ to ‘QWindow*’ Product: kaffeine Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mchehab+hua...@kernel.org Reporter: ast...@gentoo.org Target Milestone: --- Created attachment 138259 --> https://bugs.kde.org/attachment.cgi?id=138259&action=edit build.log SUMMARY kaffeine is using deprecated API that will be removed with KF6. It would be nice to already port away from it. STEPS TO REPRODUCE 1. Build KF5WindowSystem with -DKWINDOWSYSTEM_NO_WIDGETS 2. This implies EXCLUDE_DEPRECATED_BEFORE_AND_AT "5.62.0" 3. Try to build kaffeine against that library OBSERVED RESULT > kaffeine-2.0.18/src/main.cpp:183:32: error: cannot convert > ‘QPointer’ to ‘QWindow*’ > 183 | KStartupInfo::setNewStartupId(mainWindow, KStartupInfo::startupId()); > |^~ > || > |QPointer > In file included from /usr/include/KF5/KWindowSystem/KStartupInfo:1, > from kaffeine-2.0.18/work/kaffeine-2.0.18/src/main.cpp:25: > /usr/include/KF5/KWindowSystem/kstartupinfo.h:93:42: note: initializing > argument 1 of ‘static void KStartupInfo::setNewStartupId(QWindow*, const > QByteArray&)’ >93 | static void setNewStartupId(QWindow *window, const QByteArray > &startup_id); > | ~^~ SOFTWARE/OS VERSIONS Operating System: Gentoo 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.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #414 from Yannick --- @leftcrane Let's say you're up to buy a house property you order from a professional home builder that used to to many different and specific decorations in each room. You ask him to have your living room in white, your bathroom in blue, your daughter room in pink, etc... And the guy tells you this is nonsense and you should have the same paint/wallpaper color in every single room of your house. This is exactly what you are saying to us, to the users, which is very annoying and obviously your behavior is dumb. A user and a buyer will use/buy the product that meets their requirements. Innovation can generate new needs and drop others, but removing a feature that was still being used by users should never happen, unless there is something better in replacement (which can meet their needs and requirements). Activities and VDs have different usage goals. Not every users adhere to activities, and may prefer to use VDs instead. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371105] Panel tooltips don't show content
https://bugs.kde.org/show_bug.cgi?id=371105 Cornelius Schumacher changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Cornelius Schumacher --- After several updates of the underlying OS and Plasma I don't see the issue anymore. I'll close the report now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436795] databse from uninstalled version of digikam is unhelpfully persistant
https://bugs.kde.org/show_bug.cgi?id=436795 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- No, we will not delete the database when digiKam is uninstalled. Other users don't want to lose the database when they upgrade to a newer version. You haven't written anything about your system. Windows, Linux or MacOS? Which database type do you use, SQLite or MySQL internal or external? May I also ask why you want to use an old digiKam version with known bugs and not a newer version? Maik -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436743] Folder sizes(by file size) stop after 121 entries in details mode
https://bugs.kde.org/show_bug.cgi?id=436743 --- Comment #4 from ehrich.we...@gmail.com --- (sorry for the second comment, I didn't see the first had posted at all) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436743] Folder sizes(by file size) stop after 121 entries in details mode
https://bugs.kde.org/show_bug.cgi?id=436743 --- Comment #3 from ehrich.we...@gmail.com --- I found a workaround but this should still be considered a bug. If I select to show "folder sizes of contents" up to 5 levels deep, Dolphin seems to operate as one would expect but if I select to show 6 or more levels, it will eat all of my cpu and doesn't want to finish, even after hours. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436797] New: Resize mouse icon visible when it should not be.
https://bugs.kde.org/show_bug.cgi?id=436797 Bug ID: 436797 Summary: Resize mouse icon visible when it should not be. Product: dolphin Version: 21.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: naumenko.dmit...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 138258 --> https://bugs.kde.org/attachment.cgi?id=138258&action=edit Video demonstrating the issue. SUMMARY For whatever reason, sometimes(this does not always happen, but I cannot pinpoint what exactly causes it, I would say it happens randomly 50% of the time), after hovering over the divider between the file view and the left portion of the application, the resize mouse icon will stick around when it should not. This causes me to not be able to click anything. I have attached a short video file demonstrating the issue. STEPS TO REPRODUCE 1. Hover over the divider between the file view and left portion and then move the mouse left. OBSERVED RESULT The mouse resize icon flickers and it appears that the pointer is still in resize mode. I cannot click anything at this point. EXPECTED RESULT I would expect the mouse pointer not to be in resize mode. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436710] Playing of Flash-free ("plain") Rich Media annotations
https://bugs.kde.org/show_bug.cgi?id=436710 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #3 from Albert Astals Cid --- > It seems that I can't create new merge request normally. You're going to need to be a bit more verbose on what's the problem you're having ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392476] Digital Clock is persistently late by up to one second
https://bugs.kde.org/show_bug.cgi?id=392476 Timothy B changed: What|Removed |Added CC||yule2...@live.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436789] TAB key operations in the download menu of any browser
https://bugs.kde.org/show_bug.cgi?id=436789 --- Comment #4 from prote...@hotmail.it --- Created attachment 138257 --> https://bugs.kde.org/attachment.cgi?id=138257&action=edit selection after clicking on SHIFT-TAB to get the section of the file name -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436789] TAB key operations in the download menu of any browser
https://bugs.kde.org/show_bug.cgi?id=436789 --- Comment #3 from prote...@hotmail.it --- Created attachment 138256 --> https://bugs.kde.org/attachment.cgi?id=138256&action=edit loop area -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436789] TAB key operations in the download menu of any browser
https://bugs.kde.org/show_bug.cgi?id=436789 --- Comment #2 from prote...@hotmail.it --- Created attachment 138255 --> https://bugs.kde.org/attachment.cgi?id=138255&action=edit video TAB & SHIFT+TAB the first part of the video shows how TAB causes the loop, the second one shows the selection of the file name after using SHIFT+TAB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Tomasz Paweł Gajc changed: What|Removed |Added CC||tpg...@gmail.com --- Comment #29 from Tomasz Paweł Gajc --- same thing happens on OpenMandriva Lx cooker with up to date Plasma 5.21.5 and framweworks 5.82.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #413 from leftcrane --- > Don't tell users how to work ! ... (etc.) https://xkcd.com/1172/ What kind of "work"? The only type of work that is facilitated by this gimmick is the work of endlessly fiddling with desktop backgrounds. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436796] New: Seconds skip or update irregularly at minute change
https://bugs.kde.org/show_bug.cgi?id=436796 Bug ID: 436796 Summary: Seconds skip or update irregularly at minute change Product: plasmashell Version: 5.21.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: yule2...@live.com Target Milestone: 1.0 SUMMARY Clock plasmoids (including Digital Clock and its forks) would skip or briefly display the first second of each minute (e.g. 12:34:00). In rare cases, clock plasmoids would randomly skip/briefly display other seconds as well. STEPS TO REPRODUCE 1. Add any clock plasmoid that supports displaying seconds to the desktop or any panel, if there isn't one 2. Configure the plasmoid to show seconds (in the case of Digital Clock, right click the plasmoid, click "Configure Digital Clock", check "Show seconds" under the Appearance tab, and apply changes) 3. Observe that the clock updates irregularly when the minute increments (e.g. 12:00:59 -> 12:01:00) OBSERVED RESULT Within the last few seconds of any minute, the clock would slow down (i.e. one of the seconds would not update for more than 1 second). When the minute changes, the next second (e.g. 12:01:00) is shown for about half a second or not at all. EXPECTED RESULT The clock would consistently display each second in uniformly spaced intervals. SOFTWARE/OS VERSIONS Linux: Kernel 5.11 on Manjaro (I also have kernel versions 5.10 LTS and 5.4 LTS as fallbacks) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This behavior can be inconsistent, at least in recent Plasma releases, as clock plasmoids would sometimes display the first second of each minute properly. I can also work around this by restarting plasmashell over and over until the irregular updates stop, but after a while, the irregular updates return in the same plasmashell instance. This behavior affects ALL clock plasmoids (built-in Analog Clock, Zren's Event Calendar, etc.) but is most noticable with a digital clock. This behavior also occurs when the plasmoid is loaded into Latte Dock, which I no longer use as of submitting this ticket. I believe this is likely related to Bug #392476 since that ticket also deals with clock updates. My Linux kernel version and distro are likely irrelevant, but they may still be helpful. This bug has persisted since I started using Plasma daily on the same machine with version 5.16. Additionally, I first spotted this behavior when I first tried Plasma on a Linux machine running Fedora 24 back in 2016! I am frustrated that this annoyance has not been fixed in the past 5 years or so, and that I've never seen this oddity happen in other desktop environments (including Windows and macOS). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436789] TAB key operations in the download menu of any browser
https://bugs.kde.org/show_bug.cgi?id=436789 --- Comment #1 from prote...@hotmail.it --- Where it is written CTRL has to be read SHIFT. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436743] Folder sizes(by file size) stop after 121 entries in details mode
https://bugs.kde.org/show_bug.cgi?id=436743 ehrich.we...@gmail.com changed: What|Removed |Added Summary|Folder sizes stop after 121 |Folder sizes(by file size) |entries in details mode |stop after 121 entries in ||details mode --- Comment #2 from ehrich.we...@gmail.com --- I think I found the workaround but this is still a bug. Anything more than 5 levels deep will eat all of your cpu and will fail to display folder sizes properly. If it's 5 levels or fewer it seems to work as suspected, at least for that number of levels, and I'm not showing any cpu usage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436795] New: databse from uninstalled version of digikam is unhelpfully persistant
https://bugs.kde.org/show_bug.cgi?id=436795 Bug ID: 436795 Summary: databse from uninstalled version of digikam is unhelpfully persistant Product: digikam Version: 7.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Database Assignee: digikam-bugs-n...@kde.org Reporter: erich.frie...@gmail.com Target Milestone: --- SUMMARY I want to run digikam 5.9; I unfortunately uninstalled digikam 7.0 but when I install digikam 5.9 I get an error message "The database has been used with a more recent version of digikam and has been updated to a database schema which cannot be used with this version. (This means this digikam version is to old, or the database format is too recent.) Please use the more recent version of digiKam that you used before." which is extremely UNHELPFUL as I have zero interest in running 7.0, I want to run 5.9. How can I delete the database that digiKam 7.0 has created so I can run version 5.9? Please advise. I would like to do something short of wiping my hard drive and reinstalling it with version 5.9. When 7.0 uninstalled, it would be most helpful if it could dlete the databse, too. Thank You, 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.
[kaddressbook] [Bug 436794] New: Cannot delete an entry from contact group editor
https://bugs.kde.org/show_bug.cgi?id=436794 Bug ID: 436794 Summary: Cannot delete an entry from contact group editor Product: kaddressbook Version: GIT Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: j...@keelhaul.me.uk CC: to...@kde.org Target Milestone: --- Created attachment 138254 --> https://bugs.kde.org/attachment.cgi?id=138254&action=edit Contact group editor screen shot SUMMARY See screen shot. When editing a contact group, the red '-' buttons to delete an existing entry overlay the displayed email address. If the window is dragged wider then they move to the right, but they still stay at least an inch inside the right side of the list. Clicking on one of the buttons, regardless of where they are located, does not delete the entry from the group. If it is an entry which is a reference to an existing contact, then a combo box is displayed (extending all the way to the right of the list) listing the contact's email addresses. If it is an entry which is not an existing contact, then the email address changes to editable. There appears to be no way to delete an entry using the GUI, the only solution is akonadiclient. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #412 from hcvv --- @leftcrane. Please do not tell others what they want. Many want this. This feature functioned already for more then 25 years (yes, it was in CDE on Unix, not so sophisticated, but you could give every desktop a different background colour). Those who want this do know why they want it. Telling them that they do not know what they want and that you know better what they want is . -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436738] docdata duplicated each time pdf is edited
https://bugs.kde.org/show_bug.cgi?id=436738 --- Comment #6 from pbs3...@googlemail.com --- Albert's point is that I could make many copies of my pdf file, then overwrite it. Under my proposal, all the copies would have their viewing positions reset. (That is, assuming all the copies have been made in different directories sharing the same filename. And also assuming that the new version is viewed immediately after updating it.) Given that Okular already resets the viewing position in far more everyday situations like file rename, I don't see how resetting the viewing position in this exotic situation is such a big deal. Still, my proposal would probably annoy that one user who takes regular snapshots of their system, and regularly looks back at old versions of their pdf documents in old snapshots, who would now find their viewing position keep resetting. It's a question of balancing the effect of breaking one person's workflow by changing something they shouldn't be relying on anyway (https://xkcd.com/1172), given that Okular doesn't preserve viewing position that well in general, vs littering everyone else's systems with thousands of tiny harmless files which, while not taking up very much space, is certainly far from optimal. I leave it up to you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347517] No Popups from Panel or Applicaton Launcher while Windows are visible
https://bugs.kde.org/show_bug.cgi?id=347517 veggero changed: What|Removed |Added CC||niccolo.venera...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #5 from veggero --- as above -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #411 from Lehmeier --- They can do that - in addition. Don't always try to tell users how to work - when they have already found better ways ! Give them what they want (even if it is only optional), then everyone is happy and you have a few problems less! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402690] Duplicate entries in Location sidebar for encrypted volumes
https://bugs.kde.org/show_bug.cgi?id=402690 Ninguém changed: What|Removed |Added CC||lv215...@anonaddy.me --- Comment #1 from Ninguém --- Created attachment 138253 --> https://bugs.kde.org/attachment.cgi?id=138253&action=edit bug I still have the same problem in Dolphin 20.12.3, KDE 5.21.4. In the attachment, the first and the fifth entry points to the same place, this also happens with the second and the third entry. Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-16-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436793] New: keyboard shortcut wishlist
https://bugs.kde.org/show_bug.cgi?id=436793 Bug ID: 436793 Summary: keyboard shortcut wishlist Product: kdenlive Version: 20.12.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: m...@pance.ca Target Milestone: --- SUMMARY I have been using the two shortcuts "X" and "S" for a while now. This is all good. But just a small suggestion to improve it. Now, I use my right hand on the mouse, and left hand on the keyboard. And when I want to press "X" or "S" I have to look away from the screen, and down on the keyboard. It would be nice if I just keep my finger on the "X" key (cut), and when I click on it once, I get the scissors, and when I click on the "X" a second time, it reverts to "Select". This way I can keep my eyes on the screen, and know that the "X" is either "cut" or Select"! In effect, the "X" key alternates between Cut/Select. My two cents. Thanks. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Frameworks 5.80.0 Qt 5.15.2 (built against 5.15.2) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395080] Allow resizing pager with virtual desktops
https://bugs.kde.org/show_bug.cgi?id=395080 veggero changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED CC||niccolo.venera...@gmail.com --- Comment #3 from veggero --- I think a functionality to resize widgets in the panel is, right now, an overkill. It's more appropriate to use margin areas as recently introduced. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #410 from leftcrane --- > The background is a visual clue for where you are. It's a bad visual cue for the following reasons: - the desktop wallpaper might be hidden entirely by the windows. - you have to manage wallpapers for each desktop - that's very a very time consuming way of getting a "visual cue" - you have to remember which desktop background symbolizes which desktop. I don't see the rationale at all here. The visual cue should provided by a panel plasmoid. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436792] New: Project Save and Save as unusable
https://bugs.kde.org/show_bug.cgi?id=436792 Bug ID: 436792 Summary: Project Save and Save as unusable Product: kdenlive Version: 20.12.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kodaly@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCT 1.New (Ctrl+N) OK 2. Projekt beállítások Custom project folder -->/home/spagina/Dokumentumok/VideoSzerkesztes/ProbaVideo/ Add Clip or Folder OK 3. Mentés SAVE (CTRL+S) or Mentés másként.. Save as ..(CTRL+Shift+S) UNUSABLE, nothing happens ! Project name remains "Névtelen*/1000*750..." OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS xUBUNTU :Ubuntu 20.04.2 LTS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338075] Tagging RAW images for Canon EOS-1Ds with Exiv2 corrupts them - Use ExifTool instead
https://bugs.kde.org/show_bug.cgi?id=338075 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Tagging RAW images for |Tagging RAW images for |Canon EOS-1Ds corrupts them |Canon EOS-1Ds with Exiv2 ||corrupts them - Use ||ExifTool instead Component|Metadata-Raw|Metadata-ExifTool Resolution|DUPLICATE |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406857] auto-hide fails after window demands attention
https://bugs.kde.org/show_bug.cgi?id=406857 veggero changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO CC||niccolo.venera...@gmail.com --- Comment #4 from veggero --- as above -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366348] Saving metadata to video files using ExifTool
https://bugs.kde.org/show_bug.cgi?id=366348 caulier.gil...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Summary|WISH: Saving metadata to|Saving metadata to video |video files |files using ExifTool Component|Metadata-Video |Metadata-ExifTool Version Fixed In|5.1.0 | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 436791] baloo treats similar letters as different - follows Unicode standard
https://bugs.kde.org/show_bug.cgi?id=436791 Stefan Brüns changed: What|Removed |Added Summary|baloo treats similar|baloo treats similar |letters as different|letters as different - ||follows Unicode standard -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 436791] baloo treats similar letters as different
https://bugs.kde.org/show_bug.cgi?id=436791 Stefan Brüns changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Stefan Brüns --- Baloo relies on decomposition according to the Unicode standard. E.g. the letter ä has an equivalent decomposition 'a + diaresis' (diaresis: "dots"). 'ł' has no equivalent. You can see all the equivalents either in the Unicode standard, or with KCharSelect. If you think this is wrong, please report it to the Unicode consortium. Baloo is not able to and thus wont maintain a list of exceptions to the ever evolving Unicode standard. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435586] Message "Unable to create io-slave. klauncher said: Unknown protocol 'tags'." appears on every Dolphin launch
https://bugs.kde.org/show_bug.cgi?id=435586 --- Comment #8 from Andreas Sturmlechner --- (In reply to Andreas Sturmlechner from comment #7) > but I can still trigger it by right clicking into the > dolphinview, effectively cancelling context menu. Nevermind - that was just baloo-widgets still being installed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436788] TAB key operations in the download menu of any browser
https://bugs.kde.org/show_bug.cgi?id=436788 --- Comment #8 from prote...@hotmail.it --- Created attachment 138252 --> https://bugs.kde.org/attachment.cgi?id=138252&action=edit TAB & SHIFT+TAB the first part of the video shows how tab enter the loop, the second one shows the selection of the file name after using SHIFT+TAB -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 436791] New: baloo treats similar letters as different
https://bugs.kde.org/show_bug.cgi?id=436791 Bug ID: 436791 Summary: baloo treats similar letters as different Product: frameworks-baloo Version: 5.80.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: amand...@posteo.net CC: baloo-bugs-n...@kde.org, n...@kde.org Target Milestone: --- SUMMARY Hi! Thanks for making baloo, the solid indexing features are one of the things that make linux a better suited for me. I do, however, have some issues with baloo indexer. Sadly, it treats similar (national, like Polish) letters as different- sometimes. While they are different, it is not uncommon to avoid using them in filenames to save yourself some problems (admitedly, it's more of the old behaviour, as code pages were a massive PITA). Anyway, letters 'l' and 'ł' ('l' with a stroke) are not considered similar enough (even when 'l' is sometimes used when using 'ł' is inconvenient), yet letters 'e' and 'ę' ('e' with a tail) are considered similar (i.e. the search results for words with 'ę' /like: "się"/ also include phrase 'sie'). Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-16-generic OS Type: 64-bit Graphics Platform: X11 Processors: 4 × AMD PRO A12-9800B R7, 12 COMPUTE CORES 4C+8G Memory: 14.6 GiB of RAM Graphics Processor: AMD Radeon R7 Graphics kde installed from the official repository -- You are receiving this mail because: You are watching all bug changes.