[systemsettings] [Bug 417615] Option to disable kdeconnect
https://bugs.kde.org/show_bug.cgi?id=417615 Forest changed: What|Removed |Added CC||fores...@sonic.net --- Comment #10 from Forest --- +1 for adding the option on a per-user basis. It's not just a matter of convenience; the lack of this option breaks KDE Connect on my multiuser system: As soon as a second desktop session is started, the new kdeconnectd instance seems to steal the Android app's attention, leaving it unable to communicate with the first paired instance. I tried copying /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop to the second user's ~/.config/autostart/ and adding Hidden=true, as specified in the freedesktop spec. It didn't help. I tried renaming /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop. It didn't help. I searched for a systemd --user unit that I could disable. I didn't find one. This really should be a per-user option, listed in Background Services along with all the others. In the meantime, I would appreciate a workaround, if somebody knows of one. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417615] Option to disable kdeconnect
https://bugs.kde.org/show_bug.cgi?id=417615 --- Comment #11 from Forest --- > unable to communicate with the first paired instance The word "paired" should have been in parentheses. I don't know what ate them. To be clear, only one user has paired KDE Connect with the Android app, yet the second user's kdeconnectd instance makes the first instance stop working. Unless there's another way to fix this, I think I need a way to disable kdeconnectd for the second user. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449727] Cannot uninstall newly installed Plasma Style (not active currently)
https://bugs.kde.org/show_bug.cgi?id=449727 --- Comment #4 from Forest --- Yes. I reproduced it with several different themes. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] In a VM, screen will not wake up after Screen Energy Saving activates due to Powerdevil crashing
https://bugs.kde.org/show_bug.cgi?id=465399 --- Comment #7 from Forest --- Another log capture with slightly different messages: Feb 13 04:38:14 neon pulseaudio[1306]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Feb 13 04:48:08 neon org_kde_powerdevil[1526]: org.kde.kscreen.dpms: Failed to query DPMS state, cannot trigger Feb 13 04:48:08 neon org_kde_powerdevil[1526]: XIO: fatal IO error 2 (No such file or directory) on X server ":0" Feb 13 04:48:08 neon org_kde_powerdevil[1526]: after 367 requests (366 known processed) with 0 events remaining. Feb 13 04:48:08 neon org_kde_powerdevil[1526]: The X11 connection broke: Unsupported extension used (code 2) Feb 13 04:48:08 neon systemd[1298]: plasma-powerdevil.service: Main process exited, code=exited, status=1/FAILURE Feb 13 04:48:08 neon systemd[1298]: plasma-powerdevil.service: Failed with result 'exit-code'. Feb 13 04:48:09 neon systemd[1298]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 1. Feb 13 04:48:09 neon systemd[1298]: Stopped Powerdevil. Feb 13 04:48:09 neon systemd[1298]: Starting Powerdevil... Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.kscreen.dpms: DPMS extension not available Feb 13 04:48:09 neon systemd[1298]: Started Powerdevil. Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: Handle button events action could not check for screen configuration Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: The profile "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464869] Installing updates corrupts Grub 2 ( unbootable system)
https://bugs.kde.org/show_bug.cgi?id=464869 Forest changed: What|Removed |Added CC|fores...@sonic.net | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433059] "Active/Inactive Titlebar" colors are visible and editable but confusingly unused when Header colors are present
https://bugs.kde.org/show_bug.cgi?id=433059 Forest changed: What|Removed |Added CC||fores...@sonic.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433059] "Active/Inactive Titlebar" colors are visible and editable but confusingly unused when Header colors are present
https://bugs.kde.org/show_bug.cgi?id=433059 --- Comment #14 from Forest --- Worth noting: Plasma 5.20 (which is currently used in Debian Stable) has a built-in theme with clearly different active/inactive window titlebar colors, called Breeze High Contrast. That theme is gone in Plasma 5.26.90, which suggests that people upgrading to the new release will be faced with a sudden loss of functionality, and those who try to fix it through custom colors will be frustrated to find that the customization doesn't actually work. I doubt most of them will find there way here to discover the workaround. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455809] Option "Make window titlebars accent-colored" is slightly inaccurate when applied to header-color-using color schemes
https://bugs.kde.org/show_bug.cgi?id=455809 Forest changed: What|Removed |Added CC||fores...@sonic.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465353] New: Please decouple title bar color from header color
https://bugs.kde.org/show_bug.cgi?id=465353 Bug ID: 465353 Summary: Please decouple title bar color from header color Classification: Applications Product: systemsettings Version: 5.26.90 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: fores...@sonic.net CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- Color schemes that define Header colors, such as the Breeze Dark scheme, currently break some of the color settings: - The "Make window titlebars accent-colored" option changes not only the title bar, but also the tool bar and the menu bar. It paints a surprisingly large window area in that color, which can be overwhelming, especially when the accent color has high contrast with the rest of the scheme. - The colored area becomes inconsistent between windows, depending on how large their header area is, and whether they have one at all. - The "Active Titlebar" color setting simply doesn't work. Moreover, it means users cannot get the traditional title-bar-only active window coloring (which many people expect from a window manager) from the default color schemes. That includes the only dark theme that Plasma currently offers. STEPS TO REPRODUCE 1. Choose the Breeze Dark color scheme. 2a. Edit it, enabling the "make window titlebars accent-colored" option. 2b. Alternatively, change the "Active Titlebar" color. 3. Save and apply the scheme. OBSERVED RESULT Either (2a) a large area outside the title bar is painted in the accent color, or (2b) the title bar color is not changed at all. EXPECTED RESULT The active title bar color should have changed according to the chosen options. Areas outside the title bar should not have changed. The title bar is used for different things than the menu bar and tool bar. Their colors should not be coupled. Perhaps it would make sense to split the "accent-colored" option into two separate options, one for the title bar and one for the header area? SOFTWARE/OS VERSIONS Linux: KDE Neon Testing: neon-testing-20230205-0738 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Related: bug 433059, bug 455809 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465356] New: "Appearance" text color is not updated when switching to Breeze Dark theme
https://bugs.kde.org/show_bug.cgi?id=465356 Bug ID: 465356 Summary: "Appearance" text color is not updated when switching to Breeze Dark theme Classification: Applications Product: systemsettings Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: fores...@sonic.net Target Milestone: --- Created attachment 155991 --> https://bugs.kde.org/attachment.cgi?id=155991&action=edit screen shot SUMMARY When switching the desktop theme from Breeze to Breeze Dark, most of the System Settings app updates itself to use the new colors, but the "Appearance" text in the navigation area remains black, nearly invisible against the now-dark-grey background. STEPS TO REPRODUCE 1. Open System Settings: Quick Settings. (Assuming the default Breeze theme is already in use.) 2. Click Theme: Breeze Dark. 3. Click Apply. OBSERVED RESULT The "Appearance" text in the left-side navigation bar is nearly invisible, black on dark grey. EXPECTED RESULT The "Appearance" text should have been redrawn in a light color, just like all the other navigation text. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon neon-testing-20230205-0738 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: X11 Running in a libvirt VM. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] New: Live image: screen goes black and will not wake up after about 10 minutes idle
https://bugs.kde.org/show_bug.cgi?id=465399 Bug ID: 465399 Summary: Live image: screen goes black and will not wake up after about 10 minutes idle Classification: Plasma Product: Powerdevil Version: 5.26.90 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fores...@sonic.net CC: m...@ratijas.tk Target Milestone: --- The KDE Neon Live image session blanks the screen after sitting idle for about ten minutes. Mouse and keyboard activity do not wake it up. STEPS TO REPRODUCE 1. Boot the KDE Neon Testing live image in a virtual machine. (I used virt-manager/libvirt.) 2. Let it sit idle for about ten minutes, until the screen turns black. 3. Move the mouse or press keyboard buttons. OBSERVED RESULT The screen remains black. EXPECTED RESULT The screen should have awakened. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Testing Edition neon-testing-20230206-1112.iso Operating System: KDE neon Testing Edition KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 2 × Intel Xeon E3-12xx v2 (Ivy Bridge, IBRS) Memory: 3.8 GiB of RAM Graphics Processor: llvmpipe Manufacturer: QEMU Product Name: Standard PC (Q35 + ICH9, 2009) System Version: pc-q35-5.2 ADDITIONAL INFORMATION The OS is still running. Control+Alt+Fn can still switch between virtual consoles. Restarting sddm from another VC succeeds at killing the GUI session and starting a new one. Screen Locking: Lock screen automatically is not checked Power Management: Energy Saving: Screen Energy Saving is checked (Switch off after 10 min.) $ journalctl _UID=999 |tail Feb 07 01:26:49 neon plasmashell[1493]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" Feb 07 01:26:50 neon plasmashell[1493]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" Feb 07 01:27:01 neon pulseaudio[1308]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Feb 07 01:27:01 neon kded5[1448]: kf.bluezqt: PendingCall Error: "Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)" Feb 07 01:36:40 neon org_kde_powerdevil[1527]: org.kde.kscreen.dpms: Failed to query DPMS state, cannot trigger Feb 07 01:36:40 neon org_kde_powerdevil[1527]: XIO: fatal IO error 0 (Success) on X server ":0" Feb 07 01:36:40 neon org_kde_powerdevil[1527]: after 366 requests (365 known processed) with 0 events remaining. Feb 07 01:36:40 neon org_kde_powerdevil[1527]: The X11 connection broke: Unsupported extension used (code 2) Feb 07 01:36:59 neon systemd[1300]: app-org.kde.plasma\x2dwelcome@autostart.service: Consumed 3.884s CPU time. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] Live image: screen goes black and will not wake up after about 10 minutes idle
https://bugs.kde.org/show_bug.cgi?id=465399 --- Comment #1 from Forest --- Note: Waking the screen immediately will not reproduce the problem. Let it stay idle for 20 seconds or so after the screen turns black. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] Live image: screen goes black and will not wake up after Screen Energy Saving activates
https://bugs.kde.org/show_bug.cgi?id=465399 Forest changed: What|Removed |Added Summary|Live image: screen goes |Live image: screen goes |black and will not wake up |black and will not wake up |after about 10 minutes idle |after Screen Energy Saving ||activates -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] Live image: screen will not wake up after Screen Energy Saving activates
https://bugs.kde.org/show_bug.cgi?id=465399 Forest changed: What|Removed |Added Summary|Live image: screen goes |Live image: screen will not |black and will not wake up |wake up after Screen Energy |after Screen Energy Saving |Saving activates |activates | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465353] Please decouple title bar color from header color
https://bugs.kde.org/show_bug.cgi?id=465353 --- Comment #2 from Forest --- > No need to reiterate it here. :) Sorry if my wording made this seem like a duplicate report. I filed this one because the reports you linked seem focused on the labeling of the existing options, without addressing the issue that underlies them both: treating title bar and header area as if they were a single entity. > This is the intended behavior. Do you mean that decoupling the title bar color from the header color would be an unwelcome change, or merely that the existing color options were intended to (and correctly do) target the header area? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] Live image: screen will not wake up after Screen Energy Saving activates
https://bugs.kde.org/show_bug.cgi?id=465399 --- Comment #3 from Forest --- VM live session: bug is present VM installed: unknown (I'll try to find time to test this, but I have no ETA) Bare metal live session: bug does not occur on my hardware Bare metal installed: unknown (I do not have the spare hardware for testing this) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465353] Please decouple title bar color from header color
https://bugs.kde.org/show_bug.cgi?id=465353 --- Comment #4 from Forest --- > changing that would be unwelcome for those color schemes. Gotcha. > we also intentionally didn't add Header colors to all color schemes, or > require it or anything like that. For the record, the only dark scheme in the default set is Breeze Dark, which uses header colors. > you're welcome to keep using color schemes without Header colors (i.e. most > of them) I'm not concerned about myself here, as I have already hand edited the colors file, with good results. An average user wanting a dark scheme with traditional behavior might have a frustrating time, though. There seems to be no way in the UI to discover that a concept called Header Colors has been introduced, or that certain schemes behave differently depending on whether they support that concept. Even once discovered, the only way to find a suitable dark theme seems to be downloading and installing themes individually until one is stumbled upon. I suppose future wording changes in the UI (as tracked in those other bug reports) might address that, though. Okay, thanks for explaining your thinking. I think I've been heard. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465353] Please decouple title bar color from header color
https://bugs.kde.org/show_bug.cgi?id=465353 --- Comment #6 from Forest --- > there used to be no difference in titlebar color for active vs inactive > windows at all! > You used to have to notice the difference purely due to the lightness of the > titlebar text changing Heh... Yes, I remember. That stood out immediately when I first tried Plasma. Fortunately, there was also a Breeze High Contrast scheme that respected the global dark theme, and had a properly distinguished active title bar color. It's gone in the current version, with no built-in option to replace that behavior, which is something of a regression for us dark mode users. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465452] New: System Settings crash when applying global theme
https://bugs.kde.org/show_bug.cgi?id=465452 Bug ID: 465452 Summary: System Settings crash when applying global theme Classification: Applications Product: systemsettings Version: 5.26.90 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fores...@sonic.net Target Milestone: --- Application: systemsettings (5.26.90) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.15.0-58-generic x86_64 Windowing System: X11 Distribution: KDE neon Testing Edition DrKonqi: 5.26.90 [CoredumpBackend] -- Information about the crash: Note: This might look like a dupe of bug 446111, but that one was fixed last year. This occurred after a fresh install from today's KDE Neon live Image. System Settings crashed after this sequence of events: - Install from neon-testing-20230207-0250.iso in a libvirt VM on a magnetic hard drive*. - Open Settings app. - In Power: Energy Saving: Suspend session: enable auto-sleep after 1 min (but do not apply changes). - Navigate to Global Theme settings panel. - When prompted about unsaved settings on the previous panel, select Apply. - Select a different** global theme. - When prompted, select Apply. The crash doesn't happen every time, but I was able to trigger it again after several tries. * Magnetic hard drive might be relevant (due to slower I/O than an SSD) if this is a race condition. ** I selected Breeze Dark the first time this happened, but I don't remember which one I chose when producing the attached crash dump. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault PID: 1245 (systemsettings) UID: 1000 (user) GID: 1000 (user) Signal: 11 (SEGV) Timestamp: Tue 2023-02-07 14:35:34 PST (20min ago) Command Line: /usr/bin/systemsettings Executable: /usr/bin/systemsettings Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-systemsettings-82b884c1c66e4084a25d96e4286aa884.scope Unit: user@1000.service User Unit: app-systemsettings-82b884c1c66e4084a25d96e4286aa884.scope Slice: user-1000.slice Owner UID: 1000 (user) Boot ID: 2e6c3d6937e94353a8f2ab78e643d435 Machine ID: aec99798d54c473a96ceac8fa22bb527 Hostname: kdeneon Storage: /var/lib/systemd/coredump/core.systemsettings.1000.2e6c3d6937e94353a8f2ab78e643d435.1245.167580933400.zst (present) Disk Size: 10.9M Message: Process 1245 (systemsettings) of user 1000 dumped core. Found module linux-vdso.so.1 with build-id: dba798e3849739247caa8c4b4acc15cf5f1b3c88 Found module libkconfigplugin.so with build-id: bd18499bb7492191fe95679b0839ebebb80be2e5 Found module libnewstuffqmlplugin.so with build-id: 8bb6cc26248edc4a1bd8f7a7834232d5dcb87572 Found module libKF5Syndication.so.5abi1 with build-id: ae6c729225cbc1144632e600a9ac8b1684c7 Found module libKF5Attica.so.5 with build-id: efb9cc4b09ac9413faa4ca2a7b9f7dc50e92a427 Found module libkrdb.so with build-id: dc0f744fd506ba8c1031172f40f0c92170005fe1 Found module libKF5NewStuffCore.so.5 with build-id: 247f8c5c047bae688090c1d87a925b64f185a1c7 Found module kcm_lookandfeel.so with build-id: a372f82a4fe35834d3d23b450d4556f7d5be22d9 Found module libopus.so.0 with build-id: 53a29374ac557d631d863d9908ff5bec82f55ba5 Found module libvorbisenc.so.2 with build-id: 5d30e2a713669895dcf3b298ffed2e4ce56121e8 Found module libFLAC.so.8 with build-id: 6806864feabd1476fb33a8ed53d682d2a796ae05 Found module libapparmor.so.1 with build-id: 9a5086b338656ae4f09bf5185be82702ae724761 Found module libasyncns.so.0 with build-id: f192c4e5be41e201707cb7a5a962d43de3c675d2 Found module libsndfile.so.1 with build-id: 7b46d2dc278b6ab9f4f253351b41da721bdf0502 Found module libpulsecommon-15.99.so with build-id: 6b9dfe81acde696cd7ff73847465b46e7cf6a21b Found module libpulse.so.0 with build-id: de691d841cf5f2164859364225ce799e158d68d7 Found module libcanberra-pulse.so with build-id: c8828ee17d61d37382231346ccd33194d3a84ace Found module FrameworkIntegrationPlugin.so with build-id: dd8c6b88e1c771160653af3cafdd8f6be729d8cb Found module libxcb-res.so.0 with build-id: 0e1f4bff02f6f57a804423b071bff111616417e3 Found module KF5WindowSystemX11Plugin.so with build-id: b711d1d6b9367f167655a2ea8607493118013961 Found module powerdevilsuspendsessionaction_config.so with build-id: 96b263ddbc7807ed612d08322d3b12426325678e Foun
[neon] [Bug 464869] Installing updates with pkcon causes system to be unbootable
https://bugs.kde.org/show_bug.cgi?id=464869 Forest changed: What|Removed |Added CC||fores...@sonic.net --- Comment #1 from Forest --- I reproduced this today in a libvirt/KVM virtual machine, using neon-testing-20230207-0250.iso as the install medium. I used Discover to start the update sequence. After rebooting, I was presented with a completely black screen for a few minutes. The black screen was eventually replaced with a (Plymouth?) software update screen with a spinning gear. When the updates finished installing, it rebooted to the grub menu, as seen in the screen shot. Selecting either Neon or Advanced Options from the grub menu caused a reboot, and a return to the grub menu. Selecting memtest from the grub menu caused a system freeze. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] Live image: screen will not wake up after Screen Energy Saving activates
https://bugs.kde.org/show_bug.cgi?id=465399 Forest changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Forest --- Update: VM live session: Bug is present VM installed session: Bug is present Bare metal live session: Bug does not occur on my hardware Bare metal installed session: unknown (I do not have the spare hardware for testing this) Installed session + system updates: unknown (updates rendered system unbootable; see bug 464869) A few more things I noticed: - Since the screen blanker likes to engage while the Neon installer is doing its work, someone trying to install Neon is likely to find a an unresponsive black screen midway through, and have to start all over. - When switching to another VC and back to the desktop VC, the desktop sometimes appears for a fraction of a second before turning black. I don't know if that glimpse is the actual desktop or just a stale video buffer. Keyboard and mouse activity still don't restore it. - Sometimes, the Energy Saving settings panel opens with a translucent overlay, briefly showing a red speech bubble and this error message: "Power Management configuration module could not be loaded. The Power Management Service appears not to be running." The overlay then disappears to reveal the settings panel. - After that error overlay appears, the KDE Crash Handler triggers, reporting that org_kde_powerdevil closed unexpectedly. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] Live image: screen will not wake up after Screen Energy Saving activates
https://bugs.kde.org/show_bug.cgi?id=465399 --- Comment #5 from Forest --- Created attachment 156056 --> https://bugs.kde.org/attachment.cgi?id=156056&action=edit powerdevil stack trace -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] Screen will not wake up after Screen Energy Saving activates
https://bugs.kde.org/show_bug.cgi?id=465399 Forest changed: What|Removed |Added Summary|Live image: screen will not |Screen will not wake up |wake up after Screen Energy |after Screen Energy Saving |Saving activates|activates -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449727] Cannot uninstall newly installed Plasma Style (not active currently)
https://bugs.kde.org/show_bug.cgi?id=449727 Forest changed: What|Removed |Added CC||fores...@sonic.net --- Comment #2 from Forest --- I reproduced this on a fresh install from neon-testing-20230207-0250.iso. Steps: Settings: Appearance: Plasma Style: Get New Plasma Styles... Install one of them Close the Download New Plasma Styles window Select the new theme Apply changes Click the theme's Trash icon Apply changes A red error banner appears with this message: "Removing theme failed: Error: Plugin [...] is not installed." The style remains in the installed styles list, even after a reboot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465452] System Settings crash when applying global theme
https://bugs.kde.org/show_bug.cgi?id=465452 --- Comment #2 from Forest --- That bug is against Wayland, while I was using X11. Also, the linked commit seems to be about drag&drop, which I was not doing at all. Do you still think it's a duplicate? > fixed by a backported patch in the KDE Qt patch collection. Neon's may be > behind. I hate to waste my time investigating bugs that are already solved. Where can I find a Neon live image that includes already-committed fixes? -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 471552] With many applications, apper fails to ask for root password authentication, then fails due to lack of authentication.
https://bugs.kde.org/show_bug.cgi?id=471552 Forest changed: What|Removed |Added CC||fores...@nom.one -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415295] Unable to receive file from phone
https://bugs.kde.org/show_bug.cgi?id=415295 Forest changed: What|Removed |Added CC||fores...@nom.one -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415295] Unable to receive file from phone
https://bugs.kde.org/show_bug.cgi?id=415295 --- Comment #5 from Forest --- I just had this happen in Plasma 5.27.5 / Frameworks 5.103.0. It seems inconsistent. I'm sure it worked a month or two ago. The only thing I remember changing between then and now is applying Android security updates, which I wouldn't expect to break this feature. -- You are receiving this mail because: You are watching all bug changes.
[baloo-widgets] [Bug 423502] FileFetchJob::doStart causes intermittent gui blocks
https://bugs.kde.org/show_bug.cgi?id=423502
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #1 from Forest ---
Created attachment 148694
--> https://bugs.kde.org/attachment.cgi?id=148694&action=edit
backtrace while gwenview is hung in getxattr() call
I am experiencing this in Gwenview while paging through a directory of images
mounted by mount.cifs. As I flip from one photo to the next, it doesn't take
long before the UI locks up for about 35 seconds before finally responding
again. Both strace and gdb indicate that the hang is in a call to
getxattr("path.jpg", "user.baloo.rating", NULL, 0)
Curiously, getxattr() doesn't noticeably hang in a test program that calls it
in a loop with the same arguments, files, and mount point. I wonder what Baloo
or Gwenview might be doing to trigger the 35 second delay.
Gwenview Version: 20.12.3
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.16.0-0.bpo.4-amd64
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 417615] Option to disable kdeconnect
https://bugs.kde.org/show_bug.cgi?id=417615 --- Comment #13 from Forest --- Alternative workaround step 2, leaving system config files untouched: Copy /usr/share/dbus-1/services/org.kde.kdeconnect.service to ~/.local/share/dbus-1/services/ and change the Exec= line of the copy to Exec=/usr/bin/false When combined with step 1 of my workaround, this prevents kdeconnectd from launching in that user's sessions. It adds some clutter to the session log, as dbus-daemon complains that the executable is failing, but it gives up after several tries and seems to remain quiet after that. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417615] Option to disable kdeconnect
https://bugs.kde.org/show_bug.cgi?id=417615 --- Comment #12 from Forest --- I found some (ugly) workarounds for the unwanted kdeconnectd autostart. The process seems to be launched at session startup time from two distinct places: 1. /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop This can be disabled for individual users by copying the file to each user's ~/.config/autostart/ directory and adding Hidden=true to the [Desktop Entry] section of the copies. Alternatively, it can be disabled by default by adding a line like this to the file's [Desktop Entry] section: X-KDE-autostart-condition=kdeconnectd-autostartrc:General:Autostart:false Then, to re-enable it for a particular user, create a ~/.config/kdeconnectd-autostartrc file with Autostart=true in its [General] section. (The file name "kdeconnectd-autostartrc" is arbitrary; I chose it in hopes of avoiding conflicts with any standard files.) 2. /usr/share/dbus-1/services/org.kde.kdeconnect.service According to KDE docs*, this file tells every user's dbus session to launch kdeconnectd if something tries to contact it over d-bus. With this file in place, kdeconnectd is launched by systemd at session start even if a user disables the autostart .desktop file. The file can be moved to a backup directory to avoid this. However, I think a better fix would be to identify whatever is making org.kde.kdeconnect d-bus requests at session startup, and prevent that instead. * https://develop.kde.org/docs/use/d-bus/dbus_autostart_services/ Of course, these workarounds are hackish, and will probably revert to the normal (unwanted) behavior whenever KDE Connect package updates are installed. What we really need is for it to be configurable in the first place. Seems like a good fit for the Background Services panel. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 451375] New: SMS delivery reports are unavailable for messages sent via KDE Connect
https://bugs.kde.org/show_bug.cgi?id=451375 Bug ID: 451375 Summary: SMS delivery reports are unavailable for messages sent via KDE Connect Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: fores...@sonic.net Target Milestone: --- SUMMARY I have SMS delivery reports enabled on the LineageOS (Android) Messaging app, so a small check mark appears next to the timestamp of each message I send. This is often helpful when a mobile service operator is having internal problems or in weak cell service areas. When the check mark never appears, I know the recipient probably did not receive my message, and that I should send it again. On messages sent via the KDE Connect desktop interface, the check mark never appears, either in the LineageOS Messaging app or anywhere else as far as I can tell. This makes KDE Connect's SMS feature less reliable than picking up my phone and slowly typing out messages on the touch screen. It would be great if KDE Connect supported message delivery reports. SOFTWARE/OS VERSIONS Linux: 5.10.0 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.
[konsole] [Bug 331429] Tab title for SSH connections does not display username (%u) when using .ssh/config data
https://bugs.kde.org/show_bug.cgi?id=331429 Forest changed: What|Removed |Added CC||fores...@sonic.net --- Comment #8 from Forest --- This behavior also turns up without ~/.ssh/config, if the user just runs "ssh hostname", as is common when the remote and local username is the same. These days, I think escape sequences in the bash PS1 var are so widely used that it might be better to just let the remote shell set the tab title. This has the benefit of showing the correct remote username when su or sudo are used. To make Konsole do this, set the remote tab title format to "%w". I haven't been using other shells or many distros lately, so I don't know if %w would be a good default. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 451640] New: loses all connections when another virtual console / desktop session is active
https://bugs.kde.org/show_bug.cgi?id=451640 Bug ID: 451640 Summary: loses all connections when another virtual console / desktop session is active Product: konversation Version: 1.8.21123 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: fores...@sonic.net Target Milestone: --- SUMMARY I often switch between multiple X instances / desktop sessions, using Control+Alt+F7/F8 (or the Switch User feature of the desktop environment). When I run Konversation in session 1 and switch to session 2 for 10 minutes or so, Konversation loses its network connections. STEPS TO REPRODUCE 1. Join one or more servers & channels in Konversation. 2. Use the desktop environment's Switch User feature to enter a new desktop session. 3. Wait 11-12 minutes. 4. Switch back to the first desktop session. OBSERVED RESULT All IRC connections are lost, and channel tabs are grayed out. Message traffic during the time spent in the other session is presumably lost. When returning, Konversation begins trying to reestablish the connections, showing these message in server windows: [Error] Connection to server irc.oftc.net (port 6697) lost: The TLS/SSL connection has been closed. [Info] Trying to reconnect to irc.oftc.net (port 6697) in 10 seconds. EXPECTED RESULT Konversation should not have lost its connections or missed any message traffic while the other desktop session was active. SOFTWARE/OS VERSIONS Linux Version: 5.16.0 and 5.10.0 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Tested with Konversation packages from both Debian Stable and Debian Unstable. Problem exists in both. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451978] New: Kate Build plugin does not recognize pylint command output
https://bugs.kde.org/show_bug.cgi?id=451978 Bug ID: 451978 Summary: Kate Build plugin does not recognize pylint command output Product: kate Version: 20.12.2 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: fores...@sonic.net Target Milestone: --- SUMMARY Python programmers often run pylint to quickly find code defects. When pylint is used as a build command in Kate, the output is excluded from Kate's parsed output window. It is visible only by manually selecting the Full Output filter every time the command is run, which is not very useful, because warnings and errors are not flagged, and clicking on them does not navigate to the line where the problem was found, and the next/previous error shortcuts do not work. Pylint's output looks like this: * Module myfile /path/to/myfile:12:0: R0903: Too few public methods (1/2) (too-few-public-methods) /path/to/myfile:345:0: R0903: Too few public methods (1/2) (too-few-public-methods) -- Your code has been rated at 9.88/10 (previous run: 9.88/10, +0.00) The first space-delimited field of each warning/error line follows the format used by many C compilers: a colon-separated file path, line number, and column number. This makes it fairly easy for code editors to support. (Geany handles it nicely, for example.) The second field is a pylint message ID: A single capital letter followed by four numeric digits, then a colon. In regex: "^[CRWEF]\\d\\d\\d\\d:" Those letters indicate the message type: Convention, Refactor, Warning, Error, Fatal After that field is a human-readable message description. Subtleties: Pylint uses zero-based column numbers, while Kate seems to assume one-based column numbers. Pylint's output is on stdout, while Kate seems to assume errors and warnings will appear on stderr. STEPS TO REPRODUCE 1. Make "pylint %f" a build command in a Kate project. 2. Open a python file with some defects that pylint will detect. 3. Run the build command . OBSERVED RESULT No pylint output appears in Kate's output tab. Changing to tab's filter to "Full Output" reveals the pylint output, but it is just raw text. No distinction is made between errors, warnings, and misc. messages. Clicking the messages does not navigate to the relevant line of the python file. EXPECTED RESULT Pylint output should be parsed and clickable to navigate to the referenced line, and should respond to the Next Error / Previous Error shortcuts, just like any other compiler-style output. Ideally, it should also work with Kate's Errors/Warnings/Parsed Output filter. SOFTWARE/OS VERSIONS Linux Version: 5.16.0 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.
[Spectacle] [Bug 442876] Spectacle is quite slow in taking screenshots
https://bugs.kde.org/show_bug.cgi?id=442876 Forest changed: What|Removed |Added CC||fores...@sonic.net --- Comment #1 from Forest --- I tried setting desktop animation speed to "instant" and disabling compositing, but screen shots still have a painful delay after I press the keyboard shortcut. It was effectively instant when I used Xfce. This lag makes the KDE's screen shot feature mostly useless for gaming and video. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 442876] Spectacle is quite slow in taking screenshots
https://bugs.kde.org/show_bug.cgi?id=442876 --- Comment #2 from Forest --- I measured the lag at about 1/3 of a second, which is a lot of lost frames. Method: Pressing Kronometer's Start key and Spectacle's Capture Active Window key at the same time. This was on an idle system with ~4 GHz CPU, an SSD, and both apps recently used (and therefore probably cached in RAM). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 456840] New: Misleading screen displayed with connected device: This paired device is not reachable
https://bugs.kde.org/show_bug.cgi?id=456840 Bug ID: 456840 Summary: Misleading screen displayed with connected device: This paired device is not reachable Product: kdeconnect Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: fores...@sonic.net Target Milestone: --- SUMMARY When launching KDE Connect on Android, it often fails to show the main menu even when a device is paired and connected and responsive. Instead, it shows a screen with this message: "This paired device is not reachable. Make sure it is connected to your same network." Contrary to what the message says, I am able to read and send SMS messages from the paired device. I conclude that the message is a lie. STEPS TO REPRODUCE 1. Install & pair KDE Connect for Android. 2. Put the Android device to sleep for ~25 minutes. 3. Wake the device and launch KDE Connect. OBSERVED RESULT The above "paired device is not reachable" message is displayed. EXPECTED RESULT The main menu screen (send files, send clipboard, slideshow...) should be displayed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Bullseye KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have not removed Android's battery usage: background restriction from the KDE Connect app. I do not know if this affects the buggy behavior, but I wouldn't expect it to, since I observe the problem while the app is running in the foreground. Following a tip from another bug report, I discovered that I can clear the erroneous "paired device is not reachable" screen by opening the hamburger menu, choosing "pair new device", drag-down-pulling the "connect devices" screen to cause a refresh, send then selecting the paired device that is supposedly unreachable. This works, but is a lot of annoying steps, and not discoverable in any reasonable way. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 456893] New: need a way to disable menu animations
https://bugs.kde.org/show_bug.cgi?id=456893 Bug ID: 456893 Summary: need a way to disable menu animations Product: Haruna Version: 0.8.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: fores...@sonic.net Target Milestone: --- SUMMARY Haruna's menu bar doesn't respond to mouse movements or clicks immediately. When I move the mouse, it takes a moment for the highlight to appear on the item I moved to. When I click a menu item, it takes a moment for it to open. These delays seem to be caused by waiting for animations to complete. I find these delays and animations frustrating. They interfere with my muscle memory for navigating menus. They cause me to second guess my mouse aim. It feels like someone resized some of the stairs that I use to enter and leave my home, causing me to trip whenever I use them. They also break consistency on my desktop (since no other application does this), and by introducing lag, they make the application feel sluggish. I suggest making Haruna's menus consistent with the KDE desktop, or at least offering the option to do so. STEPS TO REPRODUCE 1. Move mouse to application menu. 2. Click a menu item. OBSERVED RESULT There is a delay before the hovered menu item is highlighted, and another delay before the clicked item opens. EXPECTED RESULT There should be no delays. (Unless perhaps the user has configured KDE to use some kind of global menu animations that deliberately introduce delays, but I have not.) SOFTWARE/OS VERSIONS Linux: Debian 11 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.
[Powerdevil] [Bug 440882] New: Screen Energy Saving does not respect SimulateUserActivity when XWayland is used
https://bugs.kde.org/show_bug.cgi?id=440882 Bug ID: 440882 Summary: Screen Energy Saving does not respect SimulateUserActivity when XWayland is used Product: Powerdevil Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fores...@sonic.net Target Milestone: --- SUMMARY The org.freedesktop.ScreenSaver SimulateUserActivity dbus method is supposed to reset screen blanking timeouts. It works for both the screen locker and the Screen Energy Saving feature when used in X.Org desktop sessions. However, in XWayland sessions, it works only for the screen locker: The Screen Energy Saving feature ignores SimulateUserActivity on XWayland, and the screen therefore powers off when it should not. STEPS TO REPRODUCE 1. Start a KDE Plasma 5 XWayland desktop session. (I used KUbuntu 21.04 in my test.) 2. In KDE Settings: Screen Energy Saving, enable the feature and set "Switch off after" to 1 minute. (Note: You might need real hardware, not a VM, for the option to appear.) 3. Start a shell script that runs the following command every few seconds: qdbus org.freedesktop.ScreenSaver /ScreenSaver SimulateUserActivity 4. Sit back for a minute waiting for the energy saving mode to activate. OBSERVED RESULT The screen powers off, ignoring the SimulateUserActivity calls. EXPECTED RESULT The screen should not power off. It should respect the SimulateUserActivity calls, just as it does in an X.Org session. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Problem exists with XWayland sessions, but not X11 sessions. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440882] Screen Energy Saving does not respect SimulateUserActivity in XWayland sessions
https://bugs.kde.org/show_bug.cgi?id=440882 Forest changed: What|Removed |Added Summary|Screen Energy Saving does |Screen Energy Saving does |not respect |not respect |SimulateUserActivity when |SimulateUserActivity in |XWayland is used|XWayland sessions -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440882] Screen Energy Saving does not respect SimulateUserActivity in XWayland sessions
https://bugs.kde.org/show_bug.cgi?id=440882 --- Comment #2 from Forest --- I don't know if it works in a full wayland session. I don't have a test environment for that. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440882] Screen Energy Saving does not respect SimulateUserActivity in XWayland sessions
https://bugs.kde.org/show_bug.cgi?id=440882 Forest changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439312] New: SimulateUserActivity doesn't unlock the screen, even unlocking without password is enabled
https://bugs.kde.org/show_bug.cgi?id=439312 Bug ID: 439312 Summary: SimulateUserActivity doesn't unlock the screen, even unlocking without password is enabled Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fores...@sonic.net CC: bhus...@gmail.com Target Milestone: --- SUMMARY The SimulateUserActivity doesn't actually simulate user activity. Once the lock screen appears, moving the mouse or pressing a key will wake the screen (so long as it's still within the "Allow unlocking without password" time). However, a call to SimulateUserActivity() at that time is ignored, leaving the screen locked. STEPS TO REPRODUCE 1. Workspace Behavior: Screen Locking: Lock screen automatically: After 1 minute 2. Workspace Behavior: Screen Locking: Allow unlocking without password for: 300 seconds 3. In a shell: sleep 70; qdbus org.freedesktop.ScreenSaver /ScreenSaver SimulateUserActivity 4. Idle for 60 seconds 5. Notice the screen locker activate 6. Continue idling for 10 more seconds 7. Notice that the screen does not wake when SimulateUserActivity is called 8. Generate actual user activity (move the mouse or press a key) and notice that the screen does wake OBSERVED RESULT Screen doesn't wake in response to SimulateUserActivity EXPECTED RESULT Screen should wake, just as it does with actual user activity SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Problem exists with Wayland and X11 sessions. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439312] SimulateUserActivity doesn't unlock the screen, even when unlocking without password is enabled
https://bugs.kde.org/show_bug.cgi?id=439312 Forest changed: What|Removed |Added Summary|SimulateUserActivity|SimulateUserActivity |doesn't unlock the screen, |doesn't unlock the screen, |even unlocking without |even when unlocking without |password is enabled |password is enabled -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439312] SimulateUserActivity doesn't unlock the screen, even when unlocking without password is enabled
https://bugs.kde.org/show_bug.cgi?id=439312 Forest changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Forest --- > "If the screensaver is not activated then the idle timers will be reset. " The precondition in that sentence is strange, because it doesn't match what happens with actual user activity. Perhaps it was an oversight? Was it written before the "Allow unlocking without password" configuration setting existed? > Can you expand on your use case? The use case is gaming. I maintain a utility called joystickwake that delays screen blankers in response to game controller input, but this issue also applies to games and emulators that would do so themselves. Scenario: - User starts playing a joystick-based game with no mouse or keyboard activity. - SimulateUserActivity events periodically reset the screen timeout. - User pauses the game, perhaps to answer a phone call. - SimulateUserActivity calls are not produced while the joystick is idle. - Screen times out & goes blank. - User notices this and moves the joystick to wake the screen. - Screen does not wake. - User now has to put down the joystick, walk across the room, use the mouse or keyboard to wake the screen, walk back across the room, and pick up the joystick, before resuming play. If SimulateUserActivity actually simulated user activity, moving the joystick would have been sufficient to wake the screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #29 from Forest --- > maybe also make the triangle filter toggleable? As it makes no sense with > categories sidebar placed on the right side. It can be reoriented such that it makes sense on either side, and the approach I'm using to put the sidebar on the right takes advantage of that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #32 from Forest --- Created attachment 161269 --> https://bugs.kde.org/attachment.cgi?id=161269&action=edit draft: Kickoff sidebar automatically on the right (Plasma 5.27) I have been working with Nate (KDE developer) to get this into a state that he's happy with For Plasma 6. The current iteration drops the config option and puts the sidebar on the right by default, unless Kickoff is in a panel on the right edge of the screen. (The config option might return, depending on how the discussion goes.) For testing purposes, here's another draft for Plasma 5. It doesn't remove the triangle filter (that would probably have to be a separate change) but I find that the triangle filter is much better behaved in this repositioned layout, so this might have the nice side effect of also helping people who dislike the filter. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #33 from Forest --- Strangely, a few people have given my merge request a thumbs-down, with no valid criticism beyond having to adapt their muscle memory to a positioning change. It seems those people think a one-time inconvenience to them outweighs the unending frustration to others that is caused by the current layout. If you want to see this fixed, I suppose it might help to add a thumbs-up vote on the the merge request's top level comment/description. Here's the link: https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1628 If you join the discussion there, please keep comments constructive, of course. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #36 from Forest --- >"Your account has been blocked. Please contact your GitLab administrator if you >think this is an error." > >Not sure why. I can login to my KDE Identity account. I suspect the bug tracker doesn't use the KDE identity server. (At least, I didn't notice a request to identity.kde.org when I logged in.) If that's true, I think you would have to create a new account. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #37 from Forest --- Er, I mean the Gitlab instance. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #40 from Forest --- Max wrote: > People who thumbed down probably are not satisfied for the same reason this > bug report was created — not having an option toggle in settings. Good point. I had updated the title to "place sidebar on the right in most cases", to reflect the config option's removal as requested by Nate. It's possible that those drive-by downvotes were reactions to the lack of choice. I wish they had used words to express themselves instead of mysteriously dumping on my work as a whole. > I believe that adding an option is the only way to make everyone happy. It is starting to look that way, isn't it? Nate already rejected that idea from me twice, so I'm not going to push him on it, but Noah (another KDE developer) recently chimed in agreeing with you. Perhaps adding your voice in support of it over there would help show that a user-facing option really is appropriate here? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Offer option to move categories sidebar to other side of main view for better usability and faster access to Favorites
https://bugs.kde.org/show_bug.cgi?id=443082 Forest changed: What|Removed |Added Attachment #160376|0 |1 is obsolete|| Attachment #161269|0 |1 is obsolete|| --- Comment #46 from Forest --- Created attachment 161592 --> https://bugs.kde.org/attachment.cgi?id=161592&action=edit Kickoff with switchable sidebar position (Plasma 5.27 version) My solution has been merged into Plasma 6. (Thanks, all!) Here's a Plasma 5.27 version for those who don't want to wait. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 383404] The content pane does not respect the Breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=383404
--- Comment #4 from Forest ---
Created attachment 159874
--> https://bugs.kde.org/attachment.cgi?id=159874&action=edit
Akregator 22.12.3 theme dark patch
Akregator 22.12.3 changed its grantleetheme HTML, so continuing to use
AlexandreBonneau's version yields tiny text. Here's a patch against the new
version.
The patch simply changes the foreground & background colors on two elements in
each of the four theme files:
body { color: white ! important; background: #232629 ! important; }
.headerbox { color: white ! important; }
--
You are receiving this mail because:
You are watching all bug changes.
[akregator] [Bug 471553] New: Mark Feeds as Read on a folder doesn't repaint article titles until the mouse moves
https://bugs.kde.org/show_bug.cgi?id=471553 Bug ID: 471553 Summary: Mark Feeds as Read on a folder doesn't repaint article titles until the mouse moves Classification: Applications Product: akregator Version: 5.22.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fores...@nom.one Target Milestone: --- SUMMARY After clicking Mark Feeds as Read, the article titles remain in the "unread" color until the mouse is moved. STEPS TO REPRODUCE 1. Navigate to a folder with unread articles. 2. Click and confirm Mark Feeds as Read. OBSERVED RESULT Affected article titles remain colored in the "unread" color until the mouse is moved. EXPECTED RESULT Article titles should be repainted in the "read" color. SOFTWARE/OS VERSIONS Linux: Debian 12 (bookworm) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFO Seems like a QWidget::update() call is needed somewhere. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461459] After startup, the default Breeze application launcher remains translucent, even if the panel it's in is set to opaque (fixes after opening any fullscreen window).
https://bugs.kde.org/show_bug.cgi?id=461459 Forest changed: What|Removed |Added CC||fores...@nom.one -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 Forest changed: What|Removed |Added CC||fores...@nom.one --- Comment #19 from Forest --- > a lot of the time users go quiet is because of fatigue. Indeed. This is why I stopped reporting systemd bugs, for example. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #20 from Forest --- > It was hoped that the triangle filter would alleviate complaints about > unintended category switching, > and so far it has done so. I'm afraid not. Here comes yet another complaint about unintended category switching, this time from a Plasma 5.27.5 user. I'm an imperfect human in a physical world, and as such, my mouse movements are not in perfect lines. When my pointer inevitably strays from the prescribed path on the way from launcher button to favorites list, this new launcher cruelly yanks my favorites out of view, replacing them with something unwanted and disorienting. This happens dozens of times per day, every day. A month of use has not made it easier. It feels like the UI is actively trying to defeat me. I'm baffled as to why someone would take a convenience tool like a favorites list, and move it out of easy reach, and furthermore place obstacles in the way. Is there a common use case for which this arrangement works well? If so, then it seems to me that an option to swap the favorites and categories positions would be an elegant compromise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #25 from Forest --- Created attachment 160376 --> https://bugs.kde.org/attachment.cgi?id=160376&action=edit Kickoff from Plasma 5.27.5, patched with configurable sidebar position I feel strongly that this should be configurable, so I decided to take on the work of making it so. In case anyone wants to test it, here's a patched version of the Kickoff plasmoid from Plasma 5.27.5, patched with a new "sidebar position" option. To install, create a $HOME/.local/share/plasma/plasmoids/org.kde.plasma.kickofftest/ directory and place the contents of this archive in it. This will not interfere with your existing launcher. This new one is called "Application Launcher (test)", and you'll have to manually add it to your panel. I plan to submit patches for both Plasma 5.27 and Plasma on Gitlab soon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #26 from Forest --- *both Plasma 5.27 and Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 Forest changed: What|Removed |Added Attachment #160376|Kickoff from Plasma 5.27.5, |draft: Kickoff from Plasma description|patched with configurable |5.27.5 with configurable |sidebar position|sidebar position -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417615] Option to disable kdeconnect
https://bugs.kde.org/show_bug.cgi?id=417615 --- Comment #15 from Forest --- (In reply to Bernd Steinhauser from comment #14) > I'd say the better fix would be to [...] > instead provide a systemd user unit that starts kdeconnect. Not everyone uses, or even wants, systemd. (Or linux, for that matter.) Please don't add dependencies on it. KDE already has way to manage things like this, with the Background Services and Autostart control panels. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425557] Plasma freezes when Compositor set to use OpenGL, both 2.1 or 3.0. No freeze with Xrender
https://bugs.kde.org/show_bug.cgi?id=425557 Forest changed: What|Removed |Added CC||fores...@sonic.net --- Comment #4 from Forest --- I may be experiencing the same problem. When it happens: - I can still move the mouse pointer. - Mouse clicks and drags are ignored. - Nothing other than the mouse pointer changes on-screen. - Keyboard input still works (shortcuts, typing text, etc.) but since no screen updates happen, it looks like nothing is happening. - Switching virtual consoles Control+Alt+F8/F7 does not clear the problem. I cannot reproduce it on demand, but when it happens, it's always when an application disables the compositor, such as when a video player switches to full screen. I can regain control of my desktop by manually re-enabling the compositor with Shift+Alt+F12. However, once the bad state has been triggered once, every subsequent attempt to disable the compositor (either by an app or with Shift+Alt+F12) freezes the desktop again. If I reboot, the compositor can once again be switched off or on without any trouble, until the problem appears again. That might take hours or days. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425557] Plasma freezes when Compositor set to use OpenGL, both 2.1 or 3.0. No freeze with Xrender
https://bugs.kde.org/show_bug.cgi?id=425557 --- Comment #5 from Forest --- Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 6.0.0-0.deb11.6-amd64 Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426937] kded5: Segmentation fault when I plug in controller with touchpad using xf86-input-libinput
https://bugs.kde.org/show_bug.cgi?id=426937 Forest changed: What|Removed |Added CC||fores...@sonic.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Forest changed: What|Removed |Added CC||fores...@sonic.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448797] Inappropriate "Low battery level" icon when only batteries come from external wireless devices
https://bugs.kde.org/show_bug.cgi?id=448797 Forest changed: What|Removed |Added CC||fores...@sonic.net -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 85624] idea: "web scraping" support (support script output as feed source)
https://bugs.kde.org/show_bug.cgi?id=85624 Forest changed: What|Removed |Added CC||fores...@sonic.net --- Comment #7 from Forest --- Yes, the desire for this feature still exists. (I'm another ex-Liferea user.) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 383404] The content pane does not respect the Breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=383404 Forest changed: What|Removed |Added CC||fores...@sonic.net --- Comment #3 from Forest --- > I modified all the files there Thanks for sharing those html files, Alexandre. I placed them in $HOME/.local/share/akregator/grantleetheme/5.2 and they make the content pane much easier on the eyes. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371130] unable to reassign standard shortcut for backspace to "up" instead of "back"
https://bugs.kde.org/show_bug.cgi?id=371130 Forest changed: What|Removed |Added CC||forestc...@ixio.org --- Comment #10 from Forest --- A cursory look at the code revealed (I think) where the hidden shortcut is being added: https://github.com/KDE/dolphin/blob/0303df092d93a39122fce82aade93d96d52430dc/src/dolphinmainwindow.cpp#L1315 +1 for fixing this. It wasted several hours of my day while I was test driving KDE, and didn't exactly instill confidence in the platform. If it's going to take a while to agree on a good UI for exposing all the shortcuts, how about swapping the "Back" and "Backspace" shortcuts for now? That ought to make the "Backspace" shortcut visible, which would avoid the surprising experience of a keyboard shortcut not appearing with all the other standard keyboard shortcuts, and the frustrating experience of a built-in conflict that seems impossible to resolve. The "Back" action usually comes from a dedicated mouse button or scroll wheel tilt, or (less commonly) from a dedicated button on a keyboard. I expect that remapping it is less common, so giving it the hidden shortcut position would seem to be the lesser evil. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451978] Kate Build plugin does not recognize pylint command output
https://bugs.kde.org/show_bug.cgi?id=451978 --- Comment #5 from Forest --- I haven't had a chance to test this. Please don't auto-close it. (FWIW, I strongly dislike auto-close bots in issue trackers.) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451978] Kate Build plugin does not recognize pylint command output
https://bugs.kde.org/show_bug.cgi?id=451978 Forest changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 --- Comment #6 from Forest --- In what release can this stdout/stderr merge be found and tested? Has the column numbering issue (0-based vs. 1-based) been addressed? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 494282] Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=494282 forest changed: What|Removed |Added CC||forest.n.john...@gmail.com --- Comment #3 from forest --- this happened to me when I plugged my laptop into the dock, opened krita, and then pressed new file. the file dialog appeared on a different monitor and I could not see it. I went to the system settings display settings page and tried adjusting the relative vertical position of the two monitors hoping that would fix the window that was off in lala land. The first time I did it it worked ok, then I re-set the two monitors vertical offset back to level and hit apply again, and thats when it crashed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401846] New: Unhandled instruction bytes: 0x48 0xF 0xC7 0xF1 0x73 0x14 0x48 0x89
https://bugs.kde.org/show_bug.cgi?id=401846 Bug ID: 401846 Summary: Unhandled instruction bytes: 0x48 0xF 0xC7 0xF1 0x73 0x14 0x48 0x89 Product: valgrind Version: 3.11.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: for...@prenav.com Target Milestone: --- SUMMARY Yet another amd instruction sequence that isn't handled vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF1 0x73 0x14 0x48 0x89 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401846] Unhandled instruction bytes: 0x48 0xF 0xC7 0xF1 0x73 0x14 0x48 0x89
https://bugs.kde.org/show_bug.cgi?id=401846 --- Comment #1 from Forest Rouse --- Looks like the stack trace is from grpc: ==2889== valgrind: Unrecognised instruction at address 0xabefcc. ==2889==at 0xABEFCC: ??? (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA6596D: RAND_bytes (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA1856E: bssl::ssl_client_handshake(bssl::SSL_HANDSHAKE*) (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA1C4FE: bssl::ssl_run_handshake(bssl::SSL_HANDSHAKE*, bool*) (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x9FD12F: SSL_do_handshake (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x62DE3D: create_tsi_ssl_handshaker (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x628D24: ssl_channel_add_handshakers (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x6588B5: grpc_handshakers_add (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x61BC87: connected (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x66AE13: grpc_exec_ctx_flush (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x673A37: pollset_work (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x669E39: grpc_pollset_work (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889== Your program just tried to execute an instruction that Valgrind ==2889== did not recognise. There are two possible reasons for this. ==2889== 1. Your program has a bug and erroneously jumped to a non-code ==2889==location. If you are running Memcheck and you just saw a ==2889==warning about a bad jump, it's probably your program's fault. ==2889== 2. The instruction is legitimate but Valgrind doesn't handle it, ==2889==i.e. it's Valgrind's fault. If you think this is the case or ==2889==you are not sure, please let us know and we'll try to fix it. ==2889== Either way, Valgrind will now raise a SIGILL signal which will ==2889== probably kill your program. ==2889== ==2889== Process terminating with default action of signal 4 (SIGILL) ==2889== Illegal opcode at address 0xABEFCC ==2889== at 0xABEFCC: ??? (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA6596D: RAND_bytes (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA1856E: bssl::ssl_client_handshake(bssl::SSL_HANDSHAKE*) (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA1C4FE: bssl::ssl_run_handshake(bssl::SSL_HANDSHAKE*, bool*) (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x9FD12F: SSL_do_handshake (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x62DE3D: create_tsi_ssl_handshaker (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x628D24: ssl_channel_add_handshakers (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x6588B5: grpc_handshakers_add (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x61BC87: connected (in /home/forest/.cache/bazel/_bazel_forest/fe
[valgrind] [Bug 401846] Unhandled instruction bytes: 0x48 0xF 0xC7 0xF1 0x73 0x14 0x48 0x89
https://bugs.kde.org/show_bug.cgi?id=401846 --- Comment #2 from Forest Rouse --- ==2889== valgrind: Unrecognised instruction at address 0xabefcc. ==2889==at 0xABEFCC: ??? (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA6596D: RAND_bytes (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA1856E: bssl::ssl_client_handshake(bssl::SSL_HANDSHAKE*) (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA1C4FE: bssl::ssl_run_handshake(bssl::SSL_HANDSHAKE*, bool*) (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x9FD12F: SSL_do_handshake (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x62DE3D: create_tsi_ssl_handshaker (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x628D24: ssl_channel_add_handshakers (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x6588B5: grpc_handshakers_add (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x61BC87: connected (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x66AE13: grpc_exec_ctx_flush (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x673A37: pollset_work (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x669E39: grpc_pollset_work (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889== Your program just tried to execute an instruction that Valgrind ==2889== did not recognise. There are two possible reasons for this. ==2889== 1. Your program has a bug and erroneously jumped to a non-code ==2889==location. If you are running Memcheck and you just saw a ==2889==warning about a bad jump, it's probably your program's fault. ==2889== 2. The instruction is legitimate but Valgrind doesn't handle it, ==2889==i.e. it's Valgrind's fault. If you think this is the case or ==2889==you are not sure, please let us know and we'll try to fix it. ==2889== Either way, Valgrind will now raise a SIGILL signal which will ==2889== probably kill your program. ==2889== ==2889== Process terminating with default action of signal 4 (SIGILL) ==2889== Illegal opcode at address 0xABEFCC ==2889== at 0xABEFCC: ??? (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA6596D: RAND_bytes (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA1856E: bssl::ssl_client_handshake(bssl::SSL_HANDSHAKE*) (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0xA1C4FE: bssl::ssl_run_handshake(bssl::SSL_HANDSHAKE*, bool*) (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x9FD12F: SSL_do_handshake (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x62DE3D: create_tsi_ssl_handshaker (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x628D24: ssl_channel_add_handshakers (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x6588B5: grpc_handshakers_add (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe/backend/proton/proton) ==2889==by 0x61BC87: connected (in /home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__mai
[valgrind] [Bug 401846] Unhandled instruction bytes: 0x48 0xF 0xC7 0xF1 0x73 0x14 0x48 0x89
https://bugs.kde.org/show_bug.cgi?id=401846 --- Comment #3 from Forest Rouse --- Created attachment 116728 --> https://bugs.kde.org/attachment.cgi?id=116728&action=edit Valgrind log file -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401846] vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF1 0x73 0x14 0x48 0x89
https://bugs.kde.org/show_bug.cgi?id=401846 Forest Rouse changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #5 from Forest Rouse --- Thanks. I should have suspected that this bug in fact covered what I reported as obviously only the instruction needs to be the same. I built the latest version manually instead of using what is the default version I pulled from apt and that solved the problem. -- You are receiving this mail because: You are watching all bug changes.
