[Touch-packages] [Bug 2059418] Re: Bluetooth earbuds not being 'set up' on new machine
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 up' on new machine Status in bluez package in Ubuntu: Incomplete Bug description: 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 result at the very bottom of this page indicates ‘requestor exited before bonding was completed’ . root@bill:~# bluetoothctl --version bluetoothctl: 5.64 root@bill:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:11627 acl:0 sco:0 events:466 errors:0 TX bytes:78563 acl:0 sco:0 commands:422 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'bill' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: (0xc) Revision: 0x40d LMP Version: (0xc) Subversion: 0x7225 Manufacturer: Realtek Semiconductor Corporation (93) root@bill:~# bluetoothctl Agent registered [CHG] Controller BC:C7:46:9D:25:98 Pairable: yes [bluetooth]# show Controller BC:C7:46:9D:25:98 (public) Name: bill Alias: bill Class: 0x007c0104 Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink (110b--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0a (10) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded [bluetooth]# devices Device 74:45:CE:BA:24:65 WH-CH710N At this point I started the earbuds (T60) having a problem getting set up. [CHG] Controller BC:C7:46:9D:25:98 Discoverable: yes [CHG] Controller BC:C7:46:9D:25:98 Discovering: yes [NEW] Device 34:95:04:4B:07:3C 34-95-04-4B-07-3C [CHG] Device 34:95:04:4B:07:3C RSSI: -86 [NEW] Device 0B:20:24:A3:E7:56 T60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -52 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -64 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device
[Touch-packages] [Bug 2059418] [NEW] Bluetooth earbuds not being 'set up' on new machine
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 result at the very bottom of this page indicates ‘requestor exited before bonding was completed’ . root@bill:~# bluetoothctl --version bluetoothctl: 5.64 root@bill:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:11627 acl:0 sco:0 events:466 errors:0 TX bytes:78563 acl:0 sco:0 commands:422 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'bill' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: (0xc) Revision: 0x40d LMP Version: (0xc) Subversion: 0x7225 Manufacturer: Realtek Semiconductor Corporation (93) root@bill:~# bluetoothctl Agent registered [CHG] Controller BC:C7:46:9D:25:98 Pairable: yes [bluetooth]# show Controller BC:C7:46:9D:25:98 (public) Name: bill Alias: bill Class: 0x007c0104 Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink (110b--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0a (10) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded [bluetooth]# devices Device 74:45:CE:BA:24:65 WH-CH710N At this point I started the earbuds (T60) having a problem getting set up. [CHG] Controller BC:C7:46:9D:25:98 Discoverable: yes [CHG] Controller BC:C7:46:9D:25:98 Discovering: yes [NEW] Device 34:95:04:4B:07:3C 34-95-04-4B-07-3C [CHG] Device 34:95:04:4B:07:3C RSSI: -86 [NEW] Device 0B:20:24:A3:E7:56 T60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -52 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -64 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -50 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -50 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -80 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -46 [bluetooth]# info 0B:20:24:A3:E7:56 Device 0B:20:24:A3:E7:56 (public) Name: T60 Alias: T60 Class: 0x00240404 Icon: audio-headset Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no ManufacturerData Key: 0x7262
[Touch-packages] [Bug 2039357] [NEW] Bluetooth headphones not detected properly
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 the headphones are considered mono, not stereo. Sound works, but periodically the Bluetooth connection halts the browser that's playing the sound and in about 10 seconds, Bluetooth disconnects then reconnects a short time later but with the original sound problem. The issue is with the Bluetooth detection. The symptom is no sound. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1876 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Oct 14 08:38:00 2023 InstallationDate: Installed on 2019-11-18 (1425 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to jammy on 2022-11-01 (346 days ago) dmi.bios.date: 09/21/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd09/21/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2039357 Title: Bluetooth headphones not detected properly Status in alsa-driver package in Ubuntu: New Bug description: 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 the headphones are considered mono, not stereo. Sound works, but periodically the Bluetooth connection halts the browser that's playing the sound and in about 10 seconds, Bluetooth disconnects then reconnects a short time later but with the original sound problem. The issue is with the Bluetooth detection. The symptom is no sound. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1876 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Oct 14 08:38:00 2023 InstallationDate: Installed on 2019-11-18 (1425 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to jammy on 2022-11-01 (346 days ago) dmi.bios.date: 09/21/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd09/21/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2039357/+subscriptions --
[Touch-packages] [Bug 1987665] Re: The "Settings" app is missing the 'Appearance' option
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 about the first time, the ubuntu-bug output on the terminal showed the following if that's any help: bill@bill ~$ ubuntu-bug ubuntu-settings bill@bill ~$ [75943:75943:0825/071203.322589:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported. Opening in existing browser session. You guys should use ubuntu-bug to report something and attempt to add an attachment as I did and you might see the chrome lock up yourselves. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in ubuntu-settings package in Ubuntu: New Bug description: 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: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+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 1987665] Re: The "Settings" app is missing the 'Appearance' option
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/+attachment/5611652/+files/Settings.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in ubuntu-settings package in Ubuntu: New Bug description: 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: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+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 1987665] [NEW] The "Settings" app is missing the 'Appearance' option
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: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in ubuntu-settings package in Ubuntu: New Bug description: 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: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+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 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
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 start before what it needs for life support is available makes no sense. Allowing a service to start on a bogus IP address provides no "service". What's the point of having a service technically up if it's deaf to traffic? I can't see where this qualifies as a wishlist item. The service advertises a feature and doesn't provide it. To me, that's a bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+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 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
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 rsync, the fix was to create the override.conf file containing: [Unit] After=network.target,network-online.target via the command systemctl edit rsync.service Using a similar procedure to create the override.conf file for ssh does not fix the ssh daemon startup issue. I'm curious as to why that is. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+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 1774788] Re: Daemon won't start at boot up (18LTS fully patched)
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 experience that I'm pleasantly shocked. Thank You. Thank You. Shouldn't services (sshd, rsync, etc) that depend on a NIC being available ALL wait till that's true? Shouldn't the fix presented for this bug become SOP for all the control files for services that require a NIC to be up? -- 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 rsync package in Ubuntu: Triaged Bug description: 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.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1774788/+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 1774788] Re: Daemon won't start at boot up (18LTS fully patched)
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 rsync package in Ubuntu: Triaged Bug description: 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.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1774788/+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 1774788] [NEW] Daemon won't start at boot up (18LTS fully patched)
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.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- 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 package in Ubuntu: New Bug description: 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.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1774788/+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 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
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. The Private NIC becomes available several seconds after sshd is initiated according to journalctl. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+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