[kwin] [Bug 366651] Kwin Compositor Stops Updating Windows
https://bugs.kde.org/show_bug.cgi?id=366651 Michael changed: What|Removed |Added CC||kde@callthecomputerdoctor.c ||om -- You are receiving this mail because: You are watching all bug changes.
[docs.kde.org] [Bug 468891] yes who create panic all over the world with their best looks.
https://bugs.kde.org/show_bug.cgi?id=468891 Megha M. changed: What|Removed |Added URL||https://www.meghamalik.com Keywords||bounty -- You are receiving this mail because: You are watching all bug changes.
[docs.kde.org] [Bug 468891] New: yes who create panic all over the world with their best looks.
https://bugs.kde.org/show_bug.cgi?id=468891 Bug ID: 468891 Summary: yes who create panic all over the world with their best looks. Classification: Websites Product: docs.kde.org Version: 4.12.5 Platform: Neon OS: OpenBSD Status: REPORTED Severity: normal Priority: NOR Component: Corrections Assignee: kde-doc-engl...@kde.org Reporter: mmvipmo...@gmail.com Target Milestone: --- Created attachment 158378 --> https://bugs.kde.org/attachment.cgi?id=158378=edit Solve It SUMMARY *** See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I am Megha Malik and for the last 2 years, I worked as a fashion model. I have a huge passion for acting and I love being in front of the camera. STEPS TO REPRODUCE 1. https://bit.ly/3laCtQk 2. https://bit.ly/3l2e677 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 Website: https://www.meghamalik.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386295] People and Tags Filter sidebars doesn't show the same Unconfirmed Faces
https://bugs.kde.org/show_bug.cgi?id=386295 --- Comment #9 from stefan.mueller...@gmail.com --- Cannot tell at the moment, I don't use it currently (travelling) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 467369] When creating a link to an application from the desktop context menu, selecting the program path from the browse dialogue doesn't work with spaces
https://bugs.kde.org/show_bug.cgi?id=467369 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1264 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468270] No contrast in account connection error message
https://bugs.kde.org/show_bug.cgi?id=468270 --- 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.
[plasmashell] [Bug 459724] Black Desktop / Desktop Reset (Mutiple Monitor Setup)
https://bugs.kde.org/show_bug.cgi?id=459724 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467112] All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467112 --- Comment #10 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 461684] Plasma crashes in PlasmaQuick::ContainmentView::containment() on login
https://bugs.kde.org/show_bug.cgi?id=461684 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466823] Icons on desktop disappear regularly after some time, possibly a multi-monitor issue
https://bugs.kde.org/show_bug.cgi?id=466823 --- Comment #6 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 389179] Error creating mysql db for internal server (mysql_install_db)
https://bugs.kde.org/show_bug.cgi?id=389179 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||8.1.0 Resolution|--- |FIXED --- Comment #8 from caulier.gil...@gmail.com --- mysql-bin.0* (Binary Log Files) are for recovery purpose. See details here: https://stackoverflow.com/questions/29557000/how-to-prevent-mysql-from-createing-mysql-bin-0x-files Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468692] Crash during animation, app force quit.
https://bugs.kde.org/show_bug.cgi?id=468692 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467545] KWin is not duck safe
https://bugs.kde.org/show_bug.cgi?id=467545 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #4 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.
[plasmashell] [Bug 467463] Plasma suddenly crashes without restarting
https://bugs.kde.org/show_bug.cgi?id=467463 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 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.
[plasmashell] [Bug 467586] KEmulator movement crashes Plasmashell
https://bugs.kde.org/show_bug.cgi?id=467586 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[krita] [Bug 468202] Krita on Android freezes after creating a new document or opening a pre-existing one
https://bugs.kde.org/show_bug.cgi?id=468202 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467454] Plasma crashes within 10 seconds of logon
https://bugs.kde.org/show_bug.cgi?id=467454 --- 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.
[okular] [Bug 468192] Inserted text does not appear.
https://bugs.kde.org/show_bug.cgi?id=468192 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459126] Panel configuration looks corrupted
https://bugs.kde.org/show_bug.cgi?id=459126 --- 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.
[plasmashell] [Bug 450072] Plasma Desktop loose the background picture during session on one single monitor (principal) while in dual monitor session with several activities.
https://bugs.kde.org/show_bug.cgi?id=450072 --- 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.
[plasmashell] [Bug 461144] Deleted widget after reboot always come back
https://bugs.kde.org/show_bug.cgi?id=461144 --- Comment #13 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 450396] folders from home show on desktop
https://bugs.kde.org/show_bug.cgi?id=450396 --- Comment #10 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 444590] Icons/Files moving when turn off monitor
https://bugs.kde.org/show_bug.cgi?id=444590 --- Comment #6 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 449167] Icons on desktop move randomly
https://bugs.kde.org/show_bug.cgi?id=449167 --- Comment #14 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 425781] Folders Not Displaying Correct Icon
https://bugs.kde.org/show_bug.cgi?id=425781 --- 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.
[digikam] [Bug 389046] Face suggestions disappair each time i confirm one
https://bugs.kde.org/show_bug.cgi?id=389046 --- Comment #30 from caulier.gil...@gmail.com --- @nonobio digiKam 8.0.0 is out. Problem still valid with this release ? Best regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386295] People and Tags Filter sidebars doesn't show the same Unconfirmed Faces
https://bugs.kde.org/show_bug.cgi?id=386295 --- Comment #8 from caulier.gil...@gmail.com --- @Stefan, digiKam 8.0.0 is out. Problem still valid with this release ? Best regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385148] Widgets are almost invisible using most "dark" shipped themes.
https://bugs.kde.org/show_bug.cgi?id=385148 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Form fields are almost |Widgets are almost |invisible using most "dark" |invisible using most "dark" |shipped themes |shipped themes. --- Comment #20 from caulier.gil...@gmail.com --- @Jens, digiKam 8.0.0 is out. Problem still valid with this release ? Best regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384086] Rotation of some images (JPEG, by Samsung S5 smartphone) during import is incorrect
https://bugs.kde.org/show_bug.cgi?id=384086 --- Comment #11 from caulier.gil...@gmail.com --- @Jens, digiKam 8.0.0 is out. Problem still valid with this release ? Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466019] Allow saving tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466019 Almaz changed: What|Removed |Added CC||almazgalie...@gmail.com --- Comment #4 from Almaz --- +1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463475] Konsole crashes when monitor goes to sleep
https://bugs.kde.org/show_bug.cgi?id=463475
Dick Tracey changed:
What|Removed |Added
CC||traceyd...@yandex.com
--- Comment #26 from Dick Tracey ---
This is constantly happening to me to on Arch Linux, with dolphin (likely due
to the embedded konsole in it), using 23.04.0. Virtually every time I come back
to the computer and wake the screen up, dolphin crashes, super annoying...
I filed this for Dolphin https://bugs.kde.org/show_bug.cgi?id=464967
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __memcpy_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:265
#7 0x7f04a9c535d3 in memmove (__len=262112, __src=0x7effc58be810,
__dest=) at /usr/include/bits/string_fortified.h:36
#8 copy_unswapped (rect=..., img=...,
dstBytesPerLine=262112, dst=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:547
#9 native_sub_image (swap=false, rect=..., src=...,
dstStride=262112, buffer=0x5613f67151a0) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:590
#10 QXcbBackingStoreImage::flushPixmap(QRegion const&, bool)
(this=this@entry=0x5613f6715120, region=..., fullRegion=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:669
#11 0x7f04a9c53913 in QXcbBackingStoreImage::flushPixmap(QRegion const&,
bool) (fullRegion=, this=this@entry=0x5613f6715120, region=...,
fullRegion=fullRegion@entry=true) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:690
#12 0x7f04a9c53b77 in QXcbBackingStoreImage::flushPixmap(QRegion const&,
bool) (fullRegion=false, region=..., this=0x5613f6715120) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:627
#13 QXcbBackingStoreImage::put(unsigned int, QRegion const&, QPoint const&)
(this=0x5613f6715120, dst=62914569, region=..., offset=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:741
#14 0x7f04a9c544ce in QXcbBackingStore::flush(QWindow*, QRegion const&,
QPoint const&) (this=this@entry=0x5613f6684640,
window=window@entry=0x5613f66e3d60, region=..., offset=...) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbwindow.h:120
#15 0x7f04afce45a5 in QBackingStore::flush(QRegion const&, QWindow*, QPoint
const&) (this=this@entry=0x7f049c001f70, region=..., window=0x5613f66e3d60,
offset=...) at painting/qbackingstore.cpp:252
#16 0x7f04b0382e81 in QWidgetRepaintManager::flush(QWidget*, QRegion
const&, QPlatformTextureList*) (this=this@entry=0x5613f6774d70,
widget=0x5613f6367760, region=..., widgetTextures=) at
kernel/qwidgetrepaintmanager.cpp:1198
#17 0x7f04b03833d5 in QWidgetRepaintManager::flush()
(this=this@entry=0x5613f6774d70) at kernel/qwidgetrepaintmanager.cpp:1096
#18 0x7f04b0384ab9 in QWidgetRepaintManager::paintAndFlush()
(this=0x5613f6774d70) at kernel/qwidgetrepaintmanager.cpp:1028
#19 0x7f04b03d0f79 in QWidgetWindow::handleResizeEvent(QResizeEvent*)
(event=0x775f8300, this=0x5613f66e3d60) at kernel/qwidgetwindow.cpp:842
#20 QWidgetWindow::event(QEvent*) (this=0x5613f66e3d60, event=0x775f8300)
at kernel/qwidgetwindow.cpp:322
#21 0x7f04b0378b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5613f66e3d60, e=0x775f8300) at
kernel/qapplication.cpp:3640
#22 0x7f04af68e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5613f66e3d60, event=0x775f8300) at
kernel/qcoreapplication.cpp:1064
#23 0x7f04af68e0b3 in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#24 0x7f04afb41276 in
QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*)
(e=) at kernel/qguiapplication.cpp:2610
#25 0x7f04afb298c5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#26 0x7f04a9c5a8c0 in xcbSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105
#27 0x7f04ad50f53b in g_main_dispatch (context=0x7f04a4000ee0) at
../glib/glib/gmain.c:3460
#28 g_main_context_dispatch (context=0x7f04a4000ee0) at
../glib/glib/gmain.c:4200
#29 0x7f04ad56c219 in g_main_context_iterate.constprop.0
(context=0x7f04a4000ee0, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4276
#30 0x7f04ad50e1a2 in g_main_context_iteration (context=0x7f04a4000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#31 0x7f04af6d8d3c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5613f5e381a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#32 0x7f04af68668c in
[konsole] [Bug 467191] Konsole crashes when monitor goes to sleep on X11
https://bugs.kde.org/show_bug.cgi?id=467191 --- Comment #3 from Dick Tracey --- This the bug I reported for Dolphin: https://bugs.kde.org/show_bug.cgi?id=464967 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 467191] Konsole crashes when monitor goes to sleep on X11
https://bugs.kde.org/show_bug.cgi?id=467191
Dick Tracey changed:
What|Removed |Added
CC||traceyd...@yandex.com
--- Comment #2 from Dick Tracey ---
This is happening to me in dolphin possibly because of the embedded konsole.
Also on Arch Linux with dual monitors, 23.04.0
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __memcpy_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:265
#7 0x7f04a9c535d3 in memmove (__len=262112, __src=0x7effc58be810,
__dest=) at /usr/include/bits/string_fortified.h:36
#8 copy_unswapped (rect=..., img=...,
dstBytesPerLine=262112, dst=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:547
#9 native_sub_image (swap=false, rect=..., src=...,
dstStride=262112, buffer=0x5613f67151a0) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:590
#10 QXcbBackingStoreImage::flushPixmap(QRegion const&, bool)
(this=this@entry=0x5613f6715120, region=..., fullRegion=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:669
#11 0x7f04a9c53913 in QXcbBackingStoreImage::flushPixmap(QRegion const&,
bool) (fullRegion=, this=this@entry=0x5613f6715120, region=...,
fullRegion=fullRegion@entry=true) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:690
#12 0x7f04a9c53b77 in QXcbBackingStoreImage::flushPixmap(QRegion const&,
bool) (fullRegion=false, region=..., this=0x5613f6715120) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:627
#13 QXcbBackingStoreImage::put(unsigned int, QRegion const&, QPoint const&)
(this=0x5613f6715120, dst=62914569, region=..., offset=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:741
#14 0x7f04a9c544ce in QXcbBackingStore::flush(QWindow*, QRegion const&,
QPoint const&) (this=this@entry=0x5613f6684640,
window=window@entry=0x5613f66e3d60, region=..., offset=...) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbwindow.h:120
#15 0x7f04afce45a5 in QBackingStore::flush(QRegion const&, QWindow*, QPoint
const&) (this=this@entry=0x7f049c001f70, region=..., window=0x5613f66e3d60,
offset=...) at painting/qbackingstore.cpp:252
#16 0x7f04b0382e81 in QWidgetRepaintManager::flush(QWidget*, QRegion
const&, QPlatformTextureList*) (this=this@entry=0x5613f6774d70,
widget=0x5613f6367760, region=..., widgetTextures=) at
kernel/qwidgetrepaintmanager.cpp:1198
#17 0x7f04b03833d5 in QWidgetRepaintManager::flush()
(this=this@entry=0x5613f6774d70) at kernel/qwidgetrepaintmanager.cpp:1096
#18 0x7f04b0384ab9 in QWidgetRepaintManager::paintAndFlush()
(this=0x5613f6774d70) at kernel/qwidgetrepaintmanager.cpp:1028
#19 0x7f04b03d0f79 in QWidgetWindow::handleResizeEvent(QResizeEvent*)
(event=0x775f8300, this=0x5613f66e3d60) at kernel/qwidgetwindow.cpp:842
#20 QWidgetWindow::event(QEvent*) (this=0x5613f66e3d60, event=0x775f8300)
at kernel/qwidgetwindow.cpp:322
#21 0x7f04b0378b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5613f66e3d60, e=0x775f8300) at
kernel/qapplication.cpp:3640
#22 0x7f04af68e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5613f66e3d60, event=0x775f8300) at
kernel/qcoreapplication.cpp:1064
#23 0x7f04af68e0b3 in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#24 0x7f04afb41276 in
QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*)
(e=) at kernel/qguiapplication.cpp:2610
#25 0x7f04afb298c5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#26 0x7f04a9c5a8c0 in xcbSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105
#27 0x7f04ad50f53b in g_main_dispatch (context=0x7f04a4000ee0) at
../glib/glib/gmain.c:3460
#28 g_main_context_dispatch (context=0x7f04a4000ee0) at
../glib/glib/gmain.c:4200
#29 0x7f04ad56c219 in g_main_context_iterate.constprop.0
(context=0x7f04a4000ee0, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4276
#30 0x7f04ad50e1a2 in g_main_context_iteration (context=0x7f04a4000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#31 0x7f04af6d8d3c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5613f5e381a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#32 0x7f04af68668c in
QEventLoop::exec(QFlags) (this=0x775f85f0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#33 0x7f04af6912f9 in QCoreApplication::exec() () at
[dolphin] [Bug 464967] dolphin process for another user (using kdesu) crashes after screen wake
https://bugs.kde.org/show_bug.cgi?id=464967
--- Comment #10 from Dick Tracey ---
Still happening in 23.04.0
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __memcpy_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:265
#7 0x7f04a9c535d3 in memmove (__len=262112, __src=0x7effc58be810,
__dest=) at /usr/include/bits/string_fortified.h:36
#8 copy_unswapped (rect=..., img=...,
dstBytesPerLine=262112, dst=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:547
#9 native_sub_image (swap=false, rect=..., src=...,
dstStride=262112, buffer=0x5613f67151a0) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:590
#10 QXcbBackingStoreImage::flushPixmap(QRegion const&, bool)
(this=this@entry=0x5613f6715120, region=..., fullRegion=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:669
#11 0x7f04a9c53913 in QXcbBackingStoreImage::flushPixmap(QRegion const&,
bool) (fullRegion=, this=this@entry=0x5613f6715120, region=...,
fullRegion=fullRegion@entry=true) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:690
#12 0x7f04a9c53b77 in QXcbBackingStoreImage::flushPixmap(QRegion const&,
bool) (fullRegion=false, region=..., this=0x5613f6715120) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:627
#13 QXcbBackingStoreImage::put(unsigned int, QRegion const&, QPoint const&)
(this=0x5613f6715120, dst=62914569, region=..., offset=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:741
#14 0x7f04a9c544ce in QXcbBackingStore::flush(QWindow*, QRegion const&,
QPoint const&) (this=this@entry=0x5613f6684640,
window=window@entry=0x5613f66e3d60, region=..., offset=...) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbwindow.h:120
#15 0x7f04afce45a5 in QBackingStore::flush(QRegion const&, QWindow*, QPoint
const&) (this=this@entry=0x7f049c001f70, region=..., window=0x5613f66e3d60,
offset=...) at painting/qbackingstore.cpp:252
#16 0x7f04b0382e81 in QWidgetRepaintManager::flush(QWidget*, QRegion
const&, QPlatformTextureList*) (this=this@entry=0x5613f6774d70,
widget=0x5613f6367760, region=..., widgetTextures=) at
kernel/qwidgetrepaintmanager.cpp:1198
#17 0x7f04b03833d5 in QWidgetRepaintManager::flush()
(this=this@entry=0x5613f6774d70) at kernel/qwidgetrepaintmanager.cpp:1096
#18 0x7f04b0384ab9 in QWidgetRepaintManager::paintAndFlush()
(this=0x5613f6774d70) at kernel/qwidgetrepaintmanager.cpp:1028
#19 0x7f04b03d0f79 in QWidgetWindow::handleResizeEvent(QResizeEvent*)
(event=0x775f8300, this=0x5613f66e3d60) at kernel/qwidgetwindow.cpp:842
#20 QWidgetWindow::event(QEvent*) (this=0x5613f66e3d60, event=0x775f8300)
at kernel/qwidgetwindow.cpp:322
#21 0x7f04b0378b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5613f66e3d60, e=0x775f8300) at
kernel/qapplication.cpp:3640
#22 0x7f04af68e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5613f66e3d60, event=0x775f8300) at
kernel/qcoreapplication.cpp:1064
#23 0x7f04af68e0b3 in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#24 0x7f04afb41276 in
QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*)
(e=) at kernel/qguiapplication.cpp:2610
#25 0x7f04afb298c5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#26 0x7f04a9c5a8c0 in xcbSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105
#27 0x7f04ad50f53b in g_main_dispatch (context=0x7f04a4000ee0) at
../glib/glib/gmain.c:3460
#28 g_main_context_dispatch (context=0x7f04a4000ee0) at
../glib/glib/gmain.c:4200
#29 0x7f04ad56c219 in g_main_context_iterate.constprop.0
(context=0x7f04a4000ee0, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4276
#30 0x7f04ad50e1a2 in g_main_context_iteration (context=0x7f04a4000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#31 0x7f04af6d8d3c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5613f5e381a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#32 0x7f04af68668c in
QEventLoop::exec(QFlags) (this=0x775f85f0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#33 0x7f04af6912f9 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#34 0x7f04afb3b052 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1870
#35 0x7f04b0376f2a in QApplication::exec() () at
kernel/qapplication.cpp:2832
#36 0x5613f43b1dab in main(int, char**) (argc=,
argv=) at
[Spectacle] [Bug 468874] Using background mode with `-b` to hide the GUI and just save to a file with `-o` no longer works with `-region`.
https://bugs.kde.org/show_bug.cgi?id=468874 --- Comment #4 from incom...@frogg.ie --- Ah, thank you! That's helpful :) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468890] New: Spectacle consistently crashes when trying to take a screenshot.
https://bugs.kde.org/show_bug.cgi?id=468890 Bug ID: 468890 Summary: Spectacle consistently crashes when trying to take a screenshot. Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: gabrielh...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (23.04.0) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.2.12-zen1-1-zen x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Whenever I try to take a screenshot, Spectacle crashes. When opting to "select a rectangular region", it crashes before me being able to select anything. The crash can be reproduced every time. -- Backtrace: Application: Spectacle (spectacle), signal: Bus error [KCrash Handler] #4 0x7fd7abc283dc in QQuickTransform::~QQuickTransform() () at /usr/lib/libQt5Quick.so.5 #5 0x7fd7abdb1b93 in () at /usr/lib/libQt5Quick.so.5 #6 0x7fd7abd94d82 in QAccessibleQuickItem::role() const () at /usr/lib/libQt5Quick.so.5 #7 0x7fd796b90929 in () at /usr/lib/libQt5XcbQpa.so.5 #8 0x7fd796b7cd8e in () at /usr/lib/libQt5XcbQpa.so.5 #9 0x7fd796b7da46 in () at /usr/lib/libQt5XcbQpa.so.5 #10 0x7fd7abc324bc in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #11 0x7fd7abc29ba3 in QQuickItem::setParentItem(QQuickItem*) () at /usr/lib/libQt5Quick.so.5 #12 0x7fd7abc2a162 in QQuickItem::~QQuickItem() () at /usr/lib/libQt5Quick.so.5 #13 0x7fd74e5d332b in () at /usr/lib/qt/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #14 0x7fd7abcba459 in QQuickView::~QQuickView() () at /usr/lib/libQt5Quick.so.5 #15 0x55ca2decbd6c in () #16 0x7fd7aa8b1aaa in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7fd7ac178b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7fd7aa88e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7fd7aa88eb33 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #20 0x7fd7aa8d4f58 in () at /usr/lib/libQt5Core.so.5 #21 0x7fd7a850f53b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #22 0x7fd7a856c219 in () at /usr/lib/libglib-2.0.so.0 #23 0x7fd7a850e1a2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #24 0x7fd7aa8d8d3c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x7fd7aa88668c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #26 0x7fd7aa8912f9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #27 0x55ca2de9bb17 in () #28 0x7fd7aa03c790 in () at /usr/lib/libc.so.6 #29 0x7fd7aa03c84a in __libc_start_main () at /usr/lib/libc.so.6 #30 0x55ca2de9c645 in () [Inferior 1 (process 6606) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468889] New: way to force printer to use drivers
https://bugs.kde.org/show_bug.cgi?id=468889 Bug ID: 468889 Summary: way to force printer to use drivers Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: dchme...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Systemsettings sets up so-called 'driverless' printers, sometimes (if removed) multiple times, which I've found lack quality/settings that drivers have, and seems there's no way to get rid of. STEPS TO REPRODUCE 1. Add printer drivers. 2. Watch users assume printer is set right or select one. OBSERVED RESULT Printer drivers are sometimes better than so-called 'driverless' which seems there's no way to get rid of. When users accidentally selected the driverless (not default) option we've had whole sections omitted within documents when printed, regardless of text editor or word processor. EXPECTED RESULT If one wants to use drivers, allow that and for it to be the only choice if desired. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: KDE Neon 5.n 20+ to 5.27 22.04 KDE Plasma Version: 5.n to 5.27.4 KDE Frameworks Version: 5.n to 5.105.0 Qt Version: 5.n to 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468874] Using background mode with `-b` to hide the GUI and just save to a file with `-o` no longer works with `-region`.
https://bugs.kde.org/show_bug.cgi?id=468874 --- Comment #3 from Noah Davis --- (In reply to incoming from comment #2) > Ah, my screenshot tool had `-region` hardcoded as an option, I'm assuming it > was being parsed as `-r` previously and worked just fine, using `-r` or > `--region` works just fine now! Thank you for letting me know :) Just so you know, here's what's going on when you use `-region`. All of the letters together just happen to be valid single letter flags and single letter flags can be combined without spaces when putting a single dash at the front of all of them: -r, --region: Capture a rectangular region of the screen -e, --no-decoration: In background mode, exclude decorations in the screenshot -g, --gui: Start in GUI mode (default) -i, --new-instance: Starts a new GUI instance of spectacle without registering to DBus -o, --output : In background mode, save image to specified file -n, --nonotify: In background mode, do not pop up a notification when the screenshot is taken `-g` currently gets precidence over `-b` because `-g` would otherwise be a completely useless flag, which is what was causing the change in behavior. If I knew of a way to make the last specified flag override the previous incompatible option, I could make using `-region` work again. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468888] New: KATE printing formatting problems
https://bugs.kde.org/show_bug.cgi?id=46 Bug ID: 46 Summary: KATE printing formatting problems Classification: Applications Product: kate Version: 23.04.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- KATE has several printing formatting problems, including a general KDE one I reported elsewhere. We use imperial/USA measurements--inches--but KATE describes page/margins in millimetres. We print previewed a 12-page document it said was 11 pages. It only printed the top half of lines at page bottoms. STEPS TO REPRODUCE 1. Print preview a multiple-page document 2. Check formatting of margins (maybe need to add alternative language/dialect despite not using its measurements) and number of pages 3. Print and check every line at bottom of page OBSERVED RESULT KATE misformats documents, including using other measurements than set in locale, and doesn't round up number of pages if even goes over one character, and only prints top half of lines at bottom of pages. EXPECTED RESULT Use locale. Round up number of pages. Check if last line will fit, including bottom half, and if not, start it on next page. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: KDE Neon 5.27 22.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I can test on FreeBSD UNIX, Slackware GNU/Linux, connected to same printer (on KDE Neon host) over network. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468887] New: KATE printing formatting problems
https://bugs.kde.org/show_bug.cgi?id=468887 Bug ID: 468887 Summary: KATE printing formatting problems Classification: Applications Product: kate Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- KATE has several printing formatting problems, including a general KDE one I reported elsewhere. When we have our measurements set to imperial/USA lengths, KATE doesn't show us the margins in that format rather than millimetres, which some are too short or not used at all, because on a several page file (after we select USA letter format which the paper is) all the last lines got cut in half at the bottom of the page, unreadable. When I print previewed a 12-page document it said it was 11 pages. STEPS TO REPRODUCE 1. Print preview and then print multiple-page document 2. View measurements about the page including margins (see locale not used, which you may need to add an alternative/secondary language/dialect despite not actually using its measurements) and number of pages (if it's 11 & 1/2 it'll say 11 rather than 12) 3. Check each bottom line OBSERVED RESULT Wrong formatting used in description, print preview, and for the bottom line which gets cut off. EXPECTED RESULT USE the correct lengths that are set in the locale. Check if there is space for the bottom line, and if not, start it on the next page. Round up number of pages if even goes over by one character. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: KDE Neon 5.27 22.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.19.9 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468883] [Feature Request] Add option for jpg copy
https://bugs.kde.org/show_bug.cgi?id=468883 --- Comment #2 from Noah Davis --- > This is my first time posting so if I did anything wrong, please let me know > and I will do my best to correct it. JFYI, It's not a big deal to post a duplicate bug report. While it is good to check if another report already exists, even duplicates can be a useful if imperfect way to gauge how common an issue is or how much a feature is wanted. A report that gets a lot of duplicates tends to be one that really needs to be dealt with. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 465781] Spectacle doesn't follow image format when copying image
https://bugs.kde.org/show_bug.cgi?id=465781 Noah Davis changed: What|Removed |Added CC||rerupersonal1+...@gmail.com --- Comment #13 from Noah Davis --- *** Bug 468883 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468883] [Feature Request] Add option for jpg copy
https://bugs.kde.org/show_bug.cgi?id=468883 Noah Davis changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Noah Davis --- Looks like you're not the first person to request this. Maybe I'll have to look into adding this. *** This bug has been marked as a duplicate of bug 465781 *** -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 468885] Kmag does not work
https://bugs.kde.org/show_bug.cgi?id=468885 --- Comment #1 from Cristian --- This problem started after I upgrade to Ubunto 22.04 Befor that, Kmag worked normally on Ubuntu 20 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 468824] Kubuntu Focus is not in the list of KDE patrons
https://bugs.kde.org/show_bug.cgi?id=468824 --- Comment #4 from Toni Asensi Esteve --- I'm writing this new message because Enioka is no longer on [Supporting Members](https://ev.kde.org/supporting-members/) , although Aleix Pol [wrote](https://invent.kde.org/websites/ev-kde-org/-/commit/30c761f40b775fc40908ff23f53e3ea6cfe328eb) that "Enioka is a supporting member". Enioka and Pine64 are also seen at the bottom of https://kde.org/ under the "KDE Patrons" section, although [it was written](https://invent.kde.org/websites/ev-kde-org/-/commit/30c761f40b775fc40908ff23f53e3ea6cfe328eb) that "Remove Pine64 and Enioka [...] They are no longer patrons". Thanks for caring! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468886] New: [Feature Request]
https://bugs.kde.org/show_bug.cgi?id=468886 Bug ID: 468886 Summary: [Feature Request] Classification: Applications Product: kdenlive Version: git-master Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: robjamesp...@gmail.com Target Milestone: --- I wish to see Kdenlive's Audio & Video tracks to be movable. Meaning I can place an audio track between two video tracks and the same for the video tracks. This is present in VEGAS Pro. -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 468885] New: Kmag does not work
https://bugs.kde.org/show_bug.cgi?id=468885 Bug ID: 468885 Summary: Kmag does not work Classification: Applications Product: kmag Version: 22.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sar...@users.sourceforge.net Reporter: cristianfr...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Kmag starts correctly but does not magnify anything from the desktop. It only shows a gray rectangle. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04.2 lts / GNOME 42.5 / 64 bits Intel HD Graphics KDE Plasma Version: KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 (compilado con 5.15.8) ADDITIONAL INFORMATION The same occurs with other magnifiers such as xzoom or Magnus I need Kmag for work, please Thank you -- You are receiving this mail because: You are watching all bug changes.
[kwordquiz] [Bug 467585] The Question & Answer quiz should be case-insensitive.
https://bugs.kde.org/show_bug.cgi?id=467585 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/education/kwordquiz/-/merge_requests/23 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468883] [Feature Request] Add option for jpg copy
https://bugs.kde.org/show_bug.cgi?id=468883 Bug Janitor Service changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422006] [Dolphin] Emptying trash does not trigger view refresh
https://bugs.kde.org/show_bug.cgi?id=422006 Patrick Silva changed: What|Removed |Added Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- --- Comment #26 from Patrick Silva --- I have just seen this bug with a small .jpg file sent to Trash from /Home/Download/subfolder. Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 468884] New Regression (?): Gwenview Incompatibility With Some Self Made libaom avif Photos [sxiv opens them with no problem]
https://bugs.kde.org/show_bug.cgi?id=468884 John changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 468884] New: New Regression (?): Gwenview Incompatibility With Some Self Made libaom avif Photos [sxiv opens them with no problem]
https://bugs.kde.org/show_bug.cgi?id=468884 Bug ID: 468884 Summary: New Regression (?): Gwenview Incompatibility With Some Self Made libaom avif Photos [sxiv opens them with no problem] Classification: Applications Product: gwenview Version: 22.12.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: kdelo...@mozej.com Target Milestone: --- Created attachment 158377 --> https://bugs.kde.org/attachment.cgi?id=158377=edit Gwenview and Dolphin Fail on This Self Made Avif Photo. Sxiv opens it with no problem. SUMMARY *** Gwenview can open some avif made photos, but on some it fails to open. Dolphin can't generate thumbnail. Sxiv has no problem at all. *** STEPS TO REPRODUCE 1. Make a photo with Nicon D810 [tiff, 7380x4928] 2. Import with dcraw [9.28] 3. Convert it to intermediary PNG with graphicsmagic [$ gm convert] 4. Compress your PNG photo to avif [av1] with libaom: $ avifenc -c aom -j all -d 8 -s 0 --sharpyuv -a aq-mode=2 -a sharpness=0 myphoto.png -o myphoto_compressed.avif 5. Result: Size reduction from 209M [tif]/164M [png] to 506K [avif]. OBSERVED RESULT 1. Dolphin has no thumbnail [unlike my other slef-made avif photos] 2. Gwenview can't open this avif photo 3. sxiv has absolutely zero problem with this photo EXPECTED RESULT Stop adding endless functions to gwenview. Focus on photo displaying. Make it high quality photo viewer just like sxiv. Do one thing, one thing only and do it good. Gwenview should be photo viewer not editor. Its not GIMP nor Darktable. Make it robust photo viewer. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (not manjaro) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105 Qt Version: 5.15.9 ADDITIONAL INFORMATION not sure if needed, but: ffmpegthumbs: 23.04 kimageformats: 5.105 libaom 3.6.0 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468883] New: [Feature Request] Add option for jpg copy
https://bugs.kde.org/show_bug.cgi?id=468883 Bug ID: 468883 Summary: [Feature Request] Add option for jpg copy Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: rerupersonal1+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY This is a feature request for when you copy in Spectacle. I would like to be able to set it so that when I copy an image it copies in .jpg format instead of .png format. You can set the default save format to be .jpg by default, but you can't set screenshots to use .jpg. Being able to select this is really nice because I upload a lot of images and .jpg files are quite a bit smaller. I currently use Flameshot, but I heard about spectacle and that it had an update from youtube and I really like that it can take screenshots and do video recording in the same program. I have also recently switched to Wayland which causes some issues with flameshot when having multiple monitors. Another request I have (if I can list it here as well, if not i will make new request for it) is to be able to set keybinds for starting a recording. When I was on windows, I used the gamebar to take short 30-60 second clips and it was really simple to just hit meta+alt+r to start and stop the recording. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux: Garuda Linux x86_64 KDE Plasma Version: Plasma 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 This is my first time posting so if I did anything wrong, please let me know and I will do my best to correct it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 448750] SVGs corrupted on upgrade until SVG cache is cleared
https://bugs.kde.org/show_bug.cgi?id=448750 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #9 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/141 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468882] New: Sidebar shortcut and sidebar button in toolbar not working
https://bugs.kde.org/show_bug.cgi?id=468882 Bug ID: 468882 Summary: Sidebar shortcut and sidebar button in toolbar not working Classification: Applications Product: okular Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: vive.li...@belgacom.net Target Milestone: --- Created attachment 158376 --> https://bugs.kde.org/attachment.cgi?id=158376=edit Screenshot of okular's toolbar configuration Since recent kde gear upgrade, the shortcut to toggle sidebar visibility does not work. Sidebar can still be toggled using the menu Settings -> Show sidebar but the default F7 shortcut does nothing. I have tried using another (custom) shortcut to no avail. Moreover (I suppose this is related) when I right-click on the main toolbar choose Configure toolbars and select "Main Toolbar " I can see in the "Current actions" on the right hand side that there should be a "Show sidebar" button but it does not appear in the actual toolbar. STEPS TO REPRODUCE 1. Open any pdf document in okular 2. Use menu Settings and select or unselect "Show sidebar" as you wish. 3. Use the default F7 shortcut to toggle sidebar OBSERVED RESULT The menu at step 2 makes sidebar visible or not as expected. Nothing happens after step 3. EXPECTED RESULT Side bar should appear or disappear after step 3. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch linux (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION It worked with previous okular version 22.12.3 This does not depends on the display server : it happens both with X11 and Wayland. Other keyboard shortcuts seem to work fine in okular. My keyboard is pc generic 105 keys with belgian layout. The problem persists if I close okular, delete okular's config files ~/.config/okularrc and ~/.config/okularpartrc and restart okular. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468881] New: Timestamps in directorysizes file for Trash shown in milliseconds instead of seconds since epoch
https://bugs.kde.org/show_bug.cgi?id=468881 Bug ID: 468881 Summary: Timestamps in directorysizes file for Trash shown in milliseconds instead of seconds since epoch Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lukas.sp...@web.de Target Milestone: --- SUMMARY When deleting a folder (moving it to trash) in Dolphin or with an icon on the desktop, then the directorysizes file stores a timestamp for that folder's trashinfo file in milliseconds since Epoch. However, according to the freedesktop.org specification, this should be seconds since Epoch: "Directory size cache (...) The modification time is stored as an integer, the number of seconds since Epoch." - https://specifications.freedesktop.org/trash-spec/trashspec-latest.html STEPS TO REPRODUCE 1. Delete a folder in Dolphin or from the desktop. 2. Check the content of the diretorysizes file (~/.local/share/Trash/directorysizes). OBSERVED RESULT The timestamp (second column) is shown in milliseconds since epoch EXPECTED RESULT The timestamp (second column) should be shown in seconds since epoch SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468202] Krita on Android freezes after creating a new document or opening a pre-existing one
https://bugs.kde.org/show_bug.cgi?id=468202 --- Comment #3 from irimescusebastia...@gmail.com --- (In reply to sh_zam from comment #2) > Hi! > > From the description, it seems that you have also tried the "force stop" > app, And it didn't work? When the app is frozen, do you get any dialog from > the system which says something like "The app keeps stopping, Kill? Wait"? Hello! Nope, there's no such dialog. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 indecisiveautoma...@gmail.com changed: What|Removed |Added CC||indecisiveautomator@gmail.c ||om --- Comment #25 from indecisiveautoma...@gmail.com --- FWIW Forcing X11 is not ideal when using a scaled display in a mixed-scale setup, as the window will be blurry. -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 468800] Context menu in search results view for mouse users
https://bugs.kde.org/show_bug.cgi?id=468800 mbruchert changed: What|Removed |Added CC||m...@kaidan.im --- Comment #1 from mbruchert --- (In reply to Eric Armbruster from comment #0) > Hi Jonah, Mathis, and everyone else working on AudioTube, > thanks for this really nice application! > > STEPS TO REPRODUCE > 1. Would be great to have a context menu for mouse users in the search > results view thank you:)) I implemented the right click menu everywhere just now - Mathis -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] On X11, all windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 Gauthier changed: What|Removed |Added CC||g.gue...@posteo.net --- Comment #24 from Gauthier --- I also have an issue along similar lines on Wayland (so also posted there bug 468184) When unpluging my external screen from my laptop, many windows (e.g. firefox and gnucash) are not (or not appropriately) resized when moved to the laptop screen. Specifically they are too heigh with the title bar being out of the screen, meaning I cannot move/minmize/maximize/close them, I have to use the shortcut Ctrl + F5 to move them and then resize manually. External screen is a 34" 3440x1440 whereas laptop screen is 14" 1920x1080 (no scaling applied to either). Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.1.22-060122-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 I have no idea how Kwin handles this currently (and so I don't want to tell dev how to do things) but just in case it's useful, it sounds like a systematic approach when it comes to window size and placement could be: To define window size on any given screen: width ratio = (window width in px / screen width in px) height ratio = (window height in px/ screen height in px) >> those width/height ratios can then be applied to different size screens' >> height / width in plug / unplug events which would conserve the same >> relative window size across any screen (independently of absolute screen >> size or aspect ration). To define windows placement: = horizontal ratio: distance between screen left edge and window horizontal centre / distance between screen left edge and screen horizontal centre (i.e. half screen width) vertical ratio: distance between screen top edge and window vertical centre / distance between screen top edge and screen vertical centre (i.e. half screen height) >> Those ratio can then be applied to the window (horizontal / vertical) centre >> in plug / unplug events so the relative placement is conserved across any >> screens (independently of absolute screen size or aspect ration). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #19 from Maik Qualmann --- Git commit e5d2453880118dfb37e8e3e06577306e4a96b6bb by Maik Qualmann. Committed on 23/04/2023 at 21:26. Pushed by mqualmann into branch 'master'. Workaround when reading the EXV container with ExifTool ExifTool seems to have some strange behavior here, it needs further investigation. M +3-0core/libs/metadataengine/exiftool/exiftoolparser_command.cpp https://invent.kde.org/graphics/digikam/commit/e5d2453880118dfb37e8e3e06577306e4a96b6bb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468184] Kwin moving windows and resizing them very poorly to unusable states on multi-monitor setups during unplug events
https://bugs.kde.org/show_bug.cgi?id=468184 --- Comment #3 from Gauthier --- Also wonder if this is related to the bug 452118, at least they both relate to window resizing on plug / unplug. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453877] Allow multiple simultaneous auth methods to be used without having to fail at one of them, first via multiple PAM stacks
https://bugs.kde.org/show_bug.cgi?id=453877 beedell.rokejulianlockhart changed: What|Removed |Added CC||rokejulianlockhart@outlook. ||com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 --- Comment #5 from Damian C --- I want to add that with the Night Color feature enabled, each time the "kwin_wayland_drm: Failed to create gamma blob! Invalid argument" message shows on the logs, the screen freezes (one of them, the other two won't), and it can completely freeze the kwin session. 3 monitors: One Display Port, one HDMI and one DVI. Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Nvidia Drivers: 530.41.03-1 Workaround has been to disable this feature completely. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468184] Kwin moving windows and resizing them very poorly to unusable states on multi-monitor setups during unplug events
https://bugs.kde.org/show_bug.cgi?id=468184 Gauthier changed: What|Removed |Added CC||g.gue...@posteo.net --- Comment #2 from Gauthier --- I also have an issue along those lines. When unpluging my external screen from my laptop, many windows (e.g. firefox and gnucash) are not (or not appropriately) resized when moved to the laptop screen. Specifically they are too heigh with the title bar being out of the screen, meaning I cannot move/minmize/maximize/close them, I have to use the shortcut Ctrl + F5 to move them and then resize manually. External screen is a 34" 3440x1440 whereas laptop screen is 14" 1920x1080 (no scaling applied to either). Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.1.22-060122-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 I have no idea how Kwin handles this currently (and so I don't want to tell dev how to do things) but just in case it's useful, it sounds like a systematic approach when it comes to window size and placement could be: To define window size on any given screen: width ratio = (window width in px / screen width in px) height ratio = (window height in px/ screen height in px) >> those width/height ratios can then be applied to different size screens' >> height / width in plug / unplug events which would conserve the same >> relative window size across any screen (independently of absolute screen >> size or aspect ration). To define windows placement: = horizontal ratio: distance between screen left edge and window horizontal centre / distance between screen left edge and screen horizontal centre (i.e. half screen width) vertical ratio: distance between screen top edge and window vertical centre / distance between screen top edge and screen vertical centre (i.e. half screen height) >> those ratio can then be applied to the window (horizontal / vertical) centre >> in plug / unplug events so the relative placement is conserved across any >> screens (independently of absolute screen size or aspect ration). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 beedell.rokejulianlockhart changed: What|Removed |Added CC||rokejulianlockhart@outlook. ||com -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 466063] Kalendar crashes when unlocking
https://bugs.kde.org/show_bug.cgi?id=466063 Carl Schwan changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |kalendar/commit/c925a526ceb |kalendar/commit/a5264b1cf75 |89d78514ead777576987b620cc5 |2ac5cc7ec641b09b586db1d070f |16 |0b --- Comment #16 from Carl Schwan --- Git commit a5264b1cf752ac5cc7ec641b09b586db1d070f0b by Carl Schwan. Committed on 23/04/2023 at 21:10. Pushed by carlschwan into branch 'release/23.04'. Fix crashes in incidenceoccurrencemodel The cause for these crashes is that the QPersistentModelIndex get invalided at some point and then the row is -1 which is invalid. This is probably caused by bugs somewhere in ETMCalendar. The previous code which tried to only update part of the model, which in theory should be faster was wrong since a dataChanged on the source model could result in less or more entry due to the recurrence rules changing or in a different hash due to the start or end date changing. (cherry picked from commit c925a526ceb89d78514ead777576987b620cc516) M +5-132 src/models/incidenceoccurrencemodel.cpp M +0-6src/models/incidenceoccurrencemodel.h https://invent.kde.org/pim/kalendar/commit/a5264b1cf752ac5cc7ec641b09b586db1d070f0b -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 466063] Kalendar crashes when unlocking
https://bugs.kde.org/show_bug.cgi?id=466063 Carl Schwan changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||kalendar/commit/c925a526ceb ||89d78514ead777576987b620cc5 ||16 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #15 from Carl Schwan --- Git commit c925a526ceb89d78514ead777576987b620cc516 by Carl Schwan. Committed on 23/04/2023 at 14:43. Pushed by carlschwan into branch 'master'. Fix crashes in incidenceoccurrencemodel The cause for these crashes is that the QPersistentModelIndex get invalided at some point and then the row is -1 which is invalid. This is probably caused by bugs somewhere in ETMCalendar. The previous code which tried to only update part of the model, which in theory should be faster was wrong since a dataChanged on the source model could result in less or more entry due to the recurrence rules changing or in a different hash due to the start or end date changing. M +5-132 src/models/incidenceoccurrencemodel.cpp M +0-6src/models/incidenceoccurrencemodel.h https://invent.kde.org/pim/kalendar/commit/c925a526ceb89d78514ead777576987b620cc516 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468880] New: Random kwin freezes
https://bugs.kde.org/show_bug.cgi?id=468880 Bug ID: 468880 Summary: Random kwin freezes Classification: Plasma Product: kwin Version: 5.27.4 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: retratse...@gmail.com Target Milestone: --- SUMMARY *** After upgrading to 5.27 I experience random kwin_x11 freezes multiple times a day. It hapens on my two different laptops with different cpu and gpu, so it's not hardware related. Content of last active window may remain interactive but I can not switch to other windows. I have to switch into tty terminal with ctrl+alt+f2, kill kwin with pkill -9 -f kwin (without -9 it doesn terminate) and then return back to desktop session (kwin restarts automatically). I have no exact way to reproduce, it just happens randomly. But on both machines apps I often use are Firefox, Kate, Krusader, Thunderbird, Konsole, Discord. I've recorded a strace log if it's helpful https://pastebin.com/LqRmaaSd When wreezed, strace stops printing anything. These are last 30 lines after freeze. *** SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27 (22.04 jammy) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.18 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468879] No feedback when importing large collection
https://bugs.kde.org/show_bug.cgi?id=468879 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Albums-Engine |Database-Scan Platform|Other |openSUSE -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468878] Different view modes in split mode?
https://bugs.kde.org/show_bug.cgi?id=468878 --- Comment #1 from w...@mail.ru --- I forgot to mention that 1) it applies not only to split views but also to tabs 2) it applies not only to view modes but also to sorting methods (sort by name, modified date...) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468879] New: No feedback when importing large collection
https://bugs.kde.org/show_bug.cgi?id=468879 Bug ID: 468879 Summary: No feedback when importing large collection Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Engine Assignee: digikam-bugs-n...@kde.org Reporter: espinosa...@centrum.cz Target Milestone: --- Created attachment 158375 --> https://bugs.kde.org/attachment.cgi?id=158375=edit Digikam shows no user feedback when importing a new large collection SUMMARY There is no feedback back to the user that the import is being done. Import of a large collection can take many minutes and during all this time user is left completely in dark if process failed, or if it still running; if something is happening at all. Very poor UX experience. Can put off people from using Digikam on the very start. Even worse, the import progress dialog announced "Processing is done", duration 00:00:00. Clearly a bug there. Same happens if I do "refresh" of Album during the "invisible" import. The only indication of the import in fact being under way were slowly, very slowly, appearing subdirectories under my new album. I would expect some kind of hour-glass or rotating gears. Even better, explicit indication, ideally in some non-modal view, telling me that import is being done and what directory is being processed right now. STEPS TO REPRODUCE 1. Find a large collection, mine is 237 GiB and with over 47K files. Non-removable media. Even on fast NVMe SSD it can take 15 min for Digikam to import (hart to tell how long exactly for obvious reasons) 2. Settings -> Collections -> Root Album Folders -> Add Collection 3. Hit OK OBSERVED RESULT 4. Import dialog tells you that job is done and soon disappears. But you don't see any of your collection files and directories, leaving you baffled what is happing and if you did something wrong. 5. Album (collection) subdirectories and files start to slowly appear. EXPECTED RESULT I would expect some kind of hour-glass or rotating gears. Even better, explicit indication, ideally in some non-modal view, telling me that import is being done and what directory is being processed right now. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Thumbleweed, all up-to date, all latest versions. (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 (X11) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467583] Auto tiling
https://bugs.kde.org/show_bug.cgi?id=467583 Tilmann Meyer changed: What|Removed |Added CC||m...@atiltedtree.dev -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 aron...@gmail.com changed: What|Removed |Added CC||aron...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #18 from Maik Qualmann --- I see one thing about the GPS information, it exists in EXifTool but doesn't seem to be carried over. I'll look at that tomorrow. But keep in mind that your image metadata is not valid beforehand. exiftool -validate -warning -error -a 2023-04-22_111500_7DMkII_0001_BEFORE.jpg Validate: 4 Warnings (3 minor) Warning : [minor] Invalid date/time format for XMP:DateCreated Warning : [minor] IPTC ApplicationRecordVersion too short (0 bytes; should be 2) Warning : [minor] IPTC DateCreated too long (20 bytes; should be 8) Warning : Missing required JPEG IFD0 tag 0x0213 YCbCrPositioning Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #17 from Galen Adams --- Sorry, I was sending the previous when another message came in. The GPS is written into the files by the camera. All other data is written into the files; not just floating around in some database. It is all there until I happen to decide to edit a KeyWord Tag and then it disappears. On Sun, Apr 23, 2023 at 3:30 PM Galen Adams wrote: > If that be the case, why then can I view all the data in the BEFOREs and > not see any IPTC or GPS data at all in the AFTERs; the GPS "Globe" > indicator in digiKam even disappears from the AFTERs. > The GPS is completely stripped from Windows "Properties" in the AFTERs and > disappears in FastStone; it is all there in the BEFOREs. > > If digiKam "repaired" the images, why then is that repair not evident in > any other program ? > > I am thoroughly confused and at a loss as I am not doing anything > different than I have been doing for ages and never had this before. > > > > > On Sun, Apr 23, 2023 at 3:08 PM Maik Qualmann > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=468832 >> >> --- Comment #14 from Maik Qualmann --- >> Galen, you're completely confusing something. Please check it out again. >> Your >> IPTC and GPS before images have no metadata whatsoever. >> Your other before images have different metadata errors where Exiv2 fails, >> invalid date format, unexpected GPS info pointer etc. In such a case we >> read >> the metadata with ExifTool. >> All your before pics are more or less broken, your after pics even have >> IPTC >> tags. >> >> Check if ExifTool works for you (ExifTool tab in sidebar shows metadata. >> >> With these sample images, digiKam-8.0.0 repaired your images rather than >> destroying them. >> >> Maik >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 --- Comment #9 from Steve Cossette --- (In reply to Steve Cossette from comment #8) > Just a headsup, the brand new 1.0.1 version still behaves exactly the same For some reason, this crash doesn't occur on my second machine, so honestly I don't know what to think of this. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #16 from Galen Adams --- If that be the case, why then can I view all the data in the BEFOREs and not see any IPTC or GPS data at all in the AFTERs; the GPS "Globe" indicator in digiKam even disappears from the AFTERs. The GPS is completely stripped from Windows "Properties" in the AFTERs and disappears in FastStone; it is all there in the BEFOREs. If digiKam "repaired" the images, why then is that repair not evident in any other program ? I am thoroughly confused and at a loss as I am not doing anything different than I have been doing for ages and never had this before. On Sun, Apr 23, 2023 at 3:08 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468832 > > --- Comment #14 from Maik Qualmann --- > Galen, you're completely confusing something. Please check it out again. > Your > IPTC and GPS before images have no metadata whatsoever. > Your other before images have different metadata errors where Exiv2 fails, > invalid date format, unexpected GPS info pointer etc. In such a case we > read > the metadata with ExifTool. > All your before pics are more or less broken, your after pics even have > IPTC > tags. > > Check if ExifTool works for you (ExifTool tab in sidebar shows metadata. > > With these sample images, digiKam-8.0.0 repaired your images rather than > destroying them. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442349] Folder /Pictures/DigiCam which contains all pictures suddenly changed to file digiKam.
https://bugs.kde.org/show_bug.cgi?id=442349 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.1.0 Resolution|--- |FIXED Summary|folder /Pictures/DigiCam|Folder /Pictures/DigiCam |which contains all pictures |which contains all pictures |suddenly changed to file|suddenly changed to file |digikam |digiKam. Status|REPORTED|RESOLVED --- Comment #4 from caulier.gil...@gmail.com --- Michael Abramov Pièces jointes20:48 (il y a 1 heure) À moi Traduire le message Désactiver pour : anglais Hello Gilles Recently I upgraded my laptop to Ubuntu 22.04.2 LTS and also digiKam to ver. 7.8.0, until now i did not faced any problem. Hope it will serve me better. Thank you for asking, Best regards Michael Sincerely, Mobile:+972-525237549 Fax: 153-2-5730243 P.O.B.: 573, Giv’at Ze’ev E-mail: mabramov@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468878] New: Different view modes in split mode?
https://bugs.kde.org/show_bug.cgi?id=468878 Bug ID: 468878 Summary: Different view modes in split mode? Classification: Applications Product: dolphin Version: 23.04.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: w...@mail.ru CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open dolphin in split mode 2. set different view modes (i e right view in icons view, left one in detailed list 3. try to navigate in both views OBSERVED RESULT when changing directory, view switches to the last applied mode EXPECTED RESULT view remembers its mode and stays in it until closed SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.18.5 ADDITIONAL INFORMATION i see that this bug is a duplicate of the one from 2012 but it looks like its forgotten, and i guess really a lot of people would like the "expected result" behaviour. If i get some adviсes (at least what src file should i look into) i would like to try to implement this myself -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #15 from Maik Qualmann --- As an example, if you have set GPS data at some older point and not written to the images and now delete tags that also only exist in the database and have activated the option to reread metadata on file change, your GPS information will disappear from the database. You should first write the metadata from the database to the images if writing metadata is activated in the settings. For older bugs where metadata wasn't written to images, we can't fix them today. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #14 from Maik Qualmann --- Galen, you're completely confusing something. Please check it out again. Your IPTC and GPS before images have no metadata whatsoever. Your other before images have different metadata errors where Exiv2 fails, invalid date format, unexpected GPS info pointer etc. In such a case we read the metadata with ExifTool. All your before pics are more or less broken, your after pics even have IPTC tags. Check if ExifTool works for you (ExifTool tab in sidebar shows metadata. With these sample images, digiKam-8.0.0 repaired your images rather than destroying them. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 468877] New: Wrong / Blank Sensor Names
https://bugs.kde.org/show_bug.cgi?id=468877 Bug ID: 468877 Summary: Wrong / Blank Sensor Names Classification: Applications Product: plasma-systemmonitor Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: gbug222...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 158372 --> https://bugs.kde.org/attachment.cgi?id=158372=edit Video of issue SUMMARY Clicking on some sensors will pull up totally different sensors and change the name of them in the list, or pull up a sensor with no name that disappears when the configuration is saved. STEPS TO REPRODUCE 1. Create a new system monitor sensor. 2. Try to add random sensors OBSERVED RESULT Wrong or blank sensor names EXPECTED RESULT Correct sensors SOFTWARE/OS VERSIONS Kernal: 6.2.12-arch1-1 (64-bit) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468146] Discrepancy in Game Framerate Perception and Reported FPS Graphs, VSync magic behaviour.
https://bugs.kde.org/show_bug.cgi?id=468146 --- Comment #11 from Edgars --- (In reply to Zamundaaa from comment #10) > Okay, then it's a different thing from the amd bug. > Does anything change if you set the latency policy to balanced (which was > the default in 5.26)? Didn't help, nothing changed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #5 from Galen Adams --- There are three BEFORE that should still have all data intact and three AFTER that got all IPTC and GPS stripped when editing a KeyWord Tag. Previous versions of digiKam never did this. I am using version digiKam-8.0.0-20230330T081758-Win64-debug I will attempt to get a debug log if I can figure out how. Thanks. [image: 2023-04-22_111500_7DMkII_0001_BEFORE.jpg] [image: 2023-04-22_111501_7DMkII_0002_AFTER.jpg] [image: 2023-04-22_111501_7DMkII_0002_BEFORE.jpg] [image: 2023-04-22_111530_7DMkII_0003_AFTER.jpg] [image: 2023-04-22_111530_7DMkII_0003_BEFORE.jpg] [image: AFTER.jpg] [image: GPS_Before.jpg] [image: IPTC_Before.jpg] [image: 2023-04-22_111500_7DMkII_0001_AFTER.jpg] On Sun, Apr 23, 2023 at 12:03 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468832 > > --- Comment #4 from Maik Qualmann --- > Please also create a DebugView log. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #6 from Galen Adams --- Created attachment 158364 --> https://bugs.kde.org/attachment.cgi?id=158364=edit 2023-04-22_111500_7DMkII_0001_BEFORE.jpg --- Comment #7 from Galen Adams --- Created attachment 158365 --> https://bugs.kde.org/attachment.cgi?id=158365=edit 2023-04-22_111501_7DMkII_0002_AFTER.jpg --- Comment #8 from Galen Adams --- Created attachment 158366 --> https://bugs.kde.org/attachment.cgi?id=158366=edit 2023-04-22_111501_7DMkII_0002_BEFORE.jpg --- Comment #9 from Galen Adams --- Created attachment 158367 --> https://bugs.kde.org/attachment.cgi?id=158367=edit 2023-04-22_111530_7DMkII_0003_AFTER.jpg --- Comment #10 from Galen Adams --- Created attachment 158368 --> https://bugs.kde.org/attachment.cgi?id=158368=edit 2023-04-22_111530_7DMkII_0003_BEFORE.jpg --- Comment #11 from Galen Adams --- Created attachment 158369 --> https://bugs.kde.org/attachment.cgi?id=158369=edit AFTER.jpg --- Comment #12 from Galen Adams --- Created attachment 158370 --> https://bugs.kde.org/attachment.cgi?id=158370=edit GPS_Before.jpg --- Comment #13 from Galen Adams --- Created attachment 158371 --> https://bugs.kde.org/attachment.cgi?id=158371=edit IPTC_Before.jpg -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360714] JPGEG2000 thumbnails shows as dimension 0x0 pixel - Use ExifTool to get right image properties
https://bugs.kde.org/show_bug.cgi?id=360714 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||8.1.0 Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/0f90a22 ||e71b36c95aed5a200a17a8e5ec8 ||0fd46e --- Comment #31 from Maik Qualmann --- Git commit 0f90a22e71b36c95aed5a200a17a8e5ec80fd46e by Maik Qualmann. Committed on 23/04/2023 at 19:40. Pushed by mqualmann into branch 'master'. with libjasper >= 3 we read the image metadata The broken test samples from libjasper repository are processed without crashing. FIXED-IN: 8.1.0 M +1-1NEWS M +20 -1core/dplugins/dimg/jpeg2000/dimgjpeg2000loader_load.cpp https://invent.kde.org/graphics/digikam/commit/0f90a22e71b36c95aed5a200a17a8e5ec80fd46e -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468788] Option to disable the new Spectacle toolbar (annotation tools)
https://bugs.kde.org/show_bug.cgi?id=468788 incom...@frogg.ie changed: What|Removed |Added CC||incom...@frogg.ie --- Comment #1 from incom...@frogg.ie --- A CLI option for this would also be nice, as I use Spectacle in a CLI screenshot script that's bound to my screenshot key. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468874] Using background mode with `-b` to hide the GUI and just save to a file with `-o` no longer works with `-region`.
https://bugs.kde.org/show_bug.cgi?id=468874 incom...@frogg.ie changed: What|Removed |Added Resolution|WAITINGFORINFO |INTENTIONAL Status|NEEDSINFO |RESOLVED --- Comment #2 from incom...@frogg.ie --- Ah, my screenshot tool had `-region` hardcoded as an option, I'm assuming it was being parsed as `-r` previously and worked just fine, using `-r` or `--region` works just fine now! Thank you for letting me know :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468875] Crash when opening Flatpak Permissions KCM
https://bugs.kde.org/show_bug.cgi?id=468875 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 468212] Clicking an Artist's name when viewing an Album should add to the ContentView's history
https://bugs.kde.org/show_bug.cgi?id=468212 Mel changed: What|Removed |Added CC||a...@melissaautumn.com --- Comment #3 from Mel --- I looked into this and it seems to be intentional. In `ViewManager::openChildView` there's a loop that checks to see if the upcoming view is the same type (e.g. album, artist, genre...) as the current view. If it's not it override the upcoming view with the generic base view of the new type. (Causing this exact issue, where the Album view pops up and then the specific artist's album list shows a second later.) Removing that loop resolves this issue, and fixes a lot of weird navigation issues. However this can also create a situation where if you click on the Artist a bunch of times, it will just keep appending that view to the history. If this sounds like a good change to the maintainers, I can get a merge request up with that loop removal, and a infinite history fix. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468876] Display more image properties
https://bugs.kde.org/show_bug.cgi?id=468876 --- Comment #1 from Christopher Yeleighton --- Also, MIME type is obsolete and should be replaced by Media type. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 441057] Support 60% Charge Limit threshold for Lenovo Ideapad and Legion laptops
https://bugs.kde.org/show_bug.cgi?id=441057 FreeLibre changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 441057] Support 60% Charge Limit threshold for Lenovo Ideapad and Legion laptops
https://bugs.kde.org/show_bug.cgi?id=441057 FreeLibre changed: What|Removed |Added CC|n...@kde.org| -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 441057] Support 60% Charge Limit threshold for Lenovo Ideapad and Legion laptops
https://bugs.kde.org/show_bug.cgi?id=441057 FreeLibre changed: What|Removed |Added CC||mysignu...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 464689] Add more relevant document properties in Properties dialog
https://bugs.kde.org/show_bug.cgi?id=464689 Christopher Yeleighton changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=468876 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468876] Display more image properties
https://bugs.kde.org/show_bug.cgi?id=468876 Christopher Yeleighton changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=464689 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468876] New: Display more image properties
https://bugs.kde.org/show_bug.cgi?id=468876 Bug ID: 468876 Summary: Display more image properties Classification: Applications Product: okular Version: 22.12.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Image backend components Assignee: okular-de...@kde.org Reporter: giecr...@stegny.2a.pl Target Milestone: --- Created attachment 158362 --> https://bugs.kde.org/attachment.cgi?id=158362=edit A JPEG image with an embedded comment. The Properties window does not display JPEG Comment for the current image. STEPS TO REPRODUCE 1. Open file rose.jpg! 2. Open properties! OBSERVED RESULT Path: rose.jpg Size: 2.6 KiB Pages: 1 MIME type: JPEG image (image/jpeg) EXPECTED RESULT Path: rose.jpg Size: 2.6 KiB Pages: 1 MIME type: JPEG image (image/jpeg) Comment: A red rose flower. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed 20230421 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468875] Crash when opening Flatpak Permissions KCM
https://bugs.kde.org/show_bug.cgi?id=468875 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
