[kdeconnect] [Bug 487719] kdeconnect's mdns server causes naming conflicts with avahi-daemon
https://bugs.kde.org/show_bug.cgi?id=487719 --- Comment #1 from Kelvie Wong --- Turns out you can disable MDNS from the build, for arch users I made a pkgbuild here: https://aur.archlinux.org/packages/kdeconnect-no-mdns I also updated the avahi wiki page. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 487719] New: kdeconnect's mdns server causes naming conflicts with avahi-daemon
https://bugs.kde.org/show_bug.cgi?id=487719 Bug ID: 487719 Summary: kdeconnect's mdns server causes naming conflicts with avahi-daemon Classification: Applications Product: kdeconnect Version: 24.05.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: kel...@kelvie.ca CC: andrew.g.r.hol...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY kdeconnect listens to the mdns port and runs an mdns server, which conflicts with avahi-daemon -- whenever I run both, and come up from sleep, my hostname becomes hostname-2.local, due to a "Host name conflict, retrying with myhostname-2" STEPS TO REPRODUCE 1. Install kdeconnect 2. Install avahi daemon 3. Put computer to sleep and back up (I suspect I can just turn networking on and off) OBSERVED RESULT avahi-daemon freaks out about having multiple mdns stacks on the same machine: May 28 19:13:55 kelvie-lws avahi-daemon[441170]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** May 28 19:13:55 kelvie-lws avahi-daemon[441170]: *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** kdeconnect also has these log lines, not sure if they're related: May 28 19:14:38 kelvie-lws kdeconnectd[418933]: 2024-05-28T19:14:38 kdeconnect.core: Error sending MDNS query response May 28 19:14:38 kelvie-lws kdeconnectd[418933]: 2024-05-28T19:14:38 kdeconnect.core: Error sending MDNS query response May 28 19:14:38 kelvie-lws kdeconnectd[418933]: 2024-05-28T19:14:38 kdeconnect.core: Error sending MDNS query response EXPECTED RESULT To be able to use kdeconnect without losing my original mdns name from avahi-daemon SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 Kelvie Wong changed: What|Removed |Added CC||kel...@kelvie.ca -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486535] kwin_wayland starts consuming a high amount of CPU
https://bugs.kde.org/show_bug.cgi?id=486535 Kelvie Wong changed: What|Removed |Added CC||kel...@kelvie.ca -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 470474] new nvidia beta driver (535 series) not showing statistics
https://bugs.kde.org/show_bug.cgi?id=470474 Kelvie Wong changed: What|Removed |Added CC||kel...@kelvie.ca -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466504] External touchscreen monitor maps to wrong monitor (in wayland and X11)
https://bugs.kde.org/show_bug.cgi?id=466504 Kelvie Wong changed: What|Removed |Added Resolution|--- |NOT A BUG Status|ASSIGNED|RESOLVED --- Comment #4 from Kelvie Wong --- As mentioned in the PR comments, apparently there was a toucscreen KCM module that allows this assignment, I just didn't think to look. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466504] External touchscreen monitor maps to wrong monitor (in wayland and X11)
https://bugs.kde.org/show_bug.cgi?id=466504
--- Comment #2 from Kelvie Wong ---
Ultimately, I think we need a way for a user to choose and save the input ->
output mapping (probably a job for kscreen?) but in the meantime, perhaps we
can change the check here
(https://invent.kde.org/plasma/kwin/-/blob/6745cb87ecb57669389df3925f8e1660b8a637ad/src/backends/libinput/connection.cpp#L612-617)
:
auto testScreenMatches = [device](const Output *output) {
const auto = device->size();
const auto = output->physicalSize();
return std::round(size.width()) == std::round(screenSize.width())
&& std::round(size.height()) ==
std::round(screenSize.height());
};
To allow a 5% (or some other value) margin of error in the height and width?
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 466504] External touchscreen monitor maps to wrong monitor (in wayland and X11)
https://bugs.kde.org/show_bug.cgi?id=466504 Kelvie Wong changed: What|Removed |Added Product|KScreen |kwin Assignee|kscreen-bugs-n...@kde.org |kwin-bugs-n...@kde.org Component|common |libinput --- Comment #1 from Kelvie Wong --- Just took a look, and it seems like the code that assigns this is in kwin: kwin/src/backens/libinput/connection.cpp, Connection::applyScreenToDevice The touchscreen geometry doesn't seem to match the libinput device geometry for this touchscreen. For the record, libinput list-devices has the touchscreen at 309x174mm, and xrandr has the display listed at 310x180mm (measured it and it's definitely closer to 309x174) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466504] New: External touchscreen monitor maps to wrong monitor (in wayland and X11)
https://bugs.kde.org/show_bug.cgi?id=466504 Bug ID: 466504 Summary: External touchscreen monitor maps to wrong monitor (in wayland and X11) Classification: Plasma Product: KScreen Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kel...@kelvie.ca 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 *** STEPS TO REPRODUCE 1. Connect an external monitor with touchscreen via USB-C / DP alt mode (or via USB for the input device, and HDMI for the display) 2. Extend the desktop to the external touchscreen monitor OBSERVED RESULT The touchscreen input gets mapped to the wrong monitor EXPECTED RESULT The touchscreen input device should be mapped to just the touchscreen display. Or at least this should be configurable, since it's basically impossible to detect what touchscreen belongs to what monitor (although there are heuristics, such as both plugged in at nearly the same time) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-arch1-1 (64-bit) ADDITIONAL INFORMATION lsusb shows the touchscreen as: Bus 005 Device 025: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen kscreen-doctor shows: ~ kscreen-doctor -o Output: 1 eDP-1 enabled connected priority 2 Panel Modes: 0:2256x1504@60*! 1:2256x1504@48 2:1600x1200@60 3:1280x1024@60 4:1024x768@60 5:1920x1200@60 6:1280x800@60 7:1920x1080@60 8:1600x900@60 9:1368x768@60 10:1280x720@60 Geometry: 1920,0 1805x1203 Scale: 1.25 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 2 DP-4 enabled connected priority 1 DisplayPort Modes: 0:3840x2160@60*! 1:3840x2160@50 2:3840x2160@30 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25 6:3840x2160@24 7:3840x2160@24 8:2560x1440@60 9:1920x1080@60 10:1920x1080@60 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60 14:1920x1080@50 15:1920x1080@30 16:1920x1080@30 17:1920x1080@25 18:1920x1080@24 19:1920x1080@24 20:1400x1050@60 21:1280x1024@60 22:1440x900@60 23:1280x960@60 24:1280x720@60 25:1280x720@60 26:1280x720@60 27:1280x720@50 28:1280x720@30 29:1280x720@30 30:1280x720@25 31:1280x720@24 32:1280x720@24 33:1024x768@60 34:800x600@60 35:720x480@60 36:720x480@60 37:720x480@60 38:720x480@60 39:640x480@60 40:640x480@60 41:640x480@60 42:1600x1200@60 43:1280x1024@60 44:1024x768@60 45:2560x1600@60 46:1920x1200@60 47:1280x800@60 48:3200x1800@60 49:2880x1620@60 50:2560x1440@60 51:1920x1080@60 52:1600x900@60 53:1368x768@60 54:1280x720@60 Geometry: 0,0 1920x1080 Scale: 2 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic where DP-4 is the touchscreen monitor I want to map it to, but it always maps to eDP-1 (and on another system it mapped to DP-2 instead of HDMI-0 like it was supposed to) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 447811] Spectacle when run with "-bcr" on the commandline always saves a file
https://bugs.kde.org/show_bug.cgi?id=447811 --- Comment #2 from Kelvie Wong --- I know it didn't do this before, one of the recent upgrades (at least to me) made it start doing it. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 447811] New: Spectacle when run with "-bcr" on the commandline always saves a file
https://bugs.kde.org/show_bug.cgi?id=447811 Bug ID: 447811 Summary: Spectacle when run with "-bcr" on the commandline always saves a file Product: Spectacle Version: 21.08.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: kel...@kelvie.ca CC: k...@david-redondo.de 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 *** STEPS TO REPRODUCE 1. Run `spectacle -bcr` in the commandline, to take a rectangular area, and copy it to the clipboard without prompts. 2. Select a rectangular area OBSERVED RESULT The screenshot is in the clipboard, but it is also saved in ~/Pictures (which is my default save location, but I do not have spectacle configured to auto save screenshots) EXPECTED RESULT There not be a PNG file in my ~/Pictures directory, just the clipboard. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 21.10 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421316] Crash in ContainmentInterface::addContainmentActions() when right-clicking on desktop
https://bugs.kde.org/show_bug.cgi?id=421316 Kelvie Wong changed: What|Removed |Added CC||kel...@kelvie.ca --- Comment #11 from Kelvie Wong --- I think I found an easy way to reproduce this -- just switch the desktop wallpaper plugin from slideshow (which adds context menu items) -> back to "Image", and right click the desktop. It appears the slideshow plugin adds context menu QActions, but there is a dangling reference to them after the plugin gets cleaned up when it switches back to "Image". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget with QSG_RENDER_LOOP=basic
https://bugs.kde.org/show_bug.cgi?id=368838 Kelvie Wong changed: What|Removed |Added CC||kel...@ieee.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380865] kwin_x11 freezes with 100% CPU when using Desktop Grid with Present Windows and Fill Gaps enabled
https://bugs.kde.org/show_bug.cgi?id=380865 Kelvie Wong <kel...@ieee.org> changed: What|Removed |Added Summary|kwin_x11 freezes with 100% |kwin_x11 freezes with 100% |CPU when using Desktop Grid |CPU when using Desktop Grid |with Present Windows|with Present Windows and ||Fill Gaps enabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380865] kwin_x11 freezes with 100% CPU when using Desktop Grid with Present Windows
https://bugs.kde.org/show_bug.cgi?id=380865 --- Comment #3 from Kelvie Wong <kel...@ieee.org> --- OK, I did some further digging. In PresentWindowsEffect::calculateWindowTransformationNatural, near the end, there is a do-while loop (if "Fill Gaps" is enabled); it seems to loop on and on, and doesn't ever exit this loop for several minutes, as mentioned by Mr. Kauffmann above. I turned off "Fill Gaps" to fix this, but someone should take a look at the algorithm. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380865] kwin_x11 freezes with 100% CPU when using Desktop Grid with Present Windows
https://bugs.kde.org/show_bug.cgi?id=380865 Kelvie Wong <kel...@ieee.org> changed: What|Removed |Added CC||kel...@ieee.org --- Comment #1 from Kelvie Wong <kel...@ieee.org> --- Created attachment 106103 --> https://bugs.kde.org/attachment.cgi?id=106103=edit two backtraces on all threads on kwin_x11 while it's frozen, I let it run for a few seconds before taking the second one -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354934] crash after connecting external screen
https://bugs.kde.org/show_bug.cgi?id=354934 --- Comment #4 from Kelvie Wong <kel...@ieee.org> --- This is on qt 5.5.1, and kde 5.17 (built on the 27th of dec, from the ubuntu unstable ci ppa) -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354934] crash after connecting external screen
https://bugs.kde.org/show_bug.cgi?id=354934 Kelvie Wong <kel...@ieee.org> changed: What|Removed |Added CC||kel...@ieee.org --- Comment #3 from Kelvie Wong <kel...@ieee.org> --- Created attachment 96370 --> https://bugs.kde.org/attachment.cgi?id=96370=edit Stacktrace with ScreenLocker entry I have this problem as well -- I use nightly build PPAs; this happens with almost exactly the same setup External monitor (I typically set my desktop to only display on the external display) over displayport. Trivially reproducable (on a Dell laptop) by locking the screen whilst using the external display, and turning off the external monitor (which is the primary desktop). Attaching a stacktrace as well. -- You are receiving this mail because: You are watching all bug changes.
