<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sean Gillies (Posts about bluetooth)</title><link>https://sgillies.net/</link><description></description><atom:link href="https://sgillies.net/tags/bluetooth.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 31 Dec 2023 01:26:21 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Linux on the desktop, stabilized</title><link>https://sgillies.net/2019/03/20/linux-on-the-desktop-solved.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;I've turned off Bluetooth on my Thinkpad and replaced my Bluetooth keyboard and
mouse with wireless USB units: a cheap Logitech K360 compact keyboard and M325
mouse.  After 3 days there is no sign of the &lt;a class="reference external" href="https://sgillies.net/2019/03/17/linux-on-the-desktop.html"&gt;memory leaks&lt;/a&gt; that I wrote
about on Sunday. The clue that Bluetooth, or these particular devices, might be
implicated was the presence of a gsd-wacom process at the top of top's
memory-sorted table. I've no Wacom device, but I associate them with Bluetooth.
Removing Bluetooth devices from my workplace hasn't fixed the bug in Gnome or
the device driver, but the bug is now dormant. I'm moving on.&lt;/p&gt;</description><category>bluetooth</category><category>gnome</category><category>keyboard</category><category>linux</category><category>mouse</category><category>usb</category><category>work</category><guid>https://sgillies.net/2019/03/20/linux-on-the-desktop-solved.html</guid><pubDate>Wed, 20 Mar 2019 16:57:39 GMT</pubDate></item></channel></rss>