[Touch-packages] [Bug 2045737] Re: Logitech MX Master 3 is detected as a keyboard in Power Statistics
** Package changed: gnome-power-manager (Ubuntu) => upower (Ubuntu) ** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #215 https://gitlab.freedesktop.org/upower/upower/-/issues/215 ** Also affects: upower via https://gitlab.freedesktop.org/upower/upower/-/issues/215 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2045737 Title: Logitech MX Master 3 is detected as a keyboard in Power Statistics Status in Upower: Unknown Status in upower package in Ubuntu: New Bug description: My Logitech MX Master 3 is detected as a keyboard in Power Statistics, it's not a critical issue as beyond this everything works fine. I'm using the Logitech Unifying Receiver to connect my MX Keys Keyboard and MX Master 3 Mouse, those are working fine but sometimes I get the notification of low battery, but I'm not so sure what is the device as it says Keyboard and the mouse is identified by Power Statistics as a Keyboard. This is the info from Power Statistics window: Device: battery_hidpp_battery_o Type: Leyboard Model: Wireless Mouse MX Master 3 Serial number: bc-83-96-ed Supply: No Refreshed: 0 seconds Present: Yes Rechargable: Yes State: Discharging Percentage: 50.0% This is the info related to the Dongle from lsusb: ``` Bus 003 Device 012: ID 046d:c52b Logitech, Inc. Unifying Receiver ``` lshw information: ``` *-input:12 product: Logitech MX Keys physical id: e logical name: input33 logical name: /dev/input/event6 logical name: input33::capslock logical name: input33::compose logical name: input33::kana logical name: input33::numlock logical name: input33::scrolllock logical name: /dev/input/mouse2 capabilities: usb *-input:13 product: Logitech MX Master 3 physical id: f logical name: input34 logical name: /dev/input/event7 logical name: input34::capslock logical name: input34::compose logical name: input34::kana logical name: input34::numlock logical name: input34::scrolllock logical name: /dev/input/mouse3 capabilities: usb ``` From the information above, this could be related to another package (even the kernel?) and not specifically gnome-power-manager ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-power-manager 43.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 08:33:41 2023 ExecutablePath: /usr/bin/gnome-power-statistics InstallationDate: Installed on 2023-05-04 (215 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to mantic on 2023-11-03 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/2045737/+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 1903995] Re: upower report wrong battery percentage for Logitech Unify devices
Is it related to this? https://bugs.launchpad.net/ubuntu/+source/gnome-
power-manager/+bug/2045737
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1903995
Title:
upower report wrong battery percentage for Logitech Unify devices
Status in upower package in Ubuntu:
Triaged
Bug description:
The battery percentage reported by upower for Logitech devices
connected using Unify receiver are wrong. Below are the results for
two devices: Mouse and Keyboard:
* Battery percentages reported by Unify receiver using Solaar:
$ solaar show | grep -iP "^(( \d: )|(.*batt.*))"
1: Wireless Keyboard K270(unifying)
4: BATTERY STATUS {1000}
Battery: 70%, discharging.
2: Wireless Mouse MX Master
7: BATTERY STATUS {1000}
Battery: 20%, discharging.
* Battery percentages reported by upower:
$ upower -i /org/freedesktop/UPower/devices/keyboard_hidpp_battery_0
native-path: hidpp_battery_0
model:Wireless Keyboard K270
serial: 4003-1a-39-5f-c1
power supply: no
updated: Thu 12 Nov 2020 13:59:18 CET (119 seconds ago)
has history: yes
has statistics: yes
keyboard
present: yes
rechargeable:yes
state: discharging
warning-level: none
battery-level: normal
percentage: 55% (should be ignored)
icon-name: 'battery-low-symbolic'
$ upower -i /org/freedesktop/UPower/devices/mouse_hidpp_battery_1
native-path: hidpp_battery_1
model:Wireless Mouse MX Master
serial: 4071-f8-eb-bf-d1
power supply: no
updated: Thu 12 Nov 2020 14:03:14 CET (27 seconds ago)
has history: yes
has statistics: yes
mouse
present: yes
rechargeable:yes
state: discharging
warning-level: low
battery-level: low
percentage: 10% (should be ignored)
icon-name: 'battery-caution-symbolic'
Basically the difference is big so I'm getting a lot of notifications
related to low battery even if the battery is OK:
* Mouse, upower: 10%real (Solaar): 20%
* Keyboard: upower: 70%real (Solaar): 55%
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: upower 0.99.11-1build2
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 12 13:58:35 2020
InstallationDate: Installed on 2020-04-19 (206 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-17T11:02:56.934699
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1903995/+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 1862764] Re: add-apt-repository should use signed-by
Related (but not the same)": https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1986513 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use signed-by Status in python-apt package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in software-properties package in Debian: New Bug description: add-apt-repository should use signed-by apt sources.list syntax supports limiting which keys are used to sign a given repo. It would be nice for add-apt-repository to import the key somewhere else but trusted.gpg.d and then specify path to it, using the "signed- by" field. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 12:01:49 2020 InstallationDate: Installed on 2016-01-26 (1477 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2019-01-15 (391 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-01-10T16:24:15.968394 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+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 1986513] Re: Software & Updates doesn't handle sources files properly when an entry has options
Related but not the same: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1862764 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1986513 Title: Software & Updates doesn't handle sources files properly when an entry has options Status in software-properties package in Ubuntu: Confirmed Bug description: — SYNOPSIS — Software & Updates (software-properties-gtk) has a tab "Other Software" that lists all entries in /etc/apt/sources.list and in /etc/apt/sources.list.d/*.list Some entries have an option in square brackets, e.g.: deb [arch=amd64] ... But, Software & Updates doesn't handle these options properly. 1. It removes the option if you edit the entry. 2. If the option contains "signed-by", Software & Updates doesn't even list the entry, and thus allows you to add a duplicate entry (normally prevented). — EXAMPLES — Example of point 1: Consider Google Chrome: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main #Chrome If you edit this entry in Software & Updates, it removes [arch=amd64]. The same applies to [trusted=yes]. Example of point 2: Consider SpiderOakONE, which needs "signed-by". deb [signed-by=/usr/share/keyrings/spideroakone.gpg] https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE This also happens with combinations: deb [arch=amd64 signed-by=/usr/share/keyrings/spideroakone.gpg] https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE Software & Updates doesn't even display this entry. Thus, you can manually re-add this deb, albeit without the signed-by option. — MORE DETAIL — Confusingly, you can add the option [arch=amd64] or [trusted=yes] (or both) when you add an entry in Software & Updates, but if you then edit the entry, Software & Updates removes the option. — EXPECTED BEHAVIOUR — Software & Updates should: • Display all entries • Preserve all options when editing an entry • Allow you to add suitable options when adding an entry • Allow you to edit options when editing an entry — VERSIONS — Ubuntu version: Tested on Ubuntu 20.04.4 and Ubuntu 22.04.1 software-properties-gtk version: 0.99.9.8 (on Ubuntu 20.04) 0.99.22.3 (on Ubuntu 22.04) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22.3 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 09:19:51 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-05-05 (101 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1986513/+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 1987353] Re: Software Updater not showing third-party repository with "signed-by" tag
*** This bug is a duplicate of bug 1986513 *** https://bugs.launchpad.net/bugs/1986513 ** This bug has been marked a duplicate of bug 1986513 Software & Updates doesn't handle sources files properly when an entry has options -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1987353 Title: Software Updater not showing third-party repository with "signed-by" tag Status in software-properties package in Ubuntu: Triaged Bug description: Since apt-key is now deprecated, I followed various guides and moved all third-party repository keys to /etc/apt/keyrings/, then added the "signed-by" tag to the corresponding source lists. After that, those third-party repositories no longer show up in the "Other Software" tab in Software Updater. /home/jing>lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 /home/jing>apt-cache policy update-manager update-manager: Installed: 1:22.04.9 Candidate: 1:22.04.9 Version table: *** 1:22.04.9 500 500 http://archive.ubuntu.mirror.rafal.ca/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.mirror.rafal.ca/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: update-manager 1:22.04.9 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: XFCE Date: Mon Aug 22 18:27:09 2022 InstallationDate: Installed on 2018-10-23 (1399 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to jammy on 2022-08-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1987353/+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 1862764] Re: add-apt-repository should use signed-by
I'm on Ubuntu 22.04 and I'm getting the warning of deprecated location for keys multiple times. I know that for now I can ignore it, but I'm pretty sure that a lot of people is using PPAS/External Repos and will be scared of the warnings. ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #995895 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995895 ** Also affects: software-properties (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995895 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use signed-by Status in python-apt package in Ubuntu: New Status in software-properties package in Ubuntu: Confirmed Status in software-properties package in Debian: Unknown Bug description: add-apt-repository should use signed-by apt sources.list syntax supports limiting which keys are used to sign a given repo. It would be nice for add-apt-repository to import the key somewhere else but trusted.gpg.d and then specify path to it, using the "signed- by" field. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 12:01:49 2020 InstallationDate: Installed on 2016-01-26 (1477 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2019-01-15 (391 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-01-10T16:24:15.968394 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+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 1933537] Re: add-apt-repository should store PGP keys in /usr/share/keyrings because /etc/apt/trusted.gpg.d is deprecated for third party repos
*** This bug is a duplicate of bug 1862764 *** https://bugs.launchpad.net/bugs/1862764 ** This bug has been marked a duplicate of bug 1862764 add-apt-repository should use signed-by -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1933537 Title: add-apt-repository should store PGP keys in /usr/share/keyrings because /etc/apt/trusted.gpg.d is deprecated for third party repos Status in software-properties package in Ubuntu: New Bug description: PPAs are third party repositories. for security reasons, PGP keys for these must not be placed in /etc/apt/trusted.gpg.d, according to this document: https://wiki.debian.org/DebianRepository/UseThirdParty they should instead be saved to /usr/share/keyrings and the generated .list file for the repo added should refer to its particular key by using a [signed-by=/usr/share/keyrings/...] argument. this ensures that the downloaded PGP key will only be used to verify a particular repository and is not globally available to verify package lists of all configured repositories (as are all keys found in /etc/apt/trusted.gpg.d). please fix add-apt-repository accordingly. Ubuntu 20.04.2 LTS software-properties-common 0.98.9.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1933537/+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 1802135] Re: broken touchpad after i2c-i801 blacklist change
This bug is present in Ubuntu 19.10 (yes, the beta) with a Lenovo T560. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1802135 Title: broken touchpad after i2c-i801 blacklist change Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Xenial: Fix Released Status in linux source package in Xenial: Invalid Status in kmod source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: SRU: [Impact] ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801. PNP LEN0049 will use smbus by default in kernel, but i2c bus is in runtime suspend mode in old touchpad fw. Then touchpad will not work. LEN2040 on 11e 3rd can reproduce this issue by passing psmouse.synaptics_intertouch=1 These 2 pnp device should be the same one Synaptics s3203_ver5. [Fix] i2c-i801 should auto suspend when not used, no need runtime pm. [Test Case] Tested on Thinkpad 11e 3rd. Touchpad works fine. [Regression Potential] Low, upstream fix cherry-picked. 4.18 kernel patch, no need for cosmic. Original bug report: = After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 11e 2nd gen machines. We have a fleet of approximetly 1000 of them in production running ubuntu 18.04. Prior to this update the trackpads worked out of box in 18.04. We are currently working around the issue by deploying our own blacklist files. Here is a link to the SRU justification: https://bugs.launchpad.net /hwe-next/+bug/1786574 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+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 1786574] Re: remove i2c-i801 from blacklist
This bug is present in Ubuntu 19.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: In Progress Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1811580] Re: systemd fails to start sshd at reboot
Thank you @vorlon . I made some test with that image on a clean server and it works with no issues, but I had issues in different servers with the same image and other worked fine with the same AMI. I use a proxy repository, this can be related to different/incompatible systemd and kernel versions installed using that repo? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Incomplete Bug description: So far reported issues turned out to be: - obsolete/buggy/vulnerable 3rd party provided kernels - bad permissions on / Please ensure / is owned by root:root. Please ensure you are running up to date kernels. === Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+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 1811580] Re: systemd fails to start sshd at reboot
There is something that I cant understand. I get that systemd new update changes some stuff and needs an specific path. But, why are the owners of / directory or others directories being changed? I got this issue with this ami-059eeca93cf09eebd on AWS, but not in all the servers that have this error. As AWS has no serial console access the only way to restore that servers was to create a new instance, attach the old disk, fix permissions and reattach disk to old instance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Incomplete Bug description: So far reported issues turned out to be: - obsolete/buggy/vulnerable 3rd party provided kernels - bad permissions on / Please ensure / is owned by root:root. Please ensure you are running up to date kernels. === Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+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 232172] Re: MASTER no wlan option for pppoe configuration
Wow! Almost 10 years! I don't even remember about this bug and how pppoe works! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/232172 Title: MASTER no wlan option for pppoe configuration Status in NetworkManager: Fix Released Status in Network Manager Applet: Fix Released Status in dillo package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Triaged Status in network-manager-applet package in Ubuntu: Triaged Bug description: In Ubuntu 8.04, there is possibility to set up ppoe connection using gui in network settings. But there is only possibility to use ethernet devices for setting the connection. In my case, I am using pppoe over wlan device (quite common internet connection in Germany), it means, I have to connect to WLAN bridge and then use this wlan bridge for setting pppoe connection. To do this, I have to set up it using command line tool pppoeconf. So I think this is not feature request, this is a bug in present gui, that the wlan device can't be chosen. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/232172/+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 814019] Re: epiphany/empathy-chat crashed with SIGSEGV in gtk_widget_hide()
This seems to be similar to an existing Remmina bug (sorry, private bug): https://bugs.launchpad.net/bugs/1565635 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/814019 Title: epiphany/empathy-chat crashed with SIGSEGV in gtk_widget_hide() Status in Empathy: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: I group the tabs (IRC + XMPP) and crash. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: empathy 3.1.3-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7 Uname: Linux 3.0.0-5-generic x86_64 Architecture: amd64 Date: Thu Jul 21 07:07:44 2011 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1) ProcCmdline: /usr/lib/empathy/empathy-chat ProcEnviron: SHELL=/bin/bash LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f68c84d0589:mov0x70(%rax),%ecx PC (0x7f68c84d0589) ok source "0x70(%rax)" (0xab1a) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: ?? () from /usr/lib/libgtk-3.so.0 gtk_widget_hide () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 Title: empathy-chat crashed with SIGSEGV in gtk_widget_hide() UpgradeStatus: Upgraded to oneiric on 2011-07-16 (5 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/814019/+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 1369493] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
This is still present in Ubuntu 16.04 Xenial Xerus -- 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/1369493 Title: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Status in sysvinit package in Ubuntu: Confirmed Bug description: Upgrading xorg on Utopic (booted with upstart), the install dialog-box have displayed this warning: Setting up x11-common (1:7.7+7ubuntu2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults * Setting up X socket directories...[ OK ] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: sysv-rc 2.88dsf-41ubuntu18 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 15 12:12:53 2014 PackageArchitecture: all SourcePackage: sysvinit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1369493/+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 219057] Re: Bluetooth does not coexist with WiFi
Funny thing, I didn't have many hope to my workaround because in Ubuntu 15.04 because after some minutes, It failed. But now on Ubuntu 15.10, with Bluez 5, the problem still exist but my workaround works. echo "options iwlwifi 11n_disable=1 bt_coex_active=0 power_save=0 auto_agg=0 swcrypto=1" | sudo tee /etc/modprobe.d/iwlwifi.conf > /dev/null -- 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/219057 Title: Bluetooth does not coexist with WiFi Status in bluez package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+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 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)
Hi I'm using Ubuntu 15.10 that has bluez 5. Iand using a Sony Bluetooth handsfree SBH50. Now I can choose the A2DP value, but, now I have another issue. https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057 Bluetooth can't coexist with Wifi. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1181106 Title: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) Status in Bluez Utilities: New Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: Fix Released Bug description: I upgraded to 13.04 recently and my A2DP profile, which had been working great under 12.10 is suddenly gone. Neither my blueman applet nor the built-in bluetooth manager applet can connect my external bluetooth speaker to the A2DP profile. They can connect to the bluetooth device itself just fine. Steps I'm using: * using blueman, I can connect to the external bluetooth speaker and view the device in the devices listing * I can connect the device to the Audio sink and I get a message saying it is now connected and will "show in the PulseAudio mixer" * After connecting the external speaker to the audio sink, I can also see the device in the "Play sound through" listing in the Sound system control panel, but the icon has a circle with a line through it. * but if I right-click the device and choose "Audio Profile" from the context menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I get an error message stating "failed to change profile to a2dp" I've already added "Enable=Socket" in /etc/bluetooth/audio.conf, without that I can't pair my headset. Now I can pair it, but I can't activate the A2DP profile. When I try to activate it, I see this message in my syslog : pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no transport I tried the kernel 3.9.0 because of a sound problem with my soundcard, this kernel fixed my soundcard problem, but A2DP still doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+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 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot
Hi I got the same problem in Ubuntu 14.04. I used KVM on Ubuntu 14.04 with network using bridge, modifying the /etc/network/interfaces but today I tried to set the bridge using Network Manager. After setting the bridge on network manager, I used the brctl show and the eth0 card were not linked to the bridge, but taking the advice of opening the Network Manager configuration file (/etc/NetworkManager/NetworkManager.conf) and saving it without editing it, I got the bridge up. So this problem is still there in Ubuntu 14.04, can somebody set the affect release to Ubuntu 14.04 Trusty Tahr? Also, when I set this bridge, I got an error in the network, my PC is connected to a Cisco Switch 2960-S, my port become err-disable status. Because of this I removed all the NM configuration and used the old method and the bridged network worked again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1273201 Title: bridge_ignore_without_connections.patch breaks NM created bridge at boot Status in network-manager package in Ubuntu: Fix Released Bug description: I've created a bridge with network-manager-gnome, the bridge slave physical device is eth0. After a reboot the bridge is brought up, but eth0 isn't attached. First test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0 and remove all other connections. After a reboot the bridge is brought up, but eth0 isn't attached. When I open /etc/NetworkManager/NetworkManager.conf and save it without any modification, eth0 is instantly added to my bridge. Strange! Second test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0. Disable the "autoconnect" of the default wired network. After a reboot the bridge is brought up, but eth0 isn't attached. Instead eth0 is brought up and full configured. After compiling and testing different upstream versions, i could track the problem down to bridge_ignore_without_connections.patch. A network-manager package without this specific patch, brings my bridge up at boot and adds eth0 to the bridge in both test-cases. I've checked the behaviour on my ubuntu 13.10 box with network-manager (0.9.8.0-0ubuntu22) and the trusty version network-manager (0.9.8.8-0ubuntu1) . Till now i couldn't encounter any sideeffects of removing this patch with the bridge created by libvirt. Regards Mathias Kresin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+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 219057] Re: Bluetooth does not coexist with WiFi
Has anybody checked if this issue is still present in Ubuntu 15.05? This version use Bluez version 5. -- 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/219057 Title: Bluetooth does not coexist with WiFi Status in bluez package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+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 1427672] Re: System doesn't power off when shutting down
** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763028 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1427672 Title: System doesn't power off when shutting down Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Unknown Bug description: 1. Open the session indicator (cog in top-right) 2. Shut Down... 3. Shut Down 4. The monitors go blank 5. The system doesn't power off (waited 5 minutes) Things which do work - poweroff -f - Changing to a debug shell and shutting down using login1.Manager PowerOff I can't use the system-shutdown/ functionality since shutdown doesn't get that far. I can't SSH in since network is down. I can't switch VT when it's in this state so I'm not able to interact with the system. I can't see anything on the monitors since they are turned off. Any tips on how to get useful debugging information? I'll attach journalctl from the previous boot but the last message is the journal shutting down so it's not that useful I don't think. Also syslog. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 12:57:33 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1427672/+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 219057] Re: Bluetooth does not coexist with WiFi
Hi Jumpa, just edit the file /etc/modprobe.d/iwlwifi.conf and remove de line options iwlwifi 11n_disable=1 bt_coex_active=0 power_save=0 auto_agg=0 swcrypto=1 sudo nano /etc/modprobe.d/iwlwifi.conf -- 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/219057 Title: Bluetooth does not coexist with WiFi Status in “bluez” package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+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 219057] Re: Bluetooth does not coexist with WiFi
Hi! Maybe this can be a workaround: https://answers.launchpad.net/ubuntu/+question/239371 = Try: echo options iwlwifi 11n_disable=1 bt_coex_active=0 power_save=0 auto_agg=0 swcrypto=1 | sudo tee /etc/modprobe.d/iwlwifi.conf /dev/null As one big command. Reboot to test. = I also made a change to enable A2DP in my headset. Before, when I switched to A2DP it didn't worked. = This worked for me: 1) Open /etc/bluetooth/audio.conf gksudo gedit /etc/bluetooth/audio.conf 2) find Enable =... under [General] and delete Socket fron the list [General] Enable = 3) Add this line: Disable = Socket 4) Save 5) Restart the bluetooth service sudo service bluetooth restart 6) Restar pulseaudio for good measure. pulseaudio -k pulseaudio -D 7) Cross Your Fingers and try. = Now I can use my Sony SHB50 on Ubuntu with good sound (A2DP) and my WiFi is working fine. My laptop is a Dell 3450 This is my Wifi Card: 02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34) This is how PulseAudio detected my bluetooth device: pacmd list-cards index: 2 name: bluez_card.94_CE_2C_F8_51_45 driver: module-bluetooth-device.c owner module: 24 properties: device.description = SBH50 device.string = 94:CE:2C:F8:51:45 device.api = bluez device.class = sound device.bus = bluetooth device.form_factor = headset bluez.path = /org/bluez/542/hci0/dev_94_CE_2C_F8_51_45 bluez.class = 0x240404 bluez.name = SBH50 device.icon_name = audio-headset-bluetooth device.intended_roles = phone profiles: hsp: Telefonía Duplex (HSP/HFP) (priority 20, available: unknown) a2dp: Reproducción de Alta Fidelidad (A2DP) (priority 10, available: yes) off: Apagado (priority 0, available: yes) active profile: a2dp sinks: bluez_sink.94_CE_2C_F8_51_45/#4: SBH50 sources: bluez_sink.94_CE_2C_F8_51_45.monitor/#7: Monitor of SBH50 ports: headset-output: Auriculares (priority 0, latency offset 0 usec, available: yes) properties: headset-input: Auriculares (priority 0, latency offset 0 usec, available: unknown) properties: -- 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/219057 Title: Bluetooth does not coexist with WiFi Status in “bluez” package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+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 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)
Maybe this is realated to this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725610 ** Bug watch added: Debian Bug tracker #725610 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725610 ** Also affects: pulseaudio (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725610 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1181106 Title: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) Status in Bluez Utilities: New Status in “pulseaudio” package in Ubuntu: Confirmed Status in “pulseaudio” package in Debian: Unknown Bug description: I upgraded to 13.04 recently and my A2DP profile, which had been working great under 12.10 is suddenly gone. Neither my blueman applet nor the built-in bluetooth manager applet can connect my external bluetooth speaker to the A2DP profile. They can connect to the bluetooth device itself just fine. Steps I'm using: * using blueman, I can connect to the external bluetooth speaker and view the device in the devices listing * I can connect the device to the Audio sink and I get a message saying it is now connected and will show in the PulseAudio mixer * After connecting the external speaker to the audio sink, I can also see the device in the Play sound through listing in the Sound system control panel, but the icon has a circle with a line through it. * but if I right-click the device and choose Audio Profile from the context menu and try to select High Fidelity Playback (A2DP) as the new profile, I get an error message stating failed to change profile to a2dp I've already added Enable=Socket in /etc/bluetooth/audio.conf, without that I can't pair my headset. Now I can pair it, but I can't activate the A2DP profile. When I try to activate it, I see this message in my syslog : pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no transport I tried the kernel 3.9.0 because of a sound problem with my soundcard, this kernel fixed my soundcard problem, but A2DP still doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+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 1287222] Re: openssh-client 6.5 regression bug with certain servers
** Bug watch added: Debian Bug tracker #740307 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740307 ** Also affects: openssh (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740307 Importance: Unknown Status: Unknown ** Also affects: openssh (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1026430 Importance: Unknown Status: Unknown -- 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/1287222 Title: openssh-client 6.5 regression bug with certain servers Status in “openssh” package in Ubuntu: Confirmed Status in “openssh” package in Debian: Unknown Status in “openssh” package in Fedora: Unknown Bug description: Previous working versions of SSH (6.2p2) work fine on certain host machines as follows: penSSH_6.2p2 Ubuntu-6, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to hostname [IPAddress] port 22. debug1: Connection established. debug1: identity file /home/nelsot08/.ssh/identity type -1 debug1: identity file /home/nelsot08/.ssh/identity-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version Cisco-1.25 debug1: no match: Cisco-1.25 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2p2 Ubuntu-6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 24:75:76:a1:80:0e:6c:4e:a8:c4:a6:a9:d3:34:98:18 Warning: Permanently added 'hostname,IPAddress' (RSA) to the list of known hosts. debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received But in 6.5p1 the following bug occurs: OpenSSH_6.5, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to hostname [IPAddress] port 22. debug1: Connection established. debug1: identity file /home/nelsot08/.ssh/identity type -1 debug1: identity file /home/nelsot08/.ssh/identity-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_rsa type 1 debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ed25519 type -1 debug1: identity file /home/nelsot08/.ssh/id_ed25519-cert type -1 debug1: Remote protocol version 2.0, remote software version Cisco-1.25 debug1: no match: Cisco-1.25 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.5p1 Ubuntu-4 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102430728192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Connection closed by IPAddress This is a regression and there are multiple references to this bug occurring previously: http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh- client-connection-reset-by-peer/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1287222/+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 1287222] Re: openssh-client 6.5 regression bug with certain servers
Last Modified: Jul 31,2014 Status: Fixed Severity: 3 Moderate Product: Cisco IOS Support Cases: 2 Known Affected Releases: (1) n/a Known Fixed Releases: (6) 15.5(0.6)T 15.4(1)T1.3 15.3(3)S3.4 15.5(0.12)S 15.1(2)SY3.8 15.4(1)T2 -- 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/1287222 Title: openssh-client 6.5 regression bug with certain servers Status in “openssh” package in Ubuntu: Confirmed Status in “openssh” package in Debian: Unknown Status in “openssh” package in Fedora: Unknown Bug description: Previous working versions of SSH (6.2p2) work fine on certain host machines as follows: penSSH_6.2p2 Ubuntu-6, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to hostname [IPAddress] port 22. debug1: Connection established. debug1: identity file /home/nelsot08/.ssh/identity type -1 debug1: identity file /home/nelsot08/.ssh/identity-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version Cisco-1.25 debug1: no match: Cisco-1.25 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2p2 Ubuntu-6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 24:75:76:a1:80:0e:6c:4e:a8:c4:a6:a9:d3:34:98:18 Warning: Permanently added 'hostname,IPAddress' (RSA) to the list of known hosts. debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received But in 6.5p1 the following bug occurs: OpenSSH_6.5, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to hostname [IPAddress] port 22. debug1: Connection established. debug1: identity file /home/nelsot08/.ssh/identity type -1 debug1: identity file /home/nelsot08/.ssh/identity-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_rsa type 1 debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ed25519 type -1 debug1: identity file /home/nelsot08/.ssh/id_ed25519-cert type -1 debug1: Remote protocol version 2.0, remote software version Cisco-1.25 debug1: no match: Cisco-1.25 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.5p1 Ubuntu-4 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102430728192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Connection closed by IPAddress This is a regression and there are multiple references to this bug occurring previously: http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh- client-connection-reset-by-peer/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1287222/+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 1287222] Re: openssh-client 6.5 regression bug with certain servers
Bug was fixed https://tools.cisco.com/bugsearch/bug/CSCuo76464 (sorry, you need Cisco account). So, I think that this is not a bug, but a configuration incompatibility. Simple explanation: openSSH require more security and external ssh server is not using this level of security. -- 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/1287222 Title: openssh-client 6.5 regression bug with certain servers Status in “openssh” package in Ubuntu: Confirmed Status in “openssh” package in Debian: Unknown Status in “openssh” package in Fedora: Unknown Bug description: Previous working versions of SSH (6.2p2) work fine on certain host machines as follows: penSSH_6.2p2 Ubuntu-6, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to hostname [IPAddress] port 22. debug1: Connection established. debug1: identity file /home/nelsot08/.ssh/identity type -1 debug1: identity file /home/nelsot08/.ssh/identity-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version Cisco-1.25 debug1: no match: Cisco-1.25 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2p2 Ubuntu-6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 24:75:76:a1:80:0e:6c:4e:a8:c4:a6:a9:d3:34:98:18 Warning: Permanently added 'hostname,IPAddress' (RSA) to the list of known hosts. debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received But in 6.5p1 the following bug occurs: OpenSSH_6.5, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to hostname [IPAddress] port 22. debug1: Connection established. debug1: identity file /home/nelsot08/.ssh/identity type -1 debug1: identity file /home/nelsot08/.ssh/identity-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_rsa type 1 debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ed25519 type -1 debug1: identity file /home/nelsot08/.ssh/id_ed25519-cert type -1 debug1: Remote protocol version 2.0, remote software version Cisco-1.25 debug1: no match: Cisco-1.25 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.5p1 Ubuntu-4 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102430728192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Connection closed by IPAddress This is a regression and there are multiple references to this bug occurring previously: http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh- client-connection-reset-by-peer/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1287222/+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
