[krusader] [Bug 445044] New: LOTS of metadata access warnings on start-up, a few other ones, e.g. "null action"
https://bugs.kde.org/show_bug.cgi?id=445044 Bug ID: 445044 Summary: LOTS of metadata access warnings on start-up, a few other ones, e.g. "null action" Product: krusader Version: 2.7.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: ptrenho...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY: Starting krusader from a command line displays a LOT of warning messages. STEPS TO REPRODUCE 1. Open terminal window 2. enter "krusader" OBSERVED RESULT: Several screens full of warning messages (See below) EXPECTED RESULT: Krusader screen display SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION: NOTE: I flagged this as "minor" because it seems to have no impact on krusader's functionality. $ krusader kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/sftp.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/sftp.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/filter.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/filter.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/filenamesearch.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/filenamesearch.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/about.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/about.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/applications.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/applications.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/bookmarks.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/bookmarks.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/desktop.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/desktop.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/mtp.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/mtp.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/network.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/network.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/man.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/man.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/videodvd.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/videodvd.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/activities.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/activities.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/settings.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/settings.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/recentdocuments.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/recentdocuments.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/nfs.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/nfs.so'" kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/fish.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/fish.so'" QCoreApplication::applicationDirPath: Please instantiate the QApplication object first 14:05:29.977-warning default unknown@0 # QWidget::insertAction: Attempt to insert null action 14:05:30.039-warning default unknown@0 # QWidget::insertAction: Attempt to insert null action 14:05:30.097-warning kf.i18n unknown@0 # Trying to convert empty KLocalizedString to QString. 14:05:30.312-warning kf.coreaddons unknown@0 # no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/sftp.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/sftp.so'" 14:05:30.313-warning kf.coreaddons unknown@0 # no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/filter.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/filter.so'" 14:05:30.313-warning kf.coreaddons unknown@0 # no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so'" 14:05:30.314-warning kf.coreaddons unknown@0 # no metadata found i
[frameworks-kio] [Bug 445044] LOTS of metadata access warnings on start-up, a few other ones, e.g. "null action"
https://bugs.kde.org/show_bug.cgi?id=445044 Peter C. Trenholme changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #5 from Peter C. Trenholme --- Sorry: I missed the info request. Yes, it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 433274] New: When synchronizing from a CIFS connection to a Win 10 file system to a Fedora 33 sys, several directories pop-up as "unreadable."
https://bugs.kde.org/show_bug.cgi?id=433274 Bug ID: 433274 Summary: When synchronizing from a CIFS connection to a Win 10 file system to a Fedora 33 sys, several directories pop-up as "unreadable." Product: krusader Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: synchronize Assignee: krusader-bugs-n...@kde.org Reporter: ptrenho...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY They are somewhat problematic: They all end with a . or, in some cases, a blank. The "problem" is that the pop-up in the synchronizer doesn't provide a "skip all" option, so I have to sit here waiting to the next pop-up to tell it AGAIN to skip it. STEPS TO REPRODUCE See summary OBSERVED RESULT See summary EXPECTED RESULT See summery SOFTWARE/OS VERSIONS Linux: Fedora 33 Windows: 10 Pro 21H1 macOS: N/A Linux/KDE Plasma: 5 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION This is, I believe, a feature request not a bug, although both the NT file system and the Linux file systems don't seem to have much problem with those directories. (Might be the CIFS component, but that's a different issue.) I just wanted to suggest that a "Do this for all such issues" button would be a welcome addition to issue-specific pop-up messages. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 433274] When synchronizing from a CIFS connection from a Win 10 file system to a Fedora 33 one, several directories pop-up as "unreadable."
https://bugs.kde.org/show_bug.cgi?id=433274 Peter C. Trenholme changed: What|Removed |Added Summary|When synchronizing from a |When synchronizing from a |CIFS connection to a Win 10 |CIFS connection from a Win |file system to a Fedora 33 |10 file system to a Fedora |sys, several directories|33 one, several directories |pop-up as "unreadable." |pop-up as "unreadable." -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439790] New: Exported kate theme reports (incorrect) error message wmen the theme is imported.
https://bugs.kde.org/show_bug.cgi?id=439790 Bug ID: 439790 Summary: Exported kate theme reports (incorrect) error message wmen the theme is imported. Product: kate Version: 21.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: ptrenho...@gmail.com Target Milestone: --- SUMMARY Exported kate theme reports (incorrect) error message wmen the theme is imported. STEPS TO REPRODUCE 1. Start kate 2. Export the theme 3. Exit kate 4. Open a terminal window and start kate 5. Import the save theme file 6. See the (spurious) error messages about missing "=" symbols. Note that JSON files do not, generally, use "=" delimiters. They most often use ":" delimiters, which are (correctly) used in the generated ".theme" file. OBSERVED RESULT See above EXPECTED RESULT No spurious error messages. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE: Ferora 34 (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION >From my terminal output . . . qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 13495, resource id: 14790069, major code: 40 (TranslateCoords), minor code: 0 kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 1: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 2: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 3: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 4: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 5: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 6: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 7: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 8: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 9: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /root/MyKateTheme.theme, line 10: " Invalid entry (missing '=') Oh, you may note that I was running as "root." I have another problem, unrelated to this minor one, and not (I think) a KDE one: PAM has decided that my user names (except "root") are all invalid because (as far as I can tell) I named my user accounts with the user's first names, with correct -- mixed case -- spelling. The accounts are still there -- I can su into them from root-- but not log in from console. (Sorry - just venting.) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 477297] New: Incomplete translation to Wayland (?) - minor errors showing when started from konsole
https://bugs.kde.org/show_bug.cgi?id=477297 Bug ID: 477297 Summary: Incomplete translation to Wayland (?) - minor errors showing when started from konsole Classification: Applications Product: krusader Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: ptrenho...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY See observed result STEPS TO REPRODUCE 1. Start krusader from a konsole window 2. Use krusader from the resulting window to compare two files and update one line Note: That is a specific description of the observed result, ut almost any use will produce some error or warning message(s). OBSERVED RESULT [Peter ~]$ krusader kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "No jobs" msgid_plural: "" msgctxt: "" 10:48:40.951-warning kf.i18n unknown@0 # Trying to convert empty KLocalizedString to QString. 10:52:17.845-warning default unknown@0 # Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls") 10:52:36.612-warning qt.qpa.wayland unknown@0 # setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56278d2e1500) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56278d61d510) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents EXPECTED RESULT No error or warning messages SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 39 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION I labeled this as "Minor" because it didn't seem to impact the actual system usage/output/etc, but it does seem (to me) that testing should be done with /dev/err captured and reviewed. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 431323] New: Was the swap file filled?
https://bugs.kde.org/show_bug.cgi?id=431323 Bug ID: 431323 Summary: Was the swap file filled? Product: krusader Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: ptrenho...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.7.2 "Peace of Mind") Qt Version: 5.15.2 Frameworks Version: 5.75.0 Operating System: Linux 5.9.16-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 33 (Thirty Three) -- Information about the crash: - What I was doing when the application crashed: I was attempting to update my /Backups partition from my /Common partition; $ df -h /Common /Backups Filesystem Size Used Avail Use% Mounted on /dev/sda7 723G 120G 604G 17% /Common /dev/sda6 783G 523G 221G 71% /Backups After running for about a week (On a fairly slow "AcePC," with an "atom" processor.) I turned on the screen, and found the crash report. I suspect that the data base being created (in core?) ran out of space. (I do have a fairly large swap file: $ swapon --show NAME TYPE SIZE USED PRIO /dev/sda4 partition 23.6G 107.1M -2 /dev/zram0 partition 1.8G 1.8G 100 but it looks like (see above) the in-ram swap was filled, and the backup swap file was filling.) (Which may explain why the process ran for almost a week before crashing.) When I looked at the "syncronize" display during the week, I noticed that the system was spending a lot of time getting details about directories that exist on only one side. At lot of tme and effort could be avoided if that condition was noted for latter processing when the user was selecting which items to move. (I.e., if a whole directory tree is to be moved, why bother to look at the elements of that tree? Only if the user wants to look at the tree elements (by clicking on the tree root) would there be any need to list the tree contents.) -- Backtrace: Application: Krusader - ROOT PRIVILEGES (krusader), signal: Segmentation fault [KCrash Handler] #4 0x7fea221045c5 in QTreeModel::hasChildren(QModelIndex const&) const () from /lib64/libQt5Widgets.so.5 #5 0x7fea220f8773 in QTreeViewPrivate::hasVisibleChildren(QModelIndex const&) const () from /lib64/libQt5Widgets.so.5 #6 0x7fea220fa007 in QTreeViewPrivate::layout(int, bool, bool) () from /lib64/libQt5Widgets.so.5 #7 0x7fea220fa0dd in QTreeViewPrivate::layout(int, bool, bool) () from /lib64/libQt5Widgets.so.5 #8 0x7fea220fa0dd in QTreeViewPrivate::layout(int, bool, bool) () from /lib64/libQt5Widgets.so.5 #9 0x7fea220fa0dd in QTreeViewPrivate::layout(int, bool, bool) () from /lib64/libQt5Widgets.so.5 #10 0x7fea220fa0dd in QTreeViewPrivate::layout(int, bool, bool) () from /lib64/libQt5Widgets.so.5 #11 0x7fea220fa0dd in QTreeViewPrivate::layout(int, bool, bool) () from /lib64/libQt5Widgets.so.5 #12 0x7fea221001b1 in QTreeView::doItemsLayout() () from /lib64/libQt5Widgets.so.5 #13 0x7fea220fd3f5 in QTreeView::scrollTo(QModelIndex const&, QAbstractItemView::ScrollHint) () from /lib64/libQt5Widgets.so.5 #14 0x55d45b692e49 in SynchronizerGUI::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.0] () #15 0x7fea213a33c0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #16 0x55d45b68cae8 in Synchronizer::addItem(SynchronizerFileItem*, QString const&, QString const&, QString const&, QString const&, bool, bool, unsigned long long, unsigned long long, long, long, QString const&, QString const&, QString const&, QString const&, QString const&, QString const&, unsigned int, unsigned int, QString const&, QString const&, TaskType, bool, bool) () #17 0x55d45b68cdb0 in Synchronizer::addLeftOnlyItem(SynchronizerFileItem*, QString const&, QString const&, unsigned long long, long, QString const&, QString const&, QString const&, unsigned int, QString const&, bool, bool) () #18 0x55d45b685820 in SynchronizerGUI::compare() () #19 0x7fea213a33c0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #20 0x7fea21f17316 in QAbstractButton::clicked(bool) () from /lib64/libQt5Widgets.so.5 #21 0x7fea21f17cde in QAbstractButtonPrivate::emitClicked() () from /lib64/libQt5Widgets.so.5 #22 0x7fea21f19673 in QAbstractButtonPrivate::click() () from /lib64/libQt5Widgets.so.5 #23 0x7fea21f19855 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #24 0x7fea21e68b1e in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #25 0x7fea21e27ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #26 0x7fea21e2eeeb in QApplication::notify(QObject*, QEvent*) () from /lib64/lib
[plasmashell] [Bug 391642] Plasma shell crashes when changing to desktop view
https://bugs.kde.org/show_bug.cgi?id=391642 --- Comment #19 from Peter C. Trenholme --- No recent problem. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449671] New: The "Turn off touchpad while a mouse is connected." option is missing from the Setup/Input Devices/Touclpad form.
https://bugs.kde.org/show_bug.cgi?id=449671 Bug ID: 449671 Summary: The "Turn off touchpad while a mouse is connected." option is missing from the Setup/Input Devices/Touclpad form. Product: systemsettings Version: 5.24.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwintouchscreen Assignee: kwin-bugs-n...@kde.org Reporter: ptrenho...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The option to automatically disable the touchpad when a mouse is connected is missing in the settings STEPS TO REPRODUCE 1. Go to settings - input devices - touchpad 2. Look for the option OBSERVED RESULT Option not found EXPECTED RESULT Find the option SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Without the option my wife, who has Parkinson's Disease and the typical dyskinesia, cannot type without moving the cursor all over the screen. She also has the bradykinesia symptom, which make the "Turn off while typing." option ineffective. (She tends to rest her arm on the laptop's touchpad -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 323801] Unexpected Policy Kit crash
https://bugs.kde.org/show_bug.cgi?id=323801 Peter C. Trenholme changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #3 from Peter C. Trenholme --- Sorry, I don't have that drive anymore, and it was reported more as a FYI than a bug needing fixing. It's five years old now, and not worth keeping. Changed status to Resolved, Unmaintained. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 417253] New: Possible exFAT format in USB device recognition problem.
https://bugs.kde.org/show_bug.cgi?id=417253 Bug ID: 417253 Summary: Possible exFAT format in USB device recognition problem. Product: partitionmanager Version: 4.0.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: ptrenho...@gmail.com Target Milestone: --- Application: partitionmanager (4.0.0) Qt Version: 5.13.2 Frameworks Version: 5.66.0 Operating System: Linux 5.4.15-200.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: Looking at various device and partition descriptions. I'm running a Fedora 31 system using the Plasma desktop on an Intel Atom processor in a Microsoft Surface 3 box, booting from a 2Tb USB-3 drive. I have 2 1Tb micro SD drives, and two Logitech USB device (mouse and keyboard) in an Atolla USB 4-port, powered, USB extender. (The 1Tb Micro SD cards were only ~$20 each on Amazon!) The drives are all recognized as mmcblk devices, and work well. One of the Micro SD cards is formatted as exFAT, the other as NTFS. I suspect, but cannot prove, that the crash occured when I pointed the partition manager at the exFAT (single partition) device. The partition manager screen "blinked out" (e.g., crashed) as soon as I selected one of the two MicroSD chips. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Floating point exception Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb4300e9800 (LWP 29774))] Thread 6 (Thread 0x7fb407fff700 (LWP 29783)): #0 0x7fb4337f844c in read () at /lib64/libc.so.6 #1 0x7fb43239853f in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7fb432350357 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fb4323507b2 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fb432350b93 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #5 0x7fb418d86a4a in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0 #6 0x7fb432379fc2 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #7 0x7fb432c054e2 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb4338076d3 in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb418bed700 (LWP 29782)): #0 0x7fb4337fca6f in poll () at /lib64/libc.so.6 #1 0x7fb43235080e in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fb432350943 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fb432350991 in glib_worker_main () at /lib64/libglib-2.0.so.0 #4 0x7fb432379fc2 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #5 0x7fb432c054e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7fb4338076d3 in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb419762700 (LWP 29780)): #0 0x7fb4337f844c in read () at /lib64/libc.so.6 #1 0x7fb43239853f in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7fb432350357 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fb4323507b2 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fb432350943 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fb433d90843 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fb433d3a1db in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fb435507665 in DBusThread::run() () at /lib64/libkpmcore.so.8 #8 0x7fb433b8bd96 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fb432c054e2 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb4338076d3 in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb419fa4700 (LWP 29779)): #0 0x7fb432c0bd45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb41ae3819b in util_queue_thread_func () at /usr/lib64/dri/i965_dri.so #2 0x7fb41ae37dab in impl_thrd_routine () at /usr/lib64/dri/i965_dri.so #3 0x7fb432c054e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb4338076d3 in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fb421429700 (LWP 29777)): #0 0x7fb4337fca6f in poll () at /lib64/libc.so.6 #1 0x7fb43235080e in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fb432350943 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fb433d90843 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fb433d3a1db in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fb433b8ac45 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fb4334dcf6a in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7fb433b8bd96 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fb432c054e2 in st
[krusader] [Bug 418116] New: Started from command line. MANY warning/error messages! Sloppy coding?
https://bugs.kde.org/show_bug.cgi?id=418116 Bug ID: 418116 Summary: Started from command line. MANY warning/error messages! Sloppy coding? Product: krusader Version: 2.7.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: synchronize Assignee: krusader-bugs-n...@kde.org Reporter: ptrenho...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY I've been running krusader to synchronize two (fairly large) directories for more that two weeks now. So I looked at the terminal instance from which I started it, and discovered several thousand warning messages. None of these massages are, of course, visible if the app is started from a menu, but their presence suggests the the coders did not think that wasting resources producing discarded messages was worth the time fixing the sloppy code. In any case, I fear that what should have been less that half a day of reading a reconciling the directories has now gone on for three weeks, and counting. See bellow for the top of the message list. The QPainter warnings - as far as I could see - are repeated from there to the end of the current terminal output. STEPS TO REPRODUCE: See above OBSERVED RESULT: See below EXPECTED RESULT: No errors or warnings SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Current Fedora 31. (Or current as-of 3 weeks ago) (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION 1) Sample terminal output: (See comment below) $ krusader QCoreApplication::applicationDirPath: Please instantiate the QApplication object first 10:56:17.264-warning default unknown@0 # QWidget::insertAction: Attempt to insert null action 10:56:17.272-warning default unknown@0 # QWidget::insertAction: Attempt to insert null action 10:56:17.308-warning default unknown@0 # Trying to convert empty KLocalizedString to QString. 20:19:24.139-warning qt.qpa.xcb unknown@0 # QXcbConnection: XCB error: 3 (BadWindow), sequence: 59389, resource id: 25947199, major code: 40 (TranslateCoords), minor code: 0 13:15:01.431-warning default unknown@0 # UdevQt: unhandled device action "bind" 13:15:16.116-warning default unknown@0 # UdevQt: unhandled device action "bind" 14:05:19.207-warning default unknown@0 # UdevQt: unhandled device action "unbind" 14:05:47.947-warning default unknown@0 # UdevQt: unhandled device action "unbind" Added comment ### Notice the large time gap here. I suspect that this is where the processing slowed down to about 10 seconds/file 21:53:01.574-warning default unknown@0 # QPainter::begin: Paint device returned engine == 0, type: 2 21:53:01.574-warning default unknown@0 # QPainter::translate: Painter not active 21:53:01.591-warning default unknown@0 # QPainter::save: Painter not active 21:53:01.591-warning default unknown@0 # QPainter::restore: Unbalanced save/restore 21:53:01.591-warning default unknown@0 # QPainter::brushOrigin: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::save: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::save: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::setRenderHint: Painter must be active to set rendering hints 21:53:01.606-warning default unknown@0 # QPainter::translate: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::setBrush: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::setPen: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::restore: Unbalanced save/restore 21:53:01.606-warning default unknown@0 # QPainter::setRenderHint: Painter must be active to set rendering hints 21:53:01.606-warning default unknown@0 # QPainter::translate: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::setPen: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::restore: Unbalanced save/restore 21:53:01.606-warning default unknown@0 # QPainter::save: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::setRenderHint: Painter must be active to set rendering hints 21:53:01.606-warning default unknown@0 # QPainter::translate: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::setPen: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::restore: Unbalanced save/restore 21:53:01.606-warning default unknown@0 # QPainter::save: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::setRenderHint: Painter must be active to set rendering hints 21:53:01.606-warning default unknown@0 # QPainter::translate: Painter not active 21:53:01.606-warning default unknown@0 # QPainter::setPen: Painter not active 21:53:01.607-warning default unknown@0 # QPainter::restore: Unbalanced save/restore 21:53
[plasmashell] [Bug 373742] The shell will not start until I switch to a tty window (ctrl-alt-f2) and then switch back
https://bugs.kde.org/show_bug.cgi?id=373742 --- Comment #4 from Peter C. Trenholme --- Sorry, I overlooked this request. I haven't used that system for several weeks, but, IIRC, the problem was every time I loaded from a terminal. (I did try it several times before I reported it.) I was (again, IIRC) not starting after a VT switch, but from a konsol terminal running in a KDM window. On my system, the plasma shell has not started since Fedora 23. KDM runs, and (since I put Konsole in the .conf/autostart/) I've been mostly running KDE apps from a terminal. (By the way, I think that problem was because I deleted some configuration file that the installer ASSUMES to exist. I did several re-installs and updates since F-23 with no change to that behavior.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393928] New: plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=393928
Bug ID: 393928
Summary: plasmashell crash
Product: plasmashell
Version: 5.12.4
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: ptrenho...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.12.4)
Qt Version: 5.10.1
Frameworks Version: 5.44.0
Operating System: Linux 4.16.6-302.fc28.x86_64 x86_64
Distribution: "Fedora release 28 (Twenty Eight)"
-- Information about the crash:
- What I was doing when the application crashed: I was trying to change my
wallpaper settings.
- Unusual behavior I noticed: For the last year or so my wallpaper setting have
not been saved.
- When I started plasmashell in a browser window (The KDE display manager works
fine, and I can start terminal windows, etc., with entries in
.config/autostart.)
# I used this command to start the plasmashell:
$ plasmashell -n
--desktopfile=/usr/share/applications/org.kde.plasmashell.desktop &
I noticed a lot of messages on the screen. (My added comment lines start with
#.)
# It seemed to start out fine . . .
$ org.kde.plasmaquick: Applet "Digital Clock" loaded after 168 msec
org.kde.plasmaquick: Delayed preload of "Audio Volume" after 2.896 seconds
file:///usr/share/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:384:17:
QML ColumnLayout: Binding loop detected for property "maximumWidth"
org.kde.plasmaquick: Applet "Audio Volume" loaded after 49 msec
org.kde.plasmaquick: Delayed preload of "Printers" after 1.306 seconds
file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PopupDialog.qml:105:13:
QML PropertyChanges: Cannot assign to non-existent property "tooltipText"
org.kde.plasmaquick: Applet "Printers" loaded after 17 msec
file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PopupDialog.qml:110:13:
QML PropertyChanges: Cannot assign to non-existent property "tooltipText"
org.kde.plasmaquick: Delayed preload of "Device Notifier" after 2.719 seconds
org.kde.plasmaquick: Applet "Device Notifier" loaded after 10 msec
org.kde.plasmaquick: Delayed preload of "Printers" after 1.526 seconds
file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PopupDialog.qml:105:13:
QML PropertyChanges: Cannot assign to non-existent property "tooltipText"
org.kde.plasmaquick: Applet "Printers" loaded after 17 msec
org.kde.plasmaquick: Delayed preload of "Software Updates" after 1.937 seconds
org.kde.plasmaquick: Applet "Software Updates" loaded after 50 msec
file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PopupDialog.qml:110:13:
QML PropertyChanges: Cannot assign to non-existent property "tooltipText"
org.kde.plasmaquick: Delayed preload of "Software Updates" after 1.803 seconds
org.kde.plasmaquick: Applet "Software Updates" loaded after 31 msec
org.kde.plasmaquick: Delayed preload of "Notifications" after 1.941 seconds
org.kde.plasmaquick: Applet "Notifications" loaded after 1 msec
org.kde.plasma.pulseaudio: No object for name
"alsa_output.pci-_00_14.2.analog-stereo.monitor"
org.kde.plasmaquick: Delayed preload of "Audio Volume" after 2.282 seconds
org.kde.plasmaquick: Applet "Audio Volume" loaded after 234 msec
org.kde.plasmaquick: Delayed preload of "Notifications" after 2.959 seconds
org.kde.plasmaquick: Applet "Notifications" loaded after 0 msec
org.kde.plasmaquick: Delayed preload of "Clipboard" after 4.4 seconds
org.kde.plasmaquick: Applet "Clipboard" loaded after 392 msec
org.kde.plasmaquick: Delayed preload of "Battery and Brightness" after 2.879
seconds
org.kde.plasmaquick: Applet "Battery and Brightness" loaded after 37 msec
org.kde.plasmaquick: Delayed preload of "Device Notifier" after 4.346 seconds
org.kde.plasmaquick: Applet "Device Notifier" loaded after 11 msec
org.kde.plasmaquick: Delayed preload of "Networks" after 3.145 seconds
org.kde.plasmaquick: Applet "Networks" loaded after 185 msec
org.kde.plasmaquick: Delayed preload of "Battery and Brightness" after 3.286
seconds
org.kde.plasmaquick: Applet "Battery and Brightness" loaded after 30 msec
org.kde.plasmaquick: Delayed preload of "Clipboard" after 4.478 seconds
org.kde.plasmaquick: Applet "Clipboard" loaded after 368 msec
org.kde.plasmaquick: Delayed preload of "Networks" after 3.997 seconds
org.kde.plasmaquick: Applet "Networks" loaded after 99 msec
# This is a strange message. Both mime directories exist and are readable.
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/home/Peter/.local/share/mime", "/usr/share/mime")
No file found for ".xml" , even though update-mime-info said it would exist.
Either it
[kdelibs] [Bug 202992] Kded4 crashed after package upgrade
https://bugs.kde.org/show_bug.cgi?id=202992 Peter C. Trenholme changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |UNMAINTAINED --- Comment #3 from Peter C. Trenholme --- This bug (from 2009 for Fedora 11) is long dead, and the (automated?) "needs info" reminder should not, in my opinion, be jogging me for a open needsinfo for this. In any case, the bug (as far as I can remember) never happened again after I installed the debug packages, so there was never any occasion to reply, and I presume that I assumed that the bug was automatically closed when F11 was retired. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348544] Right Clicking on Dolphin in Classic Application Menu causes a crash plasma
https://bugs.kde.org/show_bug.cgi?id=348544 --- Comment #15 from Peter C. Trenholme --- Um, thi bug was reported several years ago, and, in this thread, it is marked as NEEDSINFO, but nowhere in the body does the NEEDSINFO flag appear, and the request for information is missing. Also, unless I reported one of those "Marked as duplicate." reports, I have no idea why I received a message asking me for the needed information. In any case, I would not be able to provide information about a bug that occured on a Fedora version (11) that was obsoleted five years ago. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373742] New: The shell will not start until I switch to a tty window (ctrl-alt-f2) and then switch back
https://bugs.kde.org/show_bug.cgi?id=373742 Bug ID: 373742 Summary: The shell will not start until I switch to a tty window (ctrl-alt-f2) and then switch back Product: plasmashell Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ptrenho...@gmail.com Target Milestone: 1.0 Created attachment 102828 --> https://bugs.kde.org/attachment.cgi?id=102828&action=edit Errors and warning generated by plasmashell when started from a konsle window This happens on Fedora 24, 25 and Rawhide. Also, a few days ago the shell locked up, and, after I killed it, I restarted it from the konsole window (which was not closed when the shell was killed). There were a large number of errors and warnings displayed when the shell started. Many of these seem (to me) to be sloppy coding. Others (e.g., the lack of metadata every time my background image changes) seem to be caused by a failure to generate expected information when there's no reason to expect a casual user to know that your system expects - in this case - a directory containing several hundred images to have a "metadata" file.) Anyhow, for you perusal, I attach a copy of (some of) the messages generated when I restarted the shell. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 362597] QWidget::paintEngine: Should no longer be called
https://bugs.kde.org/show_bug.cgi?id=362597
--- Comment #4 from Peter C. Trenholme ---
I still get those messages and, on the Fedora 25 ("Rawhide") system I'm on
right now, there is no "phonon-qt4" package available. (Both installed
packages, phonon and phonon-qt5, are version 4.9.0-3.)
Note that the messages are only visible them "phonon" is started from a command
line.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 362173] New: Plasma crashed on inital start-up
https://bugs.kde.org/show_bug.cgi?id=362173 Bug ID: 362173 Summary: Plasma crashed on inital start-up Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ptrenho...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.6.0 Operating System: Linux 4.4.7-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: Just booting into the plasmashell after a reboot. (The processes - two gkrellm instances - were started.) -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f19d0552940 (LWP 2275))] Thread 8 (Thread 0x7f19c5870700 (LWP 2278)): #0 0x7f19dedf1bd1 in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f19da905390 in read (__nbytes=16, __buf=0x7f19c586fa40, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7f19c00015b0) at gwakeup.c:210 #3 0x7f19da8c1c64 in g_main_context_check (context=context@entry=0x7f19b8000990, max_priority=2147483647, fds=fds@entry=0x7f19b8003020, n_fds=n_fds@entry=1) at gmain.c:3632 #4 0x7f19da8c2110 in g_main_context_iterate (context=context@entry=0x7f19b8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3837 #5 0x7f19da8c227c in g_main_context_iteration (context=0x7f19b8000990, may_block=may_block@entry=1) at gmain.c:3901 #6 0x7f19dfc30d0b in QEventDispatcherGlib::processEvents (this=0x7f19b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #7 0x7f19dfbd96ea in QEventLoop::exec (this=this@entry=0x7f19c586fc50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7f19dfa03004 in QThread::exec (this=this@entry=0x7f19e043c040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:503 #9 0x7f19e03c84b5 in QDBusConnectionManager::run (this=0x7f19e043c040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:181 #10 0x7f19dfa07e18 in QThreadPrivate::start (arg=0x7f19e043c040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:340 #11 0x7f19de13560a in start_thread (arg=0x7f19c5870700) at pthread_create.c:334 #12 0x7f19dee01a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f19b700 (LWP 2311)): #0 0x7f19dedf5fdd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f19da8c216c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f19b4002e70, timeout=, context=0x7f19b4000990) at gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f19b4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f19da8c227c in g_main_context_iteration (context=0x7f19b4000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f19dfc30d0b in QEventDispatcherGlib::processEvents (this=0x7f19b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f19dfbd96ea in QEventLoop::exec (this=this@entry=0x7f19bfffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f19dfa03004 in QThread::exec (this=this@entry=0x563d840bf160) at thread/qthread.cpp:503 #7 0x7f19e2df81b5 in QQmlThreadPrivate::run (this=0x563d840bf160) at /usr/src/debug/qtdeclarative-opensource-src-5.6.0/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x7f19dfa07e18 in QThreadPrivate::start (arg=0x563d840bf160) at thread/qthread_unix.cpp:340 #9 0x7f19de13560a in start_thread (arg=0x7f19b700) at pthread_create.c:334 #10 0x7f19dee01a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f19b1b2c700 (LWP 2312)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f19bdcae3b3 in cnd_wait (mtx=0x563d8428ed70, cond=0x563d8428ed98) at ../../../../../include/c11/threads_posix.h:159 #2 pipe_semaphore_wait (sema=0x563d8428ed70) at ../../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 radeon_drm_cs_emit_ioctl (param=param@entry=0x563d8428ea20) at radeon_drm_winsys.c:653 #4 0x7f19bdcadb07 in impl_thrd_routine (p=) at ../../../../../include/c11/threads_posix.h:87 #5 0x7f19de13560a in start_thread (arg=0x7f19b1b2c700) at pthread_create.c:334 #6 0x7f19dee01a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f19b0312700 (LWP 2320)): #0 0x7f19dedf5fdd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x000
[systemsettings] [Bug 362597] New: QWidget::paintEngine: Should no longer be called
https://bugs.kde.org/show_bug.cgi?id=362597 Bug ID: 362597 Summary: QWidget::paintEngine: Should no longer be called Product: systemsettings Version: 5.6.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ptrenho...@gmail.com QWidget::paintEngine: Should no longer be called displayed when systemsettings5 is invoked from a command line: $ systemsettings5 QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called QWidget::paintEngine: Should no longer be called -- You are receiving this mail because: You are watching all bug changes.
