[krusader] [Bug 445549] kioslave5 blocking umount
https://bugs.kde.org/show_bug.cgi?id=445549 --- Comment #18 from Michael Lashkevich --- (In reply to darek from comment #17) > (In reply to Michael Lashkevich from comment #16) > This statement is false. I never use "Mount and open" but "Mount" only and I > have the same problem with locking. See my comment #6 and #7 for sysinfo. Maybe it behaves different in different versions of KDE. I tell what happens in my system (which can be seen in my first comment). -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 494065] Coredump on exiting gwenview annotate-tool
https://bugs.kde.org/show_bug.cgi?id=494065 --- Comment #4 from Michael Hamilton --- I was altering jpegs from a Samsung phone, I just tried images from a different camera (very old Olympus E-M5) with the same result. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 494065] Coredump on exiting gwenview annotate-tool
https://bugs.kde.org/show_bug.cgi?id=494065 --- Comment #3 from Michael Hamilton --- Here is a coredump from when I did a crop, crop/resize/... These other operations often work, but sometimes dump core. There were no message in the journal in this instance, just the report of a core dump. (gdb) bt #0 0x7fd5f2bd0180 in QObjectPrivate::isSignalConnected(unsigned int, bool) const () at /lib64/libQt6Core.so.6 #1 0x7fd5f2ce1efe in ??? () at /lib64/libQt6Core.so.6 #2 0x7fd5f2cd770a in QAbstractAnimation::setCurrentTime(int) () at /lib64/libQt6Core.so.6 #3 0x7fd5f2cd78d9 in ??? () at /lib64/libQt6Core.so.6 #4 0x7fd5f2cd13f1 in QUnifiedTimer::updateAnimationTimers() () at /lib64/libQt6Core.so.6 #5 0x7fd5f2cd66d1 in QAnimationDriver::advanceAnimation() () at /lib64/libQt6Core.so.6 #6 0x7fd5f2bd1dd6 in QObject::event(QEvent*) () at /lib64/libQt6Core.so.6 #7 0x7fd5f3dc2f6e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt6Widgets.so.6 #8 0x7fd5f2b8ec30 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #9 0x7fd5f2ceca5a in QTimerInfoList::activateTimers() () at /lib64/libQt6Core.so.6 #10 0x7fd5f2dc2e04 in ??? () at /lib64/libQt6Core.so.6 #11 0x7fd5efcc1fb8 in ??? () at /lib64/libglib-2.0.so.0 #12 0x7fd5efcc3d38 in ??? () at /lib64/libglib-2.0.so.0 #13 0x7fd5efcc43ec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #14 0x7fd5f2dc1adc in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt6Core.so.6 #15 0x7fd5f2b993db in QEventLoop::exec(QFlags) () at /lib64/libQt6Core.so.6 #16 0x7fd5f2b92bb6 in QCoreApplication::exec() () at /lib64/libQt6Core.so.6 #17 0x5616b027d80c in main (argc=, argv=) at /usr/src/debug/gwenview-24.08.1/app/main.cpp:218 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 445549] kioslave5 blocking umount
https://bugs.kde.org/show_bug.cgi?id=445549 --- Comment #16 from Michael Lashkevich --- (In reply to Michael Lashkevich from comment #14) > I confirm this bug. > > OpenSUSE 15.5, > Plasma-5.27.9 > krusader-2.8.1 I found that the problem appears when I use the (default) option "Mount and open" from the tray. If I use the option "Mount", and open the mounted filesystem directly from krusader, I can unmount flawlessly after I close the corresponding tab in krusader. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 494065] Coredump on exiting gwenview annotate-tool
https://bugs.kde.org/show_bug.cgi?id=494065 --- Comment #2 from Michael Hamilton --- If I perform an operation, such as resize, before using annotate, then I can successfully exit the annotate and save the result. But sometimes a resize or crop will also cause a coredump - not sure if it's the same issue though. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 494065] Coredump on exiting gwenview annotate-tool
https://bugs.kde.org/show_bug.cgi?id=494065 --- Comment #1 from Michael Hamilton --- This appears in the systemd journal prior to but in the same second as each coredump: org.kde.kdegraphics.gwenview.lib: Gwenview cannot apply color profile on QImage::Format_ARGB32_Premultiplied images -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 494065] New: Coredump on exiting gwenview annotate-tool
https://bugs.kde.org/show_bug.cgi?id=494065 Bug ID: 494065 Summary: Coredump on exiting gwenview annotate-tool Classification: Applications Product: gwenview Version: 24.08.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: mich...@actrix.gen.nz Target Milestone: --- Created attachment 174381 --> https://bugs.kde.org/attachment.cgi?id=174381&action=edit coredumpctl/gdb log with a backtrace, SUMMARY On exiting the gwenview annotate tool, gwenview core-dumps. Happens every time. STEPS TO REPRODUCE 1. Open a jpeg (doesn't appear to matter what file I try) 2. Choose to Annotate 3. Annotate with a line or arrow (don't think it matters what you do) 4. Press OK in the Annotate window OBSERVED RESULT Gwenview disappears and coredumpctl lists a new coredump EXPECTED RESULT Annotate window closes and gwenview shows the annotated result. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20241002 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.7-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 ADDITIONAL INFORMATION Attached a coredumpctl/gdb log with a backtrace, but only one line number is reported /usr/src/debug/gwenview-24.08.1/app/main.cpp:218 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 445549] kioslave5 blocking umount
https://bugs.kde.org/show_bug.cgi?id=445549 --- Comment #15 from Michael Lashkevich --- (In reply to Michael Lashkevich from comment #14) > I confirm this bug. > > OpenSUSE 15.5, > Plasma-5.27.9 > krusader-2.8.1 Forgot to add: encryption does not matter. Copying does not matter. It is sufficient to open a filesystem in krusader, and it is blocked till killing kioslave5 or exiting krusader. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 445549] kioslave5 blocking umount
https://bugs.kde.org/show_bug.cgi?id=445549 Michael Lashkevich changed: What|Removed |Added CC||lashk...@landau.ac.ru --- Comment #14 from Michael Lashkevich --- I confirm this bug. OpenSUSE 15.5, Plasma-5.27.9 krusader-2.8.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 335027] Touchpad on LENOVO X240
https://bugs.kde.org/show_bug.cgi?id=335027 --- Comment #29 from Michael --- PleasE ref here https://bugs.kde.org/show_bug.cgi?id=335027#c5. I'll follow up asap -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 493717] Kdiff3 1.11.4 is not updating the correct display version during the setup installation
https://bugs.kde.org/show_bug.cgi?id=493717 michael changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from michael --- The upload has been done the new checksum show be. SHA-256: 71a528f94ba4c9ebebdd6a34115e082ab9b576cdf93e9bcfa3ff269cf05e3b2d kdiff3-1.11.4-windows-64-cl.exe SHA-1: e8aefe8a6906c10128c1fe4003b60216eaffecbd kdiff3-1.11.4-windows-64-cl.exe It may take a day or two for mirrors to update. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 493717] Kdiff3 1.11.4 is not updating the correct display version during the setup installation
https://bugs.kde.org/show_bug.cgi?id=493717 --- Comment #3 from michael --- that's where it's going to be waiting for system admin to action the ticket. Oct 1, 2024 6:37:34 AM Meta : > https://bugs.kde.org/show_bug.cgi?id=493717 > > --- Comment #2 from Meta --- > (In reply to michael from comment #1) >> Corrected installer has been uploaded https://phabricator.kde.org/T17630. >> It likely be 24-48 hrs before all mirrors pickup the change once the ticket >> closes > > Hi Michael, > > We are not able to login to https://phabricator.kde.org/T17630 > > Can you please upload the correct insaller at > https://download.kde.org/stable/kdiff3/?C=M;O=D > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 493717] Kdiff3 1.11.4 is not updating the correct display version during the setup installation
https://bugs.kde.org/show_bug.cgi?id=493717 --- Comment #1 from michael --- Corrected installer has been uploaded https://phabricator.kde.org/T17630. It likely be 24-48 hrs before all mirrors pickup the change once the ticket closes -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 493717] Kdiff3 1.11.4 is not updating the correct display version during the setup installation
https://bugs.kde.org/show_bug.cgi?id=493717 michael changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 493547] KDiff3 1.11.4 crashes silently on open on Windows
https://bugs.kde.org/show_bug.cgi?id=493547 michael changed: What|Removed |Added Ever confirmed|1 |0 Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #4 from michael --- Trying uninstalling and reinstalling something might have been left behind for the old install. KDiff3 will attempt to remove all files in its install directory during an upgrade but may need a reboot to complete this process. Due how kde translations work the shell extension ends up depending on qt. These files being in use prevents their full removal with out a reboot. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 493547] KDiff3 1.11.4 crashes silently on open on Windows
https://bugs.kde.org/show_bug.cgi?id=493547 michael changed: What|Removed |Added Resolution|--- |WORKSFORME Status|ASSIGNED|RESOLVED --- Comment #2 from michael --- Just verified that the installer itself does not cause this issue if retrieved from downloaded via https://download.kde.org/stable/kdiff3/kdiff3-1.11.4-windows-64-cl.exe.mirrorlist. My issue was triggered by having a mix of qt 6.7.1 and 6.7.2 on available on the PATH. When qt detects mixed versions it aborts and attempts to log a message to console. This message may not be visible in windows. If you upgraded from an older version of kdiff3 it no longer requires separate installation of qt or kf. Theses and all other dependencies are now bundled with it and will be installed under the same directory as kdiff3 itself. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 493716] kdiff3 opens in full screen mode, impossible to exit this mode
https://bugs.kde.org/show_bug.cgi?id=493716 --- Comment #1 from michael --- Does the standard short cut alt-F3 not work for you? That shortcut is configurable so it may have been changed. In case it will be the same for all kde based apps. It should also be in the dialog that comes up on switching to full screen mode. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 493715] New: Make selection mode available on the file picker dialogs
https://bugs.kde.org/show_bug.cgi?id=493715 Bug ID: 493715 Summary: Make selection mode available on the file picker dialogs Classification: Applications Product: dolphin Version: 24.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Selection Mode Assignee: kfm-de...@kde.org Reporter: sbnav...@proton.me CC: felixer...@kde.org Target Milestone: --- SUMMARY Dolphin's selection mode triggered by spacebar is currently not available on file picker dialogs. STEPS TO REPRODUCE 1. Open a file picker dialog 2. Press spacebar 3. Selection mode is not triggered like Dolphin windows EXPECTED RESULT 1. Selection mode triggered by spacebar should be present also on the file picker window dialogs. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LG Electronics Product Name: 15Z90Q-G.AA52P System Version: 0.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493701] New: Make notifications in the notification widget history actionable
https://bugs.kde.org/show_bug.cgi?id=493701 Bug ID: 493701 Summary: Make notifications in the notification widget history actionable Classification: Plasma Product: plasmashell Version: 6.1.90 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: sbnav...@proton.me CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY Presently, only on-screen notification pop-ups are actionable, meaning once clicked, they open the app that originated the notification. However, once the pop-up time is over and the notification goes into the notification widget unread history, they are no longer actionable. Ideally, notifications should be actionable when clicked from the notification widget after pop-up time has elapsed. STEPS TO REPRODUCE 1. Trigger a Plasma notification. 2. Let the pop-up time elapse until the notification goes into the notification history. 3. Open the notification widget 4. Notifications are not actionable, clicking does nothing. EXPECTED RESULT 1. Notifications in the notification widget history should be actionable the same way as on-screen pop-up notifications. Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LG Electronics Product Name: 15Z90Q-G.AA52P System Version: 0.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 492222] "The file or folder does not exist" error message appears when program is launched.
https://bugs.kde.org/show_bug.cgi?id=49 --- Comment #6 from Michael O'Sullivan --- Hi, The error message disappears when “Reset Configuration” in the Help Menu is clicked. Problem solved. Kind regards Michael O’Sullivan e-mail: michaelanthonyosulli...@gmail.com On 10 Sep 2024, 13:35 +0100, michaelanthonyosulli...@gmail.com, wrote: > Hi, > > The bug is still there. > > > > > > Kind regards > > Michael O’Sullivan MSc MBA 🇺🇦 > Tel: +44 (0) 1622 736 241 > Mob: +44 (0) 74 11 45 22 50 > e-mail: michaelanthonyosulli...@gmail.com > e-mail: m...@sullivan-net.com > e-mail: michaelosulli...@protonmail.com > e-mail: michaelosulli...@dunelm.org.uk > Skype: mikeosullivan > On 10 Sep 2024, 04:47 +0100, Bug Janitor Service , > wrote: > > https://bugs.kde.org/show_bug.cgi?id=49 > > > > --- Comment #3 from Bug Janitor Service --- > > 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 > > days. > > Please provide the requested information, then set the bug status to > > REPORTED. > > If there is no change for at least 30 days, it will be automatically closed > > as > > RESOLVED WORKSFORME. > > > > For more information about our bug triaging procedures, please read > > 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 reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 493550] Breeze doesn't allow "menubar color customization by setting cusotm QPalette" anymore
https://bugs.kde.org/show_bug.cgi?id=493550 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 493547] KDiff3 1.11.4 crashes silently on open on Windows
https://bugs.kde.org/show_bug.cgi?id=493547 michael changed: What|Removed |Added Status|REPORTED|ASSIGNED Priority|NOR |HI Ever confirmed|0 |1 --- Comment #1 from michael --- Looks like craft has mixed qt binaries. Awaiting fix. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 353032] Add ability to set screen brightness for non-laptop displays so I can adjust to the room's lighting
https://bugs.kde.org/show_bug.cgi?id=353032 --- Comment #9 from Michael Ziegler --- Thanks for all the work :) I'm actually still interested in this and can't wait to try it out :D Much appreciated. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 489815] Shell Extension loads Qt6Core.dll and other DLLs.
https://bugs.kde.org/show_bug.cgi?id=489815 michael changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 489815] Shell Extension loads Qt6Core.dll and other DLLs.
https://bugs.kde.org/show_bug.cgi?id=489815 michael changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |NEEDSINFO --- Comment #3 from michael --- The exention is now optional if it causes an issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493510] New: Virtual desktops keep resetting their names after a reboot
https://bugs.kde.org/show_bug.cgi?id=493510 Bug ID: 493510 Summary: Virtual desktops keep resetting their names after a reboot Classification: Plasma Product: plasmashell Version: 6.1.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: sbnav...@proton.me CC: h...@kde.org Target Milestone: 1.0 SUMMARY When renaming virtual desktops, they only persist as long as the next reboot. STEPS TO REPRODUCE 1. Trigger overview / open System Settings - Window Management - Virtual Desktops 2. Rename virtual desktops from the default "Desktop 1", "Desktop 2" to another name. 3. Reboot 4. Virtual desktops reset to the default names "Desktop 1", "Desktop 2". EXPECTED RESULT Once renamed, virtual desktops should keep their new names until explicitly changed by the user. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LG Electronics Product Name: 15Z90Q-G.AA52P System Version: 0.1 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 489538] kdiff3 adds special characters on merge
https://bugs.kde.org/show_bug.cgi?id=489538 --- Comment #3 from michael --- What are the output and input encodings triggering this? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 446228] can't search bookmarks while mark microsoft edge as default web browser
https://bugs.kde.org/show_bug.cgi?id=446228 Michael changed: What|Removed |Added CC||sbnav...@proton.me --- Comment #4 from Michael --- *** Bug 492876 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 492876] Bookmark search not working with Plasma Search plugin
https://bugs.kde.org/show_bug.cgi?id=492876 Michael changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Michael --- *** This bug has been marked as a duplicate of bug 446228 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441643] Moving grouped pictures to an album changes file extension to lowercase => tagging etc. is lost
https://bugs.kde.org/show_bug.cgi?id=441643 --- Comment #9 from Michael Miller --- I'm unable to reproduce the issue with 8.5.0 pre-release on MacOS Sonoma 14.6.1. @Harald, are you able to reproduce the issue with the new pre-release version? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402346] The digikamrc file is not recorded into the digikam directory
https://bugs.kde.org/show_bug.cgi?id=402346 --- Comment #13 from Michael Miller --- Gilles and Maik, Should we be using QStandardPaths::AppConfigLocation instead of QStandardPaths::GenericConfigLocation? >From the Qt docs: > QStandardPaths::GenericConfigLocation Returns a directory location where > user-specific configuration files shared between multiple applications should > be written. This is a generic value and the returned path is never empty. > QStandardPaths::AppConfigLocation Returns a directory location where > user-specific configuration files should be written. This is an > application-specific directory, and the returned path is never empty. This > enum value was added in Qt 5.5. https://doc.qt.io/qt-6/qstandardpaths.html We could easily add some code to check for the old config file location and move it when people upgrade. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491042] MariaDB (MySQL) embedded files missing in fresh install
https://bugs.kde.org/show_bug.cgi?id=491042 --- Comment #23 from Michael Miller --- (In reply to Maik Qualmann from comment #22) > MariaDB appears to be installed in: > > /Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadbd > > MariaDB appears to be compiled with the version number in the path: > > /Applications/digiKam.org/digikam.app/Contents//lib/mariadb//lib/mariadb-10. > 11/bin/mariadbd > > Presumably mariaDB uses the path with version number in its own config. > Maybe a symlink will help? > > Maik I just added: >sudo ln -s "./mariadb" >/Applications/digiKam.org/digikam.app/Contents/lib/mariadb-10.11 but it didn't work. Same error. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491042] MariaDB (MySQL) embedded files missing in fresh install
https://bugs.kde.org/show_bug.cgi?id=491042
--- Comment #21 from Michael Miller ---
michmill@Michaels-Virtual-Machine ~ %
/Applications/digiKam.org/digikam.app/Contents/MacOS/digikam
digikam.widgets: Breeze icons resource file found
digikam.general: Qt standard translations removed: 0
digikam.general: Qt standard translations path:
"/Applications/digiKam.org/digikam.app/Contents/Resources/translations"
digikam.general: Loaded Qt standard translations "en_US" from catalog "qt"
digikam.general: Loaded Qt standard translations "en_US" from catalog "qtbase"
digikam.general: Loaded Qt standard translations "en_US" from catalog "qt_help"
digikam.general: Loaded Qt standard translations "en_US" from catalog
"qtdeclarative"
digikam.general: Loaded Qt standard translations "en_US" from catalog
"qtmultimedia"
digikam.general: Loaded Qt standard translations "en_US" from catalog
"qtwebengine"
digikam.general: Loaded Qt ECM translations "en" from catalog "kcoreaddons6_qt"
digikam.general: Loaded Qt ECM translations "en" from catalog
"kwidgetsaddons6_qt"
qt.svg: Could not create image from "/media/250gb/valokuvat/Syksy 02-09-05
Kuusamo, inkavaaralla luonnonpuistossa suomen komeimman kosken
kuvaamista/img_5766_4.jpg"
qt.svg: Could not create image from "/media/250gb/valokuvat/Syksy 02-09-05
Kuusamo, inkavaaralla luonnonpuistossa suomen komeimman kosken
kuvaamista/img_5766_4.jpg"
qt.qpa.fonts: Populating font family aliases took 65 ms. Replace uses of
missing font family "Bitstream Vera Sans" with one that exists to avoid this
cost.
digikam.general: Switch to widget style: "Breeze"
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type:"QMYSQL"
DB Core Name:"digikam"
DB Thumbs Name: "digikam"
DB Face Name:"digikam"
DB Similarity Name: "digikam"
Connect Options:
"UNIX_SOCKET=/Users/michmill/Library/Application
Support/digikam/digikam/db_misc/mysql.socket"
Host Name: ""
Host Port: -1
WAL Mode:false
Internal Server: true
Internal Server Path:"/Users/michmill/testpics"
Internal Server Init Cmd:
"/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadb-install-db"
Internal Server Admin Cmd:
"/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadb-admin"
Internal Server Program Cmd:
"/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadbd"
Internal Server Upgrade Cmd:
"/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadb-upgrade"
Username:"root"
Password:""
digikam.databaseserver: Database Parameters:
Type:"QMYSQL"
DB Core Name:"digikam"
DB Thumbs Name: "digikam"
DB Face Name:"digikam"
DB Similarity Name: "digikam"
Connect Options:
"UNIX_SOCKET=/Users/michmill/Library/Application
Support/digikam/digikam/db_misc/mysql.socket"
Host Name: ""
Host Port: -1
WAL Mode:false
Internal Server: true
Internal Server Path:"/Users/michmill/testpics"
Internal Server Init Cmd:
"/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadb-install-db"
Internal Server Admin Cmd:
"/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadb-admin"
Internal Server Program Cmd:
"/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadbd"
Internal Server Upgrade Cmd:
"/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadb-upgrade"
Username:"root"
Password:""
digikam.databaseserver: Internal Server data path:
"/Users/michmill/testpics/.mysql.digikam/db_data"
digikam.databaseserver: The mysql configuration was already up-to-date:
"/Users/michmill/Library/Application Support/digikam/digikam/mysql.conf"
digikam.databaseserver: Database initializer:
"/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/bin/mariadb-install-db"
QList("--defaults-file=/Applications/digiKam.org/digikam.app/Contents/Resources/digikam/database/mysql-global.conf",
"--basedir=/Applications/digiKam.org/digikam.app/Contents//lib/mariadb/",
"--datadir=/Users/michmill/testpics/.m
[digikam] [Bug 491042] MariaDB (MySQL) embedded files missing in fresh install
https://bugs.kde.org/show_bug.cgi?id=491042 --- Comment #20 from Michael Miller --- I'm still getting errors when I launch digiKam with a fresh install. https://bugs.kde.org/attachment.cgi?id=173842 Steps to reproduce: 1. Install latest digiKam-8.5.0-20240918T163828-Qt6-MacOS-arm64 2. delete ~/Library/Preferences/digikamrc 3. delete MySQL DB files (.mysql.digikam) 4. Launch digiKam from the Finder 5. During install, select MySQL Internal as the DB type No files or subdirectories in .mysql.digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491042] MariaDB (MySQL) embedded files missing in fresh install
https://bugs.kde.org/show_bug.cgi?id=491042 --- Comment #18 from Michael Miller --- Created attachment 173842 --> https://bugs.kde.org/attachment.cgi?id=173842&action=edit Latest errors -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467505] When launching the latest version of digiKam, the old internal MySql database cannot be started.
https://bugs.kde.org/show_bug.cgi?id=467505 Michael Miller changed: What|Removed |Added CC||michael_mil...@msn.com --- Comment #9 from Michael Miller --- Sorry, but the latest 8.5.0-arm package still doesn't work for me. My environment is a Mac arm64 VM. I removed previous SQLlite DBs and MariaDM files and dirs. I removed ~/Library/Preferences/digikamrc. This screenshot is the inital run of digiKam. https://bugs.kde.org/attachment.cgi?id=173822 If you try to run mariadbd from the command line using the parameters shown in the error message, you'll see what I mean in https://bugs.kde.org/show_bug.cgi?id=491042 about MariaDB files missing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491042] MariaDB (MySQL) embedded files missing in fresh install
https://bugs.kde.org/show_bug.cgi?id=491042 --- Comment #15 from Michael Miller --- Created attachment 173822 --> https://bugs.kde.org/attachment.cgi?id=173822&action=edit more error info -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491042] MariaDB (MySQL) embedded files missing in fresh install
https://bugs.kde.org/show_bug.cgi?id=491042 --- Comment #14 from Michael Miller --- Created attachment 173821 --> https://bugs.kde.org/attachment.cgi?id=173821&action=edit digiKam initial run -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491042] MariaDB (MySQL) embedded files missing in fresh install
https://bugs.kde.org/show_bug.cgi?id=491042 --- Comment #9 from Michael Miller --- Hi Gilles and Maik, New Homebrew MariaDB bundling is waiting for MR approval. There's more cleanup that could be done to reduce the final package size, but this works well. The MariaDB install is also portable so it can be run from anywhere as long as it keeps it relative location in the DK bundle. There are 4 changes to Macports needed to make this work, if you want to use it. 1. https://invent.kde.org/graphics/digikam/-/blob/9b08d1df1f6917a0493d63c0e2a87476b6a6ab16/project/bundles/homebrew/04mm-build-installer.sh#L154 2. https://invent.kde.org/graphics/digikam/-/blob/9b08d1df1f6917a0493d63c0e2a87476b6a6ab16/project/bundles/homebrew/04mm-build-installer.sh#L457 3. https://invent.kde.org/graphics/digikam/-/blob/9b08d1df1f6917a0493d63c0e2a87476b6a6ab16/project/bundles/homebrew/04mm-build-installer.sh#L723 4. https://invent.kde.org/graphics/digikam/-/blob/9b08d1df1f6917a0493d63c0e2a87476b6a6ab16/core/app/utils/digikam_globals_bundles.cpp#L176 Please note, the relative path in the bundle at runtime for MariaDB is derived from https://invent.kde.org/graphics/digikam/-/blob/9b08d1df1f6917a0493d63c0e2a87476b6a6ab16/core/app/utils/digikam_globals_bundles.cpp#L194 which is #ifdef to Homebrew. I don't see any harm in making this change for all MacOS builds, and not just Homebrew since both statements will evaluate to the same value once DK is installed. I'm using my custom tool to rebase the rpaths in the binaries, but I think adding @executable_path/../../.. rpaths should be enough, and it's already being done in the Macports 04 script, so you may be able to remove my rebasing loop. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491042] MariaDB (MySQL) embedded files missing in fresh install
https://bugs.kde.org/show_bug.cgi?id=491042 --- Comment #8 from Michael Miller --- Maik and Giles, >Another question is whether the MariaDB directory is complete (including data >folders). This is what I saw with 8.4.0. Several files were missing to initialize MariaDB, including setup scripts. The DK SQL plugin found all the right binaries and libraries, but was unable to initialize the DB. In my Homebrew bundle, I rsync the entire mariadb subtree with symlinks and then prune. This seems to work for initializing DK with a new DB, but I get an error message when I use the database migration tool. I'll merge my changes into master later tonight. My MariaDB bundling code will be in ./project/bundles/homebrew/04mm-build-installer.sh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491042] MariaDB (MySQL) embedded files missing in fresh install
https://bugs.kde.org/show_bug.cgi?id=491042 --- Comment #3 from Michael Miller --- Have you tried to do a SQLite to MariaDB database migration with 8.5.0 Arm64? I haven't tried with Macports yet, but with Homebrew I can't do a migration. I can use MariaDB when I initially configure a new install, and I can migrate FROM MariaDB to SQLite. I cannot, however, migrate from SQLite to MariaDB. It says it's not active. I' wondering if it's a Homebrew issue or something in code since MariaDB works fine for new installs. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491040] Unable to use Darktable for demosaicing on MacOS ARM
https://bugs.kde.org/show_bug.cgi?id=491040 --- Comment #10 from Michael Miller --- I marked the issue as resolved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491040] Unable to use Darktable for demosaicing on MacOS ARM
https://bugs.kde.org/show_bug.cgi?id=491040 Michael Miller changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491040] Unable to use Darktable for demosaicing on MacOS ARM
https://bugs.kde.org/show_bug.cgi?id=491040 --- Comment #9 from Michael Miller --- Thanks. I've been using it in my Homebrew build for a while now. It works well. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 335027] Touchpad on LENOVO X240
https://bugs.kde.org/show_bug.cgi?id=335027 --- Comment #27 from Michael --- (In reply to Nate Graham from comment #26) > Plasma 6 is shipped on Manjaro now; were you able to test it? Thank you @ Nate. Unfortunately this topic is still on my to-do list. I'm working hard every day but there are other issues in paid contract projects but also with our PCs, where we run MANJARO / KDE6 and are juggling around with the black screens after suspend, ref. https://bugs.kde.org/show_bug.cgi?id=483163#c46 or https://discuss.kde.org/t/plasma-6-lock-screen-renders-black-troubleshooting-help/1. Please rest assured that I will rebuild the X240 with MANJARO / KDE6 as soon as my projects allow. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491857] Unable to build on MacOS arm64 with Macports.
https://bugs.kde.org/show_bug.cgi?id=491857 --- Comment #32 from Michael Miller --- Hi Maik and Gilles, It looks like changing to KF 6.5.0 breaks some ext_breeze patches. Also, I tried using 8.5.0 and I still get the same cfrelease error in solid. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491857] Unable to build on MacOS arm64 with Macports.
https://bugs.kde.org/show_bug.cgi?id=491857 --- Comment #31 from Michael Miller --- Hi Gilles, Thanks for the info about QtCurves. I now have the UI looking the way it should. https://imgur.com/a/ego6gvf digiKam Homebrew issues: * Mac menu bar doesn't work * MariaDB - this is just moving/linking the files to the right place * Spell check - no spell-checkers are available -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491857] Unable to build on MacOS arm64 with Macports.
https://bugs.kde.org/show_bug.cgi?id=491857 --- Comment #29 from Michael Miller --- I have these in Homebrew. Are these all files what we need for QtCurve? >/opt/homebrew/share/QtCurve >/opt/homebrew/share/QtCurve/Breeze.qtcurve -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491857] Unable to build on MacOS arm64 with Macports.
https://bugs.kde.org/show_bug.cgi?id=491857 --- Comment #26 from Michael Miller --- That looks EXACTLY like mine. Same issues with the UI. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491857] Unable to build on MacOS arm64 with Macports.
https://bugs.kde.org/show_bug.cgi?id=491857 --- Comment #24 from Michael Miller --- I think got the same thing a few weeks ago. If you're getting the same thing I did, it's bug possibly in solid where it's doing a cfrelease on a null pointer. I have a patch in my repo that solves it. I'm checking in a new round of commits to my master that will include the fix. The patch is wrapped so it only applies to Homebrew, but if works for you we can change it to all Mac builds. https://invent.kde.org/michmill/digi-kam-mac-os-arm-64-michmill/-/blob/8f259403e34ce9217cf31e4b068f689cf9a99209/project/bundles/3rdparty/ext_kf6/solid-iokit-cfrelease.patch Once the merge from my branch into my master is complete, I'll do a MR from my private fork to digikam master. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #53 from Michael Miller --- Hi Gilles, I submitted the first MR. It's for calling fixbundledatapath.sh as part of patching ext_kf6. Please take a look and accept when you can, it should help you with Macports when you get to this point. I appears other contributors are submitting commits after I submitted my MR, so while the MR was all green when I submitted it, it's now red because it's at least 1 commit behind. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 492222] "The file or folder does not exist" error message appears when program is launched.
https://bugs.kde.org/show_bug.cgi?id=49 --- Comment #4 from Michael O'Sullivan --- Hi, The bug is still there. Kind regards Michael O’Sullivan MSc MBA 🇺🇦 Tel: +44 (0) 1622 736 241 Mob: +44 (0) 74 11 45 22 50 e-mail: michaelanthonyosulli...@gmail.com e-mail: m...@sullivan-net.com e-mail: michaelosulli...@protonmail.com e-mail: michaelosulli...@dunelm.org.uk Skype: mikeosullivan On 10 Sep 2024, 04:47 +0100, Bug Janitor Service , wrote: > https://bugs.kde.org/show_bug.cgi?id=49 > > --- Comment #3 from Bug Janitor Service --- > 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 > days. > Please provide the requested information, then set the bug status to REPORTED. > If there is no change for at least 30 days, it will be automatically closed as > RESOLVED WORKSFORME. > > For more information about our bug triaging procedures, please read > 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 reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #52 from Michael Miller --- Hi Gilles, >Do not try to build an universal version, this will bloat the bundles for >nothing as a x86_64 version already exists. No, my plan is to do at least 3 different builds Mac ARM64, Mac x86-64, Linux x86-64 (AppImage) and minimally test each one to make sure I didn't break anything. My build machines: * Mac ARM64 - Sonoma (M1) * Mac x86-64 Sonoma (Core I9) (I don't have an older Mac with an old version of the OS) * Linux x86-64 - Kubuntu 24.02 (VM on Core I9 Mac) Since almost all my changes are to the 01-04 build Bah files, CMake and patch files I think this should be sufficient to ensure I didn't break anything. I don't think I had to change any source files other than core/app/main/main.cpp. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #50 from Michael Miller --- Hi Gilles, Your suggestions sound good. I’ll wait until later to work on the spell checker and the icons. Since I have a working build, I’ll start doing pull requests of my changes small pieces at a time to get them into master. I’ll start with ext_kf6 tomorrow. Let me know how quickly you want the changes. I don’t want to overload the team with a bunch of merge requests at once, nor is it a good idea to submit one massive change. Do the tests work on Mac? I have working Mac ARM64, Mac x86-64, and Kubuntu x86-64 dev environments, so I’d like to test my changes as many ways as possible before I do the PR. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #46 from Michael Miller --- Hi Gilles, I saw your comment over on bug https://bugs.kde.org/show_bug.cgi?id=491857. I wanted to let you know about a week ago I spent about 1.5 days on the Orbit2 bug and could not figure it out, so I went back to using Homebrew. My thought is I'm probably 90% there using Homebrew, and I can't even get through script 01-build-macports. Plus, Homebrew is so much faster to set up. As for the issues I'm working on, thank you for the info about fixbudnledatapath.sh. Once I updated the ext_kf6 CMakeFile.txt to call the patch, all the kxmlgui5 files are loading from the bundle. Thank you again. I'm in progress of fixing sonnet/hunspell dictionary issues ([kf.sonnet.core] No language dictionaries for the language: en_US). Homebrew doesn't provide dictionaries with Sonnet or Hunspell, so I'm downloading them separately. At the moment I'm using https://github.com/LibreOffice/dictionaries. Is there a list of languages I should install? I could use some help with loading icons. DXmlGuiWindow::setupIconThere finds both Breeze and Breeze-dark icon .rcc files, it loads the .rcc files, but the icons aren't displayed in the UI. Breeze and Breeze-Dark are not options in Settings->Miscellaneous->Appearance tab. Are other files needed more than the .rcc files? Could this be an issue with Qt6/KF6? Cheers, Mike -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492422] Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
https://bugs.kde.org/show_bug.cgi?id=492422 --- Comment #16 from Michael Catanzaro --- Are we waiting for code review now? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #44 from Michael Miller --- I created a new branch from digikam master to update the ext_kf6 CMakeFile.txt so it includes fixbundledatapath.sh, but I'm unable to push my new branch because I'm not a project member. Any chance you can add me? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #43 from Michael Miller --- I meant to say to the PATCH_COMMAND, not CONFIGURE_COMMAND. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #42 from Michael Miller --- Hi Gilles, >Install the current digiKam Qt5 X86 PKG and look like the rc files are >installed here in the bundle : >/Applications/digiKam.org/digikam.app/Contents/Resources/kxmlgui5/digikam Yes, I have the files in the same place in my bundle, but digiKam isn't looking for them there. I used Inspector to look at all the file fstats and file opens. DK isn't trying to look for the .rc files in ./Resources/xmlgui5/digikam. >Don't forget one important point : the data install path for Qt is patched >while compiling KDE framework, digiKam core, and plugins. It's a long long >long story about a Qt5 bug under MacOS. For Qt6, i don't know if the problem >have been fixed. There is a script to patch source codes before compiling : YES! This is it. fixbundledatapath.sh is being copied and added to the CONFIGURE_COMMAND in the ext_kf5/CMakeLists.txt, but it's NOT in ext_kf6/CMakeLists.txt. >In the x86 bundle, ExifTool is installed here : >/Applications/digiKam.org/digikam.app/Contents/bin ExifTool is in the same place in my bundle. Again, DK isn't looking there. I have the bin directory defined in my qt.com as Binaries=bin. Using Inspector, I can see the DK is just using the PATH, and not looking in the Qt defined bin directory. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 492876] Bookmark search not working with Plasma Search plugin
https://bugs.kde.org/show_bug.cgi?id=492876 Michael changed: What|Removed |Added Summary|Bookmark search not working |Bookmark search not working |with Krunner plugin |with Plasma Search plugin -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 492876] New: Bookmark search not working with Krunner plugin
https://bugs.kde.org/show_bug.cgi?id=492876 Bug ID: 492876 Summary: Bookmark search not working with Krunner plugin Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: sbnav...@proton.me Target Milestone: --- Created attachment 173475 --> https://bugs.kde.org/attachment.cgi?id=173475&action=edit Screenshot SUMMARY Plasma Search options on the Browser Integration add-on currently provides check-boxes for finding currently opened browser tabs and searching through browser history, but searching through bookmarks is missing. Hence, even though the Plasma Search plugin "Bookmarks - Find and open bookmarks" is enabled and starred as favorite, searching through bookmarks doesn't work on Plasma Search unlike tabs or history. STEPS TO REPRODUCE 1. Install Plasma Browser Integration add-on on Firefox/Chromium 2. Enable the Bookmarks plugin for Plasma Search 3. Mark some website as a bookmark in the web browser where the add-on is installed. It won't be displayed in Plasma search results. EXPECTED RESULT With the Bookmarks plugin enabled on Plasma Search, web browser bookmarks should appear when Plasma browser integration add-on is installed. SOFTWARE/OS VERSIONS Operating System: Fedora Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-0.rc6.49.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LG Electronics Product Name: 15Z90Q-G.AA52P System Version: 0.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #37 from Michael Miller --- Final update for today. App package and package installed DK starts. DK is finding most of the libraries. Running the app from the installer works. ImageMagick works, as do most of the tools. It's almost usable as an installed app. Current issues: * Still can't figure out how to load the kxmlgui5/digikam/*.rc files from within the app bundle. Any help would be greatly appreciated. * Even when placing the kxmlgui5/digikam/*.rc files in ~/Library/kxmlgui5/digikam, the UI is still not correct. Icons are missing and the UI proportions are off. Again, any help would be appreciated. * Can't start exiftool. I can run it from the command line. DK can find it but not start it. * No available spell-check back-ends. It appears sonnet can't find the language files. * Need to update MariaDB bundling steps. I feel like the remaining issues are just simple pathing problems. Hopefully you can find some time to look, Gilles. Thank you for all your time. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 488624] kdiff3 unusable due to crashing
https://bugs.kde.org/show_bug.cgi?id=488624 --- Comment #7 from michael --- Have a patch attempt in master.. That may help with the this. If so it can be back ported to stable. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #34 from Michael Miller --- Hi Gilles, I got most of the Qt paths working in the past hour. It's now picking up the values in the ./Resources/qt.conf file, so that's fixed. I'm working on QtWebEngine and ImageMagick paths now. The latest commit to the fox_bundle_01 branch has my changes. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 488624] kdiff3 unusable due to crashing
https://bugs.kde.org/show_bug.cgi?id=488624 michael changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #5 from michael --- Going the address this directly sorry for the delay unfortunately I find myself as the only one doing work with this code. My attention has been else where lately. In particular dealing with the odd error on startup that I managed to reproduce. So far this hasn't happened for me but looks like an issue with Diff3Line::getString itself. Look at it now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #32 from Michael Miller --- Hi Gilles, I've been continuing to work on a Homebrew based arm64 build of digiKam. I'm still struggling with setting the runtime paths to libraries, plugins, translations, and other correctly. I've looked at all the makefiles and the scripts, but I just can't figure out which flags are used at compile time, and which flags are embedded in the code to be used at runtime. The only solution I've found so far is by using several environment variables to redirect Qt and other modules at runtime. If you have time, can you take a look at my private repo to see what I'm doing wrong? Use the "fix_bundle_01" branch, and look at README-MM in ./project/bundles/homebrew for additional details. https://invent.kde.org/michmill/digi-kam-mac-os-arm-64-michmill.git -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 335027] Touchpad on LENOVO X240
https://bugs.kde.org/show_bug.cgi?id=335027 --- Comment #25 from Michael --- PleasE ref here https://bugs.kde.org/show_bug.cgi?id=335027#c5. I'll follow up asap -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 492566] New: Can't remove breakpoints
https://bugs.kde.org/show_bug.cgi?id=492566 Bug ID: 492566 Summary: Can't remove breakpoints Classification: Applications Product: kate Version: 24.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: michaelalexsan...@protonmail.com Target Milestone: --- SUMMARY When attempting to remove a breakpoint, it will blink for an instant, but still remain there. STEPS TO REPRODUCE 1. Start the debugger. 2. Insert a breakpoint. 3. Attempt to remove it. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482887] plasmashell crashes in KAStatsFavoritesModel::Private::Private
https://bugs.kde.org/show_bug.cgi?id=482887 --- Comment #36 from Michael Hamilton --- (In reply to Harald Sitter from comment #34) > Looks useful enough. It's a different trace though. Best file a new bug > report. Thanks. https://bugs.kde.org/show_bug.cgi?id=492560 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492560] New: Crash in kastatsfavoritesmodel.cpp at login
https://bugs.kde.org/show_bug.cgi?id=492560 Bug ID: 492560 Summary: Crash in kastatsfavoritesmodel.cpp at login Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: mich...@actrix.gen.nz Target Milestone: 1.0 SUMMARY Occasional failure on login STEPS TO REPRODUCE 1. Login. 2. See if the session fails to start. 3. If login succeeds, return to step 1. One thing that might be different from most logins, my login runs various processes that raise several desktop notifications and updates some of them too. OBSERVED RESULT Login occasionally fails to completely start the desktop, or errors and them recovers. EXPECTED RESULT Login always works SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240829 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 Manufacturer: ASUS ADDITIONAL INFORMATION This stack trace is missing some line numbers for some Tumbleweed packages (not sure why), but line numbers are present for many such as kastatsfavoritesmodel.cpp. #0 0x7fe243a94c5c in __pthread_kill_implementation () at /lib64/libc.so.6 #1 0x7fe243a411c6 in raise () at /lib64/libc.so.6 #2 0x7fe246f36c54 in KCrash::defaultCrashHandler(int) () at /lib64/libKF6Crash.so.6 #3 0x7fe243a41290 in () at /lib64/libc.so.6 #4 __gnu_cxx::__atomic_add (__val=1, __mem=0x454545454545454d) at /usr/include/c++/13/ext/atomicity.h:71 #5 __gnu_cxx::__atomic_add_dispatch (__val=1, __mem=0x454545454545454d) at /usr/include/c++/13/ext/atomicity.h:111 #6 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_add_ref_copy (this=0x4545454545454545) at /usr/include/c++/13/bits/shared_ptr_base.h:152 #7 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator= (__r=, this=0x5597f058cd40) at /usr/include/c++/13/bits/shared_ptr_base.h:1088 #8 std::__shared_ptr::operator= (this=0x5597f058cd38) at /usr/include/c++/13/bits/shared_ptr_base.h:1523 #9 std::shared_ptr::operator= (this=0x5597f058cd38) at /usr/include/c++/13/bits/shared_ptr.h:414 #10 KAStatsFavoritesModel::Private::addResult (this=this@entry=0x5597eff2b000, _resource=..., index=21, index@entry=-1, notifyModel=notifyModel@entry=false, mimeType=...) at /usr/src/debug/plasma-workspace-6.1.4/applets/kicker/plugin/kastatsfavoritesmodel.cpp:353 #11 0x7fe1ea9ba3b0 in KAStatsFavoritesModel::Private::Private (this=0x5597eff2b000, parent=, clientId=, this=, parent=, clientId=) at /usr/src/debug/plasma-workspace-6.1.4/applets/kicker/plugin/kastatsfavoritesmodel.cpp:237 #12 0x7fe1ea9bb455 in KAStatsFavoritesModel::initForClient (this=0x5597f0458f40, clientId=...) at /usr/src/debug/plasma-workspace-6.1.4/applets/kicker/plugin/kastatsfavoritesmodel.cpp:550 #13 0x7fe1ea99f0f0 in KAStatsFavoritesModel::qt_metacall (this=0x5597f0458f40, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0x7fffd9a79f28) at /usr/src/debug/plasma-workspace-6.1.4/build/applets/kicker/kickerplugin_autogen/7RBZBFH7CH/moc_kastatsfavoritesmodel.cpp:325 #14 0x7fe24571da93 in ??? () at /lib64/libQt6Qml.so.6 #15 0x7fe2456084fb in ??? () at /lib64/libQt6Qml.so.6 #16 0x7fe24560b271 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /lib64/libQt6Qml.so.6 #17 0x7fe24565291f in ??? () at /lib64/libQt6Qml.so.6 #18 0x7fe24565860a in ??? () at /lib64/libQt6Qml.so.6 #19 0x7fe2455c33ae in ??? () at /lib64/libQt6Qml.so.6 #20 0x7fe2455c8d6d in QV4::Function::call(QObject*, void**, QMetaType const*, int, QV4::ExecutionContext*) () at /lib64/libQt6Qml.so.6 #21 0x7fe2456ebbf5 in QQmlJavaScriptExpression::evaluate(void**, QMetaType const*, int) () at /lib64/libQt6Qml.so.6 #22 0x7fe24569b02b in QQmlBoundSignalExpression::evaluate(void**) () at /lib64/libQt6Qml.so.6 #23 0x7fe24569f05b in ??? () at /lib64/libQt6Qml.so.6 #24 0x7fe245709b28 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /lib64/libQt6Qml.so.6 #25 0x7fe2443e79d8 in ??? () at /lib64/libQt6Core.so.6 #26 0x7fe245713f26 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /lib64/libQt6Qml.so.6 #27 0x7fe2456ae5c9 in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () at /lib64/libQt6Qml.so.6 #28 0x7fe2456ae8cc in QQmlComponentPrivate::completeCreate() () at /lib64/libQt6Qml.so.6 #29 0x7fe24705b713 in PlasmaQuick::SharedQmlEngine::completeInitialization(QHash const&) () at /lib64/libPlasmaQuick.so.6 #30 0x7fe24703ffd4 in PlasmaQuick::AppletQuickItem::i
[plasmashell] [Bug 482887] plasmashell crashes in KAStatsFavoritesModel::Private::Private
https://bugs.kde.org/show_bug.cgi?id=482887 --- Comment #35 from Michael Hamilton --- (In reply to Justin Zobel from comment #33) > Interesting as it should download all required debug symbols, might be worth > bringing up with Fedora if they are missing symbols in their debuginfod > server. It was Tumbleweed. I suspect the missing symbols may be because TW has rolled on and debuginfod can no longer find matching downloads for the obsolete packages (total guess however). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 492553] New: Text highlight on Places panel displays correctly only after second click
https://bugs.kde.org/show_bug.cgi?id=492553 Bug ID: 492553 Summary: Text highlight on Places panel displays correctly only after second click Classification: Applications Product: dolphin Version: 24.05.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: michaelgauci...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 173240 --> https://bugs.kde.org/attachment.cgi?id=173240&action=edit Top: Expected result, bottom: Observed result When an entry in the Places panel is selected, the selection text changes colour briefly then reverts back to the non-highlighted colour, only to be corrected permanently when the entry is clicked again. STEPS TO REPRODUCE 1. Choose a theme other than Breeze 2. Open Dolphin 3. Select one of the entries from the Places panel Tested on: KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482887] plasmashell crashes in KAStatsFavoritesModel::Private::Private
https://bugs.kde.org/show_bug.cgi?id=482887 --- Comment #32 from Michael Hamilton --- (In reply to Justin Zobel from comment #31) > Michael thanks for the added report, it is however missing debug symbols, > please see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > for info on how to ensure the symbols are installed, thanks. I got this dump as result of following the coredumpctl instructions and answering use debuginfod in the affirmative. I noted the line numbers such as at /usr/src/debug/plasma-workspace/plasma-workspace-6.0.1/applets/kicker/plugin/kastatsfavoritesmodel.cpp:189 and figured this was what you needed. I am on OpenSUSE TW, so I inferred from the instructions, that using debuginfod was the right way to go. Happy to try something else. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 492528] Icon in system area of the control bar should open akregator window
https://bugs.kde.org/show_bug.cgi?id=492528 Michael changed: What|Removed |Added CC||mailinglis...@kmhessler.de -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 492528] New: Icon in system area of the control bar should open akregator window
https://bugs.kde.org/show_bug.cgi?id=492528 Bug ID: 492528 Summary: Icon in system area of the control bar should open akregator window Classification: Applications Product: akregator Version: 6.1.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mailinglis...@kmhessler.de Target Milestone: --- Since Plasma 6.0 clicking the icon in system area of the control bar is no longer opening the akregator window. This has been the fact with all plasma 5.x versions. I found a workaround: * Settings > Akregator-Settings > Show icon in system area of the control bar * unselect / save and * select / save brings back the desired behavior. But after a reboot, the misbehavior is back and the procedure needs to be reproduced. I'd appreciate if the old function could be restored. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.6.46-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #30 from Michael Miller ---
Hi Gilles,
> It's normal as you use directly the pre-compiled version of the packages. But
> in fact we cannot do it as the Qt6Mysql plugin is not provided in precompiled
> version (at least i seen in my previous tests 2 months ago). So whole Qt6
> must be recompiled and it's take age.
Doesn't including qt-mysql or my-mariadb fix this? Look at the module log, I
can see the qt-mariadb plugin being loaded.
>Note the ${KDE_INSTALL_FULL_PLUGINDIR} variable taken from ECM.
> Note the ${QT_PLUGINS_DIR} variable taken from CMake.
I'm looking for a way for us to modify these paths at run-time. According to
the Qt documentation I should be able to do this for Qt with the qt.conf file.
Do you know if there is a similar file for KF?
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 482887] plasmashell crashes in KAStatsFavoritesModel::Private::Private
https://bugs.kde.org/show_bug.cgi?id=482887 --- Comment #30 from Michael Hamilton --- I'm on 6.1.4 using Nvidia and I'm still seeing something similar as recently as yesterday. Operating System: openSUSE Tumbleweed 20240829 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 Manufacturer: ASUS #0 0x7fe243a94c5c in __pthread_kill_implementation () at /lib64/libc.so.6 #1 0x7fe243a411c6 in raise () at /lib64/libc.so.6 #2 0x7fe246f36c54 in KCrash::defaultCrashHandler(int) () at /lib64/libKF6Crash.so.6 #3 0x7fe243a41290 in () at /lib64/libc.so.6 #4 __gnu_cxx::__atomic_add (__val=1, __mem=0x454545454545454d) at /usr/include/c++/13/ext/atomicity.h:71 #5 __gnu_cxx::__atomic_add_dispatch (__val=1, __mem=0x454545454545454d) at /usr/include/c++/13/ext/atomicity.h:111 #6 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_add_ref_copy (this=0x4545454545454545) at /usr/include/c++/13/bits/shared_ptr_base.h:152 #7 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator= (__r=, this=0x5597f058cd40) at /usr/include/c++/13/bits/shared_ptr_base.h:1088 #8 std::__shared_ptr::operator= (this=0x5597f058cd38) at /usr/include/c++/13/bits/shared_ptr_base.h:1523 #9 std::shared_ptr::operator= (this=0x5597f058cd38) at /usr/include/c++/13/bits/shared_ptr.h:414 #10 KAStatsFavoritesModel::Private::addResult (this=this@entry=0x5597eff2b000, _resource=..., index=21, index@entry=-1, notifyModel=notifyModel@entry=false, mimeType=...) at /usr/src/debug/plasma-workspace-6.1.4/applets/kicker/plugin/kastatsfavoritesmodel.cpp:353 #11 0x7fe1ea9ba3b0 in KAStatsFavoritesModel::Private::Private (this=0x5597eff2b000, parent=, clientId=, this=, parent=, clientId=) at /usr/src/debug/plasma-workspace-6.1.4/applets/kicker/plugin/kastatsfavoritesmodel.cpp:237 #12 0x7fe1ea9bb455 in KAStatsFavoritesModel::initForClient (this=0x5597f0458f40, clientId=...) at /usr/src/debug/plasma-workspace-6.1.4/applets/kicker/plugin/kastatsfavoritesmodel.cpp:550 #13 0x7fe1ea99f0f0 in KAStatsFavoritesModel::qt_metacall (this=0x5597f0458f40, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0x7fffd9a79f28) at /usr/src/debug/plasma-workspace-6.1.4/build/applets/kicker/kickerplugin_autogen/7RBZBFH7CH/moc_kastatsfavoritesmodel.cpp:325 #14 0x7fe24571da93 in ??? () at /lib64/libQt6Qml.so.6 #15 0x7fe2456084fb in ??? () at /lib64/libQt6Qml.so.6 #16 0x7fe24560b271 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /lib64/libQt6Qml.so.6 #17 0x7fe24565291f in ??? () at /lib64/libQt6Qml.so.6 #18 0x7fe24565860a in ??? () at /lib64/libQt6Qml.so.6 #19 0x7fe2455c33ae in ??? () at /lib64/libQt6Qml.so.6 #20 0x7fe2455c8d6d in QV4::Function::call(QObject*, void**, QMetaType const*, int, QV4::ExecutionContext*) () at /lib64/libQt6Qml.so.6 #21 0x7fe2456ebbf5 in QQmlJavaScriptExpression::evaluate(void**, QMetaType const*, int) () at /lib64/libQt6Qml.so.6 #22 0x7fe24569b02b in QQmlBoundSignalExpression::evaluate(void**) () at /lib64/libQt6Qml.so.6 #23 0x7fe24569f05b in ??? () at /lib64/libQt6Qml.so.6 #24 0x7fe245709b28 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /lib64/libQt6Qml.so.6 #25 0x7fe2443e79d8 in ??? () at /lib64/libQt6Core.so.6 #26 0x7fe245713f26 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /lib64/libQt6Qml.so.6 #27 0x7fe2456ae5c9 in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () at /lib64/libQt6Qml.so.6 #28 0x7fe2456ae8cc in QQmlComponentPrivate::completeCreate() () at /lib64/libQt6Qml.so.6 #29 0x7fe24705b713 in PlasmaQuick::SharedQmlEngine::completeInitialization(QHash const&) () at /lib64/libPlasmaQuick.so.6 #30 0x7fe24703ffd4 in PlasmaQuick::AppletQuickItem::itemForApplet(Plasma::Applet*) () at /lib64/libPlasmaQuick.so.6 #31 0x7fe24706c9e9 in ??? () at /lib64/libPlasmaQuick.so.6 #32 0x7fe245713a74 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /lib64/libQt6Qml.so.6 #33 0x7fe2456ae5c9 in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () at /lib64/libQt6Qml.so.6 #34 0x7fe2456ae8cc in QQmlComponentPrivate::completeCreate() () at /lib64/libQt6Qml.so.6 #35 0x7fe24705b713 in PlasmaQuick::SharedQmlEngine::completeInitialization(QHash const&) () at /lib64/libPlasmaQuick.so.6 #36 0x7fe24703ffd4 in PlasmaQuick::AppletQuickItem::itemForApplet(Plasma::Applet*) () at /lib64/libPlasmaQuick.so.6 #37 0x7fe24705489c in ??? () at /lib64/libPlasmaQuick.so.6 #38 0x5597d93762af in ShellCorona::createWaitingPanels (this=) at /usr/src/debug/plasma-workspace-6.1.4/shell/shellcorona.cpp:1544 #39
[systemsettings] [Bug 444569] Keyboard layout shortcuts activate wrong language [regression]
https://bugs.kde.org/show_bug.cgi?id=444569 --- Comment #14 from Michael Lashkevich --- It turned out that to get rid of crashes it is sufficient to delete the file ~/.config/kaccountsrc -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492422] Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
https://bugs.kde.org/show_bug.cgi?id=492422 --- Comment #14 from Michael Catanzaro --- Good news: with your latest patch, there are no more fd errors other than fd leaks. If I determine that any of these look like valgrind issues, then I'll report a follow-up bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492422] Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
https://bugs.kde.org/show_bug.cgi?id=492422 --- Comment #13 from Michael Catanzaro --- I am only just now realizing that both of the ioctls that I mentioned as follow-ups, SYNC_IOC_MERGE and DRM_IOCTL_PRIME_HANDLE_TO_FD, are also the ones that I mentioned in comment #1 and which you had already attempted to support. Well, this is why testing is important. :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492422] Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
https://bugs.kde.org/show_bug.cgi?id=492422 --- Comment #11 from Michael Catanzaro --- (In reply to Michael Catanzaro from comment #10) > I suspect we're just missing one last ioctl that creates fds. I will > investigate. I believe it's coming from DRM_IOCTL_PRIME_HANDLE_TO_FD. (It's coming from driver-specific code, unfortunately. I only investigated the amdgpu code.) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492422] Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
https://bugs.kde.org/show_bug.cgi?id=492422 --- Comment #10 from Michael Catanzaro --- (In reply to Mark Wielaard from comment #8) > Could you test this updated patch to see if it handles file descriptor > tracking for all three ioctls now? Yes. There is a massive improvement in the results I see. There are only a few fd reuse errors remaining, and they all look like this: ==14900== File descriptor 17: /memfd:mutter-shared (deleted) is already closed ==14900==at 0x60F9F9C: close (close.c:27) ==14900==by 0x433901CD: wsi_destroy_image (wsi_common.c:789) ==14900==by 0x4339B192: wsi_wl_swapchain_images_free (wsi_common_wayland.c:2238) ==14900==by 0x4339B1F5: wsi_wl_swapchain_destroy (wsi_common_wayland.c:2306) ==14900==by 0x50DF509: gdk_vulkan_context_dispose (gdkvulkancontext.c:370) ==14900==by 0x49E9E7A: g_object_unref (gobject.c:4415) ==14900==by 0x51A5F35: gsk_gpu_renderer_unrealize (gskgpurenderer.c:247) ==14900==by 0x51409FC: gsk_vulkan_renderer_unrealize (gskvulkanrenderer.c:142) ==14900==by 0x5102635: gsk_renderer_unrealize (gskrenderer.c:380) ==14900==by 0x4DD12A7: gtk_window_unrealize (gtkwindow.c:4407) ==14900==by 0x4B2AEB3: gtk_application_window_real_unrealize (gtkapplicationwindow.c:528) ==14900==by 0x49DEE79: g_cclosure_marshal_VOID__VOID (gmarshal.c:117) I suspect we're just missing one last ioctl that creates fds. I will investigate. And then there are several fd leaks reported. Some of them are surely real, but some look like we're perhaps missing a DRM ioctl that closes fds? Probably best for me to investigate and create a separate bug report if valgrind turns out to be to blame. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #28 from Michael Miller --- A forked the project into my own repo. I changed about 15 or 16 files, so I thought this might be easier for you to take a look. I'm still having path issues with Qt. Maybe you will have better luck. https://invent.kde.org/michmill/digi-kam-mac-os-arm-64-michmill -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492422] Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
https://bugs.kde.org/show_bug.cgi?id=492422 --- Comment #5 from Michael Catanzaro --- (In reply to Mark Wielaard from comment #3) > Could you test with this? It fixes the issue I reported. Thank you! But there is another one that looks almost identical: ==130394== File descriptor 28: file descriptor 28 is already closed ==130394==at 0x60F9F9C: close (close.c:27) ==130394==by 0x4339341C: wsi_create_sync_for_image_syncobj (wsi_common_drm.c:413) ==130394==by 0x43390E67: wsi_common_acquire_next_image2 (wsi_common.c:1205) ==130394==by 0x43390C92: wsi_AcquireNextImageKHR (wsi_common.c:1186) ==130394==by 0x50E0265: gdk_vulkan_context_begin_frame (gdkvulkancontext.c:652) ==130394==by 0x50B0A46: gdk_draw_context_begin_frame_full (gdkdrawcontext.c:399) ==130394==by 0x5193169: gsk_gpu_frame_default_begin (gskgpuframe.c:87) ==130394==by 0x51AEB4F: gsk_vulkan_frame_begin (gskvulkanframe.c:160) ==130394==by 0x51934C8: gsk_gpu_frame_begin (gskgpuframe.c:209) ==130394==by 0x51A6AC1: gsk_gpu_renderer_render (gskgpurenderer.c:446) ==130394==by 0x5102C24: gsk_renderer_render (gskrenderer.c:495) ==130394==by 0x4DC25C4: gtk_widget_render (gtkwidget.c:12012) The difference is the line number changed from wsi_common_drm.c:410 to wsi_common_drm.c:413. This time it's a different file descriptor coming from a different ioctl: SYNC_IOC_MERGE. (The line numbers are from mesa 24.1.6-1.fc40.) I found some documentation here though: https://github.com/torvalds/linux/blob/fb24560f31f9dff2c97707cfed6029bfebebaf1c/include/uapi/linux/sync_file.h#L19 and it looks like the second fd2 is opened. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492422] Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
https://bugs.kde.org/show_bug.cgi?id=492422 --- Comment #4 from Michael Catanzaro --- (In reply to Mark Wielaard from comment #2) > I'll take a look at those other ioctls. Is there a description of how the > DRM_IOCTLs handle fds in general? Are there any that close/destroy an fd? Or > are you always supposed to use the "normal" close syscall on them? I don't know, but I'll ask graphics developers to answer this. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492422] Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
https://bugs.kde.org/show_bug.cgi?id=492422 --- Comment #1 from Michael Catanzaro --- Unfortunately Benjamin thinks we'll need a lot more than one new ioctl for `valgrind --track-fds=yes` to be useful for GTK applications, including at least SYNC_IOC_MERGE and DRM_IOCTL_PRIME_HANDLE_TO_FD. I also forgot to include a link to my GTK issue report: https://gitlab.gnome.org/GNOME/gtk/-/issues/6969 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492422] New: Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
https://bugs.kde.org/show_bug.cgi?id=492422 Bug ID: 492422 Summary: Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD Classification: Developer tools Product: valgrind Version: 3.23.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: mcatanz...@gnome.org Target Milestone: --- SUMMARY It's hard to use valgrind to debug file descriptor errors in GTK applications because valgrind doesn't understand that DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD may allocate a file descriptor. STEPS TO REPRODUCE 1. GSK_RENDERER=vulkan valgrind --tool=none --track-fds=yes gnome-calculator OBSERVED RESULT valgrind will print some actual fd bugs in GTK, but it will be very hard to tell what is a real bug and what is not, because valgrind will also print a bunch of false positive complaints that look like this: ==34793== File descriptor 27: /dmabuf: is already closed ==34793==at 0x63C7F9C: close (close.c:27) ==34793==by 0x397D1542: wsi_create_sync_for_image_syncobj (wsi_common_drm.c:410) ==34793==by 0x397CEE67: wsi_common_acquire_next_image2 (wsi_common.c:1205) ==34793==by 0x397CEC92: wsi_AcquireNextImageKHR (wsi_common.c:1186) ==34793==by 0x4EEA265: gdk_vulkan_context_begin_frame (gdkvulkancontext.c:652) ==34793==by 0x4EBAA46: gdk_draw_context_begin_frame_full (gdkdrawcontext.c:399) ==34793==by 0x4F9D169: gsk_gpu_frame_default_begin (gskgpuframe.c:87) ==34793==by 0x4FB8B4F: gsk_vulkan_frame_begin (gskvulkanframe.c:160) ==34793==by 0x4F9D4C8: gsk_gpu_frame_begin (gskgpuframe.c:209) ==34793==by 0x4FB0AC1: gsk_gpu_renderer_render (gskgpurenderer.c:446) ==34793==by 0x4F0CC24: gsk_renderer_render (gskrenderer.c:495) ==34793==by 0x4BCC5C4: gtk_widget_render (gtkwidget.c:12012) It will also print the backtrace to where the fd was previously allocated and previously closed, but this is irrelevant. wsi_create_sync_for_image_syncobj() is getting the fds via the DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD ioctl before closing them, so they're coming straight from the kernel. valgrind just doesn't know about this. EXPECTED RESULT No bogus complaints SOFTWARE/OS VERSIONS Fedora 40: gtk4-4.14.4-2.fc40, valgrind-1:3.23.0-4.fc40 ADDITIONAL INFORMATION I've figured out that we need to add VKI_DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD and struct vki_drm_syncobj_handle in vki-linux-drm.h, and then add ML_(record_fd_open_nameless) somewhere in syswrap-linux.c. But that looks a little complicated. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #27 from Michael Miller --- Good to know about gmic. I'll post error logs of the gmic build tomorrow. The biggest problem I'm running into is Qt not finding the plugins. If I run digikam without relocating the libraries (still hard-coded to /opt/homebrew), everything runs fine. Once I rebase the library paths, it can't find the plugins anymore. I've tried using the qt.conf file to point to the plugins, and putting the environment variables in the LSEnvironment section of the Info.plist, but neither works. If I run digikam from the command line, and I have QT_PLUGIN_PATH and QT_QPA_PLATFORM_PLUGIN_PATH set in the environment it works fine as well. I am using a different program to relocate the binaries and run install_make_tool. I have a Python script I wrote a while ago to allow me to make a relocatable install of MariaDB. I modified RelocatableBinaries in common.sh to use my tool. It's a bit slower, but it is giving me the results I need. Can you think of any reason why it's not picking up the settings in qt.conf? Per the Qt documentation, I've put qt.conf in Contents/Resources. I've also tried the bundle root, and Contents/MacOS so it's beside the main binary. It's just not picking up the settings. I think my next step is to build Qt from source so I can debug into it to see why it's not using the settings in qt.conf. As for the dark-icons, the cmake file is completely different, so the patch doesn't work. I've looked at it, and I think I can figure it out with a little time. if I have time, I'll clone digikam into my own repo so you can see my changes. One final note, total build time is less than an hour in my UTM arm64 dev VM from 01-04 if Homebrew is installed in /opt/homebrew. So that's a nice bonus. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #25 from Michael Miller --- I have a (mostly) working build using Homebrew. I've just been struggling with creating a good bundle. The 2 items I had to comment out was the dark-icons and gmic. I'll revisit them once I figure out how to bundle. Specifically, it's Qt. I've tried multiple approaches to getting it to work, but still no luck. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491857] Unable to build on MaOS: ERROR: Unmodified ffmpeg >= 5.0 is not supported.
https://bugs.kde.org/show_bug.cgi?id=491857 --- Comment #7 from Michael Miller --- Alternatively, you could create patch files and keep Valadoc. See https://trac.macports.org/ticket/70547 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343690] Missing windows tabbing
https://bugs.kde.org/show_bug.cgi?id=343690 Michael D changed: What|Removed |Added CC|nortex...@gmail.com | -- 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 fully updated when changing global themes in Global Theme KCM (Quick Settings and Colors KCMs are unaffected)
https://bugs.kde.org/show_bug.cgi?id=421745 Michael Weghorn changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kde-gtk-config/commit/16 |ma/kde-gtk-config/-/commit/ |08cf03670c71d85f110a7d2dda1 |ffe400047ae4cd9836aff7f9a17 |c576e939032 |95115edb738d0 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #91 from Michael Weghorn --- Git commit ffe400047ae4cd9836aff7f9a1795115edb738d0 by Michael Weghorn. Committed on 24/08/2024 at 10:50. Pushed by ngraham into branch 'master'. kded: Handle global theme change A "Global Theme" can include almost all of the visual appearance settings, so call `GtkConfig::applyAllSettings` to make sure all of them are in sync after being notified about a change of the global theme. M +4-0kded/gtkconfig.cpp https://invent.kde.org/plasma/kde-gtk-config/-/commit/ffe400047ae4cd9836aff7f9a1795115edb738d0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 492222] "The file or folder does not exist" error message appears when program is launched.
https://bugs.kde.org/show_bug.cgi?id=49 --- Comment #2 from Michael O'Sullivan --- Hi, I’ve just downloaded the new version (24.08.0) and exactly the same thing is happening - I get an error message saying “The file or folder does not exist”. Kind regards Michael O'Sullivan Michael O’Sullivan MSc MBA 🇺🇦 Tel: +44 (0) 1622 736 241 Mob: +44 (0) 74 11 45 22 50 e-mail: michaelanthonyosulli...@gmail.com e-mail: m...@sullivan-net.com e-mail: michaelosulli...@protonmail.com e-mail: michaelosulli...@dunelm.org.uk Skype: mikeosullivan On 26 Aug 2024, 17:40 +0100, Jean-Baptiste Mardelle , wrote: > https://bugs.kde.org/show_bug.cgi?id=49 > > Jean-Baptiste Mardelle changed: > > What |Removed |Added > > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Jean-Baptiste Mardelle --- > Thanks for your report. Could you check if the same happens with the soon to > be > announced 24.08.0 version, downloadable from here. > https://cdn.kde.org/ci-builds/multimedia/kdenlive/release-24.08/ > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 492222] New: "The file or folder does not exist" error message appears when program is launched.
https://bugs.kde.org/show_bug.cgi?id=49 Bug ID: 49 Summary: "The file or folder does not exist" error message appears when program is launched. Classification: Applications Product: kdenlive Version: 24.05.2 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: michaelanthonyosulli...@gmail.com Target Milestone: --- Created attachment 172978 --> https://bugs.kde.org/attachment.cgi?id=172978&action=edit Screenshot of error message *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Launch kdenlive 24.05.2 on MacOS Monterey 12.7.6 2. Error message "The file or folder does not exist" appears before the application can be launched 3. Click OK to acknowledge error message and program launches normally. OBSERVED RESULT Error message "The file or folder does not exist" appears before the application can be launched EXPECTED RESULT No error message. SOFTWARE/OS VERSIONS Windows: macOS: Monterey 12.7.6 (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #24 from Michael Miller --- Hi Gilles, Here's a list of libs I've found so far. These are either missing or unable to be found by @rpath/[optional dir/]: 1. QtDBus.framework/Versions/A/QtDBus: Not found. Should be in ./opt/qt/lib/ 2. libopencv_ml.410.dylib: Incorrect @rpath/libopencv_core.410.dylib. Should be @rpath/opt/opencv/lib/libopencv_core.410.dylib 3. libgcc_s.1.1.dylib: Not found. Should be in ./opt/gcc/lib/gcc/current/ 4. libjxl_cms.0.10.dylib: Wrong location. Should be ./opt/jpeg-xl/lib 5. QtQuickWidgets.framework/Versions/A/QtQuickWidgets: At this point I went to bed. I also noticed we need a better app Info.plist. Additional items: 1. architecture in LSExecutableArchitectures 2. update the LSEnvironment with HOMEBREW_PREFIX, and updated PATH 3. LSMinimumSystemVersion should match config.sh->OSX_MIN_TARGET I have a static Info.plist I'm using for now. I'll add it to my list of "to do" for the arm64 build. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #22 from Michael Miller --- Thank you Gilles. I've stopped exploring Craft, and I'm continuing with Homebrew. Update: I've given up trying to pin to a specific package variant with Homebrew, and I'm now using the latest of each package. Three issues I've found so far. 1. Some Homebrew bottles have the dynamic library paths hard coded to /opt/homebrew instead of @rpath. If you try to use install_name_tool on them, the code signature becomes invalid. You need to run the codesign tool to update the signature, but since you didn't compile the binary yourself, codesign fails. One way to fix this is to just build all the packages yourself using "brew --build-from-source install X". This however takes a very long time. An alternate solution is to install Homebrew to a custom directory. By doing this, Homebrew will automatically build from source only the packages (bottles) that are hard-coded to /opt/homebrew, so it is faster. This also has the added benefit of not "polluting" an existing Homebrew installation. 2. Not all of the needed libraries are being packaged by 04-build-installer.sh. This is slow work going through and finding the libraries that are missing. 3. I think not all the updated binaries are being re-signed by codesign. Again, it's slow work going through them. -- 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 fully updated when changing global themes in Global Theme KCM (Quick Settings and Colors KCMs are unaffected)
https://bugs.kde.org/show_bug.cgi?id=421745 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 492019] Label names for Keyboard Shortcuts KCM: "KWin" and "plasmashell" names are more developer-friendly than user-friendly
https://bugs.kde.org/show_bug.cgi?id=492019 --- Comment #7 from Michael --- Thanks for the encouragement. Done. https://invent.kde.org/documentation/develop-kde-org/-/issues/175 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350446] Port MacOS PKG to Arm64 Apple Silicon.
https://bugs.kde.org/show_bug.cgi?id=350446 --- Comment #19 from Michael Miller --- I think the biggest blocker to using Craft package manager was I wasn't aware it existed. :) I'll take a look at it tonight. Thank you for the suggestion. Cheers, Mike -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 492019] Label names for Keyboard Shortcuts KCM: "KWin" and "plasmashell" names are more developer-friendly than user-friendly
https://bugs.kde.org/show_bug.cgi?id=492019 --- Comment #5 from Michael --- "Plasma Desktop" is fine, it's consistent and is promoted heavily. "KWin" is fine to be replaced with simply "Window manager" for end-user facing labels. If we were to prefix everything with "KDE" then we could easily go overboard because *everythin*g in System Settings is KDE technology. I would like to see the HIG talk about user-facing proper nouns. It goes over what our acronyms should be [https://develop.kde.org/hig/text_and_labels/#acronyms], but we don't have a common and congruent way of relating what "KWin" is. I'm thinking of opening a bug report for the HIG for user-facing KDE proper nouns so that we're all on the same page: Akonadi = ?? Baloo = ?? Powerdevil = KDE Power Management (maybe drop the KDE part?) KWin = ? Do we need this? -- You are receiving this mail because: You are watching all bug changes.
