[Touch-packages] [Bug 42382] Re: bash completion does not work for ssh
Though I could not get `~/.ssh.known_hosts` to not hash, I was able to configure SSH to use the `~/.ssh/config` file for autocompletion. Documented here: http://unix.stackexchange.com/questions/136351/autocomplete-server-names-for-ssh-and-scp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/42382 Title: bash completion does not work for ssh Status in bash package in Ubuntu: Invalid Bug description: bash completion does not work for ssh. I have verified that the bash completion portion in the /ect/profiile, /etc/bash_completion and my .bash_profile / .bashrc do not have any commented parts that would inhibit it from working. The bash completion works for other commands. After looking at .ssh/know_hosts filethat may be the issue. It does not look like a normal knowhost file Here is a snippet. |1|AYGo+egg1pJpsfvebubolAnKnkY=|9gSlcIoCPlH17m8gjAH2G/3f+BM= ssh-rsa B3NzaC1yc2EBIwAAAIEAu9qQ1aV3NzGRzNwE0J8fL5s8rTXnkhVply2yFHKO87M/HJsIJSy/oyEvZU0T0lRIZF/MG0HDIIbtf30O5xOKlxvnLs2KMzVqc7nJc9a+iyak0G1cHLkO8ey2fKuGO7jBq0h6dgz07B188If7L7hwS45OTA0geWh8W2gRgn712/c= Here is the actual ssh tab complete invocation out of bash.. ssh |1| It does appear that it is working as it parsing the know_hosts file and getting "|1|" but it is actually meaningless as it should be a host name. Maybe a comand sub issue with ssh? Maybe this should be routed to the ssh folks ??? Note: the original reporter indicated the bug was in package 'bash- completion'; however, that package was not published in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/42382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385245] Re: Beats Studio wireless bluetooth headphones wont pair w/ ubuntu 14.04
I can confirm that there is an issue with the Beats headset. I have the Beats Studio Wireless headset, and it pairs just fine with my Android phone and with a coworker's Windows laptop. However I am having problems connecting it to Kubuntu 14.10. When I run `hcitool scan` the headset is sometimes found, sometimes not (most often not). I often run the scan a few times, then when the headset is found I connect via Bluez. Of course, the problem might be with the Bluetooth dongle, this is the dongle that I am using: Bus 002 Device 010: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1385245 Title: Beats Studio wireless bluetooth headphones wont pair w/ ubuntu 14.04 Status in bluez package in Ubuntu: Confirmed Bug description: I have Beats Studio wireless bluetooth headphones and when adding device (pair bluetooth device) it wont pair w/ ubuntu 14.04 system. Closest thing I've found is this: https://code.google.com/p/chromium/issues/detail?id=379126 It looks like it's working on ChromeOS so I'm hoping it's possible it will work w/ ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1385245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1184006] Re: wrong conffile prompt for /etc/default/rcS when UTC=no
This bug seems to have been closed WONTFIX as it affects older,
unsupported Ubuntu versions. However, I have encountered this bug on an
upgrade from 15.10 to 16.04, and other dupes of the bug show that other
users are encountering the bug on newer Ubuntu versions as well.
Please reopen. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1184006
Title:
wrong conffile prompt for /etc/default/rcS when UTC=no
Status in clock-setup package in Ubuntu:
Confirmed
Status in sysvinit package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in clock-setup source package in Saucy:
Won't Fix
Status in sysvinit source package in Saucy:
Won't Fix
Status in ubiquity source package in Saucy:
Won't Fix
Bug description:
Because we're not following Debian on the use of /etc/adjtime for UTC
settings and instead keeping it in /etc/default/rcS, users who have
the non-default setting of UTC=no will get inappropriate conffile
prompts on upgrade to saucy.
We need to deal with this by either reverting /etc/default/rcS's
conffile status, or moving this UTC setting out of /etc/default/rcS
(options: /etc/default/hwclock, /etc/init/hwclock{,-save}.override).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1184006/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
