SUMMARY If clock on the icon to start Clock it briefly goes to startup and then it closes and do not see. I do note that the earlier versions used to do this at times too. About 2 versions of clock before latest one worked and started up fine. But the previous version and current version if try to start it.... yeah... goes to start and disappears. STEPS TO REPRODUCE 1. Click on clock icon to start it 2. 3. OBSERVED RESULT Window opens as it tries to start up, then window disappears. it is a black window only no gui of a clock. EXPECTED RESULT Want app to run as when it is working it is a great app. Just it does not appear reliable with mint cinnamon sadly. SOFTWARE/OS VERSIONS Latest version of KClock Linux Mint Cinnamon 22.1 Cinnamon Version 6.4.8 Linux Kernel 6.8.0-55-generic Processor AMD Ryzen 3 3200G with Radeon Vega Graphics x 4 Memory 15.5GB Graphics Card AMD Navi 23 Radeon RX6600 Display Server X11 ADDITIONAL INFORMATION With the latest updates of Kclock this appears to be a permanent issue cannot get it to startup properly at all... it tries then fails.
Try to start it from terminal and see if you get any helpful error messages! Maybe post them here too. Maybe it's some Cinnamon or Linux Mint problem / conflict since Linux Mint developers don't care at all about Qt / KDE software.
Yes, please get the console logs from starting `kclock` in the terminal. For the time being, you can also try and see if the kclock flatpak works.
(In reply to John from comment #1) > Try to start it from terminal and see if you get any helpful error messages! > Maybe post them here too. > > Maybe it's some Cinnamon or Linux Mint problem / conflict since Linux Mint > developers don't care at all about Qt / KDE software. Hello John and Devin Lin, thank you both for replying so fast. I am sorry for my delay in replying to you both. I have done as you both suggested and tried starting it through terminal. This is the messages that then came up in Terminal. ---------------------------------- ~$ kclock Gtk-Message: 13:23:00.545: Failed to load module "xapp-gtk3-module" /usr/share/libdrm/amdgpu.ids: No such file or directory Qt: Session management error: Could not open network socket Qt: Session management error: Could not open network socket /usr/share/libdrm/amdgpu.ids: No such file or directory kf.kirigami.layouts: FormData.buddyFor must be a direct child of the attachee. Attachee: QQuickColumnLayout(0x570bb43f2fc0, parent=0x570bb43bf100, geometry=0,0 0x0), buddyFor: SpinBox_QMLTYPE_186(0x570bb43f8840, parent=0x570bb43f35d0, geometry=0,0 0x0) kf.dbusaddons: Failed to register name 'org.kde.kclockd' with DBUS - does this process have permission to use the name, and do no other processes own it already? ^C ------------------------------------------------------------------------ Thank you both for your time and effort in trying to assist me in this issue it is greatly appreciated :) .
I have just done a Kernel Update in Linux Mint Which has taken it to Linux Kernel 6.8.0-56-generic This appears to have fixed it..... as after doing the terminal copy and paste and reading that information it appeared to me at least that it considered it was not installed. So I went and reinstalled it fully. It still would not load properly again the starting to then collapsing of the window. But, since updating the kernel to the one above. KClock appears to be running fine and working the best it has ever worked to be honest. Much faster than it ever used too. So my personal belief it was something within that kernel which was somehow thinking it wasnt there or failing in some task. As said done the kernel update this morning and since then it has been the best it has ever been. Fast and accurate. Thank you. This is a great clock with great features. Long may it continue to be. :)
🐛🧹 ⚠️ 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!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.