[Touch-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
Just to give a data point, mesa/23.3.3-1ubuntu1 fixes many issues with snaps and LibGL on my laptop, namely: - white blank screen when opening firmware-updater snap - no OpenGL hardware acceleration but software rendering only in chromium snap, and missing background effect in Google Meet because of that - Zoom snap wouldn't start with "Failed to create OpenGL context" And by installing the ubuntu-desktop-installer snap by hand after updating to mesa/23.3.3-1ubuntu1, I don't see the white blank window any longer. I'm pretty sure the issue will go away when mesa/23.3.3-1ubuntu1 gets promoted to noble from noble-proposed and a new image gets built. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Committed Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
fwiw, this worked for me with 22.04 LTS ISO. #cloud-config autoinstall: version: 1 identity: hostname: ubuntu-server username: ubuntu # password=ubuntu password: "$6$exDY1mhS4KUYCE/2$zmn9ToZwTKLhCw.b4/b.ZRTIZM30JZ4QrOQ2aOXJ8yk96xpcCof0kxKwuX1kqLG/ygbJ1f8wxED22bTL4F46P0" ssh: install-server: yes # https://launchpad.net/bugs/1974483 allow-pw: no -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Jammy: Confirmed Bug description: With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+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 1987252] Re: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections
** Description changed: - When running a laptop with a mesh WiFi network, frequent disconnections - happen like 10 to 20 times per hour. And the issue has disappeared by + When running a laptop with a mesh WiFi network, frequent errors/notices + are recorded on an access point. And the issue has disappeared by applying the following patch. https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6 > RRM: Include passive channels in active beacon report scan > When receiving a beacon report request with the mode set to active, > channels that are marked as NO_IR were not added to the scan request. > However, active mode just mean that active scan is allowed, but not > that it is a must, so these channels should not be omitted. > Include channels that are marked as NO_IR in the scan request even > if the mode is set to active. So I'd like to request a backport of it. I believe the following combination of parameters is the key to trigger the "Beacon request: No valid channels" issue. - two or more access points as a mesh with 802.11k/v enabled - wpasupplicant 2.10 series or lower - - kinetic with wpasupplicant=2.10-9ubuntu1 - - jammy and wpasupplicant=2:2.10-6ubuntu2 - - or lower - - Using 5GHz - - and all of 5GHz channels are marked as: - - NO_IR (sudo wpa_cli get_capability freq) - - or PASSIVE-SCAN (iw reg get) + - kinetic with wpasupplicant=2.10-9ubuntu1 - jammy and wpasupplicant=2:2.10-6ubuntu2 + - or lower + - Running two AP in 5GHz + - and all of used 5GHz channels by the APs are marked as: + - NO_IR (sudo wpa_cli get_capability freq) + - or PASSIVE-SCAN (iw reg get) The log has a sudden "Connection to AP lost" with "No beacon heard and the time event is over already" as follows: > kernel: [136930.972759] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136931.217753] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136931.229486] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.234536] wlp3s0: authenticated > kernel: [136931.239353] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.253596] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136931.255411] wlp3s0: associated > kernel: [136931.843561] iwlwifi :03:00.0: No beacon heard and the time event is over already... > kernel: [136931.843650] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136932.067556] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136932.078277] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.085292] wlp3s0: authenticated > kernel: [136932.087341] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.100737] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136932.103238] wlp3s0: associated > kernel: [136932.392477] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by 6c:5a:b0:xx:yy:zz And wpa_supplicant considers it in syslog as: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=6c:5a:b0:xx:yy:zz reason=4 locally_generated=1 By enabling debug of wpa_supplicant with `sudo wpa_cli log_level DEBUG`, I found "Beacon request: No valid channels" message on the client (Ubuntu laptop) at the same timing as 11k measuremrent on the AP every 6 seconds. > Aug 21 14:01:06 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:06 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:06 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:12 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:12 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:12 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:18 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:18 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:18 t480 wpa_supplicant[1613]: Beacon request: No valid channels This suggests that there is a clear disagreement around 11k between the client and the AP. And after applying the patch above, the AP can see the proper response to 11k measurement, and frequent disconnections are not reproducible. > Sun Aug 21 18:15:55 2022 daemon.notice nrd[22822] estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from
[Touch-packages] [Bug 1987252] Re: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections
** Patch added: "rrm-include-passive-channels-in-active-beacon-report-scan.patch" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1987252/+attachment/5610935/+files/rrm-include-passive-channels-in-active-beacon-report-scan.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1987252 Title: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections Status in wpa package in Ubuntu: New Bug description: When running a laptop with a mesh WiFi network, frequent disconnections happen like 10 to 20 times per hour. And the issue has disappeared by applying the following patch. https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6 > RRM: Include passive channels in active beacon report scan > When receiving a beacon report request with the mode set to active, > channels that are marked as NO_IR were not added to the scan request. > However, active mode just mean that active scan is allowed, but not > that it is a must, so these channels should not be omitted. > Include channels that are marked as NO_IR in the scan request even > if the mode is set to active. So I'd like to request a backport of it. I believe the following combination of parameters is the key to trigger the "Beacon request: No valid channels" issue. - two or more access points as a mesh with 802.11k/v enabled - wpasupplicant 2.10 series or lower - kinetic with wpasupplicant=2.10-9ubuntu1 - jammy and wpasupplicant=2:2.10-6ubuntu2 - or lower - Using 5GHz - and all of 5GHz channels are marked as: - NO_IR (sudo wpa_cli get_capability freq) - or PASSIVE-SCAN (iw reg get) The log has a sudden "Connection to AP lost" with "No beacon heard and the time event is over already" as follows: > kernel: [136930.972759] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136931.217753] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136931.229486] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.234536] wlp3s0: authenticated > kernel: [136931.239353] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.253596] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136931.255411] wlp3s0: associated > kernel: [136931.843561] iwlwifi :03:00.0: No beacon heard and the time event is over already... > kernel: [136931.843650] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136932.067556] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136932.078277] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.085292] wlp3s0: authenticated > kernel: [136932.087341] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.100737] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136932.103238] wlp3s0: associated > kernel: [136932.392477] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by 6c:5a:b0:xx:yy:zz And wpa_supplicant considers it in syslog as: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=6c:5a:b0:xx:yy:zz reason=4 locally_generated=1 By enabling debug of wpa_supplicant with `sudo wpa_cli log_level DEBUG`, I found "Beacon request: No valid channels" message on the client (Ubuntu laptop) at the same timing as 11k measuremrent on the AP every 6 seconds. > Aug 21 14:01:06 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:06 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:06 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:12 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:12 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:12 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:18 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:18 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:18 t480 wpa_supplicant[1613]: Beacon request: No valid channels This suggests that there is a clear disagreement around 11k between the client and the AP. And after applying the patch above, the AP can see the proper response to 11k measurement, and frequent disconnections are not reproducible. > Sun Aug 21 18:15:55 2022
[Touch-packages] [Bug 1987252] Re: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections
** Description changed: When running a laptop with a mesh WiFi network, frequent disconnections happen like 10 to 20 times per hour. And the issue has disappeared by applying the following patch. https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6 > RRM: Include passive channels in active beacon report scan > When receiving a beacon report request with the mode set to active, > channels that are marked as NO_IR were not added to the scan request. > However, active mode just mean that active scan is allowed, but not > that it is a must, so these channels should not be omitted. > Include channels that are marked as NO_IR in the scan request even > if the mode is set to active. So I'd like to request a backport of it. - How to reproduce: + I believe the following combination of parameters is the key to trigger + the "Beacon request: No valid channels" issue. - [environment] - two or more access points as a mesh with 802.11k/v enabled - - client with jammy and wpasupplicant=2:2.10-6ubuntu2 or kinetic with wpasupplicant=2.10-9ubuntu1 - - Intel AC 8265 or equivalent generation - - make sure a laptop is power-supply connected - - make sure a WiFi device has "Power Management:off" in `iwconfig` to exclude the influence of power saving features - - use 11ac(5GHz) + - wpasupplicant 2.10 series or lower + - kinetic with wpasupplicant=2.10-9ubuntu1 + - jammy and wpasupplicant=2:2.10-6ubuntu2 + - or lower + - Using 5GHz + - and all of 5GHz channels are marked as: + - NO_IR (sudo wpa_cli get_capability freq) + - or PASSIVE-SCAN (iw reg get) - The log has a sudden "Connection to AP lost" with "No beacon heard and - the time event is over already" as follows: + + The log has a sudden "Connection to AP lost" with "No beacon heard and the time event is over already" as follows: > kernel: [136930.972759] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136931.217753] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136931.229486] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.234536] wlp3s0: authenticated > kernel: [136931.239353] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.253596] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136931.255411] wlp3s0: associated > kernel: [136931.843561] iwlwifi :03:00.0: No beacon heard and the time event is over already... > kernel: [136931.843650] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136932.067556] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136932.078277] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.085292] wlp3s0: authenticated > kernel: [136932.087341] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.100737] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136932.103238] wlp3s0: associated > kernel: [136932.392477] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by 6c:5a:b0:xx:yy:zz And wpa_supplicant considers it in syslog as: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=6c:5a:b0:xx:yy:zz reason=4 locally_generated=1 By enabling debug of wpa_supplicant with `sudo wpa_cli log_level DEBUG`, I found "Beacon request: No valid channels" message on the client (Ubuntu laptop) at the same timing as 11k measuremrent on the AP every 6 seconds. > Aug 21 14:01:06 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:06 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:06 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:12 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:12 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:12 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:18 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:18 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:18 t480 wpa_supplicant[1613]: Beacon request: No valid channels This suggests that there is a clear disagreement around 11k between the client and the AP. And after applying the patch above, the AP can see the proper response to 11k measurement, and frequent disconnections are not reproducible. > Sun Aug 21 18:15:55 2022 daemon.notice nrd[22822]
[Touch-packages] [Bug 1987252] Re: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections
The output above was with Intel Wi-Fi 6 AX201. And another colleague in EU had Intel 8200 series and the output was all *with* NO_IR. > Mode[A] Channels: > 36 = 5180 MHz (NO_IR) > 40 = 5200 MHz (NO_IR) > 44 = 5220 MHz (NO_IR) > 48 = 5240 MHz (NO_IR) > 52 = 5260 MHz (NO_IR) (DFS) > 56 = 5280 MHz (NO_IR) (DFS) > 60 = 5300 MHz (NO_IR) (DFS) > 64 = 5320 MHz (NO_IR) (DFS) > 100 = 5500 MHz (NO_IR) (DFS) > 104 = 5520 MHz (NO_IR) (DFS) > 108 = 5540 MHz (NO_IR) (DFS) > 112 = 5560 MHz (NO_IR) (DFS) > 116 = 5580 MHz (NO_IR) (DFS) > 120 = 5600 MHz (NO_IR) (DFS) > 124 = 5620 MHz (NO_IR) (DFS) > 128 = 5640 MHz (NO_IR) (DFS) > 132 = 5660 MHz (NO_IR) (DFS) > 136 = 5680 MHz (NO_IR) (DFS) > 140 = 5700 MHz (NO_IR) (DFS) > 144 = 5720 MHz (NO_IR) (DFS) > 149 = 5745 MHz (NO_IR) > 153 = 5765 MHz (NO_IR) > 157 = 5785 MHz (NO_IR) > 161 = 5805 MHz (NO_IR) > 165 = 5825 MHz (NO_IR) So it must be dependent on the vendor/model/generation of WiFi cards. In any case, I'm more than happy to offer any information required and test something as necessary. Thanks, ** Description changed: When running a laptop with a mesh WiFi network, frequent disconnections happen like 10 to 20 times per hour. And the issue has disappeared by applying the following patch. https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6 > RRM: Include passive channels in active beacon report scan > When receiving a beacon report request with the mode set to active, > channels that are marked as NO_IR were not added to the scan request. > However, active mode just mean that active scan is allowed, but not > that it is a must, so these channels should not be omitted. > Include channels that are marked as NO_IR in the scan request even > if the mode is set to active. So I'd like to request a backport of it. - How to reproduce: [environment] - - two or more access points as a mesh with 802.11k/v enabled - - client with jammy and wpasupplicant=2:2.10-6ubuntu2 - - make sure a laptop is power-supply connected - - make sure a WiFi device has "Power Management:off" in `iwconfig` to exclude the influence of power saving features + - two or more access points as a mesh with 802.11k/v enabled- client with jammy and wpasupplicant=2:2.10-6ubuntu2 + - make sure a laptop is power-supply connected + - make sure a WiFi device has "Power Management:off" in `iwconfig` to exclude the influence of power saving features - use 11ac(5GHz) - - The log has a sudden "Connection to AP lost" with "No beacon heard and the time event is over already" as follows: + The log has a sudden "Connection to AP lost" with "No beacon heard and + the time event is over already" as follows: > kernel: [136930.972759] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136931.217753] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136931.229486] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.234536] wlp3s0: authenticated > kernel: [136931.239353] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.253596] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136931.255411] wlp3s0: associated > kernel: [136931.843561] iwlwifi :03:00.0: No beacon heard and the time event is over already... > kernel: [136931.843650] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136932.067556] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136932.078277] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.085292] wlp3s0: authenticated > kernel: [136932.087341] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.100737] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136932.103238] wlp3s0: associated > kernel: [136932.392477] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by 6c:5a:b0:xx:yy:zz And wpa_supplicant considers it in syslog as: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=6c:5a:b0:xx:yy:zz reason=4 locally_generated=1 - - By enabling debug of wpa_supplicant with `sudo wpa_cli log_level DEBUG`, I found "Beacon request: No valid channels" message on the client (Ubuntu laptop) at the same timing as 11k measuremrent on the AP every 6 seconds. + By enabling debug of wpa_supplicant with `sudo wpa_cli log_level DEBUG`, + I found "Beacon request: No valid channels" message on the client + (Ubuntu laptop) at the same timing as 11k measuremrent on the AP every 6 + seconds. > Aug 21 14:01:06 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:06 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ - > + > > Aug 21 14:01:06 t480 wpa_supplicant[1613]: Beacon request: No valid channels - > + > > Aug 21
[Touch-packages] [Bug 1987252] Re: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections
I forgot to mention; 2.10-9ubuntu1 in kinetic didn't make a difference so I went down the path of finding a commit in upstream. My colleague in EU kindly shared an output of `sudo wpa_cli get_capability freq` and it had 5GHz channels *without* NO_IR. So the key to reproduce the issue would be regulations set for countries/regions. > Mode[A] Channels: > 36 = 5180 MHz (NO_IR) > 40 = 5200 MHz (NO_IR) > 44 = 5220 MHz (NO_IR) > 48 = 5240 MHz (NO_IR) > 52 = 5260 MHz (NO_IR) (DFS) > 56 = 5280 MHz (NO_IR) (DFS) > 60 = 5300 MHz (NO_IR) (DFS) > 64 = 5320 MHz (NO_IR) (DFS) > 100 = 5500 MHz (NO_IR) (DFS) > 104 = 5520 MHz (NO_IR) (DFS) > 108 = 5540 MHz (NO_IR) (DFS) > 112 = 5560 MHz (NO_IR) (DFS) > 116 = 5580 MHz (NO_IR) (DFS) > 120 = 5600 MHz (NO_IR) (DFS) > 124 = 5620 MHz (NO_IR) (DFS) > 128 = 5640 MHz (NO_IR) (DFS) > 132 = 5660 MHz (NO_IR) (DFS) > 136 = 5680 MHz (NO_IR) (DFS) > 140 = 5700 MHz (NO_IR) (DFS) > 144 = 5720 MHz (NO_IR) (DFS) > 149 = 5745 MHz > 153 = 5765 MHz > 157 = 5785 MHz > 161 = 5805 MHz > 165 = 5825 MHz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1987252 Title: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections Status in wpa package in Ubuntu: New Bug description: When running a laptop with a mesh WiFi network, frequent disconnections happen like 10 to 20 times per hour. And the issue has disappeared by applying the following patch. https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6 > RRM: Include passive channels in active beacon report scan > When receiving a beacon report request with the mode set to active, > channels that are marked as NO_IR were not added to the scan request. > However, active mode just mean that active scan is allowed, but not > that it is a must, so these channels should not be omitted. > Include channels that are marked as NO_IR in the scan request even > if the mode is set to active. So I'd like to request a backport of it. How to reproduce: [environment] - two or more access points as a mesh with 802.11k/v enabled - client with jammy and wpasupplicant=2:2.10-6ubuntu2 - make sure a laptop is power-supply connected - make sure a WiFi device has "Power Management:off" in `iwconfig` to exclude the influence of power saving features - use 11ac(5GHz) The log has a sudden "Connection to AP lost" with "No beacon heard and the time event is over already" as follows: > kernel: [136930.972759] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136931.217753] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136931.229486] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.234536] wlp3s0: authenticated > kernel: [136931.239353] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.253596] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136931.255411] wlp3s0: associated > kernel: [136931.843561] iwlwifi :03:00.0: No beacon heard and the time event is over already... > kernel: [136931.843650] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136932.067556] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136932.078277] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.085292] wlp3s0: authenticated > kernel: [136932.087341] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.100737] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136932.103238] wlp3s0: associated > kernel: [136932.392477] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by 6c:5a:b0:xx:yy:zz And wpa_supplicant considers it in syslog as: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=6c:5a:b0:xx:yy:zz reason=4 locally_generated=1 By enabling debug of wpa_supplicant with `sudo wpa_cli log_level DEBUG`, I found "Beacon request: No valid channels" message on the client (Ubuntu laptop) at the same timing as 11k measuremrent on the AP every 6 seconds. > Aug 21 14:01:06 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:06 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:06 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:12 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:12 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:12 t480 wpa_supplicant[1613]: Beacon request:
[Touch-packages] [Bug 1987252] Re: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections
I've been using the custom build with the patch for one and a half days and it's far stable now. https://launchpad.net/~nobuto/+archive/ubuntu/experimental- packages/+build/24301259/+files/wpasupplicant_2.10-6ubuntu2.1~ppa1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1987252 Title: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections Status in wpa package in Ubuntu: New Bug description: When running a laptop with a mesh WiFi network, frequent disconnections happen like 10 to 20 times per hour. And the issue has disappeared by applying the following patch. https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6 > RRM: Include passive channels in active beacon report scan > When receiving a beacon report request with the mode set to active, > channels that are marked as NO_IR were not added to the scan request. > However, active mode just mean that active scan is allowed, but not > that it is a must, so these channels should not be omitted. > Include channels that are marked as NO_IR in the scan request even > if the mode is set to active. So I'd like to request a backport of it. How to reproduce: [environment] - two or more access points as a mesh with 802.11k/v enabled - client with jammy and wpasupplicant=2:2.10-6ubuntu2 - make sure a laptop is power-supply connected - make sure a WiFi device has "Power Management:off" in `iwconfig` to exclude the influence of power saving features - use 11ac(5GHz) The log has a sudden "Connection to AP lost" with "No beacon heard and the time event is over already" as follows: > kernel: [136930.972759] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136931.217753] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136931.229486] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.234536] wlp3s0: authenticated > kernel: [136931.239353] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.253596] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136931.255411] wlp3s0: associated > kernel: [136931.843561] iwlwifi :03:00.0: No beacon heard and the time event is over already... > kernel: [136931.843650] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136932.067556] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136932.078277] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.085292] wlp3s0: authenticated > kernel: [136932.087341] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.100737] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz (capab=0x1511 status=0 aid=2) > kernel: [136932.103238] wlp3s0: associated > kernel: [136932.392477] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by 6c:5a:b0:xx:yy:zz And wpa_supplicant considers it in syslog as: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=6c:5a:b0:xx:yy:zz reason=4 locally_generated=1 By enabling debug of wpa_supplicant with `sudo wpa_cli log_level DEBUG`, I found "Beacon request: No valid channels" message on the client (Ubuntu laptop) at the same timing as 11k measuremrent on the AP every 6 seconds. > Aug 21 14:01:06 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:06 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:06 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:12 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:12 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:12 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:18 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Aug 21 14:01:18 deco daemon.err nrd[22822] estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:18 t480 wpa_supplicant[1613]: Beacon request: No valid channels This suggests that there is a clear disagreement around 11k between the client and the AP. And after applying the patch above, the AP can see the proper response to 11k measurement, and frequent disconnections are not reproducible. > Sun Aug 21 18:15:55 2022 daemon.notice nrd[22822] estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving
[Touch-packages] [Bug 1987252] [NEW] "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections
Public bug reported: When running a laptop with a mesh WiFi network, frequent disconnections happen like 10 to 20 times per hour. And the issue has disappeared by applying the following patch. https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6 > RRM: Include passive channels in active beacon report scan > When receiving a beacon report request with the mode set to active, > channels that are marked as NO_IR were not added to the scan request. > However, active mode just mean that active scan is allowed, but not > that it is a must, so these channels should not be omitted. > Include channels that are marked as NO_IR in the scan request even > if the mode is set to active. So I'd like to request a backport of it. How to reproduce: [environment] - two or more access points as a mesh with 802.11k/v enabled - client with jammy and wpasupplicant=2:2.10-6ubuntu2 - make sure a laptop is power-supply connected - make sure a WiFi device has "Power Management:off" in `iwconfig` to exclude the influence of power saving features - use 11ac(5GHz) The log has a sudden "Connection to AP lost" with "No beacon heard and the time event is over already" as follows: > kernel: [136930.972759] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136931.217753] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136931.229486] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.234536] wlp3s0: authenticated > kernel: [136931.239353] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136931.253596] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz > (capab=0x1511 status=0 aid=2) > kernel: [136931.255411] wlp3s0: associated > kernel: [136931.843561] iwlwifi :03:00.0: No beacon heard and the time > event is over already... > kernel: [136931.843650] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost > kernel: [136932.067556] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz > kernel: [136932.078277] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.085292] wlp3s0: authenticated > kernel: [136932.087341] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3) > kernel: [136932.100737] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz > (capab=0x1511 status=0 aid=2) > kernel: [136932.103238] wlp3s0: associated > kernel: [136932.392477] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as > advertised by 6c:5a:b0:xx:yy:zz And wpa_supplicant considers it in syslog as: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=6c:5a:b0:xx:yy:zz reason=4 locally_generated=1 By enabling debug of wpa_supplicant with `sudo wpa_cli log_level DEBUG`, I found "Beacon request: No valid channels" message on the client (Ubuntu laptop) at the same timing as 11k measuremrent on the AP every 6 seconds. > Aug 21 14:01:06 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: > Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId > 255 ChanId 48 ESSId 0 > Aug 21 14:01:06 deco daemon.err nrd[22822] > estimatorCmnHandleBeaconReportEvent: Invalid beacon report for > D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:06 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:12 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: > Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId > 255 ChanId 48 ESSId 0 > Aug 21 14:01:12 deco daemon.err nrd[22822] > estimatorCmnHandleBeaconReportEvent: Invalid beacon report for > D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:12 t480 wpa_supplicant[1613]: Beacon request: No valid channels > > Aug 21 14:01:18 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: > Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId > 255 ChanId 48 ESSId 0 > Aug 21 14:01:18 deco daemon.err nrd[22822] > estimatorCmnHandleBeaconReportEvent: Invalid beacon report for > D4:3B:04:XX:YY:ZZ > > Aug 21 14:01:18 t480 wpa_supplicant[1613]: Beacon request: No valid channels This suggests that there is a clear disagreement around 11k between the client and the AP. And after applying the patch above, the AP can see the proper response to 11k measurement, and frequent disconnections are not reproducible. > Sun Aug 21 18:15:55 2022 daemon.notice nrd[22822] > estimatorPerformMeasurement: Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on > channel 48 from serving BSS APId 255 ChanId 48 ESSId 0 > Sun Aug 21 18:15:55 2022 daemon.notice nrd[22822] > wlanifBSteerEventsHandleBeaconReport: Beacon report from D4:3B:04:XX:YY:ZZ: > APId 1 ChanId 48 ESSId 0 bssid 6C:5A:B0:XX:YY:AA rcpi: 104 > Sun Aug 21 18:15:55 2022 daemon.notice nrd[22822] > wlanifBSteerEventsHandleBeaconReport: Beacon report from D4:3B:04:XX:YY:ZZ: > APId 255 ChanId 48 ESSId 0 bssid 6C:5A:B0:XX:YY:BB rcpi: 68 [AP] - TP-Link Deco X60 as the main AP with the bridge mode - another Deco X60 as the sub AP [client] - Intel AC 8265 $ lspci -nnkv | sed -n '/Network/,/^$/p' 03:00.0 Network controller [0280]: Intel
[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
> TL;DR: pipewire-pulse and PulseAudio should *not* be installed at the same time as they serve the same function and applications don't know the difference. This is not the case at least for the default Ubuntu flavor (w/ GNOME). $ curl -s https://cdimages.ubuntu.com/daily-live/current/jammy-desktop-amd64.manifest | egrep 'pipewire|pulseaudio' gstreamer1.0-pipewire:amd64 0.3.44-1 gstreamer1.0-pulseaudio:amd64 1.18.5-1ubuntu3 libpipewire-0.3-0:amd64 0.3.44-1 libpipewire-0.3-common 0.3.44-1 libpipewire-0.3-modules:amd64 0.3.44-1 pipewire:amd64 0.3.44-1 pipewire-bin0.3.44-1 pipewire-media-session 0.4.1-2 pulseaudio 1:15.0+dfsg1-1ubuntu6 pulseaudio-module-bluetooth 1:15.0+dfsg1-1ubuntu6 pulseaudio-utils1:15.0+dfsg1-1ubuntu6 -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5
[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
I can confirm that after stopping pipewire temporarily by: $ systemctl --user stop pipewire.socket pipewire.service The volume level is properly recovered across plugging in and out a headset for example, which is good. Both pulseaudio and pipewire are installed out of the box and running if I'm not mistaken. $ apt show pulseaudio |& grep Task: Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntu-desktop-raspi, kubuntu-desktop, xubuntu-core, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi $ apt show pipewire |& grep Task: Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntu-desktop-raspi, kubuntu-desktop, xubuntu-core, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu:
[Touch-packages] [Bug 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options
>From a duplicate of this bug, as tldr: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1939933 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597 > > > Does that mean that enabling it, would only add some dependencies but > > > not actually do anything? > > > > Yes, a (soft) dependency should probably be added against > > gstreamer1.0-plugins-bad, but as I said, the needed version (>= 1.19) is > > not yet in debian > > https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/commit/b916522382aaa33f216636a292e97cd769ac4093 > > 1.19.1 -- 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/1870829 Title: AptX and AptX HD unavailable as Bluetooth audio quality options Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: Unknown Bug description: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+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 1939933] Re: pulseaudio is not built with AptX support
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
> > Does that mean that enabling it, would only add some dependencies but
> > not actually do anything?
>
> Yes, a (soft) dependency should probably be added against
> gstreamer1.0-plugins-bad, but as I said, the needed version (>= 1.19) is
> not yet in debian
https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/commit/b916522382aaa33f216636a292e97cd769ac4093
> 1.19.1
--
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/1939933
Title:
pulseaudio is not built with AptX support
Status in pulseaudio package in Ubuntu:
New
Status in pulseaudio package in Debian:
Unknown
Bug description:
The changelog mentions AptX, but it's not actually enabled in the
build if I'm not mistaken. Aptx support seems to require gstreamer in
the build dependency at least.
[changelog]
pulseaudio (1:15.0+dfsg1-1ubuntu1) impish; urgency=medium
* New upstream version resynchronized on Debian
- Support for bluetooth LDAC and AptX codecs and HFP profiles for
improved audio quality
[upstream release notes]
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/15.0/#supportforldacandaptxbluetoothcodecsplussbcxqsbcwithhigher-qualityparameters
[meson.build]
bluez5_gst_dep = dependency('gstreamer-1.0', version : '>= 1.14', required :
get_option('bluez5-gstreamer'))
bluez5_gstapp_dep = dependency('gstreamer-app-1.0', required :
get_option('bluez5-gstreamer'))
have_bluez5_gstreamer = false
if bluez5_gst_dep.found() and bluez5_gstapp_dep.found()
have_bluez5_gstreamer = true
cdata.set('HAVE_GSTLDAC', 1)
cdata.set('HAVE_GSTAPTX', 1)
endif
[build log]
https://launchpadlibrarian.net/551304449/buildlog_ubuntu-impish-amd64.pulseaudio_1%3A15.0+dfsg1-1ubuntu1_BUILDING.txt.gz
...
Dependency gstreamer-1.0 skipped: feature gstreamer disabled
Dependency gstreamer-app-1.0 skipped: feature gstreamer disabled
Dependency gstreamer-rtp-1.0 skipped: feature gstreamer disabled
Run-time dependency gstreamer-1.0 found: NO (tried pkgconfig and cmake)
Run-time dependency gstreamer-app-1.0 found: NO (tried pkgconfig and cmake)
...
Enable D-Bus: true
Enable BlueZ 5: true
Enable native headsets:true
Enable ofono headsets:true
Enable GStreamer based codecs: false
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1939933/+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 1939933] Re: pulseaudio is not built with AptX support
** Bug watch added: Debian Bug tracker #991597
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
** Also affects: pulseaudio (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
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/1939933
Title:
pulseaudio is not built with AptX support
Status in pulseaudio package in Ubuntu:
New
Status in pulseaudio package in Debian:
Unknown
Bug description:
The changelog mentions AptX, but it's not actually enabled in the
build if I'm not mistaken. Aptx support seems to require gstreamer in
the build dependency at least.
[changelog]
pulseaudio (1:15.0+dfsg1-1ubuntu1) impish; urgency=medium
* New upstream version resynchronized on Debian
- Support for bluetooth LDAC and AptX codecs and HFP profiles for
improved audio quality
[upstream release notes]
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/15.0/#supportforldacandaptxbluetoothcodecsplussbcxqsbcwithhigher-qualityparameters
[meson.build]
bluez5_gst_dep = dependency('gstreamer-1.0', version : '>= 1.14', required :
get_option('bluez5-gstreamer'))
bluez5_gstapp_dep = dependency('gstreamer-app-1.0', required :
get_option('bluez5-gstreamer'))
have_bluez5_gstreamer = false
if bluez5_gst_dep.found() and bluez5_gstapp_dep.found()
have_bluez5_gstreamer = true
cdata.set('HAVE_GSTLDAC', 1)
cdata.set('HAVE_GSTAPTX', 1)
endif
[build log]
https://launchpadlibrarian.net/551304449/buildlog_ubuntu-impish-amd64.pulseaudio_1%3A15.0+dfsg1-1ubuntu1_BUILDING.txt.gz
...
Dependency gstreamer-1.0 skipped: feature gstreamer disabled
Dependency gstreamer-app-1.0 skipped: feature gstreamer disabled
Dependency gstreamer-rtp-1.0 skipped: feature gstreamer disabled
Run-time dependency gstreamer-1.0 found: NO (tried pkgconfig and cmake)
Run-time dependency gstreamer-app-1.0 found: NO (tried pkgconfig and cmake)
...
Enable D-Bus: true
Enable BlueZ 5: true
Enable native headsets:true
Enable ofono headsets:true
Enable GStreamer based codecs: false
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1939933/+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 1939933] [NEW] pulseaudio is not built with AptX support
Public bug reported:
The changelog mentions AptX, but it's not actually enabled in the build
if I'm not mistaken. Aptx support seems to require gstreamer in the
build dependency at least.
[changelog]
pulseaudio (1:15.0+dfsg1-1ubuntu1) impish; urgency=medium
* New upstream version resynchronized on Debian
- Support for bluetooth LDAC and AptX codecs and HFP profiles for
improved audio quality
[upstream release notes]
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/15.0/#supportforldacandaptxbluetoothcodecsplussbcxqsbcwithhigher-qualityparameters
[meson.build]
bluez5_gst_dep = dependency('gstreamer-1.0', version : '>= 1.14', required :
get_option('bluez5-gstreamer'))
bluez5_gstapp_dep = dependency('gstreamer-app-1.0', required :
get_option('bluez5-gstreamer'))
have_bluez5_gstreamer = false
if bluez5_gst_dep.found() and bluez5_gstapp_dep.found()
have_bluez5_gstreamer = true
cdata.set('HAVE_GSTLDAC', 1)
cdata.set('HAVE_GSTAPTX', 1)
endif
[build log]
https://launchpadlibrarian.net/551304449/buildlog_ubuntu-impish-amd64.pulseaudio_1%3A15.0+dfsg1-1ubuntu1_BUILDING.txt.gz
...
Dependency gstreamer-1.0 skipped: feature gstreamer disabled
Dependency gstreamer-app-1.0 skipped: feature gstreamer disabled
Dependency gstreamer-rtp-1.0 skipped: feature gstreamer disabled
Run-time dependency gstreamer-1.0 found: NO (tried pkgconfig and cmake)
Run-time dependency gstreamer-app-1.0 found: NO (tried pkgconfig and cmake)
...
Enable D-Bus: true
Enable BlueZ 5: true
Enable native headsets:true
Enable ofono headsets:true
Enable GStreamer based codecs: false
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
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/1939933
Title:
pulseaudio is not built with AptX support
Status in pulseaudio package in Ubuntu:
New
Bug description:
The changelog mentions AptX, but it's not actually enabled in the
build if I'm not mistaken. Aptx support seems to require gstreamer in
the build dependency at least.
[changelog]
pulseaudio (1:15.0+dfsg1-1ubuntu1) impish; urgency=medium
* New upstream version resynchronized on Debian
- Support for bluetooth LDAC and AptX codecs and HFP profiles for
improved audio quality
[upstream release notes]
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/15.0/#supportforldacandaptxbluetoothcodecsplussbcxqsbcwithhigher-qualityparameters
[meson.build]
bluez5_gst_dep = dependency('gstreamer-1.0', version : '>= 1.14', required :
get_option('bluez5-gstreamer'))
bluez5_gstapp_dep = dependency('gstreamer-app-1.0', required :
get_option('bluez5-gstreamer'))
have_bluez5_gstreamer = false
if bluez5_gst_dep.found() and bluez5_gstapp_dep.found()
have_bluez5_gstreamer = true
cdata.set('HAVE_GSTLDAC', 1)
cdata.set('HAVE_GSTAPTX', 1)
endif
[build log]
https://launchpadlibrarian.net/551304449/buildlog_ubuntu-impish-amd64.pulseaudio_1%3A15.0+dfsg1-1ubuntu1_BUILDING.txt.gz
...
Dependency gstreamer-1.0 skipped: feature gstreamer disabled
Dependency gstreamer-app-1.0 skipped: feature gstreamer disabled
Dependency gstreamer-rtp-1.0 skipped: feature gstreamer disabled
Run-time dependency gstreamer-1.0 found: NO (tried pkgconfig and cmake)
Run-time dependency gstreamer-app-1.0 found: NO (tried pkgconfig and cmake)
...
Enable D-Bus: true
Enable BlueZ 5: true
Enable native headsets:true
Enable ofono headsets:true
Enable GStreamer based codecs: false
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1939933/+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 388553] Re: Wi-Fi Protected Setup (WPS) not supported
FWIW, I was able to use WPS push botton with 19.10 as of today. There was a message as "Alternatively you can connect by pushing the “WPS” button on your router" and it just worked for me. The UI patch seems merged in upstream 7 months ago. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/329 ** Attachment added: "wps.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/388553/+attachment/5289768/+files/wps.png -- 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/388553 Title: Wi-Fi Protected Setup (WPS) not supported Status in Ayatana Design: New Status in NetworkManager: In Progress Status in network-manager package in Ubuntu: Triaged Bug description: As the title the Wi-Fi Protected Setup (WPS) is not supported by NetworkManager (but is supported by wpa_supplicant). The WPS WI-Fi standard is implementated in various newer access points and allow user to configure the access point in just a few of steps and do all configuring process very simple. Specifications: http://www.wi-fi.org/wifi-protected-setup/ To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/388553/+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 1509829] [NEW] lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc
Public bug reported: When logging into lightdm guest session, mozc gives an error saying "Failed to start Kana/Kanji conversion program. You need to reboot". Thus Japanese text cannot be input. [possibly related messages] 10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 audit(1445787629.866:709): apparmor="DENIED" operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" name="/dev/shm/sem.69ef545277bb" pid=9534 comm="fcitx" requested_mask="l" denied_mask="l" fsuid=120 ouid=120 target="/dev/shm/oFbWJv" 10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 audit(1445787629.870:710): apparmor="DENIED" operation="bind" profile="/usr/lib/lightdm/lightdm-guest-session" pid=9554 comm="mozc_server" family="unix" sock_type="stream" protocol=0 requested_mask="bind" denied_mask="bind" addr="@tmp/.mozc.d23bc799563c3f748fa591c15f46c971.session" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 26 00:45:41 2015 InstallationDate: Installed on 2015-10-25 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1509829 Title: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc Status in lightdm package in Ubuntu: New Bug description: When logging into lightdm guest session, mozc gives an error saying "Failed to start Kana/Kanji conversion program. You need to reboot". Thus Japanese text cannot be input. [possibly related messages] 10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 audit(1445787629.866:709): apparmor="DENIED" operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" name="/dev/shm/sem.69ef545277bb" pid=9534 comm="fcitx" requested_mask="l" denied_mask="l" fsuid=120 ouid=120 target="/dev/shm/oFbWJv" 10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 audit(1445787629.870:710): apparmor="DENIED" operation="bind" profile="/usr/lib/lightdm/lightdm-guest-session" pid=9554 comm="mozc_server" family="unix" sock_type="stream" protocol=0 requested_mask="bind" denied_mask="bind" addr="@tmp/.mozc.d23bc799563c3f748fa591c15f46c971.session" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 26 00:45:41 2015 InstallationDate: Installed on 2015-10-25 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1509829/+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 1509829] Re: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc
output of `journalctl -k`. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1509829/+attachment/4504791/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1509829 Title: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc Status in lightdm package in Ubuntu: New Bug description: When logging into lightdm guest session, mozc gives an error saying "Failed to start Kana/Kanji conversion program. You need to reboot". Thus Japanese text cannot be input. [possibly related messages] 10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 audit(1445787629.866:709): apparmor="DENIED" operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" name="/dev/shm/sem.69ef545277bb" pid=9534 comm="fcitx" requested_mask="l" denied_mask="l" fsuid=120 ouid=120 target="/dev/shm/oFbWJv" 10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 audit(1445787629.870:710): apparmor="DENIED" operation="bind" profile="/usr/lib/lightdm/lightdm-guest-session" pid=9554 comm="mozc_server" family="unix" sock_type="stream" protocol=0 requested_mask="bind" denied_mask="bind" addr="@tmp/.mozc.d23bc799563c3f748fa591c15f46c971.session" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 26 00:45:41 2015 InstallationDate: Installed on 2015-10-25 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1509829/+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 1489730] Re: after upgrading, one finger tap no longer works
** Package changed: unity-settings-daemon (Ubuntu) => ubuntu-settings (Ubuntu) ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Nobuto Murata (nobuto) -- 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/1489730 Title: after upgrading, one finger tap no longer works Status in ubuntu-settings package in Ubuntu: New Bug description: After apt upgrade on wily, one finger tap on touchpad no longer works. libunity-settings-daemon1: - 15.04.1+15.10.20150720-0ubuntu1 + 15.04.1+15.10.20150825-0ubuntu1 libunity-control-center1: - 15.04.0+15.10.20150814-0ubuntu1 + 15.04.0+15.10.20150818-0ubuntu1 unity-settings-daemon: - 15.04.1+15.10.20150720-0ubuntu1 + 15.04.1+15.10.20150825-0ubuntu1 unity-control-center: - 15.04.0+15.10.20150814-0ubuntu1 + 15.04.0+15.10.20150818-0ubuntu1 gnome-settings-daemon-schemas: - 3.14.2-3ubuntu2 + 3.16.2-3ubuntu1 [before the upgrade] $ synclient | grep TapButton TapButton1 = 1 TapButton2 = 3 TapButton3 = 0 [after the upgrade] $ synclient | grep TapButton TapButton1 = 0 TapButton2 = 0 TapButton3 = 0 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-settings-daemon 15.04.1+15.10.20150825-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 28 15:39:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-13 (106 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1489730/+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 1489730] Re: after upgrading, tap-to-click no longer works by default
** Summary changed: - after upgrading, one finger tap no longer works + after upgrading, tap-to-click no longer works by default -- 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/1489730 Title: after upgrading, tap-to-click no longer works by default Status in ubuntu-settings package in Ubuntu: New Bug description: After apt upgrade on wily, one finger tap on touchpad no longer works. libunity-settings-daemon1: - 15.04.1+15.10.20150720-0ubuntu1 + 15.04.1+15.10.20150825-0ubuntu1 libunity-control-center1: - 15.04.0+15.10.20150814-0ubuntu1 + 15.04.0+15.10.20150818-0ubuntu1 unity-settings-daemon: - 15.04.1+15.10.20150720-0ubuntu1 + 15.04.1+15.10.20150825-0ubuntu1 unity-control-center: - 15.04.0+15.10.20150814-0ubuntu1 + 15.04.0+15.10.20150818-0ubuntu1 gnome-settings-daemon-schemas: - 3.14.2-3ubuntu2 + 3.16.2-3ubuntu1 [before the upgrade] $ synclient | grep TapButton TapButton1 = 1 TapButton2 = 3 TapButton3 = 0 [after the upgrade] $ synclient | grep TapButton TapButton1 = 0 TapButton2 = 0 TapButton3 = 0 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-settings-daemon 15.04.1+15.10.20150825-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 28 15:39:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-13 (106 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1489730/+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
Re: [Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK
2015-07-07 0:38 GMT+09:00 Gunnar Hjalmarsson 1468...@bugs.launchpad.net: On 07/06/2015 05:14 PM, Nobuto Murata wrote: On 06/23/2015 07:42 PM, tomoe_musashi wrote: and of course, i still hope that ubuntu could drop those 69-language-selector fontconfig files, just like what F13 did. Can you explain a bit how F13 dropped the files? In Ubuntu, language- selector no longer manages fontconfig files. Actually it does. The Japanese fontconfig files were moved to fonts- takao, but there are still a bunch of 69-language-selector-zh-* files, and I think tomoe_musashi is referring to those. Ah, right. I thought CJK related files were moved when fontconfig-voodoo was dropped. Thanks for the correction. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1468027 Title: change default CJK fonts to Noto CJK Status in fonts-noto package in Ubuntu: New Status in language-selector package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: just realize that fonts-noto-cjk is available in the repository, finally its packaged. i don't really know about korean community. But for Chinese and Japanese community, i think that the answer is clear. noto-cjk is definitely better what we had before, like fonts- wqy and fonts-droid. Android community had received these complains for years, finally they got them fixed on lollipop. Fedora also set it as default chinese font start from F21. and of course, i still hope that ubuntu could drop those 69-language-selector fontconfig files, just like what F13 did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1468027/+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 1468027] Re: change default CJK fonts to Noto CJK
Hello tomoe_musashi, I believe Noto Sans CJK is one of the best fonts available in free/libre licenses for Japanese. However I'm not convinced to set the Noto Sans CJK as default yet and I would like to know your motivations here. But for Chinese and Japanese community, i think that the answer is clear. noto-cjk is definitely better what we had before, like fonts- wqy and fonts-droid. For Japanese locale, what makes you so confident when compared to fonts- takao, the current default font? Android community had received these complains for years, finally they got them fixed on lollipop. Fedora also set it as default chinese font start from F21. Can you point to a link where the discussion happened in Fedora? and of course, i still hope that ubuntu could drop those 69-language- selector fontconfig files, just like what F13 did. Can you explain a bit how F13 dropped the files? In Ubuntu, language- selector no longer manages fontconfig files. Instead font packages have fontconfig files, e.g. /etc/fonts/conf.avail/65-fonts-takao-pgothic.conf in fonts-takao-pgothic. Even with Noto Sans CJK I think we still need to choose font family name per locale such as Noto Sans CJK JP for ja_JP locale. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1468027 Title: change default CJK fonts to Noto CJK Status in fonts-noto package in Ubuntu: New Status in language-selector package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: just realize that fonts-noto-cjk is available in the repository, finally its packaged. i don't really know about korean community. But for Chinese and Japanese community, i think that the answer is clear. noto-cjk is definitely better what we had before, like fonts- wqy and fonts-droid. Android community had received these complains for years, finally they got them fixed on lollipop. Fedora also set it as default chinese font start from F21. and of course, i still hope that ubuntu could drop those 69-language-selector fontconfig files, just like what F13 did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1468027/+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 1430893] Re: [FFe] Install Fcitx for Chinese users
So if @nobuto can tell that using fcitx as default is desired for Japanese users, let's talk with other people on desktop team next week (preferably on IRC). Well, fcitx-anthy(LP: #1356222) and fcitx-mozc are still in universe. No Japanese engine for fcitx to seed is available yet. @ikuya, can you point out severe issues with ibus which justify to hurry migration in this cycle? In my opinion the plan in this FFe description below sounds realistic to me. this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 1430893] Re: [FFe] Install Fcitx for Chinese users
Maybe theoretical, but: If LC_CTYPE is set explicitly, its value is not surrounded by quotes in the locale output. I actually hit this issue and opened an separate bug as LP: #1431862. If you guys intend to fix it in a series of this bug, please mark it as a duplicate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 1377370] Re: ubuntu-desktop should depend on ibus-gtk
It's better to be backported to utopic as well, but I'm not sure if ubuntu-meta can be SRUed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1377370 Title: ubuntu-desktop should depend on ibus-gtk Status in One Hundred Papercuts: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Note that ubuntu-desktop depends on ibus-gtk3 already. Looking at /usr/share/im-config/data/21-ibus.rc GTK_IM_MODULE is only set to ibus if both gtk-2.0 and gtk-3.0 ibus modules are present. Otherwise it's set to xim. If GTK_IM_MODULE=xim and ibus is running, then various bugs happen like LP: #1374721 and LP: #1375742. Installing ibus-gtk makes those problems go away. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-desktop 1.327 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 4 13:49:55 2014 InstallationDate: Installed on 2014-09-03 (30 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1377370/+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 1296487] Re: Initial zoom level is slightly under 100%
It looks like it's no longer reproducible on vivid. I'm not sure where exatly it's fixed. eog: Installed: 3.14.3-1ubuntu2 light-themes: Installed: 14.04+15.04.20150212-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in Eye of GNOME: New Status in eog package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: When opening an image, the zoom level is displayed as 100%, but the image is visibly blurry from being slightly zoomed out. There are a few pixels of black bar on the right and left edges of the image. Expanding the window vertically lets the image display at 1:1 zoom. This occurs with images that should be small enough to be displayed at 100% zoom. For example: a 960x540 image on a 1920x1080 display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 18:06:29 2014 InstallationDate: Installed on 2014-02-16 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1296487/+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 1377370] Re: ubuntu-desktop should depend on ibus-gtk
** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) = Nobuto Murata (nobuto) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1377370 Title: ubuntu-desktop should depend on ibus-gtk Status in One Hundred Papercuts: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Note that ubuntu-desktop depends on ibus-gtk3 already. Looking at /usr/share/im-config/data/21-ibus.rc GTK_IM_MODULE is only set to ibus if both gtk-2.0 and gtk-3.0 ibus modules are present. Otherwise it's set to xim. If GTK_IM_MODULE=xim and ibus is running, then various bugs happen like LP: #1374721 and LP: #1375742. Installing ibus-gtk makes those problems go away. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-desktop 1.327 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 4 13:49:55 2014 InstallationDate: Installed on 2014-09-03 (30 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1377370/+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 1164252] Re: Improve default selection of IBus related packages
From utopic, ibus-gtk no longer be pulled automatically. I have proposed a merge especially for ibus-gtk in bug #1377370. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1164252 Title: Improve default selection of IBus related packages Status in Ubuntu Kylin: Fix Released Status in ubuntu-meta package in Ubuntu: In Progress Bug description: Currently we have: Input methods: * (im-config) * (ibus) * (ibus-gtk3) * (ibus-table) * (ibus-pinyin) * (ibus-pinyin-db-android) This is suboptimal in many ways. 1. ibus-gtk should be included, since we have notable GTK2 applications like Firefox and LibreOffice. 2. ibus-table doesn't provide a working input method by itself, it needs at least one of ibus-table-* package to work. 3. ibus-pinyin is useful for only limited set of people; even Simplified Chinese language support defaults to ibus-sunpinyin while UbuntuKylin and LinuxDeepin (a noteable Ubuntu-based distro in China) switch to Fcitx altogether. The conclusion is that the real workhorse IBus related packages would be pulled by language support. For meta package like ubuntu-desktop, we either leave a barebone IBus (ibus, ibus-gtk, ibus-gtk3) or remove IBus altogether. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1164252/+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 1377370] Re: ubuntu-desktop should depend on ibus-gtk
related: bug #1164252 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1377370 Title: ubuntu-desktop should depend on ibus-gtk Status in One Hundred Papercuts: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Note that ubuntu-desktop depends on ibus-gtk3 already. Looking at /usr/share/im-config/data/21-ibus.rc GTK_IM_MODULE is only set to ibus if both gtk-2.0 and gtk-3.0 ibus modules are present. Otherwise it's set to xim. If GTK_IM_MODULE=xim and ibus is running, then various bugs happen like LP: #1374721 and LP: #1375742. Installing ibus-gtk makes those problems go away. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-desktop 1.327 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 4 13:49:55 2014 InstallationDate: Installed on 2014-09-03 (30 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1377370/+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 1420105] Re: package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1419554 *** https://bugs.launchpad.net/bugs/1419554 ** This bug has been marked a duplicate of bug 1419554 Can't upgrade procps in LXC 1.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1420105 Title: package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in procps package in Ubuntu: New Bug description: Inside a trusty container on vivid host. $ running-in-container lxc $ sudo dpkg --configure -a Setting up procps (1:3.3.9-1ubuntu2.1) ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: error processing package procps (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: procps ProblemType: Package DistroRelease: Ubuntu 14.04 Package: procps 1:3.3.9-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Feb 10 14:20:43 2015 DpkgTerminalLog: Log started: 2015-01-23 00:43:14 Log ended: 2015-01-23 00:43:19 Log started: 2015-02-10 14:20:41 ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: procps Title: package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1420105/+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 1420640] [NEW] upstart job fails to start with limit nofile unlimited unlimited
Public bug reported: Upstart cookbook refers to limit nofile unlimited unlimited. http://upstart.ubuntu.com/cookbook/#limit However it fails to start jobs, for example: $ sudo stop cron $ echo limit nofile unlimited unlimited | sudo tee /etc/init/cron.override $ sudo start cron start: Job failed to start Feb 11 16:02:52 lifebook kernel: [36027.452599] init: Failed to spawn cron main process: unable to set nofile resource limit: Operation not permitted ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 .etc.init.cron.override: limit nofile unlimited unlimited ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 11 16:03:27 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-09 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150207) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny'] modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu/networks/default.xml'] ** Affects: upstart Importance: Undecided Status: New ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Also affects: upstart Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1420640 Title: upstart job fails to start with limit nofile unlimited unlimited Status in Upstart: New Status in upstart package in Ubuntu: New Bug description: Upstart cookbook refers to limit nofile unlimited unlimited. http://upstart.ubuntu.com/cookbook/#limit However it fails to start jobs, for example: $ sudo stop cron $ echo limit nofile unlimited unlimited | sudo tee /etc/init/cron.override $ sudo start cron start: Job failed to start Feb 11 16:02:52 lifebook kernel: [36027.452599] init: Failed to spawn cron main process: unable to set nofile resource limit: Operation not permitted ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 .etc.init.cron.override: limit nofile unlimited unlimited ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 11 16:03:27 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-09 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150207) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny'] modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu/networks/default.xml'] To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1420640/+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 1420105] Re: package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[/var/log/upstart/procps.log] sysctl: setting key kernel.printk: Read-only file system sysctl: setting key net.ipv6.conf.all.use_tempaddr: Read-only file system sysctl: setting key net.ipv6.conf.default.use_tempaddr: Read-only file system sysctl: setting key kernel.kptr_restrict: Read-only file system sysctl: setting key fs.protected_hardlinks: Read-only file system sysctl: setting key fs.protected_symlinks: Read-only file system sysctl: setting key kernel.sysrq: Read-only file system sysctl: setting key net.ipv4.conf.default.rp_filter: Read-only file system sysctl: setting key net.ipv4.conf.all.rp_filter: Read-only file system sysctl: setting key kernel.yama.ptrace_scope: Read-only file system sysctl: setting key vm.mmap_min_addr: Read-only file system sysctl: setting key net.ipv6.conf.all.use_tempaddr: Read-only file system sysctl: setting key net.ipv6.conf.default.use_tempaddr: Read-only file system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1420105 Title: package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in procps package in Ubuntu: New Bug description: Inside a trusty container on vivid host. $ running-in-container lxc $ sudo dpkg --configure -a Setting up procps (1:3.3.9-1ubuntu2.1) ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: error processing package procps (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: procps ProblemType: Package DistroRelease: Ubuntu 14.04 Package: procps 1:3.3.9-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Feb 10 14:20:43 2015 DpkgTerminalLog: Log started: 2015-01-23 00:43:14 Log ended: 2015-01-23 00:43:19 Log started: 2015-02-10 14:20:41 ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: procps Title: package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1420105/+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 1420105] [NEW] package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Inside a trusty container on vivid host. $ running-in-container lxc $ sudo dpkg --configure -a Setting up procps (1:3.3.9-1ubuntu2.1) ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: error processing package procps (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: procps ProblemType: Package DistroRelease: Ubuntu 14.04 Package: procps 1:3.3.9-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Feb 10 14:20:43 2015 DpkgTerminalLog: Log started: 2015-01-23 00:43:14 Log ended: 2015-01-23 00:43:19 Log started: 2015-02-10 14:20:41 ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: procps Title: package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1420105 Title: package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in procps package in Ubuntu: New Bug description: Inside a trusty container on vivid host. $ running-in-container lxc $ sudo dpkg --configure -a Setting up procps (1:3.3.9-1ubuntu2.1) ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: error processing package procps (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: procps ProblemType: Package DistroRelease: Ubuntu 14.04 Package: procps 1:3.3.9-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Feb 10 14:20:43 2015 DpkgTerminalLog: Log started: 2015-01-23 00:43:14 Log ended: 2015-01-23 00:43:19 Log started: 2015-02-10 14:20:41 ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: procps Title: package procps 1:3.3.9-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1420105/+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 1296487] Re: Initial zoom level is slightly under 100%
** Package changed: light-themes (Ubuntu) = ubuntu-themes (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in Eye of GNOME: New Status in “eog” package in Ubuntu: Confirmed Status in “ubuntu-themes” package in Ubuntu: Confirmed Bug description: When opening an image, the zoom level is displayed as 100%, but the image is visibly blurry from being slightly zoomed out. There are a few pixels of black bar on the right and left edges of the image. Expanding the window vertically lets the image display at 1:1 zoom. This occurs with images that should be small enough to be displayed at 100% zoom. For example: a 960x540 image on a 1920x1080 display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 18:06:29 2014 InstallationDate: Installed on 2014-02-16 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1296487/+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 1379441] Re: installation fails when /var/cache/lxc is read-only
overlayfs, sound good. I will try it to see if it works for me without patching. ** Patch removed: lxc_sru_trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229945/+files/lxc_sru_trusty.debdiff ** Patch removed: lxc_utopic.debdiff https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229943/+files/lxc_utopic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1379441 Title: installation fails when /var/cache/lxc is read-only Status in “lxc” package in Ubuntu: Incomplete Bug description: I'm following this guide: https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/ [quote] Now restart “p1″ and you’ll see /var/cache/lxc in there, showing the same thing as you have on the host. Note that if you want the container to only be able to read the data, you can simply add “ro” as a mount flag in the fstab. [/quote] However lxc package installation fails when /var/cache/lxc is read- only. Is it possible to mark chmod 700 /var/cache/lxc in postinst as optional to allow read-only filesystem on /var/cache/lxc? Steps to reproduce: $ sudo lxc-create -t ubuntu-cloud -n bind-mount-ro-test -- --release trusty -S ~/.ssh/id_rsa.pub $ echo 'lxc.aa_profile = lxc-container-default-with-nesting' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config $ echo 'lxc.mount.entry = /var/cache/lxc var/cache/lxc none bind,create=dir,ro' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config [login to the container] $ sudo apt-get install lxc snip Setting up lxc (1.0.5-0ubuntu0.1) ... Setting up lxc dnsmasq configuration. chmod: changing permissions of '/var/cache/lxc': Read-only file system dpkg: error processing package lxc (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of lxc-templates: lxc-templates depends on lxc (= 0.8.0~rc1-4ubuntu43); however: Package lxc is not configured yet. dpkg: error processing package lxc-templates (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: lxc lxc-templates [lxc.postinst] # Up to version 1.0.0~alpha2-0ubuntu4 lxc was installed world # readable. After that version if users want it that way for # convenience, then that's fine. But one time go ahead and # forcibly change the permissions. if dpkg --compare-versions $2 lt 1.0.0~alpha2-0ubuntu5; then chmod 700 /var/lib/lxc chmod 700 /var/cache/lxc fi ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha1-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 10 02:04:01 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-19 (143 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+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 1379441] [NEW] installation fails when /var/cache/lxc is read-only
Public bug reported: I'm following this guide: https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/ [quote] Now restart “p1″ and you’ll see /var/cache/lxc in there, showing the same thing as you have on the host. Note that if you want the container to only be able to read the data, you can simply add “ro” as a mount flag in the fstab. [/quote] However lxc package installation fails when /var/cache/lxc is read-only. Is it possible to mark chmod 700 /var/cache/lxc in postinst as optional to allow read-only filesystem on /var/cache/lxc? Steps to reproduce: $ sudo lxc-create -t ubuntu-cloud -n bind-mount-ro-test -- --release trusty -S ~/.ssh/id_rsa.pub $ echo 'lxc.aa_profile = lxc-container-default-with-nesting' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config $ echo 'lxc.mount.entry = /var/cache/lxc var/cache/lxc none bind,create=dir,ro' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config [login to the container] $ sudo apt-get install lxc snip Setting up lxc (1.0.5-0ubuntu0.1) ... Setting up lxc dnsmasq configuration. chmod: changing permissions of '/var/cache/lxc': Read-only file system dpkg: error processing package lxc (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of lxc-templates: lxc-templates depends on lxc (= 0.8.0~rc1-4ubuntu43); however: Package lxc is not configured yet. dpkg: error processing package lxc-templates (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: lxc lxc-templates [lxc.postinst] # Up to version 1.0.0~alpha2-0ubuntu4 lxc was installed world # readable. After that version if users want it that way for # convenience, then that's fine. But one time go ahead and # forcibly change the permissions. if dpkg --compare-versions $2 lt 1.0.0~alpha2-0ubuntu5; then chmod 700 /var/lib/lxc chmod 700 /var/cache/lxc fi ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha1-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 10 02:04:01 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-19 (143 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1379441 Title: installation fails when /var/cache/lxc is read-only Status in “lxc” package in Ubuntu: New Bug description: I'm following this guide: https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/ [quote] Now restart “p1″ and you’ll see /var/cache/lxc in there, showing the same thing as you have on the host. Note that if you want the container to only be able to read the data, you can simply add “ro” as a mount flag in the fstab. [/quote] However lxc package installation fails when /var/cache/lxc is read- only. Is it possible to mark chmod 700 /var/cache/lxc in postinst as optional to allow read-only filesystem on /var/cache/lxc? Steps to reproduce: $ sudo lxc-create -t ubuntu-cloud -n bind-mount-ro-test -- --release trusty -S ~/.ssh/id_rsa.pub $ echo 'lxc.aa_profile = lxc-container-default-with-nesting' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config $ echo 'lxc.mount.entry = /var/cache/lxc var/cache/lxc none bind,create=dir,ro' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config [login to the container] $ sudo apt-get install lxc snip Setting up lxc (1.0.5-0ubuntu0.1) ... Setting up lxc dnsmasq configuration. chmod: changing permissions of '/var/cache/lxc': Read-only file system dpkg: error processing package lxc (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of lxc-templates: lxc-templates depends on lxc (= 0.8.0~rc1-4ubuntu43); however: Package lxc is not configured yet. dpkg: error processing package lxc-templates (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: lxc lxc-templates [lxc.postinst] # Up to version 1.0.0~alpha2-0ubuntu4 lxc was installed world # readable. After that version if users want it that way for # convenience, then that's fine. But one time go ahead and # forcibly change the permissions. if dpkg --compare-versions $2 lt 1.0.0~alpha2-0ubuntu5; then
[Touch-packages] [Bug 1379441] Re: installation fails when /var/cache/lxc is read-only
** Patch added: lxc_utopic.debdiff https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229943/+files/lxc_utopic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1379441 Title: installation fails when /var/cache/lxc is read-only Status in “lxc” package in Ubuntu: New Bug description: I'm following this guide: https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/ [quote] Now restart “p1″ and you’ll see /var/cache/lxc in there, showing the same thing as you have on the host. Note that if you want the container to only be able to read the data, you can simply add “ro” as a mount flag in the fstab. [/quote] However lxc package installation fails when /var/cache/lxc is read- only. Is it possible to mark chmod 700 /var/cache/lxc in postinst as optional to allow read-only filesystem on /var/cache/lxc? Steps to reproduce: $ sudo lxc-create -t ubuntu-cloud -n bind-mount-ro-test -- --release trusty -S ~/.ssh/id_rsa.pub $ echo 'lxc.aa_profile = lxc-container-default-with-nesting' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config $ echo 'lxc.mount.entry = /var/cache/lxc var/cache/lxc none bind,create=dir,ro' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config [login to the container] $ sudo apt-get install lxc snip Setting up lxc (1.0.5-0ubuntu0.1) ... Setting up lxc dnsmasq configuration. chmod: changing permissions of '/var/cache/lxc': Read-only file system dpkg: error processing package lxc (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of lxc-templates: lxc-templates depends on lxc (= 0.8.0~rc1-4ubuntu43); however: Package lxc is not configured yet. dpkg: error processing package lxc-templates (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: lxc lxc-templates [lxc.postinst] # Up to version 1.0.0~alpha2-0ubuntu4 lxc was installed world # readable. After that version if users want it that way for # convenience, then that's fine. But one time go ahead and # forcibly change the permissions. if dpkg --compare-versions $2 lt 1.0.0~alpha2-0ubuntu5; then chmod 700 /var/lib/lxc chmod 700 /var/cache/lxc fi ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha1-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 10 02:04:01 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-19 (143 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+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 1379441] Re: installation fails when /var/cache/lxc is read-only
--- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ** Patch added: lxc_sru_trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229945/+files/lxc_sru_trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1379441 Title: installation fails when /var/cache/lxc is read-only Status in “lxc” package in Ubuntu: New Bug description: I'm following this guide: https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/ [quote] Now restart “p1″ and you’ll see /var/cache/lxc in there, showing the same thing as you have on the host. Note that if you want the container to only be able to read the data, you can simply add “ro” as a mount flag in the fstab. [/quote] However lxc package installation fails when /var/cache/lxc is read- only. Is it possible to mark chmod 700 /var/cache/lxc in postinst as optional to allow read-only filesystem on /var/cache/lxc? Steps to reproduce: $ sudo lxc-create -t ubuntu-cloud -n bind-mount-ro-test -- --release trusty -S ~/.ssh/id_rsa.pub $ echo 'lxc.aa_profile = lxc-container-default-with-nesting' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config $ echo 'lxc.mount.entry = /var/cache/lxc var/cache/lxc none bind,create=dir,ro' | sudo tee -a /var/lib/lxc/bind-mount-ro-test/config [login to the container] $ sudo apt-get install lxc snip Setting up lxc (1.0.5-0ubuntu0.1) ... Setting up lxc dnsmasq configuration. chmod: changing permissions of '/var/cache/lxc': Read-only file system dpkg: error processing package lxc (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of lxc-templates: lxc-templates depends on lxc (= 0.8.0~rc1-4ubuntu43); however: Package lxc is not configured yet. dpkg: error processing package lxc-templates (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: lxc lxc-templates [lxc.postinst] # Up to version 1.0.0~alpha2-0ubuntu4 lxc was installed world # readable. After that version if users want it that way for # convenience, then that's fine. But one time go ahead and # forcibly change the permissions. if dpkg --compare-versions $2 lt 1.0.0~alpha2-0ubuntu5; then chmod 700 /var/lib/lxc chmod 700 /var/cache/lxc fi ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha1-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 10 02:04:01 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-19 (143 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+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 1346815] Re: lxc-clone causes duplicate MAC address and IP address
You can also easily work around this by adding
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
to your /etc/lxc/default.conf or ~/.local/share/lxc/default.conf.
hmm, /etc/lxc/default.conf already had lxc.network.hwaddr =
00:16:3e:xx:xx:xx in my env. Besides, I have changed the line in
/var/lib/lxc/ORIG_CONTAINER/config. It works for me as a workaround.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1346815
Title:
lxc-clone causes duplicate MAC address and IP address
Status in “lxc” package in Ubuntu:
Fix Committed
Status in “lxc” source package in Trusty:
Triaged
Bug description:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
Expected result:
2 container will have different MAC and IP address each other.
Actual result:
2 container will have duplicate MAC and IP address.
# grep lxc.network.hwaddr /var/lib/lxc/{foo,bar}/config
/var/lib/lxc/foo/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
/var/lib/lxc/bar/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
$ sudo lxc-ls -f
NAME STATEIPV4 IPV6 GROUPS AUTOSTART
-
bar RUNNING 10.0.7.60 - - NO
foo RUNNING 10.0.7.60 - - NO
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lxc 1.1.0~alpha1-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 22 17:56:44 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-19 (64 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1346815/+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 1346815] [NEW] lxc-clone causes duplicate MAC address and IP address
Public bug reported:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
Expected result:
2 container will have different MAC and IP address each other.
Actual result:
2 container will have duplicate MAC and IP address.
# grep lxc.network.hwaddr /var/lib/lxc/{foo,bar}/config
/var/lib/lxc/foo/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
/var/lib/lxc/bar/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
$ sudo lxc-ls -f
NAME STATEIPV4 IPV6 GROUPS AUTOSTART
-
bar RUNNING 10.0.7.60 - - NO
foo RUNNING 10.0.7.60 - - NO
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lxc 1.1.0~alpha1-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 22 17:56:44 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-19 (64 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apparmor apport-bug utopic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1346815
Title:
lxc-clone causes duplicate MAC address and IP address
Status in “lxc” package in Ubuntu:
New
Bug description:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
Expected result:
2 container will have different MAC and IP address each other.
Actual result:
2 container will have duplicate MAC and IP address.
# grep lxc.network.hwaddr /var/lib/lxc/{foo,bar}/config
/var/lib/lxc/foo/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
/var/lib/lxc/bar/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
$ sudo lxc-ls -f
NAME STATEIPV4 IPV6 GROUPS AUTOSTART
-
bar RUNNING 10.0.7.60 - - NO
foo RUNNING 10.0.7.60 - - NO
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lxc 1.1.0~alpha1-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 22 17:56:44 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-19 (64 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1346815/+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 1346815] Re: lxc-clone causes duplicate MAC address and IP address
After installing old packages, it seems a regression between
https://launchpad.net/ubuntu/+source/lxc/1.0.4-0ubuntu2/+build/6098430
and
https://launchpad.net/ubuntu/+source/lxc/1.1.0~alpha1-0ubuntu1/+build/6162946
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1346815
Title:
lxc-clone causes duplicate MAC address and IP address
Status in “lxc” package in Ubuntu:
New
Bug description:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
Expected result:
2 container will have different MAC and IP address each other.
Actual result:
2 container will have duplicate MAC and IP address.
# grep lxc.network.hwaddr /var/lib/lxc/{foo,bar}/config
/var/lib/lxc/foo/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
/var/lib/lxc/bar/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
$ sudo lxc-ls -f
NAME STATEIPV4 IPV6 GROUPS AUTOSTART
-
bar RUNNING 10.0.7.60 - - NO
foo RUNNING 10.0.7.60 - - NO
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lxc 1.1.0~alpha1-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 22 17:56:44 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-19 (64 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1346815/+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
