[valgrind] [Bug 331550] Detect the potential of mis-malloc/free in different libraries
https://bugs.kde.org/show_bug.cgi?id=331550 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #2 from Paul Floyd --- The problem isn't malloc and family being called _from_different libraries. The problem is if there are calls to versions of malloc _in_ different libraries. Do we have a fast way to tell which library (or exe) contains used allocation functions? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475646] New: Wifi notification wont go awat
https://bugs.kde.org/show_bug.cgi?id=475646 Bug ID: 475646 Summary: Wifi notification wont go awat Classification: Plasma Product: plasmashell Version: master Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: omervx...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 162317 --> https://bugs.kde.org/attachment.cgi?id=162317=edit The notification pic after i connect to wifi SUMMARY *** This notification doesn’t go away after i connect to wifi im on kubuntu 22.04 plasma version 5.27.8 and im using win10 dark theme 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 EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.27.8 (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.
[systemsettings] [Bug 438496] Keyboard layout switching shortcut stops working after a period of inactivity
https://bugs.kde.org/show_bug.cgi?id=438496 Denis Klychkov changed: What|Removed |Added CC||kd.sn...@gmail.com --- Comment #23 from Denis Klychkov --- I also have this issue for several years. It happens only in X session when switching mode is set to anything but "Global". I experienced it in Arch, OpenSUSE and Manjaro. It relates neither to suspending the PC, nor to inactivity periods. I used to catch it during my active work. At some moment the layout switching hotkey stops working. I have to open settings and reapply them. Finally I gave up with it when I had to re-enable the hotkeys three or four times in an hour. Now I have to use the "Global" switching mode, as it is the only working option. I can try to investigate and even fix it if somebody shows me possible places to look for the issue. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 475634] valgrind is not starting
https://bugs.kde.org/show_bug.cgi?id=475634 --- Comment #2 from Paul Floyd --- Also does it work with the simplest tool, "--tool=none"? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475645] New: Wallpaper or desktop glitch following interaction with context menu
https://bugs.kde.org/show_bug.cgi?id=475645 Bug ID: 475645 Summary: Wallpaper or desktop glitch following interaction with context menu Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: p...@wwphil.ca Target Milestone: --- Created attachment 162316 --> https://bugs.kde.org/attachment.cgi?id=162316=edit Wallpaper or desktop glitch following interaction with context menu SUMMARY Arch linux, Wayland. AMD gpu. It's a minor issue but it's been happening to me for over a year. Sometimes, when I switch between apps or interact with a context menu, the desktop and wallpaper "resize" and think the monitor is 1080p (only on the main monitor)... STEPS TO REPRODUCE 1. Open context menu of an application in system tray (for example Steam or Discord) 2. Immediately click outside of context menu, on wallpaper for example OBSERVED RESULT Suddenly desktop / wallpaper is resized to 1920x1080 and goes to the upper left corner EXPECTED RESULT Wallpaper and desktop should always use the whole screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux, Wayland, kernel 6.5.6-arch2-1 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION If I right click on the wallpaper in the corner, I get a context menu, but right click on the background anywhere else does nothing. I can still use the whole screen, but some apps will only use that upper left corner where the wallpaper is. To correct I just change resolution and click revert to go back, and everything is fine again until the next time. Happens a few times a day. I can reproduce it but not at will. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 475634] valgrind is not starting
https://bugs.kde.org/show_bug.cgi?id=475634 --- Comment #1 from Paul Floyd --- Try removing the vgdb options. Valgrind will be stopped waiting for a vgdb connection via named pipe. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 475634] valgrind is not starting
https://bugs.kde.org/show_bug.cgi?id=475634 Paul Floyd changed: What|Removed |Added Summary|valgrind is no starting |valgrind is not starting CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474126] System settings crash on opening 'Application Style'
https://bugs.kde.org/show_bug.cgi?id=474126 FirstAirBender changed: What|Removed |Added CC||noblech...@web.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474126] System settings crash on opening 'Application Style'
https://bugs.kde.org/show_bug.cgi?id=474126 --- Comment #2 from FirstAirBender --- Created attachment 162315 --> https://bugs.kde.org/attachment.cgi?id=162315=edit New crash information added by DrKonqi systemsettings (5.27.8) using Qt 5.15.11 I tried opening application style and the settings app just crashed -- Backtrace (Reduced): #7 0x7f14716a00c2 in qt_assert(char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 [...] #10 0x7f14725e6f44 in QStyleFactory::create(QString const&) () at /usr/lib/libQt5Widgets.so.5 [...] #12 0x7f146f6a4901 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #13 0x7f146f650667 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #14 0x7f146f651016 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467560] Keywords assigned by Synology Photos is written in XMP metadata but not recognized by digiKam.
https://bugs.kde.org/show_bug.cgi?id=467560 --- Comment #13 from caulier.gil...@gmail.com --- @malte.boen...@web.de, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #9 from caulier.gil...@gmail.com --- Hi Maik, Yes IPTC Urgency is and older way to store Rating when digiKam XMP+sidecar support was not yet usable. Now the situation is completely different and definitively, this can be removed at all. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468348] MySQL remote database: After hibernation, no enlarge window, no display
https://bugs.kde.org/show_bug.cgi?id=468348 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.2.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED -- 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 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468830] Metadata is lost after write operation when the size of XMP JPEG segment is larger than 65535 bytes when using Exiftool backend
https://bugs.kde.org/show_bug.cgi?id=468830 --- Comment #7 from caulier.gil...@gmail.com --- @José, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer + ExifTool backend available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 472868] Doesn't Compile with LLVM's libc++ and compiler-rt
https://bugs.kde.org/show_bug.cgi?id=472868 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #14 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 471899] 2nd monitor screen is flickering
https://bugs.kde.org/show_bug.cgi?id=471899 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |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.
[www.kde.org] [Bug 475051] Remove release_announcements.po from l10n list
https://bugs.kde.org/show_bug.cgi?id=475051 --- 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.
[PlasmaTube] [Bug 469752] Settings selection dots scroll past the box
https://bugs.kde.org/show_bug.cgi?id=469752 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 468790] Window title not visible in the title bar in Gnome 44 (Fedora Silverblue 38, PlasmaTube installed from Flathub)
https://bugs.kde.org/show_bug.cgi?id=468790 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |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.
[Elisa] [Bug 471090] Elisa's theme only partially changed when changing global theme from Breeze Light to Breeze Dark (until application's restart)
https://bugs.kde.org/show_bug.cgi?id=471090 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471065] Discover does not open app information and does not install packages
https://bugs.kde.org/show_bug.cgi?id=471065 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469191] Markers and thumbnails not showing on any map view when Google Maps is the selected map
https://bugs.kde.org/show_bug.cgi?id=469191 --- Comment #8 from caulier.gil...@gmail.com --- @Jez, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469372] "Image cannot be loaded" – some images not rendered correctly
https://bugs.kde.org/show_bug.cgi?id=469372 --- Comment #29 from caulier.gil...@gmail.com --- @Tim, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469384] Export to iNaturalist tool do not respond.
https://bugs.kde.org/show_bug.cgi?id=469384 --- Comment #7 from caulier.gil...@gmail.com --- @Patrick, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469423] digiKam creates duplicate files when local directory is a onedrive folder
https://bugs.kde.org/show_bug.cgi?id=469423 --- Comment #8 from caulier.gil...@gmail.com --- @Jürgen, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #9 from caulier.gil...@gmail.com --- @Marvin, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469688] Unable to launch the software after installation
https://bugs.kde.org/show_bug.cgi?id=469688 --- Comment #5 from caulier.gil...@gmail.com --- @ktvheihei...@foxmail.com, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #17 from caulier.gil...@gmail.com --- @Judah, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
https://bugs.kde.org/show_bug.cgi?id=470566 --- Comment #50 from caulier.gil...@gmail.com --- @maison, What the status of this entry ? Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470693] Improve geolocation feature online documentation.
https://bugs.kde.org/show_bug.cgi?id=470693 caulier.gil...@gmail.com changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470693] Improve geolocation feature online documentation.
https://bugs.kde.org/show_bug.cgi?id=470693 caulier.gil...@gmail.com changed: What|Removed |Added Component|Geolocation-Places |Documentation Summary|Unable to expand map of |Improve geolocation feature |geolocated images |online documentation. --- Comment #7 from caulier.gil...@gmail.com --- Peter, Didi you seen my previous comment ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470694] Some Face Regions are Rotated
https://bugs.kde.org/show_bug.cgi?id=470694 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #4 from caulier.gil...@gmail.com --- @CM, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471200] Windows 10 DigiKam Crash at Launch After Updating to 8.0.0
https://bugs.kde.org/show_bug.cgi?id=471200 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.2.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471269] Application crashes when album contains avif file
https://bugs.kde.org/show_bug.cgi?id=471269 --- Comment #8 from caulier.gil...@gmail.com --- @SA, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471299] Crash when opening the setup dialog.
https://bugs.kde.org/show_bug.cgi?id=471299 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Setup-Views --- Comment #3 from caulier.gil...@gmail.com --- @santiago, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471992] digikam 8.0.0 crashes when downloading face files
https://bugs.kde.org/show_bug.cgi?id=471992 --- Comment #8 from caulier.gil...@gmail.com --- @Mike, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472091] Tag Tree Ignored with Item->ReRead Metadata from File
https://bugs.kde.org/show_bug.cgi?id=472091 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- @Stewart, Did you seen the previous message from Maik ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472133] At 4k resolution, high resolution adaptation mode is selected, and some window fonts are too small
https://bugs.kde.org/show_bug.cgi?id=472133 --- Comment #2 from caulier.gil...@gmail.com --- @echo, Did you see the previous message from Maik ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472266] digikam face recognition ignores imported face tag data
https://bugs.kde.org/show_bug.cgi?id=472266 --- Comment #2 from caulier.gil...@gmail.com --- @Justin, Did you see the previous message from Maik ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472273] Auto Brightness in Raw Default Settings turns off but does not turn on again
https://bugs.kde.org/show_bug.cgi?id=472273 --- Comment #4 from caulier.gil...@gmail.com --- @IvorJ, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472416] Add a new option in Face Recognition about duplication of a Confirmed Face.
https://bugs.kde.org/show_bug.cgi?id=472416 caulier.gil...@gmail.com changed: What|Removed |Added Severity|minor |wishlist Summary|Face Recognition- |Add a new option in Face |Duplication of a Confirmed |Recognition about |Face|duplication of a Confirmed ||Face. CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472452] Face Recognition fails (process stuck at 0%)
https://bugs.kde.org/show_bug.cgi?id=472452 --- Comment #2 from caulier.gil...@gmail.com --- @Perry, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472508] Scanning AV1 files results in crash
https://bugs.kde.org/show_bug.cgi?id=472508 --- Comment #13 from caulier.gil...@gmail.com --- @linc...@vandymail.com, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473376] Digikam does not use date/time from metadata
https://bugs.kde.org/show_bug.cgi?id=473376 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||8.2.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473436] digiKam Sometimes hangs when the editor saves.
https://bugs.kde.org/show_bug.cgi?id=473436 --- Comment #2 from caulier.gil...@gmail.com --- @j...@acm.org, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473449] Duplicate search restriction is sometimes ignored
https://bugs.kde.org/show_bug.cgi?id=473449 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- @Michael, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473961] The program get close when i am trying to qualify several images automatically at once.
https://bugs.kde.org/show_bug.cgi?id=473961 --- Comment #3 from caulier.gil...@gmail.com --- @Cadasur, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 474357] Face Tag shown at wrong location
https://bugs.kde.org/show_bug.cgi?id=474357 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #8 from caulier.gil...@gmail.com --- @joerg.me...@vint.de, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 474472] MySQL doesn't support modern caching_sha2_password
https://bugs.kde.org/show_bug.cgi?id=474472 --- Comment #3 from caulier.gil...@gmail.com --- @Lucas Jandrew, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Dilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 474677] Deleting files generates an error about permissions on .dtrash
https://bugs.kde.org/show_bug.cgi?id=474677 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- @j...@acm.org, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Dilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 474762] New album (on external HDD) scan crashes at startup
https://bugs.kde.org/show_bug.cgi?id=474762 --- Comment #2 from caulier.gil...@gmail.com --- @famille.frances...@sfr.fr, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Dilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 475432] Deleting impossible
https://bugs.kde.org/show_bug.cgi?id=475432 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #4 from caulier.gil...@gmail.com --- @dch.dup...@gmail.com, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Dilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475644] New: Resizing when selecting and moving groups of clips
https://bugs.kde.org/show_bug.cgi?id=475644 Bug ID: 475644 Summary: Resizing when selecting and moving groups of clips Classification: Applications Product: kdenlive Version: 23.08.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: horrormakesusha...@gmail.com Target Milestone: --- SUMMARY We create slideshows of excerpts of our podcast to upload to Youtube. For these slideshows we use the first two tracks alternate between pictures of our guests and pictures of our podcast's logos. So the first track is all pictures of our guests, and the second track is all images of our logos. Previously the excerpts we were uploading were only 60-120 seconds long, so there were very few transitions, but we now want to upload entire episodes, which are 60-90 minutes long. Since we only get a handful of pictures from each guest, rather than rotate through those for that length of time we've decided to use pictures from all of our guests. We're in our 4th year, so the slideshow of each year's guests can be pics of the guests from that season. As such, what we've done is create a long slideshow as a template. We export the video for an episode, then we take the images of that guest, move them to the back of the slideshow, and move all guest images back up to the front. This way the first images for that video will be of the guest in that video. We've noticed that after moving the clips some have been resized or moved off their alignment (we give exact details below). Our best guess is that the moves are being split into multiple groups of actions, with some being done properly and some not. STEPS TO REPRODUCE 1. Create a slideshow with 120 images, each displayed for 60 seconds, with 3-second transitions, and a transition on the last one to use for snap-to alignment. 2. Select the first 5 images of the top track, move them to the back. 3. Select all images of the top track, drag them forwards to 0:00. 4. Check length and alignment of all images in the first track. OBSERVED RESULT The 14th image in the first track is 54 seconds long 15th - 32nd images are 60 seconds long, but off alignment by 6 seconds 33rd - 48th were 60 seconds long and on alignment 49th - 57th are 60 seconds long, but off alignment by 6 seconds 58th was 54 seconds long 59th & 60th are 60 seconds long, but off alignment by 6 seconds EXPECTED RESULT Images would be moved without being resized or changing alignment. SOFTWARE/OS VERSIONS Windows: Win10 ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 --- Comment #11 from Chris --- (In reply to Björn Bidar (Thaodan) from comment #8) > *** Bug 455113 has been marked as a duplicate of this bug. *** Bug 455113 is an actual bug because it does something it shouldn't: connecting to Gmail when it's a Yahoo address. In light of this, shouldn't this bug be considered an actual one too, instead of being classified as a mere wishlist item? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475643] New: Kate/Kwrite: When saving a newly created file, add it to the Open Recent list
https://bugs.kde.org/show_bug.cgi?id=475643 Bug ID: 475643 Summary: Kate/Kwrite: When saving a newly created file, add it to the Open Recent list Classification: Applications Product: kate Version: 23.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: k...@callthecomputerdoctor.com Target Milestone: --- When I create and save a new document in Kate/Kwrite, and then come back to Kate/Kwrite, I cannot easily open the file I just saved, it's not present in the Open Recent list. STEPS TO REPRODUCE 1. Create a new file, save it, close it. OBSERVED RESULT Go to File -> Open Recent and notice that the newly saved file is not present. I have to go through File -> Open, then dig around to find the file I just saved. EXPECTED RESULT The newly saved file should be at the top of the Open Recent list. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475642] New: Transparent XWayland Windows can have strange artifacts, demonstrated with Oneko and Neko98.
https://bugs.kde.org/show_bug.cgi?id=475642 Bug ID: 475642 Summary: Transparent XWayland Windows can have strange artifacts, demonstrated with Oneko and Neko98. Classification: Plasma Product: kwin Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: platform-x11-nested Assignee: kwin-bugs-n...@kde.org Reporter: sa...@sarahduck.ca Target Milestone: --- Created attachment 162314 --> https://bugs.kde.org/attachment.cgi?id=162314=edit A screenshot of both Oneko and Neko98 with identical artifacting. SUMMARY On Fedora, running Oneko from the repos, from Flathub, or running Neko98 through Wine results in overlapping frames of animation. They look just fine on the standalone X11 session. I had a friend of mine running Gnome 44 on NixOS attempt to install and run Oneko, and it looked just fine on Wayland, so I'm guessing this is a KDE specific issue. I've managed to reproduce it both on my laptop with an AMD CPU/GPU, and on my tablet with an Intel CPU/GPU. STEPS TO REPRODUCE 1. Run Oneko on KDE Wayland OBSERVED RESULT I've attached a screenshot, they look very wrong. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38, KDE 5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475639] plymouth-kcm caused crash apon saving changes of boot splash screen
https://bugs.kde.org/show_bug.cgi?id=475639 rustmil...@proton.me changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from rustmil...@proton.me --- *** This bug has been marked as a duplicate of bug 475067 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475067] plymouth-kcm caused crash apon saving changes of boot splash screen
https://bugs.kde.org/show_bug.cgi?id=475067 --- Comment #4 from rustmil...@proton.me --- *** Bug 475639 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475067] plymouth-kcm caused crash apon saving changes of boot splash screen
https://bugs.kde.org/show_bug.cgi?id=475067 --- Comment #3 from rustmil...@proton.me --- (In reply to Nate Graham from comment #1) > Thank you for the bug report! Unfortunately I can't reproduce the crash > myself on current git master, and the backtrace is incomplete and missing > debug symbols for the following lines that we need to figure out exactly > what's going wrong: > > > #5 0x7fb82a1f2c06 in () at > > /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_plymouth.so > > #6 0x7fb84fab1d06 in () at /usr/lib/libKF5KCMUtils.so.5 > > Could you please install debug symbols for plymouth-kcm and the kcmutils > framework, reproduce the crash, and attach a new symbolicated backtrace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports for details about how to do this. > > Thanks again! Application: systemsettings (5.27.8) Qt Version: 5.15.11 Frameworks Version: 5.110.0 Operating System: Linux 6.5.7-arch1-1 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Save and exit system settings while still saving will cause crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f1c4d6c149d in QObjectPrivate::maybeSignalConnected(unsigned int) const () at /usr/lib/libQt5Core.so.5 #5 0x7f1c4d6cfdef in () at /usr/lib/libQt5Core.so.5 #6 0x7f1c155c4c06 in KCMPlymouth::busyChanged() (this=0x5560d01ba2b0) at /usr/src/debug/plymouth-kcm/build/src/kcm_plymouth_autogen/EWIEGA46WW/moc_kcm.cpp:304 #7 KCMPlymouth::setBusy(bool const&) (busy=, this=0x5560d01ba2b0) at /usr/src/debug/plymouth-kcm/plymouth-kcm-5.27.8/src/kcm.cpp:160 #8 KCMPlymouth::save() (this=0x5560d01ba2b0) at /usr/src/debug/plymouth-kcm/plymouth-kcm-5.27.8/src/kcm.cpp:206 #9 0x7f1c4e112d06 in KCModuleQml::save() (this=0x5560d130d620) at /usr/src/debug/kcmutils5/kcmutils-5.110.0/src/kcmoduleqml.cpp:306 #10 0x7f1c4e11ada8 in KCModuleProxy::save() (this=) at /usr/src/debug/kcmutils5/kcmutils-5.110.0/src/kcmoduleproxy.cpp:279 #11 0x7f1c4efe6ab6 in ModuleView::moduleSave(KCModuleProxy*) (this=0x5560d02e2270, module=) at /usr/src/debug/systemsettings/systemsettings-5.27.8/core/ModuleView.cpp:379 #12 0x7f1c4efe6e2f in ModuleView::moduleSave() (this=) at /usr/src/debug/systemsettings/systemsettings-5.27.8/core/ModuleView.cpp:370 #13 0x7f1c4efeb6af in ModuleView::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=0x7ffcb2e38bb0) at /usr/src/debug/systemsettings/build/core/systemsettingsview_autogen/EWIEGA46WW/moc_ModuleView.cpp:133 #14 0x7f1c4d6d06a3 in () at /usr/lib/libQt5Core.so.5 #15 0x7f1c4e8c2527 in KAuth::ObjectDecorator::authorized(KAuth::Action const&) () at /usr/lib/libKF5Auth.so.5 #16 0x7f1c4d6d04e7 in () at /usr/lib/libQt5Core.so.5 #17 0x7f1c4e45c677 in QAbstractButton::clicked(bool) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f1c4e45ef2a in () at /usr/lib/libQt5Widgets.so.5 #19 0x7f1c4e46042c in () at /usr/lib/libQt5Widgets.so.5 #20 0x7f1c4e4605d0 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7f1c4e3af1a1 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #22 0x7f1c4e3788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #23 0x7f1c4e37ddaf in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #24 0x7f1c4d69b5b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #25 0x7f1c4e37c0ea in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #26 0x7f1c4e3cce85 in () at /usr/lib/libQt5Widgets.so.5 #27 0x7f1c4e3cebd7 in () at /usr/lib/libQt5Widgets.so.5 #28 0x7f1c4e3788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #29 0x7f1c4d69b5b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #30 0x7f1c4db4194c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #31 0x7f1c4db2a6e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #32 0x7f1c4b55ec75 in () at /usr/lib/libQt5WaylandClient.so.5 #33 0x7f1c4bd0df19 in () at /usr/lib/libglib-2.0.so.0 #34 0x7f1c4bd6c2b7 in () at /usr/lib/libglib-2.0.so.0 #35 0x7f1c4bd0c112 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #36 0x7f1c4d6ea3cc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #37 0x7f1c4d69a2c4 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #38 0x7f1c4d69b763 in QCoreApplication::exec() () at
[dragonplayer] [Bug 475641] New: Make F11 be an alternate shortcut for fullscreen to be in harmony with other apps
https://bugs.kde.org/show_bug.cgi?id=475641 Bug ID: 475641 Summary: Make F11 be an alternate shortcut for fullscreen to be in harmony with other apps Classification: Applications Product: dragonplayer Version: 23.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@callthecomputerdoctor.com CC: myr...@kde.org, sit...@kde.org Target Milestone: --- F11 is the standard keyboard shortcut to make a web browser full screen, which is what most people know, and this has been adopted by Kwrite, Kate, Gwenview, VLC and is used to hide/show the preview pane in Dolphin and the standard open/save dialog box. STEPS TO REPRODUCE 1. Open Dragon, press F11 OBSERVED RESULT Nothing EXPECTED RESULT Go full screen. Can F11 key be made an alternate for the F key in place of Ctrl-Shift-F? SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475067] plymouth-kcm caused crash apon saving changes of boot splash screen
https://bugs.kde.org/show_bug.cgi?id=475067 --- Comment #2 from rustmil...@proton.me --- If you save then quickly exit then this bug occurs. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 475640] New: Make F11 be an alternate shortcut for fullscreen to be in harmony with other apps
https://bugs.kde.org/show_bug.cgi?id=475640 Bug ID: 475640 Summary: Make F11 be an alternate shortcut for fullscreen to be in harmony with other apps Classification: Applications Product: okular Version: 23.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: k...@callthecomputerdoctor.com Target Milestone: --- F11 is the standard keyboard shortcut to make a web browser full screen, which is what most people know, and this has been adopted by Kwrite, Kate, Gwenview, VLC and is used to hide/show the preview pane in Dolphin and the standard open/save dialog box. STEPS TO REPRODUCE 1. Open Okular, press F11 OBSERVED RESULT Nothing EXPECTED RESULT Should go full screen. Can F11 key be made an alternate for the Ctrl-Shift-F key? SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475639] New: plymouth-kcm caused crash apon saving changes of boot splash screen
https://bugs.kde.org/show_bug.cgi?id=475639 Bug ID: 475639 Summary: plymouth-kcm caused crash apon saving changes of boot splash screen Classification: Applications Product: systemsettings Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rustmil...@proton.me Target Milestone: --- Application: systemsettings (5.27.8) Qt Version: 5.15.11 Frameworks Version: 5.110.0 Operating System: Linux 6.5.7-arch1-1 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Save and exit system settings while still saving will cause crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f1c4d6c149d in QObjectPrivate::maybeSignalConnected(unsigned int) const () at /usr/lib/libQt5Core.so.5 #5 0x7f1c4d6cfdef in () at /usr/lib/libQt5Core.so.5 #6 0x7f1c155c4c06 in KCMPlymouth::busyChanged() (this=0x5560d01ba2b0) at /usr/src/debug/plymouth-kcm/build/src/kcm_plymouth_autogen/EWIEGA46WW/moc_kcm.cpp:304 #7 KCMPlymouth::setBusy(bool const&) (busy=, this=0x5560d01ba2b0) at /usr/src/debug/plymouth-kcm/plymouth-kcm-5.27.8/src/kcm.cpp:160 #8 KCMPlymouth::save() (this=0x5560d01ba2b0) at /usr/src/debug/plymouth-kcm/plymouth-kcm-5.27.8/src/kcm.cpp:206 #9 0x7f1c4e112d06 in KCModuleQml::save() (this=0x5560d130d620) at /usr/src/debug/kcmutils5/kcmutils-5.110.0/src/kcmoduleqml.cpp:306 #10 0x7f1c4e11ada8 in KCModuleProxy::save() (this=) at /usr/src/debug/kcmutils5/kcmutils-5.110.0/src/kcmoduleproxy.cpp:279 #11 0x7f1c4efe6ab6 in ModuleView::moduleSave(KCModuleProxy*) (this=0x5560d02e2270, module=) at /usr/src/debug/systemsettings/systemsettings-5.27.8/core/ModuleView.cpp:379 #12 0x7f1c4efe6e2f in ModuleView::moduleSave() (this=) at /usr/src/debug/systemsettings/systemsettings-5.27.8/core/ModuleView.cpp:370 #13 0x7f1c4efeb6af in ModuleView::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=0x7ffcb2e38bb0) at /usr/src/debug/systemsettings/build/core/systemsettingsview_autogen/EWIEGA46WW/moc_ModuleView.cpp:133 #14 0x7f1c4d6d06a3 in () at /usr/lib/libQt5Core.so.5 #15 0x7f1c4e8c2527 in KAuth::ObjectDecorator::authorized(KAuth::Action const&) () at /usr/lib/libKF5Auth.so.5 #16 0x7f1c4d6d04e7 in () at /usr/lib/libQt5Core.so.5 #17 0x7f1c4e45c677 in QAbstractButton::clicked(bool) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f1c4e45ef2a in () at /usr/lib/libQt5Widgets.so.5 #19 0x7f1c4e46042c in () at /usr/lib/libQt5Widgets.so.5 #20 0x7f1c4e4605d0 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7f1c4e3af1a1 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #22 0x7f1c4e3788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #23 0x7f1c4e37ddaf in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #24 0x7f1c4d69b5b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #25 0x7f1c4e37c0ea in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #26 0x7f1c4e3cce85 in () at /usr/lib/libQt5Widgets.so.5 #27 0x7f1c4e3cebd7 in () at /usr/lib/libQt5Widgets.so.5 #28 0x7f1c4e3788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #29 0x7f1c4d69b5b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #30 0x7f1c4db4194c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #31 0x7f1c4db2a6e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #32 0x7f1c4b55ec75 in () at /usr/lib/libQt5WaylandClient.so.5 #33 0x7f1c4bd0df19 in () at /usr/lib/libglib-2.0.so.0 #34 0x7f1c4bd6c2b7 in () at /usr/lib/libglib-2.0.so.0 #35 0x7f1c4bd0c112 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #36 0x7f1c4d6ea3cc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #37 0x7f1c4d69a2c4 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #38 0x7f1c4d69b763 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #39 0x5560ceff0bd9 in main(int, char**) (argc=, argv=) at /usr/src/debug/systemsettings/systemsettings-5.27.8/app/main.cpp:188 [Inferior 1 (process 17986) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 475638] using include in ssh config doesn't traverse all includes, only the first
https://bugs.kde.org/show_bug.cgi?id=475638 andreas changed: What|Removed |Added Version|unspecified |23.08.1 CC||something.burner.mail@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 475638] New: using include in ssh config doesn't traverse all includes, only the first
https://bugs.kde.org/show_bug.cgi?id=475638 Bug ID: 475638 Summary: using include in ssh config doesn't traverse all includes, only the first Classification: Frameworks and Libraries Product: kio-extras Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: SFTP Assignee: plasma-b...@kde.org Reporter: something.burner.m...@gmail.com Target Milestone: --- SUMMARY In order to make my `~/.ssh/` cleaner, I looked for ways to use multiple files in different folders together. I found Include and then set it all up in a structured way. When I tested the setup in the terminal to ssh into whatever host from any included config file, I'm able to connect no issue. When I then tried to move some files from one ssh host to another in dolphin, using sftp://, I only got connection to one, the other showed an `Authentication failed` error. These two targets are in different files, both included from `~/.ssh/config`. After some testing, I found out, that only the first Include actually gets parsed, not any other include in the same file, as when I changed the order of includes, suddenly the one that initially worked, didn't anymore, while the other now worked like nothing happened. STEPS TO REPRODUCE 1. set up the ssh config like so, with your own testing data, having the same config for both a and b, only with different names, to make it as simple as possible: ~/.ssh/config: # start Include ~/.ssh/a/config Include ~/.ssh/b/config # end ~/.ssh/a/config # start Host ahost HostName 192.168.0.48 User "root" IdentityFile ~/.ssh/a/akey # end ~/.ssh/b/config # start Host bhost HostName 192.168.0.48 User "root" IdentityFile ~/.ssh/b/bkey # end 2. validate both `ssh ahost` and `ssh bhost` work as expected 3. try connection to `sftp://ahost` and `sftp://bhost` 4. reverse the order of includes in `~/.ssh/config` 5. try step 3 again OBSERVED RESULT Only the host from the file included first will connect, the other will error with the following message: `Failed to resolve hostname bhost (Name or service not known)` (this is from the initial include order) EXPECTED RESULT Both hosts connect without any issue, similar to how the both work using `ssh host`. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (from the About this System panel) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 456661] Key binding conflict when F11 is doubly-bound to full screen mode
https://bugs.kde.org/show_bug.cgi?id=456661 Michael changed: What|Removed |Added CC||kde@callthecomputerdoctor.c ||om -- You are receiving this mail because: You are watching all bug changes.
[Marknote] [Bug 475637] New: Right clicking on a Notebook in the sidebar causes the UI to "jump"
https://bugs.kde.org/show_bug.cgi?id=475637 Bug ID: 475637 Summary: Right clicking on a Notebook in the sidebar causes the UI to "jump" Classification: Applications Product: Marknote Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@kaidan.im Reporter: justin.zo...@gmail.com CC: c...@carlschwan.eu, m...@kaidan.im Target Milestone: --- STEPS TO REPRODUCE 1. Have at least one notebook 2. Right-click on the notebook icon in the left notebook list OBSERVED RESULT UI elements "jump" EXPECTED RESULT Nothing or a context menu to manage that notebook (rename/delete) Latest flatpak from https://invent.kde.org/office/marknote/-/jobs/1237454/artifacts/file/marknote.flatpak -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475549] Intermittent Flickering/Disappearance of Browser and Task-bar panels during Plasma-Wayland sessions.
https://bugs.kde.org/show_bug.cgi?id=475549 --- Comment #4 from Gary S. Martin --- http://0x0.st/H4GM.txt Under the lts kernel, simpledrm is deactivated as it should be. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475549] Intermittent Flickering/Disappearance of Browser and Task-bar panels during Plasma-Wayland sessions.
https://bugs.kde.org/show_bug.cgi?id=475549 --- Comment #3 from Gary S. Martin --- The flickering occurs less often and for generally shorter durations under the lts kernel than under the current kernel. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 475636] System Monitor crashed sometimes when starting in GNOME with the error "stack smashing detected"
https://bugs.kde.org/show_bug.cgi?id=475636 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 475636] New: System Monitor crashed sometimes when starting in GNOME with the error "stack smashing detected"
https://bugs.kde.org/show_bug.cgi?id=475636 Bug ID: 475636 Summary: System Monitor crashed sometimes when starting in GNOME with the error "stack smashing detected" Classification: Applications Product: plasma-systemmonitor Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: matt.fagn...@bell.net CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 162313 --> https://bugs.kde.org/attachment.cgi?id=162313=edit Full trace of all threads of the third System Monitor crash SUMMARY I was using GNOME 45.0 on Wayland in a Fedora 39 KDE Plasma installation. I clicked on the button at top left of the screen. I entered monitor in the search bar and clicked on Plasma System Monitor. System Monitor crashed sometimes when starting in GNOME with the error "stack smashing detected" in the journal and the trace. This problem happened three times each of which were on the first time I ran System Monitor in different GNOME sessions. System Monitor briefly appeared and then crashed. System Monitor ran normally on subsequent times I ran it in the same GNOME session. drkonqi didn't appear the first two crashes. I removed plasma-drkonqi and reproduced the crash a third time so that the core dump would be saved. coredumpctl gdb showed that System Monitor aborted with the "stack smashing detected" error shown in __GI___fortify_fail in frame 5. Core was generated by `/usr/bin/plasma-systemmonitor'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7f27ed48ba00 (LWP 49125))] (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f27eb8aa8a3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7f27eb8588ee in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7f27eb8408ff in __GI_abort () at abort.c:79 #4 0x7f27eb8417d0 in __libc_message (fmt=fmt@entry=0x7f27eb9be309 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150 #5 0x7f27eb93dcd9 in __GI___fortify_fail (msg=msg@entry=0x7f27eb9be321 "stack smashing detected") at fortify_fail.c:24 #6 0x7f27eb93ef64 in __stack_chk_fail () at stack_chk_fail.c:24 #7 0x7f27ed7c463b in loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (v4=0x55c03f8eba30, object=, property=) at jsruntime/qv4qobjectwrapper.cpp:207 #8 0x7f27ed7c5525 in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) (object=0x7f27d02d35c0, engine=0x55c03f8eba30, lookup=0x55c0409f0d10) at jsruntime/qv4qobjectwrapper.cpp:880 #9 0x7f27ed7e5b0a in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) (frame=0xbfe5, frame@entry=0x7ffd40e123d0, engine=0x55c03f8eba30, code=0x7f277e9e2e2e "") at jsruntime/qv4vme_moth.cpp:641 #10 0x7f27ed7ea59f in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) (frame=frame@entry=0x7ffd40e123d0, engine=engine@entry=0x55c03f8eba30) at jsruntime/qv4vme_moth.cpp:466 --Type for more, q to quit, c to continue without paging--c #11 0x7f27ed77a512 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) (this=this@entry=0x55c0408e3df0, thisObject=, argv=argv@entry=0x7f27d02d35b0, argc=, context=) at jsruntime/qv4function.cpp:69 #12 0x7f27ed910760 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) (this=this@entry=0x55c0409f1ff0, callData=0x7f27d02d3580, isUndefined=isUndefined@entry=0x7ffd40e125bf) at qml/qqmljavascriptexpression.cpp:212 #13 0x7f27ed916ee7 in QQmlBinding::evaluate(bool*) (this=this@entry=0x55c0409f1ff0, isUndefined=isUndefined@entry=0x7ffd40e125bf) at ../../include/QtQml/5.15.10/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #14 0x7f27ed91b49b in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (this=0x55c0409f1ff0, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:254 #15 0x7f27ed918d35 in QQmlBinding::update(QFlags) (this=0x55c0409f1ff0, flags=...) at qml/qqmlbinding.cpp:194 #16 0x7f27ed8f4527 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=0x0) at qml/qqmlnotifier.cpp:104 #17 0x7f27ec0e81c0 in doActivate(QObject*, int, void**) (sender=0x55c0409f1910, signal_index=15, argv=0x0) at kernel/qobject.cpp:3817 #18
[KScreen] [Bug 457726] kscreen_backend_launcher block entering Screen Energy saving
https://bugs.kde.org/show_bug.cgi?id=457726 daxdow...@gmail.com changed: What|Removed |Added CC||daxdow...@gmail.com --- Comment #13 from daxdow...@gmail.com --- Still happening 10/14 on KDE Plasma 5.27.8. KDE Frameworks Version: 5.11.0 Qt VersioN: 5.15.10 Kernel Version: 6.5.7-300.fc39.x86_64 X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475635] New: "Show FPS" effect does nothing
https://bugs.kde.org/show_bug.cgi?id=475635 Bug ID: 475635 Summary: "Show FPS" effect does nothing Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mashkal2...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 162312 --> https://bugs.kde.org/attachment.cgi?id=162312=edit no fps SUMMARY "Show FPS" effect does not show FPS STEPS TO REPRODUCE 1. system settings > desktop effects 2. check show fps 3. apply OBSERVED RESULT fps is not shown EXPECTED RESULT fps is shown 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.
[valgrind] [Bug 475634] New: valgrind is no starting
https://bugs.kde.org/show_bug.cgi?id=475634 Bug ID: 475634 Summary: valgrind is no starting Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: massif Assignee: n...@valgrind.org Reporter: dark_foo...@yahoo.fr Target Milestone: --- SUMMARY I am running the git master version of 03 October 23. I am launching a heavy software Ran this : valgrind '--tool=massif' '--time-unit=ms' '--vgdb=yes' '--vgdb-error=0' '--trace-children=yes' '--threshold=0.01' '--main-stacksize=1000' my_soft & Valgrind is starting with this : ==2807== Massif, a heap profiler ==2807== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote ==2807== Using Valgrind-3.22.0.GIT and LibVEX; rerun with -h for copyright info But as I have a backtrace and this warning : ==2807== If you believe this happened as a result of a stack ==2807== overflow in your program's main thread (unlikely but ==2807== possible), you can try to increase the size of the ==2807== main thread stack using the --main-stacksize= flag. ==2807== The main thread stack size used in this run was 10002432. I re-do : valgrind '--tool=massif' '--time-unit=ms' '--vgdb=yes' '--vgdb-error=0' '--trace-children=yes' '--threshold=0.01' '--main-stacksize=1200' my_soft & I have no more the starting log: "Massif, a heap profiler" and : vgdb detailed_snapshot /tmp/massif2023-10-15_00-02-50_0.out vgdb error: no FIFO found and no pid given It is as "valgrind is not started at all" and Strangely by removing the "&" at the end of the line valgrind '--tool=massif' '--time-unit=ms' '--vgdb=yes' '--vgdb-error=0' '--trace-children=yes' '--threshold=0.01' '--main-stacksize=1200' my_soft I see the "Massif, a heap profiler" boot log. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ARM chipset -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475633] New: Some desktop effects preview gifs missing.
https://bugs.kde.org/show_bug.cgi?id=475633 Bug ID: 475633 Summary: Some desktop effects preview gifs missing. Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mashkal2...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 162311 --> https://bugs.kde.org/attachment.cgi?id=162311=edit . SUMMARY The following effects have preview gifs that fail to load: sliding popups track mouse snap helper invert fade desktop desktop grid overview STEPS TO REPRODUCE 1. workspace behaviour > desktop effects > (find effect) > click video preview button 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475632] External monitor turns off during start of Plasma
https://bugs.kde.org/show_bug.cgi?id=475632 Piotr Mierzwinski changed: What|Removed |Added Keywords||qt6, wayland CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475632] New: External monitor turns off during start of Plasma
https://bugs.kde.org/show_bug.cgi?id=475632 Bug ID: 475632 Summary: External monitor turns off during start of Plasma Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Since couple weeks I experience issue like in subject. I work with passwordless user account, which starts Wayland session. Monitor is connected via HDMI, via USB (type C) hub. Please notice that this was working well couple weeks ago. Anyway. Splash screen starts working, and after couple of seconds I can see like my external monitor turns off. Using keyboard I wake up it and get lock screen. After unlock it, Plasma starts normally, so in my case are opening Firefox windows (I have save session turned on, but unfortunately other applications are not restored) and shows: wallpaper and panel. STEPS TO REPRODUCE prerequisite: external monitor 1. Start Plasma with passwordless user account (not sure if this is enough, didn't test with normal account) 2. 3. OBSERVED RESULT External monitor turns off in moment of start Plasma EXPECTED RESULT External monitor should not turns off in moment of start Plasma SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240 Qt Version: 6.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no title-bar under Wayland: add Qt plugin wayland-decoration-client.
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #10 from Bob --- Inconclusive, that one doesn't even want to start on Ubuntu (23.10) I'm afraid: ``` ./digikam-master-381-linux-gcc-x86_64.AppImage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. -- Detected host Linux ubuntu-64-23.10 -- AppImage mounted directory: /tmp/.mount_digikaHnSI0k Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so Check library libpango-1.0.so.0 Check library libpangocairo-1.0.so.0 Check library libgmodule-2.0.so.0 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0:/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 digikam: symbol lookup error: /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0: undefined symbol: g_string_free_and_steal Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. QSocketNotifier: Can only be used with threads started with QThread /tmp/.mount_digikaHnSI0k/AppRun.wrapped: symbol lookup error: /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_proxy_marshal_flags ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475631] New: Desktop effect activation requirements not visible in menu
https://bugs.kde.org/show_bug.cgi?id=475631 Bug ID: 475631 Summary: Desktop effect activation requirements not visible in menu Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mashkal2...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY The settings button for desktop effects is not clickable until the effect is enabled and applied. It's annoying to have to check the box, apply, click settings, read activation requirements, close settings, perform activation requirements just to see what the effect does STEPS TO REPRODUCE 1. desktop effects 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475258] Since 3 days cannot update the system
https://bugs.kde.org/show_bug.cgi?id=475258 --- Comment #3 from Piotr Mierzwinski --- I'm not going to test it. Just back to "Unstable Edition", which I can update every day. I believe that when other (qt5) applications (konsole and others) will be ready for qt6 then will appear in "Unstable Edition". -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475630] New: crashes and misbehaves when compose key sequence is begun then canceled
https://bugs.kde.org/show_bug.cgi?id=475630 Bug ID: 475630 Summary: crashes and misbehaves when compose key sequence is begun then canceled Classification: Applications Product: kate Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: daniel.san...@pobox.com Target Milestone: --- Application: kate (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.5.0-2-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: if I accidentally hit the compose key and then undo, I find that my undo history becomes corrupted. This particular time, it actually crashed after accidentally hitting it.· I'm on bookworm, so this is the most recent stable Debian. I have not noticed this flaw in "Bullseye" The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #4 0x7f0815d54d27 in ?? () from /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #5 0x7f0815d531ea in ?? () from /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #6 0x7f0815d57e02 in KateUndoManager::undo() () from /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #7 0x7f08166e8f7c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f081755c782 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f081755f3ab in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f081755ff7d in QAction::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f0817562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f08166b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0816d6c76b in QShortcutMap::dispatchEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7f0816d6d0bb in QShortcutMap::tryShortcut(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f0816d15376 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7f0816d390cd in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7f0810de9063 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so #18 0x7f08166e8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f0817c9103f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #20 0x7f08166dd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f0817562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f08166b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f08166b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f081670a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f081451e7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f081451ea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f081451eacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f0816709836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f08166b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f08166b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x55ca2108ee33 in ?? () #32 0x7f08162461ca in __libc_start_call_main (main=main@entry=0x55ca2108dfa0, argc=argc@entry=3, argv=argv@entry=0x7ffec8294798) at ../sysdeps/nptl/libc_start_call_main.h:58 #33 0x7f0816246285 in __libc_start_main_impl (main=0x55ca2108dfa0, argc=3, argv=0x7ffec8294798, init=, fini=, rtld_fini=, stack_end=0x7ffec8294788) at ../csu/libc-start.c:360 #34 0x55ca21090a91 in ?? () [Inferior 1 (process ) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 475117] Kasts built against qt6 version: various errors, menu and dialog glitches
https://bugs.kde.org/show_bug.cgi?id=475117 --- Comment #6 from ratijas --- I can confirm that our Dialogs are not in their greatest shape -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475579] Monitor visualization is too narrow on a vertical screen
https://bugs.kde.org/show_bug.cgi?id=475579 --- Comment #3 from ratijas --- > bot, you are drunk I tried it before. The bot will force-set qt6 keyword again and again anyway, so I guess it needs to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] New: Plasma Wayland session (kwin_wayland) random crashes (segfault)
https://bugs.kde.org/show_bug.cgi?id=475629 Bug ID: 475629 Summary: Plasma Wayland session (kwin_wayland) random crashes (segfault) Classification: Plasma Product: kwin Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: irecca@gmail.com Target Milestone: --- Created attachment 162310 --> https://bugs.kde.org/attachment.cgi?id=162310=edit backtrace SUMMARY Plasma Wayland session crashes randomly for me. kwin_wayland[1248]: segfault at 160 ip 7ff88534f136 sp 7ffd0ea0db30 error 6 in libQt5Qml.so.5.15.11[7ff8852a7000+281000] likely on CPU 15 (core 7, socket 0) I suspect it started after one of the latest minor Qt5 updates, backtrace points into Qt5Qml 5.15.11. STEPS TO REPRODUCE Unknown, crashes appear randomly. OBSERVED RESULT kwin_wayland crashes. EXPECTED RESULT kwin_wayland should not crash. SOFTWARE/OS VERSIONS Linux: 6.5.7 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Arch Linux packages: kwin 5.27.8-4 plasma-desktop 5.27.8-2 plasma-wayland-session 5.27.8-2 qt5-base 5.15.11+kde+r136-1 qt5-declarative 5.15.11+kde+r30-1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475628] New: Dolphin opens incorrect folders on startup
https://bugs.kde.org/show_bug.cgi?id=475628 Bug ID: 475628 Summary: Dolphin opens incorrect folders on startup Classification: Applications Product: dolphin Version: 23.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mashkal2...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin always reopens same locations on startup. STEPS TO REPRODUCE 1. Ensure that "show on startup" is set to some arbitrary directory 2. log in 3. OBSERVED RESULT Dolphin is opened, with multiple tabs and windows, none of which are the location specified in startup. EXPECTED RESULT dolphin is not opened. But even if it is, only a single window is opened. But even if multiple windows are opened, only a single tab is opened in each one. But even if multiple tabs are opened, they are opened to the location specified in the startup box. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.2.0-34-generic (64-bit) Graphics Platform: X11 Processors: 20 × 13th Gen Intel® Core™ i5-13600K Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Manufacturer: ASRock Product Name: Z690M-ITX/ax -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475585] KPhotoAlbum crashes on clicking "Copy Image to ..." in Full screen preview in Annotations window
https://bugs.kde.org/show_bug.cgi?id=475585 Johannes Zarl-Zierl changed: What|Removed |Added Status|VERIFIED|RESOLVED Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/kphotoalbum/-/commit/2 |hics/kphotoalbum/-/commit/c |516c6e6ba68fba2ba92d758124c |6c7df0d8cdb79a9e2ea49f88c1d |726447bb6126|181beabb6bae Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Johannes Zarl-Zierl --- Git commit c6c7df0d8cdb79a9e2ea49f88c1d181beabb6bae by Johannes Zarl-Zierl. Committed on 14/10/2023 at 23:33. Pushed by johanneszarl into branch 'master'. Restrict set of context menu actions available in annotation dialog's fullscreen preview This also removes the copy/link actions that caused the crash in bug #475585, which should never have been available at this place in the program. M +1-1AnnotationDialog/Dialog.cpp M +3-0CHANGELOG.md M +5-4MainWindow/Window.cpp M +84 -45 Viewer/ViewerWidget.cpp M +6-3Viewer/ViewerWidget.h https://invent.kde.org/graphics/kphotoalbum/-/commit/c6c7df0d8cdb79a9e2ea49f88c1d181beabb6bae -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 475626] Discover program for Grub Customizer locked with the word Loading
https://bugs.kde.org/show_bug.cgi?id=475626 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.24.7 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.24.7, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 475586] Still Can't Add Calendar from Google to Korganizer
https://bugs.kde.org/show_bug.cgi?id=475586 --- Comment #2 from jshand2...@gmail.com --- Created attachment 162309 --> https://bugs.kde.org/attachment.cgi?id=162309=edit after setting up google calendar -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 475586] Still Can't Add Calendar from Google to Korganizer
https://bugs.kde.org/show_bug.cgi?id=475586 --- Comment #1 from jshand2...@gmail.com --- Created attachment 162308 --> https://bugs.kde.org/attachment.cgi?id=162308=edit after restart of service -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 475627] New: Unable to access store.kde.org
https://bugs.kde.org/show_bug.cgi?id=475627 Bug ID: 475627 Summary: Unable to access store.kde.org Classification: Websites Product: www.kde.org Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: rvdois+rvu...@rokejulianlockhart.anonaddy.com Target Milestone: --- Created attachment 162307 --> https://bugs.kde.org/attachment.cgi?id=162307=edit Depiction of the problem. SUMMARY Unable to access https://store.kde.org/ STEPS TO REPRODUCE 1. Visit https://store.kde.org/ OBSERVED RESULT See the attached file. EXPECTED RESULT It should load. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231012 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.6-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475357] Regression in Dolphin 23.08.1 - Expandable folders in Details view mode broken
https://bugs.kde.org/show_bug.cgi?id=475357 Shay G changed: What|Removed |Added CC||govers...@gmail.com --- Comment #2 from Shay G --- I have something similar but I don't use LUKS. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 475626] New: Discover program for Grub Customizer locked with the word Loading
https://bugs.kde.org/show_bug.cgi?id=475626 Bug ID: 475626 Summary: Discover program for Grub Customizer locked with the word Loading Classification: Applications Product: Discover Version: 5.24.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: sjfog...@outlook.com CC: aleix...@kde.org Target Milestone: --- Created attachment 162306 --> https://bugs.kde.org/attachment.cgi?id=162306=edit screeshoot of what the discover utility program looks like for grup customizer 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. installing software and selected multiple applications 2. Discover was unable to handle the multiple selection of apps 3. I let it sit over night and the next day is when I discovered that the grub customize is locked with the word Loading OBSERVED RESULT grub customize is locked with the word "Loading" EXPECTED RESULT It should say Install or Remove SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475625] New: Krita refuses to open recently created, and older kra files
https://bugs.kde.org/show_bug.cgi?id=475625 Bug ID: 475625 Summary: Krita refuses to open recently created, and older kra files Classification: Applications Product: krita Version: 5.1.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: la...@disroot.org Target Milestone: --- Created attachment 162305 --> https://bugs.kde.org/attachment.cgi?id=162305=edit A wall of drippy latex with a paw sticking out. Fails to load in Krita 5.1.5 SUMMARY I cannot open about half of the kra files I've made throughout my lifetime. The error message that I get is as follows: Could not open /path/to/file.kra. Reason: Krita does not support this file format. STEPS TO REPRODUCE 1. Download the attachment 2. Open it in Krita OBSERVED RESULT Could not open /path/to/file.kra. Reason: Krita does not support this file format. EXPECTED RESULT Opened successfully SOFTWARE/OS VERSIONS OS: Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 6.1.53-gentoo-r1 Pretty Productname: Gentoo Linux Product Type: gentoo Product Version: 2.14 Desktop: i3, no compositor, NVIDIA proprietary driver Qt Version: 5.15.10 ADDITIONAL INFORMATION I thought this only happened to old files at first, but today I made another Krita file and in the evening it failed to open! D: -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475624] filter masks + layers crash my tablet
https://bugs.kde.org/show_bug.cgi?id=475624 Katarzyna Buzala changed: What|Removed |Added Component|* Unknown |Filter Layers -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475624] New: filter masks + layers crash my tablet
https://bugs.kde.org/show_bug.cgi?id=475624 Bug ID: 475624 Summary: filter masks + layers crash my tablet Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: katarzynabuzala2...@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 0. The info it wants me to paste in cant be copied in 1. Use samsung s7fe tablet 2. try to use a filter layer or mask OBSERVED RESULT Program freezes completely and dies. Filter masks and layers just DO NOT WORK on the samsung s7FE EXPECTED RESULT filter masks/layers are supposed to change the colours of stuff underneath. I want to use the gradient map feature. SOFTWARE/OS VERSIONS Samsung s7FE tablet (bought new, used for 2 weeks as the first owner) Android version 13 ADDITIONAL INFORMATION also left feedback on the google play store in case they can help -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468910] crashes on startup after nested timeline insert. Cannot save nor reuse files
https://bugs.kde.org/show_bug.cgi?id=468910 comicfans44 changed: What|Removed |Added CC||comicfan...@gmail.com --- Comment #5 from comicfans44 --- I have similar problem, I'm already using 23.08.1 (win10), my operation steps: 1. created a 1920*1200 30fps project, add many clips and effects 2. create new 1920*1080 25fps project, add project1 as media 3. try to insert project1 media into timeline 4. kdenlive crashed I tried several times, kdenlive always crash and can't recover. and I changed second new project as 1920 * 1080 30 fps, such operation can complete -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475615] Some Plasmashell context menus are in its own window when using drawing tablet
https://bugs.kde.org/show_bug.cgi?id=475615 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Nate Graham --- This is on Wayland, right? Can you reproduce this with all context menus, or only some? If only some, which ones? I tried to reproduce on Wayland with my stylus, but even though it has multiple buttons, none of them seem to trigger a right-click in any apps I tried with. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 Björn Bidar (Thaodan) changed: What|Removed |Added CC||kalzwa...@yahoo.com --- Comment #9 from Björn Bidar (Thaodan) --- *** Bug 462042 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 444301] Akonadi opens gmail login webpage when adding a yahoo account
https://bugs.kde.org/show_bug.cgi?id=444301 Björn Bidar (Thaodan) changed: What|Removed |Added CC||bjorn.bi...@thaodan.de Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Björn Bidar (Thaodan) --- *** This bug has been marked as a duplicate of bug 457233 *** -- You are receiving this mail because: You are watching all bug changes.
