[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 John A changed: What|Removed |Added CC||drjohnny...@gmail.com --- Comment #50 from John A --- I can confirm that the regression appears in Kubuntu 19.04 with kwin 5.15.90, an NVIDIA Optimus setup (NVIDIA is selected as the primary GPU), OpenGL 3.1 used as the rendering backend and options nvidia_drm modeset=1 set(to enable PRIME Synchronization and eliminate horizontal screen tearing). KWin hangs when using active screen edges (Present Windows), Alt-tabbing and sometimes when maximizing or moving a window. Switching the rendering backend to XRender resolves the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #54 from John A --- (In reply to Jeffery Patton from comment #51) > (In reply to John A from comment #50) > > I can confirm that the regression appears in Kubuntu 19.04 with kwin > > 5.15.90, an NVIDIA Optimus setup (NVIDIA is selected as the primary GPU), > > OpenGL 3.1 used as the rendering backend and options nvidia_drm modeset=1 > > set(to enable PRIME Synchronization and eliminate horizontal screen > > tearing). > > > > KWin hangs when using active screen edges (Present Windows), Alt-tabbing and > > sometimes when maximizing or moving a window. > > > > Switching the rendering backend to XRender resolves the issue. > > XRender doesn't resolve the issue, it's an ugly workaround that forces > software rendering. It's just about as bad as disabling Prime Sync. > > Thanks for confirming this affects the upcoming 5.16 as well though. Oh I agree that XRender is an ugly workaround. I was just pointing out that KWin does not hang when XRender is used as the rendering backend. In addition, the aforementioned fork (kwin-lowlatency) exhibits the same behaviour. I will apply the patches mentioned in this thread and report back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #55 from John A --- (In reply to John A from comment #54) > (In reply to Jeffery Patton from comment #51) > > (In reply to John A from comment #50) > > > I can confirm that the regression appears in Kubuntu 19.04 with kwin > > > 5.15.90, an NVIDIA Optimus setup (NVIDIA is selected as the primary GPU), > > > OpenGL 3.1 used as the rendering backend and options nvidia_drm modeset=1 > > > set(to enable PRIME Synchronization and eliminate horizontal screen > > > tearing). > > > > > > KWin hangs when using active screen edges (Present Windows), Alt-tabbing > > > and > > > sometimes when maximizing or moving a window. > > > > > > Switching the rendering backend to XRender resolves the issue. > > > > XRender doesn't resolve the issue, it's an ugly workaround that forces > > software rendering. It's just about as bad as disabling Prime Sync. > > > > Thanks for confirming this affects the upcoming 5.16 as well though. > > Oh I agree that XRender is an ugly workaround. I was just pointing out that > KWin does not hang when XRender is used as the rendering backend. > > In addition, the aforementioned fork (kwin-lowlatency) exhibits the same > behaviour. > > I will apply the patches mentioned in this thread and report back. Just to be clear, when I wrote that kwin-lowlatency exhibits the same behaviour, I meant it hangs, it does not resolve the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #67 from John A --- (In reply to hugues31100 from comment #66) > (In reply to Luca Carlon from comment #65) > > What distro? > > I use Manjaro Download the KWin sources from https://download.kde.org/stable/plasma/$pkgver/$pkgname-$pkgver.tar.xz, edit the file main_x11.cpp (apply the patch https://phabricator.kde.org/file/data/telix5fjwmcuir3v5yxs/PHID-FILE-dldsuycendhh6yyimgsp/Masterwork_From_Distant_Lands) and compress the sources to a tar.xz. Edit the PKGBUILD from https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/kwin with your own source tar.xz (compute the sha256sum for it and replace the field sha256sums in your PKGBUILD). Then, use the edited PKGBUILD to build and install the package. You have to repeat the process for qtbase , look at https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/qt5-base. The patch for qtbase is: diff --git a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp index 4adf662152..434ea60bfb 100644 --- a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp +++ b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp @@ -601,6 +601,7 @@ void QGLXContext::doneCurrent() else glXMakeCurrent(m_display, 0, 0); m_isPBufferCurrent = false; +m_swapInterval = -1; } void QGLXContext::swapBuffers(QPlatformSurface *surface) If for whatever reason you cannot apply the patches, just edit theses two files since the patches are pretty small in size. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #71 from John A --- (In reply to Drake from comment #69) > (In reply to Jeffery Patton from comment #68) > > (In reply to John A from comment #67) > > > (In reply to hugues31100 from comment #66) > > > > (In reply to Luca Carlon from comment #65) > > > > > What distro? > > > > > > > > I use Manjaro > > > > > > Download the KWin sources from > > > https://download.kde.org/stable/plasma/$pkgver/$pkgname-$pkgver.tar.xz, > > > edit > > > the file main_x11.cpp (apply the patch > > > https://phabricator.kde.org/file/data/telix5fjwmcuir3v5yxs/PHID-FILE- > > > dldsuycendhh6yyimgsp/Masterwork_From_Distant_Lands) and compress the > > > sources > > > to a tar.xz. > > > Edit the PKGBUILD from > > > https://git.archlinux.org/svntogit/packages.git/tree/trunk/ > > > PKGBUILD?h=packages/kwin with your own source tar.xz (compute the > > > sha256sum > > > for it and replace the field sha256sums in your PKGBUILD). > > > Then, use the edited PKGBUILD to build and install the package. > > > You have to repeat the process for qtbase , look at > > > https://git.archlinux.org/svntogit/packages.git/tree/trunk/ > > > PKGBUILD?h=packages/qt5-base. > > > The patch for qtbase is: > > > diff --git > > > a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > > > b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > > > index 4adf662152..434ea60bfb 100644 > > > --- > > > a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > > > +++ > > > b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > > > @@ -601,6 +601,7 @@ void QGLXContext::doneCurrent() > > > else > > > glXMakeCurrent(m_display, 0, 0); > > > m_isPBufferCurrent = false; > > > +m_swapInterval = -1; > > > } > > > > > > void QGLXContext::swapBuffers(QPlatformSurface *surface) > > > > > > If for whatever reason you cannot apply the patches, just edit theses two > > > files since the patches are pretty small in size. > > > > How about for Debian/Ubuntu/KDE Neon? > > > > I use KDE Neon (well, not as of late partly due to this bug) and I guess > > many of the steps are similar, except for the fact I'm dealing with Debian > > packages. Do I like, build KWin, then use checkinstall to create a package > > and install the package, or what? :/ > > > I suggest to wait for an official fix, else you have to repeat the build > process with each kwin update. > > If you still want to apply the patch, you need to know at least some basic > stuff how to build a package from source. Because this is different to every > distro, i cant cover every distro here, but usually every distro has a good > documentation how to build a package from source. I will show you today how > to do that in Kubuntu. > > Lets assume you have Kubuntu Disco Dingo, in that case you need to obtain > the sources for kwin Disco Dingo first. > > You can fetch them via web: > https://packages.ubuntu.com/disco/kde/kwin-x11 > > Or via apt-get(recommended) > apt-get source kwin-x11 > > > After you downloaded the sources you can apply the patch to main_x11.cpp. If > you aren't able to apply the patch for whatever reason, you can, like > Jeffery already mentioned, just edit the files manually because the patch > files are very small. After you have done that you need to install a few > required build-tools: > > sudo apt-get install build-essential fakeroot dpkg-dev > > Now the only step left, before we can start the build, is to get the > dependencies for the build itself. You can download and install them with: > > sudo apt-get build-dep kwin-x11 > > now we can start to create the build file > we can do this with cmake ./ > > And then we can start the build with the command > make > > After that you can install the package. You need to repeat the step for > qtbase but with the patch below > > - > --- > diff --git > a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > index 4adf662152..434ea60bfb 100644 > --- a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > +++ b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > @@ -601,
[kwin] [Bug 363006] KWin crashed while started after reboot
https://bugs.kde.org/show_bug.cgi?id=363006 --- Comment #4 from John A. Ward --- Created attachment 103413 --> https://bugs.kde.org/attachment.cgi?id=103413&action=edit New crash information added by DrKonqi kwin_x11 (5.7.5) using Qt 5.6.2 - What I was doing when the application crashed:This crash happened on FIRST boot of the system, and the system seems to be running without re-starting, false error? -- Backtrace (Reduced): #6 0x7f0dfbf41853 in QtPrivate::QStringList_contains(QStringList const*, QString const&, Qt::CaseSensitivity) () at /lib64/libQt5Core.so.5 #7 0x7f0dfdc2efe2 in QDBusConnectionPrivate::isServiceRegisteredByThread(QString const&) () at /lib64/libQt5DBus.so.5 #8 0x7f0dfdc36c68 in QDBusConnectionPrivate::sendWithReplyAsync(QDBusMessage const&, QObject*, char const*, char const*, int) () at /lib64/libQt5DBus.so.5 #9 0x7f0dfdc26318 in QDBusConnection::asyncCall(QDBusMessage const&, int) const () at /lib64/libQt5DBus.so.5 #10 0x7f0e0476add5 in KWin::LogindIntegration::logindServiceRegistered() () at /lib64/libkwin.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363006] KWin crashed while started after reboot
https://bugs.kde.org/show_bug.cgi?id=363006 John A. Ward changed: What|Removed |Added CC||j...@mbstemps.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 --- Comment #9 from John A. Ward --- (In reply to Bug Janitor Service from comment #8) > 🐛🧹 ⚠️ 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 correct, my error on reporting, also working on Fedora 39 install. The Fedora 40 is KDE 6.xx and problem is still critical, I have noticed that one time, the next morning after doing update, reboot, re-arrange icons. the previous day it was ok the next morning, then I started vnc and then the problem returned. I use an 'older' version of vnc, from -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 John A. Ward changed: What|Removed |Added Version|5.27.11 |6.2.2 --- Comment #12 from John A. Ward --- (In reply to Bug Janitor Service from comment #11) > 🐛🧹 ⚠️ 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! KDE has said the bug is fixed in 6.3, but doing a dnf upgrade hasn't gotten that change yet so I can't verify that problem has been solved, I will respond again when the 6.3 KDE is in Fedora update. Thank You John -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] New: Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 Bug ID: 493554 Summary: Icons move AFTER being Locked. Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.27 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Icon Assignee: plasma-b...@kde.org Reporter: j...@mbstemps.com Target Milestone: 1.0 Created attachment 174006 --> https://bugs.kde.org/attachment.cgi?id=174006&action=edit main screen SUMMARY I have my application on Fedora 39 and all is well, moved to Fedora 40 and icons move after being arranged and 'locked'. My application uses 4x icons that need to be in a specific order. After arranging the icons, I lock them and continue testing the system, my system is up-to-date with Fedora dnf update. I am using the x11 windows, since the Wayland system doesn't emulate x11 well enough. I use kde - vnc for my application. If I setup the system all is good, then the next day SOME of the icons move, the Day AFTER more move and finally all have moved back into alpha order, which renders the system unuseable to me AND my clients. Thank you in advance. Joh I have done the Waayland-x11 update already STEPS TO REPRODUCE 1. Set up Icons 2. lock the screen 3. OBSERVED RESULT The Icons move into alpha order. EXPECTED RESULT Icons need to stay in order. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: F40 KDE Plasma Version: 5.27 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 --- Comment #1 from John A. Ward --- Created attachment 174007 --> https://bugs.kde.org/attachment.cgi?id=174007&action=edit showing icons moving Screens before, and at next day, and next day -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 --- Comment #3 from John A. Ward --- Do you need any further information, why anyone would mandate a move to Wayland when it doesn't work is beyond me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 --- Comment #5 from John A. Ward --- Mr. Graham, I did the upgrade from the Fedora site from Fedora 39 to Fedora 40, so I got whatever Red Hat - Fedora is distributing. What should I do to make the system supportable? I did what I normally do to upgrade to the latest release. I would appreciate your comments on this method of upgrading and suggestions for what I should try. There are Wayland-X11 patches that Fedora distributes to make systems still work after the upgrade. I still don't understand how a major factor in Linux, such as KDE can embrace MAJOR changes to the system that Break working Systems, your comments are welcome. Thank you for your comments so far. John A. Ward > On 09/30/2024 4:40 PM EDT Nate Graham wrote: > > > https://bugs.kde.org/show_bug.cgi?id=493554 > > --- Comment #4 from Nate Graham --- > I'm asking about the process by which you accomplished this, because to my > knowledge Fedora 40 doesn't support Plasma 5.27. If I'm correct and you > managed > to force it in there through extraordinary means, then I'm afraid KDE won't be > able to offer support, because iIt becomes quite possible that any weird > random > issues you're seeing are the result of components that were not designed to > work together being forced to anyway. In this case, you become the system > integrator, and responsibility for debugging issues falls on your own > shoulders. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 --- Comment #6 from John A. Ward --- Mr. Graham, I didn't mention that I used the DNF method, somebody should look into that. It sounds like DNF didn't replace KDE with the new version? John > On 10/01/2024 3:03 PM EDT John A. Ward wrote: > > > https://bugs.kde.org/show_bug.cgi?id=493554 > > --- Comment #5 from John A. Ward --- > Mr. Graham, > > I did the upgrade from the Fedora site from Fedora 39 to Fedora 40, so I got > whatever Red Hat - Fedora is distributing. What should I do to make the > system > supportable? I did what I normally do to upgrade to the latest release. I > would appreciate your comments on this method of upgrading and suggestions for > what I should try. > > There are Wayland-X11 patches that Fedora distributes to make systems still > work after the upgrade. > > I still don't understand how a major factor in Linux, such as KDE can embrace > MAJOR changes to the system that Break working Systems, your comments are > welcome. > > Thank you for your comments so far. > John A. Ward > > > On 09/30/2024 4:40 PM EDT Nate Graham wrote: > > > > > > https://bugs.kde.org/show_bug.cgi?id=493554 > > > > --- Comment #4 from Nate Graham --- > > I'm asking about the process by which you accomplished this, because to my > > knowledge Fedora 40 doesn't support Plasma 5.27. If I'm correct and you > > managed > > to force it in there through extraordinary means, then I'm afraid KDE won't > > be > > able to offer support, because iIt becomes quite possible that any weird > > random > > issues you're seeing are the result of components that were not designed to > > work together being forced to anyway. In this case, you become the system > > integrator, and responsibility for debugging issues falls on your own > > shoulders. > > > > -- > > You are receiving this mail because: > > You reported the bug. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] When encountering a "zero screens connected" condition, desktop icons get re-arranged (first time in alphabetical order, then after that randomly)
https://bugs.kde.org/show_bug.cgi?id=482875 John A. Ward changed: What|Removed |Added CC||j...@mbstemps.com --- Comment #32 from John A. Ward --- Thank you for your work, and responding. I guess my action should be, load new updates. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 --- Comment #15 from John A. Ward --- (In reply to Nate Graham from comment #2) > How did you manage to get Plasma 5.27 on Fedora KDE 40? Nate, as I wrote earlier, my fault I looked at a fedora 39 computer, the Fedora 40 is currently 6.2.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 John A. Ward changed: What|Removed |Added Version|6.2.2 |6.2.3 --- Comment #16 from John A. Ward --- (In reply to Bug Janitor Service from comment #13) > 🐛🧹 ⚠️ 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! Still doesn't work and current version is 6.2.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493554] Icons move AFTER being Locked.
https://bugs.kde.org/show_bug.cgi?id=493554 --- Comment #14 from John A. Ward --- I have been doing updates basically every day, the KDE version is 6.2.3 and the problem is still there. There was a message that the problem has been solved in Version 6.3.x, is Fedora going to include the update OR is there some other way to get the update. I have been in this process for close to 3 months and have had to update the computers I hope to sell with Fedora 39, which of course is kind of unsupported now. Thank You for your efforts. John -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 456808] Crash when changing scan source or color option
https://bugs.kde.org/show_bug.cgi?id=456808 John A. Ward changed: What|Removed |Added CC||j...@mbstemps.com -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 456808] Crash when changing scan source or color option
https://bugs.kde.org/show_bug.cgi?id=456808 --- Comment #13 from John A. Ward --- I found a solution, the device wasn't scaned by the scanning program, when I called it from Libreoffice it worked fine. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 497964] New: skanlie says invalid option?
https://bugs.kde.org/show_bug.cgi?id=497964 Bug ID: 497964 Summary: skanlie says invalid option? Classification: Applications Product: Skanlite Version: 23.08.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: j...@mbstemps.com Target Milestone: --- Application: skanlite (23.08.5) Qt Version: 5.15.14 Frameworks Version: 5.116.0 Operating System: Linux 6.11.4-101.fc39.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 39 (Thirty Nine)" DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: went to do a scan, source option was flatbed and I selecte letter(alto didn[t work when i didn't select letter) The crash can be reproduced every time. -- Backtrace: Application: Skanlite (skanlite), signal: Segmentation fault [KCrash Handler] #4 0x7fd1b1485382 in esci_reset () at /usr/lib64/sane/libsane-epson2.so.1 #5 0x7fd1b148602c in sane_epson2_control_option () at /usr/lib64/sane/libsane-epson2.so.1 #6 0x7fd1dc57a03c in KSaneCore::BaseOption::writeData(void*) () at /lib64/libKSaneCore.so.1 #7 0x7fd1dc57cff3 in KSaneCore::ListOption::setValue(QVariant const&) () at /lib64/libKSaneCore.so.1 #8 0x7fd1db2e9471 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #9 0x7fd1dcd92fda in KSaneIface::LabeledCombo::emitChangedValue(int) () at /lib64/libKF5Sane.so.5 #10 0x7fd1db2e9471 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #11 0x7fd1dc0bcb63 in QComboBox::activated(int) () at /lib64/libQt5Widgets.so.5 #12 0x7fd1dc0be4f7 in QComboBoxPrivate::emitActivated(QModelIndex const&) () at /lib64/libQt5Widgets.so.5 #13 0x7fd1db2e95f8 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #14 0x7fd1dc0bcf19 in QComboBoxPrivateContainer::itemSelected(QModelIndex const&) () at /lib64/libQt5Widgets.so.5 #15 0x7fd1dc0bd84d in QComboBoxPrivateContainer::eventFilter(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #16 0x7fd1db2b4f46 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #17 0x7fd1dbfaeaa5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #18 0x7fd1dbfb7396 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #19 0x7fd1db2b5198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #20 0x7fd1dbfb55e4 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #21 0x7fd1dc00dc42 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #22 0x7fd1dc01062f in QWidgetWindow::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #23 0x7fd1dbfaeab5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #24 0x7fd1db2b5198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #25 0x7fd1db76cccb in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #26 0x7fd1db74ad6c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #27 0x7fd1c8d1c436 in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #28 0x7fd1d9b11e5c in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0 #29 0x7fd1d9b6cf68 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0 #30 0x7fd1d9b0fad3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #31 0x7fd1db3075f9 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #32 0x7fd1db2b3b5b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #33 0x7fd1db2bbdeb in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #34 0x55d4dbfd1604 in main () [Inferior 1 (process 2163517) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 497145] New: crash when pressing the 'scan' button
https://bugs.kde.org/show_bug.cgi?id=497145 Bug ID: 497145 Summary: crash when pressing the 'scan' button Classification: Applications Product: Skanlite Version: 23.08.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: j...@mbstemps.com Target Milestone: --- Application: skanlite (23.08.5) Qt Version: 5.15.14 Frameworks Version: 5.116.0 Operating System: Linux 6.11.4-101.fc39.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 39 (Thirty Nine)" DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: nothing unusual, selected from the application menu The crash can be reproduced every time. -- Backtrace: Application: Skanlite (skanlite), signal: Segmentation fault [KCrash Handler] #4 0x7f3b3c128e41 in e2_init_parameters () at /usr/lib64/sane/libsane-epson2.so.1 #5 0x7f3b3c131f68 in sane_epson2_start () at /usr/lib64/sane/libsane-epson2.so.1 #6 0x7f3b66bea50e in KSaneCore::ScanThread::run() () at /lib64/libKSaneCore.so.1 #7 0x7f3b65ef5d2d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f3b658ac907 in start_thread () at /lib64/libc.so.6 #9 0x7f3b65933adc in clone3 () at /lib64/libc.so.6 Thread 1 (Thread 0x7f3b611daa00 (LWP 1393870) "skanlite"): #1 0x7f3b65ef7c6b in QSemaphore::acquire(int) () at /lib64/libQt5Core.so.5 #2 0x7f3b660e9561 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #3 0x7f3b660e4451 in QObject::destroyed(QObject*) () at /lib64/libQt5Core.so.5 #4 0x7f3b660e60fb in QObject::~QObject() () at /lib64/libQt5Core.so.5 #5 0x7f3b663e22cc in (anonymous namespace)::Q_QGS_s_globalData::innerFunction()::Holder::~Holder() () at /lib64/libKF5IconThemes.so.5 #6 0x7f3b6585efd6 in __run_exit_handlers () at /lib64/libc.so.6 #7 0x7f3b6585f11e in exit () at /lib64/libc.so.6 #8 0x7f3b610a78b3 in QXcbConnection::processXcbEvents(QFlags) [clone .cold] () at /lib64/libQt5XcbQpa.so.5 #9 0x7f3b610d842f in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #10 0x7f3b64b11e5c in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0 #11 0x7f3b64b6cf68 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0 #12 0x7f3b64b0fad3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #13 0x7f3b661075f9 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #14 0x7f3b660b3b5b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #15 0x7f3b660bbdeb in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #16 0x5575146c8604 in main () [Inferior 1 (process 1393870) detached] The reporter indicates this bug may be a duplicate of or related to bug 473557. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 460969] New: Could not find plugin kcm_cookies
https://bugs.kde.org/show_bug.cgi?id=460969 Bug ID: 460969 Summary: Could not find plugin kcm_cookies Classification: Applications Product: konqueror Version: 21.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcookiejar Assignee: fa...@kde.org Reporter: jab_creati...@yahoo.com Target Milestone: --- SUMMARY I needed to clear cookies in Konquorer while testing the KHTML engine. I received the error "Could not find plugin kcm_cookies" in the area of the configuration window where it should have loaded. STEPS TO REPRODUCE 1. Open Konquorer. 2. Go to the "Settings" file menu and then "Configure Konquorer...". 3. The cookie management panel's menu item should be under "History", it is blank. I just downloaded and installed the latest 64 bit ISO from the Kubuntu website for the explicit purposes of testing out KHTML. Unfortunately deleting the cookie on the server with the browser closed somehow manages to not reset the session cookie. I also am not familiar with the KDE file system nor Konquorer's profile location so I do not know how to manually delete the cookie in the file system. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 272550] Benchmark - Failure to give focus to anchors, not triggering event listeners
https://bugs.kde.org/show_bug.cgi?id=272550 --- Comment #3 from John A. Bilicki III --- The benchmark is no longer up and I don't have the time to restore it. If I were working on bugs I would have given a bug with the word benchmark top priority as people take such criteria in to consideration when choosing which browser to use. All I can do at this point is explain what happened. A while script would give focus to anchors. Each anchor should have had it's onfocus attribute trigger and that would have changed the background-color of the page. Only Firefox 3.6 and older (and I think (real) Opera at that time actually correctly triggered the focus event for the anchors. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 272550] Benchmark - Failure to give focus to anchors, not triggering event listeners
https://bugs.kde.org/show_bug.cgi?id=272550 --- Comment #5 from John A. Bilicki III --- No problem. Looks like I attached the benchmark as intended. I would test it in Firefox 3.6 to see what you should expect. Just look up Firefox FTP to find those older versions, they're not hidden like Chrome. -- You are receiving this mail because: You are watching all bug changes.
