[kwin] [Bug 485730] Severe stuttering with Plasma 6.0.4
https://bugs.kde.org/show_bug.cgi?id=485730 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477016] Brightness flicker with adaptive sync
https://bugs.kde.org/show_bug.cgi?id=477016 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485639] Adaptive Sync has inconsistent refresh in KWin Plasma/6.0 (AMDGPU)
https://bugs.kde.org/show_bug.cgi?id=485639 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme
https://bugs.kde.org/show_bug.cgi?id=484473 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483307] New: Can't hide "Create data project with K3b" context menu
https://bugs.kde.org/show_bug.cgi?id=483307 Bug ID: 483307 Summary: Can't hide "Create data project with K3b" context menu Classification: Applications Product: dolphin Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: leguen.yann...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The context menu "Create data project with K3b" is not hidden when it is unchecked in Dolphin settings. STEPS TO REPRODUCE 1. Uncheck "Create data project with K3b in "Configure Dolphin..." -> "Context Menu". 2. Apply and restart Dolphin. 3. The context menu still appears on a right click. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Dolphin and K3b are both on version 24.02.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474083] Lock/Logout icon size changes when only one action is visible
https://bugs.kde.org/show_bug.cgi?id=474083 --- Comment #9 from Yannick --- Great ! I'm glad I fixed this issue that was irritating me... and happy I could find it pretty quickly and give a first concrete contribution to the KDE Plasma project. I'm aware of the tools that exist for devs work, as my job is project/product owner. The projects or products I own strongly rely on IT projects, like were my studies (computer science). I didn't want to lose time in finding how to do a merge request just for 2 lines of code. Though I know the existence and purpose of tools like Git, I didn't want to take the hassle just for once. Thank you Nate for the time you spent for initiating the merge request and giving me credit (as co-author). It's very nice ! Le jeu., sept. 7, 2023 à 15:42, Nate Graham a écrit: https://bugs.kde.org/show_bug.cgi?id=474083 Nate Graham changed: What |Removed |Added CC| |adam.m.fontenot+kde@gmail.c | |om --- Comment #8 from Nate Graham --- *** Bug 468475 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474083] Lock/Logout icon size changes when only one action is visible
https://bugs.kde.org/show_bug.cgi?id=474083 --- Comment #4 from Yannick --- Hi Nate, I'd looked for it the other day, but I don't how to do it and where at. I'd found a kde.org webpage where it says where to go whether we need to declare a bug or want to contribute to an existing project or submit a merge request, etc. My understanding is that we need to have an account, fins the project then fork the project, and have a git repository, ...All that complexity just to change one file !?So I chose to upload that single file within the bug page to let someone like you or the author to check if the fix is okay and then merge it. I also wonder why the -1 was there and its purpose. Maybe it was useful at sometime as a workaround to a panel bug that might have been fixed in the meantime, and now that -1 is useless and causes a graphical bug in some cases. Le mar., sept. 5, 2023 à 22:30, Nate Graham a écrit: https://bugs.kde.org/show_bug.cgi?id=474083 Nate Graham changed: What |Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474083] Lock/Logout icon size bug within plasma panel
https://bugs.kde.org/show_bug.cgi?id=474083 --- Comment #2 from Yannick --- I've just added a "default panel" and it appeared to the left edge of the screen. I've tested the existing widget and then the one I've fixed, there is no regression, it works the same : - 1 icon fills the width of the panel - 2 icons fill the width of the panel but they are aside so their sizes are smaller - 3 icons or more, each icon fills the width of the panel and is put above/below the others. Then, I've moved that new panel to the top edge of the screen (the panel is bigger than mine and is above/over it). I've added the existing widget and the one I've fixed, both work the same, no regression : - 1 icon fill the the height of the panel - 2 icons fill the height of the panel, they have smaller icon sizes and 1 icon is above the other. - 3 icons or more, each icon takes all the height and icons are after/before the others. So, the fix works for tiny bars. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474083] Lock/Logout icon size bug within plasma panel
https://bugs.kde.org/show_bug.cgi?id=474083 Yannick changed: What|Removed |Added CC||yb21...@yahoo.fr --- Comment #1 from Yannick --- I've found the issue in the file /usr/share/plasma/plasmoids/org.kde.plasma.lock_logout/contents/ui/lockout.qml. The solution to fix the issue is to remove the " - 1" to the following lines of code : #21 : return height < minButtonSize * visibleButtons ? height * visibleButtons : height / visibleButtons - 1; FIX : return height < minButtonSize * visibleButtons ? height * visibleButtons : height / visibleButtons ; #28 : return width >= minButtonSize * visibleButtons ? width / visibleButtons - 1 : width * visibleButtons FIX : return width >= minButtonSize * visibleButtons ? width / visibleButtons : width * visibleButtons I've only tested the with the top bar with 24px height, and it works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474083] Lock/Logout icon size bug within plasma panel
https://bugs.kde.org/show_bug.cgi?id=474083 Yannick changed: What|Removed |Added Platform|Other |Archlinux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474083] New: Lock/Logout icon size bug within plasma panel
https://bugs.kde.org/show_bug.cgi?id=474083 Bug ID: 474083 Summary: Lock/Logout icon size bug within plasma panel Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: yb21...@yahoo.fr Target Milestone: 1.0 Created attachment 161358 --> https://bugs.kde.org/attachment.cgi?id=161358=edit 5 widgets side-by-side, the first has 3 actions, and the 4 others have each 1 action. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Add a Plasma Panel (optional : place it at the top, and set its height at 24px). 2. In that panel, add the Lock/Logout plasmoid. 3. Go into the Lock/Logout plasmoid settings, and choose only one action (1 box checked only). OBSERVED RESULT We can see that the icon size is smaller when there is only 1 action chosen to compare with the size of the icons when there are at least 2 actions chosen. EXPECTED RESULT Whether you choose 1 or more actions, the icon(s) size(s) should be the same. To me the correct size is the one used when there are at least 2 actions chosen. The fix should be done to context where the user chooses only 1 action. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, but the OS is not the problem (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION My purpose of putting 3 independent lock/logout plasmoids with 1 action each, is to be able to order in the panel each icon/action the way I want, which is not allowed by the widget. Being able to reorder the actions/icons would be a nice feature. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 466040] Konversation dumps core on exit
https://bugs.kde.org/show_bug.cgi?id=466040 Yannick changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 466040] Konversation dumps core on exit
https://bugs.kde.org/show_bug.cgi?id=466040 --- Comment #5 from Yannick --- (In reply to Enrico from comment #4) > Hello, I can't test in on Sid because the whole Debian is in a kind of > "freeze" for the upcoming release of "Bookworm". It will probably take 1-2 > month and I have been told that I won't receive this kind of updates until > the final release. > > Anyway, I tested it on Ubuntu 23.04 beta with Frameworks 104 and Plasma > 5.27.4 and konversation exits normally. Ok, I guess the issue can be closed then :) It can always be reopened later if necessary. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468235] Screen refresh rate stuck at 60hz even when set to 144hz in the display settings
https://bugs.kde.org/show_bug.cgi?id=468235 --- Comment #3 from Yannick --- Additional observation: if the screen goes into sleep mode then turns back on, it goes back to 60hz. But powering it off and on after that fixes the problem again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468235] Screen refresh rate stuck at 60hz even when set to 144hz in the display settings
https://bugs.kde.org/show_bug.cgi?id=468235 --- Comment #1 from Yannick --- Turning the monitor off and on again changes the refresh rate to the correct value. However it's still locked at 60hz when the system is rebooted. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] Window buttons are too big and blurry
https://bugs.kde.org/show_bug.cgi?id=468203 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #7 from Yannick --- Same issue here with breeze-gtk 5.27.4 on Wayland, GTK CSD window buttons are big and blurry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468235] Screen refresh rate stuck at 60hz even when set to 144hz in the display settings
https://bugs.kde.org/show_bug.cgi?id=468235 Yannick changed: What|Removed |Added Platform|Other |Archlinux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468235] New: Screen refresh rate stuck at 60hz even when set to 144hz in the display settings
https://bugs.kde.org/show_bug.cgi?id=468235 Bug ID: 468235 Summary: Screen refresh rate stuck at 60hz even when set to 144hz in the display settings Classification: Plasma Product: kwin Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: leguen.yann...@gmail.com Target Milestone: --- SUMMARY *** My display comes with 4 different refresh rates: 60hz, 120hz, 144hz and 165hz. Since kwin 5.27.4, the screen refresh rate is stuck at 60hz whether I select 60hz, 120hz or 144hz from the Plasma display settings (confirmed by checking the screen OSD menu). It happens on both Wayland and X11 sessions. xrandr displays the selected refresh rate. Setting the refresh rate to 165hz works as intended though. Downgrading to kwin 5.27.3 solves the issue. *** STEPS TO REPRODUCE 1. Select a 120hz or 144hz refresh rate from Plasma display settings 2. Moving the mouse cursor / windows around seems sluggish 3. The screen OSD confirms that it's still running at 60hz SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION My display is an Iiyama G-Master GB2770QSU-B1 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 466040] Konversation dumps core on exit
https://bugs.kde.org/show_bug.cgi?id=466040 --- Comment #2 from Yannick --- It looks like it's no longer happening. Maybe the Frameworks 5.104.0 or Plasma 5.27.3 update somehow fixed the issue. @Enrico: Do you still encounter the issue on Debian? -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 466040] New: Konversation dumps core on exit
https://bugs.kde.org/show_bug.cgi?id=466040 Bug ID: 466040 Summary: Konversation dumps core on exit Classification: Applications Product: konversation Version: 1.9.22122 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: leguen.yann...@gmail.com Target Milestone: --- Created attachment 156466 --> https://bugs.kde.org/attachment.cgi?id=156466=edit Backtrace SUMMARY *** Konversation works normally but dumps core on exit. I use a Wayland session, I haven't tried on X11. *** STEPS TO REPRODUCE 1. Start Konversation and use it. 2. Quit Konversation. 3. Konversation doesn't terminate gracefully and dumps core (as shown by coredumpctl). SOFTWARE/OS VERSIONS Linux: Archlinux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462928] New: Copying a file after another copies the first file again
https://bugs.kde.org/show_bug.cgi?id=462928 Bug ID: 462928 Summary: Copying a file after another copies the first file again Classification: Applications Product: dolphin Version: 22.12.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: yannick.roeh...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If I copy two files, one after the other by dropping the files between two dolphin windows, when dropping the second file dolphin actually drops the first file and offers me to overwrite it. Note that that works if I'm using two tabs instead of two windows. STEPS TO REPRODUCE 1. Create two folders and open them in separate dolphin windows. 2. In one folder. Create a 1.txt file with "one" inside. Create a 2.txt file with "two" inside. 3. Copy 1.txt by drag and dropping the file to the window with the second folder. 4. Copy 2.txt by drag and dropping the file. OBSERVED RESULT Dolphin says that 1.txt is already in the folder. If I accept the overwrite, the content of 1.txt is "one" so it's not 2.txt that have been copies with 1.txt name. EXPECTED RESULT Both file are copied. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION I tried with Konqueror and the copy works as expected. Also note that I'm using a locally compile dolphin 22.12.0 on Debian unstable. Maybe the problem occurs because I'm not having other 22.12.0 libraries. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461985] webdav nextcloud integration : every created file fails to a generic file with propfind xml content
https://bugs.kde.org/show_bug.cgi?id=461985 Yannick LIMBALLE changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Yannick LIMBALLE --- issue resolved when updating to : kf5-kio-core 5.100.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461985] webdav nextcloud integration : every created file fails to a generic file with propfind xml content
https://bugs.kde.org/show_bug.cgi?id=461985 --- Comment #3 from Yannick LIMBALLE --- issue resolved when updating to : kf5-kio-core 5.100.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461985] webdav nextcloud integration : every created file fails to a generic file with propfind xml content
https://bugs.kde.org/show_bug.cgi?id=461985 Yannick LIMBALLE changed: What|Removed |Added Version|22.08.1 |21.08.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461985] New: webdav nextcloud integration : every created file fails to a generic file with propfind xml content
https://bugs.kde.org/show_bug.cgi?id=461985 Bug ID: 461985 Summary: webdav nextcloud integration : every created file fails to a generic file with propfind xml content Classification: Applications Product: dolphin Version: 22.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: shoot...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Using a webdavs integration under Linux KDE Dolphin file browser in the form : webdavs://usern...@server.com/remote.php/dav/files/username/ The access is made from an app password and is working well in the authentication phase. Access is granted and file browsing is well working. The issue is every try to upload or create a new file from scratch result in having a default 167 kb file with a XML content which corresponds to a propfind request in webdav. The content of the file is : On the other hand, browsing files or downloading files from the webdav folders are working nice. Moreover, web browser upload or file creation is well working. The issue is showing itself only on upload and file creation using webdav integration through Dolphin client (version 22.08.2) STEPS TO REPRODUCE 1. Configuration a Dolphin network folder following the procedure given by nextcloud support page (https://docs.nextcloud.com/server/latest/user_manual/en/files/access_webdav.html#accessing-files-with-kde-and-dolphin-file-manager) 2. Upload a file into the network folder once mounted 3. If the file is 167 kb file size, check the content is the same as below : OBSERVED RESULT see above EXPECTED RESULT the real source file is being uploaded. A newly created file is empty. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 37 kernel 6.0.8 (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451631] [Wayland] Plasmashell freezes briefly after focusing the desktop if it was started with a non-empty clipboard history
https://bugs.kde.org/show_bug.cgi?id=451631 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #7 from Yannick --- Same issue here, on Archlinux and Plasma 5.25.2 on wayland (no issue on X11). I've got the same messages in the journal log when the freeze happens. However on my end it only seems to happen when there's a document in the clipboard, it doesn't happen with text selection in the clipboard. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448275] All qt apps are freezed/crashed after screen wake up
https://bugs.kde.org/show_bug.cgi?id=448275 --- Comment #7 from Yannick --- It looks like it's fixed on my end now! It may be related to the Plasma 5.24.3 or Qt 5.15.3 updates. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448275] All qt apps are freezed/crashed after screen wake up
https://bugs.kde.org/show_bug.cgi?id=448275 --- Comment #5 from Yannick --- Created attachment 146485 --> https://bugs.kde.org/attachment.cgi?id=146485=edit Dolphin unresponsive KDE apps such as Dolphin, Yakuake (when it is visible) or System Settings, etc. no longer seem to crash, but they become unresponsive for a while after the screen wakes up (the window is greyed out, as in the screenshot attached). After a minute or so the applications can be used normally again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448275] All qt apps are freezed/crashed after screen wake up
https://bugs.kde.org/show_bug.cgi?id=448275 --- Comment #4 from Yannick --- Created attachment 146484 --> https://bugs.kde.org/attachment.cgi?id=146484=edit Dolphin output with WAYLAND_DEBUG=1 Here is the output of Dolphin 21.12.2 with the WAYLAND_DEBUG=1 environment variable set, after turning off then on a DisplayPort monitor. The output is very large, I suppose it starts to be relevant at line 1018: "qt.qpa.wayland: Creating a fake screen in order for Qt not to crash" GPU: AMD RX560 (with Mesa 21.3.5) Plasma version: 5.24.0 Frameworks version: 5.90.0 Distribution: Archlinux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448275] All qt apps are freezed/crashed after screen wake up
https://bugs.kde.org/show_bug.cgi?id=448275 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #2 from Yannick --- I have the exact same issue. Not all Qt apps are affected though, VLC for example is still responsive after the monitor wakes up. It looks like only KDE apps are affected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #456 from Yannick --- Now, even Microsoft with Windows 11 is capable of having a different wallpaper per virtual desktop. Plasma will soon be the only desktop environment for which it is impossible to have such a feature though it used to exist in KDE4. As expected and announced in the past, KDE Team wants people to use activities instead of virtual desktops. It is obviously that today they force them to, because of technical limitations they don't want to fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #34 from Yannick --- I have the exact same issue as Rainer Finke described, on Plasma 5.22.0. Plasmashell crashes just by turning my DisplayPort monitor off and on. Restarting plasmashell brings the session back. Sadly I didn't find any related core dump with coredumpctl. OS: Arch Linux KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9 GPU: AMD RX560 (mesa drivers) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #424 from Yannick --- I feel like what the DEVs are hardly trying to tell us is that we shall focus on the Activities features instead of VDs, because each activity has its own wallpaper, own widgets, etc. Why not... BUT - why didn't they dropped the VDs from Plasma and they seem to abandon VDs ? Why can't we use the cube on activities whenever we switch activity (the cube is still linked to VDs) ? - Why do we share same panels across all activities (we can only choose on which activities we want an icon/widget to be printed/showed except for panels themselves) ? To me the design should be reviewed completely for KDE Plasma 6, and be as close as possible to the one used in KDE4 in which all the features we are asking for were working correctly and smoothly, without tricks/hints/add-ons. If I remember well, KDE 5 Frameworks and Plasma teams/devs said that there were too many bugs generated by KDE4 because of its design and crossed features within VDs and Activities (that were introduced) and that the maintenance had become difficult (a nightmare ?) which explained why the KDE 5 design had been reviewed and had completely made VDs and Activities different, and focusing that Activities would replace VDs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #414 from Yannick --- @leftcrane Let's say you're up to buy a house property you order from a professional home builder that used to to many different and specific decorations in each room. You ask him to have your living room in white, your bathroom in blue, your daughter room in pink, etc... And the guy tells you this is nonsense and you should have the same paint/wallpaper color in every single room of your house. This is exactly what you are saying to us, to the users, which is very annoying and obviously your behavior is dumb. A user and a buyer will use/buy the product that meets their requirements. Innovation can generate new needs and drop others, but removing a feature that was still being used by users should never happen, unless there is something better in replacement (which can meet their needs and requirements). Activities and VDs have different usage goals. Not every users adhere to activities, and may prefer to use VDs instead. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384782] Allow manually re-ordering tray icons
https://bugs.kde.org/show_bug.cgi?id=384782 --- Comment #21 from Yannick --- My understanding is that ordering should be done in Entries page, I agree with Nate that is does more sense as it is the place where all items are shown, the one activated, deactived, showing/not showing. Konrad, you have very good questions. Either way looks good to me : - adding the "items ordering" options in general page (just like icons size option) with "default mode" and "manual mode", radio button or dropdownlist. - adding the checkbox in the Entries page aside the existing one, but for "manual ordering" option. In the Entries page : - In "default" mode, we shall keep the actual behavior. - In "manual" mode, at first time I suggest to have Notification icon at the top of the list and the other items sorted alphabetically. Then the user would change the order (drag-and-drop), and of course he could also move the Notification icon. In case the user deactivates the "manual" mode, nothing should be lost but kept in his preferences (stored settings). That way, in case the user would reactivate the mode, the items would be in the same order than previously. If possible, when "manual" mode is set, the system tray should be consistent/aligned with the order set by the user. That means the system tray would behave differently in "manual mode" than in "default mode". So, in "manual mode" it should not care of categories, but care of user's ordering only. In case any new icon/item appears, i think it should go at the last position. Then it is up to the user to rearrange it later. In case the manual mode was used at least once (settings stored) but deactivated, any new item/icon should also be added/recorded at the end of the manual ordering list. Adding items as first may annoy the user in case he doesn't care of that new item. Also, the more he gets new icons, the more his manual order would get changed/messed up. So adding items as last seems to be the best option. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384782] Allow manually re-ordering tray icons
https://bugs.kde.org/show_bug.cgi?id=384782 --- Comment #17 from Yannick --- Thanks to Nate Graham for considering my demand and idea (sorting in Entries page with a draggable system). I've suggested that idea because I thought the icons were sorted in the same order of the entries page from system tray settings (as it is where we can set the icons we want to always show or hide). But if the sorting can be implemented directly in the system tray as an easier solution, that one is best ! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436064] Plasma's native panel lacks popular Dock-like features and options
https://bugs.kde.org/show_bug.cgi?id=436064 Yannick changed: What|Removed |Added Summary|Plasma's native panel |Plasma's native panel lacks |misses Dock-like features |popular Dock-like features |and options |and options -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436064] New: Plasma's native panel misses Dock-like features and options
https://bugs.kde.org/show_bug.cgi?id=436064 Bug ID: 436064 Summary: Plasma's native panel misses Dock-like features and options Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: yb21...@yahoo.fr Target Milestone: 1.0 SUMMARY Plasma's native panel misses Dock-like options and features : - colored panel with/without transparency (blur) - floating panel (height/margin from the side of the screen). - choose indicator type/shape (dot, line, square, circle, cross, triangle, or whatever with a specific image/icon), choose its color and shadow options. - shape of each corner (squared, rounded, curve scale/degree, edge width ...). - parabolic zoom effect to panel items, not just the taskbar icons (Kickmenu). - border width and color (thin, thick, specific value) - ... STEPS TO REPRODUCE 1. Open Plasma's native panel settings 2. Compare with Latte-dock settings and features 3. Compare with competitors docks settings OBSERVED RESULT The user can customize the panel but he is too limited to compare to competitors panels settings. EXPECTED RESULT The user is able to customize plasma's native panel with more settings for its look and feel and behavior. Main settings would allow to set a panel to look like most popular and famous panels / docks (Windows, macOS, Chrome OS, macOS, Gnome's dash to dock, ...). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.11 / Plasma 5 (available in About System) KDE Plasma Version: 5.21 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The idea is to allow similar options and features of other docks in Plasma's own panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436063] Can not rearrange system tray icons / entries
https://bugs.kde.org/show_bug.cgi?id=436063 Yannick changed: What|Removed |Added Summary|Rearrange system tray icons |Can not rearrange system |/ entries |tray icons / entries -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436063] New: Rearrange system tray icons / entries
https://bugs.kde.org/show_bug.cgi?id=436063 Bug ID: 436063 Summary: Rearrange system tray icons / entries Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: yb21...@yahoo.fr CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY In the System tray widget settings, at the entries page, I wish to rearrange and set a specific order for the entries. The purpose of this is to have these entries / icons ordered in the same way in the panel. STEPS TO REPRODUCE 1. Add a system tray widget in a panel 2. Go to the system tray settings 3. Go to the enteies page OBSERVED RESULT It is not possible to change the order of the entries. EXPECTED RESULT The user can rearrange and set the entries in the order he wishes. The icons are displayed in the same order in the system tray widget (within the panel). This could be done by selecting an entry then drag and drop it before or after another entry. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: plasma 5.11 / Plasma 5 (available in About System) KDE Plasma Version: 5.21 KDE Frameworks Version: ? Qt Version: ? ADDITIONAL INFORMATION Same demand as bug id 180997 but for plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433741] Invisible close, maximize and minimize buttons on CSD GTK applications
https://bugs.kde.org/show_bug.cgi?id=433741 Yannick changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433741] Invisible close, maximize and minimize buttons on CSD GTK applications
https://bugs.kde.org/show_bug.cgi?id=433741 --- Comment #1 from Yannick --- Oh damn sorry, I rebooted my computer, tried again with a clean profile, and now it works... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433741] New: Invisible close, maximize and minimize buttons on CSD GTK applications
https://bugs.kde.org/show_bug.cgi?id=433741 Bug ID: 433741 Summary: Invisible close, maximize and minimize buttons on CSD GTK applications Product: Breeze Version: 5.21.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: leguen.yann...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 136252 --> https://bugs.kde.org/attachment.cgi?id=136252=edit CSD GTK window with missing buttons SUMMARY The close, maximize, minimize buttons are invisible on CSD GTK windows with the Breeze-gtk theme. STEPS TO REPRODUCE 1. Start a Plasma session with a clean profile 2. Launch a CSD GTK application (Simple-scan in my example) 3. The close, maximize, minimize buttons are invisible but are clickable. 4. Delete .config/gtk-3.0/window_decorations.css and restart the GTK application. The window buttons are now visible, but they will become invisible again on the next session restart (because window_decorations.css will be recreated). OBSERVED RESULT The close, maximize, minimize window buttons are invisible. EXPECTED RESULT They should be visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux / Plasma 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 GTK version: 3.24.26 ADDITIONAL INFORMATION Oddly enough, the GTK window decorations display correctly on an older profile, and the contents of window_decorations.css is exactly the same. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433347] Dolphin may crash when repeatedly opening and closing dialog
https://bugs.kde.org/show_bug.cgi?id=433347 Yannick Armand changed: What|Removed |Added CC||yannick.armand@protonmail.c ||om --- Comment #2 from Yannick Armand --- I am not able to reproduce the problem (on a different system). Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-3-amd64 OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 433329] Add a context menu on the files: new, rename and delete
https://bugs.kde.org/show_bug.cgi?id=433329 --- Comment #1 from Yannick Armand --- I can't change the severity to "wishlist". Can someone do it for me? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 433348] "Rename" action is disabled until a second document is open
https://bugs.kde.org/show_bug.cgi?id=433348 Yannick Armand changed: What|Removed |Added Ever confirmed|0 |1 CC||yannick.armand@protonmail.c ||om Status|REPORTED|CONFIRMED --- Comment #1 from Yannick Armand --- I can reproduce the issue Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-3-amd64 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 432573] Code folding not working properly for Python
https://bugs.kde.org/show_bug.cgi?id=432573 Yannick Armand changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||yannick.armand@protonmail.c ||om --- Comment #1 from Yannick Armand --- The problem seems generic: as soon as there is an empty line between the line of code that defines a block (`def`, `if`...) and the code inside this block, the code fold is not proposed. This code proposes 4 folds: def test(): code = "" if True: code = "" while False: code = "" test: something This code does not offer any fold: def test(): code = "" if True: code = "" while False: code = "" test: something -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 433329] New: Add a context menu on the files: new, rename and delete
https://bugs.kde.org/show_bug.cgi?id=433329 Bug ID: 433329 Summary: Add a context menu on the files: new, rename and delete Product: kate Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: yannick.arm...@protonmail.com Target Milestone: --- It would be nice to have additional options for file manipulation in the context menu (right-click) of a file: create a new file, rename and delete. For file renaming and deletion it would be contextual to the clicked file. For file creation, it would be proposed on the contextual menu of the folders. For the creation of a file at the root we can imagine that the option would also appear when we right-click on a file in the desired folder and create the file in the same folder. It would also be nice to have the same actions concerning folders: create a folder, rename and delete. Other evolutions could be made later, such as entering a name like "a/b/c.md" which would create the corresponding folder architecture, but this is not the purpose of this request. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433126] Inactive title bar elements in Breeze Light have the same color as active title bar elements
https://bugs.kde.org/show_bug.cgi?id=433126 --- Comment #3 from Yannick --- Created attachment 135961 --> https://bugs.kde.org/attachment.cgi?id=135961=edit inactive CSD Inactive CSD elements, on the other hand, behave "as before" since they have a lighter shade of grey than active decorations. Side-by-side comparison with inactive Kate and Simple-scan windows on the attached picture. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433126] Inactive title bar elements in Breeze Light have the same color as active title bar elements
https://bugs.kde.org/show_bug.cgi?id=433126 Yannick changed: What|Removed |Added Summary|Inactive title bar text in |Inactive title bar elements |Breeze Light has the same |in Breeze Light have the |color as active title bar |same color as active title |text|bar elements -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433158] New: Different menu item height between breeze and breeze-gtk
https://bugs.kde.org/show_bug.cgi?id=433158 Bug ID: 433158 Summary: Different menu item height between breeze and breeze-gtk Product: Breeze Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: leguen.yann...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 135836 --> https://bugs.kde.org/attachment.cgi?id=135836=edit Menu item height comparison SUMMARY On Plasma 5.21.0, the menu items seem larger in GTK3 applications using the breeze-gtk theme compared to the menu items of Qt applications using the breeze theme. It doesn't seem to affect Firefox and Thunderbird for some reason, but it's visible on Shotwell and Handbrake for example. On GTK2 applications (tested with Gimp) the menu item height seems smaller. SOFTWARE/OS VERSIONS OS: Archlinux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433126] Inactive title bar text in Breeze Light has the same color as active title bar text
https://bugs.kde.org/show_bug.cgi?id=433126 --- Comment #1 from Yannick --- Created attachment 135801 --> https://bugs.kde.org/attachment.cgi?id=135801=edit "Classic" Breeze theme (active window on the left, inactive on the right) For reference, the same screenshot with the "classic" Breeze theme. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433126] Inactive title bar text in Breeze Light has the same color as active title bar text
https://bugs.kde.org/show_bug.cgi?id=433126 Yannick changed: What|Removed |Added Summary|Inactive title bar text in |Inactive title bar text in |Breeze-light has the same |Breeze Light has the same |color as active title bar |color as active title bar |text|text -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433126] New: Inactive title bar text in Breeze-light has the same color as active title bar text
https://bugs.kde.org/show_bug.cgi?id=433126 Bug ID: 433126 Summary: Inactive title bar text in Breeze-light has the same color as active title bar text Product: Breeze Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: leguen.yann...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- Created attachment 135800 --> https://bugs.kde.org/attachment.cgi?id=135800=edit Breeze Light (active window on the left, inactive on the right) SUMMARY With the new Breeze Light theme, it's a bit hard to distinguish active window decorations from inactive ones, as the title bar text seems to keep the same color on both active and inactive windows. I edited the Breeze Light color scheme and changed the "inactive title bar text" color to a lighter one, but it didn't have any effect. With the "classic" Breeze theme (dark title bars) everything works as expected. SOFTWARE/OS VERSIONS OS: Archlinux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433103] New Plasma 5.21 start menu window is too small
https://bugs.kde.org/show_bug.cgi?id=433103 --- Comment #4 from Yannick --- Indeed, the spacing between buttons is inconsistent. I guess the reason why the top and bottom bars are swapped compared to yours is because my panel is on the bottom of the screen, and yours is probably on top? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433103] New Plasma 5.21 start menu window is too small
https://bugs.kde.org/show_bug.cgi?id=433103 --- Comment #2 from Yannick --- Created attachment 135784 --> https://bugs.kde.org/attachment.cgi?id=135784=edit screenshot_plasma_5.21.0_archlinux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433103] New Plasma 5.21 start menu window is too small
https://bugs.kde.org/show_bug.cgi?id=433103 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #1 from Yannick --- Same issue on Archlinux with Plasma 5.21.0. In attachment, a screenshot in which the insufficient horizontal space is quite visible. I use the Ubuntu fonts, but with the Noto Sans fonts there is a bit more horizontal space. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 420969] "Find" input box stops reacting to keyboard after switching to "Replace" mode
https://bugs.kde.org/show_bug.cgi?id=420969 Yannick Armand changed: What|Removed |Added CC||yannick.armand@protonmail.c ||om --- Comment #2 from Yannick Armand --- I can't reproduce the issue. I'm on Debian, with more up-to-date packages. Has the problem been solved or is it environment specific? Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 333401] Bookmark information gets lost when another line is moved across bookmarked line
https://bugs.kde.org/show_bug.cgi?id=333401 Yannick Armand changed: What|Removed |Added CC||yannick.armand@protonmail.c ||om --- Comment #3 from Yannick Armand --- This problem is still present (Kate 20.12.2, KDE Frameworks 5.78.0). (Does the status of the ticket have to be set to CONFIRMED?) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431197] Sub-pixel anti-aliasing is not being applied
https://bugs.kde.org/show_bug.cgi?id=431197 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #18 from Yannick --- I can confirm this issue on Archlinux and Plasma 5.20.5. Qt apps running on Plasma have their text rendered using gray-scale (tested with Dolphin and VLC), while GTK3 apps (also running on Plasma) have their text rendered with RGB anti-aliasing (tested with Simple-scan). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430513] New: Snippets expansion incorrect when placeholders and not separated by spaces
https://bugs.kde.org/show_bug.cgi?id=430513
Bug ID: 430513
Summary: Snippets expansion incorrect when placeholders and not
separated by spaces
Product: kate
Version: 20.08.2
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: plugin-snippets
Assignee: kwrite-bugs-n...@kde.org
Reporter: b...@ygingras.net
Target Milestone: ---
SUMMARY
STEPS TO REPRODUCE
1. Create the following snippet: Test${foo="foo"}${bar="bar"}. ${cursor}
2. Expand the snippet
OBSERVED RESULT
The snippet expansion starts with "foo" being empty.
EXPECTED RESULT
The snippet expansion should starts with "foo" being "foo".
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu Linux 20.10
KDE Frameworks Version:
5.74.0
Qt Version: 5.14.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 401797] KWin/Wayland capping framerate to 60 fps in XWayland in borderless fullscreen (Wine)
https://bugs.kde.org/show_bug.cgi?id=401797 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #13 from Yannick --- On Archlinux with Kwin 5.19.5, I also notice a difference between OpenGL (native games or wine + wineD3D) and Vulkan games (wine + dxvk in that case). I have a 144hz display. OpenGL games on Plasma-wayland are smooth, while Vulkan games are stuttering. However, when I start a Proton game with the "DXVK_HUD=fps" parameter, the FPS counter can go beyond 144 fps (it depends how well my GPU performs I guess), it doesn't seem to be capped to 144 fps even though the game is visibly stuttering. I'm not sure if my observations are related to this bug report or if I should open a new one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #366 from Yannick --- It has been so long since people raised that missing feature / regression. My comment is dated january 2016 ! More than 4 years... It looks like no official solution will be released. I think that mainly they don't care of the users. Either they are too confident on their work or they let you choose any desktop environment you (user) prefer. In both cases it leads to ignore what users want, leaving them to their own choice's paradigm : keep using KDE or switch to another DE. I still experiment many annoying/unacceptable bugs in main features (icons task manager panel rearranging, resizing, screen-side change, ...). So I don't think we'll see the return of that feature. I'm seriously thinking about switching KDE to another DE between these : Gnome, Deepin, XFCe, LXQt. With priority given to the one that would have this feature we're requiring to KDE. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420017] Add language windows is flickering
https://bugs.kde.org/show_bug.cgi?id=420017 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #2 from Yannick --- In my case, it doesn't flicker but adding a new language does nothing. The only language that appears is American English, even though Plasma uses the French localization. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419263] Right click on system tray icon brings wrong menu
https://bugs.kde.org/show_bug.cgi?id=419263 --- Comment #5 from Yannick Roehlly --- Hi Michail. I've tested the new code. It works! Thanks for the super fast answer and correction. Concerning your last comment, I don't have the problem with the 0.9.9 version. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419263] New: Right click on system tray icon brings wrong menu
https://bugs.kde.org/show_bug.cgi?id=419263 Bug ID: 419263 Summary: Right click on system tray icon brings wrong menu Product: lattedock Version: git (master) Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: yannick.roeh...@gmail.com Target Milestone: --- SUMMARY Right clicking on a system tray icon brings the system tray global configuration menu instead of the one from the clicked icon. The only way to access the icon contextual menu is to do a long click on the icon. STEPS TO REPRODUCE 1. Launch Kmail with system tray integration 2. Right click on the Kmail icon in the system tray OBSERVED RESULT The contextual menu appearing is (maybe not the exact wording as my locale is not English) - Configure system tray - Configure Latte... - Quit Latte - Add widgets... - Edit Panel... EXPECTED RESULT The Kmail contextual menu should appear: - Check mail - Check mail in... - etc... SOFTWARE/OS VERSIONS Locally compiled package on Debian Sid. Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION The problem is also present in the version 0.9.10 (not available in the version selection box of the bug tracker ;-)) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412988] Black buttons on GTK3 applications
https://bugs.kde.org/show_bug.cgi?id=412988 --- Comment #1 from Yannick --- Damn, I just noticed that there was already a bug report for this. Sorry for the inconvenience. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412988] New: Black buttons on GTK3 applications
https://bugs.kde.org/show_bug.cgi?id=412988 Bug ID: 412988 Summary: Black buttons on GTK3 applications Product: Breeze Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: leguen.yann...@gmail.com Target Milestone: --- Created attachment 123213 --> https://bugs.kde.org/attachment.cgi?id=123213=edit Shotwell preferences I upgraded to Plasma 5.17 and noticed that buttons were broken on GTK3 applications, they often appear to be black. When I hover the mouse over them, they sometimes turn white or blue again, but not in a consistent way. I also noticed that on Shotwell, despite checking the "Use a dark theme" on the application preferences, the theme was always light. STEPS TO REPRODUCE Start a GTK3 application and look at the buttons in applications preferences for example. OBSERVED RESULT Some buttons are black. EXPECTED RESULT Unchecked buttons are white, checked buttons are blue. SOFTWARE/OS VERSIONS OS: ArchLinux Plasma 5.17.0 Frameworks 5.63.0 Qt version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405351] Plasma crashes with frameworks-plasma 5.56.0
https://bugs.kde.org/show_bug.cgi?id=405351 --- Comment #8 from Yannick --- It doesn't crash anymore with your package. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405351] Plasma crashes with frameworks-plasma 5.56.0
https://bugs.kde.org/show_bug.cgi?id=405351 --- Comment #6 from Yannick --- Created attachment 118719 --> https://bugs.kde.org/attachment.cgi?id=118719=edit backtrace Here is the backtrace that I got with coredumpctl. Should I also enable debug symbols for the plasma-workspace package? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405351] Plasma crashes with frameworks-plasma 5.56.0
https://bugs.kde.org/show_bug.cgi?id=405351 --- Comment #4 from Yannick --- (In reply to Antonio Rojas from comment #3) > (In reply to Yannick from comment #2) > > I compiled plasma-framework with debug symbols, but now after 5 attempts I'm > > unable to open the crash handler window again :( > > Does that mean it doesn't crash, or still crashes but you don't get a > drkonqi window It still crashes, the drkonqi icon appears on the systray but even when I click on it, it won't open the window. Then the taskbar dies anyway, so I can't click on it again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405351] Plasma crashes with frameworks-plasma 5.56.0
https://bugs.kde.org/show_bug.cgi?id=405351 --- Comment #2 from Yannick --- I compiled plasma-framework with debug symbols, but now after 5 attempts I'm unable to open the crash handler window again :( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405351] New: Plasma crashes with frameworks-plasma 5.56.0
https://bugs.kde.org/show_bug.cgi?id=405351 Bug ID: 405351 Summary: Plasma crashes with frameworks-plasma 5.56.0 Product: frameworks-plasma Version: 5.56.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: leguen.yann...@gmail.com Target Milestone: --- Created attachment 118717 --> https://bugs.kde.org/attachment.cgi?id=118717=edit crash report With plasma-frameworks 5.56.0, both Plasma X11 and Wayland crashes at login. On the X11 session, the screen turns black and the taskbar disappears after a while, but I could export the crash log in time. STEPS TO REPRODUCE Start a Plasma session (X11 or Wayland). OBSERVED RESULT The screen turns black and the taskbar disappears. EXPECTED RESULT The session starts correctly. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma : 5.15.2 KDE Frameworks : 5.56.0 Qt : 5.12.1 Kernel : 5.0.0-arch1-1-ARCH OS type : 64-bit Processors : 4 × Intel® Core™ i5-3570 CPU @ 3.40GHz RAM : 15,6 Gio ADDITIONAL INFORMATION I use an AMD GPU (RX560). The session starts normally again when downgrading to frameworks-plasma 5.55.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404442] Selected window appears twice on desktop grid (X11)
https://bugs.kde.org/show_bug.cgi?id=404442 --- Comment #3 from Yannick --- Created attachment 118139 --> https://bugs.kde.org/attachment.cgi?id=118139=edit "qdbus org.kde.KWin /KWin supportInformation" output Provided the requested output as attachment -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404442] Selected window appears twice on desktop grid (X11)
https://bugs.kde.org/show_bug.cgi?id=404442 --- Comment #2 from Yannick --- Created attachment 118138 --> https://bugs.kde.org/attachment.cgi?id=118138=edit screenshot of the issue -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404442] New: Selected window appears twice on desktop grid (X11)
https://bugs.kde.org/show_bug.cgi?id=404442 Bug ID: 404442 Summary: Selected window appears twice on desktop grid (X11) Product: kwin Version: 5.15.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: leguen.yann...@gmail.com Target Milestone: --- A selected window appears twice on the desktop grid when the cursor hovers the current workspace of this window. It happens only on a X11 session. Screenshot: https://i.imgur.com/aZHosiz.jpg STEPS TO REPRODUCE 1. Go to the desktop grid 2. Select a window 3. Move it but keep the mouse cursor above the workspace of this window OBSERVED RESULT The window is displayed twice, one below the mouse cursor and a second one on the workspace miniature. EXPECTED RESULT The window is only displayed once, below the mouse cursor SOFTWARE/OS VERSIONS ArchLinux KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390567] Plasma crash when typing text in the kickoff menu
https://bugs.kde.org/show_bug.cgi?id=390567 Yannick <leguen.yann...@gmail.com> changed: What|Removed |Added Summary|Plasma crash when typing|Plasma crash when typing |text in the kickoff menu & |text in the kickoff menu |krunner | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390567] New: Plasma crash when typing text in the kickoff menu & krunner
https://bugs.kde.org/show_bug.cgi?id=390567 Bug ID: 390567 Summary: Plasma crash when typing text in the kickoff menu & krunner Product: plasmashell Version: 5.12.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: leguen.yann...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.1) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: It happens since the update to Qt 5.10.1. Every time I search an application or a document through the Plasma kickoff menu or through Alt+f2, Plasma crashes. Most of the time, the screen just turns black and there's nothing I can do except switching to a TTY. 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 0x7f47c281c800 (LWP 607))] Thread 25 (Thread 0x7f46a89df700 (LWP 966)): #0 0x7f47bb57c3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f47bc3c302c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f46da9d742f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f46da9dc479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f46da9d6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f46da9dc4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f46da9d6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f46da9d9c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f47bc3c1b4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f47bb57608c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f47bbcc9e7f in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f46a91e0700 (LWP 965)): #0 0x7f47bb57c3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f47bc3c302c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f46da9d742f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f46da9dc479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f46da9d6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f46da9dc4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f46da9d6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f46da9d9c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f47bc3c1b4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f47bb57608c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f47bbcc9e7f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f46a99e1700 (LWP 964)): #0 0x7f47bb57c3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f47bc3c302c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f46da9d742f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f46da9dc479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f46da9d6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f46da9dc4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f46da9d6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f46da9d9c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f47bc3c1b4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f47bb57608c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f47bbcc9e7f in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f46aa1e2700 (LWP 963)): #0 0x7f47bb57c3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f47bc3c302c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f46da9d742f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f46da9dc479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f46da9d6924 in
[kwin] [Bug 388885] Pointer does not unfreeze after closing an app that locks it
https://bugs.kde.org/show_bug.cgi?id=35 Yannick <leguen.yann...@gmail.com> changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #4 from Yannick <leguen.yann...@gmail.com> --- I can confirm this issue, on Archlinux with Plasma 5.12.0. In my case however, the cursor is unfrozen after holding Escape for 3 seconds. It only happens when I run Xonotic through XWayland. When Xonotic uses the SDL Wayland backend (SDL_VIDEODRIVER=wayland), the cursor is unfrozen as expected when closing the app. However, with the game Neverball, pressing Escape in-game pauses the game (but doesn't close it) and the cursor remains frozen, with both the X11 and Wayland SDL backends. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386954] Pointer locking/confinement issues
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #14 from Yannick <leguen.yann...@gmail.com> --- The issue is still here with Plasma 5.12.0. When I start Neverball with both the X11 and Wayland SDL backends, pressing "Escape" in the game will not unlock the cursor. I have to Alt+tab out or press "Escape" during 3 seconds to unlock it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386954] Pointer locking/confinement issues
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #13 from Yannick <leguen.yann...@gmail.com> --- I applied the patch on top of Kwin 5.11.5. I'm not sure if it's the right thing to do, but building kwin-git and all its *-git dependencies would take ages on my computer. I still had issues with Neverball and Xonotic. The pointer is not unlocked when I press Escape on Neverball, and is often not properly confined to the Xonotic in-game menu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386993] New: SDL Wayland backend doesn't work on Plasma
https://bugs.kde.org/show_bug.cgi?id=386993 Bug ID: 386993 Summary: SDL Wayland backend doesn't work on Plasma Product: kwin Version: 5.11.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: leguen.yann...@gmail.com Target Milestone: --- On ArchLinux, SDL2 applications default to the X11 backend, but the Wayland backend can be forced with the "SDL_VIDEODRIVER=wayland" parameter. When I use this parameter with SDL games such as Neverball or Xonotic, the game doesn't start and I have this output: "wl_registry@2: error 0: invalid version for global wl_data_device_manager (8): have 2, wanted 3 Failure to initialize SDL (The video driver did not add any displays)" I'm not sure if it's a bug or a known limitation to the current Plasma session? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386954] Pointer locking/confinement issues
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #8 from Yannick <leguen.yann...@gmail.com> --- I tried Neverball and Xonotic on a Weston session, and didn't have any of the problems I encountered with Plasma. The pointer is correctly locked/unlocked on Weston. I made sure to run both games with the X11 SDL backend (SDL_VIDEODRIVER=x11). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386954] Pointer locking/confinement issues
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #5 from Yannick <leguen.yann...@gmail.com> --- Sorry, my bad: I made another test with Neverball. When I press "Escape", the mouse pointer remains visible. It just won't move. I noticed a few more things: - I can also unlock the pointer on Neverball by pressing Alt+Tab a few times. - As long as the OSD is visible, no game input is taken into consideration (for example, I can't use Escape to exit Neverball or Space/right click to jump into Xonotic action). - When I quit Xonotic, the mouse cursor remains locked on the desktop. Pressing Escape during 3 seconds unlocks it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386954] Pointer locking/confinement issues
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #4 from Yannick <leguen.yann...@gmail.com> --- Hi, 1. I use xorg-server-xwayland 1.19.5 2. There should be a mouse cursor on the neverball screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386954] Pointer locking/confinement issues
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #2 from Yannick <leguen.yann...@gmail.com> --- I am aware that the issue with NetRadiant is not easily reproducible, because this application is quite specific and requires a special setup, sorry for that :( But maybe other applications have the same usability issue (it's probably the case for other *radiant forks like GTKRadiant). I tried Blender and it worked fine, though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386954] Pointer locking/confinement issues
https://bugs.kde.org/show_bug.cgi?id=386954 --- Comment #1 from Yannick <leguen.yann...@gmail.com> --- Created attachment 108881 --> https://bugs.kde.org/attachment.cgi?id=108881=edit NetRadiant layout, with 3D and 2D views -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386954] New: Pointer locking/confinement issues
https://bugs.kde.org/show_bug.cgi?id=386954 Bug ID: 386954 Summary: Pointer locking/confinement issues Product: kwin Version: 5.11.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: leguen.yann...@gmail.com Target Milestone: --- Created attachment 108880 --> https://bugs.kde.org/attachment.cgi?id=108880=edit Pressing "escape" during a Neverball game Hello, I gave the Plasma Wayland session a try and ran into some issues with pointer locking/confinement. All games and apps in my tests ran through XWayland. If this bug report should be split into several parts, please tell me :) - Neverball, a 3D game, works mostly fine in windowed mode, but when you press "escape" during a game, the mouse pointer is not usable right away. You have to press "Escape" during 3 seconds to unlock it and navigate in the game menu. Screenshot in attachment. - I also tried Xonotic (an open-source FPS game) in fullscreen mode. When the game starts, it displays a menu. A Kwin OSD appears, saying that the pointer is confined to the current window. However, the in-game mouse pointer disappears on some areas of the screen and is almost impossible to use. By opening the in-game console, I can however start a game session. Another OSD appears and states that the mouse pointer is locked to its current position. Most of the time it works just fine, it is perfectly possible to play and returning to the menu unlocks the in-game cursor, yay :) However, sometimes the pointer isn't locked to its position and it is impossible to reliably move around in the game. - I also experienced an issue with NetRadiant, an open-source map editor for games based on Quake engines. You can move around a 3D or 2D view of a map by right-clicking in the chosen view, then moving the mouse (see the attached screenshot). A Kwin OSD states that the pointer is locked when you right-click on it, everything works fine in that regard. However, when the right mouse button is released, the pointer is not unlocked, and you have to press "Escape" for 3 seconds. It is a big usability issue, because you often switch from one view to another. On the Plasma X11 session, everything works fine, as there are no OSDs and no need to press "Escape" during 3 seconds to unlock the cursor. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 385627] GTK2 scrollbars look weird
https://bugs.kde.org/show_bug.cgi?id=385627 Yannick <leguen.yann...@gmail.com> changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 385627] GTK2 scrollbars look weird
https://bugs.kde.org/show_bug.cgi?id=385627 --- Comment #2 from Yannick <leguen.yann...@gmail.com> --- Actually the scrollbar goes a bit beyond its frame, hence the weird look. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 385627] GTK2 scrollbars look weird
https://bugs.kde.org/show_bug.cgi?id=385627 --- Comment #1 from Yannick <leguen.yann...@gmail.com> --- Created attachment 108288 --> https://bugs.kde.org/attachment.cgi?id=108288=edit scrollbar highlighted by mouse cursor -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 385627] New: GTK2 scrollbars look weird
https://bugs.kde.org/show_bug.cgi?id=385627 Bug ID: 385627 Summary: GTK2 scrollbars look weird Product: Breeze Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: gtk theme Assignee: scionicspec...@gmail.com Reporter: leguen.yann...@gmail.com Target Milestone: --- Created attachment 108287 --> https://bugs.kde.org/attachment.cgi?id=108287=edit scrollbar at the bottom extremity After upgrading to Plasma 5.11.0, I noticed weird scrollbars on GTK2 apps using the breeze-gtk theme. When a scrollbar is at the very top or bottom of a window, it looks like you can still scroll a bit. Hovering the mouse cursor over it displays it correctly, though :) See screenshots in attachment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384172] Status information glitches on Plasma task manager
https://bugs.kde.org/show_bug.cgi?id=384172 --- Comment #6 from Yannick <leguen.yann...@gmail.com> --- Something else: it seems to happen on the tasks that are on the left of the Dolphin tasks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384172] Status information glitches on Plasma task manager
https://bugs.kde.org/show_bug.cgi?id=384172 --- Comment #5 from Yannick <leguen.yann...@gmail.com> --- (In reply to Kai Uwe Broulik from comment #3) > Haven't experienced that yet. In fact, I don't even get the badge with the > number here :/ I did some further testing, and I think the issue only happens when "Show only tasks from the current desktop" is disabled. I made several file transfers to an USB drive with this option enabled, and I couldn't reproduce the issue. As soon as I disabled this option, the badges appeared on the wrong tasks again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384172] Status information glitches on Plasma task manager
https://bugs.kde.org/show_bug.cgi?id=384172 --- Comment #2 from Yannick <leguen.yann...@gmail.com> --- (In reply to Eike Hein from comment #1) > Kai? Huh? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384172] New: Status information glitches on Plasma task manager
https://bugs.kde.org/show_bug.cgi?id=384172 Bug ID: 384172 Summary: Status information glitches on Plasma task manager Product: plasmashell Version: 5.10.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: leguen.yann...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 107587 --> https://bugs.kde.org/attachment.cgi?id=107587=edit Taskbar screenshot with the glitches When the taskbar option "Show progress and status information in task buttons" is checked, wrong progress indicators are often displayed in taskbar entries after a file transfer with Dolphin. These glitches appear after the file transfer has ended, and remain visible until I close the window. I could reproduce this bug on an ArchLinux machine + another one with KDE Neon. See the screenshot in attachment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383058] kwin sometimes segfaults while Alt+tabbing
https://bugs.kde.org/show_bug.cgi?id=383058 --- Comment #3 from Yannick <leguen.yann...@gmail.com> --- Ok, no problem :> Hopefully, Mesa 17.2 will fix it. In the meantime, setting the Alt+Tab style to "large icons" (with no thumbnail at all) looks like a good workaround. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383058] kwin sometimes segfaults while Alt+tabbing
https://bugs.kde.org/show_bug.cgi?id=383058 --- Comment #1 from Yannick <leguen.yann...@gmail.com> --- I didn't have this problem when I was using an nvidia discrete GPU, or intel graphics. It happens since I switched to an AMD discrete GPU. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383058] New: kwin sometimes segfaults while Alt+tabbing
https://bugs.kde.org/show_bug.cgi?id=383058 Bug ID: 383058 Summary: kwin sometimes segfaults while Alt+tabbing Product: kwin Version: 5.10.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leguen.yann...@gmail.com Target Milestone: --- Application: kwin_x11 (5.10.4) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was alt-tabbing between applications (with the "thumbnail" alt-tab style, not sure I translate this word correctly here). I released the Alt+tab keys, but the "thumbnails" remained on the screen for a few seconds, then kwin crashed. It happens from time to time, it's quite hard to reproduce. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f618aea4840 (LWP 578))] Thread 11 (Thread 0x7f614b427700 (LWP 681)): #0 0x7f61839cf1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f6186d5db04 in () at /usr/lib/libQt5Script.so.5 #2 0x7f6186d5db49 in () at /usr/lib/libQt5Script.so.5 #3 0x7f61839c9049 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f618a837f0f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f614c429700 (LWP 679)): #0 0x7f61839cf1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f615752050c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f6157520218 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f61839c9049 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f618a837f0f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f614cc2a700 (LWP 678)): #0 0x7f61839cf1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f615752050c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f6157520218 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f61839c9049 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f618a837f0f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f6154d27700 (LWP 677)): #0 0x7f61839cf1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f615752050c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f6157520218 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f61839c9049 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f618a837f0f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f6155528700 (LWP 676)): #0 0x7f61839cf1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f615752050c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f6157520218 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f61839c9049 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f618a837f0f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f6155f2e700 (LWP 675)): #0 0x7f61839cf1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f615752050c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f6157520218 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f61839c9049 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f618a837f0f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f615672f700 (LWP 674)): #0 0x7f61839cf1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f615752050c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f6157520218 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f61839c9049 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f618a837f0f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f6163576700 (LWP 661)): #0 0x7f618a82df76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f6187e3eba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f6187e4033f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f6187de6ffb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6187c0040e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f61824cb1d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f6187c0515b in () at /usr/lib/libQt5Core.so.5 #7 0x7f61839c9049 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f618a837f0f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f616aca4700 (LWP 616)): #0 0x7f618a82df76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f6187e3eba3 in qt_safe_poll(pollfd*, unsigned long,
[kwin] [Bug 382485] OpenGL 2 compositing setup failed
https://bugs.kde.org/show_bug.cgi?id=382485 --- Comment #6 from Yannick <leguen.yann...@gmail.com> --- Ok, forget what I said in my previous comment... I just had the same issue with the OpenGL 3.1 backend (starting Steam will disable kwin compositing, and it won't enable it again). -- You are receiving this mail because: You are watching all bug changes.
