[plasmashell] [Bug 434068] The new "fade the screen when you don't move the mouse for a bit" stuck my monitor on a lower brightness
https://bugs.kde.org/show_bug.cgi?id=434068 --- Comment #2 from Keziolio --- Ok now I get it, kde has introduced the protocol thing that modifies the backlight of desktop monitors attached by displayport, just like laptops, but I've never seen this before on a desktop computer, for some reason one of my monitors remembers the default brightness, the other one does not, and this caused the bug when the power interrupted, so not a kde bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434068] The new "fade the screen when you don't move the mouse for a bit" stuck my monitor on a lower brightness
https://bugs.kde.org/show_bug.cgi?id=434068 Keziolio changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Keziolio --- Apparently I can't reproduce this, so idk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434068] New: The new "fade the screen when you don't move the mouse for a bit" stuck my monitor on a lower brightness
https://bugs.kde.org/show_bug.cgi?id=434068 Bug ID: 434068 Summary: The new "fade the screen when you don't move the mouse for a bit" stuck my monitor on a lower brightness Product: plasmashell Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: keziolio...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY title STEPS TO REPRODUCE 1. wait for the screen to fade by not using the computer 2. abrupt power failure 3. reboot to a dim monitor OBSERVED RESULT the screen is dim EXPECTED RESULT when booting the computer, the screen should be reset to the normal brightness SOFTWARE/OS VERSIONS Archlinux, everything up to date ADDITIONAL INFORMATION How do I manually reset this to normal and disable this forever? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #20 from Keziolio --- The old code was updating history inside the request visible pixmap function, those two things are semantically not the same, they were put in the same place for reasons unknown to me, my new implementation just exposed this original bad design decision -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422050] Scrolling issues with PageDown/PageUp navigation
https://bugs.kde.org/show_bug.cgi?id=422050 --- Comment #13 from Keziolio --- Just to remind everyone, there's already !194 that was addressing this bug two months ago, by reverting to the old behavior. I can understand why you wouldn't want that patch given the circumstances, but really, the fix is sound, I shouldn't be still hearing people complain about this bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422702] New: Virtual keyboard stopped working since the last update, wayland
https://bugs.kde.org/show_bug.cgi?id=422702 Bug ID: 422702 Summary: Virtual keyboard stopped working since the last update, wayland Product: kwin Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: keziolio...@gmail.com Target Milestone: --- SUMMARY Virtual keyboard closes itself after pressing a key, after the new 5.19 update STEPS TO REPRODUCE 1. start kde on wayland in a touchscreen device without a physical keyboard 2. press on a text box 3. try to write in the text box with the virtual keyboard OBSERVED RESULT The keyboard closes itself EXPECTED RESULT The keyboard should write stuff in the text box SOFTWARE/OS VERSIONS Everything up to date on Archlinux -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422050] Scrolling issues with PageDown/PageUp navigation
https://bugs.kde.org/show_bug.cgi?id=422050 --- Comment #5 from Keziolio --- > with these limitations It's not a limitation of the smooth scrolling itself, I'm incredibly busy in this period and wasn't able to provide a decent fix for the other bug, those are all easy fixes but I literally don't have the time, feel free to disable all the offending stuff, I'll come back next month, sorry. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 Keziolio changed: What|Removed |Added CC||keziolio...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420842] Scrolling with browse tool sticks at first after inertial scrolling implemented
https://bugs.kde.org/show_bug.cgi?id=420842 --- Comment #4 from Keziolio --- This is a QScroller feature almost for sure. It's one of the configuration parameters that Qt documentation explicitly says to keep to the "platform optimized" values. https://doc.qt.io/qt-5/qscrollerproperties.html You feel it's too severe? (btw, try it in your phone, it does the same) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] 20.04.0 significantly slows down mouse scrolling with a "hyperscroll" mouse or a touchpad driver that sends mouse wheel scroll events when configured for greater speed
https://bugs.kde.org/show_bug.cgi?id=420492 --- Comment #17 from Keziolio --- The animation is controlled by time and it's independent from system performance -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] 20.04.0 significantly slows down mouse scrolling with a "hyperscroll" mouse or a touchpad driver that sends mouse wheel scroll events when configured for greater speed
https://bugs.kde.org/show_bug.cgi?id=420492 --- Comment #15 from Keziolio --- > Changing the value for nSteps to 2000 from 200 brought back the scrolling > from previous versions. It seems that the regression may be in animation > speed rather than scrolling if none of the code has changed. So it turns out that the hyperscroll mouse doesn't do per pixel scrolling, it just sends normal mouse events at an ungodly rate -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] 20.04.0 significantly slows down mouse scrolling with a "hyperscroll" mouse or a touchpad driver that sends mouse wheel scroll events when configured for greater speed
https://bugs.kde.org/show_bug.cgi?id=420492 --- Comment #10 from Keziolio --- Albert, Regarding the touchpad, nothing was broken, the behavior is the same as before Regarding the hyperscroll mouse, I have no idea since I don't have that device, it's still not "broken" My digression was an answer to David's comment, regarding the fact that the hyperscoll device events are probably handled in the same way as a regular mouse / touchpad, and that's quite suboptimal if we want to achieve a polished experience, but it's not worse than it was before There is no major breakage, calm down Regarding the original bug, the behaviour of the scroll events is programmed to be literally the same as it was before, probably QScroller::scrollTo behaves in a suboptimal way if it's flooded with events, I'll see if something comes to mind -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] 20.04.0 significantly slows down mouse scrolling with a "hyperscroll" mouse or a touchpad driver that sends mouse wheel scroll events when configured for greater speed
https://bugs.kde.org/show_bug.cgi?id=420492 --- Comment #5 from Keziolio --- 1) I don't clearly remember the details, but I remember the fact that I had to do a fair bunch of hacks because Qt on Linux doesn't give us precise informations on the matter, this is the reason we don't have the inertial scrolling on touchpad; if I remember correctly, unfortunately, everything goes down the same pipe: mouse discrete scrolling, mouse free scroll, touchpad scroll, etc. And yes, I opened a Qt issue, and they told me to bugger off, you can see the details on the original discussion And yes, this is quite sad and is currently the bottleneck in getting all of this working in a decent way, but I'm not sure if I have the energy to try and patch upstream Qt 2) By "you" I was meaning to the bug OP, not you David :P I'm sure you can compile Okular 3) It'be cool to have all the options in the Okular settings panel, I'm not aware on a method to disable it -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] 20.04.0 significantly slows down mouse scrolling with a "hyperscroll" mouse or a touchpad driver that sends mouse wheel scroll events when configured for greater speed
https://bugs.kde.org/show_bug.cgi?id=420492 --- Comment #2 from Keziolio --- In the original discussion about the smooth scrolling we diverged from the Qt defaults in some settings, you are probably affected by this configuration https://invent.kde.org/kde/okular/-/blob/master/ui/pageview.cpp#L450 Unfortunately I don't have a mouse with that feature, are you able to test with that value increased from 1 to something like 5-10, at your liking? I can provide you with a precompiled archlinux package if you trust random binaries from the internet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417764] segfault when creating and deleting a lot of widgets (tested with the notes)
https://bugs.kde.org/show_bug.cgi?id=417764 --- Comment #1 from Keziolio --- Created attachment 126089 --> https://bugs.kde.org/attachment.cgi?id=126089&action=edit valgrind log This is the end of the output when plasmashell managed to crash valgrind -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417764] New: segfault when creating and deleting a lot of widgets (tested with the notes)
https://bugs.kde.org/show_bug.cgi?id=417764 Bug ID: 417764 Summary: segfault when creating and deleting a lot of widgets (tested with the notes) Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: keziolio...@gmail.com Target Milestone: 1.0 SUMMARY When pasting something in the desktop, and deleting the note widget that appeared, several dozen times, plasmashell crashes STEPS TO REPRODUCE 1. open plasmashell 2. create dozens of notes on the desktop 3. delete the above notes 4. repeat ... 5. observe the random crash Arch Linux, I compiled plasmashell from git This is one crash (gdb) bt #0 0x76b11cbd in KWindowInfo::state() const () at /usr/lib/libKF5WindowSystem.so.5 #1 0x76b11ce9 in KWindowInfo::hasState(QFlags) const () at /usr/lib/libKF5WindowSystem.so.5 #2 0x7fffed304224 in TaskManager::XWindowTasksModel::data(QModelIndex const&, int) const () at /usr/lib/libtaskmanager.so.6 #3 0x753b3815 in QAbstractProxyModel::data(QModelIndex const&, int) const () at /usr/lib/libQt5Core.so.5 #4 0x7fffed2d5404 in TaskManager::TaskFilterProxyModel::acceptsRow(int) const () at /usr/lib/libtaskmanager.so.6 #5 0x753c8435 in () at /usr/lib/libQt5Core.so.5 #6 0x753c9c8b in () at /usr/lib/libQt5Core.so.5 #7 0x754274a0 in () at /usr/lib/libQt5Core.so.5 #8 0x75394246 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #9 0x753ba86a in () at /usr/lib/libQt5Core.so.5 #10 0x753bc028 in () at /usr/lib/libQt5Core.so.5 #11 0x754274a0 in () at /usr/lib/libQt5Core.so.5 #12 0x75394246 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #13 0x7fffed2febf8 in () at /usr/lib/libtaskmanager.so.6 #14 0x7542746e in () at /usr/lib/libQt5Core.so.5 #15 0x7fffefbff111 in () at /usr/lib/qt/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so #16 0x753eeea7 in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () at /usr/lib/libQt5Core.so.5 #17 0x70d8dab3 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /usr/lib/libQt5XcbQpa.so.5 #18 0x70d8e839 in QXcbConnection::processXcbEvents(QFlags) () at /usr/lib/libQt5XcbQpa.so.5 #19 0x70db7ba4 in () at /usr/lib/libQt5XcbQpa.so.5 #20 0x737bd39e in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #21 0x737bf1b1 in () at /usr/lib/libglib-2.0.so.0 #22 0x737bf1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #23 0x7544a020 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #24 0x753f04cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x753f84d6 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #26 0x555869bc in main(int, char**) (argc=1, argv=0x7fffdb58) at /tmp/plasma-workspace/shell/main.cpp:228 Another crash (may be different) with all the threads: Thread 100 (Thread 0x7fff4e7fc700 (LWP 30672)): #0 0x74930cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7521bcb4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7521bd92 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7760856b in () at /usr/lib/libQt5Quick.so.5 #4 0x776087fb in () at /usr/lib/libQt5Quick.so.5 #5 0x75215fc6 in () at /usr/lib/libQt5Core.so.5 #6 0x7492a46f in start_thread () at /usr/lib/libpthread.so.0 #7 0x74d3c3d3 in clone () at /usr/lib/libc.so.6 Thread 99 (Thread 0x7fff4effd700 (LWP 30671)): #0 0x74930cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fffdf275dfc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fffdf2759f8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7492a46f in start_thread () at /usr/lib/libpthread.so.0 #4 0x74d3c3d3 in clone () at /usr/lib/libc.so.6 Thread 98 (Thread 0x7ffea9ffb700 (LWP 30669)): #0 0x74930cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7521bcb4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7521bd92 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7760856b in () at /usr/lib/libQt5Quick.so.5 #4 0x776087fb in () at /usr/lib/libQt5Quick.so.5 #5 0x75215fc6 in () at /usr/lib/libQt5Core.so.5 #6 0x7ff
[dolphin] [Bug 415212] Dolphin crashed when renaming folder
https://bugs.kde.org/show_bug.cgi?id=415212 Keziolio changed: What|Removed |Added CC||keziolio...@gmail.com --- Comment #1 from Keziolio --- I'm seeing extremely frequent crashes since the latest release on Archlinux too, especially, but not only, when dealing with multiple tabs on multiple devices Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f943575c800 (LWP 2362))] Thread 21 (Thread 0x7f93e5de5700 (LWP 2384)): #0 0x7f943c8d89ef in poll () from /usr/lib/libc.so.6 #1 0x7f943847a120 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f943847a1f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f943a87db2c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f943a82483c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f943a656305 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f943a657530 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 20 (Thread 0x7f93e67fc700 (LWP 2383)): #0 0x7f94390d7c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f942d63d48c in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x7f942d63d088 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 19 (Thread 0x7f93e6ffd700 (LWP 2382)): #0 0x7f94390d7c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f942d63d48c in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x7f942d63d088 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 18 (Thread 0x7f93e77fe700 (LWP 2381)): #0 0x7f94390d7c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f942d63d48c in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x7f942d63d088 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 17 (Thread 0x7f93e7fff700 (LWP 2380)): #0 0x7f94390d7c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f942d63d48c in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x7f942d63d088 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 16 (Thread 0x7f9408ff9700 (LWP 2379)): #0 0x7f94390d7c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f942d63d48c in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x7f942d63d088 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 15 (Thread 0x7f94097fa700 (LWP 2378)): #0 0x7f94390d7c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f942d63d48c in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x7f942d63d088 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 14 (Thread 0x7f9409ffb700 (LWP 2377)): #0 0x7f94390d7c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f942d63d48c in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x7f942d63d088 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 13 (Thread 0x7f940a7fc700 (LWP 2376)): #0 0x7f94390d7c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f942d63d48c in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x7f942d63d088 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 12 (Thread 0x7f940affd700 (LWP 2375)): #0 0x7f94390d7c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f942d63d48c in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x7f942d63d088 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7f94390d14cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f943c8e32d3 in clone () from /usr/lib/libc.so.6 Thread 11 (Thread 0x7f940b7
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #5 from Keziolio --- I'll have more time later this week -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #3 from Keziolio --- diff --git a/ui/pageview.cpp b/ui/pageview.cpp index e0401826d..b97f05a62 100644 --- a/ui/pageview.cpp +++ b/ui/pageview.cpp @@ -1372,7 +1372,7 @@ void PageView::slotRealNotifyViewportChanged( bool smoothMove ) const QPoint centerCoord = viewportToContentArea( vp ); // if smooth movement requested, setup parameters and start it -center( centerCoord.x(), centerCoord.y(), smoothMove ); +center( centerCoord.x(), centerCoord.y(), false ); d->blockPixmapsRequest = false; This works around the problem disabling the smooth scrolling, I don't see what side effect that would have on the navigation -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #2 from Keziolio --- This seems to be the offending commit https://invent.kde.org/kezik/okular/commit/6516c91302b24d8e48545393edb67f2a6c0e599b -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 Keziolio changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 Keziolio changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #16 from Keziolio --- Oh ok, thanks for the support -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #13 from Keziolio --- "kwin" is always broken since I can't open yakuake in the rightmost monitor, the problem is persistent Is the issue with the panel and not with kwin? I'm confused on what does what -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #12 from Keziolio --- Created attachment 122516 --> https://bugs.kde.org/attachment.cgi?id=122516&action=edit xprop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #11 from Keziolio --- Created attachment 122515 --> https://bugs.kde.org/attachment.cgi?id=122515&action=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #8 from Keziolio --- Yes I can, both "symptoms" persist with compositing disabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #6 from Keziolio --- I can reproduce the bug with "Full Screen Repaints" enabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #3 from Keziolio --- The screenshot "Full Screen (All Monitors)" in spectacle looks good, so does the qdbus command you gave me, it's not broken Regarding the screenshots issue, it's just the "preview" thing inside spectacle that is shifted, and I can't reach the leftmost part because it's "outside" the monitors -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] New: General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 Bug ID: 411652 Summary: General breakage with multiple monitors (affecting yakuake and spectacle) Product: kwin Version: 5.16.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multihead Assignee: kwin-bugs-n...@kde.org Reporter: keziolio...@gmail.com Target Milestone: --- SUMMARY Please see the video: https://youtu.be/zikzg5cDIrs This is with xorg, mesa with amd gpu The two major things are: 1) spectacle's "rectangular region" mode is shifted to the left, and I can't screenshot the left part of the desktop 2) yakuake doesn't show up on a monitor, or, with two monitors, it shows but with a smaller / wrong width This seems to also glitch part of some applications, for example QtCreator works "better" on the left monitor, on the rightmost one it tends to glitch and not update the screen / render some panels with wrong size STEPS TO REPRODUCE 1. attach more than one monitor (tested with 2 and 3 4k monitors) 2. admire the breakage I can reproduce this with another clean user, so it shouldn't be a configuration issue OBSERVED RESULT Bugs EXPECTED RESULT The absence of bugs SOFTWARE/OS VERSIONS Latest version of everything in Arch Linux, this has been going on for ages ADDITIONAL INFORMATION $ xrandr --listmonitors Monitors: 3 0: +*DisplayPort-1 3840/600x2160/340+3840+0 DisplayPort-1 1: +DisplayPort-0 3840/607x2160/345+7680+0 DisplayPort-0 2: +HDMI-A-1 3840/608x2160/345+0+0 HDMI-A-1 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 402878] Display GPU loads and vRAM in Ksysguard
https://bugs.kde.org/show_bug.cgi?id=402878 Keziolio changed: What|Removed |Added CC||keziolio...@gmail.com --- Comment #2 from Keziolio --- Is it theoretically possible to have ksysguard organize what it finds in "semantical" categories? For example, making an extra folder called "Quick Sensors" at the top, with inside: "CPU Usage" "CPU Temperature" "GPU Usage" "GPU Temperature" etc And obviously ksysguard internally searches the most relevant source and attaches it to the relative virtual sensor. That would lay the ground for solving this issue and it'll make ksysguard more usable, because now for gpu temp I have to dig into the hardware sensor and hope that "amdgpu-pci-0900" is what I need. I can find that but non technical users will struggle -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391369] plasmashell crashes when reordering tasks
https://bugs.kde.org/show_bug.cgi?id=391369 --- Comment #6 from Keziolio --- > Does anyone have this with Qt >= 5.12? Yes, I have installed Qt 5.12.0 https://www.archlinux.org/packages/extra/x86_64/qt5-base/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391369] plasmashell crashes when reordering tasks
https://bugs.kde.org/show_bug.cgi?id=391369 --- Comment #4 from Keziolio --- While trying to reproduce my bug (that was marked as duplicate of this), while running plasmashell in gdb, I got this: othing to load - the client id is empty Nothing to load - the client id is empty file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/DashboardRepresentation.qml:977: TypeError: Cannot read property 'textWidth' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/DashboardRepresentation.qml:968:36: QML Highlight: Cannot anchor to an item that isn't a parent or sibling. file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/DashboardRepresentation.qml:968:36: QML Highlight: Cannot anchor to an item that isn't a parent or sibling. file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/DashboardRepresentation.qml:968:36: QML Highlight: Cannot anchor to an item that isn't a parent or sibling. qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [Detaching after fork from child process 1250] file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/ItemGridView.qml:420: TypeError: Cannot read property 'itemIndex' of null Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. 0x7fffeffdbfd0 in ?? () from /usr/lib/libQt5WaylandClient.so.5 (gdb) Using Wayland-EGL Is this of any use? I still get this bug on recent archlinux packages -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399208] Okular has an extemely high latency when scrolling with a wacom tablet
https://bugs.kde.org/show_bug.cgi?id=399208 Keziolio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #9 from Keziolio --- It seems that it's Qt's job to avoid this issue, or, at least, there's a difference in how Qt handles the mouse vs the touch thing I opened a Qt bug report for this issue: https://bugreports.qt.io/browse/QTBUG-71708 So I'm closing this for now -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400733] Application crash on text highlight
https://bugs.kde.org/show_bug.cgi?id=400733 --- Comment #2 from Keziolio --- Archlinux already distributed the fixed poppler, it'll reach manjaro soon -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400733] Application crash on text highlight
https://bugs.kde.org/show_bug.cgi?id=400733 Keziolio changed: What|Removed |Added Resolution|--- |DUPLICATE CC||keziolio...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Keziolio --- *** This bug has been marked as a duplicate of bug 400511 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400511] Crash when trying to highlight/underline a text
https://bugs.kde.org/show_bug.cgi?id=400511 Keziolio changed: What|Removed |Added CC||simg...@gmail.com --- Comment #4 from Keziolio --- *** Bug 400733 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399208] Okular has an extemely high latency when scrolling with a wacom tablet
https://bugs.kde.org/show_bug.cgi?id=399208 --- Comment #7 from Keziolio --- Created attachment 115966 --> https://bugs.kde.org/attachment.cgi?id=115966&action=edit path -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399208] Okular has an extemely high latency when scrolling with a wacom tablet
https://bugs.kde.org/show_bug.cgi?id=399208 --- Comment #6 from Keziolio --- sorry :C I made a patch that fixes the issue, can you look into it? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399208] Okular has an extemely high latency when scrolling with a wacom tablet
https://bugs.kde.org/show_bug.cgi?id=399208 Keziolio changed: What|Removed |Added Assignee|okular-de...@kde.org|keziolio...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399208] Okular has an extemely high latency when scrolling with a wacom tablet
https://bugs.kde.org/show_bug.cgi?id=399208 --- Comment #4 from Keziolio --- I tried with the nvidia card in my hybrid graphics laptop, running okular with bumblebee, the problem is reproduced (it can still be an intel bug, idk) I tried in my tablet with a touchscreen (and intel soc), and the problem is reproduced, so it's not only the wacom tablet that causes the bug, but probably everything that works like a touchscreen -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399208] Okular has an extemely high latency when scrolling with a wacom tablet
https://bugs.kde.org/show_bug.cgi?id=399208 --- Comment #3 from Keziolio --- I compiled okular 1.1.3 and 1.0.3 and the problem was still present, I'm pretty sure that the regression was more recent than that... So where should I look? I haven't noticed this kind of slowdown in other parts of the system, there's something that breaks okular in a specific way... I think the problem can be worked around by consuming the input as fast as possible and updating the page position once every screen refresh, I can mind a bad framerate but not 30+ seconds of latency, I think this is still an okular issue, but I was not even able to find the relevant file/function in the okular source code and it's not that well documented, if someone can help in that regard that'll be great This is the output of perf top when the latency is rolling: Samples: 347K of event 'cycles:ppp', 4000 Hz, Event count (approx.): 74074580252 Overhead Shared ObjectSymbol 34.75% [kernel] [k] copy_user_enhanced_fast_string 3.13% [kernel] [k] __check_object_size 1.64% libc-2.28.so [.] __memmove_avx_unaligned_erms 1.38% [kernel] [k] __radix_tree_lookup 1.03% perf [.] hpp__sort_overhead -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399208] New: Okular has an extemely high latency when scrolling with a wacom tablet
https://bugs.kde.org/show_bug.cgi?id=399208 Bug ID: 399208 Summary: Okular has an extemely high latency when scrolling with a wacom tablet Product: okular Version: 1.5.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: keziolio...@gmail.com Target Milestone: --- SUMMARY When scrolling with a wacom tablet, the pages move slower than the input, accumulating up to dozens of seconds of latency, rendering the software unusable STEPS TO REPRODUCE 1. Attach a wacom tablet to the pc 2. Open a pdf document in okular 3. Scroll the document with the wacom tablet and notice the sluggishness OBSERVED RESULT I made a video https://youtu.be/BJEZYtXhhMI EXPECTED RESULT It should move the page without latency, I can mind low framerate since i'm with a 4k screen on intel graphics but this is bad IMPORTANT: It was working fine at the beginning of this year! So the regression is somewhat recent I tried with a new user and on another pc and the problem is confirmed SOFTWARE VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 I'm using arch linux so it has always been recent and close to upstream ADDITIONAL INFORMATION Looking at ksysguard when okular is moving by itself, I see xorg hogging a cpu core at 100%, okular is using 2% of the cpu, so is kwin_x11 Wayland is not an option on my setup -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394127] New: Plasma hangs when screenshotting yakuake from spectacle
https://bugs.kde.org/show_bug.cgi?id=394127 Bug ID: 394127 Summary: Plasma hangs when screenshotting yakuake from spectacle Product: plasmashell Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: keziolio...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.10.1 Frameworks Version: 5.45.0 Operating System: Linux 4.16.8-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Making a screenshot of yakuake with spectacle in the "active window" mode, including title bar and borders It crashes every time journalctl says this: May 11 15:26:32 desktop kwin_x11[660]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 9368, resource id: 54525956, major code: 18 (ChangeProperty), minor code: 0 May 11 15:26:33 desktop kcminit[1044]: Initializing "kcm_input" : "kcminit_mouse" May 11 15:26:33 desktop kcminit[1044]: kcm_input: Using X11 backend May 11 15:26:33 desktop kwin_x11[660]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10342, resource id: 52428804, major code: 18 (ChangeProperty), minor code: 0 May 11 15:26:33 desktop kcminit[1055]: Initializing "kcm_input" : "kcminit_mouse" May 11 15:26:33 desktop kcminit[1055]: kcm_input: Using X11 backend May 11 15:26:33 desktop kwin_x11[660]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10903, resource id: 54525956, major code: 18 (ChangeProperty), minor code: 0 May 11 15:26:33 desktop kcminit[1063]: Initializing "kcm_input" : "kcminit_mouse" May 11 15:26:33 desktop kcminit[1063]: kcm_input: Using X11 backend May 11 15:26:33 desktop kwin_x11[660]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11100, resource id: 56623108, major code: 18 (ChangeProperty), minor code: 0 May 11 15:26:39 desktop spectacle[976]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 3485, resource id: 31457937, major code: 14 (GetGeometry), minor code: 0 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdfd8ab7800 (LWP 667))] Thread 17 (Thread 0x7fded29f5700 (LWP 886)): #0 0x7fdfcc8ce2d9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7fdfcc886a55 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7fdfcc88744e in () at /usr/lib/libglib-2.0.so.0 #3 0x7fdfcc88763e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fdfd295c254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fdfd28fe31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fdfd270d71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fded95a32ea in KCupsConnection::run() () at /usr/lib/libkcupslib.so #8 0x7fdfd2712abd in () at /usr/lib/libQt5Core.so.5 #9 0x7fdfd18c5075 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fdfd201653f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fdedad04700 (LWP 885)): #0 0x7fdfd200bea9 in poll () at /usr/lib/libc.so.6 #1 0x7fdfcc887523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fdfcc88763e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fdfd295c254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fdfd28fe31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fdfd270d71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fdfd2712abd in () at /usr/lib/libQt5Core.so.5 #7 0x7fdfd18c5075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fdfd201653f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fdef1590700 (LWP 869)): #0 0x7fdfd18caffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdf281b5964 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fdf281b5658 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fdfd18c5075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fdfd201653f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fdf1a7fc700 (LWP 868)): #0 0x7fdfd18caffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdf281b5964 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fdf281b5658 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fdfd18c5075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fdfd201653f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fdf1affd700 (LWP 866)): #0 0x7fdfcc8ce2d9 in g_mutex_lock ()
[plasmashell] [Bug 393479] New: Crash when opening an application from the launcher
https://bugs.kde.org/show_bug.cgi?id=393479 Bug ID: 393479 Summary: Crash when opening an application from the launcher Product: plasmashell Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: keziolio...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.4) Qt Version: 5.10.1 Frameworks Version: 5.45.0 Operating System: Linux 4.16.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: opening falkon from the application dashboard with a wayland touchscreen device The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0c6ed9b800 (LWP 721))] Thread 15 (Thread 0x7f0b86c5c700 (LWP 2564)): #0 0x7f0c67b843bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0c689c5fac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0c6c7ba5fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7f0c6c7baa84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f0c689c4acd in () at /usr/lib/libQt5Core.so.5 #5 0x7f0c67b7e08c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f0c682cce7f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f0b8627a700 (LWP 2408)): #0 0x7f0c67b843bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0c689c5fac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0c6c7ba5fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7f0c6c7baa84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f0c689c4acd in () at /usr/lib/libQt5Core.so.5 #5 0x7f0c67b7e08c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f0c682cce7f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f0b8760f700 (LWP 995)): #0 0x7f0c67b843bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0c689c5fac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0c6c7ba5fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7f0c6c7baa84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f0c689c4acd in () at /usr/lib/libQt5Core.so.5 #5 0x7f0c67b7e08c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f0c682cce7f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f0ba11de700 (LWP 989)): #0 0x7f0c67b843bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0c689c5fac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0c6c7ba5fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7f0c6c7baa84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f0c689c4acd in () at /usr/lib/libQt5Core.so.5 #5 0x7f0c67b7e08c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f0c682cce7f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f0b9953a700 (LWP 988)): #0 0x7f0c682c297b in poll () at /usr/lib/libc.so.6 #1 0x7f0c62b8a523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f0c62b8a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f0c68c0e264 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f0c68bb032b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f0c689bf72e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f0c6bb92319 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f0c689c4acd in () at /usr/lib/libQt5Core.so.5 #8 0x7f0c67b7e08c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f0c682cce7f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f0b99eab700 (LWP 839)): #0 0x7f0c67b843bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0c689c5fac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0c6c7ba5fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7f0c6c7baa84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f0c689c4acd in () at /usr/lib/libQt5Core.so.5 #5 0x7f0c67b7e08c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f0c682cce7f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f0b9bbda700 (LWP 831)): #0 0x7f0c67b843bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0c689c5fac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0c6c7ba5fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7f0c6c7baa84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f0c689c4acd in () at /usr/lib/libQt5Co
[plasmashell] [Bug 393461] New: Plasma on wayand crashes randomly when opening the application dashboard or apps from it
https://bugs.kde.org/show_bug.cgi?id=393461 Bug ID: 393461 Summary: Plasma on wayand crashes randomly when opening the application dashboard or apps from it Product: plasmashell Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: keziolio...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.4) Qt Version: 5.10.1 Frameworks Version: 5.45.0 Operating System: Linux 4.16.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Opening the applications launcher wayland touchscreen only device it does not crash every time The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fee9d1e6800 (LWP 701))] Thread 13 (Thread 0x7fedcf62f700 (LWP 853)): #0 0x7fee95fce3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fee96e0ffac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fee9ac045fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fee9ac04a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fee96e0eacd in () at /usr/lib/libQt5Core.so.5 #5 0x7fee95fc808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fee96716e7f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fedbf7fe700 (LWP 834)): #0 0x7fee95fce3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fee96e0ffac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fee9ac045fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fee9ac04a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fee96e0eacd in () at /usr/lib/libQt5Core.so.5 #5 0x7fee95fc808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fee96716e7f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fedb700 (LWP 828)): #0 0x7fee95fce3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fee96e0ffac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fee9ac045fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fee9ac04a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fee96e0eacd in () at /usr/lib/libQt5Core.so.5 #5 0x7fee95fc808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fee96716e7f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fedcd4f3700 (LWP 827)): #0 0x7fee967083d8 in read () at /usr/lib/libc.so.6 #1 0x7fee91019ed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fee90fd3ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fee90fd44c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fee90fd463e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fee97058264 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fee96ffa32b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fee96e0972e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fee99fdc319 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fee96e0eacd in () at /usr/lib/libQt5Core.so.5 #10 0x7fee95fc808c in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fee96716e7f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fedcdee1700 (LWP 826)): #0 0x7fee95fce3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fee96e0ffac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fee9ac045fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fee9ac04a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fee96e0eacd in () at /usr/lib/libQt5Core.so.5 #5 0x7fee95fc808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fee96716e7f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fedcee26700 (LWP 810)): #0 0x7fee95fce3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fee96e0ffac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fee9ac045fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fee9ac04a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fee96e0eacd in () at /usr/lib/libQt5Core.so.5 #5 0x7fee95fc808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fee96716e7f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fedea73c700 (LWP 797)): #0 0x7fee95fce3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fee96e0ffac in QWaitCondition::wait(QMutex*, unsigned long) () a
[okular] [Bug 379815] New: random crash when changing system audio volume with media keys
https://bugs.kde.org/show_bug.cgi?id=379815 Bug ID: 379815 Summary: random crash when changing system audio volume with media keys Product: okular Version: 1.1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: keziolio...@gmail.com Target Milestone: --- Okular crashed randomly when increasing the volume with the keyboard media keys, I was not able to reproduce Arch linux with kde-unstable, okular 1.1.1, everything is up to date mag 14 16:24:05 desktop systemd-coredump[9116]: Process 15413 (okular) of user 1000 dumped core. Stack trace of thread 15413: #0 0x7f879a206a10 raise (libc.so.6) #1 0x7f879a20813a abort (libc.so.6) #2 0x7f87856a7212 pa_fdsem_post (libpulsecommon-10.0.so) #3 0x7f87856bf2ea pa_srbchannel_write (libpulsecommon-10.0.so) #4 0x7f87856bd4fd n/a (libpulsecommon-10.0.so) #5 0x7f87856be668 n/a (libpulsecommon-10.0.so) #6 0x7f87856be989 n/a (libpulsecommon-10.0.so) #7 0x7f87856bf20a n/a (libpulsecommon-10.0.so) #8 0x7f8785b07f36 n/a (libpulse-mainloop-glib.so.0) #9 0x7f87950097b7 g_main_context_dispatch (libglib-2.0.so.0) #10 0x7f8795009a20 n/a (libglib-2.0.so.0) #11 0x7f8795009acc g_main_context_iteration (libglib-2.0.so.0) #12 0x7f879abdc07f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #13 0x7f879ab858ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #14 0x7f879ab8de14 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #15 0x0040b97d n/a (okular) #16 0x7f879a1f3511 __libc_start_main (libc.so.6) #17 0x0040d24a _start (okular) Stack trace of thread 15415: #0 0x7f879a2b567d poll (libc.so.6) #1 0x7f87950099b6 n/a (libglib-2.0.so.0) #2 0x7f8795009acc g_main_context_iteration (libglib-2.0.so.0) #3 0x7f879abdc07f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x7f879ab858ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x7f879a9a7a73 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x7f879aff1125 n/a (libQt5DBus.so.5) #7 0x7f879a9ac6d8 n/a (libQt5Core.so.5) #8 0x7f8796f512e7 start_thread (libpthread.so.0) #9 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15418: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15414: #0 0x7f879a2b567d poll (libc.so.6) #1 0x7f8797d048e0 n/a (libxcb.so.1) #2 0x7f8797d06679 xcb_wait_for_event (libxcb.so.1) #3 0x7f878f642239 n/a (libQt5XcbQpa.so.5) #4 0x7f879a9ac6d8 n/a (libQt5Core.so.5) #5 0x7f8796f512e7 start_thread (libpthread.so.0) #6 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15416: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15419: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15417: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15420: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378174] It crashed just after I started the pc
https://bugs.kde.org/show_bug.cgi?id=378174 Keziolio changed: What|Removed |Added Resolution|BACKTRACE |INVALID Status|NEEDSINFO |RESOLVED --- Comment #2 from Keziolio --- I can't reproduce this crash any more, so I think this can be closed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379044] New: Crash when pressing the "add widget" button on the panel
https://bugs.kde.org/show_bug.cgi?id=379044 Bug ID: 379044 Summary: Crash when pressing the "add widget" button on the panel Product: plasmashell Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: keziolio...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.10-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: It sometimes crashes also when pressing the bottom-right hamburger icon for opening the settings. Last time I reported with drconqi (or how it's named) I was answered that the backtrace was not useful, because of missing debug symbols, but now the GUI is saying "the report is useful" so here it is The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7bd8b57800 (LWP 524))] Thread 31 (Thread 0x7f7ab1ffb700 (LWP 13574)): #0 0x7f7bcd024e64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f7bccfdefb9 in g_main_context_query () at /usr/lib/libglib-2.0.so.0 #2 0x7f7bccfdf718 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f7bccfdf8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f7bd2b2106b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f7bd2aca89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f7bd28eca73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f7bd5a25025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f7bd28f16d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f7bd17a62e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f7bd220454f in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f7ab27fc700 (LWP 1636)): #0 0x7f7bd17ac756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7bd28f258b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7b10e211d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7b10e259d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7b10e20263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7b10e25a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7b10e20263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7b10e25a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7b10e20263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f7b10e25a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f7b10e20263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f7b10e25a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f7b10e20263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f7b10e23249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f7bd28f16d8 in () at /usr/lib/libQt5Core.so.5 #15 0x7f7bd17a62e7 in start_thread () at /usr/lib/libpthread.so.0 #16 0x7f7bd220454f in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f7ab2ffd700 (LWP 1635)): #0 0x7f7bd17ac756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7bd28f258b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7b10e211d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7b10e259d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7b10e20263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7b10e25a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7b10e20263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7b10e25a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7b10e20263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f7b10e25a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f7b10e20263 in ThreadWeaver::Weaver::applyForWork(ThreadWe
[kwin] [Bug 378114] After trying kde with wayland, compositor on xorg is broken with opengl, have to use xrender to see the effects
https://bugs.kde.org/show_bug.cgi?id=378114 --- Comment #4 from Keziolio --- Removing that line fixed the issue, opengl now works on xorg, I don't know if I changed compositor settings: I tried now to go xorg -> wayland -> xorg without touching anything and the problem did not occur. Tried to change from opengl 3.1 to 2.0 on wayland and it crashed on me with a black screen, so I don't really know what happened By the way, I don't see an option to change egl related stuff on the panel (i'm not sure if there was such a thing in te past?) but I have not touched anything that wasn't on the gui. That line appeared on its own. Thanks for the support -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378114] After trying kde with wayland, compositor on xorg is broken with opengl, have to use xrender to see the effects
https://bugs.kde.org/show_bug.cgi?id=378114 --- Comment #2 from Keziolio --- Created attachment 104848 --> https://bugs.kde.org/attachment.cgi?id=104848&action=edit kwinrc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378174] New: It crashed just after I started the pc
https://bugs.kde.org/show_bug.cgi?id=378174 Bug ID: 378174 Summary: It crashed just after I started the pc Product: kwin Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: keziolio...@gmail.com Target Milestone: --- Application: kwin_x11 (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.5-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: It crashed just after I started the computer, sddm auto login, recovered itself, it's the second time something like this happens recently The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9effb2c840 (LWP 1995))] Thread 11 (Thread 0x7f9ed37fe700 (LWP 3354)): #0 0x003f8220d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x003fb1789234 in () at /usr/lib/libQt5Script.so.5 #2 0x003fb1789279 in () at /usr/lib/libQt5Script.so.5 #3 0x003f822072e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x003f81aec54f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f9ee0a21700 (LWP 3084)): #0 0x003f8220d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ee363d68b in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ee363d3b7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x003f822072e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x003f81aec54f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f9ee1222700 (LWP 3083)): #0 0x003f8220d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ee363d68b in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ee363d3b7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x003f822072e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x003f81aec54f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f9ee1a23700 (LWP 3082)): #0 0x003f8220d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ee363d68b in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ee363d3b7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x003f822072e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x003f81aec54f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f9ee2224700 (LWP 3081)): #0 0x003f8220d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ee363d68b in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ee363d3b7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x003f822072e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x003f81aec54f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f9ee2c2a700 (LWP 3080)): #0 0x003f8220d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ee363d68b in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ee363d3b7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x003f822072e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x003f81aec54f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f9ef5170700 (LWP 3078)): [KCrash Handler] #6 0x003f901b7d70 in QLockFile::isLocked() const () at /usr/lib/libQt5Core.so.5 #7 0x003429c39fb2 in () at /usr/lib/libKF5ConfigCore.so.5 #8 0x003429c1dbe8 in KConfig::sync() () at /usr/lib/libKF5ConfigCore.so.5 #9 0x7f9efc2b93c4 in () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #10 0x003f902b40be in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #11 0x003f902c0d98 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x003f902b4b63 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7f9f06bd634c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f9f06bddb61 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x003f90288440 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x003f902dbcbe in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #17 0x003f902d9bda in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x003f9028689a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x003f900a8a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #20 0x003f900ad6d8 in () at /usr/lib/libQt5Core.so.5 #21 0x003f822072e7 in start_thread () at /usr/lib/libpthread.so.0 #22 0x003f81aec54
[kwin] [Bug 378114] New: After trying kde with wayland, compositor on xorg is broken with opengl, have to use xrender to see the effects
https://bugs.kde.org/show_bug.cgi?id=378114 Bug ID: 378114 Summary: After trying kde with wayland, compositor on xorg is broken with opengl, have to use xrender to see the effects Product: kwin Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: keziolio...@gmail.com Target Milestone: --- On an intel laptop with mesa drivers. Only xrender shows the effects (blur around windows, transparency, animations, etc) With opengl, both 2.0 and 3.1, it doesn't, used to work before i tried to open wayland, it's broken in xorg now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361342] Yet another broken panel strut
https://bugs.kde.org/show_bug.cgi?id=361342 Keziolio changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361343] Application launcher not positioned correctly with a portrait monitor in a multi monitor configuration
https://bugs.kde.org/show_bug.cgi?id=361343 Keziolio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Keziolio --- This bug seems related to this: https://bugs.kde.org/show_bug.cgi?id=361342 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 361345] Yakuake not working in plasma 5 with a portrait monitor
https://bugs.kde.org/show_bug.cgi?id=361345 --- Comment #2 from Keziolio --- Yes it fixes it, in fact, I reported one of the bugs you linked So i think this bug report can be closed. I hope it will be fixed soon. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361342] Problem in dragging windows with a portrait monitor
https://bugs.kde.org/show_bug.cgi?id=361342 --- Comment #5 from Keziolio --- It's related to this bug i reported too https://bugs.kde.org/show_bug.cgi?id=361345 If i keep the panel on "windows can cover" everything is fixed, the app launcher and yakuake, if i put it back to "always visible" it breaks again -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361342] Problem in dragging windows with a portrait monitor
https://bugs.kde.org/show_bug.cgi?id=361342 --- Comment #4 from Keziolio --- Here's the output of xprop https://gist.github.com/Keziolio/b1a7ae8256ea3534fd6ff36d23303639 Changing the panel fixes the problem, and fixes also this bug i reported https://bugs.kde.org/show_bug.cgi?id=361343 that seems related Here's a diff of the xprop output before and after changing the panel (so from the broken to the working setup) $ diff withproblem.txt noproblem.txt 1,2c1,2 < _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 3455 < _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 3455, 0, 0, 0, 0, 0, 0, 1920, 3839 --- > _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 0 > _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 9c9 < _NET_WM_USER_TIME(CARDINAL) = 6820922 --- > _NET_WM_USER_TIME(CARDINAL) = 6884682 355c355 < user specified size: 368 by 35 --- > user specified size: 418 by 35 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361342] Problem in dragging windows with a portrait monitor
https://bugs.kde.org/show_bug.cgi?id=361342 --- Comment #2 from Keziolio --- Here's the output https://gist.github.com/Keziolio/080cfdc222e724ceaa613291a4aa638c Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361297] Plasma desktop unusable with a portrait monitor, several glitches
https://bugs.kde.org/show_bug.cgi?id=361297 Keziolio changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Keziolio --- I opened other bug reports for all the individual problems listed here, this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 361345] New: Yakuake not working in plasma 5 with a portrait monitor
https://bugs.kde.org/show_bug.cgi?id=361345 Bug ID: 361345 Summary: Yakuake not working in plasma 5 with a portrait monitor Product: yakuake Version: 3.0.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: h...@kde.org Reporter: keziolio...@gmail.com I have 3 fullhd monitors, when I rotated the right one in portrait mode, yakuake stopped working, if I click the key I bound to it nothing happens. The process is still there but it gives no signs of life. If, on a terminal, i kill the yakuake process and start it again, it works just fine, but if i start the system with it it doesn't. In gnome it works as usual, this problem is present with plasma desktop. It was working just fine with all the monitors in landscape. Reproducible: Always Steps to Reproduce: 1. Rotate a monitor in portrait 2. Restart and try to open yakuake Actual Results: Nothing happens Expected Results: It should work without the need to killing it and restarting it every time -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361343] New: Application launcher not positioned correctly with a portrait monitor in a multi monitor configuration
https://bugs.kde.org/show_bug.cgi?id=361343 Bug ID: 361343 Summary: Application launcher not positioned correctly with a portrait monitor in a multi monitor configuration Product: plasmashell Version: 5.6.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: keziolio...@gmail.com CC: plasma-b...@kde.org I have 3 monitors with one of them (the right one) set in portrait (vertical) position The application launcher is not positioned correctly, it's too high, look at the video to see exactly what's happening Video: https://www.youtube.com/watch?v=WpbPixYt19k I found a temporary fix, just changing an option on the screen settings and applying. The fix doesn't last after a reboot/logout. Video of the fix: https://www.youtube.com/watch?v=auSDQTyYMQo (just for clarity) None of those problems were present when i had all my monitors in landscape. Reproducible: Always Steps to Reproduce: 1. Rotate a monitor in the settings 2. Restart the computer or log out Actual Results: The application launcher menu is not vertically aligned with the panel at the bottom of the screen, the menu appears several hundred of pixels too high Expected Results: The menu should appear just above the panel -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361342] New: Problem in dragging windows with a portrait monitor
https://bugs.kde.org/show_bug.cgi?id=361342 Bug ID: 361342 Summary: Problem in dragging windows with a portrait monitor Product: kwin Version: 5.6.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: multihead Assignee: kwin-bugs-n...@kde.org Reporter: keziolio...@gmail.com I have 3 monitors with one of them set in portrait (vertical) position It's impossible to drag windows correctly, they hang at some point and resize/teleport randomly, making the desktop unusable Video: https://www.youtube.com/watch?v=WpbPixYt19k I found a temporary fix, just changing an option on the screen settings and applying. The fix doesn't last after a reboot. Video of the fix: https://www.youtube.com/watch?v=auSDQTyYMQo (just for clarity) The problem is always reproducible on my setup. None of those problems were present when i had all my monitors in landscape. Reproducible: Always Steps to Reproduce: 1. Rotate a monitor in the settings 2. Restart the computer Arch linux, everything up to date, nvidia gpu with latest stable drivers (361.28) Primary screen is the center one -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361297] New: Plasma desktop unusable with a portrait monitor, several glitches
https://bugs.kde.org/show_bug.cgi?id=361297
Bug ID: 361297
Summary: Plasma desktop unusable with a portrait monitor,
several glitches
Product: plasmashell
Version: 5.6.1
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: Multi-screen support
Assignee: aleix...@kde.org
Reporter: keziolio...@gmail.com
CC: plasma-b...@kde.org
I encountered all those glitches while putting one of my monitors in portrait
(vertical) position, none of this was seen before with 3 landscape monitors
The problems are: (see the video for better understanding)
- The application launcher ("start menu") is not positioned correctly
- It's impossible to drag windows correctly, they hang at some point and
resize/teleport randomly, making the desktop unusable
- Yakuake doesn't work
- I noticed also issues with the background in the vertical monitor (background
being in landscape mode leaving a black space) but i couldn't reproduce after
updating to 5.6.1 so *maybe* it's fixed
- I noticed also issues with the cursor size, it was changing its size
randomly, i later forced it to the small size, the change took effect after
restarting
Another guy on irc had similar problems with a portrait monitor
Video: https://www.youtube.com/watch?v=WpbPixYt19k
I found a temporary fix, just changing an option on the screen settings and
applying. But yakuake still doesn't work after. And it breaks again after
logout/restart.
Video of the fix: https://www.youtube.com/watch?v=auSDQTyYMQo
The problem is always reproducible here
--
You are receiving this mail because:
You are watching all bug changes.
