[Discover] [Bug 454391] Discover package list title has no top padding
https://bugs.kde.org/show_bug.cgi?id=454391 Mateus changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Mateus --- (In reply to Nate Graham from comment #1) > What font and font size are you using? Cannot reproduce with both Noto Sans > 10 (the default) or Noto Sans 11 with Discover in either mobile or > 3-column/widescreen view. I'm using the default font as well (Noto Sans 10). Changing the font size to something else fixes the issue; it seems to be only 10pt that's causing the glitch. I also tried changing the scaling factor back to 100% (from 125%) but the problem still persists. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 454391] Discover package list title has no top padding
https://bugs.kde.org/show_bug.cgi?id=454391 --- Comment #3 from Mateus --- Created attachment 149217 --> https://bugs.kde.org/attachment.cgi?id=149217&action=edit Packages list in Noto Sans 5pt I now changed the font size to something very small (5pt) and it gets even weirder. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 454391] Discover package list title has no top padding
https://bugs.kde.org/show_bug.cgi?id=454391 --- Comment #6 from Mateus --- (In reply to guimarcalsilva from comment #4) > (In reply to Nate Graham from comment #1) > > What font and font size are you using? Cannot reproduce with both Noto Sans > > 10 (the default) or Noto Sans 11 with Discover in either mobile or > > 3-column/widescreen view. > > I can confirm this bug happens. > > It's easy to reproduce it if you resize the window on the Home page so it > switches to the mobile layout, but it doesn't happen if Discover already > opens in the mobile mode. Make sure to open Discover with a large window, > then resize it horizontally until it switches its layout, then you'll see > the bug. If you click on the search button at the bottom and back to the > home button, the bug disappears and does not happen again until restarting > Discover. > > I'm using Plasma on Wayland with a 1920x1080 screen at 100% scale and the > default Nono Sans 10pt. Can confirm that opening Discover, shrinking to mobile size, pressing search then home and resizing so it becomes desktop-sized again "fixes" the problem until Discover is restarted. Should have mentioned in the original report that I'm using a 27" 4K monitor. Maybe it has something to do with the way it draws elements in desktop mode compared to mobile. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454246] New: Reverse four-finger gestures to exit overview and desktop grid
https://bugs.kde.org/show_bug.cgi?id=454246 Bug ID: 454246 Summary: Reverse four-finger gestures to exit overview and desktop grid Product: kwin Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: mateusbmelchia...@gmail.com Target Milestone: --- Created attachment 149124 --> https://bugs.kde.org/attachment.cgi?id=149124&action=edit Visual representation of when a user might want to exit overview by swiping up SUMMARY The new 1:1 gestures in 5.25 beta are intuitive when launching overview and desktop grid, but they do not follow expected behaviour to exit these effects. For example, one would expect a four-finger swipe up when inside overview to exit the effect, as well as a four-finger swipe down from desktop grid to return to the desktop. STEPS TO REPRODUCE 1. Open overview with four-finger swipe down 2. Try to exit the effect by four-finger swipe the opposite direction 3. Have desktop grid appear instead SOFTWARE/OS VERSIONS KDE Plasma: 5.24.90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454126] Floating panel shadow appears wrong
https://bugs.kde.org/show_bug.cgi?id=454126 Mateus changed: What|Removed |Added CC||mateusbmelchia...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454246] While in Present Windows effect, four-finger swipe up does not close it, and instead opens Desktop Grid effect
https://bugs.kde.org/show_bug.cgi?id=454246 --- Comment #2 from Mateus --- (In reply to Nate Graham from comment #1) > Can confirm. Interestingly it works in the Desktop grid effect; swiping down > with four fingers returns you to where yo were before, instead of opening > the Present Windows effect. Could be my work laptop’s terrible trackpad, but for me returning from Desktop grid is glitchy and eventually opens overview if I keep swiping down -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 454391] New: Discover package list title has no top padding
https://bugs.kde.org/show_bug.cgi?id=454391 Bug ID: 454391 Summary: Discover package list title has no top padding Product: Discover Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: mateusbmelchia...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 149205 --> https://bugs.kde.org/attachment.cgi?id=149205&action=edit Package titles in the middle column have no top padding SUMMARY When in three column mode (categories, package list, package info), the title of the packages in the list don't have any top padding, which makes it inconsistent with the rest of the UI. STEPS TO REPRODUCE 1. Open discover 2. Select a package 3. Package titles in the middle column will have no padding SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Kionite 36 KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426464] Transparent Plasma themes are missing transparency in Wayland session with proprietary NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=426464 --- Comment #14 from Mateus --- (In reply to Alessandro Astone from comment #13) > This happens on any Xwayland window with transparency. The plasma panel and > kickoff must be using Xwayland by default. This does indeed make sense. I remember seeing some errors related to Xwayland on journalctl. I'll see if I can find them again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426464] Transparent Plasma themes are missing transparency in Wayland session with proprietary NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=426464 --- Comment #15 from Mateus --- > The plasma panel and kickoff must be using Xwayland by default. Launched a Wayland session and I can confirm this is not the case. `xwininfo` cannot select any plasma panel and `xlsclients` lists firefox only. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426464] Transparent Plasma themes are missing transparency in Wayland session with proprietary NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=426464 --- Comment #16 from Mateus --- Only relevant info I could find inside journalctl is that this set of messages appear every time I try to open a plasma panel: Sep 05 19:51:21 mainpc plasmashell[576]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Sep 05 19:51:21 mainpc plasmashell[576]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x5603e60dfa30, name="popupWindow") Sep 05 19:51:21 mainpc plasmashell[576]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x5603e60dfa30, name="popupWindow") Sep 05 19:51:21 mainpc plasmashell[576]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x5603e60dfa30, name="popupWindow") Sep 05 19:51:26 mainpc plasmashell[576]: kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/applications.so" "Failed to extract plugin meta data from '/usr/lib/qt/plugins/kf5/kio/applications.so'" Sep 05 19:51:26 mainpc plasmashell[576]: kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/desktop.so" "Failed to extract plugin meta data from '/usr/lib/qt/plugins/kf5/kio/desktop.so'" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442529] New: Changing settings in Wayland causes black screen
https://bugs.kde.org/show_bug.cgi?id=442529 Bug ID: 442529 Summary: Changing settings in Wayland causes black screen Product: kwin Version: 5.22.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mateusbmelchia...@gmail.com Target Milestone: --- Created attachment 141600 --> https://bugs.kde.org/attachment.cgi?id=141600&action=edit Image showing observed result SUMMARY Changing settings in System Settings when using Wayland causes screen to go black, requiring a reboot. STEPS TO REPRODUCE 1. Open System Settings in a Wayland session 2. Change any setting under Compositor (I tested with Latency) OBSERVED RESULT See attached image SOFTWARE/OS VERSIONS Linux kernel: 5.14.3-arch1-1 NVidia Driver version: 470.63.01 KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442543] New: "Unable to assign [undefined] to bool" warnings all over journalctl
https://bugs.kde.org/show_bug.cgi?id=442543 Bug ID: 442543 Summary: "Unable to assign [undefined] to bool" warnings all over journalctl Product: plasmashell Version: 5.22.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mateusbmelchia...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Ever since updating to plasma 5.22.90 my journalctl log has been filled with the same warning: file:///usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/ui/main.qml:112:17: Unable to assign [undefined] to bool This seems to be a type issue with Plasma Workspace although I'm not sure whether it is causing any issue or not. I am currently running Arch Linux with kernel 5.14.5-arch1-1 and Nvidia drivers 470.63.01. STEPS TO REPRODUCE 1. Lanuch plasma after updating to 5.22.90 2. Open journalctl 3. Be flooded SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.22.90 KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426464] Transparent Plasma themes are missing transparency in Wayland session with proprietary NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=426464 Mateus changed: What|Removed |Added CC||mateusbmelchia...@gmail.com --- Comment #9 from Mateus --- Can confirm the issue on a fresh Arch Install running Plasma 5.22 with Nvidia 465.31-8. X11 also works just fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426464] Transparent Plasma themes are missing transparency in Wayland session with proprietary NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=426464 --- Comment #10 from Mateus --- After poking around for a while I think the problem is in the plasma shell and not kwin. The task switcher and window translucency effects work as expected, so it should be something related to the panels themselves. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454654] New: When using accent colors in window titlebar from a dark wallpaper, some text elements are hard to see
https://bugs.kde.org/show_bug.cgi?id=454654 Bug ID: 454654 Summary: When using accent colors in window titlebar from a dark wallpaper, some text elements are hard to see Product: systemsettings Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: mateusbmelchia...@gmail.com CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- Created attachment 149355 --> https://bugs.kde.org/attachment.cgi?id=149355&action=edit Example of poorly visible text SUMMARY When I choose to use accent color from my wallpaper, the resulting color is a dark shade of gray (#54636b) which causes most text elements in application headers to become white. However, some elements like the "Install" button in discover or the menu bar in Kate still use a dark font, which makes them hard to see. STEPS TO REPRODUCE 1. Set accent color to a dark color 2. Tint application headers with accent color 3. Observe difference in font color between elements Linux/KDE Plasma: Fedora Kionite 36 KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Google authentication process gets stuck due to excessively old version of signon-ui library
https://bugs.kde.org/show_bug.cgi?id=420280 Mateus Honorato changed: What|Removed |Added CC||mateush.honor...@gmail.com --- Comment #105 from Mateus Honorato --- I'm still dealing with this bug on Arch Linux, even tho the signon-ui package version is quite new, 0.17+20231016-2.1. When running systemsettings from the terminal and trying to login to my account, I get this errors on the terminal: file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitHeight" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "value" "google" Looking for plugin "" Starting auth session with "oauth2" Info: Id: 3 caption: "google" owner: "" userName: "" qt.dbus.integration: Could not disconnect "com.google.code.AccountsSSO.SingleSignOn.Identity" to "destroyed(QObject*)" : Pointers are not supported: QObject* Error: "Access grant not present" I'm using Wayland and nvidia drivers. I was able to login once in the Xorg session, but it doesn't always work, and even when I get to login successfully, the google drive integration in Dolphin randomly stops working when accessing folders. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483438] New: Timezones in Digital Clock widget appear selectable when they are not
https://bugs.kde.org/show_bug.cgi?id=483438 Bug ID: 483438 Summary: Timezones in Digital Clock widget appear selectable when they are not Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: mateusbmelchia...@gmail.com Target Milestone: 1.0 Created attachment 167097 --> https://bugs.kde.org/attachment.cgi?id=167097&action=edit Current behavior with multiple timezones in Digital Clock SUMMARY When displaying multiple timezones in the Digital Clock widget, the first timezone in the list appears if it is "selected" but clicking it (or any other timezone) does nothing. Similarly, the user can also use the arrow keys to navigate the timezone list but selecting any of them with Enter also doesn't result in anything. I think the ideal solution would be to either make the timezones not selectable or make it so selecting them opens KClock (maybe that's already the case and it's not working because I'm using the Flatpak?) STEPS TO REPRODUCE 1. Configure Digital Clock to show multiple timezones 2. Open the widget 3. Observe timezones OBSERVED RESULT Timezones are a selectable list but selecting them doesn't do anything. EXPECTED RESULT Either timezones should not be selectable or selecting them should result in some action (like opening KClock or displaying some message if it is not installed). Still, having the first timezone in the list as "selected" by default can cause confusion as it doesn't mean that it is the currently displayed timezone. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Kinoite 40 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 439916] New: Latte crashes whenever there is a widget reloading
https://bugs.kde.org/show_bug.cgi?id=439916 Bug ID: 439916 Summary: Latte crashes whenever there is a widget reloading Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mateush.honor...@gmail.com Target Milestone: --- Application: latte-dock (0.9.12) Qt Version: 5.15.3 Frameworks Version: 5.84.0 Operating System: Linux 5.8.0-59-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.3 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: I was connecting with a bluetooth device from the system tray added on a Latte panel, and the entire Latte application crashed. - Unusual behavior I noticed: This also happens while interacing with some other widgets sometimes, whenever something is loading. - Additional Information: I have the plasma-systray-latte-tweaks added, but I've already tried to remove it and the problem persists. The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 4034] [New LWP 4036] [New LWP 4037] [New LWP 4038] [New LWP 4039] [New LWP 4040] [New LWP 4047] [New LWP 5071] [New LWP 5072] [New LWP 5074] [New LWP 5075] [New LWP 5076] [New LWP 5078] [New LWP 5095] [New LWP 5118] [New LWP 5119] [New LWP 5122] [New LWP 5167] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x5572938d5bf0) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7fb63c5f9980 (LWP 4033))] Thread 19 (Thread 0x7fb5c976b700 (LWP 5167)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55728e0946d4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55728e094680, cond=0x55728e0946a8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55728e0946a8, mutex=0x55728e094680) at pthread_cond_wait.c:647 #3 0x7fb6409d8f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb64283cb44 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fb64283cfb9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fb6409d2dbc in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb63f87c609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb640504293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fb5ca242700 (LWP 5122)): #0 __GI___libc_read (nbytes=16, buf=0x7fb5ca241a10, fd=57) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=57, buf=0x7fb5ca241a10, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fb63ebc2b2f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb63eb79ebe in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb63eb7a312 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb63eb7a4a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb640c13fcb in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb640bb825b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb6409d1c22 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb6409d2dbc in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb63f87c609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fb640504293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fb5eccba700 (LWP 5119)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55729b8473f0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55729b8473a0, cond=0x55729b8473c8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55729b8473c8, mutex=0x55729b8473a0) at pthread_cond_wait.c:647 #3 0x7fb6409d8f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb64283cb44 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fb64283cfb9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fb6409d2dbc in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb63f87c609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb640504293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fb5ee702700 (LWP 5118)): #0 __GI___libc_read (nbytes=16, buf=0x7fb5ee7019f0, fd=53) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=53, buf=0x7fb5ee7019f0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fb63ebc2b2f in () at /l
[systemsettings] [Bug 423571] Desktop Behaviour - Animation speed
https://bugs.kde.org/show_bug.cgi?id=423571 Mateus Mercer changed: What|Removed |Added CC||accou...@matbm.net --- Comment #16 from Mateus Mercer --- Today my ~/.config/kwinrc file had the 0.5 animation speed written to it. One thing that I did differently from other users is that I stopped the plasma desktop with logout to restart it. Maybe for some reason this was the root cause. I had to delete the 0.5 animation speed line from my ~/.config/kwinrc file to make it back to normal. My system: KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 QT Version: 5.15.2 kwin Version: 5.21.3 distro: Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433664] Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)
https://bugs.kde.org/show_bug.cgi?id=433664 Mateus Honorato changed: What|Removed |Added Version|5.21.1 |5.21.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433664] Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)
https://bugs.kde.org/show_bug.cgi?id=433664 --- Comment #2 from Mateus Honorato --- still present today. just found out this might have something to do with my dual display setup. when the problem happens, if I go to the display settings, disable and enable one of the displays, things come back to normal -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 477634] New: Application title goes outside its card
https://bugs.kde.org/show_bug.cgi?id=477634 Bug ID: 477634 Summary: Application title goes outside its card Classification: Applications Product: Discover Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: mateusbmelchia...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 163551 --> https://bugs.kde.org/attachment.cgi?id=163551&action=edit Visual bug demonstration. SuperTuxKart's title goes slightly off its card SUMMARY Some application titles in Discover's Home page go outside the bounds of the application "card". From what I can see, this only happens if the application name has a large name with no spaces. STEPS TO REPRODUCE 1. Open Discover 2. Observe SuperTuxKart in Highest-Rated Games SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kde Neon Unstable KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 477634] Application title goes outside its card
https://bugs.kde.org/show_bug.cgi?id=477634 --- Comment #1 from Mateus Melchiades --- After some further experimentation I realized that this issue only happens on a very specific window size (which happened to be the default size for my screen). The best approach to reproduce the issue is to slowly reduce Discover's width. The issue happens just before the UI switches to 3 cards per column. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 430956] New: Latte Dock crashes on startup
https://bugs.kde.org/show_bug.cgi?id=430956 Bug ID: 430956 Summary: Latte Dock crashes on startup Product: lattedock Version: 0.9.11 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: mateush.honor...@gmail.com Target Milestone: --- Created attachment 134386 --> https://bugs.kde.org/attachment.cgi?id=134386&action=edit kcrash genereted info Application: latte-dock (0.9.11) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.4.0-58-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: Nothing, I was just starting the system. Sometimes this is happening when plasma-session is starting. I have Latte added to startup on Autostart Settings, and no panels added in plasmashell itself. - Unusual behavior I noticed: KDE Connect also crashes sometimes on startup. Krunner and Dolphin is unable to search for files. - Custom settings of the application: I have only 5 custom widgets added to a panel with Latte: Window Title, Global Menu, System Tray (with Latte Tweaks), Event Calendar and Window App Buttons. The crash can be reproduced sometimes. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 430956] Latte Dock crashes on startup
https://bugs.kde.org/show_bug.cgi?id=430956 --- Comment #1 from Mateus Honorato --- Also, I wasn't able to report the bug using kcrash dialog, because the product is identified there as "latte-dock" but here the name is "lattedock", so it says the project can't be found or I don't have permission to submit a bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433664] New: Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)
https://bugs.kde.org/show_bug.cgi?id=433664 Bug ID: 433664 Summary: Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update) Product: kwin Version: 5.21.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mateush.honor...@gmail.com Target Milestone: --- Created attachment 136197 --> https://bugs.kde.org/attachment.cgi?id=136197&action=edit output of 'qdbus org.kde.KWin /KWin supportInformation' SUMMARY After disabling and enabling the compositor, or restarting kwin with kwin_x11 --replace, the desktop becomes very slow, with like 1-2 fps, and becomes pretty much unusable. The only solution is to logout and login again. This started happening after the Plasma 5.21 update. STEPS TO REPRODUCE 1. Restarting kwin or disabling and enabling the compositor in system settings OBSERVED RESULT Every window or plasmashell itself is stuttering, slow, just the mouse pointer is moving fine with normal framerate, the windows become slow and everything gets really slow. EXPECTED RESULT Normal behavior of the desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.21.1 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Graphics platform: X11 (In the wayland session, everything seems fine) Kernel Version: 5.4.0-66-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3230M CPU @ 2.60GHz Memory: 7,7 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433664] Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)
https://bugs.kde.org/show_bug.cgi?id=433664 --- Comment #1 from Mateus Honorato --- https://drive.google.com/file/d/1m9SAKBYt1kY5zhtoY9i8JMs2rXKigaGB/view?usp=sharing video of the issue -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426412] Kwin laggy after pausing and un-pausing compositing
https://bugs.kde.org/show_bug.cgi?id=426412 Mateus Honorato changed: What|Removed |Added CC||mateush.honor...@gmail.com --- Comment #2 from Mateus Honorato --- This also happens on intel graphics -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409985] Promo video for Latte v0.9
https://bugs.kde.org/show_bug.cgi?id=409985 Mateus Honorato changed: What|Removed |Added CC||mateush.honor...@gmail.com Assignee|mvourla...@gmail.com|mateush.honor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376042] Systemsettings crash when pressing the back button
https://bugs.kde.org/show_bug.cgi?id=376042 Mateus Honorato changed: What|Removed |Added CC||mateush.honor...@gmail.com --- Comment #2 from Mateus Honorato --- I'm having the same bug after update to KDE 5.9.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383098] Plasma crash on audio volume change
https://bugs.kde.org/show_bug.cgi?id=383098 Mateus Honorato changed: What|Removed |Added CC||mateush.honor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383098] Plasma crash on audio volume change
https://bugs.kde.org/show_bug.cgi?id=383098 --- Comment #2 from Mateus Honorato --- Created attachment 107115 --> https://bugs.kde.org/attachment.cgi?id=107115&action=edit New crash information added by DrKonqi plasmashell (5.10.4) using Qt 5.9.1 - What I was doing when the application crashed: just before i changed the audio output from internal speaker to HDMI -- Backtrace (Reduced): #6 QVector::count (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:234 #7 QQmlPropertyCache::property (index=58, this=0x0) at ../../include/QtQml/5.9.1/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:711 #8 QQmlBinding::getPropertyData (this=this@entry=0x5c9a690, propertyData=propertyData@entry=0x7ffc0eb32bc8, valueTypeData=valueTypeData@entry=0x7ffc0eb32bd0) at qml/qqmlbinding.cpp:520 #9 0x7f6220cc9ac2 in GenericBinding<10>::write (this=0x5c9a690, result=..., isUndefined=, flags=...) at qml/qqmlbinding.cpp:246 #10 0x7f6220cca740 in QQmlNonbindingBinding::doUpdate (this=0x5c9a690, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:210 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382770] New: plasmashell crashed when mouse scrolling to increase volume from panel widget
https://bugs.kde.org/show_bug.cgi?id=382770 Bug ID: 382770 Summary: plasmashell crashed when mouse scrolling to increase volume from panel widget Product: plasmashell Version: 5.10.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mateush.honor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.4) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.10.0-27-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: i was with a bluetooth headphone connected, a bluetooth mouse connected too. - Unusual behavior I noticed: plasmashell crashes frequently on my system. also, sometimes, it feels very slow, even when I have noting running - Custom settings of the application: I use a custom icon theme (papirus), and also some custom widgets, like event calendar The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd7241348c0 (LWP 1862))] Thread 19 (Thread 0x7f96135f6700 (LWP 21013)): #0 0x7fd71347b24f in pa_pstream_unref () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #1 0x7fd71347b7a3 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #2 0x7fd71347c01a in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #3 0x7fd7141f60b7 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fd7141f64bc in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fd7141f6560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fd7142047a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7fd71348c078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #8 0x7fd71df276ba in start_thread (arg=0x7f96135f6700) at pthread_create.c:333 #9 0x7fd71e98f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7fd63ccb3700 (LWP 21012)): #0 0x7fd71a360a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd71a31c4a6 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd71f2ab94b in QEventDispatcherGlib::processEvents (this=0x7f961c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7fd71f2547ca in QEventLoop::exec (this=this@entry=0x7fd63ccb2ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #4 0x7fd71f07dcd4 in QThread::exec (this=this@entry=0x6aeb4f0) at thread/qthread.cpp:515 #5 0x7fd72174bfa5 in QQmlThreadPrivate::run (this=0x6aeb4f0) at qml/ftw/qqmlthread.cpp:147 #6 0x7fd71f082989 in QThreadPrivate::start (arg=0x6aeb4f0) at thread/qthread_unix.cpp:368 #7 0x7fd71df276ba in start_thread (arg=0x7fd63ccb3700) at pthread_create.c:333 #8 0x7fd71e98f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7fd63e0b4700 (LWP 21008)): #0 0x7fd71e98370d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd71a31c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd71a31c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd71f2ab94b in QEventDispatcherGlib::processEvents (this=0x7f96180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fd71f2547ca in QEventLoop::exec (this=this@entry=0x7fd63e0b3ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fd71f07dcd4 in QThread::exec (this=this@entry=0x6a57640) at thread/qthread.cpp:515 #6 0x7fd72174bfa5 in QQmlThreadPrivate::run (this=0x6a57640) at qml/ftw/qqmlthread.cpp:147 #7 0x7fd71f082989 in QThreadPrivate::start (arg=0x6a57640) at thread/qthread_unix.cpp:368 #8 0x7fd71df276ba in start_thread (arg=0x7fd63e0b4700) at pthread_create.c:333 #9 0x7fd71e98f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7fd6457fa700 (LWP 8452)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd71f0838eb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x4d2a650) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x502d200, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fd660eef07f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7fd660ef
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 Mateus Mercer changed: What|Removed |Added CC||accou...@matbm.net --- Comment #88 from Mateus Mercer --- TLDR: the easiest way to free the memory and stop for a while the problem: THIS WILL CLOSE ALL NON-KDE APPS, BE CAREFUL `kwin_wayland replace` After that, DONT disconnect the external monitor to avoid the issue, avoid it going to sleep mode too if possible. Force the computer to not sleep. I'm facing this issue too, it starts happening after I disconnect and connect my external monitor. ``` Operating System: Fedora Linux 41 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.8-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 62.5 GiB of RAM Graphics Processor 1: Mesa Intel® UHD Graphics Graphics Processor 2: llvmpipe Manufacturer: Redacted Product Name: Redacted ``` I notice this errors when plugging and unplugging the monitor: ``` Mar 26 22:49:54 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 22:50:00 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 22:56:00 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 22:56:00 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 22:56:00 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 22:56:01 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 22:56:01 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 23:32:32 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 23:32:33 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 27 00:10:56 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT" Mar 27 00:10:56 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 27 00:14:32 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT" Mar 27 00:14:32 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 27 00:17:37 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 27 00:18:32 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT" Mar 27 00:18:32 fedora kwin_wayland[2185]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" ``` Additionally, a bunch of stuff crashes, if the monitor is sleeping and I login back: ``` Mar 26 10:22:20 fedora kernel: usb 3-2.3: device descriptor read/64, error -32 Mar 26 10:22:20 fedora kernel: usb 3-2.3: device descriptor read/64, error -32 Mar 26 10:22:20 fedora kernel: usb 3-2.3: device descriptor read/64, error -32 Mar 26 10:22:20 fedora kernel: usb 3-2.3: device descriptor read/64, error -32 Mar 26 10:22:20 fedora kernel: usb 3-2.3: device not accepting address 13, error -71 Mar 26 10:22:20 fedora kernel: usb 3-2.3: device not accepting address 14, error -71 Mar 26 10:22:20 fedora kernel: usb 3-2-port3: unable to enumerate USB device Mar 26 10:22:14 fedora systemd-modules-load[397]: Failed to find module 'vhba' Mar 26 13:22:22 fedora kernel: Mar 26 13:22:23 fedora bluetoothd[1114]: Failed to set mode: Failed (0x03) Mar 26 13:22:24 fedora systemd-coredump[1479]: Process 545 (plymouthd) of user 0 dumped core. ... Mar 26 15:30:20 fedora kwin_wayland[2173]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 15:51:57 fedora kwin_wayland[2173]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 15:52:03 fedora kwin_wayland[2173]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Mar 26 21:05:56 fedora org_kde_powerdevil[2410]: Attempting to unlock display lock owned by different thread Mar 26 21:05:56 fedora org_kde_powerdevil[2410]: Unexpected er
[kwin] [Bug 496469] Memory leaks and instabilities with different GPUs driving multi-monitor setups when a screen wakes / is added
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #159 from Mateus Mercer --- I was able to ask for NVidia reponse at #kwin:kde.org matrix channel, here's what we got: > regarding that kwin_wayland leak you pinged about, we have a fix that should > be coming in (I think) the next 570 release. I don't know the exact date when > that will drop but will try to ping here again when it does -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities with different GPUs driving multi-monitor setups when a screen wakes / is added
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #157 from Mateus Mercer --- (In reply to Zamundaaa from comment #156) > Sure, it's all in the #kwin matrix room. https://i.imgur.com/1msvYCF.png Yeah, we actually can't see it. So, everyone here is in the dark with a device that memory leaks if you unplug/plug again the external monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities with different GPUs driving multi-monitor setups when a screen wakes / is added
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #158 from Mateus Mercer --- (In reply to Zamundaaa from comment #156) > Sure, it's all in the #kwin matrix room. https://i.imgur.com/1msvYCF.png Yeah, we actually can't see it. So, everyone here is in the dark with a device that memory leaks if you unplug/plug again the external monitor. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 475144] New: No Way to Disable Autoplay
https://bugs.kde.org/show_bug.cgi?id=475144 Bug ID: 475144 Summary: No Way to Disable Autoplay Classification: Applications Product: Haruna Version: 0.12.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: mateusgoncalvesdel...@gmail.com Target Milestone: --- SUMMARY *** I would like for there to be another option inside the Playlist settings tab called "Disable Auto Play". Currently, Haruna keeps on playing the next video in the playlist. I would like to see a function similar to YouTube's playlist. If Auto Play is enabled then just keep playing the next video. If Auto Play is disabled then stop the video at the last frame. To play the next video user has to press the forward button or use a keyboard shortcut. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413214] New: KWin Crashes after computer is suspended
https://bugs.kde.org/show_bug.cgi?id=413214 Bug ID: 413214 Summary: KWin Crashes after computer is suspended Product: kwin Version: 5.12.9 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mateus.naza...@yahoo.com.br Target Milestone: --- Application: kwin_x11 (5.12.9) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Everytime I suspend/lock using the shortcut (CTRL + ALT + L) or automatically after my setted time, it crashes. I've searched for people with related problems, and it seems like an old bug with NVidia cards that didn't resolve. The icons on the tray bar and the titles of icons in the desktop gets glitchy after these steps. Sometimes, I have problem with resizing windows after this. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a9467ecc0 (LWP 2030))] Thread 5 (Thread 0x7f0a61123700 (LWP 3813)): #0 0x7f0a94003cf6 in __GI_ppoll (fds=0x7f0a54001938, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0a91405651 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0a91406d6e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0a913ae9fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0a911cd23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0a8bb556f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f0a911d217d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0a8d0696db in start_thread (arg=0x7f0a61123700) at pthread_create.c:463 #8 0x7f0a9401088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f0a60922700 (LWP 2170)): #0 0x7f0a8d06f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f0a90606fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0a8d06f9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f0a90606f68, cond=0x7f0a90606f90) at pthread_cond_wait.c:502 #2 0x7f0a8d06f9f3 in __pthread_cond_wait (cond=0x7f0a90606f90, mutex=0x7f0a90606f68) at pthread_cond_wait.c:655 #3 0x7f0a903105f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f0a90310639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f0a8d0696db in start_thread (arg=0x7f0a60922700) at pthread_create.c:463 #6 0x7f0a9401088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0a71c9b700 (LWP 2165)): #0 0x7f0a911d3873 in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f0a91407015 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0a913ae9fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0a911cd23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0a8bb556f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7f0a911d217d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0a8d0696db in start_thread (arg=0x7f0a71c9b700) at pthread_create.c:463 #7 0x7f0a9401088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0a73fff700 (LWP 2125)): #0 0x7f0a94003cf6 in __GI_ppoll (fds=0x7f0a6c00ecc8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0a91405651 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0a91406d6e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0a913ae9fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0a911cd23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0a8aa2ed45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f0a911d217d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0a8d0696db in start_thread (arg=0x7f0a73fff700) at pthread_create.c:463 #8 0x7f0a9401088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f0a9467ecc0 (LWP 2030)): [KCrash Handler] #6 0x7f0a90b7d2af in KWin::WindowQuadList::makeInterleavedArrays(unsigned int, KWin::GLVertex2D*, QMatrix4x4 const&) const
[kwin] [Bug 399499] Crash in makeInterleavedArrays
https://bugs.kde.org/show_bug.cgi?id=399499 --- Comment #46 from Mateus N. Coelho --- (In reply to David Edmundson from comment #37) > Can someone who can reproduce this run > > > QT_LOGGING_RULES="kwin_scene_opengl.debug=true;libkwinglutils.debug=true'" > kwin_x11 --replace > > from a terminal trigger a crash and then paste the whole output here please. qt.core.logging: Ignoring malformed logging rule: 'libkwinglutils.debug=true'' Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations. kwin_scene_opengl: Initializing OpenGL compositing OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce MX130/PCIe/SSE2 OpenGL version string: 4.6.0 NVIDIA 430.26 OpenGL shading language version string: 4.60 NVIDIA Driver: NVIDIA Driver version: 430.26 GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 X server version: 1.20.4 Linux kernel version: 5.0 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_scene_opengl: 0x0: OpenGL debug output initialized kwin_scene_opengl: Initializing fences for synchronization with the X command stream kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) will use SYSTEM HEAP memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast). kwin_scene_opengl: OpenGL 2 compositing successfully initialized kf5.kcoreaddons.desktopparser: Property type "Url" is not a known QVariant type. Found while parsing property definition for "X-KWin-Video-Url" in "/usr/share/kservicetypes5/kwineffect.desktop" kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 2 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20084: Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping. kwin_scene_opengl: 0x20092: Program/shader state performance warning: Vertex shader in program 1 is being recompiled based on GL state. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATI
[kdenlive] [Bug 390906] Kdenlive crashes with playback setting "Use GPU processing (Movit library)"
https://bugs.kde.org/show_bug.cgi?id=390906 Mateus Seenem Tavares changed: What|Removed |Added CC||maseta.mat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397108] New: GPU crash when setting the needle
https://bugs.kde.org/show_bug.cgi?id=397108 Bug ID: 397108 Summary: GPU crash when setting the needle Product: kdenlive Version: 18.04.3 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: maseta.mat...@gmail.com Target Milestone: --- Created attachment 114277 --> https://bugs.kde.org/attachment.cgi?id=114277&action=edit kde error didnt sent -- Information about the crash: - What I was doing when the application crashed: Changing the needle position - Unusual behavior I noticed: If I save at every or almost every modification, i can use with speed kdenlive running without primusrun (to run with my dedicated video board (nvidia 950m)) it is pretty stable, but already face almost same thing with videos encoded diferent, so, maybe is the way it handles the files, and with the ones more heavy it will crash sooner than latter, even without gpu - Custom settings of the application: primusrun kdenlive The crash can be reproduced every time. The reporter indicates this bug may be a duplicate of or related to bug 392902. Possible duplicates by query: bug 392902. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397108] GPU crash when setting the needle
https://bugs.kde.org/show_bug.cgi?id=397108 --- Comment #2 from Mateus Seenem Tavares --- hm, gonna tried that, but after disabling gpu aceleration(moovit) it comes back normal. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460408] New: Login screen won't accept password.
https://bugs.kde.org/show_bug.cgi?id=460408 Bug ID: 460408 Summary: Login screen won't accept password. Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: raphael.mateusdne...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Since yesterday, whenever my screen locks itself due to inactivity, i cannot log in anymore. It won't accept the correct password. But if i click on switch user and just log in with the same exact user it works. Those have to work differently somehow since they also have different backgrounds. STEPS TO REPRODUCE 1. Go to toilet and swipe through instagram a bit too long 2. Come back, move mouse and try to type in password OBSERVED RESULT Pretends the password is wrong EXPECTED RESULT Log me in SOFTWARE/OS VERSIONS KDE Neon: KDE Neon User - 5.26 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Only since yesterday (13.10.22) -- You are receiving this mail because: You are watching all bug changes.
