[Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
I also have this issue on a Thinkpad T14s, AMD Ryzen 7 PRO 4750U. The issue is not present with kernels 5.9.10 or 5.15.23. It is present with the default kernel from the most recent KDE Neon (5.13). Here's a short video, it's the same pattern (static and vertical lines on the right) as the other video in this thread: https://twitter.com/tlhunter/status/1493107390731874305 The pattern is reminiscent to an HDMI desync issue but the vertical lines do make it distinct. It appeared to affect the laptop screen but not an external display. The static appeared after the screen went to sleep and woke back up, though I don't believe the system went to sleep. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930541] Re: Maven 3.6.3-1 fails to run with OpenJDK 16
Please fix it ASAP! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930541 Title: Maven 3.6.3-1 fails to run with OpenJDK 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maven/+bug/1930541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936261] [NEW] Session creation inhibited when trying to connect to VNC server after Ubuntu 21.04 upgrade
Public bug reported: After upgrading to Ubuntu 21.04 from 20.10, connecting to VNC server will not work from some clients. Prompts for password, then the client gives the error message "The connection closed unexpectedly." Gnome- remote-desktop package gives the following error message in syslog: > gnome-remote-de[111245]: Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Session creation inhibited ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936261 Title: Session creation inhibited when trying to connect to VNC server after Ubuntu 21.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1936261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934697] [NEW] Default keyring password keeps resetting if set to empty
Public bug reported: My system (on which I'm the only user) has full-disk encryption turned on, and I thus have the same password for both the encryption password and my user account. Likewise, I have automatic login turned on so I don't have to type my password twice, as it would be quite redundant. With automatic login turned on, I thus changed my password for my default keyring to be nothing, as one, the security of full-disk encryption solves all of the needs that a keyring password would for me, and two, I'd like to not have to enter my keyring password every time I boot. Issue is that for some strange reason the keyring password miraculously keeps resetting to the password of my user account. I don't know why, I don't know how, but it's been happening for at least the past couple of months, awaiting me to make an Ubuntu One account so I could report the issue. The machine that's affected has been wiped at least three times over the past few months (due to various reasons), and the issue has also happened on another machine I was temporarily using at one point. --- OS Version: Ubuntu 20.04.2 LTS Package Version: 3.36-1 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Description changed: My system (on which I'm the only user) has full-disk encryption turned on, and I thus have the same password for both the encryption password and my user account. Likewise, I have automatic login turned on so I don't have to type my password twice, as it would be quite redundant. With automatic login turned on, I thus changed my password for my - default keyring to be nothing, as the security of full-disk encryption - solves all of the needs that a keyring password would for me. + default keyring to be nothing, as one, the security of full-disk + encryption solves all of the needs that a keyring password would for me, + and two, I'd like to not have to enter my keyring password every time I + boot. Issue is that for some strange reason the keyring password miraculously keeps resetting to the password of my user account. I don't know why, I don't know how, but it's been happening for at least the past couple of months, awaiting me to make an Ubuntu One account so I could report the issue. The machine that's affected has been wiped at least three times over the past few months (due to various reasons), and the issue has also happened on another machine I was temporarily using at one point. --- OS Version: Ubuntu 20.04.2 LTS Package Version: 3.36-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934697 Title: Default keyring password keeps resetting if set to empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1934697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631169] Re: doxygen-jquery.patch modification misapplied to dynsection.js
I'm not sure who's maintaining these issues, but I've changed this to fix released per the previous comment. ** Changed in: doxygen (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631169 Title: doxygen-jquery.patch modification misapplied to dynsection.js To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/doxygen/+bug/1631169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916325] Re: Overly strict NAME_REGEX rejects valid hostnames
** Changed in: subiquity (Ubuntu) Assignee: (unassigned) => Jonathan Hunter (jmhunter) ** Changed in: subiquity (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916325 Title: Overly strict NAME_REGEX rejects valid hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1916325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916325] Re: Overly strict NAME_REGEX rejects valid hostnames
Thank you Ryan - much appreciated. I have created a pull request against subiquity, it's my first one but hope it is OK :) https://github.com/canonical/subiquity/pull/914 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916325 Title: Overly strict NAME_REGEX rejects valid hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1916325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916325] [NEW] Overly strict NAME_REGEX rejects valid hostnames
Public bug reported: All our servers' hostnames start with a location identifier, which is mostly numeric e.g. 123, 124 or sometimes 12A. A full hostname might be 12a-proxy-01.mydomain.co.uk, for example. We are switching to Ubuntu but have hit this bug in the 20.04 curtin installer, which prevents us setting the hostname during installation. (Tested on plain 20.04 and on 20.04.02) Our workaround has been to set a dummy hostname on installation, and then change it back once curtin has finished - but that gets messy especially as we are now looking into cloud-init and automation, where this won't work. The NAME_REGEX quoted by curtin is "[a-z_][a-z0-9_-]*" which correctly prevents hostnames starting with a hyphen.. but it also prevents otherwise perfectly valid hostnames that start with a number. (Interestingly, an underscore is not defined as a valid hostname character, but is included as valid in the regex above) I believe the correct NAME_REGEX would be "[a-z0-9_][a-z0-9_-]*" - i.e. adding 0-9 as valid characters at the start. (I've left the underscore character in, also) Thanks Jonathan Ref: https://man7.org/linux/man-pages/man7/hostname.7.html#:~:text=Valid%20characters%20for%20hostnames%20are,to%20an%20address%20for%20use. Each element of the hostname must be from 1 to 63 characters long and the entire hostname, including the dots, can be at most 253 characters long. Valid characters for hostnames are ASCII(7) letters from a to z, the digits from 0 to 9, and the hyphen (-). A hostname may not start with a hyphen. ** Affects: curtin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916325 Title: Overly strict NAME_REGEX rejects valid hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1916325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1905483] Re: Lubuntu installer cannot deal with a virgin disc.
Thank you for that. It would have been good manners to inform me that the "bug" had been fixed when it was resolved. On 25/01/2021 19:29, Walter Lapchynski wrote: > "Seems" is the appropriate word. The reality is, it's long resolved. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905483 Title: Lubuntu installer cannot deal with a virgin disc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1905483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905483] Re: Lubuntu installer cannot deal with a virgin disc.
There seems to have been no action on this bug. There is a (clumsy) work around: install another distribution (Q4OS in my case) and then reinstall ubuntu. If that doesn't give you a clue that there is an issue here, I give up! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905483 Title: Lubuntu installer cannot deal with a virgin disc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1905483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: apt (Ubuntu) Assignee: (unassigned) => Hunter Temple (xdieagainx) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910896] Re: package linux-image-5.8.0-36-generic 5.8.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.8.0-36-generic package pre-removal script subprocess returned error exit s
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Removing old bcmwl-6.30.223.271+bdcom DKMS files... -- Deleting module version: 6.30.223.271+bdcom completely from the DKMS tree. -- Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-36-generic Building for architecture x86_64 Building initial module for 5.8.0-36-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910896 Title: package linux-image-5.8.0-36-generic 5.8.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.8.0-36-generic package pre- removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
Actually, it looks like the pen is working in X11. Never mind that part. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
Thank you for the workaround! With the latest Ubuntu this works with just the "pci=nocrs" parameter. The pen input works fully in Wayland, but not at all in X11. Also, I wrote an installation guide for this laptop with more fixes and tips: https://sciactive.com/2020/12/04/how-to-install-ubuntu-on-acer-spin-5-sp513-54n-for-the-perfect-linux-2-in-1/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1905483] Re: Lubuntu installer cannot deal with a virgin disc.
Thank you for your message. Your hint about the *esp* flag was all that was needed. There is still an issue: the diagnostic "A partition ..." is worse than useless and should be changed. As an ex-compiler writer, I can only stress that *all* diagnostics *must* be accurate and not misleading! If the partition is the first partition, is of an appropriate size and the mount point is //boot/efi /then the Configurator should quietly set the flags, perhaps with a warning message, and get on with it. This process should be smooth and friendly and *not* p*ss off the user before he/she has had a chance to use what is a nice and friendly system. Your comments about invoking "apport-collect" are hardly relevant when the issue is with the fourth screen of a system install. Is apport accessible at that time. Secondly, having written to the disc, it is no longer "virgin" and the issue is not repeatable. I trust that you find this experience useful. John Hunter On 25/11/2020 01:52, Chris Guiver wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please execute the following command only once, as it > will automatically gather debugging information, in a terminal: > > apport-collect 1905483 > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > re: the ESP flag. I'll point you to > https://askubuntu.com/questions/1273421/lubuntu-installer-giving-error- > after-partition-creation-your-system-may-or-may/1276789 which maybe > helpful . The ESP flag is also mentioned in the installation section of > the Lubuntu manaul > https://manual.lubuntu.me/stable/1/1.3/installation.html?highlight=esp%20flag > > I'm also marking this incomplete, as without the calamares session.log > file from the install, exploration of the issue cannot be accomplished. > The session.log file can be found in ~/.cache/calamares/session.log > whilst *live* session is being run (if I remember correctly) but will > automatically be submitted if `ubuntu-bug calamares` is used in > submitting the bug. > > Using `apport-bug` would also have provided package versions & media > info which is missing, this will be provided by `apport-collect` if run > on your box (some details are kept in /var/log/installer post-install). > > When you've provided this information, please change the status back to > "New". Likewise if I've made an error or other, it can be changed back > to "New" with comment explaining why. > > Thank you for taking the time to report this bug and helping to make > Lubuntu better. > > ** Changed in: calamares (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905483 Title: Lubuntu installer cannot deal with a virgin disc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1905483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905483] [NEW] Lubuntu installer cannot deal with a virgin disc.
Public bug reported: I am trying to install Lubuntu 20.04 on a completely virgin machine, a NUC10 (never had Windows on it). I first tried to use the installer disc editor to partition a 2TB FireCuda disc. At the end of the set up, the installer complained "A partition was configured with mount point /boot/efi but its esp flag is not set. To set the flag, go back and edit the partition". Unfortunately, going back to set the esp flag is useless as there is no facility to set this flag! Second try: kill the installer and configure the disc manually with fdisk. Then restart the installer and when we get to the disc configuration it came up with "A partition was configured ...". Either the disc configurator should have the facility to set the esp flag or, preferably, the complaining software should set the flag automatically and, possibly, issue a friendly warning. I never got as far as being able to track down the guilty package; try "installation script"? John Hunter ** Affects: calamares (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905483 Title: Lubuntu installer cannot deal with a virgin disc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1905483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
@mhalsharif: I'm currently not using any Apple hardware, but I'm seeing all the same behavior you are (except I don't lose settings on lock/unlock). I have currently done the following things: * I moved all my keyboard customizations from dconf settings [/org/gnome/desktop/input-sources/xkb-options] (which is where Tweak Tool puts the config) and put them in /etc/default/keyboard:XKBOPTIONS. Since these settings are default, when the keyboard resets to these defaults, it resets back to the config I want. (This fixes the keyboard reset, but still will not fix the mouse resetting issue.) If you want to try this approach, you can just add the default configuration options like this: XKBOPTIONS="shift:both_capslock,ctrl:swap_lalt_lctl_lwin,caps:escape" * I have also downgraded mutter (`sudo apt install mutter=3.36.1-3ubuntu3 mutter-common=3.36.1-3ubuntu3 libmutter-6-0=3.36.1-3ubuntu3 gir1.2-mutter-6=3.36.1-3ubuntu3`). This downgraded version fixes all the resetting issues (although I'm stuck on the downgraded mutter version until a fix gets released). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1899206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
@mhalsharif: Interesting observation! Just for the record, although I experience the original issue, I don't think I'm losing anything by doing lock/unlock. I frequently lock/unlock my desktop and the lock duration can be anywhere from a few seconds to many hours. I think I would notice pretty quickly if I had this problem. Could you clarify if you lose the customized settings only in the lock- screen (where you type your password) or are your settings lost even after you successfully get back into your own desktop? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1899206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
@Gunnar: as a "volunteer who tries to help", you have been immensely helpful!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1899206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
@Gunnar: Confirmed! The mutter downgrade fixes it: `sudo apt install mutter=3.36.1-3ubuntu3 mutter-common=3.36.1-3ubuntu3 libmutter-6-0=3.36.1-3ubuntu3 gir1.2-mutter-6=3.36.1-3ubuntu3`. Thanks so much! This looks like the bug was introduced in mutter between 3.36.1-3ubuntu3 and 3.36.6-1ubuntu0.20.04.2. I posted this observation in the linked mutter bug as well (in case it might help them narrow things). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
@Gunnar: I only first recognized the issue last week -- it's possible I had been affected by the issue for longer, but did not realize it. After reading the description in the linked mutter bug, it does sound like I'm very likely affected by the same bug. Tonight, I'll try the downgrade for the mutter packages as well. Thanks for working through this with me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
@Gunnar. Yes, I rebooted after downgrade. After rebooting, I confirmed (`dpkg -l` and `gnome-shell --version`) that I was using the downgraded version. I'm wondering if I should be going back to versions which are even older? Is it safe to downgrade to even earlier versions of gnome-shell and gnome-shell-common without messing up other software on my system? Is there a list of even older downgrade versions you recommend I should try? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
@Gunnar I downgraded to 3.36.1-5ubuntu1 (for gnome-shell and gnome- shell-common). Downgrading to 3.36.1-5ubuntu1 did not fix the issue for me (like it fixed things for Detlef). Even with 3.36.1-5ubuntu1, I still lose my customized keyboard tweaks (stored in `org.gnome.desktop.input-sources -> xkb-options`). It always defaults back to whatever is in `/etc/default/keyboard -> XKBOPTIONS`. I also lose my mouse speed setting. With 3.36.1-5ubuntu1, after doing Alt-F2 -> "r", my desired settings are correctly applied. Are there any other tests I should try since my observations are different from Detlef? @Detlef: Do you ever experience the loss of the mouse speed setting (with either version of gnome-shell)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
I did a bit more digging (based on Bernard Stafford's suggestion that USB keyboard unplug/reconnect) is causing the reconnected keyboard to go back to the default keyboard config. I was able to get my keyboard customizations to apply to the reconnected USB keyboard by explicitly adding them to /etc/default/keyboard:XKBOPTIONS. When they are set only by Tweak tool (and not in /etc/default/keyboard:XKBOPTIONS), the options only seem to be defined in dconf in "org.gnome.desktop.input-sources xkb-options ['shift:both_capslock', 'ctrl:swap_lalt_lctl_lwin']". These settings seem to stop working when a USB keyboard is reconnected. This is the behavior which seems to have changed in the past month or so. (Thanks to Bernard for suggesting I even look into default keyboard configuration. This should help some.) In addition to the keyboard settings not getting applied to the reconnected USB keyboard, it also appears that the mouse tracking speed setting (established in Gnome settings) is also lost on USB reconnect. This is also new behavior (almost certainly related to the reconnect issue I'm seeing with the USB keyboard). I don't think it's very ergonomic to need to restart my Gnome session just to get my expected keyboard and mouse settings established when i reconnect my input devices back into my laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899206] [NEW] Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
Public bug reported: I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized keyboard settings on reconnect. Is there anything I can do to force the application of the custom keyboard tweaks on USB keyboard reconnect? Is anyone else able to reproduce this? I don't have any other machines with Ubuntu 20.04.1 to test with. Thanks! (This is also cross-posted at askubuntu: https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional- layout-options-not-working) ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877886] Re: update 19.10 to 20.04 fail because of disk-space
** Summary changed: - update 19.10 to 20.04 fail because disck-space + update 19.10 to 20.04 fail because of disk-space -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877886 Title: update 19.10 to 20.04 fail because of disk-space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1877886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
As per comment 25, the issue seems to affect other Lenovo systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I have submitted the patch for stable kernels: https://patchwork.kernel.org/patch/11297115/ Assuming it is accepted, it will probably turn up in Ubuntu kernels eventually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
That is a shame. Here is a new patch that disables command queuing which should avoid the problem. The old patch is then not needed. ** Patch added: "0001-mmc-sdhci-Workaround-broken-command-queuing-on-Intel.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5312929/+files/0001-mmc-sdhci-Workaround-broken-command-queuing-on-Intel.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I need to see if the value of the SSC1 register changed. It is shown in the CQHCI REGISTER DUMP looking like "mmc0: cqhci: Task clr: 0x | SSC1: 0x00010008" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I would start with a working setup, presumably Ubuntu 18.04. Then get the latest stable kernel (note, it is possible -rc kernels are broken): git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git -b linux-5.4.y Patch it, build and install. Amend /etc/defaults/grub to have: GRUB_TIMEOUT_STYLE=menu GRUB_DISABLE_SUBMENU=y GRUB_TIMEOUT=10 GRUB_CMDLINE_LINUX_DEFAULT="" To have affect need to do: sudo update-grub Then you should at least be able to choose the kernel and see some messages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Err, here is the patch ** Patch added: "0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311922/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Here is an updated patch without the dependency on #include If it doesn't work, please provide kernel messages. ** Patch removed: "0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311741/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Actually it should apply cleanly to any kernel from 4.17 onward (4.16 would require a little backporting) To apply the patch, in the linux git directory: git am 0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Is it possible to try this patch? ** Patch added: "0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311741/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I have some ideas that I am testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
No, acpidump should not show any difference running from a newer kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853036] Re: Ubuntu 19.10: 'Power Off' and 'Reboot' do not work from session manager
This was also posted by another user as a Question. I'm linking it for reference: https://answers.launchpad.net/ubuntu/+question/685270 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853036 Title: Ubuntu 19.10: 'Power Off' and 'Reboot' do not work from session manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1853036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853036] [NEW] Ubuntu 19.10: 'Power Off' and 'Reboot' do not work from session manager
Public bug reported: I'm not really sure which package/component is relevant here. I already posted this in AskUbuntu, but it seems as if it could be a bug, so I thought I would add it here as well. I upgraded to 19.10. On the session manager login screen, the 'Power Off' and 'Restart' options seem to have no effect. When I'm logged in as a user, the 'Power Off' command works. `shutdown now` also works fine. I also tried a 19.10 virtual machine. It also has the problem where initiating 'Power Off' from the session manager screen seems to have no effect. (I have seen other questions which sound related, but I don't think I'm in the same situation as those other users.) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: reboot shutdown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853036 Title: Ubuntu 19.10: 'Power Off' and 'Reboot' do not work from session manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1853036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Can someone please provide an acpidump? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818407] Re: Cant access emmc, error -84
I tried to reproduce this problem with an ASUS L403NA with an Intel N4200 processor and SanDisk DF4064 eMMC, but it worked fine. For people still experiencing this issue, here is a debug patch that will print debug information to the kernel messages to help analyze the issue. It can be applied to linux stable v5.3.y . If you try this patch, please attach the kernel messages to this bug. ** Patch added: "Debugging patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+attachment/5301398/+files/0001-HACK-mmc-Add-HS400-debug-prints-sdhci-IRQ-error-prin.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818407 Title: Cant access emmc, error -84 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832495] [NEW] Browser windows spread across workspaces upon restore
Public bug reported: This bug has shown up in every version of Linux Mint I have used (currently 18.3 Cinnamon 64-bit). It occurs by doing the following: Immediately after initiating restore of a multi-window browser session (e.g. FireFox), switch to a different workspace. If the system is in the early stages of restoring multiple browser windows (and/or multiple tabs) when switch to workspace is done, then whatever windows / tabs are being restored at that instant will "follow" into the workspace just switched to. So the effect is to spread the multi-window session across multiple workspaces, when they should be restored only in the workspace where restoration was initiated. The three workarounds for this bug that I am aware of are: 1) Don't use more than one workspace (obviously unacceptable), 2) Don't open more than one browser window (also unacceptable), 3) Wait a sufficient amount of time for all windows to be started up in the workspace from which browser restoration started before switching to another workspace. It should be obvious that the more browser windows there are to restore, the easier it is to reproduce this bug, and more time user must wait before switching to another workspace. I often restore browser sessions made up of 20 browser windows or more, so it is quite easy for me to reproduce! ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832495 Title: Browser windows spread across workspaces upon restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1832495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631169] Re: doxygen-jquery.patch modification misapplied to dynsection.js
Hey Morty, Thanks for the tip. This wasn't a problem with the upstream package. It was a problem with a patch that was inappropriately applied when it was packaged for debian. I haven't checked to see if it has fixed in the latest debian packaging. -Hunter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631169 Title: doxygen-jquery.patch modification misapplied to dynsection.js To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/doxygen/+bug/1631169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825699] Re: Touchpad not working after upgrade to 19.04
** Summary changed: - Touchpad not working after upgrade to 19.05 + Touchpad not working after upgrade to 19.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825699 Title: Touchpad not working after upgrade to 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge
** Summary changed: - Buy Adipex Online To Suppress Appetite + [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1140716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822103] Re: upgrade from 18.4 to 18.10 iio-sensor-proxy not working
Also persists after purge and upgrade of different versions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822103 Title: upgrade from 18.4 to 18.10 iio-sensor-proxy not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1822103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822103] [NEW] upgrade from 18.4 to 18.10 iio-sensor-proxy not working
Public bug reported: After upgrade from 18.4 to 18.10 iio-sensor-proxy did not pickup hardware. I had no problem with ubuntu 18.4. The iio-sensor-proxy says that it support my hardware on github. Prehapse a new build or rollback build for the new repository? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: iio-sensor-proxy 2.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 09:06:48 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iio-sensor-proxy UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iio-sensor-proxy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822103 Title: upgrade from 18.4 to 18.10 iio-sensor-proxy not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1822103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819543] Re: Does not exit correctly, have to "kill -9
** Summary changed: - Does not exit correctluy, have to "kill -9 + Does not exit correctly, have to "kill -9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819543 Title: Does not exit correctly, have to "kill -9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1819543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766851] Re: Missing `linux-update-symlinks` causes Linux package installation to fail
I'm also seeing this, when attempting to provision a vagrant box with 16.04. I have, in my Vagrantfile: ``` config.vm.box_url = 'https://app.vagrantup.com/bento/boxes/ubuntu-16.04/versions/2.3.1/providers/virtualbox.box' ``` And I see the error during `vagrant up --provision`: ``` ... Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: linux-update-symlinks: not found dpkg: error processing package linux-image-4.4.0-143-generic (--configure): subprocess installed post-installation script returned error exit status 127 ... ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766851 Title: Missing `linux-update-symlinks` causes Linux package installation to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1766851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821407] Re: Security vulnerabilities in Putty prior to 0.71
Tried to link CVEs to the bug report but the database hasn't been pulled recently enough. Will try again later today or tomorrow. ** Tags added: bionic ** Tags added: cosmic disco xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821407 Title: Security vulnerabilities in Putty prior to 0.71 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/putty/+bug/1821407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821407] [NEW] Security vulnerabilities in Putty prior to 0.71
*** This bug is a security vulnerability *** Public security bug reported: Putty 0.71 was released, patching major security vulnerabilities present in previous versions. Vulnerabilities are laid out in the following CVE reports, ranging in severity from High to Critical: CVE-2019-9898 Potential recycling of random numbers used in cryptography exists within PuTTY before 0.71. CVE-2019-9897 Multiple denial-of-service attacks that can be triggered by writing to the terminal exist in PuTTY versions before 0.71. CVE-2019-9895 In PuTTY versions before 0.71 on Unix, a remotely triggerable buffer overflow exists in any kind of server-to-client forwarding. CVE-2019-9894 A remotely triggerable memory overwrite in RSA key exchange in PuTTY before 0.71 can occur before host key verification. Threats can be mitigated by providing Putty 0.71 to Ubuntu via Apt on Disco, Cosmic, Bionic, and Xenial, if not others. ** Affects: putty (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821407 Title: Security vulnerabilities in Putty prior to 0.71 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/putty/+bug/1821407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr
It says the sender of this error is gnome-session-b? who's that? where's the code that generates this error? I'm on 18.10, upgraded from 18.04 CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
I don't understand this logic. So all of us using 18.04 LTS will have to live with this? Doesn't long term support indicate that this will get fixed? There's no workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748715] Re: Ubuntu Mate Welcome and Software Boutique Empty Screen
** Summary changed: - Ubuntu Mate Welcome and Software Boutque Empty Screen + Ubuntu Mate Welcome and Software Boutique Empty Screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748715 Title: Ubuntu Mate Welcome and Software Boutique Empty Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1748715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793229] [NEW] [VYBE, Realtek ALC892, Green Line Out, Rear] skipping/underruns
Public bug reported: Audio (from many sources) skips/hiccups pretty often (I'd say at least once every 30 seconds.) Iv'e tried all three workarounds here without success: https://wiki.ubuntu.com/Audio/PositionReporting Happy to debug as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ahh2147 F pulseaudio /dev/snd/controlC0: ahh2147 F pulseaudio Date: Tue Sep 18 18:41:45 2018 InstallationDate: Installed on 2018-09-08 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: Sep 18 18:40:10 timberwolf dbus-daemon[787]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=121 pid=1133 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Sep 18 18:40:16 timberwolf dbus-daemon[787]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.65' (uid=121 pid=1133 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [VYBE, Realtek ALC892, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: DBZ6810H.86A.0014.2011.0413.1049 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DZ68DB dmi.board.vendor: Intel Corporation dmi.board.version: AAG27985-100 dmi.chassis.type: 3 dmi.chassis.vendor: MAINGEAR dmi.modalias: dmi:bvnIntelCorp.:bvrDBZ6810H.86A.0014.2011.0413.1049:bd04/13/2011:svnMAINGEAR:pnVYBE:pvr:rvnIntelCorporation:rnDZ68DB:rvrAAG27985-100:cvnMAINGEAR:ct3:cvr: dmi.product.name: VYBE dmi.sys.vendor: MAINGEAR ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793229 Title: [VYBE, Realtek ALC892, Green Line Out, Rear] skipping/underruns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1793229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784128] Re: after autoupdate symbols on session screen not func.
** Summary changed: - after autoupdate simbols on session screen not func. + after autoupdate symbols on session screen not func. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784128 Title: after autoupdate symbols on session screen not func. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1784128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
It is wonderful news! It works - I can now find two devices! Whether I can work out how to use them is another matter, but as far as I can see the bug is fixed. Thanks for your efforts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
I hope that is good news! How do I install the fix on my system - the link seems to be to source code? I am very busy at the moment, and may not be able to do much testing till next week. On 10/07/18 02:42, Daniel van Vugt wrote: > Yes that was released a few hours ago: > https://launchpad.net/ubuntu/+source/linux-firmware/1.157.20 > > George: as the original reporter can you confirm that today's update to > the 'linux-firmware' package has fixed it? > > ** Changed in: linux-firmware (Ubuntu) > Status: Confirmed => Incomplete > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > > ** Changed in: bluez (Ubuntu) > Status: Confirmed => Incomplete > > ** Changed in: bluez (Ubuntu) > Status: Incomplete => Invalid > > ** Changed in: linux (Ubuntu) > Status: Incomplete => Invalid > -- George Hunter 10A Roome Bay Crescent CrailTel 01333 451 442 Fife KY10 3TTEmail ad...@roomebay.me.uk UK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717218] Re: Ubuntu 16.04: Can't install 'ubuntu-desktop' error during a partial upgrade of the system
I am having this same problem. I am a newbie to Linux and to computing, as a whole. Please refer to the most "beginner-friendly" fix/guide to this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717218 Title: Ubuntu 16.04: Can't install 'ubuntu-desktop' error during a partial upgrade of the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1717218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
(on ubuntu 18.04 beta 2)i had the same problem after upgrading to nvidia-drivers-390.48, than i could not login even using nouveau after removing all nvidia driver. GDM3 could not manage to boot properly but just installing lightdm and setting it to default let me login successfully (i did not remove gdm so it was not necessary to do so to fix it) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
i had the same problem in ubuntu 18.04 after upgrading to nvidia- drivers-390.48, than i could not login even using nouveau after removing all nvidia driver. GDM3 could not manage to boot properly but just installing lightdm and setting it to default let me login successfully (i did not remove gdm so it was not necessary to do so to fix it) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't display
** Summary changed: - can't open system settings(Ubuntu 17.10), icon is visible but settings don't dislay + can't open system settings(Ubuntu 17.10), icon is visible but settings don't display -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721637 Title: can't open system settings(Ubuntu 17.10), icon is visible but settings don't display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1721637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU
@kamalmostafa - Adding another datapoint: installed 4.4.0-117.141 on a vm guest on ESXi 6.0 on a host running Intel Xeon CPU E5-2695 v4 (Broadwell) and the issue still occurs. Disabling the apparmor profile for sssd allows boot to complete and restores sssd functionality. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746806 Title: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
I upgraded linux-firmware/1.157.16 to linux-firmware/1.157.17, which is what I think is neede to fix bug 1747336, but it made no difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
** Description changed: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service -Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset -Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago - Docs: man:bluetoothd(8) - Main PID: 790 (bluetoothd) -Status: "Running" -CGroup: /system.slice/bluetooth.service -└─790 /usr/lib/bluetooth/bluetoothd + Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset + Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago + Docs: man:bluetoothd(8) + Main PID: 790 (bluetoothd) + Status: "Running" + CGroup: /system.slice/bluetooth.service + └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 - Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset + Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 - Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset + Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no 1: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date - >uname -a + >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. - >hcitool dev + >hcitool dev Devices: - hci024:0A:64:F5:EE:86 + hci0 24:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue - [2.030855] usb 1-1.4: Product: Bluetooth Radio + [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd + Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 r
[Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
#26. I have finally managed to boot Ubuntu 18.04. It makes no difference. #31. Setting AutoEnable=true makes no difference to the symptoms. If including it in the config file requires subsequent modifications elsewhere, it seems simpler to remove it. There are four config files in /etc/bluetooth, consisting almost entirely of comments. /etc/bluetooth >ls input.conf main.conf network.conf proximity.conf #33. Done that, no difference. I am proposing to undo it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
for Daniel I have now downloaded "Ubuntu 18.04 LTS amd64", which appears on my desktop as a bootable disc. but how do I boot it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
~ >dmesg>dmesg.txt ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+attachment/5051467/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
I've now updated to kernel 4.15.1 ~ >uname -a Linux george-CM6330 4.15.1-041501-generic #201802031831 SMP Sat Feb 3 18:32:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It makes no difference to the symptoms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
I tried downloading these, bur got an errorr 404 - File not Found. Supposing I had succeeded, how do I install them? Is it just install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
I am not sure how I go about installing the 4.15 kernel I have used Synaptic package manager to upgrade linux-firmware to 1.157.15 and the kernel to 4.13.0.32.52. Neither fixed the problem, but the kernal produced a second Bluetooth icon on the task bar, with a different drop down menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: Ubuntu 16.04 can't find any Bluetooth devices
bug 1542743 takes me into uncharted territory - patching the kernel is well outside my comfort zone. But the fix suggested at #14 does not work (see #35) for the kernel version 4.13 which I believe is the one I have. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045643/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045642/+files/rfkill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] modified.conffile..etc.bluetooth.main.conf.txt
apport information ** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045641/+files/modified.conffile..etc.bluetooth.main.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045640/+files/getfacl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045635/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045636/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045637/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045634/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045639/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045638/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045633/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045631/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045632/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1745828/+attachment/5045630/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745828] Re: Ubuntu 16.04 can't find any Bluetooth devices
apport information ** Tags added: apport-collected xenial ** Description changed: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci024:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Thanking you in anticipation + --- + ApportVersion: 2.20.1-0ubuntu2.15 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2017-09-06 (145 days ago) + InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) + InterestingModules: rfcomm bnep btusb bluetooth + MachineType: ASUSTeK Computer INC. CM6330_CM6630_CM6730_CM6830_M11AA-8 + Packag
[Bug 1745828] [NEW] Ubuntu 16.04 can't find any Bluetooth devices
Public bug reported: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci024:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Thanking you in anticipation ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1745828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724961] Re: Mate Tweak - Only two options are available in panel list
** Summary changed: - Mate Tweak - Only two options are avaliably in panel list + Mate Tweak - Only two options are available in panel list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724961 Title: Mate Tweak - Only two options are available in panel list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1724961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687885] Re: Stop browser
** Summary changed: - Stop brawser + Stop browser -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687885 Title: Stop browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1687885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709714] Re: start-up backgrounds are fixed.
** Summary changed: - srart-up backgrounds are fixed. + start-up backgrounds are fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709714 Title: start-up backgrounds are fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1709714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730521] Re: transparency gone in dock panel (wayland)
*** This bug is a duplicate of bug 1730489 *** https://bugs.launchpad.net/bugs/1730489 ** Summary changed: - transparencey gone in dock panel (wayland) + transparency gone in dock panel (wayland) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730521 Title: transparency gone in dock panel (wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729719] Re: os won't install
** Summary changed: - os won't insatll + os won't install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729719 Title: os won't install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1729719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728222] Re: display updates are erroneous during scrolling after starting search
** Summary changed: - display updates are errornous during scrolling after starting search + display updates are erroneous during scrolling after starting search -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728222 Title: display updates are erroneous during scrolling after starting search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1728222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop
I should add that mine wasn't a fresh install of Ubuntu 17.10, but rather an upgrade from 17.04 (do-release-upgrade). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722121 Title: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop
I'm seeing this issue as well. I can also confirm that copying doesn't work when Terminal is opened by right-clicking the desktop and selecting Open Terminal, but DOES work when I've opened it by other means. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722121 Title: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720788] [NEW] zooming out when trim margins is active gets stuck between 100% and Fit Width
Public bug reported: When viewing a document with the option "View -> Trim View -> Trim Margins" active, if one tries to zoom out several times, okular ends up stuck between the 100% and "Fit Width" levels, cycling between the two. Source package: /usr/bin/okular 1) Ubuntu release Description:Ubuntu Artful Aardvark (development branch) Release:17.10 2) Package version okular: Installed: 4:17.04.3-0ubuntu1 Candidate: 4:17.04.3-0ubuntu1 Version table: *** 4:17.04.3-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status 3) okular would proceed zooming out from 100% to 75% and beyond. 4) okular is stuck between the "Fit Width" and 100% zoom levels. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: okular 4:17.04.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 2 08:57:55 2017 SourcePackage: okular UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: okular (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720788 Title: zooming out when trim margins is active gets stuck between 100% and Fit Width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1720788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714658] Re: gnome-shell crashed with SIGSEGV in g_closure_invoke() after clicking on "show applications"
** Summary changed: - gnome-shell crashed with SIGSEGV in g_closure_invoke() after clciking on "show applications" + gnome-shell crashed with SIGSEGV in g_closure_invoke() after clicking on "show applications" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714658 Title: gnome-shell crashed with SIGSEGV in g_closure_invoke() after clicking on "show applications" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984899] Re: right-click menu profile preference does not work
** Summary changed: - right-click menu profile preference not work + right-click menu profile preference does not work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984899 Title: right-click menu profile preference does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/984899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709686] Re: Thunar crashes with error "Bus error (core dumped)" when opening "Properties" of a file if thunar-gtkhash is installed
** Summary changed: - Thunar crasshes with error "Bus error (core dumped)" when opening "Properties" of a file if thunar-gtkhash is installed + Thunar crashes with error "Bus error (core dumped)" when opening "Properties" of a file if thunar-gtkhash is installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709686 Title: Thunar crashes with error "Bus error (core dumped)" when opening "Properties" of a file if thunar-gtkhash is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkhash/+bug/1709686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
