[Touch-packages] [Bug 2059418] Re: Bluetooth earbuds not being 'set up' on new machine

2024-04-02 Thread Bill Gradwohl
Purchased via : https://www.amazon.com/gp/product/B0C3W4MNN1 FCC ID:2A33A-T60 -- 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/2059418 Title: Bluetooth earbuds not being 'set

[Touch-packages] [Bug 2059418] [NEW] Bluetooth earbuds not being 'set up' on new machine

2024-03-28 Thread Bill Gradwohl
Public bug reported: The problem concerns earbuds 0B:20:24:A3:E7:56 T60 that worked perfectly under completely patched Ubuntu 22.04 on my old machine but now refuse to be setup on a new box running completely patched Ubuntu 22.04 . Other old bluetooth gadgets attached without issue. The end resul

[Touch-packages] [Bug 2039357] [NEW] Bluetooth headphones not detected properly

2023-10-14 Thread Bill Gradwohl
Public bug reported: On a fresh system boot, stereo Bluetooth headphones with a microphone that identify as WH-CH710N connect but provide no sound until Settings is used to pick the only microphone option, the headphones, whereupon sound immediately works. Thereafter, doing a sound Test reveals t

[Touch-packages] [Bug 1987665] Re: The "Settings" app is missing the 'Appearance' option

2022-08-25 Thread Bill Gradwohl
I tried to use ubuntu-bug to report the lock up of chrome during the ubuntu-bug reporting process but ubuntu-bug won't allow a report on ubuntu-bug itself. bill@bill ~$ ubuntu-bug ubuntu-bug dpkg-query: no packages found matching ubuntu-bug FYI - When I attempted to report the bug this page is a

[Touch-packages] [Bug 1987665] Re: The "Settings" app is missing the 'Appearance' option

2022-08-25 Thread Bill Gradwohl
I tried to attach an image to this report AFTER the report was already accepted and chrome locked up immediately after I selected a file. That's the second lock up when selecting a file. ** Attachment added: "Settings.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/

[Touch-packages] [Bug 1987665] [NEW] The "Settings" app is missing the 'Appearance' option

2022-08-25 Thread Bill Gradwohl
Public bug reported: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: U

[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-07-11 Thread Bill Gradwohl
For anyone that's interested --- I added the following to root's crontab: @reboot sleep 120 && /bin/systemctl restart sshd That works for me to get sshd up AND listening -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ope

[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-06-21 Thread Bill Gradwohl
Robie: If the service offers a mechanism to set a specific NIC to listen on, then the service should make good on that offer when it's requested. Doesn't that make sense to you? All services that require a NIC to function should wait for that NIC to come alive. Having a service start or attempt to

[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-06-15 Thread Bill Gradwohl
I created Bug 1774788 which is for rsyncd not starting at boot and was provided with a fix by Andreas Hasenack that works. I tried using that fix for ssh and it does not work. Both services fail when an attempt is made to specify a particular NIC via their respective config files. In the case of r

[Touch-packages] [Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)

2018-06-04 Thread Bill Gradwohl
I'm a recent convert to Ubuntu, having been on Fedora from FC2 through F26; quite a long time. Over the last few years, their support became nonexistent. Bugs reported would not even be acknowledged, much less worked on. To have someone actually respond to a bug report is so unusual in my experienc

[Touch-packages] [Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)

2018-06-04 Thread Bill Gradwohl
I'm impressed! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) Status in rsync: Unknown Status in rsyn

[Touch-packages] [Bug 1774788] [NEW] Daemon won't start at boot up (18LTS fully patched)

2018-06-02 Thread Bill Gradwohl
Public bug reported: By adding the 'address=' option to the /etc/rsyncd.conf file, the daemon fails at boot. Once the NIC(s) is/are up, it will start fine when executed via systemctl start rsync ● rsync.service - fast remote file copy program daemon Loaded: loaded (/lib/systemd/system/rsync.

[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-04-28 Thread Bill Gradwohl
I installed version 16LTS recently and just upgraded the box to 18LTS and both display the error. I have 2 NICs (Private / Public) with an sshd config file set to only listen to the private side. It appears sshd attempt to start after the Public NIC is up, but before the private NIC is available.