[digikam] [Bug 471489] Unable to move gif files to trash
https://bugs.kde.org/show_bug.cgi?id=471489 --- Comment #4 from thelittlest...@foxmail.com --- (In reply to caulier.gilles from comment #3) > Did you open the gif file in another application (as VLC for ex) to display > contents ? If yes, the file must be locked by windows. I'm sure that no another application occupied the file. I guess digiKam's own preview function occupied the file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375420] Auto-hide inactive cursor
https://bugs.kde.org/show_bug.cgi?id=375420 Anya Smith changed: What|Removed |Added CC||anantann...@gmail.com --- Comment #5 from Anya Smith --- Unfortunate that this won't be implemented for Wayland. Other Wayland compositors, such as Sway, have implemented it long ago. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471489] Unable to move gif files to trash
https://bugs.kde.org/show_bug.cgi?id=471489 --- Comment #3 from caulier.gil...@gmail.com --- Did you open the gif file in another application (as VLC for ex) to display contents ? If yes, the file must be locked by windows. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471489] Unable to move gif files to trash
https://bugs.kde.org/show_bug.cgi?id=471489 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |8.0.0 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471489] Unable to move gif files to trash
https://bugs.kde.org/show_bug.cgi?id=471489 --- Comment #2 from thelittlest...@foxmail.com --- (In reply to caulier.gilles from comment #1) > Which digiKam version did you use ? > > When you talk about trash, it's about the internal digiKam trash or the > Windows bin recycler ? 1. Both 7.10.0 & 8.0.0 have this problem 2. Internal difiKam trash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471489] Unable to move gif files to trash
https://bugs.kde.org/show_bug.cgi?id=471489 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Which digiKam version did you use ? When you talk about trash, it's about the internal digiKam trash or the Windows bin recycler ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471454] Dolphin icon disappears from the task manager during data transfer
https://bugs.kde.org/show_bug.cgi?id=471454 Justin Zobel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||justin.zo...@gmail.com --- Comment #1 from Justin Zobel --- This is an issue with shaders as the icon has a badge while transferring. *** This bug has been marked as a duplicate of bug 470600 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470600] Task Manager icons disappear when badged due to unported shader effect
https://bugs.kde.org/show_bug.cgi?id=470600 Justin Zobel changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Justin Zobel --- *** Bug 471454 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 471490] New: Website mentioned in templete was modified maliciously
https://bugs.kde.org/show_bug.cgi?id=471490 Bug ID: 471490 Summary: Website mentioned in templete was modified maliciously Classification: Websites Product: bugs.kde.org Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: major Priority: NOR Component: templates Assignee: sysad...@kde.org Reporter: thelittlest...@foxmail.com CC: she...@kde.org 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. https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports 2. The website has been maliciously modified 3. OBSERVED RESULT Large amount of junk contents EXPECTED RESULT Useful contents SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471489] New: Unable to move gif files to trash
https://bugs.kde.org/show_bug.cgi?id=471489 Bug ID: 471489 Summary: Unable to move gif files to trash Classification: Applications Product: digikam Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Albums-Trash Assignee: digikam-bugs-n...@kde.org Reporter: thelittlest...@foxmail.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. Choose one gif file and open it in Preview mode(window) 2. Press Delete key then confirm moving files to trash 3. If the file is still playing, the file will can't be moved to trash 4. But if the playing is complete, this gif file will be deleted successfully I think the preview system is still occupying the file even when moving the file. I did not test other file formats, but this problem may be widespread in dynamic image formats. OBSERVED RESULT Program warns failed to move file to trash EXPECTED RESULT Move the file to trash successfully even the file preview is still playing. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470090] [Wayland][Nvidia?] Ksplashqml, plasma and systemsettings crash on login
https://bugs.kde.org/show_bug.cgi?id=470090 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|UNMAINTAINED|WORKSFORME --- Comment #18 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.
[kwin] [Bug 437925] Crash in BlurEffect::blurRegion
https://bugs.kde.org/show_bug.cgi?id=437925 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #12 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.
[kwin] [Bug 470898] resource leak: the number of threads increases over time, boundlessly
https://bugs.kde.org/show_bug.cgi?id=470898 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471488] Add shortcuts for half-page scrolling
https://bugs.kde.org/show_bug.cgi?id=471488 beavailable changed: What|Removed |Added CC||beavaila...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471488] New: Add shortcuts for half-page scrolling
https://bugs.kde.org/show_bug.cgi?id=471488 Bug ID: 471488 Summary: Add shortcuts for half-page scrolling Classification: Applications Product: okular Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: beavaila...@proton.me Target Milestone: --- Like vim, if okular could scroll half-page with D and U it will be more convenient to use. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471487] Mounting ISO doesn't update Places panel until Dolphin gets restarted
https://bugs.kde.org/show_bug.cgi?id=471487 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413709] krunner searches for the text suggested by auto-completion before actually accepting the suggestion
https://bugs.kde.org/show_bug.cgi?id=413709 Alexander Lohnau changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/2f440982378a7e11d4659493a ||978fbd1ebd107bd Version Fixed In||6.0 Resolution|--- |FIXED --- Comment #11 from Alexander Lohnau --- Git commit 2f440982378a7e11d4659493a978fbd1ebd107bd by Alexander Lohnau. Committed on 27/06/2023 at 00:59. Pushed by alex into branch 'master'. krunner: Show suggestions as grayed out text, press arrow-right to apply This way, we do not apply a suggestion without asking the user for it. Using the grayed out text, it is made clear to the user what the suggestion is. Because the old behavior is desirable for existing users, it is still kept as an option. The code required for it is minimal anyway. FIXED-IN: 6.0 M +29 -1krunner/qml/RunCommand.qml M +5-2krunner/view.cpp M +19 -0krunner/view.h https://invent.kde.org/plasma/plasma-workspace/-/commit/2f440982378a7e11d4659493a978fbd1ebd107bd -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471487] New: Mounting ISO doesn't update Places panel until Dolphin gets restarted
https://bugs.kde.org/show_bug.cgi?id=471487 Bug ID: 471487 Summary: Mounting ISO doesn't update Places panel until Dolphin gets restarted Classification: Applications Product: dolphin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins: ISO mounting Assignee: kwon-young.c...@hotmail.fr Reporter: guimarcalsi...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY You have to restart Dolphin after mounting an ISO image if you want to see it listed on the Places panel. STEPS TO REPRODUCE 1. Mount an ISO with Dolphin using the context menu (needs the dolphin-plugins package) OBSERVED RESULT Nothing visible will happen on the Places panel. You have to restart Dolphin to see the newly mounted ISO there. EXPECTED RESULT Dolphin should update the Places panel as soon as the ISO gets mounted without the need to restart it. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 5.19.0-45-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471296] Files on desktop do not have a preview due to lack of Qt6-based kio-extras
https://bugs.kde.org/show_bug.cgi?id=471296 --- Comment #10 from Patrick Silva --- ffmpegthumbs and kdegraphics-thumbnailers packages are installed, .heic file has preview after re-login. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471486] New: kio-gdrive not installed by default on KDE Neon
https://bugs.kde.org/show_bug.cgi?id=471486 Bug ID: 471486 Summary: kio-gdrive not installed by default on KDE Neon Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: guimarcalsi...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY KDE itself recommends shipping kio-gdrive in the wiki (https://community.kde.org/Distributions/Packaging_Recommendations). Unfortunately, it's not installed by default on KDE Neon, making the Online Accounts feature on System Settings significantly less useful. STEPS TO REPRODUCE 1. Make a fresh install of KDE Neon 2. Log into a Google Account OBSERVED RESULT Nothing happens EXPECTED RESULT Google Drive files are listed in Dolphin SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 5.19.0-45-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471485] New: ffmpegthumbs not installed by default on KDE Neon
https://bugs.kde.org/show_bug.cgi?id=471485 Bug ID: 471485 Summary: ffmpegthumbs not installed by default on KDE Neon Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: guimarcalsi...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Dolphin on KDE Neon, by default, doesn't show video thumbnails. The issue is resolved by installing ffmpegthumbs with "sudo apt install ffmpegthumbs" and enabling it in Dolphin. Considering that KDE's own Wiki recommends shipping it by default, it makes sense it should be part of the Neon ISO as well. STEPS TO REPRODUCE 1. Make a fresh install of Neon 2. Access a folder with videos with Dolphin OBSERVED RESULT No thumbnails are generated EXPECTED RESULT Thumbnails should be generated without having to resort to installing additional packages SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 5.19.0-45-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 447277] Missing power profile functionality due to power-profiles-daemon not being installed by default
https://bugs.kde.org/show_bug.cgi?id=447277 guimarcalsi...@gmail.com changed: What|Removed |Added CC||guimarcalsi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 447277] Missing power profile functionality due to power-profiles-daemon not being installed by default
https://bugs.kde.org/show_bug.cgi?id=447277 guimarcalsi...@gmail.com changed: What|Removed |Added Component|Packages Testing Edition|Packages User Edition -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 447277] Missing power profile functionality due to power-profiles-daemon not being installed by default
https://bugs.kde.org/show_bug.cgi?id=447277 guimarcalsi...@gmail.com changed: What|Removed |Added Summary|Missing power profile |Missing power profile |functionality |functionality due to ||power-profiles-daemon not ||being installed by default -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 447277] Missing power profile functionality
https://bugs.kde.org/show_bug.cgi?id=447277 guimarcalsi...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from guimarcalsi...@gmail.com --- I can confirm power profiles are missing on a brand-new Neon Stable 5.27.6 install. The problem is resolved running "sudo apt install power-profiles-daemon" and restarting. power-profiles-daemon should be installed by default on the ISO. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 471484] New: Kamoso crashes when trying to open Kamoso a second time
https://bugs.kde.org/show_bug.cgi?id=471484
Bug ID: 471484
Summary: Kamoso crashes when trying to open Kamoso a second
time
Classification: Applications
Product: kamoso
Version: 23.04.2
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: aleix...@kde.org
Reporter: antti.s...@gmail.com
Target Milestone: ---
Application: kamoso (23.04.2)
Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.3.8-arch1-1-bcachefs-git x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.6 [KCrashBackend]
-- Information about the crash:
Simply opening Kamoso several times causes Kamoso to crash. Might be a
duplicate of #459700 as the first instance of Kamoso hogs the camera to itself
The crash can be reproduced sometimes.
-- Backtrace:
Application: Kamoso (kamoso), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fac82129f82 in g_type_check_instance_is_fundamentally_a
(type_instance=0x55fed0361f30, fundamental_type=0x50 [None]) at
../glib/gobject/gtype.c:4167
#7 0x7fac82114b0d in g_object_notify (object=0x55fed0361f30,
property_name=0x7fac5e4ba989 "zoom") at ../glib/gobject/gobject.c:1584
#8 0x7fac821036c0 in g_closure_invoke (closure=0x55fecfdfb750,
return_value=0x0, n_param_values=2, param_values=0x7ffeac69d500,
invocation_hint=0x7ffeac69d480) at ../glib/gobject/gclosure.c:832
#9 0x7fac82131938 in signal_emit_unlocked_R.isra.0
(node=node@entry=0x55fecf3dd3d0, detail=detail@entry=2843,
instance=instance@entry=0x55fecfcd7230,
emission_return=emission_return@entry=0x0,
instance_and_params=instance_and_params@entry=0x7ffeac69d500) at
../glib/gobject/gsignal.c:3812
#10 0x7fac82122aa7 in g_signal_emit_valist (instance=,
signal_id=, detail=,
var_args=var_args@entry=0x7ffeac69d6c0) at ../glib/gobject/gsignal.c:3565
#11 0x7fac82122d34 in g_signal_emit (instance=,
signal_id=, detail=) at
../glib/gobject/gsignal.c:3622
#12 0x7fac8210e636 in g_object_dispatch_properties_changed
(object=0x55fecfcd7230, n_pspecs=, pspecs=) at
../glib/gobject/gobject.c:1428
#13 0x7fac80ae7dc8 in gst_object_dispatch_properties_changed
(object=0x55fecfcd7230, n_pspecs=1, pspecs=0x7ffeac69d830) at
../gstreamer/subprojects/gstreamer/gst/gstobject.c:455
#14 0x7fac82103c72 in g_object_notify_queue_thaw (object=0x55fecfcd7230,
nqueue=) at ../glib/gobject/gobject.c:359
#15 0x7fac82116856 in g_object_set_valist (var_args=0x7ffeac69d9c0,
first_property_name=, object=) at
../glib/gobject/gobject.c:2793
#16 g_object_set_valist (object=, first_property_name=, var_args=0x7ffeac69d9c0) at ../glib/gobject/gobject.c:2742
#17 0x7fac82116c99 in g_object_set (_object=0x55fecfcd7230,
first_property_name=first_property_name@entry=0x7fac5e4ba989 "zoom") at
../glib/gobject/gobject.c:2957
#18 0x7fac5e4b64e9 in gst_camera_bin_create_elements (camera=0x55fecfd78b70
[GstCameraBin|camerabin]) at
../gstreamer/subprojects/gst-plugins-bad/gst/camerabin2/gstcamerabin2.c:1742
#19 gst_camera_bin_change_state (element=0x55fecfd78b70 [GstElement|camerabin],
trans=GST_STATE_CHANGE_NULL_TO_READY) at
../gstreamer/subprojects/gst-plugins-bad/gst/camerabin2/gstcamerabin2.c:1891
#20 0x7fac80b1732f in gst_element_change_state
(element=element@entry=0x55fecfd78b70 [GstElement|camerabin],
transition=transition@entry=GST_STATE_CHANGE_NULL_TO_READY) at
../gstreamer/subprojects/gstreamer/gst/gstelement.c:3093
#21 0x7fac80b178f6 in gst_element_set_state_func (element=0x55fecfd78b70
[GstElement|camerabin], state=GST_STATE_READY) at
../gstreamer/subprojects/gstreamer/gst/gstelement.c:3047
#22 0x55fece41dc97 in WebcamControl::playDevice(Device*)
(this=0x7ffeac69e120, device=0x55fecf8a1940) at
/usr/include/qt/QtCore/qscopedpointer.h:138
#23 0x55fece41f07a in WebcamControl::onBusMessage(_GstMessage*)
(message=, this=) at
/usr/src/debug/kamoso/kamoso-23.04.2/src/video/webcamcontrol.cpp:308
#24 webcamWatch(GstBus*, GstMessage*, gpointer) (message=,
user_data=0x7ffeac69e120) at
/usr/src/debug/kamoso/kamoso-23.04.2/src/video/webcamcontrol.cpp:244
#25 0x7fac80afea28 in gst_bus_source_dispatch (source=0x55fecfcf7fe0,
callback=0x55fece41ee00 ,
user_data=0x7ffeac69e120) at
../gstreamer/subprojects/gstreamer/gst/gstbus.c:821
#26 0x7fac809b9981 in g_main_dispatch (context=0x7fac74000ee0) at
../glib/glib/gmain.c:3460
#27 g_main_context_dispatch (context=0x7fac74000ee0) at
../glib/glib/gmain.c:4200
#28 0x7fac80a16b39 in g_main_context_iterate.isra.0
(context=context@entry=0x7fac74000ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#29 0x7fac809b7032 in g_main_context_iteration (context=0x7fac74000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#30
[kwin] [Bug 452119] With an Intel iGPU, animations aren't as smooth on Wayland versus Xorg
https://bugs.kde.org/show_bug.cgi?id=452119 --- Comment #60 from medin --- (In reply to Nate Graham from comment #58) > ...And if the issue does go away with that effect disabled, then the issue > was probably Bug 469151 which has just been fixed! It doesn't differ too much with Background contrast effect, on the other hand it seems disabling Blur makes really animations much smoother, especially with Task Manager thumbnails. And one thing to note is that mouse lagging seems to be somehow improved without needing to add KWIN_DRM_NO_AMS=1 as env var. The problem is that Wayland when idle looks good and smooth but starts to greatly slow down animations when you open some apps, and some apps are randomly frozen (grayed effect) and you need to wait for them to finish their works, I don't know if it's coming from my weak CPU, but on X11 the balance between heavy loading and animations seems much better handled than Wayland. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471483] New: Problems with C1 control codes (U+0080 through U+009F)
https://bugs.kde.org/show_bug.cgi?id=471483 Bug ID: 471483 Summary: Problems with C1 control codes (U+0080 through U+009F) Classification: Applications Product: konsole Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: f.heckenb...@fh-soft.de Target Milestone: --- Konsole recently (apparently between versions 20 and 22) added support for 8-bit C1 control codes (U+0080 through U+009F). While formally correct, in practice it seems to cause more problems than benefits: On the one hand, I don't know any application that actually outputs these characters. Wikipedia (https://en.wikipedia.org/wiki/C0_and_C1_control_codes) seems to agree: "the 8-bit forms of these codes are almost never used. CSI, DCS and OSC are used to control text terminals and terminal emulators, but almost always by using their 7-bit escape code representations." On the other hand, they can actively cause problems (which contributed to their not being used much). In previous times, there were issues in not 8-bit-clean environments; these days rather with UTF-8. To quote Wikipedia again, "the UTF-8 encodings of their corresponding codepoints are two bytes long like their escape code forms (for instance, CSI at U+009B is encoded as the bytes 0xC2, 0x9B in UTF-8), so there is no advantage to using them rather than the equivalent two-byte escape sequence. When these codes appear in modern documents, web pages, e-mail messages, etc., they are usually intended to be printing characters at that position in a proprietary encoding such as Windows-1252 or Mac OS Roman that use the C1 codes to provide additional graphic characters." ... or, I'd like to add, mojibake. E.g. the German letter "ß" is U+00DF with UTF-8 encoding 0xC3 0x9F. I had a long-running program (with UTF-8 output) in a Konsole window set to ISO-8859-1 accidentally, and from the first occurrence of that letter, Konsole waited for the end of the supposedly APC sequence which never came, so it swallowed all further output including probably some important messages from the program. Sure, mojibake is not nice in general, but for languages with few non-ASCII characters such as German, quite tolerable. Swallowing all output makes matters much worse. So I'd suggest to add at least an option to disable their handling. STEPS TO REPRODUCE 1. Set encoding to ISO-8859-1 in Konsole window 2. Run in that window (this should be independent of shells and locale settings, though UTF-8 locale must be installed): LC_ALL=C.UTF-8 /usr/bin/printf 'Gro\u00df\n'; echo Good OBSERVED RESULT Groà (Output cut off and window "dead", or possibly revived by control characters in shell prompt.) EXPECTED RESULT GroÃ? Good % (Mojibake in first line, but second line correct.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 464225] copy/move symbolic link moves link destination instead
https://bugs.kde.org/show_bug.cgi?id=464225 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452119] With an Intel iGPU, animations aren't as smooth on Wayland versus Xorg
https://bugs.kde.org/show_bug.cgi?id=452119 --- Comment #59 from kde@grau.net --- (In reply to David Edmundson from comment #57) > Can reporters here confirm if performance improves if the effect "background > contrast" is disabled? Unfortunately, I'm currently away for a longer time from my computer. Therefore I cannot check, if enabling or disabling the effect makes any difference. Generally, I don't have any effects active in order to put as little strain on the GPU (and CPU) as possible, so I __THINK__ that I am experiencing the slower and more sluggish performance on Wayland vs Xorg without having this effect enabled. I cannot comment, however, if the performance would be even worse if I had enabled this effect. I will check as soon as I get back to the computer. And while I am at it, a big THANK YOU for looking into this issue :-) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 470529] "cover.jpg" file not recognized for use as album art
https://bugs.kde.org/show_bug.cgi?id=470529 --- Comment #7 from Jack Hill --- I think this behaviour is not what people expect, so I would call it a bug. I have submitted a merge request (which is linked in this bug report) so the issue should be fixed shortly. On 26 June 2023 21:07:56 BST, bugzilla_nore...@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=470529 > >--- Comment #6 from paninomaninod...@gmail.com --- >(In reply to Jack Hill from comment #3) >> When you say that the file name was "Case Cover Back Inner", did this have a >> jpg or png file extension? >> >> If it was .jpg, then I think the problem is that Elisa scans images with the >> glob "*[Cc]over*.jpg". So if you had the files "Case Cover Back Inner.jpg" >> and "cover.jpg" then the first match would be "Case Cover Back Inner.jpg", >> and so Elisa would use that as the cover image. > >This explains a lot... >How would I know. > >So it's not a "bug", it's just that the way Elisa works internally is >"obscure"? > >-- >You are receiving this mail because: >You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464830] [Request] Update kdevelop snap to latest (22.12.1)
https://bugs.kde.org/show_bug.cgi?id=464830 Ian H changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #3 from Ian H --- installed: 23.04.1(64) 812MB classic throws errors when building/running qt projects. my guess is it is loading up an incompatible lib during build/run. /Qt/5.15.12/gcc_64/bin/repc: symbol lookup error: /Qt/5.15.12/gcc_64/bin/repc: undefined symbol: _ZdlPvm, version Qt_5 installed: 23.04.2(66) 812MB classic crashes at kdevelop launch snap run kdevelop Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. Segmentation fault (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471482] New: Auto-hiding panel unhides permanently when changing screen resolution on Wayland
https://bugs.kde.org/show_bug.cgi?id=471482 Bug ID: 471482 Summary: Auto-hiding panel unhides permanently when changing screen resolution on Wayland Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bugs.7n...@aleeas.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY On Wayland, auto-hiding panels unhide when changing the screen resolution. They stay visible on the screen and won't hide again until the user interacts with them (i.e. moves the mouse over them and away again). STEPS TO REPRODUCE 1. Set up an auto-hiding panel (and wait for it to hide) 2. Change the screen resolution (or, if running a nested KWin session, resize the inner KWin window) OBSERVED RESULT The panel unhides as if activated by moving the mouse cursor to the panel's screen edge. In contrast to the latter action, the panel will stay visible until the user interacts with the panel (e.g. by moving the mouse over it and away again). EXPECTED RESULT The panel should stay hidden when changing resolutions. SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed (also tested Ubuntu 23.04) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Graphics Platform: Wayland ADDITIONAL INFORMATION The behavior described in https://bugs.kde.org/show_bug.cgi?id=387252 sounds very similar: > (Basically whenever a geometry change request was posted for the panel (e.g. > implicit size of Task Manager changing due to items being added/removed) KWin > would unhide the panel as it could have moved out of the visible are and > become unreachable. It then didn't re-apply the auto hiding) I tried debugging this myself for a bit, but the interaction between KWin/plasmashell is still a bit over my head :) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 470529] "cover.jpg" file not recognized for use as album art
https://bugs.kde.org/show_bug.cgi?id=470529 --- Comment #6 from paninomaninod...@gmail.com --- (In reply to Jack Hill from comment #3) > When you say that the file name was "Case Cover Back Inner", did this have a > jpg or png file extension? > > If it was .jpg, then I think the problem is that Elisa scans images with the > glob "*[Cc]over*.jpg". So if you had the files "Case Cover Back Inner.jpg" > and "cover.jpg" then the first match would be "Case Cover Back Inner.jpg", > and so Elisa would use that as the cover image. This explains a lot... How would I know. So it's not a "bug", it's just that the way Elisa works internally is "obscure"? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466939] plasmashell crashes when dropping widget from widget explorer
https://bugs.kde.org/show_bug.cgi?id=466939 Nicolas Fella changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Nicolas Fella --- No, seems fine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470897] Crash when Right-Clicking an application during search.
https://bugs.kde.org/show_bug.cgi?id=470897 Nicolas Fella changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Nicolas Fella --- Fixed with https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1590 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469263] Wrong tooltip text for Refresh button
https://bugs.kde.org/show_bug.cgi?id=469263 Felix Ernst changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/b92bb43 ||e9da038c68ff8cf3f95e043a2e4 ||2b6c75 Resolution|--- |FIXED --- Comment #2 from Felix Ernst --- Git commit b92bb43e9da038c68ff8cf3f95e043a2e42b6c75 by Felix Ernst, on behalf of Tem PQD. Committed on 26/06/2023 at 19:32. Pushed by felixernst into branch 'master'. Fix Refresh tooltip text and add Refresh whatsThis text M +8-1src/dolphinmainwindow.cpp https://invent.kde.org/system/dolphin/-/commit/b92bb43e9da038c68ff8cf3f95e043a2e42b6c75 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452119] With an Intel iGPU, animations aren't as smooth on Wayland versus Xorg
https://bugs.kde.org/show_bug.cgi?id=452119 --- Comment #58 from Nate Graham --- ...And if the issue does go away with that effect disabled, then the issue was probably Bug 469151 which has just been fixed! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471481] Clicking/ticking noise in rendered video
https://bugs.kde.org/show_bug.cgi?id=471481 --- Comment #1 from Lennart --- Created attachment 159920 --> https://bugs.kde.org/attachment.cgi?id=159920=edit audio rendered in Reaper as 16bit PCM wav (no clicking sound) -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking
https://bugs.kde.org/show_bug.cgi?id=402789 Bug 402789 depends on bug 422878, which changed state. Bug 422878 Summary: Change to work with GitLab issues https://bugs.kde.org/show_bug.cgi?id=422878 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |INTENTIONAL -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471481] New: Clicking/ticking noise in rendered video
https://bugs.kde.org/show_bug.cgi?id=471481 Bug ID: 471481 Summary: Clicking/ticking noise in rendered video Classification: Applications Product: kdenlive Version: 23.04.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: lennart_na...@hotmail.com Target Milestone: --- SUMMARY *** I want to make short mp4 videos for Tiktok of me playing guitar. I record the audio in Reaper, export as wav, combine this with video recorded on my phone (Android) and render as generic mp4 (h.264/aac). There is no apparent issue with the audio until after I render the video, which has a strange clicking/ticking noise. Please refer to the video linked here to get a better idea of the noise: https://youtube.com/shorts/Fo9gyW0XBu0?feature=share I have tried different rendering presets (mainly lossless and generic ones), with mixed results. Either the video had the clicking noise, it didn't have video and/or audio, or it simply wouldn't open in any app. The only preset where the audio was fine, was if I render as wmv, which I then have to convert online to mp4 because that is the only format Tiktok accepts. I have messed around in Reaper switching between 44.1Hz and 48Hz, 16bit and 24bit, with no notable difference. I found the troubleshooting guide, which specifies that audio files should be 16bit PCM, but this also made no difference. I attached the 16bit PCM recording to this report in case it would help you find a fix. I tried different methods of recording, either through my audio interface or Zoom H5 handy recorder. My amp has USB for recording and firmware updates, and this is currently the only way to not have that clicking sound in the video after rendering in Kdenlive. So there is a way around it but it's not exactly practical, and I'm still very puzzled why the sound occurs. It's possible the issue lies in my recording hardware, but then I wouldn't know why there is no problem with the audio during recording or after rendering in Reaper. I couldn't find anything about people having this specific problem. Berndmj over on the Kdenlive subreddit tried to help but also couldn't find a solution, and suggested I make this bug report. *** STEPS TO REPRODUCE 1. add audio file to Kdenlive (with or without a video clip) 2. render as generic mp4 h.264/aac OBSERVED RESULT Intermittent clicking/ticking sound through the video EXPECTED RESULT No intermittent clicking/ticking sound through the video ;) SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 422878] Change to work with GitLab issues
https://bugs.kde.org/show_bug.cgi?id=422878 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|CONFIRMED |RESOLVED --- Comment #1 from Nate Graham --- There are currently no plans to do so. See https://community.kde.org/Get_Involved/Issue_Reporting/Why_not_GitLab_Issues. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 464225] copy/move symbolic link moves link destination instead
https://bugs.kde.org/show_bug.cgi?id=464225 Nate Graham changed: What|Removed |Added Product|dolphin |frameworks-kio Severity|normal |critical Assignee|dolphin-bugs-n...@kde.org |kio-bugs-n...@kde.org Version|unspecified |5.102.0 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Priority|NOR |VHI Component|general |general CC||a.samir...@gmail.com, ||kdelibs-b...@kde.org, ||lameventa...@gmail.com, ||n...@kde.org --- Comment #7 from Nate Graham --- Raising priority and severity due to data loss impact. On first glance, some of the commits in https://invent.kde.org/frameworks/kio/-/merge_requests/511 and https://invent.kde.org/frameworks/kio/-/merge_requests/592 look like they could have caused this. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled and more than one monitor connected
https://bugs.kde.org/show_bug.cgi?id=471439 --- Comment #3 from Basti --- For comparison - Backtrace of Okular crash: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7efd2e7a7d14 in QWidget::hide() () from /usr/lib/libQt5Widgets.so.5 #5 0x7efd2e900c46 in ?? () from /usr/lib/libQt5Widgets.so.5 #6 0x7efd2e901381 in QMenuBar::changeEvent(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #7 0x7efd2e7aeecf in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #8 0x7efd2e778b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #9 0x7efd2da8e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x7efd2e7a318c in QWidgetPrivate::updateFont(QFont const&) () from /usr/lib/libQt5Widgets.so.5 #11 0x7efd2e7af380 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7efd2e778b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x7efd2da8e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #14 0x7efd2e7ccb18 in ?? () from /usr/lib/libQt5Widgets.so.5 #15 0x7efd2e7ccb48 in ?? () from /usr/lib/libQt5Widgets.so.5 #16 0x7efd2e7cd206 in ?? () from /usr/lib/libQt5Widgets.so.5 #17 0x7efd2dabecf0 in ?? () from /usr/lib/libQt5Core.so.5 #18 0x7efd2df4ef94 in QWindow::screenChanged(QScreen*) () from /usr/lib/libQt5Gui.so.5 #19 0x7efd2df431d4 in QWindowPrivate::emitScreenChangedRecursion(QScreen*) () from /usr/lib/libQt5Gui.so.5 #20 0x7efd2e79c974 in QWidgetPrivate::create() () from /usr/lib/libQt5Widgets.so.5 #21 0x7efd2e79cca4 in QWidget::create(unsigned long long, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #22 0x7efd2e8feb2f in ?? () from /usr/lib/libQt5Widgets.so.5 #23 0x7efd2e8fef68 in QMenuBar::QMenuBar(QWidget*) () from /usr/lib/libQt5Widgets.so.5 #24 0x7efd2e8c442c in QMainWindow::menuBar() const () from /usr/lib/libQt5Widgets.so.5 #25 0x7efd08cdf2c2 in Okular::Part::setupActions() () from /usr/lib/qt/plugins/okularpart.so #26 0x7efd08ce4d2c in Okular::Part::Part(QWidget*, QObject*, QList const&) () from /usr/lib/qt/plugins/okularpart.so #27 0x7efd08cf3f97 in ?? () from /usr/lib/qt/plugins/okularpart.so #28 0x7efd2edb67a5 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () from /usr/lib/libKF5CoreAddons.so.5 #29 0x55e03ee22bb6 in ?? () #30 0x55e03ee1f661 in ?? () #31 0x7efd2d239850 in __libc_start_call_main (main=main@entry=0x55e03ee1e060, argc=argc@entry=1, argv=argv@entry=0x7fffe036bad8) at ../sysdeps/nptl/libc_start_call_main.h:58 #32 0x7efd2d23990a in __libc_start_main_impl (main=0x55e03ee1e060, argc=1, argv=0x7fffe036bad8, init=, fini=, rtld_fini=, stack_end=0x7fffe036bac8) at ../csu/libc-start.c:360 #33 0x55e03ee20345 in ?? () [Inferior 1 (process 5787) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471480] New: taskbar overlaps other windows
https://bugs.kde.org/show_bug.cgi?id=471480 Bug ID: 471480 Summary: taskbar overlaps other windows Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: kake...@gmail.com Target Milestone: 1.0 Created attachment 159919 --> https://bugs.kde.org/attachment.cgi?id=159919=edit overlaps other windows, although it should automatically hide Sometimes freezes -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 471479] Application crashes as soon as an attempt is made to chage IMAP server
https://bugs.kde.org/show_bug.cgi?id=471479 Carl Schwan changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Carl Schwan --- This is a crash in the account wizard, it's using an old and unmaintained technology called QtScript and your backtrace indicated that it crashed there. We are currently rewriting it, since QtScript is not available in Qt6 anymore. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471451] Upload to SmugMug fails for certain files
https://bugs.kde.org/show_bug.cgi?id=471451 --- Comment #3 from dw-...@digger.net --- Hi Maik I don't think this is a duplicate of bug 434556, because that bug is about some random intermittent failure where all uploads stop working though they work at a different time. This bug is a reliable failure for a specific file, while all other files continue working. Is there a way to get digiKam to log more detail that what I've already included here (which was using 'export QT_LOGGING_RULES="digikam*=true"')? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled and more than one monitor connected
https://bugs.kde.org/show_bug.cgi?id=471439 Basti changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #2 from Basti --- Sorry for the inconvenience, it seems that I closed this issue too early. The crash does not happen, while only using the Laptop display. When connecting an external monitor via thunderbolt/usb-c, all applications again crash on startup. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled and more than one monitor connected
https://bugs.kde.org/show_bug.cgi?id=471439 Basti changed: What|Removed |Added Summary|Konsole and other KDE |Konsole and other KDE |applications crash on |applications crash on |startup with global app |startup with global app |menu enabled|menu enabled and more than ||one monitor connected -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471322] Crash when starting and using rpm-ostree updates
https://bugs.kde.org/show_bug.cgi?id=471322 Timothée Ravier changed: What|Removed |Added Summary|Make rpm-ostree updates |Crash when starting and |optional|using rpm-ostree updates -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471322] Make rpm-ostree updates optional
https://bugs.kde.org/show_bug.cgi?id=471322 Timothée Ravier changed: What|Removed |Added CC||t...@siosm.fr --- Comment #4 from Timothée Ravier --- Please do the following and report the crash backtrace: ``` # Layer gdb-minimal $ sudo rpm-ostree install gdb-minimal # Setup a symlink $ sudo ln -nsf /usr/bin/gdb-minimal /usr/local/bin/gdb # Trigger the crash again. DrKonqi should get you a backtrace now ``` -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470994] Crash when starting and using rpm-ostree updates
https://bugs.kde.org/show_bug.cgi?id=470994 Timothée Ravier changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||t...@siosm.fr --- Comment #1 from Timothée Ravier --- *** This bug has been marked as a duplicate of bug 471322 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471322] Make rpm-ostree updates optional
https://bugs.kde.org/show_bug.cgi?id=471322 --- Comment #3 from Timothée Ravier --- *** Bug 470994 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469406] Kate 23.04.0 crashing at start on macOS Ventura 13.3.1
https://bugs.kde.org/show_bug.cgi?id=469406 Laurent Trinques changed: What|Removed |Added CC||scor...@qelectrotech.org --- Comment #7 from Laurent Trinques --- (In reply to Harish from comment #6) > Can anyone suggest where I can download 22.12.2 version? Same for me, https://www.macupdate.com/app/mac/63455/kate Kate Version 22.12.2 --> link error 404 !!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 soredake changed: What|Removed |Added CC|broaden_acid002@simplelogin | |.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 nather...@gmail.com changed: What|Removed |Added CC|nather...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 stefanfunk1...@gmail.com changed: What|Removed |Added CC||stefanfunk1...@gmail.com --- Comment #15 from stefanfunk1...@gmail.com --- just chiming in, that just recently i have been getting the same issue. started around june 21st/22nd. im on arch linux, with kde wayland. i cant reproduce the error well, but i happens several times per play session, that the camera will just randomly snap to a different direction while controlling the camera manually with the mouse buttons. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 471479] New: Application crashes as soon as an attempt is made to chage IMAP server
https://bugs.kde.org/show_bug.cgi?id=471479 Bug ID: 471479 Summary: Application crashes as soon as an attempt is made to chage IMAP server Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Microsoft Windows OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Account Wizard Assignee: kdepim-b...@kde.org Reporter: j...@jdgwf.com CC: c...@carlschwan.eu Target Milestone: --- Application: accountwizard (0.2) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: FreeBSD 13.2-RELEASE amd64 Windowing System: X11 Distribution (Platform): Microsoft Windows DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: Very unexpected crash. Setup works great until I add a "Genereic IMAP Server" I can change my username and outgoing server but as soon as I keydown the incoming server it crashes hard back to Kmail or (if initial startup) the desktop. The checkbox for Downloading all email is also safe for changing. In addition as soon as I "finish" the Assistant App crashes. The crash can be reproduced every time. -- Backtrace: Application: Account Assistant (accountwizard), signal: Segmentation fault (lldb) process attach --pid 1503 Process 1503 stopped * thread #1, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00084263e1b8 libc.so.7`__sys_wait4 + 8 libc.so.7`__sys_wait4: -> 0x84263e1b8 <+8>: syscall 0x84263e1ba <+10>: jb 0x84263adb8 0x84263e1c0 <+16>: retq 0x84263e1c1: int3 thread #2, name = 'llvmpipe-0', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #3, name = 'llvmpipe-1', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #4, name = 'llvmpipe-2', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #5, name = 'llvmpipe-3', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #6, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #7, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #8, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #9, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #10, name = 'account:disk$0', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #11, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd95dd libthr.so.3`___lldb_unnamed_symbol619 + 237 libthr.so.3`___lldb_unnamed_symbol619: -> 0x82fdd95dd <+237>: leaq 0x38(%rbx), %rsi 0x82fdd95e1 <+241>: movq $0x0, 0x38(%rbx) 0x82fdd95e9 <+249>: movq %rdx, %rdi 0x82fdd95ec <+252>: shlq $0x4, %rdi thread #12, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00084263df5a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x84263df5a <+10>: jb
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled
https://bugs.kde.org/show_bug.cgi?id=471439 Basti changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Basti --- Nvm, seems like I was just missing some necessary dbus packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 Antti Savolainen changed: What|Removed |Added CC||antti.s...@gmail.com --- Comment #54 from Antti Savolainen --- I'll add my participation to the pile. I'm having the same issue Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.8-arch1-1-bcachefs-git Graphics Platform: Wayland Processors: Intel Core i5-6600K Graphics Card: GeForce GTX 1060 6GB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466771] Some windows are painted black on X11, processes freeze
https://bugs.kde.org/show_bug.cgi?id=466771 --- Comment #19 from nttkde --- I have noticed that over time Plasma rendering gets more sluggish (overall low framerate, things like menu item highlight changes etc. behave sluggishly) and that seems to be when I really start getting the black windows too. The Xorg process will have high CPU usage when doing something like playing a video in Firefox (but not when I'm not doing anything on the desktop). Not sure what is cause and what is symptom in this case though. In my case running kwin --replace fixes the sluggishness, Xorg CPU usage returns to being always at low levels and windows seem to render normally again (at least until things start slowing down again). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471478] New: General search finds only untranslated string, while KCM search only finds translated one
https://bugs.kde.org/show_bug.cgi?id=471478 Bug ID: 471478 Summary: General search finds only untranslated string, while KCM search only finds translated one Classification: Applications Product: systemsettings Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 159918 --> https://bugs.kde.org/attachment.cgi?id=159918=edit Screenshot STEPS TO REPRODUCE 1. German locale 2. Search for "Contrast" 3. Within the workspace effects, search for "Contrast" again. --> Nothing found. 4a. At point 3 change "Contrast" to "Kontrast": Now the relevant item is found. 4b. At point 2 change "Contrast" to "Kontrast": Nothing is found. EXPECTED RESULT 1) The untranslated original English string should always be found, both in the general search and in case of the KCM filter. 2) The translated string should also be searchable in the general filter if it's searchable within an KCM. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230623 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421745] On Wayland, the color scheme of gtk3 apps is not immediately updated when I change the global theme; the apps need to be restarted
https://bugs.kde.org/show_bug.cgi?id=421745 --- Comment #71 from medin --- For anyone suffering from this problem on Arch based distros, simply go to Plasma settings then select "Startup and Shutdown" then "Background Services", locate "GNOME/GTK Settings Synchronization Service" and stop it then restart it to get the applied global theme to propagate to all running GTK+ apps without needing to restart them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471132] _NET_FRAME_EXTENTS returns incorrect output on XWAYLAND
https://bugs.kde.org/show_bug.cgi?id=471132 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/4214 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 471477] New: Show total playlist length / duration
https://bugs.kde.org/show_bug.cgi?id=471477 Bug ID: 471477 Summary: Show total playlist length / duration Classification: Applications Product: Elisa Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: m...@kisaragi-hiu.com Target Milestone: --- SUMMARY Sometimes it is useful to know the length of, at the very least, the current playlist. I use it to estimate the amount of time I would've spent working on something else once the album ends. Amarok appears to have this feature judging by Bugzilla's automatic duplicate search, and Spotify also has this feature which is how I became aware of it. STEPS TO REPRODUCE 1. Play an album or an existing playlist OBSERVED RESULT No way to find the total length of the playlist other than adding up individual track lengths manually EXPECTED RESULT Total length of the playlist shown somewhere in the interface for the current playlist SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471476] New: unhandled amd64-linux syscall: 441
https://bugs.kde.org/show_bug.cgi?id=471476 Bug ID: 471476 Summary: unhandled amd64-linux syscall: 441 Classification: Developer tools Product: valgrind Version: 3.21.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: cachegrind Assignee: n...@valgrind.org Reporter: ronnebaumfinan...@gmail.com Target Milestone: --- SUMMARY *** unhandled amd64-linux syscall: 441 I received this warning message when running the commands below. I ran the same command on a couple C programs after receiving the warning, and they all output the same message show below. The warning states that there is an unhandled amd64-linux syscall, specifying 441. I'm not very inclined when it comes to hardware, but I am on an intel cpu, so I'm curious as to why there would be an amd syscall. The programs that I ran the command on were compiled with the c89, c99, gcc, and clang compilers. All of the programs output the same warning message shown below. *** STEPS TO REPRODUCE 1. valgrind --tool=cachegrind ls -l ./ (cmd source: https://courses.cs.washington.edu/courses/cse326/05wi/valgrind-doc/cg_main.html) I get the following output after running the command: $ valgrind --tool=cachegrind ls -l ./ WARNING: unhandled amd64-linux syscall: 441 You may be able to write your own handler. Read the file README_MISSING_SYSCALL_OR_IOCTL. Nevertheless we consider this a bug. Please report it at http://valgrind.org/support/bug_reports.html. EXPECTED OUTCOME: something along the lines of: ==31751== I refs: 27,742,716 ==31751== I1 misses: 276 ==31751== L2 misses: 275 ==31751== I1 miss rate:0.0% ==31751== L2i miss rate:0.0% ==31751== ==31751== D refs: 15,430,290 (10,955,517 rd + 4,474,773 wr) ==31751== D1 misses:41,185 (21,905 rd +19,280 wr) ==31751== L2 misses:23,085 ( 3,987 rd +19,098 wr) ==31751== D1 miss rate:0.2% ( 0.1% + 0.4%) ==31751== L2d miss rate:0.1% ( 0.0% + 0.4%) ==31751== ==31751== L2 misses: 23,360 ( 4,262 rd +19,098 wr) ==31751== L2 miss rate: 0.0% ( 0.0% + 0.4%) SOFTWARE/OS VERSIONS clang: 15.0.7 gcc: 13.1.1 archlinux: 6.3.9 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 471475] 3 screen configuration doesn't "write".
https://bugs.kde.org/show_bug.cgi?id=471475 Kevin "G" changed: What|Removed |Added CC||krg...@kevingarand.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 471475] New: 3 screen configuration doesn't "write".
https://bugs.kde.org/show_bug.cgi?id=471475 Bug ID: 471475 Summary: 3 screen configuration doesn't "write". Classification: Plasma Product: KScreen Version: git-stable-Plasma/5.27 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: krg...@kevingarand.com Target Milestone: --- SUMMARY I love Plasma, but no matter the distro, when I setup my 3 screens and configure them how I like them, I choose "apply" and go to move to another setting, Plasma then asks "do you wish to keep this setting" even though I have already chosen apply. I choose yes, and then a simple reboot the configuration isn't saved or "written". It simply goes back to default, which isn't how i want them, obv.Please fix!! I humbly (not a programmer) appreciate anyone's help in advance. *** 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. Either Live or install Plasma, go to configure display 2. Set displays as you want them, I have 3, and choose Apply. Go to another setting, it will ask you "Do you wish to keep this setting" you choose yes and reboot. 3. Displays goes back to default, as if when Apply was chosen, something didn't write the config. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Does this in every distro, Fedora, KUbuntu, Debian-KDE, OpenSuse. (available in About System) KDE Plasma Version: pretty much all since 5.25 or before. KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
