[ksplash] [Bug 487038] Plasma broke login/splash themes
https://bugs.kde.org/show_bug.cgi?id=487038 --- Comment #5 from GregS --- Still got the problem, crickets from this site. The comment "Third-party splash screens may need adjustments to work with Plasma 6, this is expected and not a bug." is less thanhelpful, because NOWHERE can I find any advice on how to 'adjust' third party splash screens etc. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 487038] Plasma broke login/splash themes
https://bugs.kde.org/show_bug.cgi?id=487038 GregS changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 487038] Plasma broke login/splash themes
https://bugs.kde.org/show_bug.cgi?id=487038 --- Comment #4 from GregS --- I have confirmed QuickControls IS installed (somewhere on the system??); but Plasma obviousluy camnnot locate it. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 487038] Plasma broke login/splash themes
https://bugs.kde.org/show_bug.cgi?id=487038 --- Comment #2 from GregS --- Nicholas, The ONLY theme that works is the default (Breeze?). I have tried several of the downloadable styles (the previous ones such as Oxygen no longer appear to be supported?), none of which work and several encounter the error message quoted. I also cannot find any useful advice on QuickControls anywhere. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 487038] New: Plasma broke login/splash themes
https://bugs.kde.org/show_bug.cgi?id=487038 Bug ID: 487038 Summary: Plasma broke login/splash themes Classification: Plasma Product: ksplash Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: greg.shepp...@bigpond.com Target Milestone: --- SUMMARY Since upgrading to Fedora 40 KDE spin, both login and splash screen customisation from previous versions is now unworkable. I am also unable to access menu items in many applications (File menu works OK, takes a lot of fiddling to access any others with the mouse). Occasional flickering of windows also occurs. STEPS TO REPRODUCE 1. Start System Settings/Colours & Themes 2. Select downloaded custom theme in Global, Splash Screen or Login Screen (SDDM) 3. Reboot OBSERVED RESULT Only the default themes (Trees -> KDE splash) appears. Often an error message (Main.qml:23:1:module QtQuickControls ver 1.1 not installed) appears on the login screen - depending upon which login theme is selected. The ONLY apparent difference is the layout of the user selector, the background remains the 'tree' theme, apparently drawn by a 10-y-o! Completely unable to effect any change to splash. EXPECTED RESULT Display of the selected theme(s) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I have searched for a means to install QuickControls, the only sources are directed to programmers using qml and none are at all helpful (I cannot even find if I have a .qml file, much less add the link...) -- You are receiving this mail because: You are watching all bug changes.
[krecipes] [Bug 411157] New: Cannot store images
https://bugs.kde.org/show_bug.cgi?id=411157 Bug ID: 411157 Summary: Cannot store images Product: krecipes Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: greg.shepp...@bigpond.com Target Milestone: --- SUMMARY I can select and insert an image into the active recipe, save it, but on reopening the default penguin (Tux) image reappears. STEPS TO REPRODUCE 1. Insert graphic from file 2. Save recipe 3. Reopen recipe OBSERVED RESULT Default image is restored. EXPECTED RESULT inserted image should appear. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 30 KDE Spin (updated to Aug 19) (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.
[frameworks-baloo] [Bug 389848] baloo crash on login
https://bugs.kde.org/show_bug.cgi?id=389848 --- Comment #37 from GregS --- (In reply to Don Curtis from comment #33) > (My DrKonqi crash report: Bug 396277) > In my case, this behaviour appeared after the following upgrade: > Qt Version: 5.6.2 upgraded to 5.9.4; > Frameworks Version: 5.32.0 upgraded to 5.45.0; > (Distribution upgrade from openSUSE Leap 42.3 to Leap 15.0). > > I noticed that, with the updated system version and, a "fresh" test user, > Baloo didn't crash. > Also not after I enabled the PIM plugin in the Digital Clock -- akonadi > started. > Also not with a user which doesn't use the Kontact PIM -- only digiKam and > Oracle's VirtualBox -- akonadi is not started for this user. > > For the case of the user which was suffering the Baloo crashes I did the > following from a VT with the Display Manager stopped: > 1. Removed the following files in '~/.config/': > baloorc > baloofilerc > baloofileinformationrc > 2. Removed the entire contents of '~/.local/share/baloo/': > index > index-lock > KDE PIM Kontact directories > 3. Restarted the Display Manager and logged in the user with the "Baloo > crashing issue". > > Baloo doesn't crash any more. > > My guess at the root cause: > * Outdated Baloo configuration files and an outdated index database cause >an exception with the current Baloo implementation. Tried this (Fedora 27 - has been a recurring issue since Fedora 22). So far, no more crashes. I guess the suggestion above WRT outdated files may be on the money. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 393896] New: baloo continually crashes on boot
https://bugs.kde.org/show_bug.cgi?id=393896 Bug ID: 393896 Summary: baloo continually crashes on boot Product: frameworks-baloo Version: 5.44.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: greg.shepp...@bigpond.com Target Milestone: --- Application: baloo_file_extractor (5.44.0) Qt Version: 5.9.4 Frameworks Version: 5.44.0 Operating System: Linux 4.16.5-200.fc27.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Booting into user with Fedora 27; this occurs with all users on the system and has been happening (and previously reported) since Fedora 22. It has contiuned to occur with each upgrade; clearly it has NOT been fixed. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6b5c135500 (LWP 1995))] Thread 3 (Thread 0x7f6b3dd0b700 (LWP 2111)): #0 0x7f6b586ccc6b in poll () from /lib64/libc.so.6 #1 0x7f6b5399ce99 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f6b5399cfac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f6b59522c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f6b594d096a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f6b593218ca in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f6b5acf1449 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f6b59325de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f6b575d050b in start_thread () from /lib64/libpthread.so.0 #9 0x7f6b586d716f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f6b4757a700 (LWP 2025)): #0 0x7f6b586ccc6b in poll () from /lib64/libc.so.6 #1 0x7f6b53325fe7 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f6b53327dda in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f6b4a118bf9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f6b59325de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f6b575d050b in start_thread () from /lib64/libpthread.so.0 #6 0x7f6b586d716f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f6b5c135500 (LWP 1995)): [KCrash Handler] #6 0x7f6b586819a1 in __memmove_sse2_unaligned_erms () from /lib64/libc.so.6 #7 0x7f6b59328200 in QByteArray::QByteArray(char const*, int) () from /lib64/libQt5Core.so.5 #8 0x7f6b5b390511 in Baloo::IdFilenameDB::get(unsigned long long) () from /lib64/libKF5BalooEngine.so.5 #9 0x7f6b5b389f0f in Baloo::DocumentUrlDB::get(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #10 0x7f6b5b39a834 in Baloo::Transaction::documentUrl(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #11 0x564acb66f878 in Baloo::App::processNextFile() () #12 0x7f6b59506934 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f6b594fb21b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f6b5a13e92c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f6b5a146174 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f6b594d1be7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f6b59521f5b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #18 0x7f6b59522829 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #19 0x7f6b5399cb77 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7f6b5399cf20 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #21 0x7f6b5399cfac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7f6b59522c2f in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f6b594d096a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f6b594d9094 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x564acb66ea2f in main () The reporter indicates this bug may be a duplicate of or related to bug 360946. Possible duplicates by query: bug 373006, bug 360648, bug 354705. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 393756] New: Baloo file extractor fail on logon
https://bugs.kde.org/show_bug.cgi?id=393756 Bug ID: 393756 Summary: Baloo file extractor fail on logon Product: frameworks-baloo Version: 5.44.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: greg.shepp...@bigpond.com Target Milestone: --- Application: baloo_file_extractor (5.44.0) Qt Version: 5.9.4 Frameworks Version: 5.44.0 Operating System: Linux 4.16.5-200.fc27.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Every logon, the same message appears that baloo has crashed. this has been occuring since Fedora 22 (previously reported), now occurring with F27. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5b5037b500 (LWP 1759))] Thread 3 (Thread 0x7f5b31f55700 (LWP 1846)): #0 0x7f5b4c912c6b in poll () from /lib64/libc.so.6 #1 0x7f5b47be2e99 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f5b47be2fac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f5b4d768c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f5b4d71696a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f5b4d5678ca in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f5b4ef37449 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f5b4d56bde2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f5b4b81650b in start_thread () from /lib64/libpthread.so.0 #9 0x7f5b4c91d16f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5b3b7c0700 (LWP 1760)): #0 0x7f5b4c912c6b in poll () from /lib64/libc.so.6 #1 0x7f5b4756bfe7 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f5b4756ddda in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f5b3e35ebf9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f5b4d56bde2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f5b4b81650b in start_thread () from /lib64/libpthread.so.0 #6 0x7f5b4c91d16f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5b5037b500 (LWP 1759)): [KCrash Handler] #6 0x7f5b4c8c79a1 in __memmove_sse2_unaligned_erms () from /lib64/libc.so.6 #7 0x7f5b4d56e200 in QByteArray::QByteArray(char const*, int) () from /lib64/libQt5Core.so.5 #8 0x7f5b4f5d6511 in Baloo::IdFilenameDB::get(unsigned long long) () from /lib64/libKF5BalooEngine.so.5 #9 0x7f5b4f5cff0f in Baloo::DocumentUrlDB::get(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #10 0x7f5b4f5e0834 in Baloo::Transaction::documentUrl(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #11 0x55f4536d7878 in Baloo::App::processNextFile() () #12 0x7f5b4d74c934 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f5b4d74121b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f5b4e38492c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f5b4e38c174 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f5b4d717be7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f5b4d767f5b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #18 0x7f5b4d768829 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #19 0x7f5b47be2b77 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7f5b47be2f20 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #21 0x7f5b47be2fac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7f5b4d768c2f in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f5b4d71696a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f5b4d71f094 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x55f4536d6a2f in main () Possible duplicates by query: bug 373006. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
